Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP)
39
Release Notes for Cisco ONS 15454 Release 5.0.5
OL-8073-01
New Features and Functionality
DDTS # CSCeg68057
When issuing the TL1 command “RTRV-COND-VT1” with an AID block of “SLOT-*” the TL1 agent
will incur an exception and cause the shelf controller to reset. The standby shelf controller will become
active. To avoid this, do not use the “SLOT-*” AID with this command. This issue is resolved in Release
5.0.2.
will incur an exception and cause the shelf controller to reset. The standby shelf controller will become
active. To avoid this, do not use the “SLOT-*” AID with this command. This issue is resolved in Release
5.0.2.
DDTS # CSCed08144
Rarely, TL1 autonomous messages might not be displayed in a session after several days of PM-related
provisioning changes. This issue is resolved in Release 5.0.
provisioning changes. This issue is resolved in Release 5.0.
DDTS # CSCeb33033
An exception is raised when retrieving PM stats via TL1 for the protect card of a 1:1 protection group
when the working card is active. To avoid this issue, retrieve stats from the working card instead of the
protect card. This issue is resolved in Release 5.0.
when the working card is active. To avoid this issue, retrieve stats from the working card instead of the
protect card. This issue is resolved in Release 5.0.
DDTS # CSCdz26071
The TL1 COPY-RFILE command, used for SW download, database backup, and database restore,
currently does not allow a user-selected port parameter to make connections to the host. The command
expects the default parameter of Port 21 and will only allow that number. This issue is resolved in
Release 5.0.
currently does not allow a user-selected port parameter to make connections to the host. The command
expects the default parameter of Port 21 and will only allow that number. This issue is resolved in
Release 5.0.
DDTS # CSCdz79471
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.
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.7.
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.7.
New Features and Functionality
This section highlights new features and functionality for Release 5.0.x. For detailed documentation of
each of these features, consult the user documentation.
each of these features, consult the user documentation.
Note
Features introduced in the Release 4.7 DWDM platform are repeated herein for ease of access.