Примечания к выпуску для Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP)

In Release 6.0 a Mismatch Equipment Attributes (MEA) alarm is raised incorrectly against the B-Side 
BIC (EIA) on an ONS 15454 node using the 15454-SA-HD (high density) chassis with 1BNCB48, 
1BNCB24, or 1SMBB84 EIAs installed. The 1BNCB48, 1BNCB24, and 1SMBB84 EIA panels are 
compatible with the 15454-SA-HD shelf assembly; however, the software in Release 6.0 fails to 
recognize their compatibility. The MEA alarm raised as a result of this issue is not service impacting, 
but does cause a standing alarm. 

As a workaround to the standing alarm, you can change the BIC-MEA alarm severity by creating and 
using a custom alarm profile following the steps that apply for your network in the NTP-A71 Create, 
Download, and Assign Alarm Severity Profiles procedure of the Manage Alarms chapter in the Cisco 
ONS 15454 Procedure Guide, Release 6.0. This issue will be resolved in Release 6.1. 

A CTC client session can disconnect from an ONS node during simultaneous deletion of large numbers 
of VT level circuits (3000+). Connectivity to the node will recover without any user action. If the 
condition persists, restart the CTC session to reconnect. This issue is under investigation.

When retrieving GBIC inventory for the FC_MR-4, nothing is returned for the CLEI code. In a future 
release, enhanced inventory information will be available for ONS GBICs. This will include the CLEI 
code.

When you create a bidirectional BLSR-path protection IDRI circuit using auto-routing and select the 
PCA option for secondary spans, the circuit is created over working BLSR spans and does not use PCA 
spans. To enforce the use of the PCA option, provision the circuit using manual routing. This issue will 
not be resolved.

The Wait To Restore (WTR) alarm does not appear to be raised for as long as the WTR timer is set for. 
The WTR is raised correctly, but the alarm is hidden for the first 12 seconds due to the clear soaking time 
for a CLDRESTART alarm. You can see this behavior if you set up a 1+1 bidirectional revertive 
protection group, remove the working card, and then reinsert the card. There are no plans to change this 
behavior.

If you create a PM schedule with the Start time for the PM report equal to 00:00 (in TL1, “0-0”), after a 
few minutes the PM report start time might change to 23:59 (in TL1, “23-59”). This issue will not be 
resolved.