Release Notes

Release Notes for Cisco ONS 15454 SDH Release 4.1.3

OL-4984-01

Caveats

Upgrades

DDTS # CSCec42769 Database Corruption with ONS 15454 SDH Release 4.0, 4.0.1, 4.1

Caution Before you upgrade to Release 4.1.3 from Release 4.0, 4.0.1, or 4.1, you must read this caveat and

run the SDH Circuit Repair Utility (VcCheck) provided on the software CD (also available on CCO).

The XCVXL card on the ONS 15454 SDH allows the intermixing of VC12 and VC3 payloads within a

single VC4. When a VC4 contains only one VC12 tributary and at least one VC3 tributary and the VC12

is deleted, the database becomes corrupt.

The database load process on the ONS 15454 SDH occurs during a TCC2 reboot, TCC2 protection

switch, software activation, or database restore. When the database is loaded containing this corruption

the load process fails, causing the corrupt database to be deleted from the TCC2 flash memory. The

previous saved database is then loaded instead. When all saved databases on a TCC2 contain the

corruption, the TCC2 will load with the default provisioning, and all existing provisioning will be lost.

If this issue occurs you will see a loss of either some or all provisioning after a TCC2 switch or reset.

To ensure that your network is not vulnerable to this issue, you must first determine if the issue already

exists within your network, and if so, correct it. You can detect the issue by using 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 CCO. Once you have alleviated immediate risk from

the issue, you must upgrade to Release 4.6, or maintenance Release 4.1.3 (or any later release) to avoid

further risk.

The VcCheck utility and its associated README file (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.

This issue is resolved in Release 4.6 and maintenance Release 4.1.3 (caveated herein because of the

upgrade issue).

Line Cards

DDTS # CSCec49231

In an LMSP 1+1 configuration, followint an XCVXL reset, The HP-PLM alarm might become stuck.

The following steps will reproduce this issue.

Step 1 Create a circuit from and to DS3i-N-12 cards through an STM16 LMSP (1+1) in a two-node

configuration.

Step 2 Perform a LOCKOUT on the cross connect cards (XCVXL).

Step 3 Perform a hard reset on the active XCVXL cards.

Traffic goes down, then returns after the XCVXLs finish booting. The false HP-PLM alarms are now

present on the STM16 span card. Once the false HP-PLM alarms are detected; to remove the false

alarms, perform a TCC side switch. This issue will be resolved in a future release.