Document ID: 48509
February 4, 2004
ONS 15454 SDH with XC-VXL-10G or XC-VXL-2.5G
Releases 4.0, 4.0.1 and 4.1
The database can become corrupted on an ONS 15454 SDH with XC-VXL cards when provisioning VC12 tributary circuits.
The XC-VXL card on the ONS 15454 SDH allows the ability to groom VC12 tributary circuits. Under certain scenarios, creating and deleting VC12 circuits can cause the database to become corrupt. The database load process on the ONS 15454 SDH occurs during a TCC2 reboot, TCC2 protection switch, software activation, or database restore.
In Release 4.1, when a database is loaded containing this corruption, the load process fails, causing the corrupt database to be deleted from the TCC2 flash memory. In Release 4.0, either the above scenario occurs, or both TCC2s reboot indefinitely. If this issue occurs, you will see a loss of all provisioning after a TCC2 switch or reset.
To detect the issue on one Network Element (NE), or on a network, use the SDH Circuit Repair Utility (VcCheck) provided on the ONS 15454 SDH Release 4.1.3 and 4.6 software CDs. The VcCheck tool is also available for download from the Software Download Page (registered customers only) on Cisco.com. Before using the VcCheck tool, read the VcCheck README. Once you have alleviated the immediate risk from the issue, you must upgrade to Release 4.6, maintenance Release 4.1.3 or any later release to avoid further risk. The VcCheck utility and its associated README file, which is in the same directory with the tool, provide details on how to temporarily alleviate this issue before upgrading to a release in which the issue is resolved.
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
A hard reset of an active TCC2 causes the deletion of the node database.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
|Updated: Feb 10, 2004||Document ID: 48509|