Table of Contents

Introduction
Software and Associated Hardware
Cisco IOS Packaging
Memory Requirements
Caveats and Caveats Corrected for Release 11.2(15)WA3(6), 11.2(12)WA3(5), and 11.2(10)WA3(4)

Release 11.2(15)WA3(6) Caveats Corrected
Release 11.2(15)WA3(6) Caveats
Release 11.2(12)WA3(5) Caveats Corrected
Release 11.2(12)WA3(5) Caveats
Release 11.2(10)WA3(4) Caveats Corrected
Release 11.2(10)WA3(4) Caveats

Caveats and Caveats Corrected For Release 11.2(8)WA3(3) and 11.2(5)WA3(2b)

Release 11.2(8)WA3(3) Caveats Corrected
Release 11.2(8)WA3(3) Caveats
Release 11.2(5)WA3(2b) Caveats Corrected
Release 11.2(5)WA3(2b) Caveats

Modifications and Caveats For Release 11.2(2)WA3(1a)

Release 11.2(2)WA3(1a) Caveats

Documentation
Cisco Connection Online

Cisco IOS Release 11.2(15)WA3(6)
Release Notes for LightStream 1010 ATM Switch Software

August 20, 1998

LightStream 1010 ATM Release 11.2(15)WA3(6)

This release note describes the features and caveats for Cisco  IOS Release  11.2(15)WA3(6) for the LightStream 1010 ATM switch software. The LightStream 1010 ATM switch software is based on Cisco IOS Release 11.2(15).

Introduction

This release note discusses the following topics:

• Software and Associated Hardware

• Cisco IOS Packaging

• Memory Requirements

• Caveats and Caveats Corrected for Release 11.2(15)WA3(6), 11.2(12)WA3(5), and 11.2(10)WA3(4)

• Caveats and Caveats Corrected For Release 11.2(8)WA3(3) and 11.2(5)WA3(2b)

• Modifications and Caveats For Release 11.2(2)WA3(1a)

• Documentation

• Cisco Connection Online

Software and Associated Hardware

This section describes the software and associated hardware support for the LightStream 1010 Multiservice ATM switch.

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

Table 2 lists minimum software requirements for the LightStream 1010 ATM switch components.

Table 2: 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 DS3 port adapters	WAS1-1
WAI-E3-2BNC	2-port E3 port adapters	WAS1-1
WAI-T3-4BNC	4-port DS3 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	ASP1 with FC-per-class Queuing (FC-PCQ2)	WAS1-3
L1010-ASP-B-FCPFQ	ASP1 with FC-per-flow Queuing (FC-PFQ3)	WAS4-1
L1010-PWR-DC	Power Supply DC	WAS3-1
LS1010-ASP-C-FC1	Hot swappable ASP with FC-PCQ2	WAS3-6, WAS4-6
LS101-ASP-C-FCPFQ	Hot swappable multiservice switch route processor	WAS4-6

1ASP = ATM switch processor. 2FC-PCQ = feature card per-class queueing. 3FC-PFQ = feature card per-flow queueing.

Table 3 lists of the minimum software required for each ATM feature. Only ATM features are listed. Features, such as Simple Network Management Protocol (SNMP) are assumed as given.

Table 3: Minimum Software Requirements for Each ATM Feature

Software Feature	Minimum Release Required
Point-to-point and point to multipoint permanent VCCs and VPCs	WAS1-1
Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.0)	WAS1-1
VP tunneling	WAS1-1
ILMI	WAS1-1
IISP	WAS1-1
LANE client (LEC) on ASP	WAS1-1
ATM ARP client on ASP	WAS1-1
Port snooping	WAS1-1
ATM access lists	WAS1-1
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)	WAS1-2, WAS2-1
Soft VCCs and VPCs	WAS1-2, WAS2-1
ATM ARP server on ASP	WAS1-2, WAS2-1
PNNI version 1.0 single level	WAS2-1
Circuit Emulation	WAS3-1
E.164 address translation	WAS3-1
OAM F4 and F5	WAS3-1
ILMI version 4.0	WAS3-1
Point-to-point and point-to-multipoint switched VCC s and VPCs (UNI 4.0)	WAS3-1
LEC and LANE services (LECS/BUS/LES) on ASP	WAS3-1
ATM RMON	WAS3-2
ATM accounting	WAS3-2
Supplemental AToM MIB	WAS4-1
Signaling diagnostics and MIB	WAS4-1
ATM accounting enhancements	WAS4-1
PVC accounting	WAS4-1
ATM soft restart	WAS4-1
Closed user groups	WAS4-1
Access lists on ILMI registration	WAS4-1
Support for non-zero MCR on ABR connections (requires FC-PFQ)	WAS4-1
Network clock enhancements for smooth switchover (requires FC-PFQ)	WAS4-1
Logical multicast support (requires FC-PFQ)	WAS4-1
Dual Leaky Bucket policing (requires FC-PFQ)	WAS4-1
Shaped VP tunnels for CBR traffic (requires FC-PFQ)	WAS4-1
Multiple weighted dynamic thresholds for selective packet discard and marking	WAS4-1
Per VC snooping	WAS4-1
PNNI version 1.0 multilevel hierarchy	WAS4-2
Token Ring LANE services	WAS4-1
CISCO-COPY-CONFIG-MIB support	WAS4-2
CISCO-SYSLOG-MIB support	WAS4-2
Scheduler/service class/PVC configuration for FC-PFQ feature card	WAS4-2
Substitution for other service categories in shaped VP tunnel (requires FC-PFQ)	WAS4-2
E.164 autoconversion	WAS4-2
ATM tag switch router (TSR)	WAS4-2
VPI/VCI range support in ILMI 4.0	WAS4-2
Multipoint-to-point UNI signaling	WAS4-2
Left-justified E.164 AFI support	WAS4-6

Table 4 lists the feature licenses and when they would be used. All functionality is included in the base code. The feature license is only required if that feature is to be implemented.

Table 4: Feature Licenses

Part Number	Description	Minimum Software Release
FR-WA-SX-PNNI	Required only if a client is upgrading from a WAS1 release that supported IISP only to a release that includes PNNI support.	Not Applicable
FR-WA-SX-HPNNI	License for hierarchical PNNI support	WAS4-2
FR-WA-SX-TAGSW	License for tag switching	WAS4-2
FR-WA-SX-TSHPNNI	License for tag and hierarchical PNNI	WAS4-2

Cisco IOS Packaging

The LightStream 1010 supports the routing of ATM signaling requests across a network of switches using the ATM routing protocols. Two standard routing protocols have been developed by the ATM Forum---Interim InterSwitch Signaling Protocol (IISP) and the Private Network-to-Network Interface (PNNI) Protocol, version 1.0. Both protocols are supported by the LightStream 1010 ATM switch.

Table 5 lists the feature set for the Cisco  IOS Release 11.2(15)WA3(6), 11.2(12)WA3(5), 11.2(10)WA3(4), 11.2(8)WA3(3), and 11.2(5)WA3(2b) of the LightStream 1010 ATM switch software.

Table 6 lists the feature set for the Cisco  IOS Release 11.2(2)WA3(1a) of the LightStream 1010 ATM switch software.

Memory Requirements

The system Dynamic Random Access Memory (DRAM) resides on a SIMM module on the ATM Switch Processor (ASP). The default DRAM configuration is 16  MB. The amount of DRAM required on the ASP module is determined by the number of active physical and logical ports (virtual path tunnels) and the expected number of active switched virtual channels (SVCs) through the switch.

Table 7 provides an approximate guide to use when determining the amount of DRAM required for a switch with 32 physical ports.

Caveats and Caveats Corrected for Release 11.2(15)WA3(6), 11.2(12)WA3(5), and 11.2(10)WA3(4)

This section contains listings of the caveats and corrected caveats for each release. Use Table 7 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:

• Release 11.2(15)WA3(6) Caveats Corrected

• Release 11.2(15)WA3(6) Caveats

• Release 11.2(12)WA3(5) Caveats Corrected

• Release 11.2(12)WA3(5) Caveats

• Release 11.2(10)WA3(4) Caveats Corrected

• Release 11.2(10)WA3(4) Caveats

Table 8 Cisco IOS Release Caveats and Caveats Corrected Reference

DDTS Number	11.2(15)WA3(6)		11.2(12)WA3(5)		11.2(10)WA3(4)
	Caveat Corrected	Caveat	Caveat Corrected	Caveat	Caveat Corrected	Caveat
CSCdi55937		X		X		X
CSCdi72255	X			X		X
CSCdi74229		X		X		X
CSCdi75584		X		X		X
CSCdi81974		X
CSCdi82954		X		X		X
CSCdi83275		X		X		X
CSCdi83567		X		X		X
CSCdi85540		X				X
CSCdi92142		X		X		X
CSCdi93291						X
CSCdj01016		X		X		X
CSCdj01757		X		X		X
CSCdj02004					X
CSCdj03229				X		X
CSCdj03281		X
CSCdj03621					X
CSCdj04898					X
CSCdj10889		X				X
CSCdj11070		X
CSCdj13326		X
CSCdj13565		X		X		X
CSCdj15388					X
CSCdj18430		X		X		X
CSCdj18678		X		X		X
CSCdj22451					X
CSCdj24272		X		X		X
CSCdj25769	X			X		X
CSCdj25772		X		X		X
CSCdj28496	X			X		X
CSCdj32484		X		X		X
CSCdj33346		X
CSCdj41665					X
CSCdj41709					X
CSCdj42669		X
CSCdj42967		X		X		X
CSCdj48158					X
CSCdj48371					X
CSCdj49255					X
CSCdj50142					X
CSCdj50627		X				X
CSCdj50993					X
CSCdj53797			X
CSCdj57479			X
CSCdj59640		X		X
CSCdj61842		X				X
CSCdj63058					X
CSCdj70898			X			X
CSCdj72017					X
CSCdj73705			X			X
CSCdj74469			X			X
CSCdj78305				X
CSCdj82090			X			X
CSCdj84492			X
CSCdj85540			X			X
CSCdj85627	X			X
CSCdj85853		X		X
CSCdj87463	X			X
CSCdj88091				X
CSCdj90806	X			X
CSCdj91059			X			X
CSCdj92142				X
CSCdj95371	X			X
CSCdk01031		X
CSCdk02119	X			X
CSCdk05437	X			X
CSCdk05447	X			X
CSCdk08318	X			X
CSCdk17127	X			X
CSCdk17133	X			X
CSCdk01629	X			X

Release 11.2(15)WA3(6) Caveats Corrected

This section describes caveats that have been corrected by Release 11.2(15)WA3(6) for the LightStream 1010 ATM switch.

• The traffic that can go through an E3 board for one PVC is limited to 65535 cells per second independent of the framing type used. There is no benefit configuring G832 framing.
  [CSCdi72255]

• Using an OC12 PAM on LightStream 1010 as a network clock source results in bad clock quality.
  [CSCdj25769]

• The fail over time for the LightStream 1010 CES soft VC on a redundant link could be inconsistent, with a range from less than a second to 15 seconds.
  [CSCdj28496]

• A CES PVC cannot be cross-connected to a tunnel interface.
  [CSCdj85627]

• When no cable is physically attached to the CES interface, PAM remains in the up/up state unless administratively shut down.
  [CSCdj87463]

• When the soft VC connected over a VP tunnel route is broken, it takes approximately 45 seconds to reestablish the soft VC over an alternative path, because the destination end of the soft VC is not released soon enough. Shortening the time it takes ILMI to detect the keepalive failure can speed the process to release the destination end of the soft VC and reestablish an alternative route.
  [CSCdj90806]

• When the interface being used by a soft-vc vpi is shut down, the following happens:

Using fast-retry, each VC is released. Using slow-retry, after the soft-vc retry timer (180s) expired, the SETUP message is no longer rejected.
[CSCdj95371]

• Symptom: PNNI port numbers for internal prefixes are updated incorrectly in the routing table when the received prefixes advertise non-zero port numbers. This problem occurs only with internal prefixes and not with exterior routes. This is only important when the routes have to be flushed and are not removed from the routing table; you can see these routes using the show atm route command. However, these entries do get removed from the PNNI database, and the routes are marked as "DN" in the routing table; you can see the stale entries using the show atm route command. This problem does not occur in an all-Cisco environment.
  [CSCdk02119\

• After executing the command show atm vc signalling detail, a LightStream 1010 with software version 11.2(12)WA3.5 restarts with a software forced crash at PC 0x60099C34.
  [CSCdk05437]

• Enabling 'service log backtrace' generates garbage in the log file of a LightStream 1010 running ls1010-wp-mz.112-12.WA3.5.bin.
  [CSCdk05447]

• 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.
[CSCdk08318]

• 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.
  [CSCdk17127]

• A ring-back tone cannot be heard from the other side of a PBX when on-hook-detect is set.
  [CSCdk17133]

• UNI 3.0 has mode field in AAL5 which is stripped in UNI 3.1. When the setup originates from the UNI 3.1 side, the setup does not carry mode. Some vendor switches running LANE 3.0 reject the connection because of the absence of mode information.
  [CSCdk01629]

Release 11.2(15)WA3(6) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(12)WA3(5).

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 ASP ATM interface supports is 10.

• The remote defect identification (RDI) cells sent by an end point in response to the Alarm Indicator Signal (AIS) are not propagated beyond that intermediate switch. Once the fault on one interface is detected, the switch removes the connection leg entries for both interfaces, even though the other interface might be up. As a result, the RDI cells are dropped at the switch.
  [CSCdi55937]

• When a large number (more than 1000) of SVCs are present on a specific interface and a shutdown command is executed, "%SYS-3-CPUHOG:" message might appear. All the SVCs on that interface are released as expected. This message indicates that the process has run for a long time before it returns the control to the kernel which then can schedule other tasks.
  [CSCdi74229]

• Under very heavy traffic conditions the switch can experience temporary queue cell failures. This should clear up once the traffic congestion clears up.
  [CSCdi75584]

• Under certain conditions on the Ethernet interface 2/0/0, a message like the one below might appear. This in no way affects the functioning of the switch or the Ethernet interface.

  %SYS-2-GETBUF: Bad getbuffer, bytes= 65532
  -Process= "", ipl= 2, pid= 37
  -Traceback= 600593A4 601B135C 601AF558 6019F900
  [CSCdi81974]
  

• Due to sensitive receiver circuitry, noise can be interpreted as a valid signal. This condition causes the DS3 controller to interpret the condition as a bad signal, turning the RX LEDs red on that port.
  [CSCdi82954]

• Under heavy signaling activities, 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 would appear on the console:

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

The system continues to function, in most instances, but might stop accepting any more calls from the end systems.

Workaround

If the switch does not bring up more calls, toggling an interface might help to reinitialize all the connections and bring the system back to working condition.
[CSCdi83275]

• When an AddParty message is sent across an E.164 interface, and the message does not include the CallingPartyAddress information element, the AddParty request is rejected on the first attempt. The second attempt will be successful.

Workaround

The normal mode of operation is to include the CallingPartyAddress information element in the AddParty message.
[CSCdi83567]

• Logical multicasting is not supported in this LightStream 1010 release.
  [CSCdi85540]

• A LAN Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LAN Emulation Servers (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 Version 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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'

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

• You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:

  • VBR: SCR + sustained-cell-rate-margin0-factor x (PCR - SCR)

  • ABR, UBR: no bandwidth is allocated (guaranteed)

[CSCdj01016]

• Using the copy flash bootflash command causes a power-supply failure message when there are two power supplies installed and one of them is turned off. Normally both power supplies are turned on for redundancy.
  [CSCdj01757]

• If a T1/E1 port is configured as the clock source for the system, and that port receives transitions in link status that affect the clock, other interfaces that derive their clock from that clock source may go down for a moment. This situation only occurs when transitions are less than 1 second.
  [CSCdj03281]

• Inconsistent ATM RMON call attempt counters on incoming and outgoing ports.

The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces due to switch crankback attempts. This might cause a discrepancy between the call attempt counters shown on the following:

• Portselgroup representing the interface on which the call came in

• PortSelgroup representing the interface over which an attempt was made to forward the call

This might be more evident when a call fails to be established.
[CSCdj10889]

• When disabling Cisco Discovery Protocol (CDP) on ATM interface 2/0/0.x configured as an LEC, the new configuration is not saved to nonvolatile random-access memory (NVRAM) and does not appear when using the show running-config command. CDP is disabled on the interface until you reload the software. After you reload the software, CDP is again reenabled on the interface. This is caused by the new configuration not being saved to NVRAM prior to reloading the software.
  [CSCdj11070]

• ATM Accounting background notification is not supported and requires the following workarounds:

  • To change connection-type for the selection entry, first use the shutdown command on all interfaces where ATM accounting is enabled. The interfaces can be brought back up after the connection type for the selection entry is changed using the no shutdown command.

  • To enable or disable ATM accounting globally, first use the shutdown command on all the interfaces where ATM accounting is enabled. The interfaces can be brought up after the enable and disable operation is complete using the no shutdown command.

  • To enable or disable ATM accounting on an interface, first use the shutdown command on that interface. The interface can be brought up after the enable/disable operation is complete using the no  shutdown command.

Support for ATM accounting background notifications is provided in the next maintenance release.
[CSCdj13326]

• ATM-RMON data collection cannot be configured on subinterfaces or tunnels. The atm  rmon  collect command is accepted for hardware interfaces only, and ignored for subinterfaces. SNMP and NVGEN support (via the portSelTable) is not possible until 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 that interface.
  [CSCdj13565]

• The cell counts on a snooped interface are double the actual number of cells transmitted.
  [CSCdj18430]

• For the 25-Mbps PAM, SNMP support is not fully available. The "ciscoAtmIfPhysEntryData" table and LED information will be supported in a future release.
  [CSCdj18678]

• The NO SHUT command causes the system to reset when a PAM is not present.
  [CSCdj24272]

• A LightStream 1010 could experience cell loss during hot swapping one of its power supplies.
  [CSCdj25772]

• A tftp download to the LightStream 1010 could fail due to an ARP table corruption problem. This problem only affects the tftp download.

Workaround

Use the ip host-routing command in the general configuration mode.
[CSCdj32484]

• When using a script to configure an ESI address on a router, only the router table lists the address; the switch does not show any address in its table. This only occurs when running a script through autotest.
  [CSCdj33346]

• Attempting to create 96 tunnels between two nodes on 3 parallel links) produces the following spurious memory access message:

  %ATMCORE-3-INTERNAL_ERROR: connLinkP2pPeerLegs: Null OamIfInfo Ptr
  [CSCdj42669]
  

• If the LightStream 1010 memory is almost or completely exhausted, soft PVCs that go down might not come up and will remain in RELEASING or INACTIVE state.
  [CSCdj42967]

• With the multiple LES/BUS pairs configured on a LightStream 1010 and about 20 LECs configured to join the ELANs, repeated shut/noshut of the interface for an extended period could produce the "ATMS2000_add_party_to_output_only_errors".
  [CSCdj50627]

• When running a test between two CES ports, AIS problems are seen when a CES DSX1 loopback payload is activated.
  [CSCdj59640]

• Numerous interface resets on the LightStream 1010 might generate the following error message.

%ATMSIG-3-FAILASSERT: Assertion failed: file "../atm/atmsig_ie.c", line 5950

Workaround

Correct the physical layer, which is usually the cause of the problem.
[CSCdj61842]

• If the ROM monitor environment variable boot is set to a non-existent file (using the Cisco IOS command boot system flash) and if the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.

Workaround

If you power-cycle the switch, a break character is sent to the switch to force it to the rom monitor prompt. The switch can then be manually re-booted.
[CSCdj85853]

• Using the atm ping command without specifying VCI value uses last VCI value automatically.

When using the atm ping command with OAM cells, if you only specify a VPI (but no VCI), the software takes one of these VCI values:

• Last VCI used if an ATM ping was executed

• Lowest VCI value if no prior ATM pings were executed
  [CSCdk01031]

Release 11.2(12)WA3(5) Caveats Corrected

This section describes caveats that have been corrected by Release 11.2(12)WA3(5) for the LightStream 1010 ATM switch.

• When you configure LES/BUS LANE service on the cpu port of the LightStream 1010, the following caveat exists.Under heavy signalling traffic, usually when the switch resets and tries to come back with a large number of clients for each LES/BUS, a warning message
  "CPUHOG - atmsig_output" appears on the console. This has no real impact on the system functionality or performance.
  [CSCdj57479]

• Consider a scenario in which two LightStream 1010 ATM switches are connected over ATM, with classical IP running over ATM. One of the LightStream 1010s is also connected to an Ethernet backbone. With ip host-routing turned on, disconnecting the ATM connection (physically removing the connection) causes the LightStream 1010 to flood the Ethernet backbone with ARP packets, affecting the Ethernet backbone's performance. The problem occurs only if ip host-routing is turned on (it is off by default) and the ATM connection is physically removed.

Workaround

Do not turn on ip host-routing.
[CSCdj53797]

• Improve pak element allocation mechanisms to reduce memory fragmentation.
  [CSCdj70898]

• ATC code point conversion based on UNI version.
  [CSCdj73705]

• CES: After hotswapping the CES card, some lines from "show ces int" are unavailable.
  [CSCdj74469]

• SSCOP: Reserved field in an ENDAK PDU is sometimes set to non-zero value.
  [CSCdj82090]

• Start VCI assignments from 35 for SVCs.
  [CSCdj84492]

• Switch crashes while writing core if the core file length is greater than 32 characters.
  [CSCdj85540]

• ATMSIG: An extra byte is added in the calling party subaddress IE.
  [CSCdj91059]

Release 11.2(12)WA3(5) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(12)WA3(5).

The following caveats have been identified for this release of the LightStream 1010 ATM switch software.

• When using a script to configure an ESI address on a router, only the router table lists the address; the switch does not show any address in its table. This only occurs when running a script through autotest.
  [CSCdj33346]

• Attempting to create 96 tunnels between two nodes on 3 parallel links produces the following spurious memory access message:

  %ATMCORE-3-INTERNAL_ERROR: connLinkP2pPeerLegs: Null OamIfInfo Ptr
  [CSCdj42669]
  

• When running a test between two CES ports, AIS problems are seen when a CES DSX1 loopback payload is activated.
  [CSCdj59640]

• A CES PVC cannot be cross-connected to a tunnel interface.

Workaround

Use CES soft-VCs instead; a soft CES VC connects to a tunnel interface.
[CSCdj85627]

• If the ROM monitor environment variable boot is set to a non-existent file (using the Cisco IOS command boot system flash) and if the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.

Workaround

If you power-cycle the switch, a break character is sent to the switch to force it to the rom monitor prompt. The switch can then be manually re-booted.
[CSCdj85853]

• When no cable is physically attached to the CES interface, PAM will remain in the up/up state unless administratively shut down.
  [CSCdj87463]

• When the soft VC over a VP tunnel route is broken, it takes approximately 45 seconds to reestablish the soft VC over an alternative path because the destination end of the soft VC is not released soon enough. Shortening the time it takes ILMI to detect the keepalive failure can speed the process to release the destination end of the soft VC and re-establish an alternative route.

Workaround: Modify the ATM ILMI keepalive timer to less than 5 seconds.
[CSCdj90806]

• When the interface being used by a soft-vc vpi is shut down, the following happens:

Using fast-retry, each VC is released. Using slow-retry, after the soft-vc retry timer (180s) expired, the SETUP message is no longer rejected.
[CSCdj95371]

• Using the atm ping command without specifying VCI value uses the last VCI value automatically. When using the atm ping command with OAM cells, and only specifying a VPI (but no VCI), the software takes one of these VCI values:

  • Last VCI used if an ATM ping was executed

  • Lowest VCI value if no prior ATM pings were executed
    [CSCdk01031]

• Symptom: PNNI port numbers for internal prefixes are updated incorrectly in the routing table when the received prefixes advertise non-zero port numbers. This problem occurs only with internal prefixes and not with exterior routes. This is only important when the routes have to be flushed and are not removed from the routing table; you can see these routes using the show atm route command. However, these entries do get removed from the PNNI database, and the routes are marked as "DN" in the routing table; you can see the stale entries using the show atm route command. This problem does not occur in an all-Cisco environment.
  [CSCdk02119]

• After executing the command show atm vc signalling detail, an LS1010 with software version 11.2(12)WA3.5 restarts with a Software forced crash at PC 0x60099C34.
  [CSCdk05437]

• Enabling 'service log backtrace' generates garbage in the log file of an LS1010 running ls1010-wp-mz.112-12.WA3.5.bin.
  [CSCdk05447]

• 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
[CSCdk08318]

• 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.
  [CSCdk17127]

• A ring back tone can not be heard from the other side of a PBX when on-hook-detect is set.
  [CSCdk17133]

• When a SETUP for an ABR SVC is received on an NNI interface, signaling does not allocate a traffic parameter negotiation structure for the SVC to automatically negotiate PCR down to line-rate.
  [CSCdj88091]

• 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 Version  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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for 
elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for 
elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for 
elan 
'sysa_70k_31_a1.3_LAN'

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

• When running a test between two CES ports, AIS problems are seen when a CES DSX1 loopback payload is activated.
  [CSCdj59640]

• When IP host routing is enabled and saved to NVRAM, the only way to remove this command from the configuration is to delete and rebuild the NVRAM in 11.2(12)WA3(5).
  [CSCdj78305]

• A CES PVC cannot be cross-connected to a tunnel interface.

Workaround

Use CES soft-VCs instead; a soft CES VC connects to a tunnel interface.
[CSCdj85627]

• If the ROM monitor environment variable boot is set to a non-existent file (using the Cisco IOS command boot system flash) and if the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.

Workaround

If you power-cycle the switch, a break character is sent to the switch to force it to the rom monitor prompt. The switch can then be manually re-booted.
[CSCdj85853]

• The ASP ATM interface supports a maximum number of 10 ELAN LES/BUS pairs.

• You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:

  • VBR: SCR + sustained-cell-rate-margin0-factor x (PCR - SCR)

  • ABR, UBR: no bandwidth is allocated (guaranteed)

[CSCdj01016]

• Using the copy flash bootflash command causes a power-supply failure message when there are two power supplies installed and one of them is turned off. Normally both power supplies are turned on for redundancy.
  [CSCdj01757]

• A DS-3 PAM interface connected to a Cisco BPX might go down and come back up after a no shutdown command. Operation is normal after it comes back up for the second time.
  [CSCdj03229]

• ATM-RMON data collection cannot be configured on subinterfaces or tunnels. The atm  rmon  collect command is accepted for hardware interfaces only, and ignored for subinterfaces. SNMP and NVGEN support (via the portSelTable) is not possible until 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 that interface.
  [CSCdj13565]

• The cell counts on a snooped interface are double the actual number of cells transmitted.
  [CSCdj18430]

• For the 25-Mbps PAM, SNMP support is not fully available. The "ciscoAtmIfPhysEntryData" table and LED information will be supported in a future release.
  [CSCdj18678]

• The NO SHUT command causes the system to reset when a PAM is not present.
  [CSCdj24272]

• Using an OC12 PAM on a LightStream 1010 as a network clock source results in bad clock quality.
  [CSCdj25769]

• A LightStream 1010 could experience cell loss during hot swapping one of its power supplies.
  [CSCdj25772]

• The fail over time for the LightStream 1010 CES soft VC on a redundant link could be inconsistent, with a range from less than a second to 15 seconds.
  [CSCdj28496]

• A tftp download to the LightStream 1010 could fail due to an ARP table corruption problem. This problem only affects the tftp download.

Workaround

Use the ip host-routing command in the general configuration mode.
[CSCdj32484]

• If the LightStream 1010 memory is almost or completely exhausted, soft PVCs that go down might not come up and will remain in RELEASING or INACTIVE state.
  [CSCdj42967]

• The remote defect identification (RDI) cells sent by an end point in response to the Alarm Indicator Signal (AIS) are not propagated beyond that intermediate switch. Once the fault on one interface is detected, the switch removes the connection leg entries for both interfaces, even though the other interface might be up. As a result, the RDI cells are dropped at the switch.
  [CSCdi55937]

• The traffic that can go through an E3 board for one PVC is limited to 65535 cells per second independent of the framing type used. There is no benefit configuring G832 framing.
  [CSCdi72255]

• When a large number (more than 1000) of SVCs are present on a specific interface and a shutdown command is executed the, "%SYS-3-CPUHOG:" message might appear. All the SVCs on that interface are released as expected. This message indicates that the process has run for a long time before it returns the control to the kernel to i.e. schedule other tasks.
  [CSCdi74229]

• Under very heavy traffic conditions the switch can experience temporary queue cell failures. This should clear up once the traffic congestion clears up.
  [CSCdi75584]

• Due to sensitive receiver circuitry, noise can be interpreted as a valid signal. This condition causes the DS-3 controller to interpret the condition as a bad signal, turning the RX LEDs red on that port.
  [CSCdi82954]

• Under heavy signaling activities 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 would appear on the console:

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

The system continues to function, in most instances, but might stop accepting any more calls from the end systems.

Workaround

If the switch does not bring up more calls, toggling an interface might help to reinitialize all the connections and bring the system back to working condition.
[CSCdi83275]

• When an AddParty message is sent across an E.164 interface, and the message does not include the CallingPartyAddress information element, the AddParty request is rejected on the first attempt. The second attempt will be successful.

Workaround

The normal mode of operation is to include the CallingPartyAddress information element in the AddParty message.
[CSCdi83567]

• A LAN Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LAN Emulation Servers (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 Version 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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'

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

• UNI 3.0 has mode field in AAL5 which is stripped in UNI 3.1. When the setup originates from the UNI 3.1 side, the setup does not carry mode. Some vendor switches running LANE 3.0 reject the connection because of the absence of mode information.
  [CSCdk01629]

Release 11.2(10)WA3(4) Caveats Corrected

This section describes caveats that have been corrected by Release 11.2(10)WA3(4) for the LightStream 1010 ATM switch.

• The Ethernet port on the LightStream 1010 is sometimes found in a frozen state. "show interface ethernet2/0/0" shows the interface as up but the output queue full. Issuing a "clear interface ethernet2/0/0" command clears this state.
  [CSCdj02004]

• The Receive cell counter on the virtual circuit VPI=0, VCI=32 shows erroneous cell counts.
  [CSCdj03621]

• The SNMP agent on the LightStream 1010 switch always returns "Slot empty" value even if a flash card is present in the PCMCIA slot.
  [CSCdj04898]

• The Ethernet interface might fail to respond when the input queue is wedged, 40/40 in the LightStream 1010.

Workaround

Issue the "clear int e2/0/0 command" to bring the interface back up.
[CSCdj15388]

• LightStream 1010 may log %SYS-3-MGDTIMER:Uninitialized timer, timer stop, timer = [hex]. This message may not cause traffic or network problems.
  [CSCdj22451]

• T1/E1 PAMs when hot swapped by oc3 PAM could lock up the switch. This effect is seen only if oc3 is hot swapped into a slot where T1/E1 was residing.

Workaround

Make sure oc3 is not hot swapped in the slot that was used by T1/E1. If an oc3 card needs to be hot swapped in place of T1/E1, remove the T1/E1 card, reload, and then insert oc3 PAM.
[CSCdj41665]

• The TTB length bit is not set for G832 framing. The TTB messages, which check for the continued presence of the intended transmitter, must be enabled for G832Adm framing.
  [CSCdj41709]

• The ATM Accounting periodic collection writes more records than the number of VCs it is monitoring.
  [CSCdj48371]

• The command "clear counters" can caused a T1 frame slip on the CES ports. The workaround is to not clear the counters.
  [CSCdj48158]

• For the PVPs, VPI=0 is not allowed. This restriction has been relaxed for the hard transit PVPs.
  [CSCdj49255]

• For ATM25 cards, the command "show atm vc" can potentially cause the switch to crash.
  [CSCdj50142]

• Memory leak in 11.2.8 release.
  [CSCdj50993]

• The SSCOP layer sequence number wraparound condition leads to memory leaks and memory fragmentation problems. The problem occurs when the SSCOP's send sequence number reaches a maximum value of 16777215. The switch needs to be reset to continue normal functionality.
  [CSCdj63058]

• The switch does not support restart based on VPI/VCI.
  [CSCdi72017]

Release 11.2(10)WA3(4) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(10)WA3(4).

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 ASP ATM interface supports is 10.

• You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:

  • VBR: SCR + sustained-cell-rate-margin0-factor x (PCR - SCR)

  • ABR, UBR: no bandwidth is allocated (guaranteed)

[CSCdj01016]

• Using the copy flash bootflash command causes a power-supply failure message when there are two power supplies installed and one of them is turned off. Normally both power supplies are turned on for redundancy.
  [CSCdj01757]

• A DS-3 PAM interface connected to a Cisco BPX might go down and come back up after a no shutdown command. Operation is normal after it comes back up for the second time.
  [CSCdj03229]

• Inconsistent ATM RMON call attempt counters on incoming and outgoing ports.

The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces due to switch crankback attempts. This might cause a discrepancy between the call attempt counters shown on the following:

• Portselgroup representing the interface on which the call came in

• PortSelgroup representing the interface over which an attempt was made to forward the call

This might be more evident when a call fails to be established.
[CSCdj10889]

• ATM-RMON data collection cannot be configured on subinterfaces or tunnels. The atm  rmon  collect command is accepted for hardware interfaces only, and ignored for subinterfaces. SNMP and NVGEN support (via the portSelTable) is not possible until 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 that interface.
  [CSCdj13565]

• The cell counts on a snooped interface are double the actual number of cells transmitted.
  [CSCdj18430]

• For the 25-Mbps PAM, SNMP support is not fully available. The "ciscoAtmIfPhysEntryData" table and LED information will be supported in a future release.
  [CSCdj18678]

• The "no shut" command causes the system to reset when a PAM is not present.
  [CSCdj24272]

• Using an OC12 PAM on LightStream 1010 as a network clock source results in bad clock quality.
  [CSCdj25769]

• A LightStream 1010 could experience cell loss during hot swapping one of its power supplies.
  [CSCdj25772]

• The fail over time for the LightStream 1010 CES soft VC on a redundant link could be inconsistent, with a range from less than a second to 15 seconds.
  [CSCdj28496]

• A tftp download to the LightStream 1010 could fail due to an ARP table corruption problem. This problem only affects the tftp download.

Workaround

Use the ip host-routing command in the general configuration mode.
[CSCdj32484]

• If the LightStream 1010 memory is almost or completely exhausted, soft PVCs that go down might not come up and will remain in RELEASING or INACTIVE state.
  [CSCdj42967]

• With the multiple LES/BUS pairs configured on a LightStream 1010 and about 20 LECs configured to join the ELANs, repeated shut/noshut of the interface for an extended period could produce the "ATMS2000_add_party_to_output_only_errors".
  [CSCdj50627]

• The remote defect identification (RDI) cells sent by an end point in response to the Alarm Indicator Signal (AIS) are not propagated beyond that intermediate switch. Once the fault on one interface is detected, the switch removes the connection leg entries for both interfaces, even though the other interface might be up. As a result, the RDI cells are dropped at the switch.
  [CSCdi55937]

• Numerous interface resets on the LightStream 1010 might generate the following error message.

%ATMSIG-3-FAILASSERT: Assertion failed: file "../atm/atmsig_ie.c", line 5950

Workaround

Correct the physical layer, which is usually the cause of the problem.
[CSCdj61842]

• The traffic that can go through an E3 board for one PVC is limited to 65535 cells per second independent of the framing type used. There is no benefit configuring G832 framing.
  [CSCdi72255]

• When a large number (more than 1000) of SVC s are present on a specific interface and a shutdown command is executed, "%SYS-3-CPUHOG:" message might appear. All the SVCs on that interface are released as expected. This message indicates that the process has run for a long time before it returns the control to the kernel which then can schedule other tasks.
  [CSCdi74229]

• Under very heavy traffic conditions the switch can experience temporary queue cell failures. This should clear up once the traffic congestion clears up.
  [CSCdi75584]

• Due to sensitive Receiver circuitry, noise can be interpreted as a valid signal. This condition causes the DS-3 controller to interpret the condition as a bad signal, turning the RX LEDs red on that port.
  [CSCdi82954]

• Under heavy signaling activities when a large number of LANE clients come up and down constantly, over extended periods of time, it is possible that the system might run out of AAL5 buffers and the following message appears on the console:

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

The system continues to function, in most instances, but might stop accepting any more calls from the end systems.

Workaround

If the switch does not bring up more calls, toggling an interface might help to reinitialize all the connections and bring the system back to working condition.
[CSCdi83275]

• When an AddParty message is sent across an E.164 interface, and the message does not include the CallingPartyAddress information element, the AddParty request is rejected on the first attempt. The second attempt will be successful.

Workaround

The normal mode of operation is to include the CallingPartyAddress information element in the AddParty message.
[CSCdi83567]

• Logical multicasting is not supported in this LightStream 1010 release.
  [CSCdi85540]

• A LAN Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LAN Emulation Servers (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 Version 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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'

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

• A DS-3 PAM AIS is not sent from a shutdown port when reloading the switch software. This might cause one side of the link to appear up and the other side of the link to appear down. It only occurs if one side of the link is shutdown during a power-up cycle. If the interface is brought up, both sides of the link resume correct operation.

Workaround

Ensure that the interface is not shut down during a switch software reload.
[CSCdi93291]

• Improve pak element allocation mechanisms to reduce memory fragmentation.
  [CSCdj70898]

• Uses the ATC code point conversion based on UNI version.
  [CSCdj73705]

• CES: After hotswapping CES card, some lines from "show ces int" are unavailable.
  [CSCdj74469]

• SSCOP: Reserved field in an ENDAK PDU is sometimes set to non-zero value.
  [CSCdj82090]

• The switch crashes while writing core if the core file length is greater than 32 characters.
  [CSCdj85540]

• ATMSIG: An extra byte is added in the calling party subaddress IE.
  [CSCdj91059]

Caveats and Caveats Corrected For Release 11.2(8)WA3(3) and 11.2(5)WA3(2b)

Releases before this one assumed that in each priority level the default clock (if none was configured) was the system clock (ASP reference). With this release no defaults are assumed. A clock at a priority that is not configured specifies "no clock." When clock switch over occurs, the software will switch to the next highest-configured priority network clock source and skip priorities that are not configured.

This section contains listings of the caveats and corrected caveats for these releases. Use Table 7 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:

• Release 11.2(8)WA3(3) Caveats Corrected

• Release 11.2(8)WA3(3) Caveats

• Release 11.2(5)WA3(2b) Caveats Corrected

• Release 11.2(5)WA3(2b) Caveats

Release 11.2(8)WA3(3) Caveats Corrected

This section describes caveats that have been corrected by Release 11.2(8)WA3(3) for the LightStream 1010 ATM switch.

• Networks with NNI interfaces and many SVC's (~2000) may experience buffer failures when all calls are released then setup quickly. This typically occurs when an interface is "shut" then rapidly "no shut". Also, the PNNI hops are limited to 10. It has now been raised to 20, per the PNNI specification.
  [CSCdj05818]

• When a Soft-PVC flaps (goes down and comes up) after it is setup, CrossConnectIdentifier in the 1695 atmVclTable (or atmVplTable) is not set. This happens in the source and destination switches.
  [CSCdj30548]

• On a VP Tunnel interface, if autoconfiguration is turned off and ILMI keep-alive is turned on and when the VP Tunnel status is marked as up, and autoconfiguration is off and ILMI keep-alive is on, ILMI keep-alive fails because the VP Tunnel status is still marked as up. Signaling and PNNI assume the VP Tunnel interface is active when it is down.
  [CSCdj27688]

• Compatibility Instruction Indicator checks were not done correctly. As a result, some of the messages were ignored by the switch while running UNI 4.0.
  [CSCdj27960]

• If you attempt to perform an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch agent stops working.
  [CSCdj31762]

• The microcode for the DCU on the LightStream CES PAM (Port Adaptor Module) inserted CSI=1 in odd numbered AAL1 cells, whether or not SRTS was in use. The DCU microcode and the related driver macrocode now has the CSI bit set to the correct standards.
  [CSCdj31991]

• The LightStream 1010 might crash if hostname is changed and the PNNI node is being deleted when using the no node ATM Router PNNI command.
  [CSCdj34430]

• The ATM Accounting ready file cannot be retrieved using TFTP.
  [CSCdj35955]

• Memory allocated for progress information was not freed properly.
  [CSCdj37401]

• After a no auto-summary is issued and saved in NVRAM, PNNI still summarizes the default summary address after a reboot.
  [CSCdj38313]

• The vci: 0-31 is reserved for vpi >= 1. But the switch may give vci: 0-31 for vpi >= 1 in the network side of the switch during call-setup and the call is rejected by the adjacent switch. This restriction is now removed by giving only (vci value > 31) for any vpi.
  [CSCdj39561]

• When changing framing from G832 adm to G751 adm, occasionally the framer goes out of frame on one side. You see a similar problem whenever the switch reloads in framing mode   G751 adm.
  [CSCdj37771]

• The following three problems have been fixed:

On_Demand accounting data collection would sometimes get into a loop

Connection-type checking for failed attempts was incorrect

Encoding of timestamp for data collection was incorrect for failed attempt records.
[CSCdj40236]

• The global system wide LECs address configuration, even though in the system, is not visible when you use the write terminal or show config command. However, it can be displayed by using the show atm ilmi-config command.
  [CSCdj37678]

• Address registration will sometimes fail when the peer interface is quickly toggled.

Workaround

Remove the address from the peer and then re-establish it.
[CSCdi79797]

• ILMI autoconfiguration advertises UNI 3.1 as the highest UNI version, even though the current software release supports UNI 4.0. In order to run UNI 4.0 signaling, the following steps are necessary.

Step 1 Autoconfiguration must be disabled using the following interface level command.

Switch(config-if)# no atm auto-configuration

Step 2 The UNI version must be manually configured using the following interface level command.

Switch(config-if)# atm uni version 4.0.

[CSCdj04489]

• If the clock selection on both sides of a DS-3 link are configured as loop-timed mode, that interface goes down as expected because neither side is sourcing the clock for that link. Restoring a clock to this link does not automatically bring the interface up. A manual shutdown/noshutdown is needed on that interface to bring it back up.
  [CSCdj05900]

• Soft-PVC configurations, with both originating and terminating legs on the same switch, might get cross-connected on the same switch.

The limitations follow:

• Only call attempts that failed are counted

• Calls that succeed are not counted against the total number of successful calls

Note that the Accounting management application does support Soft-PVC configurations.
[CSCdj21961]

• When a large number of SVCs are repeatedly connected and released, Accounting might retain some connection records, showing them as active connections, even though they were released.
  [CSCdj23307]

• When a large number of SVCs are brought up across VP tunnels and an interface through which all of the SVCs pass is shut down, the switch might experience memory fragmentation that results in memory exhaustion.
  [CSCdi76382]

• Address registration sometimes fails when the peer interface is quickly toggled. To fix this problem, remove the address from the peer and reestablish the connection.
  [CSCdi79797]

Release 11.2(8)WA3(3) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(8)WA3(3).

The following caveats have been identified for this release of the LightStream 1010 ATM switch software.

• The Ethernet port on the LightStream 1010 is sometimes found in a frozen state SHOW INTERFACE ETHERNETt2/0/0 shows the interface as up but the output queue full. Issuing a CLEAR INTERFACE ETHERNET2/0/0 command clears this state.
  [CSCdj02004]

• The Ethernet interface might fail to respond when the input queue is wedged, 40/40 in the LightStream 1010.

Workaround

Issue the CLEAR INTERFACE ETHERNET2/0/0 command to bring the interface back up.
[CSCdj15388]

• LightStream 1010 may log %SYS-3-MGDTIMER:Uninitialized timer, timer stop, timer = [hex]. This message might not cause traffic or network problems.
  [CSCdj22451]

• No shut causes the system to reset when PAM is not present.
  [CSCdj24272]

• The fail over time for the LightStream 1010 CES Soft-VC on a redundant link could be inconsistent, from less than a second to 15 seconds.
  [CSCdj28496]

• An LightStream 1010 could experience cell loss during hot swapping of one of its power supplies.
  [CSCdj25772]

• If a tunnel that runs between two LightStream 1010s goes down, the ATM subinterface will always show as up. Even with configuring ILMI keepalives or using OAM cells, the subinterface always stays up. Some other SHOW commands will indicate that the tunnel is down.
  [CSCdj32290]

• A tftp download to an LightStream 1010 could fail, due to an ARP table corruption problem. This problem will only affect the tftp download.

Workaround

Use the ip host-routing command in the general configuration mode.
[CSCdj32484]

• The LightStream 1010 ATM switch rejects setup when the called Party address or the Calling party address length is more than 20 bytes.
  [CSCdj38407]

• T1/E1 PAMs when hot swapped by oc3 PAM could lock up the switch. This effect is seen only if oc3 is hot swapped into a slot where T1/E1 was residing.

Workaround

Make sure oc3 is not hot swapped in the slot that was used by T1/E1. If an oc3 card needs to be hot swapped in place of T1/E1, remove the T1/E1 card, reload, and then insert oc3 PAM.
[CSCdj41665]

• The TTB length bit is not set for G832 framing. The TTB messages, which checks for the continued presence of the intended transmitter, must be enabled for G832Adm framing.
  [CSCdj41709]

• The command "clear counters" can caused a T1 frame slip on the CES ports. The workaround is to not clear the counters.
  [CSCdj48158]

• The ATM Accounting periodic collection writes more records than the number of VCs it is monitoring.
  [CSCdj48371]

• For the PVPs, VPI=0 is not allowed. This restriction has been relaxed for the hard transit PVPs.
  [CSCdj49255]

• For ATM25 cards, the command "show atm vc" can potentially cause the switch to crash.
  [CSCdj50142]

• Memory leak in 11.2.8 release.
  [CSCdj50993]

• The maximum number of ELAN LES/BUS pairs that the ASP ATM interface supports is 10.

• The SSCOP layer sequence number wraparound condition leads to memory leaks and memory fragmentation problems. The problem occurs when the SSCOP's send sequence number reaches a maximum value of 16777215. The switch needs to be reset to continue normal functionality.
  [CSCdj63058]

• When a reload is performed, the following message might appear.

%ALIGN-3-SPURIOUS: Spurious memory access made at 0x600D2EBC reading 0x0

This caveat does not affect the operation of the switch.
[CSCdi74298]

• Due to sensitive Receiver circuitry, noise can be interpreted as a valid signal. This condition causes the DS-3 controller to interpret the condition as a bad signal turning the RX LEDs red on that port.
  [CSCdi82954]

• When an AddParty message is sent across an E.164 interface, and the message does not include the CallingPartyAddress information element, the AddParty request is rejected on the first attempt. The second attempt will be successful.

Workaround

The normal mode of operation is to include the CallingPartyAddress information element in the AddParty message.
[CSCdi83567]

• Logical multicasting is not supported in this LightStream 1010 release.
  [CSCdi85540]

• A LAN Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LAN Emulation Servers (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 Version 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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'

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

• You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:

  • VBR: SCR + sustained-cell-rate-margin0-factor x (PCR - SCR)

  • ABR, UBR: no bandwidth is allocated (guaranteed)

[CSCdj01016]

• Using the copy flash bootflash command causes a power-supply failure message when there are two power supplies installed and one of them is turned off. Normally both power supplies are turned on for redundancy.
  [CSCdj01757]

• If a T1/E1 port is configured as the clock source for the system, and that port receives transitions in link status that affect the clock, other interfaces that derive their clock from that clock source may go down for a moment. This situation only occurs when transitions are less than 1 second.
  [CSCdj03281]

• ATM-RMON data collection cannot be configured on subinterfaces or tunnels. The atm  rmon  collect command is accepted for hardware interfaces only, and ignored for subinterfaces. SNMP and NVGEN support (via the portSelTable) is not possible until 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 that interface.
  [CSCdj13565]

• The remote defect identification (RDI) cells sent by an end point in response to the Alarm Indicator Signal (AIS) are not propagated beyond that intermediate switch. Once the fault on one interface is detected, the switch removes the connection leg entries for both interfaces, even though the other interface might be up. As a result, the RDI cells are dropped at the switch.
  [CSCdi55937]

• When a large number (more than 1000) of SVC s are present on a specific interface and a shutdown command is executed, "%SYS-3-CPUHOG:" message might appear. All the SVCs on that interface are released as expected. This message indicates that the process has run for a long time before it returns the control to the kernel which then can schedule other tasks.
  [CSCdi74229]

• The traffic that can go through an E3 board for one PVC is limited to 65535 cells per second independently of the framing type used. There is no benefit configuring G832 framing.
  [CSCdi72255]

• The Receive cell counter on the virtual circuit VPI=0, VCI=32 shows erroneous cell counts.
  [CSCdj03621]

• The SNMP agent on the LightStream 1010 switch always returns "Slot empty" value even if a flash card is present in the PCMCIA slot.
  [CSCdj04898]

• A DS-3 PAM AIS is not sent from a shutdown port when reloading the switch software. This might cause one side of the link to appear up and the other side of the link to appear down. It only occurs if one side of the link is shutdown during a power-up cycle. If the interface is brought up, both sides of the link resume correct operation.

Workaround

Ensure that the interface is not shut down during a switch software reload.
[CSCdi93291]

• A DS-3 PAM interface connected to a Cisco BPX might go down and come back up after a no shutdown command. Operation is normal after it comes back up for the second time.
  [CSCdj03229]

• Inconsistent ATM RMON call attempt counters on incoming and outgoing ports.

The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces due to switch crankback attempts. This might cause a discrepancy between the call attempt counters shown on the following:

• Portselgroup representing the interface on which the call came in

• PortSelgroup representing the interface over which an attempt was made to forward the call

This might be more evident when a call fails to be established.
[CSCdj10889]

• Under heavy signaling activities when a large number of LANE clients come up and down constantly, over extended periods of time, it is possible that the system might run out of AAL5 buffers and the following message appears on the console:

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

The system continues to function, in most instances, but might stop accepting any more calls from the end systems.

Workaround

If the switch does not bring up more calls, toggling an interface might help to reinitialize all the connections and bring the system back to working condition.

[CSCdi83275]

• The switch does not support restart based on VPI/VCI.
  [CSCdi72017]

• ATM Accounting background notification is not supported.

  • To change connection-type for the selection entry, first use the shutdown command on all interfaces where ATM accounting is enabled. The interfaces can be brought back up after the connection type for the selection entry is changed using the no shutdown command.

  • To enable or disable ATM accounting globally, first use the shutdown command on all the interfaces where ATM accounting is enabled. The interfaces can be brought up after the enable and disable operation is complete using the no shutdown command.

  • To enable or disable ATM accounting on an interface, first use the shutdown command on that interface. The interface can be brought up after the enable/disable operation is complete using the no  shutdown command.

Support for ATM accounting background notifications is provided in the next maintenance release.
[CSCdj13326]

• The cell counts on a snooped interface are double the actual number of cells transmitted.
  [CSCdj18430]

• For the 25-Mbps PAM, SNMP support is not fully available. The "ciscoAtmIfPhysEntryData" table and LED information will be supported in a future release.
  [CSCdj18678]

Release 11.2(5)WA3(2b) Caveats Corrected

This section describes caveats that have been corrected by the Release 11.2(5)WA3(2b) for the LightStream 1010 ATM switch.

• The following features were not supported in the previous release even though the commands might have been visible in the command-line interface.

  • ATM Accounting

  • ATM RMON

  • ATM LAN Emulation MIBs

[CSCdj03221]

• The no form for the service-category-limit command applies to all service categories instead of individual service categories.
  [CSCdj01176]

• When ATM Signaling Error debugging is enabled, the following debug message might occur:

ATMSIG: incoming msg has invalid protocol discriminator 0

This message indicates that SSCOP passed a PDU to Signaling that is not recognized as a valid message. The message might occur when heavy signaling loads occur between the switch and other Cisco Systems routers. No failure of function results from this.
[CSCdi72727]

• The following message appears when a party times-out while waiting for an acknowledgment for an outgoing setup.

crankback NULL while building IEs

This caveat does not affect the operation of the switch.
[CSCdi86055]

• Agent does not reject duplicate static routes from SNMP and does not give an error message.
  [CSCdi91087]

• Automatic summarization is ineffective after the following command sequence.

Switch# configure terminal

Switch(config)# atm router pnni

Switch(config-atm-router)# node 1 disable

Switch(config-atm-router)# node 1 enable

As a result, the end system addresses are not automatically summarized using the 13-byte prefixes derived from the switch address. Use the following command sequence, which turns automatic summarization off and on, to correct this problem.

Switch# configure terminal

Switch(config)# atm router pnni

Switch(config-atm-router)# node 1 

Switch(config-atm-router)# no auto-summary

Switch(config-atm-router)# auto-summary 

[CSCdj00300]

• When the switch receives a call-proceeding message, but does not receive a connect or release message, the switch should send a release message with cause # 102-- "recovery on timer expiry." Currently the switch sends a release message with cause # 27 -- "destination out of order."
  [CSCdj01641]

• When building the Broadband Low Layer Information (BLLI) Element in an ATM Signaling message, per information provided by a client, the length of the contents of the information to insert into the BLLI are not checked for accuracy. Currently no client is known to provide an inaccurate length parameter, but you should check to avoid a severe problem if this situation should occur.
  [CSCdj03169]

• When LES/BUS and LECS are both configured on the same LightStream1010 CPU port, the LECS is not able to distinguish the LES from an LEC.

This can cause the following symptoms:

• The show lane configuration command shows the LES as if it were an LEC.

• If a only a single LES is configured on the ELAN, then it functions normally. However, if a second LES is configured on the same ELAN for the purpose of redundancy (SSRP), it does not function correctly.

Workarounds

• Do not configure any LES/BUSs on the same LightStream 1010 CPU port as the LECS.

• Use only a single LES/BUS on the ELAN.
  [CSCdj04377]

• When a physical port type is requested from SNMP for an OC3UTP PAM, the port type field returns "other."
  [CSCdj04393]

Release 11.2(5)WA3(2b) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(5)WA3(2b).

• Networks with NNI interfaces and many SVCs (~2000) may experience buffer failures when all calls are released and set up quickly. This typically occurs when an interface is "shut" then rapidly "no shut." Also, the PNNI hops are limited to 10.
  [CSCdj05818]

• When a Soft-PVC flaps (goes down and comes up) after it is set up, CrossConnectIdentifier in the 1695 atmVclTable (or atmVplTable) is not set. This happens in the source and destination switches.
  [CSCdj30548]

• On a VP Tunnel interface, if autoconfiguration is turned off and ILMI keep-alive is turned on and the VP Tunnel status is marked as up, autoconfiguration is off and ILMI keep-alive is on, ILMI keep-alive fails because the VP Tunnel status is still marked as up. Signaling and PNNI assume the VP Tunnel interface is active when it is down.
  [CSCdj27688]

• Compatibility Instruction Indicator checks were not done correctly. As a result, some of the messages were ignored by the switch while running UNI 4.0.
  [CSCdj27960]

• If you attempt to perform an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch agent stops working.
  [CSCdj31762]

• The microcode for the DCU on the LightStream CES PAM (port adaptor module) inserted CSI=1 in odd numbered AAL1 cells, whether or not SRTS was in use. The DCU microcode and the related driver macrocode now has the CSI bit set to the correct standards.
  [CSCdj31991]

• The LightStream 1010 might crash if the hostname is changed and the PNNI node is being deleted when using the no node ATM Router PNNI command.
  [CSCdj34430]

• The ATM Accounting ready file cannot be retrieved using TFTP.
  [CSCdj35955]

• Memory allocated for progress information was not freed properly.
  [CSCdj37401]

• After a no auto-summary is issued and saved in NVRAM, PNNI still summarizes the default summary address after a reboot.
  [CSCdj38313]

• The vci: 0-31 is reserved for vpi >= 1. But the switch may give vci: 0-31 for vpi >= 1 in the network side of the switch during call-setup and the call is rejected by the adjacent switch.
  [CSCdj39561]

• On_Demand accounting data collection would sometimes get into a loop.
  Connection_type checking for failed attempts was incorrect.
  Encoding of timestamp for data collection was incorrect for failed attempt records.
  [CSCdj40236]

• The global system wide LECs address configuration, even though in the system, is not visible when you use the write terminal or show config command. However, it can be displayed by using the show atm ilmi-config command.
  [CSCdj37678]

• The maximum number of ELAN LES/BUS pairs that the ASP ATM interface supports is 10.

• Soft-PVC configurations, with both originating and terminating legs on the same switch, might get cross connected on the same switch.

The limitations are following:

• Only call attempts that failed are counted

• Calls that succeed are not counted against the total number of successful calls

Note that the Accounting management application does support Soft-PVC configurations.
[CSCdj21961]

• When a large number of SVCs are repeatedly connected and released, Accounting might retain some connection records, showing them as active connections, even though they were released.

This caveat will be fixed in the next maintenance release.
[CSCdj23307]

• When a reload is performed, the following message may appear.

%ALIGN-3-SPURIOUS: Spurious memory access made at 0x600D2EBC reading 0x0

This caveat does not affect the operation of the switch.
[CSCdi74298]

• Address registration sometimes fails when the peer interface is quickly toggled. To fix this problem, remove the address from the peer and reestablish the connection.
  [CSCdi79797]

• Due to sensitive Receiver circuitry, noise may be interpreted as a valid signal. This condition causes the DS-3 controller to interpret the condition as a bad signal turning the RX LEDs red on that port.
  [CSCdi82954]

• When an AddParty message is sent across an E.164 interface, and the message does not include the CallingPartyAddress information element, the AddParty request is rejected on the first attempt. The second attempt will be successful.

Workaround

The normal mode of operation is to include the CallingPartyAddress information element in the AddParty message.
[CSCdi83567]

• Logical multicasting is not supported in this LightStream 1010 release.
  [CSCdi85540]

• A LAN Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LAN Emulation Servers (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 Version 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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'

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

• You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:

  • VBR: SCR + sustained-cell-rate-margin0-factor x (PCR - SCR)

  • ABR, UBR: no bandwidth is allocated (guaranteed)

[CSCdj01016]

• Using the copy flash bootflash command causes a power-supply failure message when there are two power supplies installed and one of them is turned off. Normally both power supplies are turned on for redundancy.
  [CSCdj01757]

• If a T1/E1 port is configured as the clock source for the system, and that port receives transitions in link status that affect the clock, other interfaces that derive their clock from that clock source may go down for a moment. This situation only occurs when transitions are less than 1 second.
  [CSCdj03281]

• ILMI autoconfiguration advertises UNI 3.1 as the highest UNI version, even though the current software release supports UNI 4.0. In order to run UNI 4.0 signaling, the following steps are necessary.

1 Autoconfiguration must be disabled using the following interface level command.

Switch(config-if)# no atm auto-configuration

2 The UNI version must be manually configured using the following interface level command.

Switch(config-if)# atm uni version 4.0.

[CSCdj04489]

• ATM-RMON data collection cannot be configured on subinterfaces or tunnels. The atm  rmon  collect command is accepted for hardware interfaces only, and ignored for subinterfaces. SNMP and NVGEN support (via the portSelTable) is not possible until 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 that interface.
  [CSCdj13565]

• The remote defect identification (RDI) cells sent by an end point in response to the Alarm Indicator Signal (AIS) are not propagated beyond that intermediate switch. Once the fault on one interface is detected, the switch removes the connection leg entries for both interfaces, even though the other interface might be up. As a result, the RDI cells are dropped at the switch.
  [CSCdi55937]

• When a large number (more than 1000) of SVC s are present on a specific interface and a shutdown command is executed, "%SYS-3-CPUHOG:" message might appear. All the SVCs on that interface are released as expected. This message indicates that the process has run for a long time before it returns the control to the kernel which then can schedule other tasks. [CSCdi74229]

• The traffic that can go through an E3 board for one PVC is limited to 65535 cells per second independently of the framing type used. There is no benefit configuring G832 framing.
  [CSCdi72255]

• If the clock selection on both sides of a DS-3 link are configured as loop-timed mode, that interface goes down as expected because neither side is sourcing the clock for that link. Restoring a clock to this link does not automatically bring the interface up. A manual shutdown/noshutdown is needed on that interface to bring it back up.
  [CSCdj05900]

• The Receive cell counter on the virtual circuit VPI=0, VCI=32 shows erroneous cell counts.
  [CSCdj03621]

• The SNMP agent on the LightStream 1010 switch always returns "Slot empty" value even if a flash card is present in the PCMCIA slot.
  [CSCdj04898]

• A DS-3 PAM AIS is not sent from a shutdown port when reloading the switch software. This might cause one side of the link to appear up and the other side of the link to appear down. It only occurs if one side of the link is shutdown during a power-up cycle. If the interface is brought up, both sides of the link resumes operating correctly.

Workaround

Ensure that the interface is not shut down during a switch software reload.
[CSCdi93291]

• A DS-3 PAM interface connected to a Cisco BPX might go down and come back up after a no shutdown command. Operation is normal after it comes back up for the second time.
  [CSCdj03229]

• Inconsistent ATM RMON call attempt counters on incoming and outgoing ports.

The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces due to switch crankback attempts. This might cause a discrepancy between the call attempt counters shown on the following:

• Portselgroup representing the interface on which the call came in

• PortSelgroup representing the interface over which an attempt was made to forward the call.

This might be more evident when a call fails to be established.
[CSCdj10889]

• When disabling Cisco Discovery Protocol (CDP) on ATM interface 2/0/0.x configured as an LEC, the new configuration is not saved to nonvolatile random-access memory (NVRAM) and does not appear when using the show running-config command. CDP is disabled on the interface until you reload the software. After you reload the software, CDP is again re-enabled on the interface. This is caused by the new configuration not being saved to NVRAM prior to reloading the software.
  [CSCdj11070]

• Under heavy signaling activities when a large number of LANE clients come up and down constantly, over extended periods of time, it is possible that the system might run out of AAL5 buffers and the following message appears on the console:

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

The system continues to function, in most instances, but might stop accepting any more calls from the end systems.

Workaround

If the switch does not bring up more calls, toggling an interface might help to reinitialize all the connections and bring the system back to working condition.

[CSCdi83275]

• When a large number of SVCs are brought up across VP tunnels and an interface through which all of the SVCs pass is shut down, the switch might experience memory fragmentation that results in memory exhaustion.
  [CSCdi76382]

• The switch does not support restart based on VPI/VCI.
  [CSCdi72017]

• ATM Accounting background notification is not supported and requires the following workarounds:

  • To change connection-type for the selection entry, first use the shutdown command on all interfaces where ATM accounting is enabled. The interfaces can be brought back up after the connection type for the selection entry is changed using the no shutdown command.

  • To enable or disable ATM accounting globally, first use the shutdown command on all the interfaces where ATM accounting is enabled. The interfaces can be brought up after the enable and disable operation is complete using the no shutdown command.

  • To enable or disable ATM accounting on an interface, first use the shutdown command on that interface. The interface can be brought up after the enable/disable operation is complete using the no  shutdown command.

Support for ATM accounting background notifications is provided in the next maintenance release.
[CSCdj13326]

• The cell counts on a snooped interface are double the actual number of cells transmitted.
  [CSCdj18430]

• For the 25-Mbps PAM, SNMP support is not fully available. The "ciscoAtmIfPhysEntryData" table and LED information will be supported in a future release.
  [CSCdj18678]

Modifications and Caveats For Release 11.2(2)WA3(1a)

The following clock selection changes listed in Table 9 apply to release 11.2(2)WA3(1a).

Release 11.2(2)WA3(1a) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(2)WA3(1a).

The following features are not supported in this release even though the commands might be visible in the command-line interface.

• ATM Accounting

• ATM RMON

• ATM LAN Emulation MIBs
  [CSCdj03221]

Support for these features is expected in a subsequent release.

• The maximum number of ELAN LES/BUS pairs that the ASP ATM interface supports is 10.

The following caveats have been identified for this release of the LightStream 1010 ATM switch software.

• When ATM Signaling Error debugging is enabled, the following debug message might occur:

ATMSIG: incoming msg has invalid protocol discriminator 0

This message indicates that SSCOP passed a PDU to Signaling that is not recognized as a valid message. The message might occur when heavy signaling loads occur between the switch and other Cisco Systems routers. No failure of function results from this.
[CSCdi72727]

• When a reload is performed, the following message might appear.

%ALIGN-3-SPURIOUS: Spurious memory access made at 0x600D2EBC reading 0x0

This caveat does not affect the operation of the switch.
[CSCdi74298]

• Under heavy loads the following message appears on the console.

incoming pak size 16 does not match embedded msg size

This caveat does not affect the operation of the switch.
[CSCdi76330]

• Address registration sometimes fails when the peer interface is quickly toggled. To fix this problem, remove the address from the peer and reestablish the connection.
  [CSCdi79797]

• Due to sensitive Receiver circuitry, noise might be interpreted as a valid signal. This condition causes the DS-3 controller to interpret the condition as a bad signal turning the RX LEDs red on that port.
  [CSCdi82954]

• Under heavy signaling activities when a large number of LANE clients come up and down constantly, over extended periods of time, it is possible that the system would run out of AAL5 buffers and the following message appears on the console:

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

The system continues to function, in most instances but, on few occasions, it might stop accepting any more calls from the end systems.

Workaround

In case the system does not bring up more calls, toggling the interface helps reinitialize all the connections and bring the system back to working condition.
[CSCdi83275]

• When an AddParty message is sent across an E.164 interface, and the message does not include the CallingPartyAddress information element, the AddParty request is rejected on the first attempt. The second attempt will be successful.

Workaround

The normal mode of operation is to include the CallingPartyAddress information element in the AddParty message.
[CSCdi83567]

• Logical multicasting is not supported in the present LightStream 1010 release.
  [CSCdi85540]

• The following message appears when a party times-out while waiting for an acknowledgment of an outgoing setup.

crankback NULL while building IEs

This caveat does not affect the operation of the switch.
[CSCdi86055]

• When a PC running LINUX and LANE is attached to the switch as an endsystem with a LEC configured, the result might be a hanging half-leg on the switch. You can correct this situation by using the clear atm atm-vc command.
  [CSCdi90543]

• Agent does not reject duplicate static routes from SNMP and does not give an error message.
  [CSCdi91087]

• When SSRP and LECS LES/BUS are all configured on the ASP, the result can be an intermittent failure in LANE clients on the local switch and on the remote switch joining the ELAN.
  [CSCdi91727]

• A LAN Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LAN Emulation Servers (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 Version 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, using the following LES router configuration:

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

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

%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'

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

• The following message might occasionally be displayed on the console:

"%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs".

No failure of function results from this message.
[CSCdi92280]

• Automatic summarization is ineffective after the following command sequence.

Switch# configure terminal

Switch(config)# atm router pnni

Switch(config-atm-router)# node 1 disable

Switch(config-atm-router)# node 1 enable

As a result, the end system addresses are not automatically summarized using the 13-byte prefixes derived from the switch address. Use the following command sequence, which turns automatic summarization off and on, to correct this problem.

Switch# configure terminal

Switch(config)# atm router pnni

Switch(config-atm-router)# node 1 

Switch(config-atm-router)# no auto-summary

Switch(config-atm-router)# auto-summary 

[CSCdj00300]

• The LEC becomes stuck in the waitingListen and the lecsConnect states and the ASP subinterface becomes stuck in waitingIlmi state. To bring the system back to initial state, use the shut/no shut command. Also, some of the clients might stick in the waitingIlmi state.
  [CSCdj00646]

• You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:

  • VBR: SCR + sustained-cell-rate-margin0-factor x (PCR - SCR)

  • ABR, UBR: no bandwidth is allocated (guaranteed)

[CSCdj01016]

• The no form for service-category-limit command applies to all service categories instead of individual service categories.
  [CSCdj01176]

• When the switch receives a call-proceeding message, but does not receive a connect or release message, the switch should send a release message with cause # 102-- "recovery on timer expiry." Currently the switch sends a release message with cause # 27 -- "destination out of order."
  [CSCdj01641]

• Using the copy flash bootflash command causes a power-supply failure message when there are two power supplies installed and one of them is turned off. Normally both power supplies are turned on for redundancy.
  [CSCdj01757]

• When building the Broadband Low Layer Information (BLLI) Element in an ATM Signaling message, per information provided by a client, the length of the contents of the information to insert into the BLLI are not checked for accuracy. Currently no client is known to provide an inaccurate length parameter, but you should check to avoid a severe problem if this situation should occur.
  [CSCdj03169]

• If a T1/E1 port is configured as the clock source for the system, and that port receives transitions in link status that affect the clock, other interfaces that derive their clock from that clock source might go down for a moment. This situation only occurs when transitions are less than 3 seconds.
  [CSCdj03281]

• When LES/BUS and LECS are both configured on the same LightStream1010 CPU port, the LECS is not able to distinguish the LES from an LEC.

This can cause the following symptoms:

• The show lane configuration command shows the LES as if it were an LEC.

• If a only a single LES is configured on the ELAN, then LES functions normally. However, if a second LES is configured on the same ELAN for the purpose of redundancy (SSRP), it does not function correctly.

Workarounds

• Do not configure any LES/BUSs on the same LightStream 1010 CPU port as the LECS.

• Use only a single LES/BUS on the ELAN.
  [CSCdj04377]

• When physical port type is requested from SNMP for an OC3UTP PAM, the port type field returns "other."
  [CSCdj04393]

• ILMI autoconfiguration advertises UNI 3.1 as the highest UNI version, even though the current software release supports UNI 4.0. In order to run UNI 4.0 signaling, the following steps are necessary.

Step 1 Autoconfiguration must be disabled using the following interface level command.

Switch(config-if)# no atm auto-configuration

Step 2 The UNI version must be manually configured using the following interface level command.

Switch(config-if)# atm uni version 4.0.

[CSCdj04489]

Documentation

For documentation of Cisco IOS Release 11.2 LightStream 1010 ATM switch software features, refer to the following publications, available as printed manuals or electronic documents:

• LightStream 1010 ATM Switch Hardware Installation Guide

• LightStream 1010 ATM Switch Software Configuration Guide (11.2)

• LightStream 1010 ATM Switch Command Reference (11.2)

• LightStream 1010 ATM Switch ASP Installation Guide

• LightStream 1010 ATM Switch PAM Installation Guide

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 up to date 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.

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.

Copyright 1989-1998 © Cisco Systems Inc.