cc/td/doc/product/atm/c8540/wa5/12_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(7)W5(15c)

Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(7)W5(15c)

August 22, 2000

Catalyst 8540 MSR Cisco IOS Release 12.0(7)W5(15c)

Text Part Number: 78-6190-07 Rev. B0

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

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

Contents

This document includes the following sections:

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 full-duplex nonblocking switch fabric with switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.0(7)W5(15c) and includes the following sections:

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(7)W5(15c) 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:

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:

Then do the following:
Note   If you have a redundant route processor configuration, you need ROMMON image 12.0(4.6)W5(13) or later. See caveats CSCdm81581, CSCdm54297, and CSCdm43664, which are described later in these release notes, for more information.
An example follows:
    Switch(config)# boot system tftp cat8540m-wp-mz.120-4a.W5.11a 172.20.52.3
Note   The boot ROM on the Catalyst 8540 MSR can be field-upgraded via the reprogram command. For more information about upgrading the boot ROM, see the ATM Switch Router Command Reference.

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(7)W5(15c) 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-FRRJ48

4-port CE1 Frame Relay port adapter

W5-9

C85MS-1DS3-FRBNC

1-port CDS3 Frame Relay port adapter

W5-9

C85MS-1F4M-OC48SS

1-port OC-48c SMF-IR + 4-port OC-12 MMF

S854R2-12.0.4W

C85MS-1F4S-OC48SS

1-port OC-48c SMF-IR + 4-port OC-12 SMF-IR

S854R2-12.0.4W

C85MS-2F-OC48SS

2-port OC-48c SMF-IR

S854R2-12.0.4W

C8540-ARM

ATM router module

S854R2-12.0.4W

C85GE-8X-64K

C8540 (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

C85MS-8T1-IMA

8-port T1 port adapter with inverse multiplexing over ATM

S854R2-12.0.7W1

C85MS-8E1-IMA-120

8-port E1 port adapter with inverse multiplexing over ATM

S854R2-12.0.7W1

C85MS-1F4S-OC48LR

1-port OC-48c SMF-LR + 4-port OC-12 SMF-IR

S854R2-12.0.7W

C85MS-2F-OC48LR

2-port OC-48c SMF-LR

S854R2-12.0.7W

C8540-ACL

ACL daughter card

S854R2-12.0.7W

1The T1/E1 IMA port adapters also require carrier module FPGA image version 1.8 or later, and IMA port adapter functional image version 3.2 or later.

Determining Your Software Release

To determine the version of Cisco IOS software currently running on the Catalyst 8540 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(7)W5(15c)

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(7)W5(15c) 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

x

SNMP1

x

x

x

x

x

Asynchronous support

x

x

x

x

x

PPP2 (SLIP3/PPP)

x

x

x

x

x

IP4

x

x

x

x

x

NTP5

x

x

x

x

x

TACACS+6

x

x

x

x

x

Telnet

x

x

x

x

x

Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8

x

x

x

x

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI9 3.0)

x

x

x

x

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)

x

x

x

x

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)

x

x

x

x

x

Multipoint-to-point UNI signaling

x

x

x

x

x

Soft VCCs and VPCs

x

x

x

x

x

VP tunneling

x

x

x

x

x

VPI/VCI range support in ILMI 4.0

x

x

x

x

x

PNNI hierarchy

x

x

x

x

x

ILMI10 version 4.0

x

x

x

x

x

IISP11

x

x

x

x

x

LANE12 client (LEC13) and LANE services (LES14/BUS15/LECS16) on Route Processor

x

x

x

x

x

ATM ARP17 server on Route Processor

x

x

x

x

x

ATM ARP client on Route Processor

x

x

x

x

x

ATM tag switch router (TSR)

x

x

x

x

x

Port snooping

x

x

x

x

x

OAM18 F4 and F5

x

x

x

x

x

E.164 address translation

x

x

x

x

x

E.164 autoconversion

x

x

x

x

x

Circuit emulation

x

x

x

x

x

ATM access lists

x

x

x

x

x

ATM accounting

x

x

x

x

x

ATM RMON19

x

x

x

x

x

Multiple, weighted, dynamic thresholds for selective packet marking and discard

x

x

x

x

x

Shaped VP tunnels for CBR20 traffic

x

x

x

x

x

Substitution of other service categories in shaped VP tunnels

x

x

x

x

x

Dual leaky bucket policing

x

x

x

x

x

Scheduler/Service Class/PVC configuration

x

x

x

x

x

Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC)

x

x

x

x

x

Network clocking enhancements for smooth switchover

x

x

x

x

x

Per-VC or per-VP nondisruptive snooping

x

x

x

x

x

Support for non-zero MCR21 on ABR22 connections

x

x

x

x

x

Access lists on ILMI registration

x

x

x

x

x

CUGs

x

x

x

x

x

ATM soft restart

x

x

x

x

x

ATM accounting enhancements

x

x

x

x

x

CISCO-SYSLOG-MIB support

x

x

x

x

x

CISCO-CONFIG-COPY-MIB support

x

x

x

x

x

Signaling diagnostics and MIB23

x

x

x

x

x

Supplemental AToM MIB

x

x

x

x

x

Hierarchical VP tunnels

x

x

x

x

x

Remote logging for accounting

x

x

x

x

x

Tag switching VC-merge on non-UBR24 VP tunnels and hierarchical VP tunnels

x

x

x

x

x

PNNI complex node representation

x

x

x

x

x

PNNI explicit paths

x

x

x

PNNI alternate link selection

x

x

x

Tag switching CoS

x

x

x

Network Clock Distribution Protocol

x

x

x

Simple Gateway Control Protocol

x

x

x

Switch redundancy

x

x

x

CPU redundancy: PVP/PVC/VP tunnel preservation

x

x

x

12-bit VPI

x

x

x

ATM router module

x

x

ATM overbooking

x

x

Framing overhead

x

x

ATM End System Address (AESA) gateway

x

x

Online insertion and removal support for 8-port Gigabit Ethernet interface modules

x

Route processor switchover support for 8-port Gigabit Ethernet interface modules

x

Appletalk support for 8-port Gigabit Ethernet interface modules

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

W5-15

12.0(7)W5(15c)

S854R2-12.0.7W

New and Changed Information

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

New Features in Release 12.0(7)W5(15c)

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

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

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

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

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

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

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

Caveats

This section lists the caveats and corrected caveats for each release. Use Table 4 to determine the status of a particular caveat and its relevancy to your software release. In the table, "Y" indicates a corrected caveat, "N" indicates an open caveat, and "-" indicates a corrected caveat carried forward from the previous release.


Table 4: Release Caveats and Caveats Corrected Reference
DDTS Number 12.0(7)W5(15c) 12.0(4a)W5(11a) 12.0(1a)W5(9) 12.0(1a)W5(7b) 12.0(1a)W5(7a)

CSCdr41940

N

CSCdr39060

N

CSCdr36952

Y

N

CSCdr35301

N

N

CSCdr32958

N

CSCdr30421

N

N

CSCdr28797

N

N

N

CSCdr26204

N

N

CSCdr26034

N

N

CSCdr25535

N

CSCdr22770

N

N

N

N

N

CSCdr20326

N

N

N

CSCdr16404

Y

N

N

CSCdr15370

Y

N

CSCdr07165

Y

N

N

N

N

CSCdr06756

Y

N

N

CSCdr06375

Y

N

N

CSCdr06198

Y

N

CSCdr02365

N

N

CSCdr01726

N

N

N

N

N

CSCdr00623

Y

N

N

N

N

CSCdr00483

Y

N

N

CSCdr00463

Y

N

N

CSCdp94469

N

N

N

CSCdp94088

N

N

N

CSCdp93731

Y

N

N

CSCdp93395

N

CSCdp88264

Y

N

CSCdp84086

Y

N

N

CSCdp83445

Y

N

CSCdp81493

Y

N

N

CSCdp81136

N

N

N

N

N

CSCdp76943

Y

N

N

CSCdp75180

Y

N

N

N

N

CSCdp74941

N

N

N

CSCdp74821

N

N

CSCdp72650

Y

N

N

N

N

CSCdp72498

Y

N

CSCdp70903

Y

N

N

N

N

CSCdp67518

N

N

N

N

N

CSCdp66611

Y

N

N

N

N

CSCdp66533

Y

N

CSCdp64865

Y

N

CSCdp63969

N

N

N

N

N

CSCdp63799

Y

N

N

N

N

CSCdp61799

Y

N

CSCdp60263

Y

N

CSCdp59602

Y

N

CSCdp59046

N

N

N

N

N

CSCdp57307

Y

N

CSCdp57023

Y

N

N

CSCdp54685

N

N

N

N

N

CSCdp53470

Y

N

N

N

N

CSCdp50167

N

CSCdp49173

Y

N

N

N

N

CSCdp43332

Y

N

N

N

N

CSCdp43220

Y

N

N

N

N

CSCdp43184

Y

N

N

CSCdp40308

N

N

N

CSCdp39497

Y

N

CSCdp36779

Y

N

N

CSCdp34890

Y

N

CSCdp34129

Y

N

CSCdp33023

Y

N

CSCdp32289

Y

N

CSCdp31368

Y

N

CSCdp29185

Y

N

N

CSCdp25363

Y

N

CSCdp23923

N

N

CSCdp23213

N

N

CSCdp23208

Y

N

CSCdp22516

N

N

CSCdp22057

Y

N

CSCdp21879

Y

N

CSCdp21758

Y

N

CSCdp20865

Y

N

CSCdp20608

N

N

CSCdp20230

Y

N

N

N

N

CSCdp19523

Y

N

CSCdp19342

Y

N

CSCdp19060

Y

N

CSCdp15945

N

N

CSCdp14997

N

N

CSCdp14860

Y

N

CSCdp14509

Y

N

N

N

N

CSCdp13836

N

N

CSCdp11944

N

N

CSCdp10310

Y

N

CSCdp08794

N

N

N

N

N

CSCdp08255

Y

N

CSCdp08242

-

Y

N

CSCdp07226

N

N

CSCdp06298

Y

N

CSCdp05103

Y

N

CSCdp04109

N

N

CSCdp03166

N

N

CSCdp03092

N

N

CSCdp02816

N

N

CSCdp02661

N

N

CSCdp01936

Y

N

CSCdp01016

N

N

CSCdm94019

-

Y

N

CSCdm92990

-

Y

N

CSCdm92183

Y

N

CSCdm91571

-

Y

N

CSCdm91060

-

Y

N

CSCdm91042

-

Y

N

CSCdm90640

Y

N

CSCdm90166

N

N

CSCdm89519

-

Y

N

CSCdm89205

-

Y

N

CSCdm89022

Y

N

CSCdm88183

-

Y

N

CSCdm87966

-

Y

N

CSCdm87797

Y

N

CSCdm86667

-

Y

N

CSCdm84365

N

N

CSCdm83635

Y

N

CSCdm82878

Y

N

CSCdm82033

-

Y

N

CSCdm81581

-

Y

N

CSCdm80628

N

N

CSCdm77987

-

Y

N

CSCdm77667

Y

N

CSCdm74898

Y

N

N

N

N

CSCdm69765

Y

N

CSCdm69065

-

Y

N

CSCdm68761

Y

N

N

CSCdm66516

-

Y

N

CSCdm64544

-

Y

N

CSCdm63047

-

Y

N

CSCdm56393

-

Y

N

CSCdm55248

-

Y

N

CSCdm54297

-

Y

N

CSCdm54001

-

Y

N

CSCdm51009

Y

N

N

N

N

CSCdm49429

N

N

CSCdm48886

-

Y

N

CSCdm47048

-

Y

N

CSCdm47012

-

Y

N

CSCdm46430

-

Y

N

CSCdm45453

-

Y

N

CSCdm44497

-

Y

N

CSCdm44167

N

N

CSCdm44079

-

Y

N

CSCdm43664

-

Y

N

CSCdm38218

-

Y

N

CSCdm36800

N

N

CSCdm36790

-

Y

N

CSCdm36745

-

Y

N

CSCdm34634

-

Y

N

CSCdm33737

-

Y

N

CSCdm32678

N

N

N

CSCdm32506

-

Y

N

CSCdm30294

N

N

N

CSCdm30269

-

-

Y

N

N

CSCdm30023

Y

Y

N

CSCdm30009

-

-

Y

N

N

CSCdm29939

N

N

N

CSCdm29650

-

-

Y

N

N

CSCdm29529

N

N

N

CSCdm29503

-

Y

N

CSCdm29365

-

Y

N

CSCdm25175

N

N

N

CSCdm24385

N

N

N

CSCdm24192

-

-

Y

N

N

CSCdm23579

-

-

Y

N

N

CSCdm23212

-

-

Y

N

N

CSCdm20257

-

-

Y

N

N

CSCdm19670

-

Y

N

CSCdm19073

-

-

Y

N

N

CSCdm19018

-

-

Y

N

N

CSCdm15900

-

-

Y

N

N

CSCdm12694

-

-

Y

N

N

CSCdm11864

N

N

N

CSCdm08234

-

Y

N

CSCdm07857

-

-

Y

N

N

CSCdm07703

N

N

N

CSCdm05738

-

-

Y

N

N

CSCdm05084

-

Y

N

CSCdm04013

-

-

Y

N

N

CSCdm02994

-

Y

N

CSCdk92832

-

-

Y

N

N

CSCdk92661

-

-

-

Y

N

CSCdk91364

-

-

-

Y

N

CSCdk90147

-

-

Y

N

N

CSCdk90091

-

-

Y

N

N

CSCdk89501

-

-

-

Y

N

CSCdk89079

-

-

-

Y

N

CSCdk88859

Y

N

CSCdk87118

-

Y

N

CSCdk83334

-

Y

N

CSCdk82708

-

-

Y

N

N

CSCdk80021

-

Y

N

CSCdk79426

-

Y

N

CSCdk78469

-

-

Y

N

N

CSCdk77032

-

-

Y

N

N

CSCdk76280

-

-

Y

N

N

CSCdk71688

-

Y

N

N

N

CSCdk71268

-

-

Y

N

N

CSCdk69639

-

-

Y

N

N

CSCdk62547

-

-

Y

N

N

CSCdk57536

N

N

N

CSCdk52436

N

N

N

CSCdk47516

N

N

N

N

N

CSCdk42052

N

N

CSCdk33601

-

-

Y

N

N

CSCdk30912

N

N

N

CSCdk27725

-

Y

N

N

N

CSCdk26482

-

Y

N

N

N

CSCdk22791

-

-

Y

N

N

CSCdk22484

-

-

Y

N

N

CSCdk17977

-

-

Y

N

N

CSCdk07378

N

N

N

N

N

CSCdj85853

N

N

N

N

N

CSCdj84379

-

Y

N

N

N

CSCdj84344

-

-

Y

N

N

CSCdj82930

N

N

N

N

N

CSCdj80396

N

N

N

N

N

CSCdj78305

N

N

N

N

N

CSCdj71109

N

N

N

N

N

CSCdj68412

N

N

N

N

N

CSCdj47998

-

-

Y

N

N

CSCdj42967

N

N

N

N

N

CSCdj31762

-

-

Y

N

N

CSCdj18583

N

N

N

N

N

CSCdj18430

N

N

N

N

N

CSCdj13565

N

N

N

N

N

CSCdj11070

-

Y

N

N

N

CSCdj10889

N

N

N

N

N

CSCdj01016

N

N

N

N

N

CSCdi92142

N

N

N

N

N

CSCdi83275

N

N

N

N

N

CSCdi74229

N

N

N

N

N

CSCdi55937

N

N

N

N

N

Caveat Symptoms and Workarounds

Symptom: After a route processor switchover, the microcode for a Fast Ethernet (FE) interface module might not download successfully. This failure occurs infrequently but causes the interfaces on the failed FE interface module to be unusable.
Workaround: Remove and reinsert the affected FE interface module.
Symptom: After a switch processor switchover, the microcode for an 8-port Gigabit Ethernet (GE) interface module might not download successfully. You will see the following error message:
       epif_port_write_mii: Timeout for response message GigabitEthernet
This failure occurs infrequently but causes the interfaces on the failed 8-port GE interface module to be unusable.
Workaround: Issue an skmgmt reset command. When this command is issued, you might see BROUTE-VC SETUP FAILURE messages. These messages are harmless and can be ignored.
Symptom: The switch router will crash and hang when ip http server is configured and a browser connects to http://<router-ip>/%%. This defect can be exploited to produce a denial of service (DoS) attack.This information has been announced on public Internet mailing lists which are widely read both by security professionals and by security "crackers", and should be considered public information.
Workaround: Disable the IP http server with the following command:
no ip http server
Alternatively, the administrator can block port 80 connections to the switch router via access lists or other firewall methods.
For further information, refer to the security advisory available at http://www.cisco.com/warp/public/707/advisory.html
Symptom: The values for ifInOctets wrap every 15 to 30 seconds on ATM interfaces with very little traffic. The wrapping occurs when the value is about 3,000,000 octets.
Workaround: None.
Symptom: The following CPU hog messages might occur after removing an IMA port adapter that has hundreds of SVCs and PVCs configured:
    *Apr 21 10:36:40: %OIR-6-REMCARD: Card removed from slot 2, subcard 1, interfaces disabled
 *Apr 21 10:36:42: %SYS-3-CPUHOG: Task ran for 2096 msec (114/0), process = OIR Handler, PC = 600AA8D8.
 -Traceback= 600AA8E0 6035EB40 6035FC90 600988DC 600988C8
 *Apr 21 10:36:43: %LANE-5-UPDOWN: ATM9/0/0.5 elan elan_cgr05: LE Client changed state to down
 *Apr 21 10:36:43: %IMAPAM-6-LOG: pam 2/1 changed state to NO_HARDWARE
Workaround: None.
Symptom: Multicast statistics might show an incorrect kilobits per second (kbps) rate.
Workaround: None.
Symptom: Incorrect scheduling values might appear for low peak cell rates.
Workaround: None.
Symptom: On a switch using the ospf area-range command, the summary link state advertisement created might get stuck in the database and not be flushed after the command is removed.
Workaround: None.
Symptom: XPIF modules are not supported.
Workaround: None.
Symptom: An ima_failure_trap might not be generated when an IMA group gets deleted and the group state change might not be sensed by the switch processor.
Workaround: None.
Symptom: When using framing mode STM-16, the show controllers command might report the framing mode as invalid. This should not impact the network.
Workaround: None.
Symptom: DS3 Frame Relay port adapter firmware stops forwarding traffic when 16 channel groups are oversubscribed. The egress port hangs when it receives a frame with a size that is an integral multiple of 48 bytes.
Workaround: None.
Symptom: The standby switch processor (SP) does not take over when an active SP fails to initialize during system bootup.
Workaround: None.
Symptom: The ATM route processor might not forward IP traffic to the default route.
Workaround: None.
Symptom: A bus error exception might occur when adding parties to a root connection.
Workaround: None.
Symptom: If a peer system is reloaded after a route processor switchover, all traffic into the port might be dropped. This prevents well-known VCs from coming up.
Workaround: Enter the shutdown command. To restart the disabled interface, enter the no shutdown command.
Symptom: CBR soft VPs do not come up on route processor switchover.
Workaround: None.
Symptom: An IPX packet containing the wrong length in the IPX header and requiring an encapsulation change causes the ingress port to hang. The switch router must be reloaded.
Workaround: None.
Symptom: The show bridge command might not show all interfaces and the show bridge verbose command might not show all interfaces and hash entries. Entries are not displayed until they are "learned" when traffic is passed through them. If no traffic is ever passed, the entries will not be displayed.
Workaround: None.
Symptom: The Interim Local Management Interface (ILMI) status of shaped and hierarchical tunnel subinterfaces that are down (not shutdown) might get stuck in the restarting state after issuing a shutdown/no shutdown command sequence.
Workaround: Issue a shutdown/no shutdown command sequence on the main interface of the subinterface, or bring the interface up by connecting it to a peer system.
Symptom: Soft PVCs might be disabled on subinterfaces.
Workaround: None.
Symptom: When snooping is enabled on an ATM or ATM-P port, ATM PVC deletion might fail. If the deletion fails, the system does not recognize the ATM PVC deletion failure and deletes the Frame Relay PVC. This causes the ATM PVC and Frame Relay PVC to go out of sync.
Workaround: Before deleting the Frame Relay PVC, disable snooping on the ATM port.
Symptom: The show controller command does not display loopback configurations.
Workaround: None.
Symptom: Operation, administration, and maintenance (OAM) pings might not work after a route processor switchover.
Workaround: None.
Symptom: When a snooping interface that is a higher card/subcard than the snooped interface (for example, interface ATM 0/1/1 snooping interface ATM 0/1/0), the snooping interface might be in an up state instead of in a snooping state. In addition, some of the snooping VCs might not be restored. When entering the shutdown command, the high-order snooping interface might get stuck while in the going down state.
Workaround: None.
Symptom: When OAM is enabled globally and ATM and IP traffic is in the switch, a crash might occur during route processor switchover.
Workaround: None.
Symptom: The ATM interface might show different line codes after a switch processor switchover.
Workaround: Use the show controller command to find the correct line code, which is listed under the line code violation (lcv) count.
Symptom: A no loopback sonet-terminal command issued on an OC-48c interface does not bring the interface down even when no cable is connected to the port.
Workaround: Use the shutdown command to bring down the interface.
Symptom: The primary route processor might loop when a redundancy prepare-for-cpu-removal command is issued.
Workaround: None.
Symptom: Synchronous Digital Hierarchy (SDH) and other standard compliancy is not supported on the OC-48c. Also, LEDs and SONET/SDH alarm signals might not generate properly on OC-48c. When using the show controller command on OC-48c, counters might duplicate.
Workaround: None.
Symptom: When unicast and multicast traffic is present on Fast Ethernet ports, the primary route processor might loop when a redundancy prepare-for-cpu-removal command is issued.
Workaround: None.
Symptom: The show atm status command might show the status of a previously looped back interface as up when it should be showing the status as up only after the line loopback is removed from the interface.
Workaround: None.
Symptom: The display from a show switch fabric command scrolls without stopping when the screen fills. The output just continues to the end of the display.
Workaround: None.
Symptom: The switch router does not correctly handle extended QoS and end-to-end transit delay IEs. This occurs primarily when interoperating with third-party vendor equipment.
Workaround: None.
Symptom: When reprogramming a switch processor FPGA after a route processor switchover, the warning and the confirm prompts might not appear.
Workaround: None.
Symptom: The following error message might appear during switch processor FPGA reprogramming:
    Cat85xx series supports a maximum bridge table aging timer of 600 secs
Workaround: None.
Symptom: Multiple tags for the default route might occur with VC merge.
Workaround: Do not use the tag-switching ip default-route command to assign tags to the default route.
Symptom: The input queue count on a BVI interface configured on the switch router might become larger than queue depth. This will block traffic from the same bridge group.
Workaround: Increase the hold queue on the BVI interface, depending on the rate at which the input queue fills up, or redesign the network to remove BVI.
Symptom: The switch router might crash after displaying the following message:
    ipc_ok2send: Not enough room on 0, 280
Workaround: None.
Symptom: If interface snooping is configured, saved to nvram, and reloaded, the snooping VC might come up in a NO HW RES state.
Workaround: Use the shutdown command to bring down the interface.
Symptom: VP associated code point not supported in between a Catalyst 8540 MSR and a Vswitch on UNI 4.0/IISP interfaces.
Workaround: Use the atm signalling vpci command to configure the value of the VPCI that is carried in the signalling messages in the VP tunnel.
Symptom: The connected route associated with an Ethernet interface might not be in the routing table.
Workaround: Clear the routing entry or the Ethernet interface.
Symptom: When the ipx down command is issued on an interface, the routing flag for IPX remains on.
Workaround: None.
Symptom: The switch can be configured to get its network clock from a constant bit rate (CBR) port without any clock being supplied to the port.
Workaround: None.
Symptom: New SVC or soft PVC calls from a Catalyst 8540 MSR to a Fore ATM switch across a PNNI interface fail to connect. Connections initiated from the Fore switch do not fail.
Workaround: None.
Symptom: Under the heavy stress of a large volume of multicast traffic (6K (S,G) 1MB) the switch router crashes after failing to queue IPC messages.
Workaround: None.
Symptom: A mechanism is needed to troubleshoot and recover from port stuck failures.
Workaround: To recover from a port stuck failure, perform the following steps:
Default behavior
If the switch router is not configured to reset the port upon detecting a port stuck failure the port will be isolated, thus preserving the integrity of the switch router.
Nondefault behavior
If the switch router is configured to reset the port upon detection of a stuck port failure, the switch router will isolate the port from the rest of the functioning ports, and reset the port. This might affect up to three other ports in the case of Fast Ethernet 10/100 modules.
Use the following interface configuration commands to troubleshoot port stuck failures:

Command

Purpose

 epc port-reload


 Enables automatic resetting and reloading of the Ethernet interface module microcode after detecting a port stuck failure.


 epc portstuck-wait seconds


 Specifies the delay before signalling a port stuck failure (from the time the failure is detected). The default is 180 seconds. The range for seconds is 0to1200. A value of 0 seconds causes a port stuck failure to not be detected.

Caution Due to the nature of microcode architecture, do not configure low values for the wait time in the epc portstuck-wait command. The default value of 180 seconds has been carefully chosen, allowing for the hello intervals of protocols such as HSRP, EIGRP, OSPF. Configuring a low value might lead to incorrectly detecting temporary port stuck failures as real port stuck failures and will likely cause temporary connectivity loss. It is highly recommended to keep this value at least at 60 seconds. Lower values are provided to allow for some specific network designs when you can absolutely rule out temporary port stuck failure scenarios, and also as a debugging aid. For most networks, 180 seconds should work very well.
On the Catalyst 8540 MSR, routing with BVI does not work on the 8-port Gigabit Ethernet subinterfaces with the following configuration: 
    Switch(config)# interface GigabitEthernet card/subcard/port.subinterface
Switch(config-if)# encapsulation dot1Q 12 native
Workaround: Reconfigure the dot1Q VLAN as non-native.

Symptom: Variable bit rate (VBR) might allow sustainable cell rate (SCR) oversubscription.
Workaround: None.
Symptom: A Catalyst 8540 MSR might treat the link between the physical interface and the port channel interface as a multidrop link when the MAC address of the members of a port channel differs from the MAC address of the port channel itself.
Workaround: Delete the members of the port channel and then add them back in.
Symptom: The administrative status might be shown as up even when the controller is administratively down.
Workaround: None.
Symptom: Permanent virtual circuit (PVC) creation might fail if the virtual channel identifier (VCI) is greater than 24 bits. On a reload this error might happen when the VCI is greater than 12 bits.
Workaround: None.
Symptom: A Simple Network Management Protocol (SNMP) walk of the ATM virtual channel cross connect table (CCT) might incorrectly show the following for a manually created cross connect: 
    atm MIb.atmMIBObjects.atmVcCrossConnectTable.atmVcCrossConnectEntry. atmVcCrossConnectAdminStatus.4680082.16.41.32.15.9.32 = up(1)
Workaround: None.
Symptom: Inverse multiplexing over ATM (IMA) groups might intermittently fail to come up, especially after reload and on E1 links.
Workaround: Issue the following command on the IMA interfaces:
    (config-if)# fwmon "altrap 00 ff 00 ff 00 ff"
If the group remains down even after issuing this command, this indicates a persisting alarm on the line.
Symptom: When hundreds of TVCs in bidirectional mode are repeatedly configured and unconfigured on a switch router, VC resources might become exhausted.
Workaround: None.
Symptom: PNNI/ILMI VCs are sending out CLP=1 traffic.
Workaround: None.
Symptom: When configuring the Simple Network Management Protocol (SNMP) trap receiver with the snmp-server host command, the following error message might appear on the console of the switch: 
    %Bad OID Failed to create host entry.
Workaround: This error message occurs only when SNMP is initially configured on the switch and it is the first time that the snmp-server host command is issued. If the command is entered again the error message does not appear.
Symptom: PVC and VC status might not be updated in the Frame Relay end of a connection.
Workaround: None.
Symptom: The facility alarm issues a warning when the secondary route processor is brought down, but the warning goes away if the secondary route processor is initialized at ROMMON without booting.
Workaround: None.
Symptom: After booting the image, the switch router might display the following error messages and continue looping:
    00:04:06: %SYS-3-LOGGER_FLUSHED: System was paused for 00:00:34 to ensure console debugging output.
 
00:04:07: ipc_ok2send: Not enough room on 0, 84
 
00:04:07: %LINK-2-INTVULN: In critical region with interrupt level=0, intfc=ATM1/0/1 -Process= "IP-E 00:04:08: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output. IGRP Router", ipl= 0, pid= 153
-Traceback= 600711BC 60355BC4 600762CC 601C4BC8 601C3E38 601C4084 6018CEEC 6017F134 6017FF48 60182818 60194DE8 600989DC 600989C8
00:04:07: ipc_ok2send: Not enough room on 0, 84 
00:04:07: ipc_ok2send: Not enough room on 0, 84 
00:04:07: ipc_ok2send: Not enough room on 0, 84
. . .
Workaround: None.
Symptom: When E1 Frame Relay ports are coming online the following message might be displayed:
    pam_interrupt: unknown pam in slot <slot_number>
This message is harmless and does not affect the functioning of the switch router.
Workaround: None.
Symptom: When the color of an encapsulation is changed on a subinterface, the subinterface does not transition through the spanning tree states. In some situations this might result in spanning tree loops.
Workaround: To prevent looping when changing the subinterface color, delete the subinterface and recreate it with the new encapsulation color.
Symptom: When several IP/IPX ACLs are configured on Ethernet interfaces, a switchover might cause the primary CPU to crash.
Workaround: None.
Symptom: A Catalyst 8540 MSR might have problems with IPX routing using ATM router module ports. Once the LE-ARP entry times out, IPX packets are sent over the BUS. Since the route processor is not aware of the IPX packets anymore, it does not trigger the LE-ARP request and the switch router continues to forward the IPX traffic for given destination over the BUS. This problem negatively impacts IPX performance. IP performance is not affected.
Workaround: Set atm idle-timeout to 0 on all the devices in the affected ELAN before the traffic is started, or move the LES/BUS to a Catalyst 5000 ATM LANE module.
Symptom: HSRP interface tracking may incorrectly determine that a down interface is up when the software reloads.
Workaround: Issue the shutdown/no shutdown commands on the interface.
Symptom: The interface command arp timeout 300 disappears from the running configuration after a reboot.
Workaround: None.
Symptom: On reload after configuring a permanent virtual circuit (PVC), the PVC might be in the down state.
Workaround: Delete and re-install the PVC.
Symptom: If a switch processor switchover occurs before K1 boots up, the switch router might hang or crash.
Workaround: None.
Symptom: If a switchover occurs when route processor traffic exceeds 5 Mbps, causing 100% route processor utilization, the following timeout messages are 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 reenable the ports.
Workaround: Redesign the network to reduce the amount of traffic to the route processor.
Symptom: After a switch processor switchover, the input and output packet counters have invalid values.
Workaround: None.
Symptom: Ethernet interface modules reset during reinitialization after a switch processor switchover.
On a switch processor switchover, Ethernet interface modules behave as if a system reload occurred, and take the same amount of time to reinitialize as they do for a reload. Before the interface modules come up, and a switchover occurs, timeout messages are issued. This happens because the Ethernet ports are initialized through IPC, and halfway through the process the Ethernet interface modules are reset again by the switchover.
Workaround: None.
Symptom: Do not hot swap an active switch processor (SP) module before putting it in standby mode.
If an SP module is currently active while the switch router is running IOS, and the module is removed from the chassis before making it a standby module, the connections might hang. This stops switch traffic after an SP switchover.
Workaround: Before removing an active SP module, make it the standby.
First determine whether the SP module to be removed is currently active using either of the following methods:
If the SP module is active, the active LED on the module is green.
If the SP module is standby, the standby LED on the module is green.
If the SP module is currently the standby, remove it without issuing any commands.
If the SP module is currently active, use the following EXEC command to designate the other two SP modules as the active switch processor modules:
redundancy prefered-switch-card-slots slot#1 slot#2
The range of the slot value is 5 through 7. This prepares the SP module to be removed as the standby module.
Once the prompt returns, ensure that the SP module is the standby by issuing the following command:
show preferred-switch-card-slots
The SP module should no longer be active, and can be safely removed.
The following example shows how to prepare the switch router to safely remove an active SP module from slot 5:
Switch# show preferred-switch-card-slots
The currently preferred switch card slots are slot:5 and slot:7
The currently active switch card slots are slot:5 and slot: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

Symptom: OC-48c SONET is supported but SDH is not.
Workaround: None.
Symptom: If an OC-48c interface module is removed and reinserted on an active switch router when NCPD is enabled, and the clock source is set to the OC-48c interface, the ILMI state remains in waiting/restarting on the OC-48c interface.
Workaround: After the OC-48c interface module is reinserted, issue a shutdown command, followed by a no shutdown, command on the affected OC-48c interface.
Symptom: CBR interfaces might incorrectly come up when configured as structured services, even though no cables are plugged into the ports. This problem might also occur when removing the configuration of the structured services.
Workaround: Remove and reinsert the CES port adapter.
Symptom: Entering shutdown/no shutdown commands on an ATM router module interface, especially when it has several LANE clients configured, can cause the switch router to issue messages similar to the following:
    %LANE-3-LANE_ERROR: lecs finder: ILMI hung on interface ATM1/0/0
This message indicates that an internal timeout occurred. The interface recovers and normal operations are not affected.
Workaround: None.
Symptom: The show interfaces atm-sec0 command always displays zero counter values.
Workaround: None.
Symptom: The switch router might crash when logging messages to a buffer when the switch router is very active.
Workaround: None.
Symptom: If an IPX route goes down in a multiple path topology, the Catalyst 8540 MSR layer might get out of synchronization with the Layer 3 IPX routing table. A lower layer forwarding and switching anomaly might occur if the router first receives a "down" notification for a particular network from the same host that originally notified the router about that network, and then, shortly afterwards, the router receives a good route to the network from another host.
Workaround: None.
Symptom: The switch router sends PIM v2 register messages when PIM v1 is configured.
Workaround: None.
Symptom: The secondary route processor incorrectly displays out-of-sequence messages even though the packets are resent and the sequence is recovered.
Workaround: None.
Symptom: If a Fast Ethernet interface module is installed on an active switch router, cells become stuck in the switch fabric when a route processor module is inserted into the chassis.
Workaround: Upgrade to Fast Ethernet FPGA 3.3 or later.
Symptom: Flash PC cards cannot be formatted on the secondary route processor.
Workaround: Format the Flash PC card on the primary route processor then move it to the secondary route processor.
Symptom: If an 8-port Gigabit Ethernet interface module is installed on the switch router, switch processor switchover is temporarily unsupported. After issuing a redundancy prefered-switch-card-slots command, the switch router displays the following message:
There is 8 Port Gigabit Ethernet PAM in the Chassis, SP switch over is temporary unsupported
Workaround: None.
Symptom: The switch router might crash with a bus error. The interfaces were not restored after the crash.
Workaround: None.
Symptom: Even though the route processor capabilities do not match, the switch router still reports full redundancy when it boots up.
When the secondary route processor resources, such as the amount of DRAM, are equal to or greater than the primary route processor resources, the switch router is fully redundant. However, after a route processor switchover, if the new primary route processor resources are more than those of the new secondary route processor, a fully redundant switch router becomes conditionally redundant and the new primary route processor console displays a message such as the following:
    00:03:14: %COUGAR_EHSA-4-FLASH_MISMATCH: Mismatch in BOOTFLASH SIMM size between Primary and Secondary 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 both route processors on the switch router have the same resources.
Symptom: When copying a file to a Flash PC card on a secondary route processor, the switch router might return control to the user before the copy process is complete. If a reload is done before the image is completely copied, the file might be lost.
Workaround: Enter the dir sec-slotn: command to verify that the image is completely copied before reloading the switch router.
Symptom: IP multicast counters (S,G) might not be accurate.
The microcode maintains 16-bit packet counters for each (S,G) entry, which are polled every 10 seconds. If the input rate for the (S,G) entry is higher than 6.4K packets/second for a 10-second duration, the counters might overrun.
Workaround: None.
Symptom: On an OC-12 interface, the show controllers command might incorrectly show very large numbers of tx and rx counters.
Workaround: None.
Symptom: The show running-config command display contains a reference to the aux 0 port, which is not supported.
Workaround: None.
Symptom: The undebug all command does not disable the debug redundancy all command.
Workaround: Use the no debug all command to disable all debugging activity.
Symptom: If the configuration register value is set to 0x2102 while autobooting, the system might experience a TLB (translational bridging) exception if the system boot image is not specified using the boot system command. The system continues to boot without problems, despite this exception.
Workaround: When the configuration register is set to 0x2102, specify the system boot image to be autobooted using the boot system command. If the system boot image is specified using the boot system tftp command, also specify the bootloader image using the boot bootldr command. After executing these commands, save the configuration in the NVRAM, using the copy running-config startup-config command.
Symptom: All Software Upgrade (system IOS, ATM, FDDI) is broken on Cluster Manager and VSM if the cluster member's management VLAN has no IP address.
Workaround: None.
Symptom: When attempting to reprogram the ROMMON, the switch router sometimes hangs after displaying the following message:
Resetting in 3 seconds
Workaround: Remove and reinsert the route processor module or power cycle the switch router.
Symptom: The debug ncdp packets, debug ncdp errors, and debug ncdp events commands do not display any information when accessing the switch router through the Ethernet port.
Workaround: Access the switch router using the console port.
Symptom: Modem access to the console port requires special settings.
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.
Symptom: The Catalyst 8540 MSR might display a CRC error when it obtains the clock via an OC-3c link from a LightStream 1010 ATM switch and then uses or redistributes the clock over an OC-12c link.
Workaround: Use the internal clock or bring the clock source directly to the Catalyst 8540 MSR.
Symptom: The show ncdp path root command might not print any information when accessing the switch router through the Ethernet port.
Workaround: Access the switch router using the console port.
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. The switch router flushes these PTSEs after they normally age out.
Workaround: None.
Symptom: PVCs exiting the switch router over a hierarchical VP tunnel are not preserved when the route processor switches over.
The switch router stops switching traffic over such PVCs on and after the route processor switchover. The hierarchical VP tunnel remains active, however, and after the route processor switchover the VCs defined over the hierarchical VP tunnel (both PVCs and SVCs) function as expected.
Workaround: None.
Symptom: If no ACL module is present in a slot, the following message appears in the console log on a SP switchover:
    No ACL card in slot
This is an informational message only and has no affect on switch router function.
Workaround: None.
Symptom: Under certain circumstances, the Catalyst 8540 MSR might display inaccurate traffic statistics on NNI or UNI interfaces.
Workaround: None.
Symptom: Despite having enough bandwidth, resource management might reject some soft PVCs.
Workaround: None.
Symptom: After shutting down an ATM router module interface which is a member of a port channel, the interface entry is not removed from the port channel. Since removing a member interface from a port channel does not put the port channel into blocking mode, no loss of connectivity should result.
Workaround: None.
Symptom: When using the Catalyst 8540 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-12c interface modules, interfaces ATM 0/0/0, ATM 0/0/2, ATM 2/0/0, ATM 2/0/2, ATM 9/0/0, ATM 9/0/2, ATM 11/0/0, and ATM 11/0/2 might fail UPC tag mode.
Workaround: Upgrade the switch processor FPGA image to Version 1.5 (fi-c8540-msp.A.1-5) or later.
Symptom: The ILMI keepalive feature resets the interface on the second retry following a link failure. This behavior might occur despite having configured the system to allow up to five retries.
Workaround: None.
Symptom: On a system configured with either both power supplies or only power supply 1, issuing the show hardware, show hardware detail, or show tech-support commands might cause the memory corruption. If this memory corruption occurs and the show subsystem command is 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 you use power supply 0.
Symptom: Alignment correction made while running IPX routing and data packets over dot1q over fec.
Workaround: None.
Symptom: If the switch router is booted with cleared NVRAM, because the switch router is new, or after a write erase command, and the automatic configuration is skipped, the following messages are displayed:
     %Error opening tftp://255.255.255.255/network-confg (Not enough space)
 %Error opening tftp://255.255.255.255/cisconet.cfg (Not enough space)
 %Error opening tftp://255.255.255.255/switch-confg (Not enough space)
 %Error opening tftp://255.255.255.255/ciscortr.cfg (Not enough space)
These messages are harmless and can be ignored. The only effect is an increased boot time of approximately 1 minute.
Workaround: Use the automatic configuration feature upon first boot-up or when the switch router is booted after a write erase command.
Symptom: The digital cross-connect unit (DCU) might malfunction unexpectedly.
Workaround: None.
Symptom: Following a route processor switchover, the switch router might fail to recognize port adapter interfaces associated with a carrier module.
Workaround: Upgrade the carrier module FPGA image to release 1.7 or later.
Symptom: With RMON enabled on Fast Ethernet interfaces, SNMP interface counters begin to grow exponentially. Port utilization might be greater than 100% when the actual utilization might be as low as 1%. This happens with either RMON native or RMON promiscuous. While SNMP counters are erratic, the CLI remains accurate.
Workaround: None.
Symptom: Following a software reload, the Catalyst 8540 MSR might fail unexpectedly with a write bus error. This failure might occur if the system is configured with one route processor, and the switch processor modules are installed in slots 5 and 6 or in slots 6 and 7.
Workaround: Install the switch processor modules in slots 5 and 7.
Symptom: When powering up and booting the switch router with two route processors, or installing a second route processor in a working switch router, the console port of the secondary route processor might display the following error message:
    SECONDARY CPU: *** Failure - Can not sync to other CPUs sync ****
Sys Clock lock and sync failed.
The secondary route processor fails to boot and the switch router is in a non-redundant mode. This problem occurs when the Catalyst 8540 MSR with two route processors and the secondary route processor have an FPGA image version of 4.5 or earlier. To recover, power cycle the switch router or remove and reinsert the secondary route processor.
Workaround: Upgrade the route processor FPGA image to Version 4.6 or later.
Symptom: An IPX packet containing the wrong length in the IPX header and requiring an encapsulation change causes the ingress port to hang. The switch router must be reloaded.
Workaround: None.
Symptom: The squeeze command might result in an error in which the squeeze progress is not displayed. For example:
    ms04_m84_01#squeeze sec-slot0:
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of sec-slot0 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.
Symptom: The Hot Standby Router Protocol (HSRP) over a Bridge Group Virtual Interface (BVI) configuration is not supported if the BVI encompasses LANE interfaces. This configuration is valid and functional only if the BVI encompasses Ethernet interfaces.
Workaround: None.
Symptom: Appletalk is not supported on 8-port Gigabit Ethernet interface module.
Workaround: None.
Symptom: Following a change to a spanning tree, inconsistencies might occur in the bridge members information stored in the Ethernet module interface and the IOS.
Workaround: Use the clear bridge command to purge the bridging cache.
Symptom: After repeatedly entering and exiting global configuration command mode, the system might freeze unexpectedly.
Workaround: None.
Symptom: With the system is configured to autoboot, and 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.
Symptom: A T1 CES interface does not send out a remote alarm indication (RAI) in the reverse direction upon detecting an alarm indication signal (AIS).
Workaround: None.
Symptom: Attempting to format the new Intel 200 Series Flash PC 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 Flash PC card is removed from the switch router.
Workaround: Remove the Flash PC card from the switch router.
Symptom: IPX ping incorrectly shows success during simultaneous pinging.
Workaround: None.
Symptom: The Catalyst 8540 MSR sends an invalid PDU when the counters are cleared.
Workaround: None.
Symptom: The interface delay metric is set inappropriately for port channel interfaces where one or more Gigabit Ethernet interfaces or Fast Ethernet interfaces are grouped into a channel. The delay for a single Gigabit Ethernet interface is 10 microseconds. The delay for a port channel consisting of one or more Gigabit Ethernet interfaces is 100 microseconds. The delay for a single Fast Ethernet interface is 100 microseconds. The delay for a port channel made up of one or more Fast Ethernet interfaces is 1000 microseconds.
This incorrect setting has implications for routing protocols that use interface delay as part of the metric, such as IGRP and EIGRP, and might cause the routing protocol to prefer a route through a single interface over a route through a port channel, all else being equal.
Workaround: Manually configure an appropriate delay on the port channel interface with the delay command.
Symptom: The "Uptime" for the secondary route processor from a show redundancy command might display incorrectly. This problem occurs because the "Uptime" rolls over after about four hours.
Workaround: None.
Symptom: Performing an OIR on the secondary route processor might produce the following error message:
%OC3SUNI: Read diagnostics for ATM1/1/0 failed(1)
Workaround: Reboot the system.
Symptom: Configuring interfaces on line aux 0 might cause the redundancy feature to fail. The primary and secondary route processors will boot, but running the show redundancy command on the primary route processor incorrectly indicates that the secondary route processor is down.
Workaround: Remove all configuration commands from line aux 0 and reboot the switch router.
Symptom: When using FTP to transfer a core file to a server, the switch router might not create an exception dump following a system crash.
Workaround: None.
Symptom: If an interface in subslot 1 of a carrier module is the present active clock source, and an interface in subslot 2 of the same carrier module is the secondary clock source, the clock source of the secondary might be overridden to loop-timed rather than network-derived.
Workaround: None.
Symptom: The soft VCL counter incorrectly reaches its maximum value upon link transition, thus keeping soft VCs from connecting to ports which have incorrect soft VCL numbers.
Workaround: Reload the system.
Symptom: The status LED on the standby switch processor module remains red after boot up.
Workaround: None.
Symptom: When the switch router is booted after a power cycle, the reload reason in the show version command does not indicate that the "System restarted by power-on."
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
Symptom: After performing an OIR on a carrier module, the corresponding port adapter interface counter values displayed in a show interface command might become unreliable.
Workaround: None.
Symptom: When a port adapter is removed from the chassis, the entry in ciscoLS1010SubModuleTable is not deleted.
Workaround: None.
Symptom: Connections to the ATM router module interfaces cannot pass through shaped VP tunnels.
Workaround: Configure hierarchical VP tunnels for ATM router module interface connections.
Symptom: The Catalyst 8540 MSR 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.
Symptom: An unexpected system failure might occur following a show tech-support command when OC-3c interfaces are present. This might also occur with the show controllers command.
Workaround: None.
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.
Symptom: The Catalyst 8540 MSR might not allow you to configure more than 255 VPs, even though the 12-bit VPI allows a maximum of 4095 VPs.
Workaround: None.
Symptom: The 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.
Symptom: On a PNNI signalling link, the Promina 4000 NET switch sends a message that prompts the system to send a CALL PROCEEDING message and then a RELEASE message. The UNI 3.0 specification, section 5.4.5.15, defines a cause code 8a as "VPCI/VCI unacceptable." When the call goes out on a UNI 3.1 interface, this cause code should be mapped to VPI/VCI assignment failure. This mapping does not occur for PNNI links.
Workaround: None.
Symptom: EIGRP updates are missing for some addresses on ATM router module port subinterfaces.
Workaround: In global configuration mode, enter the no auto-summary command followed by auto-summary command.
Symptom: A problem in the reinitialization logic might cause the system to fail unexpectedly when a switch processor module in slot 5 is the standby and the switch processor module in slot 7 fails.
Workaround: Do not configure the switch processor in slot 5 as the standby.
When the system is configured to autoboot, and the configuration register is set to 0x2102, the secondary route processor crashes during autoboot.
Workaround: Upgrade the ROMMON image to release 12.0(4.6)W5(13) or later.
Symptom: 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.
Symptom: The CES ABCD bits are not user configurable when a fault occurs.
Workaround: None.
Symptom: When forwarding a call setup message from one VP tunnel to another, the Catalyst 8540 MSR might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.
Workaround: None.
Symptom: Configuring a channelized E1(CE1) Frame Relay 2.048-Mbps ATM port adapter for clear E1 might cause the linecode violation and LES counters to increment continually.
Workaround: None.
Symptom: atmfAtmLayerConfiguredVCCs might not include the soft PVC count.
If a router connects to an ATM interface on a Catalyst 8540 MSR where soft PVCs are configured, the PVC Discovery feature on the router fails to correctly discover all the configured PVCs and soft PVCs from the switch router. This does not happen if only PVCs are configured.
Workaround: None.
Symptom: Marker cells are not 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 VP tunnels.
Workaround: None.
Symptom: During route processor switchover, LMI times out on peer interfaces.
The Catalyst 8540 MSR requires about a minute to switch over. The Frame Relay interface might take about a minute before it can respond to any LMI activity.
Workaround: To prevent LMI timeouts on peer interface during switchover, configure an LMI timeout longer than the time it takes for the Catalyst 8540 MSR route processor to switch over. Configure lmi-n392dce, lmi-n392dte, lmi-t392dce and lmi-n391dte on the Frame Relay interface so that LMI will not bring down the interface if no LMI activity is seen for about a minute.
Symptom: After issuing a show running-config command several times, the Catalyst 8540 MSR might fail unexpectedly due to a bus error.
Workaround: None.
Symptom: The file system fails to add the secondary NVRAM and secondary RCSF on a route processor switchover.
Workaround: None.
Symptom: No means to change the default active switch processor modules is available.
Workaround: If a Catalyst 8540 MSR has three 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 module in slot 6 comes up as the standby. To change this default, use the following privileged EXEC command:
redundancy preferred-switch-card-slot slot#1 slot#2
Two preferred slots must be specified and they must be unique. The range of the slot value is 5 to 7. If one of the preferred slots selected is not a currently active switch processor module, you are asked whether the system should change the active switch processor modules to the preferred switch processor module. If such a switchover occurs, all the active connections in the system are reinitialized. If you wish to continue, then the preferred switch processor modules become active and the other switch processor module becomes the standby. This configuration remains in effect until one of the active switch processor modules is removed. The preferred switch processor module configuration is preserved across route processor switchovers. However, the preferred switch processor module setting is lost if the system is power cycled or if both route processors are reloaded to ROM monitor mode.
Symptom: Setting the gateway of last resort is delayed on route processor switchover.
The static IP routes take from 1.5 to 2 minutes to take effect on switchover.
Workaround: None.
Symptom: The primary route processor should not be hot swapped.
If a route processor that is currently running IOS is removed from the chassis in a skewed manner, such that the left side of the route processor comes out before the right side does, the traffic through the switch router might stop.
Workaround: There are some precautions to take before removing a route processor module controller from a chassis that is powered-up.
If the route processor module is currently in ROM monitor mode, then it is safe to remove it from the chassis. You can put the route processor in ROM monitor mode from IOS by issuing a reload command if the switch router is not configured to automatically boot. If the switch router is configured to automatically boot, it starts booting IOS again. To ensure that the route processor is in ROM monitor mode before removing it, use the following command:
redundancy prepare-for-cpu-removal
Execute this command on the route processor before removing it. Once this command is 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.
Issue this command after connecting to the console port of the route processor. If the system has a Y cable, then remove the Y cable and obtain a local connection to the route processor before the command is issued. Issue the command only on a route processor that is in IOS mode, even if it is the secondary route processor.
Symptom: Srecord integrity checking is not adequate.
If all the Srecord lines are removed from a functional image file, the file is corrupted and causes problems if downloaded. The reprogram command Srecord integrity checking does not catch this problem.
Workaround: None.
Symptom: Incorrect coding of the information element "call state".
Information element "call state" incorrectly sets the coding standard to 00 (ITU-T coding standard) instead of 11 as specified in the PNNI specification. This can cause compatibility problems with other vendors' implementations.
Workaround: None.
Symptom: On the Catalyst 8540 MSR it is not possible to use a VCI value higher than 8191 for soft VCs and PVCs on the same interface module or port adapter where more than one VCI is configured.
Workaround: Use VCI values lower than 8192.
Symptom: The advertised priority is not updated for PGLs configured to match the advertised priority.
Workaround: None.
Symptom: The show controller command only displays information for even-numbered ports.
The show controller command for all odd-numbered ports in a 16-port OC-3c interface module displays the information for even-numbered ports.
Workaround: None.
Symptom: The rate scheduler allocation (rsAlloc) update is accurately based on granularity of the mantissa value and might lead to oversubscription.
During the CAC process, for pure or partial rate scheduled connections, the rate actually programmed in the hardware might exceed the rate requested. This is particularly visible at very high rates, and is due to the granularity in the mantissa value (which cannot be fractional). However, the CAC allocates in its software structures only the rate requested. This might lead to an oversubscription of the rate scheduler.
This problem occurs at very high VC rates, where the CAC algorithm allocates slightly less than what the rate scheduler is programmed with (the difference is less than .03%).
Workaround: None.
Symptom: Catalyst 8540 MSR crashed with interprocess configuration (IPC) errors on route processor switchover.
The primary route processor constantly issues IPC sequence errors and the secondary crashes during a redundancy force-failover main-cpu command.
Workaround: None.
Symptom: Failed attempts to reprogram a carrier module cause the Catalyst 8540 MSR to hang.
Workaround: None.
Symptom: The switch router rejects calls with extended QoS parameters.
When ATM QoS for CDV is configured and you specify a soft VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft VC does not come up.
Workaround: None.
Symptom: The show hardware command does not display power supply IDPROM details.
Workaround: None.
Symptom: The lane server-bus ethernet command might cause an unexpected exception when issued after deleting LANE clients from the subinterface.
Workaround: None.
Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).
Workaround: None.
Symptom: The switch router rate scheduler rounds down the rates (when converting from bits per second to cells per second) when they should be rounded up.
Workaround: None.
Symptom: When a call setup message traverses a switch router running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.
Workaround: None.
Symptom: The Catalyst 8540 MSR uses backward parameters in QoS IEs for point-to-multipoint calls.
This might cause incompatibility with other vendors' implementations.
Workaround: None.
Symptom: Cell loss occurs between unlike bandwidth interfaces, such as DS3 or T1 and OC-3c, that reside on the same carrier module which has functional image version 1.4 or earlier.
Workaround: Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.
Symptom: The switch router might detect discrepancies between the software configuration and the hardware after a route processor switchover.
Across a route processor switchover, if an outdated (older than and different from the running configuration) start-up configuration synchronization is applied, or if the latest running configuration synchronization fails, then discrepancies might exist between software data structures and hardware programming. Any PVCs are preserved.
Workaround: Use the copy running-config startup-config command before a route processor switchover.
Symptom: Circuit emulation service (CES) might show an interface as UP following a loss of signal (LOS). Also, if the interface is shut down or the uplink ATM is not functioning, CES might fail to send an alarm indication signal (AIS).
Workaround: None.
Symptom: Messages appear when hot swapping a carrier module.
When you hot swap a carrier module into the Catalyst 8540 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 (address0).
Workaround: None.
Symptom: When deleting the secondary route processor's start-up configuration, a CPUHOG message appears on the secondary route processor.
The delete command only removes files. To remove devices, use the erase command.
Workaround: Use the erase command to delete devices instead of the delete command.
Symptom: Due to a bad VCXO, a packet might delay on the switch router indefinitely, causing a software crash.
Workaround: None.
Symptom: CES port LEDs on the Catalyst 8540 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.
Symptom: AAL5 CRC errors are not accounted for at the physical interface.
The show atm interface command does not display CRC errors seen at the physical interface level. These errors are not logged under AAL5 CRC.
Workaround: None.
Symptom: Some tx per-vc counters on both point-to-point and point-to-multipoint connections miscount cells. The cells are transmitted but not counted. The number of missed cells is small relative to the total number of cells counted is approximately 1% in the worst case.
Workaround: Upgrade the switch router feature card FPGA image to release fi-c8540-fc.A.4-17 or later.
Symptom: When you hot swap any interface module with an OC-12c interface module, the correct configuration for the OC-12c interface module in the port mode table does not come up properly.
Workaround: Upgrade the switch router feature card FPGA image to release fi-c8540-fc.A.4-17 or later.
Symptom: In the output of the show atm vc command, all of the packet counters are incorrectly displayed as zero.
Workaround: None.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
When an active VP tunnel subinterface is deleted, a software crash might occur.
Workaround: Shut down the subinterface before deleting it.
Symptom: A software crash might occur on the switch router running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Workaround: None.
Symptom: Online insertion and removal of port adapter modules can result in a bus error.
Workaround: Avoid the online insertion and removal of port adapter modules.
Symptom: OIR INSCARD messages display during boot.
Workaround: None.
Symptom: The Frame Relay port adapter firmware might report CRC errors on a PVC if it receives traffic using the same VPI/VCI/DLCI while the PVC is configured.
The errors only occur while the firmware is still configuring the VC. Once the PVC is configured, the CRC errors stop. Since the frames appear like zero-length AAL5 packets while the firmware is still configuring the VC, the firmware does not increment the discard bytes counter, but does increment the discard frames counter due to the CRC errors.
Workaround: Do not allow traffic to pass on the VC while it is being configured.
Symptom: While toggling the interfaces on the peer switch (LightStream 1010 ATM switch), the following error message is occasionally displayed on the Catalyst 8540 MSR:
    04:09:08: process_cubi_cell_list: cubi_oam_upcall returned an error
This occurs when a LECS is configured on the route processor port along with 10 LES/BUS/LECs on the 10 subinterfaces on the route processor port.
Workaround: None.
Symptom: Point-to-multipoint PVC preservation across a route processor switchover is not fully supported.
If traffic is flowing through a point-to-multipoint connection when a route processor switchover takes place, then some of the leaves of the connection might not be restored properly. Traffic might continue to flow through all the leaves of the connection even after the switchover, but the output of the show atm vc command might show NO HW RESOURCE for some of the leaves of the connection. In the absence of traffic, all the leaves of a point-to-multipoint connection will be restored properly across a route processor switchover.
Workaround: If possible, shut down traffic on all point-to-multipoint connections before a route processor switchover.
Symptom: When running tag switching, no tag is created for the default route.
Workaround: None.
Symptom: The sysConfigName MIB variable value is not set correctly.
If the system is set to autoboot and no explicit boot image is specified, the system boots the default image from the bootflash. In this scenario, the show version command displays the image name as "default image" instead of the actual image name. The MIB variable sysConfigName also returns an empty value.
Workaround: None.
Symptom: Soft VPs and PVPs cannot coexist due to VPI allocation errors.
When creating soft VPs, the VPI value allocated on the switched part of the soft VP path might collide with existing configured PVPs.
Workaround: There are two ways to get the soft VP up:

  • Remove the PVP.

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

Symptom: PNNI does not correctly clean up and release some of its data structures after process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is unavailable until the next reload.
Workaround: None.
Symptom: The PNNI SNMP agent is not able to discover and allow PNNI-related configurations on ATM subinterfaces.
An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.
Workaround: None.
Symptom: Connections might fail when the connect message includes an end-to-end delay IE. A Catalyst 8540 MSR that is an intermediate switch router passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
Examples of these connections include UNI 4.0, CBR, and VBR-rt.
Workaround: None.
Symptom: Reprogramming a network clock module causes a processor reset.
Reprogramming the network clock module on the primary route processor causes the route processor to reload after the download is complete. Power cycle the switch router to make the newly loaded image active.
Workaround: None.
Symptom: Reprogramming a carrier module might cause the Catalyst 8540 MSR to hang and not reboot.
After successfully reprogramming a revision 4.0 carrier module with FPGA 1.4, the Catalyst 8540 MSR might hang. To recover the switch router, remove the carrier module before rebooting.
Workaround: None.
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
Workaround: None.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.
Workaround: None.
Symptom: 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.
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.
Symptom: Tag switching and Tag Discovery Protocol (TDP) might cause memory fragmentation.
While running tag switching with a very large number of destinations, continuous toggling of VC merge (which forces all the TDP sessions to restart) on the switch router for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: When loading a software version 11.3 or later image on a switch router with 11.2 or earlier image, LECs and other LANE components might fail to come up if they are configured using an ATM address whose first 19 bytes are the same as the active ATM address of the switch router.
The ATM address of the switch router along with the first 128 values for its selector byte should be reserved for use by PNNI. Starting with the 11.3 software version, PNNI supports hierarchy and registers an ATM address for all PNNI nodes using the switch router ATM address with various selector byte values.
Workaround: If LANE components fail to come up because their ATM addresses collide with the reserved ATM addresses for PNNI, reconfigure the LANE components using different addresses. It is recommended that LANE applications use the addresses shown by the show lane default-atm-addresses command, which will eliminate this problem.
Symptom: ADD party requests over a VP tunnel do not work.
On a source node, when adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
Symptom: An unnecessary lookup for a network configuration file occurs after a route processor switchover.
When a route processor switchover occurs, the new primary route processor that is taking over might look for configuration files from a network server that might not exist. These network configuration file lookups will timeout. This causes some delay during the switchover process.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port, the switch router returns this internal error message:
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Ignore this message; it does not affect the snooping functionality.
Workaround: None.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the command has been deleted and the structures pertaining to that tunnel have been released.
Workaround: None.
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface might become overwhelmed and start generating the following error message:
     %SONICT-3-INTERNAL_ERROR:  sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck.
Workaround: Issue a shutdown/no shutdown command sequence on the interface.
Symptom: When ATM accounting is enabled, an exception might occur because resources at the destination switch router are not available.
Workaround: None.
Symptom: Another vendor's router running UNI 4.0 cannot connect a VC to a Cisco router running UNI 3.1 by way of a Catalyst 8540 MSR.
Workaround: None.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for guaranteed services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel VC simultaneously, the rate scheduler on the output interface would oversubscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MaxCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: When you set the ROM monitor environment variable to boot a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch router hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch router and send a break character to the switch router within 60 seconds to force it to the ROM monitor prompt. You can then manually reboot the switch router and reconfigure the environment variable.
Symptom: The granularity provided by the switch processor scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic 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.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
Symptom: Open Shortest Path First (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not switch to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch router for the interface that was shut, or a clear ip route command on all the switch routers to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch router that had the closed physical interface.
Symptom: The switch router issues CPU hog messages while setting up a lot of calls.
With a large number of connections installed, a show atm vc command may take longer than 2 seconds to complete. This produces a %SYS-3-CPUHOG error message from the scheduler.
Workaround: If information about a specific VC is desired, to specify the interface and the VPI/VCI needed, use the following EXEC command:
show atm vc interface card/subcard/port vpi vci
Workaround: None.
Symptom: IP host routing is still enabled in the running configuration even though it has been disabled from the CLI.
Workaround: Enable and disable IP host routing and then save the configuration to NVRAM.
Symptom: The ATM switch router does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: If there are multiple parallel paths to the same destination on the ATM switch router with a switch processor feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merged and go out of the switch router as a single VC.
Workaround: None.
Symptom: The Catalyst 8540 MSR Ethernet connection does not receive CDP multicast packets. However, the Catalyst 8540 MSR does send out CDP multicast packets.
Workaround: None.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Workaround: None.
Symptom: SNMP SET to a CES port causes the switch router to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES port adapter, the switch router stops working.
Workaround: None.
Symptom: 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.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels.
The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (through portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
Symptom: The CDP configuration for a LEC cannot be saved to NVRAM.
When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM and does not appear in the show running-config display. CDP is disabled, but the setting reverts to enabled after a reload.
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on the NNI interfaces because of switch router crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch router with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:

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

  • ABR, UBR: no bandwidth is allocated.

Workaround: None.
Symptom: A LECS expects all LESs to establish an individual control VC to the LECS to validate clients.
If different emulated LANs (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages which validates the clients into a single VC.
For example, see the following LES router configuration: 
    atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_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.
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.
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 router.
Workaround: None.
Symptom: Remote defect identification (RDI) cells (sent by an endpoint in response to alarm indication signal [AIS] cells generated at an intermediate switch router with a fault condition on an interface) are not propagated beyond the intermediate switch router. The intermediate switch router removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch router.
Workaround: None.

Related Documentation

The following sections describe the documentation available for the Catalyst 8540 MSR. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules that are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.

The most up-to-date documentation can be found on the Web via Cisco Connection online (CCO) and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.

These release notes should be used in conjunction with the documents listed in these sections.

Platform Documents

Here is a list of the platform-specific documentation available for the Catalyst 8540 MSR:

Software Documents

Here is a list of the software documentation available for the Catalyst 8540 MSR:

Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.

Note   If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.

For service and support for a product purchased directly from Cisco, use CCO.

Software Configuration Tips on the Cisco TAC Home Page

For helpful tips on configuring Cisco products, follow this path on CCO:

Service & Support: Technical Documents (button on left margin)

"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 650-556-8409.

The following sections are provided from the Technical Documents Web page:

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note   If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.





hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Aug 22 14:29:21 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.