Troubleshooting guide

6-39
ATM and Layer 3 Switch Router Troubleshooting Guide
OL-1969-01
Chapter 6 Troubleshooting Switch Router ATM Network Connections
Troubleshooting the PNNI Lowest-level Interface
Step 2 Check for the following hello states. They can indicate possible user-correctable conditions if they
remain unchanged for an extended period:
• DOWN—Lower level protocols have indicated that the link is not usable. See the previous sections
for debugging low level interface problems.
• AT TEMP T—No hello messages have been (recently) received from the neighbor, even though the
PNNI RCC PVC is up. Confirm that the remote end of the line (or VP Tunnel) is connected to the
correct port on the intended remote switch router. Also check the status of the interface at the remote
end of the line. For further analysis, see the “Debugging PNNI Hello State at the Lowest-level”
section on page 6-41.
• 1-WAY INSIDE—Hellos have been recently received from a neighbor in the same peer group, but
the neighbor has not yet acknowledged the information sent from this end. Confirm that the listed
remote node and remote port ID are correct. See the “Debugging PNNI Hello State at the
Lowest-level” section on page 6-41.
• 1-WAY OUTSIDE or 2-WAY OUTSIDE—Hellos have been recently received from a neighbor in
another peer group, but no common higher-level peer group has been found.
Step 3 If the neighbor was expected to be in the same peer group, confirm that the remote node has the expected
peer group ID. Use the show atm pnni local-node command on this node and on the neighbor node to
confirm that the lowest-level peer group IDs match.
Note If the neighbor node has multiple hierarchy levels and if one of its higher-levels matches the
level and peer group ID of the lowest-level local node, then it is normal for the Hello to the
lowest-level neighbor to reach the COMMON OUTSIDE state and for a PNNI SVCC-RCC
to also be set up to communicate to the LGN that is at the same level as this node.
Step 4 If the neighbor was supposed to be in another peer group, but the COMMON OUTSIDE state has not
been reached, use the show atm pnni hierarchy network detail command on this node and on the
neighbor node to confirm that a common higher-level peer group ID exists.
Step 5 It might take a minute or two for the higher-level LGNs to come up for some hierarchy configurations
that have multiple higher-levels or do not have interfaces fully up yet at the higher-levels. If a common
higher-level cannot be found after several minutes, see the “Debugging PNNI Hello State at the
Lowest-level” section on page 6-41. Confirm that the peer group IDs appearing in the nodal hierarchy
lists were sent in the individual hello messages on the outside link.
Step 6 If the peer group IDs do not have the expected values, use the show atm pnni local-node command on
the switch routers where the higher-level LGNs are running to confirm that peer group IDs have the
expected values. If not, verify that the peer group IDs have not been configured to nondefault values.
Step 7 Also verify that if the active ATM address has been changed on one of the switch routers, that the
lowest-level node has been disabled and reenabled to reassign the node ID and peer group IDs based on
the active ATM address (unless nondefault values are preferred).
Step 8 If common higher-levels are not running, see the “Troubleshooting PNNI Peer Group Leaders” section
on page 6-33.