This document describes the features and caveats for Cisco IOS Release 12.0(7) for the LightStream 1010 ATM switch software. This software is based on Cisco IOS Release 12.0(6).
The LightStream 1010 ATM switch provides switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.
This section describes the system requirements for Release 12.0(7) and includes the following sections:
The standard default DRAM memory for the LightStream 1010 ATM switch is 64-MB DRAM (MEM-ASP64M).
Table 2: Supported Interfaces & Their Minimum Software Requirements
| Part Number
| Description
| Minimum Software Requirement
|
|---|
WAI-OC3-4MM
| 4-port STS-3c/STM-1 multimode fiber port adapters
| WAS1-1
|
WAI-OC3-4SS
| 4-port STS-3c/STM-1 single-mode fiber port adapters
| WAS1-1
|
WAI-OC3-4U5
| 4-port STS-3c/STM-1 UTP-5 port adapters
| WAS1-1
|
WAI-OC3-4SSLR
| 4-port STS-3c/STM-1 SMF long reach port adapters
| WAS3-2
|
WAI-OC3-1S3M
| OC-3 mix port adapter module, 1 IR+ port and 3 MM ports
| WAS3-1
|
WAI-OC12-1MM
| 1-port STS-12c/STM-4c multimode fiber port adapters
| WAS1-2
|
WAI-OC12-1SS
| 1-port STS-12c/STM-4c SMF port adapters
| WAS1-1
|
WAI-OC12-1SSLR
| 1-port STS-12c/STM-4c SMF long reach port adapters
| WAS3-2
|
WAI-ATM25-12P
| 12-port ATM 25 port adapters with 96-pin telco cable
| WAS3-2
|
WAI-T3-2BNC
| 2-port DS-3 port adapters
| WAS1-1
|
WAI-E3-2BNC
| 2-port E3 port adapters
| WAS1-1
|
WAI-T3-4BNC
| 4-port DS-3 port adapters
| WAS3-1
|
WAI-E3-4BNC
| 4-port E3 port adapters
| WAS3-3
|
WAI-T1-4RJ48
| 4-port T1 (ATM) with RJ-48 interface port adapters
| WAS3-1
|
WAI-E1-4RJ48
| 4-port E1 (ATM) with RJ-48 interface port adapters
| WAS3-1
|
WAI-E1-4BNC
| 4-port E1 (ATM) with BNC interface port adapters
| WAS3-1
|
WAI-T1C-4RJ48
| 4-port T1 (circuit emulation) with RJ-48 interface port adapters
| WAS3-1
|
WAI-E1C-4RJ48
| 4-port E1 (circuit emulation) with RJ-48 interface port adapters
| WAS3-1
|
WAI-E1C-4BNC
| 4-port E1 (circuit emulation) with BNC interface port adapters
| WAS3-1
|
L1010-ASP-B-FC1
| 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
|
To determine the version of Cisco IOS software currently running on the LightStream 1010 ATM switch, log in to the switch and use the show version EXEC command. The second line in the following sample output from the show version command indicates the version number:
Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.
The Cisco IOS software is packaged in feature sets, or software images, that vary according to the platform. Table 3 lists the Cisco IOS software feature sets available for the LightStream 1010 ATM switch in Cisco IOS Release 12.0(7), along with those features supported in previous releases.
Table 3: Feature Sets Supported by the LightStream 1010 ATM switch
| Feature Set
| 12.0(7)
| 12.0(6)
| 12.0(5)
| 12.0(4)
| 12.0(2a)
| 11.3(3a)WA4(6)
|
|---|
Left-justified E.164 AFI support
| x
| x
| x
| x
| x
| x
|
SNMP1
| x
| x
| x
| x
| x
| x
|
Asynchronous support
| x
| x
| x
| x
| x
| x
|
PPP2 (SLIP3/PPP)
| x
| x
| x
| x
| x
| x
|
IP4
| x
| x
| x
| x
| x
| x
|
NTP5
| x
| x
| x
| x
| x
| x
|
TACACS+6
| x
| x
| x
| x
| x
| x
|
Telnet
| x
| x
| x
| x
| x
| x
|
Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8
| x
| x
| x
| x
| x
| x
|
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.0)
| x
| x
| x
| x
| x
| x
|
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)
| x
| x
| x
| x
| x
| x
|
Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)
| x
| x
| x
| x
| x
| x
|
Multipoint-to-point UNI signaling
| x
| x
| x
| x
| x
| x
|
Soft VCCs and VPCs
| x
| x
| x
| x
| x
| x
|
VP tunneling
| x
| x
| x
| x
| x
| x
|
VPI/VCI range support in ILMI 4.0
| x
| x
| x
| x
| x
| x
|
PNNI hierarchy
| x
| x
| x
| x
| x
| x
|
ILMI version 4.0
| x
| x
| x
| x
| x
| x
|
IISP9
| x
| x
| x
| x
| x
| x
|
LANE10 client (LEC11) and LANE Services (LES12/BUS13/LECS14) on ASP15
| x
| x
| x
| x
| x
| x
|
Token Ring LANE services
| x
| x
| x
| x
| x
| x
|
ATM ARP16 server on ASP
| x
| x
| x
| x
| x
| x
|
ATM ARP client on ASP
| x
| x
| x
| x
| x
| x
|
ATM tag switch router (TSR)
| x
| x
| x
| x
| x
| x
|
Port snooping
| x
| x
| x
| x
| x
| x
|
OAM17 F4 and F5
| x
| x
| x
| x
| x
| x
|
E.164 address translation
| x
| x
| x
| x
| x
| x
|
E.164 autoconversion
| x
| x
| x
| x
| x
| x
|
Circuit emulation
| x
| x
| x
| x
| x
| x
|
ATM access lists
| x
| x
| x
| x
| x
| x
|
ATM accounting
| x
| x
| x
| x
| x
| x
|
ATM RMON18
| x
| x
| x
| x
| x
| x
|
Multiple, weighted, dynamic thresholds for selective packet marking and discard
| x
| x
| x
| x
| x
| x
|
Shaped VP tunnels for CBR traffic (FC-PFQ only)
| x
| x
| x
| x
| x
| x
|
Substitution of other service categories in shaped VP tunnels (FC-PFQ feature cards only)
| x
| x
| x
| x
| x
| x
|
Dual leaky bucket policing (FC-PFQ feature cards only)
| x
| x
| x
| x
| x
| x
|
Scheduler/Service Class/PVC configuration for FC-PFQ feature cards
| x
| x
| x
| x
| x
| x
|
Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC) (FC-PFQ feature cards only)
| x
| x
| x
| x
| x
| x
|
Network clocking enhancements for smooth switchover (FC-PFQ feature cards only)
| x
| x
| x
| x
| x
| x
|
Per-VC or per-VP nondisruptive snooping (FC-PFQ feature cards only)
| x
| x
| x
| x
| x
| x
|
Support for non-zero MCR19 on ABR connections (FC-PFQ feature cards only)
| x
| x
| x
| x
| x
| x
|
Access lists on ILMI registration
| x
| x
| x
| x
| x
| x
|
CUGs
| x
| x
| x
| x
| x
| x
|
ATM soft restart
| x
| x
| x
| x
| x
| x
|
ATM accounting enhancements
| x
| x
| x
| x
| x
| x
|
CISCO-SYSLOG-MIB support
| x
| x
| x
| x
| x
| x
|
CISCO-CONFIG-COPY-MIB support
| x
| x
| x
| x
| x
| x
|
Signaling diagnostics and MIB
| x
| x
| x
| x
| x
| x
|
Supplemental AToM MIB
| x
| x
| x
| x
| x
| x
|
This section contains information about new features that appear in this and previous releases of Cisco IOS Release 12.0 and 11.3.
There are no new features in these releases.
The following features have been added to the LightStream 1010 ATM switch software:
- Symptom: In some cases time-division multiplexing (TDM) VCs get stuck because of excessive errors. The fix detects stuck VCs and restarts them automatically.
- Workaround: The fix detects stuck VCs and restarts them automatically.
- Symptom: On a system with an FC-PFQ, hot swapping a FR-ATM port adapter, setting the serial port on the controller, and enabling encapsulation on the Frame Relay interface via the encapsulation frame-relay ietf command might cause the system to hang and display the following error message:
FRPAM4CE1: Port Configuration returned Error
- Workaround: Reload the system.
- Symptom: A CES soft PVC compatibility problem might exist between Cisco and Fore systems which might cause a problem with the Call Setup format and the Call Connect format.
- Workaround: None.
- Symptom: When the system sends a SETUP to establish an RCC connection between the two Peer Group Leaders (PGLs), the Fore switch sends a CONNECT message back. The Cisco switch might not accept this message. If it does not, the system generates the following error messages:
1d00h: ATMSIG (0/0/0:0 0,182 - 8726/00): (vcnum:0) Connect Illegal parameters in ATM Traffic Descriptor IE.
1d00h: ATMSIG: mandatory IE with invalid content in Connect msg and the connection between the two PGLs is not established.
- The PNNI standard does not allow the use of the ATM traffic descriptor IE in the CONNECT message for RCC connections.
- Workaround: None.
- Symptom: After reloading the system, OC-3c and OC-12c connections come up without a problem. When a new module is inserted after the reload, the system recognizes the module. The modules appear in the output from the show hardware command and the show running config command; however, none of the ports send out any information. The input cell count increments, but the output cell count does not.
- Workaround: None.
- Symptom: Soft VCs showing incorrect SoftVCLs and SVCLs might not connect to certain ports.
- Workaround: None.
- Symptom: LightStream 1010 systems with the FC1 card installed might crash intermittently during boot.
- Workaround: None
- Symptom: Systems with customer equipment that require a PVP value of 0 might cause the PVP tunnel to fail on the LightStream 1010 side of the network.
- Workaround: Change the PVP value to a non-zero number.
- Symptom: If the show atm vc interface command results in a status of NO HW RESOURCE for the interface, a failure might occur in mmc_close_conn.
- Workaround: None.
- Symptom: In certain instances SSCOP might ask the remote site to resynchronize its values so that both sides agree on the current status of these values. This request is likely in a redundant hardware failover. The system recognizes the request, but sends back a response message with a UNI 3.0 format rather than a UNI 3.1 format, so the remote side cannot recognize the response.
- Workaround: None.
- Symptom: Tag switching on the atm trunk works, but if the same link becomes a part of the inverse multiplexing for ATM (IMA) group, tag switching might not work as expected.
- Workaround: None.
- Symptom: Clocking might not work with certain slots on ASP 6.0 systems.
- Workaround: None.
- Symptom: When data is being converted from bits per second to cells per second, numbers might be rounded down when they should be rounded up.
- Workaround: None.
- Symptom: A system running Cisco IOS Release 11.3(5)WA4(5) or WA5(5) might report the following error message:
LINK-3-BADMACREG: non-existent MACADDR registry for link 49
- This message might occur when the system receives an LLC2 broadcast on a LANE subinterface. In come cases, the system might crash after reporting this error message.
- Workaround: Use a separate management ELAN or use a built-in Ethernet port to manage the switch.
- Symptom: When using a 25-Mbps port adapter, the number of leaves in a point-to-multipoint connection cannot exceed 32.
- Workaround: None.
- Symptom: CES E1 PAM might fail to stop sending REMAIS yellow alarms when OOF appears for a short period.
- Workaround: None.
- Symptom: When running tag switching, no tag is created for the default route.
- Workaround: None.
- Symptom: When using the atm pnni node 1 command, the peer group leader election (PGLE) might stay in the hung state for a long time.
- Workaround: None.
- Symptom: The system might crash with a bus error exception when attempting an atm ping command on a VC if the VC has been removed via a link failure.
- Workaround: None.
- Symptom: A PNNI process is terminated when the associated node is either disabled or removed. Following process termination, PNNI might not clean up and release some of its data structures properly. As a result of not freeing the data structures, the associated memory is lost until the next reload.
- Workaround: None.
- Symptom: The SNMP agent might not be able to discover and allow PNNI-related configurations on ATM subinterfaces. An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.
- Workaround: None.
- Symptom: Connections, where end-to-end delay IE is included in the CONNECT message, might fail. Examples of these connections include UNI40, CBR, UBR-rt.
- A LightStream 1010 ATM switch that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
- Workaround: None.
- Symptom: Due to an infinite loop, a LightStream 1010 ATM switch with eight LAN emulation clients configured on the CPU and 300 point-to-point and 60 point-to-multipoint connections might crash unexpectedly at the find-buddy function.
- Workaround: None.
- Symptom: After hot swapping an OC-12 SM port adapter with an OC-12 MM port adapter the output of the show controller command might incorrectly show the module as OC-12 SM. The module itself works.
- Workaround: None.
- Symptom: CES: per-vc queues might fill with cells on 64Kbps circuits.
- With standard CES 64Kbps circuits, the per-VC queues build up with cells at a rate of about one per second. There is a mismatch between the cell-rate requested and the rate granted. This is caused by signaling a pcr of 170 cells/second, rather than the desired 172 cells/second. Because the CBR FC-PFQ traffic shaping in current software has excellent granularity, roughly a cell every two seconds is queued. After the queue fills, dropping occurs at that rate.
- Workaround: None.
- Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) might not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
- Workaround: None.
- Symptom: CES interfaces might not come up upon reload.
- The line state stays at
XmtAIS LossOfSignal. Sometimes the switch comes up, but the IF status of show ces int command always shows as DOWN and the line state is RcvAIS XmtAIS.
- Workaround: None.
- Symptom: Crash with software release 11-3-3aWA4-6.
- Data flowing over OC12 links between two LightStream 1010 ATM switches might cause memory corruption and the software release 11-3-3aWA4-6 might crash. This crash might be caused by badly formed AAL5 packets.
- Workaround: Reboot the switch.
- Symptom: The snmp get command does not work for the following MIB variables:
- dsx1LineIndex
- dsx1TimeElapsed
- dsx1ValidIntervals
- dsx1LineType
- dsx1LineCoding
- dsx1SendCode
- dsx1CircuitIdentifier
- dsx1LoopbackConfig
- dsx1LineStatus
- dsx1SignalMode
- dsx1TransmitClockSource
- Workaround: None.
- Symptom: The power-on diagnostic test might indicate snake-test failures from the ASP-PFQ.
- If the snake test fails or the switch is not reset, the red LED on the left side of the processor remains lit. Changing out power supplies and processors does not correct this problem. Consequently, there is no evidence that this alarm indicates a failed processor.
- Workaround: None
- Symptom: Crash in process_handle_watchdog might occur.
- This problem is caused by a routing loop, which is caused by metric overflow in metric aggregation.
- Workaround: None.
- Symptom: The PNNI agent returns a value of
lowestLevelOutsideLink(4) for links between nodes on the same peer group for the pnniLinkType object. The correct value is lowestLevelHorizontalLink(2).
- Workaround: None.
- Symptom: PNNI: There might be a crash at compare_avl_nodes.
- When using the pnni_election command with a freed pnni_pdb where there are two scripts running pnni commands from different threads, the CLI command creates the pnni node and passes the pnni_pdb in the csb to be processed by the next issued command. In the meantime SNMP deletes the node from under CLI.
- Workaround: None.
- Symptom: After manually configuring all the prefix and ESI addresses for LECS/LES/BUS and clients for all devices on the network and upgrading from 11.2(8.0.1) FWA4(1) to 11.3(3a)WA4.6, the LANE client on the system might not join.
- Workaround: After removing the manually configured address, the LANE client comes right up.
- Symptom: ADD Party over Tunnel might not work.
- On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
- Workaround: None.
- Symptom: Left-justified AESA feature can cause the system to crash when enabling and disabling a node with 3000 e164/f69/X121 addresses.
- Workaround: None.
- Symptom: The ATM switch might crash if you remove a snooped subinterface by entering the no interface command and then entering the show atm snoop-vc command on the snoop interface.
- Workaround: None.
- Symptom: When a LEC/LES/BUS are all on the same switch, a point-to-multipoint connection exists with the CPU as root and with several leaves on the CPU. When the LES sends a packet to all leaves, one packet needs to loop back to the CPU for the LEC. The code that performs loopback initializes hwidb->atm_db->fast_vc_info for the LANE client and eventually calls atm_input to queue the packet. However, another packet could come in on the same CPU port (for example, PNNI). This situation would cause hwidb->atm_db->fast_vc_info to be overwritten because hwidb is shared. When interrupt handling is complete for the new packet, the old packet might be misinterpreted as a totally different kind of packet.
- Workaround: None.
- Symptom: Per VC Snooping is unconfigurable or broken.
- Workaround: None.
- Symptom: When a large amount of data is sent out of the Ethernet interface, the interface might become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
- The interface stops sending data and the transmitter remains stuck until a shut/no shut command sequence is issued on the interface.
- Workaround: Issue a shut/no shut command sequence on the interface.
- Symptom: One soft-vc might not come up because the resources at the destination switch aren't available. After retrying the soft-vc several times, the system might crash because of memory corruption.
- Workaround: None.
- Symptom: You cannot use SNMP to create a soft PVC on the ATM switch.
- Workaround: None.
- Symptom: A ring-back tone cannot be heard from the other side of a PBX when on-hook-detect is set.
- Workaround: None.
- Symptom: When using more than 13 time slots with cas on-hook, the voice CBR connections might be unstable. Without on-hook-detect configuration, all CBR VCs will be stable.
- Workaround: None.
- Symptom: ILMI might not come up upon reload of vp-mux (vuni).
- ILMI on the tunnel interface (connected to the far-end peer device through a vp-mux switch and virtual UNI) has trouble staying in "WaitDevType" after reloading the vp-mux switch.
- Workaround: Shut down the tunnel interface; disable the ILMI followed by the no shut command on the tunnel interface. After the interface settles down, the ILMI on the tunnel can be reenabled. Shut the interface. Use the atm ilmi-enable command and atm auto-configuration command (if desired), then reenable the tunnel interface with the no shut command.
- Symptom: Some LANE clients cannot join an ELAN.
- The show lane command indicates that some LANE clients (still in init state as far as the LANE client router is concerned) appear in the LECS table with no information.
- The show atm vc interface command indicates that some SVCs are not connected.
- If the LANE clients try to join the ELAN, they are rejected.
- Workaround: None.
- Symptom: Funnel VCs might jeopardize quality of service (QoS) for services.
- The current multipoint-to-point funnel implementation might compromise the QOS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
- Workaround: None.
- Symptom: A LightStream 1010 switch installed in the Catalyst 5500 chassis might fail to boot up when using mixed power supplies at high temperatures.
- When using power supplies from different vendors on the Catalyst 5500 chassis, make sure that the supplies are powered-up in serial order. If you power up the power supplies simultaneously, the processor on the LightStream 1010 ATM switch might not come out of reset. For example, the processor might hang and not boot.
- Workaround: None.
- Symptom: PNNI support of left-justified E.164 AESA addresses is not available in Cisco IOS Release 11.3 (0.8)TWA4(2).
- Workaround: None.
- Symptom: Unless it is administratively shut down, the CBR interface on the CES port adapter is always in the up/up state, even when no cable is attached. If the CBR line goes down, the interface stays up/up, and the only error reported is Linestate: LossOfSignal.
- Workaround: None.
- Symptom: When the ROM monitor environment variable boot is set to a nonexistent file (using the Cisco IOS boot system flash command) and the configuration register is set to 0x2102 (autoboot), the switch might hang during the subsequent reload command issued by the software.
- Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
- Symptom: A CES PVC cannot be cross connected to a VP tunnel interface.
- Workaround: None.
- Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmitted to the scheduled rate. This might cause cells to be dropped in the WAN. Any dropping must be done prior to multiplexing onto the VP, so that a packet discard can be performed.
- Workaround: Refer to the information in the DDTs for information on how to make a conversion of a requested rate to the actual rate.
- Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
- Workaround: None.
- Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
- Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up most of the time. If the clear ip route command does not work, enter a shut/no shut command on the UNI interfaces of the switch on which the physical interface was shut to bring everything back up.
- Symptom: CPU hog condition might occur while setting up a lot of calls.
- Workaround: None.
- Symptom: IP host-routing might not disable when specified.
- Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
- Symptom: Shutting down an interface with more than 1000 tag switching VCs might cause a CPU HOG occurrence for the EXEC process. The CPUHOG occurrence does not impact the functionality of the ATM switch.
- Workaround: None
- Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
- Workaround: Reboot the switch.
- Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
- Workaround: None.
- Symptom: The following error might occur after copying the running configuration to a TFTP server and then trying to unconfigure all of the interface addresses:
SYMBOLS::::::::::::::
:/home/aks>/usr/local/bin/rsym ls1010-wp-mz.113-0.8.TWA4.1.21.symbols
Reading ls1010-wp-mz.113-0.8.TWA4.1.21.symbols
ls1010-wp-mz.113-0.8.TWA4.1.21.symbols read in
Enter hex value: 60089678 6008A6D4 6014B518 601731D0 601463F8 60146C0C 6014B68C
6014BA2C 6007EED8 6007EEC4
0x60089678:mgd_timer_complain_uninit(0x6008964c)+0x2c
0x6008A6D4:mgd_timer_stop(0x6008a694)+0x40
0x6014B518:tcp_stoptimer(0x6014b4b4)+0x64
0x601731D0:ipv4_tcp_write(0x60172f00)+0x2d0
0x601463F8:tcp_sendip(0x60146370)+0x88
0x60146C0C:tcp_retransmit(0x60146848)+0x3c4
0x6014B68C:tcp_timeout(0x6014b5c8)+0xc4
0x6014BA2C:tcp_timer(0x6014b9b8)+0x74
0x6007EED8:r4k_process_dispatch(0x6007eec4)+0x14
0x6007EEC4:r4k_process_dispatch(0x6007eec4)+0x0
- Workaround: None.
- Symptom: If there are multiple parallel paths to the same destination on a LightStream 1010 with a FC-PFQ feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of four parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
- Workaround: None.
- Symptom: The system does not support CUGs on soft PVC connections. For example, if you define a set of access policies and a CUG on an interface with the PVC leg of a soft PVC call, the CUG parameters do not apply to those calls.
- Workaround: None.
- Symptom: In a LightStream 1010 ATM switch equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
- Workaround: None.
- Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
- Workaround: None.
- Symptom: The fail over time for the circuit emulation switch (CES) soft VC on a redundant link might be inconsistent, from less than 1 second up to 15 seconds.
- Workaround: None.
- Symptom: Cell loss might occur while hot swapping a power supply.
- Workaround: None.
- Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
- Workaround: None.
- Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. Because of this, the configuration of an ABR VP tunnel subinterface is prevented.
- Workaround: None.
- Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
- Workaround: None.
- Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (by way of portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
- Workaround: None.
- Symptom: If you disable Cisco Discovery Protocol (CDP) on the 2/0/0.x interface and it is configured as a LEC, the information is not saved to NVRAM when you enter the copy running-config startup-config command. CDP is disabled in the running configuration, but it is reenabled after a system reload.
- Workaround: None.
- Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might cause a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
- Workaround: None.
- Symptom: When one of the installed power supplies is powered off, and you are copying an image to bootflash, a power supply failure message might appear.
- Workaround: None.
- Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
- VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).
- ABR, UBR: no bandwidth is allocated.
- Workaround: None.
- Symptom: A Lan Emulation Configuration Server (LECS), using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS to validate clients.
- If different Emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LES(s) multiplex the control messages (which validate the clients) into a single VC.
- For example, see the following LES router configuration:
atm1/0.1 sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2 sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3 sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4 sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of a LECS sends the following warning messages to the console stating that a LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan
'sysa_70k_31_a1.3_LAN'
- The clients are still allowed to join the ELAN. Disregard the warning message.
- Workaround: None.
- Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system might run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
- In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
- Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
- Symptom: The receiver circuitry on DS3 port adapters might interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
- Workaround: None.
- Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures.
- Workaround: This should clear after the traffic congestion clears.
- Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
- This message indicates that the release process runs for a long time before returning control to the kernel, which might then schedule other tasks. This process does not affect normal operation of the switch.
- Workaround: None.
- Symptom: E3 port adapters are limited to 65535 cells per second per PVC regardless of the framing type. There is no benefit from G832 framing.
- Workaround: None
- Symptom: When a fault condition occurs on an interface on an intermediate switch, Alarm Indication Signal (AIS) cells are generated. In response, the endpoint sends Remote Identification (RDI) cells. In some cases, these RDI cells are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when the fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
- Workaround: None.
The following sections describe documentation available for the LightStream 1010 ATM switch. Both printed manuals and electronic documents are available.
The most current documentation can be found on Cisco Connection Online (CCO) under the "Technical Assistance Center" section and on the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.
Use these release notes with the documents listed in this section.
Following is a list of the software documentation available for the LightStream 1010 ATM switch:
- LightStream 1010 ATM Switch Command Reference
- LightStream 1010 ATM Switch Software Configuration Guide
- LightStream 1010 ATM Switch Troubleshooting Guide
Following is a list of the hardware documentation available for the LightStream 1010 ATM switch:
- LightStream 1010 ATM Switch Hardware Installation Guide
- LightStream 1010 ATM Switch ASP Installation Guide
- LightStream 1010 ATM Switch PAM Installation Guide
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.
Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.
For service and support for a product purchased directly from Cisco, use CCO.
For helpful tips on configuring Cisco products, follow this path on CCO:
Service & Support: Technical Assistance Center
"Software Technical Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 650-556-8409.
In addition to "Software Technical Tips," the following sections are on the Technical Documents page:
- Cisco Product Catalog—MultiNet & Cisco Suite 100, Network Management, Cisco IOS Software Bulletins, CiscoPro Configurations.
- Field Notices—Notification of critical issues regarding Cisco products. These include problem descriptions, safety or security issues, and hardware defects.
- Hardware Technical Tips—Technical tips related to specific hardware platforms.
- Hot Tips—Popular tips and hints for a range of product suites. Gathered from Cisco's Technical Assistance Center (TAC).
- Internetworking Technical Tips—Tips for using and deploying Cisco IOS software features and services.
- Sample Configurations—Actual configuration examples complete with topology and annotations.
- Special Collections—Other helpful documents: Frequently Asked Questions, Security Advisories, References & RFCs, Case Studies, CiscoPro Documentation CD-ROM.
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:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
