Determining Your Software Release

To determine the version of Cisco IOS software currently running on the LightStream 1010 ATM switch, log in to the switch and enter the show version EXEC command. The second line in the following sample output from the show version command indicates the version number:

Feature Set Tables

The Cisco IOS software is packaged in feature sets, or software images, that vary according to the platform. Table 3 lists the Cisco IOS software feature sets available for the LightStream 1010 ATM switch in Cisco IOS Release 12.0(25), along with those features supported in previous releases.

New and Changed Information

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

Note See Table 3 for a complete list of features supported by this and previous releases.

New Features in Cisco IOS Releases 12.0(2a) Through 12.0(25)

There are no new features in these releases.

New Cisco IOS Release 11.3(3a)WA4(6) Features

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 in the left-justified encoding format.

Caveats

This section lists the caveats and corrected caveats for each release. Use Table 4 and Table 5 to determine the status of a particular caveat and its relevancy to your software release. In the table, "C" indicates a corrected caveat, and "O" indicates an open caveat. These caveats are described in detail in the next section, "Caveat Symptoms and Workarounds."

Symptom: On a Cisco LightStream 1010 or a Catalyst 8500 series ATM switch, when you use the show atminterface EXEC command on an ATM sub-interface, the total number of cells that are transmitted or received is shown as zero. The traffic rate on the sub-interface is shown incorrectly.

Workaround: Upgrade to the latest Cisco IOS release version.

CSCds21312

Symptom: In some cases, you may get spurious memory access at fastAAL5PathForBusPerformance function.

Workaround: None.

CSCdr96649

Symptom: The PNNI system capability for the Type, Length, and Value (TLV) processing code can enter an infinite loop if the TLV length of any of the contained TLVs is corrupted on reception.

Workaround: None.

CSCdr68425

Symptom: In VBR-nrt, virtual circuits (VC) traversing through a virtual path (VP) tunnel can be used to calculate the limits of peak cell rate (PCR) or sustainable cell rate (SCR) by using the connection admission control (CAC) algorithm at the following URL:

Symptom: On a Cisco LightStream LS1010 switch that is equipped with circuit emulation service (CES) port adapters, the shutting down of the constant bit rate (CBR) interface does not affect the devices that are connected to it.

Workaround: None.

CSCdr36952

Symptom: A defect in multiple versions of Cisco IOS software will cause a router or switch to stop and reload if the Cisco IOS HTTP service is enabled and an attempt is made to browse to http://<router-ip>/%%. This defect can be exploited to produce a denial of service (DoS) attack.

Workaround: Nullify the vulnerability by disabling the Cisco IOS HTTP server, by preventing access to the port in use by the HTTP server on the affected router or switch. Or apply an access-class option to the service itself. The Cisco IOS HTTP server is not enabled by default except on a small number of router models in specific circumstances.

Symptom: A Cisco router might experience problems during attempts to format, delete, or squeeze slot0 immediately after the show version command is entered or immediately after the router reloads. This is a flash timing-related issue. Commands subsequently entered will not be affected.

Workaround: None.

CSCdp97152

Symptom: The system will ignore the incoming SSCOP pdu status messages from another system and automatically reset the session after the timers expire.

Workaround: None.

CSCdp96164

Symptom: The LightStream 1010 sometimes runs out of shared memory when running LES/BUS services at a high data rate.

Workaround: Move LES/BUS to a platform that is more suitable for this service. Recommended platform is Catalyst 5000 LANE.

CSCdp83777

Symptom: When resetting a connection to an endstation, the system might crash if using
the static map command.

Symptom: New SVC or soft PVC calls from a LightStream 1010 ATM switch to a Fore ATM switch across a PNNI interface fail to connect. Connections initiated from the Fore switch do not fail.

Workaround: None.

CSCdp56613

Symptom: When fast switching an IP frame that is less than 46 bytes in length to an ATM interface, the router sets the length in the ATM adaption layer 5 (AAL5) header to 54 bytes, even though the length should be equal to the IP frame length plus the length of the AAL5 header, which is 8 bytes.

Workaround: None.

CSCdp56060

Symptom: In the Cisco IOS Release 12.0 and up, the SNMP might fail to show trace using the
VC trace application. This is caused by an incorrect cross identifier return for VCs 0/5 and 0/16.

Workaround: None.

CSCdp49173

Symptom: When hundreds of TVCs in bidirectional mode are repeatedly configured and unconfigured in a switch, VC resources might be exhausted.

Workaround: None.

CSCdp07407

Symptom: Only 99 percent of the CPU might be available when an ATM-25 is connected to ports 1 through 3 on the 4-port ATM-25 module or ports 1 through 5 and 7 through 11 on the 12-port ATM-25 module.

Workaround: None.

CSCdp05975

Symptom: The vc-merge command, activated by default, does not work with Cisco IOS Release 11.3 code. Large amounts of CRCs appear when the vc-merge command is entered.

Workaround: None.

CSCdp04722

Symptom: When a call is made over a VP tunnel, the Connection ID information element incorrectly sets the VP bits of all links to 00 (associated signaling). This setting might cause link failures outside the VP tunnel.

Workaround: None.

CSCdm91060

Symptom: ILMI keepalives might incorrectly reset the interface on the second retry of a link failure.

Workaround: None.

CSCdm89519

Symptom: In some cases, constant bit rate VCs get stuck because of excessive errors.

Workaround: None.

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 system recognizes the module. The modules appear in the output from the show hardware command and the show running config command; however, none of the ports send out any information. The input cell count increments, but the output cell count does not.

Symptom: Systems with customer equipment that requires 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.

CSCdm48736

Symptom: If entering 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.

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 recognizes the request, but sends back a response message with a UNI 3.0 format rather than a UNI 3.1 format, so the remote side cannot recognize the response.

Workaround: None.

CSCdm46270

Symptom: Packet duplication along the path between a TFTP server and a router trying to perform a TFTP write to the server can cause the write to fail.

Workaround: Write to a different TFTP server or resolve the packet duplication problem in the network between the router and the TFTP server.

CSCdm38218

Symptom: When entering the show debug command on a system that is a PNNI childless uncle, an infinite loop within the pnni_debug_show command might trigger a watchdog timeout.

Workaround: None.

CSCdm36790

Symptom: When forwarding a call setup from one VP tunnel to another, dropped information elements which are mandatory when using associated signaling might cause compatibility problems with third-party equipment.

Workaround: None.

CSCdm34806

Symptom: Tag switching on the ATM trunk works, but if the same link becomes a part of the inverse multiplexing for ATM (IMA) group, tag switching might not work as expected.

Workaround: None.

CSCdm34634

Symptom: The PVC Discovery feature on a router that is connected to an ATM interface might fail to discover all the configured PVCs and soft PVCs coming from the interface. This condition occurs only when soft PVCs are present on the configuration.

Symptom: When data is being converted from bits per second to cells per second, numbers might be rounded down when they should be rounded up.

Workaround: None.

CSCdm13922

Symptom: A system running Cisco IOS Release 11.3(5)WA4(5) or WA5(5) might report the following error message:

LINK-3-BADMACREG: non-existent MACADDR registry for link 49

This message occurs when the system receives an LLC2 broadcast on a LANE subinterface. In some cases, the system crashes after reporting this error message.

Workaround: Use a separate management ELAN or use a built-in Ethernet port to manage the switch.

CSCdm08234

Symptom: The circuit emulation service might display an interface as up when it is experiencing Loss of Signal (LOS). In addition, alarm indication signals (AIS) might not be generated during the shutdown.

Workaround: None.

CSCdm07874

Symptom: When using a 25-Mbps port adapter, the number of leaves in a point-to-multipoint connection cannot exceed 32.

Workaround: None.

CSCdm06168

Symptom: PVCs that are terminating on a CPU port over point-to-point subinterfaces might not be accepted.

Symptom: The system issues an acctngFileFull message every 10 seconds if the snmp-server enable trap atm statement is configured.

Workaround: Remove this statement from the configuration or enter the no atmacct-deb command.

CSCdk84269

Symptom: The TR-LEC might incorrectly process all registration requests received on its control distribute VC. When working correctly, it processes registration requests only when the LAN emulation client ID (LECID) in the registration message matches up with its own LECID.

Workaround: None.

CSCdk82708

Symptom: When running tag switching, no tag is created for the default route.

Workaround: None.

CSCdk82399

Symptom: When using the atm pnni nodenode command, the peer group leader election (PGLE) might stay in the hung state for a long time.

Workaround: None.

CSCdk79426

Symptom: When soft VPs are being created, the VPI value allocated on the switched part of the soft VP path might conflict with an existing configured PVP.

Workaround: To get the soft VP back up, either remove the PVP or create a PVP using the same VPI value that is on the peer switch.

CSCdk78881

Symptom: The system might crash with a bus error exception when entering the atmping command on a VC if the VC has been removed through a link failure.

Workaround: None.

CSCdk78469

Symptom: A PNNI process is terminated when the associated node is either disabled or removed. Following process termination, PNNI might not clean up and release some of its data structures properly. As a result of not freeing the data structures, the associated memory is lost until the next reload.

Workaround: Reload the system.

CSCdk77032

Symptom: The SNMP agent might not be able to discover and allow PNNI-related configurations on ATM subinterfaces. An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.

Workaround: None.

CSCdk76280

Symptom: Connections in which end-to-end delay IE is included in the CONNECT message might fail. Examples of these connections include UNI 40, CBR, and UBR-rt.

A LightStream 1010 ATM switch that is an intermediate switch passes a bad CONNECT message from one side to the other. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.

Workaround: None.

CSCdk73583

Symptom: Due to an infinite loop, 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 might crash unexpectedly at the find-buddy function.

Workaround: None.

CSCdk73478

Symptom: After hot swapping an OC-12 SM port adapter with an OC-12 MM port adapter, the output of the show controller command might incorrectly show the module as OC-12 SM. The module itself works.

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 signaling a PCR of 170 cells per second, rather than the desired 172 cells per 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.

Workaround: None.

CSCdk69639

Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) might not remove the TVCs. Reenabling tag switching on that interface puts it in the "not TDP ready" state.

Workaround: None.

CSCdk65901

Symptom: CES interfaces might not come up upon reload.

The line state stays at XmtAIS LossOfSignal. Sometimes the switch comes up, but the IF status of the show ces int command always shows as DOWN and the line state is RcvAIS XmtAIS.

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, no evidence exists that this alarm indicates a failed processor.

Workaround: None.

CSCdk54019

Symptom: Crash in process_handle_watchdog might occur.

This problem is caused by a routing loop, which is caused by metric overflow in metric aggregation.

Workaround: None.

CSCdk47194

Symptom: The PNNI agent returns 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.

CSCdk46071

Symptom: PNNI: There might be a 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 entered command. In the meantime, SNMP deletes the node from under CLI.

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.

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.

CSCdk32548

Symptom: Left-justified AESA feature can cause the system to crash when enabling and disabling a node with 3000 e164/f69/X121 addresses.

Workaround: None.

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.

Workaround: None.

CSCdk27905

Symptom: When LEC/LES/BUS are all on the same switch, a point-to-multipoint connection exists with the CPU as root and with several leaves on the CPU. 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 might be misinterpreted as a totally different kind of packet.

Workaround: None.

CSCdk27725

Symptom: When snoop-vc is configured on a port, a switch might give the following internal error message:

%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr.

Workaround: Ignore the message. It does not affect the snooping functionality.

CSCdk27716

Symptom: Per VC snooping is unconfigurable or broken.

Workaround: None.

CSCdk22791

Symptom: When a large amount of data is sent out of the Ethernet interface, the interface might become inundated 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 the shut/no shut command sequence is entered on the interface.

Workaround: Enter the shut/no shut command sequence on the interface.

CSCdk22484

Symptom: One soft VC might not come up because the resources at the destination switch are not available. After retrying the soft VC several times, the system might crash because of memory corruption.

Workaround: None.

CSCdk21557

Symptom: You cannot use SNMP to create a soft PVC on the ATM switch.

Workaround: None.

CSCdk17133

Symptom: A ring-back tone cannot be heard from the other side of a PBX when on-hook-detect is set.

Workaround: None.

CSCdk17127

Symptom: When using more than 13 time slots with cas on-hook, the voice CBR connections might be unstable. Without on-hook-detect configuration, all CBR VCs become stable.

Workaround: None.

CSCdk10398

Symptom: ILMI might 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 reloading the vp-mux switch.

Workaround: Shut down the tunnel interface; disable the ILMI, enter the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shutdown the interface. Enter the atm ilmi-enable command and atm auto-configuration command (if desired), then reenable the tunnel interface with the no shut command.

CSCdk08318

Symptom: Some LANE clients cannot join an ELAN.

The show lane command 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.

The show atm vc interface command indicates that some SVCs are not connected.

The current multipoint-to-point funnel implementation might 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 would 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.

CSCdk06610

Symptom: A LightStream 1010 switch installed in a 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).

Workaround: None.

CSCdj89223

Symptom: PNNI support of left-justified E.164 AESA addresses is not available in Cisco IOS Release 11.3(0.8)TWA4(2).

Workaround: None.

CSCdj87463

Symptom: Unless it is administratively shut down, the CBR interface on the CES port adapter is always in the up/up state, even when no cable is attached. If the CBR line goes down, the interface stays up/up, and the only error reported is Linestate: LossOfSignal.

Workaround: None.

CSCdj85853

Symptom: When the ROM monitor environment variable boot is set to a nonexistent file (using the Cisco IOS boot system flash command) and the configuration register is set to 0x2102 (autoboot), the switch might hang 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.

CSCdj85627

Symptom: A CES PVC cannot be cross connected to a VP tunnel interface.

Workaround: None.

CSCdj84981

Symptom: When hot swapping cards immediately after turning off the interrupts, the system might crash. The crash occurs because the interrupts are disabled and the hot swapping is not seen until the command is complete.

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 transmitted traffic to the scheduled rate. This might cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.

Workaround: Refer to the DDTs for information on how to convert a requested rate to the actual rate.

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.

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 the clear ip route command on the switch on the interface that was shutdown, or the clear ip route command on all the switches to bring everything back up. If entering the clear ip route command does not work, enter the shut/no shut command on the UNI interfaces of the switch on which the physical interface was shut to bring everything back up.

CSCdj80396

Symptom: The CPU HOG condition might occur while setting up a lot of calls.

Workaround: None.

CSCdj78305

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

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

CSCdj72651

Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPU HOG occurrence for the EXEC process. The CPU HOG occurrence does not impact the functionality of the ATM switch.

Workaround: None.

CSCdj71876

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.

CSCdj70619

Symptom: The following error might occur after copying the running configuration to a TFTP server and then trying to unconfigure all of the interface addresses:

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 merged and go out of the switch as a single VC.

Workaround: None.

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.

CSCdj54954

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

Workaround: None.

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.

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 to up to 15 seconds.

Workaround: None.

CSCdj25772

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

Workaround: None.

CSCdj18678

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

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

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.

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.

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 cause 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.

CSCdj01757

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

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: A LAN Emulation Configuration Server (LECS), using Cisco IOS Release 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 LESs multiplex the control messages (which validate the clients) into a single VC.

For example, see the following LES router configuration:

atm1/0.1 sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN

atm1/0.2 sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN

atm1/0.3 sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN

atm1/0.4 sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN

This configuration of 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:

The clients are still allowed to join the ELAN. Disregard the warning message.

Workaround: None.

CSCdi83275

Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system might 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.

CSCdi82954

Symptom: The receiver circuitry on DS3 port adapters might 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.

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 might then schedule other tasks. This process does not affect normal operation of the switch.

Workaround: None.

CSCdi72255

Symptom: E3 port adapters are limited to 65,535 cells per second per PVC regardless of the framing type. There is no benefit from G832 framing.

Workaround: None.

CSCdi55937

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 defect 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.

Related Documentation

The following sections describe documentation available for the LightStream 1010 ATM switch. Both printed manuals and electronic documents are available.

Use these release notes with the documents listed in this section.

Software Documents

Following is a list of the software documentation available for the LightStream 1010 ATM switch:

Documentation CD-ROM

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

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

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

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

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. ClickFeedbackin the toolbar and selectDocumentation. After you complete the form, clickSubmitto send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: