Table of Contents
Release Notes for the Catalyst 8510 CSR Cisco IOS Release 12.0(10)W5(18b)
August 2, 2000
This document provides the current Catalyst 8510 campus switch router (CSR) software features and caveats for Cisco IOS Release 12.0(10)W5(18b). It also includes information on previous releases for the Catalyst 8540 CSR and the Catalyst 8510 CSR.
This document contains the following sections:
Table 1 lists the default Flash and DRAM memory for the Catalyst 8510 CSR and Catalyst 8540 CSR, as well as memory upgrade options.
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. Refer to the Layer 3 Switching Software Feature and Configuration Guide for more information.
Table 2 and Table 3 list the interface modules supported, their part numbers, and the minimum software versions required to use them. 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
| Part Description
| Part Number
| Minimum Software Version Required
|
|---|
| Route Processors, Switch Cards, and Daughter Cards
|
|
|
Route processor
| C8541CSR-RP=
| 12.0(1a)W5(6f)
|
Switch processor
| C8542CSR-SP=
| 12.0(1a)W5(6f)
|
ACL daughter card (Catalyst 8540 CSR)
| C8540-ACL=
| 12.0(4a)WX5(11a)
|
ACL daughter card (Catalyst 8510 CSR)
| C8510-ACL=
| 12.0(10)W5(18b)
|
| Gigabit Ethernet Interface Modules
|
|
8-port Gigabit Ethernet 64K
| C85GE-8X-64K=
| 12.0(4a)WX5(11a)
|
2-port Gigabit Ethernet 16K
| C85GE-2X-16K=
| 12.0(1a)W5(6f)
|
2-port Gigabit Ethernet 64K
| C85GE-2X-64K=
| 12.0(4a)WX5(11a)
|
2-port Gigabit Ethernet 16K with ACL
| C85GE-2XACL-16K=
| 12.0(4a)WX5(11a)
|
2-port Gigabit Ethernet 64K with ACL
| C85GE-2XACL-64K=
| 12.0(4a)WX5(11a)
|
| Fast Ethernet Interface Modules
|
|
16-port 10/100 UTP 16K
| C85FE-16T-16K=
| 12.0(1a)W5(6f)
|
16-port 10/100 UTP 64K
| C85FE-16T-64K=
| 12.0(4a)WX5(11a)
|
16-port 10/100 UTP 16K with ACL
| C85FE-16TACL-16K=
| 12.0(4a)WX5(11a)
|
16-port 10/100 UTP 64K with ACL
| C85FE-16TACL-64K=
| 12.0(4a)WX5(11a)
|
16-port 100-FX MT-RJ 16K
| C85FE-16F-16K=
| 12.0(1a)W5(6f)
|
16-port 100-FX MT-RJ 64K
| C85FE-16F-64K=
| 12.0(4a)WX5(11a)
|
16-port 100-FX MT-RJ 16K with ACL
| C85FE-16FACL-16K=
| 12.0(4a)WX5(11a)
|
16-port 100-FX MT-RJ 64K with ACL
| C85FE-16FACL-64K=
| 12.0(4a)WX5(11a)
|
Table 3: Catalyst 8510 CSR Interface Modules
| Part Description
| Part Number
| Minimum Software Version Required
|
|---|
| Gigabit Ethernet Interface Modules
|
|
1-port Gigabit Ethernet 16K
| C85GE-1X-16K=
| 12.0(1a)W5(6f)
|
1-port Gigabit Ethernet 64K
| C85GE-1X-64K=
| 12.0(1a)W5(6f)
|
| Fast Ethernet Interface Modules
|
|
8-port 10/100 RJ-45 16K
| C85FE-8T-16K=
| 12.0(1a)W5(6f)
|
8-port 10/100 RJ-45 64K
| C85FE-8T-64K=
| 12.0(1a)W5(6f)
|
8-port 100-FX MT-RJ 16K
| C85FE-8F-16K=
| 12.0(1a)W5(6f)
|
8-port 100-FX MT-RJ 64K
| C85FE-8F-64K=
| 12.0(1a)W5(6f)
|
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 on the World Wide Web at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/fpga_rel/index.htm
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 32 active bridge groups
|
Integrated routing and bridging (IRB) mode support
|
Virtual LAN (VLAN) Features
|
|---|
Inter-Switch Link (ISL)-based VLAN trunking
|
802.1Q-based VLAN routing/bridging
|
|
Layer 3 Routing, Switching, and Forwarding Features
|
|---|
IP, IPX, and IP multicast routing and forwarding between Ethernet ports
|
AppleTalk 1 and 2 routing
|
IP multicast routing with up to 12,000 groups (S, G)
 |
NoteMulticast routing is not supported over BVI. |
|
QoS-based forwarding based on IP precedence
|
Load balancing among two equal-cost paths based on source and destination IP and IPX addresses
|
Supported Routing Protocols
|
|---|
BGP (Border Gateway Protocol)
|
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 56 FECs
|
Load sharing based on source and destination IP addresses of unicast packets
|
Load sharing for bridge traffic based on MAC address
|
ISL trunking (routing/bridging)
|
802.1Q routing/bridging
|
Up to 56 active FEC and GEC port channels in one system
|
|
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 trunking (routing/bridging)
|
802.1Q routing/bridging
|
Up to 56 active FEC and GEC port channels in one system
|
|
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)
- Named ACL
|
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)
|
This section lists the Catalyst 8510 CSR caveats by release number and tracking number, and indicates whether or not the issue has been corrected. An "O" indicates that the caveat is open in that release, while an "X" indicates the release in which that caveat is closed. Caveats are referenced in Table 4.
Table 4: Caveat Matrix for Catalyst 8510 CSR
| DDTS #
| 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)
|
|---|
CSCdr58338
| O
|
|
|
|
|
|
CSCdr43159
|
| X
|
|
|
|
|
CSCdr26204
| X
|
| O
|
|
|
|
CSCdp86120
|
|
| X
| O
|
|
|
CSCdp84968
|
|
| X
| O
|
|
|
CSCdp82442
|
|
| X
| O
|
|
|
CSCdp81517
|
|
| X
| O
|
|
|
CSCdp80179
|
|
| X
| O
|
|
|
CSCdp77640
|
|
| X
| O
|
|
|
CSCdp75662
|
|
| X
| O
|
|
|
CSCdp74432
|
|
| X
| O
|
|
|
CSCdp72498
|
|
| X
| O
|
|
|
CSCdp70087
|
|
| X
| O
|
|
|
CSCdp66533
| X
|
| O
|
|
|
|
CSCdp66044
|
|
| X
| O
|
|
|
CSCdp64865
|
|
| X
| O
|
|
|
CSCdp61799
|
|
| X
| O
|
|
|
CSCdp61681
|
|
| X
| O
|
|
|
CSCdp57307
|
|
| X
| O
|
|
|
CSCdp54010
|
|
| X
| O
|
|
|
CSCdp48903
|
|
| X
| O
|
|
|
CSCdp31368
|
|
| X
| O
| O
|
|
CSCdm60387
|
|
|
| X
| O
|
|
CSCdm40533
|
|
|
|
|
| X
|
CSCdm36648
|
|
|
|
|
| X
|
CSCdm35971
|
|
|
|
|
| X
|
CSCdm32706
|
|
|
| X
| O
| O
|
CSCdm28633
|
|
|
|
|
| O
|
CSCdm26948
|
|
|
| X
| O
| O
|
CSCdm25943
|
|
|
| X
| O
| O
|
CSCdk93048
|
|
|
| X
| O
| O
|
CSCdk89275
|
|
|
| X
| O
| O
|
CSCdk82832
|
| O
| O
| O
| O
| O
|
CSCdk73492
|
| O
| O
| O
| O
| O
|
CSCdk72837
|
| O
| O
| O
| O
| O
|
This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8510 CSR.
- The following warning appears:
%LSS-4-INTERNAL_WARNING: lss_record_ri_ingress: Illegal channel %d
- Symptom: This warning appears when the encapsulation type of the Gigabit EtherChannel (GEC) is changed from ISL to 802.1Q, when the GEC is configured for novell-ether encapsulation and ports are receiving IPX traffic. No functionality problems are observed.
- Workaround: None.
- Some interfaces in the outgoing interface list of the IOS multicast table might not forward traffic.
- Symptom:When the 8500 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 8540 specific lightstream interprocess communication subsystem (LSS) multicast code.
- Workaround: Enter the clear ip multicast-routing command and configure static multicast groups on the interfaces sending PIM joins.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- There are memory leaks when the process to enqueue message fails.
- Symptom: There were 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.
- 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.
- 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).
- 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.
- Route connected to Ethernet interface is not installed.
- Symptom: Connected route associated with Ethernet interface might be intermittently missing from routing table.
- Workaround: Clear either the routing entry or the Ethernet interface.
- 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.
- 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.
- 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.
- 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.
- 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.
- 2-port Gigabit Ethernet counter problems on show interface packets input.
- Symptom: Some of the interface counters display a lower value for packet counters. Increasing the frequency of poll for statistics resolved the problem. This was needed only in 2-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 a later release.
- The show epc ipmcast command sometimes reports an incorrect value.
- Symptom: The packet statistics displayed by the show epc ipmcast command sometimes reports an incorrect value. This does not impact any functionality.
- Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
- The arp timeout interface command disappears after a system reload.
- Symptom: The arp timeout 300 interface command disappears from the running config after a reboot.
- Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
- 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.
- 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.
- Workaround: None.
- 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.
- Workaround: None.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 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.
This section lists the Catalyst 8540 CSR caveats by release number and tracking number, and indicates whether or not the caveat has been corrected. An "O" indicates that the caveat is open in that release, while an "X" indicates the release in which that caveat is closed. Caveats are referenced in Table 5.
Table 5: Caveat Matrix for Catalyst 8540 CSR
| DDTS #
| 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)
|
|---|
CSCdr48489
| X
|
|
|
|
|
CSCdr43159
| X
|
|
|
|
|
CSCdp94120
| O
| O
|
|
|
|
CSCdp91190
| O
| O
| O
|
|
|
CSCdp90216
| O
| O
|
|
|
|
CSCdp86120
|
| X
| O
|
|
|
CSCdp82442
|
| X
| O
|
|
|
CSCdp81517
|
| X
| O
|
|
|
CSCdp80179
|
| X
| O
|
|
|
CSCdp77640
|
| X
| O
|
|
|
CSCdp77324
|
| X
| O
|
|
|
CSCdp77105
|
| X
| O
|
|
|
CSCdp76943
|
| X
| O
|
|
|
CSCdp72498
|
| X
| O
|
|
|
CSCdp70903
|
| X
| O
|
|
|
CSCdp70392
|
| X
| O
|
|
|
CSCdp70087
|
| X
| O
|
|
|
CSCdp69276
|
| X
| O
|
|
|
CSCdp66953
|
| X
| O
|
|
|
CSCdp66044
|
| X
| O
|
|
|
CSCdp64865
|
| X
| O
|
|
|
CSCdp61799
|
| X
| O
|
|
|
CSCdp61681
|
| X
| O
|
|
|
CSCdp60263
|
| X
| O
|
|
|
CSCdp59602
| O
| O
| O
|
|
|
CSCdp57307
|
| X
| O
|
|
|
CSCdp54010
|
| X
| O
|
|
|
CSCdp53792
| O
| O
| O
|
|
|
CSCdp53383
| O
| O
| O
|
|
|
CSCdp53262
| O
| O
| O
|
|
|
CSCdp52120
| O
| O
| O
|
|
|
CSCdp49816
| O
| O
| O
|
|
|
CSCdp49399
|
| X
| O
|
|
|
CSCdp48943
| O
| O
| O
|
|
|
CSCdp48903
|
| X
| O
|
|
|
CSCdp39497
|
| X
| O
|
|
|
CSCdp33630
| O
| O
| O
|
|
|
CSCdp29577
| O
| O
| O
|
|
|
CSCdp24812
| O
| O
| O
|
|
|
CSCdp22692
| O
| O
| O
|
|
|
CSCdp20845
|
| X
| O
|
|
|
CSCdp14175
| O
| O
| O
|
|
|
CSCdp07758
|
| X
| O
|
|
|
CSCdm92257
| O
| O
| O
|
|
|
CSCdm91042
|
|
|
| X
|
|
CSCdm88103
|
|
|
| X
|
|
CSCdm86262
|
|
|
| X
|
|
CSCdm84834
|
|
|
| X
|
|
CSCdm84798
|
|
|
| X
|
|
CSCdm76785
|
|
| X
| O
|
|
CSCdm75735
|
|
| X
| O
|
|
CSCdm73823
|
|
| X
| O
|
|
CSCdm71729
|
|
| X
| O
|
|
CSCdm68875
|
|
| O
| O
|
|
CSCdm68368
|
|
| X
| O
|
|
CSCdm64047
|
|
| X
| O
|
|
CSCdm62162
|
|
| X
| O
|
|
CSCdm58126
| O
| O
| O
| O
|
|
CSCdm57767
|
|
| X
| O
|
|
CSCdm57720
|
|
| X
| O
|
|
CSCdm57516
|
|
| X
| O
|
|
CSCdm52306
|
|
| X
| O
|
|
CSCdm50065
|
|
| X
| O
|
|
CSCdm43436
|
|
|
|
| X
|
CSCdm39686
|
|
|
|
| X
|
CSCdm34838
|
|
| X
| O
| O
|
CSCdm33903
|
|
| X
|
|
|
CSCdm33313
|
|
| X
| O
| O
|
CSCdm31218
|
|
| X
| O
| O
|
CSCdm20899
|
|
|
|
| O
|
CSCdm13198
|
|
| X
| O
|
|
This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8540 CSR.
- 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 shut/no shut command to the root interface.
- Some interfaces in the outgoing interface list of the IOS multicast table might not forward traffic.
- Symptom:When the 8500 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 8540 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.
- 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, sometimes the encapsulation 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).
- 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 CPU to be routed or bridged. Consequently, we recommend that native VLANs not be used for network traffic and that they be limited to overhead traffic that terminates at the route processor (such as, routing updates and CDP)
- Workaround: Configure the traffic on a non-native VLAN.
- The following traceback message appears:
%SK-7-ASSERT: Assertion Failure ... Cant find port channel idb ...
- Symptom: Sometimes the above message appears when 8-port Gigabit Ethernet interfaces are added to port channels.
- Workaround: None.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 redundancy preparation command, sometimes hangs the system.
- Workaround: Power cycle the system.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- With the 8-port Gigabit Ethernet interface module, spurious memory access occurs.
- Symptom: With the 8-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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Need a mechanism to troubleshoot and recover from stuck port failures.
- Symptom: There is no mechanism to detect and recover from a stuck port failures.
- Workaround: The following two new 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.
- 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: None.
- FEC: interface MAC address 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.
- 2-port Gigabit Ethernet counter problems on show interface packets input.
- Symptom: Some of the interface counters display a lower value for packet counters. Increasing the frequency of poll for statistics resolved the problem. This was needed only in 2-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 a later release.
- 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.
- 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.
- Under extreme conditions, MAC_learn IPC may be lost.
- Symptom: A host move under high traffic conditions may result in a missing MAC entry from the IOS bridging table. When routing over BVI, this may cause loss of connectivity.
- Workaround: Issue the clear bridge command.
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 do occur, clear ip mroute * should fix the problem.
- 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.
- Port stuck on reboot of connected Catalyst 8540 CSR with 70% 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 ingress tasks get continuously scheduled when it cannot meet 84-cycles budget requirement under "Auto L2-learning" conditions.
- Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
- Protocol specific IRB does not work for dot1q bridge group members on 8-port gigabit module.
- Symptom: If any bridge-group members are dot1q subinterfaces on an 8-port gigabit module, then protocol specific IRB configuration will not work over these ports because of local-switching ASIC (K1) chip limitations.
- Workaround: None.
- The show epc ipmcast command sometimes reports an incorrect value.
- Symptom: The packet statistics displayed by the show epc ipmcast command sometimes reports an incorrect value. This does not impact any functionality.
- Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
- 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.
- Packets are switched out on native VLAN, leading to routing by CPU (with BVI).
- Symptom: On EPIF-based interface modules, untagged packets coming in on the dot1q native VLAN are not processed by the microcode. Instead, they are given to the CPU, and the CPU does the processing. This means that high CPU 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.
- Assigning the same dot1q encapsulation on subinterfaces on the same slot on an 8-port Gigabit Ethernet does not always work.
- Symptom: When multiple dot1q subinterfaces are configured over interfaces belonging to the same slot of an 8-port gigabit card, 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 may not always work, depending on the deployment scenario.
- Workaround: Configure different encapsulations among the different subinterfaces in the same slot. This makes the EPIFs 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 may be used to provide local switching capability for trunk ports and possibly routing over BVI.
- Ports are not recognized as OSPF interfaces after 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.
- Connected networks are not propagated through OSPF after OIR.
- Symptom: After hot-swapping a Fast Ethernet interface module, OSPF routes are not propagated properly.
- Workaround: Issue the shut and no shut commands on the appropriate interface.
- 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.
- K1 port cannot be configured for snooping other interfaces.
- Symptom: Ports on an 8-port Gigabit Ethernet interface module cannot be snooped or used to snoop other interfaces
- Workaround: Use a Gigabit Ethernet port from a 2-port Gigabit Ethernet interface module to snoop.
- 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.
- 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.
- 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.
- 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.
- Workaround: None.
- Crash after exiting CLI configuration mode on 8540CSR.
- Symptom: The router crashes when you enter and exit CLI configuration mode repeatedly and quickly.
- Workaround: None.
- 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.
- 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.
- 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.
- 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
- Online insertion and removal (OIR) of interface modules causes failures when multicast traffic is present.
- Symptom: Following the online insertion of a 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.
- 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.
- 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 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.
- Symptom: Routing protocols take more time to converge after reboot on a router with large ACLs configured on many interfaces.
- Workaround: None. When you reboot a router, it can take considerable time to populate large ACLs on many interfaces, resulting in a delay in the convergence of some routing protocols.
- Symptom: 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 "../src-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.
- 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.
- Workaround: None.
- 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.
- Workaround: None.
- 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.
- Node crash on TFTP boot.
- Symptom: A fully loaded 8540 CSR with 2-port Gigabit Ethernet modules boots properly from bootflash and slot, but does not boot from tftp.
- Workaround: None.
- 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.
- 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.
- 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 may need to upgrade your 10/100BaseT interface module firmware. Contact your Cisco service representative for more information.
- 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.
This section describes the following Catalyst 8500 CSR restrictions:
The ACL daughter card is supported on the Catalyst 8540 CSR only. The following restrictions apply:
- 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
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 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
- 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.
The 8-port Gigabit Ethernet interface module is supported on the Catalyst 8540 CSR only. This section describes limitations of the 8-port Gigabit Ethernet interface module.
The 8-port Gigabit Ethernet interface module installed in a Catalyst 8540 CSR can support a maximum of 24 ports per bridge group.
If your Catalyst 8540 CSR has an 8-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 8-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 8-port Gigabit Ethernet interface module.
If your switch router does not have an 8-port Gigabit Ethernet interface module, you can assign port channel ID numbers up to 64.
The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of interface modules on the Catalyst 8500 CSR:
- Wait at least one minute after removing an interface module before inserting a new one.
- Do not remove more than one interface module at a time while the device is operational.
- OIR of the 8-port Gigabit Ethernet interface module is supported in Cisco IOS Release 12.0(5)W5.13 and later releases.
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 8500 CSR switch routers support extra long haul (1000BaseZX) GBICs as follows:
- Catalyst 8540 CSR: A maximum of 12 1000BaseZX GBICs per system to comply with FCC Class A emissions (CFR 47 Part 15), or 8 1000BaseZX GBICs per system to comply with EN55022 Class B emissions (CISPR22 Class B).
- Catalyst 8510 CSR: Up to four 1000BaseZX GBICs in a total of four Gigabit Ethernet interface modules to comply with radiated emissions requirements.
The Catalyst 8540 CSR supports the use of redundant route processors and switch modules. The second route processor would be installed in slot 8, and an additional switch module would be installed in slot 6.
There are some precautions that need to be taken before removing a route processor module from a chassis that is powered-up. If a route processor module that is currently running IOS is removed from the chassis in a skewed manner such that the left side of the processor comes out before the right side does, the traffic flowing through the device may stop flowing.
To avoid this, make sure the route processor module that is being removed is currently at the ROM monitor prompt; it is then safe to remove it from the chassis. One way to get the system into ROM monitor from IOS is to issue a reload command. This will work if the system is not configured to auto-boot. If the system is configured to auto-boot, it starts booting IOS again.
Since you need to ensure that a route processor is in ROM monitor before removing it, the redundancy prepare-for-cpu-removal command has been added to take the system to the ROM monitor prompt. Execute this command on the route processor being removed before removing it. Once this command is issued, the route processor will go to the ROM monitor prompt and stay there even if the system is configured to auto-boot. At this point it is safe to remove the route processor from the system.
If a Catalyst 8540 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.
Beginning with Cisco IOS Release 12.0(5)W5(13) software, the autonegotiation feature for speed and duplex on 10/100BaseT 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 router or switch running in forced full-duplex mode, you may 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 to operate in full-duplex mode or removing the full-duplex command from the other device. |
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.
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.
- Catalyst 8540 Interactive Quick Start
- Quick Reference Catalyst 8540 CSR and MSR Hardware Information
- Catalyst 8540 Campus Switch Router Route Processor and Interface Module Installation Guide
- Catalyst 8510 Interactive Quick Start
- Quick Reference Catalyst 8510 and LightStream 1010 Hardware Information
- Catalyst 8510 Campus Switch Router Processor and Interface Module Installation Guide
- Layer 3 Switching Software Feature and Configuration 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: Mon Aug 7 09:13:03 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
