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

Traffic that should be dropped remains unaffected when a BLSR Protection Channel Access (PCA) VT 
tunnel is placed OOS. You must place all circuits in the tunnel OOS before the traffic will be dropped. 
This issue will be resolved in a future release.

The two protect OC48AS cards at the ends of a four fiber BLSR span must both be configured as either 
K3 or Z2 (not a mixture). If both ends are not the same, the BLSR may fail to switch correctly. In Release 
3.4 the BLSR wizard ensures that both ends are configured correctly; however, you must still avoid 
manually changing the value on one side only (and hence, causing a mismatch) at the card level. If you 
do mismatch bytes at the card level, you can discover this by going to the BLSR edit map tied in with 
the BLSR wizard. The mismatched span will be red, and right-clicking on the span will allow you to 
correct the problem.

You must lock out protection BLSR, 1+1, and path protection configuration traffic to avoid long, or 
double traffic hits before removing an active XC, XCVT, or XC10G card. You should also make the 
active cross connect card standby before removing it.

When configuring a node with one 4 Fiber BLSR and one 2 Fiber BLSR, or with two 2 fiber BLSRs, an 
issue exists related to the version of XC deployed. Revision 004H and earlier revisions of the XC do not 
support these configurations. All later revisions of the XC and all versions of the XCVT and XC10G 
cross connects support all permutations of two BLSRs per node. 

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. This issue will be resolved in a future release.

VT1.5 BLSR squelching in BLSRs is not supported.

When restoring the database on a BLSR, follow these steps:

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

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