The Disable Inactive User (ADMIN-DISABLE) condition occurs when the administrator disables a user or when a account is inactive for a specified period.

This transient condition does not result in a standing condition.

The Disable Inactive Clear (ADMIN-DISABLE-CLR) condition occurs when the administrator clears the disable flag on a user account.

This transient condition does not result in a standing condition.

The Admin Lockout of User (ADMIN-LOCKOUT) condition occurs when the administrator locks a user account.

This transient condition does not result in a standing condition.

The Admin Lockout Clear (ADMIN-LOCKOUT-CLR) condition occurs when the administrator unlocks a user account or when the lockout time expires.

This transient condition does not result in a standing condition.

The Admin Logout of User (ADMIN-LOGOUT) condition occurs when the administrator logs off a user session.

This transient condition does not result in a standing condition.

The Suspend User (ADMIN-SUSPEND) condition occurs when the password for a user account expires.

This transient condition does not result in a standing condition.

The Suspend User Clear (ADMIN-SUSPEND-CLR) condition occurs when the user or administrator changes the password.

This transient condition does not result in a standing condition.

The Archive of Audit Log Failed (AUD-ARCHIVE-FAIL) condition occurs when the software fails to archive the audit log. The condition normally occurs when the user refers to an FTP server that does not exist, or uses an invalid login while trying to archive. The user must log in again with correct user name, password, and FTP server details.

This transient condition does not lead to a standing condition.

The Automatic WDM ANS Finish (AUTOWDMANS) condition indicates that an automatic node setup (ANS) command has been initiated. It normally occurs when you replace dense wavelength division multiplexing (DWDM) cards; the condition is an indication that the system has regulated the card.

This transient condition does not result in a standing condition.

The Database Backup Failed (DBBACKUP-FAIL) condition occurs when the system fails to back up the database when the backup command is initiated.

This condition can occur when the server is not able to handle the backup operation due to network or server issues. Repeat the same operation again and check to see if it is successful. If the backup fails, it could be due to a network issue or software program failure. Contact the Cisco Technical Assistance Center (TAC) (1 800 553-2447) for assistance.

The Database Restore Failed (DBRESTORE-FAIL) condition occurs when the system fails to restore the backed up database when the restore command is initiated.

This condition can be due to server issues, network issues, or human error (pointing to a file that does not exist, wrong file name, etc.). Retrying the database restore with the correct file will usually succeed. If the network issue persists, you must contact network lab support. If the condition is caused by a network element (NE) failure, contact the Cisco Technical Assistance Center (TAC) (1 800 553-2447) for assistance.

The Firmware Download (FIRMWARE-DOWNLOAD) condition occurs when the firmware is being downloaded during the firmware upgrade. The firmware upgrade initiates when the download is complete.

This transient condition does not result in a standing condition.

The Firmware Upgrade (FIRMWARE-UPG) condition occurs when the firmware is being upgraded. This condition reflects the upgrade status.

This transient condition does not result in a standing condition.

The Firmware Upgrade Complete (FIRMWARE-UPG-COMPLETE) condition occurs when the firmware upgrade is successfully completed.

This transient condition does not result in a standing condition.

The Firmware Upgrade Fail (FIRMWARE-UPG-FAIL) condition occurs when the firmware upgrade fails. The user must start the firmware upgrade again.

This transient condition does not result in a standing condition.

The Invalid LoginLocked Out (LOGIN-FAIL-LOCKOUT) condition occurs when you attempt to log into a locked account.

This transient condition does not result in a standing condition.

The Security: Invalid LoginAlready Logged On (LOGIN-FAIL-ONALRDY) condition occurs when a user attempts to log into a node where the user already has an existing session and a Single-User-Per-Node (SUPN) policy exists.

This transient condition does not result in a standing condition.

The Invalid LoginPassword (LOGIN-FAILURE-PSWD) condition occurs when you attempt to log in with an invalid password.

This transient condition does not result in a standing condition.

The Invalid LoginUsername (LOGIN-FAILURE-USERID) condition occurs when a user login ( SVO web interface) fails because the login username is not present on the node database. You must log in again with an existing user ID.

This transient condition is equivalent to a security warning. You must check the security log (audit log) for other security-related actions that have occurred.

The Automatic Logout of Idle User (LOGOUT-IDLE-USER) condition occurs when a user session is idle for too long (the idle timeout expires) and the session terminates as a result. You must log in again to restart your session.

The Master Key Exchange Success condition occurs when the primary key is successfully reset and the Threshold Crossing Alert (TCA) has provisioned.

This transient condition does not result in a standing condition.

The Performance Monitoring Threshold Crossing Alert (PM-TCA) condition occurs when network collisions cross the rising threshold for the first time.

The Password Change Required condition occurs when the user password needs to be changed.

This transient condition does not result in a standing condition.

The Remote Monitoring Threshold Crossing Alarm (RMON-ALARM) condition occurs when the remote monitoring (RMON) variable crosses the threshold.

The RMON Histories and Alarms Reset Reboot (RMON-RESET) condition occurs when the time-of-day settings on the control card are increased or decreased by more than five seconds. This invalidates all the history data, and RMON must restart. It can also occur when you reset a card.

The Session Time Limit Expired (SESSION-TIME-LIMIT) condition occurs when a login session exceeds the time limit and you are logged out of the session. You must log in again.

The User Locked Out (USER-LOCKOUT) condition occurs when the system locks an account because of a failed login attempt. To proceed, the administrator must unlock the account or the lockout time must expire.

The Login of User (USER-LOGIN) occurs when you begin a new session by verifying your user ID and password.

This transient condition does not result in a standing condition.

The Logout of User (USER-LOGOUT) condition occurs when you stop a login session by logging out of your account.

This transient condition does not result in a standing condition.

The Warm Restart (WRMRESTART) condition occurs when the node restarts while it is powered up. A restart can be caused by provisioning, such as a database restore or IP changes, or by software defects. A WRMRESTART is normally accompanied by MANRESET or AUTORESET to indicate whether the reset was initiated manually (MAN) or automatically (AUTO).

This is the first condition that appears after a control card is powered up. The condition changes to COLD-START if the control card is restarted from a physical reseat or a power loss.

Default Severity: Warning

Logical Object: Transient

Resource Type: OPT ODUk

The WKSWBK alarm is raised when the protection switch returns the traffic to the nominal working resource.