Troubleshooting guide

6-42
ATM and Layer 3 Switch Router Troubleshooting Guide
OL-1969-01
Chapter 6 Troubleshooting Switch Router ATM Network Connections
Troubleshooting PNNI SVCC-RCC and Higher-level Links
Step 5 Confirm that transmit messages are shown and have the expected local peer group ID and port ID. The
transmit message contains the word “Tx.”
Hello messages to peer group neighbors should look like this:
PNNI:56.1 Hello at ATM0/0/1: Tx, state 2way_in with node Switch2
NodeId: 56:160:47.00918100000000613E7B2F01.00613E7B2F99.00 Address:
47.00918100000000613E7B2F01.00613E7B2F99.01 PgId: 56:47.0091.8100.0000.0000.0000.0000
Remote: port: ATM0/0/1 (80001000),
NodeId: 56:160:47.0091810000\0000400B0A3081.00400B0A3081.00
Local port: ATM0/0/1 (80001000)all
Hello messages on outside links to another peer group should have the same information as the previous
example, but should include ULIA sequence number, hierarchy list, and aggregation token value.
Step 6 Confirm that receive messages are shown from the neighbor.
The receive message contains the word “Rx.”
Hello messages received from peer group neighbors should look like the following:
PNNI:56.1 Hello at ATM0/0/1: Rx, state 2way_in with node Switch1
NodeId: 56:160:47.00918100000000400B0A3081.00400B0A3081.00
Address: 47.00918100000000400B0A3081.00400B0A3081.01
PgId: 56:47.0091.8100.0000.0000.0000.0000
Remote: port: ATM0/0/1 (80001000), NodeId: 56:160:47.0091810000
Local port: ATM0/0/1 (80001000)
If no receive messages are shown on the local node, but the remote neighbor shows that it is transmitting
them, there is a problem with transporting the message across the PNNI PVC.
When receive messages are shown, but do not match the transmit messages of the remote neighbor, it
indicates that the line (or VP Tunnel) is connected to some remote port, but it is the wrong port.
Hello messages received on outside links from another peer group should have the same information as
in the previous example, but in addition they should show a ULIA sequence number, a hierarchy list and
sequence number, and an aggregation token value.
The hierarchy list can be examined to confirm whether a common peer group ID exists at some level.
Step 7 Look for other PNNI hello debugging error messages that might give further indication of internal or
configuration problems.
Troubleshooting PNNI SVCC-RCC and Higher-level Links
This section describes how to troubleshoot PNNI routing control channel (RCC) between LGNs.
For a network that supports PNNI hierarchy, the PNNI RCC between LGNs (or between an LGN and a
lowest-level node), is a special type of SVC connection (referred to as an SVCC-RCC). After the
SVCC-RCC is set up between the higher-level LGN peers, PNNI hello messages are sent across it.
Each hello message contains information about all of the aggregated links between the local and remote
LGN. Therefore, the following three types of states are kept independently, and all are important for
higher-level links:
• The SVCC-RCC setup state—Tracks the progress of requests to signaling to set up the SVCC-RCC.
• The RCC Hello state—An overall hello state for the RCC link, based on hello messages sent
between the local and remote LGNs.