Specifications

4-54
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches
Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005
Chapter 4 AXSM Card Management
Verifying PNNI Communications
Upnode name............
Type <CR> to continue, Q<CR> to stop:
Upnode ATM addr........00.000000000000000000000000.000000000000.00
Common peer group id...00:00.00.0000.0000.0000.0000.0000.00
M8850_LA.8.PXM.a >
In the dsppnni-link command report, there should be an entry for the port for which you are verifying
communications. The Local Phy Port Id field in this entry displays the port id in the same format shown
in the dsppnports command report. The Hello state reported for the port should be twoWayInside and
the Remote note ID should display the remote node ATM address after the second colon.
In the example, the report shown is for port 1:1.1:11. The Hello state is twoWayInside, and the ATM
address of the node at the other end of the link is
56:160:47.00918100000000036b5e31b3.00036b5e31b3.01 This link is ready to support connections
between the two switches.
Tip If the Hello state for the link is oneWayInside, that side is trying to communicate. Check the status at the
other end. Remember that the configuration at each end of the trunk must be compatible with that on the
other end. For example, if ILMI auto configuration is configured at one end and not at the other, the Hello
state cannot change to twoWayInside or twoWayOutside.
Verifying End-to-End PNNI Communications
When connections between two nodes travel over multiple trunks, use the following steps to verify that
the PNNI communications path is operational.
Step 1 Establish a CLI session using a user name at any access level. When both ends of the communications
path are connected to MGX 8850/8830 switches, you can start the CLI session at either end.
Step 2 To display information on all accessible nodes, enter the dsppnni-node-list command as shown in the
following example:
MGX8850.7.PXM.a > dsppnni-node-list
node # node id node name
------- -------------------------------------------------- ----------
1 56:160:47.00918100000000001a531c2a.00001a531c2a.01 MGX8850
node # node id node name
------- -------------------------------------------------- ----------
2 56:160:47.00918100000000036b5e2bb2.00036b5e2bb2.01 8850_NY
If a switch appears in this list, you have verified communications with it.
Step 3 To display additional information on the local switch, enter the dsppnni-node command. For example.
MGX8850.7.PXM.a > dsppnni-node
node index: 1 node name: MGX8850
Level............... 56 Lowest.............. true
Restricted transit.. off Complex node........ off
Branching restricted on
Admin status........ up Operational status.. up