Cisco Multiservice Switching Networks

The PXM-45-based MGX-8850 is the first multiservice switch that houses the controller in the switch's controller card. This section investigates its configuration.

PNNI Node Bringup: PXM-45-Based MGX-8850

Because the PNNI controller software is bundled in the PXM-45 controller card image, you do not need to configure external interfaces to add the PNNI controller. The controller-switch communication uses internal software interfaces. To add the controller, you only need to use the command addcontroller. See Example 10-10.

Example 10-10. Adding a PNNI Controller in an MGX-8850

m8850-7a.7.PXM.a > addcontroller 2 i 2 7 PNNI_CTRLR m8850-7a.7.PXM.a > dspcontroller m8850-7a System Rev: 03.00 Feb. 20, 2002 01:20:46 GMT MGX8850 Node Alarm: NONE Number of Controllers: 1 Controller Name: PNNI_CTRLR Controller Id: 2 Controller Location: Internal Controller Type: PNNI Controller Logical Slot: 7 Controller Bay Number: 0 Controller Line Number: 0 Controller VPI: 0 Controller VCI: 0 Controller In Alarm: NO Controller Error: m8850-7a.7.PXM.a >

You now configure PNNI as you did with the BPX-SES-based PNNI node. Refer to Example 10-11.

Example 10-11. Configuring the PNNI Parameters

m8850-7a.7.PXM.a > cnfpnni-node 1 -enable false m8850-7a.7.PXM.a > cnfpnni-node 1 -atmAddr 47.000000000000010002008850.00309409f6ba.01 -level 64 m8850-7a.7.PXM.a > cnfpnni-node 1 -nodeId 64:160:47.000000000000010002008850.00309409f6ba.01 m8850-7a.7.PXM.a > cnfpnni-node 1 -pgId 64:47.000000000000010000000000 m8850-7a.7.PXM.a > cnfpnni-node 1 -enable true m8850-7a.7.PXM.a > dsppnni-node node index: 1 node name: m8850-7a Level............... 64 Lowest.............. true Restricted transit.. off Complex node........ off Branching restricted on Admin status........ up Operational status.. up Non-transit for PGL election.. off Node id...............64:160:47.000000000000010002008850.00309409f6ba.01 ATM address...........47.000000000000010002008850.00309409f6ba.01 Peer group id.........64:47.00.0000.0000.0001.0000.0000.00 m8850-7a.7.PXM.a >

You also configure the SPVC prefix. See Example 10-12.

Example 10-12. Changing the SPVC Prefix

m8850-7a.7.PXM.a > cnfspvcprfx -prfx 47.000000000000010002008850 m8850-7a.7.PXM.a >

At this point, your MGX-8850-based PNNI node is configured and operational.

Configuring PNNI Interfaces

You now put together the MGX-8850 end of the PNNI link configuration to connect your two PNNI nodes.

As with the BPX-SES PNNI node, the line, port, and resource partition need to be configured in the controlled switchin this case, AXSM cards. However, there is an extra first step shown in Example 10-13configuring the card SCT in AXSM cards. This step needs to be performed with all the ports administratively down, so it is recommended that you do it before any configuration.

Example 10-13. Changing the AXSM Card SCT

m8850-7a.1.AXSM.a > cnfcdsct 3 m8850-7a.1.AXSM.a >

NOTE

The card SCT is configured in the AXSM slaves but does not exist in BXM slaves. In AXSM slaves, the card SCT contains the templates controlling ATM parameters that apply to traffic between the card you are configuring and other AXSM cards in the switch (going into and out of the midplane). SCT 0 comes bundled with the software image. However, card SCT 3 is highly recommended for the majority of applications because you do not want to perform policing going to the cross-point switch.

You start by upping line 1.2 toward the BPX-SES, adding an NNI port and a resource partition. Refer to Example 10-14. The controller-id needs to be 2, as you configured in the addcontroller command.

Example 10-14. Adding a Port and VSI Partition in an AXSM Card

m8850-7a.1.AXSM.a > upln 1.2 m8850-7a.1.AXSM.a > addport 2 1.2 96000 96000 3 2 m8850-7a.1.AXSM.a > addpart 2 1 2 1000000 1000000 1000000 1000000 0 4095 1 65535 1000 4000 m8850-7a.1.AXSM.a > dspparts if part Ctlr egr egr ingr ingr min max min max min max Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn (.0001%)(.0001%)(.0001%)(.0001%) ----------------------------------------------------------------------------- 2 1 2 1000000 1000000 1000000 1000000 0 4095 1 65535 1000 4000 m8850-7a.1.AXSM.a >

The pnport can now be seen from PNNI software (see Example 10-15), as was learned with VSI interface commands.

Example 10-15. Displaying the PnPorts

m8850-7a.7.PXM.a > dsppnports ... DSPPNPORTSPer-port status summary PortId LogicalId IF status Admin status ILMI state #Conns 7.35 17251107 up up NotApplicable 0 7.36 17251108 up up NotApplicable 0 7.37 17251109 up up NotApplicable 0 7.38 17251110 up up NotApplicable 0 1:1.2:2 16848898 up up NotApplicable 0 m8850-7a.7.PXM.a >

NOTE

The value 1:1.2:2 is the VSI interface physical descriptor ASCII value, and the value 16848898 is the decimal representation of the 32-bit Logical Interface Number (LIN). The command dsppnportidmaps shows the mapping between the two.

In AXSM cards, the physical descriptor is formed as follows: card:bay.line:port, where bay.line refers to the physical line upped with the command upln, and port is the logical port created with the command addport.

You need to enable ILMI in the VSI slave (the AXSM card) using the command upilmi. Refer to Example 10-16.

Example 10-16. Enabling ILMI in the AXSM VSI Slave

m8850-7a.1.AXSM.a > upilmi 2 1 Warning: connections (if any) on port could get rerouted. Do you want to proceed (Yes/No) ? Yes m8850-7a.1.AXSM.a >

You can see that ILMI is running between the MGX-8850 and the BPX-SES PNNI nodes from the BPX-8600 controlled switch displaying neighbor discovery information, as shown in Example 10-17.

Example 10-17. Displaying ILMI Neighbor Discovery from the Switch

b8620-5a TN Cisco BPX 8620 9.3.4L Feb. 19 2002 22:20 GMT Node Neighbor Discovery Port State Protocol Advtise NbrIpAddress NbrIfName 4.3 ACTIVE ILMI Yes 0.0.0.0 atmVirtual.01.1.2.02 Last Command: dspnebdisc Next Command:

However, as mentioned in the preceding section, the PNNI controllers do not poll ILMI from the VSI slaves. To initiate dILMI VSI protocol passthrough, you need to configure the pnports to run pnni10 signaling. See Example 10-18.

Example 10-18. Enabling Distributed ILMI

SES-3a.1.PXM.a > dnpnport 4.3 SES-3a.1.PXM.a > cnfpnportsig 4.3 -nniver pnni10 SES-3a.1.PXM.a > uppnport 4.3

ILMI information is passed through to the controller. See Example 10-19.

Example 10-19. Displaying ILMI Information from the Controller

SES-3a.1.PXM.a > dsppnilmi 4.3 Port: 4.3 Port Type: PNNI Side: symmetric Autoconfig: enable UCSM: disable Secure Link Protocol: enable Change of Attachment Point Procedures: enable Modification of Local Attributes Standard Procedure: enable Addressreg: Permit All VPI: 0 VCI: 16 Max Prefix: 16 Total Prefix: 0 Max Address: 64 Total Address: 0 Resync State: 0 Node Prefix: yes Peer Port Id: 16848898 System_Id : 0.4.222.35.136.192 Peer Addressreg: enable Peer Ip Address : 0.0.0.0 Peer Interface Name : atmVirtual.01.1.2.02 ILMI Link State : UpAndNormal ILMI Version : ilmi40 INFO: No Prefix registered INFO: No ilmi address registered SES-3a.1.PXM.a >

Finally, you also configure line 1.1 in AXSM slot 12 (pnport 12:1.1:1) as PNNI toward the MGX-8950-based PNNI node.

You follow the procedure to configure a PNNI link. You configure the card SCT, line, port, and VSI partition. This PNNI port is configured as Enhanced Virtual NNI (EVNNI) with a VPI range of 10 to 20, different than previous NNI ports. These steps are shown in Example 10-20.

Example 10-20. Configuring SCT, Line, Port and VSI Partition

m8850-7a.12.AXSM.a > dspports ifNum Line Admin Oper. Guaranteed Maximum SCT Id ifType VPI minVPI maxVPI State State Rate Rate (D:dflt (VNNI, (EVNNI,EVUNI) used) VUNI) ----- ---- ----- ----- ---------- --------- ------ ------ ------ ------ ------ 1 1.1 Up Up 600000 600000 3 EVNNI 0 10 20 m8850-7a.12.AXSM.a > dspparts if part Ctlr egr egr ingr ingr min max min max min max Num ID ID GuarBw MaxBw GuarBw MaxBw vpi vpi vci vci conn conn (.0001%)(.0001%)(.0001%)(.0001%) ----------------------------------------------------------------------------- 1 1 2 1000000 1000000 1000000 1000000 10 20 1 65535 1000 4000 m8850-7a.12.AXSM.a >

The different types of ports that can be configured and their characteristics are summarized in Table 10-1.

In BXM slaves on a BPX-SES PNNI node, the ports are either UNI or NNI, as configured with the command cnfport. You specify the VSI VPI usage when you configure the resource partition. You can set up a single VPI, a VPI range, or a full VPI range. It is recommended that you configure single VPI ports as virtual trunks using the commands uptrk and cnfrsrc.