Troubleshooting guide

6-30
ATM and Layer 3 Switch Router Troubleshooting Guide
OL-1969-01
Chapter 6 Troubleshooting Switch Router ATM Network Connections
Troubleshooting the PNNI Database
Troubleshooting the PNNI Database
This section outlines how to troubleshoot the PTSE (PNNI topology state element) database. When the
PNNI topology or prefixes do not accurately reflect the state of other nodes in the network, you have
problems with the PTSE database. All knowledge about other PNNI nodes is contained in the PTSE
databases, which exist independently for each PNNI node in the network.
This section contains the following:
• Checking PNNI Neighbor Database Synchronization
• Checking the Flat Network or the Database Within the Same Peer Group
• Checking the PNNI Hierarchical Network Database for Different Peer Groups
Checking PNNI Neighbor Database Synchronization
When a node first initializes, it exchanges PTSEs with its immediate neighbor peer nodes. The progress
of the database synchronization is tracked by the neighboring peer states.
Use the following commands to check the neighbor nodes and their corresponding states:
Follow these steps to troubleshoot PNNI neighbor database synchronization problems:
Step 1 Use the show atm pnni neighbor command to confirm the neighbor nodes and their corresponding
PNNI states.
Step 2 Check whether a neighboring peer node can reach the full state. If the neighboring peer node does not
reach the full state, the following subset of neighboring peer states might indicate problems if they
remain unchanged for an extended period:
• NPdown—There are no active links (for example, hello state 2way_in) to the neighboring peer. See
the “Checking the PNNI Lowest-Level Interface” section on page 6-36 to debug a known interface
to a neighbor node unable to reach the 2way_in state.
• Negotiating—During this transient state, the neighbors agree upon which is the master (for example,
the higher node ID) and the DS sequence number.
• Exchanging—During this state, the node describes its database by sending database summary
packets containing PTSE headers only. When both adjacent nodes have the complete list of PTSE
headers from the neighbor node, they transition to another state.
• Loading—During this state, the nodes are requesting PTSEs from the neighbor, but at least one has
not been received.
Command Purpose
show atm pnni neighbor Confirms the neighbor nodes and their
corresponding PNNI states.
debug atm pnni adj-event Confirms individual PNNI events being
exchanged.
debug atm pnni adj-packet Confirms individual PNNI packets being
exchanged.
no debug all Turns off all debugging.