Table of Contents
Release Notes for the
Catalyst 8500 Campus Switch Router Cisco IOS Release 12.0
Release Notes for the
Catalyst 8500 Campus Switch Router Cisco IOS Release 12.0
September 9, 1999
This document provides the current Catalyst 8500 CSR software features and caveats for Cisco IOS Release 12.0(4a)WX5(11a).
This document contains the following sections:
We recommend that you read the following application notes before configuring your switch router:
The Catalyst 8500 CSR ships with an 8 MB systemcode Single In-Line Memory Module (SIMM) for the onboard Flash memory software image.
To download and store a copy of the Catalyst 8500 CSR software image, we recommend using a minimum 20 MB Flash PC Card. This 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. Detailed instructions can be found in the Layer 3 Switching Software Feature and Configuration Guide.
We strongly recommend that you use the latest available software release, which is currently Cisco IOS Release (4a), WX5 (11a), for all Catalyst 8500 campus switch router 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.
This section lists the Catalyst 8500 CSR software features.
| Layer 2 Bridging Features
|
|---|
Layer 2 transparent bridging
|
Layer 2 MAC learning, aging, and switching by hardware
|
Spanning-Tree Protocol (IEEE 802.1d) support per bridge group
|
Support for a maximum of 64 active bridge groups
|
Integrated routing and bridging (IRB) mode support
|
| Layer 3 Routing, Switching, and Forwarding Features
|
|---|
IP, IPX, and IP multicast routing and forwarding between Ethernet ports
|
AppleTalk 1 and 2 routing
Note See the "AppleTalk Restrictions" section.
|
CMF (constrained multicast flooding)
|
Up to 128 IP multicast groups
|
QoS-based forwarding based on IP precedence-based forwarding
|
Load balancing among equal-cost paths based on source and destination IP and IPX addresses
|
| Supported Routing Protocols
|
|---|
RIP and RIP II (Routing Information Protocol)
|
IGRP (Interior Gateway Routing Protocol)
|
EIGRP (Enhanced Interior Gateway Routing Protocol)
|
OSPF (Open Shortest Path First)
|
IPX (Internet Packet Exchange) RIP and EIGRP
|
PIM (Protocol Independent Multicast)—sparse and dense modes
|
RTMP (AppleTalk Routing Table Maintenance Protocol)
|
AURP (AppleTalk Update-based Routing Protocol)
|
Secondary addressing
|
Static routes
|
Classless Interdomain Routing (CIDR)
|
| Fast EtherChannel (FEC) Features
|
|---|
Bundling of up to four Fast Ethernet ports in a maximum of 64 FECs
|
Load sharing based on source and destination IP addresses of unicast packets
|
Load sharing for bridge traffic based on MAC address
|
ISL
|
802.1Q routing
|
Up to 64 active FEC and GEC port channels in one system
|
| Note See the "ACL Daughter Card Restrictions" section for restrictions on FEC.
|
| Gigabit EtherChannel (GEC) Features
|
|---|
Bundling of up to four Gigabit Ethernet ports
|
Load sharing based on source and destination IP addresses of unicast packets
|
Load sharing for bridge traffic based on MAC address
|
ISL
|
802.1Q routing
|
Up to 64 active FEC and GEC port channels in one system
|
| Note See the "ACL Daughter Card Restrictions" section for restrictions on GEC.
|
| Access Control Lists (ACL)
|
|---|
Layer 2 filtering:
- MAC address filtering standard ACL
|
Layer 3 filtering using an ACL daughter card:
- IP simple ACL (1-99, 1301-1999)
- IP extended ACL (100-199, 2000-2699)
- TCP ACL based on TCP-precedence, TCP port number, TCP ToS, and TCP flags
- UDP ACL based on UPD port number
- ICMP ACL
- IPX standard ACL (800-899) without source node
- IOS ACL for control plane traffic (for example, route update filter, etc.)
- Named ACL
Note The ACL daughter card is supported in the Fast Ethernet card 4.1 version and above, and the Gigabit Ethernet card 2.0 version and above. See the "ACL Daughter Card Restrictions" section.
|
| Additional Protocols Supported
|
|---|
BOOTP (Bootstrap Protocol)
|
CGMP (Cisco Group Management Protocol) server support
|
CDP (Cisco Discovery Protocol) support on Ethernet ports
|
DHCP (Dynamic Host Configuration Protocol) Relay
|
HSRP (Hot Standby Routing Protocol) over 10/100 Ethernet, Gigabit Ethernet, FEC, GEC, and BVI (Bridge-Group Virtual Interface)
|
ICMP (Internet Control Message Protocol)
|
IGMP (Internet Group Management Protocol)
|
IPX SAP (Internet Packet Exchange Service Advertisement Protocol) and SAP filtering
|
IRB (integrated routing and bridging) routing mode support
|
SNMP (Simple Network Management Protocol)
|
UDP (User Datagram Protocol) turbo flooding
Note See the "ACL Daughter Card Restrictions" section for restrictions on UDP flooding.
|
This section lists the Catalyst 8540 CSR caveats by release number and tracking number, and indicates whether or not the issue has been corrected. Caveats are referenced in the following tables:
- Table 1: Release 12.0(4a)WX5(11a)
- Table 2: Release 12.0 (4a) W5 (11)
- Table 3: Release 12.0 (1a) W5 (6f)
- Table 4: Release 12.0 (1a) W5 (6e)
- Table 5: Release 12.0 (1a) W5 (6b)
- Table 6: Release 12.0 (1.0) W5 (6a)
- Table 7: Release 12.0 (1.0) W5 (6)
- Table 8: Release 12.0 (0.16) W5 (4)
Table 1: Release 12.0(4a)WX5(11a) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdm13198
|
| X
|
CSCdm31218
|
| X
|
CSCdm33313
|
| X
|
CSCdm34838
|
| X
|
CSCdm50065
|
| X
|
CSCdm52306
|
| X
|
CSCdm57516
|
| X
|
CSCdm57720
|
| X
|
CSCdm57767
|
| X
|
CSCdm58126
|
| X
|
CSCdm62162
|
| X
|
CSCdm62325
|
| X
|
CSCdm64047
|
| X
|
CSCdm68368
|
| X
|
CSCdm68875
|
| X
|
CSCdm71729
|
| X
|
CSCdm73823
|
| X
|
CSCdm75735
|
| X
|
CSCdm76785
|
| X
|
CSCdm84798
| X
|
|
CSCdm84834
| X
|
|
CSCdm86262
| X
|
|
CSCdm88103
| X
|
|
CSCdm91042
| X
|
|
Table 2: Release 12.0 (4a) W5 (11) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdm13198
|
| X
|
CSCdm20899
| X
|
|
CSCdm31218
|
| X
|
CSCdm33313
|
| X
|
CSCdm34838
|
| X
|
CSCdm50065
|
| X
|
CSCdm52306
|
| X
|
CSCdm57516
|
| X
|
CSCdm57720
|
| X
|
CSCdm57767
|
| X
|
CSCdm58126
|
| X
|
CSCdm62162
|
| X
|
CSCdm62325
|
| X
|
CSCdm64047
|
| X
|
CSCdm68368
|
| X
|
CSCdm68875
|
| X
|
CSCdm71729
|
| X
|
CSCdm73823
|
| X
|
CSCdm75735
|
| X
|
CSCdm76785
|
| X
|
Table 7: Release 12.0 (1.0) W5 (6) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdk57012
| X
|
|
CSCdk57596
| X
|
|
CSCdk57611
| X
|
|
CSCdk58018
| X
|
|
CSCdk59851
| X
|
|
CSCdk59996
| X
|
|
CSCdk60346
| X
|
|
CSCdk61127
| X
|
|
CSCdk61567
| X
|
|
CSCdk62035
| X
|
|
CSCdk74612
|
| X
|
CSCdk74764
|
| X
|
CSCdk75694
|
| X
|
CSCdk76674
|
| X
|
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (4a) WX5 (11a) for the Catalyst 8540 CSR.
- Non RPF (reverse path forwarding) multicast traffic is forwarded to CPU.
- Symptom: High CPU utilization if multicast traffic is high. When PIM protocol is configured, non-RPF multicast traffic is forwarded to the CPU.
- Workaround: None
- Interface MAC address change is not reflected in source MAC filtering.
- Symptom: Changing the MAC address for a bridge group member causes CPU-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.
- 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 may not work.
- Workaround: Remove the interfaces from the bridge group and then add them back into the bridge group.
- When topology changes occur, the IOS bridge table may become inconsistent.
- Symptom: When an FEC is configured as a part of a bridge group and a topology change occurs, the bridge table may 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.
- OIR is not supported for the eight port Gigabit Ethernet line module.
- Symptom: When you insert an eight port Gigabit Ethernet line 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 "../src-4k/alignment.c", line 897
FALSE
-Traceback= 6046FA4C 60096908 600971D4 600B1F10
- The LED on the line module is orange and none of the interfaces will work. The line module is non-functional.
- Workaround: Reload the Cisco IOS software, and the line module will function. The LED should always be green when the eight port Gigabit Ethernet line module is functioning.
- 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.
- Cannot receive ARP packets correctly on 802.1Q encapsulated trunk connected to a
Catalyst 5000.
- Symptom: Two Catalyst 8540s 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.
- CDP fails on a Gigabit 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.
- 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.
- 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 may become unusable unless you update the IOS image.
- Workaround: Ignore this warning for the ACL card, and continue the FPGA download. Do not ignore the warning for other controllers.
- 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.
- Duplicate STANDBY IP address message once every 30 seconds
- Symptom: When parallel interfaces between two devices are part of a bridge group with HSRP configured on the BVI, the duplicate STANDBY IP address messages appear every 30 seconds.
- Workaround: None. This does not cause any problems with functionality.
- Symptom: IPX ACL on a subinterface of a non-trunk main interface does not filter traffic.
- Workaround: Configure the ACL on the main interface instead of the subinterface to achieve the same result. Due to space limitations, IPX ACL cannot be applied directly to a subinterface of a non-trunk main interface.
- Symptom: 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.
- 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 eight port Gigabit Ethernet line 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.
- 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.
- Online insertion and removal (OIR) of line modules causes failures when multicast traffic is present.
- Symptom: Following the online insertion of a line module into a router configured with IGMP static group and running multicast traffic, failures occur when downloading to the line module.
- Workaround: Either shut down any interface configured with IGMP static group before inserting or removing line modules; or do not insert or remove line modules online when the switch router is configured with IGMP static group.
- Adjacencies are made invalid regularly.
- Symptom: After an interface timeout is expired, adjacencies for static ARP entries are refreshed every minute, which may cause momentary connectivity loss. This does not apply to dynamically created adjacencies.
- Workaround: None
- 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: Doing a shut / no shut on the bridge port where the access list is configured reprograms the MAC address in all other bridge group members.
This section summarizes the caveats that were corrected in Cisco IOS Release 12.0 (4a) WX5 (11a) for the Catalyst 8540 CSR.
- Bridging Loops occur with Itegrated Routing and Bridging (IRB).
- Symptom: With IRB configured, bridging loops occur if there is a physical loop for the broadcast domain.
- This caveat has been corrected.
- 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.
- This caveat has been corrected.
- Crash after exiting CLI configuration mode on 8540CSR.
- Symptom: The router crashes when you enter and exit CLI configuration mode repeatedly and quickly.
- This caveat has been corrected.
- AppleTalk MAC filter address not programmed in bridge table.
- Symptom: Router fails to see incoming AppleTalk broadcasts when router, configured for IRB, is routing and bridging IP and just routing AppleTalk.
- This caveat has been corrected.
- Issuing a show subsystem command causes router to crash with a bus error.
- Symptom: When you issue a show subsystem command, the router returns a bus error and crashes.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (4a) W5 (11) for the Catalyst 8540 CSR.
- Non RPF (reverse path forwarding) multicast traffic is forwarded to CPU.
- Symptom: High CPU utilization if multicast traffic is high. When PIM protocol is configured, non-RPF multicast traffic is forwarded to the CPU.
- Workaround: None
- Interface MAC address change is not reflected in source MAC filtering.
- Symptom: Changing the MAC address for a bridge group member causes CPU-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.
- 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 may not work.
- Workaround: Remove the interfaces from the bridge group and then add them back into the bridge group.
- When topology changes occur, the IOS bridge table may become inconsistent.
- Symptom: When an FEC is configured as a part of a bridge group and a topology change occurs, the bridge table may 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.
- OIR is not supported for the eight port Gigabit Ethernet line module.
- Symptom: When you insert an eight port Gigabit Ethernet line 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 "../src-4k/alignment.c", line 897
FALSE
-Traceback= 6046FA4C 60096908 600971D4 600B1F10
- The LED on the line module is orange and none of the interfaces will work. The line module is non-functional.
- Workaround: Reload the Cisco IOS software, and the line module will function. The LED should always be green when the eight port Gigabit Ethernet line module is functioning.
- 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.
- Cannot receive ARP packets correctly on 802.1Q encapsulated trunk connected to a
Catalyst 5000.
- Symptom: Two Catalyst 8540s 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.
- CDP fails on a Gigabit 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.
- 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.
- 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 may become unusable unless you update the IOS image.
- Workaround: Ignore this warning for the ACL card, and continue the FPGA download. Do not ignore the warning for other controllers.
- 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.
- Duplicate STANDBY IP address message once every 30 seconds
- Symptom: When parallel interfaces between two devices are part of a bridge group with HSRP configured on the BVI, the duplicate STANDBY IP address messages appear every 30 seconds.
- Workaround: None. This does not cause any problems with functionality.
- Symptom: IPX ACL on a subinterface of a non-trunk main interface does not filter traffic.
- Workaround: Configure the ACL on the main interface instead of the subinterface to achieve the same result. Due to space limitations, IPX ACL cannot be applied directly to a subinterface of a non-trunk main interface.
- Symptom: 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.
- 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 eight port Gigabit Ethernet line 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.
- 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.
- Online insertion and removal (OIR) of line modules causes failures when multicast traffic is present.
- Symptom: Following the online insertion of a line module into a router configured with IGMP static group and running multicast traffic, failures occur when downloading to the line module.
- Workaround: Either shut down any interface configured with IGMP static group before inserting or removing line modules; or do not insert or remove line modules online when the switch router is configured with IGMP static group.
- Adjacencies are made invalid regularly.
- Symptom: After an interface timeout is expired, adjacencies for static ARP entries are refreshed every minute, which may cause momentary connectivity loss. This does not apply to dynamically created adjacencies.
- Workaround: None
- 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: Doing a shut / no shut on the bridge port where the access list is configured reprograms the MAC address in all other bridge group members.
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (4a) W5 (11) for the Catalyst 8540 CSR.
- Gigabit Ethernet line module port failure.
- Symptom: Under certain conditions, some Gigabit Ethernet line module ports will not come up.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6f) for the Catalyst 8540 CSR.
- Gigabit Ethernet line module port failure.
- Symptom: Under certain conditions, some Gigabit Ethernet line module ports will not come up.
- Workaround: If you observe this problem, you may need to upgrade your 10/100BaseT line module firmware. Contact your Cisco service representative for more information.
- Interface MAC address change is not reflected in SMF.
- Symptom: Changing the MAC address for a bridge group member causes CPU-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.
- 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 may not work.
- Workaround: Remove the interfaces from the bridge group and then add them back into the bridge group.
- When topology changes occur, the IOS bridge table may become inconsistent.
- Symptom: When a FEC is configured as a part of a bridge group and a topology change occurs, the bridge table may 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.
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (1a) W5 (6f) for the Catalyst 8540 CSR.
- IP routing may fail due to incorrect IP prefix entries in the CAM table.
- Symptom: IP prefix entries in the CAM table may point to incorrect adjacency information, causing routing failure.
- This caveat has been corrected.
- Incorrect CAM table entries may cause HSRP failures over a BVI interface.
- Symptom: Incorrect MAC address entries in the CAM table may cause HSRP to fail over a BVI interface.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6e) for the Catalyst 8540 CSR.
- Gigabit Ethernet line module port failure.
- Symptom: Under certain conditions, some Gigabit Ethernet line module ports will not come up.
- Workaround: If you observe this problem, you may need to upgrade your 10/100BaseT line module firmware. Contact your Cisco service representative for more information.
- Interface MAC address change is not reflected in SMF.
- Symptom: Changing the MAC address for a bridge group member causes CPU-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.
- 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 may not work.
- Workaround: Remove the interfaces from the bridge group and then add them back into the bridge group.
- When topology changes occur, the IOS bridge table may become inconsistent.
- Symptom: When a FEC is configured as a part of a bridge group and a topology change occurs, the bridge table may 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.
This section summarizes the caveat that was corrected in Cisco IOS Release 12.0 (1a) W5 (6b) for the Catalyst 8540 CSR.
- Microcode does not download on some Gigabit Ethernet line modules.
- Symptom: If you are using the cat8540c-in-mz.120-1a.W5.6a.bin software image and you have any Gigabit Ethernet line modules installed, you may see the following error message:
GigabitEthernet9/0/0Line 550 enable_gigabit_mac : Write MII failed for GigabitEthernet9/0/0
- If you issue the show controller command, you may see the following error messages and 100% CPU utilization:
queue cell fail output port GigabitEthernet9/0/0 input vpi 0 input vci384
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6e) for the Catalyst 8540 CSR.
- Microcode does not download on some Gigabit Ethernet line modules.
- Symptom: If you are using the cat8540c-in-mz.120-1a.W5.6a.bin software image and you have any Gigabit Ethernet line modules installed, you may see the following error message:
GigabitEthernet9/0/0Line 550 enable_gigabit_mac : Write MII failed for GigabitEthernet9/0/0
- If you issue the show controller command, you may see the following error messages and 100% CPU utilization:
queue cell fail output port GigabitEthernet9/0/0 input vpi 0 input vci384
- Workaround: Remove the Gigabit Ethernet line module or upgrade to an image that contains the fix (cat8540c-in-mz.120-1a.W5.6b.bin).
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (1.0) W5 (6a) for the Catalyst 8540 CSR.
- IP-EIGRP cannot handle more than seven neighbors.
- Symptom: When a system has 2,000 static routes redistributing via EIGRP from either a router or another Catalyst 8540, then starts adding neighbors (on either a physical interface or a subinterface), EIGRP does not stabilize after six neighbors are added. The CPU utilization remains at 99%.
- This caveat has been corrected.
- IPX load balancing over GEC between and 8540 does not function correctly.
- Symptom: Following a reload on the Gigabit Ethernet module, the routing table address of the next hop gateway changes to zero, causing load balancing to fail on that port channel.
- This caveat has been corrected.
- Having 32 IPX/RIP neighbors causes high CPU utilization.
- Symptom: A system configured with 32 IPX/RIP neighbors shows over 90% CPU utilization.
- This caveat has been corrected.
- IPX over IRB packets are routed to the CPU, causing high utilization.
- Symptom: IPX packets coming in from a BVI interface and going out of a BVI interface on the Catalyst 8540 are routed to the CPU, causing high CPU utilization.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6e) for the Catalyst 8540 CSR.
- IP-EIGRP cannot handle more than seven neighbors.
- Symptom: When a system has 2,000 static routes redistributing via EIGRP from either a router or another Catalyst 8540, then starts adding neighbors (on either a physical interface or a subinterface), EIGRP does not stabilize after six neighbors are added. The CPU utilization remains at 99%.
- Workaround: Limit the number of IP-EIGRP neighbors to six or fewer.
- IPX load balancing over GEC between 8510 and 8540 does not function correctly.
- Symptom: Following a reload on the Gigabit Ethernet module, the routing table address of the next hop gateway changes to zero, causing load balancing to fail on that port channel.
- Workaround: Execute a shutdown and no shutdown command sequence on the affected port channel.
- Having 32 IPX/RIP neighbors causes high CPU utilization.
- Symptom: A system configured with 32 IPX/RIP neighbors shows over 90% CPU utilization.
- Workaround: Limit the number of IPX/RIP neighbors to 20 or fewer.
- IPX over IRB packets are routed to the CPU, causing high utilization.
- Symptom: IPX packets coming in from a BVI interface and going out of a BVI interface on the Catalyst 8540 are routed to the CPU, causing high CPU utilization.
- Workaround: Enter the clear ipx route * command.
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (1.0) W5 (6) for the Catalyst 8540 CSR.
- The device takes about 50 seconds to configure a subinterface on a Fast EtherChannel (FEC).
- Symptom: After configuring about 10 subinterfaces on a port channel, it takes about 50 seconds to configure each subinterface. This time increases with the addition of more subinterfaces.
- This caveat has been corrected.
- The copy tftpboot run command may time out, depending on the specific configuration.
- Symptom: After you execute a copy run tftp command and reload the system software, the copy tftp run command may abort with this message:
%Error reading tftp://172.20.46.50/vparames/sbr1_c84_01.config (Transfer aborted)
- This timeout happens when a system with a large number of ports tries to configure itself, and the tftp process times out before the end of the configuration is reached.
- This caveat has been corrected.
- Queue cell failure on a device with 150 multicast groups in 40 interfaces.
- Symptom: This error is generated when the number of entries added to the multicast groups and ports exceeds the limit of the memory on the line modules.
- This caveat has been corrected.
- EIGRP gets unstable with more than 10 neighbors (100% CPU utilization).
- Symptom: Route tables and ARP entries are programmed into each module port on the Catalyst 8540 CSR by means of LSIPC. When thousands of route or ARP entries are present, it temporarily causes 100% CPU utilization during route updates, ARP updates, or when commands like clear ip route, clear adjacency, or clear arp are issued.
- This caveat has been corrected.
- Some configuration commands may fail if a port is receiving 100% line-rate traffic.
- Symptom: If a port receives wirespeed traffic while configuration is in progress, the port may time out. This is due to lack of bandwidth on the outgoing side. The configuration commands work properly if up to 90% traffic is going through the port. Also, this in no way hampers your ability to configure the port first and then process wirespeed traffic through it.
- This caveat has been corrected.
- A fully populated Catalyst 8540 CSR (128 ports) does not stabilize with EIGRP or OSPF updates and wirespeed traffic being sent to all ports.
- Symptom: It can take 45 minutes for all interfaces to come up on a fully populated Catalyst 8540 CSR, and CPU utilization can remain close to 100% for up to 90 minutes. In some cases, the system may never stabilize at all.
- This caveat has been corrected.
- %DUAL-3-INTERNAL: IP-EIGRP 65535: Internal Error
- Symptom: This error is generated when the EIGRP process is disabled while the system is learning more than 4000 routes.
- This caveat has been corrected.
- Hidden EPC commands for multicast may fail for a system with 128 multicast groups.
- Symptom: When you run show commands, the system may crash with this message:
*** System received a Software forced crash ***
- This caveat has been corrected.
- A value greater than 180 seconds for the ip igmp query-interval command does not work.
- Symptom: PIM interfaces do not successfully join multicast groups if the ip igmp query-interval value is greater than 180 seconds.
- This caveat has been corrected.
- Bridging over ISL does not work if the encapsulation is changed.
- Symptom: If ISL encapsulation is configured, and the network administrator tries to change the encapsulation on one end of the link, bridging over the ISL stops working.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (0.16) W5 (4) for the Catalyst 8540 CSR.
- The device takes about 50 seconds to configure a subinterface on a Fast EtherChannel (FEC).
- Symptom: After configuring about 10 subinterfaces on a port channel, it takes about 50 seconds to configure each subinterface. This time increases with the addition of more subinterfaces.
- Workaround: Add all the VLANs to the configuration before putting the physical Fast Ethernet ports into a FEC. For example, first add the VLANs:
8540(config)# int port-channel 1
8540(config-if)# int port-channel 1.1
8540(config-if)# encapsulation isl 1
8540(config-if)# int port-channel 1.2
8540(config-if)# encapsulation isl 2
...
8540(config-if)# int port-channel 1.12
8540(config-if)# encapsulation isl 12
- Then put the physical interfaces into the FEC:
8540(config)# int fa0/0/0
8540(config-if)# channel-group 1
8540(config)# int fa0/0/1
8540(config-if)# channel-group 1
- You should not see any slowness if you add ISL VLANs before adding physical Fast Ethernet interfaces into a FEC.
- The copy tftpboot run command may time out, depending on the specific configuration.
- Symptom: After you execute copy run tftp and reload the system software, the copy tftp run command may abort with this message:
%Error reading tftp://172.20.46.50/vparames/sbr1_c84_01.config (Transfer aborted)
- This timeout happens when a system with a large number of ports tries to configure itself, and the tftp process times out before the end of the configuration is reached.
- Workaround: After reloading software, copy the configuration file from the tftp server to Flash memory (using, for example, the copy tftp slot0: command), then copy the configuration file from Flash memory to NVRAM with the copy slot0:filename run command.
- Multicast: queue cell failure on a device with 150 multicast groups in 40 interfaces.
- Symptom: This error is generated when the number of entries added to the multicast groups and ports exceeds the limit of the memory on the line modules.
- Workaround: Limit multicast groups to no more than 50. All 128 ports can participate in the multicast groups.
- EIGRP becomes unstable with more than 10 neighbors (100% CPU utilization).
- Symptom: Route tables and ARP entries are programmed into each module port on the Catalyst 8540 CSR by means of LSIPC. When thousands of route or ARP entries are present, it temporarily causes 100% CPU utilization during route updates, ARP updates, or when commands like clear ip route, clear adjacency, or clear arp are issued.
- Workaround: No workaround is necessary. CPU utilization returns to normal (1%) after a couple of minutes.
- Some configuration commands may fail if a port is receiving 100% line-rate traffic.
- Symptom: If a port receives wirespeed traffic while configuration is in progress, the port may time out. This is due to lack of bandwidth on the outgoing side. The configuration commands work properly if up to 90% traffic is going through the port. Also, this in no way hampers your ability to configure the port first and then process wirespeed traffic through it.
- Workaround: Enter port configuration commands when traffic is below 90% of wirespeed.
- A fully populated Catalyst 8540 CSR (128 ports) does not stabilize with EIGRP or OSPF updates and wirespeed traffic being sent to all ports.
- Symptom: It can take 45 minutes for all interfaces to come up on a fully populated Catalyst 8540 CSR, and CPU utilization can remain close to 100% for up to 90 minutes. In some cases, the system may never stabilize at all.
- Workaround: Decrease the traffic to 80% (80 Mbps) to all ports, and the system will come up. It takes about 20 minutes to populate all tables on a fully loaded system with 80% wire-rate traffic on all ports. The time to populate the tables decreases when the system has fewer line modules installed. The equivalent time for a system with two line modules is about four minutes.
- %DUAL-3-INTERNAL: IP-EIGRP 65535: Internal Error
- Symptom: This error is generated when the EIGRP process is disabled while the system is learning more than 4000 routes.
- Workaround: No workaround is necessary—it just takes longer for the system to learn the routes.
- Hidden EPC commands for multicast may fail for a system with 128 multicast groups.
- Symptom: When you run show commands, the system may crash with this message:
*** System received a Software forced crash ***
- Workaround: Use IOS commands like show ip mroute to debug multicast operation.
- A value greater than 180 seconds for the ip igmp query-interval command does not work.
- Symptom: PIM interfaces do not successfully join multicast groups if the ip igmp query-interval value is greater than 180 seconds.
- Workaround: For multicast groups, set the query interval to be less than 180 seconds. (The default value is 60 seconds.)
- Bridging over ISL does not work if the encapsulation is changed.
- Symptom: If an ISL encapsulation has been configured, and the network administrator tries to change the encapsulation on one end of the link, bridging over the ISL stops working.
- Workaround: First remove the subinterface, then add a new one with the required encapsulation.
This section lists the Catalyst 8510 CSR caveats by release number and tracking number, and indicates whether or not the issue has been corrected. Caveats are referenced in the following tables:
Table 9: Release 12.0 (4a) WX5 (11a) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdk72837
|
| X
|
CSCdk73492
|
| X
|
CSCdk82832
|
| X
|
CSCdk89275
|
| X
|
CSCdk93048
|
| X
|
CSCdm25943
|
| X
|
CSCdm26948
|
| X
|
CSCdm29063
|
| X
|
CSCdm32706
|
| X
|
CSCdm57687
|
| X
|
CSCdm60387
|
| X
|
Table 10: Release 12.0 (4a) WX5 (11) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdm13967
| X
|
|
CSCdk72837
|
| X
|
CSCdk73492
|
| X
|
CSCdk82832
|
| X
|
CSCdk89275
|
| X
|
CSCdk93048
|
| X
|
CSCdm25943
|
| X
|
CSCdm26948
|
| X
|
CSCdm28633
| X
|
|
CSCdm29063
|
| X
|
CSCdm32706
|
| X
|
CSCdm57687
|
| X
|
CSCdm60387
|
| X
|
Table 11: Release 12.0 (1a) W5 (6f) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdk72837
|
| X
|
CSCdk73492
|
| X
|
CSCdk82832
|
| X
|
CSCdk89275
|
| X
|
CSCdk93048
|
| X
|
CSCdm25943
|
| X
|
CSCdm26948
|
| X
|
CSCdm28633
|
| X
|
CSCdm29063
|
| X
|
CSCdm32706
|
| X
|
CSCdm35971
| X
|
|
CSCdm36648
| X
|
|
CSCdm40533
| X
|
|
Table 12: Release 12.0 (1a) W5 (6e) Caveat Reference
| DDTS Number
| Corrected
| Caveat
|
|---|
CSCdk72837
|
| X
|
CSCdk73492
|
| X
|
CSCdk77676
| X
|
|
CSCdk82832
|
| X
|
CSCdk86404
| X
|
|
CSCdk88347
| X
|
|
CSCdk89275
|
| X
|
CSCdk93048
|
| X
|
CSCdm25943
|
| X
|
CSCdm26948
|
| X
|
CSCdm28633
|
| X
|
CSCdm29063
|
| X
|
CSCdm32706
|
| X
|
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (4a) WX5 (11) for the Catalyst 8510 CSR.
- 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.
- CPUHOG message appears when activating OSPF on a large port channel configuration.
- Symptom: A CPUHOG 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.
- The scheduler allocate command is not supported on the Catalyst 8500 CSR.
- Symptom: Unpredictable results might occur if the CPU 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.
- The show controller command can bring down an interface.
- Symptom: Occasionally, the show controller <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.
- 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.
- CPUHOG messages appear on a 16 EtherChannel subinterfaces configuration.
- Symptom: With 16 or more subinterfaces on a port channel, the following configuration may 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 CPUHOG messages should not affect the functionality of the device.
- Removing adjacencies when bridge entry ages may lead to high CPU utilization.
- Symptom: Adjacencies are removed when a bridge table entry ages out. This causes traffic to be routed to the CPU, which may lead to high CPU utilization.
- Workaround: Set the ARP timeout value to be less than the bridge age timer.
- When a Fast EtherChannel is added to a bridge group, IOS does not program existing bridge group entries as REMOTE.
- Symptom: When a port channel is added to an existing bridge group, the IOS does not program the existing MAC addresses already in that bridge group as REMOTE entries in the newly added port channel members. This leads to the port channel members going out of sync with regard to the REMOTE entries, causing flooding in one direction.
- Workaround: None.
- 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 may lead to high CPU 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 may need to increase the number of buffers on the device using the aal5 buffers command.
- Missing MAC addresses in IOS bridge table with PO as a BG member.
- Symptom: Some MAC addresses don't appear in the IOS bridge table for a bridge group that has a port-channel as a member. This occurs when the device is learning more than 3000 MAC addresses.
- Workaround: None.
- Blocked physical port shows learned entry.
- Symptom: On a router with a rev-B1 EPIF, 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 EPIF later than rev-B1.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (4a) WX5 (11) for the Catalyst 8510 CSR.
- 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.
- CPUHOG message appears when activating OSPF on a large port channel configuration.
- Symptom: A CPUHOG 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.
- The scheduler allocate command is not supported on the Catalyst 8500 CSR.
- Symptom: Unpredictable results might occur if the CPU 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.
- The show controller command can bring down an interface.
- Symptom: Occasionally, the show controller <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.
- 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.
- CPUHOG messages appear on a 16 EtherChannel subinterfaces configuration.
- Symptom: With 16 or more subinterfaces on a port channel, the following configuration may 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 CPUHOG messages should not affect the functionality of the device.
- Removing adjacencies when bridge entry ages may lead to high CPU utilization.
- Symptom: Adjacencies are removed when a bridge table entry ages out. This causes traffic to be routed to the CPU, which may lead to high CPU utilization.
- Workaround: Set the ARP timeout value to be less than the bridge age timer.
- When a Fast EtherChannel is added to a bridge group, IOS does not program existing bridge group entries as REMOTE.
- Symptom: When a port channel is added to an existing bridge group, the IOS does not program the existing MAC addresses already in that bridge group as REMOTE entries in the newly added port channel members. This leads to the port channel members going out of sync with regard to the REMOTE entries, causing flooding in one direction.
- Workaround: None.
- 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 may lead to high CPU 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 may need to increase the number of buffers on the device using the aal5 buffers command.
- Missing MAC addresses in IOS bridge table with PO as a BG member.
- Symptom: Some MAC addresses don't appear in the IOS bridge table for a bridge group that has a port-channel as a member. This occurs when the device is learning more than 3000 MAC addresses.
- Workaround: None.
- Blocked physical port shows learned entry.
- Symptom: On a router with a rev-B1 EPIF, 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 EPIF later than rev-B1.
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (4a) WX5 (11) for the Catalyst 8510 CSR.
- %IPX-3-BADINSERT: Duplicate SAP entry insert attempted.
- Symptom: Router returns a %IPX-3-BADINSERT message when a duplicate SAP entry is made.
- This caveat has been corrected.
- 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.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6f) for the Catalyst 8510 CSR.
- 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.
- CPUHOG message appears when activating OSPF on a large port channel configuration.
- Symptom: A CPUHOG 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.
- The scheduler allocate command is not supported on the Catalyst 8500 CSR.
- Symptom: Unpredictable results might occur if the CPU 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.
- The show controller command can bring down an interface.
- Symptom: Occasionally, the show controller <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.
- 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 device 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.
- CPUHOG messages appear on a 16 EtherChannel subinterfaces configuration.
- Symptom: With 16 or more subinterfaces on a port channel, the following configuration may 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 CPUHOG messages should not affect the functionality of the device.
- Removing adjacencies when bridge entry ages may lead to high CPU utilization.
- Symptom: Adjacencies are removed when a bridge table entry ages out. This causes traffic to be routed to the CPU, which may lead to high CPU utilization.
- Workaround: Set the ARP timeout value to be less than the bridge age timer.
- 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.
- When a Fast EtherChannel is added to a bridge group, IOS does not program existing bridge group entries as REMOTE.
- Symptom: When a port channel is added to an existing bridge group, the IOS does not program the existing MAC addresses already in that bridge group as REMOTE entries in the newly added port channel members. This leads to the port channel members going out of sync with regard to the REMOTE entries, causing flooding in one direction.
- Workaround: None.
- 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 may lead to high CPU 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 may need to increase the number of buffers on the device using the aal5 buffers command.
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (1a) W5 (6f) for the Catalyst 8510 CSR.
- 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.
- This caveat has been corrected.
- Device may lose IPX connectivity over a BVI interface.
- Symptom: The device may lose IPX connectivity over a BVI interface, requiring the use of the clear ipx route * command to reestablish connectivity.
- This caveat has been corrected.
- Device may lose IP OSPF neighbors and connectivity over BVI interfaces.
- Symptom: The device may lose its IP OSPF neighbor information and connections over a BVI interface after a few days of running, requiring a system reboot.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6e) for the Catalyst 8510 CSR.
- 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.
- CPUHOG message appears when activating OSPF on a large port channel configuration.
- Symptom: A CPUHOG 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.
- The scheduler allocate command is not supported on the Catalyst 8500 CSR.
- Symptom: Unpredictable results might occur if the CPU 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.
- The show controller command can bring down an interface.
- Symptom: Occasionally, the show controller <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.
- 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 8510 CSR device 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.
- CPUHOG messages appear on a 16 EtherChannel subinterfaces configuration.
- Symptom: With 16 or more subinterfaces on a port channel, the following configuration may 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 CPUHOG messages should not affect the functionality of the device.
- Removing adjacencies when bridge entry ages may lead to high CPU utilization.
- Symptom: Adjacencies are removed when a bridge table entry ages out. This causes traffic to be routed to the CPU, which may lead to high CPU utilization.
- Workaround: Set the ARP timeout value to be less than the bridge age timer.
- 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.
- When a Fast EtherChannel is added to a bridge group, IOS does not program existing bridge group entries as REMOTE.
- Symptom: When a port channel is added to an existing bridge group, the IOS does not program the existing MAC addresses already in that bridge group as REMOTE entries in the newly added port channel members. This leads to the port channel members going out of sync with regard to the REMOTE entries, causing flooding in one direction.
- Workaround: None.
- 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 may lead to high CPU 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 may need to increase the number of buffers on the device using the aal5 buffers command.
This section summarizes caveats that were corrected in Cisco IOS Release 12.0 (1a) W5 (6e) for the Catalyst 8510 CSR.
- Catalyst 8510 does not accept untagged frames for 802.1Q trunking.
- Symptom: When the Catalyst 8510 is configured with subinterfaces to use encapsulation dot1q <vlan-tag> trunking, the native VLAN assigned to the directly connected Catalyst switch (such as the Catalyst 4000 or Catalyst 5000), will not function. The Catalyst 8510 currently does not process untagged packets received on an 802.1Q trunked interface, so all packets are dropped.
- This caveat has been corrected.
- BVI does not forward packets after a node is moved.
- Symptom: When a node is moved to a different interface, the bridge-group virtual interface (BVI) does not forward packets intended for that node.
- This caveat has been corrected.
- The clear arp command does not delete adjacency entries.
- Symptom: The Catalyst 8510 CSR uses adjacency entries internally, so it does not zero out the MAC addresses for the corresponding IP addresses when clear arp is executed. This causes a problem if a MAC address corresponding to an IP address changes and the new host does not initiate an ARP request.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1a) W5 (6b) for the Catalyst 8510 CSR.
- 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.
- CPUHOG message appears when activating OSPF on a large port channel configuration.
- Symptom: A CPUHOG message appears when OSPF is activated on a port channel interface with more than 30 subinterfaces.
- Workaround: The operation will succeed even if this message appears. No action is necessary.
- Catalyst 8510 does not accept untagged frames for 802.1Q trunking.
- Symptom: When the Catalyst 8510 is configured with subinterfaces to use encapsulation dot1q <vlan-tag> trunking, the native VLAN assigned to the directly connected Catalyst switch (such as the Catalyst 4000 or Catalyst 5000), will not function. The Catalyst 8510 currently does not process untagged packets received on an 802.1Q trunked interface, so all packets are dropped.
- Workaround: Assign the native VLAN on the switch to a nonexistent VLAN number. Make sure that the sc0 interface is not part of this VLAN. For example, if VLAN 999 does not exist anywhere in the network, then create VLAN 999, and assign it as the native VLAN for the trunked port. (A native VLAN is the VLAN the port would be in when it is not trunking.) This can be verified by using the show port trunk <mod/num> command. Note that if the port is already trunking, the trunk must be brought down to change the native VLAN.
- The scheduler allocate command is not supported on the Catalyst 8500 CSR.
- Symptom: Unpredictable results might occur if the CPU 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.
- BVI does not forward packets after a node is moved.
- Symptom: When a node is moved to a different interface, the bridge-group virtual interface (BVI) does not forward packets intended for that node.
- Workaround: Execute a shutdown and no shutdown command sequence on the affected BVI interface.
- The clear arp command does not delete adjacency entries.
- Symptom: The Catalyst 8510 CSR uses adjacency entries internally, so it does not zero out the MAC addresses for the corresponding IP addresses when clear arp is executed. This causes a problem if a MAC address corresponding to an IP address changes and the new host does not initiate an ARP request.
- Workaround: Execute the clear adjacencies command following clear arp to clear aged ARP entries in the adjacency table.
This section describes the caveat that was corrected in Cisco IOS Release 12.0 (1a) W5 (6b) for the Catalyst 8510 CSR.
- Microcode does not download on some Gigabit Ethernet line modules.
- Symptom: If you are using the cat8510c-in-mz.120-1a.W5.6a.bin software image and you have any Gigabit Ethernet line modules installed, you may see the following error message:
GigabitEthernet0/0/0Line 550 enable_gigabit_mac : Write MII failed for GigabitEthernet0/0/0
- If you issue the show controller command, you may see the following error messages and 100% CPU utilization:
queue cell fail output port GigabitEthernet0/0/0 input vpi 0 input vci384
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1.0) W5 (6a) for the Catalyst 8510 CSR.
- 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.
- CPUHOG message appears when activating OSPF on a large port channel configuration.
- Symptom: A CPUHOG message appears when OSPF is activated on a port channel interface with more than 30 subinterfaces.
- Workaround: The operation will succeed even if this message appears. No action is necessary.
- Catalyst 8510 does not accept untagged frames for 802.1Q trunking.
- Symptom: When the Catalyst 8510 is configured with subinterfaces to use encapsulation dot1q <vlan-tag> trunking, the native VLAN assigned to the directly connected Catalyst switch (such as the Catalyst 4000 or Catalyst 5000), will not function. The Catalyst 8510 currently does not process untagged packets received on an 802.1Q trunked interface, so all packets are dropped.
- Workaround: Assign the native VLAN on the switch to a nonexistent VLAN number. Make sure that the sc0 interface is not part of this VLAN. For example, if VLAN 999 does not exist anywhere in the network, then create VLAN 999, and assign it as the native VLAN for the trunked port. (A native VLAN is the VLAN the port would be in when it is not trunking.) This can be verified by using the show port trunk <mod/num> command. Note that if the port is already trunking, the trunk must be brought down to change the native VLAN.
- The scheduler allocate command is not supported on the Catalyst 8500 CSR.
- Symptom: Unpredictable results might occur if the CPU 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.
- BVI does not forward packets after a node is moved.
- Symptom: When a node is moved to a different interface, the bridge-group virtual interface (BVI) does not forward packets intended for that node.
- Workaround: Execute a shutdown and no shutdown command sequence on the affected BVI interface.
- The clear arp command does not delete adjacency entries.
- Symptom: The Catalyst 8510 CSR uses adjacency entries internally, so it does not zero out the MAC addresses for the corresponding IP addresses when clear arp is executed. This causes a problem if a MAC address corresponding to an IP address changes and the new host does not initiate an ARP request.
- Workaround: Execute the clear adjacencies command following clear arp to clear aged ARP entries in the adjacency table.
- Microcode does not download on some Gigabit Ethernet line modules.
- Symptom: If you are using the cat8510c-in-mz.120-1a.W5.6a.bin software image and you have any Gigabit Ethernet line modules installed, you may see the following error message:
GigabitEthernet0/0/0Line 550 enable_gigabit_mac : Write MII failed for GigabitEthernet0/0/0
- If you issue the show controller command, you may see the following error messages and 100% CPU utilization:
queue cell fail output port GigabitEthernet0/0/0 input vpi 0 input vci384
- Workaround: Remove the Gigabit Ethernet line module or upgrade to an image that contains the fix (cat8510c-in-mz.120-1a.W5.6b.bin).
This section describes the caveat that was corrected in Cisco IOS Release 12.0 (1.0) W5 (6a) for the Catalyst 8510 CSR.
- %ALIGN-3-CORRECT: Alignment correction made at 0x6017C6C4.
- Symptom: These alignment errors show up when a Telnet session is opened that uses TCP. The errors are harmless.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (1.0) W5 (6) for the Catalyst 8510 CSR.
- %ALIGN-3-CORRECT: Alignment correction made at 0x6017C6C4.
- Symptom: These alignment errors show up when a Telnet session is opened that uses TCP. The errors are harmless.
- Workaround: No action is necessary.
- 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.
- Catalyst 8510 does not accept untagged frames for 802.1Q trunking.
- Symptom: When the Catalyst 8510 is configured with subinterfaces to use encapsulation dot1q <vlan-tag> trunking, the native VLAN assigned to the directly connected Catalyst switch (such as the Catalyst 4000 or Catalyst 5000), will not function. The Catalyst 8510 currently does not process untagged packets received on an 802.1Q trunked interface, so all packets are dropped.
- Workaround: Assign the native VLAN on the switch to a nonexistent VLAN number. Make sure that the sc0 interface is not part of this VLAN. For example, if VLAN 999 does not exist anywhere in the network, then create VLAN 999, and assign it as the native VLAN for the trunked port. (A native VLAN is the VLAN the port would be in when it is not trunking.) This can be verified by using the show port trunk <mod/num> command. Note that if the port is already trunking, the trunk must be brought down to change the native VLAN.
This section summarizes the caveats that were corrected in Cisco IOS Release 12.0 (1.0) W5 (6) for the Catalyst 8510 CSR.
- CPU HOG messages appear after a shutdown and no shutdown command sequence on an interface.
- Symptom: CPU HOG messages appear if more than 1,024 routes are tied to an interface when you shut it down. Because of the large number of routes, the CPU is occupied by the IPX process longer than normal.
- This caveat has been corrected.
- Port stuck messages are received while bridging at line rate on a 10/100 Mbps line module when the CAM memory is full.
- Symptom: If Smartbits is used to run bridging, and the VFD2 Setup is set to infinitely increment source MAC addresses, this fills the bridging table (in CAM). This can cause numerous problems, including ports getting stuck.
- This caveat has been corrected.
- Spurious INTERNAL_ASSERT messages appear when the system boots.
- Symptom: These messages are produced by the Cisco IOS Release 12.0 (0.6) W5 (1) boot loader.
- This caveat has been corrected.
- CPU utilization is very high (up to 100%) for no obvious reason.
- Symptom: Certain types of traffic, including routing protocol updates and traffic terminating at the switch route processor, can generate extremely high CPU traffic.
- This caveat has been corrected.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (0.16) W5 (3) for the Catalyst 8510 CSR.
- CPU HOG messages appear after performing a shutdown and no shutdown command sequence on an interface.
- Symptom: If more than 1,024 routes are tied to one interface, shutting down the interface might cause a CPU HOG message to appear. This means that the CPU is occupied by the IPX process longer than the normal time because of the large number of routes.
- Workaround: No action is necessary.
- Port stuck messages are received while bridging at line rate on a 10/100 Mbps line module when the CAM memory is full.
- Symptom: If Smartbits is used to run bridging, and the VFD2 Setup is set to infinitely increment source MAC addresses, this fills the bridging table (in CAM). This can cause numerous problems, including ports getting stuck.
- Workaround: Do not configure VFD2 Setup to infinitely increment source MAC addresses.
- Spurious INTERNAL_ASSERT messages appear at boot.
- Symptom: These messages are produced by the Cisco IOS Release 12.0 (0.6) W5 (1) boot loader.
- Workaround: Use the current image, Cisco IOS Release 12.0 (0.6) W5 (3).
- CPU utilization is very high (up to 100%) for no obvious reason.
- Symptom: Certain types of traffic, including routing protocol updates and traffic terminating at the switch route processor, can generate extremely high CPU traffic.
- Workaround: None.
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0 (0.16) W5 (2) for the Catalyst 8510 CSR.
- The no interface port-channel channel-id command is not enabled. Hence, a port-channel interface cannot be deconfigured once it is configured and saved in NVRAM.
- Workaround: None.
- Occasionally, when you issue the shutdown/no shutdown command sequence on an interface, the interface remains in the down state.
- Workaround: To recover the link, issue the shutdown/no shutdown command
sequence again.
- The show interface command displays an inaccurate number of packets dropped.
- Symptom: The number displayed indicates the number of times the input buffer has exceeded its threshold rather than the number of packets lost.
- Workaround: None
- ICMP redirect messages are not generated.
- Symptom: ICMP redirects are generated when a received IP packet is routed on to the same interface or subinterface on which the packet was received and the destination IP address belongs to the same subnet as its next-hop gateway.
- Workaround: None.
- Intermittent failure when saving a very large configuration file to NVRAM.
- Symptom: When you have a configuration file that is larger than 128 KB, attempting to save the file into NVRAM may cause the system to fail. This is an intermittent and nonreproducible bug.
- Workaround: As a precautionary measure, do not copy configuration files that are larger than 128 KB into NVRAM. Instead, copy these files into Boot Flash memory or a Flash memory card (slot 0: or slot 1:).
This section summarizes the caveats that were corrected in Cisco IOS Release 12.0 (0.16) W5 (2) for the Catalyst 8510 CSR.
- An IP multicast TTL threshold will have no effect on a port-channel interface with an ISL encapsulation. Hence, the IP multicast TTL threshold is not analyzed and the packet is forwarded.
- This caveat has been corrected.
- HSRP state transition messages are displayed when issuing the clear IP route * command.
- Symptom: If you have HSRP configured and you issue a clear IP route * command on an active router with approximately 5,000 routes in its routing tables, you might receive HSRP state transition messages that the process is taking too much CPU processing power.
- This caveat has been corrected.
- Issuing a clear ip route network command deletes routes to directly connected networks.
- Workaround: From interface configuration mode, issue a no shut command on the indicated directly connected interface. When you then issue a show ip route command, you can see that the route to the directly connected network is restored.
- This caveat has been corrected.
- The Cisco Discovery Protocol (CDP) does not work when Inter-Switch Link (ISL) over Fast EtherChannel (FEC) is configured on the system.
- Symptom: If you have CDP configured on a FEC interface that has ISL configured on it, you cannot see the neighbor information when you issue a show cdp neighbor command.
- This caveat has been corrected.
This section summarizes the caveats that were corrected in Cisco IOS Release 12.0 (0.6) W5 (1) for the Catalyst 8510 CSR.
- Interval required to hot swap Ethernet line modules.
- Symptom: When hot swapping an Ethernet line module without waiting for a 10-second interval, the line module does not initialize properly.
- This caveat has been corrected.
- Warning message when issuing the clear IP route command.
- Symptom: If the Catalyst 8510 system has more than 1,024 routes in its routing tables when you issue a clear ip route command, you receive a warning message that the process is taking too much CPU (switch route processor [SRP]) processing power.
- This caveat has been corrected.
- Warning message when issuing the ospf disable command.
- Symptom: If you have the OSPF (Open Shortest Path First) protocol enabled and issue
an ospf disable command, you receive a warning message that the OSPF process is taking too much CPU (SRP) processing power.
- This caveat has been corrected.
- Interface packet counter incorrectly doubling packet count.
- Symptom: In some cases, the interface packet counter counts each terminating IP packet (a packet sent to the SRP) twice. When you issue a show interface command, the reported number of total packets received is double the actual packet count.
- This caveat has been corrected.
This section describes the following Catalyst 8500 CSR restrictions:
The eight-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
We recommend that you evaluate the level of CPU 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 CPU utilization, turning on AppleTalk could result in longer convergence times for routing protocols like EIGRP. AppleTalk packet throughput is dependent on the amount of available CPU processing power.
The four adjacent ports (such as 0-3 or 4-7) on a 10/100 interface must all use the same VLAN encapsulation, that is, either 802.1Q and native, or ISL and native.
When assigning Ethernet interfaces to an EtherChannel, all interfaces must be either Fast Ethernet or Gigabit Ethernet. You cannot mix Fast Ethernet and Gigabit Ethernet interfaces within a single EtherChannel.
Catalyst 8500 line 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
When configuring port snooping, or mirroring, the combined physical bandwidth of the source ports must not exceed the physical bandwidth of the destination port.
The snooping source port and destination port cannot be the same port.
The Catalyst 8540 CSR does not currently support the use of redundant route processors or switch modules. The route processor must be installed in slot 4, and two switch modules must be installed in slots 5 and 7. Additional route processors and/or switch modules installed in the chassis will not function.
The eight port Gigabit Ethernet line module can support a maximum of 24 ports per bridge group.
If your switch router has an eight port Gigabit Ethernet line 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 line module.
If your switch router does not have an eight port Gigabit Ethernet line module, you can assign port channel ID numbers up to 64.
The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of line modules on the Catalyst 8500 CSR:
- Do not remove (hot swap) the route processor or either switch module while the device is operational. The redundancy needed to support its removal is not available in this software release.
- Wait at least one minute after removing a line module before inserting a new one.
- Do not remove more than one line module at a time while the device is operational.
- OIR is not supported on the eight port Gigagit Ethernet line module (see CSCdm50065).
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.
The Catalyst 8540 CSR line modules can be used in a Catalyst 8540 MSR chassis, with an MSR route processor and switch modules. If you do this, you must use only CSR (Ethernet) line modules, and you must load the CSR software image on the MSR.
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/.
The following documents provide information related to Catalyst 8500 campus switch routers.
- Application Note: 8 Port Gigabit Ethernet Local Switching Line Card for the Catalyst 8540 CSR
- Application Note: ACL Daughter Card for the Catalyst 8500
- Quick Installation: Catalyst 8540 (http://www.cisco.com/mm/quickstart/8540/)
- Catalyst 8540 Chassis Installation Guide
- Catalyst 8540 Campus Switch Router Interface Module and Route Processor Installation Guide
- Quick Installation: Catalyst 8510 (http://www.cisco.com/mm/quickstart/8510/)
- Catalyst 8510 Chassis Installation Guide
- Catalyst 8510 Campus Switch Router Processor and Line Module Installation Guide
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
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.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Tue Sep 12 10:11:43 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
