Release Notes

Release Notes for Cisco ONS 15454 SDH Release 4.1.3

OL-4984-01

Caveats

Step 1 To isolate the failed node, issue a force switch toward the failure node from the adjacent east and west

nodes.

Step 2 If more than one node has failed, restore the database one node at a time.

Step 3 After the TCCi has reset and booted up, release the force switch from each node.

SNCP Functionality

DDTS # CSCeb37707

With a VT SNCP circuit, if you inject signals with a thru-mode test set into one path of the circuit in a

particular order, you may not see the appropriate alarms. This can occur when you first inject LOP-P,

then clear, then inject LOP-V. This issue will be resolved in Release 6.0.

DDTS # CSCea23862

After you perform a force switch on one of the spans of a DRI or IDRI topology with SNCP DRI circuits

present, if you then apply a clear on the same span, the state will not show up immediately in CTC. This

issue is under investigation.

DDTS # CSCea23732

If you try to manually create a VC4 circuit over a three node, STM4 SNCP using automatic routing and

a required node, but there is no protected path from the source to the destination excluding the required

node, automatic routing will fail to find a path and will raise a “ComputeRouteInMixedDomains: No

Route Found” exception. To avoid this issue, you can avoid selecting required nodes, or use manual

routing. This issue will be resolved in Release 5.0.

Active Cross Connect or TCCi/2 Card Removal

As in MS-SPRing (or BLSR) and 1+1, you must perform a lockout on SNCP (or path protection) before

removing an active cross connect or TCCi (or TCC2) card. The following rules apply to SNCP (or path

protection).

Active cross connect cards should not be removed. If the active cross connect or TCCi/2 card must be

removed, to minimize network interruption you can first perform an XC10G (or XCVXL) side switch

and then remove the card once it is in standby, or you can perform a lockout on all circuits that originate

from the node whose active cross connect or active TCCi/2 will be removed (performing a lockout on all

spans will also accomplish the same goal). No lockout is necessary for switches initiated through CTC.

Performance Monitoring

DDTS # CSCea38791

In the CTC Performance > Statistics tab of the G1000-4 or G1000-2, there are no entries for Rx/Tx

Multicast and Broadcast packets. This issue will be resolved in a future release.