Troubleshooting guide

6-32
ATM and Layer 3 Switch Router Troubleshooting Guide
OL-1969-01
Chapter 6 Troubleshooting Switch Router ATM Network Connections
Troubleshooting the PNNI Database
In the output from the show atm pnni database command in Step 1 and Step 2, check the following:
Step 1 Whether all nodes in the peer group are shown. If no overlapping sets of partial nodes are shown for two
different nodes in a peer group, it might indicate a peer group partition. Examine the interface status,
using the show atm pnni interface card/subcard/port and show atm pnni neighbor commands for links
and nodes that should connect to the nearest missing node to further isolate the problem.
Step 2 Whether the same PTSEs and similar sequence numbers appear on displays for different switch router
nodes. If they do not, redisplay for the node with the older seq no (sequence number) to see if it gets
updated. If there are differences, use the debug atm pnni flood-packet command on the originating and
other nodes to see when PTSEs are being sent and received, along with any error conditions detected.
Step 3 Whether topology or other types of information for a node are incorrect, when displayed on another
node. If they are not, use the detail option for the show atm pnni database command to display the
complete PTSE contents both on the originating node and on any other node in the peer group. Determine
whether the PTSE originates incorrectly or if there is a problem in synchronizing and flooding the PTSE
to the other node.
Checking the PNNI Hierarchical Network Database for Different Peer Groups
A logical group node (LGN) originates PTSEs, which summarize the information from the entire child
peer group it represents. The PTSEs that an LGN receives from its peer LGNs are flooded down to its
child peer group leader (PGL), which then floods the PTSEs to its peers.
Use the following commands to check the PNNI hierarchy network database configuration:
Follow these steps to troubleshoot hierarchy database problems:
Step 1 Use the show atm pnni database internal-node-number detail command on the lowest-level node to
confirm that the PTSEs were originated by all lowest-level nodes in the peer group, its higher-level
ancestor LGNs, and the PTSEs from all peers of the ancestor LGNs.
Note Use the show atm pnni hierarchy network command to determine the higher-level
ancestors for a node.
Command Purpose
show atm pnni database [internal-node-number]
[detail]
Confirms that the PTSEs originated by all
lowest-level nodes in its peer group, its
higher-level ancestor LGNs, and all peers
of the ancestor LGNs.
show atm pnni election local-node node-index
peers
Confirms the PNNI PGL election process
configuration.
show atm pnni database local-node
[internal-node-number]
Confirms the contents of the PNNI
topology database of the specified node.
debug atm pnni flood-packet local-node
node-index
Debugs PNNI flood related packets for
the local node.