This release note describes the features and caveats for Cisco IOS Release 11.2(10)WA3(4) for the LightStream 1010 Asynchronous Transfer Mode (ATM) switch software. The LightStream 1010 ATM switch software is based on Cisco IOS Release 11.2(10). This release includes enhancements for the LightStream 1010 ATM switch.
System defaults to no clock The clock priority default has changed to "no clock". See the Modifications For Release 11.2(8)WA3(3) section on the next page.
The following new hardware is supported in the LightStream 1010 ATM switch, release 11.2(8)WA3(3):
4-port E3 PAM A four port E3 PAM with network clocking options.
See the section "Documentation" for a list of documents describing these 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):
Releases before this 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. If a clock at a priority is not configured that will be reflected by the "no clock" option. Decision on the which priority to use during clock switch over will skip priorities that are not configured.
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, 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.
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:
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.
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(10)WA3(4), 11.2(8)WA3(3), and 11.2(5)WA3(2b) of the LightStream 1010 ATM switch software.
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]
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]
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]
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]
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]
An 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]
Consider a scenario in which two LightStream 1010s 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]
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 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]
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:
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]
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]
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 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 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]
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, somewhere from less than a second up 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 sub-interface will always show as up. Even with configuring ILMI keepalives or using OAM cells, the sub-interface always stays up. Some other show commands will show 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:
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]
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.
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.
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]
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 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. [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. [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:
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]
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:
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.
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.
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.
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,productdocumentation, 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.
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.
