Table of Contents
Release Notes for the
Catalyst 8500 Campus Switch Router Cisco IOS Release 12.0(5)W5(13)
Release Notes for the
Catalyst 8500 Campus Switch Router Cisco IOS Release 12.0(5)W5(13)
December 22, 1999
This document provides the current Catalyst 8500 CSR software features and caveats for Cisco IOS Release 12.0(5)W5(13).
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 12.0 (5) W5 (13), 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 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)
 |
Note Multicast 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, etc.)
- 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 8540 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 1.
Table 1: Caveat Matrix for Catalyst 8540 CSR
| DDTS #
| 12.0(5)
W5(13)
| 12.0(4a)
WX5(11a)
| 12.0(4a)
W5(11)
| 12.0(1a)
W5(6f)
| 12.0(1a)
W5(6e)
| 12.0(1a)
W5(6b)
| 12.0(1.0)
W5(6a)
| 12.0(1.0)
W5(6)
| 12.0(0.16)
W5(4)
|
|---|
CSCdp53792
| O
|
|
|
|
|
|
|
|
|
CSCdp53383
| O
|
|
|
|
|
|
|
|
|
CSCdp53262
| O
|
|
|
|
|
|
|
|
|
CSCdp52120
| O
|
|
|
|
|
|
|
|
|
CSCdp49816
| O
|
|
|
|
|
|
|
|
|
CSCdp48943
| O
|
|
|
|
|
|
|
|
|
CSCdp33630
| O
|
|
|
|
|
|
|
|
|
CSCdp29577
| O
|
|
|
|
|
|
|
|
|
CSCdp24812
| O
|
|
|
|
|
|
|
|
|
CSCdp22692
| O
|
|
|
|
|
|
|
|
|
CSCdp14175
| O
|
|
|
|
|
|
|
|
|
CSCdm92257
| O
|
|
|
|
|
|
|
|
|
CSCdm91042
|
| X
|
|
|
|
|
|
|
|
CSCdm88103
|
| X
|
|
|
|
|
|
|
|
CSCdm86262
|
| X
|
|
|
|
|
|
|
|
CSCdm84834
|
| X
|
|
|
|
|
|
|
|
CSCdm84798
|
| X
|
|
|
|
|
|
|
|
CSCdm76785
| X
| O
| O
|
|
|
|
|
|
|
CSCdm75735
| X
| O
| O
|
|
|
|
|
|
|
CSCdm73823
| X
| O
| O
|
|
|
|
|
|
|
CSCdm71729
| X
| O
| O
|
|
|
|
|
|
|
CSCdm68875
| O
| O
| O
|
|
|
|
|
|
|
CSCdm68368
| X
| O
| O
|
|
|
|
|
|
|
CSCdm64047
| X
| O
| O
|
|
|
|
|
|
|
CSCdm62162
| X
| O
| O
|
|
|
|
|
|
|
CSCdm58126
| O
| O
| O
|
|
|
|
|
|
|
CSCdm57767
| X
| O
| O
|
|
|
|
|
|
|
CSCdm57720
| X
| O
| O
|
|
|
|
|
|
|
CSCdm57516
| X
| O
| O
|
|
|
|
|
|
|
CSCdm52306
| X
| O
| O
|
|
|
|
|
|
|
CSCdm50065
| X
| O
| O
|
|
|
|
|
|
|
CSCdm43436
|
|
|
| X
|
|
|
|
|
|
CSCdm39686
|
|
|
| X
|
|
|
|
|
|
CSCdm34838
| X
| O
| O
| O
| O
|
|
|
|
|
CSCdm33903
| X
|
|
|
|
|
|
|
|
|
CSCdm33313
| X
| O
| O
| O
| O
|
|
|
|
|
CSCdm31218
| X
| O
| O
| O
| O
|
|
|
|
|
CSCdm20899
|
|
| X
| O
| O
|
|
|
|
|
CSCdm13198
| X
| O
| O
|
|
|
|
|
|
|
CSCdk91957
|
|
|
|
|
| X
| O
|
|
|
CSCdk76674
|
|
|
|
|
|
| X
| O
|
|
CSCdk75694
|
|
|
|
|
|
| X
| O
|
|
CSCdk74764
|
|
|
|
|
|
| X
| O
|
|
CSCdk74612
|
|
|
|
|
|
| X
| O
|
|
CSCdk62035
|
|
|
|
|
|
|
| X
| O
|
CSCdk61567
|
|
|
|
|
|
|
| X
| O
|
CSCdk61127
|
|
|
|
|
|
|
| X
| O
|
CSCdk60346
|
|
|
|
|
|
|
| X
| O
|
CSCdk59996
|
|
|
|
|
|
|
| X
| O
|
CSCdk59851
|
|
|
|
|
|
|
| X
| O
|
CSCdk58018
|
|
|
|
|
|
|
| X
| O
|
CSCdk57611
|
|
|
|
|
|
|
| X
| O
|
CSCdk57596
|
|
|
|
|
|
|
| X
| O
|
CSCdk57012
|
|
|
|
|
|
|
| X
| O
|
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0(5)W5(13) for the Catalyst 8540 CSR.
- 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.
- 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.
- 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.
|
Note 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.
|
Note 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 line 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 line module, OSPF routes are not propagated properly.
- Workaround: Issue the shut and no shut commands on the appropriate interface.
- K1 port can not 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 line module to snoop.
- 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.
- 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.
- 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.
This section summarizes the caveats that were corrected in Cisco IOS Release 12.0(5)W5(13) for the Catalyst 8540 CSR.
- 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.
- 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.
- Crash after exiting CLI configuration mode on 8540CSR.
- Symptom: The router crashes when you enter and exit CLI configuration mode repeatedly and quickly.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Symptom: Routing protocols take more time to converge after reboot on a router with large ACLs configured on many interfaces.
- Symptom: IPX ACL on a subinterface of a non-trunk main interface does not filter traffic.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Gigabit Ethernet line module port failure.
- Symptom: Under certain conditions, some Gigabit Ethernet line module ports will not come up.
- 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.
- 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.
- 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
- 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.
- Having 32 IPX/RIP neighbors causes high CPU utilization.
- Symptom: A system configured with 32 IPX/RIP neighbors shows over 90% CPU utilization.
- 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.
- 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%.
- 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.
- 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.
- 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 ***
- %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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 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 2.
Table 2: Caveat Matrix for Catalyst 8510 CSR
| DDTS #
| 12.0(5)
W5(13)
| 12.0(4a)
WX5(11a)
| 12.0(4a)
W5(11)
| 12.0(1a)
W5(6f)
| 12.0(1a)
W5(6e)
| 12.0(1a)
W5(6b)
| 12.0(1.0)
W5(6a)
| 12.0(1.0)
W5(6)
| 12.0(0.16)
W5(3)
| 12.0(0.16)
W5(2)
| 12.0(0.16)
W5(1)
|
|---|
CSCdm60387
| X
| O
| O
|
|
|
|
|
|
|
|
|
CSCdm40533
|
|
|
| X
|
|
|
|
|
|
|
|
CSCdm36648
|
|
|
| X
|
|
|
|
|
|
|
|
CSCdm35971
|
|
|
| X
|
|
|
|
|
|
|
|
CSCdm32706
| X
| O
| O
| O
| O
|
|
|
|
|
|
|
CSCdm28633
|
|
| X
| O
| O
|
|
|
|
|
|
|
CSCdm26948
| X
| O
| O
| O
| O
|
|
|
|
|
|
|
CSCdm25943
| X
| O
| O
| O
| O
|
|
|
|
|
|
|
CSCdm13967
|
|
| X
|
|
|
|
|
|
|
|
|
CSCdk93048
| X
| O
| O
| O
| O
|
|
|
|
|
|
|
CSCdk91957
|
|
|
|
|
| X
| O
|
|
|
|
|
CSCdk89275
| X
| O
| O
| O
| O
|
|
|
|
|
|
|
CSCdk88347
|
|
|
|
| X
| O
| O
|
|
|
|
|
CSCdk86404
|
|
|
|
| X
| O
| O
|
|
|
|
|
CSCdk82832
| O
| O
| O
| O
| O
| O
| O
|
|
|
|
|
CSCdk77676
|
|
|
|
| X
| O
| O
| O
|
|
|
|
CSCdk73492
| O
| O
| O
| O
| O
| O
| O
|
|
|
|
|
CSCdk72837
| O
| O
| O
| O
| O
| O
| O
| O
|
|
|
|
CSCdk64461
|
|
|
|
|
|
| X
| O
|
|
|
|
CSCdk49942
|
|
|
|
|
|
|
| X
| O
|
|
|
CSCdk49645
|
|
|
|
|
|
|
| X
| O
|
|
|
CSCdk47686
|
|
|
|
|
|
|
| X
| O
|
|
|
CSCdk40545
|
|
|
|
|
|
|
|
|
| X
|
|
CSCdk40372
|
|
|
|
|
|
|
|
|
| X
|
|
CSCdk39141
|
|
|
|
|
|
|
|
|
| X
|
|
CSCdk39050
|
|
|
|
|
|
|
|
|
| O
|
|
CSCdk38183
|
|
|
|
|
|
|
|
|
| X
|
|
CSCdk35757
|
|
|
|
|
|
|
|
|
| O
|
|
CSCdk31184
|
|
|
|
|
|
|
| X
| O
|
|
|
CSCdk25291
|
|
|
|
|
|
|
|
|
| O
|
|
CSCdk18420
|
|
|
|
|
|
|
|
|
| O
|
|
CSCdk17304
|
|
|
|
|
|
|
|
|
|
| X
|
CSCdk16456
|
|
|
|
|
|
|
|
|
| O
|
|
CSCdk10261
|
|
|
|
|
|
|
|
|
|
| X
|
CSCdk08740
|
|
|
|
|
|
|
|
|
|
| X
|
CSCdk02614
|
|
|
|
|
|
|
|
|
|
| X
|
This section summarizes symptoms and suggested workarounds for caveats in Cisco IOS
Release 12.0(5)W5(13) for the Catalyst 8510 CSR.
- 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 summarizes the caveats that were corrected in Cisco IOS Release 12.0(5)W5(13) for the Catalyst 8510 CSR.
- 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.
- 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.
- 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.
- 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]
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Symptom: Issuing a clear ip route network command deletes routes to directly connected networks.
- IP multicast TTL threshold does not affect packet forwarding.
- Symptom: 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.
- 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.
- 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.
- 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.
- 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.
- %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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- %IPX-3-BADINSERT: Duplicate SAP entry insert attempted.
- Symptom: Router returns a %IPX-3-BADINSERT message when a duplicate SAP entry is made.
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
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 line module can support a maximum of 24 ports per bridge group.
If your Catalyst 8540 CSR has an 8-port Gigabit Ethernet line 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 line module.
Also, if your switch router has an 8-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 8-port Gigabit Ethernet line module.
If your switch router does not have an 8-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:
- 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 of the 8-port Gigabit Ethernet line module is now supported.
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 8510 and 8540 CSR systems 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 line 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. |
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: Fri Jan 21 15:39:22 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.
