2-26
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 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 PNNI Network Planning Guide for MGX and SES Products.
Tip
Use the Copy and Paste functions of 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:
mgx8850a.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:
mgx8850a.7.PXM.a>
dsppnni-node
The switch displays a report similar to the following example:
mgx8850a.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
