|
|
Catalyst 8540 Cisco IOS Release 12.0(22)W5(25)
Text Part Number: OL-1530-06 Rev. A0
This document describes the features and caveats for Cisco IOS Release 12.0(22)W5(25) software for the Catalyst 8540 switch router.
This document includes the following sections:
The Catalyst 8540 multiservice switch router (MSR) is a 13-slot, modular chassis featuring dual, fault-tolerant, load-sharing AC or DC power supplies. The ATM switch router provides a 20-Gbps full-duplex nonblocking switch fabric with switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.
The Catalyst 8540 CSR switch router belongs to a class of high-performance Layer 3 switch routers and is optimized for the campus LAN or the intranet. The Catalyst 8540 CSR switch router provides both wirespeed Ethernet routing and switching services.
This section describes the system requirements for Cisco IOS Release 12.0(22)W5(25) and includes the following sections:
The DRAM memory configuration is 256 MB, which is the default for the Catalyst 8540.
Cisco IOS Release 12.0(22)W5(25) and later releases require a minimum of 16 MB of contiguous boot Flash memory. The Catalyst 8540 route processor now ships by default with a 16-MB boot Flash SIMM.
Earlier releases of the Catalyst 8540 switch router shipped with an 8-MB boot Flash SIMM. The 8-MB boot Flash SIMM is not large enough to store system images for Cisco IOS software releases 12.0(4a)W5(11a) and later.
To check that your system has a 16-MB boot Flash SIMM, enter the show hardware EXEC command. The part numbers for route processors with a default 16-MB boot Flash SIMM are as follows:
If you have an 8-MB boot Flash SIMM, and have no additional memory installed, we recommend that you order a spare Flash PC card programmed with the latest version of the system image, part number MEM-8540M-FLC20M=.
Alternatively, you can use one of the following options to accommodate the larger image:
 |
Note If you have a Smart Modular, Sharp, or Intel 2+ Flash PC card that was formatted using a Cisco IOS software release prior to 12.0(4a)W5(11a), reformat it with Cisco IOS Release 12.0(22)W5(25) prior to downloading the image (you might need to boot the image from a TFTP server to format the PC Flash card). Do not erase the system image on the boot Flash SIMM. If the procedure fails, you will need it to recover. (See caveat CSCdm47012 later in these release notes for more information.) |
|
Note If you have a redundant route processor configuration, you need ROMMON image 12.0(4.6)W5(13) or later. See caveats CSCdm81581, CSCdm54297, and CSCdm43664, which are described later in these release notes, for more information. |
|
Note The boot ROM on the Catalyst 8540 can be field-upgraded via the reprogram command. For more information about upgrading the boot ROM, see the ATM Switch Router Command Reference. |
For more information about downloading system images and changing the default boot image, refer to the "File Management" chapter of the Configuration Fundamentals Configuration Guide in the Cisco IOS software documentation set.
Table 1 and Table 2 list the hardware modules supported on the Catalyst 8540 in the Cisco IOS Release 12.0(22)W5(25). They also include the minimum software release requirements for the hardware.
Table 1 Supported Hardware Modules and Minimum Software Requirements
| 1The T1/E1 IMA port adapters also require carrier module FPGA image version 1.8 or later, and IMA port adapter functional image version 3.2 or later. |
Table 2 Catalyst 8540 CSR Interface Modules and Minimum Software Required
To determine the version of Cisco IOS software currently running on the Catalyst 8540, log into the switch and use the show version privileged EXEC command. The following sample output is from the show version command. The version number is indicated on the second line as shown below:
Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
Most of the port adapters and interface modules supported on the Catalyst 8540 have upgradeable FPGA and functional images. The FPGA and functional images include caveat fixes, but in most cases, it is not necessary to upgrade. The release notes that describe the caveats from the FPGA and functional images are available on the World Wide Web at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/l3sw/8540/rel_12_0/w5_6f/rel_note/fpga_rn/index.htm
For information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8540)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide.
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 3 lists the Cisco IOS software feature sets available for the Catalyst 8540 MSR. Table 4 and Table 5 lists the Cisco IOS software feature sets available for theCatalyst 8540 CSR.
Table 3 Feature Sets Supported by the Catalyst 8540 MSR
| 1SNMP = Simple Network Management Protocol
2PPP = Point-to-Point Protocol 3SLIP = Serial Line Internet Protocol 4IP = Internet Protocol 5NTP = Network Time Protocol 6TACACS+ = Terminal Access Controller Access Control System Plus 7VCCs = virtual channel connections 8VPCs = virtual path connections 9UNI = User-Network Interface 10ILMI = Integrated Local Management Interface 11IISP = Interim-Interswitch Signaling Protocol 12LANE = LAN Emulation 13LEC = LAN Emulation Client 14LES = LAN Emulation Server 15BUS = broadcast and unknown server 16LECS = LAN Emulation Configuration Server 17ARP = Address Resolution Protocol 18OAM = Operation, Administration, and Maintenance 19RMON = Remote Monitoring 20CBR = constant bit rate 21MCR = minimum cell rate 22ABR = available bit rate 23MIB = Management Information Base 24UBR = unspecified bit rate |
Table 4 Feature Sets Supported by the Catalyst 8540 CSR
| 1Route processor redundancy for the Catalyst 8540 CSR |
Table 5 Feature Sets Supported by the Catalyst 8540 CSR
| 1Route processor redundancy for the Catalyst 8540 CSR |
Table 6 lists the release names, versions, and part numbers used with the Catalyst 8540 MSR. Table 7 lists the release names, versions, and part numbers used with the Catalyst 8540 CSR.
Table 6 Release Name to Version and Part Number Matrix for Catalyst 8540 MSR
| Release Name | Release Version | Part Number |
|---|---|---|
Table 7 Release Name to Version and Part Number Matrix for Catalyst 8540 CSR
| Release Name | Release Version | Part Number |
|---|---|---|
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.0. The new features are sorted by release number. Some releases include both platforms, others only include one platform.
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(22)W5(25).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(22)W5(25).
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(20)W5(24b).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(20)W5(24b).
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(20)W5(24a).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(20)W5(24a).
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(20)W5(24).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(20)W5(24).
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(19)W5(23).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(19)W5(23).
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(18)W5(22).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(18)W5(22).
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(16)W5(21).
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(16)W5(21).
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19c):
See the "Related Documentation" section for a list of documents that describe these features.
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19c):
See the "Related Documentation" section for a list of documents that describe these features.
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(10)W5(18c):
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(7)W5(15c):
See the "Related Documentation" section for a list of documents that describe these features.
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(5)W5(13b):
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(4a)W5(11a):
|
Note For additional caveats that apply to this feature, refer to the Release Notes for the Catalyst 8500 Campus Switch Router, Cisco IOS Release 12.0. See the "Open Caveats" and "Caveats Corrected" sections for Release 12.0(4a)W5(11a). |
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(4a)WX5(11a):
See the "Related Documentation" section for a list of documents that describe these features.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(9):
See the "Related Documentation" section for a list of documents that describe these features.
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(7b):
See the "Related Documentation" section for a list of documents that describe these features.
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(1a)W5(6f).
This section lists the caveats and corrected caveats for each release. Use Table 8 to determine the status of a particular caveat and its relevancy to your software release for the Catalyst 8540 MSR switch router. Use Table 9 to determine the status of a particular caveat and its relevancy to your software release for the Catalyst 8540 CSR switch router. In the tables, "C" indicates a corrected caveat, and "O" indicates an open caveat.
Table 8 Caveat Matrix for the Catalyst 8540 MSR
| DDTS Number | 12.0 (22) W5 (25) |
12.0 (20) W5 (24b) |
12.0 (20) W5 (24a) |
12.0 (20) W5 (24) |
12.0 (19) W5 (23) |
12.0 (18) W5 (22) |
12.0 (16) W5 (21) |
12.0 (13) W5 (19c) |
12.0 (10) W5 (18c) |
12.0 (7) W5 (15c) |
12.0 (4a) W5 (11a) |
12.0 (1a) W5 (9) |
12.0 (1a) W5( 7b) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Table 9 Caveat Matrix for Catalyst 8540 CSR
| DDTS # | 12.0 (22) W5 (25) |
12.0 (20) W5 (24b) |
12.0 (20) W5 (24a) |
12.0 (20) W5 (24) |
12.0 (19) W5 (23) |
12.0 (18) W5 (22) |
12.0 (16) W5 (21) |
12.0 (13) W5 (19c) |
12.0 (10) W5 (18c) |
12.0 (10) W5 (18b) |
12.0 (5) W5 (13d) |
12.0 (5) W5 (13b) |
12.0 (5) W5 (13) |
12.0 (4a) WX5 (11a) |
12.0 (1a) W5 (6f) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This section contains listings of the caveats for the Cisco IOS software:
Symptom: When you delete well-known VCs using the atm manual-well-known-vc delete command on a snooped interface and then execute a show snoop-vc command, the switch reloads.
Symptom: On the Catalyst 8540, Catalyst 8510 MSRs, and LightStream 1010 switches, Frame Relay traffic stops flowing through previously configured PVCs when you reload the image or reboot the switch. However, the VC appears up.
Symptom: You should not configure a structured CES circuit with more than 19 timeslots across a T1 ATM interface on a Catalyst 8540 MSR. While the circuit can be configured with more than 19 timeslots and will be built over the T1 ATM interface, the Catalyst 8540 MSR will discard cells on the configured VC causing errors on the emulated circuit.
With 20 timeslots configured you see cells queued and dropped (CLP0 Q full drop) on the PVC. This problem occurs with both hard and soft PVCs are configured over the T1 atm interface.
To detect the problem, use the show atm vc int atm card/subcard/port vpi vci command and confirm the Clp0 q full drops field is increasing.
Workaround: Configure the structured CES circuit to only use 19 or fewer timeslots.
Symptom: Many PHY parity errors might appear on your switch from traffic through the OC-12 line module which causes PHY Parity Error interrupts. This could cause high CPU utilization (approximately 90percent) during a route processor switchover. This problem is caused by the PHY Parity Check bit in the SMR register being set to "1"(enabled) on a route processor switchover. The SMR register is set from 0x0 to 0xF during switchover, thereby enabling the PHY Parity Check bit. This default value of this register should be 0x0 (PHY Parity Check disabled).
Symptom: After you perform an OIR or a switch reload, the counter from show atm interfaces atm command displays an incorrect output rate value.
Symptom: When a port on a Catalyst 8540 CSR is configured as a snoop (monitor) port, the traffic on the snoop port becomes corrupted. Sniffing the same traffic on the attached Catalyst switch shows that the traffic itself is not corrupted. The problem occurs because the snoop port does not give reliable information to the monitoring station attached to that port.
Symptom: An error can occur with management protocol processing.
Workaround: Use the following URL for further information: http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
Symptom: Multicast packets of some specific lengths (121 bytes to 240 bytes) cause a portstuck condition on the ATM router module interfaces.
Symptom: The IRB connection has no connectivity in a native VLAN across ISL/dot1q Gigabit Etherchannel in the same bridge-group. However, there is connectivity on other VLANs.
Workaround: Configure a dummy VLAN as a native VLAN on the dot1q trunk.
Symptom: If you use the no negotiation auto command in interface configuration mode on a 2-port Enhanced Gigabit Ethernet interface module with GMAC-D2 (hw-version 6.0 onwards), any packets larger than 1518 bytes or less than 64 bytes are filtered by the GMAC (Gigabit Ethernet Media Access Controller).
Workaround: Reload the particular interface using the epc portstuck-manual-reload interface card/subcard/port command.
Symptom: If you configure VC-snooping on a sub-interface, then delete the subinterface, then recreate it, and if you then use the no atm snoop command to disable snooping on the same subinterface, the switch crashes.
Symptom: The console might hang if you use the hw-module subslot x/y reset command on the Frame Relay E1 port adapter.
Workaround: Shutdown all the controllers in the port adapter before issuing the hw-module subslot x/y reset command.
Symptom: Unusual delays occur in Frame Relay VC counter updates on Frame Relay ATM interface modules.
Symptom: A LightStream 1010 running 12.0(19)W5(23) showed the following alignment error:
Symptom: A high number of cells stuck in the memory buffer causes the CPU to miss the periodic poll of a certain module or interface, leading to a port stuck message. Occurrences are random and there is no predetermined sequence of events that causes this to happen.
Symptom: You might see a Bus Error exception at get_slot_ptr while trying to do the continuous snmpwalk on the ciscoLS1010SubModuleGroup object of CISCO-RHINO-MIB and simultaneously toggling the redundant power-supply after at least one route processor switchover.
Symptom: For Frame Relay terminating PVCs on Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 switches, effective "Inverse ARP Frequency" value will be 60,000 times greater than the actual intended value.
Symptom: Shaping is not available for outgoing signalling VC on the Catalyst 8540 MSR switch.
Symptom: A Catalyst 8510 CSR might produce power supply error messages when writing to the bootflash:
Symptom: Once the route processor switches over, the following error message is seen on the new Primary route processor if you have a Gigabit processor interface module installed:
Enter the show diag online access command to get more details about the failure.
Symptom: A Catalyst 8500 switch rejects SVC video calls. After first video call is built, all other video calls are rejected, and a message similar to the following is generated when a debug atm sig-all atm x/y/z command is entered:
Workaround: Upgrade the 8500 switches to Cisco IOS Release 12.1(7a)EY.
Symptom: A crash occurs while configuring Bridge Group Virtual Interface (BVI)/Enhanced Interior Gateway Routing Protocol (EIGRP), or while powering off the redundant power supply.
Symptom: When running Cisco IOS Release 12.0(18)W5(22) on a Catalyst 8540 MSR, or on a LightStream 1010, interoperability problems occur when peers run an older IOS version, and tunnels and SVC/Soft VCs are used.
Workaround: Upgrade all switches to the most current IOS release.
Symptom: When a Catalyst 8540 MSR system has a large number of inverse multiplexing over ATM (IMA) port adapter modules, a message similar to the following is generated:
Symptom: A forced crash occurs.
Symptom: A Catalyst 8540 MSR and Catalyst 8510 MSR connected via 8-port inverse multiplexing over ATM (IMA) port adapter modules change clocking configuration after the T1 interfaces bounce, resulting in a loss of synchronous clocking over the T1 IMA links. If synchronous clocking is required for circuit emulation service (CES), the CES circuit might report overruns or underruns.
Workaround: The Catalyst 8540 MSR and Catalyst 8510 MSR can be reloaded to return the clocking configuration to the original values. The T1 interfaces can be removed from the IMA group, and then can be added back and bounced. The txtiming values under the show controllers will change back to 0x2 and synchronous clocking is restored.
Symptom: A Catalyst 8540 CSR logs the following messages:
However, no connectivity problem is reported.
Symptom: The following error message does not specify which CAM/port adapter needs to be removed or reseated.
Symptom: The Management Information Base (MIB) object "ifAdminStatus" shows "UP" for an ADMIN DOWN E1 Controller after a reload or a route processor switchover.
Workaround: Enter the no shutdown/shutdown command sequence on the controller.
Symptom: When Frame Relay ATM Soft-VC is set up in Frame Relay/ATM Network Interworking (FRF.5), the usage parameter control (UPC) on the passive side always sets to PASS, irrespective of the setting on the serial interface that is set by entering the frame-relay upc-intent tag-drop command. The default is PASS; when this is changed to tag-drop, the configuration does not reflect the change, and entering the show vc int serial command always shows the UPC intent as PASS.
Symptom: When the shutdown/no shutdown command sequence is entered for a port in a CES card, a burst of bit errors can be observed on the circuit on some other port of the same port adapter.
Symptom: On the Catalyst 8540 MSR and LightStream 1010 platforms, the option to set loop timing on OC-12 ports is not available.
Symptom: Not all of the contents of the atmVcCrossConnectTable can be seen after the removal and re-insertion of a module. The message:
is seen on the console during some SNMP get operations.
Symptom: When an E1 IMA (inverse multiplexing over ATM) adapter is inserted into a chassis in which several other IMA adapters have already been added, the clock cannot be derived from the network.
Symptom: Some point-to-multipoint crossconnnect entries are missing from the atmVcCrossConnectTable when the point-to-multipoint root if-index is higher than the if-index of the leaves.
Symptom: Interfaces with Tag enabled get stuck in the TDP not ready state.
Workaround: None. The only way to bring up the Tag on such interfaces is via system reload.
Symptom: During TagVC installation, if the switch driver returns an error, the Connection Manager leaves the TagVC in the wrong FSM state. This can lead to TVCs existing on an interface when there are no tag bindings.
Workaround: None; reload the switch to clear such unused TVCs.
Symptom: When running Cisco IOS Release 12.0(13)W05(19), a bus error causes the system to restart. This occurs when an 8-port Gigabit Ethernet card with control traffic is at or near its traffic capacity.
Symptom: The SNMP TRAP object ccrCpuStatusChange returns an invalid value.
Symptom: A Catalyst 8510 reloads by bus error.
Symptom: When a Catalyst 8540 with a network clock module is connected to an external clock supply, changing the clock supply from BITS 0 to system causes the system to crash.
Symptom: After reloading core switches, all neighboring switches running 12.0(16)W6(21) and 12.0(16)W6(21a) crash and a message similar to the following is generated:
Symptom: A port of a 4-port DS3 port adaptor for LS1010s and 8540s is in a yellow or red alarm state, and stops sending DS3 framing for a brief time when the alarm is cleared from the interface and the interface transitions to an up/up state. The loss of frame (LOF) can be seen when the Acterna tool TBERD is connected to the TX port of the DS3 port.
Symptom: When using Cisco IOS Release 12.0(16)W5.21, a system crash with a bus error at imapam_mmcport_init occurs after the creation of the 131st interface.
Workaround: Remove any unused modules from the chassis so that additional virtual interfaces can be created.
Symptom: 4-path load balancing is missing for Ethernet processor interfaces.
Symptom: On a Catalyst 8540 MSR, use of the OIR online diagnostic disables the E1 interface after reloading.
Symptom: After an online insertion and removal (OIR) of a carrier module in the 8540 MSR, the input/output packet counters for the corresponding interfaces show incorrect values.
Workaround: Do not perform OIRs, or clear the counters on that interface.
Symptom: The command line interface (CLI) no negotiation auto command is not preserved in the running configuration after an OIR (or "hot swap") of an 8-port Gigabit Ethernet card.
Workaround: Configure the CLI no negotiation auto command again.
Symptom: The spanning tree protocol of a bridge-group cannot be changed.
Workaround: Deconfigure the bridge-group and then reconfigure it with a different spanning tree protocol.
Symptom: When a user specifies a Soft PVP Configured as VBR-NRT Service category in the ingress port, the service category at the egress interface of that switch is seen as UBR rather that VBR_NRT.
Symptom: A Catalyst 85xx running Cisco IOS Release 12.0(13)W5(19c) experiences high multiservice route processor utilization when Internetwork Packet Exchange (IPX) networks are added to Bridge Group Virtual Interface (BVI) interfaces; as more IPX networks are added, multiservice route processor utilization increases.
Workaround: If configuring bridging over ATM router module subinterfaces, configure a map-list for the bridged virtual circuit, using the keyword "bridge".
Symptom: FR-PVCs configurations might fail after a route processor switchover.
Workaround: Reload the switch router.
Symptom: On ATM switches, the loopback IP address is not exchanged during ILMI negotiation with the neighboring switches. Consequently, the output of the show atm ilmi-status command indicates 0.0.0.0 as the peer IP address, even though a loopback address is configured.
Workaround: Configure the IP address on an Ethernet interface.
Symptom: A Catalyst 8540 CSR with an 8-port Gigabit Ethernet module forwards duplicate broadcasts when bridging is configured on a trunk.
Symptom: When running cell-mode MPLS on a network of switch routers with redundant paths, conversion to MPLS after a routing change might take up to 4.5 minutes. OSPS converges normally.
Symptom: An ARM interface might not bridge between ATM and the native VLAN.
Workaround: Configure some other non-functional VLAN as native.
Symptom: On a Catalyst 8540 performing an ATM-Frame Relay internetworking function, the ATM-Frame Relay does not propagate when the Local Management Interface (LMI) indicates a permanent virtual connection (PVC) as inactive.
Symptom: The no ip route-cache cef command might disappear from the running configuration of the BVI interface after reloading the switch router.
Symptom: The entry for atmSoftPVccRetryThreshold feature has an incorrect default value of 0, rather than the default value of 1 that is shown in the ATM Soft PVC Management Information Base (MIB). A value of zero indicates that an infinite number of call attempts are required to increment the atmSoftPvcCallFailures object and thus disables alarms for the Soft PVCC.
Workaround: Set the atmSoftPVccRetryThreshold value to 1.
Symptom: There is a noise problem with the CES PAM hardware version one.
Symptom: When slot 0 is configured as the ARP client, the client might release the SVC within one minute of a ping.
Workaround: Use the subinterfaces of slot 0 as the ARP client instead.
Symptom: The Internetwork Packet Exchange (IPX) statistics sometimes fluctuate when no traffic is flowing through the interface. The only affected functionality is IPX statistics.
Symptom: When video traffic is switched through an 8-port Gigabit Ethernet module in a Catalyst 8540 router, a high amount of jitter is seen.
Symptom: Sending a crafted control NTP packet might cause a buffer overflow.
Workaround: Include the "ntp access-group serve-only" line in the configuration of the router.
Symptom: Under a heavy load the switch router might misorder cells going out OC12 port adapter modules.
Workaround: Use the four-port OC12 modules designed for the Catalyst 8540.
Symptom: When the routing table exceeds 50,000 entries and one or more eight-port Gigabit Ethernet interface modules are installed in the switch router, the CAM full condition might be seen. This condition will cause ports to stick.
Workaround: Perform an OIR of the module. The eight-port Gigabit Ethernet interface module is not designed to handle more than 50,000 entries.
Symptom: The SNMP polling of the MIB object atmVplOperstatus (in Virtual Path MIB) for VP tunnels shows that the VPL is DOWN, even when the tunnel is UP (as shown by the CLI).
Symptom: In bridging, the aging time of ethernet process interfaces is always set 300 seconds, despite what it is configured for.
Symptom: Even after enabling SNMP, the switch router might not be able to perform SNMP walk.
Symptom: The one-Port OC12 port adapter module might cause cell corruption. This will inevitably lead to packet corruption wherever segmentation and reassembly is performed to put the cells back into frames.
Symptom: When a static route is added to and deleted from an interface that already has a static route connected to it, the packets are process-switched.
Workaround: Enter the clear ip route command.
Symptom: On PVCs on a VP tunnel, attempts to configure usage parameter control (UPC) values other than "pass" might not succeed.
Workaround: Do not define the VP tunnel, just configure PVCs on the VPI.
Symptom: Online Diagnostic Snake tests might send ILMI traps when an interface becomes active. This can cause clients on other inter-faces to reset ILMI.
Workaround: Disable the snake test by entering the no diagnostics online snake command in global configuration mode.
Symptom: Cell memory might get stuck when ABR, IMA, and hierarchical VPs are combined.
Workaround: Enter the shutdown command on the IMA interface. Take the first link on the IMA interface out of IMA group. Enter the no shutdown command followed by the shutdown command on the interface. Enter the no shutdown command on the IMA interface.
Symptom: ifTable Indexes might not match MIB-II table indexes.
Symptom: If a switch processor switch over occurs, the IMA interface will remain in a waiting state. After this, entering the shutdown command and then the no shutdown command on the IMA interface will bring it to the "going down" state.
Workaround: To avoid this issue, disable online diagnostics before a switch processor switch over.
Symptom: If a route processor switch over is done continuously more than two times by entering the redundancy force-failover main-cpu command or once entering the EHSA null_ptr command, the new primary route processor will issue the following error message continuously:
Workaround: An online insertion and removal of the FR port adapter will stop this error message.
Symptom: The switch router might crash when being polled by SNMP.
Symptom: When using PNNI, another vendor's equipment might send an invalid PTSE update. If the switch router receives one of these invalid updates, the PNNI neighborship might not re-establish.
Symptom: After resetting an E1 device connected to the CES port there might not be connectivity about Layer one.
Workaround: Enter the shutdown command followed by the no shutdown command on the CBR interface.
Symptom: Two adjacent ATM devices had problems with ILMI negotiation. The result of the ILMI negotiation is VPI/VCI range failure.
Symptom: An ARM port configured for transparent bridging and in blocking state might forward certain frames.
Workaround: Depending on the topology, the work-around might be to ensure that a non-ARM port is in blocking state. Where this is not feasible, you need to physically shutdown the ARM port that is in the blocking state.
Symptom: A switch router might show additional atm interfaces than the number of interfaces present in the chassis. This does not affect functionality.
Symptom: SVC signalling across a VP tunnel might not work after a reload.
Symptom: On the OC-3c port adapter module, ILMI might remain in the "waitdevtype" state after a redundancy fail over.
Workaround: If the problem is seen on port 1-3, bring up port 0. If the problem is seen on port 5-7, bring up port 4. If the problem is seen on port 9-11, bring up port 8. If the problem is seen on port 14-15, bring up port 12. The port can be brought up by connecting a loopback cable, or just by using that port.
Symptom: A switch router with OC3 port adapters and five Fast Ethernet interface modules might boot up with the following error message:
Symptom: When a switch router sends a tag distribution protocol (TDP) bind request and does not receive an answer, the TVC remains unconnected. This might cause scalability problems in large networks because over time these TVCs might use up a large number of resources.
Workaround: Add a timer to clean up the VCs.
Symptom: Switch routers running Cisco IOS Release 12.0(13)W5(19) or earlier might experience a memory leak when used with an NMS (Network Management System) running SNMP whenever it accesses PNNI tables.
Workaround: Turn off NMS polling of PNNI tables and instead use the CLI or determining any PNNI information.
Symptom: Online Diagnostic might run in the background and then stop suddenly with the following error message:
Workaround: Enter the diagnostics online snake command in global configuration mode to restart the online diagnostics.
Symptom: ILMI might not properly learn the ip addresses of peer switches. After entering the show atm ilmi-status command, the interface of the peer switch is learned but its ip address is not.
Symptom: The ARM might set the CLP of all cells to one when bridging is configured over a PVC. This happens for cells being transmitted over the 1483 PVC only.
Symptom: The port stuck message might log to the system log.
Symptom: The ATM uplink module might not support map list entries for its own IP address.
Symptom: The telnet response over an ISL trunk might be very slow. This is because small ISL frames (under 94 bytes) are not padded, and some devices drop ISL frames that are smaller than 94 bytes.
Symptom: The switch router might stop switching some VCs and log error messages like the following:
Workaround: Reload the switch router.
Symptom: An ATM router module interface indicates outgoing packets when that interface is administratively down.
Workaround: None. This does not impact functionality.
Symptom: When there is a lot of signaling svc setup and teardown on an NNI tunnel, interface calls might fail with a vpi/vci collision.
Workaround: Use a regular interface (no tunnels).
Symptom: The switch router might lose traffic on its LANE/1483/1577 interfaces on an ARM. Frame interfaces (like Fast Ethernet) or non-lane interfaces on ARM (with configured PVCs) pass traffic without any problems.
Workaround: Perform an OIR on the ARM or reload the switch router.
Symptom: IP and IPX routing over BVI on an 8-port Gigabit Ethernet port or a port channel might fail when the 8-port Gigabit Ethernet interface is removed from the bridge group.
Symptom: Cell loss on PVC connections occurs when removing the active route processor.
Workaround: Entering the redundancy prepare-for-cpu-removal command might prevent any cell loss outage from affecting established PVCs.
Symptom: When using a 155-Mbps port adapter module, the show controller command output will list all port mediums as SM_IR_+.
Symptom: On a switch router performing the Frame Relay/ATM Network Internetworking function, when the Local Management Interface (LMI) indicates a PVC is inactive on an NNI interface, this information is not propagated by the Frame Relay/ATM software.
Symptom: A system running PNNI with Cisco IOS release 12.0(7)W5(15c) will reject an ATM call SETUP if the setup includes the 5a information element coded with associated signaling, explicitly the VPCI and any VCI.
If another ATM switch sends a setup that includes the 5a information element coded with the associated signalling, explicit VPCI and any VCI, the system will release the call with cause code 35: requested VPCI/VCI not available.
Call setups that include the 5a information element coded with the associated signalling, explicit VPCI, explicit VCI signalling, including those made by Cisco ATM switches are not affected by this problem.
This interoperability issue exists between Cisco ATM switches and other vendor's switches that do not explicitly request the VCI value in the call SETUP.
Symptom: The port stuck detection and recovery mechanism might not work if one of the channels of the ARM port gets stuck.
Symptom: Power-on diagnostics hang, and the IOS is unable to boot, when ARM, Fast Ethernet, and OC-12 modules are installed in the same chassis.
Symptom: IPX traceroute might skip the middle hop when the middle router is the Catalyst 8540 switch router.
Symptom: The RMON for the 8-port Gigabit Ethernet interface module might not work.
Symptom: When an OIR is performed on an ARM module, the HSRP configuration might get lost.
Symptom: The ATM User-Network Interface (UNI) does not include a cumulative round-trip time parameter in the ABR call setup. This situation might cause interoperability issues with different vendor products.
Symptom: The circuit emulation service (CES) address does not change when the switch router address is changed. When the global switch ATM address prefixes are added or deleted (via the atm address command), addresses registered for existing CES circuits are not changed.
Symptom: The show hardware detail command does not show the actual version of the FPGA for any of the daughter cards. This shows the version of the FPGA motherboard which is misleading.
Symptom: The atm arp-server nsap command is removed from the running configuration upon reloading the switch.
The copy startup-config running-config command will restore the original configuration.
Symptom: If you save the running configuration, you may see the following error:
This happens when you issue a write mem command or a copy running-config startup-config command. Issue a show file command to show the 127 entries of private configuration.
Workaround: Save the running configuration in a file, reload the router, and then issue a write mem command or copy running-config startup-config command.
Symptom: Although packets are being sent out from an ATM OC-12 interface module, the 5-minute output rate shown using the sh int atm command indicates 0 bits/sec output. This is not consistent with the output rate shown under the sh atm traffic command.
Symptom: A simultaneous encapsulation change on both sides of a link when the force-link up mode is used presents a 50 percent chance of bringing the line-protocol down. This problem does not happen when encapsulation change is done one side at a time. Problem is usually not seen when auto-negotiation is enabled.
Workaround: Issue a shutdown and no shutdown to bring the line protocol up.
Symptom: When the show atm interface traffic command is entered on a subinterface, the total number of cells that has passed might show incorrectly as zero.
Symptom: The Xconnect setup fails for unidirectional TVC if there is another one with different direction and same vpi/vci on particular interface of the Catalyst 8540 MSR. This can be seen only if VC merge is disabled.
Symptom: When the primary clock source is in the "unlockable" state, and the clock fails over to the secondary clock, the router never reverts to the primary clock source, even when the connection is clean and the clock source is present.
Symptom: The output of the command show epc if-entry is limited to 20 characters. This limits the command from showing specific port information when the module or slot combination causes the output to go beyond 20 characters. For example, when Gigabit Ethernet interfaces are installed in slot 10 or greater, the output is truncated.
Symptom: The present configuration does not work properly for frame reject (FRMR) and acknowledgement timeout messages. Occasionally a file transfer works normally, but most of the time it does not.
Symptom: Traffic pointing to an unknown route goes to the route processor even with ip unreachable disabled on the Gigabit interface input port. The traffic is dropped if the input port is an Ethernet interface port and ip unreachable is disabled.
Symptom: Ports get stuck on a Gigabit interface when booting with 12.1(1.6)W6(25) image. The same cards boot up fine with 12.1(1.6)W6(24).
Symptom: Crash after issuing a clear counters command in get_pif_no function.
Symptom: When the reset button is pushed, the switch router might not boot the main-image, and eventually goes into ROMMON.
Symptom: When HSRP is configured on the eight-port Gigabit Ethernet interface module, HSRP connectivity might be disrupted after a remote link failure is followed by a link restoration.
Workaround: Configure another HSRP group with a higher number and move the standby configuration to that group.
Symptom: The output errors counter is incorrect on Gigabit Ethernet show interface command. They have a high value 4xxxxxxxxx and a clear counter command does not change it back to 0. This value can increase or decrease over time.
Symptom: IP traffic is not sent over PVC if AAL5 MUX encapsulation is used on a point-to-point subinterface on the Catalyst 8540 MSR. If the deb atm errors command is enabled, the following error messages will appear:
Symptom: The route processor redundancy may fail if you have both PVC and bridging configured on the ARM sub-interface.
Symptom: The system is not completing a route processor failover. The secondary route processor (redundant), as it assumes function from a failover will display the following error message:
This does not affect operation of the system but will prevent the secondary route processor from booting successfully if the primary crashes.
Symptom: On an MSR switch router with enhanced Gigabit interface cards, the switch router crashes when loading a CSR image because of the CES card in the switch router.
Symptom: IPX load-balancing on IPX packets sourced from enhanced Gigabit Ethernet ports or sent out of ATM uplink ports will work only if IPX max-paths are set to 1 or an even value (i.e. 2, 4 or 6). An odd value of 3 or 5 can cause some of the IPX packets to not go out of the ATM uplink ports. This problem is seen only with SVCs over 1483 not PVCs with 1483.
Workaround: When IPX packets are sourced from enhanced Gigabit Ethernet ports, set the IPX maximum paths to 1, 2, 4 or 6. If there are an odd number of paths, change the administrative weight of one path so that there are always an even number of equal cost paths.
Symptom: The ATM router module (ARM) does not strip the Ethernet pad when switching data from Ethernet to ATM. This may occasionally lead to connectivity issues since some end-systems do not expect to see the pad.
Symptom: When an enhanced Gigabit Ethernet interface module sends out ISL packets with packet sizes 1531 to 1548, the output error counter on the egress port increases.
Symptom: The hierarchical VP tunnel configuration fails on a WAI-OC3-1S3M mixed mode port adapter module when it is in slot 0 subslot 1 of the C85MS-SCAM-2P carrier module. Slot 0 subslot 0 of the carrier module can either be empty or have another card in it, and hierarchical VP tunnel configuration will still fail. However, if the mixed mode pam is inserted in slot 0 subslot 0 of the carrier module, then the hierarchical VP tunnel can be configured.
Symptom: The switch router might be vulnerable to the successful prediction of TCP Initial Sequence Numbers. This vulnerability only applies to the security of TCP connections that originate or terminate on the affected Cisco device itself; it does not apply to TCP traffic forwarded through the affected device, in transit between two other hosts.
Workaround: Update to Cisco IOS Release 12.0(13)W5(19c).
Symptom: When IPX packets are sourced from fast Ethernet interface based ports and sent out of ATM uplink ports, IPX load balancing will work only if the IPX max-path is set to 2. A value greater than 2 can cause some of the IPX packets to not go out of ATM uplink ports. This problem is seen only with SVCs over 1483 not with PVCs over 1483. However, if all IPX traffic is sourced only from enhanced Gigabit interface ports then this problem is not seen. Six-path load balancing will work correctly.
Workaround: When IPX packets are sourced from fast Ethernet interface based ports, set IPX max-paths to less than or equal to 2.
Symptom: A bus error that occurs at PC 0x6014A9E0 causes the Catalyst 8540 MSR to crash. This occurs when the router is polled for ATM data via SNMP.
Symptom: When serial interfaces on a Frame Relay/ATM internetworking port adapter are oversubscribed, and significant data bursts occur simultaneously on multiple VCs on multiple serial interfaces, one serial interface might get stuck.
Workaround: Enter the hw-module slot/subslot command.
Symptom: The ifSpeed is reported as 100MB even when the auto-negotiation results in 10MBit.
Symptom: When the switch processor LED is red, cell loss occurs on insertion of standby switch processor.
Symptom: After replacing an ATM 155-Mbps multimode port adapter with an ATM 155-Mbps single-mode port adapter, the SNMP agent might not correctly refresh the AtmIftable: it still returns the old ciscoAtmIfPortType information for the new module. Stopping SNMP and then restarting the SNMP agent does not correctly refresh the table.
Workaround: Reload the switch router.
Symptom: The Gigabit Ethernet port on the eight-port Gigabit Ethernet interface module comes up as unshutdown after an OIR.
Symptom: Due to a hardware limitation, any packets larger than 6K could potentially cause a port stuck. After a port is stuck, the normal port stuck recovery mechanism applies.
Workaround: Configure a port-stuck reload.
Symptom: The output rate displayed in the show interfaces command on the POS interface can be artificially high at times.
Workaround: Issue the clear counters command or the shutdown and no shutdown commands.
Symptom: The default network over a POS link might not work when the outgoing interface is specified instead of the next hop interface.
Workaround: Specify the next hop interface.
Symptom: When a Catalyst 5500 connected to a Catalyst 8540 CSR is powered down, the BVI interface does not receive EIGRP and OSPF multicast hello packets.
Symptom: The system crashes when more than 80 VCs are configured on an ATM uplink port and the port is added to a bridge group. Avoid this configuration.
Symptom: The release message uses the wrong cause and diag information.
Symptom: clear atm vc option specifies VCDs from 1 to 4095 only. Therefore, any SVC with a VCD greater than 4095 cannot be cleared using this command.
Symptom: Enhanced Gigabit Ethernet ports learn MAC addresses of all zeros for packets with source MAC addresses with all zeros. This does not cause any problems.
Symptom: If you have more than 900 VCs on any interface or subinterface on the Gigabit Ethernet port with ATM uplink interface modules and you perform an online insertion and removal (OIR), a BROUTE VC release/setup failure will be indicated.
Symptom: The routing flag is not set and remains off after unconfiguring the bridge group on the system. This is only on ATM uplink ports.
Workaround: Issue the shutdown and no shutdown commands.
Symptom: When the network clock module quality is not accurate the NCDP will automatically disable. It is normal behavior of ncdp.
You can check the ncdp status with the following:
Symptom: When the ingress is a fast Ethernet interface, and the egress is an ATM uplink interface and is one of several parallel paths to a destination IPX network, shutting down this interface will cause the packets sent to this destination to use the first of the remaining parallel paths.
Workaround: The correct path will be chosen after issuing the clear ipx route* command.
Symptom: If HSRP over BVI is configured and a standby MAC address is explicitly configured on the BVI, this MAC address will not be reflected in the patricia table of the interface.
Workaround: None. The recommended option is to not use a standby MAC address and let the system choose the address.
Symptom: The two-port Gigabit Ethernet is part of a port channel, which has HSRP configured on it. Even after the two-port Gigabit Ethernet is removed from the port channel, the HSRP MAC address is retained.
Workaround: Issue the shutdown and no shutdown commands, add an IP address, or add the MAC address to a bridge group to delete the entry.
Symptom: A Catalyst 8540 with an ARM module, might take a software forced crash when attempting to establish EIGRP adjacencies.
Symptom: The ATM router module microcode for RFC1483 did not have the ability to understand CLNS topology updates forcing the card to drop packets. This also effected the IS-IS routing updates.
Workaround: Upgrade to the Cisco IOS release 12.0(11)W5(19).
Symptom: There is no support for SONET MIB objects in ATM uplink module.
Symptom: After issuing the shutdown and no shutdown commands on an interface that is part of a bridge group, sometimes the BCAST VC becomes zero.
Workaround: Issue the shutdown and no shutdown commands or remove the interface from the bridge group and add it back to restore the BCAST VC.
Symptom: Subinterfaces with the same VLAN color cannot be present in different bridge groups. This check is done when a bridge group configuration is being created or removed, not when the encapsulation is being changed.
Symptom: The router reloads when handling internetworking packet exchange (IPX) access-logging-messages. This situation may still occur if access-logging is not enabled.
You may exceed the 200 IPX network limit when the hardware is activated after being removed. When the hardware is reactivated, the interfaces that were not counted while the hardware was removed cause the limit to exceed.
Symptom: The message above might appear during bootup. The system recovers from this.
Symptom: The Gigabit Ethernet interface is part of a port channel; one of the port channel subinterfaces is a member of the bridge group. The BVI MAC address is retained on the interface even after it is removed from the bridge group.
Workaround: Issue the no mac-address command under the interface.
Symptom: The IP adjacencies are not being cleared from the Gigabit Ethernet card quickly enough.
Workaround: Upgrade to the Cisco IOS release 12.0(10)W5(18c) software or later.
Symptom: Option access-list under the show controllers command returns nothing when the interface is configured for bridge address access-list. Option mac under the show controllers command for the enhanced Gigabit interface port returns nothing when it finds a match in the Layer 2 database.
Symptom: MAC addresses are missing in the two-port Gigabit Ethernet port part of the bridge group when many MAC addresses are learned over the POS link and the POS link goes down.
Symptom: When auto negotiation is disabled on an enhanced two-port Gigabit Ethernet port, it is up even if the GBIC is not present.
Symptom: The CSR image recognizes the ATM router module and downloads the ATM router module uCode.
Symptom: The following message may appear when an incorrect signaling packet is transmitted by the peer device:
This may lead to memory corruption.
Symptom: Cannot create soft VC with 95% of PVP
The calculations for determining the limits of PCR and SCR that can be used for a VBR-NRT VC traversing through a VP tunnel using the CAC algorithm at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/wa5/12_0/3a_11//atm_tech/rm.htm#xtocid2419
This holds true for PVCs but not soft VCs.
Symptom: The alignment correction might occur with the clear bridge or show bridge commands with the ATM uplink. The system recovers from the alignment correction.
Symptom: The static bridge command might disappear from the running configuration.
Symptom: When the module is removed from the switch, the interfaces continue to show as inserted and also the IDB's are not deleted. The problem occurs with different kinds of modules in different slots.
This was noticed when a module is inserted into a slot and another is removed almost immediately. This is not seen when a good amount of time is given between the act of insertion and removal of the modules.
To prevent this, before inserting a new module into switch, wait 2 minutes after OIR.
Symptom: The ATM router module cannot remove interfaces bvi8 thru bvi11 and cannot unconfigure bridge groups 8 thru 11. This problem occurs with a configuration of 20-30 bridge groups. Some bridge groups which had BVIs enabled could not be unconfigured with the command line interface (in this case it was bridge groups 8 thru 11). The command for removing a particular BVI is not recognized, and the bridge-group could not be deleted.
This does not affect any bridging or routing functionality on the device. It is a configuration issue only.
Symptom: PIM: Watchdog timeout in pim_mps_idle_vc().
Symptom: The output of the show ethernet command might display a `lost carrier' count that is the same as that for the collision counter on that Ethernet interface. This is a counter error only, and does not actually indicate a lost carrier.
Symptom: Appletalk fails when bridged between an 8-port gig and 2-port Gigabit Ethernet card on the Catalyst 8540 MSR.
Workaround: Upgrade to IOS release 12.0(4a)W5(11a) or later.
Symptom: When two Catalyst 8540 CSRs with two-port Gigabit Ethernet interface modules are connected back-to-back, packets are lost. On one side the counters might show input and output increasing, but the other side shows only output packets increasing. The Address Resolution Protocol (ARP) from the other side is lost, and the ability to ping the other side is lost.
Symptom: On the ATM uplink any packet routed on a point-to-point interface will be routed by the route processor.
Workaround: Do not configure point-to-point subinterfaces on the ATM uplink.
Symptom: The above message might appear when changing the trunk encapsulation type of a Gigabit EtherChannel (GEC) from ISL to 802.1q, when GEC is configured for novell-ether encapsulation and ports are receiving IPX wire speed traffic. No functionality problems are observed.
Symptom: Due to a hardware limitation, any packets larger than 6K could potentially cause a port stuck. After a port is stuck, the normal port stuck recovery mechanism applies.
Symptom: When reloading a new image into the enhanced two-port Gigabit Ethernet interface module the ATM uplink enhanced Gigabit interface appears to have been reset. The enhanced two-port Gigabit Ethernet interface module download shows no effect on the ATM uplink.
Symptom: If the weighted-fair queueing is configured on an ATM IMA interface of a Catalyst 8540 MSR, the system may go into an infinite loop generating traceback messages.
Symptom: Notifications sent or received are only visible if the debug ip bgp command is configured. This might limit the ability to diagnose problems.
Symptom: When running Border Gateway Protocol (BGP), the BGP peers of the receiving border router might detect a mismatch in the code, and issue a notification message to reset their session. This does not affect the receiving border router.
Symptom: When reprogramming the switch processor(s) the Catalyst 8540 CSR might crash. No connections should be installed after reprogramming until the system reboot is complete. However, some interface modules create connections before the system reboot is complete so only the interface modules are recognized in the system crash.
Symptom: There is no instance of ACL card in the MIB table.
Symptom: In a switch equipped with circuit emulation service cards, the shutdown of a CBR interface does not affect the device connected to it.
Symptom: IP PIM Sparse-Mode using multipoint signaling over ATM can fail when the PNNI path is switched to the redundant link.
Workaround: Upgrade to Cisco IOS release 12.0(10)W5(18c) or later.
Symptom: Cannot set ifAdminStatus object on CES interfaces. Attempts to set ifAdminStatus result in the following:
Symptom: When more than one loopback interface needs to be configured, the interfaces are assigned the incorrect number, so they are all created as Loopback0. The interfaces cannot be removed.
Symptom: Under heavy multicast traffic, cells might stick in the switch fabric. This happens when a race condition occurs in the switch processor and the output VC (OVC) is not present in the active list or idle list. In this situation, the OVC is never taken up for further scheduling, and all the cells in the VC are stuck.
Workaround: Enter the clear ip multicast-routing command or enter the shutdown/no shutdown commands to the root interface.
Symptom: With an encapsulation change on a two-port Gigabit Ethernet interface module, the interface no longer sends packets. It seems that it is receiving packets and sending packets to the route processor when necessary, but the packets are not sent.
Symptom: When the switch router is reloaded, you must enter the shutdown command followed by the no shutdown command on the CBR ports in order to activate the CBR ports.
Symptom: Routed traffic does not pass through a port on the 8-port Gigabit Ethernet card when the port is in blocking mode for bridged traffic.
Symptom: When two 8540 CSR switch routers are directly connected by a two-port Gigabit Ethernet interface module, a reset of one switch router does not cause the remote switch router's interfaces to go down too. The problem is caused by the reset switch router's interfaces not going down, so remote interfaces do not go down.
Workaround: Physically remove the cable from the ports or issue the shutdown command.
Symptom: When running the Cisco IOS release 12.0(7)W5(14.74) software on a switch, it is possible that the atmVcCrossConnectAdminStatus entries will disappear.
Symptom: When the Catalyst 8540 CSR has both Protocol Independent Multicast (PIM) joins and IGMP joins coming in, one of the interfaces in the outgoing interface list of the IOS multicast table might not forward traffic. This is caused by a disconnect in the sequence of events between IOS multicast code and the Catalyst 8540 CSR specific light stream inter process communication subsystem (LSS) multicast code.
Workaround: Enter the clear ip multicast-routing command and configure static multicast groups on the interfaces sending PIM joins.
Symptom: After a route processor switchover, the microcode for a Fast Ethernet (FE) interface module might not download successfully. This failure occurs infrequently but causes the interfaces on the failed FE interface module to be unusable.
Workaround: Remove and reinsert the affected FE interface module.
Symptom: In some instances, an ATM interface on a Catalyst 8540 MSR may get stuck in a going down state.
Symptom: After a switch processor switchover, the microcode for an 8-port Gigabit Ethernet (GE) interface module might not download successfully. You will see the following error message:
This failure occurs infrequently but causes the interfaces on the failed 8-port GE interface module to be unusable.
Workaround: Enter an skmgmt reset command. When this command is entered, you might see BROUTE-VC SETUP FAILURE messages. These messages are harmless and can be ignored.
Symptom: When issuing the shutdown/no shutdown command on an ATM interface with a large number of VCs, the route processor utilization stays high for a long period of time. For example, for an 8K VC, the route processor stays high for around 720 seconds and for 4K VCs, it is around 300 seconds.
Symptom: Sometimes the above message is seen.
Symptom: On bootup, the following warning message may appear:
It has no affect on the switch.
Symptom: The switch router will crash and hang when the ip http server command is configured and a browser connects to http://<router-ip>/%%. This defect can be exploited to produce a denial of service (DoS) attack. This information has been announced on public Internet mailing lists which are widely read both by security professionals and by security "crackers," and should be considered public information.
Workaround: Disable the IP http server with the following command:
Alternatively, the administrator can block port 80 connections to the switch router via access lists or other firewall methods.
For further information, refer to the security advisory available at http://www.cisco.com/warp/public/707/advisory.html
Symptom: The values for ifInOctets wrap every 15 to 30 seconds on ATM interfaces with very little traffic. The wrapping occurs when the value is about 3,000,000 octets.
Symptom: The message above appears sometimes when an enhanced Gigabit Ethernet port is added or removed from a port channel (PO) with multicast enabled on the PO. This message is harmless and the system recovers from this.
Symptom: There may be spurious memory access in certain tag switching configuration. This does not affect any functionality.
Symptom: The prompt on the secondary route processor does not reflect the hostname of the switch router after a sync.
Symptom: The following CPU hog messages might occur after removing an IMA port adapter that has hundreds of SVCs and PVCs configured:
*Apr 21 10:36:42: %SYS-3-CPUHOG: Task ran for 2096 msec (114/0), process = OIR Handler, PC = 600AA8D8.
Symptom: When configuring region sizes you are not considering the ACL region size when checking for the total size. Configuration allows regions sizes exceeding total Tcam size. No error message is printed at the time of configuration but upon next boot you get the following error messages:
Symptom: The ip cef command does not re-enable the CEF switching on the Catalyst 8540 when previously disabled due to lack of memory. The Catalyst 8540 requires CEF switching but this can become disabled if there is insufficient memory available. When insufficient memory is available, the following message appears:
Symptom: Multicast statistics might show an incorrect kilobits per second (kbps) rate.
Symptom: After upgrading from Cisco IOS Release 12.0(5)W5(13) to Cisco IOS Release 12.0(5)W5(13b) code, CSR no longer boots. Restoring the older code corrects the problem. The crash occurs after the file is read. Removing the configuration text file from the TFTP server prevents the router from crashing. If the router is booted from the NVRAM configuration and the command copy tftp running then is issued, the router will crash. copy startup running does not crash the system.
Symptom: On a switch using the ospf area-range command, the summary link state advertisement created might get stuck in the database and not be flushed after the command is removed.
Symptom: XPIF modules are not supported.
Symptom: An ima_failure_trap might not be generated when an IMA group gets deleted and the group state change might not be sensed by the switch processor.
Symptom: When ports on the eight-port Gigabit Ethernet interface module are connected to Ethernet interfaces, you get frames with new MAC addresses. Because the ports on the 8-port Gigabit Ethernet interface module send ca-updates to the Cisco IOS, the show bridge command displays the learned MAC addresses. Although the 8-port Gigabit Ethernet interface module has incrementing SkIPC Rx failed counters, there is no side effect. The format of show skmgmt stats command has been modified to take care of this problem.
Symptom: When using framing mode STM-16, the show controllers command might report the framing mode as invalid. This should not impact the network.
Symptom: When the existing two-port Gigabit Ethernet interface module is replaced with the enhanced Gigabit Ethernet interface module by online insertion and removal (OIR), the running configuration that is part of the existing two-port Gigabit Ethernet interface module will not be available for the enhanced Gigabit Ethernet interface module.
Workaround: Save the configuration to NVRAM before doing an OIR of the two-port Gigabit Ethernet interface module with the enhanced Gigabit Ethernet interface module. Complete the OIR of all two-port Gigabit Ethernet interface modules with the enhanced Gigabit Ethernet interface modules. Enter the reload command to get the configurations of the two-port Gigabit Ethernet interface module for the enhanced Gigabit Ethernet interface module. The other option is to save the configuration to a TFTP server, edit the configuration so that only those relevant to the replaced two-port Gigabit Ethernet interface module is retained, and do a copy of this edited configuration to the running configuration.
Symptom: DS3 Frame Relay port adapter firmware stops forwarding traffic when 16 channel groups are oversubscribed. The egress port hangs when it receives a frame with a size that is an integral multiple of 48 bytes.
Symptom: The standby switch processor (SP) does not take over when an active SP fails to initialize during system bootup.
Symptom: The ATM route processor might not forward IP traffic to the default route.
Symptom: When the switch is rebooted, at the point when it is going down, the console is flushed with the following messages:
These messages have no effect on the switch.
show version command displays an extra ATM interface.
Symptoms: The number of ATM interfaces is displayed as one more than the actual hardware present in the system.
Symptom: A bus error exception might occur when adding parties to a root connection.
Symptom: If a peer system is reloaded after a route processor switchover, all traffic into the port might be dropped. This prevents well-known VCs from coming up.
Workaround: Enter the shutdown command. To restart the disabled interface, enter the no shutdown command.
Symptom: CBR soft VPs do not come up on route processor switchover.
Symptom: An IPX packet containing the wrong length in the IPX header and requiring an encapsulation change causes the ingress port to hang. The switch router must be reloaded.
Symptom: The show bridge command might not show all interfaces and the show bridge verbose command might not show all interfaces and hash entries. Entries are not displayed until they are "learned" when traffic is passed through them. If no traffic is ever passed, the entries will not be displayed.
Symptom: The Interim Local Management Interface (ILMI) status of shaped and hierarchical tunnel subinterfaces that are down (not shutdown) may remain in the restarting state after issuing a shutdown/no shutdown command sequence.
Workaround: Enter a shutdown/no shutdown command sequence on the main interface of the subinterface, or bring the interface up by connecting it to a peer system.
Symptom: Soft PVCs might be disabled on subinterfaces.
Symptom: When snooping is enabled on an ATM or ATM-P port, ATM PVC deletion might fail. If the deletion fails, the system does not recognize the ATM PVC deletion failure and deletes the Frame Relay PVC. This causes the ATM PVC and Frame Relay PVC to go out of sync.
Workaround: Before deleting the Frame Relay PVC, disable snooping on the ATM port.
Symptom: The show controller command does not display loopback configurations.
Symptom: When running 12.0 code with UNI 3.0, the Catalyst 8540 MSR may fail to send poll PDU's. This can result in a no_response_timer expiration and flapping of the sscop link.
Workaround: Configure UNI 3.1 on the link.
Symptom: A LightStream 1010 configured for MPLS (tag switching) and running the Cisco IOS 12.0(9) maintenance software release does not correctly increment counters on outgoing TVCs, although the data are being correctly sent out of the TVC.
Workaround: Upgrade to 12.0(4a)W5(11a) or higher.
Symptom: Operation, administration, and maintenance (OAM) pings might not work after a route processor switchover.
Symptom: Sometimes a MAC address learned over a port channel might not be removed from the IOS bridge table, but the entry might age out from the port channel. IPC might not be generated correctly to delete the MAC from IOS. This does not lead to incorrect routing of the packets as the packets are switched by the interface module and the table is consistent in the interface module.
Workaround: Issue the clear bridge group command.
Symptom: Under heavy traffic, if an encapsulation change (for a VLAN) is attempted on a 2-port Gigabit Ethernet interface module, the change might fail because of a microcode download failure.
Workaround: Shutdown the port (or port channel and all members of the port channel) when an encapsulation change is needed on Gigabit Ethernet ports or GEC. Make the encapsulation change, and then bring the port back up (no shutdown).
Symptom: When a snooping interface that is a higher card/subcard than the snooped interface (for example, interface ATM 0/1/1 snooping interface ATM 0/1/0), the snooping interface might be in an up state instead of in a snooping state. In addition, some of the snooping VCs might not be restored. When entering the shutdown command, the high-order snooping interface might get stuck while in the going down state.
Symptom: When OAM is enabled globally and ATM and IP traffic is in the switch, a crash might occur during route processor switchover.
Symptom: The ATM interface might show different line codes after a switch processor switchover.
Workaround: Use the show controller command to find the correct line code, which is listed under the line code violation (lcv) count.
Symptom: The above message might be seen with trunk interfaces configured in a bridge group with BVI after the clear bridge group or clear bridge command is issued. This is a transient state and the system recovers quickly.
Symptom: Packets coming in on a native VLAN being bridged to a port channel are dropped at the route processor. Untagged packets coming in on an 802.1Q trunk are associated with the native VLAN. Because of microcode limitations of the interface modules, the untagged packets are passed to the route processor to be routed or bridged. Consequently, we recommend that native VLANs not be used for network traffic and that they be limited to overhead traffic that terminates at the route processor (such as routing updates and CDP).
Workaround: Configure the traffic on a non-native VLAN.
The following traceback message appears:
%SK-7-ASSERT: Assertion Failure ... Cant find port channel idb ...
Symptom: Sometimes the above message appears when 8-port Gigabit Ethernet interfaces are added to port channels.
Symptom: A no loopback sonet-terminal command entered on an OC-48c interface does not bring the interface down even when no cable is connected to the port.
Workaround: Use the shutdown command to bring down the interface.
Symptom: When a port is temporarily stuck (such as egress starvation for a slightly extended period of time) there might be a memory leak. This happens very rarely when a port is temporarily stuck repeatedly.
Workaround: Schedule a reboot when the available memory goes down to a very low value. This caveat is fixed in Cisco IOS Release 12.0(5)W5(13b) and later releases.
Symptom: ATM signaling would not generate the connect ACK message and would result in conformance test failure.
Symptom: Under some very heavy stressful conditions with IP multicast, when the mcast fan-out expansion fails, the VCs do not release correctly.
Workaround: Stop the traffic and enter the clear ip mroute* command.
Symptom: The primary route processor might loop when a redundancy prepare-for-cpu-removal command is entered.
Symptom: Synchronous Digital Hierarchy (SDH) and other standard compliancy is not supported on the OC-48c. Also, LEDs and SONET/SDH alarm signals might not generate properly on the OC-48c. When using the show controller command on the OC-48c, counters might duplicate.
Symptom: Added code to display the SR3 and SR5 registers. No impact to functionality.
Workaround: The show controller counters command is enhanced in Cisco IOS Release 12.0(5)W5(13b) and later releases.
Symptom: If you are using IPX EIGRP, you might experience an inconsistency in SAP updates on a remote router if the serial interface is brought down for a brief time and then brought up.
Workaround: Enter the clear ip eigrp neighbors EXEC command or enter the no ipx linkup-request sap command for the serial interfaces.
Symptom: When unicast and multicast traffic is present on Fast Ethernet ports, the primary route processor might loop when a redundancy prepare-for-cpu-removal command is entered.
Symptom: The show atm status command might show the status of a previously looped back interface as up when it should be showing the status as up only after the line loopback is removed from the interface.
Symptom: Loopback cells might not pass across the 25-Mbps ATM port adapter modules.
Workaround: Configure the no atm oam intercept end-to-end command from global configuration mode.
Symptom: When IPX packets are sent to the system, and the system does cross encapsulation for IPX packets, it might lead to a stuck port situation if the IPX protocol length is wrong (or corrupt).
Workaround: Remove the interface module and reinstall it.
Symptom: A switch router with the Per-Class Queueing Feature Card (PCQ FC) might not count received cells per VC on transit VCs.
Symptom: IPX node address of BVI is sometimes made invalid after a long period of time.
Workaround: Enter the shutdown and no shutdown commands on the BVI interface to recover. The node entry is programmed properly back in the table.
Symptom: Online insertion and removal of the route processor, even after entering the prepare-for-cpu-removal command, sometimes hangs the system.
Workaround: Power cycle the system.
Symptom: Term length does not work for the show functional-image-info command.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: The display from a show switch fabric command scrolls without stopping when the screen fills. The output just continues to the end of the display.
Symptom: The switch router does not correctly handle extended QoS and end-to-end transit delay IEs. This occurs primarily when interoperating with third-party vendor equipment.
Symptom: When reprogramming a switch processor FPGA after a route processor switchover, the warning and the confirm prompts might not appear.
Symptom: The following error message might appear during switch processor FPGA reprogramming:
Symptom: Multiple tags for the default route might occur with VC merge.
Workaround: Do not use the tag-switching ip default-route command to assign tags to the default route.
Symptom: The input queue count on a BVI interface configured on the switch router might become larger than queue depth. This will block traffic from the same bridge group.
Workaround: Increase the hold queue on the BVI interface, depending on the rate at which the input queue fills up, or redesign the network to remove BVI.
Symptom: The switch router might crash after displaying the following message:
Symptom: When a port is stuck there is no debugging aid.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: When the system receives a lot of bad IPX packets, it sometimes produces a spurious memory access error. This does not impact functionality.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: With the eight-port Gigabit Ethernet interface module, spurious memory access occurs when booting the system with the latest image and copying the software configuration from a TFTP server.
Symptom: If interface snooping is configured, saved to NVRAM, and reloaded, the snooping VC might come up in a NO HW RES state.
Workaround: Use the shutdown command to bring down the interface.
Symptom: With the 8-port Gigabit Ethernet interface module, ping fails when changing the VLAN ID of a BVI interface.
Workaround: Take the subinterface out of the bridge group before changing the encapsulation. Then change the encapsulation and add the subinterface back to the bridge group.
Symptom: A VP associated code point is not supported between a Catalyst 8540 and a Vswitch on UNI 4.0/IISP interfaces.
Workaround: Use the atm signalling vpci command to configure the value of the VPCI that is carried in the signalling messages in the VP tunnel.
Symptom: The connected route associated with an Ethernet interface might not be in the routing table.
Workaround: Clear the routing entry or the Ethernet interface.
Symptom: When a port is stuck there is no debugging aid.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: Connected route associated with Ethernet interface might be intermittently missing from routing table.
Workaround: Clear the routing entry or the Ethernet interface.
Symptom: The image crashes when redundancy for the route processors is enabled.
Symptom: When the ipx down command is entered on an interface, the routing flag for IPX remains on.
Symptom: The switch can be configured to get its network clock from a constant bit rate (CBR) port without any clock being supplied to the port.
Symptom: New SVC or soft PVC calls from a Catalyst 8540 to a Fore ATM switch across a PNNI interface fail to connect. Connections initiated from the Fore switch do not fail.
Symptom: Under the heavy stress of a large volume of multicast traffic (6K [S,G] 1MB) the switch router crashes after failing to queue IPC messages.
Symptom: Counter values from the show controllers command are not descriptive enough for troubleshooting purposes. Each counter should have a label indicating the purpose of the counter.
Workaround: The output has been improved in Cisco IOS Release 12.0(5)W5(13b) and later releases.
Symptom: A mechanism is needed to troubleshoot and recover from port stuck failures.
Workaround: 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 up to three other ports in the case of Fast Ethernet 10/100 modules.
|
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. |
Use the following interface configuration commands to troubleshoot port stuck failures:
 |
Caution Due to the nature of 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, 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 at least at 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 should work very well. |
Symptom: On the Catalyst 8540, routing with BVI does not work on the 8-port Gigabit Ethernet subinterfaces with the following configuration:
Workaround: Reconfigure the dot1Q VLAN as non-native.
Symptom: Variable bit rate (VBR) might allow sustainable cell rate (SCR) oversubscription.
Symptom: A Catalyst 8540 might treat the link between the physical interface and the port channel interface as a multidrop link when the MAC address of the members of a port channel differs from the MAC address of the port channel itself.
Workaround: Delete the members of the port channel and then add them back in.
Symptom: The administrative status might be shown as up even when the controller is administratively down.
Symptom: Issue the shutdown and no shutdown commands for the new setting to take effect when you change the port speed from 10 to 100 seconds on a Catalyst 8540 CSR running 12.0(5)W5(13).
Symptom: FastEthernet interfaces that are in shutdown mode have packet output and bytes incrementing in the show interface command.
Workaround: Issue the clear counters command.
Symptom: Permanent virtual circuit (PVC) creation might fail if the virtual channel identifier (VCI) is greater than 24 bits. On a reload this error might happen when the VCI is greater than 12 bits.
Symptom: Some of the interface counters display a lower value for packet counters. Increasing the frequency of poll for statistics resolves the problem. This is needed only in two-port Gigabit Ethernet interface modules because of separate channels. This does not affect functionality.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or later.
Symptom: Cisco IOS Release 12.0(5)W5(13) and later releases boot only on route processors with hardware SAR.
Workaround: If you have a route processor with software SAR (that is, below version 5.4), you must upgrade your route processor to one with hardware SAR (version 5.6 or later). For route processor related issues, see the field notice at http://cco/warp/customer/770/fn5889_06291999.html.
Symptom: A MAC address that is learned as a REMOTE entry in the port channel members gets learned as a LOCAL entry after a host move.
Workaround: Issue the clear bridge bridge-id command.
Symptom: A host move under high traffic conditions can result in a missing MAC entry from the IOS bridging table. When routing over BVI, this might cause loss of connectivity.
Workaround: Issue the clear bridge command.
Symptom: When configuring a port channel, set the hold-queue size of the port channel to 300 and save it to NVRAM. On physical interfaces and port channels, the default hold-queue size is 75. The port channel hold-queue size should be 300. If the queue size of the port channel is not reset, there might be occasional packet drops bound to the route processor.
Symptom: These messages occur when there is IP multicast traffic and the user disables PIM on a physical interface and moves this physical interface to be a member of a port channel that is PIM enabled.
Workaround: Stop the IP multicast traffic, issue the clear ip mroute * command, and make the configuration change. If the assert messages occur, clear ip mroute * should fix the problem.
Symptom: When a member is removed from a bridge group which has HSRP over BVI configured and the router is an active router, active router MAC 0000.0c07.ac00 might not be removed from the interface.
Workaround: Issue the shutdown and no shutdown commands.
Symptom: A Simple Network Management Protocol (SNMP) walk of the ATM virtual channel cross connect table (CCT) might incorrectly show the following for a manually created cross connect:
Symptom: On a 8540 MSR running 12.0(4a)W5(11a) that the following entries may appear in the log:
The entries may appear when doing a SNMP get command. This may sometimes cause the active RP to crash and failover to the Standby RP (if available).
Workaround: Upgrade to Cisco IOS release 12.0(10)W5(18c) or later.
Symptom: Inverse multiplexing over ATM (IMA) groups might intermittently fail to come up, especially after reload and on E1 links.
Workaround: Enter the following command on the IMA interfaces:
If the group remains down even after issuing this command, this indicates a persisting alarm on the line.
Symptom: This problem is seen very infrequently when a large configuration is copied to the running configuration under heavy traffic loads.
Workaround: Issue the clear bridge command.
Symptom: For 10/100 Fast Ethernet interface modules, the internal chip set is designed to give higher priority to ingress tasks than egress tasks because of limited buffer availability on the ingress side. This design leads to a situation of egress starvation under heavy input traffic conditions when continuously scheduled ingress tasks cannot meet the 84-cycles budget requirement under "Auto L2-learning" conditions.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: When hundreds of TVCs in bidirectional mode are repeatedly configured and unconfigured on a switch router, VC resources might become exhausted.
Symptom: If any bridge-group members are 802.1q subinterfaces on an eight-port Gigabit Ethernet interface module, then protocol specific IRB configuration will not work over these ports because of local-switching ASIC (K1) chip limitations.
Symptom: The packet statistics displayed by the show epc ipmcast command sometimes report an incorrect value. This does not impact any functionality.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: PNNI/ILMI VCs are sending out CLP=1 traffic.
Symptom: When configuring the Simple Network Management Protocol (SNMP) trap receiver with the snmp-server host command, the following error message might appear on the console of the switch:
Workaround: This error message occurs only when SNMP is initially configured on the switch and it is the first time that the snmp-server host command is entered. If the command is entered again the error message does not appear.
Symptom: PVC and VC status might not be updated in the Frame Relay end of a connection.
Symptom: When the tag switching is configured while the switch is rebooting, the following warning message displays:
Symptom: The facility alarm issues a warning when the secondary route processor is brought down, but the warning goes away if the secondary route processor is initialized at ROMMON without booting.
Symptom: After booting the image, the switch router might display the following error messages and continue looping:
Symptom: The root cause of this is that the HSRP specific structures are not properly updated when an interface goes down or when a card is removed.
Workaround: Remove HSRP from the configuration before removing the card.
Symptom: When E1 Frame Relay ports are coming online the following message might be displayed:
This message is harmless and does not affect the functioning of the switch router.
Symptom: When the color of an encapsulation is changed on a subinterface, the subinterface does not transition through the spanning tree states. In some situations this might result in spanning tree loops.
Workaround: To prevent looping when changing the subinterface color, delete the subinterface and recreate it with the new encapsulation color.
Symptom: When several IP/IPX ACLs are configured on Ethernet interfaces, a switchover might cause the primary CPU to crash.
Symptoms: The following error messages might appear on the Gigabit Ethernet interface module with the ACL daughter card during a route processor switchover.
Workaround: OIR the interface module.
Symptom: On Fast Ethernet ports, untagged packets coming in on the 802.1q native VLAN are not processed by the microcode. Instead, they are transmitted to the route processor and processed. This means that high route processor utilization will be seen if untagged packets are received at a high rate on the native VLAN subinterfaces.
Generally, only management data, transmitted at a very low rate, would be seen on the native VLAN, since it is mainly used for network management purposes.
Symptom: A Catalyst 8540 might have problems with IPX routing using ATM router module ports. Once the LE-ARP entry times out, IPX packets are sent over the BUS. Since the route processor is not aware of the IPX packets anymore, it does not trigger the LE-ARP request and the switch router continues to forward the IPX traffic for the given destination over the BUS. This problem negatively impacts IPX performance. IP performance is not affected.
Workaround: Set the atm idle-timeout command to 0 on all the devices in the affected ELAN before the traffic is started, or move the LES/BUS to a Catalyst 5000 ATM LANE module.
Symptom: HSRP interface tracking may incorrectly determine that a down interface is up when the software reloads.
Workaround: Enter the shutdown/no shutdown commands on the interface.
Symptom: The interface command arp timeout 300 disappears from the running configuration after a reboot.
Symptom: If a switch processor switchover is initiated from a console port, some commands might still be able to be entered from a connection through a telnet or a vty session.
Workaround: Wait until the switchover is complete before issuing any commands from a vty port.
Symptom: The arp timeout interface command disappears from the running configuration after a reboot.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: The following message is sometimes seen:
Workaround: None; this message is harmless.
Symptom: In large bridge group and bridge group member configurations exceeding supported limits, high route processor utilization from the Tbridge Monitor process might occur. System resumes normally.
Symptom: When multiple 802.1q subinterfaces are configured over interfaces belonging to the same slot of an 8-port Gigabit Ethernet interface module, the traffic will be locally switched (broadcasts, flooding, etc.) among those interfaces, and the front-panel subinterfaces are represented by a single subinterface in the back end. Therefore, it does not consistently represent the proper configuration of front-panel subinterfaces. Because of this, the front-panel port configuration might not always work, depending on the deployment scenario.
Workaround: Configure different encapsulations among the different subinterfaces in the same slot. This makes the Ethernet interfaces in the back end perform bridging and routing.
The above workaround applies only if the subinterfaces are used to perform different switching functions. Multiple subinterfaces with the same encapsulation in the same bridge group might be used to provide local switching capability for trunk ports and possibly routing over BVI.
Symptom: On reload after configuring a permanent virtual circuit (PVC), the PVC might be in the down state.
Workaround: Delete and re-install the PVC.
Symptom: The above messages sometimes appear upon online insertion and removal (OIR) of the route processor or switch processors and also of the 2-port Gigabit Ethernet or 10/100 Fast Ethernet interface modules. This message is harmless and the system should continue to function normally after the message.
Symptom: The redundancy prepare-for-cpu-removal command initiates a route processor switchover through a software forced crash. The forced crash causes the message buffer to flush and display to the console before initiating the switchover.
Symptom: It can take up to 3 minutes to sync up the running configuration to the secondary route processor upon inserting the secondary route processor. This is not a problem. The task is run as a background task and hence runs as a low priority task.
Symptom: The switch processor switchover might generate a route processor HOG message in the Exec process. Console input is blocked until the switchover is complete. The system resumes normally.
Symptom: In bridge group and bridge group member configurations exceeding supported limits, route processor HOGs from the Net Background process might appear. System resumes normally.
Symptom: In bridge group and bridge group member configurations exceeding supported limits, route processor HOG messages from the EPAM Card Manager process might appear. System resumes normally.
Symptom: Route processor redundancy requires a software interface descriptor block for the secondary route processor. If you use up all the interface descriptor blocks through subinterface creation before booting the secondary route processor, interface descriptor block creation failure occurs. Boot the secondary route processor before attempting to configure the maximum number of interface descriptor blocks.
Symptom: If a switch processor switchover occurs before K1 boots up, the switch router might hang or crash.
Symptom: After hot-swapping a fast Ethernet interface module, OSPF interfaces are not recognized.
Workaround: Configure a loopback interface before enabling OSPF, so that the IP address of the loopback will be selected as the OSPF router ID. This is the recommended design for OSPF configuration. To minimize the convergence time, use a software interface (which never goes down unless administratively shut down) as the router ID. This will also prevent OSPF restarts upon interface toggling.
Symptom: After a switch processor switchover, the input and output packet counters have invalid values.
Symptom: Ethernet interface modules reset during reinitialization after a switch processor switchover.
On a switch processor switchover, Ethernet interface modules behave as if a system reload occurred, and take the same amount of time to reinitialize as they do for a reload. Before the interface modules come up, and a switchover occurs, timeout messages are entered. This happens because the Ethernet ports are initialized through IPC, and halfway through the process the Ethernet interface modules are reset again by the switchover.
Symptom: With the following configuration:
The switch will bootup in enable mode.
If a CPU switch-over occurs, the switch will not preserve this configuration and will boot up in user mode.
Workaround: We recommend that the user enter enable password to enter enable mode after a CPU switch over.
Symptom: After hot-swapping a fast Ethernet interface module, OSPF routes are not propagated properly.
Workaround: Issue the shutdown and no shutdown commands on the appropriate interface.
Symptom: Do not hot swap an active switch processor (SP) module before putting it in standby mode.
If an SP module is currently active while the switch router is running IOS, and the module is removed from the chassis before making it a standby module, the connections might hang. This stops switch traffic after an SP switchover.
Workaround: Before removing an active SP module, make it the standby.
First determine whether the SP module to be removed is currently active using either of the following methods:
If the SP module is active, the active LED on the module is green.
If the SP module is standby, the standby LED on the module is green.
If the SP module is currently the standby, remove it without issuing any commands.
If the SP module is currently active, use the following EXEC command to designate the other two SP modules as the active switch processor modules:
redundancy prefered-switch-card-slots slot#1 slot#2
The range of the slot value is 5 through 7. This prepares the SP module to be removed as the standby module.
Once the prompt returns, ensure that the SP module is the standby by issuing the following command:
show preferred-switch-card-slots
The SP module should no longer be active, and can be safely removed.
The following example shows how to prepare the switch router to safely remove an active SP module from slot 5:
Switch# show preferred-switch-card-slotsThe currently preferred switch card slots are slot:6 and slot:7
The currently active switch card slots are slot:6 and slot:7
Symptom: OC-48c SONET is supported but SDH is not.
Symptom: If an OC-48c interface module is removed and reinserted on an active switch router when NCPD is enabled, and the clock source is set to the OC-48c interface, the ILMI state remains in waiting/restarting on the OC-48c interface.
Workaround: After the OC-48c interface module is reinserted, enter a shutdown command, followed by a no shutdown command on the affected OC-48c interface.
Symptom: CBR interfaces might incorrectly come up when configured as structured services, even though no cables are plugged into the ports. This problem might also occur when removing the configuration of the structured services.
Workaround: Remove and reinsert the CES port adapter.
Symptom: When the secondary route processor is brought to ROMMON and initialized in the rommon, the redundancy alarm is cleared in the primary route processor even though the secondary route processor is still down.
Symptom: Entering shutdown/no shutdown commands on an ATM router module interface, especially when it has several LANE clients configured, can cause the switch router to issue messages similar to the following:
This message indicates that an internal timeout occurred. The interface recovers and normal operations are not affected.
Symptom: Under heavy stress conditions with multicast PIM-DM, there can be a situation in which VC allocation failed messages appear. This is a high stress scenario, and it happens when all the VC resources are not freed properly.
Workaround: Stop the traffic for a short time (a few minutes), enter the clear ip mroute * command, and then restart the traffic. This caveat has been resolved by ensuring that the VC resources are cleaned up properly in Cisco IOS Release 12.0(5)W5(13b) and later releases.
Symptom: The show interfaces atm-sec0 command always displays zero counter values.
Symptom: The switch router might crash when logging messages to a buffer when the switch router is very active.
Symptom: If an IPX router goes down in a multiple-path topology, the Catalyst 8540 layer might get out of synchronization with the Layer 3 IPX routing table. A lower layer forwarding and switching anomaly might occur if the router first receives a "down" notification for a particular network from the same host that originally notified the router about that network, and then, shortly afterward, the router receives a good route to the network from another host.
Symptom: The switch router sends PIM v2 register messages when PIM v1 is configured.
Symptom: The secondary route processor incorrectly displays out-of-sequence messages even though the packets are resent and the sequence is recovered.
Symptom: If a Fast Ethernet interface module is installed on an active switch router, cells become stuck in the switch fabric when a route processor module is inserted into the chassis.
Workaround: Upgrade to Fast Ethernet FPGA 3.3 or later.
Symptom: Flash PC cards cannot be formatted on the secondary route processor.
Workaround: Format the Flash PC card on the primary route processor then move it to the secondary route processor.
Symptom: If an 8-port Gigabit Ethernet interface module is installed on the switch router, switch processor switchover is temporarily unsupported. After issuing a redundancy prefered-switch-card-slots command, the switch router displays the following message:
There is 8 Port Gigabit Ethernet PAM in the Chassis, SP switch over is temporary unsupported
Symptom: A Gigabit Ethernet interface indicates it is in the up state, even though there is no longer connectivity through this interface. Pinging a device through the Catalyst 8540 MSR times out. Pinging a device from the Catalyst 8540 MSR is successful.
The sh epc if-entry int gi 0/0/0 gi 3/0/1 command displays the following message:
The shutdown/no shutdown command sequence restores the connectivity.
Symptom: A Gigabit Ethernet interface displays its status as up, however, there is no connectivity through the interface. Pinging a device through the Catalyst 8540 CSR times out but pinging a device from the Catalyst 8540 CSR is successful.
Workaround: Issue the shutdown and no shutdown commands on the appropriate interface to restore connectivity.
Symptom: Ports on an eight-port Gigabit Ethernet interface module cannot be snooped or used to snoop other interfaces.
Workaround: Use a Gigabit Ethernet port from a two-port Gigabit Ethernet interface module to snoop.
Symptom: The switch router might crash with a bus error. The interfaces were not restored after the crash.
Symptom: In rare instances, a Catalyst 8510 CSR takes a software forced crash at a program counter value of 0x6004A4D64 when running Cisco IOS Release 12.0(1a)W5(6f). Because the conditions which trigger this crash are not currently known, it is strongly advised that the router be configured to write a core dump if such an instance happens.
Symptom: Even though the route processor capabilities do not match, the switch router still reports full redundancy when it boots up.
When the secondary route processor resources, such as the amount of DRAM, are equal to or greater than the primary route processor resources, the switch router is fully redundant. However, after a route processor switchover, if the new primary route processor resources are more than those of the new secondary route processor, a fully redundant switch router becomes conditionally redundant and the new primary route processor console displays a message such as the following:
00:03:14: %COUGAR_EHSA-4-FLASH_MISMATCH: Mismatch in BOOTFLASH SIMM size between Primary and Secondary ACPMs
Workaround: Ensure that both route processors on the switch router have the same resources.
Symptom: When copying a file to a Flash PC card on a secondary route processor, the switch router might return control to the user before the copy process is complete. If a reload is done before the image is completely copied, the file might be lost.
Workaround: Enter the dir sec-slotn: command to verify that the image is completely copied before reloading the switch router.
Symptom: IP multicast counters (S,G) might not be accurate.
The microcode maintains 16-bit packet counters for each (S,G) entry, which are polled every 10 seconds. If the input rate for the (S,G) entry is higher than 6.4K packets/second for a 10-second duration, the counters might overrun.
Symptom: On an OC-12 interface, the show controllers command might incorrectly show very large numbers of tx and rx counters.
Symptom: The show running-config command display contains a reference to the aux 0 port, which is not supported.
Symptom: The undebug all command does not disable the debug redundancy all command.
Workaround: Use the no debug all command to disable all debugging activity.
Symptom: If the configuration register value is set to 0x2102 while autobooting, the system might experience a TLB (translational bridging) exception if the system boot image is not specified using the boot system command. The system continues to boot without problems, despite this exception.
Workaround: When the configuration register is set to 0x2102, specify the system boot image to be autobooted using the boot system command. If the system boot image is specified using the boot system tftp command, also specify the bootloader image using the boot bootldr command. After executing these commands, save the configuration in the NVRAM, using the copy running-config startup-config command.
Symptom: All Software Upgrade (system IOS, ATM, FDDI) is broken on Cluster Manager and VSM if the cluster member's management VLAN has no IP address.
Symptom: When attempting to reprogram the ROMMON, the switch router sometimes hangs after displaying the following message:
Workaround: Remove and reinsert the route processor module or power cycle the switch router.
Symptom: The debug ncdp packets, debug ncdp errors, and debug ncdp events commands do not display any information when accessing the switch router through the Ethernet port.
Workaround: Access the switch router using the console port.
Symptom: If ILMI is configured on the terminating interface of a soft VC, ILMI must be in the UpAndNormal state for this soft-VC to come up.
Workaround: Upgrade to the Cisco IOS release 12.0(10)W5(18c).
Symptom: Modem access to the console port requires special settings.
The Catalyst 8540 provides support for connecting the modem to the console port. However, the following settings of the modem are required:
You can configure your modem by setting the DIP switches on the modem or by connecting the modem to terminal equipment. Refer to the user manual provided with your modem for the correct configuration information.
Please note there are no hardware flow control signals available on the console port, so the console port terminal characteristics should match the modem settings.
Symptom: The Catalyst 8540 might display a CRC error when it obtains the clock via an OC-3c link from a LightStream 1010 ATM switch and then uses or redistributes the clock over an OC-12c link.
Workaround: Use the internal clock or bring the clock source directly to the Catalyst 8540.
Symptom: PVCs exiting the switch router over a hierarchical VP tunnel are not preserved when the route processor switches over.
The switch router stops switching traffic over such PVCs upon and after the route processor switchover. The hierarchical VP tunnel remains active, however, and after the route processor switchover the VCs defined over the hierarchical VP tunnel (both PVCs and SVCs) function as expected.
Symptom: If no ACL module is present in a slot, the following message appears in the console log on a SP switchover:
This is an informational message only and has no effect on switch router function.
Fast Ethernet port identifier truncated in the show atm status command.
Symptom: The show atm status command is not supported.
Workaround: The command is supported in Cisco IOS Release 12.0(5)W5(13b) or a later release.
Symptom: Bridging on a subinterface is only supported in conjunction with the IEEE Spanning Tree.
Symptom: Under certain circumstances, the Catalyst 8540 might display inaccurate traffic statistics on NNI or UNI interfaces.
Symptom: Despite having enough bandwidth, resource management might reject some soft PVCs.
Symptom: 8-port Gigabit Ethernet interfaces cannot support bridging when the bridge group runs DECNET Spanning Tree.
Symptom: After shutting down an ATM router module interface which is a member of a port channel, the interface entry is not removed from the port channel. Since removing a member interface from a port channel does not put the port channel into blocking mode, no loss of connectivity should result.
Symptom: When using the Catalyst 8540 usage parameter control (UPC) tag functions (change the CLP=0 to CLP=1), the following ports might not work: For 16-port OC-3c and 4-port OC-12c interface modules, interfaces ATM 0/0/0, ATM 0/0/2, ATM 2/0/0, ATM 2/0/2, ATM 9/0/0, ATM 9/0/2, ATM 11/0/0, and ATM 11/0/2 might fail UPC tag mode.
Workaround: Upgrade the switch processor FPGA image to Version 1.5 (fi-c8540-msp.A.1-5) or later.
Symptom: The ILMI keepalive feature resets the interface on the second retry following a link failure. This behavior might occur despite having configured the system to allow up to five retries.
Symptom: On a system configured with either both power supplies or only power supply 1, issuing the show hardware, show hardware detail, or show tech-support commands might cause the memory corruption. If this memory corruption occurs and the show subsystem command is entered, the Catalyst 8540 might fail unexpectedly.
Workaround: If the system is configured with two power supplies, remove power supply 1 before issuing any of the commands listed in the Symptom text. If the system is configured with one power supply, make sure that you use power supply 0.
Symptom: Alignment correction made while running IPX routing and data packets over dot1q over fec.
Symptom: If the switch router is booted with cleared NVRAM, because the switch router is new, or after a write erase command, and the automatic configuration is skipped, the following messages are displayed:
These messages are harmless and can be ignored. The only effect is an increased boot time of approximately 1 minute.
Workaround: Use the automatic configuration feature upon first boot-up or when the switch router is booted after a write erase command.
Symptom: The digital cross-connect unit (DCU) might malfunction unexpectedly.
Symptom: Following a route processor switchover, the switch router might fail to recognize port adapter interfaces associated with a carrier module.
Workaround: Upgrade the carrier module FPGA image to release 1.7 or later.
Symptom: With RMON enabled on Fast Ethernet interfaces, SNMP interface counters begin to grow exponentially. Port utilization might be greater than 100% when the actual utilization might be as low as 1%. This happens with either RMON native or RMON promiscuous. While SNMP counters are erratic, the CLI remains accurate.
Symptom: Following a software reload, the Catalyst 8540 might fail unexpectedly with a write bus error. This failure might occur if the system is configured with one route processor, and the switch processor modules are installed in slots 5 and 6 or in slots 6 and 7.
Workaround: Install the switch processor modules in slots 5 and 7.
Symptom: The router fails to see incoming AppleTalk broadcasts when the router, configured for IRB, is routing and bridging IP and just routing AppleTalk.
Symptom: When powering up and booting the switch router with two route processors, or installing a second route processor in a working switch router, the console port of the secondary route processor might display the following error message:
The secondary route processor fails to boot and the switch router is in a non-redundant mode. This problem occurs when the Catalyst 8540 with two route processors and the secondary route processor have an FPGA image version of 4.5 or earlier. To recover, power cycle the switch router or remove and reinsert the secondary route processor.
Workaround: Upgrade the route processor FPGA image to version 4.6 or later.
Symptom: An IPX packet containing the wrong length in the IPX header and requiring an encapsulation change causes the ingress port to hang. The switch router must be reloaded.
Symptom: On the Catalyst 8540 CSR running the W5(11) code or lower, adding logging source-interface and then removing logging source-interface might stop syslogs being sent out on Ethernet 0 (the management port). Syslogs continue to be sent out through the regular interface module ports.
Workaround: Do not configure the source-interface. If you configure the source-interface, do not remove the logging source interface. Rebooting the switch router resolves the state. An error syslog (LINK-3-UPDOWN) also corrects the problem.
Symptom: The squeeze command might result in an error in which the squeeze progress is not displayed. For example:
-Traceback= 600ACC30 6001E8B8 60037470 60038BEC 60037714 604139D8 60413A8C 60433E78 60095794 60095780
Symptom: The switch router crashes when you enter and exit configuration mode repeatedly and quickly.
Symptom: AppleTalk routing does not work when two connected ports are part of a bridge-group with AppleTalk addresses on the ports and IP addresses on the BVI.
Symptom: With IRB configured, bridging loops occur if there is a physical loop for the broadcast domain.
Symptom: The Hot Standby Router Protocol (HSRP) over a Bridge Group Virtual Interface (BVI) configuration is not supported if the BVI encompasses LANE interfaces. This configuration is valid and functional only if the BVI encompasses Ethernet interfaces.
Symptom: Appletalk is not supported on 8-port Gigabit Ethernet interface modules.
Symptom: Following a change to a spanning tree, inconsistencies might occur in the bridge members information stored in the Ethernet module interface and the IOS.
Workaround: Use the clear bridge command to purge the bridging cache.
Symptom: After repeatedly entering and exiting global configuration command mode, the system might freeze unexpectedly.
Symptom: When the system is configured to autoboot, and the redundancy prepare-for-cpu-removal command is entered, the route processor does not stay in ROMMON mode, but proceeds to autoboot again.
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
Symptom: A T1 CES interface does not send out a remote alarm indication (RAI) in the reverse direction upon detecting an alarm indication signal (AIS).
Symptom: Attempting to format the Intel 200 Series Flash PC card that is currently shipping with other platforms (such as the Catalyst 6000) might cause the Catalyst 8540 to fail unexpectedly with a bus error. If this failure occurs, the system will not boot up successfully until the Flash PC card is removed from the switch router.
Workaround: Remove the Flash PC card from the switch router.
Symptom: IPX ping incorrectly shows success during simultaneous pinging.
Symptom: When a clear bridge command is issued, MAC addresses specified for the access lists are not reprogrammed in the CAM tables.
Workaround: Issuing a shutdown/no shutdown on the bridge port where the access list is configured reprograms the MAC address in all other bridge group members.
Symptom: After an interface timeout is expired, adjacencies for static ARP entries are refreshed every minute, which might cause momentary connectivity loss. This does not apply to dynamically created adjacencies.
Symptom: The Catalyst 8540 sends an invalid PDU when the counters are cleared.
Symptom: Following the online insertion of an interface module into a router configured with IGMP static group and running multicast traffic, failures occur when downloading to the interface module.
Workaround: Either shut down any interface configured with IGMP static group before inserting or removing interface modules; or do not insert or remove interface modules online when the switch router is configured with IGMP static group.
Symptom: Path costs on Gigabit Ethernet interfaces shown by the show span command do not match the expected default value of 100.
Workaround: Set the path costs manually. One option would be to set the path cost for Gigabit EtherChannel (GEC) ports to 1 and set the path cost for the non-GEC ports to 2.
Symptom: When large numbers of MAC addresses are learned over a port channel, some addresses do not age out after the aging timer expires.
Workaround: Use the clear bridge bridge-id command to remove learned MAC addresses.
Symptom: The interface delay metric is set inappropriately for port channel interfaces where one or more Gigabit Ethernet interfaces or Fast Ethernet interfaces are grouped into a channel. The delay for a single Gigabit Ethernet interface is 10 microseconds. The delay for a port channel consisting of one or more Gigabit Ethernet interfaces is 100 microseconds. The delay for a single Fast Ethernet interface is 100 microseconds. The delay for a port channel made up of one or more Fast Ethernet interfaces is 1000 microseconds.
This incorrect setting has implications for routing protocols that use interface delay as part of the metric, such as IGRP and EIGRP, and might cause the routing protocol to prefer a route through a single interface over a route through a port channel, everything else being equal.
Workaround: Manually configure an appropriate delay on the port channel interface using the delay command.
Symptom: The "Uptime" for the secondary route processor from a show redundancy command might display incorrectly. This problem occurs because the "Uptime" rolls over after about four hours.
Message: Job <job name> ran <time>
Symptom: Job <job name> ran <time> messages appear frequently or at regular intervals.
The job event queue on the 8-port Gigabit Ethernet interface module lets the event manager know, in microseconds, the maximum amount of time a job is expected to run. It also tracks how long each job actually ran. The Job <job name> ran <time> message should alert you that a job ran longer than expected. It is not normal for the message to come often or at a regular interval.
Symptom: Performing an OIR on the secondary route processor might produce the following error message:
%OC3SUNI: Read diagnostics for ATM1/1/0 failed(1)
Workaround: Reboot the system.
Symptom: Routing protocols take more time to converge after reboot on a router with large ACLs configured on many interfaces.
Workaround: None. When you reboot a router, it can take considerable time to populate large ACLs on many interfaces, resulting in a delay in the convergence of some routing protocols.
Symptom: Configuring interfaces on line aux 0 might cause the redundancy feature to fail. The primary and secondary route processors will boot, but running the show redundancy command on the primary route processor incorrectly indicates that the secondary route processor is down.
Workaround: Remove all configuration commands from line aux 0 and reboot the switch router.
Symptom: When using FTP to transfer a core file to a server, the switch router might not create an exception dump following a system crash.
Symptom: IPX ACL on a subinterface of a non-trunk main interface does not filter traffic.
Workaround: Configure the ACL on the main interface instead of the subinterface to achieve the same result. Due to space limitations, IPX ACL cannot be applied directly to a subinterface of a non-trunk main interface.
Symptom: If an interface in subslot 1 of a carrier module is the present active clock source, and an interface in subslot 2 of the same carrier module is the secondary clock source, the clock source of the secondary might be overridden to loop-timed rather than network-derived.
Symptom: After replacing an existing configured ACL on an interface with another ACL, routed packets that should be blocked are forwarded for a very short period of time.
Workaround: Within a short period of time, the ACL is reprogrammed and block packets as required. When you remove an ACL and replace it with another ACL, ACLs are temporarily removed from memory, and the ACL flag is turned off. Some packets that should be blocked by the ACL will temporarily be permitted until the ACL flag is turned on again.
Symptom: When using Cisco IOS Release 12.0(1), the router crashes with a bus error when an attempt is made to remove the bridge-group command.
Symptom: On a router with a rev-B1 fast Ethernet interfaces, there is no way to turn off time-stamp refresh during destination address lookup. A source address is learned on a port in the initial spanning tree state. After the port goes into blocking state, a destination address lookup on the received packet keeps the entry alive. This is particularly true where the source and destination address are the same, as in the case of keepalive packets.
Workaround: None. This problem does not occur in routers with fast Ethernet interfaces later than rev-B1.
Symptom: After upgrading the ACL FPGA image using the reprogram command, the system warns you that the image is not compatible with the current IOS version, and the ACL card might become unusable unless you update the IOS image.
Workaround: Ignore this warning for the ACL card, and continue the FPGA download. Do not ignore this warning for other controllers.
Symptom: When configuring ACL on subinterface 1023 or above, the router returns the following message:
Workaround: Limit the number of subinterfaces configured with ACL to 1000 for the switch router.
Symptom: Cannot receive CDP packets on a trunk port connected to a Catalyst 5000 if CDP packets are coming on a VLAN for which a subinterface is not configured.
Workaround: To receive CDP packets, configure a dummy VLAN subinterface on the trunk port connected to the Catalyst 5000.
Symptom: Two Catalyst 8540 CSRs with 802.1Q VLAN encapsulation cannot ping each other.
Workaround: To receive ARP packets, use ISL VLAN encapsulation on trunk ports connected to a Catalyst 5000.
Symptom: The soft VCL counter incorrectly reaches its maximum value upon link transition, thus keeping soft VCs from connecting to ports which have incorrect soft VCL numbers.
Workaround: Reload the system.
Symptom: The status LED on the standby switch processor module remains red after boot up.
Symptom: When the switch router is booted after a power cycle, the reload reason in the show version command does not indicate that the "System restarted by power-on."
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
Symptom: After performing an OIR on a carrier module, the corresponding port adapter interface counter values displayed in a show interface command might become unreliable.
Symptom: When a static route pointing to one interface is changed to point to a different interface, the corresponding adjacency entry is not updated.
Workaround: Use the clear arp command to reprogram the correct adjacencies.
Symptom: When a port adapter is removed from the chassis, the entry in ciscoLS1010SubModuleTable is not deleted.
Symptom: When you insert an 8-port Gigabit Ethernet interface module while IOS is running, you see the following message:
The LED on the interface module is orange and none of the interfaces will work. The interface module is nonfunctional.
Workaround: Reload the Cisco IOS software, and the interface module will function. The LED should always be green when the 8-port Gigabit Ethernet interface module is functioning.
Symptom: Connections to the ATM router module interfaces cannot pass through shaped VP tunnels.
Workaround: Configure hierarchical VP tunnels for ATM router module interface connections.
Symptom: The Catalyst 8540 does not support a PVP tunnel with a VPI value of 0.
The IOS software relates subinterface 0 to the main interface, so interface ATM x/y/z.0 represents the main interface x/y/z. If the user attempts to create a PVP tunnel with a VPI value of 0, the system should return an error on interface ATM x/y/z.0.
Symptom: An unexpected system failure might occur following a show tech-support command when OC-3c interfaces are present. This might also occur with the show controllers command.
Symptom: The versions of the Smart Modular and Sharp Flash PC cards used to store diagnostics and IOS software images might report unrecoverable write errors. Affected cards use a Sharp chip set (LH28F016SCT).
Workaround: If you have a Smart Modular Flash PC card, the fix for this problem is available with the Cisco IOS Release 12.0(4a)W5(11a) software. Netboot the image, reformat the Flash PC card and copy the image to it. You can then autoboot from the Flash PC card.
Symptom: The Catalyst 8540 does not allow you to configure more than 255 VPs, even though the 12-bit VPI allows a maximum of 4095 VPs.
Symptom: The ciscoLS1010ChassisInletTempStatus MIB, which is an object added for the Catalyst 6400 platform, does not return a value.
Workaround: This object is not supported by the LightStream 1010 or Catalyst 8500 platforms.
Symptom: On a PNNI signalling link, the Promina 4000 NET switch sends a message that prompts the system to send a CALL PROCEEDING message and then a RELEASE message. The UNI 3.0 specification, section 5.4.5.15, defines a cause code 8a as "VPCI/VCI unacceptable." When the call goes out on a UNI 3.1 interface, this cause code should be mapped to VPI/VCI assignment failure. This mapping does not occur for PNNI links.
Symptom: EIGRP updates are missing for some addresses on ATM router module port subinterfaces.
Workaround: In global configuration mode, enter the no auto-summary command followed by the auto-summary command.
Symptom: A problem in the reinitialization logic might cause the system to fail unexpectedly when a switch processor module in slot 5 is the standby and the switch processor module in slot 7 fails.
Workaround: Do not configure the switch processor in slot 5 as the standby.
Symptom: When the system is configured to autoboot, and the configuration register is set to 0x2102, the secondary route processor crashes during autoboot.
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
Symptom: Incorrect MAC address entries in the CAM table might cause HSRP to fail over a BVI interface.
Symptom: The following messages may appear on the console. They are not reproducible.
The message appears on subinterface ATM11/0/0.14 on the ATM router module port.
Symptom: The device might lose its IP OSPF neighbor information and connections over a BVI interface after a few days of running, requiring a system reboot.
Symptom: IP prefix entries in the CAM table might point to incorrect adjacency information, causing routing failure.
Symptom: The CES ABCD bits are not user configurable when a fault occurs.
Symptom: When forwarding a call setup message from one VP tunnel to another, the Catalyst 8540 might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.
Symptom: Configuring a channelized E1 (CE1) Frame Relay 2.048-Mbps ATM port adapter for clear E1 might cause the linecode violation and LES counters to increment continually.
Symptom: The device might lose IPX connectivity over a BVI interface, requiring the use of the clear ipx route* command to reestablish connectivity.
Symptom: The command show atm resources shows that the number of cells in the UBR queue in an MSC increases continuously but slowly.This happens when traffic is sent through a Catalyst 8540 MSR at close to line rate.
Symptom: After executing an IPX ping with a timeout value of zero, subsequent IPX pings on the device will fail.
Symptom: When an FEC is configured as a part of a bridge group and a topology change occurs, the bridge table might get out of sync with the Layer 2 CAM information.
Workaround: Use the clear bridge command to keep the IOS bridge table and the Layer 2 CAM in sync.
Symptom: atmfAtmLayerConfiguredVCCs might not include the soft PVC count.
If a router connects to an ATM interface on a Catalyst 8540 where soft PVCs are configured, the PVC Discovery feature on the router fails to correctly discover all the configured PVCs and soft PVCs from the switch router. This does not happen if only PVCs are configured.
Symptom: A fully loaded Catalyst 8540 CSR with 2-port Gigabit Ethernet modules boots properly from bootflash and slot, but does not boot from tftp.
Symptom: Marker cells are not drained after entering the shutdown/no shutdown command on the interfaces.
Under stress conditions, if there are several hierarchical VP tunnels configured and if the tunnel interfaces are transitioned several times, cells might stay in the switch fabric.
This does not occur on interfaces without hierarchical VP tunnels.
Symptom: If you configure BVI, but do not want to do IP routing at the BVI level, and you have IP addresses for the interfaces in the bridge group, then routing protocols might not work.
Workaround: Remove the interfaces from the bridge group and then add them back into the bridge group.
Symptom: When a large number of bridge groups or bridge group members are configured and IRB is enabled on the devices, reloading one of the devices or configurations might lead to high route processor utilization. The side effect of this is temporary spanning-tree loops, leading to AAL5 buffer exhaustion problems.
Workaround: In this case, if IRB is enabled, you might need to increase the number of buffers on the device using the aal5 buffers command.
Symptom: During route processor switchover, LMI times out on peer interfaces.
The Catalyst 8540 requires about a minute to switch over. The Frame Relay interface might take about a minute before it can respond to any LMI activity.
Workaround: To prevent LMI timeouts on peer interfaces during switchover, configure an LMI timeout longer than the time it takes for the Catalyst 8540 route processor to switch over. Configure lmi-n392dce, lmi-n392dte, lmi-t392dce and lmi-n391dte on the Frame Relay interface so that LMI will not bring down the interface if no LMI activity is seen for about a minute.
Symptom: After entering the show running-config command several times, the Catalyst 8540 might fail unexpectedly due to a bus error.
Symptom: The file system fails to add the secondary NVRAM and secondary RCSF on a route processor switchover.
Symptom: No means to change the default active switch processor modules is available.
Workaround: If a Catalyst 8540 has three switch processor modules, by default the switch processor modules in slots 5 and 7 come up as the active switch processor modules and the switch processor module in slot 6 comes up as the standby. To change this default, use the following privileged EXEC command:
redundancy preferred-switch-card-slot slot#1 slot#2
Two preferred slots must be specified and they must be unique. The range of the slot value is 5 to 7. If one of the preferred slots selected is not a currently active switch processor module, you are asked whether the system should change the active switch processor module to the preferred switch processor module. If such a switchover occurs, all the active connections in the system are reinitialized. If you wish to continue, then the preferred switch processor modules become active and the other switch processor module becomes the standby. This configuration remains in effect until one of the active switch processor modules is removed. The preferred switch processor module configuration is preserved across route processor switchovers. However, the preferred switch processor module setting is lost if the system is power cycled or if both route processors are reloaded to ROM monitor mode.
Symptom: Setting the gateway of last resort is delayed on route processor switchover.
The static IP routes take from 1.5 to 2 minutes to take effect on switchover.
Symptom: The primary route processor should not be hot swapped.
If a route processor that is currently running IOS is removed from the chassis in a skewed manner, such that the left side of the route processor comes out before the right side does, the traffic through the switch router might stop.
Workaround: There are some precautions to take before removing a route processor module controller from a chassis that is powered-up.
If the route processor module is currently in ROM monitor mode, then it is safe to remove it from the chassis. You can put the route processor in ROM monitor mode from IOS by issuing a reload command if the switch router is not configured to automatically boot. If the switch router is configured to automatically boot, it starts booting IOS again. To ensure that the route processor is in ROM monitor mode before removing it, use the following command:
redundancy prepare-for-cpu-removal
Execute this command on the route processor before removing it. Once this command is entered, the route processor goes to ROM monitor mode and stays there even if the system is configured to automatically boot. At this point, it is safe to remove the route processor from the system.
Enter this command after connecting to the console port of the route processor. If the system has a Y cable, then remove the Y cable and obtain a local connection to the route processor before the command is entered. Enter the command only on a route processor that is in IOS mode, even if it is the secondary route processor.
Symptom: Changing the MAC address for a bridge group member causes route processor bound packets on that interface to be discarded. For a port channel, the problem occurs when the first member is removed from the port channel.
Workaround: When an interface's MAC address is changed, remove the interface from its bridge group and then add it back into the bridge group.
Symptom: Srecord integrity checking is not adequate.
If all the Srecord lines are removed from a functional image file, the file is corrupted and causes problems if downloaded. The reprogram command Srecord integrity checking does not catch this problem.
Symptom: Incorrect coding of the information element "call state."
Information element "call state" incorrectly sets the coding standard to 00 (ITU-T coding standard) instead of 11 as specified in the PNNI specification. This can cause compatibility problems with other vendors' implementations.
Symptom: On the Catalyst 8540 MSR it is not possible to use a VCI value higher than 8191 for soft VCs and PVCs on the same interface module or port adapter where more than one VCI is configured.
Workaround: Use VCI values lower than 8192.
Symptom: The advertised priority is not updated for PGLs configured to match the advertised priority.
Symptom: The show controller command only displays information for even-numbered ports.
The show controller command for all odd-numbered ports in a 16-port OC-3c interface module displays the information for even-numbered ports.
Symptom: When a peer switch with UPLINK FAST enabled is connected to a Catalyst 8500 bridge group interface, the virtual MAC address of HSRP for an ACTIVE device in one of the member interfaces of the bridge group is programmed as a REMOTE entry.
Workaround: Use the clear bridge command to update the CAM table.
Symptom: Adjacencies are removed when a bridge table entry ages out. This causes traffic to be routed to the route processor, which might lead to high route processor utilization.
Workaround: Set the ARP timeout value to be less than the bridge age timer.
Symptom: When the fiber port is shut, level 1 does not have a mechanism for disabling the transmit signal. Disabling the fiber mode causes the level 1 chip to cut itself from the optical transceiver, which puts the transceiver in a floating state. The remote connection might pick up the bad signal sent by the transceiver as a good one and declare itself as up. The randomness of this signal causes flapping. This is evident when the fiber ports are connected between the following systems:
Workaround: Change the hardware to send a constant signal (idle) when the port is shut.
Symptom: With 16 or more subinterfaces on a port channel, the following configuration might cause CPUHOG messages to appear:
Workaround: No workaround is needed; the route processor HOG messages should not affect the functionality of the device.
Symptom: The rate scheduler allocation (rsAlloc) update is accurately based on granularity of the mantissa value and might lead to oversubscription.
During the CAC process, for pure or partial rate scheduled connections, the rate actually programmed in the hardware might exceed the rate requested. This is particularly visible at very high rates, and is due to the granularity in the mantissa value (which cannot be fractional). However, the CAC allocates in its software structures only the rate requested. This might lead to an oversubscription of the rate scheduler.
This problem occurs at very high VC rates, where the CAC algorithm allocates slightly less than what the rate scheduler is programmed with (the difference is less than 0.03%).
Symptom: Failed attempts to reprogram a carrier module cause the Catalyst 8540 to hang.
Symptom: The switch router rejects calls with extended QoS parameters.
When ATM QoS for CDV is configured and you specify a soft VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft VC does not come up.
Symptom: The show hardware command does not display power supply IDPROM details.
Symptom: Under certain conditions, some Gigabit Ethernet interface module ports will not come up.
Workaround: If you observe this problem, you might need to upgrade your 10/100BASE-T interface module firmware. Contact your Cisco service representative for more information.
Symptom: The lane server-bus ethernet command might cause an unexpected exception when entered after deleting LANE clients from the subinterface.
Symptom: Under extreme low memory conditions, if a switch is configured with lots of hierarchical tunnels and LANE components are configured on the cpu port of the switch (or ATM interface of a router), removing a few subinterfaces or many several times can result in a crash. This removal without first cleaning up LANE configuration results in the loss of 6400 bytes of memory.
Workaround: Delete LANE configuration on a subinterface before deleting the subinterface itself.
Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).
Symptom: The switch router rate scheduler rounds down the rates (when converting from bits per second to cells per second) when they should be rounded up.
Symptom: When a call setup message traverses a switch router running PNNI on the ingress side and IISP (version 3.0 or 3.1) on the egress side, the message might be corrupted.
Symptom: The Catalyst 8540 uses backward parameters in QoS information elements for point-to-multipoint calls.
This might cause incompatibility with other vendors' implementations.
Symptom: PNNI load balances connections among alternate paths to a common destination as long as they have the same cumulative admin weight or other cost. However, load balancing currently only takes place among alternate paths with the same number of hops. Longer paths that have identical cumulative costs are not used for on-demand route computations.
Workaround: Configure background route computations or, for soft-VCs, explicit paths can be used to manually load balance some connections on longer paths.
Symptom: The switch router returns a %IPX-3-BADINSERT message when a duplicate SAP entry is made.
Symptom: High route processor utilization if multicast traffic is high. When PIM protocol is configured, non-RPF multicast traffic is forwarded to the route processor.
Symptom: Cell loss occurs between unlike bandwidth interfaces, such as DS3 or T1 and OC-3c, that reside on the same carrier module which has functional image version 1.4 or earlier.
Workaround: Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.
Symptom: The switch router might detect discrepancies between the software configuration and the hardware after a route processor switchover.
Across a route processor switchover, if an outdated (older than and different from the running configuration) start-up configuration synchronization is applied, or if the latest running configuration synchronization fails, then discrepancies might exist between software data structures and hardware programming. Any PVCs are preserved.
Workaround: Use the copy running-config startup-config command before a route processor switchover.
Symptom: Circuit emulation service (CES) might show an interface as UP following a loss of signal (LOS). Also, if the interface is shut down or the uplink ATM is not functioning, CES might fail to send an alarm indication signal (AIS).
Symptom: Messages appear when hot swapping a carrier module.
When you hot swap a carrier module into the Catalyst 8540 chassis, traceback messages such as the following appear on the console of the secondary route processor. These messages are harmless and can be ignored:
Symptom: When deleting the secondary route processor's start-up configuration, a CPUHOG message appears on the secondary route processor.
The delete command only removes files.
Workaround: Use the erase command to delete devices instead of the delete command.
Symptom: Due to a bad VCXO, a packet might delay on the switch router indefinitely, causing a software crash.
Symptom: CES port LEDs on the Catalyst 8540 are inconsistent with those of the LightStream 1010 ATM switch.
The Catalyst 8540 has an LED status configuration that is inconsistent with that of the LightStream 1010 ATM switch on CBR ports. When nothing is connected to the CBR port, the LED status on the LightStream 1010 ATM switch is as follows:
When nothing is connected to the CBR port, the LED status on the Catalyst 8540 is:
Symptom: AAL5 CRC errors are not accounted for at the physical interface.
The show atm interface command does not display CRC errors seen at the physical interface level. These errors are not logged under AAL5 CRC.
Symptom: When downloading an IOS image to the slot 0 Flash memory card on the Catalyst 8510 CSR by way of SNMP, the copy operation fails with a "copyUnknownFailure" message, and the formatting information on the Flash memory card is lost.
Workaround: When downloading an IOS image by way of SNMP, such as with the SWIM (Software Image Management) application of CiscoWorks2000, always use slot 1 instead of slot 0 as the target location of the IOS image.
Symptom: Some tx per-vc counters on both point-to-point and point-to-multipoint connections miscount cells. The cells are transmitted but not counted. The number of missed cells is small relative to the total number of cells counted is approximately 1% in the worst case.
Workaround: Upgrade the switch router feature card FPGA image to release fi-c8540-fc.A.4-17 or later.
Symptom: When you hot swap any interface module with an OC-12c interface module, the correct configuration for the OC-12c interface module in the port mode table does not come up properly.
Workaround: Upgrade the switch router feature card FPGA image to release fi-c8540-fc.A.4-17 or later.
Symptom: In the output of the show atm vc command, all of the packet counters are incorrectly displayed as zero.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
When an active VP tunnel subinterface is deleted, a software crash might occur.
Workaround: Shut down the subinterface before deleting it.
Symptom: A software crash might occur on the switch router running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Symptom: Online insertion and removal of port adapter modules can result in a bus error.
Workaround: Avoid the online insertion and removal of port adapter modules.
Symptom: Occasionally, the show controllers interface-name command can bring down an interface and the line protocol. The condition that leads to this scenario is random and very infrequent. The end result is that routing/bridging stops on this interface.
Symptom: OIR INSCARD messages display during boot.
Symptom: The Frame Relay port adapter firmware might report CRC errors on a PVC if it receives traffic using the same VPI/VCI/DLCI while the PVC is configured.
The errors only occur while the firmware is still configuring the VC. Once the PVC is configured, the CRC errors stop. Since the frames appear like zero-length AAL5 packets while the firmware is still configuring the VC, the firmware does not increment the discard bytes counter, but does increment the discard frames counter due to the CRC errors.
Workaround: Do not allow traffic to pass on the VC while it is being configured.
Symptom: While toggling the interfaces on the peer switch (the LightStream 1010 ATM switch), the following error message is occasionally displayed on the Catalyst 8540:
This occurs when a LECS is configured on the route processor port along with 10 LES/BUS/LECs on the 10 subinterfaces on the route processor port.
Symptom: Unpredictable results might occur if the route processor scheduler allocation is changed in the configuration file.
Workaround: Remove the scheduler allocate command from the configuration file. We recommend that you do not change the default values for this command.
Route processor HOG message appears when activating OSPF on a large port channel configuration.
Symptom: A route processor HOG message appears when OSPF is activated on a port channel interface with more than 30 subinterfaces.
Workaround: The operation succeeds even if this message appears. No action is necessary.
Symptom: Point-to-multipoint PVC preservation across a route processor switchover is not fully supported.
If traffic is flowing through a point-to-multipoint connection when a route processor switchover takes place, then some of the leaves of the connection might not be restored properly. Traffic might continue to flow through all the leaves of the connection even after the switchover, but the output of the show atm vc command might show NO HW RESOURCE for some of the leaves of the connection. In the absence of traffic, all the leaves of a point-to-multipoint connection will be restored properly across a route processor switchover.
Workaround: If possible, shut down traffic on all point-to-multipoint connections before a route processor switchover.
Symptom: When running tag switching, no tag is created for the default route.
Symptom: The sysConfigName MIB variable value is not set correctly.
If the system is set to autoboot and no explicit boot image is specified, the system boots the default image from the bootflash. In this scenario, the show version command displays the image name as "default image" instead of the actual image name. The MIB variable sysConfigName also returns an empty value.
Symptom: Soft VPs and PVPs cannot coexist due to VPI allocation errors.
When creating soft VPs, the VPI value allocated on the switched part of the soft VP path might collide with existing configured PVPs.
Workaround: There are two ways to get the soft VP up:
Symptom: PNNI does not correctly clean up and release some of its data structures after process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is unavailable until the next reload.
Symptom: The PNNI SNMP agent is not able to discover and allow PNNI-related configurations on ATM subinterfaces.
An alignment error message is printed when an SNMP walk (or other SNMP get next) request is entered.
Symptom: Connections might fail when the connect message includes an end-to-end delay IE. A Catalyst 8540 that is an intermediate switch router passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
Examples of these connections include UNI 4.0, CBR, and VBR-rt.
Symptom: Reprogramming a network clock module causes a processor reset.
Reprogramming the network clock module on the primary route processor causes the route processor to reload after the download is complete. Power cycle the switch router to make the newly loaded image active.
Symptom: Reprogramming a carrier module might cause the Catalyst 8540 to hang and not reboot.
After successfully reprogramming a revision 4.0 carrier module with FPGA 1.4, the Catalyst 8540 might hang. To recover the switch router, remove the carrier module before rebooting.
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.
Symptom: On a Catalyst 8540 system configured with 32 MB of RAM, IPC traffic between the port adapter driver and the firmware can experience a transient failure when the port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if it is reset after waiting for about 2 minutes.
This IPC failure, which is due to an unexpected firmware crash under a heavy load, does not occur on a Catalyst 8540 system configured with 64 MB of RAM.
Symptom: Tag switching and Tag Discovery Protocol (TDP) might cause memory fragmentation.
While running tag switching with a very large number of destinations, continuous toggling of VC merge (which forces all the TDP sessions to restart) on the switch router for a period of time (for example, overnight) causes memory fragmentation in the TDP process.
Symptom: When loading a software version 11.3 or later image on a switch router with 11.2 or earlier image, LECs and other LANE components might fail to come up if they are configured using an ATM address whose first 19 bytes are the same as the active ATM address of the switch router.
The ATM address of the switch router along with the first 128 values for its selector byte should be reserved for use by PNNI. Starting with the 11.3 software version, PNNI supports hierarchy and registers an ATM address for all PNNI nodes using the switch router ATM address with various selector byte values.
Workaround: If LANE components fail to come up because their ATM addresses collide with the reserved ATM addresses for PNNI, reconfigure the LANE components using different addresses. It is recommended that LANE applications use the addresses shown by the show lane default-atm-addresses command, which will eliminate this problem.
Symptom: ADD party requests over a VP tunnel do not work.
On a source node, when adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Symptom: An unnecessary lookup for a network configuration file occurs after a route processor switchover.
When a route processor switchover occurs, the new primary route processor that is taking over might look for configuration files from a network server that might not exist. These network configuration file lookups will timeout. This causes some delay during the switchover process.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port, the switch router returns this internal error message:
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Ignore this message; it does not affect the snooping functionality.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the command has been deleted and the structures pertaining to that tunnel have been released.
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface might become overwhelmed and start generating the following error message:
The interface stops sending data and the transmitter remains stuck.
Workaround: Enter a shutdown/no shutdown command sequence on the interface.
Symptom: When ATM accounting is enabled, an exception might occur because resources at the destination switch router are not available.
Symptom: Another vendor's router running UNI 4.0 cannot connect a VC to a Cisco router running UNI 3.1 by way of a Catalyst 8540.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for guaranteed services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel VC simultaneously, the rate scheduler on the output interface would oversubscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MaxCR) guarantees for other VCs on the interface.
Symptom: When you set the ROM monitor environment variable to boot a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch router hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch router and send a break character to the switch router within 60 seconds to force it to the ROM monitor prompt. You can then manually reboot the switch router and reconfigure the environment variable.
Symptom: The granularity provided by the switch processor scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmission to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Symptom: Open Shortest Path First (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not switch to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch router for the interface that was shut, or a clear ip route command on all the switch routers to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch router that had the closed physical interface.
Symptom: The switch router issues CPU hog messages while setting up many calls.
With a large number of connections installed, a show atm vc command may take longer than 2 seconds to complete. This produces a %SYS-3-CPUHOG error message from the scheduler.
Workaround: If information about a specific VC is desired, to specify the interface and the VPI/VCI needed, use the show atm vc interface command card/subcard/port vpi vci
Symptom: The ATM switch router does not currently support maxvc-number negotiation through ILMI.
Symptom: If there are multiple parallel paths to the same destination on the ATM switch router with a switch processor feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merged and go out of the switch router as a single VC.
Symptom: The Catalyst 8540 Ethernet connection does not receive CDP multicast packets. However, the Catalyst 8540 does send out CDP multicast packets.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Symptom: SNMP SET to a CES port causes the switch router to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES port adapter, the switch router stops working.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels.
The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (through portSelTable) is not possible until the interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Symptom: The CDP configuration for a LEC cannot be saved to NVRAM.
When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM and does not appear in the show running-config command display. CDP is disabled, but the setting reverts to enabled after a reload.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on the NNI interfaces because of switch router crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the Portselgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch router with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Symptom: A LECS expects all LESs to establish an individual control VC to the LECS to validate clients.
If different emulated LANs (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages which validates the clients into a single VC.
For example, see the following LES router configuration:
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
The clients are still allowed to join the ELAN. Disregard the warning message.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch router.
Symptom: Remote defect identification (RDI) cells (sent by an endpoint in response to alarm indication signal [AIS] cells generated at an intermediate switch router with a fault condition on an interface) are not propagated beyond the intermediate switch router. The intermediate switch router removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch router.
This section describes the following Catalyst 8500 MSR restrictions:
The following restrictions apply to the ACL daughter card supported on the Catalyst 8540 MSR:
The following restrictions apply to the ACL daughter card supported on the Catalyst 8540 CSR:
We recommend that you evaluate the level of CPU utilization and performance in your switch router before turning on AppleTalk. Unlike IP and IPX, AppleTalk routing and processing in the Catalyst 8540 is accomplished by the switch processor, not the interface module. This means that routing AppleTalk packets consumes more processing time than routing other protocol packets. In a switch with a sustained high CPU utilization, turning on AppleTalk could result in longer convergence times for routing protocols like EIGRP. AppleTalk packet throughput is dependent on the amount of available CPU processing power.
The Catalyst 8540 MSR ATM router module does not support the following features:
The four adjacent ports (such as 0-3 or 4-7) on a 10/100 Fast Ethernet interface must all use the same VLAN encapsulation, that is, either 802.1Q and native, or ISL and native.
When assigning Ethernet interfaces to an EtherChannel, all interfaces must be either Fast Ethernet or Gigabit Ethernet. You cannot mix Fast Ethernet and Gigabit Ethernet interfaces within a single EtherChannel.
Catalyst 8540 interface modules support a maximum of 2 paths. To improve EIGRP or OSPF convergence, set the maximum-paths for the router to 2, using the following command:
The eight-port Gigabit Ethernet interface module is supported on the Catalyst 8540 CSR only. This section describes limitations of the eight-port Gigabit Ethernet interface module.
The eight-port Gigabit Ethernet interface module installed in a Catalyst 8540 CSR can support a maximum of 128 ports per bridge group.
If your Catalyst 8540 CSR has an eight-port Gigabit Ethernet interface module, you cannot create a port channel that has some members on that module and others on other modules. All port channel members must reside on the same Gigabit Ethernet interface module.
Also, if your switch router has an eight-port Gigabit Ethernet interface module, port channel IDs 57 to 64 are reserved, and cannot be assigned to other external interfaces. If you assign a port channel ID number greater than 56, the system will respond with the following message:
If you have already assigned port channel IDs 57 to 64, you must reassign them before installing an eight-port Gigabit Ethernet interface module.
If your switch router does not have an eight-port Gigabit Ethernet interface module, you can assign port channel ID numbers up to 64.
The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of interface modules on the Catalyst 8500 CSR:
Online diagnostics, such as access tests, online insertion and removal (OIR) tests, and snake tests, detect and report hardware failures in the Catalyst 8540 during system bootup and operation. The following restrictions apply to the OIR (also known as hot swapping) tests and the snake tests on the Catalyst 8500 CSR:
|
Note Access tests are supported on all Layer 3 interface modules. Refer to the "Configuring Online Diagnostics (Catalyst 8540)" section in the Layer 3 Switching Software and Feature Configuration Guide for additional information. |
On an 8540, the reprogram command for upgrading the FPGA on the switch processor requires power cycling the box after completing the FPGA download.
The Catalyst 8540 MSR switch routers support extra long haul (1000BASE-ZX) GBICs as follows:
A Bridge-Group Virtual Interface (BVI) is a virtual interface within the campus switch router that acts like a normal routed interface. A BVI does not support bridging, but it actually represents the corresponding bridge group to routed interfaces within the switch router. The interface number is the link between the BVI and the bridge group.
Layer 3 switching software supports the routing of IP and IPX between routed interfaces and bridged interfaces in the same router, in both fast-switching and process-switching paths. BVIs do not support IP multicast routing.
The Catalyst 8540 CSR supports the use of redundant route processors and switch modules. The second route processor would be installed in slot 8, and an additional switch module would be installed in slot 6.
There are some precautions that need to be taken before removing a route processor module from a chassis that is powered-up. If a route processor module that is currently running IOS is removed from the chassis in a skewed manner such that the left side of the processor comes out before the right side does, the traffic flowing through the device might stop flowing.
To avoid this, make sure the route processor module that is being removed is currently at the ROM monitor prompt; it is then safe to remove it from the chassis. One way to get the system into ROM monitor from IOS is to issue a reload command. This will work if the system is not configured to auto-boot. If the system is configured to auto-boot, it starts booting IOS again.
Since you need to ensure that a route processor is in ROM monitor before removing it, the redundancy prepare-for-cpu-removal command has been added to take the system to the ROM monitor prompt. Execute this command on the route processor being removed before removing it. Once this command is issued, the route processor will go to the ROM monitor prompt and stay there even if the system is configured to auto-boot. At this point it is safe to remove the route processor from the system.
If a Catalyst 8540 has three switch modules, then by default the switch modules in slots 5 and 7 come up as active, and the one in slot 6 comes up as the standby. If you wish to change this default, there is a command that lets you select the "preferred" switch module slots. This command is a privileged exec level command with the following format:
redundancy preferred-switch-card-slot slot#1 slot#2
Two unique preferred slots must be specified. The range of the slot value is 5 to 7. If one of the preferred slots is not a currently active switch module, you are informed of this and asked if the system should change the active switch modules to the preferred switch modules. If such a switch-over occurs, all the active connections in the system will be reinitialized. If you wish to continue, then the preferred switch modules become active, and the other switch module becomes the standby. This configuration will remain in effect until either one of the active switch modules is removed.
The preferred switch module configuration is preserved across route processor switch-overs. However, the preferred switch modules setting will be lost if the system is power-cycled or if both route processors are reloaded to the ROM monitor.
Beginning with Cisco IOS Release 12.0(5)W5(13) software, the autonegotiation feature for speed and duplex on 10/100BASE-T Ethernet ports defaults to "on." This means that for each port, the Catalyst 8540 CSR automatically detects the port speed (10 Mbps or 100 Mbps) and duplex of the peer port, if that port also autonegotiates.
To override autonegotiation and set a port to 10 Mbps operation, issue the following command:
To set a port to 100 Mbps operation, issue the following command:
To set the duplex value for a port to full-duplex, issue the following command:
To set the duplex value for a port to half-duplex, issue the following command:
|
Caution If you connect a Catalyst 8540 CSR running Cisco IOS Release 12.0(5)W5(13) software to a switch router running in forced full-duplex mode, you might encounter symptoms such as high collision rate or reduced throughput, as the Catalyst 8540 unsuccessfully tries to autonegotiate with the other device. When autonegotiation fails, the Catalyst 8540 defaults to half-duplex operation, which causes a mismatch between it and the other device. Possible workarounds include forcing the Catalyst 8540 CSR to operate in full-duplex mode or removing the full-duplex command from the other device. |
When you connect a Catalyst 8540 CSR to a Catalyst 5000 100BASE-FX MM Ethernet interface module using ISL, ensure that the hardware version on the Catalyst 5000 interface module is 1.3 or higher. You might experience connectivity problems between the Catalyst 8540 CSR and the Catalyst 5000 if the hardware version on the Catalyst 5000 Ethernet interface module is lower than 1.3.
You can use Catalyst 8540 CSR interface modules in a Catalyst 8540 MSR chassis with an MSR route processor and switch modules. Use only CSR (Ethernet) interface modules, and load the CSR software image on the MSR.
Starting with the following software releases, hardware and software functionality interoperability exists between CSR interface modules and MSR interface modules by way of the ATM router module on the MSR chassis running an MSR image:
The Catalyst 8540 MSR system running Cisco IOS Release 12.0(0.6)W5(1) or later have been certified as Y2K Compliant. For more information, see the following URL: http://www.cisco.com/warp/public/752/2000/.
The following sections describe the documentation available for the Catalyst 8540. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules that are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.
The most up-to-date documentation can be found on the Web via Cisco.com and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.
These release notes should be used in conjunction with the documents listed in these sections:
The following is a list of the platform-specific documentation available for the Catalyst 8540:
The following is a list of the software documentation available for the Catalyst 8540:
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
|
Note If you purchased your product from a reseller, you can access Cisco.com as a guest. Cisco.com is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to Cisco.com services. |
For service and support for a product purchased directly from Cisco, use Cisco.com.
For helpful tips on configuring Cisco products, follow this path on Cisco.com:
Service & Support: Technical Documents (button on left margin)
"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From areas outside the United States, call 650-556-8409.
The following sections are provided in the Documents Section of the TAC Web page:
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
Posted: Mon Mar 10 23:56:10 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.