This document describes the features and caveats for Cisco IOS Release 12.0(13)W5(19c), and all previous releases for the Catalyst 8500 campus switch router (CSR).

Note All information pertains to both the Catalyst 8540 CSR and Catalyst 8510 CSR platforms, unless differences between the platforms are noted in the text.

This document includes the following sections:

Introduction
System Requirements
New and Changed Information
Caveats for Catalyst 8500 CSR
Restrictions
Catalyst 8540 CSR Route Processor and Switch Module Redundancy
Autonegotiation
Interoperability
Incompatibility
Y2K Compliance
Related Documentation
Obtaining Documentation
Obtaining Technical Assistance

Introduction

The Catalyst 8540 CSR and the Catalyst 8510 CSR belong to a class of high-performance Layer 3 switch routers. They are optimized for the campus LAN or the intranet and provide both wirespeed Ethernet routing and switching services.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.0(13)W5(19c), and includes the following sections:

Memory Defaults and Upgrade Options
Hardware Supported
Software Release Requirements

Memory Defaults and Upgrade Options

Table 1 lists the default Flash and DRAM memory for the Catalyst 8540 CSR and Catalyst 8510 CSR, as well as memory upgrade options.

Table 1: Catalyst 8500 CSR Default Memory and Upgrade Options

Memory Type	Catalyst 8540 CSR Defaults	Catalyst 8510 CSR Defaults	Upgrade Options

Flash memory	16 MB	16 MB	MEM-ASP-FLC16M= MEM-ASP-FLC20M=
DRAM	256 MB	64 MB	None

To download and store a copy of the Catalyst 8500 CSR software image, we recommend using a minimum 20 MB Flash PC Card, which will allow you to have two or more images installed at the same time.

The Catalyst 8500 CSR boots from its onboard Flash memory by default. To change this default to boot from a Flash PC Card instead, you must change the configuration register setting to 0x2102. Refer to the Layer 3 Switching Software Feature and Configuration Guide for more information.

Hardware Supported

Table 2 and Table 3 list the hardware modules supported on the Catalyst 8500 CSR in the Cisco IOS Release 12.0(13)W5(19) and 12.0(13)W5(19a). They also include the minimum software release requirements for the hardware.

Table 2 lists the hardware modules supported by the Catalyst 8540 CSR.
Table 3 lists the hardware modules supported by the Catalyst 8510 CSR.

Note Although minimum software versions are listed, we strongly recommend that you use the latest available software release for all Catalyst 8500 CSR hardware.

Table 2: Catalyst 8540 CSR Interface Modules and Minimum Software Required

Part Number	Description	Minimum Software Version Required

	Route Processors, Switch Cards, and Daughter Cards
C8541CSR-RP	Route processor	12.0(1a)W5(6f)
C8542CSR-SP	Switch processor	12.0(1a)W5(6f)
C8540-ACL	ACL daughter card	12.0(4a)WX5(11a)
	Gigabit Ethernet Interface Modules
C85GE-8X-64K	8-port Gigabit Ethernet 64K	12.0(4a)WX5(11a)
C85GE-2X-16K	2-port Gigabit Ethernet 16K	12.0(1a)W5(6f)
C85GE-2X-64K	2-port Gigabit Ethernet 64K	12.0(4a)WX5(11a)
C85GE-2XACL-16K	2-port Gigabit Ethernet 16K with ACL	12.0(4a)WX5(11a)
C85GE-2XACL-64K	2-port Gigabit Ethernet 64K with ACL	12.0(4a)WX5(11a)
C85EGE-2X-16K	Enhanced 2-port Gigabit Ethernet 16K	12.0(10)W5(18c)
C85EGE-2X-64K	Enhanced 2-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85EGE-2X-256K	Enhanced 2-port Gigabit Ethernet 256K	12.0(10)W5(18c)
C85-POSOC12I-64K	1-port POS OC-12c/STM-4 SMF-IR and 1-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85-POSOC12I-256K	1-port POS OC-12c/STM-4 SMF-IR and 1-port Gigabit Ethernet 256K	12.0(10)W5(18c)
C85-POSOC12L-64K	1-port POS OC-12c/STM-4 SMF-LR and 1-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85-POSOC12L-256K	1-port POS OC-12c/STM-4 SMF-LR and 1-port Gigabit Ethernet 256K	12.0(10)W5(18c)
C85-1OC3MGE-64K	1-port OC-3c/STM-1 MMF ATM Uplink and 1-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85-1OC3SGE-64K	1-port OC-3c/STM-1 SMF-IR ATM Uplink and 1-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85-1OC12MGE-64K	1-port OC-12c/STM-1 MMF ATM Uplink and 1-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85-1OC12MGE-256K	1-port OC-12c/STM-1 MMF ATM Uplink and 1-port Gigabit Ethernet 256K	12.0(10)W5(18c)
C85-1OC12SGE-64K	1-port OC-12c/STM-1 SMF-IR ATM Uplink and 1-port Gigabit Ethernet 64K	12.0(10)W5(18c)
C85-1OC12SGE-256K	1-port OC-3c/STM-1 SMF-IR ATM Uplink and 1-port Gigabit Ethernet 256K	12.0(10)W5(18c)
	Fast Ethernet Interface Modules
C85FE-16T-16K	16-port 10/100 UTP 16K	12.0(1a)W5(6f)
C85FE-16T-64K	16-port 10/100 UTP 64K	12.0(4a)WX5(11a)
C85FE-16TACL-16K	16-port 10/100 UTP 16K with ACL	12.0(4a)WX5(11a)
C85FE-16TACL-64K	16-port 10/100 UTP 64K with ACL	12.0(4a)WX5(11a)
C85FE-16F-16K	16-port 100-FX MT-RJ 16K	12.0(1a)W5(6f)
C85FE-16F-64K	16-port 100-FX MT-RJ 64K	12.0(4a)WX5(11a)
C85FE-16FACL-16K	16-port 100-FX MT-RJ 16K with ACL	12.0(4a)WX5(11a)
C85FE-16FACL-64K	16-port 100-FX MT-RJ 64K with ACL	12.0(4a)WX5(11a)

Table 3: Catalyst 8510 CSR Interface Modules and Minimum Software Required

Part Number	Description	Minimum Software Version Required

	Route Processors, Switch Cards, and Daughter Cards
C8510-SRP	Layer 3 Switch Route Processor	12.0(1a)W5(6f)
C8510-ACL=	ACL daughter card	12.0(10)W5(18b)
	Gigabit Ethernet Interface Modules
C85GE-1X-16K	1-port Gigabit Ethernet 16K	12.0(1a)W5(6f)
C85GE-1X-64K	1-port Gigabit Ethernet 64K	12.0(1a)W5(6f)
	Fast Ethernet Interface Modules
C85FE-8T-16K	8-port 10/100 RJ-45 16K	12.0(1a)W5(6f)
C85FE-8T-64K	8-port 10/100 RJ-45 64K	12.0(1a)W5(6f)
C85FE-8F-16K	8-port 100-FX MT-RJ 16K	12.0(1a)W5(6f)
C85FE-8F-64K	8-port 100-FX MT-RJ 64K	12.0(1a)W5(6f)

Software Release Requirements

Note We strongly recommend that you use the latest available software release for all Catalyst 8500 CSR hardware.

To determine the version of Cisco IOS software currently running on a Catalyst 8500 CSR, log in to the switch router and enter the show version EXEC command.

Most of the interface modules supported on the Catalyst 8500 CSR 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 online 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 8510 MSR and LightStream 1010)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide.

Feature Set Tables

The Cisco IOS 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 4 lists the software features available for the Catalyst 8500 CSR, beginning with Cisco IOS Release 12.0(1a)W5(6f).

Table 4: Feature Sets Supported by the Catalyst 8500 CSR

Feature Set	12.0(13)W5(19c)	12.0(13) W5(19a)	12.0(13)W5(19)	12.0(10) W5(18c)	12.0(10) W5(18b)	12.(5) W5(13d)	12.0(5) W5(13b)	12.0(5) W5(13)	12.0(4a) WX5(11a)	12.0(1a) W5(6f)

Layer 2 transparent bridging	x	x	x	x	x	x	x	x	x	x
Layer 2 MAC learning, aging, and switching by hardware	x	x	x	x	x	x	x	x	x	x
Spanning Tree Protocol (IEEE 802.1d) support per bridge group	x	x	x	x	x	x	x	x	x	x
Spanning Tree SNMP trap support	x	x	x	x
Maximum of 64 active bridge groups									x	x
Maximum of 128 active bridge groups	x	x	x	x	x	x	x	x
Integrated routing and bridging (IRB)	x	x	x	x	x	x	x	x	x	x
Route processor redundancy¹	x	x	x	x	x	x	x	x
Inter-Switch Link (ISL)-based VLAN trunking	x	x	x	x	x	x	x	x	x	x
802.1Q-based VLAN routing/bridging	x	x	x	x	x	x	x	x	x
IP, IPX, and IP multicast routing and forwarding	x	x	x	x	x	x	x	x	x	x
IP fragmentation support for POS/ATM uplink	x	x	x	x
AppleTalk 1 and 2 routing	x	x	x	x	x	x	x	x	x
Constrained multicast flooding (CMF)	x	x	x	x	x	x	x	x	x	x
Up to 128 IP multicast groups	x	x	x	x	x	x	x	x	x
IP multicast routing with up to 12,000 groups (S, G)	x	x	x	x	x	x	x	x
QoS-based forwarding based on IP precedence	x	x	x	x	x	x	x	x	x	x
Load balancing among two equal-cost paths based on source and destination IP and IPX addresses	x	x	x	x	x	x	x	x	x	x
Up to six equal-cost paths for IP and IPX; per-packet load balancing for IPX	x	x	x	x
BGP (Border Gateway Protocol)	x	x	x	x	x	x	x	x
RIP and RIP II (Routing Information Protocol)	x	x	x	x	x	x	x	x	x	x
IGRP (Interior Gateway Routing Protocol)	x	x	x	x	x	x	x	x	x	x
EIGRP (Enhanced Interior Gateway Routing Protocol)	x	x	x	x	x	x	x	x	x	x
OSPF (Open Shortest Path First)	x	x	x	x	x	x	x	x	x	x
Routing protocol MIB support (OSPF, BGP)	x	x	x	x
IPX (Internet Packet Exchange) RIP and EIGRP	x	x	x	x	x	x	x	x	x	x
PIM (Protocol Independent Multicast)—sparse and dense modes	x	x	x	x	x	x	x	x	x	x
RTMP (AppleTalk Routing Table Maintenance Protocol)	x	x	x	x	x	x	x	x	x
AURP (AppleTalk Update-based Routing Protocol)	x	x	x	x	x	x	x	x	x
Secondary addressing	x	x	x	x	x	x	x	x	x	x
Static routes	x	x	x	x	x	x	x	x	x	x
Classless Interdomain Routing (CIDR)	x	x	x	x	x	x	x	x	x	x
Bundling of up to four Fast Ethernet ports in a maximum of 56 FECs	x	x	x	x	x	x	x	x
Load sharing based on source and destination IP addresses of unicast packets	x	x	x	x	x	x	x	x	x	x
ISL trunking (routing/bridging)	x	x	x	x	x	x	x	x
ISL on the Fast EtherChannel	x	x		x	x	x	x	x	x	x
802.1Q routing/bridging on the Fast EtherChannel	x	x	x	x	x	x	x	x	x	x
Up to 56 active FEC and GEC port channels in one system	x	x	x	x	x	x	x	x	x	x
Up to 64 active FEC and GEC port channels in one system	x	x	x	x	x	x	x	x	x	x
Bundling of up to four Gigabit Ethernet ports	x	x	x	x	x	x	x	x	x	x
Two 1-port enhanced Gigabit Ethernet port adapters with built-in ACL functionality and 16, 64, or 256 KB of memory available for routing tables	x	x	x	x
MAC address filtering standard ACL	x	x	x	x	x	x	x	x	x	x
IP simple ACL (1-99, 1301-1999)	x	x	x	x	x	x	x	x
IP extended ACL (100-199, 2000-2699) TCP ACL based on TCP-precedence, TCP port number, TCP ToS, and TCP flags	x	x	x	x	x	x	x	x	x
IP extended ACL (100-199, 2000-2699) UDP ACL based on UPD port number	x	x	x	x	x	x	x	x	x
IP extended ACL (100-199, 2000-2699) ICMP ACL	x	x	x	x	x	x	x	x	x
IPX standard ACL (800-899) without source node	x	x	x	x	x	x	x	x	x
IOS ACL for control plane traffic (for example, route update filter)	x	x	x	x	x	x	x	x	x
Named ACL	x	x	x	x	x	x	x	x	x
BOOTP (Bootstrap Protocol)	x	x	x	x	x	x	x	x	x	x
CGMP (Cisco Group Management Protocol) server support	x	x	x	x	x	x	x	x	x	x
CDP (Cisco Discovery Protocol) support on Ethernet ports	x	x	x	x	x	x	x	x	x	x
DHCP (Dynamic Host Configuration Protocol) Relay	x	x	x	x	x	x	x	x	x	x
HSRP (Hot Standby Routing Protocol) over 10/100 Ethernet, Gigabit Ethernet, FEC, GEC, and BVI (Bridge-Group Virtual Interface)	x	x	x	x	x	x	x	x	x	x
ICMP (Internet Control Message Protocol)	x	x	x	x	x	x	x	x	x	x
IGMP (Internet Group Management Protocol)	x	x	x	x	x	x	x	x	x	x
IPX SAP (Internet Packet Exchange Service Advertisement Protocol) and SAP filtering	x	x	x	x	x	x	x	x	x	x
SNMP (Simple Network Management Protocol)	x	x	x	x	x	x	x	x	x	x
Maximum of 32 active bridge groups with BVI	x	x	x	x	x	x	x	x
Bundling of up to four Fast Ethernet ports in a maximum of 64 FECs	x	x	x	x	x	x	x	x	x	x
UDP (User Datagram Protocol) turbo flooding	x	x	x						x	x
802.1q-based VLAN routing support	x	x	x	x	x	x	x	x	x	x
Route filtering	x	x	x	x	x	x	x	x	x	x
ISL support on the GEC	x	x	x	x	x	x	x	x	x	x
802.1 routing support on the GEC	x	x	x	x	x	x	x	x	x	x
Group Virtual Interface (BVI)	x	x	x	x	x	x	x	x	x	x
Support for up to 200 IPX networks on interfaces and subinterfaces	x	x	x	x	x	x	x	x	x	x
1-port packet-over-SONET OC-12c uplink port adapter with built-in ACL functionality and a 1-port enhanced Gigabit Ethernet port adapter	x	x	x	x
IS-IS routing protocol	x	x	x	x
Switching database manager	x	x	x	x
ATM uplink: UNI 3.0	x	x	x	x
ATM uplink: UNI 3.1	x	x	x	x
ATM uplink: ILMI 3.1	x	x	x	x
ATM uplink: RFC 1483 for Bridging	x	x	x	x
ATM uplink: RFC for Routing (IP, IP multicast, IPX)	x	x	x	x
ATM uplink: RFC 1483 SVC support	x	x	x	x
ATM uplink: 13-bit virtual circuit number with up to 8K VCs	x	x	x	x
ATM uplink 4096 simultaneous SARs	x	x	x	x
ATM uplink: AAL 5	x	x	x	x
ATM uplink: F4 and F5 flows of OAM cells	x	x	x	x
ATM uplink: Traffic shaping	x	x	x	x
POS: RFC 1619 PPP over SONET/SDH	x	x	x	x
POS: RFC 1662 PPP in HDLC-like framing	x	x	x	x
POS: IP fragmentation for POS and ATM uplink	x	x	x	x
POS: SONET MIB as defined in RFC 1575	x	x	x	x
POS: Transparent Bridging (PPP/HDLC encapsulation)	x	x	x	x
POS: SPE payload scrambling	x	x	x	x
POS: SONET alarms (LOS, LOF, AIS, and RDI detection or reporting)	x	x	x	x
POS: Threshold Crossing Alerts for B1, B2, B3 with configurable thresholds	x	x	x	x
Online diagnostics providing the following types of tests: Access tests between the route processor and the ports Online insertion and removal (OIR) diagnostic tests Snake tests through the switch router to ensure connectivity between the ports	x	x	x

¹Route processor redundancy for the Catalyst 8540 CSR

Release Names, Versions, and Part Numbers

Table 5 lists the release names, versions, and part numbers used with the Catalyst 8500 CSR switch routers.

Table 5: Release Name to Version and Part Number Matrix for Catalyst 8500 CSR Switch Routers

Release Name	Release Version	Part Number for Catalyst 8540 CSR	Part Number for Catalyst 8510 CSR

W5-19c	12.0(13)W5(19c)	S854R3-12.0.13W	S851R3-12.0.13W
W5-19a	12.0(13)W5(19a)	—	S851R3-12.0.13W
W5-19	12.0(13)W5(19)	S854R3-12.0.13W	—
W5-18c	12.0(10)W5(18c)	S854R3-12.0.10	—
W5-18b	12.0(10)W5(18b)	—	S851R3-12.0.10
W5-13d	12.0(5)W5(13d)	S854R3-12.0.5MT	S851R3-12.0.5MT
W5-13b	12.0(5)W5(13b)	S854R3-12.0.5MT	S851R3-12.0.5MT
W5-13	12.0(5)W5(13)	S854R3-12.0.5W	S851R3-12.0.5W
WX5-11	12.0(4a)WX5(11a)	S854R3-12.0.4W	S851R3-12.0.4W
W5-6f	12.0(1a)W5(6f)	SRF-8540CSR2-0	SRF-8510CSR2-0

New and Changed Information

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.

Note Refer to the Release Notes for the Catalyst 8510 MSR and LightStream 1010 ATM Switch for Cisco IOS Release 12.0(13)W5(19c) and the Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(13)W5(19c) for new and changed information for the LightStream 1010 and Catalyst 8500 multiservice ATM switch router (MSR).

New Features in Release 12.0(13)W5(19c)

Catalyst 8540 CSR

No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19c).

Catalyst 8510 CSR

No new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(13)W5(19c).

New Features in Release 12.0(13)W5(19a)

Catalyst 8510 CSR

No new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(13)W5(19a).

New Features in Release 12.0(13)W5(19)

Catalyst 8540 CSR

The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19):

Online diagnostics on the route processor providing the following types of tests:

Access tests between the route processor and the ports
Online insertion and removal (OIR) diagnostic tests
Snake tests through the switch router to ensure connectivity between the ports

Catalyst 8510 CSR

Cisco IOS Release 12.0(13)W5(19) was deferred for the Catalyst 8510 CSR. See caveat CSCds85282 for further information on the deferment.

New Features in Release 12.0(10)W5(18c)

Catalyst 8540 CSR

The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(10)W5(18c):

Two-port enhanced Gigabit Ethernet interface module and software features
Packet-over-SONET uplink with enhanced Gigabit Ethernet interface module and software features
ATM uplink with enhanced Gigabit Ethernet interface module and software features

New Features in Release 12.0(10)W5(18b)

Catalyst 8510 CSR

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(10)W5(18b):

Access Control List (ACL) daughter card
ACL software features

New Features in Release 12.0(5)W5(13d)

No new features are available for Catalyst 8500 CSR in Cisco IOS Release 12.0(5)W5(13d).

New Features in Release 12.0(5)W5(13b)

Catalyst 8540 CSR

The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(5)W5(13b):

IPX cross encapsulation issue resolved
Port stuck recovery and trouble shooting
- added mechanism for debugging port stuck condition
- added mechanism to isolate stuck ports
- added mechanism for recovery from stuck port
Select bugs from IOS mainline

Catalyst 8510 CSR

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(5)W5(13b):

IPX cross encapsulation issue resolved
Select bugs from IOS mainline

New Features in Release 12.0(5)W5(13)

Catalyst 8540 CSR

The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(5)W5(13):

Route processor redundancy
BGPx4 routing protocol
IP multicast scalability
Bridging/IRB over 802.1Q
Support for 32 bridge groups with up to 128 interfaces within each bridge group
Support for the 1000BASE-ZX extended reach GBIC
On-line Insertion and Removal (OIR) for the eight-port Gigabit Ethernet interface module
AppleTalk support for the eight-port Gigabit Ethernet card

Catalyst 8510 CSR

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(5)W5(13):

BGPx4 routing protocol
IP multicast scalability
Bridging/IRB over 802.1Q
Support for 16 bridge groups with up to 32 interfaces within each bridge group
Support for the 1000BASE-ZX extended reach GBIC

New Features in Release 12.0(4a)WX5(11a)

Catalyst 8540 CSR

The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(4a)WX5(11a):

Eight-port Gigabit Ethernet interface module
Access Control List (ACL) daughter card
Support for 64K entry line cards
Support for Appletalk routing
SPF Neighbor Optimizations

Catalyst 8510 CSR

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(4a)WX5(11a):

Support for Appletalk routing
SPF Neighbor Optimizations

New Features in Release 12.0(1a)W5(6f)

Catalyst 8540 CSR

No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(1a)W5(6f).

Catalyst 8510 CSR

No new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(1a)W5(6f).

Caveats for Catalyst 8500 CSR

This section lists caveats for the Catalyst 8500 CSR by tracking number (DDTS #) and release number, and indicates whether the caveat has been corrected. An "O" indicates that the caveat is open in that release; a "C" indicates that the caveat is closed in that release.

Note Refer to the Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(13)W5(19) and Release Notes for the Catalyst 8510 MSR and LightStream 1010 STM Switch for Cisco IOS Release 12.0(13)W5(19a) for caveats for the Catalyst 8500 multiservice ATM switch router (MSR) and LightStream 1010 switch router.

Table 6 lists caveats for the Catalyst 8540 CSR. Table 7 lists caveats for the Catalyst 8510 CSR.

Table 6: Caveat Matrix for Catalyst 8540 CSR

DDTS #	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)

CSCds44073	C	O
CSCds42545	C	O
CSCds39323	C	O
CSCds38053	O	O
CSCds36571	C	O
CSCds35157	C	O
CSCds29865	O
CSCds29781	O
CSCds13037	C	C	C
CSCds12640	C	O
CSCds09613	C	O	O	O	O
CSCds09323	C
CSCds08999	O
CSCds04387	C	O
CSCds04747	C
CSCds00193	O
CSCdr93044	O	O
CSCdr91799	O	O
CSCdr91196	O	O
CSCdr91099	O	O
CSCdr86386	O
CSCdr86168	O	O
CSCdr83546	O	O
CSCdr83138	O	O
CSCdr82616	O	O
CSCdr82453	O	O
CSCdr80770	C	O
CSCdr80267	O	O
CSCdr80160	O	O
CSCdr77057	C	O
CSCdr76566	O
CSCdr75370	O	O
CSCdr74263	O	O
CSCdr72714	O	O
CSCdr71493	O	O
CSCdr70086		C	O	O	O
CSCdr69541	O	O
CSCdr69116	C	O
CSCdr69004	O
CSCdr68921	C	O
CSCdr67623	O	O
CSCdr61171		C	O	O	O
CSCdr58521	O
CSCdr56326	O
CSCdr54230	C
CSCdr54230	C
CSCdr52546	C	O
CSCdr52527	O
CSCdr48700	O	O
CSCdr48489				C	O
CSCdr46754	C
CSCdr44798		C	O	O	O
CSCdr43610	O
CSCdr43159				C	O
CSCdr38540	O
CSCdr38522	O	O
CSCdr35023	O	O
CSCdr34241	O
CSCdr32957	O
CSCdr29169	O
CSCdr23428		C	O	O	O
CSCdr22194	C	O
CSCdr16404		C	O	O	O
CSCdr13429	O	O
CSCdp94304	O	O
CSCdp94120	O	O	O	O	O
CSCdp91740	O	O
CSCdp91190	O	O	O	O	O	O
CSCdp90216	O	O	O	O	O
CSCdp86120					C	O
CSCdp82442					C	O
CSCdp81517					C	O
CSCdp80179					C	O
CSCdp77640					C	O
CSCdp77324					C	O
CSCdp77105					C	O
CSCdp76943					C	O
CSCdp72498					C	O
CSCdp70903					C	O
CSCdp70392					C	O
CSCdp70087					C	O
CSCdp69276					C	O
CSCdp66953					C	O
CSCdp66044					C	O
CSCdp65345		C	O	O	O
CSCdp64865					C	O
CSCdp61799					C	O
CSCdp61681					C	O
CSCdp60263					C	O
CSCdp59602	C	C	C	O	O	O
CSCdp57307					C	O
CSCdp55616	O
CSCdp54731	O
CSCdp54010					C	O
CSCdp53792	O	O	O	O	O	O
CSCdp53383	O	O	O	O	O	O
CSCdp53262	O	O	O	O	O	O
CSCdp52415		C	O	O	O
CSCdp52120		C	O	O	O	O
CSCdp51900	O	O
CSCdp49816	O	O	O	O	O	O
CSCdp49399					C	O
CSCdp48943	O	O	O	O	O	O
CSCdp48903					C	O
CSCdp39811	O
CSCdp39497					C	O
CSCdp34084	C	C
CSCdp33630	O	O	O	O	O	O
CSCdp30288	O
CSCdp29985	O	O
CSCdp29577	O	O	O	O	O	O
CSCdp28511	O	O
CSCdp27782	O	O
CSCdp27744	O	O
CSCdp27207	O	O
CSCdp27071	O	O
CSCdp27067	O	O
CSCdp27058	O	O
CSCdp24812	O	O	O	O	O	O
CSCdp22692	O	O	O	O	O	O
CSCdp21692	O	O
CSCdp20845					C	O
CSCdp14547		C	O	O	O	O	O	O
CSCdp14175	O	O	O	O	O	O
CSCdp07758					C	O
CSCdm95298		C	O	O	O
CSCdm92257	O	O	O	O	O	O
CSCdm91042							C	O
CSCdm88103							C	O
CSCdm86262							C	O
CSCdm84834							C	O
CSCdm84798							C	O
CSCdm76785						C	O
CSCdm75735						C	O
CSCdm73823						C	O
CSCdm71729						C	O
CSCdm68875	O	O	O	O	O	O	O
CSCdm68368						C	O
CSCdm64047						C	O
CSCdm62162						C	O
CSCdm58126	O	O	O	O	O	O	O
CSCdm57767						C	O
CSCdm57720						C	O
CSCdm57516						C	O
CSCdm52306						C	O
CSCdm50065						C	O
CSCdm43436								C
CSCdm39686								C
CSCdm34838						C	O	O
CSCdm33903						C	O
CSCdm33313						C	O	O
CSCdm31218						C	O	O
CSCdm25960		C	O	O	O
CSCdm20899	O	O	O	O	O	O	O	O
CSCdm13198						C	O

Table 7: Caveat Matrix for Catalyst 8510 CSR

DDTS #	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)

CSCds85282	C
CSCds44008	O
CSCds04747	C
CSCdr66855	O	O
CSCdr64482	O	O
CSCdr63428	O
CSCdr62978	O	O
CSCdr61171		C	O	O	O
CSCdr58338	O	O
CSCdr56798	O	O
CSCdr54230	C
CSCdr43159				C	O
CSCdr26204		C	O	O
CSCdp86120					C	O
CSCdp84968					C	O
CSCdp82442					C	O
CSCdp81517					C	O
CSCdp80179					C	O
CSCdp77640					C	O
CSCdp75662					C	O
CSCdp74432					C	O
CSCdp72498					C	O
CSCdp70087					C	O
CSCdp66533		C	O	O
CSCdp66044					C	O
CSCdp64865					C	O
CSCdp61799					C	O
CSCdp61681					C	O
CSCdp57307					C	O
CSCdp54010					C	O
CSCdp52147	O	O
CSCdp48903					C	O
CSCdp34836	O	O
CSCdp31976	O	O
CSCdp31368					C	O	O
CSCdp23213		O
CSCdp14004	O
CSCdm87397	O	O
CSCdm60387						C	O
CSCdm40533								C
CSCdm36648								C
CSCdm35971								C
CSCdm32706						C	O	O
CSCdm28633	O	O	O	O	O	O	O	O
CSCdm26948						C	O	O
CSCdm25943						C	O	O
CSCdk93048						C	O	O
CSCdk89275						C	O	O
CSCdk82832	O	O	O	O	O	O	O	O
CSCdk73492	O	O	O	O	O	O	O	O
CSCdk72837	O	O	O	O	O	O	O	O

Caveat Symptoms and Workarounds

This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8500 CSR.

CSCds85282

Power-on diagnostics hang, and the IOS is unable to boot, when ARM, Fast Ethernet, and OC-12 cards are all installed in the same chassis.

Symptom: Power-on diagnostics hang, and the IOS is unable to boot, when ARM, Fast Ethernet, and OC-12 cards are all installed in the same chassis.

Workaround: None.

CSCds44073

Enhanced two-port Gigabit Ethernet packets are not switched out of the default-route with no IP unreachable.

Symptom: Packets are not switched out of the default route when IP packets sent to an unknown destination are received at an Enhanced two-port Gigabit port with IP unreachable configured and adjacency of next-hop for default-route is not resolved.

Workaround: None.

CSCds44008

MAC address is not present in the CAM table on bridging tests.

Symptom: Under certain conditions, a Catalyst 8510 CSR might not have a certain MAC address in the CAM table. This would lead to flooding of Layer 2 traffic for a short time until the MAC addresses are learned.

Workaround: Issue clear bridge group command.

CSCds42545

Line protocol is down on encapsulation change when a force-link is used.

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 doesn't 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.

CSCds39323

Output truncated on show epc if-entry command

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.

Workaround: None.

CSCds38053

IP unreachable setting is not checked therefore traffic hits route processor.

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.

Workaround: None.

CSCds36571

Ports get stuck on bootup on a Gigabit interface.

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).

Workaround: None.

CSCds35157

Crash in reading get_pif_no function on ACL and POS tests.

Symptom: Crash after issuing a clear counters command in get_pif_no function.

Workaround: None.

CSCds29865

HSRP MAC is not programmed into patricia after link up on the eight-port Gigabit Ethernet interface module.

Symptom: When HSRP is running on the interface of the eight-port Gigabit Ethernet interface module, after remote link failure followed by link restoration HSRP connectivity might be disrupted.

Workaround: Configure another HSRP group with a higher number and move standby configuration to that new group.

CSCds29781

Incorrect output error counters on the Gigabit Ethernet interface.

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.

Workaround: None

CSCds13037

Route processor redundancy fails with a remove_conn_from_fabric error.

Symptom: A Catalyst 8540, which correctly boots as a fully redundant system, does not complete a route processor failover. The secondary route processor, as it resumes function of the primary after a failover displays the following error:

%Secondary route processor Detected

remove_conn_from_fabric: Error close party failed for ...

Workaround: None.

CSCds12640

MSR crashes when loading a CSR image because of the CES card present in the switch router.

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.

Workaround: None.

CSCds09613

IPX loadbalancing algorithm is restricted.

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.

CSCds09323

IP packets are sent over ATM router module to ATM with padding.

Symptom: Currently the ATM router module does not strip the Ethernet pad when switching data from Ethernet to ATM. This might occasionally lead to connectivity issues since some end systems do not expect to see the pad.

Workaround: None.

CSCds08999

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.

Workaround: None.

CSCds04387

IPX load balancing algorithm is restricted to two paths.

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.

CSCds04747

The switch router might be vulnerable to the successful prediction of TCP Initial Sequence Numbers.

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).

CSCds00193

The show interfaces command shows BW 100000 Kb after auto negotiating to 10 Mb.

Symptom: The ifSpeed is reported as 100MB even when the auto-negotiation results in 10MBit.

Workaround: None.

CSCdr93044

The Gigabit Ethernet port on the eight-port Gigabit Ethernet interface module in shutdown state comes up unshutdown after an online insertion and removal (OIR).

Symptom: The Gigabit Ethernet port on the eight-port Gigabit Ethernet interface module comes up as unshutdown after an OIR.

Workaround: None.

CSCdr91799

Forwarding large packets on the ATM uplink can cause a port to be stuck on the enhanced Gigabit Ethernet ports.

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.

CSCdr91196

Output rate display in show interface pos port is high.

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.

CSCdr91099

The IP default routing does not work when the POS interface is specified.

Symptom: The default network over POS link does not work when the outgoing interface is specified instead of the next-hop IP address.

Workaround: Specify the next-hop IP address.

CSCdr86386

BVI interface does not receive EIGRP hello packets.

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.

Workaround: None.

CSCdr86168

The system crashes when adding an interface with approximately 1k vc to a bridge-group.

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.

Workaround: None.

CSCdr83546

clear atm vc command does not work for VCDs greater than 4095.

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.

Workaround: None.

CSCdr83138

Source MAC address 0000.0000.0000. learned on enhanced Gigabit Ethernet ports.

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.

Workaround: None.

CSCdr82616

BROUTE-VC release/setup failure on OIR.

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.

Workaround: None.

CSCdr82453

Routing flag is not set after unconfiguring a bridge group on ATM uplink ports.

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.

CSCdr80770

Parallel paths are not always programmed in epif cam.

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.

CSCdr80167

A change in the standby MAC address is not reflected anywhere.

Symptom: If HSRP over BVI is configured and a standby MAC address is configured on the BVI, this MAC address will not be reflected in the patricia table of the interface.

Workaround: None.

CSCdr80267

HSRP: a change in the standby MAC address is not reflected anywhere.

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.

CSCdr80160

HSRP MAC address is retained even after it is removed from the port channel.

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.

Workarounds: Issue the shutdown and no shutdown commands, add an IP address, or add the MAC address to a bridge group to delete the entry.

CSCdr77057

IS-IS is not seeing clns neighbors.

Symptom: IS-IS over 1483 does not work because clns neighbors are not established. With the ATM uplink interface module, IS-IS works only when clns routing is enabled.

Workaround: None.

CSCdr76566

There is no support for SONET MIB objects in ATM uplink module.

Symptom: There is no support for SONET MIB objects in ATM uplink module.

Workaround: None.

CSCdr75370

BCAST VC=0 between two enhanced Gigabit interfaces.

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.

CSCdr74263

Same VLAN color is configurable in different bridge groups.

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.

Workaround: None.

CSCdr72714

00:02:08: %SYS-2-GETBUF: Bad getbuffer, bytes= -2008487331 Process= "Init", ipl= 0, 
pid= 2 -Traceback= 6006D014 6016239C 60335DE4 60335FB8 60336110 60336350 60029724 
60099364 60099350

Symptom: The message above might appear during bootup. The system recovers from this.

Workaround: None.

CSCdr71493

BVI MAC address is retained even after it is removed from the bridge group.

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.

CSCdr70086

IP adjacencies are not immediately updated.

Symptom: IP adjacencies are not immediately cleared from the Gigabit Ethernet interface module.

Workaround: None.

CSCdr69541

Display problems in show controllers xpif_port options.

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.

Workaround: None.

CSCdr69116

MAC addresses are missing when another link goes down on a two-port Gigabit Ethernet interface module.

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.

Workaround: None.

CSCdr69004

Enhanced two-port Gigabit Ethernet interface is up when no GBIC is present.

Symptom: When auto negotiation is disabled on an enhanced two-port Gigabit Ethernet port, it is up even if the GBIC is not present.

Workaround: None.

CSCdr68921

CSR image recognizes the ATM router module card.

Symptom: The CSR image recognizes the ATM router module and downloads the ATM router module uCode.

Workaround: None.

CSCdr67623

00:04:37: %ALIGN-3-CORRECT: Alignment correction made at 0x60674830 reading 
0x62017DB3
 00:04:37: %ALIGN-3-TRACE: -Traceback= 60674830 60674A90 600993A4 60099390 00000000 
00000000 00000000 00000000

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.

Workaround: None.

CSCdr66855

Two-port enhanced Gigabit Ethernet interface module does not come up when the system is booted.

Symptom: If the peer-device has a non-HP GBIC and is not seated properly, the "Optical Detect" LED will be OFF on this device.

Workaround: Issue the shutdown and no shutdown commands or reseat the GBICs after a power cycle.

CSCdr64482

Problem with GBIC SX with no negotiation auto.

Symptom: The 1000BASE-SX GBIC interface of a Catalyst 8540 CSR does not support the no negotiate auto mode when connected to a Catalyst 5500 with the same GBIC.

Workaround: None.

CSCdr63428

%IPC-5-NULL: Recd. msg Dest Port=0x0, seq = 3FF,ipc_process_message

Symptom: The above message might appear when booting the switch router with IPX traffic. The switch router will recover from this.

Workaround: None.

CSCdr62978

HSRP interface does not preempt after the shutdown and no shutdown commands are issued.

Symptom: An HSRP interface configured for "preempt" might not become active after reset. No error message is given.

Workaround: Set higher priority for "preempt" interfaces as a second decision instance.

CSCdr61171

Crash on an interface shutdown/no shutdown in process_handle_watchdog

Symptom: The system crashes after issuing the shutdown/no shutdown commands when the watchdog timer expires.

Workaround: None.

CSCdr58521

IP packets routed on point-to-point subinterfaces on the ATM uplink interface module are routed by the route processor.

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.

CSCdr58338

%LSS-4-INTERNAL_WARNING: lss_record_ri_ingress: Illegal channel %d

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.

Workaround: None.

CSCdr56798

Forwarding large packets on the ATM uplink can cause a port to be stuck on the enhanced Gigabit Ethernet ports.

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: None.

CSCdr56326

epc rel on the enhanced two-port Gigabit Ethernet interface module causes the ATM uplink enhanced Gigabit interface to hang.

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.

Workaround: None.

CSCdr54231

Symptom: Notifications sent or received are only visible if the debug ip bgp command is configured. This might limit the ability to diagnose problems.

Workaround: None.

CSCdr54230

BGP peers of the receiving border router might detect a mismatch in the code, and issue a notification message to reset their session.

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.

Workaround: None.

CSCdr52546

Reprogramming the switch processor(s) might crash the Catalyst 8540 CSR.

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.

Workaround: None.

CSCdr52527

There is no instance of ACL card in the MIB table.

Symptom: There is no instance of ACL card in the MIB table.

Workaround: None.

CSCdr48700

Loopback interfaces are not properly numbered.

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.

Workaround: None.

CSCdr46754

Fast Ethernet interface modules are not sending packets after encapsulation changes.

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.

Workaround: None.

CSCdr44798

Layer 3 traffic from the route processor does not pass through a blocked port on an 8-port Gigabit Ethernet interface module.

Symptom: Layer 3 traffic from the route processor does not pass through a blocked port on an 8-port Gigabit Ethernet interface module.

Workaround: None.

CSCdr48489

Cells might stick in switch fabric under heavy multicast traffic.

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.

CSCdr43610

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.

CSCdr43159

Some interfaces in the outgoing interface list of the IOS multicast table might not forward traffic.

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.

CSCdr38540

High route processor utilization on shutdown/no shutdown with a large numbers of VCs.

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.

Workaround: None.

CSCdr38522

Received malformed TLV.

Symptom: Sometimes the above message is seen.

Workaround: None.

CSCdr34241

Sync does not update the hostname or prompt on the redundant route processor.

Symptom: The prompt on the secondary route processor does not reflect the hostname of the switch router after a sync.

Workaround: None.

CSCdr35023

%LSS-7-INTERNAL_ASSERT: clear_conn_entry:: (swidb_p != NULL) Assertion Failure - File 
../ls-switching/lss_pm_api.c Line 1479
 -Process= "LSS IPmcast Process", ipl= 0, pid= 99
 -Traceback= 60553374 607A925C 607A9078 6085AC84 6066DA10 6066F880 606738D4 60674084 
60099224 60099210

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.

Workaround: None.

CSCdr32957

Enhanced two-port Gigabit Ethernet interface module ACL: Configuration allows MinAcl+AllOtherRegions > TotalTcam.

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:

ACL cannot be enabled on GigabitEthernet0/0/0 - insufficient TCAMAvailable: 24 
Configured for ACL: 2048 Use sdm access-list command to reconfig

Workaround: None.

CSCdr29169

Corrupt block prevents Catalyst 8540 CSR from booting.

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.

Workaround: None.

CSCdr23428

The eight-port Gigabit Ethernet interface module has incrementing SkIPC Rx failed counters.

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.

Workaround: None.

CSCdr22194

The existing configuration of two-port Gigabit Ethernet is lost when replaced by the enhanced two-port Gigabit Ethernet interface module.

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.

CSCdr26204

Area-range summary link-state advertisement (LSA) is stuck in the database.

Symptom: On an Catalyst 8540 MSR, running Cisco IOS image 12.0(4a)W5(11a), that is an ABR for multiple OSPF areas, if the area-range command is used, the summary LSA created might get stuck in the database and not be flushed after the command is removed.

Workaround: This condition is eliminated when either OSPF is restarted, or all the components of the summary are lost.

CSCdr16404

Redundant switch processor does not take over on a failure.

Symptom: The switch processor in standby mode does not take over when an active switch processor fails.

Workaround: None.

CSCdr14004

Symptom: In rare instances a Catalyst 8510CSR has taken a software forced crash at a program counter value of 0x6004A4D64 when running the 12.0(1a)W5(6f) IOS. Because the conditions which triggers this crash are not currently known, it is strongly advised that the router be configured to write a core dump should an instance happen.

Workaround: None.

CSCdr13429

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.

Workarounds: None.

CSCdp94304

IOS bridge table is not updated after the MAC address ages out Fast EtherChannel (FEC) members.

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.

CSCdp94120

uCode download can fail when the encapsulation is changed under heavy traffic.

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 uCode 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).

CSCdp91740

01:34:29: %TBRIDGE-4-GIANT: Giant received on Port-channel1, 1504 exceeds 1500 DA 
00d0.583f.1b47 SA 0090.214f.9047 [0x08004500]

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.

Workaround: None.

CSCdp91190

Bridging broken from native VLAN to port channel VLAN.

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.

CSCdp90216

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.

Workaround: None.

CSCdp86120

IPC not freed after continuous failure.

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.

CSCdp84968

Allocated VCs are not released if current VC leaf cannot be added.

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.

CSCdp82442

Addition of SR3 and SR5 to the show controller counters command.

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.

CSCdp81517

Inconsistency with IPX EIGRP.

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.

CSCdp80179

Commit new IPX cross encapsulation algorithm. Disable per packet load balancing.

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.

CSCdp77640

IPX node address of BVI interface becomes invalid.

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.

CSCdp77324

Online insertion and removal of the route processor does not work consistently.

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.

CSCdp75662

There are memory leaks when the process to enqueue message fails.

Symptom: There are memory leaks under certain conditions when the process to enqueue message fails.

Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.

CSCdp74432

The message memory is not freed if the packet buffer is exhausted.

Symptom: When buffer pool exhaustion happens under heavy stress and buffer allocation fails there is a leakage of memory because of queued messages.

Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.

CSCdp72498

BVI input queue gets wedged and blocks traffic on a bridge group.

Symptom: Under very specific traffic conditions, the input queue on the BVI interface might become wedged (that is, the input queue count is larger than the queue depth). This affects 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, this might be temporary. Or redesign the network (remove BVI).

CSCdp77105

The show functional-image-info command needs to be enhanced.

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.

CSCdp76943

Term length not working on the show switch fabric command.

Symptom: When you enter the show switch fabric command, the term length parameter does not limit the output screen log to one page.

Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.

CSCdp70903

Software forced crash: NP55_msc_purge_cid_cmd.

Symptom: The system sometimes crashes after seeing the following message:

ipc_ok2send: Not enough room on 0, 280

Workaround: Reboot the system.

CSCdp70392

There needs to be uCode for dumping register and packet buffers when a port is stuck.

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.

CSCdp70087

Spurious memory access error.

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.

CSCdp69276

With the eight-port Gigabit Ethernet interface module, spurious memory access occurs.

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.

Workaround: None.

CSCdp66953

Ping fails when changing the VLAN ID of a BVI 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.

CSCdp66044

Debugging aid needed when a port is stuck.

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.

CSCdp66533

Route connected to Ethernet interface is not installed.

Symptom: Connected route associated with Ethernet interface might be intermittently missing from routing table.

CSCdp65345

The system crashes upon route processor switchover.

Symptom: The image crashes when redundancy for the route processors is enabled.

Workaround: None.

CSCdp64865

The IPX routing flag is on even after the ipx down command is entered on an interface.

Symptom: When the ipx down command is entered, the IPX routing flag is still on.

Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.

CSCdp61799

The system crashed after failing to queue IPC messages.

Symptom: Under high traffic conditions the system crashed after failing to queue IPC messages.

Workaround: Reboot the system.

CSCdp61681

The show controllers output should be more descriptive.

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.

CSCdp60263

Need a mechanism to troubleshoot and recover from stuck port failures.

Symptom: There is no mechanism to detect and recover from a stuck port failure.

Workaround: The following two commands were introduced in Cisco IOS Release 12.0(5)W5(13b) to address this caveat:

The epc port-reload global configuration command is used to enable resetting/reloading the Ethernet interfaces after detecting a stuck port.
The epc portstuck-wait seconds global configuration command is used to determine how long to wait before detecting a stuck port, from the time the symptom first occurs. The default is three minutes. The range for seconds is 0 to 1200. If a value of 0 is entered, a stuck port will not be detected.

CSCdp59602

Invalid configuration.

Symptom: The following configuration does not work on the 8-port Gigabit Ethernet module:

interface GigabitEthernet3/0/2.2
  encapsulation dot1Q 12 native
  no ip directed-broadcast
  bridge-group 2

Workaround: Reconfigure the 802.1Q VLAN as non-native.

CSCdp57307

FEC: The interface MAC address is not consistent with port-channel MAC address.

Symptom: A Cisco Catalyst 5000 might treat the link between the physical interface and the port channel interface as a multi-drop link when the MAC address of members of a port channel is different from the MAC address of the Port Channel (PO) itself.

Workaround: Delete the members of the port channel and then add them back.

CSCdp55616

After changing the port speed from 10 to 100 seconds, the change does not get updated until the shutdown and no shutdown commands are issued.

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).

Workaround: None.

CSCdp54731

Catalyst 8540 CSR FastEthernet ports that are in a shutdown state have incrementing packet output.

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.

CSCdp54010

Two-port Gigabit Ethernet counter problems are encountered on the show interfaces command for packet input.

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.

CSCdp53792

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.

CSCdp53383

MAC learning inconsistencies among FEC members after a host move.

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.

CSCdp53262

Under extreme conditions, MAC_learn IPC might be lost.

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.

CSCdp52147

Hold-queue size for port channels are defaulted to 75, but they need to be 300.

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.

Workaround: None.

CSCdp52120

INTERNAL ASSERT: lss_ipm_chk_shr_vc() Assertion failure

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.

CSCdp51900

Active router MAC is not removed when the member is removed from a bridge group.

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.

CSCdp49816

Invalid root tree pointer for an existing subinterface.

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.

CSCdp49399

Port stuck on reboot of connected Catalyst 8540 CSR with 70 percent Fast Ethernet wire rate traffic.

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.

CSCdp48943

Protocol specific IRB does not work for 802.1q bridge group members on an eight-port Gigabit Ethernet interface module.

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.

Workaround: None.

CSCdp48903

The show epc ipmcast command sometimes reports an incorrect value.

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.

CSCdp39811

HSRP configuration not removed on the enhanced two-port Gigabit Ethernet interface module after a card removal.

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.

CSCdp39497

Gigabit Ethernet interfaces were getting stuck because of corrupt applets.

Symptom: The CUBI was corrupting applets.

Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.

CSCdp34836

FEC missing MAC address in all members

Symptoms: Sometimes during FEC learning, entries might not be learned right away. During this 3-4 minute period there might be flooding. After that, the entries will be learned and packets will be switched.

Workaround: None.

CSCdp34084

Error messages on a Gigabit Ethernet interface module with the ACL during route processor switchover.

Symptoms: The following error messages might appear on the Gigabit Ethernet interface module with the ACL daughter card during a route processor switchover.

NO ACL Card Detected on the PAM in Slot[0]
FATAL ERROR: ACL-FPGA reset failed

Workaround: OIR the interface module.

CSCdp33630

Packets are switched out on native VLAN, leading to routing by the route processor with BVI.

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.

Workaround: None.

CSCdp31976

Vty session is not locked when switchover is in progress.

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.

CSCdp31368

The arp timeout interface command disappears after a system reload.

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.

CSCdp30288

Received malformed TLV.

Symptom: The above message is sometimes received. This message is can be ignored.

Workaround: None.

CSCdp29985

Route processor Red: SYS-3-route processor HOG Tbridge Monitor with traceback.

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.

Workaround: None.

CSCdp29577

Assigning the same 802.1q encapsulation on subinterfaces on the same slot on an 8-port Gigabit Ethernet does not always work.

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.

CSCdp28511

%SYS-3-INTPRINT: Illegal printing attempt from interrupt level.

-Process= "OIR Handler", ipl= 2, pid= 10

-Traceback= 600386C0 60038134 602C08BC 602BAEB4 602BA000 600B07F4 603BC180 603BBE80 
602C9B88 602C9CB8 60351A74 600976F4 600976E0

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.

Workaround: None.

CSCdp27782

redundancy prepare-for-cpu-removal command causes all messages in the buffer to be dumped.

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.

Workaround: None.

CSCdp27744

Running configuration takes 3 minutes to sync to secondary route processor.

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.

Workaround: None.

CSCdp27207

SYS-3-CPUHOG in Exec process with traceback on switch processor switchover.

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.

Workaround: None.

CSCdp27071

SYS-3-CPUHOG net background with traceback.

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.

Workaround: None.

CSCdp27067

SYS-3-CPUHOG EPAM Card Manager with traceback.

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.

Workaround: None.

CSCdp27058

INTERFACE_API-1-NOMORESWIDB: No more SWIDB - for the secondary route processor IDB.

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.

Workaround: None.

CSCdp24812

Ports are not recognized as OSPF interfaces after online insertion and removal (OIR).

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.

CSCdp23213

Invalid cell count after switch switchover.

Symptom: After a switch processor switchover, input/output packet counters have an invalid value.

Workaround: None.

CSCdp22692

Connected networks are not propagated through OSPF after online insertion and removal (OIR).

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.

CSCdp21692

Facility alarm does not show any warning when the secondary route processor is down.

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.

Workaround: None.

CSCdp20845

Under heavy stress conditions, VC allocation failed messages appear.

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.

CSCdp14547

A Gigabit Ethernet interface: Status down Broute VC-0

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.

CSCdp14175

Ports on the eight-port Gigabit Ethernet interface module cannot be configured for snooping other interfaces.

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.

CSCdp14004

Software forced crash at PC 0x600A4D64 (abort).

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.

Workaround: None.

CSCdp07758

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.

CSCdm95298

Cisco IOS does not support subinterfaces in conjunction with a DEC Spanning Tree.

Symptom: Bridging on a subinterface is only supported in conjunction with the IEEE Spanning Tree.

Workaround: None.

CSCdm92257

DECNET Bridging does not work over 8-port Gigabit Ethernet interfaces.

Symptom: 8-port Gigabit Ethernet interfaces cannot support bridging when the bridge group runs DECNET Spanning Tree.

Workaround: None.

CSCdm91042

Issuing a show subsystem command causes the router to crash with a bus error.

Symptom: When you issue a show subsystem command, the router returns a bus error and crashes.

Workaround: None.

CSCdm88103

AppleTalk MAC filter address is not programmed in bridge table.

Symptom: The router fails to see incoming AppleTalk broadcasts when the router, configured for IRB, is routing and bridging IP and just routing AppleTalk.

Workaround: None.

CSCdm87397

Syslog stops working on Ethernet 0 when logging source is removed.

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.

CSCdm86262

The Catalyst 8540 CSR crashes after exiting CLI configuration mode.

Symptom: The switch router crashes when you enter and exit configuration mode repeatedly and quickly.

Workaround: None.

CSCdm84834

AppleTalk routing fails when IP configured at Bridge-Group Virtual Interface (BVI).

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.

Workaround: None.

CSCdm84798

Bridging loops occur with Integrated Routing and Bridging (IRB).

Symptom: With IRB configured, bridging loops occur if there is a physical loop for the broadcast domain.

Workaround: None.

CSCdm76785

The clear bridge command does not reprogram MAC filter addresses.

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.

CSCdm75735

Adjacencies are made invalid regularly.

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.

Workaround: None

CSCdm73823

Online insertion and removal (OIR) of interface modules causes failures when multicast traffic is present.

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.

CSCdm71729

Bridge entries programmed as dirty when bridge aging-timer modified.

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.

CSCdm68875

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.

Workaround: None.

CSCdm68368

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.

CSCdm64047

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.

CSCdm62162

Packets leak after replacing an ACL with a new ACL.

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.

CSCdm60387

Blocked physical port shows learned entry.

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.

CSCdm58126

Major version mismatch between IOS and FPGA using the reprogram command.

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.

CSCdm57767

Cannot configure ACL on all subinterfaces.

Symptom: When configuring ACL on subinterface 1023 or above, the router returns the following message:

CARD:ERROR: access_list_add;Index allocation failed for lookuptype 2
CARD:ERROR: handle_addition:access_list_add failed:label 1, Fast Ethernet3/0/0.3 
LSS_ACL_AP_OUTPUT_ACL

Workaround: Limit the number of subinterfaces configured with ACL to 1000 for the switch router.

CSCdm57720

CDP fails on a Gigabit Ethernet port with trunking enabled.

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.

CSCdm57516

Cannot receive ARP packets correctly on 802.1Q encapsulated trunk connected to a 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.

CSCdm52306

Adjacency table not updated when the interface pointed to by a static route is changed.

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.

CSCdm50065

Online insertion and removal (OIR) is not supported for the 8-port Gigabit Ethernet interface module.

Symptom: When you insert an 8-port Gigabit Ethernet interface module while IOS is running, you see the following message:

Jul 15 11:33:31.528 pdt: %OIR-6-INSCARD: Card inserted in slot 12, subcard 1, 
interfaces administratively shutdown
Jul 15 11:33:31.788 pdt: %ATMSIG-3-FAILASSERT: Assertion failed: file 
"../-4k/alignment.c," line 897
 FALSE
 -Traceback= 6046FA4C 60096908 600971D4 600B1F10

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.

CSCdm43436

Incorrect CAM table entries might cause HSRP failures over a BVI interface.

Symptom: Incorrect MAC address entries in the CAM table might cause HSRP to fail over a BVI interface.

Workaround: None.

CSCdm40533

Device might lose IP OSPF neighbors and connectivity over BVI interfaces.

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.

Workaround: None.

CSCdm39686

IP routing might fail because of incorrect IP prefix entries in the CAM table.

Symptom: IP prefix entries in the CAM table might point to incorrect adjacency information, causing routing failure.

Workaround: None.

CSCdm36648

Device might lose IPX connectivity over a BVI interface.

Symptom: The device might lose IPX connectivity over a BVI interface, requiring the use of the clear ipx route* command to reestablish connectivity.

Workaround: None.

CSCdm35971

Subsequent IPX pings fail after a ping with a timeout value of zero.

Symptom: After executing an IPX ping with a timeout value of zero, subsequent IPX pings on the device will fail.

Workaround: None.

CSCdm34838

When topology changes occur, the IOS bridge table might become inconsistent.

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.

CSCdm33903

Node crash on TFTP boot.

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.

Workaround: None.

CSCdm33313

Interface level multicast control does not work if a BVI has no IP address.

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.

CSCdm32706

Large bridge group configurations with IRB lead to AAL5 buffer exhaustion.

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.

CSCdm31218

Interface MAC address change is not reflected in source MAC filtering.

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.

CSCdm28633

HSRP MAC appears as a REMOTE entry in the CAM table for an ACTIVE router.

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.

CSCdm26948

Removing adjacencies when bridge entry ages might lead to high route processor utilization.

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.

CSCdm25960

When the fiber port LXT97X is shut, it does not send correct link pulses.

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:

When the fiber ports on the Catalyst 8540 CSR and Catalyst 8510 CSR are connected, and the port on Catalyst 8540 CSR is shut, link flapping can occur on the Catalyst 8510 CSR fiber port.
When the fiber ports on two Catalyst 8540 CSRs are connected, link flapping can occur on the fiber port of one of the Catalyst 8540 CSRs when the fiber port on the other the Catalyst 8540 CSR is shut down.
When either a Catalyst 8540 CSR or a Catalyst 8510 CSR are connected to a Catalyst 5000, link flapping can occur on the fiber port of the Catalyst 5000 if it does not detect the shutdown on the fiber port of the Catalyst 8540 CSR or the Catalyst 8510 CSR.

Workaround: Change the hardware to send a constant signal (idle) when the port is shut.

CSCdm25943

CPUHOG messages appear on a 16 EtherChannel subinterface configuration.

Symptom: With 16 or more subinterfaces on a port channel, the following configuration might cause CPUHOG messages to appear:

[no] ip routing

[no] ipx routing

[no] bridge irb

[no] bridge-g [bridge-group-no]

Workaround: No workaround is needed; the route processor HOG messages should not affect the functionality of the device.

CSCdm20899

Gigabit Ethernet interface module port failure.

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.

CSCdm13967

%IPX-3-BADINSERT: Duplicate SAP entry insert attempted.

Symptom: The switch router returns a %IPX-3-BADINSERT message when a duplicate SAP entry is made.

Workaround: None.

CSCdm13198

Non RPF (reverse path forwarding) multicast traffic is forwarded to the route processor.

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.

Workaround: None.

CSCdk93048

Formatting information is lost if an IOS image is downloaded to slot 0.

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.

CSCdk89275

The show controllers command can bring down an interface.

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.

Workaround: None.

CSCdk82832

The scheduler allocate command is not supported on the Catalyst 8500 CSR.

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.

CSCdk73492

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.

CSCdk72837

The default spanning tree path cost is incorrect on Gigabit Ethernet interfaces.

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.

Restrictions

This section describes the following Catalyst 8500 CSR restrictions:

ACL Daughter Card Restrictions (Catalyst 8540 CSR)
AppleTalk Restrictions
VLAN Encapsulation Restrictions
EtherChannel Restrictions
Maximum Path Restriction for EIGRP or OSPF
Port Snooping Restrictions
Eight-Port Gigabit Ethernet Restrictions (Catalyst 8540 CSR)
Online Insertion and Removal of Interface Modules Restrictions
Online Diagnostics Restrictions
FPGA Upgrade Restriction
1000BASE-ZX GBIC Restriction
Bridge-Group Virtual Interface Restriction

ACL Daughter Card Restrictions (Catalyst 8540 CSR)

The following restrictions apply to the ACL daughter card supported on the Catalyst 8540 CSR:

The 8-port Gigabit Ethernet interface does not support an ACL daughter card.
UDP flooding is disabled on routers with an ACL daughter card.
The following ACLs are not supported with the ACL daughter card:
- ACL for GEC, FEC, or BVI
- Dynamic ACL
- Reflexive ACL
- IPX extended ACL
- ACL logging

AppleTalk Restrictions

We recommend that you evaluate the level of route processor utilization and performance in your switch router before turning on AppleTalk, particularly in a Catalyst 8510 CSR. Unlike IP and IPX, AppleTalk routing and processing in the Catalyst 8500 CSR 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 route processor 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 route processor processing power.

VLAN Encapsulation Restrictions

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.

EtherChannel Restrictions

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.

Maximum Path Restriction for EIGRP or OSPF

Catalyst 8500 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:

8500(config)# router eigrp 109

8500(config-router)# maximum-paths 2

Port Snooping Restrictions

The snooping source port and destination port cannot be the same port.
You can only snoop with one source port and one destination port.
Snooping configuration information is not saved in NVRAM.
You cannot snoop a port that is part of a bridge group.

Eight-Port Gigabit Ethernet Restrictions (Catalyst 8540 CSR)

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.

Ports Per Bridge Group Restrictions

The eight-port Gigabit Ethernet interface module installed in a Catalyst 8540 CSR can support a maximum of 128 ports per bridge group.

Port Channel Restrictions

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:

Port channel with ID > 56 cannot be created.

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.

Online Insertion and Removal of Interface Modules Restrictions

The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of interface modules on the Catalyst 8500 CSR:

Wait at least one minute after removing an interface module before inserting a new one.
While the device is operating, remove only one interface module at a time.
OIR of the eight-port Gigabit Ethernet interface module is supported in Cisco IOS Release 12.0(5)W5.13 and later releases.

Online Diagnostics Restrictions

Online diagnostics, such as access tests, online insertion and removal (OIR) tests, and snake tests, detect and report hardware failures in the Catalyst 8540 CSR 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:

The OIR tests support all Layer 3 interface modules, with the exception of the ATM uplink interface module and the eight-port Gigabit Ethernet interface module.

The snake test on the Catalyst 8540 CSR is supported on the enhanced Gigabit Ethernet interface module, the ATM uplink with enhanced Gigabit Ethernet interface module, and the Packet-over-SONET uplink with enhanced Gigabit Ethernet interface module. Snake tests are not supported on either the Fast Ethernet interface modules or the Gigabit Ethernet interface modules.

Note Access tests are supported on all Layer 3 interface modules. Refer to the " Configuring Online Diagnostics (Catalyst 8540 CSR)" section in the L ayer 3 Switching Software and Feature Configuration Guide for additional information.

FPGA Upgrade Restriction

On an 8540 CSR, the reprogram command for upgrading the FPGA on the switch processor requires power cycling the box after completing the FPGA download.

1000BASE-ZX GBIC Restriction

The Catalyst 8500 CSR switch routers support extra long haul (1000BASE-ZX) GBICs as follows:

Catalyst 8540 CSR: A maximum of 12 1000BASE-ZX GBICs per system to comply with FCC Class A emissions (CFR 47 Part 15), or 8 1000BASE-ZX GBICs per system to comply with EN55022 Class B emissions (CISPR22 Class B).
Catalyst 8510 CSR: Up to four 1000BASE-ZX GBICs in a total of four Gigabit Ethernet interface modules to comply with radiated emissions requirements.

Bridge-Group Virtual Interface Restriction

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.

Catalyst 8540 CSR Route Processor and Switch Module Redundancy

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.

Route Processor

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.

Switch Modules

If a Catalyst 8540 CSR 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.

Autonegotiation

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 8500 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:

(config-if)# speed 10

To set a port to 100 Mbps operation, issue the following command:

(config-if)# speed 100

To set the duplex value for a port to full-duplex, issue the following command:

(config-if)# duplex full

To set the duplex value for a port to half-duplex, issue the following command:

(config-if)# duplex half

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.

Interoperability

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:

Cisco IOS Release 12.0(4a)W5(11a) supports interoperability between CSR interface modules and MSR interface modules by way of the ATM router module on the Catalyst 8540 MSR running an MSR image.
Cisco IOS Release 12.0(10)W5(18b) supports interoperability between CSR interface modules and MSR interface modules by way of the ATM router module on the Catalyst 8510 MSR running an MSR image.

Incompatibility

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.

Y2K Compliance

The Catalyst 8540 CSR and 8510 CSR systems running Cisco IOS Release 12.0(0.6)W5(1) and later have been certified as Y2K Compliant. For more information, see the following URL: http://www.cisco.com/warp/public/752/2000/.

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Documentation CD-ROM

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 might be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/public/ordsum.html

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

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

We appreciate your comments.

Obtaining Technical Assistance

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

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:

http://www.cisco.com

Technical Assistance Center

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.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

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

Contacting TAC by Telephone

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.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Hierarchical Navigation

Cisco Catalyst 8500 Series Campus Switch Routers

Release Notes for the Catalyst 8540 CSR Cisco IOS Release 12.0(13)W5(19c)

Downloads

Table of Contents

Release Notes for the Catalyst 8500 CSR for Cisco IOS Release 12.0(13)W5(19c)