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

Release 4.1 and 4.5 TL1 cannot display/retrieve/delete a DS3Xm VT Non-STS-1 
cross-connection/circuit. This applies to ONS 15454s with DS3XM VT cross-connection provisioning 
via TL1, on any STS or port other than STS-1 or PORT-1, and with the AID format of:

VT1-Slot#-Sts#-Group#-Vt#

The cross-connection is provisioned as expected; however, the connection STS number in the TL1 VT 
AID format is always shown as “1” for the RTRV-CRS::ALL command and RTRV-CRS-VT1 with the 
AID used in the creation command (the non-one STS).

This issue has an impact on any DS3Xm VT connection deletion via TL1 where the STS number is not 
actually 1. The displayed VT1 AID cannot be used to retrieve the connection, and also cannot be used 
to delete the created connection. Also, the VT alarms/events/conditions on such a DS3XM VT 
circuit/connection will have the same AID issue: the StsNumber in the AID is always 1.

To work around this issue, delete the TL1-created DS3XM VT non-STS-1 cross-connection using the 
provisioned DS3XM VT AID (non-STS-1) or using CTC. There is no workaround for the alarm/event 
reporting for the non-STS-1 DS3XM VT circuit in the impacted releases (4.1 and 4.5). This issue is 
resolved in Release 4.6 and in maintenance Release 4.1.3.

The default state, when no PST or SST inputs are given for The TL1 command, RMV-<MOD2_IO>, is 
OOS instead of OOS-MT. Thus, if you issue a RMV statement, followed by maintenance-state-only 
commands, such as OPR-LPBK, the maintenance state commands will not work, since the port will be 
in the out-of-service state (OOS), instead of the out-of-service maintenance state (OOS-MT). To work 
around this issue, place ports in the OOS-MT state, by specifying the primary state as OOS and a 
secondary state of MT in either the RMV-<MOD2_IO> command or the ED-<MOD2_IO> command.

Scripts that depend on the RMV-<MOD2_IO> command defaulting to OOS-MT without specifying the 
primary and secondary states should be updated to force the primary and secondary state inputs to be 
populated. This issue is resolved in Release 4.1.

The TL1 command, INH-USER-SECU, does not disable the userid appropriately. The command should 
disable the userid until the corresponding ALW-USER-SECU command is issued; however, the userid is 
automatically re-enabled after the user lock-out period expires. The user lockout period is set from the 
CTC. This issue is resolved in Release 4.1.

This section highlights new features and functionality for Release 4.1.x. For detailed documentation of 
each of these features, consult the user documentation.