Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Notas de publicación
21
Release Notes for Cisco ONS 15454 Release 4.0.1
OL-4470-01
Caveats
DDTS # CSCdz86121
In one rare case, the ONS 15454/15327 times out a user session without communicating the timeout to
TL1. If this happens, the TL1 user remains logged in, although the session is actually timed out. This
can occur when you log into the node with a timeout of X minutes. If the user session sits idle for all but
5 seconds of the X minutes, then you have only 5 seconds to type in a command to notify the node that
the session is active. If you try this, you will likely miss the five second window, in which case the node
will respond as though the session is inactive and deny access. However, because you have typed a key,
irrespective of the five second window, TL1 responds as though the session is active and does not log
you out (time out). You will not have access to the node and will receive a “DENY” response to TL1
commands. The error message may vary depending on commands issued. To recover from this situation,
log out and log back in to TL1. This issue will be resolved in Release 5.0.
TL1. If this happens, the TL1 user remains logged in, although the session is actually timed out. This
can occur when you log into the node with a timeout of X minutes. If the user session sits idle for all but
5 seconds of the X minutes, then you have only 5 seconds to type in a command to notify the node that
the session is active. If you try this, you will likely miss the five second window, in which case the node
will respond as though the session is inactive and deny access. However, because you have typed a key,
irrespective of the five second window, TL1 responds as though the session is active and does not log
you out (time out). You will not have access to the node and will receive a “DENY” response to TL1
commands. The error message may vary depending on commands issued. To recover from this situation,
log out and log back in to TL1. This issue will be 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 will be 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 will be resolved in
Release 5.0
DDTS # CSCea03186
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 will be alleviated in Release 4.1 by removal of the ALW-USER-SECU and
INH-USER-SECU commands. The commands will be reinstated correctly in Release 4.6.
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 will be alleviated in Release 4.1 by removal of the ALW-USER-SECU and
INH-USER-SECU commands. The commands will be reinstated correctly in Release 4.6.
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 will be resolved in Release 5.0.
primary and secondary states should be updated to force the primary and secondary state inputs to be
populated. This issue will be resolved in Release 5.0.
DDTS # CSCdu53509
When a TL1 session to a remote node (ENE) is established via a gateway node (GNE) and you have
changed the node name of the ENE via either TL1, CTC or SNMP, then you must wait for about 30
seconds to issue a TL1 command via the GNE. This delay is to permit the updates to propagate to all
nodes in the network. During this transition, neither the old node name nor the new node name can be
used in the TL1 session to access the ENE. This 30 second window may be reduced in a future release.
changed the node name of the ENE via either TL1, CTC or SNMP, then you must wait for about 30
seconds to issue a TL1 command via the GNE. This delay is to permit the updates to propagate to all
nodes in the network. During this transition, neither the old node name nor the new node name can be
used in the TL1 session to access the ENE. This 30 second window may be reduced in a future release.