New Features and Functionality
Auto-refresh PM Data
You can auto-refresh PM data using a check box and pull-down menu providing valid options on the Performance Monitoring screen in the card view. When selected, the information auto refreshes the screen every x seconds (where x is selected from the valid options or manually configured). The auto-refresh only works while the selected card is in card view. When you are not viewing this card in card view, PM data is not auto-refreshed. However, when you return to the card, the auto-refresh option has not changed. This parameter can be specified and remembered for each card individually and for each node separately.
BLSR Support
Two by Two Fiber BLSR
Prior to Release 3.3, the ONS 15327 only supported 1+1, UPSR and PPMN protection schemes. With Release 3.3, two fiber BLSR protection is fully supported and fully interoperable with ONS 15454 two fiber BLSR. The ONS 15327 node can support up to two 2 fiber BLSR configurations on any of the 4 high speed slots (Slots 1-4). The following guidelines should be used when implementing two fiber BLSR:
•You can have one BLSR operating at OC-12 and the other BLSR operating at OC-48.
•You can have both BLSRs operating at OC-12.
•You can have both BLSRs operating at OC-48.
•BLSRs are not supported with OC-3.
Traffic from one BLSR is cross-connected to the other BLSR at both the VT1.5 and STS-1 payload mappings.
To provision two 2 fiber BLSRs within the same node, from the node view, click Provisioning > Ring. BLSR provisioning is the same as in the ONS 15454 platform. Refer to the Cisco ONS 15327 User Documentation, Release 3.3 for BLSR provisioning. When provisioning two 2 fiber BLSRs within the same node, the Ring ID must be unique for each BLSR. However, the Node ID for each BLSR can be identical.
After two 2 fiber BLSRs have been provisioned, the two rings are viewable in the network view of the CTC.
16 Node BLSR Support
With Release 3.3, a BLSR can support a mix of up to 32 ONS 15454 and ONS 15327 nodes. BLSR switch times will be within 50 ms (compliant with Telcordia GR-1230-CORE), for BLSRs which are provisioned with up to 16 nodes. If more than 16 nodes are provisioned on one BLSR (a maximum of 32 is officially supported), Cisco cannot guarantee that switch times will be within the 50 ms range.
Non-Revertive BLSR
With Release 3.3, you can provision a BLSR to be revertive or non-revertive. Non-revertive BLSR switching only applies to automatically initiated switch requests (for example, signal fail or signal degrade). When a manual BLSR switch to protect is executed in CTC, traffic will return to the working channels after a Clear command is issued. In non-revertive mode, when traffic is placed on the protect channels after an automatic switch, traffic will remain on the protection channels even after the failure condition has cleared. Traffic is returned to the working channels in the following situations:
•A lockout span is executed from either the working or the protect side of the BLSR
Release Notes for Cisco ONS 15327 Release 3.3
