Guest

Cisco Catalyst 8500 Series Multiservice Switch Routers

Release Notes for the Catalyst 8510 and the LightStream 1010 Switch for Cisco IOS Release 12.1(26)EB2, Part 2: Caveats

  • Viewing Options

  • PDF (639.6 KB)
  • Feedback
Release Notes for the Catalyst 8510 and the LightStream 1010 Switch for Cisco IOS Release 12.1(26)EB2, Part 2: Caveats

Table Of Contents

Release Notes for the Catalyst 8510 and the LightStream 1010 Switch for Cisco IOS Release 12.1(26)EB2, Part 2: Caveats

How to Use This Document

If You Need More Information

Open Caveats—Cisco IOS Release 12.1(26)EB2

Open Caveats—Cisco IOS Release 12.1(26)EB1

Resolved Caveats—Cisco IOS Release 12.1(26)EB2

Resolved Caveats—Cisco IOS Release 12.1(26)EB1

Resolved Caveats—Cisco IOS Release 12.1(26)EB

Resolved Caveats—Cisco IOS Release 12.1(23)EB

Resolved Caveats—Cisco IOS Release 12.1(22)EB

Resolved Caveats—Cisco IOS Release 12.1(22)E

Resolved Caveats—Cisco IOS Release 12.1(20)EB

Resolved Caveats—Cisco IOS Release 12.1(20)E

Resolved Caveats—Cisco IOS Release 12.1(19)E2

Resolved Caveats—Cisco IOS Release 12.1(19)E

Resolved Caveats—Cisco IOS Release 12.1(14)EB1

Resolved Caveats—Cisco IOS Release 12.1(14)EB

Resolved Caveats—Cisco IOS Release 12.1(14)E1

Resolved Caveats—Cisco IOS Release 12.1(13)EB1

Resolved Caveats—Cisco IOS Release 12.1(13)E1

Resolved Caveats—Cisco IOS Release 12.1(12c)EY

Resolved Caveats—Cisco IOS Release 12.1(12c)E1

Resolved Caveats—Cisco IOS Release 12.1(12c)E

Resolved Caveats—Cisco IOS Release 12.1(11b)E1

Resolved Caveats—Cisco IOS Release 12.1(11b)E

Resolved Caveats—Cisco IOS Release 12.1(10)EY

Resolved Caveats—Cisco IOS Release 12.1(10)E

Resolved Caveats—Cisco IOS Release 12.1(7a)EY1

Resolved Caveats—Cisco IOS Release 12.1(7a)EY

Resolved Caveats—Cisco IOS Release 12.1(6)EY

Resolved Caveats—Cisco IOS Release 12.1(5)EY1

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for the Catalyst 8510 and the LightStream 1010 Switch for Cisco IOS Release 12.1(26)EB2, Part 2: Caveats


August 02, 2007

Catalyst 8510 and LightStream 1010 Switch for Cisco IOS Release 12.1(26)EB2

Text Part Number: OL-14425-01

This document lists severity 1 and 2 caveats and select severity 3 caveats from Cisco IOS Release 12.1(5a)EY up to and including Release 12.1(26)EB2. Caveats describe unexpected behavior in Cisco IOS release software for the Catalyst 8510 and the LightStream 1010 switch. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.

To improve this document, we would appreciate your comments. If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically at http://www.cisco.com/feedback/ or you can contact caveats-doc@cisco.com.

For more information, see the "Documentation Feedback" section.


Note All information pertains to both the Catalyst 8510 and LightStream 1010 switch platforms, unless differences between the platforms are noted in the text.


How to Use This Document

This document describes open and resolved severity 1 and 2 caveats and select severity 3 caveats:

The "Open Caveats" section lists open caveats that apply to the current release and might apply to previous releases.

The "Resolved Caveats" sections list caveats resolved in a particular release, but open in previous releases.

Within the sections the caveats are sorted by technology in alphabetical order. For example, AppleTalk caveats are listed separately from, and before, IP caveats. The caveats are also sorted alphanumerically by caveat number.

If You Need More Information

Cisco documentation and additional literature are available on Cisco.com.

For more information on caveats and features in Cisco IOS Release 12.1 T, see the following sources:

Dictionary of Internetworking Terms and Acronyms—The Dictionary of Internetworking Terms and Acronyms contains definitions of acronyms that are not defined in this caveats document.

Bug Toolkit—If you have an account on Cisco.com, you can also use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Service & Support: Software Center: Cisco IOS Software: BUG TOOLKIT. Another option is to go to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

Cisco IOS Release 12.1 T platform-specific release notes—These release notes describe new features and significant software components for Cisco IOS Release 12.1 T.

What's New for IOS—What's New for IOS lists recently posted Cisco IOS software releases and software releases that have been removed from Cisco.com. If you have an account on Cisco.com, you can access What's New for IOS at http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml or by logging in and selecting Software Center: Cisco IOS Software: What's New for IOS.


Note Release notes are modified only on an as-needed basis. The maintenance release number and the revision date represent the last time the release notes were modified to include new or updated information. For example, release notes are modified whenever any of the following items change: software or hardware features, feature sets, memory requirements, software deferrals for the platform, microcode or modem code, or related documents.


Open Caveats—Cisco IOS Release 12.1(26)EB2

This section describes possibly unexpected behavior by Cisco IOS Release 12.1(26)EB2. All of the caveats listed in this section are open in Cisco IOS Release 12.1(26)EB2. This section describes severity 1 and 2 caveats and select severity 3 caveats.

CSCsi76736

Symptom: The Cisco LS1010 inventory collection fails in RME. The SNMP output lists an incomplete list of sub-modules on a line card.

Workaround: Upgrade to the latest IOS version.

CSCsh82489

Symptom: The Cisco LS1010 crashes with alignment errors.

Workaround: Disable the OAM and verify.

CSCsh20571

Symptom: The Cisco LS1010 may crash when a shut is performed on an Inverse Multiplexing over ATM (IMA) interface in the IMA group.

Workaround: None.

CSCsd32869

Symptom: An SNMP query on a 64-bit integer object returns 0, while a query on a 32-bit integer returns the correct value.

Workaround: None.

Open Caveats—Cisco IOS Release 12.1(26)EB1

This section describes possibly unexpected behavior by Cisco IOS Release 12.1(26)EB1. All of the caveats listed in this section are open in Cisco IOS Release 12.1(26)EB1. This section describes severity 1 and 2 caveats and select severity 3 caveats.

CSCsb03801

Symptom: ATMSIG Input process holds memory and does not release it back to the switch.

Workaround: None

CSCef95689

Symptom: When Cisco 8540/8510 switch connects to 3d vendor switch over IMA with one active link a synchronization error may occur on 3d vendor switch.The problem does not occur for the following scenarios:

There is a Cisco to Cisco connection

There are two and more links in IMA group

There is one E1/T1 link without IMA configuration

The issue causes delayed ICP cells on Cisco side resulting in synchronization error.

Workaround: Either use two or more active links in IMA group or use single link without IMA configuration.

CSCin19522

Symptom: For Frame Relay Soft VCs that use a frame size other than 250 (default), the CTTR should not be modified.


Note This DDTS is valid for Cisco IOS Release 12.1EB only.


Workaround: Delete the Soft VC from the configuration and recreate it with a new CTTR.

CSCdm36284

Symptom: The command show atm resources displays the number of cells in the UBR queue in an MSC and it increases continuously. The increase happens very slowly.

This occurs when traffic is sent through a Catalyst 8540 MSR at line rate. Increasing the threshold group per VC queue size does not eliminate the problem.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(26)EB2

Cisco IOS Release 12.1(26)EB2 is a rebuild release for Cisco IOS Release 12.1(26)EB1. The caveats in this section are resolved in Cisco IOS Release 12.1(26)EB2 but may be open in previous Cisco IOS releases.

CSCsd95616

Two crafted Protocol Independent Multicast (PIM) packet vulnerabilities exist in Cisco IOS software that may lead to a denial of service (DoS) condition. Cisco has released free software updates that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-multicast.shtml.

CSCsf04754

Multiple Cisco products contain either of two authentication vulnerabilities in the Simple Network Management Protocol version 3 (SNMPv3) feature. These vulnerabilities can be exploited when processing a malformed SNMPv3 message. These vulnerabilities could allow the disclosure of network information or may enable an attacker to perform configuration changes to vulnerable devices. The SNMP server is an optional service that is disabled by default. Only SNMPv3 is impacted by these vulnerabilities. Workarounds are available for mitigating the impact of the vulnerabilities described in this document.

The United States Computer Emergency Response Team (US-CERT) has assigned Vulnerability Note VU#878044 to these vulnerabilities.

Common Vulnerabilities and Exposures (CVE) identifier CVE-2008-0960 has been assigned to these vulnerabilities.

This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20080610-snmpv3.shtml

Resolved Caveats—Cisco IOS Release 12.1(26)EB1

The caveat listed in this section is resolved in Cisco IOS Release 12.1(26)EB1.

CSCei61732

Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.

Cisco has made free software available that includes the additional integrity checks for affected customers.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051102-timers.shtml.

CSCei76358

Through normal software maintenance processes, Cisco is removing deprecated functionality. These changes have no impact on system operation or feature availability.

Resolved Caveats—Cisco IOS Release 12.1(26)EB

Cisco IOS Release 12.1(26)EB is a rebuild release for Cisco IOS Release 12.1(23)EB. The caveats in this section are resolved in Cisco IOS Release 12.1(26)EB but may be open in previous Cisco IOS releases.

CSCin67508

Symptom: The getmany utility program displays the wrong instances of the "ifStackTable".

Workaround: None.

CSCeg16965

Symptom: Input and output packet counters do not increment when jumbo frames pass through the interface.


Note This is a cosmetic issue and does not impact traffic.


Workaround: None.

CSCee23976

Symptom: A LightStream 1010 ATM switch might crash and display "0x602D5E58:usecdelay(0x602d5e10)".

Workaround: None.

CSCdw67033

Symptom: If configuring RFC 1483 bridging on the ATM router module, when certain RFC 1483 bridging PVC cable connections are unplugged the Catalyst 8540MSR CPU utilization will become very high. This could last a few hours until you shut down the corresponding bridge-group subinterface on the ATM router module. Only shutting down the physical ATM port does not help.

Workaround: Shut down the corresponding bridging group subinterface on the ATM router module.

CSCdw04573

Symptom: The enhanced ATM router module subinterface counters do not get updated.

Workaround: None.

CSCdw02689

Symptom: When reloading the switch the following error message appears after a varying number of SVCs are set up.

 00:20:42: %ATMCORE-3-INTERNAL_ERROR: atmCore_connCheckSpot: exhausted vpi/vci

Workaround: None

CSCdv88029

Symptom: PNNI and SSCOP signaling does not come back up on the Catalyst 8540 MSR OC-48 interfaces after a power loss and restart.

Workaround: None.

CSCdv85162

Symptom: LDP session does not go down when you use the shut command on the enhanced ATM router module interface. When tag-switching is configured on a Fast Ethernet interface and the controlling ATM router module is either not configured or shut down, TDP comes up but the tag packets received on the Fast Ethernet interface are dropped because there is no controlling ATM router module to process the packets.

Workaround: Make sure the Fast Ethernet interface is linked to an active controlling ATM router module.

CSCdv62465

Symptom: A tag switching traceback might appear when an interface is shut.

Workaround: None.

CSCdv49358

Symptom: When a circuit emulation service (CES) circuit that is carrying traffic is removed, no warning message is shown.

Workaround: None.

CSCdv35065

Symptom: PNNI goes to the down state on all interfaces, and all adjacency is lost.

Workaround: None.

CSCdv22476

Symptom: The soft-VC permanent virtual connection (PVC) status is indicated as active only when the Soft VC is established, and its connection state is up. If the Soft VC is not connected, the source end of the Soft VC indicates the PVC status as inactive instead of active, and the destination end of the Soft VC does not exist, and therefore indicates the PVC status as deleted.

Workaround: None.

CSCdv11126

Symptom: Single bit errors have been observed on CES circuits originating on the same interface module if two other circuits always carry non-spec-conform AAL1 SNP for SN=0. Only this very high number of SNP errors in 1/8 of all AAL1 cells causes the issue. Multiple SNP corrections that could be seen in production networks are handled correctly without data loss or corruption.

This is an interoperability issue with a Lucent PSAX 2300.

Workaround: None.

CSCdv00784

Symptom: The Catalyst 8540 MSR switch may ignore certain commands from the NVRAM after a reboot. This appears most often on switches with dual route processors.

Workaround: Create a connection traffic index and use that number for the setup of the PVC.

CSCdu65431

Symptom: If the ASP or 8515MSRP installed in a Catalyst 5500 chassis is OIR removed an installed OC-12 Single Mode Intermediate Reach module (WAI-OC12-1SS=) continues to send carrier on the OC-12 interface. This causes the interface of the ATM device connected to this interface to display an up/up state even though the interface is reporting constant errors.

This affects all Cisco IOS versions for the Catalyst 8510 MSR and LightStream 1010.


Note The WAI-OC12-1SSLR= and WAI-OC12-1MM= modules do not exhibit this problem.


Workaround: None.

CSCdu39277

Symptom: After performing consecutive OIRs of three traffic-shaping carrier modules (TSCAMs) in a chassis more than 20 times, memory allocation fails. Because the TSCAMs require 2 MB of contiguous memory, this failure might occur on a system with severely fragmented memory.

Workaround: Do not perform a large number of consecutive OIRs on the TSCAM and do not perform an OIR on a module that has a large number of VCs.

CSCdu35462

Symptom: After a reload, the switch router's memory might be corrupted. This occurs after the following error messages are displayed:

 TLB (store) exception occurred on ... 
 dcl-dram-excep: A3420019, dcl-memd-excep: 60C10100, dcl-io-excep: 012C1580" 
 TLB (load or instruction fetch) exception occurred on 00/05/03 10:38:16 ... 
 dcl-dram-excep: A3420019, dcl-memd-excep: 60C10100, dcl-io-excep: 012C15", 
 
 " *** Unknown External Interrupt *** Stacked Cause = 0x0, Stac

Workaround: None.

CSCdu03975

Symptom: There is a noise problem with the CES PAM hardware version one.

Workaround: None.

CSCdu01489

A ROMMON configuration might not work properly.

Symptom: A ROMMON configuration might not work properly on a slot after performing an OIR on the interface module in that slot.

Workaround: Reload the switch router.

CSCdt83187

Symptom: On the LightStream 1010 switch when you try to use the atm rmon collect interface command you receive the following error:

ATM-RMON Error: Entry not found

Workaround: None.

CSCdt78388

Symptom: The Catalyst 8510 MSR does not auto boot if the first file in the bootflash is not an executable file (for example, the running-configuration or crashinfo files).

Workaround: Delete any non-executable file from the bootflash that appears before the first bootable image.

CSCdt17751

Symptom: The following operations will result in a CPU HOG and a CPU HOG error message:

when a TSCAM is inserted or removed from the chassis

when a port adapter module (PAM) is inserted into or removed from the subcard 0 position of the TSCAM

This does not affect the future operation of the TSCAM.

Workaround: Although this CPU HOG should not have any adverse impact on the network, we recommended that any online insertion or removal of TSCAMs or port adapter modules in the subcard 0 position of the TSCAM are scheduled appropriately.

CSCds86520

Symptom: An error message appears while sending traffic with a super CAM (for example, the OC-48 combo super CAM or OC-12 super CAM) and performing the following:

Using the online diags command to enabling online diagnostics

Performing an OIR of the super CAM

Use the shutdown and the no shutdown commands on one of the interfaces

If you perform these processes on the super CAM you might see the following error message:

ALIGN-3-READEXCEPTION messages. 

Workaround: None.

CSCds27586

Symptom: The subinterfaces of an ATM router module (ATM router module or enhanced ATM router module) may appear to receive the INARP packets even though the main interface is shut down. The upper layer finally discards the packet based on the state of the interface. There is no impact on functionality.

Workaround: None.

CSCdr62898

Symptom: Per-VC drop counters are not consistent. This applies only to non-packet discard connections. The inconsistencies are between the three per-VC statistics: total RX cell drops, RX UPC violations, and RX clp0 q full drops. The total of RX UPC violations and RX Clp0 q full drops exceeds the total RX cell drops count. However, the total RX cell drops is accurate.

Workaround: None.

CSCdr30421

Symptom: Multicast stats shows an incorrect rate in kbps.

Workaround: None.

CSCdp95194

Symptom: A LightStream 1010 configured for MPLS might not correctly increment counters on outgoing TVCs, although the data is being correctly sent out of the TVC.

Workaround: None.

CSCdp80826

Symptom: OAM F5 loopback cells are not passing across 25-Mbps port adapter interfaces.

Workaround: Configure the global configuration command no atm oam intercept end-to-end on the switch.

CSCdp15454

Symptom: The PNNI on-demand routing algorithm ignores longer equal cost paths.

Workaround: None.

CSCdp02816

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

Workaround: Access the switch using the console port.

CSCdm80628

Symptom: A T1 CES interface does not send out a remote alarm indication (RAI) in the reverse direction upon detecting an alarm indication signal (AIS).

Workaround: None.

CSCdm62514

Symptom: Reset button does not work correctly, and switch does not reload.

Workaround: None.

CSCdm36800

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

Workaround: None.

CSCdm04186

Symptom: EIGRP stops advertising routes out of an interface when there does not appear to be any interface problems.

Workaround: Enter the shutdown and the no shutdown commands on the affected interface.

CSCdk73733

Symptom: Power-on diagnostics display an NVRAM-Config failure following the second power-cycle after you use the write erase command if the write memory command has not been used between power-cycles.

This failure occurs only if you use the write erase command and the power-on diagnostics runs twice without the write memory command being used.


Note Power-on diagnostics run only if the switch is powered on. Power-on diagnostics do not run when using the reload command.


Workaround: After using the write erase command, use the write memory command before power cycling the switch.

CSCdk42052

Symptom: When loading a software image version 11.3 or later on a switch router with a software image version 11.2 or earlier, LEC and other LANE components might fail to come up if they are configured using an ATM address whose first 19 bytes are the same as the active ATM address of the switch.

The ATM address of the switch along with the first 128 values for its selector byte should be reserved for use by PNNI. Starting with software image version 11.3, PNNI supports hierarchy and registers an ATM address for all PNNI nodes using the switch ATM address with various selector byte values.

Workaround: If LANE components fail to come up because their ATM addresses conflict with the reserved ATM addresses for PNNI, reconfigure the LANE components using different addresses. We recommended that LANE applications use the addresses shown by the show lane default-atm-addresses command, which eliminates this problem.

CSCdk25256

Symptom: A non-zero generic flow control (GFC) field is not reset to zero when passing through the switch router.

When cells with a non-zero GFC field are received on a PVC, they are switched on the exit port without changing the GFC field. The switch should reset to zero all GFC bits from cells received with non-zero GFC at the user network interface (UNI).

Workaround: None.

CSCdk07378

Symptom: Funnel VCs can jeopardize quality of service (QoS).

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 oversubscribes and, potentially, affects the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.

Workaround: None.

CSCdj80396

Symptom: While setting up a large number of calls, the system generates the following error message:

%SYS-3-CPUHOG: Task ran for 5852 msec (0/0), process = Exec, PC = 6008DBB4

Workaround: None.

CSCdj78305

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

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

CSCdj71109

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

Workaround: None.

CSCdj42967

Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.

Workaround: None.

CSCdj25772

Symptom: Cell loss might occur while hot swapping a power supply.

Workaround: None.

CSCdj18678

Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.

Workaround: None.

CSCdj13565

Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (through PortSelTable) is not possible until the interface's 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.

CSCdj10889

Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on PortSelectGroups representing the interface on which the call came in and the counters shown on the PortSelectGroups representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(23)EB

Cisco IOS Release 12.1(23)EB is a rebuild release for Cisco IOS Release 12.1(22)EB. The caveats in this section are resolved in Cisco IOS Release 12.1(23)EB but may be open in previous Cisco IOS releases.

CSCin70593

Symptom: When a CES circuit (CES PVC, SPVC, or SVC) is created through SNMP, there is an entry created in the "ifTable" and in the tables of the "atmfCES mib" for each circuit. After an online removal of the T1-CES or E1-CES interface module, these entries are not deleted.

Workaround: None.

CSCin69343

Symptom: On the CES-E1 or CES-T1 interfaces the admin status appears down even after entering the no shutdown command when the framing is changed.

This problem does not appear when you only enter the shutdown and no shutdown commands on the interface through SNMP. If you read the "ifAdminStatus" object, it appears as up.

This same problem is observed in the CES-T1 interface.

Workaround: None.

CSCin23067

Symptom: The number of point-to-multipoint soft-PVC connections on the destination switch displayed by the output of the show atm state command might conflict with the output of the show atm vc conn-type soft cast p2mp command. The show atm vc conn-type soft cast p2mp command displays the correct status of the point-to-multipoint soft-PVC connections on the switch.

Workaround: None.

CSCin22597

Symptom: The value of the "Number of soft vc re-try attempts:" shown in the output of the show atm soft-vc p2mp interface atm card/subcard/port vpi vci command is always one greater than the actual number of retry attempts made.This is because the counter is incremented upon starting the party retry timer and not when the timeout happens and the signaling message is sent.

Workaround: None.

CSCef69111

Symptom: Unicast reverse path forwarding (uRPF) does not drop packets that are malformed or that have forged (spoofed) addresses of hardware-switched packets on the Catalyst 8540 or Catalyst 8510 switches running Cisco IOS Release 12.1(23)E. For example, if the switch is configured to perform unicast reverse path forwarding using the ip verify unicast source reachable-via rx command or the ip verify unicast reverse-path command and the switch is running Cisco IOS Release 12.1(23)E, those hardware-switched packets might be forwarded.

Workaround: None.

CSCee91544

Symptom: The IP traffic on a Catalyst 8540 CSR running Cisco IOS Release 12.0(26)W5(28) is route processor switched instead of hardware switched if an 8-port Gigabit Ethernet interface module is replaced with a 2-port Gigabit Ethernet interface module using OIR. This route processor switching causes a high CPU load.

Workaround: Reload the switch.

CSCee43952

Symptom: In certain situations, a Catalyst 8540 2-port Enhanced Gigabit Ethernet 16K (C85GE-2X-16K) interface module might see good frames as CRC errors. This occurs when two of these same modules are communicating across the WAN link. These CRC errors eventually cause a port stuck situation.

Workaround: Terminate the WAN link on a Layer 2 switch in between the Catalyst 8540 and the WAN link not on one of the C85GE-2C-16K interface modules.

CSCed95945

Symptom: The ATM interface on a router connected to a Catalyst 8540 MSR is shut down, but the ATM interface on the Catalyst 8540 MSR continues to stay up. The expected result would be the "down" state. This occurs if a C85MS-8T1-IMA interface module in the Catalyst 8540 MSR is running Cisco IOS Release 12.1(19)E and the ATM interfaces are configured as part of an IMA group.

Workaround: None.

CSCed20914

Symptom: Using the show switch fabric command to request information about the different interfaces connected to the chassis does not reflect all of the different interface connections. Only the 155-Mbps interfaces appear in the display.

Workaround: None.

CSCdx47684

Symptom: On the Catalyst 8500 switch, a PNNI PVC link on an NNI interface might flap after the link stabilizes and the ATM PNNI VC component does not come back up.

Workaround: Bounce the PNNI process using the no atm router pnni and atm router pnni configuration commands to disable and enable the PNNI processes.

CSCdp33630

Symptom: Packets are switched out on native VLANs leading to routing by the CPU (with BVI). This occurs on EPIF-based interface modules when untagged packets coming in on the dot1q native VLAN are not processed by the microcode. Instead, they are given to the CPU, and the CPU performs the processing. This causes high CPU utilization if untagged packets are received at a high rate on the native VLAN subinterfaces.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(22)EB

Cisco IOS Release 12.1(22)EB is a rebuild release for Cisco IOS Release 12.1(20)EB. The caveats in this section are resolved in Cisco IOS Release 12.1(22)EB but may be open in previous Cisco IOS releases.

CSCin67939

Symptom: The wrong payload pattern in idle cells might be transmitted from DS-3 and E3 interfaces.

As per recommendation I.361 (of the ITU-T), the payload pattern of the idle cell is "01101010" or "0x6A". But in DS-3 and E3 interfaces of the Catalyst 8510 MSR, Catalyst 8510 MSR, and LightStream1010 ATM switches, the payload pattern of the idle cell is set to "00000000" or "0x00". This is incorrect as per the ITU-T specification.

Some interoperability issues with other devices might appear if those devices expect only the "0x6A" pattern.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)E.


Workaround: None.

CSCin67191

Symptom: Using the show vc command displays garbage data for TVC(I) type interfaces with multiple leaves. Data for TVC(O) type interfaces with multiple leaves are displayed correctly. There is no impact on functionality.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)E.


Workaround: Use the show atm vc command instead of the show vc command.

CSCin65110

Symptom: The SNMP "get" request on the "ifSpeed" object of IF-MIB returns the wrong value for the IMA group interface.

There is no other functionality impact.

Workaround: None.

CSCed91457

Symptom: When reloading the image on a LightStream 1010 ATM switch running Cisco IOS Release 12.0(28)W5(30), you might see the following error message during bootup:

%LANE-3-LANE_ERROR: lecs finder: finderGetIlmiClientId: ilmi_register_client 
failed
00:00:06: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging 
output.

%LANE-3-LECS_ERROR: registerLECSwithILMI
-Process= "Init", ipl= 2, pid= 2
-Traceback= 606891B4 6069D690 606A1AF0 6067A190 600B341C 600B34D0 600292E8 
600294AC 6009950C 
600994F8
00:00:06: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging 
output.

%LANE-3-LES_ERROR: lsv_setup_lsv_ilmi

Workaround: None.

CSCed91394

Symptom: Connectivity problems might occur across STM-4 interfaces after upgrading the switch from Cisco IOS Release 12.0(1a)W5(5b) to 12.0(24)W5(26b). This upgrade might cause all PVCs having a leg on an STM-4 interface to begin experiencing connectivity problems.

Workaround: None.

CSCed38527

Symptom: A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.

All Cisco products which contain TCP stack are susceptible to this vulnerability.

This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.

A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.

Workaround: None.

CSCed29188

Symptom: If you configure more than sixteen static MAC entries on the Catalyst 8510 MSR or Catalyst 8510 CSR, the device might generate error messages indicating that it cannot chunk_malloc.

The errors might look similar to the following:

*Dec  9 13:59:28: Can't chunk_malloc 
*Dec  9 13:59:28: Can't chunk_malloc 
*Dec  9 13:59:28: Can't chunk_malloc


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)E.


Workaround: None.

CSCed27956

Symptom: A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.

All Cisco products which contain TCP stack are susceptible to this vulnerability.

This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.

A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.

Workaround: None.

CSCed20914

Symptom: Using the show switch fabric command to request information about the different interfaces connected to the chassis does not reflect all of the different interface connections. Only the 155-Mbps interfaces appear in the display.

Workaround: None.

CSCec61153

Symptom: Debugs remain enabled for removed interfaces.

1. If you use the debug atm sig-all command, the debugs are enabled for an interface. If that interface module is removed from the chassis, the show debug command output continues to show that "sig-all" debugs are enabled for the removed interface.

2. If you use the deb atm sig-all command, the debugs are enabled for all interfaces and if an interface module is removed from the chassis, the show debug command output continues to show that "sig-all" debugs are enabled for the removed interface module.

This is only a display issue. There is no impact on functionality.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)E.


Workaround: None.

CSCeb31070

Symptom: When connecting the IMA interface module from a Catalyst 8510 MSR to a Nortel Passport 15000, the IMA interface does not come up.

Workaround: None.

CSCdx47684

Symptom: On the LightStream 1010 switch, a PNNI PVC link on an NNI interface might flap after the link stabilizes and the ATM PNNI VC component does not come back up.

Workaround: "Bounce" the PNNI process using the no atm router pnni and atm router pnni configuration commands to disable and enable the PNNI processes.

Resolved Caveats—Cisco IOS Release 12.1(22)E

Cisco IOS Release 12.1(22)E is a rebuild release for Cisco IOS Release 12.1(20)E. The caveats in this section are resolved in Cisco IOS Release 12.1(22)E but may be open in previous Cisco IOS releases.

CSCin67939

Symptom: The wrong payload pattern in idle cells might be transmitted from DS-3 and E3 interfaces.

As per recommendation I.361 (of the ITU-T), the payload pattern of the idle cell is "01101010" or "0x6A". But in DS-3 and E3 interfaces of the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream1010 ATM switches, the payload pattern of the idle cell is set to "00000000" or "0x00". This is incorrect as per the ITU-T specification.

Some interoperability issues with other devices might appear if those devices expect only the "0x6A" pattern.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)EB.


Workaround: None.

CSCin67191

Symptom: Using the show vc command displays garbage data for TVC(I) type interfaces with multiple leaves. Data for TVC(O) type interfaces with multiple leaves are displayed correctly. There is no impact on functionality.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)EB.


Workaround: Use the show atm vc command instead of the show vc command.

CSCed29188

Symptom: If you configure more than sixteen static MAC entries on the Catalyst 8510 MSR or Catalyst 8510 CSR, the device might generate error messages indicating that it cannot chunk_malloc.

The errors might look similar to the following:

*Dec  9 13:59:28: Can't chunk_malloc 
*Dec  9 13:59:28: Can't chunk_malloc 
*Dec  9 13:59:28: Can't chunk_malloc


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)EB.


Workaround: None.

CSCec87644

Symptom: IP routes through route processor interface (ATM0) are not programmed in EPIF based Ethernet interface modules.

Workaround: None.

CSCec61153

Symptom: Debugs remain enabled for removed interfaces.

1. If you use the debug atm sig-all command, the debugs are enabled for an interface. If that interface module is removed from the chassis, the show debug command output continues to show that "sig-all" debugs are enabled for the removed interface.

2. If you use the deb atm sig-all command, the debugs are enabled for all interfaces and if an interface module is removed from the chassis, the show debug command output continues to show that "sig-all" debugs are enabled for the removed interface module.

This is only a display issue. There is no impact on functionality.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)EB.


Workaround: None.

CSCeb77236

Symptom: A Catalyst 8510 MSR or Catalyst 8510 CSR running Cisco IOS Release 12.1(19)E continuously crashes when booting and trying to bring up its interfaces. This only happens if ISL/dot1Q are configured. This problem is not seen if trunking is not configured.


Note This DDTS was also resolved in Cisco IOS Release 12.1(20)EB.


Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(20)EB

Cisco IOS Release 12.1(20)EB is a rebuild release for Cisco IOS Release 12.1(19)EB. The caveats in this section are resolved in Cisco IOS Release 12.1(20)EB but may be open in previous Cisco IOS releases.

CSCeb77236

Symptom: A Catalyst 8510 MSR or Catalyst 8510 CSR running Cisco IOS Release 12.1(19)E continuously crashes when booting and trying to bring up its interfaces. This only happens if ISL/dot1Q are configured. This problem is not seen if trunking is not configured.


Note This DDTS was also resolved in Cisco IOS Release 12.1(22)E.


Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(20)E

Cisco IOS Release 12.1(20)E is a rebuild release for Cisco IOS Release 12.1(19)E2. The caveats in this section are resolved in Cisco IOS Release 12.1(20)E but may be open in previous Cisco IOS releases.

CSCin54137

Symptom: Interface up/down events occur even when the carrier delay is configured.

Carrier delay support for DS3 and E3 interfaces on the LightStream 1010 and the Catalyst 8500 MSR is required.


Note This DDTS is a workaround for CSCdy25535.


Workaround: None.

CSCeb35962

Symptom: The clear counters command used with an OC-48 ATM interface module installed does not reset the FEBE counters in the show controllers command display. See the following example:

Switch# show controllers atm11/0/0
...
LINE
  AIS = 0          RDI = 0          FEBE = 2393       BIP(B2) = 0
PATH
  AIS = 0          RDI = 0          FEBE = 228        BIP(B3) = 0
  LOP = 0

Switch# clear counters
Clear "show interface" counters on all interfaces [confirm] Y
Switch# show controllers atm11/0/0
...
LINE
  AIS = 0          RDI = 0          FEBE = 2393       BIP(B2) = 0
PATH
  AIS = 0          RDI = 0          FEBE = 228        BIP(B3) = 0
  LOP = 0

Workaround: Reload the Cisco IOS image on the switch and do not OIR the OC-48 interface module.

CSCeb29970

Symptom: When establishing soft-VP between switches, if a VP number is used by the previous switch and if that switch sends an error stating that "VPI" is already used, then the switch receiving that error should use a different VPI number during its next retry attempt. For example:

Switch-1 (1/0/0)-------(1/0/0) Switch-2 (1/1/1)---------(1/1/1) Switch-3 (1/1/0) 

1. A soft-VP call is getting initiated by Switch-1.

2. The node ID of Switch-3 is higher than Switch-2.

3. The Switch-2 ATM1/1/1 interface has a PVP configured with VPI 4 (ATM PVP 4).

In this scenario, when a call is initiated by Switch-1, it is forwarded by Switch-2 to Switch-3. Because the node ID of Switch-3 is higher than Switch-2, Switch-3 requests a VP number. If the request is for VPI 4 on Switch-3's ATM1/1/1, it will reach Switch-2's ATM1/1/1. Because there was a PVP configured on Switch-2's ATM1/1/1 interface with PVP 4, it is rejected stating that VPI is "unavailable". This error is sent to both Switch-1 and Switch-3. During the next attempt when Switch-3 requests a VPI number, it should request a different VPI number from 4.

Workaround: None.

CSCeb13499

Symptom: Problems occur in CISCO-ATM-IF-PHYS-MIB implementation:

1. ciscoAtmIfPhysLineFebeErrors returns Path FEBE errors instead of Line FEBE errors.

2. ciscoAtmIfPhysPathFebeErrors returns Line FEBE errors instead of Path FEBE errors.

This only happens with OC-3/STM-1 or OC-12/STM-4 interfaces.

Workaround: Poll ciscoAtmIfPhysLineFebeErrors when you need Path FEBE errors and poll ciscoAtmIfPhysPathFebeErrors when you need Line FEBE errors.

CSCea48476

Symptom: POD (Parallel Optical Device) fails with ATMDIAG_UNEXPECTED_PIF_INTERRUPT_ERROR. POD errors might occur in some LightStream 1010 switches. These errors occurred on ports that were up and working. This problem appears to be a false error reported by POD.

Workaround: None.

CSCdy81424

Symptom: Same problem as DDTS CSCdx58649 except the fix was not committed to the LightStream 1010 image.

Workaround: None.

CSCdw90604

Symptom: Interoperability problem between LightStream 1010 and Compaq Server with ATM NIC if you pull out the optical fiber connection and reconnect it. If you do so, ILMI keeps restarting, and never stabilizes. You can use the shutdown command on the interface, then disconnect and reconnect the fiber optic connection, and use the no shutdown command on the ATM interface to eliminate the problem. These commands cause ILMI to restart correctly.


Note Using the shutdown and the no shutdown commands on the LightStream 1010 ATM interface after the disconnection and reconnection does not solve the problem.


Workaround: Follow these steps:
1. Reboot the server.
2. Use the shutdown and the no shutdown commands on the DES ATM-Switch-Interfaces.
3. Restart the ATM NIC (only the NIC interface).
4. Bind the TCP stack.

CSCdv82794

Symptom: An ATM router module interface with a PVC configured might experience a port stuck condition.

Workaround: None.

CSCdv55117

Symptom: A Catalyst 8540 MSR locks up when configuring ATM port snooping. The switch lockup can occur if ATM port snooping is configured without an analyzer connected to the snoop port.

Workaround: Either load the most recent version of Cisco IOS or have the analyzer connected to the snoop port prior to configuring ATM port snooping. Keep the analyzer connected until the snoop configuration is removed.

CSCdt21568

Symptom: The ATM router module interface shuts down when entering the epc portstuck-manual-reload command with IP traffic. This only occurs when running the epc portstuck-manual-reload command several times.

Workaround: None.

CSCdt04810

Symptom: While executing a series of shutdown/no shutdown commands on the ATM router module interface with a large number of CLIP clients (more than 32), the following error message appears on the console:

00:58:16: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 644B0550.
-Process= "ATM ARP INPUT", ipl= 0, pid= 30
-Traceback= 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50shut

Enter hex value: 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50
0x600CE1BC:mgd_timer_complain_uninit(0x600ce190)+0x2c
0x600CF2A4:mgd_timer_stop(0x600cf26c)+0x38
0x60792B0C:atm_arp_stampvc(0x60792ad4)+0x38
0x60796850:atm_inarp_rcvdreq(0x6079620c)+0x644
0x60797744:atm_arp_process(0x60796f30)+0x814
0x600BBA64:r4k_process_dispatch(0x600bba50)+0x14
0x600BBA50:r4k_process_dispatch(0x600bba50)+0x0

This does not impact functionality. Enter the shutdown command, followed by the no shutdown command to recover.

Workaround: None.

CSCds44008

Symptom: Under certain conditions, the Catalyst 8510 does not have a certain MAC address in the CAM table. This leads to flooding of L2 traffic for a short time, until the MAC addresses are learned.

Workaround: Issue a clear br gr command.

CSCdr32958

Symptom: CPU hog by OIR handler.

Workaround: None.

CSCdr01726

Symptom: The ILMI status of shaped and hierarchical tunnel subinterfaces that are down (not shutdown) appear stuck in the Restarting state after a shutdown/no shutdown command sequence.

Workaround: None.

CSCdp79109

Symptom: The switch might have spurious memory access tags after configuring and unconfiguring tag switching on different ATM interfaces. This is not known to impact tag switching functionality on the switch. The following message might appear on the console:

*** gd03_tag_stress: Mon Jan 31 08:35:12 2000 949336512 comment         Spurious
  memory accesses on gd03_r55_11: count = 1 ***
 *** gd03_tag_stress: Mon Jan 31 08:35:12 2000 949336512 comment         1C
 1  0x60254C28 0x60236140 0x6009868C 0x60098678

Workaround: None.

CSCdp50167

Symptom: IMA group fails to come up intermittently, especially after reload and on E1 IMA links.

Workaround: Go to one of the IMA interfaces and give the following command:

Switch(config-if)# fwmon "altrap 00 ff 00 ff 00 ff"

If the group still remains down, it indicates a persisting alarm on the line. The line configuration has to be checked to clear the problem.

CSCdk88174

Symptom: The 25-Mbps ATM interface module installed in a LightStream 1010 ATM switch always displays an input rate of 25 Mbps, even if the connected ATM end-station is not sending any data.

Workaround: None.

CSCdk57536

Symptom: The following message appears on the neighbor ATM switch after using the reload command:

%SYS-3-CPUHOG: Task ran for 3984 msec (24/11), process = Net Background

Workaround: None.

CSCdk52436

Symptom: On a switch router configured with 32 MB of RAM, IPC traffic between the port adapter driver and the firmware can experience a transient failure when the port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if it is reset after waiting for about 2 minutes.

This IPC failure, which is due to an unexpected firmware crash under a heavy load, does not occur on a system configured with 64 MB of RAM.

Workaround: None.

CSCdk47516

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

Workaround: None.

CSCdk10398

Symptom: ILMI does not come up upon reload of VP-MUX (VUNI).

ILMI on the tunnel interface, which is connected to the far end peer device through a VP-MUX switch and virtual UNI, is occasionally unable to come up and stay in "WaitDevType" state after reloading the VP-MUX switch. This situation can be cleared by shutting down the tunnel interface, disabling ILMI and entering a no shutdown command on the tunnel interface. After the interface settles down, ILMI on the tunnel can then be reenabled by shutting down the interface, and entering both the atm ilmi-enable command and the atm auto-configuration command, if desired. Reenable the tunnel interface with a no shutdown command.

Workaround: None.

CSCdj85853

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

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

CSCdj84379

Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmission to the scheduled rate. This can cause cells to be dropped in the WAN. It might be better to do any dropping prior to multiplexing onto the VP, so that a packet discard can be performed. Packet discard cannot be performed on the VP trunk.

Workaround: None.

CSCdj82930

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

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

CSCdj68412

Symptom: If there are multiple parallel paths to the same destination on a switch router with a FC-PFQ 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.

CSCdj54954

Symptom: On a switch router equipped with an FC-PFQ, the maximum number of cells available for use is 64,511. The number of cells in the switch fabric is 65,535.

Workaround: None.

CSCdj18430

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

Workaround: None.

CSCdj01757

Symptom: When one of the installed power supplies is powered OFF, and you are copying an image to bootflash, a power supply failure message appears.

Workaround: None.

CSCdi92142

Symptom: A LECS, using Cisco IOS Release11.2(X), expects all LESs to establish an individual control VC to the LECS to validate clients.

If different emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LESs 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 an LECS sends the following warning messages to the console stating that an LES of one ELAN is attempting to obtain information about another ELAN:

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for 
elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for 
elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: 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 messages.

Workaround: None.

CSCdi83275

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

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

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

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

CSCdi75584

Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.

Workaround: None.

CSCdi74229

Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:

%SYS-3-CPUHOG

This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.

Workaround: None.

CSCdi55937

Symptom: Remote defect identification (RDI) cells sent by an end point 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.

Resolved Caveats—Cisco IOS Release 12.1(19)E2

Cisco IOS Release 12.1(19)E2 is a rebuild release for Cisco IOS Release 12.1(19)E. The caveats in this section are resolved in Cisco IOS Release 12.1(19)E2 but may be open in previous Cisco IOS releases.

CSCeb52110

Symptom: If your switch is running Cisco IOS Release 12.1(7a)EY and you perform an OIR of a CES interface module, this might cause the route processor to crash.

Workaround: None.

CSCea30004

Symptom: Whenever you attempt to update the Access Control List (ACL) attached to the management interface (Ethernet2/0/0) on the LightStream 1010 ATM switch, the following error message appears:

ACL is not supported

ACL functionality on the interface is not affected.

Workaround: None.

CSCdy14709

Symptom: The "ifindex persistent" feature support was added beginning with Cisco IOS Release 12.1(13)E.

The SNMP ifIndex persistence feature provides an interface index (ifIndex) value that is retained and used when the switch reboots. The ifIndex value is a unique identifying number associated with a physical or logical interface.

For additional information refer to the document, Configuring SNMP IfIndex Persistence.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(19)E

Cisco IOS Release 12.1(19)E is a rebuild release for Cisco IOS Release 12.1(14)E1. The caveats in this section are resolved in Cisco IOS Release 12.1(19)E but may be open in previous Cisco IOS releases.

CSCin44348

Symptom: The Frame Relay retry interval is shown twice in the running configuration. This means the configured Frame Relay soft VCs are not preserved after an image reload or a route processor switchover.

Workaround: None.

CSCin41597

Symptom: PNNI routing fails from one access device to a complex peer in some branches. For example, in the following network example, calls from the Ls1010 switch to an interface on the Catalyst 8540 switch are not set up.

However, calls from the Catalyst 8540 switch to the Ls1010 switch are set up correctly. If the Catalyst 8540.2 switch is configured as a simple single-level hierarchy, the calls originated from either switch to the other switch are set up without any problems.

Workaround: Configure the complex node (Catalyst 8540.2 switch) as a simple hierarchy.

CSCin40363

Symptom: The switch crashes when you run the no tag-switching mtu command.

Workaround: None.

CSCin37548

Symptom: The reloads on the simultaneous execution of certain PNNI CLIs.

For example, through a console session:

Run the show atm pnni topology command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Press the Space key on the console session.

Run the show atm pnni neighbor command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Press the Space key on the console session.

Run the show atm pnni background routes admin-weight command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Press the Space key on the console session.

Run the show atm pnni exp-path detail command and wait for the more prompt to appear. Through a Telnet session delete all the explicit paths. Press the Space key on the console session.

The following issues are also seen. Through a console session:

Run the show atm pnni topology detail command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Pressing the Space key on the console session causes spurious memory access.

Run the show atm pnni aggregation node border-detail exception-detail command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Press the Space key on the console session. The output is not aborted gracefully.

Run the show atm pnni database command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Press the Space key on the console session. The output is not aborted gracefully.

Run the show atm pnni explicit-paths detail command and wait for the more prompt to appear. Through a Telnet session delete the lowest level node. Pressing the Space key on the console causes spurious memory access and tracebacks are seen.

Workaround: None.

CSCin36885

Symptom: On a Catalyst 8510 MSR if an OC-3 interface is overbooked and configured with PVCs that consume more than 599 Mbps of bandwidth, during bootup, these PVCs are lost from the running configuration.

The following error message appears during bootup for every PVC that is rejected.

%connection creation fails: specified traffic/resource parameters are invalid

Workaround: Configure the PVCs that were lost once the switch boots up.

CSCin27583

Symptom: If a marker cell has been queued for a leaf and at the same time a new party is attempting to be installed, the add party fails and the following error message is seen:

00:04:26: ATMSIG: CONNECTION MANAGER/CAC Xconn install result 
        CONN_INSTALL_RESULT_HW_FAIL
00:05:30: %ATMSIG-3-FAILXCONN: Xconnect failed, xconn fail 
-Traceback= 607B910C 607BB960 607C6950 607B3538 607B3640 600D2FAC 600D2F98
00:05:30: ATMSIG(1/0/3:0 0,79 - 0045/25): (vcnum:0) XConnected failed To 
00:05:30: ATMSIG(1/1/0:0 0,945 - 0220/25): (vcnum:0)
00:05:30: ATMSIG: CONNECTION MANAGER/CAC Xconn install request 
         Port A -  (1/0/3) : 0  vpi = 0; vci = 79 
         Port B -  (1/1/0) : 0  vpi = 0; vci = 945; new vpi = 0; new vci = 945 
existing vpi/vci for leg B 
00:05:30: ATMSIG: CONNECTION MANAGER/CAC Xconn install result 
        CONN_INSTALL_RESULT_HW_FAIL

Workaround: The point-to-multipoint soft-PVC party comes up because of the soft-PVC retry.

CSCin06705

Symptom: Subinterfaces of route processor and ATM router module ports are not registered with SNMP ifTable.

Workaround: None.

CSCin06080

Symptom: On a LightStream 1010 switch with an E1interface connection, Detailed Device Report shows "slot number : N/A" but should display the actual interface slot number.

Workaround: None.

CSCea72899

Symptom: Soft PVC does not come up.

If a soft PVC originates from a Catalyst 8510 MSR or LightStream 1010 ATM switch is directly connected to an Alcatel switch, the soft PVC never comes up. If the call originated from the Alcatel side, the soft PVC comes up with no problem.


Note This occurs if the Catalyst 8510 MSR switch is running Cisco IOS Release 12.0(24)W5(26b).


For example:

At UNI ATM interface:

atm soft-vc 1 455 dest-add xx.348f.8001.bbfc.0000.0ba0.6f10.4080.210a.2a01.00 1 
455 rx-cttr 1 tx-cttr 1 

The Alcatel switch is directly connected, ATM NNI and PNNI are up, and adjacency is up:

show atm pnni neighbor
---
 Neighbor Name: unknown, Node number: 40
  Neighbor Node Id: 88:160:xx.348F8001BBFC00000BA06F10.408021810A00.00
  Neighboring Peer State: Full
  Link Selection For CBR    : minimize blocking of future calls
  Link Selection For VBR-RT : minimize blocking of future calls
  Link Selection For VBR-NRT: minimize blocking of future calls
  Link Selection For ABR    : balance load
  Link Selection For UBR    : balance load
   Port                      Remote Port Id            Hello state
   ATM12/0/3                 1281000                   2way_in  (Flood Port)
---
Switch# show atm route 
P  I 40  0            UP 0   39.348f.8001.bbfc.0000.0ba0.6f10/104
---

But, if the show atm pnni dtl node 40 ubr command is used:

*Apr 10 23:11:21.218: PNNI: UBR route request from ATM_OWNER_UNKNOWN
*Apr 10 23:11:21.218: PNNI: To node 88:160:xx.
348F8001BBFC00000BA06F10.408021810A00.00
*Apr 10 23:11:21.218: PNNI: selected target node 40
*Apr 10 23:11:21.218:       priority: 2  (40 0) pnni-remote-internal 
*Apr 10 23:11:21.218: PNNI: Compute On-Demand Route Based On Admin Weight
*Apr 10 23:11:21.218: PNNI: Failed To Find An On-Demand Route, 
Code: PNNI_RESOURCE_UNAVAILABLE
*Apr 10 23:11:21.218: PNNI: No Route To 
88:160:xx.348F8001BBFC00000BA06F10.408021810A00.00
*Apr 10 23:11:21.218: PNNI: Send Source Route Reply 
To Requestor: Code PNNI_RESOURCE_UNAVAILABLE
---

When the call is initiated from the LightSteam 1010 switch, nothing comes to the Alcatel switch. At the same time, when the call is initiated from the Alcatel switch, the soft PVC comes up:

Switch# show atm vc interface atm 9/1/1
Interface  VPI  VCI   Type   X-Interface      X-VPI X-VCI Encap  Status 
ATM9/1/1   0    5     PVC    ATM13/0/0        0     72    QSAAL  UP
ATM9/1/1   0    16    PVC    ATM13/0/0        0     40    ILMI   UP
>>Alcatel Init <<<<
ATM9/1/1   0    400   SoftVC ATM12/0/3        0     227          UP 
>> LS1010 Init <<<<
ATM9/1/1   1    455   SoftVC NOT CONNECTED

Workaround: None.

CSCea66219

Symptom: A memory leak occurs in the ATMSIG processes. This is observed using the show processes memory command. The ATMSIG processes hold increasing amounts of memory and free memory is decreasing.


Note This occurs on LightStream 1010 ATM switches or Catalyst 8510 MSR running Cisco IOS Release 12.0(24)W5(26b), Cisco IOS Release12.1(12c)E, or Cisco IOS Release 12.1(13)E1.


Workaround: None. The switch must be rebooted to recover.

CSCea33595

Symptom: On a LightStream 1010 switch running Cisco IOS Release 120-24.W5.26b, the system might crash because of a system restarted by a bus error at PC 0x6063F9C8, address 0xD0D0D15.

Workaround: None.

CSCdw43258

Symptom: If you use the show version command on a LightStream 1010 switch with a faulty Flash PC card, the following error message might appear:

%SYS-3-CPUHOG: Task ran for 3708 msec (343/19), process = Virtual Exec, PC = 
%600AB140.
-Traceback= 600AB148 60038620 60038D1C 60038734 600384D8 60038D1C 60038734 
6044C190 6005809C 60057DDC 6004BF74 

Workaround: Use a different Flash PC card.

CSCdv41809

Symptom: On the CES module interface, the status reads up/up and the status of the PVC to that interface is up in even though there is no physical connection at that port.

Workaround: Perform the shutdown and the no shutdown commands on the interface to clear the erroneous status.

CSCdr59877

Symptom: In the LightStream 1010 switch, the output of a show ethernet command displays the "lost carrier" count following the collision counter. This is a counter error only and does not actually indicate a lost carrier and does not impact the operation of the Ethernet interface.

Workaround: None.

CSCdk64928

Symptom: When a LightStream 1010 ATM switch has its image saved in bootflash and the config-register is configured to 0x2101, the system stays in ROMMON mode after a crash.

If the config-register is set to 0x2102, the switch crashes a second time by bus error while trying to open slot 0. The switch then recovers and boots the bootflash image.

Workaround: Set the MONRC command in the ROM monitor, which overrides any BOOT SYSTEM command from the configuration, as follows:

rommon 1>MONRC="boot bootflash:"
rommon 2>sync
rommon 3>reset

CSCdk34773

Symptom: When you try to connect Racal-Datacomm CSUs together using ports on the same CES interface module, timing problems might prevent the CSUs from starting up.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(14)EB1

Cisco IOS Release 12.1(14)EB1 is a rebuild release for Cisco IOS Release 12.1(14)EB. The caveats in this section are resolved in Cisco IOS Release 12.1(14)EB1 but may be open in previous Cisco IOS releases.

CSCin29715

Symptom: If a Frame Relay-Frame Relay PVC is deleted through SNMP Resource Management, the information is incorrect in the show frame-relay interface resource serial card/subcard/port:chn_grp_# command display.

This allows for the creation of more VCs than the physical bandwidth available.

Workaround: Delete and recreate the channel group.

CSCdt10494

Symptom: The ATM router module (8540-ARM-64K) indicates outgoing packets when on an interface that is in an admin down state.

This was observed on Cisco IOS Release Version 12.0(10)W5(18c) software for PNNI (cat8540m-WP-M). This does not impact the functionality.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(14)EB

Cisco IOS Release 12.1(14)EB is a rebuild release for Cisco IOS Release 12.1(13)EB1. The caveats in this section are resolved in Cisco IOS Release 12.1(14)EB but may be open in previous Cisco IOS releases.

CSCdz71298

Symptom: The Catalyst 8510 MSR might display the following error messages:

xpif_read_media_type: Null ds structure for Port-channel1
xpif_read_media_type: Null ds structure for Port-channel1

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(14)E1

Cisco IOS Release 12.1(14)E1 is a rebuild release for Cisco IOS Release 12.1(13)EB1. The caveats in this section are resolved in Cisco IOS Release 12.1(14)E1 but may be open in previous Cisco IOS releases.

There are no resolved caveats in this release.

Resolved Caveats—Cisco IOS Release 12.1(13)EB1

Cisco IOS Release 12.1(13)EB1 is a rebuild release for Cisco IOS Release 12.1(13)E1. The caveats in this section are resolved in Cisco IOS Release 12.1(13)EB1 but may be open in previous Cisco IOS releases.

CSCin14721

Symptom: The CBR interface module sends a "remote alarm" to the peer interface if the line flaps continuously. This causes the peer interface to change to "yellow alarm" state.

Workaround: Enter the shutdown and the no shutdown commands on the CBR interface.

CSCin12950

Symptom: Packets received with a destination multicast MAC address and destination unicast IP address are forwarded to the route processor, and then forwarded back out on the VLAN where the packets were received.

Workaround: None.

CSCin12744

Symptom: Signaling is reset on other interfaces of the device that are not connected to the peer switch being reloaded.

Workaround: None.

CSCin02864

Symptom: On interface ATM0, while breaking the packet into cells, when the MTU size configuration is checked it is checked for the cross-connect ATM interface and not for interface ATM0 itself. This means if the size of the packet exceeds the configured MTU on the cross-connect ATM interface, the following error is displayed:

%LINK-4-TOOBIG: Interface ATM1/1/3, Output packet size of 2008 bytes too big

Workaround: There are two possible workarounds for this condition: either change the MTU size on both ATM interfaces back to the default using the command no mtu in interface configuration mode, or change the MTU configuration on interface atm 0 to match the MTU configuration on the cross-connect interface using the mtu number interface configuration command.

CSCdz06963

Symptom: After a LAN emulation client (LEC) goes down, a router that has an enhanced ATM port adapter (PA-A3) may not be able to register a network service access point (NSAP) address with an Integrated Local Management Interface (ILMI). Several messages that are similar to the following may be logged in the log file:


%LANE-3-NOREGILMI: ATM1/1/0.7 LEC cannot register
39.000000000000000000000022.000163728428.07 with ILMI

%LANE-3-NOREGILMI: ATM1/1/0.6 LEC cannot register
39.000000000000000000000022.000163728428.06 with ILMI

This symptom is observed on a Cisco router that has a PA-A3 port adapter and that is running Cisco IOS Release 12.2(10a). This symptom is observed after the software is upgraded from Cisco IOS Release 12.2(8)T4.

Workaround: Reload the router.

CSCdy45231

Symptom: The IMA interface module does not generate a syslog message when the link goes down.

Workaround: None.

CSCdy44850

Symptom: The command network-clock-select priority system disappears from the running configuration after a switch reload.

After entering the command in global configuration mode, the switch parser adds the keyword "clock" at the end of the line and that causes the reload to skip the command when parsing the configuration file.

Workaround: None.

CSCdy32886

Symptom: When using version UNI 4.0, during SVC call setups, a Catalyst 8500 MSR switch in the "Call Received" state does not send a connect-ack upon reception of a connect. This causes the SVC to be released.

Workaround: Use version UNI 3.1

CSCdy07314

Symptom: A Catalyst 8500 MSR running Cisco IOS Release 12.0(20)W5(24b) might crash with a bus error in the SNMP code.

Workaround: Disabling polling chassis MIBs might prevent the crash.

CSCdx94423

Symptom: If you disconnect the transmit cable from an E1 CBR interface on a Catalyst 8540, Catalyst 8510, or LightStream 1010 switch, the interface still appears up/up. No indication of error messages appears in the log files.

When the transmit cable is reconnected, it starts to transmit traffic again. However, if the transmit cable is disconnected multiple times, the link does not pass traffic even when the transmit cable is reconnected.

Workaround: Use the shutdown and the no shutdown commands on the interface and it returns to normal, or disconnect the receive cable and reconnect it.

CSCdx93120

Symptom: On a Cisco 6400 Node Switch Processor (NSP) running Cisco IOS Release 12.2(2)B and its derivatives, using the atm ping command to test a valid and active VP might fail with the following message:

Jun 20 15:56:17.742: %ATMCORE-3-INTERNAL_ERROR: atmCore_oamRcvPing: No match.

The failure occurs when running the ping towards specific destination ATM switches, and is dependent on the format of the loopback cell received from the destination ATM switches. The occurrence of this problem is difficult to predict and depends on the particular ATM switch implementation of the destination switch.

Workaround: None.

CSCdx91019

Symptom: A Cisco 6400 NSP, running Cisco IOS Release 12.1(5)DB or 12.2(2)B, displays the following error message when you use the atm ping interface atm slot/subslot/port VPI VCI end-loopback command and enter the wrong VP/VC combination:

connection doesn't exist

Any future atm ping commands to any connections (both valid and invalid) always result in the same error message and the ping commands fail. It fails even if the connection is valid, and even if a VP ping is used (for example, no VC number is specified).

You can still use the IP ping command to diagnose the connectivity between the NRP2 (Node route processor 2) and NSP.

Workaround: None.

CSCdx04773

Symptom: When the Cisco ATM switch is running UNI 4.0 with a Fore or Marconi switch, it might release a call because of unsupported traffic parameters.

This occurs when the Cisco ATM switch is connected to the other vendor equipment and configured to operate with UNI 4.0 version across the link and as a non-negotiated link. If any traffic parameter values are modified, the Cisco ATM switch treats this as a fatal error and releases the call.

Workaround: Hardcode the UNI version to 3.1.

CSCdw93109

Symptom: When using ATM Frame Relay IWF on a Catalyst 8540 MSR running Cisco IOS Release 12.0(18)W5(22) or later, the output queue of the pseudo-ATM interface might go to 40/40 and remain there even if no traffic is going through the switch on the ATM-FR circuits.


Note A reload might be required to clean that counter, but connectivity is not impacted.


Workaround: None.

CSCdw70257

Symptom: A Catalyst 8510 MSR configured with an IMA (inverse multiplexing for ATM) bundle might not log link up-or-down status messages. Only messages displaying clock change are logged. See the following example:

 04:23:21: %CLOCKSW: Switching from ATM1/1/1 to ATM1/1/0
 04:24:26: %CLOCKSW: Unswitching from ATM1/1/0 to System
 04:25:21: %CLOCKSW: Switching from System to ATM1/1/1
 04:26:06: %CLOCKSW: Unswitching from ATM1/1/1 to System

As each interface recovers its revertive clocking and the source is recovered, link functionality is restored. Confusion can be created if there are multiple links flapping and only CLOCKSW messages are received without reporting status of the interface.

The correct physical status can be viewed properly with the show ima interface and the show ima interface atm card/subcard/port max detail commands to display the status of the interface and counters.


Note This behavior is not seen when the switch is configured as standalone.


Workaround: None.

CSCdw45551

Symptom: On the LightStream 1010 switch, the following error message appears if your switch is using Cisco IOS Release 12.0(19)W5(23):

Jan 15 12:34:19.734 CET:%ATMSIG-3-FAILXCONN: Xconnect failed, xconn fail 
-Traceback= 6054D9CC 6054F8A0 60559AF0 60548BC0 60548CC8 6009938C 60099378
Jan 15 12:34:19.738 CET: ATMSIG(0/1/0:0 0,174 - 4887/00): (vcnum:0) XConnected failed 
To 
Jan 15 12:34:19.738 CET: ATMSIG(1/0/0:0 0,251 - 93568/00): (vcnum:0)
Jan 15 12:34:19.738 CET: ATMSIG: CONNECTION MANAGER/CAC Xconn install request 
         Port A -  (0/1/0) : 0  vpi = 0; vci = 174 
         Port B -  (1/0/0) : 0  vpi = 0; vci = 251; new vpi = 0; new vci = 251 
existing vpi/vci for leg B 
Jan 15 12:34:19.738 CET: ATMSIG: CONNECTION MANAGER/CAC Xconn install result 
        CONN_INSTALL_RESULT_HW_FAIL

It appears frequently without any other preceding error messages and software/hardware changes on the switch.

Workaround: Upon its first appearance, the issue was avoided by reloading the switch.

CSCdw22559

Symptom: When an IMA interface module is installed in the switch chassis, and if "loopback PIF" is configured on any OC-3 or OC-12 interface, loopback is NOT reflected when queried through SNMP. Loopback is NOT actually being set.

Workaround: None.

CSCdw09750

Symptom: Inverse ARP does not succeed for a Frame Relay PVC terminated on an ATM router module.

Workaround: None.

CSCdv46664

Symptom: All MPLS VPN connectivity is broken on Cisco 7500, Cisco 7200, and all common platforms if there is a TCATM link between the two provider edges (PEs) that falls in the IGP path and LSP. The routers are disabled from initiating a headend VC request over a TCATM link.

Workaround: None.

CSCds77275

Symptom: On the LightStream 1010 switch, very intermittently, a SVC call could be rejected due to a VPI/VCI collision when the call is through a PVP tunnel.

Workaround: After you reseat the interface module on which the PVP tunnel is configured, the condition is cleared for some time.

Resolved Caveats—Cisco IOS Release 12.1(13)E1

Cisco IOS Release 12.1(13)E1 is a rebuild release for Cisco IOS Release 12.1(12c)EY. The caveats in this section are resolved in Cisco IOS Release 12.1(13)E1 but may be open in previous Cisco IOS releases.

CSCin12417

Symptom: An ATM interface might stick in the "going down" state if the PVC is created from the ATM router module with VCI "34" on the ATM side. For example, "atm pvc 2 35 pd on interface ATM0/0/0 7 34" causes the line to flap up and down.


Note The problem is not seen with any other VCI on the ATM side.


Workaround: Recreate the PVC using any VCI other than 34 on the ATM side.

CSCdy38993

Symptom: A route processor crash occurs when address registration fails at the switch. Also, an error message is flashed to the console. This problem occurs when traffic is flowing over a Flexwan module and either a hw-module-reset or OIR has occurred.

Workaround: None.

CSCdx65390

Symptom: When a point-to-multipoint SVC connection is set up through a switch (root and leaf are active and cross-connected), and a request is received to add a leaf through another interface, and the allocation of this half-leg fails, the connection structures associated with this half-leg are not cleaned up. This means when the connection is cleared, the failed connection cannot be released.

This ties up bandwidth and VPI and VCI resources for the root half-leg of the connection.


Note These resources cannot be cleared using the shutdown and the no shutdown commands on the interface.


Workaround: None.

CSCdx58649

Symptom: Avaya PBX and Definity PBX interoperability testing caveats.

The following caveats exist for signaled ATM point-to-multipoint (P2MP) connections and the debugging of issues related to them on the Catalyst 8500 ATM switches:

Hardware processing to release connection IDs (VPI/VCI) on low-rate P2MP connections can be slow. When add party and drop party are issued in quick succession on such a connection, insufficient time is spent waiting for completion, which causes an unnecessary rejection of the add party. There is no workaround for this issue.

When a slave NNI node (in terms of connection ID allocation) proposes a connection to the master, and the master then uses the proposed VPI/VCI itself (intending to give the slave-proposed-VC another connection ID), two SVCs end up owning the same underlying VC. The result is a dangling half-leg, and possibly allocated bandwidth that is never returned. There is no workaround for this issue.

Handling of unexpected values in the second byte of the ATM signaling message-type field is to drop the message. This is incorrect. There is no workaround.

Several debug messages received during "error" debugging are normal events. This causes clogging of the log buffer with non-errored messages. This is for "mmc errors" and "atm sig cc-errors".

Workaround: None.

CSCdx11136

Symptom: Power-on diagnostics fail on the Catalyst 8510 MSR when Cisco IOS Release 12.1(10)E or higher is loaded in the bootflash.

Workaround: None.

CSCdw27518

Symptom: Frame Relay PVC goes down and remains down after enabling the OAM feature and performing a shut / no shut on the serial interface. However, traffic flow is not affected through the PVC even though it appears down.

Workaround: Disable OAM and shut/no shut the serial interface to force the interface to appear back up.

CSCdw14139

Symptom: The combined installation of TSCAM and a mixed interface module might cause the following mmc_queuecell failure message to appear:

 
 "%AAL5-3-INTERNAL_ERROR:  aal5send: mmc_queuecell failed "

Workaround: None.

CSCdv65055

Symptom: Configuring different encapsulations on 2-port Gigabit Ethernet subinterfaces clears the existing active configuration when multiple subinterfaces are present on a main interface.

Workaround: All subinterfaces have to be configured with the same encapsulation (either 802.1 Q or Inter-Switch Link [ISL]).

CSCdt21513

Symptom: Spurious memory access at lss_arm_atm_adjacency_mac is observed after there is a CLI epc portstuck-manual-reload command entered on two ATM router module interfaces, while two Catalyst 8540 MSRs are connected.

This has no functionality impact.

Workaround: None.

CSCdt11569

Symptom: Oversized packets on the enhanced ATM router module interface are observed when it is a member of a BVI. This console output relates to the oversized packets on the enhanced ATM router module interface. The following message is displayed:


00:41:36: %TBRIDGE-4-GIANT: Giant received on ATM3/0/1, 1514 exceeds 1500
DA 0100.5e00.0005 SA 0001.4274.ee09 [0x080045C0]

The system recovers from this. The cause of this may be temporary congestion in the switch fabric, leading to the loss of the last cell of the packet.

Workaround: None.

CSCds55768

Symptom: In a multi-vendor environment, if a non-Cisco IMA interface side does not support Test pattern, as specified in inverse multiplexing for ATM (IMA) specification version 1.1 by the ATM Forum, the Cisco IMA interface status might go up and down continuously.

Workaround: None.

CSCdr02365

Symptom: The output from the show bridge command is incomplete.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(12c)EY

Cisco IOS Release 12.1(12c)EY is a rebuild release for Cisco IOS Release 12.1(12c)E1. The caveats in this section are resolved in Cisco IOS Release 12.1(12c)EY but may be open in previous Cisco IOS releases.

CSCin13430

Symptom: A memory leak might occur during an "atmSoft_timerProcess". With every "soft-vc" retry the holding memory on "atmsig CC" and "atm soft CV timer" increases and the "free" memory decreases. The free memory might fall to as low as 700K at times.

Workaround: None.

CSCin10542

Symptom: After you configure a point-to-multi point connection, if you try to remove the connection from the leaf side, the following message is displayed:

% PVC de-configuration not allowed with snooping on!!
% De-configure snooping first.

Workaround: Delete the PVC or PVP from the root end.

CSCdx49779

Symptom: The switch crashes when the IPX encapsulation is changed on Fast Ethernet or Portchannel interfaces.

This might occur after you change encapsulation and then use the shutdown and the no shutdown commands.

Workaround: None.

CSCdw65903

Symptom: Multiple Cisco products contain vulnerabilities in the processing of Simple Network Management Protocol (SNMP) messages. The vulnerabilities can be repeatedly exploited to produce a denial of service. In most cases, workarounds are available that may mitigate the impact. These vulnerabilities are identified by various groups as VU#617947, VU#107186, OUSPG #0100, CAN-2002-0012, and CAN-2002-0013.

This advisory is available at http://www.cisco.com/warp/public/707/cisco-malformed-snmp-msgs-pub.shtml.

Workaround: None.

CSCdw39079

Symptom: SSH sometimes fails with the CRC-check failed error message.

Workaround: None.

CSCdw01726

Symptom: A Simple Network Management Protocol version 3 (SNMPv3) user is created by using message digest 5 (MD5) authentication with the following commands:

snmp group groupy v3 auth

snmp user abcdefghij groupy v3 auth md5 abcdefghij

An SNMP walk is performed, the configuration is saved, and the switch is reloaded.

newhope:~/src/wccp2# snmpwalk -v 3 -u abcdefghij -A abcdefghij -a MD5 -l 
AuthNoPriv 194.12.224.11

It is working and a debug SNMP header shows this:

Incoming SNMP packet
 : v3 packet    security model: v3  security level: auth
 username: abcdefghij

A second SNMP walk is performed:

newhope:~/src/wccp2# snmpwalk -v 3 -u abcdefghij -A abcdefghij -a MD5 -l 
 AuthNoPriv 194.12.224.11

After the second SNMP walk is performed, the command does not return any output and the debug SNMP headers show this:

Incoming SNMP packet
 : v3 packet  security model: v3  security level: noauth
 : username: abcdefghij

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(12c)E1

Cisco IOS Release 12.1(12c)E1 is a rebuild release for Cisco IOS Release 12.1(12c)E. The caveats in this section are resolved in Cisco IOS Release 12.1(12c)E1 but may be open in previous Cisco IOS releases.

CSCin09752

Symptom: If an IMA group exists between a Catalyst 8540 and a Catalyst 8510 switch with CBR soft VCs configured and a link of the IMA group shuts down or fails, the IMA interfaces still display the previous bandwidth value. This bandwidth value is greater than the actual resources available on the interface and the soft VCs still appear as up on both the Catalyst 8540 and Catalyst 8510 switches. This continues to happen as more links are shut down or fail until the two CBR soft VCs that require the resources of seven E1 links still appear as up with only one E1 link actually up between the IMA interfaces and the other six links that are shut down.


Note This behavior is seen when the links are either deleted from the IMA group or are shut down.


Workaround: Use the shutdown and the no shutdown commands on the IMA group and they display the correct values of available and allocated bandwidth.

CSCdx68903

Symptom: The Catalyst 8510 MSR might encounter a memory leak in ATMSIG processes and this might render the switch unusable after one month of operation.

Workaround: None.

CSCdt60582

Symptom: Two adjacent ATM devices (for example, ATM port at Catalyst 8540, ATM NIC, or Cisco 7200 router) had problems performing ILMI negotiation. The result of the ILMI negotiation is VPI/VCI range fails and the following error message appears:

%SYS-2-MALLOCFAIL: Memory allocation of 1650891065 bytes failed from 0x6066352C,
 pool Processor, alignment 0
-Process= "ILMI Response", ipl= 0, pid= 80
-Traceback= 6009E1F4 6009FCA0 60663534 60661488 6065EF94 6065E934 6009944C 60099438

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(12c)E

Cisco IOS Release 12.1(12c)E is a rebuild release for Cisco IOS Release 12.1(11)E1. The caveats in this section are resolved in Cisco IOS Release 12.1(12c)E but may be open in previous Cisco IOS releases.

CSCin09850

Symptom: When an ATM soft-VC or soft-VCP is configured between two interfaces of a Catalyst 8540 MSR using a particular VPI, and a soft-VC or soft-VCP is configured with the same VPI, the following error appears:

%ATMCORE-3-INTERNAL_ERROR: atmCore_connAllocateHalfLeg: return resource err.2

The internal error message should not appear when the soft-VC or soft-VCP configuration fails.

Plus, the following expected message is seen more than once:

connection creation fails:vpi/vci has been used

The internal error message is not seen when a PVC configuration on an interface is followed by a PVP configuration that uses the same VPI. Also, the internal error is not seen when the interface on which the configuration is being done does not have the resources required by the soft-VC or soft-VCP.

After the configuration is executed and then fails, this causes the allocation of the bandwidth requested by the CBR VC even though no VC actually exists. If, for example, N kbps is free on an interface, and a soft-VC is configured from that interface with a VPI-VCI already in use and uses a CTTR of N kbps, the configuration fails, but all N kbps that were free on that interface are lost. This bandwidth loss is seen only with the CBR service-category.


Note Using the shutdown and the no shutdown commands on the interface does not recover the lost bandwidth.


Workaround: For the Catalyst 8540 MSR, if you switch over the route processor it recovers the lost bandwidth on the interface. No workaround exists on the Catalyst 8510 MSR. No workaround exists for the following error message:

"%ATMCORE-3-INTERNAL_ERROR: atmCore_connAllocateHalfLeg: return resource err.2

CSCin09205

Symptom: If a VC is down when the switch is reloaded, the ARM subinterface stays up even though the OAM state is OAM down.

Workaround: Bring the VC up at least once after a reload.

CSCin09194

Symptom: If you configure OAM on a PVC while it is down, the OAM state of the VC is displayed as "not applicable" instead of "OAM-Down" and never changes. This means OAM cells are not sent even after the VC comes up. This only occurs if AIS is not enabled for the VC.

Workaround: Configure OAM for a VC only when it is in up state.

CSCdx09652

Symptom: After OAM detects a failure on a PVC terminating on the ATM router module (ARM), it fails to remove the adjacency, the directly connected route, and any additional route pointing to the next hop reachable over the failed PVC. This condition might stop traffic.

Workaround: There is no workaround, other than to perform an admin shutdown of the ARM subinterface (if the PVC is the last or only PVC on that subinterface). Alternatively, you could remove the PVC until the problem has been rectified.

CSCdx06532

Symptom: The PNNI-MIB object pnniLinkIfIndex(.1.3.6.1.4.1.353.5.4.1.1.9.1.11) returns 0 on the main interface running PNNI.

This problem does not exist in Cisco IOS Release 12.0(13)W5(19c) but exists in Cisco IOS Release 12.0(18)W5(22) and 12.0(20)W5(24a).

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(11b)E1

Cisco IOS Release 12.1(11b)E1 is a rebuild release for Cisco IOS Release 12.1(11b)E. The caveats in this section are resolved in Cisco IOS Release 12.1(11b)E1 but may be open in previous Cisco IOS releases.

CSCdx29693

Symptom: An ARM configured with subinterface and PVCs loses IP connectivity over the active PVCs.

Workaround: Delete and reconfigure the PVC configuration to restore connectivity.

CSCdw84540

Symptom: LightStream 1010 switches running 12.0(X)W5 Cisco IOS may not completely adhere to the ITU-T Q.2971 "B-ISDN DSS2 UNI Layer 3 Specification for Point-to-Multipoint Call/Connection Control". This could affect interoperability.

Workaround: Configure UNI version 3.1 on the LightStream 1010 ATM interfaces if the point-to-multipoint interoperability issue is observed.

CSCdw79090

Symptom: Occasionally after a system crash or route processor switchover you may see a PVC connection that exists in the interface software configuration but not does appear configured in the interface hardware.

Workaround: Perform an OIR on the interface module with the failed connection or perform a route processor switchover to restore the connection on the interface hardware.

CSCdu44017

Symptom: After deleting a connection, an immediate request to reinstall with the same VPI/VCI results in connection-creation failure messages.

Workaround: Increase the bit map size from 32 to 64, to avoid reuse of the same VPI/VCI immediately after a call is released.

Resolved Caveats—Cisco IOS Release 12.1(11b)E

Cisco IOS Release 12.1(11)E is a rebuild release for Cisco IOS Release 12.1(10)EY. The caveats in this section are resolved in Cisco IOS Release 12.1(11)E but may be open in previous Cisco IOS releases.

CSCdw55504

Symptom: AIS signal taken into account with 2 seconds delay.

Workaround: None.

CSCdw33859

Symptom: If you use the no negotiation auto command in interface config mode on a 2-port Enhanced Gigabit Ethernet interface module with GMAC-D2 (hw-version 6.0 onwards), packets larger than 1518 bytes or less than 64 bytes are filtered by the GMAC (Gigabit Ethernet Media Access Controller).

Workaround: Reload the particular interface using the epc portstuck-manual-reload interface card/subcard/port command.

CSCdw23597

Symptom: Globally changing TDP to LDP or changing LDP to TDP sometimes causes a loss of neighbors.

Workaround: Following is a four-step workaround:

1. Configure no tag-switching ip on both sides.

2. Configure the desired protocol at each end.

3. Wait two minutes.

4. Configure tag-switching ip at each end.

CSCdw22219

Symptom: If PNNI continuously receives a high rate of corrupted PTSP packets over a long period of time, it can cause a large number of internal node numbers to be generated for bogus Node IDs. If the number of internal node numbers reaches 1032, it can cause a crash.

Under normal conditions, PTSP packets should have a very low rate of being corrupted. But if PNNI interfaces are tunneled through a network where the connections are limited to too low a rate, then it can force cell drops that can corrupt packets.

Workaround: Troubleshoot and remove the cause of PTSP packet corruption.

CSCdw10624

Symptom: You might see a Bus Error exception at get_slot_ptr while trying to do the continuous snmpwalk on the ciscoLS1010SubModuleGroup object of CISCO-RHINO-MIB and simultaneously toggling the redundant power supply after at least one route processor switchover.

Workaround: None.

CSCdv67501

Symptom: Once the route processor switches over, the following error message is seen on the new primary route processor if you have a Gigabit processor interface module installed:

%ONLINEDIAG-6-ACCESS_TEST_WARNING: Unable to read from card in slot 10 sub_card 0.

Enter the show diag online access command to get more details about the failure.

Workaround: None.

CSCdv60858

Symptom: A crash occurs while configuring BVI/eigrp or while powering off the redundant power supply.

Workaround: None.

CSCdv56244

Symptom: Catalyst 8540 CSR eight-port Gigabit Ethernet interface module fails to run CLNS.

Workaround: Update to Cisco IOS Release 12.1(11b)E.

CSCdu57077

Symptom: In a network running cell-mode MPLS (tag switching) with a large number of IP routes (and consequently, with many TVCs being set up), a 16-port OC-3 interface module might fail to allocate a new TVC on a bind request and print out the following error message. This occurs even though the number of TVCs currently set up does not reach the limit of VCs supported on that interface or the cross-connect interface.

 Jun 22 20:49:02.011: %TCATM-4-RESOURCE_LIMIT: VC resource exhausted on ATMx/y/z


Workaround: Enter the shutdown command followed by the no shutdown command on the interface for which the error message appears.

CSCdu21174

Symptom: A switch router with an eight-port Gigabit Ethernet interface module might forward duplicate broadcasts when bridging is configured on a trunk.

Workaround: None.

CSCdt96927

Symptom: The Internetwork Packet Exchange (IPX) statistics sometimes fluctuate when no traffic is flowing through the interface. The only affected functionality is IPX statistics.

Workaround: None.

CSCds08237

Symptom: The hierarchical VP tunnel configuration fails on a WAI-OC3-1S3M mixed mode port adapter module when it is in slot 0 subslot 1 of the C85MS-SCAM-2P carrier module. Slot 0 subslot 0 of the carrier module can either be empty or have another card in it, and hierarchical VP tunnel configuration will still fail. However, if the mixed mode port adapter is inserted in slot 0 subslot 0 of the carrier module, then the hierarchical VP tunnel can be configured.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(10)EY

Cisco IOS Release 12.1(10)EY is a rebuild release for Cisco IOS Release 12.1(10)E. The caveats in this section are resolved in Cisco IOS Release 12.1(10)EY but may be open in previous Cisco IOS releases.

CSCdw44534

Symptom: Excessive CLP0 discards on TSCAM for PD enabled VCs.

Workaround: None.

CSCdw41639

Symptom: The LightStream 1010 switch might drop OAM F5 END Loopback cells under its default configuration of OAM intercept (which is enabled by default).

Workaround: Disable OAM intercept to avoid dropping F5 OAM cells.

CSCdw33641

Symptom: The Catalyst 8540MSR and LightStream 1010 console hangs when using the hw-module {slot number | subslot subslot/subcard} reset command on the Frame Relay E1 interface module.

Workaround: Shut down all controllers in the module before using the hw-module {slot number | subslot subslot/subcard} reset command.

CSCdv87337

Symptom: Ping fails when one of the two parallel soft VCs is missing.

Workaround: Use clear bridge command to reset bridge forwarding cache.

CSCdv13291

Symptom: After the simultaneous rebooting of switches terminating the active and passive side of soft-VC for FRF5, randomly soft-VPC stays up, but traffic might be dropped on the Frame Relay interface module. This might occur either on the active side of soft-PVC or on the passive side of the call.

Workaround:

The Frame Relay interface module starts forwarding traffic only after you use the shutdown and the no shutdown commands on the serial interface.

You might see the following error message when you reset the Frame Relay interface module:

Error Message: Channel-Group 1 State Change on FR-PAM failed 1

For additional details, refer to DDTS CSCdv17817.

Resolved Caveats—Cisco IOS Release 12.1(10)E

Cisco IOS Release 12.1(10)E is a rebuild release for Cisco IOS Release 12.1(7a)EY1. The caveats in this section are resolved in Cisco IOS Release 12.1(10)E but may be open in previous Cisco IOS releases.

CSCdw33267

Symptom: Load balancing between provider edge (PE) to provider (P) switches and provider edge to provider edge does not work. If MPLS is enabled on the switch router running Cisco IOS Release 12.1 software, MPLS might not resolve all dependant routes for a path if you enter the shut/noshut or the clear ip route commands on the outgoing interface of the next hop router.

Workaround: None.

CSCdv48352

Symptom: When running Cisco IOS Release 12.0(18)W5(22) on a Catalyst 8540 MSR or on a LightStream 1010, interoperability problems occur when peers run an older Cisco IOS version, and tunnels and SVC/Soft VCs are used.

Workaround: Upgrade all switches to the most current Cisco IOS release.

CSCdv45286

Symptom: Point-to-multipoint PVCs that are configured by using SNMP are not preserved across route processor switchovers.

Workaround: Disable the dynamic synchronization feature.

CSCdv39328

Symptom: When using a Packet Over SONET card, the Open Shortest Path First (OSPF) routes do not come up after a route processor switchover, even though they were up before the switchover.

Workaround: None

CSCdv32093

Symptom: The switch might reload when VP tunnels are created and removed.

Workaround: None.

CSCdv21398

Symptom: The Management Information Base (MIB) object "ifAdminStatus" shows up for an ADMIN DOWN E1 Controller after a reload or a route processor switchover.

Workaround: Enter the shutdown and the no shutdown command sequence on the controller.

CSCdv15245

Symptom: With a Frame Relay-ATM soft-VC set up in FRF5, UPC on the passive side is always set to PASS, regardless of the hard setting on the serial interface with the frame-relay upc-intent tag-drop command. The default is PASS. When this is changed to tag-drop, the configuration does not reflect the change and the show vc int serial command always shows the UPC intent as PASS.

Workaround: None.

CSCdu78056

Symptom: The SNMP TRAP object ccrCpuStatusChange returns an invalid value.

Workaround: None.

CSCdu69809

Symptom: A port of a 4-port DS3 port adapter for LightStream 1010s and for Catalyst 8540s is in a yellow or red alarm state, and stops sending DS3 framing for a brief time when the alarm is cleared from the interface and the interface transitions to an UP/UP state. The loss of frame (LOF) can be seen when the Acterna tool TBERD is connected to the TX port of the DS3 port.

Workaround: None.

CSCdu50525

Symptom: The EIGRP summary routes are not properly populated in the adjacency table when a default route also exists. This affects the Fast Ethernet and ATM router module interfaces, but does not impact the Gigabit Ethernet interfaces.

Workaround: None.

CSCdu44352

Symptom: A Cisco edge services router (ESR) that is running Cisco IOS Release 12.1(2)E1 experiences interoperability problems when an ATM traffic descriptor information element is included in the CONNECT message on a non-negotiated link. Under such conditions, a STATUS message is sent with cause "invalid information element contents (100)" and the call does not succeed. This problem is observed when Cisco routers are connected to other vendor switches like FORE, and occurs only when UNI version is 4.0.

Workaround: None.

CSCdu20618

Symptom: One side of a circuit emulation service (CES) E1 port of a LightStream LS1010 switch connection remains consistently in the YELLOW alarm or ALARM INTEGRATION state.

Workaround: None.

CSCdt96389

Symptom: After rebooting the switch router, Ethernet interfaces might have invalid MAC addresses, causing connectivity problems over that interface.

Workaround: Enter the shutdown command and then the no shutdown command on the affected Ethernet interfaces.

CSCdt71010

Symptom: The ifTable indexes do not match the MIB-II table indexes.

Workaround: None.

CSCds28912

Symptom: IP traffic is not sent over a PVC if aal5mux encapsulation is used on a point-to-point subinterface on the Catalyst 8540 MSR. If the debug atm errors command is enabled, the following error messages appears:

point-to-point interface does not have a VCD

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(7a)EY1

Cisco IOS Release 12.1(7a)EY1 is a rebuild release for Cisco IOS Release 12.1(7a)EY. The caveats in this section are resolved in Cisco IOS Release 12.1(7a)EY1 but may be open in previous Cisco IOS releases.

CSCdv43426

Symptom: When a Catalyst 8540 MSR has a large number of inverse multiplexing over ATM (IMA) port adapter modules, a message similar to the following is generated:

-Process= "IMAPAM Onesec", ipl= 6, pid= 70 
-Traceback= 600D8280 600D8644 6049F928 600C03CC 600C03B8
%SCHED-3-THRASHING: Process thrashing on watched message event.

Workaround: None.

CSCdv15238

Symptom: Cisco Discovery Protocol (CDP) does not work over port channel platforms.

Workaround: None.

CSCdv11518

Symptom: After the Tag Distribution Protocol (TDP) toggles from down to up ("flaps") on the Label Controlled ATM (LC-ATM) interface, it takes a long time for the interface to become TDP ready. Entering the show tag-switching tdp discovery command might indicate that TDP is not ready, and TVCs might still be allocated on the interface. This can occur under stressful conditions in which cross-connections fail to be deallocated on the ATM switching fabric.

Workaround: None.

CSCdv07613

Symptom: Under stressful conditions such as large topology changes, TVC cross-connections might fail to be removed from the ATM switching fabric, causing the TC-ATM function to repeat attempts to remove the TVCs. This might lead to the TC-ATM state process entering a bad state and to displaying an error message.

Workaround: None.

CSCdv06370

Symptom: Not all of the contents of the atmVcCrossConnectTable can be seen after the removal and reinsertion of a module. This message is seen on the console during some Simple Network Management Protocol (SNMP) get operations:

%ATMCORE-3-INTERNAL_ERROR: ATOM ERROR: ifCB_p=NULL for lowIf 

Workaround: None.

CSCdu86398

Symptom: What is present in the Patricia trie in the Ethernet processor interface is out of synchronization with what is present in IP Cisco Express Forwarding (CEF). This might cause connectivity problems. This problem only exists on Ethernet processor interfaces; entries in the Switching Database Manager (SDM) on Gigabit processor interface cards are not affected.

Workaround: Find the route (for example, the route network_x) that is not consistent with IP CEF; enter (in the case of this example) the clear ip route network_x command.

CSCdu83797

Symptom: Some point-to-multipoint cross-connect entries are missing from the atmVcCrossConnectTable when the point-to-multipoint root if-index is higher than the if-index of the leaves.

Workaround: None.

CSCdu83707

Symptom: Interfaces with Tag enabled get stuck in the TDP not ready state.

Workaround: None. The only way to bring up the Tag on such interfaces is by performing a system reload.

CSCdu83704

Symptom: During TagVC installation, if the switch driver returns an error, the Connection Manager leaves the TagVC in the wrong FSM state. This can lead to TVCs existing on an interface when there are no tag bindings.

Workaround: None; reload the switch to clear such unused TVCs.

CSCdu82922

Symptom: When running Cisco IOS Release 12.0(13)W05(19), a bus error causes the system to restart. This occurs when an 8-port Gigabit Ethernet card with control traffic is at or near its traffic capacity.

Workaround: None.

CSCdu78141

Symptom: If a large frame or packet (more than 6096 bytes) is received on the tag control virtual circuit (0/32 of an interface enabled for tag switching), the frame is not purged from the switch fabric. Subsequent packets received on this virtual circuit are dropped, causing the Tag Distribution Protocol (TDP) and the routing session (OSPF) to time out.

Workaround: Disable, then reenable, tag switching on the affected interface; subsequent occurrences can be avoided by increasing the queue depth, using the following entry:

atm threshold 2 max-queue-limit 511

CSCdu74491

Symptom: After reloading the core switch, all neighboring switches running Cisco IOS Release 12.0(16)W6(21) or 12.0(16)W6(21a) crash, and a message similar to the following is generated:

Jul 14 05:00:09: %ATMSIG-3-FAILXCONN: Xconnect failed, xconn fail 
-Traceback= 6054A204 6054C0A0 60556188 60545538 6054561C 6009930C 600992F8
Queued messages:
Jul 14 05:00:09: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging 
output.
Jul 14 05:00:09: %ATMSIG-3-FAILXCONN: Xconnect failed, xconn fail 
-Traceback= 6054A204 6054C0A0 60556188 60545538 6054561C 6009930C 600992F8
Jul 14 05:00:09: ATMSIG(10/0/0:0 0,66 - 0004/25): (vcnum:0) XConnected failed To 
Jul 14 05:00:09: ATMSIG(ATM13/0/0 0,111 - 0046/25): (vcnum:111)
Jul 14 05:00:09: ATMSIG: CONNECTION MANAGER/CAC Xconn install request  
Port A -  (10/0/0) : 0  vpi = 0; vci = 66  
Port B -  (13/0/0) : 0  vpi = 0; vci = 111; new vpi = 0; new vci = 111 existing 
vpi/vci for leg B 
Jul 14 05:00:09: ATMSIG: CONNECTION MANAGER/CAC Xconn install result  
CONN_INSTALL_RESULT_HW_FAIL

Workaround: None.

CSCdt13517

Symptom: A LightStream 1010 stops switching some VCs, and log error messages similar to the following example are generated:

Jan  9 12:37:34.793: ATMSIG(12/1/0:0 0,37 - 274610/00): (vcnum:0) XConnected failed To
Jan  9 12:37:34.793: ATMSIG(12/0/1:0 0,268 - 398903/00): (vcnum:0)
Jan  9 12:37:34.793: ATMSIG: CONNECTION MANAGER/CAC Xconn install request         
Port A -  (12/1/0) : 0  vpi = 0; vci = 37         
Port B -  (12/0/1) : 0  vpi = 0; vci = 268; new vpi = 0; new vci = 268 existing 
vpi/vci for leg B
Jan  9 12:37:34.793: ATMSIG: CONNECTION MANAGER/CAC Xconn install result        
CONN_INSTALL_RESULT_HW_FAIL

Workaround: Reload the switch.

CSCds78385

Symptom: When using the Internetwork Packet Exchange (IPX), the output of the traceroute command skips the middle hop when the middle router is a Catalyst 8540/8510 MSR, Catalyst 8540/8510 CSR, or LightStream 1010.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(7a)EY

Cisco IOS Release 12.1(7a)EY is a rebuild release for Cisco IOS Release 12.1(6)EY1. The caveats in this section are resolved in Cisco IOS Release 12.1(7a)EY but may be open in previous Cisco IOS releases.

CSCdu56774

Symptom: In Cisco IOS Release 12.1(6)EY and earlier, only two equal-cost IP paths were supported on Fast Ethernet and Gigabit Ethernet interface modules that were based on an Ethernet processor interface.

Workaround: Upgrade to Cisco IOS Release 12.1(7a)EY; in that release, four-path load balancing for IP is available through use of the epc epif-4-path-lbal command.

CSCdu24272

Symptom: When entering the show atm ilmi-status command the switch shows the 0.0.0.0 as a peer IP address even though a loopback address is configured.

Workaround: None.

CSCdt91339

Symptom: In the ATM-MIB there is an atmVcCrossConnectTable that allows SNMP to create VC cross-connects. It is not possible to create multipoint connections. At the time of creating the second entry corresponding to the multipoint connection, SNMP reports the following error:

# ./snmpset -c private lore atmVcCrossConnectRowStatus.8431167.3.0.51.2.0.41 integer 5 
atmMIB.atmMIBObjects.atmVcCrossConnectTable.atmVcCrossConnectEntry.atmVcCrossConnectRo
wStatus.8431167.3.0.51.2.0.41 : INTEGER: createAndWait # ./snmpset -c private lore 
atmVcCrossConnectRowStatus.8431167.3.0.51.3.0.55 integer 5 snmpset: Agent reported 
error with variable #1. 
.iso.org.dod.internet.mgmt.mib-2.atmMIB.atmMIBObjects.atmVcCrossConnectTable.atmVcCros
sConnectEntry.atmVcCrossConnectRowStatus.8431167.3.0.51.3.0.55:  SNMP: A general 
failure occurred on the agent.

Workaround: None.

CSCdt73634

Symptom: If an interface comes up after the system initialization, the scheduler for that interface might not be programmed correctly. Since IMA interfaces come up after system initialization, IMA interfaces are usually affected by this.

Workaround: Enter the shutdown command on the IMA interface. Take the first link on the IMA interface out of the IMA group. Bring that interface up. Shut down that interface and then make it part of the IMA group. Enter the no shutdown command to bring the IMA interface up.

CSCdt45629

Symptom: When the switch router is under stress because there are greater than 1000 TVCs on a given interface, some TVCs might not get set up successfully and the following error message occurs:

 %TCATM-4-RESOURCE_LIMIT: VC resource exhausted


Workaround: Configure less than 1000 TVCs on the interfaces.

CSCdt44914

Symptom: The transmit side of a tag-enabled ATM interface may go into the "not TDP ready" state. Use the show tag tdp discovery command to verify that it is in the "not TDP ready" state. As a consequence, Tag is inactive on that interface.

Workaround: Enter the shutdown command followed by the no shutdown command. If this does not work, there is no workaround.

CSCdp20865

Symptom: Performing a shutdown/no shutdown command sequence on an ATM router module interface, especially when it has configured a large number of LANE clients, might cause an error message like this to appear:

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

It indicates an internal timeout occurred. It should try to self-cover and not affect any normal operations.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(6)EY

Cisco IOS Release 12.1(6)E is a rebuild release for Cisco IOS Release 12.1(5)EY1. The caveats in this section are resolved in Cisco IOS Release 12.1(6)EY but may be open in previous Cisco IOS releases.

CSCdt93866

Symptom: Sending a crafted control NTP packet might cause a buffer overflow.

Workaround: Include the "ntp access-group serve-only" line in the configuration of the router.

CSCdt86157

Symptom: The snmp polling of the virtual path mibs atmVplLastChange and atmVplOperstatus results in unavailability of the virtual path. But the polling of the virtual circuit in this virtual path states that it is available.

Workaround: None.

CSCdt63813

Symptom: A LightStream 1010 switch router might automatically reload. When you enter the show version command, the switch reports the reason as "System was restarted by error - a Software forced crash". In addition, the log error message might say:

"SYS-6-BLKINFO: Corrupted @redzone blk" 

Other messages indicating memory corruption might also occur.

Workaround: None.

CSCdt62215

Symptom: After resetting a switch or router that is connected to a CES port on a LightStream 1010 or Catalyst 8510, there is connectivity above the physical layer.

Workaround: Enter the shutdown command and then the no shutdown command on the CBR interface of the LightStream 1010 or Catalyst 8510.

CSCdt47492

Symptom: ILMI might stay in the "waitdevtype" state after a redundancy failover. This is because on an OC-3 port adapter, each of the four ports are served by one processor interface. The first port needs to be set for the other three ports to be able to receive. Sometimes this does not occur on a redundancy failover.

Workaround: Bring up port 0, if problem is seen on ports 1to 3; bring up port 4, if problem is seen on ports 5 to 7; bring up port 8, if problem is seen on ports 9 to 11; bring up port 12, if problem is seen on ports 14 to 15. The ports can be brought up by connecting a loopback cable, or by simply using that port.

CSCdt40530

Symptom: When access is made to PNNI tables, a memory leak might occur. This only happens when an Network Management System (NMS) is running SNMP on the switch router.

Workaround: Turn off NMS polling of PNNI tables and instead use the commands for determining any PNNI information.

CSCdt38604

Symptom: An IP address might not be learned by peer switch when using ILMI status.

Workaround: None.

CSCdt17850

Symptom: The outbound ACL fails to filter packets in the subinterface when the static ARP is configured and the ACL is used with it. If a static ARP is configured and the same address is moved from an interface to a subinterface of the same interface, the static ARP entry remains associated with the main interface itself.

Workaround: If the IP address is reconfigured to a subinterface of a main interface, then delete and reconfigure the ARP address.

CSCdt15978

Symptom: Telnet responses between two switch routers might be very slow.

Workaround: Replace one switch router with another that can accept ISL frames less than 94B in size (for instance, the Catalyst 5000).

CSCdt09229

Symptom: The switch router might loose traffic on its LANE or 1483 or 1577 interfaces on an ATM router module. Frame interfaces or non-LANE interfaces on an ATM router module with configured PVCs should pass traffic without any problems. It doesn't matter if the traffic is going to a route processor or not, part of the traffic is lost.

Workaround: The switch router recovers from this state only after an OIR of the module or a reload.

CSCdt05674

Symptom: A switch with a lot of FC-PCQ connections or running a lot of LANE traffic, might display the following message when the interface carrying most of the traffic is shut down:

../src-4k-ls1010/mmc_dvr.c 2428 PORT DIED: 0/0/0, taking off line

Workaround: None.

CSCds85282

Symptom: In the Cisco IOS release image ls1010-wp-mz.120-13.W5.19, the LS1010 power on diagnostic test causes the IOS not to boot while the ATM router module and Fast Ethernet modules are installed.

Workaround: Upgrade to Cisco IOS Release ls1010-wp-mz.120-13.W5.19a.

CSCds40925

Symptom: When entering the show atm interface traffic command on an ATM subinterface, the total number of cells that has passed might show as zero. This rate is incorrect.

Workaround: None.

CSCdr43326

Symptom: The atmVcCrossConnectAdminStatus entries might disappear.

Workaround: None.

CSCdr28797

Symptom: HVPT: Incorrect scheduling values installed for low PCR. When a HVPT with a PCR of 2 kbps is configured on a OC-3 interface, this results in the cell starving of WKVC on the main interface.

Workaround: None.

Resolved Caveats—Cisco IOS Release 12.1(5)EY1

Cisco IOS Release 12.1(5a)EY1 is a new build of a Cisco IOS Release. The caveats in this section are resolved in Cisco IOS Release 12.1(5a)EY1 but may be open in previous Cisco IOS releases.

CSCdt63152

Symptom: HSRP cannot be configured on Cisco IOS Release 12.1(5)EY1 image on the Catalyst 8510 MSR platform.

Workaround: None.

CSCdt53814

Symptom: An ATM router module port configured for transparent bridging and in blocking state may forward certain frames.

Workaround: Ensure that a non-ATM router module port is in blocking state. If this is not feasible, physically shut down the ATM router module port that is in blocking state.

CSCdt43218

Symptom: The IP PAT tree becomes programmed incorrectly for 1483 SVC after removing the ATM router module. If an SVC is configured on an ATM router module/enhanced ATM router module card and the card is OIRed, the adjacency available across the SVC will remain valid in the EPIF/XPIF cam. This results in packets destined to that adjacency to disappear.

Workaround: Before OIRing an ATM router module/enhanced ATM router module, remove any subinterfaces that have a SVC configurations, then proceed to do the OIR.

CSCdt24278

Symptom: The ATM router module sets the CLP of all cells to 1 when bridging is configured over a 1483 PVC. This happens for cells being transmitted over the 1483 PVC only.

Workaround: None.

CSCdt18467

Symptom: Port stuck messages might not log into the system log.

Workaround: None.

CSCdt01582

Symptom: On Cisco IOS Release 12.0(10)W5(18b), when the module with c8510-ACL is in the Catalyst 5500 chassis, the show hardware command does not show the ACL daughter card.

Workaround: None.

CSCds81263

Symptom: The IP CEF adjacencies are reported as invalid when using the ATM router module configured with LANE clients on the Catalyst 8540 MSR. The router reports an invalid cached adjacency for ip addresses that is not reachable through the LANE interface when running the show ip cef ip address command.

For example:

show ip cef 207.18.18.0
 207.18.18.0/24, version 25, cached adjacency to ATM11/0/0.1
 0 packets, 0 bytes
   via 207.18.19.1, ATM11/0/0.1, 0 dependencies
     next hop 207.18.19.1, ATM11/0/0.1
     invalid cached adjacency

With an invalid cache adjacency, all the packets destined to this address are sent to the route processor for processing.

The CEF adjacency are invalid until a LANE data direct VC and valid LE-ARP entry are established on the adjacent device. As soon as the data direct VC and LE-ARP entry are established, the adjacency are reported as valid.

Workaround: None.

CSCds69507

Symptom: If the HSRP has been configured on a Catalyst 8500 running an Cisco IOS Release 12.0(10)W5(18c), and the ATM router module is removed and then reinserted, the HSRP configuration is lost.

Workaround: None.

CSCds57646

Symptom: When a ping command is entered from one member of a BVI to the outside, it causes some pings between members of the BVI to time out.

Workaround: None.

CSCdr79972

Symptom: The ATM router module always signals a fixed value for the PCR if LANE is configured on the ATM router module. The hidden CLI gives a way to signal the user-configured PCR. This will help with ATM traffic shaping/policing by the ATM nodes in between.

Workaround: None.

CSCdr70086

Symptom: The IP adjacencies are not being cleared from the Gigabit Ethernet module quickly. The show epc ip-address command was issued on the adjacency. It was found that the entry for the host on vlan2 was still there and took some time to clear. As soon as it did clear, the ping command worked again.

Workaround: None.

CSCdr36952

Symptom: The switch router crashes and hangs 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 that are widely read by both 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 through 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.

CSCdr35301

Symptom: ifOutOctets wraps at 3000000 on an ATM interface.

Workaround: None.

CSCdr16095

Symptom: On rare occasions the switch fails SVC setups even when physical connectivity is established.

Workaround: Reload the switch.

CSCdk56557

Symptom: Spurious memory access on the show ip route command output when SONICT interface is shut down.

If you shut down a 10-Mbps port and then use the show ip route command, spurious memory access appears in the print_route_preamble():

Workaround: None.

Related Documentation

Regulatory Compliance and Safety Information for the Catalyst 8500 and LightStream 1010 Series

Site Preparation

Quick Reference Catalyst 8510 and LightStream 1010 Hardware Information

ATM and Layer 3 Module Installation Guide

Guide to ATM Technology

ATM and Layer 3 Quick Software Configuration Guide

ATM and Layer 3 Switch Router Command Reference

ATM Switch Router Software Configuration Guide

Layer 3 Software Feature and Configuration Guide

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html