Troubleshooting guide

26
Release Notes for Cisco ONS 15454 Release 7.0.2
OL-11368-01
Caveats
CSCed10127
Extra traffic is not restored when an SF-R occurs on the same span where a lockout of protect is applied
at the opposite node, and where the extra traffic is sourced, destined, or travels through the node with
the SF-R. to work around this, issue a lockout on each end of the span at the node where the SF-R occurs.
Extra traffic should then be restored. This issue will not be resolved.
CSCea59342
DS3 PCA traffic may take up to 20 seconds to recover after a BLSR switch is cleared. This can occur
with DS3 PCA traffic on two-Fiber or four-Fiber BLSR configuration with XCVT cards in the same
nodes as the DS3 cards. This issue will be resolved in a future release.
CSCdw58950
You must lock out protection BLSR, 1+1, and UPSR traffic to avoid long, or double traffic hits before
removing an active XCVT or XC10G card. You should also make the active cross connect card standby
before removing it.
CSCdv53427
In a two ring, two fiber BLSR configuration (or a two ring 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.
Database Restore on a BLSR
When restoring the database on a BLSR, follow these steps:
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 TCC2/TCC2P has reset and booted up, ensure that the “BLSR Multi-Node Table update
completed” event has occurred for all nodes in the ring.
Step 4 Release the force switch from each node.