MGX-8950-Based PNNI Node | Cisco Multiservice Switching Networks

MGX-8950 also contains the PNNI controller in the PXM-45B controller card. The configuration steps for an MGX-8950-based PNNI node bringup and interface configuration are the same as in the MGX-8850 PNNI node we explored in the preceding section. For that reason, not every configuration command is repeated in the following sections.

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

The internal PNNI controller in the MGX-8950 switch looks like Example 10-24.

Example 10-24. Displaying the PNNI Controller Details

 m8950-7b.7.PXM.a > dspcontroller m8950-7b                         System Rev: 03.00   Feb. 20, 2002 03:16:52 GMT MGX8950 (JBP-2)                                      Node Alarm: MAJOR Number of Controllers:        1 Controller Name:              PNNI_8950 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: m8950-7b.7.PXM.a >

The final PNNI configuration for the network is as displayed in Example 10-25.

Example 10-25. Displaying the PNNI Configuration Details

 m8950-7b.7.PXM.a > dsppnni-node node index: 1                      node name: m8950-7b    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.000000000000010002008950.0004c113ba46.01    ATM address...........47.000000000000010002008950.0004c113ba46.01    Peer group id.........64:47.00.0000.0000.0001.0000.0000.00 m8950-7b.7.PXM.a >

The steps to achieve this PNNI configuration are like those for the other two PNNI nodes.

Configuring PNNI Interfaces

After bringing up pnport 5:1.1:1, you have a lowest-level horizontal link in twoWayInside state. That link faces the MGX-8850 PNNI neighbor, as shown in Example 10-26.

Example 10-26. Using the Command dsppnni-neighbor

 m8950-7b.7.PXM.a > dsppnni-neighbor node index    : 1 node name     : m8850-7a Remote node id: 64:160:47.000000000000010002008850.00309409f6ba.01 Neighbor state: FULL    Port count..........         1     SVC RCC index.......         0    RX DS pkts..........         3     TX DS pkts..........         2    RX PTSP pkts........         3     TX PTSP pkts........         3    RX PTSE req pkts....         1     TX PTSE req pkts....         1    RX PTSE ack pkts....         1     TX PTSE ack pkts....         1 m8950-7b.7.PXM.a >

Both MGX-8850 and BPX-SES PNNI nodes' summary addresses are network-reachable. See Example 10-27.

Example 10-27. Using the Command dsppnni-reachable-addr

 m8950-7b.7.PXM.a > dsppnni-reachable-addr network scope...............         0     Advertising node number         2 Exterior............     false ATM addr prefix.....47.0000.0000.0000.0100.0100.8600/104 Transit network id.. Advertising nodeid..64:160:47.000000000000010001008600.00d058ac2828.01 Node name...........SES-3a scope...............         0     Advertising node number         3 Exterior............     false ATM addr prefix.....47.0000.0000.0000.0100.0200.8850/104 Transit network id.. Advertising nodeid..64:160:47.000000000000010002008850.00309409f6ba.01 Node name...........m8850-7a m8950-7b.7.PXM.a >