Troubleshooting guide

6-33
ATM and Layer 3 Switch Router Troubleshooting Guide
OL-1969-01
Chapter 6 Troubleshooting Switch Router ATM Network Connections
Troubleshooting PNNI Peer Group Leaders
If there are problems with nodes or PTSEs within the same peer group, see the troubleshooting
information in the “Checking the Flat Network or the Database Within the Same Peer Group” section on
page 6-31 of this chapter.
If there are problems with PTSEs from higher-level LGNs, confirm the following for the output display:
Step 2 In addition to its peer nodes, check that the display shows all ancestor nodes. If some ancestor nodes are
missing, see the, “Troubleshooting PNNI Peer Group Leaders.”
Step 3 If all ancestor nodes are present, but other peer LGNs are missing at one of the higher-levels, check
which switch router is acting as the ancestor LGN for the affected level, using the show atm pnni
hierarchy network detail command.
Step 4 Use the show atm pnni database local-node node-index command on the ancestor LGN switch router
after determining the locally assigned node number for the affected LGN node. This command shows
the subset of PTSEs that the higher-level LGN has in its database.
Step 5 If the peer LGNs are missing from its database, use the show atm pnni election local-node node-index
peers command to check connectivity to the missing LGNs.
Step 6 If there is no connectivity shown for some LGNs, see the “Troubleshooting PNNI Hierarchical
Networks” section on page 6-47 to isolate problems with the child peer group leader for the missing
uplink. Also, see the Troubleshooting PNNI SVCC-RCC and Higher-level Links.
Step 7 If PTSEs originated by a higher-level LGN show up incorrectly when displayed for a lowest-level LGN,
use the show atm pnni database local-node node-index command to display the higher-level PTSEs for
the ancestor LGN of the affected lowest-level node and for the originating LGN node.
Step 8 If there are differences, use the debug atm pnni flood-packet local-node node-index command on the
originating LGN and on any other affected LGN and child node.
This command shows when PTSEs are being sent and received, along with any error conditions detected.
Step 9 Check to see whether topology or other types of information for a higher-level LGN are incorrect when
displayed on a lowest-level node in another peer group. Use the detail option for the show atm pnni
database local-node node-index command.
This command shows the complete PTSE contents. Determine if the PTSE originates incorrectly or a
problem exists transporting the PTSE to other LGNs or to the lowest-level node.
Step 10 If the PTSE contents for the LGN originator do not accurately represent its child peer group information,
see either the “Troubleshooting PNNI Hierarchical Networks” section on page 6-47 or the “Debugging
Summary Addresses” section on page 6-54, depending on the type of affected PTSE.
Troubleshooting PNNI Peer Group Leaders
This section describes how to troubleshoot the PNNI peer group leader (PGL). In a PNNI network
supported hierarchy, one node within the peer group is elected as the PGL. It summarizes and aggregates
information from the entire peer group and passes that information to its parent LGN node, which
advertises the information in PTSEs to its peer LGNs at the higher hierarchy level.