Table Of Contents
Cisco ONS 15454 Release 2.3.4 Maintenance Issue Resolutions
Compatibility with Previous Versions
Product Bulletin No. 2126
Cisco ONS 15454 SONET Multiservice Provisioning Platform System Software Release 2.3.4
Release 2.3.4 is a maintenance release designed to further enhance the R2.x.x code base. This upgrade is recommended for any users presently operating software releases 2.3.3 and earlier.
Cisco ONS 15454 Release 2.3.4 Maintenance Issue Resolutions
The Cisco® ONS 15454 solution is deployed in a wide variety of customer networks in multiple applications. Customer feedback and the Cisco testing group help identify areas of improvement, which ultimately drives the constant evolution of the product and its functions. Cisco ONS 15454 Release 2.3.4 software is designed to further strengthen the overall software code base through the resolution of the following notable system anomalies.
Users operating any of the Cisco ONS 15454 Release 2.x.x software loads are encouraged to upgrade to this new software maintenance release.
Notable Resolved Issues
DDTS Number CSCdw48828
If a near-end protection switch is initiated within 30 seconds of a TCC switch, traffic will be lost. Traffic is restored by forcing traffic away from the active span and then releasing the force. To avoid this issue, lock the spans on the neighboring nodes before doing the TCC reset or reseat. This will prevent an outage as long as all spans remain intact. This issue is resolved in Releases 2.3.4, 3.2.1, and later.
DDTS Number CSCdy31096
A TCC memory corruption can occur when either of the following occurs:
•
A user logs into the VxWorks shell with a Telnet client that sends only \r (for example, no \n) after entering the password.
•
If the former occurs, the TCC may reset after closing the Telnet session. If the latter occurs, the TCC will typically reset immediately. To avoid this issue, do not use the VxWorks Telnet interface if your Telnet client does not send \r\n to terminate lines. Also, do not type more than 512 characters at the login prompt. This issue is resolved in Releases 2.3.4, 3.4, and later.
DDTS Number CSCdv44748
After resetting or replacing the standby TCC, the standby TCC may change to the READY state (standby light illuminates indicating the TCC is ready to become active) before database synchronization has necessarily taken place. A TCC switch before database synchronization can result in partial or complete provisioning loss. This issue is resolved in Release 2.3.4.
DDTS Number CSCdz18060
Rarely, the standby TCC may fail to copy the database from the active TCC after a provisioning change. This may occur due to heavy load on the node at the time of transfer. If this occurs, the database on the standby TCC will be out of sync with the database on the active TCC. To correct this situation, make a provisioning change that will have no service-affecting implications (for example, a change to contact information, or a description) to force another database save. This issue is resolved in Release 2.3.4, Release 3.4.1, and later. Please look to release notes for additional detail.
DDTS Number CSCea03171
TCC memory exhaustion (the MEM-LOW or MEM-GONE alarm will be raised) can lead to unpredictable behavior. This issue has been resolved in Release 2.3.4 (and Release 5.0 and later) by increasing the threshold at which the memory-related alarms are raised. Also, an automatic TCC reset will occur when memory reaches 180 KB in Release 2.3.4 (and Release 5.0 and later).
DDTS Number CSCdu49768 and CSCdu34969
When you reseat an active TCC, if a near-end protection switch is initiated within 30 seconds of the TCC switch, traffic will be lost. Traffic is restored by forcing traffic away from the active span and then releasing the force. To avoid this issue, lock the spans on the neighboring nodes before performing the TCC reset or reseat. This will prevent an outage as long as all spans remain intact. This issue is resolved in Releases 2.3.4, 3.2.1, and later.
DDTS Number CSCdy47156
A memory leak can occur after bulk PM retrieval. The only application that is likely to trigger this issue is the Cisco Transport Manager. Although the memory leak is small, Cisco Transport Manager gathers PM data every 15 minutes, so the amount of memory lost grows over time, and thus can become more serious over time. To avoid this issue, do not use Cisco Transport Manager to gather PM data. This issue is resolved in Release 2.3.4.
DDTS Number CSCdy53297
Logging into TL1 generates a minor memory leak (32 bytes). This issue is resolved in Release 2.3.4.
For additional details regarding R2.3.4 resolutions, consult the Release Notes (Release 2.3.4) posted to the Cisco Web site at the following URL:
http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_release_notes_list.html
Compatibility with Previous Versions
The Cisco ONS 15454 R2.3.4 software requires the use of either the TCC or TCC+ timing, communications and control processor cards. Cisco ONS 15454 common control and interface cards released before R2.2.0 are compatible with this software load. Before inserting a new node into an operating ring or linear network, all existing Cisco ONS 15454 nodes connected via optical SDCC interfaces should be upgraded to a consistent level of system software to ensure proper operation.
Availability
The Cisco ONS 15454 Release 2.3.4 system software is orderable now with shipments beginning March 24, 2003. For customers with Cisco.com accounts, R2.3.4 is also available for download from the Cisco Software Center.
Ordering Information
The Cisco ONS 15454 Release 2.3.4 system can be ordered from your Cisco sales representative or through the Cisco online ordering tool. Specific product codes and descriptions are detailed below.
More Information
For more information about the Cisco ONS 15454, go to:
http://www.cisco.com/en/US/products/hw/optical/ps2006/index.html
To order Cisco equipment, visit: