Cisco Cisco ONS 15454 SDH Multiservice Provisioning Platform (MSPP) Notas de publicación

Descargar
Página de 14
 
2
Release Notes for Cisco ONS 15454 SDH Release 8.5.4
OL-20571-01
  Changes to the Release Notes
Changes to the Release Notes
This section documents supplemental information that has been added to the Release Notes for 
Cisco ONS 15454 SDH Release 8.5.4
 since the production of the Cisco ONS 15454 SDH System 
Software CD for Release 8.5.4.
Caveats
Review the notes listed below before deploying Cisco ONS 15454 SDH. Caveats with tracking numbers 
are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without 
tracking numbers are provided to point out procedural or situational considerations when deploying the 
product.
Note
The use of 40WXC units is supported only in the networks running software Release 8.5.1 and later.
Alarms
This section documents caveats for Alarms in Release 8.5.4.
CSCsv30593—AIS-V alarm does not clear
The AIS-V alarm does not clear on VT1.5 cross connect circuits under the following conditions:
1.
Create a VT1.5 path protected circuit.
2.
Raise an SF-P alarm by injecting path errors.
3.
AIS-V alarm is raised on the VT1.5 circuit.
4.
Change the circuit state from IS to OOS-MT or OOS-DSBLD.
5.
Change the circuit state back to IS.
6.
Clear the SF-P alarm, the AIS-V alarm does not clear.
The workaround is to soft reset the cross connect card. This issue will be resolved in a future release.
CSCsv30867—The alarms do not clear after cross-connect side switch
When any VT level alarms are raised, a cross-connect side switch is performed to eliminate the alarm. 
The alarms do not clear after cross-connect side switch. The workaround is to reset the cross-connect 
card to clear the alarm. This issue will be resolved in a future release.
CSCsw98487—PROV-MISMATCH alarm is not raised when client port is in Unlocked state
The PROV-MISMATCH alarm is not raised and cleared when the client port provisioned with DVB-ASI 
or ISC-1 in the TXP_MR_2.5G card when the card is in Unlocked state. This issue will be resolved in a 
future release.