Table of Contents
Release Notes for the Catalyst 8510 and theLightStream 1010 Switch for
Cisco IOS Release 12.1(14)E1
Contents
Introduction
System Requirements
Hardware Supported
Determining Your Software Release
Other Firmware Code
Feature Set Tables
Release Names, Versions, and Part Numbers
New Features in Release 12.1(13)EB
New Features in Release 12.1(13)E1
New Features in Release 12.1(12c)EY
New Features in Release 12.1(12c)E1
New Features in Release 12.1(12c)E
New Features in Release 12.1(11b)E1
New Features in Release 12.1(11b)E
New Features in Release 12.1(10)EY
New Features in Release 12.1(10)E
New Features in Release 12.1(7a)EY1
New Features in Cisco IOS Release 12.1(7a)EY
New Features in Cisco IOS Release 12.1(6)EY
New Features in Cisco IOS Release 12.1(5)EY1
Caveat Symptoms and Workarounds
Interoperability
Y2K Compliance
Related Documentation
Documentation CD-ROM
Obtaining Documentation
Obtaining Technical Assistance
Release Notes for the Catalyst 8510 and the
LightStream 1010 Switch for
Cisco IOS Release 12.1(14)E1
Catalyst 8510 and LightStream 1010 Switch Cisco IOS Release 12.1(14)E1
Text Part Number: OL-2551-07 Rev. A0
This document describes the features and caveats for Cisco IOS Release 12.1(14)E1 software for the Catalyst 8510 and the LightStream 1010 switch.
![]() |
Note All information pertains to both the Catalyst 8510 and LightStream 1010 switch platforms, unless differences between the platforms are noted in the text. |
Contents
This document includes the following sections:
Introduction
The Catalyst 8510 and LightStream 1010 switch provide switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.
![]() |
Note The ATM switch processors (hardware version 4.0 or higher) and all port adapters can be installed in the Catalyst 5500 switch chassis. |
The Catalyst 8510 CSR belongs to a class of high-performance Layer 3 switch routers. It is optimized for the campus LAN or the intranet and provides both wirespeed Ethernet routing and switching services.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.0 and includes the following sections:
Memory Requirements
Catalyst 8510 MSR and LightStream 1010
The DRAM memory configuration is 64-MB DRAM (MEM-ASP64M), which is the default for both the Catalyst 8510 and the LightStream 1010 switch platforms.
Catalyst 8510 CSR
Table 1 lists the default Flash and DRAM memory for the Catalyst 8510 CSR, as well as memory upgrade options.
Table 1 Catalyst 8510 CSR Default Memory and Upgrade Options
| Memory Type | Catalyst 8510 CSR Defaults | Upgrade Options |
|---|---|---|
To download and store a copy of the Catalyst 8510 CSR software image, we recommend using a minimum 20 MB Flash PC Card, which will allow you to have two or more images installed at the same time.
The Catalyst 8510 CSR boots from its onboard Flash memory by default. To change this default to boot from a Flash PC Card instead, you must change the configuration register setting to 0x2102. Refer to the Layer 3 Switching Software Feature and Configuration Guide for more information.
Hardware Supported
Table 2 lists the interfaces supported by both the Catalyst 8510 MSR and LightStream 1010 switch and Cisco IOS Release 12.1(14)E1 and their minimum software release requirements. All platform specific requirements are noted in the table. Table 3 lists this information for the Catalyst 8510 CSR.
![]() |
Note Although minimum software versions are listed, we strongly recommend that you use the latest available software release for all Catalyst 8510 and LightStream 1010 hardware. |
Table 2 Catalyst 8510 MSR and LightStream 1010 Interface Modules and
Minimum Software Required
| Part Number | Description | Minimum Software Version Required |
|---|---|---|
|
4-port T1 (circuit emulation) with RJ-48 interface port adapters |
||
|
4-port E1 (circuit emulation) with RJ-48 interface port adapters |
||
|
4-port E1 (circuit emulation) with BNC interface port adapters |
||
|
ASP1 with FC-per-flow queuing (FC-PFQ3) |
||
|
Catalyst 8510 MSR: S851R2-12107EY LightStream 1010: SL10R2-12107EY |
| 1ASP = ATM switch processor.
2FC-PCQ = feature card per-class queuing. 3FC-PFQ = feature card per-flow queuing. 4IMA = inverse multiplexing over ATM. 5The LightStream 1010 switch requires the ASP-C with FC-PFQ to support the ATM router module. 6ACL = access control list. |
Table 3 Catalyst 8510 CSR Interface Modules and Minimum Software Required
| Part Number | Description | Minimum Software Version Required |
|---|---|---|
| Route Processors, Switch Cards, and Daughter Cards | ||
| Gigabit Ethernet Interface Modules | ||
| Fast Ethernet Interface Modules | ||
Determining Your Software Release
To determine the version of Cisco IOS software currently running on either the Catalyst 8510 or the LightStream 1010 switch, log in to the switch and enter the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below:
Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
Other Firmware Code
Some of the port adapters supported on the Catalyst 8510 and LightStream 1010 switch have upgradeable FPGA and functional images. The FPGA and functional images include caveat fixes, but in most cases, it is not necessary to upgrade. The release notes that describe the caveats from the FPGA and functional images are available on the World Wide Web at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/fpga_rel/index.htm
For information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8510 and LightStream 1010)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide.
Feature Set Tables
The Cisco IOS release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 4 lists the Cisco IOS software feature sets available for the Catalyst 8510 MSR and LightStream 1010 switch in Cisco IOS Release 12.1(14)E1. Table 5 lists the software feature sets available for the Catalyst 8510 CSR.
Table 4 Feature Sets Supported by the Catalyst 8510 MSR and LightStream 1010 Switch
| 1SNMP = Simple Network Management Protocol.
2PPP = Point-to-Point Protocol. 3SLIP = Serial Line Internet Protocol. 4IP = Internet Protocol. 5NTP = Network Time Protocol. 6TACACS+ = Terminal Access Controller Access Control System Plus. 7VCCs = virtual channel connections. 8VPCs = virtual path connections. 9IISP = Interim-Interswitch Signaling Protocol. 10LANE = LAN emulation. 11LEC = LAN emulation client. 12LES = LAN emulation server. 13BUS = broadcast and unknown server. 14LECS = LAN emulation configuration server. 15ASP = ATM switch processor. 16ARP = Address Resolution Protocol. 17OAM = Operation, Administration, and Maintenance. 18RMON = Remote Monitoring. 19MCR = minimum cell rate. 20You can download the Catalyst 8510 software image on a LightStream 1010 switch to support L3-ATM (via the ATM router module). However, the LightStream 1010 switch software image does not include support for the ATM router module. |
Table 5 Feature Sets Supported by the Catalyst 8510 CSR
| 1redundancy |
Release Names, Versions, and Part Numbers
Table 6 lists the release names, versions, and part numbers used with the Catalyst 8510 MSR and LightStream 1010 switch. Platform-specific information is noted in the table.Table 7 lists the release names, versions, and part numbers used with the Catalyst 8510 CSR.
Table 6 Release Name to Version and Part Number Matrix for Catalyst 8510 MSR and LightStream 1010
| Release Name | Release Version | Part Number |
|---|---|---|
|
Catalyst 8510 MSR: S851R2-12105EY |
||
Table 7 Release Name to Version and Part Number Matrix for Catalyst 8510 CSR Switch Routers
| Release Name | Release Version | Part Number |
|---|---|---|
New and Changed Information
This section includes new features that appear in this and previous releases of Cisco IOS release 12.1 software. The new features are sorted by release number.
New Features in Release 12.1(14)E1
Catalyst 8510 MSR and LightStream 1010
The following new feature is available for the Catalyst 8510 MSR in Cisco IOS Release 12.1(14)E1:
Catalyst 8510 CSR
There are no new features for the Catalyst 8510 CSR in Cisco IOS Release 12.1(14)E1.
New Features in Release 12.1(13)EB
Catalyst 8510 MSR and LightStream 1010
The following new features are available for the Catalyst 8510 MSR in Cisco IOS Release 12.1(13)EB:
- Point-to-Multipoint Soft PVCs
- Overflow Queuing for VBR-nrt on Frame Relay interface modules
- Configuring Frame Relay frame size for Frame Relay-ATM interworking
- Configuring Service Class Overbooking
- Soft-PVC support on ATM 0 interface
- RFC-2515 support
- Traffic parameter modification for Soft VCs and Soft VPs
Catalyst 8510 CSR
There are no new features for the Catalyst 8510 CSR in Cisco IOS Release 12.1(13)EB.
New Features in Release 12.1(13)E1
There are no new features in Cisco IOS Release 12.1(13)E1.
New Features in Release 12.1(12c)EY
Catalyst 8510 MSR
The following new features are available for the Catalyst 8510 MSR in Cisco IOS Release 12.1(12c)EY:
Catalyst 8510 CSR
There are no new features the Catalyst 8510 CSR in Cisco IOS Release 12.1(12c)EY.
New Features in Release 12.1(12c)E1
There are no new features in Cisco IOS Release 12.1(12c)E1.
New Features in Release 12.1(12c)E
Catalyst 8510 MSR
The following new feature is available for the Catalyst 8510 MSR in Cisco IOS Release 12.1(12c)E:
Catalyst 8510 CSR
There are no new features the Catalyst 8510 CSR in Cisco IOS Release 12.1(12c)E.
New Features in Release 12.1(11b)E1
There are no new features in Cisco IOS Release 12.1(11b)E1.
New Features in Release 12.1(11b)E
There are no new features in Cisco IOS Release 12.1(11b)E.
New Features in Release 12.1(10)EY
Catalyst 8510 MSR and LightStream 1010
The following features are available for the Catalyst 8510 and LightStream 1010 switch routers in Cisco IOS Release 12.1(10)EY:
- MPLS LDP (Label Distribution Protocol) support for both LSR (label switch router) and LER
- MPLS LER on the 10/100 Base-TX, 100 Base-FX interface modules
- Frame Relay PVCs terminated on ATM router module
- SONET MIB (RFC 2558)
- Two Ended Soft VC Configuration
- PNNI Connection Trace
- IP Multicast Over VC Mux Encapsulation
Catalyst 8510 CSR
The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.1(10)EY:
New Features in Release 12.1(10)E
Catalyst 8510 MSR and LightStream 1010
The following features are available for the Catalyst 8510 and LightStream 1010 switch routers in
Cisco IOS Release 12.1(10)E:
Catalyst 8510 CSR
There are no new features for the Catalyst 8510 CSR in Cisco IOS Release 12.1(10)E.
New Features in Release 12.1(7a)EY1
Catalyst 8510 MSR and LightStream 1010
The following features are available for the Catalyst 8510 and LightStream 1010 switch routers in
Cisco IOS Release 12.1(7a)EY1:
Catalyst 8510 CSR
The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.1(7a)EY1:
- Multiprotocol Label Switching (MPLS), Label Edge Router (LER) on Gigabit Ethernet interface modules and POS uplinks.
- IP QoS support on Gigabit Ethernet interface modules.
- VC Bundling on the ATM uplink module.
- CiscoView Autonomous Device Package (ADP).
- Policy Based Routing (PBR).
- Packet-Over-SONET Automatic Protection Switching (APS).
- Rate Limiting and per port Traffic Shaping.
New Features in Cisco IOS Release 12.1(7a)EY
Catalyst 8510 MSR
The following features are available for the Catalyst 8510 and LightStream 1010 switch routers in Cisco IOS Release 12.1(7a)EY:
- VBR on ATM router module support (Catalyst 8510 MSR and LightStream 1010 Only)
- Shaped Tunnel Support for ATM router module (Catalyst 8510 MSR and LightStream 1010 only)
- Rate Limiting
- Traffic-Shaping Carrier Module (TSCAM) (Catalyst 8510 MSR and LightStream 1010 only)
- ADP (Catalyst 8510 MSR and LightStream 1010 only)
- Radius Support (TACACS+-like authentication) (Catalyst 8510 MSR and LightStream 1010 only)
Catalyst 8510 CSR
There are no new features the Catalyst 8510 CSR in Cisco IOS Release 12.1(7a)EY.
New Features in Cisco IOS Release 12.1(6)EY
Catalyst 8510 MSR
The following new features are available for the Catalyst 8510 and LightStream 1010 switch routers in Cisco IOS Release 12.1(6)EY:
Catalyst 8510 CSR
The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.1(6)EY:
New Features in Cisco IOS Release 12.1(5)EY1
Catalyst 8510 MSR
The following new features are available for the Catalyst 8510 and the LightStream 1010 switch in Cisco IOS Release 12.1(5)EY1.
Catalyst 8510 CSR
The following new feature is available for the Catalyst 8510 CSR in Cisco IOS Release 12.1(5)EY1:
See the "Related Documentation" section for a list of documents that describe this feature.
Caveats for the Catalyst 8510 CSR and LightStream 1010
This section lists the caveats and corrected caveats for each release. Use Table 8 to determine the status of a particular caveat for the Catalyst 8510 MSR or the LightStream 1010 and its relevancy to your software release. Use Table 9 to determine the status of a particular caveat for the Catalyst 8510 CSR and its relevancy to your software release. In Table 8 and Table 9, "C" indicates a fixed or closed caveat, and "O" indicates an open or unresolved caveat. Platform specific caveats are appropriately indicated.
Table 8 Caveat Matrix for Catalyst 8510 MSR and LightStream 1010
| DDTS # | 12.1 (14) E1 |
12.1 (13) E1 |
12.1 (12c) EY |
12.1 (12c) E1 |
12.1 (12c) E |
12.1 (11b) E1 |
12.1 (11b) E |
12.1 (10) EY |
12.1 (10) E |
12.1 (7a) EY1 |
12.1 (7a) EY |
12. 1(6) EY |
12.1 (5) EY1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
CSCdv39328 |
|||||||||||||
|
CSCdv15238 |
|||||||||||||
|
CSCdu86398 |
|||||||||||||
|
CSCdu82922 |
|||||||||||||
|
CSCdu56774 |
|||||||||||||
|
CSCdu20618 |
|||||||||||||
|
CSCdt96927 |
|||||||||||||
|
CSCdt62215 |
|||||||||||||
|
CSCdt05674 |
|||||||||||||
|
CSCds78385 |
|||||||||||||
|
CSCdm04186 |
|||||||||||||
Table 9 Caveat Matrix for Catalyst 8510 CSR
| DDTS # | 12.1(10)E | 12.1(7a)EY1 | 12.1(7a)EY | 12.1(6)EY | 12.1(5)EY1 |
|---|---|---|---|---|---|
Caveat Symptoms and Workarounds
This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8510 switch and the LightStream 1010 switch.
![]() |
Note The maximum number of ELAN LES/BUS pairs that the ATM switch processor interface supports is 10. On configuring a Frame Relay NIW/SIW PVC, a small number of discarded frames are occasionally seen due to CRC errors. These discards happen even without passing traffic. |
Symptom: The CBR interface module sends a "remote alarm" to the peer interface if the line flaps continuously. This causes the peer interface to change to "yellow alarm" state.
Workaround: Enter the shutdown and no shutdown commands on the CBR interface.
Symptom: 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.
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.
Symptom: An ATM interface might stick in the state "going down" 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".
Workaround: Recreate the PVC using any VCI other than "34" on the ATM side.
Symptom: Signaling is reset on other interfaces of the device that are not connected to the peer switch being reloaded.
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:
Workaround: Delete the PVC or PVP from the root end.
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:
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:
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 no shutdown commands on the interface does not recover the lost bandwidth. |
Workaround: For the Catalyst 8540 MSR, if you switchover 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:
Symptom: If an IMA group exists between a Catalyst 8540 and Catalyst 8510 switches with CBR soft VCs configured between the switches and a link of the IMA group is shut down or fails, the IMA interfaces still display the pervious 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 2 CBR soft VCs that require the resources of 7 E1 links still appear as "up" with only 1 E1 link actually "up" between the IMA interfaces and the other 6 links that are shutdown.
![]() |
Note This behavior is seen when the links are either deleted from the IMA group or that are shutdown. |
Workaround: Use the shutdown and no shutdown commands on the IMA group and it will display the correct values of available and allocated bandwidth.
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.
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.
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.
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:
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 # interface configuration command.
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 # interface configuration command.
Symptom: On the 8-port Gigabit Ethernet module, at very high traffic rates Internal buffers (vbufs) are exhausted and ASSERTION FAILED messages appear.
Symptom: PNNI adjacency between directly connected Catalyst 8500 MSR switches fails to come up using the following configuration: both switches running IOS Release 12.1(12c)EY and a Catalyst 8510 MSR connected to a Catalyst 8540 MSR over an OC3 connection. The following conditions caused the problem to appear:
1. The Catalyst 8510 MSR was upgraded from IOS Release 12.0(7)W5(15c) to IOS Release 12.1(12c)EY
2. The PNNI adjacency did not come up after Catalyst 8510 MSR was reloaded and power cycled and the following message appeared in the console log:
3. When the physical port was changed from ATM9/1/3 to ATM 9/1/1(on the same interface module of the Catalyst 8540 MSR) the previous error message disappeared, but PNNI did not come up as shown in the following example:
4. On the Catalyst 8540 MSR, 1-way PNNI adjacency was established and the following message appeared:
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:
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.
Symptom: Same issue as DDTS CSCdx58649 except the fix was not committed to the LightStream 1010 image.
Symptom: Input errors on interface ATM0 increment one per minute. Only Input errors are incrementing and no other counters (For example, CRC and other errors).
Symptom: The K1 CPU on the 8-port Gigabit Ethernet interface module might reset itself, when the following message appears on the console:
CDP and other well-known multicast-MAC traffic received at rates greater than 700 Mbps by the 8-port Gigabit Ethernet interface module cause the K1 CPU to run out of memory. The K1 CPU might also malfunction by concatenating multiple packets causing getbuffer to fail in IOS.
Symptom: After upgrading the switch image, the LightStream 1010 switch might lose PNNI neighbors. When the "Auto-Config" function becomes stuck, it causes PNNI neighbor loss and prevents soft-PVCs from connecting.
Workaround: Use the shutdown and no shutdown commands on the interfaces or reboot the switch to recover.
Symptom: No syslog message or generic link down/up trap is generated when an IMA interface goes down.
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.
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.
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
Symptom: On a Catalyst 8500 MSR or LightStream 1010 switch with a DS3 interface, the interface goes down after only 7ms of AIS and then comes back up. For example, the following message appears:
Approximately three seconds later, the next message appears:
Symptom: Hosts connected to the Catalyst 8540 switch through an Eight Port Gigabit Ethernet module, that do not transmit data frequently are intermittently unreachable.
The connectivity to the hosts eventually recovers.
Symptom: A Catalyst 8500 MSR running Cisco IOS version 12.0(20)W5(24b) might crash with a bus error in the SNMP code.
Workaround: Disabling polling chassis MIBs might prevent the crash.
Symptom: 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:
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.
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:
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.
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.
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, that 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 no shutdown commands on the interface. |
Symptom: Avaya PBX and Definity PBX interoperability testing.
The following caveats exist for signalled ATM point-to-multipoint (P2MP) connections and the debugging of issues related to them on the Catalyst 8500 ATM switches:
- 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 signalling 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".
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 no shutdown commands.
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.
Symptom: An ARM configured with subinterface and PVCs loses IP connectivity over the active PVCs.
Workaround: To delete and reconfigure the PVC configuration restores connectivity.
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.
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 work-around, 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.
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 12.0(13)W5(19c) but exists in 12.0(18)W5(22) and 12.0(20)W5(24a).
Symptom: When the Cisco ATM switch is running UNI 4.0 with a Fore or Marconi switch, it might releasing 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 fatal error and releases the call.
Workaround: Hardcode the UNI version to 3.1
Symptom: On Frame Relay soft VCs, all frames sent with DE (discard eligibility) bit set are dropped at the serial interface even when the UPC is configured as "tag-drop" for the softVC.
Symptom: When using ATM Frame Relay IWF on a Catalyst 8540 MSR running Release 12.0(18)W5(22) or later, the output queue of the pseudo-ATM interface might go to 40/40 and remain there even if no traffic is going through the switch on the ATM-FR circuits.
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 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 no shutdown commands on the des ATM-Switch-Interfaces.
3. Restart of the ATM-NIC (only the NIC interface).
4. Bind the TCP-Stack.
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.
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.
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:
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 show ima interface and show ima interface atm card/subcard/port max detail to display the status of the interface and counters.
Symptom: If configuring RFC1483 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 shutdown the corresponding bridge-group subinterface on the ATM router module. Only shutting down the physical ATM port will not help.
Workaround: Shutdown the corresponding bridging group subinterface on ATM router module.
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.
Symptom: AIS signal taken into account with 2 seconds delay.
Symptom: On the LightStream 1010 switch, the following error message appears if your switch is using Cisco IOS Release 12.0(19)W5(23):
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.
Symptom: Excessive CLP0 discards on TSCAM for PD enabled VCs.
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.
Symptom: Multicast packets of some specific lengths (121 bytes to 240 bytes) cause a portstuck condition on the ATM router module interfaces.
Symptom: SSH fails with the CRC-check failed error message sometimes.
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), any packets larger than 1518 bytes or less than 64 bytes are filtered by the GMAC (Gigabit Ethernet Media Access Controller).
Workaround: Reload the particular interface using the epc portstuck-manual-reload interface card/subcard/port command.
Symptom: 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 nodule.
Workaround: Shutdown all controllers in the module before using the hw-module {slot number | subslot subslot/subcard} reset command.
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 Release 12.1 software, MPLS might not re-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.
Symptom: Unusual delays in Frame Relay VC counters update on Frame Relay ATM interface modules.
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.
Symptom: Globally changing TDP to LDP or changing LDP to TDP sometimes causes a loss of neighbors.
Workaround: Following is a four-step work-around:
1. Configure no tag-switching ip on both sides.
2. Configure the desired protocol at each end.
4. Configure tag-switching ip at each end.
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 rate limited to a too low rate it can force cell drops which can corrupt packets.
Workaround: Troubleshoot and remove the cause of PTSP packet corruption.
Symptom: A point-to-multi point failure might occur if a physical hardware connection does not exist but a virtual software connection is configured. Due to the connection delink failure the following error message appears on the console:
Symptom: The combined installation of TSCAM and a mixed interface module might cause the following mmc_queuecell failure message to appear:
Symptom: The ATM router module has only 147 Mbps of resources available on the ATM interfaces. The following display shows the available bit rate for an ATM router module ATM interface:
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.
Symptom: Inverse ARP does not succeed for a Frame Relay PVC terminated on ATM router module.
Symptom: The enhanced ATM router module subinterface counters do not get updated.
Symptom: When reloading the switch the following error message appears after a varying number of SVCs are setup.
Symptom: A Simple Network Management Protocol version 3 (SNMPv3) user is created by using message digest 5 (MD5) authentication with the following commands:
An SNMP walk is performed, the configuration is saved, and the switch is reloaded.
It is working and a debug snmp header shows this:
A second SNMP walk is performed:
After the second SNMP walk is performed, the command does not return any output and the debug snmp headers show this:
Symptom: PNNI and SSCOP signaling does not come back up on the Catalyst 8540 MSR OC48 interfaces after a power loss and restart.
Symptom: Ping fails when one of the two parallel soft VCs is missing.
Workaround: Use clear bridge command to reset bridge forwarding cache.
Symptom: LDP session does not go down when you shut 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 shutdown, TDP will come up but the tag packets received on the Fast Ethernet interface will be 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.
Symptom: An ATM router module interface with a PVC configured might experience a port stuck condition.
Symptom: Once the route processor switches over the following error message is seen on new Primary if we have a Gigabit processor interface module:
Enter the show diag online access command to get more details about the failure.
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]).
Symptom: A tag switching traceback might appear when an interface is shut.
Symptom: A crash occurs while configuring BVI/eigrp, or while powering off the redundant power supply.
Symptom: Catalyst 8540 CSR eight port Gigabit Ethernet interface modules fails to run CLNS.
Workaround: Update to Cisco IOS release 12.1(11b)E.
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: 1.- Load the most recent version of Cisco IOS.
2.- Have the analyzer connected to the snoop port prior to configuring ATM port snooping. Keep the analyzer connected until the snoop configuration is removed.
Symptom: When a circuit emulation service (CES) circuit that is carrying traffic is removed, no warning message is shown.
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.
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) which falls in the IGP path and LSP. The routers are disabled from initiating headend VC request over TCATM link.
Symptom: Point-to-multipoint PVCs that are configured by using SNMP are not preserved across route processor switchovers.
Workaround: Disable the dynamic synchronization feature.
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:
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.
Symptom: PNNI goes to down state on all interfaces, and all adjacency is lost.
Symptom: The switch might reload when VP tunnels are created and removed.
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.
Symptom: The Management Information Base (MIB) object "ifAdminStatus" shows "UP" for an ADMIN DOWN E1 Controller after a reload or a route processor switchover.
Workaround: Enter the no shutdown/shutdown command sequence on the controller.
Symptom: When Frame Relay/ATM Network Interworking (FRF.5) is configured on a Catalyst 8540, traffic above the peak information rate is dropped, and the INPUT ERROR counter is incremented, rather than the INPUT DROPS counter.
Symptom: With a Frame Relay-ATM Soft-VC setup 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.
Symptom: Cisco Discovery Protocol (CDP) does not work over Portchannel platforms.
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.
The Frame Relay interface module starts forwarding traffic only after you use the shutdown and no shutdown commands on the serial interface.
You might see the following error message when you reset the Frame Relay interface module:
For additional details, refer to DDTS CSCdv17817.
Symptom: After the Tag Distribution Protocol (TDP) toggles fro

