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

UNEQ-V alarms are incorrectly raised prior to connecting a TAP to a TACC, and also after disconnecting 
the TAP from the TACC. This issue is resolved in Releases 4.1.2 and 4.6.

For any STS or VT circuit that terminates on a node, an AIS (path level) that raises and clears on that 
circuit's path may result in an inability of other path alarms to be cleared. This can also occur when a 
line-level alarm occurs on the circuit path's line, causing the OC-N to send AIS-path downstream on each 
path within the line. This issue is resolved in Release 4.1.

Retrieving a diagnostic file may cause a Standby or Active TCC2 reset. This is not traffic affecting. This 
issue is resolved in Release 4.1.

If you have PCA circuits over two-fiber or four-fiber MS-SPRing protect channels, an incorrect 
auto-inservice transition occurs after traffic preemption. You may place the circuit back into the 
OOS-AINS state after the BLSR has returned to the unswitched mode, using the Circuit Editing pane of 
the CTC. This issue is resolved in Release 4.1.

In a SNCP configuration, upon detecting a double-path failure with UNEQ-P, the UNEQ-P on the protect 
path is not reported. This issue is resolved in Release 4.1.2.

In a non-revertive SNCP configuration, when a double failure is detected on both paths with UNEQ-P 
or AIS-P, upon clearing the protect path defect, the UNEQ-P or AIS-P alarm may remain stuck on the 
working path for the node. The most reliable way to remove the alarm is a TCC2 side switch. This issue 
is resolved in Release 4.1.2.

This section highlights new features and functionality for Release 4.1.x. For detailed documentation of 
each of these features, consult the user documentation.