Troubleshooting Switch Router ATM Interface Connections

Table of Contents

Troubleshooting Switch Router ATM Interface Connections
Performing Basic Interface Checks
Determining Network Connectivity
Performing OAM Loopback Tests
Using the debug Commands to Troubleshoot an Interface
Troubleshooting 155-Mbps and 622-Mbps Interfaces
Troubleshooting OC-3c, OC-12c, and OC-48c Interfaces
Troubleshooting T1 and E1 Interfaces
Troubleshooting DS3 and E3 Interfaces
Troubleshooting CES T1 and CES E1 Interfaces
Troubleshooting 25-Mbps Interfaces
Troubleshooting CDS3 Frame Relay Interfaces

Troubleshooting Switch Router ATM Interface Connections


This chapter provides troubleshooting information about connectivity and performance problems in the physical interfaces of a switch router.

The chapter includes the following sections:

Performing Basic Interface Checks

This section outlines the steps for performing basic interface checks and verifies that an ATM switch router interface is enabled and functioning correctly.

Always check the following when an interface fails:

  • The port free of dust and debris?
  • Are the cables inserted properly?
  • Do the transmit and receive cable pairs match?
  • Are the cables the proper type?

  • Note   Just because the connector fits, does not mean the wires in the cable are necessarily cross-connected correctly, and the cable is not necessarily the correct type.

  • Are the cables reliable? If not, try a different cable.
  • Are the interfaces on both sides of the cables enabled and in no-shutdown mode?
  • Are the interfaces configured properly (for example, framing mode, line coding, scrambling mode)?
  • Are the interfaces on both ends of the cable the same type of interface?

Use the following command to check the ATM physical interface configuration:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

Follow these steps to troubleshoot the physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to display status and error information about an interface.

Switch# show interfaces atm 1/0/0
ATM1/0/0 is up, line protocol is up
Hardware is oc3suni
MTU 4470 bytes, sub MTU 4470, BW 156250 Kbit, DLY 0 usec, rely 255/255, load 1/255
  Encapsulation ATM, loopback not set, keepalive not supported
  Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
527152 packets input, 27939056 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    527246 packets output, 27944038 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM or constant bit rate (CBR) field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see whether the status is up.

If down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • The clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide for configuration information.
  • The hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input and Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the cyclic redundancy check (CRC) field. The presence of many CRC errors, but not many collisions, indicates excessive noise. If the number is too high, check the cables for damage. If you are using unshielded twisted-pair (UTP) cables, make sure you are using category 5 cable and not another type, such as category 3.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 8   Check the collisions field. It shows the total number of collisions compared to the total number of output packets and should be approximately 0.1 percent or less. If the number is too high, perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide for configuration information.

If you still have not determined the problem, continue with the next phase of basic interface troubleshooting.

Checking Cell Rates

This procedure determines if the cell rate for an interface is correctly configured.

Use the following command to check the cell rate on a physical interface:

Command Purpose

show atm interface atm card/subcard/port

Confirms the ATM interface configuration.

Use the following steps to check the cell rate of the interface:


Step 1   Use the show atm interface atm command to display information about an interface.

Switch# show atm interface atm 1/0/0
Interface: ATM1/0/0 Port-type: oc3suni
Status: UP Admin Status: up
Auto-config: enabled AutoCfgState: completed
IF-Side: Network IF-type: NNI
Uni-type: not applicable Uni-version: not applicable
Max-VPI-bits: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255
ConfMinSvccVci: 33 CurrMinSvccVci: 33
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0040.0b0a.2a81.4000.0c80.8000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
4 0 0 0 0 0 0 4 4
Logical ports(VP-tunnels): 0
Input cells: 528135 Output cells: 528235
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 344844, Output AAL5 pkts: 344878, AAL5 crc errors: 0
Switch#

Step 2   Check the IF (interface) Status and Admin (administration) Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 CRC errors field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collisions. This indicates excessive noise.
  • Cable damage. If you are using UTP cables, make sure you are using category 5 cable and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide for configuration information. If you still have not determined the problem, continue with the next phase of basic interface troubleshooting.

Determining Network Connectivity

To check ATM connection reachability and network connectivity, use the ping atm interface atm command in either privileged or user mode. You can use either an IP address or an ATM address prefix as a ping destination. You can also ping a neighbor switch router by selecting the segment loopback option. In privilege extended command mode, you can select other parameters such as repeat count and timeout values.

Command Purpose

ping atm interface atm card/subcard/port vpi vci {atm-prefix prefix | end-loopback |
ip-address ip-address | seg-loopback}

Checks the interface connection.

Follow these steps to ping a specific ATM prefix in both normal and extended mode:


Step 1   Use the ping atm interface atm command, in normal mode, to confirm connectivity through a specific interface to an ATM address prefix.

Switch# ping atm interface atm 1/0/0 0 5 atm-prefix 47.009181000000000000000001
Type escape sequence to abort.
Sending 5, 53-byte OAM Echoes to 47.0091.8100.0000.0000.0000.0001..., timeout is
5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

Step 2   Check the Success rate field. It should be 100 percent. If not, check the interface configuration.

Step 3   Use the ping atm interface atm command, in extended mode, to confirm connectivity through a specific interface to an ATM address prefix and modify the default repeat or timeout.

Switch# ping
Protocol [ip]: atm
Interface [card/subcard/port]: 1/0/0
VPI [0]: 0
VCI [0]: 5
Send OAM-Segment-Loopback ? [no]:
Target IP address:
Target NSAP Prefix: 47.009181000000000000000001
Repeat count [5]:
Timeout in seconds [5]:10
Type escape sequence to abort.
Sending 5, 53-byte OAM Echoes to 47.0091.8100.0000.0000.0000.0001..., timeout is
10 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

Step 4   Check the Success rate field. It should be 100 percent. If not, check the interface configuration.


Note    If you skip both destination IP address and the ATM prefix fields, the extended ping considers its neighbor switch as its destination and uses a segment-Loopback operation, administration, and maintenance (OAM) cell. In an IP address or ATM prefix case, the ping command always uses an end-to-end OAM loopback cell.





If the success rate is less than 100 percent, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide and confirm the interface configuration.

Performing OAM Loopback Tests

OAM performs fault management and performance management functions at ATM management-plane (M-plane) layer.


Note   Current OAM implementation supports only the fault management function, which includes connectivity verification and alarm surveillance.

The ATM switch router fully supports the following ATM OAM cell flows:

  • F4 flows—OAM information flows between network elements used within virtual paths to report an unavailable path or a virtual path (VP) that cannot be guaranteed.
  • F5 flows—OAM information flows between network elements used within virtual connections to report degraded virtual channel (VC) performance such as late arriving cells, lost cells, and cell insertion problems.

You can configure both F4 and F5 flows as either end-to-end or segment-loopback, and they can be used with alarm indication signal (AIS) and remote defect indication (RDI) functions.


Note   Cells can be sent either on demand or periodically to verify link and connection integrity.

In addition to the standard OAM functions, the ATM switch router can also send OAM pings. See the "Determining Network Connectivity" section. Using OAM cells containing the ATM node addresses or IP addresses of intermediate switch routers, you can determine the integrity of a chosen connection at any intermediate point along that connection. With this information, you can debug and troubleshoot the network connection.

OAM Operation

OAM software implements ATM Layer F4 and F5 OAM fault management functions. OAM performs standard loopback (end-to-end or segment) and fault detection and notification (AIS and RDI) for each connection. It also maintains a group of timers for the OAM functions. When there is an OAM state change such as loopback failure, OAM software notifies the connection management software. The network operator can enable or disable OAM operation for the following ATM switch router components:

  • The entire ATM switch router
  • A specific ATM interface
  • Each ATM connection

OAM AIS, RDI, and loopback operations are enabled or disabled for the entire switch router using the atm oam command in global configuration mode. Use the atm oam command in interface mode to configure OAM on a specific connection. For more information about configuring OAM operations, refer to the "Configuring Operation, Administration, and Maintenance" chapter in the
ATM Switch Router Software Configuration Guide .


Note   These OAM configuration commands are not stored in the nonvolatile random-access memory (NVRAM).

If OAM operation is disabled, outgoing OAM cells are not generated, and all incoming OAM cells are discarded.

To support various OAM operations, the ATM switch router hardware provides OAM cell routing functions on a per-connection basis for each direction and for different OAM cell spans (segment and end-to-end). The hardware OAM cell routing determines the destination of an OAM cell received from the link or the network and then determines whether OAM cells are processed by the ATM switch router software.

The hardware can perform the following functions on OAM cells:

  • Intercept—Intercepted to the route processor queue and processed by the ATM switch router software
  • Relay—Relayed along user cells by hardware without any software processing
  • Discard—Discarded by hardware

An ATM connection consists of a group of network points, which are the edges of each ATM switch router or end system.

Each point can be one of the following:

  • Connection endpoint—The end of a connection where the user ATM cells are terminated
  • Segment endpoint—The end of a connection segment
  • Connecting point—The middle point of a connection segment

Figure 5-1 shows the various loopback operations available.


Figure 5-1   OAM Loopback Operations


OAM Loopback Testing

You can use the loopback test to pinpoint faults by looping a signal at various points in the network. Use the loopback test before and after the initiation of service. Figure 5-2 shows how ATM OAM cell loopbacks are performed first across the interface and then across different segments of the connection.


Figure 5-2   Loopback Testing Process


An ATM switch router generates the OAM cells and forwards them to another network element, which is responsible for returning them to the generating network elements.

Each loopback cell contains the ID of the generating network element and the ID of the network element that is looping the cells back to the originator. Any intermediate site must pass the cells on to the loopback site (the farthest point to which the cells progress) and the generating site (the point to which the cells return).

See "ATM Cell Structures," for a format description of the OAM loopback cell.

The ATM switch router provides the following three types of loopback tests:

  • Diagnostic
  • Line
  • PIF (physical interface)

  • Note   If the loopback test is successful, data is reaching the I/O module properly. However, a successful test does not verify whether the I/O module correctly encodes the data sent onto the line.

Configuring Loopback Examples

The following examples show how to perform loopback tests on the interfaces shown in Figure 5-3.

If users connected to the Fast Ethernet Catalyst 5000 switch in the manufacturing building are not able to connect to the other users outside their building (including the DNS server in the administration building), you should try a loopback test. Use the procedures described in this section to test the ATM switch router connections starting at the middle section and proceeding outward.


Figure 5-3   Loopback Test Configuration Example


Use the atm ping command to confirm the ATM connection between the administration and manufacturing buildings.

Command Purpose

ping atm interface atm card/subcard/port vpi [vci] [atm-prefix prefix] | [end-loopback] | [ip-address ip-address] | [seg-loopback]}

Checks the interface connection.

Perform the interface loopback tests in the following order:

Test 1—Segment network-side loopback between ATM switch router AdminFl1Ls1, interface 1/0/0, and ATM switch router ManuFl1Ls1, interface 4/0/1

Test 2—Segment link-side loopback between the DNS server and ATM switch router AdminFl1Ls1, interface 4/0/0

Test 3—End-to-end loopback between the DNS server and the Catalyst 5000 Fast Ethernet switch, ManuFl1CaS1, interface 1/1

Test 1—Segment Network-Side Loopback Process

Follow these steps to ping the ATM virtual channel 2, 130 between the administration and manufacturing buildings, with a segment loopback signal in normal mode:


Step 1   Use the ping atm interface atm card/subcard/port command to confirm the VP connectivity.

AdminFl1Ls1# ping atm interface atm 1/0/0 2 seg-loopback
Type escape sequence to abort.
Sending Seg-Loopback 5, 53-byte OAM Echoes to a neighbor, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
AdminFl1Ls1#

Step 2   Use the same command to ping the ATM virtual channel 2, 130 between the administration and manufacturing buildings with a segment loopback signal in normal mode:

AdminFl1Ls1# ping atm interface atm 1/0/0 2 130 seg-loopback
Type escape sequence to abort.
Sending Seg-Loopback 5, 53-byte OAM Echoes to a neighbor, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
AdminFl1Ls1#

Step 3   Check the Success rate field. If the success rate is less that 100 percent, you have a problem on the 622-Mbps connection between the administration and manufacturing buildings.

Step 4   Check the cables and the interface configuration, using the procedures in the "Performing Basic Interface Checks" section.

If the success rate is 100 percent, then this segment of the connection is not the problem. Proceed with the next phase of the interface loopback test.





Test 2—Segment Link-Side Loopback Process

Log in to the ATM switch router in the manufacturing building and use the ping atm interface atm command again to confirm the ATM connection between the ATM switch router and the Catalyst 5000 switches in the manufacturing building.

Use the following steps to ping the ATM virtual path 2 between the ATM switch router and the Catalyst 5000 switches in the manufacturing building, with a segment loopback signal in normal mode:


Step 1   Use the ping atm interface atm card/subcard/port command to confirm the VP connectivity.

ManuFl1Ls1# ping atm interface atm 4/0/0 2 seg-loopback
Type escape sequence to abort.
Sending Seg -Loopback 5, 53-byte OAM Echoes to a neighbor, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
ManuFl1Ls1#

Step 2   Check the Success rate field. If the success rate is less that 100 percent, there is a problem on the OC-3 155-Mbps connection between the ATM switch router and the Catalyst 5000 switch in the manufacturing building.

Step 3   Check the cables and the interface configuration, using the procedures in the "Performing Basic Interface Checks" section.

If the success rate is 100 percent, then this segment of the connection is not the problem. Proceed with the next phase of the interface loopback test.





Test 3—End-to-End Loopback Process

Check the end-to-end connection between the DNS server and the Catalyst 5000 switch in the manufacturing building.

Following is an example of the steps to ping the entire ATM virtual path between the administration and manufacturing buildings, with an end-to-end loopback signal in normal mode:


Step 1   Use the ping atm interface atm card/subcard/port command to confirm the VP connectivity.

AdminFl1Ls1# ping atm interface atm 4/0/0 2 end-loopback
Type escape sequence to abort.
Sending end-Loopback 5, 53-byte OAM Echoes to a neighbor, timeout is 5 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Step 2   Check the Success rate field. If the success rate is less that 100 percent, you have a problem on the OC-3 155-Mbps connection between the ATM switch router and the Catalyst 5000 switch in the manufacturing building.

Step 3   Check the cables and the interface configuration using the procedures in the "Performing Basic Interface Checks" section.

If the success rate is 100 percent, then this segment of the connection is not the problem. Continue with the next phase of the interface test.





Using the debug Commands to Troubleshoot an Interface

The debug privileged EXEC commands can provide a wealth of information about the traffic being seen (or not seen) on an interface.


Caution   Exercise care when using debug commands. Many of these commands are processor intensive and can cause serious network problems (such as degraded performance or loss of connectivity) if they are enabled on an already heavily loaded switch router. When you finish using a debug command, remember to disable it with its specific no debug command (or use the no debug all command to turn off all debugging).

For detailed information about using the debug commands, see "Debugging a Switch Router."

To isolate problems and troubleshoot the physical connections of the ATM switch router, use the following debug commands in privileged EXEC mode. Use the no form of these commands to disable debugging.

Command Purpose

debug ports {aal5 [interface atm card/subcard/port] | dcu | ds3e3 | netclock | oc12 | oc3 | t1e1}

Starts debugging at the driver level for a specific port.

debug atm oam-all

Starts debugging, using generic OAM cells.

debug atm oam-pkt

Starts debugging, using OAM packets.

debug atm errors

Starts debugging to display all ATM errors.

no debug all

Disables all debugging.

Refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide to confirm the interface configuration.

Troubleshooting 155-Mbps and 622-Mbps Interfaces

This section describes specific processes and commands used to troubleshoot the 155-Mbps and 622-Mbps port adapters.

Port Adapter LEDs

The port adapter faceplate LEDs provide status information for individual 155-Mbps and 622-Mbps single-mode and multimode fiber-optic and UTP interface connections of the port adapter. The LEDs are described in Table 5-1.


Note   Use the show controllers command to display the LED status.

Table 5-1   155-Mbps and 622-Mbps Port Adapter LED Descriptions

LED Status Description

RX (Receive)

Off
Flashing green

Red

LOS1 or port adapter is shut down.
Cells are being received. LED blinks every 5 seconds and pulse rate increases with data rate.
Alarm (LOF2, LCD3, AIS4).

TX (Transmit)

Off
Flashing green
Flashing yellow
Steady yellow

No transmit line activity indication.
Cells are being transmitted. LED pulse rate increases with data rate.
Loopback.
FERF5 alarm.

1LOS = loss of signal

2LOF = loss of frame

3LCD = loss of cell delineation

4AIS = alarm indication signal

5FERF = far-end receive failure


Note   Single-mode fiber-optic interface connectors are blue, and multimode connectors are black.

Displaying Interface Port Configuration

To display the interface configuration, use the following commands:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm interface atm card/subcard/port

Shows the interface configuration.

show controllers atm card/subcard/port

Shows the interface memory management and error counters.

Follow these steps to troubleshoot a 155-Mbps or 622-Mbps physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to check the configuration.

Switch# show interfaces atm 1/0/0
ATM1/0/0 is up, line protocol is up
Hardware is oc3suni
MTU 4470 bytes, sub MTU 4470, BW 156250 Kbit, DLY 0 usec, rely 255/255, load 1/255
  Encapsulation ATM, loopback not set, keepalive not supported
  Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 2000 bits/sec, 6 packets/sec
5 minute output rate 3000 bits/sec, 9 packets/sec
4703704 packets input, 249296312 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     54 input errors, 55 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5737496 packets output, 304087288 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see whether the status is up.

If down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input and Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors, but not many collisions, indicates excessive noise. If the number of errors is too high, check the cables for damage. If you are using UTP cable, make sure you are using category 5 cables and not another type, such as category 3.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 8   Check the collisions field. It shows the total number of collisions compared to the total number of output packets, and it should be approximately 0.1 percent or less. If the number is too high, perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to show the configuration of a 155-Mbps or 622-Mbps interface:


Step 1   Use the show atm interface atm card/subcard/port command to check the configuration.

Switch# show atm interface atm 1/0/0
Interface: ATM1/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.0000.0000.0001.4000.0c80.8000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
2 0 12 0 0 0 0 14 16
Logical ports(VP-tunnels): 0
Input cells: 4703972 Output cells: 5737883
5 minute input rate: 2000 bits/sec, 4 cells/sec
5 minute output rate: 4000 bits/sec, 9 cells/sec
Input AAL5 pkts: 169899, Output AAL5 pkts: 644764, AAL5 crc errors: 0
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 crc errors field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collisions. This indicates excessive noise.
  • Cable damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to display the memory management and error counters of a 155-Mbps or 622-Mbps ATM interface:


Step 1   Use the show controllers atm card/subcard/port command to check memory management and error counters.

Switch# show controllers atm 1/0/0
IF Name: ATM1/0/0 Chip Base Address: A8A08000
Port type: OC3 Port rate: 155 Mbps Port medium: MM Fiber
P ort status:Good Signal Loopback:None Flags:8308
T X 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:4789577, phy_rx_cnt:4704918
Switch#

Step 2   Check the Port status field. It should read "Good Signal."

Step 3   Check the Loopback field. It should read "None."

Step 4   Check the TX Led field. It should read "Traffic Pattern." If it does not, see Table 5-1 for LED descriptions.

Step 5   Check the RX Led field. It should read "Traffic Pattern." If it does not, see Table 5-1 for LED descriptions.

Step 6   Check the Framing mode field. It should match the framing mode configuration of the destination port.

Step 7   Check the Cell payload scrambling field. It should match the cell payload scrambling mode configuration of the destination port.

Step 8   Check the Sts-stream scrambling field. It should match the STS stream scrambling mode configuration of the destination port.





If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly, proceed with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."

Troubleshooting OC-3c, OC-12c, and OC-48c Interfaces

This section describes specific processes and commands used to troubleshoot the OC-3c, OC-12c, and OC-48c interface modules.

Interface Module LEDs

The interface module faceplate LEDs provide status information for individual single-mode and multimode fiber-optic interface connections of the interface module. The LEDs are described in Table 5-2.


Note   Use the show controllers command to display the LED status.

Table 5-2   OC-3c, OC-12c, and OC-48c Interface Module LED Descriptions

LED Status Description

LINK

Off
Green

Carrier detect signal not received.
Carrier detect signal received.

RX (Receive)

Off
Flashing green

Red

LOS or interface module is shut down.
Cells are being received. LED blinks every 5 seconds and pulse rate increases with data rate.
Alarm (LOF1, OCD2, AIS3, LOP4, RDI5, LCD6, UNEQ7, PLM8).

TX (Transmit)

Off
Flashing green
Flashing yellow
Steady yellow

No transmit line activity indication.
Cells are being transmitted. LED pulse rate increases with data rate.
Loopback.
RDI.

1LOF = loss of frame

2OCD = out of cell delineation

3AIS = alarm indication signal

4LOP = loss of pointer

5RDI = remote defect indicator

6LCD = loss of cell delineation (OC-48c)

7UNEQ = unequipped code (OC-48c)

8PLM = payload label mismatch (OC-48c)


Note   Single-mode fiber-optic interface connectors are blue, and multimode connectors are black.

Displaying Interface Port Configuration

To display the interface configuration, use the following commands:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm interface atm card/subcard/port

Shows the interface configuration.

show controllers atm card/subcard/port

Shows the interface memory management and error counters.

Follow these steps to troubleshoot an OC-3c, OC-12c, or OC-48c physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to check the configuration.

Switch# show interfaces atm 11/0/0
ATM11/0/0 is down, line protocol is down
Hardware is oc48c
MTU 4470 bytes, sub MTU 4470, BW 2488320 Kbit, DLY 0 usec, rely 0/255, load 15
  Encapsulation ATM, loopback not set, keepalive not supported
  Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see whether the status is up.

If the interface is down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the interface module.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input and Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors, but not many collisions, indicates excessive noise. If the number of errors is too high, check the cables for damage. If you are using UTP cable, make sure you are using category 5 cables and not another type, such as category 3.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.





If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM  Switch Router Software Configuration Guide.

Follow these steps to show the configuration of an OC-3c, OC-12c, or OC-48c interface:


Step 1   Use the show atm interface atm card/subcard/port command to check the configuration.

Switch# show atm interface atm 1/0/0
Interface: ATM1/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.0000.0000.0001.4000.0c80.8000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
2 0 12 0 0 0 0 14 16
Logical ports(VP-tunnels): 0
Input cells: 4703972 Output cells: 5737883
5 minute input rate: 2000 bits/sec, 4 cells/sec
5 minute output rate: 4000 bits/sec, 9 cells/sec
Input AAL5 pkts: 169899, Output AAL5 pkts: 644764, AAL5 crc errors: 0
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 crc errors field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collisions. This indicates excessive noise.
  • Cable damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to display the memory management and error counters of an OC-3c, OC-12c, or OC-48c ATM interface:


Step 1   Use the show controllers atm card/subcard/port command to check memory management and error counters.

Switch# show controllers atm 1/0/0
IF Name: ATM1/0/0 Chip Base Address: A8A08000
Port type: OC3 Port rate: 155 Mbps Port medium: MM Fiber
P ort status:Good Signal Loopback:None Flags:8308
T X 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:4789577, phy_rx_cnt:4704918
Switch#

Step 2   Check the Port status field. It should read "Good Signal."

Step 3   Check the Loopback field. It should read "None."

Step 4   Check the TX Led field. It should read "Traffic Pattern." If it does not, see Table 5-1 for LED descriptions.

Step 5   Check the RX Led field. It should read "Traffic Pattern." If it does not, see Table 5-1 for LED descriptions.

Step 6   Check the Framing mode field. It should match the framing mode configuration of the destination port.

Step 7   Check the Cell payload scrambling field. It should match the cell payload scrambling mode configuration of the destination port.

Step 8   Check the Sts-stream scrambling field. It should match the STS stream scrambling mode configuration of the destination port.





If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly, proceed with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."

Troubleshooting T1 and E1 Interfaces

This section describes specific processes and commands used to troubleshoot the T1 and E1 port adapters.

Port Adapter LEDs

The port adapter faceplate LEDs provide status information for individual T1 and E1 coaxial and UTP interface connections of the port adapter. The LEDs are described in Table 5-3.


Note   Use the show controllers command to display the LED status.

Table 5-3   T1 and E1 Port Adapter LED Descriptions

LED Status Description

RX (Receive)

Off
Flashing green

Red

LOS1 or port adapter is shut down.
Cells are being received. LED blinks every 5 seconds and pulse rate increases with data rate.
Alarm (LOF2, LCD3, AIS4).

TX (Transmit)

Off
Flashing green
Flashing yellow
Steady yellow

No transmit line activity indication.
Cells are being transmitted. LED pulse rate increases with data rate.
Loopback.
FERF5 alarm.

1LOS = loss of signal

2LOF = loss of frame

3LCD = loss of cell delineation

4AIS = alarm indication signal

5FERF = far-end receive failure

Displaying Interface Port Configuration

To display the T1 and E1 interface configuration, use the following commands:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm interface atm card/subcard/port

Shows the interface configuration.

show controllers atm card/subcard/port

Shows the interface memory management and error counters.

Follow these steps to troubleshoot the T1 or E1 physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to check the configuration.

Switch# show interfaces atm 0/1/0
ATM0/1/0 is down, line protocol is down
Hardware is t1suni
MTU 4470 bytes, sub MTU 0, BW 1500 Kbit, DLY 0 usec, rely 0/255, load 1/255
  Encapsulation ATM, loopback not set, keepalive not supported
  Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
  0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see that the status is up.

If the status is down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input and Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors, but not many collisions, indicates excessive noise. If the number is too high, check the cables for damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 8   Check the collisions field. It shows the total number of collisions compared to the total number of output packets, and it should be approximately 0.1 percent or less. If the number is too high, perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to troubleshoot the configuration of a T1 or E1 interface:


Step 1   Use the show atm interface atm card/subcard/port command to check the configuration.

Switch# show atm interface atm 0/1/0
Interface: ATM0/1/0 Port-type: t1suni
IF Status: DOWN Admin Status: down
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: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255
ConfMinSvccVci: 33 CurrMinSvccVci: 33
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0000.0000.0001.4000.0c80.1000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
2 0 0 0 0 0 0 2 0
Logical ports(VP-tunnels): 0
Input cells: 0 Output cells: 0
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 crc error field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collisions. This indicates excessive noise.
  • Cable damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to display the memory management and error counters of a T1 or E1 ATM interface:


Step 1   Use the show controllers atm card/subcard/port command to check memory management and error counters.

Switch# show controllers atm 0/1/0
IF Name: ATM0/1/0, SUNI PDH Chip Base Address: A8908000
IF Name: ATM0/1/0, framer Base Address: A8909000
Port type: T1 Port rate: 1.5 Mbps Port medium: UTP
Port status:Good signal Loopback:None Flags:8000
showdow clk reg value AA
TX Led: Traffic Pattern RX Led: Traffic Pattern CD Led: off
TX clock source: network-derived
T1 Framing Mode: ESF PLCP format
FERF on AIS is on
FERF on LCD is on (n/a in PLCP mode)
FERF on RED is on
FERF on OOF is on
FERF on LOS is on
LBO: between 0-110
Counters:
Key: txcell - # cells transmitted
rxcell - # cells received
lcv - # line code violations
ferr - # framing bit error event counter
bee - # bit error event, CRC-6 in ESF, Framing bit error in SF
b1 - # PLCP BIP errors
fe - # PLCP framing pattern octet errors
plcp_febe- # PLCP FEBE errors
hcs - # uncorrectable HEC errors
uicell - # unassigned/idle cells dropped
<Information Deleted>
Dump of internal registers for mask
9 9 9 9 1 1 0 0
Switch#

Step 2   Check the Port status field. It should read "Good Signal."

Step 3   Check the Loopback field. It should read "None."

Step 4   Check the TX Led field to see that it reads "Traffic Pattern." If it does not, see Table 5-3 for LED descriptions.

Step 5   Check the RX Led field to see that it reads "Traffic Pattern." If it does not, see Table 5-3 for LED descriptions.

Step 6   Check the CD field to see that it reads "Traffic Pattern." If it does not, see Table 5-3 for LED descriptions.





If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly, proceed with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."

Troubleshooting DS3 and E3 Interfaces

This section describes specific processes and commands used to troubleshoot the DS3 and E3 port adapters.

Port Adapter LEDs

The port adapter faceplate LEDs provide status information for individual DS3 and E3 coaxial interface connections of the port adapter. The LEDs are described in Table 5-4.


Note   Use the show controllers command to display the LED status.

Table 5-4   DS3 and E3 Port Adapter LED Description

LED Status Description

RX (Receive)

Off
Flashing green

Red

LOS1 or port adapter is shut down.
Cells are being received. LED blinks every 5 seconds and pulse rate increases with data rate.
Alarm (LOF2, LCD3, AIS4).

TX (Transmit)

Off
Flashing green
Flashing yellow
Steady yellow

No transmit line activity indication.
Cells are being transmitted. LED pulse rate increases with data rate.
Loopback.
FERF alarm.5

1LOS = loss of signal

2LOF = loss of frame

3LCD = loss of cell delineation

4AIS = alarm indication signal

5FERF = far-end receive failure

Displaying Interface Port Configuration

Use the following commands to display the DS3 or E3 interface configuration:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm interface atm card/subcard/port

Shows the interface configuration.

show controllers atm card/subcard/port

Shows the interface memory management and error counters.

Follow these steps to troubleshoot the DS3 or E3 physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to check the configuration.

Switch# show interfaces atm 0/1/0
ATM0/1/0 is down, line protocol is down
Hardware is ds3suni_Quad
MTU 4470 bytes, sub MTU 4470, BW 45000 Kbit, DLY 0 usec, rely 0/255, load 1/255
  Encapsulation ATM, loopback not set, keepalive not supported
  Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Replace faulty hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field. The status should be up.

If the interface is down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input or the Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors but not many collisions is an indication of excessive noise. If the number is too high, check the cables to determine if any are damaged. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 8   Check the Collisions field. This value indicates the total number of collisions compared to the total number of output packets and should be approximately 0.1 percent or less. If the number is too high, perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to show how to troubleshoot the configuration of a DS3 or E3 interface:


Step 1   Use the show atm interface atm card/subcard/port command to check the configuration.

Switch# show atm interface atm 0/1/0
Interface: ATM0/1/0 Port-type: ds3suni_Quad
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: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255
ConfMinSvccVci: 33 CurrMinSvccVci: 33
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0040.0b0a.2a81.4000.0c80.1000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
2 0 0 0 0 0 0 2 0
Logical ports(VP-tunnels): 0
Input cells: 0 Output cells: 0
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 crc error field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collisions. This indicates excessive noise.
  • Cable damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to display the memory management and error counters of a DS3 or E3 ATM interface:


Step 1   Use the show controllers atm card/subcard/port command to check memory management and error counters.

Switch# show controllers atm 0/1/0
IF Name: ATM0/1/0, Chip Base Address: A8908000
Port type: DS3 Port rate: 45 Mbps Port medium: Coax
Port status:Good Signal Loopback:None Flags:8000
TX Led: Traffic Pattern RX Led: Traffic Pattern TX clock source: network-de
rived
DS3 Framing Mode: cbit adm
FERF on AIS is on
FERF on LCD is on (n/a in PLCP mode)
FERF on RED is on
FERF on OOF is on
FERF on LOS is on
LBO: <= 225'
PDH counters:
Key: txcell - # cells transmitted
rxcell - # cells received
lcv - # line code violations
ferr - DS3: # F-bit/M-bit errors; E3: # framing errors
exzs_ier - T3: # excessive zeros; E3 G.832: # iec errors
perr - DS3: # P-bit errors; E3 G.832: # BIP-8 errors
cperr - DS3: # path parity errors
febe - DS3 or E3 G.832: # FEBE errors
b1 - # PLCP BIP errors
fe - # PLCP framing pattern octet errors
plcp_febe- # PLCP FEBE errors
hcs - # uncorrectable HEC errors
uicell - # unassigned/idle cells dropped
<Information Deleted>
Netclock Reg1 Shadow:55, Netclock Reg2 Shadow:1,
Interrupt Status:DF, ASP ClkSel:C7FF
Switch#

Step 2   Check the Port status field. It should read "Good signal."

Step 3   Check the Loopback field. It should read "None."

Step 4   Check the TX Led field. It should read "Traffic Pattern." If it does not, see Table 5-4 for LED descriptions.

Step 5   Check the RX Led field. It should read "Traffic Pattern." If it does not, see Table 5-4 for LED descriptions.





If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly, proceed with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."

Troubleshooting CES T1 and CES E1 Interfaces

This section describes specific processes and commands used to troubleshoot T1 and E1 circuit emulation service (CES) port adapters.

Port Adapter LEDs

The port adapter faceplate LEDs provide status information for individual CES T1 and CES E1 UTP and coaxial interface connections of the port adapter. The LEDs are described in Table 5-5.

Table 5-5   CES T1 and CES E1 Port Adapter LED Descriptions

LED Status Description

RX (Receive)

Off
Flashing green

Red

LOS1 or port adapter is shut down.
Cells are being received. LED blinks every five seconds and pulse rate increases with data rate.
Alarm (LOF2, LCD3, AIS4).

TX (Transmit)

Off
Flashing green
Flashing yellow
Steady yellow

No transmit line activity indication.
Cells are being transmitted. LED pulse rate increases with data rate.
Loopback.
FERF alarm.5

1LOS = loss of signal

2LOF = loss of frame

3LCD = loss of cell delineation

4AIS = alarm indication signal

5FERF = far-end receive failure


Note   Single-mode fiber-optic interface connectors are blue, and multimode connectors are black.

Displaying Interface Port Configuration

To display the CES T1 and CES E1 interface configuration, use the following commands:

Command Purpose

show interfaces cbr card/subcard/port

Shows the status of the physical interface.

show ces interface atm card/subcard/port

Shows the interface configuration.

Follow these steps to troubleshoot the CES physical interface:


Step 1   Use the show interfaces cbr card/subcard/port command to check the configuration.

Switch# show interfaces cbr 3/0/0
CBR3/0/0 is up, line protocol is up
Hardware is DCU
MTU 53 bytes, BW 1544 Kbit, DLY 0 usec, rely 0/255, load 1/255
  Encapsulation ATMCES-T1, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the CBR field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see whether the status is up.

If the interface is down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input and Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors but not many collisions indicates excessive noise. If the number is too high, check the cables for damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3. Also check the clock mode, framing, and line coding configuration for each end of the connection.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 8   Check the collisions field. It shows the total number of collisions compared to the total number of output packets and should be approximately 0.1 percent or less. If the number is too high, perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to troubleshoot the configuration of a CES interface:


Step 1   Use the show ces interface cbr card/subcard/port command to check the configuration.

Switch# show ces interface cbr 3/0/0
Interface: CBR3/0/0 Port-type:T1-DCU
IF Status: UP Admin Status: UP
Channels in use on this port:
LineType: ESF LineCoding: B8ZS LoopConfig: NoLoop
SignalMode: NoSignalling XmtClock: network-derived
DataFormat: UnStructured AAL1 Clocking Mode: Synchronous LineLength: 0_110
LineState: XmtAIS LossOfSignal
Errors in the Current Interval:
PCVs 0 LCVs 0 ESs 0 SESs 0 SEFSs 0
UASs 0 CSSs 0 LESs 0 BESs 0 DMs 0
Errors in the last 24Hrs:
PCVs 0 LCVs 0 ESs 0 SESs 0 SEFSs 0
UASs 0 CSSs 0 LESs 0 BESs 0 DMs 0
Input Counters: 0 cells, 0 bytes
Output Counters: 0 cells, 0 bytes
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   If the DataFormat field indicates that the circuit is unstructured, check the AAL1 Clocking Mode field to ensure that it matches the AAL1 clocking mode of the destination interface.

Step 4   Check the LineLength field to see if the value is correct. Measure the distance between the ATM switch router and the customer provided equipment (CPE) or regenerating device. The maximum supported distance for CES T1 interfaces is 650 feet, or 198 meters. The maximum supported distance for CES E1 interfaces and 820 feet, or 248.5 meters. The default value is 0 to 110 feet.


Note    For detailed cabling and hardware information, refer to the "CES T1 and E1 Port Adapters" chapter in the ATM Port Adapter and Interface Module Installation Guide.

Step 5   Check the Input Counters and Output Counters fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.





If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly, continue with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."

Troubleshooting 25-Mbps Interfaces

This section describes specific processes and commands used to troubleshoot the 25-Mbps port adapter.

Port Adapter LEDs

The port adapter faceplate LEDs provide status information for individual 25-Mbps UTP interface connections of the port adapter. The LEDs are described in Table 5-6.


Note   Use the show controllers command to display the LED status.

Table 5-6   25-Mbps UTP Port Adapter LED Descriptions

LED Status Description

TX (Transmit)

Off
Flashing green

Flashing yellow
Steady yellow
Red

No receive line activity indication.
Cells are being received. LED blinks every 5 seconds and pulse rate increases with data rate.
Loopback.
FERF alarm.1
Alarm indication (LOF2, LCD3).

1FERF = far-end receive failure

2LOF = loss of frame

3LCD = loss of cell delineation

Displaying Interface Port Configuration

To display the 25-Mbps interface configuration, use the following commands:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm interface atm card/subcard/port

Shows the interface configuration.

show controllers atm card/subcard/port

Shows the interface memory management and error counters.

Follow these steps to troubleshoot the 25-Mbps physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to check the configuration.

Switch# show interfaces atm 1/0/0
ATM1/0/0 is UP, line protocol is UP
Hardware is ATM25
MTU 4470 bytes, sub MTU 4470, BW 25600 Kbit, DLY 0 usec, rely 0/255, load 1/255
  Encapsulation ATM, loopback not set, keepalive not supported
  Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see that the status is up.

If the interface is down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm the encapsulation method matches the interface type.

Step 5   Check the Last input or the Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors, but not many collisions, indicates excessive noise. If the number is too high, check the cables for damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.

Step 8   Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 9   Check the collisions field. It shows the total number of collisions compared to the total number of output packets and should be approximately 0.1 percent or less. If the number is too high perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to show how to troubleshoot the configuration of a 25-Mbps interface:


Step 1   Use the show atm interface atm card/subcard/port command to check the configuration.

Switch# show atm interface atm 1/0/0
Interface: ATM1/0/0 Port-type: ATM25
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: 2 Max-VCI-bits: 14
Max-VP: 4 Max-VC: 16383
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c84.8000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Installed-Conns
2 0 0 0 0 0 2 0
Logical ports(VP-tunnels): 0
Input cells: 0 Output cells: 0
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0
Switch#
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 crc errors field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collision, indicates excessive noise.
  • Cables damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly proceed with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."

Troubleshooting CDS3 Frame Relay Interfaces

This section describes specific processes and commands used to troubleshoot the channelized DS3 Frame Relay port adapter (CDS3).

Port Adapter LEDs

The port adapter faceplate LEDs provide status information for individual channelized DS3 Frame Relay port adapter (CDS3) coaxial interface connections of the port adapter. The LEDs are described in Table 5-7.

Table 5-7   CDS3 Frame Relay Adapter LEDs

LED State Description

CD (carrier detect)

Off
Green

Carrier detect signal not received
Carrier detect signal received

RX (receive)

Off
Flashing green
Red

LOS1 or shutdown
Cells being received
Alarm (LOF2, LCD3, AIS4)

TX (transmit)

Off
Flashing green
Steady yellow

No transmit line activity
Cells being transmitted
Alarm FERF5

1LOS = loss of signal

2LOF = loss of frame

3LCD = loss of cell delineation

4AIS = alarm indication signal

5FERF = far-end receive failure

Displaying Interface Port Configuration

To display the channelized DS3 Frame Relay port adapter (CDS3) interface configuration, use the following commands:

Command Purpose

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm interface atm card/subcard/port

Shows the interface configuration.

show controllers e1 card/subcard/port

Shows the interface memory management and error counters.

Follow these steps to troubleshoot the DS3 or E3 Frame Relay physical interface:


Step 1   Use the show interfaces atm card/subcard/port command to check the configuration.

Switch# show interfaces atm 4/0/0
ATM-P4/0/0 is up, line protocol is up
Hardware is ATM-PSEUDO
MTU 4470 bytes, sub MTU 4470, BW 6000 Kbit, DLY 0 usec, rely 0/255, load 1/255
   Encapsulation ATM, loopback not set, keepalive not supported
Encapsulation(s):
2000 maximum active VCs, 0 current VCCs
VC idle disconnect time: 300 seconds
   Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Switch#

Step 2   Check the ATM-P field to see whether the interface is up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Replace faulty hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the line protocol field to see if the status is up.

If the interface is down, check for the following:

  • The line protocol software processes might have determined that the line is unusable. Try swapping the cable.
  • The local or remote interface might be misconfigured. Check the interface configuration.
  • Clocking might be misconfigured or the source interface might have failed. Refer to the "Initially Configuring the ATM Switch Router" chapter in the
    ATM Switch Router Software Configuration Guide .
  • Hardware might have failed. Try swapping the port adapter.

Step 4   Check the Encapsulation field. Confirm that the encapsulation method matches the interface type.

Step 5   Check the Last input or the Last output fields. They show the number of hours, minutes, and seconds since the last packet was successfully received or transmitted by the interface.

Step 6   Check the output hang field. It shows the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission.

Step 7   Check the CRC field. The presence of many CRC errors but not many collisions is an indication of excessive noise. If the number is too high, check the cables to determine if any are damaged. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.


Note    Errors and the input and output difference should not exceed 0.5 to 2.0 percent of traffic on the interface.

Step 8   Check the Collisions field. This value indicates the total number of collisions compared to the total number of output packets and should be approximately 0.1 percent or less. If the number is too high, perform the following tasks:

  • Use a protocol analyzer to check for late collisions. Collisions do not occur in a properly designed network. Collisions usually occur when cables are too long.
  • Check the diameter of the network and make sure it is within specification.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to show how to troubleshoot the configuration of a DS3 or E3 Frame Relay interface:


Step 1   Use the show atm interface atm card/subcard/port command to check the configuration.

Switch# show atm interface atm 4/0/0
Interface: ATM-P4/0/0 Port-type: ATM-PSEUDO
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: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255
ConfMinSvccVci: 35 CurrMinSvccVci: 35
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.00e0.4fac.b401.4000.0c82.0000.00
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
7 0 0 0 0 0 0 7 7
Logical ports(VP-tunnels): 0
Input cells: 0 Output cells: 0
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 1, Output AAL5 pkts: 0, AAL5 crc errors: 0
Switch#

Step 2   Check the IF Status and Admin Status fields to see whether they are up.

If down, check for the following:

  • Disconnected or faulty cabling—Check cables.
  • Hardware failure—Swap hardware.

If administratively down, the interface has been administratively taken down. Use the no shutdown interface configuration command to reenable the interface.

Step 3   Check the Input cells and Output cells fields. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, the interface is experiencing congestion and dropping cells.

Step 4   Check the AAL5 crc error field. If the errors and the input and output difference exceed 0.5 to 2.0 percent of traffic on the interface, check for the following:

  • Many CRC errors, but not many collisions. This indicates excessive noise.
  • Cable damage. If you are using UTP cables, make sure you are using category 5 cables and not another type, such as category 3.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Follow these steps to display the memory management and error counters of a DS3 or E3 ATM interface:


Step 1   Use the show controllers atm card/subcard/port command to check memory management and error counters.

Switch# show controllers e1 4/0/0
E1 4/0/0 is down.
 PAM state is Up
FPGA Version: fi-c8510-4e1fr.A.3.2
Firmware Version: fi-c8510-4e1fr.A.2.3
   Transmitter is sending LOF Indication (RAI).
   Receiver has loss of signal.
Framing is crc4, Line Code is HDB3, Clock Source is line.
Data in current interval (143 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
143 Unavail Secs
Data in Interval 1:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
900 Unavail Secs
.
(Information Deleted)
.
     Total Data (last 95 15 minute intervals):
2 Line Code Violations,0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 2 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
1833290 Unavail Secs, 0 Stuffed Secs
Switch#

Step 2   Check the Receiver field. If the receiver has a loss of signal check the following:

  • Confirm the cable between the interface port and the Service Provider equipment or terminal equipment is connected correctly. Confirm the cable is hooked up to the correct ports. Correct the cable connections if necessary.
  • Check the cable integrity by looking for breaks or other physical abnormalities in the cable. Ensure the pinouts are set correctly. Replace the cable if necessary.




If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

If the interface is still not operating correctly, proceed with the troubleshooting process in "Troubleshooting Switch Router ATM Network Connections."