Cisco IOS Release 11.2 Release Notes for LightStream 1010 ATM Switch Software

June 26, 1997

LightStream 1010 ATM Release 11.2(5)WA3(2b)

This release notes describe the features and caveats for Cisco IOS Release 11.2(5)WA3(2b) for the LightStream 1010 Asynchronous Transfer Mode (ATM) switch software. The LightStream 1010 ATM switch software is based on Cisco IOS Release 11.2(5). This release includes enhancements for the LightStream 1010 ATM switch.

Introduction

This release note discusses the following topics:

• New Release 11.2(5)WA3(2b) Features, page 2

• New Release 11.2(2)WA3(1a) Features, page 2

• Modifications for Release 11.2(2)WA3(1a), page 3

• Documentation, page 3

• Platform Support, page 4

• Cisco IOS Packaging, page 4

• Memory Requirements, page 5

• Release 11.2(5)WA3(2b) Caveats Corrected, page 6

• Release 11.2(5)WA3(2b) Caveats, page 8

• Release 11.2(2)WA3(1a) Caveats, page 12

• Cisco Connection Online, page 16

New Release 11.2(5)WA3(2b) Features

The following features have been added to the LightStream 1010 ATM switch software:

• ATM Accounting

• ATM Remote Monitoring (RMON)

• 25-Mbps Port Adapter Module (PAM)

• OC-12 Long Reach PAM

• OC-3 Long Reach PAM

See the section "Documentation" for a list of documents describing these features.

New Release 11.2(2)WA3(1a) Features

The following features have been added to the LightStream 1010 ATM switch software:

• Configurable well-known VCs for Signaling/ILMI/PNNI

• Soft-VC route optimization

• E.164 address translation

• UNI 4.0 features (ABR Signaling, PCR negotiation, Frame Discard, Anycast, and incremental QoS parameters)

• Access List based on Time of Day and Access List MIB

• PNNI MIBs

• IISP Auto configuration

• LANE services (LES/BUS/LECS) on ASP

• Enable/disable of Signaling/PNNI/SSCOP on a per port basis

• The LightStream 1010 IISP software image is no longer available as a separate image. Instead both the ATM routing modes, PNNI and IISP, functionalities are available in the LightStream 1010 PNNI software image. The default routing mode is PNNI. To restrict the routing mode to static (analogous to 11.1 release IISP image) configure the routing mode to static by using the atm routing-mode static global configuration command. Please refer to the LightStream 1010 ATM Switch Software Configuration Guide for more information.

The following new hardware is supported in the LightStream 1010 ATM switch release 11.2(2)WA3(1a):

• T1/E1 PAM

• OC-3 Mixed (3 multi-mode and 1 single-mode)

• DS-3 Quad/Dual

• -48 VDC Power Supply

• T1/E1 Circuit Emulation Services (CES) PAM

• Hotswap ASP (LS1015) for Catalyst 5500

Modifications for Release 11.2(2)WA3(1a)

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

Table  1: Clock Selection Changes for Release 11.2(2)WA3(1a)

Clock Mode	Release 11.1	Release 11.2
Network Derived	Derives clock from the port selected as the network clock at the highest priority. This can be the ASP if all clocks are bad or there was no selection.	If no selection for network-clock-select has been made the clock defaults to the ASP (default).
Free-running	Uses the ASP clock (default).	Uses the port Local oscillator on the PAM when available.
Loop-timed	Uses the clock derived from the receive side.	Uses the clock derived from the receive side.

In the 11.2 release, the default clock selected on any port was changed. The default mode is network-derived. If no port is selected as the source of the network clock, the default is the system clock supplied by the ASP. In the 11.1 release, if no clock source was specified for a port, the clock mode default was free-running, which was internally equivalent to selecting the system clock supplied by the ASP. The defaults are not saved in the configuration.

If you changed the default in 11.1 to network-derived, when upgrading to release 11.2, because network-derived is the default, the clock mode remains the same. However, if you move back to release 11.1 that port reverts to the free-running (with ASP) clock default configuration. If you want network-derived clock you must reconfigure the port.

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

For electronic documentation of Release 11.2 ATM switch software features available on the Cisco Connection Documentation, Enterprise Series CD-ROM, refer to the LightStream 1010 ATM Switch Software Configuration Guide and LightStream 1010 ATM Switch Command Reference publications, which are located in the LightStream 1010 database under ATM Adapters and Switches database.

You can also access Cisco technical documentation on the World Wide Web: http://www.cisco.com.

Platform Support

This release supports the LightStream 1010 ATM switch.

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.

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

Table  2: Cisco IOS Release 11.2(5)WA3(2b) for LightStream 1010 ATM Software Features 

Type	Feature
Cisco IOS Base Features	SNMP
	Asynchronous support (RS232)
	PPP (SLIP/PPP)
	IP
	NTP
	TACACS+
	Telnet
ATM Features	Point-to-point and point-to-multipoint Permanent VCCs and VPCs
	Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.0)
	Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.1)
	Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 4.0)
	Soft VCCs and VPCs
	VP Tunneling
	PNNI version 1.0
	ILMI version 4.0
	IISP
	LANE client (LEC) and LANE Services (LES/BUS/LECS) on ASP
	ATM ARP server on ASP
	ATM ARP client on ASP
	Port snooping
	OAM F4 and F5
	E.164 Address Translation
	Circuit Emulation
	ATM Access lists
	ATM Accounting
	ATM RMON

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

Table  3: Cisco IOS Release 11.2(2)WA3(1a) for LightStream 1010 ATM Software Features 

Type	Feature
Cisco IOS Base Features	SNMP
	Asynchronous support (RS232)
	PPP (SLIP/PPP)
	IP
	NTP
	TACACS+
	Telnet
ATM Features	Point-to-point and point-to-multipoint Permanent VCCs and VPCs
	Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.0)
	Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.1)
	Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 4.0)
	Soft VCCs and VPCs
	VP Tunneling
	PNNI version 1.0
	ILMI version 4.0
	IISP
	LANE client (LEC) and LANE Services (LES/BUS/LECS) on ASP
	ATM ARP server on ASP
	ATM ARP client on ASP
	Port snooping
	OAM F4 and F5
	E.164 Address Translation
	Circuit Emulation
	ATM Access lists

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 4 provides an approximate guide to use when determining the amount of DRAM required for a switch with 32 physical ports.

Table  4: DRAM Required Determined by SVCs

SVCs Required	DRAM Required
Less than 4000 active SVCs	16 MB DRAM
Between 4000 and 16,000 active SVCs	32 MB DRAM
Between 16,000 and 32,000 active SVCs	64 MB DRAM

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

1. Do not configure any LES/BUSs on the same LightStream 1010 CPU port as the LECS.
   
   
2. 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]

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

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.

• 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

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

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

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

1. Do not configure any LES/BUSs on the same LightStream 1010 CPU port as the LECS.
   
   
2. 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.

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

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

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

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

Cisco Connection Online

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

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

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

You can access CCO in the following ways:

• WWW:  http://www.cisco.com

• WWW:  http://www-europe.cisco.com

• WWW:  http://www-china.cisco.com

• Telnet:  cco.cisco.com

• Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

---

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

---