|
|
March 24, 1997
LightStream 1010 ATM Release 11.2(2)WA3(1a)
This release notes describe the features and caveats for Cisco Internetwork Operating System (Cisco IOS) Release 11.2(2)WA3(1a) for the LightStream 1010 Asynchronous Transfer Mode (ATM) switch software. The LightStream 1010 ATM switch software is based on Cisco IOS Release 11.2(2). This release includes enhancements in support of the LightStream 1010 ATM switch.
This release note discusses the following topics:
The following features have been added to the LightStream 1010 ATM switch software:
The following new hardware is supported in the LightStream 1010 ATM switch release 11.2(2)WS3(1a):
The following clock selection changes listed in Table 1 apply to release 11.2(2)WA3(1a).
| Clock Mode | Release 11.1 | Release 11.2 |
|---|---|---|
Network Derived | Derives clock from the port selected as the network clock at the highest priority. This can be the ASP if all clocks are bad or there was no selection. | If no selection for network-clock-select has been made the clock defaults to the ASP (default). |
Free-running | Uses the ASP clock (default). | Uses the port Local oscillator on the PAM when available. |
Loop-timed | Uses the clock derived from the receive side. | Uses the clock derived from the receive side. |
In the 11.2 release, the default clock selected on any port was changed. The default mode is network-derived. If no port is selected as the source of the network clock, the default is the system clock supplied by the ASP. In the 11.1 release, if no clock source was specified for a port, the clock mode default was free-running, which was internally equivalent to selecting the system clock supplied by the ASP. The defaults are not saved in the configuration.
If you changed the default in 11.1 to network-derived, when upgrading to release 11.2, because network-derived is the default, the clock mode remains the same. However, if you move back to release 11.1 that port reverts to the free-running (with ASP) clock default configuration. If you want network-derived clock you must reconfigure the port.
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:
For electronic documentation of Release 11.2 ATM switch software features available on the Cisco Connection Documentation, Enterprise Series CD-ROM, refer to the LightStream 1010 ATM Switch Software Configuration Guide and LightStream 1010 ATM Switch Command Reference publications, which are located in the LightStream 1010 database under ATM Adapters and Switches database.
You can also access Cisco technical documentation on the World Wide Web: http://www.cisco.com.
This release supports the LightStream 1010 ATM switch.
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(2)WA3(1a) of the LightStream 1010 ATM switch software.
| Type | Feature |
|---|---|
Cisco IOS Base Features | SNMP |
Asynchronous support (RS232) | |
PPP (SLIP/PPP) | |
IP | |
NTP | |
TACACS+ | |
Telnet | |
ATM Features | Point-to-point and point-to-multipoint Permanent VCCs and VPCs |
Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.0) | |
Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 3.1) | |
Point-to-point and point-to-multipoint Switched VCCs and VPCs (UNI 4.0) | |
Soft VCCs and VPCs | |
VP Tunneling | |
PNNI version 1.0 | |
ILMI version 4.0 | |
IISP | |
LANE client (LEC) and LANE Services (LES/BUS/LECS) on ASP | |
ATM ARP server on ASP | |
ATM ARP client on ASP | |
Port snooping | |
OAM F4 and F5 | |
E.164 Address Translation | |
Circuit Emulation | |
ATM Access lists |
The system Dynamic Random Access Memory (DRAM) resides on a SIMM module on the ATM Switch Processor (ASP). The default DRAM configuration is 16 MB. The amount of DRAM required on the ASP module is determined by the number of active physical and logical ports (virtual path tunnels) and the expected number of active switched virtual channels (SVCs) through the switch.
Table 3 provides an approximate guide to use when determining the amount of DRAM required for a switch with 32 physical ports.
| SVCs Required | DRAM Required |
|---|---|
Less than 4000 active SVCs | 16 MB DRAM |
Between 4000 and 16,000 active SVCs | 32 MB DRAM |
Between 16,000 and 32,000 active SVCs | 64 MB DRAM |
This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the LightStream 1010 ATM switch for Release 11.2(2)WA3(1a).
The following features are not supported in this release even though the commands may be visible in the command line interface.
The following caveats have been identified for this release of the LightStream 1010 ATM switch software.
When ATM Signaling Error debugging is enabled, the following debug message might occur:
ATMSIG: incoming msg has invalid protocol discriminator 0
This message indicates that SSCOP passed a PDU to Signaling that is not recognized as a valid message. The message might occur when heavy signaling loads occur between the switch and other Cisco Systems routers. No failure of function results from this.
[CSCdi72727]
When a reload is performed, the following message may appear.
%ALIGN-3-SPURIOUS: Spurious memory access made at 0x600D2EBC reading 0x0
This caveat does not affect the operation of the switch.
[CSCdi74298]
Under heavy loads the following message appears on the console.
incoming pak size 16 does not match embedded msg size
This caveat does not affect the operation of the switch.
[CSCdi76330]
Address registration sometimes fails when the peer interface is quickly toggled. To fix this problem, remove the address from the peer and reestablish the connection.
[CSCdi79797]
Due to sensitive Receiver circuitry, noise may be interpreted as a valid signal. This condition causes the E3 controller to interpret the condition as a bad signal turning some RX LEDs red.
[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 will appear on the console:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
The system continues to function, in most instances but, on few occasions, it may stop accepting any more calls from the end systems.
To workaround this problem, in case the system could not bring up more calls, toggling the interface will help to reinitialize all the connections and bring the system back to working condition.
[CSCdi83275]
When there is no Calling Party Address in the AddParty ATM Signaling message, the AddParty fails on the first attempt. Adding the Calling Party Address in the AddParty message eliminates this problem.
[CSCdi83567]
Logical multicasting is not supported in the present LS1010 release.
[CSCdi85540]
Under heavy LANE control traffic, when many clients are brought up and down, some of the clients might become stuck in an indeterminate state. To work around this problem, either toggle the interface on which it is defined or deconfigure/reconfigure the specific LEC.
[CSCdi85598]
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]
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]
When different ELANs are configured on multiple ASP subinterfaces, then all LESs multiplex the control messages, which validate the clients into a single VC. The LECS sends a warning message to the console even though the clients are allowed to join the ELAN.
[CSCdi92142]
The following message may occasionally be displayed on the console:
"%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs".
No failure of function results from this.
[CSCdi92280]
Automatic summarization is ineffective after the following command sequence.
Switch# configure terminal
Switch(config)# atm router pnni
Switch(config-atm-router)# node 1 disable
Switch(config-atm-router)# node 1 enable
As a result, the end system addresses are not automatically summarized using the 13-byte prefixes derived from the switch address. Use the following command sequence, which turns automatic summarization off and on, to correct this problem.
Switch# configure terminal
Switch(config)# atm router pnni
Switch(config-atm-router)# node 1
Switch(config-atm-router)# no auto-summary
Switch(config-atm-router)# auto-summary [CSCdj00300]
The LEC becomes stuck in the waitingListen and the lecsConnect states and the ASP subinterface becomes stuck in waitingIlmi state. To bring the system back to initial state, use the shut/no shut command. Also, some of the clients might stick in the waitingIlmi state.
[CSCdj00646]
You can create VBR, ABR, and UBR VCs across the switch with PCR values greater than interface line rate. Currently, the actual allocated bandwidth is as follows:
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 causes a power-supply failure message when there are two power supplies and the problem occurs only when one of the installed power supplies is turned off. Normally both power supplies are turned on for redundancy.
[CSCdj01757]
When building the Broadband Low Layer Information (BLLI) Element in an ATM Signaling message, per information provided by a client, the length of the contents of the information to insert into the BLLI are not checked for accuracy. Currently no client is known to provide an inaccurate length parameter, but you should check to avoid a severe problem if this situation should occur.
[CSCdj03169]
If a T1/E1 port is configured as the clock source for the system, and that port receives transitions in link status that affect the clock, other interfaces that derive their clock from that clock source may go down for a moment. This situation only occurs when transitions are less than 3 seconds.
[CSCdj03281]
When LES/BUS and LECS are both configured on the same LightStream1010 CPU port, the LECS will not be able to distinguish the LES from an LEC.
This can cause the following symptoms:
1. The show lane configuration command will show the LES as if it were an LEC.
2. If a only a single LES is configured on the ELAN, then it will still function. However, if a second LES is configured on the same ELAN for the purpose of redundancy (SSRP), it will not function correctly.
1. Do no configure any LES/BUSs on the same LightStream 1010 CPU port as the LECS is configured.
2. Or, use only a single LES/BUS on the ELAN.
[CSCdj04377]
For a OC3 UTP5 PAM, when physical port type is requested from SNMP, the port type field returns "other."
[CSCdj04393]
ILMI auto-configuration 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.
Switch(config-if)# no atm auto-configuration
Switch(config-if)# atm uni version 4.0. [CSCdj04489]
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.
|
|