This document describes the features and caveats for Cisco IOS Release 12.0(6) for the LightStream 1010 ATM switch software. This software is based on Cisco IOS Release 12.0(5).
The LightStream 1010 ATM Switch and Catalyst 8510 MSR 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 processor and port adapters can be installed in the Catalyst 5500 switch chassis.
To determine the version of Cisco IOS software currently running on the LightStream 1010 ATM Switch and Catalyst 8510 MSR, log into the switch and use the show version EXEC command. The following is sample output from the show version command. The second line show the version number.
Cisco Internetwork Operating System Software
IOS (tm) LS1010 WA5-5 Software (LS1010-WP-M), Version 12.0 (6)
Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
The Cisco IOS software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. The following section lists the features set matrix and the features supported by each feature set.
Table 3 lists the Cisco IOS software feature sets available for the LightStream 1010 ATM Switch and Catalyst 8510 MSR in Cisco IOS Release 12.0(6) along with those features supported in the previous release.
The following features have been added to the LightStream 1010 ATM switch software:
The aesa embedded-number left-justified command was added to allow all reachable address prefixes with the E.164 AFI to be automatically converted into the left-justified encoding format.
The debug atm pnni command was revised to add the embedded-number option.
The show atm pnni aesa embedded-number command was added to display E.164 AESAs with the E.164 AFI to the left-justified encoding format.
See the section "Documentation Updates" for a list of documents that describe these features.
This section contains listings of the caveats and corrected caveats for each release. Use Table 4 to determine if a particular caveat applies to your software release, or if a particular caveat was corrected in your software release. These caveats are described in detail in the following sections:
Symptom: After hotswapping an OC-12 SM port adapter with an OC-12 MM port adapter the show controller output incorrectly shows the module as OC-12 SM. The module itself works correctly; only the show controller output is incorrect.
CSCdk78881
Symptom: The system might crash with a bus error exception when attempting an atmping on a VC if the VC has been removed via a link failure.
CSCdm48364
Symptom: In certain instances SSCOP might ask the remote site to resynchronize its values so that both sides agree on the current status of these values. This request is likely in a redundant hardware failover. The system recognized the request, but sent back a response message with a UNI 3.0 format rather than a UNI 3.1 format, so the remote side could not recognize the response.
CSCdm48406
Symptom: Running a system test that sets up and releases SVCs through a switch might cause the following error:
spurious memory access: get_latest_hw_counter
CSCdm56393
Symptom: Soft VCs showing incorrect SoftVCLs and and SVCLs might not connect to certain ports.
CSCdm58868
Symptom: After reloading the system, OC-3c and OC-12c connections come up without a problem. When a new module is inserted after the reload, the module is recognized by the system. The modules appear in the output from the show hardware and the show running config commands; however, none of the ports send out any information. The input cell count increments, but the output cell count does not.
Symptom: When a fault condition occurs on an interface on an intermediate switch, Alarm Indication Signal (AIS) cells are generated. In response, the endpoint sends Remote Identification (RDI) cells. In some cases, these RDI cells are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when the fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
CSCdi74229
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
CSCdi75584
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures.
Workaround: This should clear after the traffic congestion clears.
CSCdi82954
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Workaround: None.
CSCdi83275
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
CSCdi92142
Symptom: A LAN Emulation Configuration Server (LECS) expects all LAN Emulation Servers (LESs) to establish an individual control VC to the LECS to validate clients.
If different Emulated Local Area Networks (ELANs), 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.
Workaround: None
CSCdj01016
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Symptom: When one of the installed power supplies is powered off, and you are copying an image to bootflash, a power supply failure message might appear.
Workaround: None.
CSCdj10889
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
CSCdj11070
Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
Workaround: None.
CSCdj13565
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (by way of portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
CSCdj18430
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
CSCdj18583
Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. This situation prevents the configuration of an ABR VP tunnel subinterface.
Workaround: None.
SCdj18678
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
CSCdj25772
Symptom: Cell loss might occur while hot swapping a power supply.
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.
CSCdj54954
Symptom: In a system equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
CCSCdj68412
Symptom: If there are multiple parallel paths to the same destination on a system with an 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 insome cases and the TVCs might be VC merged and go out of the switch as a single VC.
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
CSCdj71109
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
CSCdj72651
Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPUHOG occurrence for the EXEC process.
Workaround: There is no workaround for this problem; however, the CPUHOG occurrence does not impact the functionality of the ATM switch.
CSCdj78305
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
CSCdj80396
Symptom: A CPUHOG condition might occur while setting up many calls.
Workaround: None.
CSCdj82930
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not be switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on which the interface was shut, or enter a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not work, enter a shutdown/no shutdown command on the UNI interfaces on the switch on which the physical interface was shut. This should bring all of the interfaces back up.
CSCdj84344
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
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 transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
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.
CSCdk06610
Symptom: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
Workaround: When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered-up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
CSCdk07378
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
CSCdk10398
Symptom: ILMI does not come up upon reload of vp-mux Virtual UNI (vuni).
ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and vuni) has trouble staying in "WaitDevType" after reload of the vp-mux switch.
Workaround: This situation can be cleared by shutting down the tunnel interface; disable the ILMI and issue the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shut the interface. Use the commands atm ilmi-enable and atm auto-configuration (if desired),then reenable the tunnel interface with the no shut command.
CSCdk33601
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
CSCdk42052
Symptom: After manually configuring all the prefix and ESI addresses for LECS/LES/BUS and clients for all devices on the network and upgrading from 11.2(8.0.1) FWA4(1) to 11.3(3a)WA4.6, the LANE client on the system might not join.
Workaround: After removing the manually configured address, the LANE client comes right up.
CSCdk62547
Symptom: The snmp get command does not work for the following MIB variables:
dsx1LineIndex
dsx1TimeElapsed
dsx1ValidIntervals
dsx1LineType
dsx1LineCoding
dsx1SendCode
dsx1CircuitIdentifier
dsx1LoopbackConfig
dsx1LineStatus
dsx1SignalMode
dsx1TransmitClockSource
dsx1Fdl
Workaround: None.
CSCdm48409
Symptom: Running a system test that sets up and releases SVCs through a switch might cause the following error:
spurious memory access: getSvcRxUpc and get SvcPd
Workaround: None.
CSCdm13922
Symptom: A system running Cisco IOS Release 11.3(5)WA4(5) or WA5(5) reports the following error message:
LINK-3-BADMACREG: non-existent MACADDR registry for link 49
This message might occur when the system receives an LLC2 broadcast on a LANE subinterface. In come cases, the system might crash after reporting this error message.
Workaround: Use a separate management ELAN or use a built-in Ethernet port for management of the switch.
CSCdm48409
Symptom: Running a system test that sets up and releases SVCs through a switch might cause the following error:
spurious memory access: getSvcRxUpc and get SvcPd
Workaround: None.
CSCdm48736
Symptom: If the show atm vc interface command results in a status of NO HW RESOURCE for the interface, a failure might occur in mmc_close_conn.
Workaround: None.
CSCdm48886
Symptom: Systems with customer equipment that require a PVP value of 0 might cause the PVP tunnel to fail on the LightStream 1010 side of the network.
Workaround: Change the PVP value to a non-zero number.
CSCdm59691
Symptom: When the system sends a SETUP to establish an RCC connection between the two Peer Group Leaders (PGLs), the Fore switch sends a CONNECT message back. This message is not accepted by the Cisco switch. The system generates the following error messages:
1d00h: ATMSIG: mandatory IE with invalid content in Connect msg and the connection between the two PGLs is not established.
The PNNI standard does not allow the use of the ATM traffic descriptor IE in the CONNECT message for RCC connections.
Workaround: None.
CSCdm60267
Symptom: A CES soft PVC compatibility problem might exist between Cisco and Fore systems resulting in a problem with the Call Setup format and the Call Connect format.
Workaround: None.
CSCdm61609
Symptom: On a system with an FC-PFQ , hot swapping a FR-ATM port adapter, setting the serial port on the controller, and enabling encapsulation on the Frame Relay interface via the encapsulation frame-relay ietf commandmight cause the system to hang and display the following error message:
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.
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.
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.
CSCdi82954
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Workaround: None.
CSCdi83275
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
CSCdi92142
Symptom: A LECS, using Cisco IOS Version 11.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 LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration:
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface 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 message.
Workaround: None.
CSCdj01016
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
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.
CSCdj10889
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
CSCdj11070
Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
Workaround: None.
CSCdj13565
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (by way of portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
CSCdj18430
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
CSCdj18583
Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
CSCdj18678
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
CSCdj25772
Symptom: Cell loss might occur while hot swapping a power supply.
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.
CSCdj54954
Symptom: In a LightStream 1010 ATM switch equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
CSCdj68412
Symptom: If there are multiple parallel paths to the same destination on a LightStream 1010 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.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
CSCdj71876
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
CSCdj72651
Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPUHOG occurrence for the EXEC process.
Workaround: There is no workaround for this problem. The CPUHOG occurrence does not impact the functionality of the ATM switch.
CSCdj78305
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
CSCdj80396
Symptom: CPU hog while setting up a lot of calls.
CSCdj82930
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
CSCdj84344
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
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 transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
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.
CSCdk06610
Symptom: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered-up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
CSCdk07378
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QOS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
CSCdk10398
Symptom: ILMI does not come up upon reload of vp-mux (vuni).
ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and virtual UNI) has trouble staying in "WaitDevType" after reload of the vp-mux switch.
Workaround: This situation can be cleared by shutting down the tunnel interface; disable the ILMI followed by the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shut the interface. Use the commands atm ilmi-enable and atm auto-configuration (if desired),then reenable the tunnel interface with the no shut command.
CSCdk33601
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
CSCdk62547
Symptom: The snmp get command does not work for the following MIB variables:
dsx1LineIndex
dsx1TimeElapsed
dsx1ValidIntervals
dsx1LineType
dsx1LineCoding
dsx1SendCode
dsx1CircuitIdentifier
dsx1LoopbackConfig
dsx1LineStatus
dsx1SignalMode
dsx1TransmitClockSource
dsx1Fdl
CSCdm48406
Symptom: Running a system test that sets up and releases SVCs through a switch might cause the following error:
spurious memory access: get_latest_hw_counter
CSCdm48409
Symptom: Running a system test that sets up and releases SVCs through a switch might cause the following error:
spurious memory access: getSvcRxUpc and get SvcPd
CSCdm48736
Symptom: If the show atm vc interface command results in a status of NO HW RESOURCE for the interface, a failure might occur in mmc_close_conn.
Symptom: When a LEC/LES/BUS are all on the same switch, a point-to-multipoint connection exits with the CPU as root and one leaf on the CPU (in addition to other leaves). When the LES sends a packet to all leaves, one packet needs to loop back to the CPU for the LEC. The code that performs loopback initializes hwidb->atm_db->fast_vc_info for the LANE client and eventually calls atm_input to queue the packet. However, another packet could come in on the same CPU port (for example, PNNI). This situation would cause hwidb->atm_db->fast_vc_info to be overwritten because hwidb is shared. When interrupt handling is complete for the new packet, the old packet can be misinterpreted as a totally different kind of packet.
CSCdk64465
Symptom: Crash with software release 11-3-3aWA4-6.
Data flowing over OC12 links between two LightStream 1010 ATM switches can cause potential memory corruption leading to system crashes. This crash might be caused due to badly formed AAL5 packets.
Workaround: Reboot the switch.
CSCdk69639
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
CSCdk73583
Symptom: A LightStream 1010 ATM switch with eight LAN emulation clients configured on the CPU and 300 point-to-point and 60 point-to-multipoint connections crashes unexpectedly at the find-buddy function due to an infinite loop.
CSCdk76280
Symptom: Connections, where end-to-end delay IE is included in the CONNECT message, might fail. Examples of these connections include UNI40, CBR, UBR-rt.
A LightStream 1010 ATM switch that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
CSCdk77032
Symptom: The PNNI SNMP agent is not able to discover and allow PNNI-related configurations on ATM subinterfaces. An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.
CSCdk78469
Symptom: PNNI does not clean up and release some of its data structures properly, following process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is lost until the next reload.
CSCdk82708
Symptom: When running tag switching, no tag is created for the default route.
CSCdk93395
Symptom: CES E1 PAM might fail to stop sending REMAIS yellow alarms when OOF appears for a short period.
CSCdm07874
Symptom: When using a 25-Mbps port adapter, the number of leaves in a point-to-multipoint connection cannot exceed 32.
CSCdm21728
Symptom: Clocking does not work with certain slots on ASP 6.0 systems.
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.
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.
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.
CSCdi82954
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Workaround: None.
CSCdi83275
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
CSCdi92142
Symptom: A LECS, using Cisco IOS Version 11.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 LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration:
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface 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 message.
Workaround: None.
CSCdj01016
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
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.
CSCdj10889
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
CSCdj11070
Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
Workaround: None.
CSCdj13565
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (by way of portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
CSCdj18430
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
CSCdj18583
Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
CSCdj18678
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
CSCdj25772
Symptom: Cell loss might occur while hot swapping a power supply.
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.
CSCdj54954
Symptom: In a LightStream 1010 ATM switch equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
CSCdj68412
Symptom: If there are multiple parallel paths to the same destination on a LightStream 1010 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.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
CSCdj71876
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
CSCdj72651
Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPUHOG occurrence for the EXEC process.
Workaround: There is no workaround for this problem. The CPUHOG occurrence does not impact the functionality of the ATM switch.
CSCdj78305
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
CSCdj80396
Symptom: CPU hog while setting up a lot of calls.
CSCdj82930
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
CSCdj84344
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
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 transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
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.
CSCdk06610
Symptom: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered-up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
CSCdk07378
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QOS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
CSCdk10398
Symptom: ILMI does not come up upon reload of vp-mux (vuni).
ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and virtual UNI) has trouble staying in "WaitDevType" after reload of the vp-mux switch.
Workaround: This situation can be cleared by shutting down the tunnel interface; disable the ILMI followed by the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shut the interface. Use the commands atm ilmi-enable and atm auto-configuration (if desired),then reenable the tunnel interface with the no shut command.
CSCdk33601
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
CSCdk62547
Symptom: The snmp get command does not work for the following MIB variables:
dsx1LineIndex
dsx1TimeElapsed
dsx1ValidIntervals
dsx1LineType
dsx1LineCoding
dsx1SendCode
dsx1CircuitIdentifier
dsx1LoopbackConfig
dsx1LineStatus
dsx1SignalMode
dsx1TransmitClockSource
dsx1Fdl
CSCdk64465
Symptom: Crash with software release 11-3-3aWA4-6.
Data flowing over OC12 links between two LightStream 1010 ATM switches can cause potential memory corruption leading to system crashes. This crash might be caused due to badly formed AAL5 packets.
Symptom: ATM Accounting: Exception in validblock_diagnose because resources at the destination switch were not available.
CSCdk22791
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck until a shut/no shut command sequence is issued on the interface.
CSCdk27716
Symptom: Per VC Snooping unconfigurable or broken.
CSCdk32548
Symptom: Left-justified AESA feature can cause the system to crash when enabling and disabling a node with 3000 e164/f69/X121 addresses.
CSCdk82399
Symptom: When using the atm pnni node 1 command, the peer group leader election (PGLE) might stay in the hung state for a long time.
Workaround: None.
CSCdk46071
Symptom: PNNI: crash at compare_avl_nodes.
When using the pnni_election command with a freed pnni_pdb where there are two scripts running pnni commands from different threads, the CLI command creates the pnni node and passes the pnni_pdb in the csb to be processed by the next issued command. In the meantime SNMP deletes the node from under CLI.
CSCdk47194
Symptom: PNNI: MIBS, wrong link-type in pnniLinkTable.
The PNNI agent returned a value of lowestLevelOutsideLink(4) for links between nodes on the same peer group for the pnniLinkType object. The correct value is lowestLevelHorizontalLink(2).
CSCdk54019
Symptom: Crash in process_handle_watchdog
This problem is caused by a routing loop, which is caused by metric overflow in metric aggregation.
CSCdk54678
Symptom: Power-on diagnostic test indicates snake-test failures from the ASP-PFQ.
If the snake test fails or the switch is not reset, the red LED on the left side of the processor remains lit. Changing out power supplies and processors does not correct this problem. Consequently, there is no evidence that this alarm indicates a failed processor.
CSCdk71494
Symptom: CES: per-vc queues fill with cells on 64-kbps circuits.
With standard CES 64-kbps circuits, the per-VC queues build up with cells at a rate of about one per second. There is a mismatch between the cell-rate requested and the rate granted. This is caused by signalling a pcr of 170 cells/second, rather than the desired 172 cells/second. Because the CBR FC-PFQ traffic shaping in current software has excellent granularity, roughly a cell every two seconds is queued. After the queue fills, dropping occurs at that rate.
CSCdk65901
Symptom: CES interfaces do not come up upon reload.
The line state stays at XmtAIS LossOfSignal. Sometimes the switch comes up, but the IF status of show ces int always shows as DOWN and the line state is RcvAIS XmtAIS.
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.
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.
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.
CSCdi82954
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Workaround: None.
CSCdi83275
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
CSCdi92142
Symptom: A LECS, using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS in order 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 LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration:
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface 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 message.
Workaround: None.
CSCdj01016
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
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.
CSCdj10889
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
CSCdj11070
Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
Workaround: None.
CSCdj13565
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (by way of portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
CSCdj18430
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
CSCdj18583
Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
CSCdj18678
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
CSCdj25772
Symptom: Cell loss might occur while hot swapping a power supply.
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.
CSCdj54954
Symptom: In a LightStream 1010 ATM switch equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
CSCdj68412
Symptom: If there are multiple parallel paths to the same destination on a LightStream 1010 ATM switch 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.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
CSCdj71876
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
CSCdj72651
Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPUHOG occurrence for the EXEC process.
Workaround: There is no workaround for this problem. The CPUHOG occurrence does not impact the functionality of the ATM switch.
CSCdj78305
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
CSCdj80396
Symptom: CPU hog while setting up a lot of calls.
CSCdj82930
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
CSCdj84344
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
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 transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
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.
CSCdk06610
Symptom: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered-up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
CSCdk07378
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QOS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
CSCdk10398
Symptom: ILMI does not come up upon reload of vp-mux (vuni).
ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and virtual UNI) has trouble staying in WaitDevType after reload of the vp-mux switch.
Workaround: This situation can be cleared by shutting down the tunnel interface; disable the ILMI followed by the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shut the interface. Use the commands atm ilmi-enable and atm auto-configuration (if desired),then reenable the tunnel interface with the no shut command.
CSCdk33601
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
CSCdk62547
Symptom: The snmp get command does not work for the following MIB variables:
dsx1LineIndex
dsx1TimeElapsed
dsx1ValidIntervals
dsx1LineType
dsx1LineCoding
dsx1SendCode
dsx1CircuitIdentifier
dsx1LoopbackConfig
dsx1LineStatus
dsx1SignalMode
dsx1TransmitClockSource
dsx1Fdl
CSCdk64465
Symptom: Crash with software release 11-3-3aWA4-6.
Data flowing over OC12 links between two ls1010 switches can cause potential memory corruption leading to system crashes. This crash might be caused by badly formed AAL5 packets.
This section describes caveats from Cisco IOS Release 11.3(2) TWA4(4) that have been corrected by Cisco IOS Release 11.3(3a) WA4(6) of the LightStream 1010 ATM switch software.
CSCdi72255
Symptom: E3 port adapters are limited to 65535 cells per second per PVC regardless of the framing type. There is no benefit from G832 framing.
CSCdj28496
Symptom: The fail over time for the circuit emulation switch (CES) soft VC on a redundant link might be inconsistent, from less than 1 second up to 15 seconds.
CSCdj85627
Symptom: A CES PVC cannot be cross connected to a VP tunnel interface.
CSCdj87463
Symptom: The CBR interface on the CES port adapter is always in the up/up state, even when no cable is attached, unless it is administratively shut down. If the CBR line goes down, the interface stays up/up, and the only error reported is Linestate: LossOfSignal.
CSCdj89223
Symptom: PNNI support of left-justified E.164 AESA addresses is not available in Cisco IOS Release 11.3 (0.8)TWA4(2) release.
CSCdk08318
Symptom: Some LANE clients cannot join an ELAN.
show lane indicates that some LANE clients (still in init state as far as the LANE client router is concerned) appear in the LECS table with no information.
sh atm vc int a13/0/0 indicates that some SVCs are not connected.
If the LANE clients try to join the ELAN, they are rejected.
CSCdk17127
Symptom: Using more than 13 time slots with cas on-hook, the voice CBR connections were unstable. Without on-hook-detect configuration, all CBR VCs are stable.
CSCdk17133
Symptom: A ring-back tone cannot be heard from the other side of a PBX when on-hook-detect is set.
CSCdk21557
Symptom: You cannot use SNMP to create a soft PVC on the ATM switch.
CSCdk29039
Symptom: The ATM switch might crash if you remove a snooped subinterface by entering the no interface command and then entering the show atm snoop-vc command on the snoop interface.
CSCdj59621
Symptom: The system does not support CUGs on soft PVC connections. For example, if you define a set of access policies and a CUG on an interface with the PVC leg of a soft PVC call, the CUG parameters do not apply to those calls.
Workaround: None.
CSCdk54678
Symptom: Power-on diagnostic test indicates snake-test failures from the ASP-PFQ.
If the snake-test fails or the switch is not reset, the red led on the left side of the processor remains lit. Changing out power supplies and processors does not correct this problem. Consequently, there is no evidence that this alarm indicates a failed processor.
This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Cisco IOS Release 11.3(3a)WA4(6).
The following caveats have been identified for this release of the LightStream 1010 ATM switch software:
The maximum number of ELAN LES/BUS pairs that the processor ATM interface supports is 10.
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.
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.
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.
CSCdi82954
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX light emitting diode (LED) lights up.
Workaround: None.
CSCdi83275
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
CSCdi92142
Symptom: A LECS, using Cisco IOS Version 11.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 LES(s) multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration:
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface 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 message.
Workaround: None.
CSCdj01016
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
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.
CSCdj10889
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
CSCdj11070
Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
Workaround: None.
CSCdj13565
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (by way of portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
CSCdj18430
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
CSCdj18583
Symptom: Supporting ABR VP tunnels require interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
CSCdj18678
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
CSCdj25772
Symptom: Cell loss might occur while hot swapping a power supply.
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.
CSCdj54954
Symptom: In a LightStream 1010 ATM switch equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
CSCdj68412:
Symptom: If there are multiple parallel paths to the same destination on a LightStream 1010 AMT switch 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.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
CSCdj71876
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
CSCdj72651
Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPUHOG occurrence for the EXEC process.
Workaround: There is no workaround for this problem. The CPUHOG occurrence does not impact the functionality of the ATM switch.
CSCdj78305
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
CSCdj80396
Symptom: CPU hog while setting up a lot of calls.
CSCdj82930
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces on the switch on which the physical interface was shut to bring everything back up.
CSCdj84344
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
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 transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
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.
CSCdk06610
Symptom: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
CSCdk07378
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QOS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
CSCdk10398
Symptom: ILMI does not come up upon reload of vp-mux (vuni).
ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and virtual UNI) has trouble staying in WaitDevType after reload of the vp-mux switch.
Workaround: This situation can be cleared by shutting down the tunnel interface; disabling the ILMI followed by the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be re-enabled. Shut the interface. Use the commands atm ilmi-enable and atm auto-configuration (if desired),then re-enable the tunnel interface with the no shut command.
CSCdk22484
Symptom: ATM Accounting : Exception in validblock_diagnose because resources at destination switch were not available.
CSCdk22791
Symptom: When a large amount of data is sent out of the ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck.
Workaround: Issue a shut/no shut command sequence on the interface.
CSCdk27716
Symptom: Per VC Snooping unconquerable or broken.
Workaround: None.
CSCdk32548
Symptom: Crash at pnni_route-bg
Left-justified AESA feature can cause the system to crash when enabling and disabling a node with 3k of e164/f69/X121 addresses.
Workaround: None.
CSCdk33601
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Workaround: None.
CSCdk46071
Symptom: PNNI: crash at compare_avl_nodes.
When using the pnni_election command with a freed pnni_pdb where there are two scripts running pnni commands from different threads, the CLI command creates the pnni node and passes the pnni_pdb in the csb to be processed by the next issued command. In the mean time SNMP deletes the node from under CLI.
Workaround: When CLI resumes the next command uses a copy of the node pdb that has been freed by SNMP. The fix to such a scenario is to get the pnni_pdb from the PNNI_node_tbl entry if it exists, otherwise it means that the node has been removed and the switch aborts the execution of the command. Modify all of the CLI node commands to use the new scheme.
CSCdk47194
Symptom: PNNI: MIBS, wrong link-type in pnniLinkTable.
The PNNI agent returned a value of lowestLevelOutsideLink(4) for links between nodes on the same peer group for the pnniLinkType object. The correct value is lowestLevelHorizontalLink(2).
Workaround: None.
CSCdk54019
Symptom: Crash in process_handle_watchdog
This problem is caused by a routing loop, which is caused by metric overflow in metric aggregation.
Workaround: None.
CSCdk62547
Symptom: The snmp get command does not work for the following MIB variables:
dsx1LineIndex
dsx1TimeElapsed
dsx1ValidIntervals
dsx1LineType
dsx1LineCoding
dsx1SendCode
dsx1CircuitIdentifier
dsx1LoopbackConfig
dsx1LineStatus
dsx1SignalMode
dsx1TransmitClockSource
dsx1Fdl
Workaround: None.
CSCdk64465
Symptom: Crash with software release 11-3-3aWA4-6.
Data flowing over OC12 links between two LightStream 1010 ATM switches can cause potential memory corruption leading to system crashes. This crash might be caused by badly formed AAL5 packets.
Workaround: Reboot the switch.
CSCdk65901
Symptom: CES interfaces do not come up upon reload.
The line state stays at XmtAIS LossOfSignal. Sometimes the switch comes up, but the IF status of show ces int always shows as DOWN and the line state is RcvAIS XmtAIS.
Workaround: None
CSCdk71494
Symptom: CES: per-vc queues fill with cells on 64Kbps circuits.
With standard CES 64Kbps circuits, the per-VC queues build up with cells at a rate of about one per second. There is a mismatch between the cell-rate requested and the rate granted. This is caused by signaling a pcr of 170 cells/second, rather than the desired 172 cells/second. Because the CBR FC-PFQ traffic shaping in current software has excellent granularity, roughly a cell every two seconds is queued. After the queue fills, dropping occurs at that rate.
An Update to theLightStream 1010 ATM Switch and Catalyst 8510 MSR Command Reference document was created to reflect information added after printing the manual.
The following sections describe the documentation available for the LightStream 1010 ATM Switch and Catalyst 8510 MSR. These documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules, which are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.
The most up-to-date documentation can be found on the Web by way of Cisco Connection Online (CCO) and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.
These release notes should be used in conjunction with the documents listed in this section.
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.
For service and support for a product purchased directly from Cisco, use CCO.
For helpful tips on configuring Cisco products, follow this path on CCO:
Software & Support: Technical Tips(button on left margin)
"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 650-596-4408.
The following sections are provided from the Technical Tips page:
Field Notices—Designed to provide notification of critical issues regarding Cisco products. These include problem descriptions, safety or security issues, and hardware defects.
Hardware—Technical Tips related to specific hardware platforms.
Internetworking Features—Tips on using and deploying Cisco IOS software features and services.
Sample Configurations—Actual configuration examples complete with topology and annotations.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information,productdocumentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
