Table of Contents
Troubleshooting the Catalyst 8540 CSR and Catalyst 8510 CSR
General Troubleshooting Guidelines
Troubleshooting Cell Transmission Problems
Troubleshooting IP Routing
Troubleshooting IPX Routing
Troubleshooting IP Multicast
Troubleshooting Layer 2 Switching
Troubleshooting Commands
Converted show epc Commands
show controllers and show switch Commands
Port Commands
Troubleshooting the Catalyst 8540 CSR and Catalyst 8510 CSR
This document describes how to troubleshoot the Catalyst 8540 CSR and Catalyst 8510 CSR switch routers.
This document includes the following sections:
General Troubleshooting Guidelines
This section describes general troubleshooting guidelines for the Catalyst 8540 CSR and Catalyst 8510 CSR.
Verifying Hardware and Software Versions
Display the hardware and software versions to ensure that they are the most recent. Very old hardware and software versions (two or three versions back) can have problems that have been fixed in more recent versions. Use the following EXEC commands to display the version information:
| Command |
Purpose |
|
show version
|
Displays the software version information.
|
|
show hardware [detail]
|
Displays detailed hardware information including revision level and version.
|
|
show functional-image slot slot
|
Displays functional image information.
|
|
Follow these steps to verify the hardware and software versions:
Step 1 First display the system software version:
Cisco Internetwork Operating System Software
IOS (tm) L3 Switch/Router Software (C8540CSR-IN-M), Version 12.0(10)W5(18c) RE
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Sat 19-Aug-00 00:11 by integ
Image text-base: 0x60010930, data-base: 0x608CA000
ROM: System Bootstrap, Version 12.0(4.6)W5(13) RELEASE SOFTWARE
8540CSR uptime is 2 minutes
System restarted by reload
System image file is "slot0:cat8540c-in-mz.120-10.W5.18c.bin"
cisco C8540CSR (R5000) processor with 262144K/256K bytes of memory.
R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache)
1 Ethernet/IEEE 802.3 interface(s)
16 FastEthernet/IEEE 802.3 interface(s)
13 Gigabit Ethernet/IEEE 802.3z interface(s)
3 ATM network interface(s)
2 Packet over SONET network interface(s)
505K bytes of non-volatile configuration memory.
20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
16384K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0
Step 2 Use the show hardware command to display the hardware revision levels:
C8540 named Router, Date: 13:59:13 UTC Mon Jan 3 2000
Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP
---- ------------ ---------- -- -------- --------- -------- ------- --- ---
0/* K1 GIGETHERN 73-3324-03 A0 0336441Y Oct 13 99 0 3.4
1/* CMPM Card 73-3944-03 09 03445724 Nov 09 99 3.0
1/0 XPIF POS OC1 73-4462-01 09 034558YP Nov 09 99 1.1
2/* CMPM Card 73-3944-03 A0 04087BW8 Mar 22 00 0 3.0
2/0 XPIF POS OC1 73-4462-01 A0 04046NRQ Mar 22 00 0 2.0
2/1 XPIF GIGE PA 73-4167-05 A0 04097GRJ Mar 22 00 0 1.0
3/* CMPM Card 73-3944-03 A0 04087BXK Mar 15 00 0 3.0
3/0 XPIF ATM OC3 73-3889-03 A0 040879AA Mar 15 00 0 1.0
3/1 XPIF GIGE PA 73-4167-05 A0 04097GQA Mar 15 00 0 1.0
4/* Route Proc 73-3775-04 A0 03201VCZ Oct 04 99 0 5.7
5/* Switch Card 73-3327-08 A0 032428ZR Jun 15 99 0 8.0
7/* Switch Card 73-3327-08 A0 032428ZE Jun 15 99 0 8.0
10/* ETHERNET PAM 73-3753-04 A0 03020FCA Sep 22 99 0 4.1
11/* CMPM Card 73-3944-03 A0 04087BY5 Mar 13 00 0 3.0
11/0 XPIF GIGE PA 73-4415-05 A0 04087AZE Mar 13 00 0 1.0
11/1 XPIF GIGE PA 73-4415-05 A0 04087AZL Mar 13 00 0 1.0
12/* CMPM Card 73-3944-03 A0 04087BWS Mar 14 00 0 3.0
12/0 XPIF ATM OC1 73-3889-03 A0 040879AO Mar 14 00 0 1.0
12/1 XPIF GIGE PA 73-4167-05 A0 04107N8R Mar 14 00 0 1.0
Model Ver. Serial MAC-Address MAC-Size RMA RMA-Number MFG-Date
------ ---- -------- ------------ -------- --- ---------- -----------
C8540 2 12237014 00D0BA1D3200 1024 0 0 Jun 18 1999
Slot Part No. Rev Serial No. RMA No. Hw Vrs Power Consumption
---- ---------------- ---- ----------- ----------- ------- -----------------
0 34-0829-02 A000 APQ02450080 00-00-00-00 1.0 2746 cA
The hardware version is listed in the Hw Vrs column.
Step 3 Use the show hardware detail command to display detailed information about the hardware, including the functional image versions.
Router#
show hardware detail slot: 3/0 Controller-Type : XPIF ATM OC3 PM - 1 Port SM_IR
Part Number: 73-3889-03 Revision: A0
Serial Number: CAB040879AA Mfg Date: Mar 15 00
RMA Number: 0 H/W Version: 1.0
XPIF Version: 3001 CAM size: 64 KB
Ucode Version: 1.0 CAM Type: Private TCAM
Optical Line Daughter Card Serial EEPROM:
Part Number: 73-3975-02 Revision: A0
Serial Number: CAB0407768M Mfg Date: 2000/04/10
RMA Number: 0 HW Rever: 1.0
TCAM Daughter Card Serial EEPROM:
Part Number: 73-3970-02 Revision: A0
Serial Number: CAB04087BXK Mfg Date: 2000/03/04
RMA Number: 0 HW Rever: 2.0
slot: 3/1 Controller-Type : XPIF GIGE PAM
Part Number: 73-4167-05 Revision: A0
Serial Number: CAB04097GQA Mfg Date: Mar 15 00
RMA Number: 0 H/W Version: 1.0
XPIF Version: 3001 CAM size: 64 KB
Ucode Version: 1.0 CAM Type: Private TCAM
Port 0: DONE GBIC Vendor: No vendor info.
slot: 4/* Controller-Type : Route Proc
Part Number: 73-3775-04 Revision: A0
Serial Number: CAB03201VCZ Mfg Date: Oct 04 99
RMA Number: 0 H/W Version: 5.7
slot: 5/* Controller-Type : Switch Card
Part Number: 73-3327-08 Revision: A0
Serial Number: CAB032428ZR Mfg Date: Jun 15 99
RMA Number: 0 H/W Version: 8.0
slot: 7/* Controller-Type : Switch Card
Part Number: 73-3327-08 Revision: A0
Serial Number: CAB032428ZE Mfg Date: Jun 15 99
RMA Number: 0 H/W Version: 8.0
Step 4 Use the show functional-image command to display detailed information about the functional images for the route processors, switch processors, and Fast Ethernet and Gigabit Ethernet interface modules for the Catalyst 8540 CSR. The following example shows how to display the functional image for the route processor in slot 4:
Router#
show functional-image slot 4 Details for cpu Image on slot: 4
Functional Version of the FPGA Image: 4.8
#Jtag-Distribution-Format-B
#HardwareRequired: 100(3.0-19,4.0-19,5.0-19)
#Section1Format: MOTOROLA_EXORMAX
Copyright (c) 1996-00 by cisco Systems, Inc.
on: Mon Mar 6 13:59:17 PST 2000
using: /vob/cougar/bin/jtag_script Version 1.13
Part type Bits Config file
10k50 10 ../cidrFpga2/max/cidr_fpga.ttf
xcs4062 3 ../cubiFpga2/xil/cubi.bit
xcs4062 3 ../cubiFpga2/xil/cubi.bit
XC4005 3 /vob/cougar/custom/common/jtcfg/xil/jtcfg_r.bit
Number of instruction bits = 21
FPGA config file information:
Bitgen date/time Sum File
100/03/02 19:14:49 7068 ../cidrFpga2/max/cidr_fpga.ttf
1999/04/15 18:46:32 36965 ../cubiFpga2/xil/cubi.bit
1999/04/15 18:46:32 36965 ../cubiFpga2/xil/cubi.bit
98/06/11 16:56:44 49904 /vob/cougar/custom/common/jtcfg/xil/jtcfg_r.bit
Check the Functional Version and #HardwareRequired fields to determine the FPGA version and the hardware version required for the FPGA. Compare this with the hardware version with the show hardware command output displayed in Step 2 and Step 3. If the FPGA version does not support the hardware version, download a new FPGA image, upgrade the hardware, or both.
If the functional image is not the most recent, you can download the functional image to the switch router from CCO. Use the reprogram command to update the functional image to the processor or interface module. The following example shows how to reprogram the route processor in slot 4 with the functional image fi-c8540-rp.A.4-8.bin from the Flash PC card in slot 0:
Router#
reprogram slot0:fi-c8540-rp.A.4-8.bin 4
 |
Note You can only issue the reprogram command from the console session prompt. |
You can find the functional images and release notes on CCO at the following URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat8540c-fpga
|
Note After you have determined the hardware and software versions on the switch router, research the release notes and DDTS database for symptoms resembling those you are observing. Often, the problem has already been discovered and a workaround provided. |
Interface Troubleshooting
Follow these steps to troubleshoot physical interface problems:
Step 1 Use the show interfaces command to display interface status and configuration information:
Router#
show interfaces fastethernet 2/0/1FastEthernet2/0/1 is up, line protocol is up
Hardware is epif_port, address is 0090.2141.bc28 (bia 0090.2141.bc28)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
Auto-duplex, Auto Speed, 100BaseTX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:02, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1822108 packets input, 182785487 bytes, 0 no buffer
Received 26 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 1630790 multicast
0 input packets with dribble condition detected
17976 packets output, 6021960 bytes, 0 underruns(0/0/0)
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Step 2 Check the FastEthernet or GigabitEthernet 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 hardware might have failed. Try swapping the interface module.
For more information on interface configuration, refer to the Layer 3 Software Feature and Configuration Guide.
Follow these steps to troubleshoot interface and controller problems:
Step 1 Use the show interfaces and show controllers command to display configuration and status information for the interface.
Figure 1 shows the difference between the show controllers command output for releases up to and including 12.0(5)W5(13) and the releases after 12.0(5)W5(13).
Figure 1 show interfaces and show controllers Command Output
Step 2 Check the interface status line in the show interfaces command display. This line indicates that the interfaces are configured as automatic duplex, automatic speed, and 100BaseTX.
Step 3 Check the Chip Status Register field contents in the show controllers command output to verify that the link is up and the link is configured the same as the output from the show interfaces command.
General Troubleshooting Commands
In all cases when troubleshooting a problem, use the following commands:
| Command |
Purpose |
|
show tech-support
|
Displays comprehensive system information for technical support.
|
|
show switch module
|
Displays switch module information. This command replaces show mmc port.
|
|
show epc lsipc detail
|
Displays detailed LS IPC message information.
|
|
show epc queuing
|
Displays queuing statistics. Enter this command more than once and watch the values change.
|
|
show epc status
|
Displays the status of the ports.
|
|
show switch fabric
|
Displays switch fabric information. Enter this command more than once and watch the values change.
|
|
show epc counters
|
Displays statistical information for the ports.
|
|
show hardware detail
|
Displays detailed information for the switch router hardware.
|
|
Troubleshooting Cell Transmission Problems
You might see problems of cell transmission through the switch router detected by a build-up of cells on an internal virtual channel (VC). There are several reasons why these problems occur:
- Switch card failures
- Port stuck problems
Troubleshooting Switch Card Failures
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:
Step 1 Under the lightest possible traffic, issue the show switch fabric command on the switch router to clear the counters.
Router#
show switch fabric MMC Switch Fabric (idb=0x61DD8F0C)
Key: Rej. Cells - # cells rejected due to lack of resources
Inv. Cells - # good cells that came in on a non-existent conn.
Mem Buffs - # cell buffers currently in use
RX Cells - # rx cells (16-bit)
TX Cells - # tx cells (16-bit)
Rx HEC - # cells Received with HEC errors
Tx PERR - # cells with memory parity errors
MSC# Rej. Cells Inv. Cells Mem. Buffs Rx Cells Tx Cells Rx HEC Tx PErr
----- ----------- ------------ ----------- ----------- ---------- ---------- ----------
MSC 0: 0 110018 0 0 0 0 0
MSC 1: 0 231044 0 0 0 0 0
MSC 2: 0 234283 0 0 0 0 0
MSC 3: 0 232492 0 0 0 0 0
MSC 4: 0 242004 0 0 0 0 0
MSC 5: 0 120995 345 0 0 0 0
MSC 6: 0 111466 0 0 0 0 0
MSC 7: 0 334398 0 0 0 0 0
Rejected Cells: 0
Invalid Cells: 1616700
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.
Router#
show switch fabric MMC Switch Fabric (idb=0x60CF1788)
Key: Rej. Cells - # cells rejected due to lack of resources
Inv. Cells - # good cells that came in on a non-existent conn.
Mem Buffs - # cell buffers currently in use
RX Cells - # rx cells (16-bit)
TX Cells - # tx cells (16-bit)
Rx HEC - # cells Received with HEC errors
Tx PERR - # cells with memory parity errors
MSC# Rej. Cells Inv. Cells Mem. Buffs Rx Cells Tx Cells Rx HEC Tx PErr
----- ----------- ------------ ----------- ----------- ---------- ---------- ----------
MSC 0: 2189 6 14177 0 0 0 0
Rejected Cells: 2189
Invalid Cells: 58
Look at the values in the Rejected Cells and Invalid Cells fields. Note that the Rejected Cells and Invalid Cells fields 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.
INT X-INT VCI QCNT VCI QCNT
Status of GigabitEthernet0/0/0: OK
Status of GigabitEthernet0/0/1: OK
Status of GigabitEthernet1/0/0: OK
Status of GigabitEthernet1/0/1: OK
Status of GigabitEthernet2/0/0: OK
Status of GigabitEthernet2/0/1: OK
Status of GigabitEthernet3/0/0: OK
Status of GigabitEthernet3/0/1: OK
Status of GigabitEthernet9/0/0: OK
Status of GigabitEthernet9/0/1: OK
Status of GigabitEthernet10/0/0: OK
Status of GigabitEthernet10/0/1: OK
Status of GigabitEthernet11/0/0: OK
Status of GigabitEthernet11/0/1: OK
Status of GigabitEthernet12/0/0: OK
Status of GigabitEthernet12/0/1: OK
If the queues are empty and all of the ports show OK status, then the problem is not the ports, but with the switch processor.
You can resolve this problem by upgrading your system software image to release version 12.0(4a)WX5(11) or later, replacing the switch processors, or both.
Troubleshooting Port Stuck Problems
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:
Step 1 Use the show switch fabric command to display the activity in the switch processors.
|
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. |
Router#
show switch fabric MMC Switch Fabric (idb=0x60CF1788)
Key: Rej. Cells - # cells rejected due to lack of resources
Inv. Cells - # good cells that came in on a non-existent conn.
Mem Buffs - # cell buffers currently in use
RX Cells - # rx cells (16-bit)
TX Cells - # tx cells (16-bit)
Rx HEC - # cells Received with HEC errors
Tx PERR - # cells with memory parity errors
MSC# Rej. Cells Inv. Cells Mem. Buffs Rx Cells Tx Cells Rx HEC Tx PErr
----- ----------- ------------ ----------- ----------- ---------- ---------- ----------
MSC 0: 389023 7896 14177 0 0 0 0
MSC 1: 0 32709 2070 0 0 0 0
MSC 6: 0 6170 1351 0 0 0 0
MSC 7: 0 9624 1280 0 0 0 0
Rejected Cells: 389023
Invalid Cells: 56399
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.
Router#
show switch fabric MMC Switch Fabric (idb=0x60CF1788)
Key: Rej. Cells - # cells rejected due to lack of resources
Inv. Cells - # good cells that came in on a non-existent conn.
Mem Buffs - # cell buffers currently in use
RX Cells - # rx cells (16-bit)
TX Cells - # tx cells (16-bit)
Rx HEC - # cells Received with HEC errors
Tx PERR - # cells with memory parity errors
MSC# Rej. Cells Inv. Cells Mem. Buffs Rx Cells Tx Cells Rx HEC Tx PErr
----- ----------- ------------ ----------- ----------- ---------- ---------- ----------
MSC 0: 2189 6 14177 0 0 0 0
Rejected Cells: 2189
Invalid Cells: 58
Look at the values in the Rejected Cells and Invalid Cells fields. Note that the Rejected Cells and Invalid Cells fields 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.
INT X-INT VCI QCNT VCI QCNT
Gi0/0/0 Gi1/0/0 67 640 62 0
Gi0/0/0 Gi1/0/0 71 546 66 0
Gi0/0/1 Gi1/0/0 67 135 147 0
Gi0/0/1 Gi1/0/0 69 18 149 0
Gi1/0/0 SRP 35 0 342 1791
Gi1/0/0 Gi0/0/0 62 0 67 640
Gi1/0/0 Gi0/0/0 66 0 71 546
Gi1/0/0 Gi0/0/1 147 0 67 135
Gi1/0/0 Gi0/0/1 149 0 69 18
Gi1/0/0 Gi1/0/1 152 0 67 639
Gi1/0/0 Gi12/0/0 577 0 67 640
Gi1/0/0 Gi12/0/0 578 0 68 16
Gi1/0/0 Gi12/0/0 579 0 69 38
Gi1/0/0 Gi12/0/0 580 0 70 16
Gi1/0/0 Gi12/0/1 662 0 67 640
Gi1/0/0 Gi12/0/1 666 0 71 640
Gi1/0/1 Gi1/0/0 67 639 152 0
Gi12/0/0 Gi1/0/0 67 640 577 0
Gi12/0/0 Gi1/0/0 68 16 578 0
Gi12/0/0 Gi1/0/0 69 38 579 0
Gi12/0/0 Gi1/0/0 70 16 580 0
Gi12/0/1 Gi1/0/0 67 640 662 0
Gi12/0/1 Gi1/0/0 71 640 666 0
Status of GigabitEthernet0/0/0: OK
Status of GigabitEthernet0/0/1: OK
Status of GigabitEthernet1/0/0: not OK
Status of GigabitEthernet1/0/1: OK
Status of GigabitEthernet2/0/0: OK
Status of GigabitEthernet2/0/1: OK
Status of GigabitEthernet12/0/0: OK
Status of GigabitEthernet12/0/1: OK
The show epc queueing 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 queueing 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 will not resolve the problem.
Configuring Automatic Port Stuck Failure Recovery
To recover from a port stuck failure, perform the following tasks:
- Detect port stuck failure.
- Isolate the cell stuck failure.
- If it is only a port stuck failure, isolate the port from the other functional ports.
- Depending on the configuration option for reset of the stuck port, one of the the following actions will occur:
-
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 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 route to automatically recover from port stuck failures, use the following interface configuration commands:
| Command |
Purpose |
|
Router(config-if)# epc port-reload
|
Enables automatic resetting and reloading of the interface module microcode after detecting a port stuck failure.
|
|
Router(config-if)# epc portstuck-wait seconds
|
Specifies the delay before signalling a port stuck failure (from the time the failure is detected). The default is 180 seconds. The range for seconds is 0 to 200. A value of 0 seconds causes a port stuck failure to not be detected.
|
|
 |
Caution Due to 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 will likely cause temporary connectivity loss. It is highly recommended to keep this value to at least 60 seconds. 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 will work very well. |
Connectivity Troubleshooting Commands
To troubleshoot a connectivity problem between a port and another port or end-station, use the following commands:
| Command |
Purpose |
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
|
Displays interface configuration, status, and statistics.
|
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port
|
Displays controller status for the specified interface.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port all
|
Displays all interface entry information for the specific interface.
|
|
show epc ip-prefix interface {fastethernet | gigabitethernet} slot/subslot/port all-entries
|
Displays all ip prefix entries for the specified interface.
|
|
show epc ip-address interface {fastethernet | gigabitethernet} slot/subslot/port all-entries
|
Displays all adjacent IP addresses for the specified interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipucast detail
|
Displays IP unicast patricia tree for the specified interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail
|
Displays the MAC patricia tree for the specified interface.
|
|
Troubleshooting IP Routing
The Catalyst 8540 CSR and Catalyst 8510 CSR use Cisco Express Forwarding (CEF). Much of the internal troubleshooting determines whether the central CEF information in the route processor is consistent with the distributed information in the content addressable memory (CAM) on the interfaces.
Follow these steps to troubleshoot IP routing problems:
Step 1 Verify the status of the IP routing table using the show ip route, show ip cef, and show adjacency detail commands as shown in Figure 2.
Figure 2 Displaying Router Table Information
- Verify in the show ip route command output that all the routes needed are in the routing table. If routes are missing, go through normal IP routing troubleshooting for the routing protocol in use.
- Verify in the show ip cef command output that the next hop or outgoing interface is valid.
- Verify in the show ip adjacency detail command output that the MAC rewrite information is correct for the interface. This information is built from the ARP table and resides on the route processor. The first 12 hexadecimal digits (or 6 bytes) represent the destination MAC address (DA), the next 12 hexadecimal digits (or 6 bytes), represent the source MAC address (SA), and the last 4 hexadecimal digits (or 2 bytes) represent the protocol field.
Step 2 Use the show epc ip-prefix, show epc ip-address, and show epc ifmapping commands to verify that the hardware is correct. Figure 3 shows output from these commands.
Figure 3 Hardware Verification
- The IP address in the show epc ip-prefix command output for the ingress interface should match the next hop IP address in the show epc cef command output in Figure 2. To remove inconsistencies between the CEF table and the IP prefix table, use the clear ip route command to rebuild these tables. You can either clear a specific route or use an asterisk (*) to clear all routes.
|
Caution Use the clear ip route command carefully. It causes a temporary increase in switch router activity which can lead to traffic disruptions. |
- The MAC address shown in the show ip ip-address command output should match the destination MAC address in the show adjacency command output in Figure 2.
- Using the interface number from the show epc ip-address command output, confirm the interface mapping with the show epc ifmapping command.
Step 3 Verify the CAM entry information using the show epc patricia ipucast and show epc cam commands.Figure 4 show the CAM entry information for the example network.
Figure 4 CAM Contents Verification
- Use the show epc patricia ipucast detail command to display the CAM entry location for the interface. Verify that the IF number and MAC address shown in Figure 2 match the output shown in Figure 3.
- Use the show epc cam command to display the CAM location which should match the destination MAC address. Figure 5 describes the format of the CAM entry contents.
Figure 5 CAM Entry Format
The DA MAC address in this entry is 0x00902141 and the interface number is 4.
Step 4 Use the show epc if-entry command on the ingress interface to confirm that the source address in the egress interface entry matches the source address shown by the show adjacency detail command output in Figure 2. Figure 6 shows the show epc if-entry command output.
Figure 6 Ingress Interface Entry
Step 5 To remove inconsistencies between the adjacency table and the IP address table, use the clear arp or clear adjacencies command to rebuild these tables.
|
Caution Use the clear arp and clear adjacencies commands carefully. They cause a temporary increase in switch router activity which can lead to traffic disruptions. |
IP Routing Troubleshooting Commands
To troubleshoot an IP routing problem, use the following commands:
| Command |
Purpose |
|
show ip route
|
Displays routing table entries.
|
|
show ip cef
|
Displays Cisco Express Forwarding information.
|
|
show adjacency detail
|
Displays IP address table information for adjacent nodes.
|
|
show ip route summary
|
Displays summary information about the routing table entries.
|
|
show ip protocols
|
Displays IP routing protocol parameters and statistics.
|
|
show ip interface brief
|
Displays IP interface status and configuration information.
|
|
show ip traffic
|
Displays IP protocol traffic statistics.
|
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the ingress interface)
|
Displays interface configuration, status, and statistics on the ingress interface.
|
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the egress interface)
|
Displays interface configuration, status, and statistics on the egress interface.
|
|
show epc freecam interface slot/subslot/port
|
Displays information about free space in the content addressable memory.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port all
|
Displays all interface entry information for the specific interface.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port entry {fastethernet | gigabitethernet} slot/subslot/port
|
Displays interface entry information for the specific interface.
|
|
show epc ip-prefix interface {fastethernet | gigabitethernet} slot/subslot/port all-entries (on the ingress interface)
|
Displays the IP network entries for the ingress interface.
|
|
show epc ip-prefix interface {fastethernet | gigabitethernet} slot/subslot/port all-entries (on the egress interface)
|
Displays the IP network entries for the egress interface.
|
|
show epc ip-address interface {fastethernet | gigabitethernet} slot/subslot/port all-entries (on the ingress interface)
|
Displays the IP addresses of adjacent interfaces.
|
|
show epc ip-address interface {fastethernet | gigabitethernet} slot/subslot/port all-entries (on the egress interface)
|
Displays the IP addresses of adjacent interfaces.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipucast detail (on the ingress interface)
|
Displays the patricia tree entries in the CAM.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipucast detail (on the egress interface)
|
Displays the patricia tree entries in the CAM.
|
|
If a BVI is involved in the problem, use the following commands:
| Command |
Purpose |
|
show bridge group
|
Displays bridge group configuration and status information.
|
|
show interfaces irb
|
Displays integrated routing and bridging configuration and status for all interfaces.
|
|
show smf
|
Displays software MAC address information.
|
|
show interfaces bvi number
|
Displays BVI interface information.
|
|
show bridge number group
|
Displays the status of the member ports in the specified bridge group.
|
|
show bridge number
|
Displays the status of the bridge group.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail
|
Displays the MAC patricia tree for the physical interface in the bridge group with a problem.
|
|
Troubleshooting IPX Routing
IPX troubleshooting is similar to IP troubleshooting. The key is to check the consistency between the route processor table information and CAM tables on the ports.
Step 1 First verify that the system software is functioning properly. The show ipx route and show ipx servers commands display information in the route processor memory. Figure 7 provides example displays of IPX information in the route processor memory.
Figure 7 Route Processor IPX Information
The show ipc route command displays the IPX routes through the switch router. In this example, the routes are 8511 and 8512, the SAP server number is 8541, the egress interface is GigabitEthernet 11/0/1, and the node address is 8510.0010.7bfa.5f1f.
|
Note The SAP entries reside in route processor memory, not in the port CAM tables. |
Step 2 Now use the show epc ipx-prefix, show epc ipx-node, and show epc ipx cam commands to display the CAM tables for the ingress interface in question. The route lookups and packet rewrites are performed by the ingress interface. The example shown in Figure 8 uses the route numbers and MAC addresses highlighted in Figure 7.
Figure 8 Ingress Interface CAM Table Information
- The show epc ipx-prefix command output for route 8512 to the egress interface shows the address of the CAM entry. The address is hexadecimal 101B, which you can convert to decimal 4123.
- The show epc node command output for node address 8510.0010.7bfa.5f1f confirms the information in the show epc ipx-prefix command output.
- The show epc cam command output for the CAM entry address displayed in the show ipx route command output confirms the destination MAC address.
Step 3 Figure 9 shows the format of the CAM entry. The last two bytes of the entry contain the interface number.
Figure 9 CAM Entry Format
Use the show epc ifmapping command output to verify the interface number for the egress interface.
Step 4 You can obtain detailed information about the IPX prefix and node for both directly connected and remote networks using the show epc patricia ipx detail command (see Figure 10).
Figure 10 IPX Prefix and Node Information
\
- If you want to examine information for a directly connected network, look at the entries that contain the status CONNECTED. In the example in Figure 10, look at entry 2#. Verify that the Prefix field contents matches the egress route number from the show ipx route command output in Figure 7. Also note that the second node entry matches the show epc cam command output shown in Figure 8.
- For a remote connection, the word "dirty" is a normal entry type. In the example in Figure 10, entry 3# and entry 4# are remote entries. NHOP1 is a pointer to the adjacency entry for the next hop to get to networks nodes 8512 and 8511. These are not the MAC addresses of the next hop. If the entry says valid, it means that the entry is usable.
Step 5 Use the show epc if-entry command on the ingress interface to display information about the egress interface. In the example shown in Figure 11, the ingress interface is GigabitEthernet 11/0/1 and the egress interface is GigabitEthernet 10/0/0.
Figure 11 Interface Entry Information
IPX Routing Troubleshooting Commands
To troubleshoot an IPX problem, use the following commands:
| Command |
Purpose |
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the ingress interface)
|
Displays interface configuration, status, and statistics on the ingress interface.
|
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the egress interface)
|
Displays interface configuration, status, and statistics on the ingress interface.
|
|
show ipx route
|
Displays the IPX routing table.
|
|
show ipx servers
|
Displays SAP server status information.
Note Use this command only if you have a server or SAP reachability problem.
|
|
show ipx interface brief
|
Displays IPX interface configuration and status.
|
|
show epc freecam interface slot/subslot/port
|
Displays information about free space in the content addressable memory.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipx detail (on the ingress interface)
|
Displays the IPX patricia tree for the ingress interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipx detail (on the egress interface)
|
Displays the IPX patricia tree for the egress interface.
|
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipx-prefix all-entries (on the ingress interface)
|
Displays all the IPX prefixes for the ingress interface.
|
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipx-prefix all-entries
(on the egress interface)
|
Displays all the IPX prefixes for the egress interface.
|
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipx-prefix fail-entries
(on the ingress interface)
|
Displays inconsistent IPX prefixes for the ingress interface.
|
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipx-prefix fail-entries
(on the egress interface)
|
Displays inconsistent IPX prefixes for the egress interface.
|
|
If a BVI is involved, use the following commands:
| Command |
Purpose |
|
show bridge group
|
Displays bridge group configuration and status information.
|
|
show interfaces irb
|
Displays integrated routing and bridging configuration and status for all interfaces.
|
|
show smf
|
Displays software MAC address information.
|
|
show interfaces bvi number
|
Displays BVI interface information.
|
|
show bridge number group
|
Displays the status of the member ports in the specified bridge group.
|
|
show bridge number
|
Displays the status of the bridge group.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail
|
Displays the MAC patricia tree for the specified interface physical interface in the bridge group BVI with a problem.
|
|
Troubleshooting IP Multicast
IP multicast troubleshooting is similar to IP troubleshooting. The key is to check the consistency between the route processor table information and CAM tables on the interfaces.
Follow these steps to troubleshoot IP multicast problems:
Step 1 Use the show epc if-entry command to display information about VC status:
J1#
show epc if-entry interface fastethernet 1/0/15 entry gigabitethernet 0/0/0 IF Entry for GigabitEthernet0/0/0 on FastEthernet1/0/15
Mac(hex) - 00:90:21:41:BC:07
isMyInteface : False isSubInterface : False
Status Up Broute VC - 67 Bcast VC - 0
State : Not-Applicable/Listening/Blocking
IP routing on bridging off
IPX routing off bridging off
ICMP Redirect enabled Unreachable enabled
IP Multicast enabled: ttl-threshold: 5
- Check the Status field to ensure that the route is up.
- Check the IP routing field to ensure that it is on.
- Check the IP Multicast field to ensure that it is enabled.
If you have any problems with these fields, check the interface configuration. For information about configuring interfaces, refer to the Layer 3 Software Feature and Configuration Guide.
Step 2 Display the IP multicast entries contained in the CPU using the show ip mroute command.
c8540-r6-1#
show ip mroute IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
X - Proxy Join Timer Running
Outgoing Interface Flags: H - Hardware switched
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.2.236.92), 00:58:34/00:03:09, RP 10.6.11.10, flags: S
Incoming interface: POS12/0/0, RPF nbr 10.6.11.10
FastEthernet3/0/13, Forward/Sparse, 00:57:56/00:03:09
FastEthernet2/0/15, Forward/Sparse, 00:58:13/00:02:53
(10.64.1.19, 224.2.236.92), 00:58:13/00:03:22, flags: T
Incoming interface: POS12/0/0, RPF nbr 10.6.11.10
FastEthernet3/0/13, Forward/Sparse, 00:57:56/00:03:08
FastEthernet2/0/15, Forward/Sparse, 00:58:13/00:02:53
Step 3 Use the address and interface information from the show ip mroute command output in Step 2 to display the CAM information with the show epc ipmcast command.
c8540-r6-1#
show epc ipmcast 224.2.236.92 10.64.1.19 detail interface pos 12/0/0MEMBER_ENTRY, root vc = 0/801, packet counter = 47
(224.2.236.92, 10.64.1.19), CAM Loc 0x17102, 00 34 48 00 00 2F 32 11
Send_to_cpu flag not set, SPT flag set
p2mp vc:root POS12/0/0, VPI = 0, VCI = 801
leaf FastEthernet2/0/15, VPI = 0, VCI = 762
FastEthernet3/0/13, VPI = 0, VCI = 751
- Multicast group 224.2.236.92 and source 10.64.1.19 has a CAM entry on interface POS 12/0/0.
- The Send_to_cpu flag is appropriately not set for a specified source (S, G) within a group indicating that the traffic is switched in the data plane by the interface. The Send_to_cpu flag is set for table entries for all sources within a group (*, G) to maintain the state for this entry on the control plane.
Step 4 Display the status of the VC for the incoming interface displayed in the show ip mroute command output in Step 2.
c8540-r6-1#
show atm-internal vc cast-type p2mp interface pos 12/0/0 Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status
POS12/0/0 0 801 PVC Fa2/0/15 0 762 UP
- Check that the VC identifier in the VPI and VCI columns matches for the corresponding interface listed in the show epc ipmcast command output shown in Step 3.
- Check that the VC identifier listed in X-VPI and X-VCI columns matches the entry for the corresponding interface listed in the show epc ipmcast command output shown in Step 3.
If there are inconsistencies or non-zero invalid entries in the tables, you can use the clear ip mroute * command to rebuild the tables.
|
Caution Use the clear ip mroute command carefully. It causes a temporary increase in switch router activity, which can lead to traffic disruptions. |
IP Multicast Troubleshooting Commands
To troubleshoot an IP multicast problem, use the following commands:
| Command |
Purpose |
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the ingress interface)
|
Displays interface configuration, status, and statistics on the ingress interface.
|
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the egress interface)
|
Displays interface configuration, status, and statistics on the egress interface.
|
|
show ip mroute
|
Displays the IP multicast routing table.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port all (on the ingress interface)
|
Displays all interface entry information for the ingress interface.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port entry {fastethernet | gigabitethernet} slot/subslot/port (on the egress interface)
|
Displays interface entry information for the egress interface.
|
|
show epc ipmcast groupaddr interface {fastethernet | gigabitethernet} [cam {0 | 1}] (on the ingress interface)
|
Displays the IP multicast routing table information stored on the ingress interface for a particular group IP address.
|
|
show epc ipmcast groupaddr interface {fastethernet | gigabitethernet} [cam {0 | 1}] (on the egress interface)
|
Displays the IP multicast routing table information stored on the egress interface for a particular group IP address.
|
|
show epc ipmcast groupaddr all interface {fastethernet | gigabitethernet} slot/subslot/port (on the ingress interface)
|
Displays the IP multicast routing table information stored on the ingress interface for a particular group IP address.
|
|
show epc ipmcast groupaddr all interface {fastethernet | gigabitethernet} slot/subslot/port (on the egress interface)
|
Displays all IP multicast routing table information stored on the egress interface for a particular group IP address.
|
|
show epc ipmcast groupaddr detail interface {fastethernet | gigabitethernet}
(on the ingress interface)
|
Displays detailed IP multicast routing table information stored on the ingress interface for a particular group and source IP address.
|
|
show epc ipmcast groupaddr detail interface {fastethernet | gigabitethernet}
(on the egress interface)
|
Displays detailed IP multicast routing table information stored on the egress interface for a particular group and source IP address.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipmcast detail
(on the ingress interface)
|
Displays detailed IP multicast patricia tree information for the ingress interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipmcast detail
(on the egress interface)
|
Displays detailed IP multicast patricia tree information for the egress interface.
|
|
Troubleshooting Layer 2 Switching
The switch router might be configured with Layer 2 ports using bridge groups.
To troubleshoot Layer 2 switching, perform the following steps:
Step 1 Use the show spanning-tree, show bridge, and show epc mac commands to display bridge group information as shown in Figure 12.
Figure 12 Bridge Group Information
- Find the entries in the show spanning-tree command output for the interfaces in question.
- Find the entries for those interfaces in the show bridge command output.
- Use that information to display the MAC address information in the interface CAM using the show epc mac command. Verify that the information displayed is consistent.
Step 2 Use the show epc patricia command to display Layer 2 information in the CAM for each interface.
Figure 13 Layer 2 CAM Information
Verify that the information from the show epc patricia command output in Figure 13 is consistent with the command outputs in Figure 12.
If there are inconsistencies or non-zero invalid entries in the tables, you can use the clear bridge command to rebuild the tables.
|
Caution Use the clear bridge command carefully. It causes a temporary increase in switch router activity which can lead to traffic disruptions. |
Step 3 Display the interface table entry in the CAM using the show epc if-entry command. Figure 14 shows the CAM interface table entry for the example network interface.
Figure 14 CAM Interface Information
- Check the Status field to ensure that the interface is Up.
- Check the IP routing and IPX routing fields to ensure that they are off and that bridging is on.
- Check the AppleTalk routing field to ensure that it is off.
Refer to the Layer 3 Software Feature and Configuration Guide if any changes are necessary to the configuration of the interface.
Layer 2 Bridging Troubleshooting Commands
To troubleshoot a Layer 2 bridging problem, use the following commands:
| Command |
Purpose |
|
show bridge group
|
Displays bridge group configuration and status information.
|
|
show bridge
|
Displays the status of all the bridge groups on the switch router.
|
|
show spanning-tree number
|
Displays the spanning tree topology for a bridge group.
|
|
show interfaces bvi number
|
Displays BVI interface configuration, status, and statistics. Use this command when the BVI is part of a bridge group.
|
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the ingress interface)
|
Displays interface configuration, status, and statistics on the ingress interface.
|
|
show interfaces {fastethernet | gigabitethernet} slot/subslot/port
(on the egress interface)
|
Displays interface configuration, status, and statistics on the egress interface.
|
|
show switch bridge-table entry
|
Displays bridge table entry summary.
|
|
show epc freecam interface {fastethernet | gigabitethernet} slot/subslot/port
|
Displays information about free space in the content addressable memory.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port all
|
Displays all interface entry information for the specific interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail (on the ingress interface)
|
Displays the MAC patricia tree for the ingress interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail (on the egress interface)
|
Displays the MAC patricia tree for the egress interface.
|
|
If a BVI is involved, use the following commands:
| Command |
Purpose |
|
show bridge group
|
Displays bridge group configuration and status information.
|
|
show interfaces irb
|
Displays integrated routing and bridging configuration and status for all interfaces.
|
|
show smf
|
Displays software MAC address information.
|
|
show interfaces bvi number
|
Displays BVI interface information.
|
|
show bridge number group
|
Displays the status of the member ports in the specified bridge group.
|
|
show bridge number
|
Displays the status of the bridge group.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail
|
Displays the MAC patricia tree for the specified interface physical interface in the bridge group with a problem.
|
|
Troubleshooting Commands
The switch router software provides several show commands that can be used for troubleshooting. This section contains lists of show commands grouped by the features they troubleshoot.
Troubleshooting Trunk Port Problems
To troubleshoot trunk port problems, use the following command:
| Command |
Purpose |
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port vlan vlan detail
|
Displays the patricia tree information for the specified VLAN (for each VLAN on trunk).
|
|
Troubleshooting AppleTalk Problems
To troubleshoot an AppleTalk problem, use the following commands:
| Command |
Purpose |
|
show appletalk route
|
Displays the AppleTalk routing table entries.
|
|
show appletalk interface brief
|
Displays AppleTalk configuration and status information for all interfaces.
|
|
show appletalk zone
|
Displays AppleTalk zone table information.
|
|
show appletalk interface {fastethernet | gigabitethernet} slot/subslot/port (on the ingress interface)
|
Displays AppleTalk configuration and status information for the ingress interface.
|
|
show appletalk interface {fastethernet | gigabitethernet} slot/subslot/port (on the egress interface)
|
Displays AppleTalk configuration and status information for the egress interface.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port all (on the ingress interface)
|
Displays all interface entry information for the ingress interface.
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port entry {fastethernet | gigabitethernet} slot/subslot/port (on the egress interface)
|
Displays detailed interface entry information for the egress interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail (on the ingress interface)
|
Displays the MAC patricia tree for the ingress interface.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail (on the egress interface)
|
Displays the MAC patricia tree for the egress interface.
|
|
show smf
|
Displays software MAC address information.
|
|
If a BVI is involved, use the following commands:
| Command |
Purpose |
|
show bridge group
|
Displays bridge group configuration and status.
|
|
show interfaces irb
|
Displays integrated routing and bridging configuration and status for all interfaces.
|
|
show smf
|
Displays software MAC address information.
|
|
show interfaces bvi number
|
Displays BVI interface information.
|
|
show bridge number group
|
Displays the status of the member ports in the specified bridge group.
|
|
show bridge number
|
Displays the status of the bridge group.
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail
|
Displays the MAC patricia tree for the problematic physical interface in the bridge group.
|
|
Converted show epc Commands
In the 12.0(10)W5(18) system software release, some of the show commands commonly used for troubleshooting have been converted from show epc commands to show controllers commands. The show controllers commands are described in the next section. Table 1 provides the mapping of the command syntax conversion.
Table 1 show Command Conversion
| Release 12.0(5)W5(13d) and Earlier show Command Syntax |
Release 12.0(10)W5(18) show Command Syntax |
|
show epc ip-prefix interface {fastethernet | gigabitethernet} slot/subslot/port all-entries
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ip-prefix all-entries
|
|
show epc ip-prefix interface {fastethernet | gigabitethernet} slot/subslot/port
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ip-prefix
|
|
show epc ip-address interface {fastethernet | gigabitethernet} slot/subslot/port all-entries
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ip-address all-entries
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipucast detail
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port patricia ipucast detail
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port all
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port if-entry all
|
|
show epc if-entry interface {fastethernet | gigabitethernet} slot/subslot/port entry {fastethernet | gigabitethernet} slot/subslot/port
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port if-entry entry {fastethernet | gigabitethernet} slot/subslot/port
|
|
show epc freecam interface slot/subslot/port
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port freecam
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port mac detail
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port patricia mac detail
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port vlan vlan detail
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port patricia vlan vlan detail
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipx detail
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port patricia ipx detail
|
|
show epc patricia interface {fastethernet | gigabitethernet} slot/subslot/port ipmcast detail
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port patricia ipmcast detail
|
|
show epc ipmcast groupaddr interface {fastethernet | gigabitethernet} [cam {0 | 1}]
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipmcast groupaddr [cam {0 | 1}]
|
|
show epc ipmcast groupaddr all interface {fastethernet | gigabitethernet}
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipmcast groupaddr all
|
|
show epc ipmcast groupaddr detail interface {fastethernet | gigabitethernet}
|
show controllers {fastethernet | gigabitethernet} slot/subslot/port ipmcast groupaddr detail
|
|
show epc counters
|
show controllers c8500 counters
|
|
show epc lsipc detail
|
show controllers c8500 epc detail
|
|
show epc queuing
|
show controllers c8500 queuing
|
|
show controllers and show switch Commands
This section contains descriptions of show controllers and show switch commands that are useful for troubleshooting.
show controllers
To display the controller register values, use the show controllers EXEC command.
- show controllers interface-type slot/subslot/interface
Syntax Description
|
interface-type
|
Specifies an interface type as fastethernet, gigabitethernet, or atm.
|
|
slot/subslot/interface
|
Identifies the interface specified in interface-type.
|
|
Command Modes
Privileged EXEC
Usage Guidelines
This command uses IPC to get the values of MAC registers and MII registers. If the interface processor stops responding to IPC, the counter values shown are no longer current.
Examples
The following is sample output from the show controllers command for a Fast Ethernet interface:
Router#
show controllers fastethernet 11/0/4 IF Name:FastEthernet11/0/4
Loopback Reg [3-0]|[7-4]:0x8|0x8
Duplex/Speed Reg [3-0]|[7-4]:0xFFFF|0x0
SMDR 0x0060 (Tx En, Rx En)
SSMR 0x4000 SIMR 0x0000 MBXW 0x0000 MBXR 0x0000
SPER 0xF000 GMUX VER 0xF000 MARKER 0x0000
CMCR :0x00000443 CMPR :0x140A0E60
Control Register (0x0):0x2000
Status Register (0x1):0x780D (Link Up)
PHY Identification Register 1 (0x2):0x7810
PHY Identification Register 2 (0x3):0x43
Auto Neg. Advertisement Reg (0x4):0x81 (Speed 100,Duplex half)
Auto Neg. Partner Ability Reg (0x5):0x0 (Peer not auto-negotiating)
Auto Neg. Expansion Register (0x6):0x0
Mirror Register (0x10):0x630
Interrupt Enable Register (0x11):0x0
Interrupt Status Register (0x12):0x4000
Configuration Register (0x13):0x0 (UTP, Tx Enable)
Chip Status Register (0x14):0x28C8 (Link Up, Half, 100)
Link Status Register [3-0]|[7-4]:0x1|0x0
Header Sequence Errors = 0
Slicer Transmit Counters:
Table 2 describes some of the important fields in the previous display.
Table 2 show controllers Registers and Descriptions for Fast Ethernet Interfaces
| Register Type |
Register Name |
Description |
| Slicer Registers |
SMDR
|
Should show a value of 0x60
|
|
SSTR
|
Value of 0x1008 or 0x1009 indicates that the Ethernet processor microcode has not been successfully downloaded.
|
| MAC Registers |
CMCR
|
For Catalyst 8510 Fast Ethernet cards when the interface is not shut down:
- Full duplex = 0x00000423
- Half duplex = 0x00000403
- Auto = negotiated duplex value
For Catalyst 8540 Fast Ethernet cards when the interface is not shut down:
- Full duplex = 0x00000463
- Half duplex = 0x00000443
- Auto = negotiated duplex value
|
| MII Registers |
Status register (0x1)
|
- Bit 14 = 100 Mbps, full duplex
- Bit 13 = 100 Mbps, half duplex
- Bit 12 = 10 Mbps, full duplex
- Bit 11 = 10 Mbps, half duplex
- Bit 5 = autonegotiation complete
- Bit 3 = autonegotiation capable
- Bit 2 = link up
Bits 11 through 14 indicate link capability.
|
|
Auto-
negotiation advertisement register (0x4)
|
- Bit 13 = remote fault
- Bit 8 = 100 Mbps, full duplex
- Bit 7 = 100 Mbps
- Bit 6 = 10 Mbps, full duplex
- Bit 5 = 10 Mbps
- Bit 0 = 1 (fixed value)
Bits 5 through 8 indicate link capability.
|
|
Auto- negotiated partner ability register (0x5)
|
Same values as autonegotiation advertisement register. Bits 5 through 8 indicate link partner capability. This register is set to nonzero only if the local and peer are configured to autonegotiate.
|
|
Chip status register (0x14)
|
- Bit 13 = link up
- Bit 12 = full duplex
- Bit 11 = 100 Mbps
- Bit 9 = autonegotiation complete
- Bit 5 = symbol error
- Bit 4 = MLT3 error
- Bit 0 = PLL lock
|
|
The following is sample output from the show controllers command for a Gigabit Ethernet interface:
Router#
show controllers gigabitethernet 9/0/0 IF Name:GigabitEthernet9/0/0
Gigabit Ether Status :0x310 (Link Down, Rx Sync-N, Optical detect-N)
Mode Parallel Register :0x36
Port 0 Serial Mode Register :0x1
Port 1 Serial Mode Register :0x1
Link Interrupt Enable :0x1
SMDR 0x0060 (Tx En, Rx En)
SSMR 0x4000 SIMR 0x0000 MBXW 0x0000 MBXR 0x0000
SPER 0xF000 GMUX VER 0x17B1 MARKER 0x17B1
CMCR :0x00000423 CMPR :0x140A0E61
Control Register (0x0):0x4140
Status Register (0x1):0x159
Auto Neg. Advt. Register (0x4):0x20
Auto Neg. Partner Ability Reg (0x5):0x0
RX Configuration Register (0xA):0x21
TR_IPG_TIME Register (0x10):0x6
PAUSE_TIME Register (0x11):0x0
PAUSE_SA1 Register (0x12):0x0
PAUSE_SA2 Register (0x13):0x0
PAUSE_SA3 Register (0x14):0x0
Pause Watermark Register (0x15):0xC040
TX FIFO Watermark Register (0x16):0xFF02
PAUSE_STAT_SENT Register (0x17):0x0
PAUSE_STAT_RCVD Register (0x18):0x0
Memory Address Register (0x19):0x0
Memory Control Register (0x1A):0x1
Memory Data High Register (0x1B):0x0
Memory Data Low Register (0x1C):0x0
Sys Control Register (0x1E):0x70C
Sys Status Register (0x1F):0x0
Link Status Register [3-0]|[7-4]:0x0|0x0
Header Sequence Errors = 0
Slicer Transmit Counters:
Header Sequence Errors = 0
Slicer Transmit Counters:
Table 3 describes some of the important fields in the previous display.
Table 3 show controllers Registers and Descriptions for Gigabit Ethernet Interfaces
| Register Type |
Register Name |
Description |
|
Gigabit Ether status
|
- Bit 7 = link up
- Bit 6 = rx sync
- Bit 5 = optical detect
- Bit 2 = link up
- Bit 1 = rx sync
- Bit 0 = optical detect
Bits 5 through 7 apply to port 1; bits 0 through 2 apply to port 0.
|
| MAC Registers |
CMCR
|
Should be 0x00000423
|
| MII Registers |
Control register (0x0)
|
- Bit 13 = loopback enable
- Bit 12 = autonegotiation enable
ATM router module port has loopback enable bit set.
|
|
Status register (0x1)
|
- Bit 5 = autonegotiation complete
- Bit 3 = autonegotiation capable
- Bit 2 = link up
|
|
Auto- negotiation advertisement register (0x4)
|
- Bit 12 through 13 = remote fault
- Bit 6 = half duplex
- Bit 5 = full duplex
- Bits 4 through 0 = 00000 (fixed)
|
|
Auto- negotiation partner ability register (0x5)
|
Same values as autonegotiation advertisement register. This register is set to nonzero only if the local and peer are configured to autonegotiate.
|
|
System control register (0x1e)
|
Bit 4 = link up
|
| Hardware channel counters |
|
For Gigabit Ethernet or ATM router module ports there are eight channels that show eight sets of counters.
|
|
show controllers access-list
To display the access control list (ACL) entries on an interface module, use the show controllers access-list command.
- show controllers interface-type slot/subslot/interface access-list {in | out}
Syntax Description
|
interface-type
|
Specifies an interface type as fastethernet or gigabitethernet.
|
|
slot/subslot/interface
|
Identifies the interface specified in interface-type.
|
|
in
|
Displays TCAM entries for input ACL configuration.
|
|
out
|
Displays TCAM entries for output ACL configuration.
|
|
Command Modes
Privileged EXEC
Usage Guidelines
This command displays TCAM entries for an ACL configured on an interface. It interprets the contents of TCAM and displays them in the same format as the Cisco IOS ACL commands, such as the show access-lists command.
|
Note Because of optimization, there might not be a one-to-one mapping of the output of the show controllers access-list command and the original access list. |
Examples
The following is sample output from the show controllers access-list command:
Router#
show controllers fastethernet 3/0/0 access-list in Input ACL entries for Interface FastEthernet3/0/0 Index:6 Label:2
[V:0 M:1][0 IP] deny ip 100.1.3.0 0.0.0.255 any
[V:0 M:2][1 IP] permit ip any any
[V:0 M:3][2 IPX] permit 1 2.1000.0000.0003
[V:0 M:4][3 IPX] deny 1 2
[V:0 M:5][4 IPX] deny any any
This output corresponds to the following access-list configuration:
Router#
show running-config interface fastethernet 3/0/0 Building configuration...
interface FastEthernet3/0/0
ip address 1.0.0.1 255.0.0.0
Table 4 describes the fields in the show controllers access-list display.
Table 4 show controllers access-list Field Descriptions
| Field |
Description |
|
Index
|
Index used for this interface for ACL lookups
|
|
Label
|
Label used to identify TCAM entries for this ACL
|
|
[V:num1 M:num2]
|
TCAM value location and TCAM mask location
|
|
[protocol]
|
IP or IPX
|
|
show controllers adjacency
To display the IP address table on an interface module, use the show controllers adjacency privileged EXEC command.
- show controllers interface-type slot/subslot/interface adjacency {ip-address | detail} [cam module-num]
Syntax Description
|
interface-type
|
Specifies an interface type as fastethernet, gigabitethernet, or atm.
|
|
slot/subslot/interface
|
Identifies the interface specified in interface-type.
|
|
ip-address
|
Specifies an IP address to display from the table.
|
|
detail
|
Displays additional information.
|
|
cam module-num
|
Specifies the CAM module to display.
|
|
Command Modes
Privileged EXEC
Usage Guidelines
This command displays the IP address table on each interface module. This table contains IP address entries present in the ARP table (displayed by the show arp command) and adjacency table (displayed by the show adjacency command). This table has a one-to-one correspondence with the adjacency table.
Examples
The following is sample output from the show controllers adjacency command:
Router#
show controllers fastethernet 3/0/0 adjacency detail IPaddr:1.0.0.2 MACaddr:00e0.4f5d.f000 FastEthernet3/0/0(6)
IPaddr:2.0.0.6 MACaddr:0007.0007.0007 FastEthernet3/0/2(8)
IPaddr:1.0.0.5 MACaddr:0005.0005.0005 FastEthernet3/0/0(6)
IPaddr:2.0.0.5 MACaddr:0006.0006.0006 FastEthernet3/0/2(8)
Total number of IP adjacency entries:4
Missing IP adjacency entries:0
show controllers cef
To display the IP prefix table on interface modules, use the show controllers cef EXEC command.
- show controllers interface-type slot/subslot/interface cef {prefix mask | detail | missing | summary} [cam module-num]
Syntax Description
|
interface-type
|
Specifies an interface type as fastethernet, gigabitethernet, or atm.
|
|
slot/subslot/interface
|
Identifies the interface specified in interface-type.
|
|
prefix
|
Specifies an IP address prefix to display from the table.
|
|
mask
|
Specifies an IP address mask.
|
|
detail
|
Displays additional information.
|
|
missing
|
Displays all entries that are present in the CEF table but missing from the interface module IP prefix table.
|
|
summary
|
Displays only a summary of the IP prefix table.
|
|
cam module-num
|
Specifies the CAM1 module to display.
|
|
CAM = content addressible memory
|
Command Modes
Privileged EXEC
Usage Guidelines
This command displays the IP prefix table on each interface module. The table contains IP prefix entries present in the IP routing table (displayed by the show ip route command) and CEF table (displayed by the show ip cef command). This table has a one-to-one correspondence with the CEF table.
Examples
The following is sample output from the show controllers cef summary command.
Router#
show controllers fastethernet 3/0/0 cef summary Total IP Prefix Entries in CAM:14
Missing IP Prefix Entries in CAM:0
CEF entries not populated:8
The following is sample output from the show controllers cef missing command:
Router#
show controllers fastethernet 3/0/0 cef missing Total IP Prefix Entries in CAM:15
Missing IP Prefix Entries in CAM:0
CEF entries not populated:15
The following is sample output from the show controllers cef detail command:
Router#
show controllers fastethernet 3/0/0 cef detail Default Network Information:
128.46.167.95/32 not populated
128.118.25.3/32 not populated
140.247.60.28/32 not populated
171.69.1.129/32 not populated
224.0.0.0/4 not populated
255.255.255.255/32 not populated
Total IP Prefix Entries in CAM:15
Missing IP Prefix Entries in CAM:0
CEF entries not populated:15
Table 5 describes some of the fields in the display.
Table 5 show controllers cef Field Descriptions
| Field |
Description |
|
Prefix
|
IP prefix entry
|
|
Masklen
|
Mask length of IP prefix entry
|
|
SRP
|
Packets are sent to the route processor
|
|
Missing
|
IP prefix entry is present in CEF table but missing from interface module prefix table
|
|
Not populated
|
IP prefix entry present in CEF table but not populated in the interface module prefix table for one of the following reasons:
- Prefix entry with all zeros or all ones
- Prefix entries reachable via management port (ethernet0)
- Prefix entries with corresponding adjacency entries (displayed with the show adjacency command)
- Prefix entries that have one of the gateways as a management port
- 224.0.0.0/4 overlaps with 224.0.0.0/24
|
|
Default network
|
Default network information
|
|
Load balancing
|
Displays whether load balancing is on or off for default network
|
|
show controllers database layer2
To display the contents of the Layer 2 CAM on interface modules, use the show controllers database layer2 privileged EXEC command.
- show controllers interface-type slot/subslot/interface database layer2
- show controllers interface-type slot/subslot/interface database layer2 detail [cam module-num]
- show controllers interface-type slot/subslot/interface database layer2 vlan vlan_id [cam module-num]
Syntax Description
|
interface-type
|
Specifies an interface type as fastethernet, gigabitethernet, or atm.
|
|
slot/subslot/interface
|
Identifies the interface specified in interface-type.
|
|
detail
|
Displays additional information.
|
|
vlan vlan_id
|
Displays all entries associated with the VLAN.
|
|
cam module-num
|
Specifies the CAM module to display.
|
|
Command Modes
Privileged EXEC
Usage Guidelines
The CAM number should be specified for dual CAM interfaces, such as a single interface of a 2-port GigabitEthernet interface module. For GigabitEthernet interfaces, if the CAM number is not specified then the commands displays information from CAM 0 by default .
Examples
The following is sample output from the show controllers database layer2 command:
Router#
show controllers interface fastethernet 1/0/0 database layer2 1# MAC addr:0000.0000.0000 VC:0 Entry:
2# MAC addr:0900.2b01.0001 MyMAC
3# MAC addr:0180.c200.0000 MyMAC
4# MAC addr:0100.0ccc.cccd MyMAC
5# MAC addr:0100.0ccc.cccc MyMAC
Total number of MAC entries: 5
The following is sample output from the show controllers database layer2 detail command:
Router# show controllers interface fastethernet 1/0/0 database layer2 detail
