![]() |
ATM and Layer 3 Troubleshooting Guide, 12.0(13)W5(19)
|
|||||||||||||||||||||||||||||||||
Troubleshooting Switch Router ATM Network Connections
![]() |
||||||||||||||||||||||||||||||||||
|
Table of ContentsTroubleshooting Switch Router ATM Network ConnectionsChecking Network Connections Troubleshooting PVP and PVC Connections Checking the PVC Interface Status
Troubleshooting Soft PVC ConnectionsChecking the VPI and VCI Numbers Checking the VPI and VCI Ranges Checking the UBR Resources Checking the VBR and CBR Resources Debugging the PVC Connection Management Checking the Interface Status
Troubleshooting SVC Connections on a PNNI Routing NetworkChecking the VPI Number, VCI Number, and ATM Address Checking the Connection Management Debugging the Connection Management Checking the SVC Status at the End UNI Interface
Troubleshooting the PNNI DatabaseChecking UNI Interfaces Debugging SVC Signalling Alternate SVC Diagnostics Debugging PNNI SVC Routing Checking ATM Routes Checking PNNI Topology Checking SVC Downstream Checking PNNI Neighbor Database Synchronization
Troubleshooting PNNI Peer Group LeadersChecking the Flat Network or the Database Within the Same Peer Group Checking the PNNI Hierarchical Network Database for Different Peer Groups Troubleshooting the PNNI Lowest Level Interface Checking the PNNI Lowest Level Interface
Troubleshooting PNNI SVCC-RCC and Higher Level LinksChecking the PNNI and Signalling Control Channels Checking PNNI PVC Status on Lowest Level Interfaces Checking PNNI Interface Metric Configuration for Lowest Level Interfaces Debugging PNNI Hello State at the Lowest Level Checking the PNNI Aggregated Horizontal Link Interface Status
Troubleshooting PNNI Hierarchical NetworksChecking SVCC-RCC Status Checking SVCC-RCC Hello State Debugging SVCC-RCC and Higher Level Link Problems Checking Uplinks for Peer Group
Troubleshooting PNNI Addresses and Address SummarizationChecking Missing Upnode or Aggregation Token Pairs Checking the Induced Port on the LGNs Checking Link Aggregation Troubleshooting Virtual Path Tunnel Connections Checking VP Tunnel Configuration
Troubleshooting Dropped ConnectionsChecking Virtual Path PVP Configuration Debugging VP Tunnel Connection Management Determining Cell Drop Location
Checking Line and Circuit Oversubscription Checking Traffic Priority Checking Network Circuit Timing Troubleshooting Switch Router ATM Network ConnectionsThis chapter describes troubleshooting information about connectivity and performance problems in ATM switching network connections, and contains the following sections:
Checking Network ConnectionsBefore you begin, make sure that all physical port connections are working correctly. See "Troubleshooting Switch Router ATM Interface Connections." Confirm the following:
Troubleshooting PVP and PVC ConnectionsThis section describes how to troubleshoot permanent virtual paths (PVPs) and permanent virtual channels (PVCs). PVP and PVC connections are used primarily between buildings as the backbone connection and between frequently accessed hosts, such as the Domain Name System (DNS) server. In the example network in Figure 6-1, the primary PVC configured as the backbone connection between the switch router on Floor 1 in the administration building and the switch router on Floor 1 in the manufacturing building has the following virtual path identifier (VPI) and virtual channel identifier (VCI) numbers: Figure 6-1 PVC VPI and VCI Test in the Example Network This section contains the following procedures: For detailed configuration information, refer to the "Configuring Virtual Connections" chapter in the ATM Switch Router Software Configuration Guide. For detailed information about configuring PVCs and traffic shaping on the Catalyst 5000 and 6000 ATM modules, refer to the ATM Configuration Guide and Command Reference: Catalyst 5000 and 6000 ATM Modules. Checking the PVC Interface StatusUse the following command to confirm that the configured PVC interface status is up: Follow these steps to check the interface status: Step 1 Use the show atm status command to check the status of the interface PVP. Step 2 Check the IF (Interface) Status field to confirm that the interface is up. If it is not, see "Troubleshooting Switch Router ATM Interface Connections." Step 3 Check the Admin (Administration) Status field to confirm that the interface is up. If it is not, see "Troubleshooting Switch Router ATM Interface Connections." Checking the VPI and VCI NumbersUse the following command to confirm the configured PVC interface VPI and VCI numbers: Follow these 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 the numbers at both ends of the connection between the administration building and the manufacturing building: Step 2 Check the VPI and VCI fields. They show the VPI and VCI of the PVC connection at the administration building. Step 3 Check the Cross-connect-interface and Cross-connect-VPI and Cross-connect-VCI fields. They indicate the VPI and VCI of the PVC connection at the manufacturing building. Checking the VPI and VCI RangesUse the following commands to check the VPI and VCI ranges of the PVC connection: Follow these steps to check the VPI and VCI ranges of the PVC connection at the administration building: Step 1 Use the show atm ilmi-status atm command to confirm the ranges of the connection at the administration building. Step 2 Check the Peer MaxVPCs and Peer MaxVCCs fields. They indicate the VPI and VCI ranges of the PVC connection at the manufacturing building. Step 3 Use the show atm ilmi-status atm command to confirm VPI and VCI ranges of the PVC connection at the manufacturing building. Step 4 Check the Peer MaxVPCs and Peer MaxVCCs fields. They indicate the VPI and VCI ranges of the PVC connection at the administration building. Step 5 If either the VPI or VCI of the PVC are configured incorrectly, refer to Chapter 6, "Configuring Virtual Connections," of the ATM Switch Router Software Configuration Guide . Checking the UBR ResourcesUse the following commands to confirm unspecified bit rate (UBR) for the PVP and PVC best-effort connection limit configuration:
Follow these steps to confirm UBR for the PVC and PVP 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. Step 2 Check the Best effort connection limit field max (maximum) connections number. If the number is too low, increase it using the atm cac best-effort-limit interface command. Step 3 Check the Best effort connection field to determine the number of established connections. If no connections are available, the connection fails. To modify the best-effort connection limit, refer to the "Configuring Resource Management" chapter in the ATM Switch Router Software Configuration Guide . Checking the VBR and CBR ResourcesUse the following commands to confirm the VBR and CBR resources of the configured PVP:
The Catalyst 5000 and 6000 ATM modules do not support the show atm interface resource atm command. To check the status of a virtual connection on a Catalyst 5000 or 6000 ATM module, use the show atm vc command. For detailed information about configuring traffic shaping on the Catalyst 5000 and 6000 ATM modules, refer to the ATM Configuration Guide and Command Reference: Catalyst 5000 and 6000 ATM Modules. The following example shows the status for all configured VCs on a Catalyst 5000 or 6000 ATM module: The following example shows how to display the status for a specific VCD on a Catalyst 5000 or 6000 ATM module: Debugging the PVC Connection ManagementUse the following commands to debug the PVC connection management:
Troubleshooting Soft PVC ConnectionsThis section describes how to troubleshoot a soft PVC configuration. Soft PVCs are used primarily to connect hosts that do not support signalling and cannot use SVCs. In the example network in Figure 6-2, the connection between the switch router on Floor 1 in the administration building and the e-mail server has the following VPI and VCI numbers and ATM address: Figure 6-2 Soft PVC Test in the Example Network This section contains the following procedures: For detailed information, refer to the "Configuring Virtual Connections" chapter in the Checking the Interface StatusUse the following command to check soft PVC connection interface status: Follow these steps to confirm the soft PVC interface is up: Step 1 Use the show atm status command to check the interface status. Step 2 Confirm that the IF Status field corresponding to the soft PVC interface is up. If it is down, see "Troubleshooting Switch Router ATM Interface Connections." Step 3 Confirm that the Admin Status field is up. If it is down, see "Troubleshooting Switch Router ATM Interface Connections." Step 4 If both fields are up, continue with the following troubleshooting sections. Checking the VPI Number, VCI Number, and ATM AddressUse the following command to confirm the VPI, VCI, and ATM address of the configured soft PVC: Follow these 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 the numbers at both ends of the connection between the administration building switch router and the e-mail server that does not support signalling: 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 VCI 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 configurations are incorrect, refer to the "Configuring Virtual Connections," of the ATM Switch Router Software Configuration Guide . 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 field. The number should be 0. Checking the Connection ManagementUse the following command to check soft PVC connection management:
Debugging the Connection ManagementUse the following commands to debug the PVC connection management:
Troubleshooting SVC Connections on a PNNI Routing NetworkThis section describes how to troubleshoot switched virtual channel (SVC) connections, using the show command and debug command. These commands can be used to troubleshoot problems with SVC setup between end systems. The SVCs are automatically configured on the switch router when the cables are connected and the switch router is powered on. In the example network in Figure 6-3, EndSys1 originates the signalling messages, which attempt to establish an SVC connection to EndSys2. In this example, Endsys1 connects directly to the switch router, named RemDvLs1, over the User-Network Interface (UNI) connection at ATM interface 3/1/1. Endsys2 is connected directly to the switch router, EngFl1Ls1, over the UNI connection at ATM interface 0/0/0. Both switch routers connect to other switch routers using network-to-network interface (NNI) connections. Figure 6-3 SVC \QConnection Example This section contains the following procedures: Checking the SVC Status at the End UNI InterfaceUse the following commands to check SVC interface status: Follow these steps to confirm whether there is a new SVC connection from the originating side of the UNI interface to the intended remote or destination ATM network service access point (NSAP) address: Step 1 Use the show atm vc signalling interface atm card/subcard/port detail command on the originating side. |