Specifications

2-24
Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide
Release 3, Part Number 78-14788-01 Rev. C0, January 2004
Chapter 2 Configuring General Switch Features
Configuring PNNI Node Parameters
Note The ATM address in the example above shares the same seven most-significant bytes (level 56
peer groups use the first 7 bytes) as the peer group ID example in the previous section, so PNNI
can advertise only the peer group ID outside of the peer group. If the ATM address and peer
group ID used different prefixes, PNNI would have to advertise the node ATM address and the
peer group ID. The ATM address should conform to your ATM address plan. For more
information, refer to the Cisco MGX and SES PNNI Network Planning Guide.
Tip Use the Copy and Paste functions of the terminal session software to copy an existing ATM
address into the command line. Then you can use your editing keys to make changes to the
address before pressing Enter to execute the command.
Step 4 Enable PNNI node operation by entering the following command:
8850_LA.7.PXM.a > cnfpnni-node <node-index> -enable true
Replace <node-index> with the value you used when disabling and reconfiguring the PNNI node.
Step 5 To display the PNNI node configuration, enter the command:
8850_LA.7.PXM.a > dsppnni-node
The switch displays a report similar to the following:
8850_LA.7.PXM.a > dsppnni-node
node index: 1 node name: 8850_LA
Level............... 56 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...............56:160:47.00918100000000001a531c2a.00001a531c2a.01
ATM address...........47.00918100000100001a531c2a.00001a531c2a.01
Peer group id.........56:47.00.9181.0000.0100.0000.0000.00
Setting the PNNI Node ID
The PNNI node ID appears in many CLI displays, including the dsppnni-node command display. The
default node ID is PNNIlevel:160:defaultATMaddress. If you change the PNNI level or the node ATM
address, you should also change the node ID so that the node ID represents the correct PNNI level and
ATM address. This will make it easier to identify the node when using CLI commands because most CLI
commands reference the node ID, not the node ATM address. For example:
8850_LA.7.PXM.a > dsppnni-link
node index : 1
Local port id: 16848897 Remote port id: 16848897
Local Phy Port Id: 1:2.1:1
Type. lowestLevelHorizontalLink Hello state....... twoWayInside
Derive agg........... 0 Intf index........... 16848897
SVC RCC index........ 0 Hello pkt RX......... 22366
Hello pkt TX......... 22178