Troubleshooting guide

6-47
ATM and Layer 3 Switch Router Troubleshooting Guide
OL-1969-01
Chapter 6 Troubleshooting Switch Router ATM Network Connections
Troubleshooting PNNI Hierarchical Networks
The debug atm pnni svcc-rcc remote-node internal-node-number command is normally more helpful
when used on the switch router that has the higher numbered LGN node ID, because that is the SVC
originator (for example, the calling side). However, it is useful to display the debugging hello messages
at both ends for debugging RCC hello problems.
Step 2 Wait approximately one minute to allow any SVCC setup retries to be listed and turn off debugging,
using the no debug all command.
Step 3 Scroll to the top of the screen and confirm the following:
If the SVCC-RCC has not yet reached the SVCC_UP state, confirm that a queued ATM_SETUP line is
displayed and make note of the service category. Normally the service category is VBR-NRT, except for
cases where the SVC must traverse a VP tunnel or some link that does not support VBR-NRT.
When the service category changes with each attempt, release messages are being received. This
indicates that no path exists for each attempted service category. Check the topology, using the
show atm pnni topology command to see whether PNNI shows a route to the remote LGN.
Note Of course, the horizontal link between these LGNs is not listed as up in the topology, but the
special case of SVCC-RCC setup does not require an UP status.
Step 4 Check whether the debugging line following the queued ATM_SETUP phrase shows the ATM address
of the intended remote LGN node. If it does not, these messages might belong to the SVCC-RCC for
another remote LGN.
If there are no setup attempts for the case where an expected SVCC-RCC has not yet reached the
SVCC_UP state, proceed to the, “Troubleshooting PNNI Hierarchical Networks” section.
If there are setup attempts, but release messages are received for each attempt, note the cause code which
might explain the problem. Proceed to the “Troubleshooting SVC Connections on a PNNI Routing
Network” section on page 6-16, keeping in mind that the origination interface is the route processor port.
Step 5 Note any other debugging error messages that might be printed in SVCC-RCC debugging mode.
For RCC hello FSM problems, the full hello messages are listed, along with the horizontal link extension
entries for all aggregation tokens. By listing the hello messages at both ends of the SVCC-RCC, it is
possible to locate where missing or mismatched information takes place.
Troubleshooting PNNI Hierarchical Networks
This section describes how to troubleshoot PNNI uplink and aggregation problems for hierarchical
networks by the LGN.
Links that connect border nodes between two different peer groups are referred to as outside links. When
the hello state finds a common higher-level ancestor LGN on an outside link, it transitions to the common
outside state. At this time each border node advertises an uplink PTSE to its peer nodes. The uplink
PTSE contains the resource information for both directions of the outside link along with the node ID
and peer group ID of the upnode and the aggregation token for the link.
The PGL uses the uplink PTSE information to aggregate the resource information from all outside links
with the same aggregation token that connects to another peer group. The PGL notifies its parent LGN
whenever there are changes to an uplink status. The parent LGN creates either an induced horizontal link
or an induced uplink for each aggregation token to an upnode at the same or higher-level.