3-68
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 3 Provisioning PXM1E Communication Links
General PXM1E Configuration Procedures
Verifying PNNI Trunk Communications
After you configure both ends of a PNNI trunk, it should be ready to support SVCs and any SPVCs or
SPVPs that are configured. To verify that the trunk is functioning, use the following procedure.
Step 1
Establish a CLI session using a user name at any access level. When both ends of the trunk are connected
to Cisco MGX 8850 (PXM1E/PXM45) switches, you can start the CLI session at either end.
Step 2
If you do not know the line number you are validating, you can view the port and line numbers by
entering the dsppnports command. The first three numbers identify the slot, bay, and line. For example,
port 10:2.1:3 represents slot 10, bay 2, line 1. The remaining number is the interface number assigned
with the addport command.
Step 3
Enter the dsppnni-link command as follows:
mgx8830a.1.PXM.a >
dsppnni-link
The dsppnni-link command displays a report for every PNNI link on the switch. The following example
shows the report for a switch with a single PNNI link.
mgx8830a.1.PXM.a >
dsppnni-link
node index : 1
Local port id: 16845569 Remote port id: 17176579
Local Phy Port Id: 1:2.3:1
Type. lowestLevelHorizontalLink Hello state....... twoWayInside
Derive agg........... 0 Intf index........... 16845569
SVC RCC index........ 0 Hello pkt RX......... 1505
Hello pkt TX......... 1498
Remote node name.......porche
Remote node id.........56:160:47.00918100000000036b5e2b1f.00036b5e2b1f.01
Upnode id..............0:0:00.000000000000000000000000.000000000000.00
Upnode ATM addr........00.000000000000000000000000.000000000000.00
Common peer group id...00:00.00.0000.0000.0000.0000.0000.00
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 above, the report shown is for port 1:1.1:1. The Hello state is twoWayInside, and the ATM
address of the node at the other end of the link is 47.00918100000000107b65f33c.00107b65f33c.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.
