|
|
This chapter provides troubleshooting information about connectivity and performance problems in the Ethernet, ATM uplink, and POS uplink physical interfaces of a Layer 3 enabled ATM switch router.
The chapter includes the following sections:
 |
Note For detailed cabling and hardware information for each port adapter, refer to the Catalyst 8540 CSR Route Processor and Interface Module Installation Guide. |
You might see problems of cell transmission through the switch router, detected by a buildup of cells on an internal virtual channel (VC). These problems occur for the following reasons:
A switch processor can have a cell stuck problem in internal virtual channels (VCs), resulting from timing issues in the hardware and software on the Catalyst 8540 CSR. You might see more than one port affected on one or more interface modules. Online insertion and removal (OIR) of the interface module will temporarily fix the problem.
Follow these steps to troubleshoot cell stuck problems:
The show switch fabric command clears the counters after it displays. Entering the command again shows the current activity on the switch router.
Step 2 Issue the show switch fabric command again to show new activity.
Look at the values in the Rejected Cells and Invalid Cells fields. Note that the Rejected Cells and Invalid Cells field counters are increasing. This means there might be a problem in the switch fabric.
Step 3 Verify that no ports are involved by issuing the show epc queuing and show epc status commands.
If the queues are empty and all of the ports show OK status, then the problem is not the ports, it is the switch processor.
You can resolve this problem by upgrading your system software image to release Cisco IOS Release version 12.0(4a)WX5(11) or later, by replacing the switch processors, or by doing both.
If one or more Fast Ethernet or Gigabit Ethernet ports are not transmitting cells, then the failure might be a port stuck problem.
Follow these steps to troubleshoot a port stuck problem:
|
Note Be sure to use the show switch fabric command during the lightest possible traffic conditions because actual traffic might be using the memory buffers. |
The show switch fabric command clears the counters after it displays. Entering the command again shows the current activity on the switch router.
Step 2 Enter the show switch fabric command again.
Look at the values in the Rejected Cells and Invalid Cells fields. Note that the Rejected Cells and Invalid Cells field counters are increasing. This means there might be a problem in the switch fabric.
Step 3 Use the show epc queuing and show epc status command to display interface queues and status.
The show epc queuing command output shows that no activity is going across interface GigabitEthernet 1/0/0. This is verified in the show epc status command output, which indicates that interface GigabitEthernet 1/0/0 is "not OK." You have confirmed that the problem is a stuck port.
|
Note You might see a few cells in the QCNT column in the show epc queuing command output. That is normal. Issue the command several times to verify that traffic is moving through the queues. If the QCNT column values are incrementing and incrementing for the VCIs belonging to a particular interface, the problem is probably a stuck port. |
You can remedy the port stuck condition by removing and reinserting the interface module. A shutdown/no shutdown command sequence on the problem interface does not resolve the problem.
To recover from a port stuck failure, perform the following tasks:
If the switch router is not configured to reset the port upon detecting a port stuck failure, the port will be isolated, thus preserving the integrity of the switch router.
If the switch router is configured to reset the port upon detection of a stuck port failure, the switch router will isolate the port from the rest of the functioning ports, and reset the port. This might affect other ports on the interface module.
|
Note If you configure the switch router as described in the nondefault behavior section after a port stuck failure is detected, the switch router will not reset the Ethernet ports. The Ethernet interface must be configured to reset before the port stuck failure occurs. Also, the default behavior is to not reset the port if a port stuck failure is detected. If the Ethernet interface is not configured to reset when a port stuck failure is detected, schedule the switch router for downtime to remove and reinsert the module. |
To configure the switch router to automatically recover from port stuck failures, use the following interface configuration commands:
 |
Caution Because of the nature of the microcode architecture, do not configure low values for the wait time in the epc portstuck-wait command. The default value of 180 seconds has been carefully chosen, allowing for the hello intervals of protocols such as HSRP, EIGRP, and OSPF. Configuring a low value might lead to incorrectly detecting temporary port stuck failures as real port stuck failures, and can cause a temporary loss of connectivity. It is highly recommended to keep this value to at 60 seconds, at a minimum. Lower values are provided to allow for some specific network designs when you can absolutely rule out temporary port stuck failure scenarios, and also as a debugging aid. For most networks, 180 seconds works very well. |
To troubleshoot a connectivity problem between a port and another port or end-station, use the following commands:
This section describes specific processes and commands used to troubleshoot the 10/100BASE-T and BASE-FX Ethernet interface modules.
The Catalyst 8500 CSR supports two different interface modules. The 10/100BASE-T Ethernet interface module supports 100-Mbps Layer 2 or Layer 3 UTP connections. The 100BASE-FX Ethernet interface module supports 100-Mbps Layer 2 or Layer 3 multimode fiber connections.
This section includes the following:
The 10/100BASE-T Ethernet interface module supports 16 10-Mbps or 100-Mbps Layer 2 or Layer 3 unshielded twisted-pair (UTP) ports. This module supports full-duplex or half-duplex connections and Fast EtherChannel operation. The 10/100BASE-T interface module is available with 16K or 64K of memory. Routing tables use this memory.
Table 10-1 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
The 100BASE-FX Ethernet interface module supports 100-Mbps Layer 2 or Layer 3 multimode fiber connections. This module supports full-duplex connections and Fast EtherChannel operation. It provides 16 multimode fiber ports that have MT-RJ connectors. The 100BASE-FX interface module is available with 16K or 64K of memory. Routing tables use this memory.
Table 10-2 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
| LED | State | Description |
|---|---|---|
Port is transmitting a packet. Green for approximately 50 ms. |
||
To display the 10/100 Ethernet interface module configuration and status, use the following commands:
| Command | Purpose |
|---|---|
Follow these steps to troubleshoot a 10/100 Ethernet interface module:
Step 2 Check the FastEthernet field to see whether the interface is up. If it is down, check for the following:
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:
Step 4 Check the duplex mode field. It should match the speed of the interface and be configured as Auto-negotiation.
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 fields. These numbers indicate packet collisions and these numbers should be very low. The total number of collisions, with respect to the total number of output packets, should be 0.1 percent or less.
Step 9 Check the late collisions fields. Late collisions should never occur in a properly designed Ethernet network. They usually occur when Ethernet cables are too long or when there are too many repeaters in the network.
Step 10 Check carrier fields. These numbers indicate a lost carrier detect signal and can be caused by a malfunctioning interface that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
Step 11 Check the buffer fields. These numbers indicate the number of received packets discarded because there was no buffer space. Broadcast storms on Ethernet networks, and bursts of noise on serial lines, are often responsible for no-input buffer events.
If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide.
Follow these steps to troubleshoot the status of 10/100BASE-T and BASE-FX interfaces:
Step 2 Check the Chip Status Register field. It should match the link status, duplex mode, and speed shown in the previous show interface command. If it does not, see the "Troubleshooting Half- or Full-Duplex Negotiation" section.
Follow these steps to troubleshoot the counters of the Fast Ethernet interface module physical interface:
Step 2 Check the Interface State field. It should indicate the interfaces are up.
Step 3 Check the Input Packets and Output Packets fields. The show controllers c8500 counters command should be entered at least twice. The counters in the Input Packets and Output Packets fields should be incrementing. This information can also be displayed using the show interfaces command.
|
Note The clear counters command does not clear the show controllers c8500 counters command display. |
If you determine that the interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide .
This section describes specific processes and commands used to troubleshoot the Gigabit Ethernet interface modules.
The Catalyst 8500 CSR supports three different interface modules for Gigabit Ethernet transmission over fiber connections: the eight-port Gigabit Ethernet interface module, the two-port Gigabit Ethernet interface module, and the two-port enhanced Gigabit Ethernet interface module.
This section includes the following:
The switch router uses two different Gigabit Ethernet interface-modules hardware types.
The two- and eight-port Gigabit Ethernet interface modules use the Ethernet processor interface (EPIF) that has an internal binary CAM search engine built into the processor.
The enhanced Gigabit Ethernet interface module uses the Gigabit processor interface (XPIF) that has a faster external search engine using a Cisco Systems proprietary FPGA and Ternary CAM (TCAM) for the Layer 3 routing and Layer 2 switching functionality.
The two-port and eight-port Gigabit Ethernet interface modules are full-width modules. The Ethernet interface processors support 1000-Mbps Layer 2 or Layer 3 fiber-optic connections. They provide Gigabit Ethernet ports that have Gigabit Interface Converter (GBIC) modular transceivers and SC-type fiber connectors. The two-port Gigabit Ethernet interface module is available with 16K or 64K of memory. The eight-port Gigabit Ethernet interface module is available with 16K of routing table memory.
The two-port enhanced Gigabit Ethernet interface module with Gigabit interface processors supports 1000-Mbps multimode and single-mode Layer 2 and Layer 3 fiber-optic connections. It consists of two one-port Gigabit Ethernet port adapters attached to a carrier module. The port adapters are not hot-swappable, but the complete interface module is hot-swappable. The port adapters have GBIC modular transceivers and SC-type fiber connectors. The interface module is full-duplex, supports Fast EtherChannel operation, and provides built-in ACL functionality. It is available with 16K, 64K, or 256K of routing table memory.
The troubleshooting procedures are slightly different for the Ethernet processor interface and Gigabit processor interface modules. You need to determine which type of Gigabit interface module you are troubleshooting.
To display the Gigabit Ethernet interface and enhanced Gigabit Ethernet interface modules installed in your switch router, use the following commands:
| Command | Purpose |
|---|---|
Follow these steps to determine which type of Gigabit Ethernet interface modules are installed in your switch router:
Step 2 Check the Ctrlr-Type field of the show hardware command.
The interface module installed in slot 11 has the following components:
|
Note The individual enhanced Gigabit Ethernet interface modules are not hot-swappable, but the entire carrier module with both interface modules installed is hot-swappable. |
In the previous show hardware command example, the GIGETHERNET interface module installed in slot 10/* does not have "XPIF" preceding its controller type, and is an Ethernet processor (EPIF) type Gigabit Ethernet interface module.
Step 3 Use the show hardware detail command to check the Gigabit interface processor type in greater detail.
Step 4 Check the Controller-Type field in the show hardware detail command.
The interface module installed in slot 11 has the following components:
In the previous show hardware detail command example, the interface module installed in slot 10/* has GIGETHERNET PAM listed in the Controller-Type field and is an Ethernet processor type interface.
Step 5 Use the show interfaces GigabitEthernet card/subcard/port command as another way to check the Gigabit Ethernet interface processor type.
Step 6 Check the Hardware field. In this example, the hardware is listed as xpif_port, indicating this interface module uses the Gigabit processor interface.
Step 7 Use the show interfaces GigabitEthernet card/subcard/port command on a different interface to check the Gigabit Ethernet interface processor type.
Step 8 In this show interface GigabitEthernet card/subcard/port command example, again check the Hardware field. The hardware is listed as epif_gigether_port, indicating this interface module uses the Ethernet processor interface type.
Troubleshooting the Gigabit interface module with the Ethernet interface processor is described in the following sections:
Troubleshooting the enhanced Gigabit interface module with the Gigabit interface processor is described in the following troubleshooting sections:
The eight-port Gigabit Ethernet interface module supports 1000-Mbps Layer 2 or Layer 3 fiber-optic connections. It provides eight Gigabit Ethernet ports that have Gigabit Interface Converter (GBIC) modular transceivers and SC-type fiber connectors. The eight-port Gigabit Ethernet interface module is available with 16K of memory. Routing tables use this memory.
Figure 10-1 is a block diagram of the eight Gigabit Ethernet port interface module, and shows how the interface communicates with the route processor and switch fabric across the backplane.
Table 10-3 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
The two-port Gigabit Ethernet interface module supports 1000-Mbps Layer 2 or Layer 3 fiber-optic connections. It provides two Gigabit Ethernet ports that have GBIC modular transceivers and SC-type fiber connectors. The two-port Gigabit Ethernet interface module is available with
16K or 64K of memory. Routing tables use this memory.
Table 10-4 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
To display the Gigabit Ethernet interface module using the Ethernet processor interface type configuration and status, use the following commands:
| Command | Purpose |
|---|---|
Follow these steps to troubleshoot a Gigabit Ethernet interface module physical interface:
Step 2 Check the GigabitEthernet field to see whether the interface is up.
If the interface is down, check for the following:
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:
Step 4 Check the duplex mode field. It should match the speed of the interface and be configured as Auto-negotiation.
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 fields. These numbers indicate packet collisions, and these numbers should be very low. The total number of collisions with respect to the total number of output packets should be approximately 0.1 percent or less.
Step 9 Check the late collisions fields. Late collisions should never occur in a properly designed Ethernet network. They usually occur when Ethernet cables are too long or when there are too many repeaters in the network.
Step 10 Check the carrier fields. These numbers indicate a lost carrier detect signal, and can be caused by a malfunctioning interface that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
Step 11 Check the buffers fields. These numbers indicate the number of received packets discarded because there was no buffer space. Broadcast storms on Ethernet networks, and bursts of noise on serial lines, are often responsible for no-input buffer events.
If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide.
Follow these steps to troubleshoot the status of a Gigabit Ethernet interface module:
|
Note The Catalyst 8540 CSR has no switch feature card. Consequently, you can not check the number of cells switched on an individual VC. |
Step 2 Check the Chip Status Register field. It should match the link status, duplex mode, and speed shown in the previous show interface command. If it does not, see the "Troubleshooting Half- or Full-Duplex Negotiation" section.
Follow these steps to troubleshoot the counters of the Gigabit Ethernet interface module physical interface:
Step 2 Check the Interface State field. It should indicate the interfaces are up.
Step 3 Check the Input Packets and Output Packets fields. The show controllers c8500 counters command should be entered at least twice. The counters in the Input Packets and Output Packets fields should be incrementing. This information can also be displayed using the show interfaces command.
|
Note The clear counters command does not clear the show controllers c8500 counters command display. |
If you determine that the interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide .
The two-port enhanced Gigabit Ethernet interface module supports 1000-Mbps multimode and single-mode Layer 2 and Layer 3 fiber-optic connections. It consists of two one-port Gigabit Ethernet port adapters attached to a carrier module. The port adapters are not hot-swappable, but the complete interface module is hot-swappable. The port adapters have GBIC modular transceivers and SC-type fiber connectors. The interface module is full-duplex, supports Fast EtherChannel operation, and provides built-in ACL functionality. It is available with 16K, 64K, or 256K of routing table memory.
|
Note The port adapters within the two-port interface modules must have matching routing table memory. That is, if the ATM OC-12c port adapter has 64K of routing table memory, the Gigabit Ethernet port adapter must have 64K of routing table memory for the interface module to function properly. |
Figure 10-2 is a block diagram of the enhanced Gigabit Ethernet interface module and shows how the interface communicates with the switch fabric across the backplane.
The enhanced Gigabit Ethernet interface module uses the Gigabit processor interface (XPIF) with a faster external search engine that has a Cisco Systems proprietary FPGA and Ternary CAM (TCAM) to provide the search engine for the Layer 3 routing and Layer 2 switching functionality.
The Gigabit Ethernet interface module with the Gigabit processor interface is used with all of the interface modules described in the troubleshooting sections:
Table 10-5 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
To display the enhanced Gigabit Ethernet interface module configuration and status, use the following commands:
| Command | Purpose |
|---|---|
Follow these steps to troubleshoot an enhanced Gigabit Ethernet interface module physical interface:
Step 2 Check the GigabitEthernet field to see whether the interface is up.
If down, check for the following:
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:
Step 4 Check the duplex mode field. It should match the speed of the interface and be configured as Auto-negotiation.
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 fields. These numbers indicate packet collisions, and these numbers should be very low. The total number of collisions with respect to the total number of output packets should be 0.1 percent or less.
Step 9 Check the late collisions fields. Late collisions should never occur in a properly designed Ethernet network. They usually occur when Ethernet cables are too long or when there are too many repeaters in the network.
Step 10 Check carrier fields. These numbers indicate a lost carrier detect signal and can be caused by a malfunctioning interface that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
Step 11 Check the buffers fields. These numbers indicate the number of received packets discarded because there was no buffer space. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.
If you determine that the physical interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide.
Follow these steps to troubleshoot the status of a Gigabit Ethernet interface module:
|
Note The Catalyst 8540 CSR has no switch feature card and does not support the show controllers GigabitEthernet command and no individual VC statistics are available. |
Step 2 Check the Chip Status Register field. It should match the link status, duplex mode, and speed shown in the previous show interface command.
If not, see the "Troubleshooting Half- or Full-Duplex Negotiation" section.
Follow these steps to troubleshoot the counters of the Gigabit Ethernet interface module physical interface:
Step 2 Check the Interface State field. It should indicate the interfaces are up.
Step 3 Check the Input Packets and Output Packets fields. The show controllers c8500 counters command should be entered at least twice. The counters in the Input Packets and Output Packets fields should be incrementing. This information can also be displayed using the show interfaces command.
|
Note The clear counters command does not clear the show controllers c8500 counters command display. |
If you determine that the interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide .
The ATM Uplink interface module has one ATM uplink port and one Enhanced Gigabit Ethernet port, and is designed specifically for large-enterprise and service-provider networks.
Up to eight of the ATM Uplink with Enhanced Gigabit Ethernet Modules may be installed in a Catalyst 8540 chassis, providing eight ATM uplink ports and eight ports of nonblocking, wire-speed Gigabit Ethernet capacity in the core of an Enterprise network.
An example application of the ATM uplink is traffic from a LAN switch being aggregated at the Catalyst 8540 CSR and then passed to the ATM network over the ATM uplink. The Layer 3 enabled ATM uplink supports RFC 1483 (Multiprotocol Encapsulation over ATM), which provides for the mapping of Layer 3 addresses to ATM virtual circuits, and traffic shaping. Refer to the Guide to ATM Technology for additional information on RFC 1483.
The two ATM uplink with enhanced Gigabit Ethernet interface modules are the OC-3c and the OC-12c. The ATM OC-3c or OC-12c uplink with enhanced Gigabit Ethernet interface modules consist of two port adapters that are attached to a carrier module. The port adapters are not hot-swappable, but the interface module as a whole is hot-swappable. The ATM OC-3c uplink port adapter or the OC-12c uplink port adapter resides on the left side of the interface module, and the one-port enhanced Ethernet Gigabit port adapter resides on the right side. This combination provides an Ethernet port for connection to, or within, a LAN and an ATM uplink port to a metropolitan-area network (MAN).
The ATM OC-3c uplink port adapter supports 155-Mbps multimode or single-mode intermediate-reach fiber connections. It supports Fast EtherChannel operation, uses SC-type connectors, and has built-in ACL functionality. The OC-3c has 64K of routing table memory.
The ATM OC-12c uplink port adapter supports 622-Mbps multimode or single-mode intermediate-reach fiber connections. It supports Fast EtherChannel, SC-type connectors, and has built-in ACL functionality. The OC-12c has 64K or 256K of routing table memory.
|
Note The port adapters within the ATM OC-12c or OC-3c uplink with enhanced Ethernet interface modules must have matching routing table memory. As an example, if the ATM OC-12c uplink port adapter has 64K of routing table memory, the enhanced Gigabit Ethernet port adapter must have 64K of routing table memory for the interface module to function properly. |
Table 10-6 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
| 1LOS = Loss of signal
2LOF = Loss of frame 3LOP = Loss of pointer 4AIS-L = Line alarm indication signal 5AIS-P = Path alarm indication signal 6RDI-L = Line remote defect indication 7RDI-P = Path remote defect indication 8UNEQ-P = Path unequipped 9PLM-P = Path payload label mismatch |
To display the interface configuration, use the following commands:
Follow these steps to troubleshoot an ATM uplink physical interface:
Step 2 Use the show running-config interface atm card/subcard/port.sub-interface command to check the subinterface status.
Step 3 Use the show interface atm card/subcard/port command to check the interface status.
Step 4 Check the status of the interface. If the ATM interface is down and the line protocol is down, begin checking for active alarms and defects.
Step 5 Check the MTU field. This indicates the largest number of bytes of "payload" data a frame can carry, not counting the frame's header and trailer. For an ATM interface, the MTU should be 4470 bytes.
Step 6 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 7 Use the show controllers atm card/subcard/port command to check the interface memory status and configuration.
Step 8 Check the Interface Configuration Mode field. This field indicates the clock configuration and the administrative status of the interface.
Step 9 Check Sonet Overhead fields. These fields indicate the following:
Step 10 Check the Content of Path trace field. The path trace buffer is used to communicate information regarding the remote hostname, interface name/number, and IP address. This is a Cisco-proprietary use of the J1 (path trace) byte.
Step 11 Check the Active defects field. It indicates the currently configured alarms with defects and is a primary troubleshooting indicator.
Step 12 Check the Alarm reporting enabled field—It is a list of alarms for which you enabled reporting by entering the pos report interface command.
Step 13 Check the Active Defects field—It is a list of all currently active defects.
Step 14 Check the OC12 Counters field. If this number is incrementing, this indicates a problem in the network.
Check for any BIP(B1)/BIP(B2)/BIP(B3) (Bit interleaved parity) error reported.
Check the FEBE (Far end block errors).
Step 15 Check the OC12 error secs field. This field shows the total seconds where there were one or more alarms since the switch was rebooted.
Check AIS (Alarm indication signal).
Check RDI (Remote defect indication).
Step 16 Check the OC12 error free secs field. It indicates the number of seconds since the last error.
Step 17 Check the BER thresholds field. It is a list of bit error rate (BER) thresholds that have been crossed.
Step 18 Check the TCA thresholds field. It is a list of threshold crossing alarms (TCA).
If you determine that the interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide .
The Packet-over-SONET (POS) uplink with enhanced Gigabit Ethernet interface module consists of two port adapters that are attached to a carrier module. The port adapters are not hot-swappable, but the interface module as a whole is hot-swappable. The Packet-over-SONET OC-12c uplink port adapter resides on the left side of the interface module, and the one-port enhanced Gigabit Ethernet port adapter resides on the right side. This combination provides an Ethernet port for connection to, or within, LANs, and a POS uplink port for connection to an ISP or MAN.
The Packet-over-SONET OC-12c uplink port adapter supports 622-Mbps single-mode intermediate and long-reach fiber connections. The Packet-over-SONET OC-12c uplink port adapter is a serial link, uses SC-type connectors, and has built-in ACL functionality. It is available with 64K or 256K of memory. Routing tables use this memory.
|
Note The port adapters within the Packet-over-SONET OC-12c interface module must have matching routing table memory. As an example, if the Packet-over-SONET OC-12c POS port adapter has 64K of routing table memory, the enhanced Gigabit Ethernet port adapter must have 64K of routing table memory for the interface module to function properly. |
For detailed Cisco Packet over SONET/SDH (POS) technology information, see the following documents:
Table 10-7 describes the LEDs used to confirm and troubleshoot the operation of interface modules. The LEDs on interface modules indicate the status of the modules and their ports.
To display the interface configuration, use the following commands:
| Command | Purpose |
|---|---|
Follow these steps to troubleshoot the physical interface:
Step 2 Check the POS field. If the link is down/down, start checking for active alarms and defects. Troubleshooting here is similar to serial interface troubleshooting.
Step 3 POS defects and alarms are similar to alarms occurring when troubleshooting and diagnosing T1/E1 and T3/E3 connections (for example, LOS, LOF, and AIS). For T1 connection troubleshooting procedures, refer to the T1 Troubleshooting at the following URL: http://www.cisco.com/warp/public/116/t1_flchrt_main.html
If you determine that the interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide .
Follow these steps to troubleshoot the POS physical interface:
|
Note The numbers under the Section and Line are accumulators and tell you the number of times the condition has occurred, not if it is currently happening. |
Step 2 Check LOF (loss of frame)—LOF is detected when a severe error framing (SEF) defect on the incoming SONET signal persists for 3 ms.
Step 3 Check LOS (loss of signal)—LOS is detected when an all-zeros pattern on the incoming SONET signal lasts 19 plus or minus 3 ms or longer. This defect might also be reported if the received signal level drops below the specified threshold.
Step 4 Check whether a Bit interleaved parity (BIP [B1]/BIP [B2]/BIP [B3]) error has been reported.
Step 5 Check the Alarm indication signal (AIS) field.
Step 6 Check the Remote defect indication (RDI) field.
Step 7 Check the Far end block errors (FEBE) field.
Step 8 Check the loss of pointer (LOP) Path field —LOP is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag (NDF) enabled indications.
Step 9 Check the NEWPTR Inexact count field for of the number of times the SONET framer has validated a new SONET pointer value (H1, H2).
Step 10 Check the PSE Inexact count field for of the number of times the SONET framer has detected a positive stuff event in the received pointer (H1, H2).
Step 11 Check the NSE Inexact count field for of the number of times the SONET framer has detected a negative stuff event in the received pointer (H1, H2).
Step 12 Check the Active Alarms field—It is a list of current Alarms as enforced by Sonet Alarm Hierarchy.
Step 13 Check the Active Defects field—It is a list of all currently active SONET defects.
Step 14 Check the Alarm reporting enabled field—It is a list of alarms that you enabled reporting for with the pos report interface command.
Step 15 Check the COAPS fields—These are an inexact count of the number of times a new APS value has been detected in the K1 and K2 bytes. These fields indicate the following:
Step 16 Check the PSBF field—It is an inexact count of the number of times a protection switching byte failure has been detected (no three consecutive SONET frames contain identical K1 bytes).
Step 17 Check the PSBF_state field—It lists protection switching byte failure state.
Step 18 Check the Rx(K1/K2)/Tx(K1/K2) field—It lists contents of the received and transmitted K1 and K2 bytes.
Step 19 Check the S1S0 field—It lists the two S bits received in the last H1 byte.
Step 20 Check the C2 field—It lists the value extracted from the SONET path signal label byte (C2).
Step 21 Check the PATH TRACE BUFFER field—It lists the SONET path trace buffer is used to communicate information regarding the remote hostname, interface name/number, and IP address. This is a Cisco-proprietary use of the J1 (path trace) byte.
Step 22 Check the BER thresholds field—It list of the bit-error rate (BER) thresholds you configured with the pos threshold interface command.
Step 23 Check the TCA thresholds field—It list of threshold crossing alarms (TCA) you configured with the pos threshold interface command.
If you determine that the interface is configured incorrectly, refer to the "Configuring Interfaces" chapter in the Layer 3 Switching Software Feature and Configuration Guide .
The access control list (ACL) daughter card implements data-plane access lists in hardware, providing high-speed performance. This extends the traffic control and security capabilities of the Catalyst 8540 beyond control-plane access lists, which are currently supported. See the "Comparing Data Plane and Control Plane Traffic" section.
The ACL daughter cards can be used with existing 10/100BASE-TX, 100BASE-FX, and Gigabit Ethernet interface modules on the switch router. The ACL daughter cards provide data-plane ACL functionality for both IP and IPX traffic.
The switch router supports control-plane access lists such as permit and deny IP and IPX routes and IPX Service Advertisement Protocol (SAP) filtering without the daughter card. The daughter card enables data-plane ACLs for IP and IPX traffic.
The ACL daughter card is a field-replaceable unit that can be mounted onto the following switch router interface modules:
The ACL daughter card allows you to create lists for network control and security that filter packet flow into or out of router interfaces.
Following is a description of the packet flow through an ACL daughter card:
Step 2 The appropriate information (for example, IP addresses, protocol, and port numbers) is extracted from the packet.
Step 3 The information described in Step 2 is passed to Access List Controller.
Step 4 The Access List Controller creates the ACL word for the ciscoCAM (132 bits).
Step 5 The ciscoCAM and associated RAM returns the access or deny bit and an index.
Step 6 The Ethernet processor interface accepts (forwards) or denies (drops) the packet.
To display the ACL daughter card interface module configuration, use the following commands:
Follow these steps to troubleshoot the status of an ACL daughter card:
This interface has access group 110 enabled.
Step 2 Use the show access-lists command to confirm the status and configuration of the access lists configured on the Layer 3 enabled ATM switch router.
For detailed information about access list filters and their configuration, refer to the "Configuring IP Services" chapter in the Cisco IOS IP and IP Routing Configuration Guide .
Step 3 Use the show epc acl lookup command for a specific interface and IP addresses to display the response of the access list daughter card to a connection attempt from a source IP address to a destination.
In the following example, the packets are allowed to cross the switch router:
In the following example, the packets are denied access to cross the switch router:
Posted: Wed Jan 22 01:43:52 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
