Release Notes

21
Release Notes for Cisco ONS 15454 SDH Release 4.1.3
OL-4984-01
Caveats
To see this issue, on a node participating in a two fiber MS-SPRing with PCA circuits terminating at the
node over the two fiber MS-SPRing, cause an SF-R by failing the receive fiber in one direction (say,
west). Then issue a lockout span in the other direction (in our example, east). Since the lockout span has
higher priority than the SF-R, the ring switch should clear and PCA traffic should be restored on spans
without a fiber fault. The ring switch does clear, but PCA traffic does not restore. To correct this issue,
clear the fiber fault. All traffic restores properly. This issue will be resolved in a future release.
DDTS # CSCdw53481
Two MS-Rs are not allowed to coexist. If you execute a manual ring switch command on one side of an
MS-SPRing node and apply another manual ring switch command on other side of the node, the second
manual ring switch command is rejected. This works as designed. The implementation complies with
Telcordia GR-1230, R6-102.
DDTS # CSCdx45851
On a four fiber MS-SPRing, restoring the database for all nodes at the same time could cause VC4-16c
traffic to fail to switch. Do not restore the database for multiple nodes simultaneously. The proper
procedure for restoring the database for multiple nodes is to restore one node at a time. This procedure
is documented in the user documentation.
DDTS # CSCdx19598
A rare hardware failure on an STM16AS card transmitter can trigger SEF on the receiving STM16AS
card in a four fiber MS-SPRing (or BLSR) configuration. The BER calculations are suspended when
SEF is detected, so SD or SF is never raised. Likewise SEF is not considered a signal failure condition
like LOS or LOF, so a protection switch will not occur. If this occurs, use the CTC GUI to force a
protection switch on the MS-SPRing (or BLSR). This issue will not be resolved.
DDTS # CSCdv53427
In a two ring, two fiber MS-SPRing (or BLSR) configuration (or a two ring MS-SPRing or BLSR
configuration with one two fiber and one four fiber ring) it is possible to provision a circuit that begins
on one ring, crosses to a second ring, and returns to the original ring. Such a circuit can have protection
vulnerabilities if one of the common nodes is isolated, or if a ring is segmented in such a way that two
non-contiguous segments of the circuit on the same ring are each broken. There are two possible
workarounds for this issue:
1. Manually route the circuit to avoid the “one circuit over two ring” routing scenario.
2. When routing the circuit automatically, select the Using Required Nodes/Spans option in the Circuit
Routing Preference screen, then select the appropriate spans to avoid the “one circuit over two ring”
routing scenario.
This issue will be resolved in a future release.
Database Restore on an MS-SPRing (or BLSR)
When restoring the database on an MS-SPRing (or BLSR), follow these steps: