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

After a software upgrade from Release 3.3 to 3.4, where a Lockout Protect Span is issued on all nodes 
before activation (as it should be), the lockout conditions may persist even after clearing them in CTC. 
To correct this situation, reissue each lockout and then clear it again. This issue is resolved in Release 
4.0.

If you upgrade one of the rings in a two by two BLSR configuration, an EXTRA-TRAF-PREEMPT 
alarm may be raised and subsequently fail to clear on one of the rings. If the ring that has the stuck alarm 
already has some PCA circuits on it, you can issue and then clear a Force Ring. This should clear the 
stuck alarm. If no PCA circuits exist on the ring, then create one temporarily, and follow the above 
procedure to clear the alarm. After the alarm clears, you can remove the Force Ring, then delete the PCA 
circuit. This issue is resolved in Release 4.0.

After a BLSR span or ring switch, traffic is switched to a different set of nodes and a protection STS is 
used. At this point, any ongoing J1 monitoring does not follow the switch. As a result, there is no J1 
monitoring on the protection path. If there is a mismatch of the J1 string on the protection path, the 
TIM_P alarm will not be raised. Also, you can retrieve the actual captured J1 string on the working path, 
but if BLSR switched from working to protect, you cannot retrieve the J1 string on the protect path. This 
issue is resolved in Release 4.0.

In a 2 fiber BLSR, if there is a ring or span Wait to Restore (WTR), the Clear button in CTC will clear 
the WTR state and revert traffic to Working right away, while the TL1 RLS-PROTNSW command does 
not behave in this same manner. To get the WTR to clear immediately, you must use the CTC Clear 
button. This issue is resolved in Release 4.0.

In a four-node, OC-192, four fiber BLSR, traffic remains lost after a lockout is cleared on an adjacent 
node when the local node has an SF-R raised. To correct this problem if it occurs, issue a force ring on 
the side of the SF-R affected node that the SF-R is raised on. This issue is resolved in Release 4.0.

Under some conditions, a lockout-of-protect span condition might be raised (or fail to clear) upon 
creating a BLSR. If this occurs, issue a manual switch ring command, then check to see that the ring 
switched properly. Afterwards, clear the command. This issue is resolved in Release 4.0.

On a four-node, OC-192, four fiber BLSR, switching will not occur when an SD-R is present after 
clearing an SD-P. After clearing the SD-P, issue a force ring on the side of the SD-R affected node that 
the SD-R is reported against. This issue is resolved in Release 4.0.