Cisco IOS Release 12.0(5)
Release Notes for LightStream 1010 ATM Switch Software

This document describes the features and caveats for Cisco IOS Release 12.0(5) for the LightStream 1010 ATM switch software. This software is based on Cisco IOS Release 12.0(4).

This document includes the following sections:

Introduction

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.

Version and Part Number Matrix

Table 1 lists the release names, versions, and part numbers used with the LightStream 1010 ATM switch.

Release Name	Release Version	Part Number
WAS1-1	11.1.(4)	SF-WAS1-11.1.4
WAS1-2	11.1.(401)	SF-WAS1-11.1.401
WAS1-3	11.1.(6)	SF-WAS1-11.1.6
WAS1-4	11.1.(8)	SF-WAS1-11.1.8
WAS1-5	11.1.(9)	SF-WAS1-11.1.9
WAS1-6	11.1.(11)	SF-WAS1-11.1.11
WAS2-1	11.1.(401)	SF-WAS2-11.1.401
WAS2-2	11.1.(6)	SF-WAS2-11.1.6
WAS2-3	11.1.(8)	SF-WAS2-11.1.8
WAS2-4	11.1.(9)	SF-WAS2-11.1.9
WAS2-5	11.1.(11)	SF-WAS2-11.1.11
WAS3-1	11.2(2)WA3(1a)	SF-WAS3-11.2.2
WAS3-2	11.2(5)WA3(2b)	SF-WAS3-11.2.5
WAS3-3	11.2(8)WA3(3)	SF-WAS3-11.2.8
WAS3-4	11.2(10)WA3(4)	SF-WAS3-11.2.10
WAS3-5	11.2(12)WA3(5)	SF-WAS3-5
WAS3-6	11.2(15)WA3(6)	SF-WAS3-6
WAS3-7	11.2(15)WA3(7)	SF-WAS3-7
WAS4-1	11.2.0(8.0.1)FWA4(1)	SF-WAS4-11.2.8.1S
WAS4-2	11.3(0.8)TWA4(2)	SF-WAS4-2
WAS4-4	11.3(2a)WA4(4)	SF-WAS4-4
WAS4-6	11.3(3a)WA4(6)	SF-WAS4-6
WAS4-7	12.0(2a)	SF-WAS4-7
WAS4-8	11.3(5)WA4(8d)	SF-WAS4-8
12.0(4)	12.0(4a)	SL10R2-12.0.4
12.0(5)	12.0(5)	SL10R2-12.0.5

Table 1:

Release Name Release Version Part Number

WAS1-1

11.1.(4)

SF-WAS1-11.1.4

WAS1-2

11.1.(401)

SF-WAS1-11.1.401

WAS1-3

11.1.(6)

SF-WAS1-11.1.6

WAS1-4

11.1.(8)

SF-WAS1-11.1.8

WAS1-5

11.1.(9)

SF-WAS1-11.1.9

WAS1-6

11.1.(11)

SF-WAS1-11.1.11

WAS2-1

11.1.(401)

SF-WAS2-11.1.401

WAS2-2

11.1.(6)

SF-WAS2-11.1.6

WAS2-3

11.1.(8)

SF-WAS2-11.1.8

WAS2-4

11.1.(9)

SF-WAS2-11.1.9

WAS2-5

11.1.(11)

SF-WAS2-11.1.11

WAS3-1

11.2(2)WA3(1a)

SF-WAS3-11.2.2

WAS3-2

11.2(5)WA3(2b)

SF-WAS3-11.2.5

WAS3-3

11.2(8)WA3(3)

SF-WAS3-11.2.8

WAS3-4

11.2(10)WA3(4)

SF-WAS3-11.2.10

WAS3-5

11.2(12)WA3(5)

SF-WAS3-5

WAS3-6

11.2(15)WA3(6)

SF-WAS3-6

WAS3-7

11.2(15)WA3(7)

SF-WAS3-7

WAS4-1

11.2.0(8.0.1)FWA4(1)

SF-WAS4-11.2.8.1S

WAS4-2

11.3(0.8)TWA4(2)

SF-WAS4-2

WAS4-4

11.3(2a)WA4(4)

SF-WAS4-4

WAS4-6

11.3(3a)WA4(6)

SF-WAS4-6

WAS4-7

12.0(2a)

SF-WAS4-7

WAS4-8

11.3(5)WA4(8d)

SF-WAS4-8

12.0(4)

12.0(4a)

SL10R2-12.0.4

12.0(5)

12.0(5)

SL10R2-12.0.5

Release Name to Version and Part Number Matrix

System Requirements

This section describes the systems requirements for Release 12.0(5) and includes the following sections:

Memory Requirements

DRAM memory configuration is 64-MB DRAM (MEM-ASP64M). As of WA4, this is the standard default memory for the LightStream 1010 product.

Hardware Supported

Table 2 lists the interfaces supported on the LightStream 1010 ATM Switch and Catalyst 8510 MSR Release 12.0(5) and their minimum software release.

Table 2: Supported Interfaces & Their Minimum Software Requirements

Part Number	Description	Minimum Software Requirement
WAI-OC3-4MM	4-port STS-3c/STM-1 multimode fiber port adapters	WAS1-1
WAI-OC3-4SS	4-port STS-3c/STM-1 single-mode fiber port adapters	WAS1-1
WAI-OC3-4U5	4-port STS-3c/STM-1 UTP-5 port adapters	WAS1-1
WAI-OC3-4SSLR	4-port STS-3c/STM-1 SMF long reach port adapters	WAS3-2
WAI-OC3-1S3M	OC-3 mix port adapter module, 1 IR+ port and 3 MM ports	WAS3-1
WAI-OC12-1MM	1-port STS-12c/STM-4c multimode fiber port adapters	WAS1-2
WAI-OC12-1SS	1-port STS-12c/STM-4c SMF port adapters	WAS1-1
WAI-OC12-1SSLR	1-port STS-12c/STM-4c SMF long reach port adapters	WAS3-2
WAI-ATM25-12P	12-port ATM 25 port adapters with 96-pin telco cable	WAS3-2
WAI-T3-2BNC	2-port DS-3 port adapters	WAS1-1
WAI-E3-2BNC	2-port E3 port adapters	WAS1-1
WAI-T3-4BNC	4-port DS-3 port adapters	WAS3-1
WAI-E3-4BNC	4-port E3 port adapters	WAS3-3
WAI-T1-4RJ48	4-port T1 (ATM) with RJ-48 interface port adapters	WAS3-1
WAI-E1-4RJ48	4-port E1 (ATM) with RJ-48 interface port adapters	WAS3-1
WAI-E1-4BNC	4-port E1 (ATM) with BNC interface port adapters	WAS3-1
WAI-T1C-4RJ48	4-port T1 (circuit emulation) with RJ-48 interface port adapters	WAS3-1
WAI-E1C-4RJ48	4-port E1 (circuit emulation) with RJ-48 interface port adapters	WAS3-1
WAI-E1C-4BNC	4-port E1 (circuit emulation) with BNC interface port adapters	WAS3-1
L1010-ASP-B-FC1	ASP¹ with FC-per-class Queuing (FC-PCQ²)	WAS1-3
L1010-ASP-B-FCPFQ	ASP¹ with FC-per-flow Queuing (FC-PFQ³)	WAS4-1
L1010-PWR-DC	Power Supply DC	WAS3-1

¹ ASP = ATM switch processor.
² FC-PCQ = feature card per-class queueing.
³ FC-PFQ = feature card per-flow queueing.

Determining Your Software Release

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 (5)

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

Feature Set Tables

The Cisco IOS software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. The following section lists the features 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(5) along with those features supported in the previous release.

Table 3: Feature Sets Supported by the LightStream 1010 ATM Switch and Catalyst 8510 MSR

Feature Set	12.0(5)	12.0(4)	12.0(2a)	11.3(3a)WA4(6)
Left-justified E.164 AFI support	x	x	x	x
SNMP¹	x	x	x	x
Asynchronous support	x	x	x	x
PPP² (SLIP³/PPP)	x	x	x	x
IP⁴	x	x	x	x
NTP⁵	x	x	x	x
TACACS+⁶	x	x	x	x
Telnet	x	x	x	x
Point-to-point and point-to-multipoint permanent VCCs⁷ and VPCs⁸	x	x	x	x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.0)	x	x	x	x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)	x	x	x	x
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)	x	x	x	x
Multipoint-to-point UNI signaling	x	x	x	x
Soft VCCs and VPCs	x	x	x	x
VP tunneling	x	x	x	x
VPI/VCI range support in ILMI 4.0	x	x	x	x
PNNI hierarchy	x	x	x	x
ILMI version 4.0	x	x	x	x
IISP⁹	x	x	x	x
LANE¹⁰ client (LEC¹¹) and LANE Services (LES¹²/BUS¹³/LECS¹⁴) on ASP¹⁵	x	x	x	x
Token Ring LANE services	x	x	x	x
ATM ARP¹⁶ server on ASP	x	x	x	x
ATM ARP client on ASP	x	x	x	x
ATM tag switch router (TSR)	x	x	x	x
Port snooping	x	x	x	x
OAM¹⁷ F4 and F5	x	x	x	x
E.164 address translation	x	x	x	x
E.164 autoconversion	x	x	x	x
Circuit emulation	x	x	x	x
ATM access lists	x	x	x	x
ATM accounting	x	x	x	x
ATM RMON¹⁸	x	x	x	x
Multiple, weighted, dynamic thresholds for selective packet marking and discard	x	x	x	x
Shaped VP tunnels for CBR traffic (FC-PFQ only)	x	x	x	x
Substitution of other service categories in shaped VP tunnels (FC-PFQ feature cards only)	x	x	x	x
Dual leaky bucket policing (FC-PFQ feature cards only)	x	x	x	x
Scheduler/Service Class/PVC configuration for FC-PFQ feature cards	x	x	x	x
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC) (FC-PFQ feature cards only)	x	x	x	x
Network clocking enhancements for smooth switchover (FC-PFQ feature cards only)	x	x	x	x
Per-VC or per-VP nondisruptive snooping (FC-PFQ feature cards only)	x	x	x	x
Support for non-zero MCR¹⁹ on ABR connections (FC-PFQ feature cards only)	x	x	x	x
Access lists on ILMI registration	x	x	x	x
CUGs	x	x	x	x
ATM soft restart	x	x	x	x
ATM accounting enhancements	x	x	x	x
CISCO-SYSLOG-MIB support	x	x	x	x
CISCO-CONFIG-COPY-MIB support	x	x	x	x
Signaling diagnostics and MIB	x	x	x	x
Supplemental AToM MIB	x	x	x	x

¹SNMP = Simple Network Management Protocol.
²PPP = Point-to-Point Protocol.
³SLIP = Serial Line Internet Protocol.
⁴IP = Internet Protocol.
⁵NTP = Network Time Protocol.
⁶TACACS+ = Terminal Access Controller Access Control System.
⁷VCCs = virtual channel connections.
⁸VPCs = virtual path connections.
⁹IISP = Interim-Interswitch Signaling Protocol
¹⁰LANE = LAN Emulation.
¹¹LEC = LAN Emulation Client.
¹²LES = LAN Emulation Server.
¹³BUS = broadcast and unknown server.
¹⁴LECS = LAN Emulation Configuration Server.
¹⁵ASP = ATM switch processor.
¹⁶ARP = Address Resolution Protocol.
¹⁷OAM = Operation, Administration, and Maintenance.
¹⁸RMON = Remote Monitoring
¹⁹MCR = minimum cell rate

New and Changed Information

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

New Features in Release 12.0(5)

There are no new features in this release.

New Features in Release 12.0(4)

There are no new features in this release.

New Features in Release 12.0(2a)

There are no new features in this release.

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

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

Caveats

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:

Table 4: Cisco IOS Release Caveats and Caveats Corrected Reference

DDTS Number	12.0(5)		12.0(4)		12.0(2a)		11.3(3a)WA4(6)
DDTS Number	Caveat Corrected	Caveat	Caveat Corrected	Caveat	Caveat Corrected	Caveat	Caveat Corrected	Caveat
CSCdi55937		x		x		x		x
CSCdi72255							x
CSCdi74229		x		x		x		x
CSCdi75584		x		x		x		x
CSCdi82954		x		x		x		x
CSCdi83275		x		x		x		x
CSCdi92142		x		x		x		x
CSCdj01016		x		x		x		x
CSCdj01757		x		x		x		x
CSCdj10889		x		x		x		x
CSCdj11070		x		x		x		x
CSCdj13565		x		x		x		x
CSCdj18430		x		x		x		x
CSCdj18583		x		x		x		x
CSCdj18678		x		x		x		x
CSCdj25772		x		x		x		x
CSCdj28496							x
CSCdj42967		x		x		x		x
CSCdj54954		x		x		x		x
CSCdj59621							x
CSCdj68412		x		x		x		x
CSCdj70619		x		x		x		x
CSCdj71109		x		x		x		x
CSCdj71876		x		x		x		x
CSCdj72651		x		x		x		x
CSCdj78305		x		x		x		x
CSCdj80396		x		x		x		x
CSCdj82930		x		x		x		x
CSCdj84344		x		x		x		x
CSCdj84379		x		x		x		x
CSCdj85627							x
CSCdj85853		x		x		x		x
CSCdj87463							x
CSCdj89223							x
CSCdk06610		x		x		x		x
CSCdk07378		x		x		x		x
CSCdk08318							x
CSCdk10398		x		x		x		x
CSCdk17127							x
CSCdk17133							x
CSCdk21557							x
CSCdk22484					x			x
CSCdk22791					x			x
CSCdk27716					x			x
CSCdk27905			x
CSCdk29039							x
CSCdk32548					x			x
CSCdk33601		x		x		x		x
CSCdk46071					x			x
CSCdk47194					x			x
CSCdk54019					x			x
CSCdk54678		x		x		x		x
CSCdk62547		x		x		x		x
CSCdk64465			x	x		x		x
CSCdk65901					x			x
CSCdj69739			x
CSCdk71494					x		x
CSCdk73583			x
CSCdk76280			x
CSCdk77032			x
CSCdk78469			x
CSCdk82399			x
CSCdk82708			x
CSCdk90222			x
CSCdk93395			x
CSCdm07874			x
CSCdm21728			x	x
CSCdm48406		x
CSCdm48409		x
CSCdm48736		x
CSCdm49146	x

Cisco IOS Release 12.0(5) Caveats Corrected

CSCdm49146

: Symptom: LightStream 1010 systems with the FC1 card installed might experience intermittent crashes during boot.

Cisco IOS Release 12.0(5) Caveats

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

atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN

: This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:

%LANE-4-LECS_WARNING: interface 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:

VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).
ABR, UBR: no bandwidth is allocated.

Workaround: None.

CSCdj01757

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

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.
: Workaround: None.

CSCdj70619

: Symptom: TCP: %SYS-3-MGDTIMER:Uninitialized timer : mgd_timer_complain_uninit.
: Workaround: None.

CSCdj71109

: 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 may 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

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.

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.

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.

Cisco IOS Release 12.0(4) Caveats Corrected

CSCdk27905

: 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 may 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.

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.

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.

Cisco IOS Release 12.0(4) Caveats

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

atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN

: This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:

%LANE-4-LECS_WARNING: interface 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

VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).
ABR, UBR: no bandwidth is allocated.

Workaround: None.

CSCdj01757

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

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.
: Workaround: None.

CSCdj70619

: Symptom: TCP: %SYS-3-MGDTIMER:Uninitialized timer : mgd_timer_complain_uninit.
: Workaround: None.

CSCdj71109

: 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 may 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 may be caused due to 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.

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.

Cisco IOS Release 12.0(2a) Caveats Corrected

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

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.

Cisco IOS Release 12.0(2a) Caveats

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

atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN

: This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:

%LANE-4-LECS_WARNING: interface 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

VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).
ABR, UBR: no bandwidth is allocated.

Workaround: None.

CSCdj01757

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

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.
: Workaround: None.

CSCdj70619

: Symptom: TCP: %SYS-3-MGDTIMER:Uninitialized timer : mgd_timer_complain_uninit.
: Workaround: None.

CSCdj71109

: 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 may 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 may 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.

Cisco IOS Release 11.3(3a)WA4(6) Caveats Corrected

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.

Cisco IOS Release 11.3(3a)WA4(6) Caveats

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:

atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN

: This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:

%LANE-4-LECS_WARNING: interface 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

VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).
ABR, UBR: no bandwidth is allocated.

Workaround: None.

CSCdj01757

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

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.

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.

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.
: Workaround: None.

CSCdj70619

: Symptom: TCP: %SYS-3-MGDTIMER:Uninitialized timer : mgd_timer_complain_uninit.
: Workaround: None.

CSCdj71109

: 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 may 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.

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.
: 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 may 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.

Documentation Updates

An Update to the LightStream 1010 ATM Switch and Catalyst 8510 MSR Command Reference document was created to reflect information added after printing the manual.

Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.

Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.

For service and support for a product purchased directly from Cisco, use CCO.

Software Configuration Tips on the Cisco TAC Home Page

For helpful tips on configuring Cisco products, follow this path on CCO:

Software & Support: Technical Tips (button on left margin)

"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 650-596-4408.

The following sections are provided from the Technical Tips 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.
Software Products—MultiNet & Cisco Suite 100, Network Management, Cisco IOS Software Bulletins, CiscoPro Configurations.
Special Collections—Other Helpful Documents: Frequently Asked Questions, Security Advisories, References & RFCs, Case Studies, CiscoPro Documentation CD-ROM.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

WWW: http://www.cisco.com
WWW: http://www-europe.cisco.com
WWW: http://www-china.cisco.com
Telnet: cco.cisco.com
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.

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.

Table of Contents

Cisco IOS Release 12.0(5) Release Notes for LightStream 1010 ATM Switch Software

Cisco IOS Release 12.0(5) Release Notes for LightStream 1010 ATM Switch Software

Cisco IOS Release 12.0(5)
Release Notes for LightStream 1010 ATM Switch Software

Cisco IOS Release 12.0(5)
Release Notes for LightStream 1010 ATM Switch Software