Troubleshooting guide

6-45
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 4 Check whether the SVCC has the intended remote (LGN) node and rem-node (remote node) name. If it
does not, verify the LGN ancestor information for the child PGL that was the intended remote LGN node.
Step 5 If for an extended period the SVCC setup state (listed for the detail option) is not SVCC_UP, the
following subset of SVCC setup states might indicate correctable conditions:
• WA IT _I NI TI AL —An approximate four-second delay after an uplink PTSE to a new upnode LGN
with a common peer group ID has been received before the SVCC-RCC setup is attempted. The state
should change automatically to another one of the setup states, and no user actions are required.
• WAIT_CONNECT, WAIT_DELAY_RETRY, or WAIT_IMMED_RETRY—An SVC setup request
has been sent to signalling, but the SVC connection has either been released or the connect
confirmation has not been received.
Proceed to the “Troubleshooting SVC Connections on a PNNI Routing Network” section on
page 6-16, keeping in mind that the originating interface is the route processor port for this node
(ATM 0 for a standard switch router). However, if those steps show no signaling debugging
messages, proceed to the “Debugging SVCC-RCC and Higher-level Link Problems” section on
page 6-46.
• WA IT _S ET UP —A called side node that has received an uplink PTSE to a new upnode LGN with a
common PG ID, but it is still waiting for the SVC signaling setup message to arrive from the remote
SVC originator LGN node. Further debugging should take place on the remote side switch router
where the remote LGN resides. Repeat these debugging steps for the remote side switch router.
• WAIT_REL_SYS_BUSY—An internal software condition resulting from a shortage of route
processor processor memory. If this condition persists or recurs, be sure that the route processor card
has sufficient memory to support the software version listed by the show version command.
Checking SVCC-RCC Hello State
Use the following command to check the SVCC-RCC hello state:
Follow these steps to check the SVCC-RCC hello state:
Step 1 Use the show atm pnni svcc-rcc local-node node-index command without the detail option to
determine the SVCC-RCC hello state.
Command Purpose
show atm pnni svcc-rcc [local-node node-index] Confirms the SVCC-RCC hello state.