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

Release Notes for the Catalyst 8540 MSR for Cisco IOS Release 12.0(3c)W5(9)

May 11, 1999

Catalyst 8540 MSR Cisco IOS Release 12.0(3c)W5(9)

This document describes the features and caveats for Cisco IOS 12.0(3c)W5(9) for the Catalyst 8540 MSR software.

For a list of software caveats that apply to 12.0(3c)W5(9), 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 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 and includes the following sections:

Memory Requirements

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

Hardware Supported

Table 1 lists the hardware modules supported on the Catalyst 8540 MSR Release 12.0(3c)W5(9) and their minimum software release.

Note You can use the Catalyst 8540 CSR line modules in a Catalyst 8540 MSR chassis, with an MSR route processor and switch modules. If you choose to do this, you can use only CSR (Ethernet) line modules, not a mix of both MSR and CSR modules. Additionally, you must load the CSR software image, Cisco IOS Release12.0(1.0)W5(6a) or a later release, on the slot 4 route processor of the MSR. This functionality is not supported on the slot 8 route processor of the MSR.


Table 1: Supported Hardware Modules and Their Minimum Software Requirements (continued)
Part Number Description Minimum Software Requirement

C8540-PWR-AC

C8540 AC Power Supply

W5-7

C8540-PWR-AC/2

C8540 Redundant AC Power Supply

W5-7

C8540-PWR-DC

C8540 DC Power Supply

W5-7

C8540-PWR-DC/2

C8540 Redundant DC Power Supply

W5-7

C8545MSR-MRP4CLK

C8540 Multiservice Route Processor

W5-7

C8545MSR-MRP3CLK

C8540 Multiservice Route Processor Stratum 3

W5-7

UPG-MSR-MRP-3CLK

C8540 Stratum 3 Clock Module Upgrade

W5-7

C8546MSR-MSP-FCL

C8540 Switch Processor with ATM Feature Card

W5-7

C85MS-SCAM-2P

C8540 SuperCAM for LS1010 Port Modules

W5-7

C85MS-4F-OC12SS

C8540 4-port OC-12 single-mode fiber line module

W5-7

C85MS-4F-OC12MM

C8540 4-port OC-12 multimode fiber line module

W5-7

C85MS-4E1-FRR548

C8540 4-port CEI Frame Relay port adapter

W5-9

C85MS-1DS3-FRBNC

C8540 1-port CDS3 Frame Relay port adapter

W5-9

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

Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.

Other Firmware Code

This section describes the firmware code installed on an interface that may be updated in the field.

Table 2 lists the port adapters and the firmware that may be updated in the field.


Table 2: Interfaces Supporting Field Upgrade and Version
Interface, Module, or Port Adapter Type Product Name Firmware Filename

CPU

Multiservice Route Processor

fi-c8540-rp.A.4-4

Network Clock Module

Stratum 3 Clock Module Upgrade

fi-c8540-nclk.A.8-0

Switch Card

Multiservice Switch Processor

fi-c8540-msp.A.1-4

Switch Processor Feature Card

MSP with ATM FC

fi-c8540-fc.A.4-17

SuperCAM

SuperCAM for ATM PAMs

fi-c8540-scam.A.1-5

OC motherboard

4-port OC-12 SMF-IR

fi-c8540-oc-mb.A.5-4

OC12 daughter card

4-port OC-12 SMF-IR, 4-port OC-12 MMF

fi-c8540-oc12.A.5-2

Rommon

ROM Monitor

COUGAR_RM.120-0.19.W5.5.srec

OC3 daughter card

16-port OC-3 MMF

fi-c8540-oc3.A.1-21

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

Feature Set Tables

The Cisco IOS 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. The following section lists the features supported by the feature set.

Table 3 lists the Cisco IOS software feature sets available for the Catalyst 8540 MSR.


Table 3: Feature Sets Supported by the Catalyst 8540 MSR (continued)
Feature Set 12.0(3c)W5(9) 12.0(1a)W5(7b) 12.0(1a)W5(7a)

Left-justified E.164 AFI support

x

x

x

SNMP1

x

x

x

Asynchronous support

x

x

x

PPP2 (SLIP3/PPP)

x

x

x

IP4

x

x

x

NTP5

x

x

x

TACACS+6

x

x

x

Telnet

x

x

x

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

x

x

x

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

x

x

x

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

x

x

x

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

x

x

x

Multipoint-to-point UNI signaling

x

x

x

Soft VCCs and VPCs

x

x

x

VP tunneling

x

x

x

VPI/VCI range support in ILMI 4.0

x

x

x

PNNI hierarchy

x

x

x

ILMI10 version 4.0

x

x

x

IISP11

x

x

x

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

x

x

x

ATM ARP17 server on Route Processor

x

x

x

ATM ARP client on Route Processor

x

x

x

ATM tag switch router (TSR)

x

x

x

Port snooping

x

x

x

OAM18 F4 and F5

x

x

x

E.164 address translation

x

x

x

E.164 autoconversion

x

x

x

Circuit emulation

x

x

x

ATM access lists

x

x

x

ATM accounting

x

x

x

ATM RMON19

x

x

x

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

x

x

x

Shaped VP tunnels for CBR20 traffic

x

x

x

Substitution of other service categories in shaped VP tunnels

x

x

x

Dual leaky bucket policing

x

x

x

Scheduler/Service Class/PVC configuration

x

x

x

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

x

x

x

Network clocking enhancements for smooth switchover

x

x

x

Per-VC or per-VP nondisruptive snooping

x

x

x

Support for non-zero MCR21 on ABR22 connections

x

x

x

Access lists on ILMI registration

x

x

x

CUGs

x

x

x

ATM soft restart

x

x

x

ATM accounting enhancements

x

x

x

CISCO-SYSLOG-MIB support

x

x

x

CISCO-CONFIG-COPY-MIB support

x

x

x

Signaling diagnostics and MIB23

x

x

x

Supplemental AToM MIB

x

x

x

Hierarchical VP tunnels

x

x

x

Remote logging for accounting

x

x

x

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

x

x

x

PNNI complex node representation

x

x

x

PNNI explicit paths

x

PNNI alternate link selection

x

Tag switching CoS

x

Network Clock Distribution Protocol

x

Simple Gateway Control Protocol

x

Switch redundancy

x

CPU redundancy: PVP/PVC/VP tunnel preservation

x

12-bit VPI

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

New and Changed Information

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

New Features in Release 12.0(3c)W5(9)

This section lists some of the new features available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(3c)W5(9) software.

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

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

There are no new features being added for release 12.0(1a)W5(7b).

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

This section lists some of the new features available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(1a)W5(7a) software.

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

Important Notes

Note the following:

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

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


Table 4: 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

Caveats

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

Note There were no caveats corrected for Cisco IOS Release 12.0(1a)W5(7a) because this was the first release of the software for the Catalyst 8540 MSR.


Table 5: Release Caveats and Caveats Corrected Reference  
DDTS Number Software Release Software Release Software Release
12.0(3c)W5(9) 12.0(1a)W5(7b) 12.0(1a)W5(7a)
Corrected Caveat Corrected Caveat Corrected Caveat

CSCdi55937

x

x

x

CSCdi74229

x

x

x

CSCdi83275

x

x

x

CSCdi92142

x

x

x

CSCdj01016

x

x

x

CSCdj10889

x

x

x

CSCdj11070

x

x

x

CSCdj13565

x

x

x

CSCdj18430

x

x

x

CSCdj18583

x

x

x

CSCdj31762

x

x

x

CSCdj42967

x

x

x

CSCdj47998

x

x

x

CSCdj68412

x

x

x

CSCdj71109

x

x

x

CSCdj78305

x

x

x

CSCdj80396

x

x

x

CSCdj82930

x

x

x

CSCdj84344

x

x

x

CSCdj84379

x

x

x

CSCdj85853

x

x

x

CSCdk07378

x

x

x

CSCdk17977

x

x

x

CSCdk22484

x

x

x

CSCdk22791

x

x

x

CSCdk26482

x

x

x

CSCdk27725

x

x

x

CSCdk30912

x

CSCdk33601

x

x

x

CSCdk47516

x

x

x

CSCdk52436

x

CSCdk57536

x

CSCdk62547

x

x

x

CSCdk69639

x

x

x

CSCdk71268

x

x

x

CSCdk71688

x

x

x

CSCdk76280

x

x

x

CSCdk77032

x

x

x

CSCdk79426

x

CSCdk78469

x

x

x

CSCdk80021

x

CSCdk82708

x

x

x

CSCdk83334

x

CSCdk87118

x

CSCdk89079

x

x

CSCdk89501

x

x

CSCdk90091

x

x

x

CSCdk90147

x

x

x

CSCdk91364

x

x

CSCdk92661

x

x

CSCdk92832

x

x

x

CSCdm04013

x

x

x

CSCdm05084

x

CSCdm05738

x

x

x

CSCdm07703

x

CSCdm07857

x

x

x

CSCdm11864

x

CSCdm12694

x

x

x

CSCdm15900

x

x

x

CSCdm19018

x

x

x

CSCdm19073

x

x

x

CSCdm19670

x

CSCdm20257

x

x

x

CSCdm23212

x

x

x

CSCdm23579

x

x

x

CSCdm24192

x

x

x

CSCdm24385

x

CSCdm25175

x

CSCdm29503

x

CSCdm29529

x

CSCdm29650

x

x

x

CSCdm29939

x

CSCdm30009

x

x

x

CSCdm30023

x

CSCdm30269

x

x

x

CSCdm30294

x

CSCdm32678

x

CSCdm33737

x

Cisco IOS Release 12.0(3c)W5(9) Caveats Corrected

Symptom: SNMP SET to a CES port causes the switch to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.
Symptom: The Catalyst 8540 MSR Ethernet connection does not receive CDP multicast packets. However, the Catalyst 8540 MSR does send out CDP multicast packets.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Symptom: Another vendor's router, when running UNI 4.0, cannot connect a VC to a Cisco router, which runs UNI 3.1, by way of a Catalyst 8540 MSR.
Symptom: ATM Accounting: Exception in validblock_diagnose because resources at destination switch were not available.
Symptom: When a large amount of data is sent out of the ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck.
Symptom: ADD party over tunnel does not work.
On a source node, when adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.
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.
Symptom: Reprogramming a SCAM caused the Catalyst 8540 MSR to hang and not reboot.
After successfully reprogramming a revision 4.0 SCAM with FPGA 1.4, the Catalyst 8540 MSR might hang. Power-cycling was not successful in rebooting until the SCAM was removed.
Symptom: Connections where end-to-end delay IE is included in the connect message might fail. Examples of these connections include UNI40, CBR, and UBR-rt.
A Catalyst 8540 MSR that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
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.
Symptom: PNNI does not clean up and release some of its data structures properly, following process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is lost until the next reload.
Symptom: When running tag switching, no tag is created for the default route.
Symptom: A software crash might occur on the switch running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
Symptom: Some tx per-vc counters on both point-to-point and point-to-multipoint connections miscount cells. The cells are transmitted but not counted. The number of missed cells is small relative to the total number of cells counted (approximately 1% in the worst case).
Upgrade the Switch Feature Card FPGA image to release fi-c8540-fc.A.4-17 or later.
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.
Symptom: Due to a bad VCXO, a packet might delay on the switch indefinitely and cause a software crash.
Symptom: Messages appear when hot swapping an OC-12 port adapter.
When you hot swap an OC-12 port adapter into the Catalyst 8540 MSR chassis, traceback messages such as the following appear on the console of the secondary route processor. These messages are harmless and can be ignored.
IDPROM in slot 10 not properly programmed
IDPROM in slot 12 not properly programmed
01:01:55: %SCHED-2-WATCH: Attempt to lock uninitialized watched semaphore (address 0).
Symptom: Under certain circumstances, cell loss occurs between unlike bandwidth interfaces that reside on the same carrier module.
Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.
Symptom: The Catalyst 8540 MSR switch uses backward parameters in QoS IE for point-to-multipoint calls.
This might cause incompatibility with other vendors' implementations.
Symptom: When a call setup traverses a switch running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.
Symptom: The granularity of the switch's rate scheduler is such that rates are rounded down (when converting from bits per second to cells per second) when in fact they should be rounded up.
Symptom: Under certain circumstances, the lane server-bus ethernet command can cause an unexpected exception.
Symptom: show hardware command does not display power supply IDPROM details.
The show hardware command should include the details of IDPROM information in the power supplies.
Symptom: The switch rejects calls with extended QoS parameters.
When ATM QoS for CDV is configured and you specify a soft-VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft-VC does not come up .
Symptom: Failed attempts to reprogram a SCAM cause the Catalyst 8540 MSR to hang.
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.
Symptom: Primary route processor should not be hot swapped.
There are some precautions that need to be taken before removing a route processor module controller from a chassis that is powered-up:
If a route processor that is currently running IOS is removed from the chassis in a skewed manner, such that the left side of the route processor comes out before the right side does, the traffic through the switch might stop.
If the route processor module that is being removed is currently in ROM monitor mode, then it is safe to remove it from the chassis.
One way to get the system to ROM monitor mode from IOS is to issue a reload command. This will work if the system is not configured to automatically boot. If the system is configured to automatically boot, it starts booting IOS again. Since the route processor must be in ROM monitor mode before removing it, the following command has been added to take to the system from the IOS prompt to the ROM monitor mode prompt:
redundancy prepare-for-cpu-removal
One must execute this command on the route processor before removing it. Once this command is issued the route processor will go to ROM monitor mode and stay there even if the system is configured to automatically boot. At this point it is safe to remove the route processor from the system.
It is important to note that the command must be executed after connecting to the console port of the route processor being removed. If the system has a Y cable, then the Y cable must be removed and a local connection to the route processor being removed must be obtained before the command is issued. The command must be issued on a route processor that is in IOS mode, even if it is the secondary route processor.
Symptom: No means to change the default active switch cards is available.
If a Catalyst 8540 MSR has 3 switch cards, then by default the switch cards in slots 5 and 7 come up as the active switch cards and the card in slot 6 comes up as the standby switch card. To change this default, use the following privileged EXEC command:
redundancy preferred-switch-card-slot <slot#1> <slot#2>
Two preferred slots must be specified and they should be unique. The range of the slot value is 5 to 7. If one of the preferred slots selected is not a currently active switch card, you are asked if the system should change the active switch cards to the preferred switch cards. If such a switchover occurs, all the active connections in the system will be reinitialized. If you wish to continue, then the preferred switch cards become active and the other switch card becomes the standby. This configuration will remain in effect until one of the active switch cards is removed. The preferred switch card configuration is preserved across route processor switchovers. However, the preferred switch cards setting will be lost if the system is power cycled or if both route processors are reloaded to ROM monitor mode.

Cisco IOS Release 12.0(3c)W5(9) Caveats

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

Symptom: Remote defect identification (RDI) cells sent by an endpoint in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
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: A LECS expects all LES's to establish an individual control VC to the LECS to validate clients.
If different emulated Local Area Networks (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: CDP config cannot be saved to NVRAM for the LEC.
When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM (it also does not show up when doing a write term). The disabling does work, but you lose it again after a reload.
Workaround: None.
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 cell count reported on a snooped interface is twice the actual number of cells transmitted.
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: 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: If there are multiple parallel paths to the same destination on the ATM switch with a switch processor feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable IP routing and then save the configuration to NVRAM.
Symptom: CPU hog while setting up a lot of calls.
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 get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces of the switch which had the closed physical interface to bring everything back up.
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: Refer to the DDTs for information on how to make a conversion of a requested rate to the actual rate.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port, the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Workaround: These messages can be ignored; they do not affect the snooping functionality.
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: Tag switching and Tag Discovery Protocol (TDP) memory fragmentation
While running tag switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: On a Catalyst 8540 MSR configured with 32MB RAM, IPC traffic between the port adapter driver and the firmware can experince a transient failure when port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if its given a reset after waiting for about 2 minutes.
This IPC failure due to unexpected firmware crash under heavy load does not occur on a Catalyst 8540 MSR system configured with 64 MB RAM.
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: Reprogramming a network clock module causes a processor reset.
Reprogramming the network clock module on the primary route processor causes the route processor to reload after the download is complete. The system needs to be power-cycled before the newly loaded image becomes active.
Workaround: None.
Symptom: Soft VP and PVP cannot coexist due to VPI allocation errors.
When creating soft VPs, the VPI value allocated on the switched part of the soft VP path might collide with existing configured PVP.
Workaround: There are two ways to get the soft VP up:
Symptom: sysConfigName variable value not set correctly.
If the system is set to autoboot and no explicit boot image is specified, the system boots the default image from the bootflash. In this scenario, the show version command displays the image name as "default image" instead of the actual image name. The MIB variable sysConfigName also returns an empty value.
Workaround: None.
Symptom: Point-to-multipoint PVC preservation across a route processor switchover is not fully supported.
If traffic is flowing through a point-to-multipoint connection when a route processor switchover takes place, then it is possible that some of the leaves of the connection will not be restored properly. Traffic might continue to flow through all the leaves of the connection even after the switchover, but the output of the show atm vc command might show NO HW RESOURCE for some of the leaves of the connection. In the absence of traffic, all the leaves of a point-to-multipoint connection will be restored properly across a route processor switchover.
Work-around: If possible, shut down traffic on all point-to-multipoint connections before a route processor switchover.
Symptom: While toggling the interfaces on the peer switch (LightStream 1010 ATM switch), the following error messages is occasionally displayed on the Catalyst 8540 MSR:
04:09:08: process_cubi_cell_list: cubi_oam_upcall returned an error
This occurs when LECS is configured on the route processor port along with 10 LES/BUS/clients on the 10 subinterfaces on the route processor port.
Workaround: None.
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 conected to the port LED, the status on the LightStream 1010 ATM switch will be:
S1=red; S2=red; CD=off;
When nothing is conected to the CBR port, the LED status on the Catalyst 8540 MSR will be:
S1=red; S2=red; CD=green;
Workaround: None.
Symptom: On deleting the secondary route processor's startup configuration, a CPUHOG message appears on the secondary route processor.
The delete command for devices is no longer supported. This is only for files. However, the erase command can be used.
Workaround: None.
Symptom: Detect discrepancies between the software configuration and the hardware after a route processor switchover.
Across a route processor switchover, if an outdated (older than and different from the running configuration) startup configuration sync is applied, or if the latest running configuration sync fails, then, although PVCs can be preserved, discrepancies might exist between software data structures and hardware programming.
Workaround: Use the copy running-config startup-config command before a route processor switchover.
Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).
Workaround: None.
Symptom: Catalyst 8540 MSR crashed with IPC errors on switchover.
Primary constantly issues IPC sequence errors and the secondary crashes during a redundancy force-failover main-cpu command.
Workaround: None.
Symptom: Update rsAlloc accurately based on granularity of the mantissa value.
During the CAC process, for pure or partial rate scheduled connections, the rate actually programmed in the hardware might exceed the rate requested. This is particulary 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: The show controller command only displays information for even-numbered ports.
The show controller command for all odd-numbered ports in a 16-port OC-3 SPAM displays the information for even-numbered ports.
Workaround: None.
Symptom: Advertised priority not updated for PGL if configured to match advertised priority.
Workaround: None.
On the Catalyst 8540 MSR, under certain conditions, it is not possible to use a VCI value higher than 8191 for SoftVCs and PVCs.
Workaround: Use a VCI value lower than 9192.
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: Setting the gateway of last resort is delayed on switchover.
The static ip routes take from 1.5 to 2 minutes to take effect on switchover.
Workaround: None
Symptom: File system prefix exits tracebacks on switchover.
Workaround: None
Symptom: While switching the route processor over, LMI times out on the peer interface.
At present, the Catalyst 8540 MSR requires about a minute to switch. The frame-relay interface might take about a minute before it can respond to any LMI activity.
Workaround: To prevent LMI timeouts on peer interface during switchover, configure the LMI timeout to be larger than the time it takes for Catalyst 8540 MSR route processor to switchover. Configure lmi-n392dce, lmi-n392dte, lmi-t392dce and lmi-n391dte on the frame-relay interface, such that LMI will not bring down the interface if no LMI activity is seen for about a minute.
Symptom: Marker cells are not being drained after shut/no shut of the interfaces.
Under stress conditions, if there are several hierarchical VP tunnels configured and if the tunnel interfaces are transitioned several times, cells might stay in the switch fabric.
This does not occur on interfaces without hierarchical tunnels.
Workaround: None.

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

Symptom: OIR INSCARD messages display during boot.
Symptom: Online insertion and removal of port adapter modules can result in a bus error.
Symptom: In the output of the show atm vc command, all of the packet counters are incorrectly displayed as zero.
Symptom: When you hot swap any port adapter module with an OC-12 interface module, the correct configuration for the OC-12 interface module in the port mode table does not come up properly.

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

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

The following caveats have been identified for this release of the Catalyst 8540 MSR software:

Symptom: Remote defect identification (RDI) cells sent by an endpoint in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
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: A LECS expects all LES's to establish an individual control VC to the LECS to validate clients.
If different emulated Local Area Networks (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validates the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: CDP config cannot be saved to NVRAM for the LEC.
When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM (it also does not show up when doing a write term). The disabling does work, but you lose it again after a reload.
Workaround: None.
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 cell count reported on a snooped interface is twice the actual number of cells transmitted.
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: SNMP SET to a CES port causes the switch to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.
Workaround: None.
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: 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: If there are multiple parallel paths to the same destination on the ATM switch with a switch processor feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable IP routing and then save the configuration to NVRAM.
Symptom: CPU hog while setting up a lot of calls.
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 get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
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: 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: Refer to the DDTs for information on how to make a conversion of a requested rate to the actual rate.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: Another vendor's router, when running UNI 4.0, cannot connect a VC to a Cisco router, which runs UNI 3.1, by way of a Catalyst 8540 MSR.
Workaround: None.
Symptom: ATM Accounting : Exception in validblock_diagnose because resources at destination switch were not available.
Workaround: None.
Symptom: When a large amount of data is sent out of the ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck.
Workaround: Issue a shut/no shut command sequence on the interface.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Workaround: These messages can be ignored; they do not affect the snooping functionality.
Symptom: ADD party over tunnel does not work.
On a source node, when adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
Symptom: Tag switching and Tag Discovery Protocol (TDP) memory fragmentation
While running tag switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.
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: Reprogramming a SCAM caused the Catalyst 8540 MSR to hang and not reboot.
After successfully reprogramming a revision 4.0 SCAM with FPGA 1.4, the Catalyst 8540 MSR might hang. Power-cycling was not successful in rebooting until the SCAM was removed.
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. The system needs to be power-cycled before the newly loaded image becomes active.
Workaround: None.
Symptom: Connections where end-to-end delay IE is included in the connect message might fail. Examples of these connections include UNI40, CBR, and UBR-rt.
A Catalyst 8540 MSR that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
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: PNNI does not clean up and release some of its data structures properly, following process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is lost until the next reload.
Workaround: None.
Symptom: When running tag switching, no tag is created for the default route.
Workaround: None.
Symptom: A software crash might occur on the switch running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Workaround: None.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
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 Feature Card FPGA image to release fi-c8540-fc.A.4-17 or later.
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: Due to a bad VCXO, a packet might delay on the switch indefinitely, causing a software crash.
Workaround: None.
Symptom: Messages appear when hot swapping a OC-12 port adapter.
When you hot swap a OC-12 port adapter into the Catalyst 8540 MSR chassis, traceback messages such as the following appear on the console of the secondary route processor. These messages are harmless and can be ignored.
IDPROM in slot 10 not properly programmed
IDPROM in slot 12 not properly programmed
01:01:55: %SCHED-2-WATCH: Attempt to lock uninitialized watched semaphore (address 0).
Workaround: None.
Symptom: Under certain circumstances, cell loss occurs between unlike bandwidth interfaces that reside on the same carrier module.
Workaround: Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.
Symptom: The Catalyst 8540 MSR switch uses backward parameters in QoS IE for point-to-multipoint calls.
This might cause incompatibility with other vendors' implementations.
Wordaround: None.
Symptom: When a call setup traverses a switch running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.
Wordaround: None.
Symptom: The granularity of the switch's rate scheduler is such that rates are rounded down (when converting from bits per second to cells per second) when in fact they should be rounded up.
Workaround: None.
Symptom: Under certain circumstances, the lane server-bus ethernet command can cause an unexpected exception.
Workaround: None.
Symptom: show hardware command does not display power supply IDPROM details.
The show hardware command should include the details of IDPROM information in the power supplies.
Workaround: None.
Symptom: The switch rejects calls with extended QoS parameters.
When ATM QoS for CDV is configured and you specify a soft-VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft-VC does not come up.
Workaround: None.
Symptom: Failed attempts to reprogram a SCAM cause the Catalyst 8540 MSR to hang.
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: Primary route processor should not be hot swapped.
Workaround: None.
Symptom: No means to change the default active switch cards is available.
Workaround: None.

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

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

The following caveats have been identified for this release of the Catalyst 8540 MSR software:

Symptom: Remote defect identification (RDI) cells sent by an endpoint in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
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: A LECS expects all LES's to establish an individual control VC to the LECS to validate clients.
If different emulated Local Area Networks (ELANs) are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: CDP config cannot be saved to NVRAM for the LEC.
When disabling CDP on the atm0.x interface, which has been configured as a LEC, the information is not saved to NVRAM (it also does not show up when doing a write term). The disabling does work, but you lose it again after a reload.
Workaround: None.
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 cell count reported on a snooped interface is twice the actual number of cells transmitted.
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: SNMP SET to a CES port causes the switch to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.
Workaround: None.
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: 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: If there are multiple parallel paths to the same destination on the ATM switch with a switch processor feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable IP routing and then save the configuration to NVRAM.
Symptom: CPU hog while setting up a lot of calls.
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 get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
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: 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: Refer to the DDTs for information on how to make a conversion of a requested rate to the actual rate.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: Another vendor's router, when running UNI 4.0, cannot connect a VC to a Cisco router, which runs UNI 3.1, by way of a Catalyst 8540 MSR.
Workaround: None.
Symptom: ATM Accounting : Exception in validblock_diagnose because resources at destination switch were not available.
Workaround: None.
Symptom: When a large amount of data is sent out of the ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck.
Workaround: Issue a shut/no shut command sequence on the interface.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Workaround: These messages can be ignored; they do not affect the snooping functionality.
Symptom: ADD party over tunnel does not work.
On a source node, when adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
Symptom: Tag switching and Tag Discovery Protocol (TDP): memory fragmentation
While running tag-switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM port adapters and CES port adapters.
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: Reprogramming a SCAM caused the Catalyst 8540 MSR to hang and not reboot.
After successfully reprogramming a revision 4.0 SCAM with FPGA 1.4, the Catalyst 8540 MSR might hang. Power-cycling was not successful in rebooting until the SCAM was removed.
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. The system needs to be power-cycled before the newly loaded image becomes active.
Workaround: None.
Symptom: Connections where end-to-end delay IE is included in the connect message might fail. Examples of these connections include UNI40, CBR, and UBR-rt.
A Catalyst 8540 MSR that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
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: PNNI does not clean up and release some of its data structures properly, following process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is lost until the next reload.
Workaround: None.
Symptom: When running tag switching, no tag is created for the default route.
Workaround: None.
Symptom: OIR INSCARD messages display during boot.
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: A software crash might occur on the switch running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Workaround: None.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
Workaround: None.
Symptom: In the output of the show atm vc command, all of the packet counters are incorrectly displayed as zero.
Workaround: None.
Symptom: When you hot swap any port adapter module with an OC-12 interface module, the correct configuration for the OC-12 interface module in the port mode table does not come up properly.
Workaround: Upgrade the Switch Feature Card FPGA image to release fi-c8540-fc.A.4-17 or later.
Symptom: Some tx per-vc counters on both point-to-point and point-to-multipoint connections miscount cells. The cells are transmitted but not counted. The number of missed cells is small relative to the total number of cells counted (approximately 1% in the worst case).
Workaround: Upgrade the Switch Feature Card FPGA image to release fi-c8540-fc.A.4-17 or later.
CSCdm04013
Symptom: AAL5 CRC errors are not accounted for at the physical interface.
The show atm interface command does not display CRC errors seen at the physical interface level. These errors are not logged under AAL5 CRC.
Workaround: None.
Symptom: Due to a bad VCXO, a packet might delay on the switch indefinitely and cause a software crash.
Workaround: None
Symptom: Messages appear when hot swapping a OC-12 port adapter.
When you hot swap a OC-12 port adapter into the Catalyst 8540 MSR chassis, traceback messages such as the following appear on the console of the secondary route processor. These messages are harmless and can be ignored.
IDPROM in slot 10 not properly programmed
IDPROM in slot 12 not properly programmed
01:01:55: %SCHED-2-WATCH: Attempt to lock uninitialized watched semaphore (address 0).
Workaround: None.
Symptom: Under certain circumstances, cell loss occurs between unlike bandwidth interfaces that reside on the same carrier module.
Workaround: Upgrade the carrier module FPGA image to release fi-c8540-scam.A.1-5 or later.
Symptom: The Catalyst 8540 MSR switch uses backward parameters in QoS IE for point-to-multipoint calls.
This might cause incompatibility with other vendors' implementations.
Wordaround: None.
Symptom: When a call setup traverses a switch running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.
Workaround: None.
Symptom: The granularity of the switch's rate scheduler is such that rates are rounded down (when converting from bits per second to cells per second) when in fact they should be rounded up.
Workaround: None.
Symptom: Under certain circumstances, the lane server-bus ethernet command can cause an unexpected exception.
Workaround: None.
Symptom: show hardware command does not display power supply IDPROM details.
The show hardware command should include the details of IDPROM information in the power supplies.
Workaround: None.
Symptom: The switch rejects calls with extended QoS parameters.
When ATM QoS for CDV is configured and you specify a soft-VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft-VC does not come up.
Workaround: None.
Symptom: Failed attempts to reprogram a SCAM cause the Catalyst 8540 MSR to hang.
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: Primary route processor should not be hot swapped.
Workaround: None.
Symptom: No means to change the default active switch cards is available.
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:

Software & Support: Technical Tips (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-596-4408.

The following sections are provided from the Technical Tips 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 Sep 14 19:31:01 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.