Table of Contents

Contents
Introduction
System Requirements

Memory Requirements
Minimum Flash Memory Requirements
Hardware Supported
Determining Your Software Release
Other Firmware Code
Feature Set Tables
Release Names, Versions, and Part Numbers

New and Changed Information

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(7a)

Caveats

Cisco IOS Release 12.0(4a)W5(11a) Caveats Corrected
Cisco IOS Release 12.0(4a)W5(11a) Caveats
Cisco IOS Release 12.0(1a)W5(9) Caveats Corrected
Cisco IOS Release 12.0(1a)W5(9) Caveats
Cisco IOS Release 12.0(1a)W5(7b) Caveats Corrected
Cisco IOS Release 12.0(1a)W5(7b) Caveats
Cisco IOS Release 12.0(1a)W5(7a) Caveats

Related Documentation

Platform Documents
Software Documents

Service and Support

Software Configuration Tips on the Cisco TAC Home Page

Cisco Connection Online
Documentation CD-ROM

Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(4a)W5(11a)

March 14, 2000

Catalyst 8540 MSR Cisco IOS Release 12.0(4a)W5(11a)

This document describes the features and caveats for Cisco IOS Release 12.0(4a)W5(11a) software for the Catalyst 8540 multiservice ATM switch router (MSR).

For a list of caveats that apply to Cisco IOS Release 12.0(4a)W5(11a) software, refer to the "Caveats" section.

Contents

This document includes the following sections:

• Introduction

• System Requirements

• New and Changed Information

• Caveats

• Related Documentation

• Service and Support

• Cisco Connection Online

• Documentation CD-ROM

Introduction

The Catalyst 8540 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 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.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.0(4a)W5(11a) and includes the following sections:

• Memory Requirements

• Minimum Flash Memory Requirements

• Hardware Supported

• Determining Your Software Release

• Other Firmware Code

• Feature Set Tables

• Release Names, Versions, and Part Numbers

Memory Requirements

The DRAM memory configuration is 256 MB, which is the default for the Catalyst 8540 MSR.

Minimum Flash Memory Requirements

Cisco IOS software release 12.0(4a)W5(11a) and later releases require a minimum of 16-MB of contiguous boot Flash memory. The Catalyst 8540 MSR route processor now ships by default with a 16-MB boot Flash SIMM.

Earlier releases of the Catalyst 8540 MSR ATM 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:

• 73-2644-06 Rev. A0 for the Catalyst 8540 MSR

• 73-3775-03 Rev. A0 for the Catalyst 8540 CSR

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:

• Option 1---If you already have a Flash PC card, download the system image to the Flash PC card.

---

Note If you have a Smart Modular, Sharp, or Intel 2+ Flash PC card that was formatted using a Cisco IOS software release other than 12.0(4a)W5(11a), reformat it with release 12.0(4a)W5(11a) prior to downloading the image (You might need to boot the image from a TFTP server to format the PC Flash card). Do not erase the system image on the boot Flash SIMM. If the procedure fails, you will need it to recover. (See caveat CSCdm47012 later in these release notes for more information.)

---

Then do the following:

• Enter the config-register 0x2102 global configuration command to change the configuration register to boot from the Flash PC card, instead of the system-code SIMM (default).

• Enter the boot system slot0:filename global configuration command to specify the system image to boot on the Flash PC card.

• Enter the copy system:running-config nvram:startup-config privileged EXEC command to save the configuration changes to NVRAM.

An example follows:

Switch(config)# config-register 0x2102
EHSA:Syncing confreg: 256 to secondary
Switch(config)# boot system slot0:cat8540m-wp-mz.120-4a.W5.11a
Switch(config)# end 
Switch# copy running-config startup-config

• Option 2---Download the system image to a TFTP server and boot the system image from the TFTP server. Enter the boot system tftp filename ip-address global configuration command to boot the system image from the TFTP server, instead of the system-code SIMM (default).

An example follows:

Switch(config)# boot system tftp cat8540m-wp-mz.120-4a.W5.11a 172.20.52.3

---

Note You can boot only the primary route processor from a TFTP server, not the secondary.

---

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 lists the hardware modules supported by the Catalyst 8540 MSR and Cisco IOS Release 12.0(4a)W5(11a) software, and their minimum software release requirements.

Table 1: Supported Hardware Modules and Their Minimum Software Requirements

Part Number	Description	Minimum Software Requirement
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-4SM	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-1SM	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+4xOC-12 MMF	S854R2-12.0.4W
C85MS-1F4S-OC48SS	1-port OC-48c SMF-IR+4xOC-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 (CSR) 8-port Gigabit Ethernet 64K line module	S854R2-12.0.4W
C85GE-2X-16K	C8540 (CSR) 2-port Gigabit Ethernet 16K line module	S854R2-12.0.4W
C85GE-2X-64K	C8540 (CSR) 2-port Gigabit Ethernet 64K line module	S854R2-12.0.4W
C85GE-2XACL-16K	C8540 (CSR) 2-port Gigabit Ethernet 16K with ACL line module	S854R2-12.0.4W
C85GE-2XACL-64K	C8540 (CSR) 2-port Gigabit Ethernet 64K with ACL line module	S854R2-12.0.4W
C85FE-16T-16K	C8540 (CSR) 16-port 10/100 UTP 16K interface module	S854R2-12.0.4W
C85FE-16T-64K	C8540 (CSR) 16-port 10/100 UTP 64K interface module	S854R2-12.0.4W
C85FE-16TACL-16K	C8540 (CSR) 16-port 10/100 UTP 16K with ACL interface module	S854R2-12.0.4W
C85FE-16TACL-64K	C8540 (CSR) 16-port 10/100 UTP 64K with ACL interface module	S854R2-12.0.4W
C85FE-16F-16K	C8540 (CSR) 16-port 100-FX-MT-RJ 16K interface module	S854R2-12.0.4W
C85FE-16F-64K	C8540 (CSR) 16-port 100-FX-MT-RJ 64K interface module	S854R2-12.0.4W
C85FE-16FACL-16K	C8540 (CSR) 16-port 100-FX-MT-RJ 16K with ACL interface module	S854R2-12.0.4W
C85FE-16FACL-64K	C8540 (CSR) 16-port 100-FX-MT-RJ 64K with ACL interface module	S854R2-12.0.4W

Determining Your Software Release

To determine the version of Cisco IOS software currently running on the Catalyst 8540 MSR, log into the switch and use the show version EXEC command. The following sample output is from the show version command. The version number is indicated on the second line as shown below:

Cisco Internetwork Operating System Software
IOS (tm) PNNI Software (cat8540m-WP-M), Version 12.0(4a)W5(11a)
 

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 MSR have upgradeable FPGA and functional images. The FPGA and functional images include caveat fixes, but in most cases, it is not necessary to upgrade. The release notes that describe the caveats from the FPGA and functional images are available on the World Wide Web at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/fpga_rel/index.htm

For information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8540 MSR)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide.

Feature Set Tables

The Cisco IOS 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. Table 2 lists the Cisco IOS software feature sets available for the Catalyst 8540 MSR.

Table 2: Feature Sets Supported by the Catalyst 8540 MSR

Feature Set	12.0(4a)W5(11a)	12.0(1a)W5(9)	12.0(1a)W5(7b)	12.0(1a)W5(7a)
Left-justified E.164 AFI support	x	x	x	x
SNMP1	x	x	x	x
Asynchronous support	x	x	x	x
PPP2 (SLIP3/PPP)	x	x	x	x
IP4	x	x	x	x
NTP5	x	x	x	x
TACACS+6	x	x	x	x
Telnet	x	x	x	x
Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8	x	x	x	x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI9 3.0)	x	x	x	x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)	x	x	x	x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)	x	x	x	x
Multipoint-to-point UNI signaling	x	x	x	x
Soft VCCs and VPCs	x	x	x	x
VP tunneling	x	x	x	x
VPI/VCI range support in ILMI 4.0	x	x	x	x
PNNI hierarchy	x	x	x	x
ILMI10 version 4.0	x	x	x	x
IISP11	x	x	x	x
LANE12 client (LEC13) and LANE services (LES14/BUS15/LECS16) on Route Processor	x	x	x	x
ATM ARP17 server on Route Processor	x	x	x	x
ATM ARP client on Route Processor	x	x	x	x
ATM tag switch router (TSR)	x	x	x	x
Port snooping	x	x	x	x
OAM18 F4 and F5	x	x	x	x
E.164 address translation	x	x	x	x
E.164 autoconversion	x	x	x	x
Circuit emulation	x	x	x	x
ATM access lists	x	x	x	x
ATM accounting	x	x	x	x
ATM RMON19	x	x	x	x
Multiple, weighted, dynamic thresholds for selective packet marking and discard	x	x	x	x
Shaped VP tunnels for CBR20 traffic	x	x	x	x
Substitution of other service categories in shaped VP tunnels	x	x	x	x
Dual leaky bucket policing	x	x	x	x
Scheduler/Service Class/PVC configuration	x	x	x	x
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC)	x	x	x	x
Network clocking enhancements for smooth switchover	x	x	x	x
Per-VC or per-VP nondisruptive snooping	x	x	x	x
Support for non-zero MCR21 on ABR22 connections	x	x	x	x
Access lists on ILMI registration	x	x	x	x
CUGs	x	x	x	x
ATM soft restart	x	x	x	x
ATM accounting enhancements	x	x	x	x
CISCO-SYSLOG-MIB support	x	x	x	x
CISCO-CONFIG-COPY-MIB support	x	x	x	x
Signaling diagnostics and MIB23	x	x	x	x
Supplemental AToM MIB	x	x	x	x
Hierarchical VP tunnels	x	x	x	x
Remote logging for accounting	x	x	x	x
Tag switching VC-merge on non-UBR24 VP tunnels and hierarchical VP tunnels	x	x	x	x
PNNI complex node representation	x	x	x	x
PNNI explicit paths	x	x
PNNI alternate link selection	x	x
Tag switching CoS	x	x
Network Clock Distribution Protocol	x	x
Simple Gateway Control Protocol	x	x
Switch redundancy	x	x
CPU redundancy: PVP/PVC/VP tunnel preservation	x	x
12-bit VPI	x	x
ATM Router Module	x
ATM overbooking	x
Framing overhead	x
ATM End System Address (AESA) gateway	x

1SNMP = Simple Network Management Protocol. 2PPP = Point-to-Point Protocol. 3SLIP = Serial Line Internet Protocol. 4IP = Internet Protocol. 5NTP = Network Time Protocol. 6TACACS+ = Terminal Access Controller Access Control System. 7VCCs = virtual channel connections. 8VPCs = virtual path connections. 9UNI = User-Network Interface 10ILMI = Integrated Local Management Interface 11IISP = Interim-Interswitch Signaling Protocol. 12LANE = LAN Emulation. 13LEC = LAN Emulation Client. 14LES = LAN Emulation Server. 15BUS = broadcast and unknown server. 16LECS = LAN Emulation Configuration Server. 17ARP = Address Resolution Protocol. 18OAM = Operation, Administration, and Maintenance. 19RMON = Remote Monitoring. 20CBR = constant bit rate 21MCR = minimum cell rate. 22ABR = available bit rate 23MIB = Management Information Base 24UBR = unspecified bit rate

Release Names, Versions, and Part Numbers

Table 3 lists the release names, versions, and part numbers used with the Catalyst 8540 MSR.

Table 3: Release Name to Version and Part Number Matrix

Release Name	Release Version	Part Number
W5-7	12.0(1a)W5(7b)	SRF-8540MSR5-7
W5-9	12.0(3c)W5(9)	SRF-8540MSR5-9
W5-11	12.0(4a)W5(11a)	S854R2-12.0.4W

New and Changed Information

This section lists new features that appear in this and previous releases of Cisco IOS Release 12.0(1a).

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

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

• 2-Port ATM Router Module interface module

---

Note For additional caveats that apply to this feature, refer to the Release Notes for the Catalyst 8500 Campus Switch Router, Cisco IOS Release 12.0. See the "Open Caveats" and "Caveats Corrected" sections for Release 12.0(4a)WX5(11a).

---

• Support for all Catalyst 8540 CSR interface modules

• OC-48c interface module

• ATM Oversubscription/Overbooking

• Framing Overhead

• AESA Gateway

See the "Related Documentation" section for a list of documents that describe these features.

New Features in Release 12.0(1a)W5(9)

The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(9):

• Redundancy and Enhanced High System Availability (ESHA)

• OC-12c MMF Interface Module

• OC-3c MMF Interface Module

• 12-bit VPI

• Network Clock Distribution Protocol (NCDP)

• Simple Gateway Control Protocol (SGCP)

• PNNI Link Selection

• PNNI Explicit Paths

• CDS3 and CE1 Frame Relay Port Adapter

• Tag Switching CoS

See the "Related Documentation" section for a list of documents that describe these features.

New Features in Release 12.0(1a)W5(7b)

There are no new features being added for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(7b).

New Features in Release 12.0(1a)W5(7a)

The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(7a):

• Hierarchical VP Tunnels

• Remote Logging for Accounting

• Tag Switching VC-Merge on Non-UBR VP Tunnels and Hierarchical VP Tunnels

• PNNI: Complex Node Representation

• OC-12 multimode fiber line module

See the "Related Documentation" section for a list of documents that describe these features.

Caveats

This section lists the corrected caveats and open caveats for each release. Use Table 4 to determine if a particular caveat applies to your software release, or if a particular caveat was corrected in your software release. These caveats are described in detail in the following sections:

• Cisco IOS Release 12.0(4a)W5(11a) Caveats Corrected

• Cisco IOS Release 12.0(4a)W5(11a) Caveats

• Cisco IOS Release 12.0(1a)W5(9) Caveats Corrected

• Cisco IOS Release 12.0(1a)W5(9) Caveats

• Cisco IOS Release 12.0(1a)W5(7b) Caveats Corrected

• Cisco IOS Release 12.0(1a)W5(7b) Caveats

• Cisco IOS Release 12.0(1a)W5(7a) Caveats

Table 4: Release Caveats and Caveats Corrected Reference  

DDTS Number	Software Release		Software Release		Software Release		Software Release
	12.0(4a)W5(11a)		12.0(1a)W5(9)		12.0(1a)W5(7b)		12.0(1a)W5(7a)
	Corrected	Caveat	Corrected	Caveat	Corrected	Caveat	Corrected	Caveat
CSCdi55937		x		x		x		x
CSCdi74229		x		x		x		x
CSCdi83275		x		x		x		x
CSCdi92142		x		x		x		x
CSCdj01016		x		x		x		x
CSCdj10889		x		x		x		x
CSCdj11070	x			x		x		x
CSCdj13565		x		x		x		x
CSCdj18430		x		x		x		x
CSCdj18583		x		x		x		x
CSCdj31762			x			x		x
CSCdj42967		x		x		x		x
CSCdj47998			x			x		x
CSCdj68412		x		x		x		x
CSCdj71109		x		x		x		x
CSCdj78305		x		x		x		x
CSCdj80396		x		x		x		x
CSCdj82930		x		x		x		x
CSCdj84344			x			x		x
CSCdj84379	x			x		x		x
CSCdj85853		x		x		x		x
CSCdk07378		x		x		x		x
CSCdk17977			x			x		x
CSCdk22484			x			x		x
CSCdk22791			x			x		x
CSCdk26482	x			x		x		x
CSCdk27725	x			x		x		x
CSCdk30912		x		x
CSCdk33601			x			x		x
CSCdk42052		x
CSCdk47516		x		x		x		x
CSCdk52436		x		x
CSCdk57536		x		x
CSCdk62547			x			x		x
CSCdk69639			x			x		x
CSCdk71268			x			x		x
CSCdk71688	x			x		x		x
CSCdk76280			x			x		x
CSCdk77032			x			x		x
CSCdk78469			x			x		x
CSCdk79426	x			x
CSCdk80021	x			x
CSCdk82708			x			x		x
CSCdk83334	x			x
CSCdk87118	x			x
CSCdk88859		x
CSCdk89079					x			x
CSCdk89501					x			x
CSCdk90091			x			x		x
CSCdk90147			x			x		x
CSCdk91364					x			x
CSCdk92661					x			x
CSCdk92832			x			x		x
CSCdm04013			x			x		x
CSCdm05084	x			x
CSCdm05738			x			x		x
CSCdm07703		x		x
CSCdm07857			x			x		x
CSCdm08234	x			x
CSCdm11864		x		x
CSCdm12694			x			x		x
CSCdm15900			x			x		x
CSCdm19018			x			x		x
CSCdm19073			x			x		x
CSCdm19670	x			x
CSCdm20257			x			x		x
CSCdm23212			x			x		x
CSCdm23579			x			x		x
CSCdm24192			x			x		x
CSCdm24385		x		x
CSCdm25175		x		x
CSCdm29365	x			x
CSCdm29503	x			x
CSCdm29529		x		x
CSCdm29650			x			x		x
CSCdm29939		x		x
CSCdm30009			x			x		x
CSCdm30023	x			x
CSCdm30269			x			x		x
CSCdm30294		x		x
CSCdm32506	x			x
CSCdm32678		x		x
CSCdm33737	x			x
CSCdm34634	x			x
CSCdm36745	x			x
CSCdm36790	x			x
CSCdm36800		x
CSCdm38218	x			x
CSCdm43664	x			x
CSCdm44167		x
CSCdm44079	x			x
CSCdm44497	x			x
CSCdm45453	x			x
CSCdm46430	x			x
CSCdm47012	x			x
CSCdm47048	x			x
CSCdm48886	x			x
CSCdm49429		x
CSCdm54001	x			x
CSCdm54297	x			x
CSCdm55248	x			x
CSCdm56393	x			x
CSCdm63047	x			x
CSCdm64544	x			x
CSCdm66516	x			x
CSCdm68761		x		x
CSCdm69065	x			x
CSCdm77667		x
CSCdm77987	x			x
CSCdm80628		x
CSCdm81581	x			x
CSCdm82033	x			x
CSCdm82878		x
CSCdm84365		x
CSCdm86667		x
CSCdm87797		x
CSCdm87966	x			x
CSCdm88183	x			x
CSCdm89205	x			x
CSCdm89519	x			x
CSCdm90166		x
CSCdm91042	x			x
CSCdm91060	x			x
CSCdm91571	x			x
CSCdm92183		x
CSCdm92990	x			x
CSCdm94019	x			x
CSCdp01016		x
CSCdp01936		x
CSCdp02661		x
CSCdp02816		x
CSCdp03092		x
CSCdp03166		x
CSCdp04109		x
CSCdp05103		x
CSCdp07226		x
CSCdp08242		x
CSCdp08255		x
CSCdp10310		x
CSCdp11944		x
CSCdp13836		x
CSCdp14860		x
CSCdp14997		x
CSCdp15945		x
CSCdp19060		x
CSCdp20608		x
CSCdp20865		x
CSCdp21758		x
CSCdp21879		x
CSCdp22516		x
CSCdp23208		x
CSCdp23213		x
CSCdp23923		x

Cisco IOS Release 12.0(4a)W5(11a) Caveats Corrected

• CSCdj11070

Symptom: CDP config cannot be saved to NVRAM for the LEC.

When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM (it also does not show up when doing a write term). The disabling does work, but you lose it again after a reload.

• CSCdj84379

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

• CSCdk26482

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 phylo

This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.

• CSCdk27725

Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo

When snoop-VC is configured on a port, the switch returns these internal error messages.

%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr

• CSCdk71688

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. The system needs to be power-cycled before the newly loaded image becomes active.

• CSCdk79426

Symptom: Soft VP and PVP 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 the existing configured PVP.

• CSCdk80021

Symptom: sysConfigName variable value 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.

• CSCdk83334

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 it is possible that some of the leaves of the connection will 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.

• CSCdk87118

Symptom: While toggling the interfaces on the peer switch (LightStream 1010 ATM switch), the following error messages is occasionally displayed on the Catalyst 8540 MSR:

04:09:08: process_cubi_cell_list: cubi_oam_upcall returned an error

This occurs when LECS is configured on the route processor port along with 10 LES/BUS/clients on the 10 subinterfaces on the route processor port.

• CSCdm05084

Symptom: CES port LEDs on the Catalyst 8540 MSR are inconsistent with the LightStream 1010 ATM switch.

The Catalyst 8540 MSR has inconsistent LED status with the LightStream 1010 ATM switch on CBR ports. When nothing is connected to the port LED, the status on the LightStream 1010 ATM switch will be:

S1=red; S2=red; CD=off;

When nothing is connected to the CBR port, the LED status on the Catalyst 8540 MSR will be:

S1=red; S2=red; CD=green;

• CSCdm08234

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

• CSCdm19670

Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).

• CSCdm29365

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-3 SPAM displays the information for even-numbered ports.

• CSCdm29503

Symptom: Advertised priority not updated for PGL if configured to match advertised priority.

• CSCdm30023

Symptom: Setting the gateway of last resort is delayed on switchover.

The static ip routes take from 1.5 to 2 minutes to take effect on switchover.

• CSCdm32506

Symptom: When issuing a show running-config command the Catalyst 8540 MSR might fail unexpectedly, due to a bus error.

• CSCdm33737

Symptom: Marker cells are not being drained after shutdown/no shutdown of 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 tunnels.

• CSCdm34634

Symptom: The soft pvc count might not be included in atmfAtmLayerConfiguredVCCs.

• CSCdm36745

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.

• CSCdm36790

Symptom: When forwarding a call setup from one VP tunnel to another, the Catalyst 8540 MSR might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.

• CSCdm38218

Symptom: If a show debugging command is issued on a Catalyst 8540 MSR that is configured as a PNNI "childless uncle," an infinite loop condition might occur that causes a watchdog timeout.

• CSCdm43664

• CSCdm54297

• CSCdm81581

SECONDARY CPU: *** Failure - Can not sync to other CPUs sync ****
Sys Clock lock and sync failed.

Cisco IOS Release 12.0(4a)W5(11a) Caveats

This section describes unsupported features and limitations, caveats, and potentially unexpected behavior by the Catalyst 8540 MSR for Cisco IOS Release 12.0(4a)W5(11a).

• With some OC-12 single-mode fiber line modules, the link fails to be present after the fiber cable has been inserted. Make sure that the fiber cables are completely seated by pushing on the strain reliefs of the individual fibers until they click into place to complete the optical connection. In some cases, the small metal septum on the transceiver front panel obstructs the connection.

• The maximum number of ELAN LES/BUS pairs supported is 10.

• The Catalyst 8540 MSR does not support Token Ring LANE.

• The ATM router module does not support Fast Simple Server Redundancy Protocol (FSSRP).

• CSCdi55937

Symptom: Remote defect identification (RDI) cells sent by an endpoint in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch 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.

Workaround: None.

• CSCdi74229

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-CPUHOG
 

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

Workaround: None.

• CSCdi83275

Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:

%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts 
 

In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.

Workaround: Toggle the interface to reinitialize all connections and restore normal operation.

• CSCdi92142

Symptom: A LAN Emulation Configuration Server (LECS) expects all LAN Emulation Servers (LESs) to establish an individual control VC to the LECS to validate clients.

If different emulated Local Area Networks (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validate 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_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
 

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

• CSCdj01016

Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:

• VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).

• ABR, UBR: no bandwidth is allocated.

Workaround: None.

• CSCdj10889

Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch 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.

• CSCdj13565

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.

• CSCdj18430

Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.

Workaround: None.

• CSCdj18583

Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.

Workaround: None.

• CSCdj42967

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.

• CSCdj68412

Symptom: If there are multiple parallel paths to the same destination on the ATM switch 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 as a single VC.

Workaround: None.

• CSCdj71109

Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.

Workaround: None.

• CSCdj78305

Symptom: IP host-routing does not disable when specified.

Workaround: Enable and disable IP routing and then save the configuration to NVRAM.

• CSCdj80396

Symptom: With a large number of connections installed, a show atm vc command may take longer than two seconds to complete. This delay will produce a %SYS-3-CPUHOG error message from the scheduler.

Workaround: If you are looking for a specific VC, specify the interface and VPI/VCI when issuing the show atm vc command.

• CSCdj82930

Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.

Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command on the UNI interfaces of the switch that had the closed physical interface.

• CSCdj85853

Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.

Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.

• CSCdk07378

Symptom: Funnel VCs can jeopardize quality of service (QoS) for 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 SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.

Workaround: None.

• CSCdk30912

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.

• CSCdk42052

Symptom: When loading a software version 11.3, or later, image on a switch with 11.2, or earlier, image, LEC 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.

The ATM address of the switch 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 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.

• CSCdk47516

Symptom: Tag switching and Tag Discovery Protocol (TDP) 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 for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.

Workaround: None.

• CSCdk52436

Symptom: On a Catalyst 8540 MSR system configured with 32 MB 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 MSR system configured with 64 MB RAM.

Workaround: None.

• CSCdk57536

Symptom: If some interfaces have state transitions ("go down" and "come back up"), occasionally the "Net Background" process might cause a CPU_HOG error.

Workaround: None.

• CSCdk88859

Symptom: The Frame Relay port adapter firmware might report CRC errors on a PVC if it receives traffic using the same VPI/VCI/DLCI as the PVC being configured. The errors only occur while the firmware is still configuring the VC. Once the PVC has been configured, the CRC errors are discontinued. Since the frames appear like zero-length AAL5 packets while the firmware is still configuring the VC, the firmware does not increment discard bytes, but only increments discard frames due to the CRC error counter.

Workaround: Do not allow traffic to pass on the VC while it is being configured on the port adapter.

• CSCdm07703

Symptom: On deleting the secondary route processor's start-up configuration, a CPUHOG message appears on the secondary route processor.

The delete command for devices is no longer supported. This is only for files. However, the erase command can be used.

Workaround: Use the erase command to delete devices instead of the delete command.

• CSCdm11864

Symptom: 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 sync is applied, or if the latest running configuration sync fails, then, although PVCs can be preserved, discrepancies might exist between software data structures and hardware programming.

Workaround: Use the copy running-config startup-config command before a route processor switchover.

• CSCdm24385

Symptom: The Catalyst 8540 MSR system might crash with IPC errors on switchover.

The primary processor constantly issues IPC sequence errors and the secondary processor crashes during a redundancy force-failover main-cpu command.

Workaround: None.

• CSCdm25175

Symptom: Update rsAlloc accurately based on granularity of the mantissa value.

During the CAC process, for pure or partial rate scheduled connections, the rate actually programmed in the hardware might exceed the rate requested. This problem 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 volume than the rate scheduler's program (the difference is less than .03%).

Workaround: None.

• CSCdm29529

On the Catalyst 8540 MSR, under certain conditions, it is not possible to use a VCI value higher than 8191 for SoftVCs and PVCs.

Workaround: Use a VCI value lower than 8192.

• CSCdm29939

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

• CSCdm30294

Symptom: File system prefix exits tracebacks on switchover.

Workaround: None

• CSCdm32678

Symptom: While switching the route processor over, LMI times out on the peer interface.

At present, the Catalyst 8540 MSR requires about a minute to switch. The frame-relay interface might take about a minute before it can respond to any LMI activity.

Workaround: To prevent LMI timeouts on peer interface during switchover, configure the LMI timeout to be larger than the time it takes for Catalyst 8540 MSR route processor to switch over. Configure lmi-n392dce, lmi-n392dte, lmi-t392dce and lmi-n391dte on the frame-relay interface, such that LMI does not bring down the interface if no LMI activity is seen for about a minute.

• CSCdm36800

Symptom: The CES ABCD bits are not user configurable when a fault occurs.

Workaround: None.

• CSCdm44167

Symptom: EIGRP updates missing for some addresses on ATM router module port subinterfaces.

Workaround: In global configuration mode, enter the no auto-summary command followed by auto-summary command.

• CSCdm49429

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.

• CSCdm68761

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.

• CSCdm77667

Symptom: IPX ping incorrectly shows success when simultaneous pinging.

Workaround: None.

• CSCdm80628

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.

• CSCdm82878

Symptom: Following a change to a spanning tree, there might be inconsistencies in the bridge members information stored in the EPAM and the IOS.

Workaround: Use the clear bridge command to purge the bridging cache.

• CSCdm84365

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.

• CSCdm86667

Symptom: Running a 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 complete

ms04_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 60095780

Workaround: None.

• CSCdm87797

Symptom: An IPX packet containing the wrong length in the IPX header and requiring encapsulation change causes the ingress port to hang. The switch must be reloaded.

Workaround: None.

• CSCdm90166

Symptom: If the switch is booted with NVRAM which is cleared because the switch 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 is booted after a write erase command.

• CSCdm92183

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, there should be no loss of connectivity.

Workaround: None.

• CSCdp01016

Symptom: If no ACL module is present in a slot, the following message appears in console log on a SP switchover:

No ACL card in slot
 

This is an informational message only and has no affect on switch function.

Workaround: None.

• CSCdp01936

PVCs exiting the switch over a hierarchical VP tunnel are not preserved when the route processor switches over. The switch stops switching traffic over such PVCs on and after the route processor switchover. The hierarchical VP tunnel remains active, however, and the VCs defined over the hierarchical VP tunnel subsequent to the route processor switchover, both PVCs and SVCs, function as expected.

Workaround: None.

• CSCdp02661

Symptom: When changing a PNNI node's level, PTSEs belonging to the old node are completely flushed from the node, but might not be completely flushed from the network. As a result these PTSEs might reappear in the local node's PTSE database after database synchronization with neighbor nodes.

The reappearance of the old PTSEs does not affect PNNI functionality in any way. These PTSEs will be flushed after they normally age out.

Workaround: None.

• CSCdp02816

Symptom: The show ncdp path root command might not print any information when you access the switch through the Ethernet port.

Workaround: Access the switch using the console port.

• CSCdp03092

Symptom: The Catalyst 8540 MSR might display a CRC error when it obtains the clock via an OC-3 link from a LightStream 1010 ATM switch and then uses or redistributes the clock over an OC-12 link.

Workaround: Use the internal clock or bring the clock source directly to the Catalyst 8540 MSR.

• CSCdp03166

Symptom: The Catalyst 8540 MSR 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.

• CSCdp04109

Symptom: The debug ncdp packets, debug ncdp errors, and debug ncdp events commands do not display any information when you access the switch through the Ethernet port.

Workaround: Access the switch using the console port.

• CSCdp05103

Symptom: When attempting to reprogram the ROMMON, the switch sometimes hangs after displaying the following message:

Resetting in 3 seconds

Workaround: Hot swap the route processor or power cycle the switch.

• CSCdp07226

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, the system boot image that needs to be autobooted must be specified using the boot system command. If the system image is specified using the boot system ftfp command, the bootloader image also needs to be specified using the boot bootldr command. After these commands have been executed, save the configuration in the NVRAM using the copy running-config startup-config command.

• CSCdp08242

Symptom: The undebug all command does not disable the debug redundancy all command.

Workaround: Use the no debug all command to disable the debug redundancy all command.

• CSCdp08255

Symptom: The show running-config command display contains a reference to the aux 0 port, which is not supported.

Workaround: None.

• CSCdp10310

Symptom: IP multicast counters (S,G) may 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 can be overrun.

Workaround: None.

• CSCdp11944

Symptom: When copying a file to a Flash memory card on a secondary route processor, the switch 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.

• CSCdp13836

Symptom: When the secondary route processor's resources, such as the amount of DRAM, are same as or more than the primary route processor's resources, the switch is fully redundant. However, after a route processor switchover, if the new primary route processor's resources are more than the new secondary route processor's, a fully redundant switch becomes conditionally redundant and the new primary route processor's 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 ACPMs
  BOOTFLAH SIMM Size - Primary = 16 MB, Secondary = 8 MB
  Because of the BOOTFLASH size mismatch, the files that fits in the
  Primary ACPM's BOOTFLASH may not fit in the Secondary's BOOTFLASH, if and
  when a switchover occurs.  This may cause loss of information. The system 
  is now running CONDITIONALLY REDUNDANT - subject to the above mentioned 
  mentioned restriction
 

Workaround: Ensure that the both route processors on the switch have the same resources.

• CSCdp14860

Symptom: If an 8-port Gigabit Ethernet card is installed on the switch, switch processor switchover is temporarily unsupported. After issuing a redundancy prefered-switch-card-slots command, the switch displays the following message:

There is 8 Port Gigabit Ethernet PAM in the Chassis, SP switch over is temporary unsupported

Workaround: None.

• CSCdp14997

Symptom: PC cards cannot be formatted on the secondary route processor.

Workaround: Format the PC card on the primary route processor then move it to the secondary route processor.

• CSCdp15945

Symptom: If a Fast Ethernet interface module is installed on an active switch, 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.

• CSCdp19060

Symptom: The secondary route processor incorrectly displays out-of-sequence messages even though the packets are resent and the sequence is recovered.

Workaround: None.

• CSCdp20608

Symptom: The show interfaces atm-sec0 command always displays zero counter values.

Workaround: None.

• CSCdp20865

Symptom: Entering shutdown/no shutdown commands on an ATM router module interface, especially when it has several LANE clients configured, can cause the switch to issue messages similar to the following:

%LANE-3-LANE_ERROR: lecs finder: ILMI hung on interface ATM1/0/0

This message indicates that an internal timeout occurred. The interface recovers and any normal operations are not affected.

Workaround: None.

• CSCdp21758

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.

• CSCdp21879

Symptom: If an OC-48c interface module is removed and reinserted on an active switch 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, issue a shutdown command followed by a no shutdown command on the affected OC-48c interface.

• CSCdp22516

Symptom: An active switch processor module should not be hot swapped before it is put in standby mode.

If a SP module is currently active while the system is running IOS, and the module is removed from the chassis before making it a standby module, the connections might hang. This disrupts traffic after 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. This is done using either of the following methods:

• Use the show preferred-switch-card-slots command.

• Look at the LEDs on the SP modules.

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 to be removed is currently the standby, it can be removed without issuing any commands.

If the SP module is currently active, issue the following command to designate the other two SP modules as the active switch 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, to ensure that the SP module to be removed is the standby issue the following command:

show preferred-switch-card-slots

The SP module to be removed should no longer be active and can be safely removed.

The following example shows how to prepare the switch 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:7

Switch# redundancy prefered-switch-card-slots 6 7

Switch# show preferred-switch-card-slots

The currently preferred switch card slots are slot:6 and slot:7
The currently active switch card slots are slot:6 and slot:7

• CSCdp23208

Symptom: On switch processor switchover, Ethernet interface modules behave as if a system reload has occurred and take the same amount of time to reinitialize as it does for a reload. Before the interface modules come up, if a switchover is done timeout messages are issued. This happens because the Ethernet ports are being initialized through IPC and half way through the Ethernet interface modules are reset again because of the switchover.

Workaround: None.

• CSCdp23213

Symptom: After a switch processor switchover, the input and output packet counters have invalid values.

Workaround: None.

• CSCdp23923

Symptom: If a switchover occurs when route processor traffic exceeds 5 Mbps causing 100% route processor utilization, the following timeout message is displayed:

 1d13h: %LINK-3-UPDOWN: Interface ATM9/1/0, changed state to down
 1d13h: %LINK-3-UPDOWN: Interface ATM9/1/1, changed state to down
 1d13h: %LINK-3-UPDOWN: Interface ATM9/1/2, changed state to down
 1d13h: %LINK-3-UPDOWN: Interface ATM9/1/3, changed state to downTimeout wait for download response
 

As a result, Fast Ethernet (FE) or Gigabit Ethernet (GE) ports might not come up. Remove and reinsert the FE/GE interface module to allow the ports to be reenabled.

Workaround: Redesign the network to reduce the amount of traffic to the route processor.

Cisco IOS Release 12.0(1a)W5(9) Caveats Corrected

• CSCdj31762

Symptom: SNMP SET to a CES port causes the switch to hang.

If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.

• CSCdj47998

Symptom: The Catalyst 8540 MSR Ethernet connection does not receive CDP multicast packets. However, the Catalyst 8540 MSR does send out CDP multicast packets.

• CSCdj84344

Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.

• CSCdk17977

Symptom: Another vendor's router, when running UNI 4.0, cannot connect a VC to a Cisco router, which runs UNI 3.1, by way of a Catalyst 8540 MSR.

• CSCdk22484

Symptom: ATM Accounting: Exception in validblock_diagnose because resources at destination switch were not available.

• CSCdk22791

Symptom: When a large amount of data is sent out of the Ethernet interface, the interface can become overwhelmed and start generating the error message:

%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs

The interface stops sending data and the transmitter remains stuck.

• CSCdk33601

Symptom: ADD party over tunnel does 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.

• CSCdk62547

Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.

• CSCdk69639

Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface puts it in the "not TDP ready" state.

• CSCdk71268

Symptom: Reprogramming a SCAM caused the Catalyst 8540 MSR to hang and not reboot.

After successfully reprogramming a revision 4.0 SCAM with FPGA 1.4, the Catalyst 8540 MSR might hang. Power-cycling was not successful in rebooting until the SCAM was removed.

• CSCdk76280

Symptom: Connections where end-to-end delay IE is included in the connect message might fail. Examples of these connections include UNI40, CBR, and UBR-rt.

A Catalyst 8540 MSR that is an intermediate switch 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.

• CSCdk77032

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

• CSCdk78469

Symptom: PNNI does not clean up and release some of its data structures properly, following 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 lost until the next reload.

• CSCdk82708

Symptom: When running tag switching, no tag is created for the default route.

• CSCdk90091

Symptom: A software crash might occur on the switch running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.

• CSCdk90147

Symptom: A crash might occur while removing subinterfaces using the no interface command.

• CSCdk92832

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 (approximately 1% in the worst case).

Upgrade the Switch Feature Card FPGA image to release fi-c8540-fc.A.4-17 or later.

• CSCdm04013

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.

• CSCdm05738

Symptom: Due to a bad VCXO, a packet might delay on the switch indefinitely and cause a software crash.

• CSCdm07857

Symptom: Messages appear when hot swapping an OC-12 port adapter.

When you hot swap an OC-12 port adapter into the Catalyst 8540 MSR 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 programmed

IDPROM in slot 12 not properly programmed

01:01:55: %SCHED-2-WATCH: Attempt to lock uninitialized watched semaphore (address 0).

• CSCdm12694

Symptom: Under certain circumstances, cell loss occurs between unlike bandwidth interfaces that reside on the same carrier module.

Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.

• CSCdm15900

Symptom: The Catalyst 8540 MSR switch uses backward parameters in QoS IE for point-to-multipoint calls.

This might cause incompatibility with other vendors' implementations.

• CSCdm19018

Symptom: When a call setup traverses a switch running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.

• CSCdm19073

Symptom: The granularity of the switch's rate scheduler is such that rates are rounded down (when converting from bits per second to cells per second) when in fact they should be rounded up.

• CSCdm20257

Symptom: Under certain circumstances, the lane server-bus ethernet command can cause an unexpected exception.

• CSCdm23212

Symptom: show hardware command does not display power supply IDPROM details.

The show hardware command should include the details of IDPROM information in the power supplies.

• CSCdm23579

Symptom: The switch 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 .

• CSCdm24192

Symptom: Failed attempts to reprogram a SCAM cause the Catalyst 8540 MSR to hang.

• CSCdm29650

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.

• CSCdm30009

Symptom: Primary route processor should not be hot swapped.

There are some precautions that need to be taken before removing a route processor module controller from a chassis that is powered-up:

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 might stop.

If the route processor module that is being removed is currently in ROM monitor mode, then it is safe to remove it from the chassis.

One way to get the system to ROM monitor mode from IOS is to issue a reload command. This works if the system is not configured to automatically boot. If the system is configured to automatically boot, it starts booting IOS again. Since the route processor must be in ROM monitor mode before removing it, the following command has been added to take to the system from the IOS prompt to the ROM monitor mode prompt:

redundancy prepare-for-cpu-removal

One must execute this command on the route processor before removing it. Once this command is issued 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.

It is important to note that the command must be executed after connecting to the console port of the route processor being removed. If the system has a Y cable, then the Y cable must be removed and a local connection to the route processor being removed must be obtained before the command is issued. The command must be issued on a route processor that is in IOS mode, even if it is the secondary route processor.

• CSCdm30269

Symptom: No means to change the default active switch processor modules is available.

If a Catalyst 8540 MSR has 3 switch processor modules, then by default the switch processor modules in slots 5 and 7 come up as the active switch processor modules and the switch processor modules 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 should 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 if the system should change the active switch cards to the preferred switch processor module. If such a switchover occurs, all the active connections in the system will be 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 card configuration is preserved across route processor switchovers. However, the preferred switch processor module setting will be lost if the system is power cycled or if both route processors are reloaded to ROM monitor mode.

Cisco IOS Release 12.0(1a)W5(9) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the Catalyst 8540 MSR for Cisco IOS Release 12.0(1a)W5(9).

• With some OC-12 single-mode fiber line modules, the link fails to be present after the fiber cable has been inserted. Make sure that the fiber cables are completely seated by pushing on the strain reliefs of the individual fibers until they click into place to complete the optical connection. In some cases, the small metal septum on the transceiver front panel obstructs the connection.

• The maximum number of ELAN LES/BUS pairs supported is 10.

• CSCdi55937

Symptom: Remote defect identification (RDI) cells sent by an endpoint in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch 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.

Workaround: None.

• CSCdi74229

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-CPUHOG
 

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

Workaround: None.

• CSCdi83275

Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:

%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts 
 

In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.

Workaround: Toggle the interface to reinitialize all connections and restore normal operation.

• CSCdi92142

Symptom: A LECS expects all LES's to establish an individual control VC to the LECS to validate clients.

If different emulated Local Area Networks (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validate 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_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
 

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

• CSCdj01016

Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:

• VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).

• ABR, UBR: no bandwidth is allocated.

Workaround: None.

• CSCdj10889

Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch 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.

• CSCdj11070

Symptom: CDP config cannot be saved to NVRAM for the LEC.

When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM (it also does not show up when doing a write term). The disabling does work, but you lose it again after a reload.

Workaround: None.

• CSCdj13565

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.

• CSCdj18430

Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.

Workaround: None.

• CSCdj18583

Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.

Workaround: None.

• CSCdj42967

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.

• CSCdj68412

Symptom: If there are multiple parallel paths to the same destination on the ATM switch 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 merge and go out of the switch as a single VC.

Workaround: None.

• CSCdj71109

Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.

Workaround: None.

• CSCdj78305

Symptom: IP host-routing does not disable when specified.

Workaround: Enable and disable IP routing and then save the configuration to NVRAM.

• CSCdj80396

Symptom: CPU hog while setting up a lot of calls.

Workaround: None.

• CSCdj82930

Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.

Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command on the UNI interfaces of the switch that had the closed physical interface.

• CSCdj84379

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

• CSCdj85853

Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.

Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.

• CSCdk07378

Symptom: Funnel VCs can jeopardize quality of service (QoS) for 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 SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.

Workaround: None.

• CSCdk26482

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 phylo

This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.

Workaround: None.

• CSCdk27725

Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo

When snoop-VC is configured on a port, the switch returns these internal error messages.

%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr

Workaround: These messages can be ignored; they do not affect the snooping functionality.

• CSCdk30912

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 timeout. This causes some delay during the switchover process.

Workaround: None.

• CSCdk47516

Symptom: Tag switching and Tag Discovery Protocol (TDP) 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 for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.

Workaround: None.

• CSCdk52436

Symptom: On a Catalyst 8540 MSR system configured with 32 MB 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 MSR system configured with 64 MB RAM.

Workaround: None.

• CSCdk57536

Symptom: If some interfaces have state transitions ("go down" and "come back up"), occasionally the "Net Background" process might cause a CPU_HOG error.

Workaround: None.

• CSCdk71688

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. The system needs to be power-cycled before the newly loaded image becomes active.

Workaround: None.

• CSCdk79426

Symptom: Soft VP and PVP 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 PVP.

Workaround: There are two ways to get the soft VP up:

• Remove the PVP.

• Create a PVP using the same VPI value on the peer switch. This forces the peer switch to allocate a different VPI value for the soft VP.

• CSCdk80021

Symptom: sysConfigName variable value 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.

• CSCdk83334

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 it is possible that some of the leaves of the connection will 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.

Work-around: If possible, shut down traffic on all point-to-multipoint connections before a route processor switchover.

• CSCdk87118

Symptom: While toggling the interfaces on the peer switch (LightStream 1010 ATM switch), the following error messages is occasionally displayed on the Catalyst 8540 MSR:

04:09:08: process_cubi_cell_list: cubi_oam_upcall returned an error

This occurs when LECS is configured on the route processor port along with 10 LES/BUS/clients on the 10 subinterfaces on the route processor port.

Workaround: None.

• CSCdm05084

Symptom: CES port LEDs on the Catalyst 8540 MSR are inconsistent with the LightStream 1010 ATM switch.

The Catalyst 8540 MSR has inconsistent LED status with 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 MSR is:

S1=red; S2=red; CD=green;

Workaround: None.

• CSCdm07703

Symptom: On deleting the secondary route processor's startup configuration, a CPUHOG message appears on the secondary route processor.

The delete command for devices is no longer supported. This is only for files. However, the erase command can be used.

Workaround: Use the erase command to delete devices instead of the delete command.

• CSCdm08234

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.

• CSCdm11864

Symptom: 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) startup configuration sync is applied, or if the latest running configuration sync fails, then, although PVCs can be preserved, discrepancies might exist between software data structures and hardware programming.

Workaround: Use the copy running-config startup-config command before a route processor switchover.

• CSCdm19670

Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).

Workaround: None.

• CSCdm24385

Symptom: Catalyst 8540 MSR crashed with IPC errors on switchover.

Primary constantly issues IPC sequence errors and the secondary crashes during a redundancy force-failover main-cpu command.

Workaround: None.

• CSCdm25175

Symptom: Update rsAlloc accurately based on granularity of the mantissa value.

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 particular 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 .03%).

Workaround: None.

• CSCdm29365

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-3 SPAM displays the information for even-numbered ports.

Workaround: None.

• CSCdm29503

Symptom: Advertised priority not updated for PGL if configured to match advertised priority.

Workaround: None.

• CSCdm29529

On the Catalyst 8540 MSR, under certain conditions, it is not possible to use a VCI value higher than 8191 for SoftVCs and PVCs.

Workaround: Use a VCI value lower than 8192.

• CSCdm29939

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

• CSCdm30023

Symptom: Setting the gateway of last resort is delayed on switchover.

The static ip routes take from 1.5 to 2 minutes to take effect on switchover.

Workaround: None

• CSCdm30294

Symptom: File system prefix exits tracebacks on switchover.

Workaround: None

• CSCdm32506

Symptom: When issuing a show running-config command the Catalyst 8540 MSR might fail unexpectedly, due to a bus error.

Workaround: None.

• CSCdm32678

Symptom: While switching the route processor over, LMI times out on the peer interface.

At present, the Catalyst 8540 MSR requires about a minute to switch. The frame-relay interface might take about a minute before it can respond to any LMI activity.

Workaround: To prevent LMI timeouts on peer interface during switchover, configure the LMI timeout to be larger than the time it takes for Catalyst 8540 MSR route processor to switchover. Configure lmi-n392dce, lmi-n392dte, lmi-t392dce and lmi-n391dte on the frame-relay interface, such that LMI will not bring down the interface if no LMI activity is seen for about a minute.

• CSCdm33737

Symptom: Marker cells are not being drained after shutdown/no shutdown of 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 tunnels.

Workaround: None.

• CSCdm34634

Symptom: The soft pvc count might not be included in atmfAtmLayerConfiguredVCCs.

Workaround: None.

• CSCdm36745

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.

• CSCdm36790

Symptom: When forwarding a call setup from one VP tunnel to another, the Catalyst 8540 MSR might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.

Workaround: None.

• CSCdm38218

Symptom: If a show debugging command is issued on a Catalyst 8540 MSR that is configured as a PNNI "childless uncle," an infinite loop condition might occur that causes a watchdog timeout.

Workaround: None.

• CSCdm43664

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.

• CSCdm44079

Symptom: A problem in the reinitialization logic might cause the system to fail unexpectedly when a switch card in slot 5 is the standby processor and the switch card in slot 7 fails.

Workaround: None.

• CSCdm44497

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 UNI3.0 specification, section 5.4.5.15, defines a cause code 8a as "VPCI/VCI unacceptable." When the call goes out on a uni3.1 interface, this cause code should be mapped to VPI/VCI assignment failure. This mapping does not occur for PNNI links.

Workaround: None.

• CSCdm45453

Symptom: The ciscoLS1010ChassisInletTempStatus MIB, 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.

• CSCdm46430

Symptom: The system might not allow you to configure more than 255 VPs, even though the Catalyst 8540 MSR supports a maximum of 4095 VPs.

Workaround: None.

• CSCdm47012

The new 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 For redundant systems, only the primary route processor can be netbooted.

---

• CSCdm47048

Symptom: An unexpected system failure might occur following a show tech-support command.

Workaround: None.

• CSCdm48886

The LightStream 1010 ATM switch does not support a PVP tunnel with a VPI value of 0. The IOS 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.

• CSCdm54001

Symptom: After performing an OIR on a board, the corresponding interface counters might become unreliable.

Workaround: None.

• CSCdm54297

When the switch is booted after a power-cycle, reload reason in the show version command does not indicated that the "System restarted by power-on."

Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.

• CSCdm55248

The status LED on the standby switch card remains red after boot up.

Workaround: None.

• CSCdm56393

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.

• CSCdm63047

Symptom: If atm 1/0/0 is the present active clock source and atm 1/1/0 is the secondary clock source, the clock source of the secondary might be overridden to loop-timed rather than network-derived.

Workaround: None.

• CSCdm64544

Symptom: When using exception core via FTP, an exception dump might not be performed following a system crash.

Workaround: None.

• CSCdm66516

Symptom: Configuring interfaces under 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 indicates that the secondary route processor is `down.'

Workaround: Remove all configuration commands from line aux 0 and reboot the switch.

• CSCdm68761

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.

• CSCdm69065

Symptom: The "Uptime" displayed for the secondary route processor following a show redundancy command might display incorrectly. This problem occurs because the uptime "rolls over" after about four hours.

Workaround: None.

• CSCdm77987

Symptom: Attempting to format the new Intel 200 Series PCMCIA card that is currently shipping with other platforms (such as the Catalyst 6000) might cause the Catalyst 8540 MSR to fail unexpectedly with a bus error. If this failure occurs, the system will not boot up successfully until the PCMCIA card is removed from the Catalyst 8540 MSR.

Workaround: Remove the PCMCIA card from the switch.

• CSCdm81581

With the system configured to autoboot, when the redundancy prepare-for-cpu-removal command is issued, 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.

• CSCdm82033

Symptom: After repeated configuration commands, the system might freeze unexpectedly.

Workaround: None.

• CSCdm87966

Symptom: When powering up and booting the switch router with two route processors or installing a second route processor in a working switch, 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 MSR switch router with two route processors and the secondary route processor have an FPGA image version of 4.5 or earlier.

Workaround: Upgrade the route processor FPGA image to Version 4.6 or later. You can also power cycle the switch router or perform the OIR (online insertion and removal) procedure on the secondary route processor.

• CSCdm88183

Symptom: Following a software reload, the Catalyst 8540 MSR might fail unexpectedly with a write bus error. This failure might occur if the system is configured with one route processor and if the MSPs are installed in slots 5,6 or 6,7.

Workaround: Install the MSPs in slots 5 and 7.

• CSCdm89205

Symptom: Following a processor card switchover, a number of interfaces might not be recognized.

Workaround: Upgrade the carrier module FPGA image to release 1.7 or later.

• CSCdm89519

Symptom: The Digital Crossconnect Unit (DCU) might malfunction unexpectedly.

Workaround: None.

• CSCdm91042

Symptom: On a system configured with either both power supplies or with only power supply 1, issuing the show hardware, show hardware detail, or show tech-support commands might cause the memory to be corrupted. If this memory corruption occurs and the show subsystem command is issued, the Catalyst 8540 MSR 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 text. If the system is configured with one power supply, make sure that power supply 0 is being used.

• CSCdm91060

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.

• CSCdm91571

Symptom: When using the Catalyst 8540 MSR 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-12 port adapters, 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, ATM 11/0/2 might fail the UPC tag mode.

---

Note All other interfaces should work.

---

Workaround: Upgrade the switch processor FPGA image to Version 1.5 (fi-c8540-msp.A.1-5).

• CSCdm92990

Symptom: Despite having enough bandwidth, Resource Management might reject some soft PVCs.

Workaround: None.

• CSCdm94019

Symptom: Under certain circumstances, the Catalyst 8540 MSR might display inaccurate traffic statistics on NNI or UNI interfaces.

Workaround: None.

Cisco IOS Release 12.0(1a)W5(7b) Caveats Corrected

• CSCdk89079

Symptom: OIR INSCARD messages display during boot.

• CSCdk89501

Symptom: Online insertion and removal of port adapter modules can result in a bus error.

• CSCdk91364

Symptom: In the output of the show atm vc command, all of the packet counters are incorrectly displayed as zero.

• CSCdk92661

Symptom: When you hot swap any port adapter module with an OC-12 interface module, the correct configuration for the OC-12 interface module in the port mode table does not come up properly.

Cisco IOS Release 12.0(1a)W5(7b) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the Catalyst 8540 MSR for Cisco IOS Release 12.0(1a)W5(7b).

• The maximum number of ELAN LES/BUS pairs supported is 10.

• CSCdi55937

Symptom: Remote defect identification (RDI) cells sent by an endpoint in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch 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.

Workaround: None.

• CSCdi74229

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-CPUHOG
 

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

Workaround: None.

• CSCdi83275

Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:

%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts 
 

In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.

Workaround: Toggle the interface to reinitialize all connections and restore normal operation.

• CSCdi92142

Symptom: A LECS expects all LES's to establish an individual control VC to the LECS to validate clients.

If different emulated Local Area Networks (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LES(s) 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_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
 

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

• CSCdj01016

Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:

• VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).

• ABR, UBR: no bandwidth is allocated.

Workaround: None.

• CSCdj10889

Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch 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.

• CSCdj11070

Symptom: CDP config cannot be saved to NVRAM for the LEC.

When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM (it also does not show up when doing a write term). The disabling does work, but you lose it again after a reload.

Workaround: None.

• CSCdj13565

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.

• CSCdj18430

Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.

Workaround: None.

• CSCdj18583

Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.

Workaround: None.

• CSCdj31762

Symptom: SNMP SET to a CES port causes the switch to hang.

If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.

Workaround: None.

• CSCdj42967

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.

• CSCdj47998

Symptom: The Catalyst 8540 MSR Ethernet connection does not receive CDP multicast packets. However, the Catalyst 8540 MSR does send out CDP multicast packets.

Workaround: None.

• CSCdj68412

Symptom: If there are multiple parallel paths to the same destination on the ATM switch 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 merge and go out of the switch as a single VC.

Workaround: None.

• CSCdj71109

Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.

Workaround: None.

• CSCdj78305

Symptom: IP host-routing does not disable when specified.

Workaround: Enable and disable IP routing and then save the configuration to NVRAM.

• CSCdj80396

Symptom: CPU hog while setting up a lot of calls.

Workaround: None.

• CSCdj82930

Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.

Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command on the UNI interfaces of the switch that had the closed physical interface.