|
|
Table Of Contents
Release Notes for the Catalyst 8540 for Cisco IOS Release 12.0(28)W5(31)
Minimum Flash Memory Requirements
Determining Your Software Release
Release Names, Versions, and Part Numbers
New Features in Release 12.0(28)W5(31)
New Features in Release 12.0(28)W5(30a)
New Features in Release 12.0(28)W5(30)
New Features in Release 12.0(27)W5(29)
New Features in Release 12.0(26)W5(28)
New Features in Release 12.0(24)W5(26c)
New Features in Release 12.0(24)W5(26b)
New Features in Release 12.0(24)W5(26)
New Features in Release 12.0(22)W5(25)
New Features in Release 12.0(20)W5(24b)
New Features in Release 12.0(20)W5(24a)
New Features in Release 12.0(20)W5(24)
New Features in Release 12.0(19)W5(23)
New Features in Release 12.0(18)W5(22)
New Features in Release 12.0(16)W5(21)
New Features in Release 12.0(13)W5(19c)
New Features in Release 12.0(10)W5(18c)
New Features in Release 12.0(7)W5(15c)
New Features in Release 12.0(5)W5(13b)
New Features in Release 12.0(4a)W5(11a)
New Features in Release 12.0(1a)W5(9)
New Features in Release 12.0(1a)W5(7b)
New Features in Release 12.0(1a)W5(6f)
Caveat Symptoms and Workarounds
ACL Daughter Card Restrictions
ATM Router Module Restrictions
VLAN Encapsulation Restrictions
Maximum Path Restriction for EIGRP or OSPF
Eight-Port Gigabit Ethernet Restrictions (Catalyst 8540 CSR)
Online Insertion and Removal of Interface Modules Restrictions
Online Diagnostics Restrictions
Bridge-Group Virtual Interface Restriction
Catalyst 8540 Route Processor and Switch Module Redundancy
Autonegotiation (Catalyst 8540 CSR)
Incompatibility (Catalyst 8540 CSR)
Software Configuration Tips on the Cisco TAC Home Page
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Catalyst 8540 for Cisco IOS Release 12.0(28)W5(31)
March 25, 2005
Catalyst 8540 for Cisco IOS Release 12.0(28)W5(31)
Text Part Number: OL-6718-01 Rev. A1
This document describes the features and caveats for Cisco IOS Release 12.0(28)W5(31) software for the Catalyst 8540 switch router.
Contents
This document includes the following sections:
•
Caveats
•
•
•
•
•
•
Introduction
The Catalyst 8540 multiservice switch router (MSR) is a 13-slot, modular chassis featuring dual, fault-tolerant, load-sharing AC or DC power supplies. The ATM switch router provides a 20-Gbps full-duplex nonblocking switch fabric with switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.
The Catalyst 8540 CSR switch router belongs to a class of high-performance Layer 3 switch routers and is optimized for the campus LAN or the intranet. The Catalyst 8540 CSR switch router provides both wirespeed Ethernet routing and switching services.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.0(28)W5(31) and includes the following sections:
•
•
•
Memory Requirements
The DRAM memory configuration is 256 MB, which is the default for the Catalyst 8540.
Minimum Flash Memory Requirements
Cisco IOS Release 12.0(28)W5(31) and later releases require a minimum of 16 MB of contiguous boot Flash memory. The Catalyst 8540 route processor now ships by default with a 16-MB boot Flash SIMM.
Earlier releases of the Catalyst 8540 switch router shipped with an 8-MB boot Flash SIMM. The 8-MB boot Flash SIMM is not large enough to store system images for Cisco IOS software releases 12.0(4a)W5(11a) and later.
To check that your system has a 16-MB boot Flash SIMM, enter the show hardware EXEC command. The part numbers for route processors with a default 16-MB boot Flash SIMM are as follows:
•
•
If you have an 8-MB boot Flash SIMM, and have no additional memory installed, we recommend that you order a spare Flash PC card programmed with the latest version of the system image, part number MEM-8540M-FLC20M=.
Alternatively, you can use one of the following options to accommodate the larger image:
•
Note
Then do the following:
–
Note
–
–
An example follows:
Switch(config)# config-register 0x2102EHSA:Syncing confreg: 256 to secondarySwitch(config)# boot system slot0:cat8540m-wp-mz.120-4a.W5.11aSwitch(config)# endSwitch# copy running-config startup-config•
An example follows:
Switch(config)# boot system tftp cat8540m-wp-mz.120-4a.W5.11a 172.20.52.3
Note
Note
For more information about downloading system images and changing the default boot image, refer to the "File Management" chapter of the Configuration Fundamentals Configuration Guide in the Cisco IOS software documentation set.
Hardware Supported
Table 1 and Table 2 list the hardware modules supported on the Catalyst 8540 in the Cisco IOS Release 12.0(28)W5(31). They also include the minimum software release requirements for the hardware.
•
•
Note
Table 1 Catalyst 8540 MSR Interface Modules and Minimum Software Required
C8540-PWR-AC
AC Power Supply
W5-7
C8540-PWR-AC/2
Redundant AC Power Supply
W5-7
C8540-PWR-DC
DC Power Supply
W5-7
C8540-PWR-DC/2
Redundant DC Power Supply
W5-7
C8545MSR-MRP4CLK
Multiservice Route Processor
W5-7
C8545MSR-MRP3CLK
Multiservice Route Processor Stratum 3
W5-7
UPG-MSR-MRP-3CLK
Stratum 3 Clock Module Upgrade
W5-7
C8546MSR-MSP-FCL
Switch Processor with ATM Feature Card
W5-7
C85MS-SCAM-2P
Super Carrier for LightStream 1010 ATM switch port adapters
W5-7
WAI-OC-3-4MM
4-port 155-Mbps Synchronous Optical Network (SONET) STS-3c/SDH STM-1 port adapter
W5-7
WAI-OC-3-4SS
4-port 155-Mbps SONET STS-3c/SDH STM-1 port adapter
W5-7
WAI-OC3-1S3M
4-port 155-Mbps SONET STS-3c/SDH STM-1 port adapter
W5-7
WAI-OC3-4U5
4-port 155-Mbps SONET STM-1 UTP-5 port adapter
W5-7
C85MS-16F-OC3MM
16-port SONET STS-3c /SDH STM-1 interface module
W5-7
WAI-OC12-1SS
1-port 622-Mbps SONET STS-12c/SDH STM-4c port adapter
W5-7
WAI-OC12-1MM
1-port 622-Mbps SONET STS-12c/SDH STM-4c port adapter
W5-7
WAI-E1-4RJ48
4-port E1 port adapter
W5-7
WAI-T1-4RJ48
4-port T1 port adapter
W5-7
WAI-E1-4BNC
4-port E1 port adapter
W5-7
C85MS-4F-OC12SS
4-port SONET STS-12c/SDH STM-4c interface module
W5-7
C85MS-4F-OC12MM
4-port SONET STS-12c/SDH STM-4c interface module
W5-7
WAI-E1C-4BNC
4-port CES E1 port adapter
W5-7
WAI-E1C-4RJ48
4-port CES E1 port adapter
W5-7
WAI-T1C-4RJ48
4-port CES T1 port adapter
W5-7
WAI-T3-2BNC
2-port DS3 port adapter
W5-7
WAI-T3-4BNC
4-port DS3 port adapter
W5-7
WAI-E3-2BNC
2-port E3 port adapter
W5-7
WAI-E3-4BNC
4-port E3 port adapter
W5-7
C85MS-4E1-FRR548
4-port CE1 Frame Relay port adapter
W5-9
C85MS-1DS3-FRBNC
1-port CDS3 Frame Relay port adapter
W5-9
C85MS-1F4M-OC48SS
1-port OC-48c SMF-IR + 4-port OC-12 MMF
S854R2-12.0.4W
C85MS-1F4S-OC48SS
1-port OC-48c SMF-IR + 4-port OC-12 SMF-IR
S854R2-12.0.4W
C85MS-2F-OC48SS
2-port OC-48c SMF-IR
S854R2-12.0.4W
C8540-ARM
ATM router module
S854R2-12.0.4W
C85GE-8X-64K
C8540 8-port Gigabit Ethernet 64K line module
S854R2-12.0.4W
C85GE-2X-16K
C8540 2-port Gigabit Ethernet 16K line module
S854R2-12.0.4W
C85GE-2X-64K
C8540 2-port Gigabit Ethernet 64K line module
S854R2-12.0.4W
C85GE-2XACL-16K
C8540 2-port Gigabit Ethernet 16K with ACL line module
S854R2-12.0.4W
C85GE-2XACL-64K
C8540 2-port Gigabit Ethernet 64K with ACL line module
S854R2-12.0.4W
C85FE-16T-16K
C8540 16-port 10/100 UTP 16K interface module
S854R2-12.0.4W
C85FE-16T-64K
C8540 16-port 10/100 UTP 64K interface module
S854R2-12.0.4W
C85FE-16TACL-16K
C8540 16-port 10/100 UTP 16K with ACL interface module
S854R2-12.0.4W
C85FE-16TACL-64K
C8540 16-port 10/100 UTP 64K with ACL interface module
S854R2-12.0.4W
C85FE-16F-16K
C8540 16-port 100-FX-MT-RJ 16K interface module
S854R2-12.0.4W
C85FE-16F-64K
C8540 16-port 100-FX-MT-RJ 64K interface module
S854R2-12.0.4W
C85FE-16FACL-16K
C8540 16-port 100-FX-MT-RJ 16K with ACL interface module
S854R2-12.0.4W
C85FE-16FACL-64K
C8540 16-port 100-FX-MT-RJ 64K with ACL interface module
S854R2-12.0.4W
C85MS-8T1-IMA
8-port T1 port adapter with inverse multiplexing over ATM
S854R2-12.0.7W1
C85MS-8E1-IMA-120
8-port E1 port adapter with inverse multiplexing over ATM
S854R2-12.0.7W1
C85MS-1F4S-OC48LR
1-port OC-48c SMF-LR + 4-port OC-12 SMF-IR
S854R2-12.0.7W
C85MS-2F-OC48LR
2-port OC-48c SMF-LR
S854R2-12.0.7W
C85EGE-2X-16K
Enhanced 2-port Gigabit Ethernet 16K
S854R2-12.0.10W
C85EGE-2X-64K
Enhanced 2-port Gigabit Ethernet 64K
S854R2-12.0.10W
C85EGE-2X-256K
Enhanced 2-port Gigabit Ethernet 256K
S854R2-12.0.10W
C85-POSOC12I-64K
1-port POS OC-12c/STM-4 SMF-IR and 1-port Gigabit Ethernet 64K
S854R2-12.0.10W
C85-POSOC12I-256K
1-port POS OC-12c/STM-4 SMF-IR and 1-port Gigabit Ethernet 256K
S854R2-12.0.10W
C85-POSOC12L-64K
1-port POS OC-12c/STM-4 SMF-LR and 1-port Gigabit Ethernet 64K
S854R2-12.0.10W
C85-POSOC12L-256K
1-port POS OC-12c/STM-4 SMF-LR and 1-port Gigabit Ethernet 256K
S854R2-12.0.10W
1 The T1/E1 IMA port adapters also require carrier module FPGA image version 1.8 or later, and IMA port adapter functional image version 3.2 or later.
Determining Your Software Release
To determine the version of Cisco IOS software currently running on the Catalyst 8540, log into the switch and use the show version privileged EXEC command. The following sample output is from the show version command. The version number is indicated on the second line:
Cisco Internetwork Operating System SoftwareIOS (tm) PNNI Software (cat8540m-WP-M), Version 12.0(28)W5(31)Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
Other Firmware Code
Most of the port adapters and interface modules supported on the Catalyst 8540 have upgradable 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 functional images are available on the World Wide Web at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/l3sw/8540/rel_12_0/w5_6f/rel_note/fpga_rn/index.htm
For information describing the firmware update process, refer to the ATM Switch Router Software Configuration Guide.
Feature Set Tables
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Those features are listed by release number in the following tables:
•
•
•
Note
Table 3 Feature Sets Supported by the Catalyst 8540 MSR
(10)
W5
(18c)
(7)
W5
(15c)
(4a)
W5
(11a)
(1a)
W5
(9)
(1a)
W5
(7b)Left-justified E.164 AFI support
x
x
x
x
x
x
SNMP1
x
x
x
x
x
x
Asynchronous support
x
x
x
x
x
x
x
x
x
x
x
x
IP4
x
x
x
x
x
x
NTP5
x
x
x
x
x
x
TACACS+6
x
x
x
x
x
x
Telnet
x
x
x
x
x
x
Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8
x
x
x
x
x
x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI9 3.0)
x
x
x
x
x
x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)
x
x
x
x
x
x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)
x
x
x
x
x
x
Multipoint-to-point UNI signaling
x
x
x
x
x
x
Soft VCCs and VPCs
x
x
x
x
x
x
VP tunneling
x
x
x
x
x
x
VPI/VCI range support in ILMI 4.0
x
x
x
x
x
x
PNNI hierarchy
x
x
x
x
x
x
ILMI10 version 4.0
x
x
x
x
x
x
IISP11
x
x
x
x
x
x
LANE12 client (LEC13 ) and LANE services (LES14 /BUS15 /LECS16 ) on route processor
x
x
x
x
x
x
ATM ARP17 server on route processor
x
x
x
x
x
x
ATM ARP client on route processor
x
x
x
x
x
x
ATM tag switch router (TSR)
x
x
x
x
x
x
Port snooping
x
x
x
x
x
x
OAM18 F4 and F5
x
x
x
x
x
x
E.164 address translation
x
x
x
x
x
x
E.164 autoconversion
x
x
x
x
x
x
Circuit emulation
x
x
x
x
x
x
ATM access lists
x
x
x
x
x
x
ATM accounting
x
x
x
x
x
x
ATM RMON19
x
x
x
x
x
x
Multiple, weighted, dynamic thresholds for selective packet marking and discard
x
x
x
x
x
x
Shaped VP tunnels for CBR20 traffic
x
x
x
x
x
x
Substitution of other service categories in shaped VP tunnels
x
x
x
x
x
x
Dual leaky bucket policing
x
x
x
x
x
x
Scheduler/Service Class/PVC configuration
x
x
x
x
x
x
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC)
x
x
x
x
x
x
Network clocking enhancements for smooth switchover
x
x
x
x
x
x
Per-VC or per-VP nondisruptive snooping
x
x
x
x
x
x
x
x
x
x
x
x
Access lists on ILMI registration
x
x
x
x
x
x
CUGs
x
x
x
x
x
x
ATM soft restart
x
x
x
x
x
x
ATM accounting enhancements
x
x
x
x
x
x
CISCO-SYSLOG-MIB support
x
x
x
x
x
x
CISCO-CONFIG-COPY-MIB support
x
x
x
x
x
x
Signaling diagnostics and MIB23
x
x
x
x
x
x
Supplemental AToM MIB
x
x
x
x
x
x
Hierarchical VP tunnels
x
x
x
x
x
x
Remote logging for accounting
x
x
x
x
x
x
Tag switching VC-merge on non-UBR24 VP tunnels and hierarchical VP tunnels
x
x
x
x
x
x
PNNI complex node representation
x
x
x
x
x
x
PNNI explicit paths
x
x
x
x
x
PNNI alternate link selection
x
x
x
x
x
Tag switching CoS
x
x
x
x
x
Network Clock Distribution Protocol
x
x
x
x
x
Simple Gateway Control Protocol
x
x
x
x
x
Switch redundancy
x
x
x
x
x
CPU redundancy: PVP/PVC/VP tunnel preservation
x
x
x
x
x
12-bit VPI
x
x
x
x
x
ATM router module
x
x
x
x
ATM overbooking
x
x
x
x
Framing overhead
x
x
x
x
ATM End System Address (AESA) gateway
x
x
x
x
Online insertion and removal support for 8-port Gigabit Ethernet interface modules
x
x
x
Route processor switchover support for 8-port Gigabit Ethernet interface modules
x
x
x
Appletalk support for 8-port Gigabit Ethernet interface modules
x
x
x
RFC 1483 PVC support on the ATM router modules
x
x
RFC 1577 PVC support on the ATM router modules
x
x
Spanning Tree SNMP trap support
x
x
IP fragmentation support for POS/ATM uplink
x
x
BGP (Border Gateway Protocol)
x
x
Routing protocol MIB support (OSPF, BGP)
x
x
ISL trunking (routing/bridging)
x
x
Enhanced Gigabit Ethernet port adapters with built-in ACL functionality and 16, 64, or 256 KB of memory available for routing tables
x
x
IP simple ACL (1-99, 1301-1999)
x
x
Maximum of 32 active bridge groups with BVI
x
x
1-port packet-over-SONET OC-12c uplink port adapter with built-in ACL functionality and a 1-port enhanced Gigabit Ethernet port adapter
x
x
IS-IS routing protocol
x
x
Switching database manager
x
x
POS RFC 1619 PPP over SONET/SDH
x
x
POS RFC 1662 PPP in HDLC-like framing
x
x
POS IP fragmentation for POS and ATM uplink
x
x
POS SONET MIB as defined in RFC 1575
x
x
POS Transparent Bridging (PPP/HDLC encapsulation)
x
x
POS SPE payload scrambling
x
x
POS SONET alarms (LOS, LOF, AIS, and RDI detection/reporting)
x
x
POS Threshold Crossing Alerts for B1, B2, B3 with configurable thresholds
x
x
Online diagnostics providing the following types of tests:
Accessibility tests between the route processor and the ports
Online insertion and removal (OIR) diagnostic tests
Snake tests through the switch router to ensure connectivity between the ports
x
1 SNMP = Simple Network Management Protocol
2 PPP = Point-to-Point Protocol
3 SLIP = Serial Line Internet Protocol
4 IP = Internet Protocol
5 NTP = Network Time Protocol
6 TACACS+ = Terminal Access Controller Access Control System Plus
7 VCCs = virtual channel connections
8 VPCs = virtual path connections
9 UNI = User-Network Interface
10 ILMI = Integrated Local Management Interface
11 IISP = Interim-Interswitch Signaling Protocol
12 LANE = LAN Emulation
13 LEC = LAN Emulation Client
14 LES = LAN Emulation Server
15 BUS = broadcast and unknown server
16 LECS = LAN Emulation Configuration Server
17 ARP = Address Resolution Protocol
18 OAM = Operation, Administration, and Maintenance
19 RMON = Remote Monitoring
20 CBR = constant bit rate
21 MCR = minimum cell rate
22 ABR = available bit rate
23 MIB = Management Information Base
24 UBR = unspecified bit rate
Table 4 Feature Sets Supported by the Catalyst 8540 CSR Part 1—Releases 12.0(28)W5(31) to 12.0(13)W5(19)
(28)
W5
(30a)
(28)
W5
(30)
(27)
W5
(29)
(26)
W5
(28)
(24)
W5
(26c)
(24)
W5
(26b)
(22)
W5
(25)
(20)
W5
(24b)
(20)
W5
(24)
(19)
W5
(23)
(18)
W5
(22)
(16)
W5
(21)
(13)
W5(
19c)
(13)
W5
(19)Layer 2 transparent bridging
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Layer 2 MAC learning, aging, and switching by hardware
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Spanning Tree Protocol (IEEE 802.1d) support per bridge group
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Spanning Tree SNMP trap support
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Maximum of 64 active bridge groups
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Integrated routing and bridging (IRB)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Route processor redundancy1
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Inter-Switch Link (ISL)-based VLAN trunking
x
x
x
x
x
x
x
x
x
x
x
x
x
x
802.1Q-based VLAN routing/bridging
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IP, IPX, and IP multicast routing and forwarding
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IP fragmentation support for POS/ATM uplink
x
x
x
x
x
x
x
x
x
x
x
x
x
x
AppleTalk 1 and 2 routing
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Up to 128 IP multicast groups
x
x
x
x
x
x
x
x
x
x
x
x
x
x
QoS-based forwarding based on IP precedence
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Load balancing among two equal-cost paths based on source and destination IP and IPX addresses
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Up to six equal-cost paths for IP and IPX; per-packet load balancing for IPX for Enhanced Gigabit Ethernet only
x
x
x
x
x
x
x
x
x
x
x
x
x
x
BGP (Border Gateway Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
RIP and RIP II (Routing Information Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IGRP (Interior Gateway Routing Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
EIGRP (Enhanced Interior Gateway Routing Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
OSPF (Open Shortest Path First)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Routing protocol MIB support (OSPF, BGP)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IPX (Internet Packet Exchange) RIP and EIGRP
x
x
x
x
x
x
x
x
x
x
x
x
x
x
PIM (Protocol Independent Multicast)— sparse and dense modes
x
x
x
x
x
x
x
x
x
x
x
x
x
x
RTMP (AppleTalk Routing Table Maintenance Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
AURP (AppleTalk Update-based Routing Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Secondary addressing
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Static routes
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Classless Interdomain Routing (CIDR)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Load sharing based on source and destination IP addresses of unicast packets
x
x
x
x
x
x
x
x
x
x
x
x
x
x
ISL trunking (routing/ bridging)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
ISL on the Fast EtherChannel
x
x
x
x
x
x
x
x
x
x
x
x
x
802.1Q routing/ bridging on the Fast EtherChannel
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Enhanced Gigabit Ethernet port adapters with built-in ACL functionality and 16, 64, or 256 KB of memory available for routing tables
x
x
x
x
x
x
x
x
x
x
x
x
x
x
MAC address filtering
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IP simple ACL (1-99, 1301-1999)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IP extended ACL (100-199, 2000-2699)
TCP ACL based on TCP-precedence, TCP port number, TCP ToS, and TCP flags
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IP extended ACL (100-199, 2000-2699)
UDP ACL based on UPD port number
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IP extended ACL (100-199, 2000-2699)
ICMP ACL
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IPX standard ACL (800-899) without source node
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IOS ACL for control plane traffic (for example, route update filter)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Named ACL
x
x
x
x
x
x
x
x
x
x
x
x
x
x
BOOTP (Bootstrap Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
CGMP (Cisco Group Management Protocol) server support
x
x
x
x
x
x
x
x
x
x
x
x
x
x
CDP (Cisco Discovery Protocol) support on Ethernet ports
x
x
x
x
x
x
x
x
x
x
x
x
x
x
DHCP (Dynamic Host Configuration Protocol) Relay
x
x
x
x
x
x
x
x
x
x
x
x
x
x
HSRP (Hot Standby Routing Protocol) over 10/100 Ethernet, Gigabit Ethernet, FEC, GEC, and BVI (Bridge-Group Virtual Interface)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
ICMP (Internet Control Message Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IGMP (Internet Group Management Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IPX SAP (Internet Packet Exchange Service Advertisement Protocol) and SAP filtering
x
x
x
x
x
x
x
x
x
x
x
x
x
x
SNMP (Simple Network Management Protocol)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Maximum of 32 active bridge groups with BVI
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Bundling of up to four Fast Ethernet ports in a maximum of 64 FECs
x
x
x
x
x
x
x
x
x
x
x
x
x
x
802.1q-based VLAN routing support
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Route filtering
x
x
x
x
x
x
x
x
x
x
x
x
x
x
ISL support on the GEC
x
x
x
x
x
x
x
x
x
x
x
x
x
x
802.1 routing support on the GEC
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Group Virtual Interface (BVI)
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Support for up to 200 IPX networks on interfaces and subinterfaces
x
x
x
x
x
x
x
x
x
x
x
x
x
x
1-port packet-over-SONET OC-12c uplink port adapter with built-in ACL functionality and a 1-port enhanced Gigabit Ethernet port adapter
x
x
x
x
x
x
x
x
x
x
x
x
x
x
IS-IS routing protocol
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Switching database manager
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: UNI 3.0
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: UNI 3.1
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: ILMI 3.1
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: RFC 1483 for Bridging
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: RFC for Routing (IP, IP multicast, IPX)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: RFC 1483 SVC support
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: 13-bit virtual circuit number with up to 8K VCs
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink 4096 simultaneous SARs
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: AAL 5
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: F4 and F5 flows of OAM cells
X
X
X
X
X
X
X
X
X
X
X
X
X
X
ATM uplink: Traffic shaping
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: RFC 1619 PPP over SONET/SDH
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: RFC 1662 PPP in HDLC-like framing
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: IP fragmentation for POS and ATM uplink
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: SONET MIB as defined in RFC 1575
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: Transparent Bridging (PPP/HDLC encapsulation)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: SPE payload scrambling
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: SONET alarms (LOS, LOF, AIS, and RDI detection or reporting)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
POS: Threshold Crossing Alerts for B1, B2, B3 with configurable thresholds
X
X
X
X
X
X
X
X
X
X
X
X
X
X
SNMP provisioning of ATM interface traps to an SNMP Host
X
X
X
X
X
X
IP multicast routing with up to 12,000 groups (S, G)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Bundling of up to four Gigabit Ethernet ports in a maximum of 8 Gigabit Ethernet Channels
X
X
X
X
X
X
X
X
X
X
X
X
X
X
1 Route processor redundancy for the Catalyst 8540 CSR
Table 5 Feature Sets Supported by the Catalyst 8540 CSR Part 2—Releases 12.0(10)W5(18c) to
12.0(1a)W5(6f)
W5(18c)
W5(18b)
W5(13d)
W5(13b)
W5(13)
WX5(11a)
W5(6f)Layer 2 transparent bridging
x
x
x
x
x
x
x
Layer 2 MAC learning, aging, and switching by hardware
x
x
x
x
x
x
x
Spanning Tree Protocol (IEEE 802.1d) support per bridge group
x
x
x
x
x
x
x
Spanning Tree SNMP trap support
x
Maximum of 64 active bridge groups
x
x
x
x
x
x
x
Integrated routing and bridging (IRB)
x
x
x
x
x
x
x
Route processor redundancy1
x
x
x
x
x
Inter-Switch Link (ISL)-based VLAN trunking
x
x
x
x
x
x
x
802.1Q-based VLAN routing/bridging
x
x
x
x
x
x
IP, IPX, and IP multicast routing and forwarding
x
x
x
x
x
x
x
IP fragmentation support for POS/ATM uplink
x
AppleTalk 1 and 2 routing
x
x
x
x
x
x
Up to 128 IP multicast groups
x
x
x
x
x
x
QoS-based forwarding based on IP precedence
x
x
x
x
x
x
x
Load balancing among two equal-cost paths based on source and destination IP and IPX addresses
x
x
x
x
x
x
x
Up to six equal-cost paths for IP and IPX; per-packet load balancing for IPX for Enhanced Gigabit Ethernet only
x
x
x
x
x
x
x
BGP (Border Gateway Protocol)
x
x
x
x
x
RIP and RIP II (Routing Information Protocol)
x
x
x
x
x
x
x
IGRP (Interior Gateway Routing Protocol)
x
x
x
x
x
x
x
EIGRP (Enhanced Interior Gateway Routing Protocol)
x
x
x
x
x
x
x
OSPF (Open Shortest Path First)
x
x
x
x
x
x
x
Routing protocol MIB support (OSPF, BGP)
x
IPX (Internet Packet Exchange) RIP and EIGRP
x
x
x
x
x
x
x
PIM (Protocol Independent Multicast)— sparse and dense modes
x
x
x
x
x
x
x
RTMP (AppleTalk Routing Table Maintenance Protocol)
x
x
x
x
x
x
AURP (AppleTalk Update-based Routing Protocol)
x
x
x
x
x
x
Secondary addressing
x
x
x
x
x
x
x
Static routes
x
x
x
x
x
x
x
Classless Interdomain Routing (CIDR)
x
x
x
x
x
x
x
Load sharing based on source and destination IP addresses of unicast packets
x
x
x
x
x
x
x
ISL trunking (routing/ bridging)
x
x
x
x
x
ISL on the Fast EtherChannel
x
x
x
x
x
x
x
802.1Q routing/ bridging on the Fast EtherChannel
x
x
x
x
x
x
x
Enhanced Gigabit Ethernet port adapters with built-in ACL functionality and 16, 64, or 256 KB of memory available for routing tables
x
MAC address filtering
x
x
x
x
x
x
x
IP simple ACL (1-99, 1301-1999)
x
x
x
x
x
IP extended ACL (100-199, 2000-2699)
TCP ACL based on TCP-precedence, TCP port number, TCP ToS, and TCP flags
x
x
x
x
x
x
IP extended ACL (100-199, 2000-2699)
UDP ACL based on UPD port number
x
x
x
x
x
x
IP extended ACL (100-199, 2000-2699)
ICMP ACL
x
x
x
x
x
x
IPX standard ACL (800-899) without source node
x
x
x
x
x
x
IOS ACL for control plane traffic (for example, route update filter)
x
x
x
x
x
x
Named ACL
x
x
x
x
x
x
BOOTP (Bootstrap Protocol)
x
x
x
x
x
x
x
CGMP (Cisco Group Management Protocol) server support
x
x
x
x
x
x
x
CDP (Cisco Discovery Protocol) support on Ethernet ports
x
x
x
x
x
x
x
DHCP (Dynamic Host Configuration Protocol) Relay
x
x
x
x
x
x
x
HSRP (Hot Standby Routing Protocol) over 10/100 Ethernet, Gigabit Ethernet, FEC, GEC, and BVI (Bridge-Group Virtual Interface)
x
x
x
x
x
x
x
ICMP (Internet Control Message Protocol)
x
x
x
x
x
x
x
IGMP (Internet Group Management Protocol)
x
x
x
x
x
x
x
IPX SAP (Internet Packet Exchange Service Advertisement Protocol) and SAP filtering
x
x
x
x
x
x
x
SNMP (Simple Network Management Protocol)
x
x
x
x
x
x
x
Maximum of 32 active bridge groups with BVI
x
x
x
x
x
Bundling of up to four Fast Ethernet ports in a maximum of 64 FECs
x
x
x
x
x
x
x
Bundling of up to four Gigabit Ethernet ports in a maximum of 8 Gigabit Ethernet Channels
x
x
x
x
x
x
x
802.1q-based VLAN routing support
x
x
x
x
x
x
x
Route filtering
x
x
x
x
x
x
x
ISL support on the GEC
x
x
x
x
x
x
x
802.1 routing support on the GEC
x
x
x
x
x
x
x
Group Virtual Interface (BVI)
x
x
x
x
x
x
x
Support for up to 200 IPX networks on interfaces and subinterfaces
x
x
x
x
x
x
x
IP multicast routing with up to 12,000 groups (S, G)
x
x
x
x
x
x
x
IS-IS routing protocol
x
x
x
x
x
x
x
Switching database manager
x
x
ATM uplink: UNI 3.0
x
x
ATM uplink: UNI 3.1
x
x
ATM uplink: ILMI 3.1
x
x
ATM uplink: RFC 1483 for Bridging
x
x
ATM uplink: RFC for Routing (IP, IP multicast, IPX)
x
x
ATM uplink: RFC 1483 SVC support
x
x
ATM uplink: 13-bit virtual circuit number with up to 8K VCs
x
x
ATM uplink 4096 simultaneous SARs
x
x
ATM uplink: AAL 5
x
x
ATM uplink: F4 and F5 flows of OAM cells
x
x
ATM uplink: Traffic shaping
x
x
POS: RFC 1619 PPP over SONET/SDH
x
x
POS: RFC 1662 PPP in HDLC-like framing
x
x
POS: IP fragmentation for POS and ATM uplink
x
x
POS: SONET MIB as defined in RFC 1575
x
x
POS: Transparent Bridging (PPP/HDLC encapsulation)
x
x
POS: SPE payload scrambling
x
x
POS: SONET alarms (LOS, LOF, AIS, and RDI detection or reporting)
x
x
POS: Threshold Crossing Alerts for B1, B2, B3 with configurable thresholds
x
x
1 Route processor redundancy for the Catalyst 8540 CSR
Release Names, Versions, and Part Numbers
Table 6 lists the release names, versions, and part numbers used with the Catalyst 8540 MSR. Table 7 lists the release names, versions, and part numbers used with the Catalyst 8540 CSR.
New and Changed Information
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.0. The new features are sorted by release number. Some releases include both platforms, others only include one platform.
New Features in Release 12.0(28)W5(31)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(28)W5(31).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(28)W5(31).
New Features in Release 12.0(28)W5(30a)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(28)W5(30a).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(28)W5(30a).
New Features in Release 12.0(28)W5(30)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(28)W5(30).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(28)W5(30).
New Features in Release 12.0(27)W5(29)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(27)W5(29).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(27)W5(29).
New Features in Release 12.0(26)W5(28)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(26)W5(28).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(26)W5(28).
New Features in Release 12.0(24)W5(26c)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(24)W5(26c).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(24)W5(26c).
New Features in Release 12.0(24)W5(26b)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(24)W5(26b).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(24)W5(26b).
New Features in Release 12.0(24)W5(26)
Catalyst 8540 MSR
The following new feature is available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(24)W5(26).
•
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(24)W5(26).
New Features in Release 12.0(22)W5(25)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(22)W5(25).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(22)W5(25).
New Features in Release 12.0(20)W5(24b)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(20)W5(24b).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(20)W5(24b).
New Features in Release 12.0(20)W5(24a)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(20)W5(24a).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(20)W5(24a).
New Features in Release 12.0(20)W5(24)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(20)W5(24).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(20)W5(24).
New Features in Release 12.0(19)W5(23)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(19)W5(23).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(19)W5(23).
New Features in Release 12.0(18)W5(22)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(18)W5(22).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(18)W5(22).
New Features in Release 12.0(16)W5(21)
Catalyst 8540 MSR
No new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(16)W5(21).
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(16)W5(21).
New Features in Release 12.0(13)W5(19c)
Catalyst 8540 MSR
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19c):
•
•
•
•
•
•
•
•
•
See the " Related Documentation" section for a list of documents that describe these features.
Catalyst 8540 CSR
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19c):
•
–
–
–
See the " Related Documentation" section for a list of documents that describe these features.
New Features in Release 12.0(10)W5(18c)
Catalyst 8540 CSR
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(10)W5(18c):
•
•
•
New Features in Release 12.0(7)W5(15c)
Catalyst 8540 MSR
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(7)W5(15c):
•
–
–
–
•
•
See the " Related Documentation" section for a list of documents that describe these features.
New Features in Release 12.0(5)W5(13b)
Catalyst 8540 CSR
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(5)W5(13b):
•
•
–
–
–
•
•
•
•
•
•
•
•
New Features in Release 12.0(4a)W5(11a)
Catalyst 8540 MSR
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(4a)W5(11a):
•
Note
•
•
•
•
•
Catalyst 8540 CSR
The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(4a)WX5(11a):
•
•
•
•
•
See the " Related Documentation" section for a list of documents that describe these features.
New Features in Release 12.0(1a)W5(9)
Catalyst 8540 MSR
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(9):
•
•
•
•
•
•
•
•
•
•
See the " Related Documentation" section for a list of documents that describe these features.
New Features in Release 12.0(1a)W5(7b)
Catalyst 8540 MSR
The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(7b):
•
•
•
•
•
See the " Related Documentation" section for a list of documents that describe these features.
New Features in Release 12.0(1a)W5(6f)
Catalyst 8540 CSR
No new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(1a)W5(6f).
Caveats
This section lists the caveats and corrected caveats for each release. Use Table 8 to determine the status of a particular caveat and its relevancy to your software release for the Catalyst 8540 MSR switch router. Use Table 9 to determine the status of a particular caveat and its relevancy to your software release for the Catalyst 8540 CSR switch router. In the tables, "C" indicates a corrected caveat, and "O" indicates an open caveat.
Caveat Symptoms and Workarounds
This section contains listings of the caveats for the Cisco IOS software:
–
–
–
–
•
Symptom: The wrong payload pattern in idle cells might be transmitted from DS-3 and E3 interfaces.
As per recommendation I.361 (of the ITU-T), the payload pattern of the idle cell is "01101010" or "0x6A". But in DS-3 and E3 interfaces of the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switches, the payload pattern of the idle cell is set to "00000000" or "0x00". This is incorrect as per the ITU-T specification.
Some interoperability issues with other devices might appear if those devices expect only the "0x6A" pattern.
Workaround: None.
•
Symptom: Using the show vc command displays garbage data for TVC(I) type interfaces with multiple leaves. Data for TVC(O) type interfaces with multiple leaves are displayed correctly.
Note
Workaround: Use the show atm vc command instead of the show vc command.
•
Symptom: A burst of noise on the physical link can cause the PNNI Hello for the link to stay in the down state on one end of the link and in the attempt state on the other end.
Workaround: Use the shutdown and no shutdown commands on the interface (or subinterface) to force the PNNI Hello to come up.
•
Symptom: The input and output counters for the OC-12 interface display a huge value. This problem is seen with traffic running just after bootup or after performing a "clear counters" when traffic is flowing across the link. For example:
4294944186 packets input, 4293742466 bytes, 0 no bufferWorkaround: None.
•
Symptom: The show NCDP sources command always displays "health: unknown" after configuration.
Workaround: None.
•
Symptom: In certain situations, the 8-port Gigabit Ethernet front end input queue displays negative values. This has been seen with the TTL value of 1 only in the lab.
This issue is cosmetic and has no effect on the performance of the Catalyst 8540 switch or on the 8-port Gigabit Ethernet interface module.
Workaround: None.
•
Symptom: After a switch processor switchover the input and output cells and the rate counters for IMA, CES, and OC-48 interfaces display incorrect values.
Workaround: None.
•
Symptom: The following issues could be seen on the simultaneous execution of certain PNNI CLIs.
The switch reloads when:
a.
b.
c.
d.
The following issues are also seen:
e.
f.
g.
h.
Workaround: None.
•
Symptom: On a Catalyst 8540 MSR, if an OC-3 interface is overbooked and configured with PVCs that consume more than 599 Mbps of bandwidth, during bootup these PVCs are lost from the running configuration.
The following error message appears during bootup for every PVC that is rejected.
%connection creation fails: specified traffic/resource parameters are invalidWorkaround: Configure the PVCs that were lost once the switch boots up.
•
Symptom: If the BITS port in T1 mode is the primary clock and it changes to "unlockable", the clock switches to the next priority clock but does not revert to the BITS port even when it is reconfigured correctly.
Workaround: Reconfigure the BITS clock source as in the following example:
switch(config)# no network-clock-select 1 BITS 0switch(config)# network-clock-select 1 BITS 0•
Symptom: The CBR interface module sends a "remote alarm" to the peer interface if the line flaps continuously. This causes the peer interface to change to "yellow alarm" state.
Workaround: Enter the shutdown and no shutdown commands on the CBR interface.
•
Symptom: When bursty traffic is sent to the ARM via a carrier module installed 1-port OC-12 interface module in a peer Catalyst 8540 MSR, the ARM interface displays underruns and drops packets.
Workaround: None.
•
Symptom: A memory leak might occur during an "atmSoft_timerProcess". With every "soft-vc" retry the holding memory on "atmsig CC" and "atm soft CV timer" increases and the "free" memory decreases. The free memory might fall to as low as 700K at times.
Workaround: None.
•
Symptom: The redundancy manual sync running config command does not synchronize the running-configuration files if the sync running config command is disabled at the "Switch(config-r-mc)#" configuration level.
Workaround: Use the automatic sync running config command by enabling it at the "Switch(config-r-mc)#" mode. For example:
Switch(config-r-mc)# sync config running•
Symptom: Packets received with a destination multicast MAC address and destination unicast IP address are forwarded to the Route Processor, which in turn forwards it like any normal IP packet
Workaround: None.
•
Symptom: The switch might reload if the show atm snoop-vc EXEC command is entered after an inverse multiplexing over ATM (IMA) interface that is being snooped is deleted.
Workaround: None.
•
Symptom: A fully utilized IMA group with eight E1 links is configured between two switches. The eight soft-VCs each use the resources offered by an E1 link. When traffic is flowing across the links and three of the links of the IMA group on one switch are shut down, traffic stops flowing through all soft-VCs. Then, soon after, the three links are shut down. Then all soft-VCs shut down and none of the VCs come up again.They remain in the NOT CONNECTED state.
Workaround: None.
•
Symptom: The console freezes when the OC-12 interface is used as a snoop test port.
Workaround: None.
•
Symptom: When you delete well-known VCs using the atm manual-well-known-vc delete command on a snooped interface and then execute a show snoop-vc command, the switch reloads.
Workaround: None.
•
Symptom: On the Catalyst 8540, Catalyst 8510 MSR, and the LightStream 1010 switch, Frame Relay traffic stops flowing through previously configured PVCs when you reload the image or reboot the switch. However, the VC appears up.
Workaround: None.
•
Symptom: The ATM uplink interface module on the Catalyst 8540 CSR sends multicast packets in 1483 bridge PDU format.
Workaround: None.
•
Symptom: If tag-switching is disabled on an interface being snooped and a show atm snoop-vc command is executed, the switch reloads.
Workaround: None.
•
Symptom: When the VCI range for tag switching is configured on an ATM interface, these VCI values are not reused when a new bind request is received.
Workaround: Disable and reenable tag switching on ATM interface.
•
Symptom: When you create a PVC with InARP configured, the PVCs was not linked to InARP chain. This means the broadcast packets are not sent through the InArp PVCs that are terminated on ATM0 interface. Because of this, routing updates are not sent causing OSPF/EIGRP neighbors to not be established.
Workaround: None.
•
Symptom: On a Catalyst 8540 MSR switch connected to a third party switch over an IMA connection with only one active link a synchronization error might occur on the third party switch.
This problem does not appear on connections between Cisco equipment, if there are at least two links in the IMA group, or if the E1/T1 link is not an IMA connection. This is caused by delayed ICP cells on the Cisco side causing the synchronization error.
Workaround: Use two or more active links in the IMA group or use a single link without the IMA configuration.
•
Symptom: A Catalysts MSR 8540 CES E1 structured channel connection, configured as synchronous, hangs due to line errors if the following occurs:
–
–
Workaround: Clear counters or enter the shutdown and no shutdown commands on the CBR interface.
•
A Cisco device running Cisco IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DoS) attack from a malformed BGP packet. Only devices with the command `bgp log-neighbor-changes' configured are vulnerable. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet.
If a misformed packet is received and queued up on the interface, this bug may also be triggered by other means which are not considered remotely exploitable such as the use of the command `show ip bgp neighbors' or running the command `debug ip bgp <neighbor> updates' for a configured bgp neighbor.
Cisco has made free software available to address this problem.
For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20050126-bgp.shtml
•
Symptom: Soft PVC call setup might fail going through third-party ATM switches. These third-party ATM switches might use Extended QoS Information Element (0xEC) with "Acceptable Backward Peak-to-Peak Cell Delay Variation Identifier" without the corresponding cumulative forward and/or backward Peak-to-Peak CDV.
Workaround: None.
•
Symptom: The 8-port Gigabit Ethernet interface module (C85GE-8X-64K) does not forward broadcasts when spanning is disabled. All connected ports have problems transmitting broadcasts out if the 8-port Gigabit Ethernet interface module:
–
–
–
Workaround: Make the connection on the 8-port Gigabit Ethernet interface module starting with the highest port number. For example, starting with port 8.
•
Symptom: On an interface module with a soft-VC configured, if an interface is shut down or if the interface module is removed from the chassis the following cause code appears in the "debug atm sig-all" display of subsequent soft-VC requests:
cause = normal call clearing, location = UserThis cause code is not correct. The "Resource Unavailable class definitions" cause code should appear.
Workaround: None.
•
Symptom: The Catalyst 8540 MSR might experience a memory leak on the Pool Manager and Frame Relay LMI.
Workaround: None.
•
Symptom: The CISCO-PROCESS-MIB is not present in Cisco IOS Release 12.0(4.6)W5(13) and Cisco IOS Release 12.0(24)W5(26c). You must configure SNMP on the switch.
Workaround: None.
•
Symptom: On the Catalyst 8540 MSR running Cisco IOS Release 12.1(20)E, the input packet counter wraps when reaching around 65000 packets. The following example shows the interface counters:
53816 packets input, 2852248 bytes, 0 no bufferA few seconds later, you see the following counters for the same interface display:
3067 packets input, 162551 bytes, 0 no bufferThis problem started after a reload of the switch and is seen on OC-3 interfaces.
Workaround: None.
•
Symptom: A fiber-optic Fast Ethernet interface module connecting a Catalyst 8540 to a Catalyst 5000 interface module, WS-U5533 or WS-U5538, might flap up-and-down intermittently. This might occur once per day or for longer intervals. Both the Catalyst 8540 and Catalyst 5000 ends of the connection log the link flap.
The problem occurs with the following interface modules:
–
–
This problem does not happen with WS-X5236-FX-MT.
Workaround: None.
•
Symptom: Using SNMP to create a soft VC fails if the source leg is on a VP-tunnel.
The UNDO_FAILED_ERROR appears and NOT CONNECTED appears in the X-Interface column of the show atm vc interface command display.
Workaround: None.
•
Symptom: A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
Workaround: None.
•
Symptom: On the Catalyst 8540 MSR a cross-connection PVC with a high VCI number cannot be created.
The following error message appears:
Switch(config)# interface atm 0/0/1Switch(config-if)# atm pvc 16 12311 interface ATM0/0/0 16 12311../c8540-atms5000/NP5500/NP55_token_mgmt.c 864: Out of ovc entries for msc 0../c8540-atms5000/NP5500/NP55_conn_resources.c 208: Couldn't allocate ovc - msc 0../c8540-atms5000/NP5500/NP55_connection.c 587: Couldn't allocate output side resources for msc 0%connection creation fails: connection installation failureOn interface ATM0/0/1 (16/12311) - interface ATM0/0/0 (16/12311)Switch# show debugGeneric ATM MMC:ATM MMC ERRORS debugging is onATM Connection Management event debugging is onATM Connection Management error debugging isswitch#Workaround: None.
•
Symptom: A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
Workaround: None.
•
Symptom: Using the show switch fabric command to request information about the different interfaces connected to the chassis does not reflect all of the different interface connections. Only the 155-Mbps interfaces appear in the display.
Workaround: None.
•
Symptom: A switched virtual circuit (SVC) may not get established causing ping command failures between routers. This symptom is observed in Cisco IOS Release 12.3.
Workaround: None.
•
Symptom: Building integrated timing supply (BITS) clocking problems.
If the clock source is changed to BITS and the network clock module fails to lock on to the BITS source, the network clock on the Catalyst 8540 MSR switches back to "System" (the internal Stratum 3 NetClk module). Immediately after that change, the primary route processor of the Catalyst 8540 MSR reloads because of a memory alignment error.
Workaround: None.
•
Symptom: On a Catalyst 8540 MSR running Cisco IOS Release 12.1(7a)EY, if you OIR the CES interface module the route processor might crash.
Workaround: None.
•
Symptom: When establishing soft-VP between switches, if a VP number is used by the previous switch and if that switch sends an error stating that "VPI" is already used, then the switch receiving that error should use a different VPI number during its next retry attempt. For example
Switch-1 (1/0/0)-------(1/0/0) Switch-2 (1/1/1)---------(1/1/1) Switch-3 (1/1/0)1. Assume a soft-VP call is getting initiated by Switch-1.
2. Assume that the node ID of Switch-3 is higher than Switch-2.
3. Assume that the Switch-2 ATM1/1/1 interface has a PVP configured with VPI 4 (ATM PVP 4).
In this scenario, when a call is initiated by Switch-1, it is forwarded by Switch-2 to Switch-3. Because the node ID of Switch-3 is higher than Switch-2, Switch-3 requests a VP number. If the request is for VPI 4 on Switch-3's ATM1/1/1, it will reach Switch-2's ATM1/1/1. Because there was a PVP configured on Switch-2's ATM1/1/1 interface with PVP 4, it is rejected stating that VPI is "unavailable". This error is sent to both Switch-1 and Switch-3. So, during the next attempt when Switch-3 requests a VPI number, it should request a different VPI number from 4.
Workaround: None.
•
Symptom: Problems occur in CISCO-ATM-IF-PHYS-MIB implementation:
1. ciscoAtmIfPhysLineFebeErrors returns Path FEBE errors instead of Line FEBE
errors.
2. ciscoAtmIfPhysPathFebeErrors returns Line FEBE errors instead of Path FEBE
errors.
This only happens with OC-3/STM1 or OC-12/STM4 interfaces.
Workaround: Poll ciscoAtmIfPhysLineFebeErrors when you need Path FEBE errors and poll ciscoAtmIfPhysPathFebeErrors when you need Line FEBE errors.
•
Symptom: The ATM interface does not reset the VCI/VPI connection after restart.
Workaround: None.
•
Symptom: Soft PVC does not come up.
If a Soft PVC originates from a Catalyst 8500 switch directly connected to an Alcatel switch, the Soft PVC never comes up. If the call originated from the Alcatel side, the Soft PVC comes up with no problem.
Note
For example:
At UNI ATM interface:
atm soft-vc 1 455 dest-add xx.348f.8001.bbfc.0000.0ba0.6f10.4080.210a.2a01.00 1 455 rx-cttr 1 tx-cttr 1Alcatel switch directly connected, ATM NNI, PNNI up and adjacency up:
show atm pnni neighbor---Neighbor Name: unknown, Node number: 40Neighbor Node Id: 88:160:xx.348F8001BBFC00000BA06F10.408021810A00.00Neighboring Peer State: FullLink Selection For CBR : minimize blocking of future callsLink Selection For VBR-RT : minimize blocking of future callsLink Selection For VBR-NRT: minimize blocking of future callsLink Selection For ABR : balance loadLink Selection For UBR : balance loadPort Remote Port Id Hello stateATM12/0/3 1281000 2way_in (Flood Port)---Switch# show atm routeP I 40 0 UP 0 39.348f.8001.bbfc.0000.0ba0.6f10/104---But, if the show atm pnni dtl node 40 ubr command is used:
*Apr 10 23:11:21.218: PNNI: UBR route request from ATM_OWNER_UNKNOWN*Apr 10 23:11:21.218: PNNI: To node 88:160:xx.348F8001BBFC00000BA06F10.408021810A00.00*Apr 10 23:11:21.218: PNNI: selected target node 40*Apr 10 23:11:21.218: priority: 2 (40 0) pnni-remote-internal*Apr 10 23:11:21.218: PNNI: Compute On-Demand Route Based On Admin Weight*Apr 10 23:11:21.218: PNNI: Failed To Find An On-Demand Route,Code: PNNI_RESOURCE_UNAVAILABLE*Apr 10 23:11:21.218: PNNI: No Route To88:160:xx.348F8001BBFC00000BA06F10.408021810A00.00*Apr 10 23:11:21.218: PNNI: Send Source Route ReplyTo Requestor: Code PNNI_RESOURCE_UNAVAILABLE---When the call is initiated from the Catalyst 8500 switch, nothing comes up over to the Alcatel switch. At the same time, when the call is initiated from the Alcatel switch, the Soft PVC comes up:
Switch# show atm vc interface atm 9/1/1Interface VPI VCI Type X-Interface X-VPI X-VCI Encap StatusATM9/1/1 0 5 PVC ATM13/0/0 0 72 QSAAL UPATM9/1/1 0 16 PVC ATM13/0/0 0 40 ILMI UP>>Alcatel Init <<<<ATM9/1/1 0 400 SoftVC ATM12/0/3 0 227 UP>> LS1010 Init <<<<ATM9/1/1 1 455 SoftVC NOT CONNECTEDWorkaround: None.
•
Symptom: A memory leak occurs in the ATMSIG processes. This is observed using the show processes memory command. The ATMSIG processes hold increasing amounts of memory and free memory is decreasing.
Note
Workaround: None. The switch must be rebooted to recover.
•
Symptom: When configuring a soft-VC on the Catalyst 8540 or the switch on the other end, the VC will not come up.
The debug atm sig-soft command shows the following on the Catalyst 8540 MSR.
Mar 13 21:50:57: ATMSOFT(ATM1/1/0 vpi = 253; vci = 129) Received SETUPMar 13 21:50:57: ATMSOFT(ATM1/1/0 vpi = 253; vci = 129) half leg alloc/rmreserve failMar 13 21:50:57: ATMSOFT(ATM1/1/0 vpi = 253; vci = 129) Call rejectedMar 13 21:50:57: reason: vpi/vci has been used received rel comp atdest, bad param,could be relcollision pvlIfCB_p:0 pvlVpi:0 pvlVci:0Workaround: None.
•
Symptom: On a switch running Cisco IOS Release version 120-24.W5.26b, the switch might crash due to a system restarted by a bus error at PC 0x6063F9C8, address 0xD0D0D15.
Workaround: None.
•
Symptom: Whenever you attempt to update the Access Control List (ACL) attached to the management interface (Ethernet2/0/0) on the switch, the following error message appears:
ACL is not supportedACL functionality on the interface is not affected.
Workaround: None.
•
Symptom: The Catalyst 8540 CSR might display the following messages when running Cisco IOS Release 12.0(20)W5(26) software:
Jan 9 160611 EST %ALIGN-3-CORRECT Alignment correction made at0x603954BC reading 0x6200E625Jan 9 160611 EST %ALIGN-3-TRACE -Traceback= 603954BC 6036BD246036BB58 60076ABC 6005C948 6005CA80 6005CDCC 6007C4E4There is no noticeable impact to the operation of the switch.
Workaround: Downgrade to Cisco IOS Release 12.0(20)W5(24a) software or earlier.
•
Symptom: On the Catalyst 8540 CSR the Underruns counter on the egress interface increment. This occurs because the Catalyst 8540 CSR is a cut through switch and it starts forwarding once a predefined number of bytes are received by the ingress interface. However, if any input errors occur (for example, bad CRC, alignment errors, or giant packet errors) after the switch starts forwarding, the switch would have already started forwarding the frame and will register an underrun error on the egress port.
To determine the cause of underruns on a particular interface, the counters on all other Fast Ethernet or Gigabit Ethernet interfaces need to be checked for input errors and eliminated.
Note
Workaround: None.
•
Symptom: Under certain circumstances, when an OC-12 interface flaps up-and-down on a Catalyst 8540 MSR running Cisco IOS Release 12.1(12)E or EY software, the switch fabric might start dropping cells on VCs exiting this interface
Workaround: This problem might go away if you reload the switch image.
•
Symptom: Cisco routers and switches running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected. A workaround is available.
Cisco has made software available, free of charge, to correct the problem.
Workaround: This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml
•
Symptom: The Catalyst 8540 might display following error messages:
xpif_read_media_type: Null ds structure for Port-channel1xpif_read_media_type: Null ds structure for Port-channel1Workaround: None.
•
Symptom: Internal buffers (vbufs) are exhausted, ASSERTION FAILED, and some high-priority IPC (interprocess communications) drops occur.
Workaround: None.
•
Symptom: Catalyst 8540 CSR hangs and must be rebooted. But, several errors appear, as in the following:
Nov 11 20:31:31 GMT: %LSS-7-INTERNAL_ASSERT: clear_conn_entry:: (swidb_p != NULL) AssertionFailure - File ../ls-switching/lss_pm_api.c Line 1390-Process= "LSS IPmcast Process", ipl= 0, pid= 89-Traceback= 605F931C 605FFE1C 605FFC38 6070D47C 6070F388 607137B8 60713F24 60097734 60097720Nov 11 20:31:31 GMT: %LSS-7-INTERNAL_ASSERT: clear_conn_entry:: (coredb_p != NULL) AssertionFailure - File ../ls-switching/lss_pm_api.c Line 1397-Process= "LSS IPmcast Process", ipl= 0, pid= 89-Traceback= 605F9384 605FFE1C 605FFC38 6070D47C 6070F388 607137B8 60713F24 60097734 60097720Nov 11 20:32:13 GMT: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x605FFDE0 reading 0xCNov 11 20:32:13 GMT: %ALIGN-3-TRACE: -Traceback= 605FFDE0 605FFC38 6070D47C 6070F388 607137B860713F24 60097734 60097720Nov 11 20:32:13 GMT: %ALIGN-3-TRACE: -Traceback= 605FFDE8 605FFC38 6070D47C 6070F388 607137B860713F24 60097734 60097720Nov 11 20:32:13 GMT: %ALIGN-3-TRACE: -Traceback= 605FFE10 605FFC38 6070D47C 6070F388 607137B860713F24 60097734 60097720Nov 11 20:32:13 GMT: %ALIGN-3-TRACE: -Traceback= 605F9328 605FFE1C 605FFC38 6070D47C 6070F388607137B8 60713F24 60097734Nov 11 20:32:13 GMT: %ALIGN-3-TRACE: -Traceback= 605FEE48 605F93EC 605FFE1C 605FFC38 6070D47C6070F388 607137B8 60713F24Nov 11 20:32:13 GMT: %ALIGN-3-TRACE: -Traceback= 605FFE1C 605FFC38 6070D47C 6070F388 607137B860713F24 60097734 60097720Nov 11 20:32:18 GMT: %LSS-7-INTERNAL_ASSERT: lss_ipm_chk_shr_vc: (main_lss_mdb->vci == lss_mdb->vci) Assertion Failure - File ../ls-switching/lss_mro2-Process= "IP Input", ipl= 0, pid= 53-Traceback= 6070DC58 607115D4 60711A24 60712D14 60293270 60291440 60291028 601B4228 601B3580601B375C 601B38D0 60097734 60097720Nov 11 20:32:21 GMT: %LSS-7-INTERNAL_ASSERT: lss_ipm_chk_shr_vc: (main_lss_mdb->vci == lss_mdb->vci) Assertion Failure - File ../ls-switching/lss_mro2-Process= "IP Input", ipl= 0, pid= 53-Traceback= 6070DC58 607115D4 60711A24 60712D14 60293270 60291440 60291028 601B4228 601B3580601B375C 601B38D0 60097734 600977208540c#8540c# show alignmentAlignment data for:L3 Switch/Router Software (C8540CSR-IN-M), Version 12.0(5)W5(13b) RELEASE SOFTWARECompiled Thu 24-Feb-00 15:31 by integNo alignment data has been recorded.Total Spurious Accesses 26, Recorded 7Address Count TracebackC 3 0x605FFDE0 0x605FFC38 0x6070D47C 0x6070F388 0x607137B8 0x60713F24 0x600977340x6009772014 3 0x605FFDE8 0x605FFC38 0x6070D47C 0x6070F388 0x607137B8 0x60713F24 0x600977340x600977201A 3 0x605FFE10 0x605FFC38 0x6070D47C 0x6070F388 0x607137B8 0x60713F24 0x600977340x6009772050 3 0x605F9328 0x605FFE1C 0x605FFC38 0x6070D47C 0x6070F388 0x607137B8 0x60713F240x6009773450 3 0x605FEE48 0x605F93EC 0x605FFE1C 0x605FFC38 0x6070D47C 0x6070F388 0x607137B80x60713F24A0 3 0x605FFE1C 0x605FFC38 0x6070D47C 0x6070F388 0x607137B8 0x60713F24 0x600977340x6009772034 8 0x6042DA38 0x6042D5AC 0x6014B7BC 0x6014C45C 0x60147368 0x60156AC8 0x601E24B00x60097734Version found in Cisco IOS Release L3 Switch/Router Software (C8540CSR-IN-M), Cisco IOS Release 12.0(5)W5(13b).
System image file is "bootflash:cat8540c-in-mz.120-5.W5.13b.bin".
Features being used include:
–
–
–
–
–
–
Workaround: None.
•
Symptom: Ethernet interface modules fail Online Access Test after upgrade from Cisco IOS Release 12.0.5.W5.13 to Cisco IOS Release 12.0.22.W5.25.
Workaround: This access test failure is caused by the incompatibility of hardware version (4.1) and firmware version (2.1) of the Ethernet interface modules installed in the switch. By upgrading to the latest firmware version (3.3), this problem can be resolved.
•
Symptom: The show ces address command has been enhanced to provide CES address directly via SNMP for the Catalyst 8540 MSR.
Workaround: None.
•
Symptom: On a Catalyst 8540 MSR switch, in the show switch fabric command display the Rx Cells and Tx Cells counters remain at 0 under MSC3 even though traffic is flowing through the ports linked to that MSC.
Note
Workaround: None
•
Symptom: Cell drops occur at an OC-12 interface module with a Hierarchical VP tunnel if the hierarchical VP tunnel is configured on interface 0, the primary Route Processor is in slot 8, and the secondary Route Processor has come up in slot 4.
This same problem might occur if a hierarchical VP tunnel is defined on interface 9, the primary Route Processor is in slot 4, and the secondary Route Processor has come up in slot 8.
This happens when the secondary Route Processor boots up and there is a Hierarchical VP tunnel on any of the interfaces that share the same MSC as the secondary Route Processor.
This does not occur if the Redundant Route Processor is never booted.
Workaround: Use slot 2 or slot 11 for OC12 interface module with the hierarchical VP tunnel.
•
Symptom: Input errors on interface ATM0 are incrementing one per minute. Only Input errors is incrementing and no other counters (For example, CRC and other errors).
Workaround: None.
•
Symptom:
The Cisco Catalyst 8540 switch running Cisco IOS Release 12.0(18)W5(22) might experience a memory leak in pool manager.
The system logs may indicate tracebacks similar to the following:
%SYS-2-MALLOCFAIL: Memory allocation of 496 bytes failed from 0x6006CA58, poolProcessor, alignment 0 -Process= "Pool Manager", ipl= 6, pid= 4-Traceback= 6009E434 6009FEE0 6006CA60 600AA200 6009968C 60099678For further information on memory leaks, refer to Troubleshooting Memory Problems http://www.cisco.com/warp/public/63/mallocfail.shtml#subfour
Workaround: None.
•
Symptom: The K1 might reset itself when a getbuffer fails in Cisco IOS software for tunneled packets or IPC through mailbox.
Workaround: None.
•
Symptom: A Catalyst 8540 MSR switch running Cisco IOS Release 12.0(16)W5(21a) may display the following error message:
%ATMCORE-3-INTERNAL_ERROR: ATOM ERROR: leg->snmpInfo.xconnectIndex is NULLThis message is displayed during SNMP polling.
Note
Workaround: None.
•
Symptom: The Catalyst 8500 MSR switch might experience a memory leak with the IP Simple Network Management Protocol (SNMP) process.
Workaround: None.
•
Symptom: The IMA interface module does not generate a syslog message when the link goes down.
Workaround: None.
•
Symptom: Hosts that do not transmit data frequently and are connected to the Catalyst 8500 switch through an 8-port Gigabit Ethernet module are intermittently unreachable.
The connectivity to the hosts eventually recovers.
Workaround: None.
•
Symptom: Enable optipoll by default on switches running 12.0W5 based images to permanently remove ILMI/SNMP timing issues for ILMI keepalive messages.
Workaround: None.
•
Symptom: A Catalyst 8500 MSR running Cisco IOS Release 12.0(20)W5(24b) might crash with a bus error in the SNMP code.
Workaround: Disabling polling chassis MIBs might prevent the crash.
•
Symptom: If you disconnect the transmit cable from an E1 CBR interface on a Catalyst 8540, the interface still appears up/up. No indication of error messages appear in the log files.
When the transmit cable is reconnected, it starts to transmit traffic again. However, if the transmit cable is disconnected multiple times, the link does not pass traffic even when the transmit cable is reconnected.
Workaround: Use the shutdown and no shutdown commands on the interface and it returns to normal, or disconnect the receive cable and reconnect it.
•
Symptom: On a Cisco 6400 Node Switch Processor (NSP) running Cisco IOS Release 12.2(2)B and its derivatives, using the atm ping command to test a valid and active VP might fail with the following message:
Jun 20 15:56:17.742: %ATMCORE-3-INTERNAL_ERROR: atmCore_oamRcvPing: No match.The failure occurs when running the ping towards specific destination ATM switches, and is dependent on the format of the loopback cell received from the destination ATM switches. The occurrence of this problem is difficult to predict and depends on the particular ATM switch implementation of the destination switch.
Workaround: None.
•
Symptom: A Cisco 6400 NSP, running Cisco IOS Release 12.1(5)DB or 12.2(2)B, displays the following error message when you use the atm ping interface atm slot/subslot/port VPI VCI end-loopback command and enter the wrong VP/VC combination:
connection doesn't existAny future atm ping commands to any connections (both valid and invalid) always result in the same error message and the ping commands fails. It fails even if the connection is valid, and even if a VP ping is used (for example, no VC number is specified).
You can still use the IP ping command to diagnose the connectivity between the NRP2 (Node Route Processor 2) and NSP.
Workaround: None.
•
Symptom: Queue stuck on Catalyst 8540 MSR switch backplane. One of the cross-connect VCs on the ATM switch backplane is stuck and causing packet loss on traffic passing over the stuck VC.
Workaround: Either OIR the interface module (either a software OIR or the physical OIR) or reload the software image.
•
Symptom: A Catalyst 8540 CSR configured for IRB/BVI does not perform MAC learning in the microcode based on the reception of ARP requests. This includes gratuitous ARPs. This might cause problems with redundancy and failover mechanisms that rely on advertising the new location of a virtual IP/MAC pair via gratuitous ARP. Gratuitous ARP updates the bridge and ARP tables of devices in the network when a failover occurs. The Cisco PIX firewall also uses this mechanism for failover.
Workaround: There is no workaround for this problem in an IRB configuration on this platform. In a bridging only configuration, this problem does not occur.
Clearing the bridge table removes the condition. After the aging period (5 minutes) the connection is also restored.
•
Symptom: Switch processors must be the same hardware version or boot failure occurs. For example, a switch processor with hardware version 8.0 and RMA=0 and a switch processor with hardware version 7.2 and RMA=1, cause the switch to hang when booted. But, RMA number does not matter, for example, a switch processor, hardware version 8.0 with RMA=0 and a switch processor, hardware version 8.0 with RMA=1 function correctly in the same chassis.
This creates an issue when RMAing a new unit. You MUST check the switch processor hardware version in lab first to determine if it is the same version as the switch processor installed in the chassis.
Workaround: Remove ALL linecards and leave only the two switch processors and one route processor in the chassis. this will boot successfully and then you can determine the hardware versions (Hw Vrs) of each switch processor and confirm that they are the same.
•
Symptom: Loopback not working properly on ATM T1 interface module. Duplicate of DDTS CSCdw22559.
Workaround: None.
•
Symptom: A switch running Cisco IOS Release 12.0(19)W5(23) might display the following error messages in the log:
%SYS-2-NOBLOCK: idle with blocking disabled.-Process= "ATMSIG Client", ipl= 0, pid= 77CEST: %SYS-2-BLOCKHUNG: Task hung with blocking disabled, value = 0x1.-Process= "ATMSIG Client", ipl= 0, pid= 77Functionality of the switch is not affected.
Workaround: None.
•
Symptom: Avaya PBX and Definity PBX interoperability testing.
The following caveats exist for signalled ATM point-to-multipoint (P2MP) connections and the debugging of issues related to them on the Catalyst 8500 ATM switches:
–
–
–
–
Workaround: None.
•
Symptom: A Catalyst 8540 MSR running Cisco IOS (tm) PNNI Software (cat8540m-WP-M), Release 12.0(20)W5(24a) RELEASE SOFTWARE, and using the QUAD E3 interface module might experience a limitation to the number of soft-VCs that can be established to its interfaces.
Output seen on the remote switch indicates "NOT CONNECTED" when using the show atm vc command.
The following similar output might appear when using the debug atm sig-soft interfaces atm card/subcard/port command:
*May 14 06:57:09.511: ATMSOFT(ATM10/1/0 vpi = 249; vci = 32 ) Received SETUP*May 14 06:57:09.511: ATMSOFT(ATM10/1/0 vpi = 249; vci = 32 ) tx/rcv row indexs*May 14 06:57:09.511: RxQosIndex = 2147483647 TxQosIndex = 2147483647*May 14 06:57:09.511: ATMSOFT(ATM10/1/0 vpi = 249; vci = 32 ) Prepare for XConnect Installation*May 14 06:57:09.511: ATMSOFT(ATM10/1/0 vpi = 249; vci = 32 ) Call rej - xconnect fail*May 14 06:57:09.511: ATMSOFT(ATM10/1/0 vpi = 249; vci = 32 ) Call rejected*May 14 06:57:09.511: reason: connection installation failure received rel comp at dest, bad param,could be rel collision pvlIfCB_p:0 pvlVpi:0 pvlVci:0Workaround: None.
•
Symptom: When setting up SVCs over an NNI link, one system becomes the master in terms of deciding which VPI/VCIs are assigned to SVCs. When the slave signals a Connection ID in SETUP, it may specify a VPI/VCI value. The Catalyst 8540 MSR signals the lowest VCI in the address range.
When signaled over a VP tunnel, the Connection Identifier IE formulated by the slave specifies that the VCI signalled is to be ignored.
However, when connection management allocates the half-leg for the ingress interface, if the connection ID specified in the ID matches an already-existing connection, and the connection signaled is point-to-multipoint link, the Connection Manager assumes the signaled SVC is the same as the one already allocated. This causes two SVCs point to the same VPI/VCI. This, subsequently, results in the deletion of the existing half-leg, the bandwidth allocated by the SVC lost, and the existing connection turned into a half-leg connection (dangling).
Workaround: None. The dangling half-leg can be recovered for SVCs by using the shutdown and no shutdown commands on the interface.
•
Symptom: You should not configure a structured CES circuit with more than 19 timeslots across a T1 ATM interface on a Catalyst 8540 MSR. While the circuit can be configured with more than 19 timeslots and will be built over the T1 ATM interface, the Catalyst 8540 MSR will discard cells on the configured VC causing errors on the emulated circuit.
With 20 timeslots configured you see cells queued and dropped (CLP0 Q full drop) on the PVC. This problem occurs when both hard and soft PVCs are configured over the T1 ATM interface.
To detect the problem, use the show atm vc int atm card/subcard/port vpi vci command and confirm the Clp0 q full drops field is increasing.
Switch# show atm vc interfaces atm 2/0/3 0 50Interface: ATM2/0/3, Type: oc3suniVPI = 0 VCI = 50Status: UPTime-since-last-status-change: 00:29:20Connection-type: PVCCast-type: point-to-pointPacket-discard-option: disabledUsage-Parameter-Control (UPC): passWrr weight: Not-applicableNumber of OAM-configured connections: 0OAM-configuration: disabledOAM-states: Not-applicableCross-connect-interface: ATM0/0/0, Type: t1suniCross-connect-VPI = 0Cross-connect-VCI = 50Cross-connect-UPC: passCross-connect OAM-configuration: disabledCross-connect OAM-state: Not-applicableThreshold Group: 1, Cells queued: 126Rx cells: 6007758, Tx cells: 5866714Tx Clp0:5866714, Tx Clp1: 0Rx Clp0:6007758, Rx Clp1: 0Rx Upc Violations:0, Rx cell drops:140920Rx Clp0 q full drops:140920, Rx Clp1 qthresh drops:0 <-------Cells are dropped HereRx connection-traffic-table-index: 1448Rx service-category: CBR (Constant Bit Rate)Rx pcr-clp01: 1448Rx scr-clp01: noneRx mcr-clp01: noneRx cdvt: 1024 (from default for interface)Rx mbs: noneTx connection-traffic-table-index: 1448Tx service-category: CBR (Constant Bit Rate)Tx pcr-clp01: 1448Tx scr-clp01: noneTx mcr-clp01: noneTx cdvt: noneTx mbs: noneWorkaround: Configure the structured CES circuit to only use 19 or fewer timeslots.
•
Symptom: A PNNI PVC link on an NNI interface might flap after the link stabilizes and the ATM PNNI VC component does not come back up.
Workaround: "Bounce" the PNNI process using the no atm router pnni and atm router pnni configuration commands to disable and enable the PNNI processes.
•
Symptom: Many PHY parity errors might appear on your switch from traffic through the OC-12 line module which causes PHY Parity Error interrupts. This could cause high CPU utilization (approximately 90percent) during a route processor switchover. This problem is caused by the PHY Parity Check bit in the SMR register being set to "1"(enabled) on a route processor switchover. The SMR register is set from 0x0 to 0xF during switchover, thereby enabling the PHY Parity Check bit. This default value of this register should be 0x0 (PHY Parity Check disabled).
Workaround: None.
•
Symptom: An unexpected reload of the switch occurs when you try to set the MIB object pnniSummaryAddressSuppress (PNNI-MIB).
This occurs when there is a summary for an ATM address prefix and you are still trying to set a summary suppress for the same ATM address prefix through the SNMP interface.
Workaround: None.
•
Symptom: The Catalyst 8540 MSR running Cisco IOS Release 12.0(18)W5(22) is unable to ping device off of the 8 port Gigabit Ethernet interface module.
Reload resolves this issue temporarily, only to reoccur in 10 to 15 days.
Workaround: Reload the switch.
•
Symptom: A Soft VC or Soft PVC connecting two ATM interfaces in the same Catalyst 8540 MSR might become stuck for no reason.
Workaround: Remove and reapply the Soft VC configuration on the source ATM interface.
•
Symptom: After you perform an OIR or a switch reload, the counter from show atm interfaces atm command displays an incorrect output rate value.
Workaround: None.
•
Symptom: A SNMP get-request on the MIB object pnniLinkIfIndex that is defined in the PNNI-MIB module returns 0.
This symptom is observed on PNNI interfaces of Cisco ATM switches. The symptom does not occur on virtual path tunnel interfaces.
Workaround: None.
•
Symptom: When the Cisco ATM switch is running UNI 4.0 with a Fore or Marconi switch, it might release a call because of unsupported traffic parameters.
This occurs when the Cisco ATM switch is connected to the other vendor equipment and configured to operate with UNI 4.0 version across the link and as a non-negotiated link. If any traffic parameter values are modified, the Cisco ATM switch treats this as a fatal error and releases the call.
Workaround: Hardcode the UNI version to 3.1
•
Symptom: On Frame Relay soft VCs, all frames sent with DE (discard eligibility) bit set are dropped at the serial interface even when the UPC is configured as "tag-drop" for the Soft VC.
Workaround: None.
•
Symptom: When using ATM Frame Relay IWF on a Catalyst 8500 MSR running Release 12.0(18)W5(22) or later, the output queue of the pseudo-ATM interface might go to 40/40 and remain there even if no traffic is going through the switch on the ATM-FR circuits.
Note
Workaround: None.
•
Symptom: On an ATM router module (ARM) that is running Cisco IOS Release 12.0(13)W5(19c), the ARM port may become stuck when a backup server is moved to a different switch.
Workaround: Configure the epc port-reload global configuration command for autorecovery on the stuck ARM port.
•
Symptom: When a port on a Catalyst 8540 CSR is configured as a snoop (monitor) port, the traffic on the snoop port becomes corrupted. Sniffing the same traffic on the attached Catalyst switch shows that the traffic itself is not corrupted. The problem occurs because the snoop port does not give reliable information to the monitoring station attached to that port.
Workaround: None.
•
Symptom: LightStream 1010 switches running 12.0(X)W5 IOS may not completely adhere to the ITU-T Q.2971 "B-ISDN DSS2 UNI Layer 3 Specification for Point-to-Multipoint Call/Connection Control." This could affect interoperability.
Workaround: Configure UNI Version 3.1 on the switch interfaces if the point-to-multipoint interoperability issue is observed.
•
Symptom: A switch configured for IMA bundling may not log link up and down messages. Only messages displaying the clock changes are logged as in the following example:
04:23:21: %CLOCKSW: Switching from ATM1/1/1 to ATM1/1/004:24:26: %CLOCKSW: Unswitching from ATM1/1/0 to System04:25:21: %CLOCKSW: Switching from System to ATM1/1/104:26:06: %CLOCKSW: Unswitching from ATM1/1/1 to SystemAs each interface recovers revertive clocking the messages appear correctly and source is recovered. Messages appear incorrectly if there are multiple links going up and down and only CLOCKSW messages are received without reporting status of the interface.
The correct physical status can be viewed properly with the show ima interface and show ima interface atm card/subcard/port detail commands. These commands accurately display the status of the port with usual counters.
Note
Workaround: None.
•
Symptom: An error can occur with management protocol processing.
Workaround: Use the following URL for further information: http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
•
Symptom: The switch silently drops OAM F5 with OAM intercept enabled.
The switch might drop OAM (Operation Administration and Maintenance) F5 END Loopback cells with its default configuration of OAM intercept.
Workaround: Disable OAM intercept to avoid dropping F5 OAM cells.
•
Symptom: Multicast packets of some specific lengths (121 bytes to 240 bytes) cause a portstuck condition on the ATM router module interfaces.
Workaround: None.
•
Symptom: The IRB connection has no connectivity in a native VLAN across ISL/dot1q Gigabit Etherchannel in the same bridge-group. However, there is connectivity on other VLANs.
Workaround: Configure a dummy VLAN as a native VLAN on the dot1q trunk.
•
Symptom: If you use the no negotiation auto command in interface configuration mode on a 2-port Enhanced Gigabit Ethernet interface module with GMAC-D2 (hw-version 6.0 onwards), any packets larger than 1518 bytes or less than 64 bytes are filtered by the GMAC (Gigabit Ethernet Media Access Controller).
Workaround: Reload the particular interface using the epc portstuck-manual-reload interface card/subcard/port command.
•
Symptom: If you configure VC-snooping on a sub-interface, then delete the subinterface, then recreate it, and if you then use the no atm snoop command to disable snooping on the same subinterface, the switch crashes.
Workaround: None.
•
Symptom: The console might hang if you use the hw-module subslot x/y reset command on the Frame Relay E1 port adapter.
Workaround: Shutdown all the controllers in the port adapter before issuing the hw-module subslot x/y reset command.
•
Symptom: Unusual delays occur in Frame Relay VC counter updates on Frame Relay ATM interface modules.
Workaround: None.
•
Symptom: A LightStream 1010 running 12.0(19)W5(23) showed the following alignment error:
Dec 11 08:04:28.227 MET: %ALIGN-3-CORRECT: Alignment correction made at 0x60329860 reading 0x614202C1Workaround: None.
•
Symptom: After upgrading to Cisco IOS Release 12.0(19)W5(23) the following error message appears in the system log:
*Nov 25 15:47:31: ACL Daughter Card detected on the PAMin Slot [9]*Nov 25 15:47:32: ipc_send2wire: No Mlet code for type: 111*Nov 25 15:47:32: ipc_send2wire: No Mlet code for type: 111This has no effect on the switch.
Workaround: None.
•
Symptom: When an IMA interface module is installed in the switch chassis, and if "loopback PIF" is configured on any OC-3 or OC-12 interface, loopback is NOT reflected when queried through SNMP. Loopback is NOT actually being set.
Workaround: None.
•
Symptom: If an IMA port that is connected to an IMA interface module installed in a Catalyst 8540 MSR is reset, it can cause the installed IMA interface module to fail.
Workaround: An OIR of the IMA interface module clears the failed state and restores service.
•
Symptom: Only 147 Mbps of resources are available on the ATM interfaces of the ARM and ARM II modules.
Workaround: None.
•
Symptom: The output of the show memory command displays incorrect values for PrevF and NextF fields. This may result in the Exec stack getting corrupted. This has no impact on the performance of the switch.
Workaround: None.
•
Symptom: A high number of cells stuck in the memory buffer causes the CPU to miss the periodic poll of a certain module or interface, leading to a port stuck message. Occurrences are random and there is no predetermined sequence of events that causes this to happen.
Workaround: None.
•
Symptom: You might see a Bus Error exception at get_slot_ptr while trying to do the continuous snmpwalk on the ciscoLS1010SubModuleGroup object of CISCO-RHINO-MIB and simultaneously toggling the redundant power-supply after at least one route processor switchover.
Workaround: None.
•
Symptom: For Frame Relay terminating PVCs on Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 switches, effective "Inverse ARP Frequency" value will be 60,000 times greater than the actual intended value.
Workaround: None.
•
Symptom: Two Catalyst 8500 switches are connected with only one level of PNNI hierarchy on one switch (level:56) and three levels on the other switch (levels:56,64 and 104) and the switches are at the same peer group at the highest level. There are 15 CBR shaped tunnels and 15 unshaped tunnels on the connecting link between the switches. In this situation, UBR soft-VCs are not set up between the switches when there are more than 10 CBR shaped tunnels configured on the link between the switches. Plus, memory is held up because of the soft-VC setup retries. Eventually the amount of memory held up inhibits you from executing certain commands.
Workaround: None.
•
Symptom: The Catalyst 8540 might experience a port stuck condition on the ATM router module (ARM) interface with a PVC configured.
Workaround: Use the epc port-reload command to automatically recover from portstuck.
•
Symptom: Shaping is not available for outgoing signalling VC on the Catalyst 8540 MSR switch.
Workaround: None.
•
Symptom: A Catalyst 8510 CSR might produce power supply error messages when writing to the bootflash:
kockopes#copy slot0:cat8510c-in-mz_120-18_W5_22.bin bootflash: Destination filename [cat8510c-in-mz_120-18_W5_22.bin]? CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCC 00:08:37: %CI-3-PSFAIL: Power supply 1 failureCCCCCCCCCCCCCCCCCCCCCCCC 00:08:40: %CI-6-PSOK: Power supply 1 OKCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCWorkaround: None.
•
Symptom: Once the route processor switches over, the following error message is seen on the new Primary route processor if you have a Gigabit processor interface module installed:
%ONLINEDIAG-6-ACCESS_TEST_WARNING: Unable to read from card in slot 10 sub_card 0.Enter the show diag online access command to get more details about the failure.
Workaround: None.
•
Symptom: The "DE bit tagged locally" counter should increment for all frames above the CIR and conforming to the policy. This feature is available on Stratacom ATM switches.
Workaround: None.
•
Symptom: A Catalyst 8500 switch rejects SVC video calls. After first video call is built, all other video calls are rejected, and a message similar to the following is generated when a debug atm sig-all atm x/y/z command is entered:
ATMSIG(0/0/0:11 11,35 - 0023/00):(vcnum:0) building cause code - cause = (0x23)requested VPCI/VCI not available, IE_cause = (0x23)requested VPCI/VCI not available, location = Private Network 1d02h: ATMSIG(0/0/0:11 11,35 - 0023/00):(vcnum:0) Output Release Complete msg, Call Initiated(N1) state 1d02h: SIG->CC: Svc Event Release Completed, State Dead 1d02h:ATMSIG(0/0/0:11 11,35 - 0023/00): (vcnum:0) Call Initiated(N1) -> DeadWorkaround: Upgrade the Catalyst 8500 switches to Cisco IOS Release 12.1(7a)EY.
•
Symptom: A crash occurs while configuring Bridge Group Virtual Interface (BVI)/Enhanced Interior Gateway Routing Protocol (EIGRP), or while powering off the redundant power supply.
Workaround: None.
•
Symptom: When a CES circuit carrying traffic is removed, there is no warning message shown.
Workaround: None.
•
Symptom: When running Cisco IOS Release 12.0(18)W5(22) on a Catalyst 8540 MSR, or on a LightStream 1010, interoperability problems occur when peers run an older IOS version, and tunnels and SVC/Soft VCs are used.
Workaround: Upgrade all switches to the most current IOS release.
•
Symptom: When using snmpwalk and the getbulk operation on the MIB tree, a memory leak occurs.
Workaround: None.
•
Symptom: When a Catalyst 8540 MSR system has a large number of inverse multiplexing over ATM (IMA) port adapter modules, a message similar to the following is generated:
-Process= "IMAPAM Onesec", ipl= 6, pid= 70-Traceback= 600D8280 600D8644 6049F928 600C03CC 600C03B8%SCHED-3-THRASHING: Process thrashing on watched message event.Workaround: None.
•
Symptom: On the CES module interface, the status reads UP/UP and the status of PVC to that interface is UP in even though there is no physical connection at that port.
Workaround: Perform shutdown and no shutdown on the interface to clear the erroneous status.
•
Symptom: A forced crash occurs.
Workaround: None.
•
Symptom: PNNI goes to "down" state on all interfaces and all adjacencies are lost.
Workaround: None.
•
Symptom: A Catalyst 8540 MSR and Catalyst 8510 MSR connected via 8-port inverse multiplexing over ATM (IMA) port adapter modules change clocking configuration after the T1 interfaces bounce, resulting in a loss of synchronous clocking over the T1 IMA links. If synchronous clocking is required for circuit emulation service (CES), the CES circuit might report overruns or underruns.
Workaround: The Catalyst 8540 MSR and Catalyst 8510 MSR can be reloaded to return the clocking configuration to the original values. The T1 interfaces can be removed from the IMA group, and then can be added back and bounced. The txtiming values under the show controllers will change back to 0x2 and synchronous clocking is restored.
Symptom: A Catalyst 8540 CSR logs the following messages:
%SK-4-WARNING: Slot10: Job ScxMan-pathTable-review ran 10992 (its runTimeMax was 8000)%SK-4-WARNING: Slot10: Job ScxMan-interruptHandler ran 24378 (its runTimeMax was 20000)%SK-4-WARNING: Slot10: Internal Warning: Dropped 22 high priority IPC packets%SK-4-WARNING: Slot10: Internal Warning: Dropped 22 high priority IPC packets%SK-4-WARNING: Slot10: Internal Warning: Dropped 22 high priority IPC packets%SK-4-WARNING: Slot10: Internal Warning: Dropped 22 high priority IPC packets%SK-4-WARNING: Slot10: Internal Warning: Dropped 22 high priority IPC packets%SK-3-ERROR: Slot10: Have run out of vbufs (internal buffers)-Process= "SK-IPC Input", ipl= 0, pid= 119-Traceback= 603E1260 603E1950 603E2258 603E20B8 603F75DC 60097734 60097720%SK-4-WARNING: Slot10: Internal Warning: Dropped 32 high priority IPC packets%SK-3-ERROR: Slot10: Have run out of vbufs (internal buffers)-Process= "SK-IPC Input", ipl= 0, pid= 119-Traceback= 603E1260 603E1950 603E2258 603E20B8 603F75DC 60097734 60097720%SK-4-WARNING: Slot10: Internal Warning: Dropped 18 high priority IPC packetsHowever, no connectivity problem is reported.
Workaround: None.
•
Symptom: The following error message does not specify which CAM/port adapter needs to be removed or reseated.
%OIR-3-LONGSTALL: Long bus stall (20000 s), the new PAM may not seated properly, Please remove it and try againWorkaround: None.
•
Symptom: On Frame Relay to ATM Soft PVC connections the Frame Relay UNI interface status is incorrect. The soft-VC PVC status is marked Active only when the soft-VC is established and its connection state is UP. If the soft VC is not connected, the source end of the soft-VC indicates the PVC status as INACTIVE instead of ACTIVE, while the destination end of the soft-VC does not exist and hence indicates the PVC status is DELETED.
Workaround: None.
•
Symptom: The Management Information Base (MIB) object "ifAdminStatus" shows "UP" for an ADMIN DOWN E1 Controller after a reload or a route processor switchover.
Workaround: Enter the no shutdown/shutdown command sequence on the controller.
•
Symptom: SK Kernel on the 8-port Gigabit Ethernet module occasionally crashes.
Workaround: Run any IOS Release prior to Release 12.1(5)EY.
•
Symptom: On the Frame Relay interface module, if any DROPS occur, the INPUT/OUTPUT ERROR counter is incremented instead of INPUT/OUTPUT DROPS counter.
Workaround: None.
•
Symptom: When Frame Relay ATM soft-VC is set up in Frame Relay/ATM Network Interworking (FRF.5), the usage parameter control (UPC) on the passive side always sets to PASS, irrespective of the setting on the serial interface that is set by entering the frame-relay upc-intent tag-drop command. The default is PASS; when this is changed to tag-drop, the configuration does not reflect the change, and entering the show vc int serial command always shows the UPC intent as PASS.
Workaround: None.
•
Symptom: You might need to specify a minimum VPI on Catalyst 8500 switches when it is communicating with a Cisco Broadband Switch Module (BXM) Series switch. If you do not, a Soft PVC might not be torn down because the Virtual Switch Interface (VSI) on the BXM interface uses VPI 0.
Workaround: None.
•
Symptom: When the shutdown/no shutdown command sequence is entered for a port in a CES card, a burst of bit errors can be observed on the circuit on some other port of the same port adapter.
Workaround: None.
•
Symptom: On the Catalyst 8540 MSR and LightStream 1010 platforms, the option to set loop timing on OC-12 ports is not available.
Workaround: None.
•
Symptom: Not all of the contents of the atmVcCrossConnectTable can be seen after the removal and re-insertion of a module. The message:
%ATMCORE-3-INTERNAL_ERROR: ATOM ERROR: ifCB_p=NULL for lowIfis seen on the console during some SNMP get operations.
Workaround: None.
•
Symptom: When an E1 IMA (inverse multiplexing over ATM) adapter is inserted into a chassis in which several other IMA adapters have already been added, the clock cannot be derived from the network.
Workaround: None.
•
Symptom: Some point-to-multipoint crossconnnect entries are missing from the atmVcCrossConnectTable when the point-to-multipoint root if-index is higher than the if-index of the leaves.
Workaround: None.
•
Symptom: Interfaces with Tag enabled get stuck in the TDP not ready state.
Workaround: None. The only way to bring up the Tag on such interfaces is via system reload.
•
Symptom: During TagVC installation, if the switch driver returns an error, the Connection Manager leaves the TagVC in the wrong FSM state. This can lead to TVCs existing on an interface when there are no tag bindings.
Workaround: None; reload the switch to clear such unused TVCs.
•
Symptom: When running Cisco IOS Release 12.0(13)W05(19), a bus error causes the system to restart. This occurs when an 8-port Gigabit Ethernet card with control traffic is at or near its traffic capacity.
Workaround: None.
•
Symptom: The SNMP TRAP object ccrCpuStatusChange returns an invalid value.
Workaround: None.
•
Symptom: A Catalyst 8510 reloads by bus error.
Workaround: None.
•
Symptom: When a Catalyst 8540 with a network clock module is connected to an external clock supply, changing the clock supply from BITS 0 to system causes the system to crash.
Workaround: None.
•
Symptom: After reloading core switches, all neighboring switches running 12.0(16)W6(21) and 12.0(16)W6(21a) crash and a message similar to the following is generated:
Jul 14 02:48:23: %ATMSIG-3-FAILXCONN: Xconnect failed, xconn fail -Traceback= 6054A204 6054C0A0 60556188 60545538 6054561C 6009930C 600992F8 Jul 14 02:48:23: ATMSIG(9/1/0:0 0,78 - 0209/62): (vcnum:0) XConnected failed To Jul 14 02:48:23: ATMSIG(ATM13/0/0 0,64 - 0018/62): (vcnum:64) Jul 14 02:48:23: ATMSIG: CONNECTION MANAGER/CAC Xconn install request Port A - (9/1/0) : 0 vpi = 0; vci = 78 Port B - (13/0/0) : 0 vpi = 0; vci = 64; new vpi = 0; new vci = 64 existing vpi/vci for leg B Jul 14 02:48:23: ATMSIG: CONNECTION MANAGER/CAC Xconn install result CONN_INSTALL_RESULT_HW_FAILWorkaround: None.
•
Symptom: A port of a 4-port DS3 port adaptor for LS1010s and 8540s is in a yellow or red alarm state, and stops sending DS3 framing for a brief time when the alarm is cleared from the interface and the interface transitions to an up/up state. The loss of frame (LOF) can be seen when the Acterna tool TBERD is connected to the TX port of the DS3 port.
Workaround: None.
•
Symptom: When using Cisco IOS Release 12.0(16)W5.21, a system crash with a bus error at imapam_mmcport_init occurs after the creation of the 131st interface.
Workaround: Remove any unused modules from the chassis so that additional virtual interfaces can be created.
•
Symptom: 4-path load balancing is missing for Ethernet processor interfaces.
Workaround: None.
•
Symptom: On a Catalyst 8540 MSR, use of the OIR online diagnostic disables the E1 interface after reloading.
Workaround: None.
•
Symptom: After an online insertion and removal (OIR) of a carrier module in the 8540 MSR, the input/output packet counters for the corresponding interfaces show incorrect values.
Workaround: Do not perform OIRs, or clear the counters on that interface.
•
Symptom: The command line interface (CLI) no negotiation auto command is not preserved in the running configuration after an OIR (or "hot swap") of an 8-port Gigabit Ethernet card.
Workaround: Configure the CLI no negotiation auto command again.
•
Symptom: The spanning tree protocol of a bridge-group cannot be changed.
Workaround: Deconfigure the bridge-group and then reconfigure it with a different spanning tree protocol.
•
Symptom: When a user specifies a Soft PVP Configured as VBR-NRT Service category in the ingress port, the service category at the egress interface of that switch is seen as UBR rather that VBR_NRT.
Workaround: None.
•
Symptom: After a switch processor or route processor switch over, incorrect values appear in the show interface atm display counters for the OC-3 interface module.
Workaround: Reload the switch.
•
Symptom: A Catalyst 85xx running Cisco IOS Release 12.0(13)W5(19c) experiences high multiservice route processor utilization when Internetwork Packet Exchange (IPX) networks are added to Bridge Group Virtual Interface (BVI) interfaces; as more IPX networks are added, multiservice route processor utilization increases.
Workaround: If configuring bridging over ATM router module subinterfaces, configure a map-list for the bridged virtual circuit, using the keyword "bridge".
For example:
interface ATM3/0/0.50 multipointno ip directed-broadcastmap-group b50atm pvc 2 50 pd on interface ATM0/0/0 1 50bridge-group 50map-list b50bridge atm-vc 50 broadcast•
Symptom: FR-PVCs configurations might fail after a route processor switchover.
Workaround: Reload the switch router.
•
Symptom: On ATM switches, the loopback IP address is not exchanged during ILMI negotiation with the neighboring switches. Consequently, the output of the show atm ilmi-status command indicates 0.0.0.0 as the peer IP address, even though a loopback address is configured.
Workaround: Configure the IP address on an Ethernet interface.
•
Symptom: A Catalyst 8540 CSR with an 8-port Gigabit Ethernet module forwards duplicate broadcasts when bridging is configured on a trunk.
Workaround: None.
•
Symptom: One side of a circuit emulation service (CES) E1 port of a the switch connection remains consistently in the YELLOW alarm or ALARM INTEGRATION state.
Workaround: None.
•
Symptom: When running cell-mode MPLS on a network of switch routers with redundant paths, conversion to MPLS after a routing change might take up to 4.5 minutes. OSPS converges normally.
Workaround: None.
•
Symptom: An ARM interface might not bridge between ATM and the native VLAN.
Workaround: Configure some other non-functional VLAN as native.
•
Symptom: On a Catalyst 8540 performing an ATM-Frame Relay internetworking function, the ATM-Frame Relay does not propagate when the Local Management Interface (LMI) indicates a permanent virtual connection (PVC) as inactive.
Workaround: None.
•
Symptom: The no ip route-cache cef command might disappear from the running configuration of the BVI interface after reloading the switch router.
Workaround: None.
•
Symptom: The entry for atmSoftPVccRetryThreshold feature has an incorrect default value of 0, rather than the default value of 1 that is shown in the ATM Soft PVC Management Information Base (MIB). A value of zero indicates that an infinite number of call attempts are required to increment the atmSoftPvcCallFailures object and thus disables alarms for the Soft PVCC.
Workaround: Set the atmSoftPVccRetryThreshold value to 1.
•
Symptom: There is a noise problem with the CES PAM hardware version one.
Workaround: None.
•
Symptom: When slot 0 is configured as the ARP client, the client might release the SVC within one minute of a ping.
Workaround: Use the subinterfaces of slot 0 as the ARP client instead.
•
Symptom: The Internetwork Packet Exchange (IPX) statistics sometimes fluctuate when no traffic is flowing through the interface. The only affected functionality is IPX statistics.
Workaround: None.
•
Symptom: When video traffic is switched through an 8-port Gigabit Ethernet module in a Catalyst 8540 router, a high amount of jitter is seen.
Workaround: None.
•
Symptom: Sending a crafted control NTP packet might cause a buffer overflow.
Workaround: Include the "ntp access-group serve-only" line in the configuration of the router.
•
Symptom: Under a heavy load the switch router might misorder cells going out OC12 port adapter modules.
Workaround: Use the four-port OC12 modules designed for the Catalyst 8540.
•
Symptom: When the routing table exceeds 50,000 entries and one or more eight-port Gigabit Ethernet interface modules are installed in the switch router, the CAM full condition might be seen. This condition will cause ports to stick.
Workaround: Perform an OIR of the module. The eight-port Gigabit Ethernet interface module is not designed to handle more than 50,000 entries.
•
Symptom: The SNMP polling of the MIB object atmVplOperstatus (in Virtual Path MIB) for VP tunnels shows that the VPL is DOWN, even when the tunnel is UP (as shown by the CLI).
Workaround: None.
•
Symptom: In bridging, the aging time of Ethernet process interfaces is always set to 300 seconds, despite what it is configured for.
Workaround: None.
•
Symptom: Even after enabling SNMP, the switch router might not be able to perform SNMP walk.
Workaround: None.
•
Symptom: The one-Port OC12 port adapter module might cause cell corruption. This will inevitably lead to packet corruption wherever segmentation and reassembly is performed to put the cells back into frames.
Workaround: None.
•
Symptom: When a static route is added to and deleted from an interface that already has a static route connected to it, the packets are process-switched.
Workaround: Enter the clear ip route command.
•
Symptom: On PVCs on a VP tunnel, attempts to configure usage parameter control (UPC) values other than "pass" might not succeed.
Workaround: Do not define the VP tunnel, just configure PVCs on the VPI.
•
Symptom: Online Diagnostic Snake tests might send ILMI traps when an interface becomes active. This can cause clients on other inter-faces to reset ILMI.
Workaround: Disable the snake test by entering the no diagnostics online snake command in global configuration mode.
•
Symptom: Cell memory might get stuck when ABR, IMA, and hierarchical VPs are combined.
Workaround: Enter the shutdown command on the IMA interface. Take the first link on the IMA interface out of IMA group. Enter the no shutdown command followed by the shutdown command on the interface. Enter the no shutdown command on the IMA interface.
•
Symptom: The ifTable Indexes might not match MIB-II table indexes.
Workaround: None.
•
Symptom: If a switch processor switch over occurs, the IMA interface will remain in a waiting state. After this, entering the shutdown command and then the no shutdown command on the IMA interface will bring it to the "going down" state.
Workaround: To avoid this issue, disable online diagnostics before a switch processor switch over.
•
Symptom: If a route processor switch over is done continuously more than two times by entering the redundancy force-failover main-cpu command or once entering the EHSA null_ptr command, the new primary route processor will issue the following error message continuously:
%FRPAM(pciread):returned error 0x2000000!%FRPAM(pciread): pci addr 0x02080208! read failed!!%FRPAM(pciread): time taken to read 0x02080208! is 8loop_count 1
Workaround: An online insertion and removal of the FR port adapter will stop this error message.
•
Symptom: The switch router might crash when being polled by SNMP.
Workaround: None.
•
Symptom: The SNMP ccrCpuStatusChange traps are sent regularly with a ccrCpuStatus of ok(2) even though there is no change in the status of the CPU. This happens only when commands such as show running-config or write memory are entered.
Workaround: Disable the traps.
•
Symptom: When using PNNI, another vendor's equipment might send an invalid PTSE update. If the switch router receives one of these invalid updates, the PNNI neighborship might not re-establish.
Workaround: None.
•
Symptom: After resetting an E1 device connected to the CES port there might not be connectivity about Layer one.
Workaround: Enter the shutdown command followed by the no shutdown command on the CBR interface.
•
Symptom: Two adjacent ATM devices had problems with ILMI negotiation. The result of the ILMI negotiation is VPI/VCI range failure.
Workaround: None.
•
Symptom: An ARM port configured for transparent bridging and in blocking state might forward certain frames.
Workaround: Depending on the topology, the work-around might be to ensure that a non-ARM port is in blocking state. Where this is not feasible, you need to physically shutdown the ARM port that is in the blocking state.
•
Symptom: A switch router might show additional atm interfaces than the number of interfaces present in the chassis. This does not affect functionality.
Workaround: None.
•
Symptom: SVC signalling across a VP tunnel might not work after a reload.
Workaround: None.
•
Symptom: On the OC-3c port adapter module, ILMI might remain in the "waitdevtype" state after a redundancy fail over.
Workaround: If the problem is seen on port 1-3, bring up port 0. If the problem is seen on port 5-7, bring up port 4. If the problem is seen on port 9-11, bring up port 8. If the problem is seen on port 14-15, bring up port 12. The port can be brought up by connecting a loopback cable, or just by using that port.
•
Symptom: A switch router with OC3 port adapters and five Fast Ethernet interface modules might boot up with the following error message:
epif_aal5_fastsend: bad vcinfo This message may appear 100sof times and slow down the boot process. Normal operation does not seem affectedonce the 8500 has finished booting.Workaround: None.
•
Symptom: When a switch router sends a tag distribution protocol (TDP) bind request and does not receive an answer, the TVC remains unconnected. This might cause scalability problems in large networks because over time these TVCs might use up a large number of resources.
Workaround: Add a timer to clean up the VCs.
•
Symptom: Switch routers running Cisco IOS Release 12.0(13)W5(19) or earlier might experience a memory leak when used with an NMS (Network Management System) running SNMP whenever it accesses PNNI tables.
Workaround: Turn off NMS polling of PNNI tables and instead use the CLI or determining any PNNI information.
•
Symptom: Online Diagnostic might run in the background and then stop suddenly with the following error message:
1d23h: %SCHED-2-EDISMSCRIT: Critical/high priority process Online Diagnostics may not dismiss. -Process= "Online Diags", ipl= 0, pid= 62Workaround: Enter the diagnostics online snake command in global configuration mode to restart the online diagnostics.
•
Symptom: ILMI might not properly learn the ip addresses of peer switches. After entering the show atm ilmi-status command, the interface of the peer switch is learned but its ip address is not.
Workaround: None.
•
Symptom: The ARM might set the CLP of all cells to one when bridging is configured over a PVC. This happens for cells being transmitted over the 1483 PVC only.
Workaround: None.
•
Symptom: The port stuck message might log to the system log.
Workaround: None.
•
Symptom: The ATM uplink module might not support map list entries for its own IP address.
Workaround: None.
•
Symptom: The telnet response over an ISL trunk might be very slow. This is because small ISL frames (under 94 bytes) are not padded, and some devices drop ISL frames that are smaller than 94 bytes.
Workaround: None.
•
Symptom: The switch router might stop switching some VCs and log error messages like the following:
12:37:34.793: ATMSIG(12/1/0:0 0,37 - 274610/00): (vcnum:0) XConnected failed To Jan 9 12:37:34.793: ATMSIG(12/0/1:0 0,268 - 398903/00): (vcnum:0) Jan 9 12:37:34.793: ATMSIG: CONNECTION MANAGER/CAC Xconn install request Port A - (12/1/0) : 0 vpi = 0; vci = 37 Port B - (12/0/1) : 0 vpi = 0; vci = 268; new vpi = 0; new vci = 268 existing vpi/vci for leg B Jan 9 12:37:34.793: ATMSIG: CONNECTION MANAGER/CAC Xconn install result CONN_INSTALL_RESULT_HW_FAILWorkaround: Reload the switch router.
•
Symptom: An ATM router module interface indicates outgoing packets when that interface is administratively down.
Workaround: None. This does not impact functionality.
•
Symptom: When there is a lot of signaling svc setup and teardown on an NNI tunnel, interface calls might fail with a vpi/vci collision.
Workaround: Use a regular interface (no tunnels).
•
Symptom: The switch router might lose traffic on its LANE/1483/1577 interfaces on an ARM. Frame interfaces (like Fast Ethernet) or non-lane interfaces on ARM (with configured PVCs) pass traffic without any problems.
Workaround: Perform an OIR on the ARM or reload the switch router.
•
Symptom: IP and IPX routing over BVI on an 8-port Gigabit Ethernet port or a port channel might fail when the 8-port Gigabit Ethernet interface is removed from the bridge group.
Workaround: None.
•
Symptom: Cell loss on PVC connections occurs when removing the active route processor.
Workaround: Entering the redundancy prepare-for-cpu-removal command might prevent any cell loss outage from affecting established PVCs.
•
Symptom: When using a 155-Mbps port adapter module, the show controller command output will list all port mediums as SM_IR_+.
Workaround: None.
•
Symptom: On a switch router performing the Frame Relay/ATM Network Internetworking function, when the Local Management Interface (LMI) indicates a PVC is inactive on an NNI interface, this information is not propagated by the Frame Relay/ATM software.
Workaround: None.
•
Symptom: A system running PNNI with Cisco IOS release 12.0(7)W5(15c) will reject an ATM call SETUP if the setup includes the 5a information element coded with associated signaling, explicitly the VPCI and any VCI.
If another ATM switch sends a setup that includes the 5a information element coded with the associated signalling, explicit VPCI and any VCI, the system will release the call with cause code 35: requested VPCI/VCI not available.
Call setups that include the 5a information element coded with the associated signalling, explicit VPCI, explicit VCI signalling, including those made by Cisco ATM switches are not affected by this problem.
This interoperability issue exists between Cisco ATM switches and other vendor's switches that do not explicitly request the VCI value in the call SETUP.
Workaround: None.
•
Symptom: The port stuck detection and recovery mechanism might not work if one of the channels of the ARM port gets stuck.
Workaround: None.
•
Symptom: Power-on diagnostics hang, and the IOS is unable to boot, when ARM, Fast Ethernet, and OC-12 modules are installed in the same chassis.
Workaround: None
•
Symptom: IPX traceroute might skip the middle hop when the middle router is the Catalyst 8540 switch router.
Workaround: None.
•
Symptom: The RMON for the 8-port Gigabit Ethernet interface module might not work.
Workaround: None.
•
Symptom: When an OIR is performed on an ARM module, the HSRP configuration might get lost.
Workaround: None.
•
Symptom: The ATM User-Network Interface (UNI) does not include a cumulative round-trip time parameter in the ABR call setup. This situation might cause interoperability issues with different vendor products.
Workaround: None.
•
Symptom: The circuit emulation service (CES) address does not change when the switch router address is changed. When the global switch ATM address prefixes are added or deleted (via the atm address command), addresses registered for existing CES circuits are not changed.
Workaround: None.
•
Symptom: The show hardware detail command does not show the actual version of the FPGA for any of the daughter cards. This shows the version of the FPGA motherboard which is misleading.
Workaround: None.
•
Symptom: The atm arp-server nsap command is removed from the running configuration upon reloading the switch.
The copy startup-config running-config command will restore the original configuration.
Workaround: None.
•
Symptom: If you save the running configuration, you may see the following error:
ROUTER# copy run startDestination filename [startup-config]?startup-config file open failed (File table overflow)This happens when you issue a write mem command or a copy running-config startup-config command. Issue a show file command to show the 127 entries of private configuration.
Workaround: Save the running configuration in a file, reload the router, and then issue a write mem command or copy running-config startup-config command.
•
Symptom: Although packets are being sent out from an ATM OC-12 interface module, the 5-minute output rate shown using the sh int atm command indicates 0 bits/sec output. This is not consistent with the output rate shown under the sh atm traffic command.
Workaround: None.
•
Symptom: A simultaneous encapsulation change on both sides of a link when the force-link up mode is used presents a 50 percent chance of bringing the line-protocol down. This problem does not happen when encapsulation change is done one side at a time. Problem is usually not seen when auto-negotiation is enabled.
Workaround: Issue a shutdown and no shutdown to bring the line protocol up.
•
Symptom: When the show atm interface traffic command is entered on a subinterface, the total number of cells that has passed might show incorrectly as zero.
Workaround: None.
•
Symptom: The Xconnect setup fails for unidirectional TVC if there is another one with different direction and same vpi/vci on particular interface of the Catalyst 8540 MSR. This can be seen only if VC merge is disabled.
Workaround: None.
•
Symptom: When the primary clock source is in the "unlockable" state, and the clock fails over to the secondary clock, the router never reverts to the primary clock source, even when the connection is clean and the clock source is present.
Workaround: None.
•
Symptom: The output of the command show epc if-entry is limited to 20 characters. This limits the command from showing specific port information when the module or slot combination causes the output to go beyond 20 characters. For example, when Gigabit Ethernet interfaces are installed in slot 10 or greater, the output is truncated.
Workaround: None.
•
Symptom: The present configuration does not work properly for frame reject (FRMR) and acknowledgement timeout messages. Occasionally a file transfer works normally, but most of the time it does not.
Workaround: None.
•
Symptom: Traffic pointing to an unknown route goes to the route processor even with ip unreachable disabled on the Gigabit interface input port. The traffic is dropped if the input port is an Ethernet interface port and ip unreachable is disabled.
Workaround: None.
•
Symptom: Ports get stuck on a Gigabit interface when booting with 12.1(1.6)W6(25) image. The same cards boot up fine with 12.1(1.6)W6(24).
Workaround: None.
•
Symptom: Crash after issuing a clear counters command in get_pif_no function.
Workaround: None.
•
Symptom: When the reset button is pushed, the switch router might not boot the main-image, and eventually goes into ROMMON.
Workaround: None.
•
Symptom: When HSRP is configured on the eight-port Gigabit Ethernet interface module, HSRP connectivity might be disrupted after a remote link failure is followed by a link restoration.
Workaround: Configure another HSRP group with a higher number and move the standby configuration to that group.
•
Symptom: The output errors counter is incorrect on Gigabit Ethernet show interface command. They have a high value 4xxxxxxxxx and a clear counter command does not change it back to 0. This value can increase or decrease over time.
Workaround: None.
•
Symptom: IP traffic is not sent over PVC if AAL5 MUX encapsulation is used on a point-to-point subinterface on the Catalyst 8540 MSR. If the deb atm errors command is enabled, the following error messages will appear:
point-to-point interface does not have a VCDWorkaround: None.
•
Symptom: The route processor redundancy may fail if you have both PVC and bridging configured on the ARM sub-interface.
Workaround: None.
•
Symptom: The system is not completing a route processor failover. The secondary route processor (redundant), as it assumes function from a failover will display the following error message:
%Secondary CPU Detectedremove_conn_from_fabric: Error close party failed for . . .This does not affect operation of the system but will prevent the secondary route processor from booting successfully if the primary crashes.
Workaround: None.
•
Symptom: On an MSR switch router with enhanced Gigabit interface cards, the switch router crashes when loading a CSR image because of the CES card in the switch router.
Workaround: None.
•
Symptom: IPX load-balancing on IPX packets sourced from enhanced Gigabit Ethernet ports or sent out of ATM uplink ports will work only if IPX max-paths are set to 1 or an even value (i.e. 2, 4 or 6). An odd value of 3 or 5 can cause some of the IPX packets to not go out of the ATM uplink ports. This problem is seen only with SVCs over 1483 not PVCs with 1483.
Workaround: When IPX packets are sourced from enhanced Gigabit Ethernet ports, set the IPX maximum paths to 1, 2, 4 or 6. If there are an odd number of paths, change the administrative weight of one path so that there are always an even number of equal cost paths.
•
Symptom: The ATM router module (ARM) does not strip the Ethernet pad when switching data from Ethernet to ATM. This may occasionally lead to connectivity issues since some end-systems do not expect to see the pad.
Workaround: None.
•
Symptom: When an enhanced Gigabit Ethernet interface module sends out ISL packets with packet sizes 1531 to 1548, the output error counter on the egress port increases.
Workaround: None.
•
Symptom: The hierarchical VP tunnel configuration fails on a WAI-OC3-1S3M mixed mode port adapter module when it is in slot 0 subslot 1 of the C85MS-SCAM-2P carrier module. Slot 0 subslot 0 of the carrier module can either be empty or have another card in it, and hierarchical VP tunnel configuration will still fail. However, if the mixed mode pam is inserted in slot 0 subslot 0 of the carrier module, then the hierarchical VP tunnel can be configured.
Workaround: None.
•
Symptom: The switch router might be vulnerable to the successful prediction of TCP Initial Sequence Numbers. This vulnerability only applies to the security of TCP connections that originate or terminate on the affected Cisco device itself; it does not apply to TCP traffic forwarded through the affected device, in transit between two other hosts.
Workaround: Update to Cisco IOS Release 12.0(13)W5(19c).
•
Symptom: When IPX packets are sourced from fast Ethernet interface based ports and sent out of ATM uplink ports, IPX load balancing will work only if the IPX max-path is set to 2. A value greater than 2 can cause some of the IPX packets to not go out of ATM uplink ports. This problem is seen only with SVCs over 1483 not with PVCs over 1483. However, if all IPX traffic is sourced only from enhanced Gigabit interface ports then this problem is not seen. Six-path load balancing will work correctly.
Workaround: When IPX packets are sourced from fast Ethernet interface based ports, set IPX max-paths to less than or equal to 2.
•
Symptom: A bus error that occurs at PC 0x6014A9E0 causes the Catalyst 8540 MSR to crash. This occurs when the router is polled for ATM data via SNMP.
Workaround: None.
•
Symptom: When serial interfaces on a Frame Relay/ATM internetworking port adapter are oversubscribed, and significant data bursts occur simultaneously on multiple VCs on multiple serial interfaces, one serial interface might get stuck.
Workaround: Enter the hw-module slot/subslot command.
•
Symptom: The ifSpeed is reported as 100MB even when the auto-negotiation results in 10MBit.
Workaround: None.
•
Symptom: When the switch processor LED is red, cell loss occurs on insertion of standby switch processor.
Workaround: None.
•
Symptom: No SNMP trap exists corresponding to the following syslog message:
%ATM-4-ILMIKEEPALIVEFAIL.Workaround: Enable syslog traps on switch to capture these failures
•
Symptom: After replacing an ATM 155-Mbps multimode port adapter with an ATM 155-Mbps single-mode port adapter, the SNMP agent might not correctly refresh the AtmIftable: it still returns the old ciscoAtmIfPortType information for the new module. Stopping SNMP and then restarting the SNMP agent does not correctly refresh the table.
Workaround: Reload the switch router.
•
Symptom: The Gigabit Ethernet port on the eight-port Gigabit Ethernet interface module comes up as unshutdown after an OIR.
Workaround: None.
•
•
Workaround: Configure a port-stuck reload.
•
Symptom: The output rate displayed in the show interfaces command on the POS interface can be artificially high at times.
Workaround: Issue the clear counters command or the shutdown and no shutdown commands.
•
Symptom: The default network over a POS link might not work when the outgoing interface is specified instead of the next hop interface.
Workaround: Specify the next hop interface.
•
Symptom: When a Catalyst 5500 connected to a Catalyst 8540 CSR is powered down, the BVI interface does not receive EIGRP and OSPF multicast hello packets.
Workaround: None.
•
Symptom: The system crashes when more than 80 VCs are configured on an ATM uplink port and the port is added to a bridge group. Avoid this configuration.
Workaround: None.
•
Symptom: The release message uses the wrong cause and diag information.
Workaround: None.
•
Symptom: clear atm vc option specifies VCDs from 1 to 4095 only. Therefore, any SVC with a VCD greater than 4095 cannot be cleared using this command.
Workaround: None.
•
Symptom: Enhanced Gigabit Ethernet ports learn MAC addresses of all zeros for packets with source MAC addresses with all zeros. This does not cause any problems.
Workaround: None.
•
Symptom: If you have more than 900 VCs on any interface or subinterface on the Gigabit Ethernet port with ATM uplink interface modules and you perform an online insertion and removal (OIR), a BROUTE VC release/setup failure will be indicated.
Workaround: None.
•
Symptom: The routing flag is not set and remains off after unconfiguring the bridge group on the system. This is only on ATM uplink ports.
Workaround: Issue the shutdown and no shutdown commands.
•
Symptom: When the network clock module quality is not accurate the NCDP will automatically disable. It is normal behavior of ncdp.
You can check the ncdp status with the following:
switch# show ncdp port atm2/0/0port data --(35)-----ATM2/0/0--------------port_id : 35state : disabled^^^^^^^^Workaround: None.
•
Symptom: When the ingress is a fast Ethernet interface, and the egress is an ATM uplink interface and is one of several parallel paths to a destination IPX network, shutting down this interface will cause the packets sent to this destination to use the first of the remaining parallel paths.
Workaround: The correct path will be chosen after issuing the clear ipx route* command.
•
Symptom: If HSRP over BVI is configured and a standby MAC address is explicitly configured on the BVI, this MAC address will not be reflected in the patricia table of the interface.
Workaround: None. The recommended option is to not use a standby MAC address and let the system choose the address.
•
Symptom: The two-port Gigabit Ethernet is part of a port channel, which has HSRP configured on it. Even after the two-port Gigabit Ethernet is removed from the port channel, the HSRP MAC address is retained.
Workaround: Issue the shutdown and no shutdown commands, add an IP address, or add the MAC address to a bridge group to delete the entry.
•
Symptom: A Catalyst 8540 with an ARM module, might take a software forced crash when attempting to establish EIGRP adjacencies.
Workaround: None.
•
Symptom: The ATM router module microcode for RFC1483 did not have the ability to understand CLNS topology updates forcing the card to drop packets. This also effected the IS-IS routing updates.
Workaround: Upgrade to the Cisco IOS release 12.0(11)W5(19).
•
Symptom: There is no support for SONET MIB objects in ATM uplink module.
Workaround: None.
•
Symptom: After issuing the shutdown and no shutdown commands on an interface that is part of a bridge group, sometimes the BCAST VC becomes zero.
Workaround: Issue the shutdown and no shutdown commands or remove the interface from the bridge group and add it back to restore the BCAST VC.
•
Symptom: Subinterfaces with the same VLAN color cannot be present in different bridge groups. This check is done when a bridge group configuration is being created or removed, not when the encapsulation is being changed.
Workaround: None.
•
Symptom: The router reloads when handling internetworking packet exchange (IPX) access-logging-messages. This situation may still occur if access-logging is not enabled.
You may exceed the 200 IPX network limit when the hardware is activated after being removed. When the hardware is reactivated, the interfaces that were not counted while the hardware was removed cause the limit to exceed.
Workaround: None.
•
00:02:08: %SYS-2-GETBUF: Bad getbuffer, bytes= -2008487331 Process= "Init", ipl= 0, pid= 2 -Traceback= 6006D014 6016239C 60335DE4 60335FB8 60336110 60336350 60029724 60099364 60099350Symptom: The message above might appear during bootup. The system recovers from this.
Workaround: None.
•
Symptom: The Gigabit Ethernet interface is part of a port channel; one of the port channel subinterfaces is a member of the bridge group. The BVI MAC address is retained on the interface even after it is removed from the bridge group.
Workaround: Issue the no mac-address command under the interface.
•
Symptom: The IP adjacencies are not being cleared from the Gigabit Ethernet card quickly enough.
Workaround: Upgrade to the Cisco IOS release 12.0(10)W5(18c) software or later.
•
Symptom: Option access-list under the show controllers command returns nothing when the interface is configured for bridge address access-list. Option mac under the show controllers command for the enhanced Gigabit interface port returns nothing when it finds a match in the Layer 2 database.
Workaround: None.
•
Symptom: MAC addresses are missing in the two-port Gigabit Ethernet port part of the bridge group when many MAC addresses are learned over the POS link and the POS link goes down.
Workaround: None.
•
Symptom: When auto negotiation is disabled on an enhanced two-port Gigabit Ethernet port, it is up even if the GBIC is not present.
Workaround: None.
•
Symptom: The CSR image recognizes the ATM router module and downloads the ATM router module micro-Code.
Workaround: None.
•
Symptom: The following message may appear when an incorrect signaling packet is transmitted by the peer device:
SYS-2-BADSHARE: Bad refcount in datagram_doneThis may lead to memory corruption.
Workaround: None.
•
Symptom: Cannot create soft VC with 95% of PVP
The calculations for determining the limits of PCR and SCR that can be used for a VBR-NRT VC traversing through a VP tunnel using the CAC algorithm at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/wa5/12_0/3a_11//atm_tech/rm.htm#xtocid2419
This holds true for PVCs but not soft VCs.
Workaround: None.
•
00:04:37: %ALIGN-3-CORRECT: Alignment correction made at 0x60674830 reading 0x62017DB300:04:37: %ALIGN-3-TRACE: -Traceback= 60674830 60674A90 600993A4 60099390 00000000 00000000 00000000 00000000Symptom: The alignment correction might occur with the clear bridge or show bridge commands with the ATM uplink. The system recovers from the alignment correction.
Workaround: None.
•
Symptom: If the peer device has a non-HP Gigabit interface converter (GBIC) and is not seated properly, the "Optical Detect" LED will be OFF on this device.
Workaround: Enter the shutdown and no shutdown commands or reseat the GBICs after a power cycle.
•
Symptom: The static bridge command might disappear from the running configuration.
Workaround: None.
•
Symptom: When the module is removed from the switch, the interfaces continue to show as inserted and also the IDB's are not deleted. The problem occurs with different kinds of modules in different slots.
This was noticed when a module is inserted into a slot and another is removed almost immediately. This is not seen when a good amount of time is given between the act of insertion and removal of the modules.
To prevent this, before inserting a new module into the switch, wait 2 minutes after OIR.
Workaround: None.
•
Symptom: The ATM router module cannot remove interfaces bvi8 thru bvi11 and cannot unconfigure bridge groups 8 thru 11. This problem occurs with a configuration of 20-30 bridge groups. Some bridge groups which had BVIs enabled could not be unconfigured with the command line interface (in this case it was bridge groups 8 thru 11). The command for removing a particular BVI is not recognized, and the bridge-group could not be deleted.
This does not affect any bridging or routing functionality on the device. It is a configuration issue only.
Workaround: None.
•
Symptom: The HSRP interface does not preempt after the shutdown and no shutdown commands are entered.
An HSRP interface configured for "preempt" might not become active after reset. No error message is given.
Workaround: Set higher priority for "preempt" interfaces as a second decision instance.
•
Symptom: PIM: Watchdog timeout in pim_mps_idle_vc().
Workaround: None.
•
Symptom: The output of the show interface ethernet command might display a `lost carrier' count that is the same as that for the collision counter on that Ethernet interface. This is a counter error only, and does not actually indicate a lost carrier.
Workaround: None.
•
Symptom: Appletalk fails when bridged between an 8-port gig and 2-port Gigabit Ethernet card on the Catalyst 8540 MSR.
Workaround: Upgrade to IOS release 12.0(4a)W5(11a) or later.
•
Symptom: When two Catalyst 8540 CSRs with two-port Gigabit Ethernet interface modules are connected back-to-back, packets are lost. On one side the counters might show input and output increasing, but the other side shows only output packets increasing. The Address Resolution Protocol (ARP) from the other side is lost, and the ability to ping the other side is lost.
Workaround: Reset the GBIC.
•
Symptom: On the ATM uplink any packet routed on a point-to-point interface will be routed by the route processor.
Workaround: Do not configure point-to-point subinterfaces on the ATM uplink.
•
%LSS-4-INTERNAL_WARNING: lss_record_ri_ingress: Illegal channel %dSymptom: The above message might appear when changing the trunk encapsulation type of a Gigabit EtherChannel (GEC) from ISL to 802.1q, when GEC is configured for novell-ether encapsulation and ports are receiving IPX wire speed traffic. No functionality problems are observed.
Workaround: None.
•
Symptom: Due to a hardware limitation, any packets larger than 6K could potentially cause a port stuck. After a port is stuck, the normal port stuck recovery mechanism applies.
Workaround: None.
•
Symptom: When reloading a new image into the enhanced two-port Gigabit Ethernet interface module the ATM uplink enhanced Gigabit interface appears to have been reset. The enhanced two-port Gigabit Ethernet interface module download shows no effect on the ATM uplink.
Workaround: None.
•
Symptom: If the weighted-fair queueing is configured on an ATM IMA interface of a Catalyst 8540 MSR, the system may go into an infinite loop generating traceback messages.
Workaround: Do not configure.
•
Symptom: Notifications sent or received are only visible if the debug ip bgp command is configured. This might limit the ability to diagnose problems.
Workaround: None.
•
Symptom: When running Border Gateway Protocol (BGP), the BGP peers of the receiving border router might detect a mismatch in the code, and issue a notification message to reset their session. This does not affect the receiving border router.
Workaround: None.
•
Symptom: When reprogramming the switch processor(s) the Catalyst 8540 CSR might crash. No connections should be installed after reprogramming until the system reboot is complete. However, some interface modules create connections before the system reboot is complete so only the interface modules are recognized in the system crash.
Workaround: None.
•
Symptom: There is no instance of ACL card in the MIB table.
Workaround: None.
•
Symptom: In a switch equipped with circuit emulation service cards, the shutdown of a CBR interface does not affect the device connected to it.
Workaround: None.
•
Symptom: IP PIM Sparse-Mode using multipoint signaling over ATM can fail when the PNNI path is switched to the redundant link.
Workaround: Upgrade to Cisco IOS release 12.0(10)W5(18c) or later.
•
Symptom: Cannot set ifAdminStatus object on CES interfaces. Attempts to set ifAdminStatus result in the following:
vvvError code set in packet - Bad variable value. Index: 1.^^^Workaround: None.
•
Symptom: When more than one loopback interface needs to be configured, the interfaces are assigned the incorrect number, so they are all created as Loopback0. The interfaces cannot be removed.
Workaround: None.
•
Symptom: Under heavy multicast traffic, cells might stick in the switch fabric. This happens when a race condition occurs in the switch processor and the output VC (OVC) is not present in the active list or idle list. In this situation, the OVC is never taken up for further scheduling, and all the cells in the VC are stuck.
Workaround: Enter the clear ip multicast-routing command or enter the shutdown/no shutdown commands to the root interface.
•
Symptom: With an encapsulation change on a two-port Gigabit Ethernet interface module, the interface no longer sends packets. It seems that it is receiving packets and sending packets to the route processor when necessary, but the packets are not sent.
Workaround: None.
•
Symptom: When the switch router is reloaded, you must enter the shutdown command followed by the no shutdown command on the CBR ports in order to activate the CBR ports.
Workaround: None.
•
Symptom: Routed traffic does not pass through a port on the 8-port Gigabit Ethernet card when the port is in blocking mode for bridged traffic.
Workaround: None.
•
Symptom: When two 8540 CSR switch routers are directly connected by a two-port Gigabit Ethernet interface module, a reset of one switch router does not cause the remote switch router's interfaces to go down too. The problem is caused by the reset switch router's interfaces not going down, so remote interfaces do not go down.
Workaround: Physically remove the cable from the ports or issue the shutdown command.
•
Symptom: When running the Cisco IOS release 12.0(7)W5(14.74) software on a switch, it is possible that the atmVcCrossConnectAdminStatus entries will disappear.
Workaround: None.
•
Symptom: When the Catalyst 8540 CSR has both Protocol Independent Multicast (PIM) joins and IGMP joins coming in, one of the interfaces in the outgoing interface list of the IOS multicast table might not forward traffic. This is caused by a disconnect in the sequence of events between IOS multicast code and the Catalyst 8540 CSR specific light stream inter process communication subsystem (LSS) multicast code.
Workaround: Enter the clear ip multicast-routing command and configure static multicast groups on the interfaces sending PIM joins.
•
Symptom: After a route processor switchover, the microcode for a Fast Ethernet (FE) interface module might not download successfully. This failure occurs infrequently but causes the interfaces on the failed FE interface module to be unusable.
Workaround: Remove and reinsert the affected FE interface module.
•
Symptom: In some instances, an ATM interface on a Catalyst 8540 MSR may get stuck in a going down state.
Workaround: None.
•
Symptom: After a switch processor switchover, the microcode for an 8-port Gigabit Ethernet (GE) interface module might not download successfully. You will see the following error message:
epif_port_write_mii: Timeout for response message GigabitEthernetThis failure occurs infrequently but causes the interfaces on the failed 8-port GE interface module to be unusable.
Workaround: Enter an skmgmt reset command. When this command is entered, you might see BROUTE-VC SETUP FAILURE messages. These messages are harmless and can be ignored.
•
Symptom: When issuing the shutdown/no shutdown command on an ATM interface with a large number of VCs, the route processor utilization stays high for a long period of time. For example, for an 8K VC, the route processor stays high for around 720 seconds and for 4K VCs, it is around 300 seconds.
Workaround: None.
•
Received malformed TLV.Symptom: Sometimes the above message is seen.
Workaround: None.
•
Symptom: On bootup, the following warning message may appear:
IPC-5-NULL:Recd. msg Dest PortIt has no affect on the switch.
Workaround: None.
•
Symptom: The switch router will crash and hang when the ip http server command is configured and a browser connects to http://<router-ip>/%%. This defect can be exploited to produce a denial of service (DoS) attack. This information has been announced on public Internet mailing lists which are widely read both by security professionals and by security "crackers," and should be considered public information.
Workaround: Disable the IP http server with the following command:
no ip http server
Alternatively, the administrator can block port 80 connections to the switch router via access lists or other firewall methods.
For further information, refer to the security advisory available at http://www.cisco.com/warp/public/707/advisory.html
•
Symptom: The values for ifInOctets wrap every 15 to 30 seconds on ATM interfaces with very little traffic. The wrapping occurs when the value is about 3,000,000 octets.
Workaround: None.
•
%LSS-7-INTERNAL_ASSERT: clear_conn_entry:: (swidb_p != NULL) Assertion Failure - File ../ls-switching/lss_pm_api.c Line 1479-Process= "LSS IPmcast Process", ipl= 0, pid= 99-Traceback= 60553374 607A925C 607A9078 6085AC84 6066DA10 6066F880 606738D4 60674084 60099224 60099210Symptom: The message above appears sometimes when an enhanced Gigabit Ethernet port is added or removed from a port channel (PO) with multicast enabled on the PO. This message is harmless and the system recovers from this.
Workaround: None.
•
Symptom: There may be spurious memory access in certain tag switching configuration. This does not affect any functionality.
Show alignment data for:
PNNI Software (cat8540m-WP-M), Version 12.0(9.5)W5(17.14) INTERIM TEST SOFTWARE Compiled Mon 24-Apr-00 01:51 byNo alignment data has been recorded.Total Spurious Accesses 590, Recorded 1Address Count Traceback10 590 0x60409014 0x604093D4 0x603FB810 0x603F63F40x603F6A40 0x60099224 0x60099210.Workaround: None.
•
Symptom: The prompt on the secondary route processor does not reflect the hostname of the switch router after a sync.
Workaround: None.
•
Symptom: The following CPU hog messages might occur after removing an IMA port adapter that has hundreds of SVCs and PVCs configured:
*Apr 21 10:36:40: %OIR-6-REMCARD: Card removed from slot 2, subcard 1, interfaces disabled*Apr 21 10:36:42: %SYS-3-CPUHOG: Task ran for 2096 msec (114/0), process = OIR Handler, PC = 600AA8D8.-Traceback= 600AA8E0 6035EB40 6035FC90 600988DC 600988C8*Apr 21 10:36:43: %LANE-5-UPDOWN: ATM9/0/0.5 elan elan_cgr05: LE Client changed state to down*Apr 21 10:36:43: %IMAPAM-6-LOG: pam 2/1 changed state to NO_HARDWAREWorkaround: None
•
Symptom: When configuring region sizes you are not considering the ACL region size when checking for the total size. Configuration allows regions sizes exceeding total Tcam size. No error message is printed at the time of configuration but upon next boot you get the following error messages:
ACL cannot be enabled on GigabitEthernet0/0/0 - insufficient TCAMAvailable: 24 Configured for ACL: 2048 Use sdm access-list command to reconfigWorkaround: None.
•
Symptom: The ip cef command does not re-enable the CEF switching on the Catalyst 8540 when previously disabled due to lack of memory. The Catalyst 8540 requires CEF switching but this can become disabled if there is insufficient memory available. When insufficient memory is available, the following message appears:
"%FIB-2-FIBDOWN: CEF has been disabled due to a low memory condition.Workaround: None.
•
Symptom: Multicast statistics might show an incorrect kilobits per second (kbps) rate.
Workaround: None.
•
Symptom: After upgrading from Cisco IOS Release 12.0(5)W5(13) to Cisco IOS Release 12.0(5)W5(13b) code, CSR no longer boots. Restoring the older code corrects the problem. The crash occurs after the file is read. Removing the configuration text file from the TFTP server prevents the router from crashing. If the router is booted from the NVRAM configuration and the command copy tftp running then is issued, the router will crash. copy startup running does not crash the system.
Workaround: None.
•
Symptom: On a switch using the ospf area-range command, the summary link state advertisement created might get stuck in the database and not be flushed after the command is removed.
Workaround: None.
•
Symptom: XPIF modules are not supported.
Workaround: None.
•
Symptom: An ima_failure_trap might not be generated when an IMA group gets deleted and the group state change might not be sensed by the switch processor.
Workaround: None.
•
Symptom: When ports on the eight-port Gigabit Ethernet interface module are connected to Ethernet interfaces, you get frames with new MAC addresses. Because the ports on the 8-port Gigabit Ethernet interface module send ca-updates to the Cisco IOS, the show bridge command displays the learned MAC addresses. Although the 8-port Gigabit Ethernet interface module has incrementing SkIPC Rx failed counters, there is no side effect. The format of show skmgmt stats command has been modified to take care of this problem.
Workaround: None.
•
Symptom: When using framing mode STM-16, the show controllers command might report the framing mode as invalid. This should not impact the network.
Workaround: None.
•
Symptom: When the existing two-port Gigabit Ethernet interface module is replaced with the enhanced Gigabit Ethernet interface module by online insertion and removal (OIR), the running configuration that is part of the existing two-port Gigabit Ethernet interface module will not be available for the enhanced Gigabit Ethernet interface module.
Workaround: Save the configuration to NVRAM before doing an OIR of the two-port Gigabit Ethernet interface module with the enhanced Gigabit Ethernet interface module. Complete the OIR of all two-port Gigabit Ethernet interface modules with the enhanced Gigabit Ethernet interface modules. Enter the reload command to get the configurations of the two-port Gigabit Ethernet interface module for the enhanced Gigabit Ethernet interface module. The other option is to save the configuration to a TFTP server, edit the configuration so that only those relevant to the replaced two-port Gigabit Ethernet interface module is retained, and do a copy of this edited configuration to the running configuration.
•
Symptom: DS3 Frame Relay port adapter firmware stops forwarding traffic when 16 channel groups are oversubscribed. The egress port hangs when it receives a frame with a size that is an integral multiple of 48 bytes.
Workaround: None.
•
Symptom: The standby switch processor (SP) does not take over when an active SP fails to initialize during system bootup.
Workaround: None.
•
Symptom: The ATM route processor might not forward IP traffic to the default route.
Workaround: None.
•
Symptom: When the switch is rebooted, at the point when it is going down, the console is flushed with the following messages:
Note: A random Spanning Tree Bridge Identifier address of 0000.0c00.9a70 has been chosen for Bridge Group 12 since 00:00:39: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.00:00:40: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.%SYS-3-LOGGER_FLUSHED:System was paused for 00:00:00 to ensure console debugging output.There is no mac address associated with the selected interface.00:00:40: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.These messages have no effect on the switch.
Workaround: None.
•
show version command displays an extra ATM interface.
Symptoms: The number of ATM interfaces is displayed as one more than the actual hardware present in the system.
Workaround: None.
•
Symptom: A bus error exception might occur when adding parties to a root connection.
Workaround: None.
•
Symptom: If a peer system is reloaded after a route processor switchover, all traffic into the port might be dropped. This prevents well-known VCs from coming up.
Workaround: Enter the shutdown command. To restart the disabled interface, enter the no shutdown command.
•
Symptom: CBR soft VPs do not come up on route processor switchover.
Workaround: None.
•
Symptom: An IPX packet containing the wrong length in the IPX header and requiring an encapsulation change causes the ingress port to hang. The switch router must be reloaded.
Workaround: None.
•
Symptom: The show bridge command might not show all interfaces and the show bridge verbose command might not show all interfaces and hash entries. Entries are not displayed until they are "learned" when traffic is passed through them. If no traffic is ever passed, the entries will not be displayed.
Workaround: None.
•
Symptom: The Interim Local Management Interface (ILMI) status of shaped and hierarchical tunnel subinterfaces that are down (not shutdown) may remain in the restarting state after issuing a shutdown/no shutdown command sequence.
Workaround: Enter a shutdown/no shutdown command sequence on the main interface of the subinterface, or bring the interface up by connecting it to a peer system.
•
Symptom: Soft PVCs might be disabled on subinterfaces.
Workaround: None.
•
Symptom: When snooping is enabled on an ATM or ATM-P port, ATM PVC deletion might fail. If the deletion fails, the system does not recognize the ATM PVC deletion failure and deletes the Frame Relay PVC. This causes the ATM PVC and Frame Relay PVC to go out of sync.
Workaround: Before deleting the Frame Relay PVC, disable snooping on the ATM port.
•
Symptom: The show controller command does not display loopback configurations.
Workaround: None.
•
Symptom: When running 12.0 code with UNI 3.0, the Catalyst 8540 MSR may fail to send poll PDU's. This can result in a no_response_timer expiration and flapping of the sscop link.
Workaround: Configure UNI 3.1 on the link.
•
Symptom: A switch configured for MPLS (tag switching) and running the Cisco IOS 12.0(9) maintenance software release does not correctly increment counters on outgoing TVCs, although the data are being correctly sent out of the TVC.
Workaround: Upgrade to 12.0(4a)W5(11a) or higher.
•
Symptom: Operation, administration, and maintenance (OAM) pings might not work after a route processor switchover.
Workaround: None.
•
Symptom: Sometimes a MAC address learned over a port channel might not be removed from the IOS bridge table, but the entry might age out from the port channel. IPC might not be generated correctly to delete the MAC from IOS. This does not lead to incorrect routing of the packets as the packets are switched by the interface module and the table is consistent in the interface module.
Workaround: Issue the clear bridge group command.
•
Symptom: Under heavy traffic, if an encapsulation change (for a VLAN) is attempted on a 2-port Gigabit Ethernet interface module, the change might fail because of a microcode download failure.
Workaround: Shutdown the port (or port channel and all members of the port channel) when an encapsulation change is needed on Gigabit Ethernet ports or GEC. Make the encapsulation change, and then bring the port back up (no shutdown).
•
Symptom: When a snooping interface that is a higher card/subcard than the snooped interface (for example, interface ATM 0/1/1 snooping interface ATM 0/1/0), the snooping interface might be in an up state instead of in a snooping state. In addition, some of the snooping VCs might not be restored. When entering the shutdown command, the high-order snooping interface might get stuck while in the going down state.
Workaround: None.
•
Symptom: When OAM is enabled globally and ATM and IP traffic is in the switch, a crash might occur during route processor switchover.
Workaround: None.
•
Symptom: The ATM interface might show different line codes after a switch processor switchover.
Workaround: Use the show controller command to find the correct line code, which is listed under the line code violation (lcv) count.
•
01:34:29: %TBRIDGE-4-GIANT: Giant received on Port-channel1, 1504 exceeds 1500 DA 00d0.583f.1b47 SA 0090.214f.9047 [0x08004500]Symptom: The above message might be seen with trunk interfaces configured in a bridge group with BVI after the clear bridge group or clear bridge command is issued. This is a transient state and the system recovers quickly.
Workaround: None.
•
Symptom: Packets coming in on a native VLAN being bridged to a port channel are dropped at the route processor. Untagged packets coming in on an 802.1Q trunk are associated with the native VLAN. Because of microcode limitations of the interface modules, the untagged packets are passed to the route processor to be routed or bridged. Consequently, we recommend that native VLANs not be used for network traffic and that they be limited to overhead traffic that terminates at the route processor (such as routing updates and CDP).
Workaround: Configure the traffic on a non-native VLAN.
•
The following traceback message appears:
%SK-7-ASSERT: Assertion Failure... Cant find port channel idb...Symptom: Sometimes the above message appears when 8-port Gigabit Ethernet interfaces are added to port channels.
Workaround: None.
•
Symptom: A no loopback sonet-terminal command entered on an OC-48c interface does not bring the interface down even when no cable is connected to the port.
Workaround: Use the shutdown command to bring down the interface.
•
Symptom: When a port is temporarily stuck (such as egress starvation for a slightly extended period of time) there might be a memory leak. This happens very rarely when a port is temporarily stuck repeatedly.
Workaround: Schedule a reboot when the available memory goes down to a very low value. This caveat is fixed in Cisco IOS Release 12.0(5)W5(13b) and later releases.
•
Symptom: ATM signaling would not generate the connect ACK message and would result in conformance test failure.
Workaround: None.
•
Symptom: Under some very heavy stressful conditions with IP multicast, when the mcast fan-out expansion fails, the VCs do not release correctly.
Workaround: Stop the traffic and enter the clear ip mroute* command.
•
Symptom: The primary route processor might loop when a redundancy prepare-for-cpu-removal command is entered.
Workaround: None.
•
Symptom: Synchronous Digital Hierarchy (SDH) and other standard compliancy is not supported on the OC-48c. Also, LEDs and SONET/SDH alarm signals might not generate properly on the OC-48c. When using the show controller command on the OC-48c, counters might duplicate.
Workaround: None.
•
Symptom: Added code to display the SR3 and SR5 registers. No impact to functionality.
Workaround: The show controller counters command is enhanced in Cisco IOS Release 12.0(5)W5(13b) and later releases.
•
Symptom: If you are using IPX EIGRP, you might experience an inconsistency in SAP updates on a remote router if the serial interface is brought down for a brief time and then brought up.
Workaround: Enter the clear ip eigrp neighbors EXEC command or enter the no ipx linkup-request sap command for the serial interfaces.
•
Symptom: When unicast and multicast traffic is present on Fast Ethernet ports, the primary route processor might loop when a redundancy prepare-for-cpu-removal command is entered.
Workaround: None.
•
Symptom: The show atm status command might show the status of a previously looped back interface as up when it should be showing the status as up only after the line loopback is removed from the interface.
Workaround: None.
•
Symptom: Loopback cells might not pass across the 25-Mbps ATM port adapter modules.
Workaround: Configure the no atm oam intercept end-to-end command from global configuration mode.
•
Symptom: When IPX packets are sent to the system, and the system does cross encapsulation for IPX packets, it might lead to a stuck port situation if the IPX protocol length is wrong (or corrupt).
Workaround: Remove the interface module and reinstall it.
•
Symptom: A switch router with the Per-Class Queueing Feature Card (PCQ FC) might not count received cells per VC on transit VCs.
Workaround: None.
•
Symptom: IPX node address of BVI is sometimes made invalid after a long period of time.
Workaround: Enter the shutdown and no shutdown commands on the BVI interface to recover. The node entry is programmed properly back in the table.
•
Symptom: Online insertion and removal of the route processor, even after entering the prepare-for-cpu-removal command, sometimes hangs the system.
Workaround: Power cycle the system.
•
Symptom: Term length does not work for the show functional-image-info command.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: The display from a show switch fabric command scrolls without stopping when the screen fills. The output just continues to the end of the display.
Workaround: None.
•
Symptom: The switch router does not correctly handle extended QoS and end-to-end transit delay IEs. This occurs primarily when interoperating with third-party vendor equipment.
Workaround: None.
•
Symptom: When reprogramming a switch processor FPGA after a route processor switchover, the
warningand theconfirmprompts might not appear.Workaround: None.
•
Symptom: The following error message might appear during switch processor FPGA reprogramming:
Cat85xx series supports a maximum bridge table aging timer of 600 secsWorkaround: None.
•
Symptom: Multiple tags for the default route might occur with VC merge.
Workaround: Do not use the tag-switching ip default-route command to assign tags to the default route.
•
Symptom: The input queue count on a BVI interface configured on the switch router might become larger than queue depth. This will block traffic from the same bridge group.
Workaround: Increase the hold queue on the BVI interface, depending on the rate at which the input queue fills up, or redesign the network to remove BVI.
•
Symptom: The switch router might crash after displaying the following message:
ipc_ok2send: Not enough room on 0, 280Workaround: None.
•
Symptom: When a port is stuck there is no debugging aid.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: When the system receives a lot of bad IPX packets, it sometimes produces a spurious memory access error. This does not impact functionality.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: With the eight-port Gigabit Ethernet interface module, spurious memory access occurs when booting the system with the latest image and copying the software configuration from a TFTP server.
Workaround: None.
•
Symptom: If interface snooping is configured, saved to NVRAM, and reloaded, the snooping VC might come up in a NO HW RES state.
Workaround: Use the shutdown command to bring down the interface.
•
Symptom: With the 8-port Gigabit Ethernet interface module, ping fails when changing the VLAN ID of a BVI interface.
Workaround: Take the subinterface out of the bridge group before changing the encapsulation. Then change the encapsulation and add the subinterface back to the bridge group.
•
Symptom: A VP associated code point is not supported between a Catalyst 8540 and a V switch on UNI 4.0/IISP interfaces.
Workaround: Use the atm signalling vpci command to configure the value of the VPCI that is carried in the signalling messages in the VP tunnel.
•
Symptom: The connected route associated with an Ethernet interface might not be in the routing table.
Workaround: Clear the routing entry or the Ethernet interface.
•
Symptom: When a port is stuck there is no debugging aid.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: Connected route associated with Ethernet interface might be intermittently missing from routing table.
Workaround: Clear the routing entry or the Ethernet interface.
•
Symptom: The image crashes when redundancy for the route processors is enabled.
Workaround: None.
•
Symptom: When the ipx down command is entered on an interface, the routing flag for IPX remains on.
Workaround: None.
•
Symptom: The switch can be configured to get its network clock from a constant bit rate (CBR) port without any clock being supplied to the port.
Workaround: None.
•
Symptom: New SVC or soft PVC calls from a Catalyst 8540 to a Fore ATM switch across a PNNI interface fail to connect. Connections initiated from the Fore switch do not fail.
Workaround: None.
•
Symptom: Under the heavy stress of a large volume of multicast traffic (6K [S,G] 1MB) the switch router crashes after failing to queue IPC messages.
Workaround: None.
•
Symptom: Counter values from the show controllers command are not descriptive enough for troubleshooting purposes. Each counter should have a label indicating the purpose of the counter.
Workaround: The output has been improved in Cisco IOS Release 12.0(5)W5(13b) and later releases.
•
Symptom: A mechanism is needed to troubleshoot and recover from port stuck failures.
Workaround: To recover from a port stuck failure, perform the following tasks:
–
–
–
–
Default behavior
If the switch router is not configured to reset the port upon detecting a port stuck failure the port will be isolated, thus preserving the integrity of the switch router.
Nondefault behavior
If the switch router is configured to reset the port upon detection of a stuck port failure, the switch router will isolate the port from the rest of the functioning ports, and reset the port. This might affect up to three other ports in the case of Fast Ethernet 10/100 modules.
Note
Use the following interface configuration commands to troubleshoot port stuck failures:
Caution
•
Symptom: On the Catalyst 8540, routing with BVI does not work on the 8-port Gigabit Ethernet subinterfaces with the following configuration:
Switch(config)# interface GigabitEthernet card/subcard/port.subinterfaceSwitch(config-if)# encapsulation dot1Q 12 nativeWorkaround: Reconfigure the dot1Q VLAN as non-native.
•
Symptom: Variable bit rate (VBR) might allow sustainable cell rate (SCR) oversubscription.
Workaround: None.
•
Symptom: A Catalyst 8540 might treat the link between the physical interface and the port channel interface as a multidrop link when the MAC address of the members of a port channel differs from the MAC address of the port channel itself.
Workaround: Delete the members of the port channel and then add them back in.
•
Symptom: The administrative status might be shown as up even when the controller is administratively down.
Workaround: None.
•
Symptom: Issue the shutdown and no shutdown commands for the new setting to take effect when you change the port speed from 10 to 100 seconds on a Catalyst 8540 CSR running 12.0(5)W5(13).
Workaround: None.
•
Symptom: FastEthernet interfaces that are in shutdown mode have packet output and bytes incrementing in the show interface command.
Workaround: Issue the clear counters command.
•
Symptom: Permanent virtual circuit (PVC) creation might fail if the virtual channel identifier (VCI) is greater than 24 bits. On a reload this error might happen when the VCI is greater than 12 bits.
Workaround: None.
•
Symptom: Some of the interface counters display a lower value for packet counters. Increasing the frequency of poll for statistics resolves the problem. This is needed only in two-port Gigabit Ethernet interface modules because of separate channels. This does not affect functionality.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or later.
•
Symptom: Cisco IOS Release 12.0(5)W5(13) and later releases boot only on route processors with hardware SAR.
Workaround: If you have a route processor with software SAR (that is, below version 5.4), you must upgrade your route processor to one with hardware SAR (version 5.6 or later). For route processor related issues, see the field notice at http://cco/warp/customer/770/fn5889_06291999.html.
•
Symptom: A MAC address that is learned as a REMOTE entry in the port channel members gets learned as a LOCAL entry after a host move.
Workaround: Issue the clear bridge bridge-id command.
•
Symptom: A host move under high traffic conditions can result in a missing MAC entry from the IOS bridging table. When routing over BVI, this might cause loss of connectivity.
Workaround: Issue the clear bridge command.
•
Symptom: When configuring a port channel, set the hold-queue size of the port channel to 300 and save it to NVRAM. On physical interfaces and port channels, the default hold-queue size is 75. The port channel hold-queue size should be 300. If the queue size of the port channel is not reset, there might be occasional packet drops bound to the route processor.
Workaround: None.
•
INTERNAL ASSERT: lss_ipm_chk_shr_vc() Assertion failureSymptom: These messages occur when there is IP multicast traffic and the user disables PIM on a physical interface and moves this physical interface to be a member of a port channel that is PIM enabled.
Workaround: Stop the IP multicast traffic, issue the clear ip mroute * command, and make the configuration change. If the assert messages occur, clear ip mroute * should fix the problem.
•
Symptom: When a member is removed from a bridge group which has HSRP over BVI configured and the router is an active router, active router MAC 0000.0c07.ac00 might not be removed from the interface.
Workaround: Issue the shutdown and no shutdown commands.
•
Symptom: A Simple Network Management Protocol (SNMP) walk of the ATM virtual channel cross connect table (CCT) might incorrectly show the following for a manually created cross connect:
atm MIb.atmMIBObjects.atmVcCrossConnectTable.atmVcCrossConnectEntry. atmVcCrossConnectAdminStatus.4680082.16.41.32.15.9.32 = up(1)Workaround: None.
•
Symptom: On a 8540 MSR running 12.0(4a)W5(11a) that the following entries may appear in the log:
*Dec 10 04:54:03.806: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x60448AF0 reading 0x0*Dec 10 04:54:03.806: %ALIGN-3-TRACE: -Traceback= 60448AF0 60448958 604468EC 601451D0 60148840 60149004 60143FB8 60153718The entries may appear when doing a SNMP get command. This may sometimes cause the active RP to crash and failover to the Standby RP (if available).
Workaround: Upgrade to Cisco IOS release 12.0(10)W5(18c) or later.
•
Symptom: Inverse multiplexing over ATM (IMA) groups might intermittently fail to come up, especially after reload and on E1 links.
Workaround: Enter the following command on the IMA interfaces:
(config-if)# fwmon "altrap 00 ff 00 ff 00 ff"If the group remains down even after issuing this command, this indicates a persisting alarm on the line.
•
Symptom: This problem is seen very infrequently when a large configuration is copied to the running configuration under heavy traffic loads.
Workaround: Issue the clear bridge command.
•
Symptom: For 10/100 Fast Ethernet interface modules, the internal chip set is designed to give higher priority to ingress tasks than egress tasks because of limited buffer availability on the ingress side. This design leads to a situation of egress starvation under heavy input traffic conditions when continuously scheduled ingress tasks cannot meet the 84-cycles budget requirement under "Auto L2-learning" conditions.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: When hundreds of TVCs in bidirectional mode are repeatedly configured and unconfigured on a switch router, VC resources might become exhausted.
Workaround: None.
•
Symptom: If any bridge-group members are 802.1q subinterfaces on an eight-port Gigabit Ethernet interface module, then protocol specific IRB configuration will not work over these ports because of local-switching ASIC (K1) chip limitations.
Workaround: None.
•
Symptom: The packet statistics displayed by the show epc ipmcast command sometimes report an incorrect value. This does not impact any functionality.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: PNNI/ILMI VCs are sending out CLP=1 traffic.
Workaround: None.
•
Symptom: When configuring the Simple Network Management Protocol (SNMP) trap receiver with the snmp-server host command, the following error message might appear on the console of the switch:
%Bad OID Failed to create host entry.Workaround: This error message occurs only when SNMP is initially configured on the switch and it is the first time that the snmp-server host command is entered. If the command is entered again the error message does not appear.
•
Symptom: PVC and VC status might not be updated in the Frame Relay end of a connection.
Workaround: None.
•
Symptom: When the tag switching is configured while the switch is rebooting, the following warning message displays:
ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:invalid tvcWorkaround: None.
•
Symptom: The facility alarm issues a warning when the secondary route processor is brought down, but the warning goes away if the secondary route processor is initialized at ROMMON without booting.
Workaround: None.
•
Symptom: After booting the image, the switch router might display the following error messages and continue looping:
00:04:06: %SYS-3-LOGGER_FLUSHED: System was paused for 00:00:34 to ensure console debugging output.00:04:07: ipc_ok2send: Not enough room on 0, 8400:04:07: %LINK-2-INTVULN: In critical region with interrupt level=0, intfc=ATM1/0/1 -Process= "IP-E 00:04:08: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. IGRP Router", ipl= 0, pid= 153-Traceback= 600711BC 60355BC4 600762CC 601C4BC8 601C3E38 601C4084 6018CEEC 6017F134 6017FF48 60182818 60194DE8 600989DC 600989C800:04:07: ipc_ok2send: Not enough room on 0, 8400:04:07: ipc_ok2send: Not enough room on 0, 8400:04:07: ipc_ok2send: Not enough room on 0, 84. . .Workaround: None.
•
Symptom: The root cause of this is that the HSRP specific structures are not properly updated when an interface goes down or when a card is removed.
Workaround: Remove HSRP from the configuration before removing the card.
•
Symptom: When E1 Frame Relay ports are coming online the following message might be displayed:
pam_interrupt: unknown pam in slot <slot_number>This message is harmless and does not affect the functioning of the switch router.
Workaround: None.
•
Symptom: When the color of an encapsulation is changed on a subinterface, the subinterface does not transition through the spanning tree states. In some situations this might result in spanning tree loops.
Workaround: To prevent looping when changing the subinterface color, delete the subinterface and recreate it with the new encapsulation color.
•
Symptom: When several IP/IPX ACLs are configured on Ethernet interfaces, a switchover might cause the primary CPU to crash.
Workaround: None.
•
Symptoms: The following error messages might appear on the Gigabit Ethernet interface module with the ACL daughter card during a route processor switchover.
NO ACL Card Detected on the PAM in Slot[0]FATAL ERROR: ACL-FPGA reset failedWorkaround: OIR the interface module.
•
Symptom: On Fast Ethernet ports, untagged packets coming in on the 802.1q native VLAN are not processed by the microcode. Instead, they are transmitted to the route processor and processed. This means that high route processor utilization will be seen if untagged packets are received at a high rate on the native VLAN subinterfaces.
Generally, only management data, transmitted at a very low rate, would be seen on the native VLAN, since it is mainly used for network management purposes.
Workaround: None.
•
Symptom: A Catalyst 8540 might have problems with IPX routing using ATM router module ports. Once the LE-ARP entry times out, IPX packets are sent over the BUS. Because the route processor is not aware of the IPX packets anymore, it does not trigger the LE-ARP request and the switch router continues to forward the IPX traffic for the given destination over the BUS. This problem negatively impacts IPX performance. IP performance is not affected.
Workaround: Set the atm idle-timeout command to 0 on all the devices in the affected ELAN before the traffic is started, or move the LES/BUS to a Catalyst 5000 ATM LANE module.
•
Symptom: HSRP interface tracking may incorrectly determine that a down interface is up when the software reloads.
Workaround: Enter the shutdown/no shutdown commands on the interface.
•
Symptom: The interface command arp timeout 300 disappears from the running configuration after a reboot.
Workaround: None.
•
Symptom: If a switch processor switchover is initiated from a console port, some commands might still be able to be entered from a connection through a telnet or a vty session.
Workaround: Wait until the switchover is complete before issuing any commands from a vty port.
•
Symptom: The arp timeout interface command disappears from the running configuration after a reboot.
Workaround: Upgrade to Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: The following message is sometimes seen:
Received malformed TLVWorkaround: None; this message is harmless.
•
Symptom: In large bridge group and bridge group member configurations exceeding supported limits, high route processor utilization from the Tbridge Monitor process might occur. System resumes normally.
Workaround: None.
•
Symptom: When multiple 802.1q subinterfaces are configured over interfaces belonging to the same slot of an 8-port Gigabit Ethernet interface module, the traffic will be locally switched (broadcasts, flooding, etc.) among those interfaces, and the front-panel subinterfaces are represented by a single subinterface in the back end. Therefore, it does not consistently represent the proper configuration of front-panel subinterfaces. Because of this, the front-panel port configuration might not always work, depending on the deployment scenario.
Workaround: Configure different encapsulations among the different subinterfaces in the same slot. This makes the Ethernet interfaces in the back end perform bridging and routing.
The above workaround applies only if the subinterfaces are used to perform different switching functions. Multiple subinterfaces with the same encapsulation in the same bridge group might be used to provide local switching capability for trunk ports and possibly routing over BVI.
•
Symptom: On reload after configuring a permanent virtual circuit (PVC), the PVC might be in the down state.
Workaround: Delete and re-install the PVC.
•
%SYS-3-INTPRINT: Illegal printing attempt from interrupt level. -Process= "OIR Handler", ipl= 2, pid= 10 -Traceback= 600386C0 60038134 602C08BC 602BAEB4 602BA000 600B07F4 603BC180 603BBE80 602C9B88 602C9CB8 60351A74 600976F4 600976E0Symptom: The above messages sometimes appear upon online insertion and removal (OIR) of the route processor or switch processors and also of the 2-port Gigabit Ethernet or 10/100 Fast Ethernet interface modules. This message is harmless and the system should continue to function normally after the message.
Workaround: None.
•
Symptom: The redundancy prepare-for-cpu-removal command initiates a route processor switchover through a software forced crash. The forced crash causes the message buffer to flush and display to the console before initiating the switchover.
Workaround: None.
•
Symptom: It can take up to 3 minutes to sync up the running configuration to the secondary route processor upon inserting the secondary route processor. This is not a problem. The task is run as a background task and hence runs as a low priority task.
Workaround: None.
•
Symptom: The switch processor switchover might generate a route processor HOG message in the Exec process. Console input is blocked until the switchover is complete. The system resumes normally.
Workaround: None.
•
Symptom: In bridge group and bridge group member configurations exceeding supported limits, route processor HOGs from the Net Background process might appear. System resumes normally.
Workaround: None.
•
Symptom: In bridge group and bridge group member configurations exceeding supported limits, route processor HOG messages from the EPAM Card Manager process might appear. System resumes normally.
Workaround: None.
•
Symptom: Route processor redundancy requires a software interface descriptor block for the secondary route processor. If you use up all the interface descriptor blocks through subinterface creation before booting the secondary route processor, interface descriptor block creation failure occurs. Boot the secondary route processor before attempting to configure the maximum number of interface descriptor blocks.
Workaround: None.
•
Symptom: If a switch processor switchover occurs before K1 boots up, the switch router might hang or crash.
Workaround: None.
•
Symptom: After hot-swapping a fast Ethernet interface module, OSPF interfaces are not recognized.
Workaround: Configure a loopback interface before enabling OSPF, so that the IP address of the loopback will be selected as the OSPF router ID. This is the recommended design for OSPF configuration. To minimize the convergence time, use a software interface (which never goes down unless administratively shut down) as the router ID. This will also prevent OSPF restarts upon interface toggling.
•
Symptom: After a switch processor switchover, the input and output packet counters have invalid values.
Workaround: None.
•
Symptom: Ethernet interface modules reset during reinitialization after a switch processor switchover.
On a switch processor switchover, Ethernet interface modules behave as if a system reload occurred, and take the same amount of time to reinitialize as they do for a reload. Before the interface modules come up, and a switchover occurs, timeout messages are entered. This happens because the Ethernet ports are initialized through IPC, and halfway through the process the Ethernet interface modules are reset again by the switchover.
Workaround: None.
•
Symptom: With the following configuration:
line con 0exec-timeout 0 0privilege level 15 <<<<<<<<<<<<<<<<<<length 48transport input noneThe switch will bootup in enable mode.
If a CPU switch-over occurs, the switch will not preserve this configuration and will boot up in user mode.
Workaround: We recommend that the user enter enable password to enter enable mode after a CPU switch over.
•
Symptom: After hot-swapping a fast Ethernet interface module, OSPF routes are not propagated properly.
Workaround: Issue the shutdown and no shutdown commands on the appropriate interface.
•
Symptom: Do not hot swap an active switch processor (SP) module before putting it in standby mode.
If an SP module is currently active while the switch router is running IOS, and the module is removed from the chassis before making it a standby module, the connections might hang. This stops switch traffic after an SP switchover.
Workaround: Before removing an active SP module, make it the standby.
First determine whether the SP module to be removed is currently active using either of the following methods:
–
–
If the SP module is active, the active LED on the module is green.
If the SP module is standby, the standby LED on the module is green.If the SP module is currently the standby, remove it without issuing any commands.
If the SP module is currently active, use the following EXEC command to designate the other two SP modules as the active switch processor modules:
redundancy prefered-switch-card-slots slot#1 slot#2
The range of the slot value is 5 through 7. This prepares the SP module to be removed as the standby module.
Once the prompt returns, ensure that the SP module is the standby by issuing the following command:
show preferred-switch-card-slots
The SP module should no longer be active, and can be safely removed.
The following example shows how to prepare the switch router to safely remove an active SP module from slot 5:
Switch#show preferred-switch-card-slots The currently preferred switch card slots are slot:5 and slot:7 The currently active switch card slots are slot:5 and slot:7Switch#redundancy prefered-switch-card-slots 6 7Switch#show preferred-switch-card-slotsThe currently preferred switch card slots are slot:6 and slot:7 The currently active switch card slots are slot:6 and slot:7•
Symptom: OC-48c SONET is supported but SDH is not.
Workaround: None.
•
Symptom: If an OC-48c interface module is removed and reinserted on an active switch router when NCPD is enabled, and the clock source is set to the OC-48c interface, the ILMI state remains in waiting/restarting on the OC-48c interface.
Workaround: After the OC-48c interface module is reinserted, enter a shutdown command, followed by a no shutdown command on the affected OC-48c interface.
•
Symptom: CBR interfaces might incorrectly come up when configured as structured services, even though no cables are plugged into the ports. This problem might also occur when removing the configuration of the structured services.
Workaround: Remove and reinsert the CES port adapter.
•
Symptom: When the secondary route processor is brought to ROMMON and initialized in the rommon, the redundancy alarm is cleared in the primary route processor even though the secondary route processor is still down.
Workaround: None.
•
Symptom: Entering shutdown/no shutdown commands on an ATM router module interface, especially when it has several LANE clients configured, can cause the switch router to issue messages similar to the following:
%LANE-3-LANE_ERROR: lecs finder: ILMI hung on interface ATM1/0/0This message indicates that an internal timeout occurred. The interface recovers and normal operations are not affected.
Workaround: None.
•
Symptom: Under heavy stress conditions with multicast PIM-DM, there can be a situation in which
VC allocation failedmessages appear. This is a high stress scenario, and it happens when all the VC resources are not freed properly.Workaround: Stop the traffic for a short time (a few minutes), enter the clear ip mroute * command, and then restart the traffic. This caveat has been resolved by ensuring that the VC resources are cleaned up properly in Cisco IOS Release 12.0(5)W5(13b) and later releases.
•
Symptom: The show interfaces atm-sec0 command always displays zero counter values.
Workaround: None.
•
Symptom: The switch router might crash when logging messages to a buffer when the switch router is very active.
Workaround: None.
•
Symptom: If an IPX router goes down in a multiple-path topology, the Catalyst 8540 layer might get out of synchronization with the Layer 3 IPX routing table. A lower layer forwarding and switching anomaly might occur if the router first receives a "down" notification for a particular network from the same host that originally notified the router about that network, and then, shortly afterward, the router receives a good route to the network from another host.
Workaround: None.
•
Symptom: The switch router sends PIM v2 register messages when PIM v1 is configured.
Workaround: None.
•
Symptom: The secondary route processor incorrectly displays out-of-sequence messages even though the packets are resent and the sequence is recovered.
Workaround: None.
•
Symptom: If a Fast Ethernet interface module is installed on an active switch router, cells become stuck in the switch fabric when a route processor module is inserted into the chassis.
Workaround: Upgrade to Fast Ethernet FPGA 3.3 or later.
•
Symptom: Flash PC cards cannot be formatted on the secondary route processor.
Workaround: Format the Flash PC card on the primary route processor then move it to the secondary route processor.
•
Symptom: If an 8-port Gigabit Ethernet interface module is installed on the switch router, switch processor switchover is temporarily unsupported. After issuing a redundancy prefered-switch-card-slots command, the switch router displays the following message:
There is 8 Port Gigabit Ethernet PAM in the Chassis, SP switch over is temporary unsupportedWorkaround: None.
•
Symptom: A Gigabit Ethernet interface indicates it is in the up state, even though there is no longer connectivity through this interface. Pinging a device through the Catalyst 8540 MSR times out. Pinging a device from the Catalyst 8540 MSR is successful.
The sh epc if-entry int gi 0/0/0 gi 3/0/1 command displays the following message:
Status Down Broute VC - 0The shutdown/no shutdown command sequence restores the connectivity.
Workaround: None.
•
Symptom: A Gigabit Ethernet interface displays its status as up, however, there is no connectivity through the interface. Pinging a device through the Catalyst 8540 CSR times out but pinging a device from the Catalyst 8540 CSR is successful.
Workaround: Issue the shutdown and no shutdown commands on the appropriate interface to restore connectivity.
•
Symptom: Ports on an eight-port Gigabit Ethernet interface module cannot be snooped or used to snoop other interfaces.
Workaround: Use a Gigabit Ethernet port from a two-port Gigabit Ethernet interface module to snoop.
•
Symptom: The switch router might crash with a bus error. The interfaces were not restored after the crash.
Workaround: None.
•
Symptom: In rare instances, a Catalyst 8510 CSR takes a software forced crash at a program counter value of 0x6004A4D64 when running Cisco IOS Release 12.0(1a)W5(6f). Because the conditions which trigger this crash are not currently known, it is strongly advised that the router be configured to write a core dump if such an instance happens.
Workaround: None.
•
Symptom: Even though the route processor capabilities do not match, the switch router still reports full redundancy when it boots up.
When the secondary route processor resources, such as the amount of DRAM, are equal to or greater than the primary route processor resources, the switch router is fully redundant. However, after a route processor switchover, if the new primary route processor resources are more than those of the new secondary route processor, a fully redundant switch router becomes conditionally redundant and the new primary route processor console displays a message such as the following:
00:03:14: %COUGAR_EHSA-4-FLASH_MISMATCH: Mismatch in BOOTFLASH SIMM size between Primary and Secondary ACPMsBOOTFLAH SIMM Size - Primary = 16 MB, Secondary = 8 MBBecause of the BOOTFLASH size mismatch, the files that fits in thePrimary ACPM's BOOTFLASH may not fit in the Secondary's BOOTFLASH, if andwhen a switchover occurs. This may cause loss of information. The systemis now running CONDITIONALLY REDUNDANT - subject to the above mentionedmentioned restrictionWorkaround: Ensure that both route processors on the switch router have the same resources.
•
Symptom: When copying a file to a Flash PC card on a secondary route processor, the switch router might return control to the user before the copy process is complete. If a reload is done before the image is completely copied, the file might be lost.
Workaround: Enter the dir sec-slotn: command to verify that the image is completely copied before reloading the switch router.
•
Symptom: IP multicast counters (S,G) might not be accurate.
The microcode maintains 16-bit packet counters for each (S,G) entry, which are polled every 10 seconds. If the input rate for the (S,G) entry is higher than 6.4K packets/second for a 10-second duration, the counters might overrun.
Workaround: None.
•
Symptom: On an OC-12 interface, the show controllers command might incorrectly show very large numbers of tx and rx counters.
Workaround: None.
•
Symptom: The show running-config command display contains a reference to the aux 0 port, which is not supported.
Workaround: None.
•
Symptom: The undebug all command does not disable the debug redundancy all command.
Workaround: Use the no debug all command to disable all debugging activity.
•
Symptom: If the configuration register value is set to 0x2102 while autobooting, the system might experience a TLB (translational bridging) exception if the system boot image is not specified using the boot system command. The system continues to boot without problems, despite this exception.
Workaround: When the configuration register is set to 0x2102, specify the system boot image to be autobooted using the boot system command. If the system boot image is specified using the boot system tftp command, also specify the bootloader image using the boot bootldr command. After executing these commands, save the configuration in the NVRAM, using the copy running-config startup-config command.
•
Symptom: All Software Upgrade (system IOS, ATM, FDDI) is broken on Cluster Manager and VSM if the cluster member's management VLAN has no IP address.
Workaround: None.
•
Symptom: When attempting to reprogram the ROMMON, the switch router sometimes hangs after displaying the following message:
Resetting in 3 secondsWorkaround: Remove and reinsert the route processor module or power cycle the switch router.
•
Symptom: The debug ncdp packets, debug ncdp errors, and debug ncdp events commands do not display any information when accessing the switch router through the Ethernet port.
Workaround: Access the switch router using the console port.
•
Symptom: If ILMI is configured on the terminating interface of a soft VC, ILMI must be in the UpAndNormal state for this soft-VC to come up.
Workaround: Upgrade to the Cisco IOS release 12.0(10)W5(18c).
•
Symptom: Modem access to the console port requires special settings.
The Catalyst 8540 provides support for connecting the modem to the console port. However, the following settings of the modem are required:
1. Enable auto answer mode.
2. Suppress result codes.
You can configure your modem by setting the DIP switches on the modem or by connecting the modem to terminal equipment. Refer to the user manual provided with your modem for the correct configuration information.
Please note there are no hardware flow control signals available on the console port, so the console port terminal characteristics should match the modem settings.
Workaround: None.
•
Symptom: The Catalyst 8540 might display a CRC error when it obtains the clock over an OC-3c link from a LightStream 1010 ATM switch and then uses or redistributes the clock over an OC-12c link.
Workaround: Use the internal clock or bring the clock source directly to the Catalyst 8540.
•
Symptom: PVCs exiting the switch router over a hierarchical VP tunnel are not preserved when the route processor switches over.
The switch router stops switching traffic over such PVCs upon and after the route processor switchover. The hierarchical VP tunnel remains active, however, and after the route processor switchover the VCs defined over the hierarchical VP tunnel (both PVCs and SVCs) function as expected.
Workaround: None.
•
Symptom: If no ACL module is present in a slot, the following message appears in the console log on a SP switchover:
No ACL card in slotThis is an informational message only and has no effect on switch router function.
Workaround: None.
•
Fast Ethernet port identifier truncated in the show atm status command.
Symptom: The show atm status command is not supported.
Workaround: The command is supported in Cisco IOS Release 12.0(5)W5(13b) or a later release.
•
Symptom: Bridging on a subinterface is only supported in conjunction with the IEEE Spanning Tree.
Workaround: None.
•
Symptom: Under certain circumstances, the Catalyst 8540 might display inaccurate traffic statistics on NNI or UNI interfaces.
Workaround: None.
•
Symptom: Despite having enough bandwidth, resource management might reject some soft PVCs.
Workaround: None.
•
Symptom: 8-port Gigabit Ethernet interfaces cannot support bridging when the bridge group runs DECNET Spanning Tree.
Workaround: None.
•
Symptom: After shutting down an ATM router module interface which is a member of a port channel, the interface entry is not removed from the port channel. Since removing a member interface from a port channel does not put the port channel into blocking mode, no loss of connectivity should result.
Workaround: None.
•
Symptom: When using the Catalyst 8540 usage parameter control (UPC) tag functions (change the CLP=0 to CLP=1), the following ports might not work: For 16-port OC-3c and 4-port OC-12c interface modules, interfaces ATM 0/0/0, ATM 0/0/2, ATM 2/0/0, ATM 2/0/2, ATM 9/0/0, ATM 9/0/2, ATM 11/0/0, and ATM 11/0/2 might fail UPC tag mode.
Note
Workaround: Upgrade the switch processor FPGA image to Version 1.5 (fi-c8540-msp.A.1-5) or later.
•
Symptom: The ILMI keepalive feature resets the interface on the second retry following a link failure. This behavior might occur despite having configured the system to allow up to five retries.
Workaround: None.
•
Symptom: On a system configured with either both power supplies or only power supply 1, issuing the show hardware, show hardware detail, or show tech-support commands might cause the memory corruption. If this memory corruption occurs and the show subsystem command is entered, the Catalyst 8540 might fail unexpectedly.
Workaround: If the system is configured with two power supplies, remove power supply 1 before issuing any of the commands listed in the Symptom section. If the system is configured with one power supply, make sure that you use power supply 0.
•
Symptom: Alignment correction made while running IPX routing and data packets over dot1q over fec.
Workaround: None.
•
Symptom: If the switch router is booted with cleared NVRAM, because the switch router is new, or after a write erase command, and the automatic configuration is skipped, the following messages are displayed:
%Error opening tftp://255.255.255.255/network-confg (Not enough space)%Error opening tftp://255.255.255.255/cisconet.cfg (Not enough space)%Error opening tftp://255.255.255.255/switch-confg (Not enough space)%Error opening tftp://255.255.255.255/ciscortr.cfg (Not enough space)These messages are harmless and can be ignored. The only effect is an increased boot time of approximately 1 minute.
Workaround: Use the automatic configuration feature upon first boot-up or when the switch router is booted after a write erase command.
•
Symptom: The digital cross-connect unit (DCU) might malfunction unexpectedly.
Workaround: None.
•
Symptom: Following a route processor switchover, the switch router might fail to recognize port adapter interfaces associated with a carrier module.
Workaround: Upgrade the carrier module FPGA image to release 1.7 or later.
•
Symptom: With RMON enabled on Fast Ethernet interfaces, SNMP interface counters begin to grow exponentially. Port utilization might be greater than 100% when the actual utilization might be as low as 1%. This happens with either RMON native or RMON promiscuous. While SNMP counters are erratic, the CLI remains accurate.
Workaround: None.
•
Symptom: Following a software reload, the Catalyst 8540 might fail unexpectedly with a write bus error. This failure might occur if the system is configured with one route processor, and the switch processor modules are installed in slots 5 and 6 or in slots 6 and 7.
Workaround: Install the switch processor modules in slots 5 and 7.
•
Symptom: The router fails to see incoming AppleTalk broadcasts when the router, configured for IRB, is routing and bridging IP and just routing AppleTalk.
Workaround: None.
•
Symptom: When powering up and booting the switch router with two route processors, or installing a second route processor in a working switch router, the console port of the secondary route processor might display the following error message:
SECONDARY CPU: *** Failure - Can not sync to other CPUs sync ****Sys Clock lock and sync failed.The secondary route processor fails to boot and the switch router is in a non-redundant mode. This problem occurs when the Catalyst 8540 with two route processors and the secondary route processor have an FPGA image version of 4.5 or earlier. To recover, power cycle the switch router or remove and reinsert the secondary route processor.
Workaround: Upgrade the route processor FPGA image to version 4.6 or later.
•
Symptom: An IPX packet containing the wrong length in the IPX header and requiring an encapsulation change causes the ingress port to hang. The switch router must be reloaded.
Workaround: None.
•
Symptom: On the Catalyst 8540 CSR running the W5(11) code or lower, adding logging source-interface and then removing logging source-interface might stop syslogs being sent out on Ethernet 0 (the management port). Syslogs continue to be sent out through the regular interface module ports.
Workaround: Do not configure the source-interface. If you configure the source-interface, do not remove the logging source interface. Rebooting the switch router resolves the state. An error syslog (LINK-3-UPDOWN) also corrects the problem.
•
Symptom: The squeeze command might result in an error in which the squeeze progress is not displayed. For example:
ms04_m84_01#squeeze sec-slot0:All deleted files will be removed. Continue? [confirm]Squeeze operation may take a while. Continue? [confirm]Squeeze of sec-slot0 completems04_m84_01#17:48:06:%SCHED-2-EDISMSCRIT:Critical/high priority process IPC Seat Manager may not dismiss.-Process= "IPC Seat Manager", ipl= 0, pid= 14-Traceback= 600ACC30 6001E8B8 60037470 60038BEC 60037714 604139D8 60413A8C 60433E78 60095794 60095780Workaround: None.
•
Symptom: The switch router crashes when you enter and exit configuration mode repeatedly and quickly.
Workaround: None.
•
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.
•
Symptom: With IRB configured, bridging loops occur if there is a physical loop for the broadcast domain.
Workaround: None.
•
Symptom: The Hot Standby Router Protocol (HSRP) over a Bridge Group Virtual Interface (BVI) configuration is not supported if the BVI encompasses LANE interfaces. This configuration is valid and functional only if the BVI encompasses Ethernet interfaces.
Workaround: None.
•
Symptom: Appletalk is not supported on 8-port Gigabit Ethernet interface modules.
Workaround: None.
•
Symptom: Following a change to a spanning tree, inconsistencies might occur in the bridge members information stored in the Ethernet module interface and the IOS.
Workaround: Use the clear bridge command to purge the bridging cache.
•
Symptom: After repeatedly entering and exiting global configuration command mode, the system might freeze unexpectedly.
Workaround: None.
•
Symptom: When the system is configured to autoboot, and the redundancy prepare-for-cpu-removal command is entered, the route processor does not stay in ROMMON mode, but proceeds to autoboot again.
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
•
Symptom: A T1 CES interface does not send out a remote alarm indication (RAI) in the reverse direction upon detecting an alarm indication signal (AIS).
Workaround: None.
•
Symptom: Attempting to format the Intel 200 Series Flash PC card that is currently shipping with other platforms (such as the Catalyst 6000) might cause the Catalyst 8540 to fail unexpectedly with a bus error. If this failure occurs, the system will not boot up successfully until the Flash PC card is removed from the switch router.
Workaround: Remove the Flash PC card from the switch router.
•
Symptom: IPX ping incorrectly shows success during simultaneous pinging.
Workaround: None.
•
Symptom: When a clear bridge command is issued, MAC addresses specified for the access lists are not reprogrammed in the CAM tables.
Workaround: Issuing a shutdown/no shutdown on the bridge port where the access list is configured reprograms the MAC address in all other bridge group members.
•
Symptom: After an interface timeout is expired, adjacencies for static ARP entries are refreshed every minute, which might cause momentary connectivity loss. This does not apply to dynamically created adjacencies.
Workaround: None
•
Symptom: The Catalyst 8540 sends an invalid PDU when the counters are cleared.
Workaround: None.
•
Symptom: Following the online insertion of an interface module into a router configured with IGMP static group and running multicast traffic, failures occur when downloading to the interface module.
Workaround: Either shut down any interface configured with IGMP static group before inserting or removing interface modules; or do not insert or remove interface modules online when the switch router is configured with IGMP static group.
•
Symptom: Path costs on Gigabit Ethernet interfaces shown by the show span command do not match the expected default value of 100.
Workaround: Set the path costs manually. One option would be to set the path cost for Gigabit EtherChannel (GEC) ports to 1 and set the path cost for the non-GEC ports to 2.
•
Symptom: When large numbers of MAC addresses are learned over a port channel, some addresses do not age out after the aging timer expires.
Workaround: Use the clear bridge bridge-id command to remove learned MAC addresses.
•
Symptom: The interface delay metric is set inappropriately for port channel interfaces where one or more Gigabit Ethernet interfaces or Fast Ethernet interfaces are grouped into a channel. The delay for a single Gigabit Ethernet interface is 10 microseconds. The delay for a port channel consisting of one or more Gigabit Ethernet interfaces is 100 microseconds. The delay for a single Fast Ethernet interface is 100 microseconds. The delay for a port channel made up of one or more Fast Ethernet interfaces is 1000 microseconds.
This incorrect setting has implications for routing protocols that use interface delay as part of the metric, such as IGRP and EIGRP, and might cause the routing protocol to prefer a route through a single interface over a route through a port channel, everything else being equal.
Workaround: Manually configure an appropriate delay on the port channel interface using the delay command.
•
Symptom: The "Uptime" for the secondary route processor from a show redundancy command might display incorrectly. This problem occurs because the "Uptime" rolls over after about four hours.
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 8-port Gigabit Ethernet interface module lets the event manager know, in microseconds, the maximum amount of time a job is expected to run. It also tracks how long each job actually ran. The Job <job name> ran <time> message should alert you that a job ran longer than expected. It is not normal for the message to come often or at a regular interval.
Workaround: None.
•
Symptom: Performing an OIR on the secondary route processor might produce the following error message:
%OC3SUNI: Read diagnostics for ATM1/1/0 failed(1)Workaround: Reboot the system.
•
Symptom: Routing protocols take more time to converge after reboot on a router with large ACLs configured on many interfaces.
Workaround: None. When you reboot a router, it can take considerable time to populate large ACLs on many interfaces, resulting in a delay in the convergence of some routing protocols.
•
Symptom: Configuring interfaces on line aux 0 might cause the redundancy feature to fail. The primary and secondary route processors will boot, but running the show redundancy command on the primary route processor incorrectly indicates that the secondary route processor is down.
Workaround: Remove all configuration commands from line aux 0 and reboot the switch router.
•
Symptom: When using FTP to transfer a core file to a server, the switch router might not create an exception dump following a system crash.
Workaround: None.
•
Symptom: IPX ACL on a subinterface of a non-trunk main interface does not filter traffic.
Workaround: Configure the ACL on the main interface instead of the subinterface to achieve the same result. Due to space limitations, IPX ACL cannot be applied directly to a subinterface of a non-trunk main interface.
•
Symptom: If an interface in subslot 1 of a carrier module is the present active clock source, and an interface in subslot 2 of the same carrier module is the secondary clock source, the clock source of the secondary might be overridden to loop-timed rather than network-derived.
Workaround: None.
•
Symptom: After replacing an existing configured ACL on an interface with another ACL, routed packets that should be blocked are forwarded for a very short period of time.
Workaround: Within a short period of time, the ACL is reprogrammed and block packets as required. When you remove an ACL and replace it with another ACL, ACLs are temporarily removed from memory, and the ACL flag is turned off. Some packets that should be blocked by the ACL will temporarily be permitted until the ACL flag is turned on again.
•
Symptom: When using Cisco IOS Release 12.0(1), the router crashes with a bus error when an attempt is made to remove the bridge-group command.
Workaround: None.
•
Symptom: On a router with a rev-B1 fast Ethernet interfaces, there is no way to turn off time-stamp refresh during destination address lookup. A source address is learned on a port in the initial spanning tree state. After the port goes into blocking state, a destination address lookup on the received packet keeps the entry alive. This is particularly true where the source and destination address are the same, as in the case of keepalive packets.
Workaround: None. This problem does not occur in routers with fast Ethernet interfaces later than rev-B1.
•
Symptom: After upgrading the ACL FPGA image using the reprogram command, the system warns you that the image is not compatible with the current IOS version, and the ACL card might become unusable unless you update the IOS image.
Workaround: Ignore this warning for the ACL card, and continue the FPGA download. Do not ignore this warning for other controllers.
•
Symptom: When configuring ACL on subinterface 1023 or above, the router returns the following message:
CARD:ERROR: access_list_add;Index allocation failed for lookuptype 2CARD:ERROR: handle_addition:access_list_add failed:label 1, Fast Ethernet3/0/0.3 LSS_ACL_AP_OUTPUT_ACLWorkaround: Limit the number of subinterfaces configured with ACL to 1000 for the switch router.
•
Symptom: Cannot receive CDP packets on a trunk port connected to a Catalyst 5000 if CDP packets are coming on a VLAN for which a subinterface is not configured.
Workaround: To receive CDP packets, configure a dummy VLAN subinterface on the trunk port connected to the Catalyst 5000.
•
Symptom: Two Catalyst 8540 CSRs with 802.1Q VLAN encapsulation cannot ping each other.
Workaround: To receive ARP packets, use ISL VLAN encapsulation on trunk ports connected to a Catalyst 5000.
•
Symptom: The soft VCL counter incorrectly reaches its maximum value upon link transition, thus keeping soft VCs from connecting to ports which have incorrect soft VCL numbers.
Workaround: Reload the system.
•
Symptom: The status LED on the standby switch processor module remains red after boot up.
Workaround: None.
•
Symptom: When the switch router is booted after a power cycle, the reload reason in the show version command does not indicate that the "System restarted by power-on."
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
•
Symptom: After performing an OIR on a carrier module, the corresponding port adapter interface counter values displayed in a show interface command might become unreliable.
Workaround: None.
•
Symptom: When a static route pointing to one interface is changed to point to a different interface, the corresponding adjacency entry is not updated.
Workaround: Use the clear arp command to reprogram the correct adjacencies.
•
Symptom: When a port adapter is removed from the chassis, the entry in ciscoLS1010SubModuleTable is not deleted.
Workaround: None.
•
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 shutdownJul 15 11:33:31.788 pdt: %ATMSIG-3-FAILASSERT: Assertion failed: file "../src-4k/alignment.c," line 897FALSE-Traceback= 6046FA4C 60096908 600971D4 600B1F10The LED on the interface module is orange and none of the interfaces will work. The interface module is nonfunctional.
Workaround: Reload the Cisco IOS software, and the interface module will function. The LED should always be green when the 8-port Gigabit Ethernet interface module is functioning.
•
Symptom: Connections to the ATM router module interfaces cannot pass through shaped VP tunnels.
Workaround: Configure hierarchical VP tunnels for ATM router module interface connections.
•
Symptom: The Catalyst 8540 does not support a PVP tunnel with a VPI value of 0.
The IOS software relates subinterface 0 to the main interface, so interface ATM x/y/z.0 represents the main interface x/y/z. If the user attempts to create a PVP tunnel with a VPI value of 0, the system should return an error on interface ATM x/y/z.0.
Workaround: None.
•
Symptom: An unexpected system failure might occur following a show tech-support command when OC-3c interfaces are present. This might also occur with the show controllers command.
Workaround: None.
•
Symptom: The versions of the Smart Modular and Sharp Flash PC cards used to store diagnostics and IOS software images might report unrecoverable write errors. Affected cards use a Sharp chip set (LH28F016SCT).
Workaround: If you have a Smart Modular Flash PC card, the fix for this problem is available with the Cisco IOS Release 12.0(4a)W5(11a) software. Netboot the image, reformat the Flash PC card and copy the image to it. You can then autoboot from the Flash PC card.
Note
•
Symptom: The Catalyst 8540 does not allow you to configure more than 255 VPs, even though the 12-bit VPI allows a maximum of 4095 VPs.
Workaround: None.
•
Symptom: The
ciscoLS1010ChassisInletTempStatusMIB, which is an object added for the Catalyst 6400 platform, does not return a value.Workaround: This object is not supported by the LightStream 1010 or Catalyst 8500 platforms.
•
Symptom: On a PNNI signalling link, the Promina 4000 NET switch sends a message that prompts the system to send a CALL PROCEEDING message and then a RELEASE message. The UNI 3.0 specification, section 5.4.5.15, defines a cause code 8a as "VPCI/VCI unacceptable." When the call goes out on a UNI 3.1 interface, this cause code should be mapped to VPI/VCI assignment failure. This mapping does not occur for PNNI links.
Workaround: None.
•
Symptom: EIGRP updates are missing for some addresses on ATM router module port subinterfaces.
Workaround: In global configuration mode, enter the no auto-summary command followed by the auto-summary command.
•
Symptom: A problem in the reinitialization logic might cause the system to fail unexpectedly when a switch processor module in slot 5 is the standby and the switch processor module in slot 7 fails.
Workaround: Do not configure the switch processor in slot 5 as the standby.
•
Symptom: When the system is configured to autoboot, and the configuration register is set to 0x2102, the secondary route processor crashes during autoboot.
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
•
Symptom: Incorrect MAC address entries in the CAM table might cause HSRP to fail over a BVI interface.
Workaround: None.
•
Symptom: The following messages may appear on the console. They are not reproducible.
15:28:43: %LANE-3-LEC_CONTROL_MSG: Received bad control message on interface ATM11/0/0.14Cant find ARM bound VC, port = 102, vci=0The message appears on subinterface ATM11/0/0.14 on the ATM router module port.
Workaround: None.
•
Symptom: The device might lose its IP OSPF neighbor information and connections over a BVI interface after a few days of running, requiring a system reboot.
Workaround: None.
•
Symptom: IP prefix entries in the CAM table might point to incorrect adjacency information, causing routing failure.
Workaround: None.
•
Symptom: The CES ABCD bits are not user configurable when a fault occurs.
Workaround: None.
•
Symptom: When forwarding a call setup message from one VP tunnel to another, the Catalyst 8540 might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.
Workaround: None.
•
Symptom: Configuring a channelized E1 (CE1) Frame Relay 2.048-Mbps ATM port adapter for clear E1 might cause the linecode violation and LES counters to increment continually.
Workaround: None.
•
Symptom: The device might lose IPX connectivity over a BVI interface, requiring the use of the clear ipx route* command to reestablish connectivity.
Workaround: None.
•
Symptom: The command show atm resources shows that the number of cells in the UBR queue in an MSC increases continuously but slowly.This happens when traffic is sent through a Catalyst 8540 MSR at close to line rate.
Workaround: None.
•
Symptom: After executing an IPX ping with a timeout value of zero, subsequent IPX pings on the device will fail.
Workaround: None.
•
Symptom: When an FEC is configured as a part of a bridge group and a topology change occurs, the bridge table might get out of sync with the Layer 2 CAM information.
Workaround: Use the clear bridge command to keep the IOS bridge table and the Layer 2 CAM in sync.
•
Symptom: atmfAtmLayerConfiguredVCCs might not include the soft PVC count.
If a router connects to an ATM interface on a Catalyst 8540 where soft PVCs are configured, the PVC Discovery feature on the router fails to correctly discover all the configured PVCs and soft PVCs from the switch router. This does not happen if only PVCs are configured.
Workaround: None.
•
Symptom: A fully loaded Catalyst 8540 CSR with 2-port Gigabit Ethernet modules boots properly from bootflash and slot, but does not boot from tftp.
Workaround: None.
•
Symptom: Marker cells are not drained after entering the shutdown/no shutdown command on the interfaces.
Under stress conditions, if there are several hierarchical VP tunnels configured and if the tunnel interfaces are transitioned several times, cells might stay in the switch fabric.
This does not occur on interfaces without hierarchical VP tunnels.
Workaround: None.
•
Symptom: If you configure BVI, but do not want to do IP routing at the BVI level, and you have IP addresses for the interfaces in the bridge group, then routing protocols might not work.
Workaround: Remove the interfaces from the bridge group and then add them back into the bridge group.
•
Symptom: When a large number of bridge groups or bridge group members are configured and IRB is enabled on the devices, reloading one of the devices or configurations might lead to high route processor utilization. The side effect of this is temporary spanning-tree loops, leading to AAL5 buffer exhaustion problems.
Workaround: In this case, if IRB is enabled, you might need to increase the number of buffers on the device using the aal5 buffers command.
•
Symptom: During route processor switchover, LMI times out on peer interfaces.
The Catalyst 8540 requires about a minute to switch over. The Frame Relay interface might take about a minute before it can respond to any LMI activity.
Workaround: To prevent LMI timeouts on peer interfaces during switchover, configure an LMI timeout longer than the time it takes for the Catalyst 8540 route processor to switch over. Configure lmi-n392dce, lmi-n392dte, lmi-t392dce and lmi-n391dte on the Frame Relay interface so that LMI will not bring down the interface if no LMI activity is seen for about a minute.
•
Symptom: After entering the show running-config command several times, the Catalyst 8540 might fail unexpectedly due to a bus error.
Workaround: None.
•
Symptom: The file system fails to add the secondary NVRAM and secondary RCSF on a route processor switchover.
Workaround: None.
•
Symptom: No means to change the default active switch processor modules is available.
Workaround: If a Catalyst 8540 has three switch processor modules, by default the switch processor modules in slots 5 and 7 come up as the active switch processor modules and the switch processor module in slot 6 comes up as the standby. To change this default, use the following privileged EXEC command:
redundancy preferred-switch-card-slot slot#1 slot#2
Two preferred slots must be specified and they must be unique. The range of the slot value is 5 to 7. If one of the preferred slots selected is not a currently active switch processor module, you are asked whether the system should change the active switch processor module to the preferred switch processor module. If such a switchover occurs, all the active connections in the system are reinitialized. If you wish to continue, then the preferred switch processor modules become active and the other switch processor module becomes the standby. This configuration remains in effect until one of the active switch processor modules is removed. The preferred switch processor module configuration is preserved across route processor switchovers. However, the preferred switch processor module setting is lost if the system is power cycled or if both route processors are reloaded to ROM monitor mode.
•
Symptom: Setting the gateway of last resort is delayed on route processor switchover.
The static IP routes take from 1.5 to 2 minutes to take effect on switchover.
Workaround: None.
•
Symptom: The primary route processor should not be hot swapped.
If a route processor that is currently running IOS is removed from the chassis in a skewed manner, such that the left side of the route processor comes out before the right side does, the traffic through the switch router might stop.
Workaround: There are some precautions to take before removing a route processor module controller from a chassis that is powered-up.
If the route processor module is currently in ROM monitor mode, then it is safe to remove it from the chassis. You can put the route processor in ROM monitor mode from IOS by issuing a reload command if the switch router is not configured to automatically boot. If the switch router is configured to automatically boot, it starts booting IOS again. To ensure that the route processor is in ROM monitor mode before removing it, use the following command:
redundancy prepare-for-cpu-removal
Execute this command on the route processor before removing it. Once this command is entered, the route processor goes to ROM monitor mode and stays there even if the system is configured to automatically boot. At this point, it is safe to remove the route processor from the system.
Enter this command after connecting to the console port of the route processor. If the system has a Y cable, then remove the Y cable and obtain a local connection to the route processor before the command is entered. Enter the command only on a route processor that is in IOS mode, even if it is the secondary route processor.
•
Symptom: Changing the MAC address for a bridge group member causes route processor bound packets on that interface to be discarded. For a port channel, the problem occurs when the first member is removed from the port channel.
Workaround: When an interface's MAC address is changed, remove the interface from its bridge group and then add it back into the bridge group.
•
Symptom: Srecord integrity checking is not adequate.
If all the Srecord lines are removed from a functional image file, the file is corrupted and causes problems if downloaded. The reprogram command Srecord integrity checking does not catch this problem.
Workaround: None.
•
Symptom: Incorrect coding of the information element "call state."
Information element "call state" incorrectly sets the coding standard to 00 (ITU-T coding standard) instead of 11 as specified in the PNNI specification. This can cause compatibility problems with other vendors' implementations.
Workaround: None.
•
Symptom: On the Catalyst 8540 MSR it is not possible to use a VCI value higher than 8191 for soft VCs and PVCs on the same interface module or port adapter where more than one VCI is configured.
Workaround: Use VCI values lower than 8192.
•
Symptom: The advertised priority is not updated for PGLs configured to match the advertised priority.
Workaround: None.
•
Symptom: The show controller command only displays information for even-numbered ports.
The show controller command for all odd-numbered ports in a 16-port OC-3c interface module displays the information for even-numbered ports.
Workaround: None.
•
Symptom: When a peer switch with UPLINK FAST enabled is connected to a Catalyst 8500 bridge group interface, the virtual MAC address of HSRP for an ACTIVE device in one of the member interfaces of the bridge group is programmed as a REMOTE entry.
Workaround: Use the clear bridge command to update the CAM table.
•
Symptom: Adjacencies are removed when a bridge table entry ages out. This causes traffic to be routed to the route processor, which might lead to high route processor utilization.
Workaround: Set the ARP timeout value to be less than the bridge age timer.
•
Symptom: When the fiber port is shut, level 1 does not have a mechanism for disabling the transmit signal. Disabling the fiber mode causes the level 1 chip to cut itself from the optical transceiver, which puts the transceiver in a floating state. The remote connection might pick up the bad signal sent by the transceiver as a good one and declare itself as up. The randomness of this signal causes flapping. This is evident when the fiber ports are connected between the following systems:
–
–
–
Workaround: Change the hardware to send a constant signal (idle) when the port is shut.
•
Symptom: With 16 or more subinterfaces on a port channel, the following configuration might cause CPUHOG messages to appear:
[no] ip routing[no] ipx routing[no] bridge irb[no] bridge-g [bridge-group-no]Workaround: No workaround is needed; the route processor HOG messages should not affect the functionality of the device.
•
Symptom: The rate scheduler allocation (rsAlloc) update is accurately based on granularity of the mantissa value and might lead to oversubscription.
During the CAC process, for pure or partial rate scheduled connections, the rate actually programmed in the hardware might exceed the rate requested. This is particularly visible at very high rates, and is due to the granularity in the mantissa value (which cannot be fractional). However, the CAC allocates in its software structures only the rate requested. This might lead to an oversubscription of the rate scheduler.
This problem occurs at very high VC rates, where the CAC algorithm allocates slightly less than what the rate scheduler is programmed with (the difference is less than 0.03%).
Workaround: None.
•
Symptom: Failed attempts to reprogram a carrier module cause the Catalyst 8540 to hang.
Workaround: None.
•
Symptom: The switch router rejects calls with extended QoS parameters.
When ATM QoS for CDV is configured and you specify a soft VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft VC does not come up.
Workaround: None.
•
Symptom: The show hardware command does not display power supply IDPROM details.
Workaround: None.
•
Symptom: Under certain conditions, some Gigabit Ethernet interface module ports will not come up.
Workaround: If you observe this problem, you might need to upgrade your 10/100BASE-T interface module firmware. Contact your Cisco service representative for more information.
•
Symptom: The lane server-bus ethernet command might cause an unexpected exception when entered after deleting LANE clients from the subinterface.
Workaround: None.
•
Symptom: Under extreme low memory conditions, if a switch is configured with lots of hierarchical tunnels and LANE components are configured on the cpu port of the switch (or ATM interface of a router), removing a few subinterfaces or many several times can result in a crash. This removal without first cleaning up LANE configuration results in the loss of 6400 bytes of memory.
Workaround: Delete LANE configuration on a subinterface before deleting the subinterface itself.
•
Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).
Workaround: None.
•
Symptom: The switch router rate scheduler rounds down the rates (when converting from bits per second to cells per second) when they should be rounded up.
Workaround: None.
•
Symptom: When a call setup message traverses a switch router running PNNI on the ingress side and IISP (version 3.0 or 3.1) on the egress side, the message might be corrupted.
Workaround: None.
•
Symptom: The Catalyst 8540 uses backward parameters in QoS information elements for point-to-multipoint calls.
This might cause incompatibility with other vendors' implementations.
Workaround: None.
•
%IPX-3-BADINSERT: Duplicate SAP entry insert attempted.Symptom: The switch router returns a %IPX-3-BADINSERT message when a duplicate SAP entry is made.
Workaround: None.
•
Symptom: High route processor utilization if multicast traffic is high. When PIM protocol is configured, non-RPF multicast traffic is forwarded to the route processor.
Workaround: None.
•
Symptom: Cell loss occurs between unlike bandwidth interfaces, such as DS3 or T1 and OC-3c, that reside on the same carrier module which has functional image version 1.4 or earlier.
Workaround: Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.
•
Symptom: The switch router might detect discrepancies between the software configuration and the hardware after a route processor switchover.
Across a route processor switchover, if an outdated (older than and different from the running configuration) start-up configuration synchronization is applied, or if the latest running configuration synchronization fails, then discrepancies might exist between software data structures and hardware programming. Any PVCs are preserved.
Workaround: Use the copy running-config startup-config command before a route processor switchover.
•
Symptom: Circuit emulation service (CES) might show an interface as UP following a loss of signal (LOS). Also, if the interface is shut down or the uplink ATM is not functioning, CES might fail to send an alarm indication signal (AIS).
Workaround: None.
•
Symptom: Messages appear when hot swapping a carrier module.
When you hot swap a carrier module into the Catalyst 8540 chassis, traceback messages such as the following appear on the console of the secondary route processor. These messages are harmless and can be ignored:
IDPROM in slot 10 not properly programmedIDPROM in slot 12 not properly programmed01:01:55: %SCHED-2-WATCH: Attempt to lock uninitialized watched semaphore (address0).Workaround: None.
•
Symptom: When deleting the secondary route processor's start-up configuration, a CPUHOG message appears on the secondary route processor.
The delete command only removes files.
Workaround: Use the erase command to delete devices instead of the delete command.
•
Symptom: Due to a bad VCXO, a packet might delay on the switch router indefinitely, causing a software crash.
Workaround: None.
•
Symptom: CES port LEDs on the Catalyst 8540 are inconsistent with those of the LightStream 1010 ATM switch.
The Catalyst 8540 has an LED status configuration that is inconsistent with that of the LightStream 1010 ATM switch on CBR ports. When nothing is connected to the CBR port, the LED status on the LightStream 1010 ATM switch is as follows:
S1=red; S2=red; CD=off
When nothing is connected to the CBR port, the LED status on the Catalyst 8540 is:
S1=red; S2=red; CD=green
Workaround: None.
•
Symptom: AAL5 CRC errors are not accounted for at the physical interface.
The show atm interface command does not display CRC errors seen at the physical interface level. These errors are not logged under AAL5 CRC.
Workaround: None.
•
Symptom: When downloading an IOS image to the slot 0 Flash memory card on the Catalyst 8510 CSR by way of SNMP, the copy operation fails with a "copyUnknownFailure" message, and the formatting information on the Flash memory card is lost.
Workaround: When downloading an IOS image by way of SNMP, such as with the SWIM (Software Image Management) application of CiscoWorks2000, always use slot 1 instead of slot 0 as the target location of the IOS image.
•
Symptom: Some tx per-vc counters on both point-to-point and point-to-multipoint connections miscount cells. The cells are transmitted but not counted. The number of missed cells is small relative to the total number of cells counted is approximately 1% in the worst case.
Workaround: Upgrade the switch router feature card FPGA image to release fi-c8540-fc.A.4-17 or later.
•
Symptom: When you hot swap any interface module with an OC-12c interface module, the correct configuration for the OC-12c interface module in the port mode table does not come up properly.
Workaround: Upgrade the switch router feature card FPGA image to release fi-c8540-fc.A.4-17 or later.
•
Symptom: In the output of the show atm vc command, all of the packet counters are incorrectly displayed as zero.
Workaround: None.
•
Symptom: A crash might occur while removing subinterfaces using the no interface command.
When an active VP tunnel subinterface is deleted, a software crash might occur.
Workaround: Shut down the subinterface before deleting it.
•
Symptom: A software crash might occur on the switch router running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is
pnni_link_av.Workaround: None.
•
Symptom: Online insertion and removal of port adapter modules can result in a bus error.
Workaround: Avoid the online insertion and removal of port adapter modules.
•
Symptom: Occasionally, the show controllers interface-name command can bring down an interface and the line protocol. The condition that leads to this scenario is random and very infrequent. The end result is that routing/bridging stops on this interface.
Workaround: None.
•
Symptom: OIR INSCARD messages display during boot.
Workaround: None.
•
Symptom: The Frame Relay port adapter firmware might report CRC errors on a PVC if it receives traffic using the same VPI/VCI/DLCI while the PVC is configured.
The errors only occur while the firmware is still configuring the VC. Once the PVC is configured, the CRC errors stop. Since the frames appear like zero-length AAL5 packets while the firmware is still configuring the VC, the firmware does not increment the discard bytes counter, but does increment the discard frames counter due to the CRC errors.
Workaround: Do not allow traffic to pass on the VC while it is being configured.
•
Symptom: While toggling the interfaces on the peer switch (the LightStream 1010 ATM switch), the following error message is occasionally displayed on the Catalyst 8540:
04:09:08: process_cubi_cell_list: cubi_oam_upcall returned an errorThis occurs when a LECS is configured on the route processor port along with 10 LES/BUS/LECs on the 10 subinterfaces on the route processor port.
Workaround: None.
•
Symptom: Unpredictable results might occur if the route processor scheduler allocation is changed in the configuration file.
Workaround: Remove the scheduler allocate command from the configuration file. We recommend that you do not change the default values for this command.
•
Route processor HOG message appears when activating OSPF on a large port channel configuration.
Symptom: A route processor HOG message appears when OSPF is activated on a port channel interface with more than 30 subinterfaces.
Workaround: The operation succeeds even if this message appears. No action is necessary.
•
Symptom: Point-to-multipoint PVC preservation across a route processor switchover is not fully supported.
If traffic is flowing through a point-to-multipoint connection when a route processor switchover takes place, then some of the leaves of the connection might not be restored properly. Traffic might continue to flow through all the leaves of the connection even after the switchover, but the output of the show atm vc command might show NO HW RESOURCE for some of the leaves of the connection. In the absence of traffic, all the leaves of a point-to-multipoint connection will be restored properly across a route processor switchover.
Workaround: If possible, shut down traffic on all point-to-multipoint connections before a route processor switchover.
•
Symptom: When running tag switching, no tag is created for the default route.
Workaround: None.
•
Symptom: The sysConfigName MIB variable value is not set correctly.
If the system is set to autoboot and no explicit boot image is specified, the system boots the default image from the bootflash. In this scenario, the show version command displays the image name as "default image" instead of the actual image name. The MIB variable sysConfigName also returns an empty value.
Workaround: None.
•
Symptom: Soft VPs and PVPs cannot coexist due to VPI allocation errors.
When creating soft VPs, the VPI value allocated on the switched part of the soft VP path might collide with existing configured PVPs.
Workaround: There are two ways to get the soft VP up:
–
–
•
Symptom: PNNI does not correctly clean up and release some of its data structures after process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is unavailable until the next reload.
Workaround: None.
•
Symptom: The PNNI SNMP agent is not able to discover and allow PNNI-related configurations on ATM subinterfaces.
An alignment error message is printed when an SNMP walk (or other SNMP get next) request is entered.
Workaround: None.
•
Symptom: Connections might fail when the connect message includes an end-to-end delay IE. A Catalyst 8540 that is an intermediate switch router passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
Examples of these connections include UNI 4.0, CBR, and VBR-rt.
Workaround: None.
•
Symptom: Reprogramming a network clock module causes a processor reset.
Reprogramming the network clock module on the primary route processor causes the route processor to reload after the download is complete. Power cycle the switch router to make the newly loaded image active.
Workaround: None.
•
Symptom: Reprogramming a carrier module might cause the Catalyst 8540 to hang and not reboot.
After successfully reprogramming a revision 4.0 carrier module with FPGA 1.4, the Catalyst 8540 might hang. To recover the switch router, remove the carrier module before rebooting.
Workaround: None.
•
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
Workaround: None.
•
Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.
Workaround: None.
•
Symptom: On a Catalyst 8540 system configured with 32 MB of RAM, IPC traffic between the port adapter driver and the firmware can experience a transient failure when the port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if it is reset after waiting for about 2 minutes.
This IPC failure, which is due to an unexpected firmware crash under a heavy load, does not occur on a Catalyst 8540 system configured with 64 MB of RAM.
Workaround: None.
•
Symptom: Tag switching and Tag Discovery Protocol (TDP) might cause memory fragmentation.
While running tag switching with a very large number of destinations, continuous toggling of VC merge (which forces all the TDP sessions to restart) on the switch router for a period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
•
Symptom: When loading a software version 11.3 or later image on a switch router with 11.2 or earlier image, LECs and other LANE components might fail to come up if they are configured using an ATM address whose first 19 bytes are the same as the active ATM address of the switch router.
The ATM address of the switch router along with the first 128 values for its selector byte should be reserved for use by PNNI. Starting with the 11.3 software version, PNNI supports hierarchy and registers an ATM address for all PNNI nodes using the switch router ATM address with various selector byte values.
Workaround: If LANE components fail to come up because their ATM addresses collide with the reserved ATM addresses for PNNI, reconfigure the LANE components using different addresses. It is recommended that LANE applications use the addresses shown by the show lane default-atm-addresses command, which will eliminate this problem.
•
Symptom: ADD party requests over a VP tunnel do not work.
On a source node, when adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
•
Symptom: An unnecessary lookup for a network configuration file occurs after a route processor switchover.
When a route processor switchover occurs, the new primary route processor that is taking over might look for configuration files from a network server that might not exist. These network configuration file lookups will timeout. This causes some delay during the switchover process.
Workaround: None.
•
Symptom: Snooping error:
%ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfoWhen snoop-VC is configured on a port, the switch router returns this internal error message:
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptrIgnore this message; it does not affect the snooping functionality.
Workaround: None.
•
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phyloThis error message appears because the tunnel specified in the command has been deleted and the structures pertaining to that tunnel have been released.
Workaround: None.
•
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface might become overwhelmed and start generating the following error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufsThe interface stops sending data and the transmitter remains stuck.
Workaround: Enter a shutdown/no shutdown command sequence on the interface.
•
Symptom: When ATM accounting is enabled, an exception might occur because resources at the destination switch router are not available.
Workaround: None.
•
Symptom: Another vendor's router running UNI 4.0 cannot connect a VC to a Cisco router running UNI 3.1 by way of a Catalyst 8540.
Workaround: None.
•
Symptom: Funnel VCs can jeopardize quality of service (QoS) for guaranteed services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel VC simultaneously, the rate scheduler on the output interface would oversubscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MaxCR) guarantees for other VCs on the interface.
Workaround: None.
•
Symptom: When you set the ROM monitor environment variable to boot a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch router hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch router and send a break character to the switch router within 60 seconds to force it to the ROM monitor prompt. You can then manually reboot the switch router and reconfigure the environment variable.
•
Symptom: The granularity provided by the switch processor scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmission to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: None.
•
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
•
Symptom: Open Shortest Path First (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not switch to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch router for the interface that was shut, or a clear ip route command on all the switch routers to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch router that had the closed physical interface.
•
Symptom: The switch router issues CPU hog messages while setting up many calls.
With a large number of connections installed, a show atm vc command may take longer than 2 seconds to complete. This produces a
%SYS-3-CPUHOGerror message from the scheduler.Workaround: If information about a specific VC is desired, to specify the interface and the VPI/VCI needed, use the show atm vc interface command card/subcard/port vpi vci
•
Symptom: The ATM switch router does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
•
Symptom: If there are multiple parallel paths to the same destination on the ATM switch router with a switch processor feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merged and go out of the switch router as a single VC.
Workaround: None.
•
Symptom: The Catalyst 8540 Ethernet connection does not receive CDP multicast packets. However, the Catalyst 8540 does send out CDP multicast packets.
Workaround: None.
•
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Workaround: None.
•
Symptom: SNMP SET to a CES port causes the switch router to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES port adapter, the switch router stops working.
Workaround: None.
•
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels.
The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (through portSelTable) is not possible until the interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
•
Symptom: The CDP configuration for a LEC cannot be saved to NVRAM.
When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM and does not appear in the show running-config command display. CDP is disabled, but the setting reverts to enabled after a reload.
Workaround: None.
•
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on the NNI interfaces because of switch router crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the Portselgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
•
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch router with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
–
–
Workaround: None.
•
Symptom: A LECS expects all LESs to establish an individual control VC to the LECS to validate clients.
If different emulated LANs (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages which validates the clients into a single VC.
For example, see the following LES router configuration:
atm1/0.1 sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LANatm1/0.2 sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LANatm1/0.3 sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LANatm1/0.4 sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LANThis configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan'sysa_70k_31_a1.1_LAN'%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan'sysa_70k_31_a1.2_LAN'%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan'sysa_70k_31_a1.3_LAN'The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
•
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOGThis message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch router.
Workaround: None.
•
Symptom: Remote defect identification (RDI) cells (sent by an endpoint in response to alarm indication signal [AIS] cells generated at an intermediate switch router with a fault condition on an interface) are not propagated beyond the intermediate switch router. The intermediate switch router removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch router.
Workaround: None.
Restrictions
This section describes the following Catalyst 8500 MSR restrictions:
•
•
•
•
•
•
•
•
•
ACL Daughter Card Restrictions
Catalyst 8540 MSR
The following restrictions apply to the ACL daughter card supported on the Catalyst 8540 MSR:
•
•
•
–
–
–
–
–
Catalyst 8540 CSR
The following restrictions apply to the ACL daughter card supported on the Catalyst 8540 CSR:
•
•
•
–
–
–
–
–
AppleTalk Restrictions
We recommend that you evaluate the level of CPU utilization and performance in your switch router before turning on AppleTalk. Unlike IP and IPX, AppleTalk routing and processing in the Catalyst 8540 is accomplished by the switch processor, not the interface module. This means that routing AppleTalk packets consumes more processing time than routing other protocol packets. In a switch with a sustained high CPU utilization, turning on AppleTalk could result in longer convergence times for routing protocols like EIGRP. AppleTalk packet throughput is dependent on the amount of available CPU processing power.
ATM Router Module Restrictions
The Catalyst 8540 MSR ATM router module does not support the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
VLAN Encapsulation Restrictions
The four adjacent ports (such as 0-3 or 4-7) on a 10/100 Fast Ethernet interface must all use the same VLAN encapsulation, that is, either 802.1Q and native, or ISL and native.
EtherChannel Restrictions
When assigning Ethernet interfaces to an EtherChannel, all interfaces must be either Fast Ethernet or Gigabit Ethernet. You cannot mix Fast Ethernet and Gigabit Ethernet interfaces within a single EtherChannel.
Maximum Path Restriction for EIGRP or OSPF
Catalyst 8540 interface modules support a maximum of 2 paths. To improve EIGRP or OSPF convergence, set the maximum-paths for the router to 2, using the following command:
8540(config)# router eigrp 1098540(config-router)# maximum-paths 2Port Snooping Restrictions
•
•
•
•
Eight-Port Gigabit Ethernet Restrictions (Catalyst 8540 CSR)
The eight-port Gigabit Ethernet interface module is supported on the Catalyst 8540 CSR only. This section describes limitations of the eight-port Gigabit Ethernet interface module.
Ports Per Bridge Group Restrictions
The eight-port Gigabit Ethernet interface module installed in a Catalyst 8540 CSR can support a maximum of 128 ports per bridge group.
Port Channel Restrictions
If your Catalyst 8540 CSR has an eight-port Gigabit Ethernet interface module, you cannot create a port channel that has some members on that module and others on other modules. All port channel members must reside on the same Gigabit Ethernet interface module.
Also, if your switch router has an eight-port Gigabit Ethernet interface module, port channel IDs 57 to 64 are reserved, and cannot be assigned to other external interfaces. If you assign a port channel ID number greater than 56, the system will respond with the following message:
Port channel with ID > 56 cannot be created.If you have already assigned port channel IDs 57 to 64, you must reassign them before installing an eight-port Gigabit Ethernet interface module.
If your switch router does not have an eight-port Gigabit Ethernet interface module, you can assign port channel ID numbers up to 64.
Online Insertion and Removal of Interface Modules Restrictions
The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of interface modules on the Catalyst 8500 CSR:
•
•
•
Online Diagnostics Restrictions
Online diagnostics, such as access tests, online insertion and removal (OIR) tests, and snake tests, detect and report hardware failures in the Catalyst 8540 during system bootup and operation. The following restrictions apply to the OIR (also known as hot swapping) tests and the snake tests on the Catalyst 8500 CSR:
•
•
Note
FPGA Upgrade Restriction
On an 8540, the reprogram command for upgrading the FPGA on the switch processor requires power cycling the box after completing the FPGA download.
1000BASE-ZX GBIC Restriction
The Catalyst 8540 MSR switch routers support extra long haul (1000BASE-ZX) GBICs as follows:
•
•
Bridge-Group Virtual Interface Restriction
A Bridge-Group Virtual Interface (BVI) is a virtual interface within the campus switch router that acts like a normal routed interface. A BVI does not support bridging, but it actually represents the corresponding bridge group to routed interfaces within the switch router. The interface number is the link between the BVI and the bridge group.
Layer 3 switching software supports the routing of IP and IPX between routed interfaces and bridged interfaces in the same router, in both fast-switching and process-switching paths. BVIs do not support IP multicast routing.
Catalyst 8540 Route Processor and Switch Module Redundancy
The Catalyst 8540 CSR supports the use of redundant route processors and switch modules. The second route processor would be installed in slot 8, and an additional switch module would be installed in slot 6.
Route Processor
There are some precautions that need to be taken before removing a route processor module from a chassis that is powered-up. If a route processor module that is currently running IOS is removed from the chassis in a skewed manner such that the left side of the processor comes out before the right side does, the traffic flowing through the device might stop flowing.
To avoid this, make sure the route processor module that is being removed is currently at the ROM monitor prompt; it is then safe to remove it from the chassis. One way to get the system into ROM monitor from IOS is to issue a reload command. This will work if the system is not configured to auto-boot. If the system is configured to auto-boot, it starts booting IOS again.
Since you need to ensure that a route processor is in ROM monitor before removing it, the redundancy prepare-for-cpu-removal command has been added to take the system to the ROM monitor prompt. Execute this command on the route processor being removed before removing it. Once this command is issued, the route processor will go to the ROM monitor prompt and stay there even if the system is configured to auto-boot. At this point it is safe to remove the route processor from the system.
Switch Modules
If a Catalyst 8540 has three switch modules, then by default the switch modules in slots 5 and 7 come up as active, and the one in slot 6 comes up as the standby. If you wish to change this default, there is a command that lets you select the "preferred" switch module slots. This command is a privileged exec level command with the following format:
redundancy preferred-switch-card-slot slot#1 slot#2
Two unique preferred slots must be specified. The range of the slot value is 5 to 7. If one of the preferred slots is not a currently active switch module, you are informed of this and asked if the system should change the active switch modules to the preferred switch modules. If such a switch-over occurs, all the active connections in the system will be reinitialized. If you wish to continue, then the preferred switch modules become active, and the other switch module becomes the standby. This configuration will remain in effect until either one of the active switch modules is removed.
The preferred switch module configuration is preserved across route processor switch-overs. However, the preferred switch modules setting will be lost if the system is power-cycled or if both route processors are reloaded to the ROM monitor.
Autonegotiation (Catalyst 8540 CSR)
Beginning with Cisco IOS Release 12.0(5)W5(13) software, the autonegotiation feature for speed and duplex on 10/100BASE-T Ethernet ports defaults to "on." This means that for each port, the Catalyst 8540 CSR automatically detects the port speed (10 Mbps or 100 Mbps) and duplex of the peer port, if that port also autonegotiates.
To override autonegotiation and set a port to 10 Mbps operation, issue the following command:
(config-if)# speed 10To set a port to 100 Mbps operation, issue the following command:
(config-if)# speed 100To set the duplex value for a port to full-duplex, issue the following command:
(config-if)# duplex fullTo set the duplex value for a port to half-duplex, issue the following command:
(config-if)# duplex half
Caution
Incompatibility (Catalyst 8540 CSR)
When you connect a Catalyst 8540 CSR to a Catalyst 5000 100BASE-FX MM Ethernet interface module using ISL, ensure that the hardware version on the Catalyst 5000 interface module is 1.3 or higher. You might experience connectivity problems between the Catalyst 8540 CSR and the Catalyst 5000 if the hardware version on the Catalyst 5000 Ethernet interface module is lower than 1.3.
Interoperability
You can use Catalyst 8540 CSR interface modules in a Catalyst 8540 MSR chassis with an MSR route processor and switch modules. Use only CSR (Ethernet) interface modules, and load the CSR software image on the MSR.
Starting with the following software releases, hardware and software functionality interoperability exists between CSR interface modules and MSR interface modules by way of the ATM router module on the MSR chassis running an MSR image:
•
•
Y2K Compliance
Related Documentation
The following sections describe the documentation available for the Catalyst 8540. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules that are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.
The most up-to-date documentation can be found on the Web via Cisco.com and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.
These release notes should be used in conjunction with the documents listed in these sections:
Platform Documents
The following list includes the platform-specific documentation available for the Catalyst 8540:
•
•
•
Software Documents
The following list includes the software documentation available for the Catalyst 8540:
•
•
•
•
•
•
Service and Support
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
Note
For service and support for a product purchased directly from Cisco, use Cisco.com.
Software Configuration Tips on the Cisco TAC Home Page
For helpful tips on configuring Cisco products, follow this path on Cisco.com:
Service & Support: Technical Documents (button on left margin)
"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From areas outside the United States, call 650-556-8409.
The following sections are provided in the Documents Section of the TAC Web page:
•
•
•
•
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0411R)
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
Posted: Fri Mar 25 04:09:30 PST 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
