|
|
This chapter presents troubleshooting information about connectivity and performance problems in ATM switching network connections. The chapter begins by providing general information about checking the network connections on the ATM switch. It then describes how to troubleshoot network connectivity and performance problems in the following sections:
This section assumes that all physical port connections are working correctly. (See the chapter "Troubleshooting ATM Switch Interface Connections.") Be sure you have confirmed the following:
This section describes troubleshooting permanent virtual paths (PVPs) and permanent virtual circuits (PVCs). PVP and PVC connections are used primarily between buildings as the backbone connection and between frequently accessed hosts, such as the domain name service (DNS) server.
In the example network (see Figure 5-1) the primary PVC configured as the backbone connection between the ATM switch on floor 1 in the administration building and the ATM switch, on floor 1 in the manufacturing building has the following virtual path identifier (VPI) and virtual channel identifier (VCI) numbers:
This section contains the following procedures:
For detailed configuration information see the section "Configure Permanent Virtual Path Connections," in the chapter "Configuring Virtual Connections," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes troubleshooting the PVP and PVC interface status. For detailed interface troubleshooting steps, see the chapter "Troubleshooting ATM Switch Interface Connections."
Use the following command to confirm that the configured PVC interface status is up:
| Command | Task |
|---|---|
show atm status | Confirm the interface status. |
Use the following steps to check the interface status:
Step 1 Use the show atm status command to check the interface PVP status.
Switch# show atm status
NUMBER OF INSTALLED CONNECTIONS: (P2P=Point to Point, P2MP=Point to MultiPoint)
Type PVCs SoftPVCs SVCs TVCs PVPs SoftPVPs SVPs Total
P2P 26 0 1 0 0 0 0 27
P2MP 0 0 0 0 0 0 0 0
TOTAL INSTALLED CONNECTIONS = 27
PER-INTERFACE STATUS SUMMARY AT 16:02:57 UTC Mon May 11 1998:
Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello
Name Status Status Status Reg State State State
------------- -------- ------------ -------- ------------ --------- --------
ATM10/0/0 UP up done UpAndNormal Active LoopErr
ATM10/0/1 UP up done UpAndNormal Active n/a
ATM10/0/2 DOWN down waiting n/a Idle n/a
ATM10/0/3 UP up done UpAndNormal Active LoopErr
ATM10/0/3.80 UP up done UpAndNormal Active LoopErr
ATM10/1/0 DOWN down waiting n/a Idle n/a
ATM10/1/1 UP up done UpAndNormal Active n/a
ATM10/1/2 UP up done UpAndNormal Active LoopErr
ATM10/1/3 UP up done UpAndNormal Active LoopErr
ATM10/1/3.80 UP up done UpAndNormal Active LoopErr
ATM13/0/0 UP up n/a UpAndNormal Idle n/a
Switch#
Step 2 Check the IF status field to confirm that the interface is up. If not, refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 3 Check the Admin Status field to confirm that the interface is up. If not, refer to the chapter "Troubleshooting ATM Switch Interface Connections."
This section describes troubleshooting a PVP and PVC connection VPI and VCI number configuration.
Use the following command to confirm the configured PVC interface VPI and VCI numbers:
| Command | Task |
|---|---|
show atm vc interface atm card/subcard/port vpi vci | Confirm the interface status. |
Use the following steps to check the VPI and VCI numbers configured for the PVC connection:
Step 1 Use the show atm vc interface atm command to confirm VPI and VCI numbers at both ends of the PVC connection between the administration building and the manufacturing building:
AdminFl1Ls1# show atm vc interface atm 3/1/0 50 100 Interface: ATM3/1/0, Type: oc12suni
VPI = 50 VCI = 100 Status: UP Time-since-last-status-change: 5w1d Connection-type: PVC Cast-type: point-to-point Packet-discard-option: disabled Usage-Parameter-Control (UPC): pass Wrr weight: 32 Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable
Cross-connect-interface: ATM0/1/0, Type: oc12suni
Cross-connect-VPI = 75
Cross-connect-VCI = 150 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state: Not-applicable Threshold Group: 5, Cells queued: 0 Rx cells: 0, Tx cells: 0 Tx Clp0:0, Tx Clp1: 0 Rx Clp0:0, Rx Clp1: 0 Rx Upc Violations:0, Rx cell drops:0 Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0 Rx connection-traffic-table-index: 1 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 7113539 Rx scr-clp01: none Rx mcr-clp01: none Rx cdvt: 1024 (from default for interface) Rx mbs: none Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none Tx cdvt: none Tx mbs: none AdminFl1Ls1#
Step 2 Check the VPI and VCI fields. They indicate the VPI and VCI of the PVC connection at the administration building.
Step 3 Check the Cross-connect-interface and Cross-connect-VPI and -VCI fields. They indicate the VPI and VCI of the PVC connection at the manufacturing building.
This section describes troubleshooting a PVP and PVC connection VPI and VCI range configuration.
Use the following commands to check the VPI and VCI range of the PVC connection:
| Command | Task |
|---|---|
show atm ilmi-status atm card/subcard/port | Confirm the range configuration of the PVC and its VPI and VCI numbers. |
Use the following steps to check the VPI and VCI range of the PVC connection at the administration building:
Step 1 Use the show atm ilmi-status atm command to confirm VPI and VCI range of the PVC connection at the administration building.
AdminFl1Ls1# show atm ilmi-status atm 3/1/0 Interface : ATM3/1/0 Interface Type : Private NNI ILMI VCC : (50, 100) ILMI Keepalive : Disabled ILMI State: UpAndNormal Peer IP Addr: 172.20.41.93 Peer IF Name: ATM0/1/1 Peer MaxVPIbits: 8 Peer MaxVCIbits: 14
Peer MaxVPCs: 255 Peer MaxVCCs: 16383 Peer MaxSvccVpi: 255 Peer MinSvccVci: 33 Peer MaxSvpcVpi: 255 Configured Prefix(s) : 47.0091.8100.0000.0040.0b0a.2a81 AdminFl1Ls1#
Step 2 Check the Peer MaxVPCs and Peer MaxVccs fields. They indicate the VPI and VCI range of the PVC connection at the manufacturing building.
Step 3 Use the show atm ilmi-status atm command to confirm VPI and VCI range of the PVC connection at the manufacturing building.
ManuFl1Ls1# show atm ilmi-status atm 0/1/0 Interface : ATM0/1/0 Interface Type : Private NNI ILMI VCC : (75, 150) ILMI Keepalive : Disabled ILMI State: UpAndNormal Peer IP Addr: 172.20.41.93 Peer IF Name: ATM0/1/0 Peer MaxVPIbits: 8 Peer MaxVCIbits: 14
Peer MaxVPCs: 255 Peer MaxVCCs: 16383 Peer MaxSvccVpi: 255 Peer MinSvccVci: 33 Peer MaxSvpcVpi: 255 Configured Prefix(s) : 47.0091.8100.0000.0040.0b0a.2a81 ManuFl1Ls1#
Step 4 Check the Peer MaxVPCs and Peer MaxVccs fields. They indicate the VPI and VCI range of the PVC connection at the administration building.
Step 5 If either the VPI or VCI of the PVC are configured incorrectly, go to the chapter "Configuring Virtual Connections," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes troubleshooting a PVP and PVC connection configured as a unspecified bit rate (UBR) connection.
Use the following commands to confirm UBR PVC and PVP best effort connection limit configuration:
| Command | Task |
|---|---|
show atm interface resource atm card/subcard/port | For UBR connections, confirm connection admission control (CAC) best-effort-limit configuration. |
show atm resource | For VBR and CBR connections, confirm that the resources requested are available. |
Use the following steps to confirm UBR PVC and PVP connections best effort connection limit configuration on the interface.
Step 1 Use the show atm interface resource atm card/subcard/port command to confirm the maximum number best-effort-connection limit configuration number.
Switch# show atm interface resource atm 10/0/0
Resource Management configuration:
Output queues:
Max sizes(explicit cfg): none cbr, none vbr-rt, none vbr-nrt, none abr-ubr
Max sizes(installed): 256 cbr, 256 vbr-rt, 4096 vbr-nrt, 12032 abr-ubr
Efci threshold: 25% cbr, 25% vbr-rt, 25% vbr-nrt, 25% abr, 25% ubr
Discard threshold: 87% cbr, 87% vbr-rt, 87% vbr-nrt, 87% abr, 87% ubr
Abr-relative-rate threshold: 25% abr
Pacing: disabled 0 Kbps rate configured, 0 Kbps rate installed
Service Categories supported: cbr,vbr-rt,vbr-nrt,abr,ubr
Link Distance: 0 kilometers
Controlled Link sharing:
Max aggregate guaranteed services: none RX, none TX
Max bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
none abr RX, none abr TX, none ubr RX, none ubr TX
Min bandwidth: none cbr RX, none cbr TX, none vbr RX, none vbr TX,
none abr RX, none abr TX, none ubr RX, none ubr TX
Best effort connection limit: 10 max connections
Max traffic parameters by service (rate in Kbps, tolerance in cell-times):
Peak-cell-rate RX: none cbr, none vbr, none abr, none ubr
Peak-cell-rate TX: none cbr, none vbr, none abr, none ubr
Sustained-cell-rate: none vbr RX, none vbr TX
Minimum-cell-rate RX: none abr, none ubr
Minimum-cell-rate TX: none abr, none ubr
CDVT RX: none cbr, none vbr, none abr, none ubr
CDVT TX: none cbr, none vbr, none abr, none ubr
MBS: none vbr RX, none vbr TX
Resource Management state:
Cell-counts: 0 cbr, 0 vbr-rt, 0 vbr-nrt, 0 abr-ubr
Available bit rates (in Kbps):
147743 cbr RX, 147743 cbr TX, 147743 vbr RX, 147743 vbr TX,
0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX
Allocated bit rates:
0 cbr RX, 0 cbr TX, 0 vbr RX, 0 vbr TX,
0 abr RX, 0 abr TX, 0 ubr RX, 0 ubr TX
Best effort connections: 1 pvcs, 0 svcs
Switch#
Step 2 Check the Best effort connections limit field max connections number.
Step 3 Check the Best effort connections field to determine the connections established. If there are no connections available, the connection to fails.
To modify the best-effort connection limit see the section "Configure the Limits of Best-Effort Connections," in the chapter "Configuring Resource Management," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes troubleshooting a PVP and PVC connection configured as variable bit rate (VBR) or constant bit rate (CBR) connection.
Use the following commands to confirm the VPI and VPI numbers of the configured PVC:
| Command | Task |
|---|---|
show atm interface resource atm card/subcard/port | For UBR connections, confirm CAC best-effort-limit configuration. |
show atm resource | For VBR and CBR connections, confirm that the resources requested are available. |
This section describes continued troubleshooting of the PVP and PVC connection using debug commands.
Use the following commands to debug the PVC connection management:
| Command | Task |
|---|---|
debug atm conn errors | Enable connection management error debugging. |
debug atm conn events | Enable connection management event debugging. |
undebug all | Disable all debugging. |
This section describes troubleshooting a soft permanent virtual circuit (PVC) configuration. Soft PVCs are used primarily to connect hosts that do not support signalling and cannot use switched virtual circuits (SVCs).
In the example network (see Figure 5-2) the connection between the ATM switch on floor 1 in the administration building and the e-mail server has the following VPI and VCI numbers and ATM address:
This section contains the following procedures:
For detailed information see the section "Configure Soft PVC Connections," in the chapter "Configuring Virtual Connections," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes troubleshooting soft PVC connection interface status.
Use the following command to check soft PVC connection interface status:
| Command | Task |
|---|---|
show atm status | Confirm the interface status is up. |
Use the following steps to confirm the soft PVC interface is up:
Step 1 Use the show atm status command to check the soft PVC interface status.
<TBD Replace>
Switch#show atm status
NUMBER OF INSTALLED CONNECTIONS: (P2P=Point to Point, P2MP=Point to MultiPoint)
Type PVCs SoftPVCs SVCs TVCs PVPs SoftPVPs SVPs Total
P2P 17 0 0 0 0 0 0 17
P2MP 0 0 0 0 0 0 0 0
TOTAL INSTALLED CONNECTIONS = 17
PER-INTERFACE STATUS SUMMARY AT 13:41:00 UTC Tue May 12 1998:
Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello
Name Status Status Status Reg State State State
------------- -------- ------------ -------- ------------ --------- --------
ATM-P0/0/3 UP up waiting n/a none n/a
ATM0/1/0 DOWN down waiting n/a Idle n/a
ATM0/1/1 DOWN down waiting n/a Idle n/a
ATM0/1/2 DOWN down waiting n/a Idle n/a
ATM0/1/3 DOWN down waiting n/a Idle n/a
ATM1/0/0 UP up n/a UpAndNormal Active n/a
ATM1/0/0.80 UP up waiting WaitDevType Idle n/a
ATM1/0/1 DOWN down waiting n/a Idle n/a
ATM1/0/2 DOWN down waiting n/a Idle n/a
ATM1/0/3 UP up done UpAndNormal Active n/a
ATM1/1/0 UP up n/a UpAndNormal Active n/a
ATM1/1/1 DOWN down waiting n/a Idle n/a
ATM1/1/2 DOWN down waiting n/a Idle n/a
ATM1/1/3 UP up done UpAndNormal Active n/a
ATM1/1/3.80 UP up waiting WaitDevType Idle n/a
ATM2/0/0 UP up n/a UpAndNormal Idle n/a
ATM4/1/0 DOWN down waiting n/a Idle n/a
ATM4/1/1 DOWN down waiting n/a Idle n/a
ATM4/1/2 DOWN down waiting n/a Idle n/a
ATM4/1/3 DOWN down waiting n/a Idle n/a
Switch#
Step 2 Confirm that the IF Status field corresponding to the soft PVC interface is UP. f the field is down refer to the previous chapter "Troubleshooting ATM Switch Interface Connections."
Step 3 Confirm that the Admin Status field is up. If the field is down refer to the previous chapter "Troubleshooting ATM Switch Interface Connections."
Step 4 If both fields are UP continue with the following troubleshooting sections.
This section describes troubleshooting soft PVC VPI and VCI numbers and the destination ATM address.
Use the following command to confirm the VPI, VCI, and ATM address of the configured soft PVC:
| Command | Task |
|---|---|
show atm vc interface atm card/subcard/port | Confirm the configuration of VPI, VCI and ATM address numbers of a soft PVC. |
Use the following steps to confirm the VPI, VCI, and ATM address of the configured soft PVC:
Step 1 Use the show atm vc interface atm command to confirm VPI and VCI numbers at both ends of the soft PVC connection between the administration building ATM switch and the e-mail server that does not support signalling:
AdminFl1Ls1# show atm vc interface atm 4/0/0 150 250 Interface: ATM4/0/0, Type: oc3suni
VPI = 150 VCI = 250 Status: NOT CONNECTED Time-since-last-status-change: 00:00:45 Connection-type: SoftVC Cast-type: point-to-point Soft vc location: Source
Remote ATM address: 47.1111.1111.00.1111.1111.1111.1111.1111.1111.1111.00
Remote VPI: 100
Remote VCI: 200
Soft vc call state: Active
Number of soft vc re-try attempts: 4 Slow-retry-interval: 60 seconds Next retry in: 29 seconds Aggregate admin weight: 0 Packet-discard-option: disabled Usage-Parameter-Control (UPC): pass Wrr weight: 32 Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Threshold Group: 5, Cells queued: 0 Rx cells: 0, Tx cells: 0 Tx Clp0:0, Tx Clp1: 0 Rx Clp0:0, Rx Clp1: 0 Rx Upc Violations:0, Rx cell drops:0 Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0 Rx connection-traffic-table-index: 1 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 7113539 Rx scr-clp01: none Rx mcr-clp01: none Rx tolerance: 1024 (from default for interface) Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none Tx tolerance: none AdminFl1Ls1#
Step 2 Check the Remote ATM address. This address should match the ATM address at the other end of the soft PVC connection.
Step 3 Check the VPI and VPI fields. They indicate the VPI and VCI configuration of this interface.
Step 4 Check the Remote VPI and Remote VCI fields. They indicate the VPI and VCI configuration of the interface in the e-mail server.
If you determine that the VPI and VCI configuration is incorrect, refer to the chapter "Configuring Virtual Connections," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Step 5 Check the Soft vc call state field. This field should be Active.
Step 6 Check the Number of soft vc re-try attempts. The number should be 0.
This section describes troubleshooting soft PVC connection management.
Use the following command to check soft PVC connection management:
| Command | Task |
|---|---|
show atm interface atm card/subcard/port | Confirm the interface status and configuration. |
This section describes continued troubleshooting of the soft PVC connection management using debug commands.
Use the following commands to debug the PVC connection management:
| Command | Task |
|---|---|
debug atm conn errors | Enable connection management error debugging. |
debug atm conn events | Enable connection management event debugging. |
undebug all | Disable all debugging. |
This section describes troubleshooting switched virtual circuit (SVC) connections using the show and debug commands. These commands can be used to troubleshoot problems with SVC setup between end systems. SVCs are the most common ATM switch connections and are used between ATM-attached end systems that support signalling. The SVCs are automatically configured on the ATM switch when the cables are connected and the switch is powered on.
In the example network (see Figure 5-3) EndSys1 originates the signalling messages which attempt to establish an SVC connection to EndSys2. In this example, Endsys1 connects directly to ATM switch, named RemDvLs1, over UNI connection at ATM interface 3/1/1. Endsys2 is connected directly to the ATM switch, EngFl1Ls1, over the UNI connection at ATM interface 0/0/0. Both ATM switches connect to other ATM switches using NNI connections.
This section contains the following procedures:
Signalling must be enabled on the originating or terminating interface to allow dynamic configuration of the connection from the UNI attached end systems to the ATM switches. This section describes the process used to check and troubleshoot ILMI/PNNI signalling at the ATM switch.
Use the following commands to check SVC interface status:
| Command | Task |
|---|---|
show atm vc signalling interface atm card/subcard/port detail | Confirm the SVC connection to the intended destination ATM NSAP address. |
show atm vc interface atm card/subcard/port vpi vci | Confirm the destination UNI connection is up, and confirm the correct traffic characteristics are being used. |
Use the following steps to confirm whether there is a new connection of Type SVC from the originating side of the UNI interface to the intended remote or destination ATM NSAP address:
Step 1 Use the show atm vc signalling interface atm 3/1/1 detail command on the originating side.
RemDvLs1# show atm vc signalling interface atm 3/1/1 detail <Display Omited> RemDvLs1#
Step 2 If the connection is up, confirm the correct traffic characteristics using the VPI and VCI listed in the previous command for the SVC to the target ATM NSAP address.
RemDvLs1#show atm vc interface atm 3/1/1 0 18 Interface: ATM3/1/1, Type: oc3suni VPI = 0 VCI = 18 Status: UP <Display Omited> RemDvLs1#
Step 3 If the connection is not UP, or not shown, continue with the following section "Check UNI Interfaces."
This section describes troubleshooting both UNI interfaces at the originating and terminating ends (RemFl1Ls1 ATM 3/1/1and EngFl1Ls1 ATM0/0/0, in this example) of the SVC connection to confirm the interface status is up, has the correct interface type, and the UNI version is compatible with the end system.
Use the following commands to check the UNI configuration on the originating and terminating interfaces of the end systems:
| Command | Task |
|---|---|
show atm interface atm card/subcard/port | Confirm the interface status, UNI type, and UNI version. |
show atm interface atm card/subcard/port status | Confirm the interface ILMI and active signalling (SSCOP) status. |
show running-config | Confirm the interface configuration is valid. |
show atm ilmi-status atm card/subcard/port | Confirm the end systems ATM addresses are registered for the UNI interface. |
Use the following steps to confirm the originating end of the SVC connection (RemFl1Ls1 ATM 3/1/1 in this example) has the correct interface status, type, and UNI version compatible with the end system.
Step 1 Use the show atm interface atm command on the originating end of the SVC connection (RemDvLs1 ATM3/1/1 in this example).
RemDvLs1# show atm interface atm 3/1/1 Interface: ATM3/1/1 Port-type: oc3suni
IF Status: UP Admin Status: up Auto-config: enabled AutoCfgState: completed
IF-Side: Network IF-type: UNI
Uni-type: Private Uni-version: V3.1 Max-VPI-bits: 2 Max-VCI-bits: 10 Max-VP: 255 Max-VC: 16383 ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 3 ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 3 ConfMinSvccVci: 33 CurrMinSvccVci: 33 Svc Upc Intent: pass Signalling: Enabled ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c85.0000.00 Configured virtual links: PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns 2 0 0 0 0 0 0 2 2 Logical ports(VP-tunnels): 0 Input cells: 113971 Output cells: 98053 5 minute input rate: 2000 bits/sec, 4 cells/sec 5 minute output rate: 2000 bits/sec, 4 cells/sec Input AAL5 pkts: 64732, Output AAL5 pkts: 80752, AAL5 crc errors: 0 EngFl1Ls1#
Step 2 Check that the IF Status is UP. If not, refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 3 Check that the IF- type is UNI. If not, refer to the section "Configure UNI interfaces," in the chapter "Configuring Interfaces," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Step 4 Check that the UNI-version is compatible at both end-systems. If not, refer to the section "Configure UNI interfaces," in the chapter "Configuring Interfaces," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Step 5 Next use the show atm interface atm command to confirm the terminating end of the SVC connection (EngFl1Ls1 ATM0/0/0 in this example).
EngFl1Ls1# show atm interface atm 0/0/0 Interface: ATM0/0/0 Port-type: oc3suni
IF Status: UP Admin Status: up Auto-config: enabled AutoCfgState: completed
IF-Side: Network IF-type: UNI
Uni-type: Private Uni-version: V3.1 Max-VPI-bits: 2 Max-VCI-bits: 10 Max-VP: 255 Max-VC: 16383 ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 3 ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 3 ConfMinSvccVci: 33 CurrMinSvccVci: 33 Svc Upc Intent: pass Signalling: Enabled ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c85.0000.00 Configured virtual links: PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns 2 0 0 0 0 0 0 2 2 Logical ports(VP-tunnels): 0 Input cells: 113971 Output cells: 98053 5 minute input rate: 2000 bits/sec, 4 cells/sec 5 minute output rate: 2000 bits/sec, 4 cells/sec Input AAL5 pkts: 64732, Output AAL5 pkts: 80752, AAL5 crc errors: 0 EngFl1Ls1#
Step 6 Check that the IF Status is UP. If not, refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 7 Check that the interface type is UNI. If not, refer to the section "Configure UNI interfaces," in the chapter "Configuring Interfaces," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Step 8 Check that the UNI-version is compatible at both end systems. If not, refer to the section "Configure UNI interfaces," in the chapter "Configuring Interfaces," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Use the following steps to confirm the SVC connections have the correct ILMI and active signalling SSCOP status:
Step 1 Use the show atm interface atm card/subcard/port status command to confirm the originating end of the SVC connection:
RemDvLs1# show atm interface atm 3/1/1 status Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello Name Status Status Status Reg State State State ------------- -------- ------------ -------- ------------ --------- -------- ATM3/1/1 UP up done UpAndNormal Active LoopErr RemDvLs1#
Step 2 Use the show atm interface atm card/subcard/port status command to confirm the terminating end of the SVC connection:
EngFl1Ls1# show atm interface atm 0/0/0 status
Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello
Name Status Status Status Reg State State State
------------- -------- ------------ -------- ------------ --------- --------
ATM0/0/0 UP up done UpAndNormal Active LoopErr
EngFl1Ls1#
Step 3 Check that the IF Status is UP. If not, refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 4 Confirm the ILMI Addr Reg State is UpAndNormal.
Step 5 Confirm the SSCOP State is Active.
If either of these steps indicate a problem, use the show running-config command to check both terminating and originating ends of the SVC connection for a valid configuration. Otherwise, continue with the following checks.
Step 1 Use the show running-config command to check the originating end of the SVC connection for a valid configuration.
Step 2 Use the show running-config command to check the terminating end of the SVC connection for a valid configuration.
Use the following steps to check the addresses registered for the UNI interfaces:
Step 1 If the interfaces support ILMI, use the show atm ilmi-status atm command on the originating end of the SVC to verify that the expected end system ATM addresses are registered for the UNI interfaces:
Step 2 If the interfaces support ILMI, use the show atm ilmi-status atm command on the terminating end of the SVC to verify that the expected end system ATM addresses are registered for the UNI interfaces:
Step 3 Check that the expected end system ATM address are registered for the UNI interfaces.
For interfaces that do not support ILMI, use the show running-config command to verify that a static route has been configured with the correct end system ATM address.
If static route has not been configured, go to the chapter "Initially Configuring the LightStream 1010 ATM Switch," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information. Otherwise, continue with the next phase of SVC troubleshooting if you still have not determined the problem with the SVC configuration.
This section describes using the debug atm sig-all command to troubleshoot the SVC shown in Figure 5-3.
Use the following debug commands to check SVC signalling:
| Command | Task |
|---|---|
debug atm sig-all atm card/subcard/port | Confirm the SVC connection to the intended destination ATM NSAP address. |
undebug all | Turn off debugging. |
Use the following steps to turn on signalling debugging for the originating end ATM switch UNI interface (on RemDvLs1 ATM3/1/1 in this example) and then retry the setup of the SVC from EndSys1.
Step 1 Use the debug atm sig-all atm card/subcard/port command to enable signalling debugging for the originating end ATM switch UNI interface (on RemDvLs1 ATM3/1/1).
Step 2 Retry to set up the SVC from EndSys1.
If no debug printouts occur on ATM switch (RemDvLs1 in this example), then the problem is upstream on either the originating UNI interface, on the originating switch itself, or in EndSys1.
Step 3 If debug printouts do occur, turn off further printouts using the undebug all command.
Step 4 Scroll back up near the beginning of the debug printouts to confirm the following:
This section describes debugging PNNI SVC routing using the debug atm pnni route-all command to troubleshoot the SVC shown in Figure 5-3.
Use the following command to debug PNNI SVC routing:
| Command | Task |
|---|---|
debug atm pnni route-all atm | Confirm the SVC connection PNNI routing. |
undebug all | Turn off debugging. |
Use the following steps to enable PNNI routing debugging for the originating end ATM switch UNI interface (on RemDvLs1 ATM 3/1/1):
Step 1 Use the debug atm pnni route-all command enable PNNI routing debugging for the originating end ATM switch UNI interface.
Step 2 Retry to set up the SVC from EndSys1.
Step 3 Then turn off further debug printouts with an undebug all command.
Examine the printouts to check the following:
Step 4 Check for correct Service Class, correct target address, and at least 1 POA (Point of Attachment) was found for the target Node. If no best match or POAs were found, proceed to the section "Check ATM Routes."
Step 5 Check that at least 1 Ports to Next DTL Node n was found. If no ports were found, check for proper UNI/NNI interface configuration and status on the interfaces to the next indicated node n.
Step 6 If the initial Source Route Reply code is PNNI_SUCCESS and there are further tries with Crankback Set, it indicates that the problem is downstream of this switch. Make a note of the original SOURCE ROUTE, shown as a list of DTLs (Designated Transit Lists, which are lists of node IDs and ports) as well as any calculated port list to the next node. Continue with the section "Check SVC Downstream."
If the Source Route Reply code is other than PNNI_SUCCESS, the actual code gives information about the nature of the problem when routing constraints were not met.
This section describes displaying the list of routes and destination prefixes that the originating end switch, RemFl1Ls1 node in this example, has learned.
Use the following command to list the routes and destination prefixes:
| Command | Task |
|---|---|
show atm route | Display the destination prefixes the originating switch has learned. |
Use the following steps to list the routes learned by the originating end ATM switch UNI interface
Step 1 Use the show atm route command to display a list of routes learned by the originating end ATM switch UNI interface (on RemFl1Ls1 ATM 3/1/1in this example).
Step 2 Confirm that a prefix matching the intended target address is shown with a ST (State) UP. If there is more than one prefix that exactly matches the corresponding prefix of the target address, PNNI will choose the longest matching prefix.
If the longest matching prefix ST is DN (Down) for a node other than node 1, it indicates that there is no connectivity to that node. Continue to the next section "Check PNNI Topology."
Step 3 Confirm that the Node n shown for the longest matching prefix is the terminating ATM switch (EngFl1Ls1 for this example). If PNNI Hierarchy is being used, the node can instead be a logical group node (LGN) ancestor of the terminating ATM switch.
If the wrong node is listed with a matching prefix, check for proper ATM address configuration for the destination switch (EngFl1Ls1 in this example) as well as for its UNI interface and for any hierarchy ancestor LGN.
Step 4 If there is no matching prefix appearing in the list of prefixes reachable from the originating end switch (RemFl1Ls1 in this example) use the show atm route command on the terminating node (EngFl1Ls1 in this example).
If the prefix appears correctly on the terminating node, continue to the section "Check PNNI Topology."
This section describes examining the node and port status listing using the show atm pnni topology and show atm election peers commands. These commands display the actual topology of connected ATM switch nodes that the originating switch node (RemFl1Ls1 in this example) has learned. Confirm that an unbroken path of nodes and links with the status up can be found between the originating and terminating side AMT switches (or for hierarchy, to a terminating end ancestor LGN).
Use the following commands to examining the node PNNI topology and ATM switch connectivity:
| Command | Task |
|---|---|
show atm pnni topology | Display the actual topology of the connected nodes. |
show atm election peers | Display the connectivity to a specific node within a peer group. |
Use the following steps to display the actual topology of the connected ATM switch nodes that the originating switch (RemFl1Ls1 in this example) has learned:
Step 1 Use the show atm pnni topology command to display the actual topology of the connected ATM switch nodes.
Step 2 If the terminating node is not shown or if necessary links are down or missing for an unbroken path, it indicates that the originating switch (RemFl1Ls1 in this example) cannot find a path to the terminating node. Either there is a physical problem at the indicated network failure location, or else PNNI is unable to update its database to reflect the actual network condition.
Step 3 Use the show atm pnni election peer command to confirm whether this node has connectivity to any particular node within the same peer group.
If a peer node is missing or is shown as NO for the Connected column, then PNNI considers that there is no path to that node.
Step 4 Check for physical problems using the show atm pnni interface command on the indicated failing nodes. If no physical problems are shown for the indicated failing nodes, proceed to the section "Troubleshooting PNNI Database Problems."
If an unbroken path does exist based on the topology display, but the PNNI routing debugging showed that the destination was not initially PNNI_SUCCESS, it could mean that there are routing restrictions based on QoS, CAC, scope, or other path constraints that could not be met.
This section describes troubleshooting the SVC connection downstream from the originating node. This section is separated into two parts:
Proceed to the part that best describes your network PNNI configuration.
This section describes troubleshooting an SVC connection downstream in a flat network hierarchy.
Use the following commands to check ATM signalling events on the terminating ATM switch:
| Command | Task |
|---|---|
debug atm sig-events atm card/subcard/port | Confirm the SVC connection from the destination end of the SVC. |
undebug all | Turn off debugging. |
Use the following steps to enable ATM signalling events debugging for the terminating end ATM switch UNI interface (on EngFl1Ls1 ATM 0/0/0):
Step 1 Use the debug atm sig-events atm card/subcard/port command to display signalling events at the terminating end ATM switch UNI interface.
Step 2 Retry to set up the SVC from EndSys1.
Step 3 If no debug printouts occur on terminating switch (EngFl1Ls1 in this example) then the signalling messages are not reaching the terminating node. Check for valid signalling status on the NNI links interconnecting the ATM switch nodes using the show atm status and show atm interface commands.
If debug printouts are shown on the terminating switch (EngFl1Ls1 in this example) the problem has been isolated to either the terminating ATM switch, UNI, or End System.
Step 4 Turn off further debug printouts with undebug all command and scroll up to the beginning of the printouts to confirm the following:
Step 5 Check for valid Called Party Addr and Calling Party Address (or a valid target addr in the ROUTING INTERFACE information). If these are not valid, the printout might be for some other SVC setup.
If ROUTING INTERFACE: err_code shows an err_code other than PNNI success, refer to the "Debug PNNI SVC Routing" process for the terminating switch node (EngFl1Ls1 in this example).
Step 6 Check if there is an Input Event: Rcvd Release printout and look at the following cause = reason and location. This indicates that the problem is downstream on the terminating end system.
This section describes continued troubleshooting of an SVC connection downstream if the network is supporting PNNI hierarchy.
Use the following commands to troubleshoot an SVC connection at the terminating end ATM switch:
| Command | Task |
|---|---|
debug atm sig-events atm card/subcard/port | Determine the Exit Border Node for the local peer group. |
undebug all | Turn off debugging. |
show atm pnni identifiers | Determine the internal node number and name corresponding to the exit border node ID |
Use the following steps to enable ATM signalling events debugging for the terminating end ATM switch UNI interface (on EngFl1Ls1 ATM 3/1/3):
Step 1 Start signalling events debugging with the debug atm sig-events atm card/subcard/port command to display signalling events on terminating end ATM switch UNI interface.
Step 2 Retry to set up the SVC from EndSys1.
Step 3 If no debug printouts occur on terminating switch (EngFl1Ls1 in this example) then the signalling messages are not reaching the terminating node. Check for valid signalling status on the NNI links interconnecting the ATM switch nodes using the show atm status and show atm interface commands.
If debug printouts are shown on the terminating switch (EngFl1Ls1 in this example) the problem has been isolated to either the terminating ATM switch, UNI, or End System.
Step 4 Turn off further debug printouts with undebug all command.
Step 5 Examine the initial SOURCE ROUTE. The last node ID listed for the lowest level DTL (shown as DTL 1>) is the Exit Border Node for the local Peer Group. Make a note of the Exit Border Node ID and port.
Use the following steps to determine the internal node number and name corresponding to the exit border node ID for the terminating end ATM switch UNI interface (EngFl1Ls1 ATM 3/1/3 in this example):
Step 1 Use the show atm pnni identifiers command to determine the internal node number and name corresponding to the exit border node ID.
The (lowest level) neighbor node on the other end of the exit border port is the entry border node for the next peer group.
Step 2 After determining the next entry border node, repeat the troubleshooting steps in the following sections on that node:
Step 3 Repeat these steps on that node and continue until either the terminating peer group is reached or the problem is isolated.
This section deals with the condition when the PNNI topology or prefixes do not accurately reflect the state of other nodes in the network due to problems with the PTSE (PNNI Topology State Element) 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 is separated into the following:
This section describes troubleshooting PNNI neighbor database synchronization problems. 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:
| Command | Task |
|---|---|
show atm pnni neighbor | Confirm the neighbor nodes and their corresponding PNNI states. |
debug atm pnni adj-event | Confirm individual PNNI events being exchanged. |
debug atm pnni adj-packet | Confirm individual PNNI packets being exchanged. |
Use the following 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 if 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:
If the neighbor state machine remains in the Negotiating, Exchanging or Loading state, turn on debugging using the debug atm pnni adj-event and debug atm pnni adj-packet commands in order to see the individual events and the packets being exchanged.
This section describes troubleshooting the list of all nodes in the peer group along with the PTSEs that each node originates.
Use the following command to check the nodes in the peer group:
| Command | Task |
|---|---|
show atm pnni database [internal_node_number] [detail] | Confirm all nodes in the peer group with the PTSEs that each node originates. |
Use the following steps to list all nodes in the peer group along with the PTSEs that each node originates:
Step 1 Use the show atm pnni database command to list all nodes in the peer group.
Switch#show atm pnni database 1 Node 1 ID 96:160:47.00918100000000E04FACB401.00E04FACB401.00 (name: Switch) PTSE ID Length Type Seq no. Checksum Lifetime Description 1 92 97 117 37853 3143 Nodal info 2 52 224 3331 18077 3016 Int. Reachable Address Switch#
Step 2 Use the show atm pnni database command again with the detail command option.
Switch#show atm pnni database 1 detail
Node 1 ID 96:160:47.00918100000000E04FACB401.00E04FACB401.00 (name: Switch)
PTSE ID Length Type Seq no. Checksum Lifetime Description
1 92 97 117 37853 3135 Nodal info
Time to refresh 1441, time to originate 0
Type 97 (Nodal info), Length 48
ATM address 47.00918100000000E04FACB401.00E04FACB401.00
priority 0, leader bit NOT SET
preferred PGL 0:0:00.000000000000000000000000.000000000000.00
2 52 224 3331 18077 3008 Int. Reachable Address
Time to refresh 1478, time to originate 0
Type 224 (Int. Reachable Address), Length 32, Port 0, vp capable
Scope (level) 0, Address info length (ail) 16, Address info count 1
Pfx: 47.0091.8100.0000.00e0.4fac.b401..., length 104
Switch#
These commands should have similar information when the command is displayed on any other node in the same peer group.
The only differences are the internal node numbers (Node n) are independently assigned by each node so that node 1 represents the node itself and other numbers are assigned as new nodes are discovered. The PTSE information may also differ for the valid case where some nodes have received more recent information than other nodes. A redisplay of the information on the node which originally displayed older information for some PTSEs normally shows more recent information, but might also have even newer information for other PTSEs.
In the show atm pnni database command displays, check the following output display(s):
Step 3 Check that all nodes in the peer group are shown. If non-overlapping sets of partial nodes are shown for two different nodes in a peer group, it can 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 in order to isolate the problem further.
Step 4 Check that the same PTSEs and similar sequence numbers appear on displays for different ATM switch nodes. If 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 5 Check if topology or other specific types of information for a node are incorrect when displayed on another node. If 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. You should determination whether the PTSE is originating incorrectly or if there is a problem in synchronizing and flooding the PTSE to the other node.
This section describes troubleshooting hierarchy database problems. An LGN (Logical Group Node) 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 PGL (Peer Group Leader) which then floods the PTSEs to its peers.
Use the following commands to check the PNNI hierarchy network database configuration:
| Command | Task |
|---|---|
show atm pnni database [internal-node-number] [detail] | Confirm 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 local_node_number peers | Confirm the PNNI peer group leader election process configuration. |
show atm pnni database local-node [internal-node-number] | Confirm the contents of the PNNI topology database of the specified node. |
debug atm pnni flood-packet local-node local-node-number | Debug PNNI flood related packets for the local node. |
Use the following 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 the PTSEs originated by all lowest level nodes in its peer group, its higher level ancestor LGNs, and the PTSEs from all peers of the ancestor LGNs.
If there are problems with nodes or PTSEs within the same peer group, refer to the troubleshooting information in the section "Check Flat Network or Within the Same Peer Group Database Problems."
If there are problems with PTSEs from higher level LGNs, confirm the following for the output display(s):
Step 2 In addition to its peer nodes, check that the display shows all ancestor nodes. If some ancestor nodes are missing, go to the section "Troubleshooting PNNI Peer Group Leader Problems."
Step 3 If all ancestor nodes are present, but other peer LGNs are missing at one of the higher levels, check which ATM switch 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 local-node-number command on that ATM switch after determining its 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 local-node-number peers command to check connectivity to the missing LGNs.
Step 6 If there is no connectivity shown for some LGNs, go to the section "Troubleshooting PNNI Uplink and Aggregation Problems for Hierarchal Networks" to isolate problems at the child Peer Group Leader for the missing uplink. Also, see the section on "Troubleshooting PNNI SVCC-RCC and Higher Level Link Problems."
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 local-node-number 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 local-node-number command on the originating LGN and on any other affected LGN and child node(s).
This command shows when PTSEs are being sent and received, along with any error conditions detected.
Step 9 Check if topology or other specific 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 local-node-number command.
This command shows the complete PTSE contents. You should determine if the PTSE is being originated incorrectly or if there is a problem transporting 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, go to either the section "Troubleshooting PNNI Uplink and Aggregation Problems for Hierarchal Networks" or "Debug Summary Address Problems" depending on the type of affected PTSE.
This section describes troubleshooting the PNNI peer group leader (PGL). In a PNNI network which supports 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.
Use the following commands to check the peer group leader configuration:
| Command | Task |
|---|---|
show atm pnni hierarchy network [detail] | Confirm configured PNNI hierarchy and its status in detail. |
show atm pnni election [local-node local_node_number] | Confirm peer group leader election process for the local node. |
show atm pnni hierarchy local-configured | Confirm configured PNNI hierarchy for the local node. |
show atm pnni election peers | Confirm peer group leader election priority and preferred PGL as advertised by all peers in the peer group. |
Use the following steps to troubleshoot the PNNI PGL:
Step 1 Use the show atm pnni hierarchy network detail command display the Peer Group Leader and ancestor LGN for all higher hierarchy levels.
Step 2 If no active parent LGNs are shown, use the show atm pnni election local-node local_node_number command on the node (or nodes) which are configured to allow operation as the PGL. If the problem occurs for elections on a higher level, use the local-node option to specify the node index number of the higher level node.
Switch# show atm pnni election local-node 1 PGL Status.............: Not PGL Preferred PGL..........: NULL Preferred PGL Priority.: n/a Active PGL.............: NULL Active PGL Priority....: n/a Active PGL For.........: n/a Current FSM State......: PGLE Operating: Not PGL Last FSM State.........: PGLE Calculating Last FSM Event.........: Preferred PGL Is Not Self Configured Priority....: 0 Advertised Priority....: 0 Conf. Parent Node Index: NONE PGL Init Interval......: 15 secs Search Peer Interval...: 75 secs Re-election Interval...: 15 secs Override Delay.........: 30 secs Switch#
Step 3 Confirm that the election leadership-priority is configured to a non-zero value and that the expected primary PGL has the highest priority.
Step 4 Confirm that the peer group leader has a parent node configured that is enabled and running. Use the show atm pnni hierarchy local-configured command to view the locally configured parent nodes.
Switch# show atm pnni hierarchy local-configured Locally configured parent nodes: Node Parent Index Level Index Local-node Status Node Name ~~~~~ ~~~~~ ~~~~~~ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~ 1 96 N/A Enabled/ Running Switch Switch#
Step 5 Use the show atm pnni election peers command to see which other peer nodes are known by a local node. Only those nodes which are listed as Connected are eligible to be the preferred PGL for a local node.
Switch# show atm pnni election peers Node No. Priority Connected Preferred PGL ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~ 1 0 Yes NONE Switch#
Step 6 If the expected leader still does not become PGL, check the Current FSM State using the shown for the show atm pnni election command (preferably on the ATM switch which should be acting as the PGL). The following subset of election states might indicate possible user correctable conditions if they remain unchanged for an extended period:
For other PGL election problems not isolated by these steps, use the debug atm pnni election command to turn on debugging messages which show the election events and state changes leading up to the election outcome as well as some additional election error conditions.
This section describes troubleshooting the lowest level PNNI interface connection problems.
This section contains the following procedures:
This section describes troubleshooting the lowest level PNNI interface status.
Use the following command to check the lowest-level PNNI interface status:
| Command | Task |
|---|---|
show atm interface atm card/subcard/port [status] | Confirm PNNI interface and administration status plus the hello state. |
show atm status | Display status information for all of the interfaces. |
show atm routing-mode | Check the ATM switch routing mode. |
no atm routing-mode static | If needed, configure the switch to allow PNNI operation. |
show atm interface card/subcard/port | Confirm that the interface is configured with:
|
Use the following steps to troubleshoot the lowest level PNNI interface status:
Step 1 Use the show atm interface atm card/subcard/port status command to confirm PNNI interface and administration status plus the hello state.
If the IF Status and Admin Status are not up, make sure that the interface is not configured as shutdown. If they still don't change to the UP state, refer to the chapter "Troubleshooting ATM Switch Interface Connections."
If the PNNI Hello state is n/a or not shown for an NNI interface between two ATM switches, check the ATM switch routing mode using the show atm routing-mode command. If it is not dynamic (PNNI), use the no atm routing-mode static command to allow PNNI operation. If this doesn't work, confirm that the installed software version allows PNNI operation.
If the Hello State shows LoopErr, it means that the line side is connected to another port on the same ATM switch, or to another switch which has an identical Node ID.
Step 2 Check the output of the show atm interface atm card/subcard/port command to confirm that the interface is configured with the following:
If the interface is Port-type: vp tunnel, confirm that the VP tunnel is configured correctly at both ends. Refer to the section "Troubleshooting Virtual Path Tunnel Connections."
Also confirm that the listed port adapter Port-type supports ATM VCs on its line side. If not, then this interface will not be usable either as an NNI or as a UNI signalling interface.
This section describes if the PNNI Hello state is down, checking that the PNNI Routing Control Channel (RCC) and Signalling Control Channel virtual circuits (VCs) are up.
Use the following command to check the status of the PNNI RCC and signalling control channels:
| Command | Task |
|---|---|
show atm interface atm card/subcard/port | Confirm the PNNI signalling control channels status. |
Use the following steps to check that the PNNI RCC and signalling control channel VCs are up:
Step 1 Use the show atm vc interface atm card/subcard/port command to confirm status of the signalling control channels:
Switch#show atm vc interface ATM0/0/1 Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status ATM0/0/1 0 5 PVC ATM2/0/0 0 43 QSAAL UP ATM0/0/1 0 16 PVC ATM2/0/0 0 35 ILMI UP ATM0/0/1 0 18 PVC ATM2/0/0 0 107 PNNI UP Switch#
Step 2 Check the following:
If VCs with Encap types of PNNI and Q.2931 Signalling ATM Adaptation Layer (QSAAL) are not shown, check the interface configuration to confirm that signalling is enabled.
If the interface has the manual-well-known-vc mode enabled, either disable the manual-well-known-vc mode, or if that is the preferred mode, then manually configure PVCs with encapsulation types of PNNI and QSAAL.
If VCs with PNNI and QSAAL are shown, but the Status is not UP on an interface with an IF Status that is UP, confirm that the interface has the manual-well-known-VC mode disabled and that the interface is type NNI.
This section describes troubleshooting the PNNI PVC. If the PNNI PVC is up but the PNNI Hello State is not 2way-in or comm_out, check the PNNI status further using this process.
Use the following commands to check the PNNI PVC status:
| Command | Task |
|---|---|
show atm pnni interface atm card/subcard/port detail | Confirm the PNNI PVC status. |
show atm pnni interface | Confirm the status of all PNNI interfaces. |
show atm pnni local-node | Confirm that the lowest level peer group IDs match. |
show atm pnni hierarchy network detail | Confirm that a common higher level peer group ID exists. |
Use the following steps to troubleshoot the PNNI PVC status:
Step 1 Use the show atm pnni interface atm card/subcard/port detail command to confirm PNNI PVC status:
Step 2 Check the following subset of Hello states. They may indicate possible user correctable conditions if they remain unchanged for an extended period:
Step 3 If the neighbor was expected to be in the same peer group, confirm that the Remote Node has the expected peer group ID. Use the show atm pnni local-node command on this node and on the neighbor node in order to confirm that the lowest level peer group IDs match.
Step 4 If the neighbor was supposed to be in another peer group, but the COMMON OUTSIDE state has not been reached, use the show atm pnni hierarchy network detail command on this node and on the neighbor node in order to confirm that a common higher level Peer Group ID exists.
Step 5 It may take a minute or two for the higher level LGNs to come up for some hierarchy configurations that have multiple higher levels or do not have interfaces fully up yet at the higher levels. If a common higher level can't be found after several minutes, go to the section "Debug PNNI Hello at the Lowest-level" to check the peer group IDs appearing in the nodal hierarchy lists sent in the individual Hello messages on the outside link.
Step 6 If the Peer Group IDs do not have the expected values, use the show atm pnni local-node command on the ATM switches where the higher level LGNs are running in order to confirm that Peer Group IDs have the expected values. If not, verify that the Peer Group IDs have not been configured to non-default values.
Step 7 Also verify that if the active ATM address has been changed on one of the ATM switches, that the lowest level node has been disabled and reenabled in order to reassign the Node ID and Peer Group IDs based on the active ATM address (unless non-default values are preferred).
Step 8 If common higher levels are not running, see the section "Troubleshooting PNNI Peer Group Leader Problems."
This section describes troubleshooting PNNI metric configuration and resource availability information for the lowest level interfaces.
Use the following commands to check the PNNI interface metric configuration:
| Command | Task |
|---|---|
show atm pnni interface atm card/subcard/port | Confirm PNNI interface metric configuration. |
show running-config | Confirm administrative weight (AW) value, to see the significant change boundaries. |
show controllers atm card/subcard/port | Confirm MCR value, port type and port rate. |
show atm pnni resources atm card/subcard/port | Confirm significant change boundaries. |
Use the following steps to troubleshoot PNNI metric configuration and resource availability information for the lowest level interfaces:
Step 1 Use the show atm pnni interface atm card/subcard/port detail command to confirm the PNNI interface metric configuration
Switch1# show atm pnni interface atm 0/0/1 detail PNNI Interface(s) for local-node 1 (level=96): Port ATM0/0/0 RCC is up , Hello state 2way_in with node Switch Error: Port Looped back Next hello occurs in 0 seconds, Dead timer fires in 68 seconds CBR : AW 5040 MCR 155519 ACR 147743 CTD 154 CDV 138 CLR0 10 CLR01 10 VBR-RT : AW 5040 MCR 155519 ACR 155519 CTD 707 CDV 691 CLR0 8 CLR01 8 VBR-NRT: AW 5040 MCR 155519 ACR 155519 CLR0 8 CLR01 8 ABR : AW 5040 MCR 155519 ACR 0 UBR : AW 5040 MCR 155519 Aggregation Token: configured 0 , derived 0, remote 0 Switch# Switch#
Step 2 Check AW (Administrative Weight) Configuration---If the AW value is not as expected, use the show running-config command to check the administrative-weight mode (for the ATM router PNNI configuration on this ATM switch).
Also, check whether the admin-weight has been configured to a nondefault value for the specific interface.
Step 3 Check MCR (Maximum Cell Rate) Configuration---If the MCR value is not as expected, check the port type and port rate with the show controller atm card/subcard/port command (for physical interfaces only).
Step 4 Use the show running-config command to check the ATM pacing configuration. For VP tunnels, check the configuration of the corresponding PVP connection.
Step 5 Check available cell rate (ACR), cell transfer delay (CTD) or cell delay variation (CDV) configuration---Use the show atm pnni resource atm card/subcard/port command to see the significant change boundaries.
Step 6 The allocated bit rates (which affect the allowed cell rate [ACR]) can be checked with the show atm interface resource atm card/subcard/port command.
Step 7 Check CLR0 and CLR01 (cell loss ratio [CLR] for CLP=0 and for CLP=0+1) configuration---Use the show controllers atm card/subcard/port command to see detailed error information for a specific interface.
This section describes further PNNI Hello debugging at the lowest interface level.
Use the debug atm pnni hello atm card/subcard/port command at both the local end and (if possible) the remote end of the interface in order to see the actual Hello messages being transmitted along with some additional error condition messages:
| Command | Task |
|---|---|
debug atm pnni hello atm card/subcard/port | Confirm the actual Hello messages being transmitted. |
Use the following steps for further PNNI Hello debugging at the lowest interface level:
Step 1 Use the debug atm pnni hello atm command at the local end of the interface to see the actual Hello messages being transmitted with some additional error condition messages.
Switch1# debug atm pnni hello ATM0/0/1 <display omitted>
Step 2 Use the debug atm pnni hello atm card/subcard/port command at the remote end (if possible) of the interface to see the actual Hello messages being transmitted.
Step 3 Use the debug atm pnni hello atm card/subcard/port command at the neighbor node (if possible) of the interface to see the actual Hello messages being transmitted.
Step 4 After the display prints out two screens full of information, turn off further printouts using the undebug all command.
Step 5 Scroll back up in order to confirm the following:
If no printouts are shown at all, be sure debugging is on, confirm that this is an NNI interface and recheck interface debugging steps in these previous sections, "Check PNNI Lowest-level Interface Problems," "Check the PNNI and Signalling Control Channels," and "Check PNNI Hello Problems on Lowest Level Interfaces."
Step 6 Confirm that transmit messages are shown and have the expected local Peer Group ID, Port ID and other information. 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 7 Confirm that receive message(s) 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, it indicates a problem in 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 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 8 Look for other PNNI Hello debugging error messages that might give a further indication of internal or configuration problems.
This section describes troubleshooting 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:
For detailed information see the section "Configure Aggregation Mode," in the chapter "Configuring ATM Routing and PNNI," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
The following section contains the following procedures:
This section describes troubleshooting a higher level LGN and the status of all PNNI aggregated horizontal links and induced uplinks at that level.
Use the following commands to check the status of all PNNI aggregated horizontal links and induced uplinks:
| Command | Task |
|---|---|
show atm pnni interface local-node local_node_number | Confirm the status of all PNNI aggregated horizontal links and induced uplinks. |
show atm pnni neighbor | Verify that the neighbor peer LGN has reached the Full state for its database synchronization. |
Use the following steps to troubleshoot a higher level LGN and the status of all PNNI aggregated horizontal links and induced uplinks at that level.
Step 1 Use the show atm pnni interface local-node local_node_number command to check all PNNI aggregated horizontal links and induced uplinks at the LGN level:
Switch1# show atm pnni interface local-node 1
PNNI Interface(s) for local-node 2 (level=40):
Local Port Type RCC HrzLn St Deriv Agg Remote Port Rem Node(No./Name)
~~~~~~~~~~~~~ ~~~~~ ~~~ ~~~~~~~~ ~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~
2C49000 HrzLn UP 2way 0 2230000 10 Switch2.2.40
2C49003 HrzLn UP 2way 3 2230003 10 Switch2.2.40
2276000 UpLnk - n/a 0 FFFFFFFF 11 Switch4
Switch1#
If all of the expected interfaces between a pair of LGNs are missing, or if the RCC is not UP, continue with the following SVCC-RCC checks.
If the RCC is listed as UP, but ports are missing for some expected aggregation token(s), continue to the "Troubleshooting PNNI Uplink and Aggregation Problems for Hierarchal Networks" section.
For example, if the RCC is listed as UP, but the HrzLn State is other than 2way, the following subset of (aggregated) horizontal link states might indicate conditions you can correct, if they remain unchanged for an extended period:
This section describes troubleshooting the status of SVCC-RCCs from a local LGN node to all of its LGN peers.
Use the following command to confirm the status of SVCC-RCCs from a local LGN node:
| Command | Task |
|---|---|
show atm pnni svcc-rcc [local-node local_node_number] detail | Confirm confirm the status of SVCC-RCCs from a local LGN node to all of its LGN peers |
show version | Confirm the CPU card has sufficient memory to support the software version |
Use the following steps to troubleshoot the status of SVCC-RCCs from a local LGN node to all of its LGN peers:
Step 1 Use the show atm pnni svcc-rcc local-node local_node_number detail command to confirm the status of SVCC-RCCs from a local LGN node.
Step 2 Confirm that the RCC state is UP (with SVCC Setup State shown as SVCC_UP for the detailed display). Make a note of whether this is the calling side or the called side as shown on the same display line where the SVCC Setup State appears.
Step 3 If the RCC state is UP, but the Hello State is not 2way_in, proceed to the "Check SVCC-RCC Hello" section. Otherwise if the RCC state is not UP, continue with the following checks.
Step 4 Confirm that the SVCC has the intended remote (LGN) Node and rem-node name. If not, verify the LGN ancestor information for the child PGL which 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 possible conditions you can correct:
This section describes troubleshooting the SVCC-RCC hello state of the local node.
Use the following commands to check the SVCC-RCC hello state:
| Command | Task |
|---|---|
show atm pnni svcc-rcc [local-node < local-node-number] | Confirm the SVCC-RCC hello state. |
Use the show atm pnni svcc-rcc local-node local-node-number command to determine the SVCC-RCC Hello state, without the detail option:
Using the show atm pnni svcc-rcc local-node local-node-number command to check the following:
If the SVCC-RCC state is UP, but the Hello State is other than 2way_in, the following subset of RCC Hello States may indicate possible user correctable conditions, if they remain unchanged for an extended period:
If the previous steps cannot isolate the cause of a problem with higher level link status, this section describes debugging and show commands that will recognize the following:
Use the following commands to debug and check the SVCC-RCC setup:
| Command | Task |
|---|---|
debug atm pnni svcc-rcc remote-node remote-node-number | Confirm the SVCC-RCC setup, the RCC Hello, and aggregated horizontal link state transitions, plus full hello message contents. |
show atm pnni topology | Confirm if PNNI shows a route to the remote LGN. |
Use the debug atm pnni svcc-rcc remote-node remote-node-number command to debug and check the SVCC-RCC setup:
Step 1 Use the debug atm pnni svcc-rcc remote-node remote-node-number command on the ATM switch that has the higher numbered LGN Node ID, since that is the SVC originator (for example, the calling side).
 | Caution Since this debugging mode controls extensive information, it is best to filter the output by specifying either a local-node or preferably the target remote node number, if it is known. |
The debug atm pnni svcc-rcc remote-node remote-node-number command is normally more helpful when used on the ATM switch that has the higher numbered LGN Node ID, since that is the SVC originator (for example, the calling side). However, it is useful to display the debugging Hello messages at both ends for debugging RCC Hello problems.
Step 2 Wait approximately 30 seconds or one minute to allow any SVCC setup retries to be listed and turn off debugging, using the undebug all command.
Step 3 Then scroll back up to the top of the screen to confirm the following:
If the SVCC-RCC has not yet reached the SVCC_UP state, confirm that a queued ATM_SETUP line is displayed and make note of the service category. Normally the service category will be VBR-NRT, except for cases where the SVC must traverse a VP tunnel or some link that doe not support VBR-NRT.
When the service category changes with each attempt, it indicates that release messages are being received, which indicate that no path exists for each attempted service category. Check the topology using the show atm pnni topology command to see if PNNI shows a route to the remote LGN.
Step 4 Confirm that the debugging line following the queued ATM_SETUP phrase shows a Setup-> ATM address for the ATM address of the intended remote LGN node. If not, these messages may belong to the SVCC-RCC for another remote LGN.
If there are no Setup attempts for the case where an expected SVCC-RCC has not yet reached the SVCC_UP state, proceed to the section on "Troubleshooting PNNI Uplink and Aggregation Problems for Hierarchal Networks".
If there are Setup attempts, but Release messages are received for each attempt, make note of the Cause code which may explain the cause of the problem. If not, proceed to the section called "Troubleshooting SVC Connections on a PNNI Routing Network," but consider the origination interface to be the CPU port (ATM 2/0/0 for a standard ATM switch).
Step 5 Make note of any other debugging error messages which might be printed in SVCC-RCC debugging mode.
For RCC hello FSM problems, the full hello messages will be listed, along with the horizontal link extension entries for all aggregation tokens. By listing the hello messages at both ends of the SVCC-RCC, it is possible to locate where missing or mismatched information takes place.
This section describes troubleshooting PNNI uplink and aggregation problems for hierarchal networks by the LGN.
Links that connect border nodes between two different peer groups are referred to as outside links. When the hello state finds a common higher level ancestor LGN on an outside link transitions to the common outside state. At this time each border node will advertise an uplink PTSE to its peer nodes. The uplink PTSE contains the resource information for both directions of the outside link along with the node ID and peer group ID of the upnode and the aggregation token for the link.
The PGL (peer group leader) uses the uplink PTSE information to aggregate together the resource information from all outside links with the same aggregation token which connect to another peer group. The PGL notifies its parent LGN whenever there are changes to an uplink status. The parent LGN creates either an induced horizontal link or an induced uplink for each aggregation token to an upnode at the same or higher level.
For detailed information see the section "Configure Aggregation Mode," in the chapter "Configuring ATM Routing and PNNI," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section contains the following procedures:
This section describes troubleshooting the uplink for the peer group on the PGL.
To see the table which summarizes all of the uplinks for a Peer Group, execute the show atm pnni aggregation link command on the ATM switch acting as the PGL. The display also shows the port identity of the induced horizontal or uplink for the parent LGN.
Use the following command to check the uplinks for the peer group on the PGL:
| Command | Task |
|---|---|
show atm pnni aggregation link | Confirm the PGL summary Uplink to the peer group. |
Use the following steps to check the PGL uplink summaries:
Step 1 Use the show atm pnni aggregation link command.
Switch# show atm pnni aggregation link
PNNI link aggregation for local-node 2 (level=40, name=Switch5.2.40)
Upnode Number: 10 Upnode Level: 40 Upnode Name: Switch7.2.40
AggToken InducPort BorderPort Border Node(No./Name)
~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
0 2C49000 ATM0/1/0 9 Switch6
ATM0/1/2 1 Switch5
3 2C49003 ATM0/0/0 11 Switch3
Upnode Number: 11 Upnode Level: 24 Upnode Name: Switch8.3.24
AggToken InducPort BorderPort Border Node(No./Name)
~~~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
0 2276000 ATM0/1/1 9 Switch6
Step 2 If an expected Upnode and Aggregation Token pair is missing from the PGL uplink summaries table, continue with the following section "Check Missing Upnode or AggToken" to determine the PGL knows about an uplink PTSE originated by one or more known border nodes.
This section describes troubleshooting missing Upnode and AggToken pairs on border nodes.
Use the following commands to check the for Uplink PTSEs and derived aggregation token configuration:
| Command | Task |
|---|---|
show atm pnni database [internal-node-number] [detail] | Confirm uplink PTSEs for the border nodes. |
show atm pnni interface atm card/subcard/port [detail] | Confirm the hello state and derived aggregation token value on the node. |
Use the following steps to troubleshoot missing upnode and aggregation token pairs on border nodes:
Step 1 Use the show atm pnni database command to check the PGL for Uplink PTSE originated by border nodes.
Switch#show atm pnni database 1 Node 1 ID 96:160:47.00918100000000E04FACB401.00E04FACB401.00 (name: Switch) PTSE ID Length Type Seq no. Checksum Lifetime Description 1 92 97 117 37853 3143 Nodal info 2 52 224 3331 18077 3016 Int. Reachable Address Switch#
Step 2 Check if an expected upnode and aggregation token pair is missing from the table listed on the PGL. Also check if the PGL receives an uplink PTSE originated by one or more of the known border nodes.
Step 3 Next, use the internal-node-number option and the detail option to examine the contents of the uplink PTSE for a border node.
Switch# show atm pnni database 1 detail
Node 1 ID 96:160:47.00918100000000E04FACB401.00E04FACB401.00 (name: Switch)
PTSE ID Length Type Seq no. Checksum Lifetime Description
1 92 97 117 37853 3143 Nodal info
2 52 224 3331 18077 3016 Int. Reachable Address
Switch#show atm pnni database 1 detail
Node 1 ID 96:160:47.00918100000000E04FACB401.00E04FACB401.00 (name: Switch)
PTSE ID Length Type Seq no. Checksum Lifetime Description
1 92 97 117 37853 3135 Nodal info
Time to refresh 1441, time to originate 0
Type 97 (Nodal info), Length 48
ATM address 47.00918100000000E04FACB401.00E04FACB401.00
priority 0, leader bit NOT SET
preferred PGL 0:0:00.000000000000000000000000.000000000000.00
2 52 224 3331 18077 3008 Int. Reachable Address
Time to refresh 1478, time to originate 0
Type 224 (Int. Reachable Address), Length 32, Port 0, vp capable
Scope (level) 0, Address info length (ail) 16, Address info count 1
Pfx: 47.0091.8100.0000.00e0.4fac.b401..., length 104
Switch#
Step 4 If an expected uplink PTSE is missing, execute the same command on the border node ATM switch.
Step 5 If the uplink PTSE is present in the border node database, but not in the PGL database, go to the "Troubleshooting PNNI Database Problems" section for further debugging.
Step 6 If the Uplink PTSE is missing from border node database, use the show atm pnni interface atm command to verify the Hello state for the interface to the other peer group.
Switch# show atm pnni interface atm 10/0/0 PNNI Interface(s) for local-node 1 (level=96): Port ATM10/0/0 RCC is up , Hello state 2way_in with node Switch Error: Port Looped back Next hello occurs in 2 seconds, Dead timer fires in 67 seconds Switch#
Step 7 If a lowest-level outside link interface is not in the common outside state, proceed to the "Check PNNI Lowest-level Interface Problems" section.
Step 8 If the missing interface is a higher level induced uplink, perform the same checks at the next lower hierarchy level on the ATM switch acting as the LGN (and child PGL) node.
Step 9 If the derived aggregation token does not have the expected value, use the detail option to show additional interface information.
Switch# show atm pnni interface atm 10/0/0 detail PNNI Interface(s) for local-node 1 (level=96): Port ATM10/0/0 RCC is up , Hello state 2way_in with node Switch Error: Port Looped back Next hello occurs in 6 seconds, Dead timer fires in 69 seconds CBR : AW 5040 MCR 155519 ACR 147743 CTD 154 CDV 138 CLR0 10 CLR01 10 VBR-RT : AW 5040 MCR 155519 ACR 155519 CTD 707 CDV 691 CLR0 8 CLR01 8 VBR-NRT: AW 5040 MCR 155519 ACR 155519 CLR0 8 CLR01 8 ABR : AW 5040 MCR 155519 ACR 0 UBR : AW 5040 MCR 155519 Aggregation Token: configured 0 , derived 0, remote 0 Switch#
Step 10 Check for correct aggregation token local and remote configuration.
Step 11 Verify the expect upnode node ID and common peer group ID.
This section describes troubleshooting the induced port on the LGN. If the induced port value is missing or does not appear to be functional for an aggregate token and upnode combination, use the following command to check the higher level interfaces for the parent LGN local-node.
Use the following command to check the induced port on the LGN:
| Command | Task |
|---|---|
show atm pnni interface local-node local_node_number | Confirm the higher level interfaces for the parent LGN local-node configuration. |
Use the following steps to troubleshoot the port on the LGN:
Step 1 Use the show atm pnni interface local-node local_node_number command to check the induced port on the LGN:
Step 2 If the interface port does not appear up, go to the section "Troubleshooting PNNI SVCC-RCC and Higher Level Link Problems."
This section describes troubleshooting the aggregated metrics along with the border node interface metrics for each aggregation token.
Use the following commands to check link aggregation:
| Command | Task |
|---|---|
show atm pnni aggregation link border-detail | Confirm per service class aggregation mode (best-link or aggressive) |
show atm pnni database node_number detail | Confirm uplink PTSEs. |
Use the following steps to troubleshoot the aggregated metrics along with the border node interface metrics for each aggregation token:
Step 1 Use the show atm pnni aggregation link border-detail command to confirm per-service class aggregation mode:
Step 1 Check the per-service class aggregation mode (best-link or aggressive). The aggregation mode can be changed in order to control the resulted aggregated metrics.
If the aggregated metrics are inaccurate due to the contribution of one or more border node interfaces which are significantly different from all others, new aggregation token(s) can be configured in order to treat those aggregated links separately at the higher level.
If the contribution from a border node interface is not as expected, check the border node Uplink PTSE using the show atm pnni database n detail command where n is the node number of the border node.
Step 2 Use the same show atm pnni database n detail command executed on the border node ATM switch to verify the same uplink PTSE information.
If the two show atm pnni database n detail command displays show significantly different information, go to the section "Troubleshooting PNNI Database Problems." Otherwise, see the "Check PNNI Lowest-level Interface Problems" section at the subsection called "Check PNNI Metric Troubleshooting for Lowest-level Interfaces."
If the border node is a higher level LGN which has an induced uplink, check the link aggregation at the next lower hierarchy level on the ATM switch acting as the border node.
This section describes troubleshooting PNNI address and address summarization problems. Summary addresses can be used to decrease the amount of information advertised by a PNNI node, and thereby contribute to scaling in large networks.
This section is separated into the following subsections:
This section describes troubleshooting PNNI address prefix configurations. A single default summary address is configured for each logical group node in the PNNI hierarchy. The length of that summary for any LGN equals the level of the child peer group, and its value is equal to the first level bits of the child peer group identifier. This address prefix is advertised into the peer group LGN.
Use the following commands to check PNNI address prefix configuration:
| Command | Task |
|---|---|
show atm route | Confirm the list of all prefixes known by the node. |
show atm address | Confirm the correct prefix is present for the active ATM Address. |
show atm pnni database local-node-number PTSE_ID detail | Confirm the actual prefixes being advertised. |
show atm pnni hierarchy network detail | Confirm which ATM switch is acting as the ancestor LGN. |
show atm route | Confirm the child PGL is up and that the scope is appropriate to allow advertising at the higher level. |
show atm pnni scope | Confirm the configuration of the UNI scope map. |
Use the following steps to troubleshoot PNNI address prefix configuration:
Step 1 Use the show atm route command to confirm the list of all prefixes known by the node:
Switch# show atm route
Codes: P - installing Protocol (S - Static, P - PNNI, R - Routing control),
T - Type (I - Internal prefix, E - Exterior prefix, SE -
Summary Exterior prefix, SI - Summary Internal prefix,
ZE - Suppress Summary Exterior, ZI - Suppress Summary Internal)
P T Node/Port St Lev Prefix
~ ~~ ~~~~~~~~~~~~~~~~ ~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
P SI 1 0 UP 0 47.0091.8100.0000.00e0.4fac.b401/104
R I 1 ATM10/1/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.0080.1c93.8060/152
R I 1 ATM10/0/1 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b030/152
R I 1 ATM10/0/1 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b031/152
R I 1 ATM10/0/1 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b032/152
R I 1 ATM13/0/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b401/152
R I 1 ATM13/0/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b402/152
R I 1 ATM13/0/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b403/152
R I 1 ATM13/0/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b404/152
R I 1 ATM13/0/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.00e0.4fac.b405/152
R I 1 ATM13/0/0 UP 0 47.0091.8100.0000.00e0.4fac.b401.4000.0c/128
Switch#
Step 2 Verify that any expected address, prefix, or summary address appears as up in the list of prefixes.
If the interface addresses do not have the expected prefix, verify the correct prefix is present for the active ATM address, using the show atm address command.
Step 3 To see the actual prefixes being advertised by a local node, use the show atm pnni database local-node-number command to get the PTSE ID number for the internal reachable address PTSE.
Step 4 Then use the show atm pnni database local-node-number PTSE_ID detail command to see the full contents of the PTSE.
Switch# show atm pnni database 1 1 detail
1 92 97 551 37417 2116 Nodal info
Time to refresh 646, time to originate 0
Type 97 (Nodal info), Length 48
ATM address 47.00918100000000E04FACB401.00E04FACB401.01
priority 0, leader bit NOT SET, restricted transit bit NOT SET
complex node bit NOT SET, restricted branching bit NOT SET
non-transit for PGL election bit NOT SET
preferred PGL 0:0:00.000000000000000000000000.000000000000.00
Type 640 (System Capabilities Info), Length 24
System Type: ls1010, Major Version: 11, Minor Version: 3
System Name: Switch
Switch#
Step 5 To see if a prefix is being advertised at the higher levels, determine which ATM switch is acting as the ancestor LGN, use the show atm pnni hierarchy network detail command.
Step 6 Use the show atm pnni database local-node-number PTSE_ID detail command on the ATM switch acting as the ancestor LGN.
Step 7 If the expected prefix is not being advertised at the higher level, display the same information for the child PGL. If it is not present at the child PGL level, but was present at the originating node, see the section "Troubleshooting PNNI Database Problems."
Step 8 If prefix is present at the child PGL, but is missing for the parent LGN, verify that it is listed as up in the show atm route command display.
Step 9 Verify that the Scope (level) is appropriate to advertise at the desired higher levels.
Step 10 If the Scope (level) does not have the expected value for a local prefix, check the configuration of the UNI scope map using the command show atm pnni scope. If it is not the desired map, the mode can be changed to manual, and the desired scope translation levels can be configured.
It is normal for the prefixes to be missing if there is a shorter matching summary prefix configured at its level. The summary prefix will be advertised instead of any longer prefixes which match.
However, if the summary prefix is configured for suppress, none of the prefixes which match it will be advertised.
This section describes troubleshooting PNNI summary address problems.
Use the following commands to show summary addresses:
| Command | Task |
|---|---|
show atm pnni summary [local-node node-index] | Confirm summary information advertised by PNNI node. |
show running-config | Confirm no auto-summary is not configured and summary address has not been manually configured. |
show atm address | Confirm active and no-active switch addresses. |
show atm pnni local-node | Confirm node and peer group IDs of higher local-nodes |
Use the following steps to troubleshoot summary addresses and suppressed summary addresses for all of the local-nodes on an ATM switch:
Step 1 Use the show atm pnni summary command to display the PNNI summary address configuration.
Step 2 Check if any expected summary addresses appear in the list for the expected local-node for the correct Internal or Ext (Exterior) type and with the expected suppressed/non-suppressed attribute.
Step 3 Verify that all longer prefixes and addresses matching any summary addresses are reachable at the local-node or at a node in a child peer group. Otherwise, some addresses may be unreachable.
Step 4 Verify that the Scope (level) is appropriate to advertise at all desired higher levels.
Step 5 If the default switch address summary is missing, use the show running-config command to make sure that no auto-summary is not configured for the affected local-node.
Step 6 If an automatically generated ATM summary address is not the expected address, use the show atm address command to show the configured active and nonactive switch addresses.
Step 7 Use the show atm pnni local-node command to check the node IDs and peer group IDs of higher level local-nodes. If they are not based on the prefix of the ATM address, verify that no other peer group IDs have been manually configured. And verify that the lowest-level node on the ATM switch has been disabled and re-enabled since the last time the active switch ATM address was reconfigured.
Step 8 If an unexpected summary address appears in the list, use the show running-config command to make sure that the summary address has not been manually configured.
If a summary prefix has been configured, but it is not possible to route to the summarized addresses from another peer group, check for an overlapping summary address within the other peer group. If the overlapping summary is for an automatically generated prefix it could mean the ATM node addresses need to be modified in order to give unique prefixes for the ancestors of the two peer groups.
This section describes troubleshooting virtual path (VP) tunnels. VP tunnels are used primarily between private ATM networks across public ATM networks, such as telecom carriers, that do not yet support ATM signalling. Signalling traffic is mapped into the VP tunnel and the switches will allocate virtual channel connection (VCC) on that VP instead of the default VP=0. This allows signalling to travel transparently through the public network.
This section describes troubleshooting virtual path tunnel configurations. In the example network, (see Figure 5-4) the PVC tunnel connection configured between the ATM switch on floor 1 of the administration building and the ATM switch on floor 1 of the remote sales building has the following interface and subinterface numbers:
This section contains the following procedures:
For detailed configuration information see the section "Configure a Public Network Tunnel Interface," in the chapter "v," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes troubleshooting the VP tunnel configuration. If the permanent virtual path (PVP) subinterface numbers do not match on both ends of the VP tunnel, the connection is not established.
To show the ATM virtual interface configuration, use the following command:
| Command | Task |
|---|---|
show atm interface [atm card/subcard/port[.vpt #]] | Show the ATM interface configuration. |
Use the following steps to troubleshoot VP tunnel connections:
Step 1 Use the show atm interface atm card/subcard/port command to display the configuration of switch AdminFl1Ls1, located in the headquarters building at subinterface 1/0/0.99:
AdminFl1Ls1# show atm interface atm 1/0/0.99
Interface: ATM1/0/0.99 Port-type: vp tunnel IF Status: UP Admin Status: up Auto-config: enabled AutoCfgState: waiting for response from peer IF-Side: Network IF-type: UNI Uni-type: Private Uni-version: V3.0 Max-VPI-bits: 0 Max-VCI-bits: 14 Max-VP: 0 Max-VC: 16383 Signalling: Enabled
ATM Address for Soft VC:44.4444.4444.4444.4444.4444.4444.4444.4444.00Configured virtual links: PVCLs SoftVCLs SVCLs Total-Cfgd Installed-Conns 4 0 0 4 4 AdminFl1Ls1#
Step 2 Check the IF status field to confirm the interface is UP. If not refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 3 Check the Admin Status field to confirm the interface is up. If not refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 4 Check the Interface and ATM Address for Soft VC fields. They indicate that the virtual path tunnel is configured correctly.
Step 5 Use the show atm interface atm card/subcard/port command to display the configuration of switch RsalFl1Ls1, located in the remote sales building at subinterface 4/0/0.99:
RsalFl1Ls1# show atm interface atm 4/0/0.99
Interface: ATM4/0/0.99 Port-type: vp tunnel IF Status: UP Admin Status: up Auto-config: enabled AutoCfgState: waiting for response from peer IF-Side: Network IF-type: UNI Uni-type: Private Uni-version: V3.0 Max-VPI-bits: 0 Max-VCI-bits: 14 Max-VP: 0 Max-VC: 16383 Signalling: Enabled
ATM Address for Soft VC:33.3333.3333.3333.3333.3333.3333.3333.3333.00Configured virtual links: PVCLs SoftVCLs SVCLs Total-Cfgd Installed-Conns 4 0 0 4 4 RsalFl1Ls1#
Step 6 Check the IF status field to confirm the interface is UP." If not refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 7 Check the Admin Status field to confirm the interface is UP. If not refer to the chapter "Troubleshooting ATM Switch Interface Connections."
Step 8 Check the Interface and ATM address for Soft VC fields. They indicate that the virtual path tunnel is configured correctly.
If you determine that the PVP is not configured correctly refer to chapter "Configuring Interface Types," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Continue with the next phase of VP tunnel troubleshooting if you still have not determined the problem.
This section describes checking the virtual path PVP configuration on both ends of the connection between the administration building and the remote sales building across the public network.
To confirm the ATM virtual circuit interface configuration, use the following command:
| Command | Task |
|---|---|
show atm vc interface atm card/subcard/port | Show the ATM VC interface configuration. |
The following example shows how to confirm the configuration of ATM subinterface 1/0/0.99 on switch AdminFl1Ls1 located in the administration building:
AdminFl1Ls1# show atm vc interface atm 1/0/0 Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status ATM1/0/0 0 5 PVC ATM2/0/0 0 41 QSAAL UP ATM1/0/0 0 16 PVC ATM2/0/0 0 33 ILMI UP
ATM1/0/0 99 40PVC ATM4/0/0.99 99 50 UP AdminFl1Ls1#
The interface ATM 1/0/0/ field indicates that the cross-connect is configured correctly.
The following example shows how to confirm the configuration of ATM subinterface 1/0/0.99 on switch RsalFl1Ls1 located in the remote sales building:
RsalFl1Ls1# show atm vc interface atm 4/0/0 Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status ATM4/0/0 0 5 PVC ATM2/0/0 0 41 QSAAL UP ATM4/0/0 0 16 PVC ATM2/0/0 0 33 ILMI UP
ATM4/0/0 99 40PVC ATM1/0/0.99 99 50 UP RsalFl1Ls1#
The interface ATM 4/0/0/ field indicates that the cross-connect is configured correctly.
If you determine that the PVP is not configured correctly refer to the chapter "Configuring Interface Types," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes continued troubleshooting of the VP tunnel connections using debug commands.
Use the following commands to debug the VP tunnel connection management:
| Command | Task |
|---|---|
debug atm conn errors | Enable connection management error debugging. |
debug atm conn events | Enable connection management event debugging. |
undebug all | Disable all debugging. |
This section describes troubleshooting the PVC traffic being dropped. In the example network (see Figure 5-5) the connection between the DNS and e-mail servers and the ATM switch on floor 1 of the administration building and the Catalyst 5000 switch on floor 1 of the manufacturing building is dropping cells sat some node in the connection.
This connection includes the following interfaces:
This section contains the following procedures:
For detailed configuration information see the chapter "Configuring Resource Management," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
This section describes troubleshooting a virtual connection to determine where the cells are being dropped along the length of the circuit.
Use the following command to determine the point where the cells are being dropped.
| Command | Task |
|---|---|
show atm vc traffic interface atm card/subcard/port | Check the virtual circuits for interface where cells are being dropped. |
Use the following steps to troubleshoot a virtual connection to determine where the cells are being dropped along the length of the circuit.
Step 1 Use the show atm vc traffic interface atm command to look for mismatching numbers on both ends of the cable starting with the backbone interface connection at the ATM switch in the administration building and ending with the backbone interface connection at the manufacturing building.
AdminFl1Ls1# show atm vc traffic interface atm 1/0/0 Interface VPI VCI Type rx-cell-cnts tx-cell-cnts ATM3/1/0 0 5 PVC 672286 672286 ATM3/1/0 0 16 PVC 45 45
ATM3/1/0 0 18 PVC 730020 730155 ATM3/1/0 12 67 PVC 0 0 AdminFl1Ls1#
Step 2 Use the same command to look for mismatching numbers on the interface connection at the ATM switch in the manufacturing building.
ManuFl1Ls1# show atm vc traffic interface atm 0/1/0 Interface VPI VCI Type rx-cell-cnts tx-cell-cnts ATM0/1/0 0 5 PVC 672286 672286 ATM0/1/0 0 16 PVC 45 45
ATM0/1/0 0 18 PVC 730020 730155 ATM0/1/0 12 67 PVC 0 0 ManuFl1Ls11#
Step 3 Use the same command to look for mismatching numbers on the interface connection at the ATM switch to Catalyst 5000 Fast Ethernet switch in the manufacturing building.
ManuFl1Ls1# show atm vc traffic interface atm 4/0/0 Interface VPI VCI Type rx-cell-cnts tx-cell-cnts ATM4/0/0 0 5 PVC 672286 672286 ATM4/0/0 0 16 PVC 45 45
ATM4/0/0 0 18 PVC 730020 155 ATM4/0/0 12 67 PVC 0 0 ManuFl1Ls11#
Notice that the number of received and transmitted cell counts are vastly different, which indicates that this is the interface where the cells are being dropped.
Continue with the next phase of troubleshooting to determine why the cells are being dropped.
This section describes troubleshooting a line and circuit to see if they have been oversubscribed and are dropping cells.
Use the following commands to check the line and circuit under test for oversubscription:
| Command | Task |
|---|---|
show interface atm card/subcard/port | Check to see if the line is oversubscribed. |
show atm interface atm card/subcard/port | Check to see if the circuit is oversubscribed. |
Use the following steps to troubleshoot a virtual connection to check the line and circuit under test for oversubscription:
Step 1 Use the show interface atm command to check ATM interface 1/0/0 for oversubscription:
Step 2 Use the show atm interface atm command to check ATM interface 4/0/0 for oversubscription:
If the line or circuit is oversubscribed causing cells to be dropped, add more interfaces or circuits between the switches.
If you determine that the line or circuit is oversubscribed refer the chapter "Configuring Virtual Circuits," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Continue with the next phase of troubleshooting if you still have not determined the problem why the cells are being dropped.
This section describes troubleshooting circuit traffic priority and policing. If a circuit is configured with multiple traffic types and some have a higher priority, or QoS, than some cells, with a lower priority, are going to be dropped on a congested circuit.
For detailed information see the chapter "Configuring Resource Management," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Use the following commands to determine the configuration cell traffic priority and policing:
| Command | Task |
|---|---|
show atm interface resource atm card/subcard/port | Confirm the configuration of resource management looking for traffic priority conflicts. |
show atm vc interface atm card/subcard/port vpi vci | Confirm the configuration of the VC looking for policing conflicts. |
Use the following steps to determine the configuration cell traffic priority and policing:
Step 1 Use the show atm resources atm command to confirm traffic priority:
Step 2 Use the show atm vc interface atm command to confirm traffic policing:
If you determine that traffic priority or policing is causing cells to be dropped refer to the chapter "Configuring Resource Management," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Continue with the next phase of troubleshooting dropped cell if you still have not determined the problem.
This section describes troubleshooting network timing configuration. If the network timing is misconfigured, the network clock could become unsynchronized and the switch could start dropping cells.
For detailed information see the section "Configure Network Clocking," in the chapter "Initially Configuring the LightStream 1010 ATM Switch," of the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Use the following commands to determine the clocking configuration of the interface:
| Command | Task |
|---|---|
show network-clocks | Show the network clocking configuration. |
show running-config | Show the interface clock source configuration. |
show controllers [atm card/subcard/port] | Show the interface controller status. |
Use the following steps to determine the clocking configuration of the interface:
Step 1 Use the show network command to display the switch clock source configuration.
ManuFl1Ls11# show network Priority 1 clock source: ATM0/0/0 Priority 2 clock source: ATM0/0/3 Priority 3 clock source: ATM1/0/0 Priority 4 clock source: No clock Priority 5 clock source: System clock Current clock source: ATM0/0/0, priority: 1 ManuFl1Ls11#
Step 2 Make note of the interface configured as Priority 1 clock source.
Step 3 Use the show running-config command to display the clock source configuration of ATM interface 4/0/0:
ManuFl1Ls11# show running-config Building configuration... Current configuration: ! version 11.2 no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! boot bootldr bootflash:/tftpboot/ls1010-wp-mz.112-1.4.WA3.0.15 ! network-clock-select 2 ATM3/1/0 <Information Deleted> ! interface ATM4/0/0 no keepalive atm manual-well-known-vc atm access-group tod1 in atm pvc 0 35 rx-cttr 3 tx-cttr 3 interface ATM2/0/0 0 any-vci encap qsaal atm route-optimization soft-vc interval 360 time-of-day 18:0 5:0
clock-source network-derived ! <Information Deleted> ManuFl1Ls11#
The clock source field indicates the clocking configuration of ATM interface 4/0/0.
Step 4 Use the show controllers atm card/subcard/port command to display the interface controller status of ATM interface 4/0/0:
ManuFl1Ls11# show controllers atm 4/0/0 IF Name: ATM4/0/0 Chip Base Address: A8808000 Port type: 155UTP Port rate: 155 Mbps Port medium: UTP Port status:SECTION LOS Loopback:None Flags:8300
TX Led: Traffic Pattern RX Led: Traffic Pattern TX clock source: network-derived Framing mode: sts-3c Cell payload scrambling on Sts-stream scrambling on OC3 counters: Key: txcell - # cells transmitted rxcell - # cells received b1 - # section BIP-8 errors b2 - # line BIP-8 errors b3 - # path BIP-8 errors ocd - # out-of-cell delineation errors - not implemented g1 - # path FEBE errors z2 - # line FEBE errors chcs - # correctable HEC errors uhcs - # uncorrectable HEC errors <Information Deleted> phy_tx_cnt:0, phy_rx_cnt:0 ManuFl1Ls11#
Step 5 Check the TX clock source field. This field indicates that the clocking configuration of the interface is either internal or network derived.
If you determine that the clock configuration is causing cells to be dropped refer to the chapter "Initially Configuring the ATM switch," in the LightStream 1010 ATM Switch Software Configuration Guide for configuration information.
Posted: Fri Apr 9 10:29:44 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.