Cisco Cisco ONS 15454 SDH Multiservice Provisioning Platform (MSPP)
3
Release Notes for Cisco ONS 15454 SDH Release 5.0.6
OL-8285-01
Changes to the Release Notes
Changes to the Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco ONS
15454 SDH Release 5.0.6 since the production of the Cisco ONS 15454 SDH System Software CD for
Release 5.0.6.
15454 SDH Release 5.0.6 since the production of the Cisco ONS 15454 SDH System Software CD for
Release 5.0.6.
The following changes have been added to the release notes for Release 5.0.6.
Changes to Caveats
The following caveat has been added.
Changes to Resolved Caveats
The following resolved caveat has been added.
Caveats
Review the notes listed below before deploying the ONS 15454 SDH. Caveats with bug database
tracking numbers are known system limitations that are scheduled to be addressed in a subsequent
release. Caveats without bug database tracking numbers are provided to point out procedural or
situational considerations when deploying the product.
tracking numbers are known system limitations that are scheduled to be addressed in a subsequent
release. Caveats without bug database tracking numbers are provided to point out procedural or
situational considerations when deploying the product.
Software Upgrades
CSCsc48391
When upgrading or reverting software on a node configured for Y cable protection with distance
extension turned on, Y cable protection switches might occur, causing Fibre channel/FICON link
reinitialization. No alarms will be present at the time of the switch. To avoid this issue ensure that a
lockout or lockon command is in place prior to the activation or revert. This issue is addressed in Release
7.0, which ensures that the traffic hit is removed in this configuration.
extension turned on, Y cable protection switches might occur, causing Fibre channel/FICON link
reinitialization. No alarms will be present at the time of the switch. To avoid this issue ensure that a
lockout or lockon command is in place prior to the activation or revert. This issue is addressed in Release
7.0, which ensures that the traffic hit is removed in this configuration.