- 3.1 Transients Indexed By Alphabetical Entry
- 3.2 Trouble Notifications
- 3.3 Transient Conditions
- 3.3.1 ADMIN-DISABLE
- 3.3.2 ADMIN-DISABLE-CLR
- 3.3.3 ADMIN-LOCKOUT
- 3.3.4 ADMIN-LOCKOUT-CLR
- 3.3.5 ADMIN-LOGOUT
- 3.3.6 ADMIN-SUSPEND
- 3.3.7 ADMIN-SUSPEND-CLR
- 3.3.8 AUD-ARCHIVE-FAIL
- 3.3.9 AUTOWDMANS
- 3.3.10 BLSR-RESYNC
- 3.3.11 DBBACKUP-FAIL
- 3.3.12 DBRESTORE-FAIL
- 3.3.13 EFM-ERR-FRM
- 3.3.14 EFM-FRM-PER
- 3.3.15 EFM-FRM-SEC
- 3.3.16 EFM-RLBK-FAIL
- 3.3.17 EFM-SYM-PER
- 3.3.18 FIREWALL-DIS
- 3.3.19 FRCDWKSWBK-NO-TRFSW
- 3.3.20 FRCDWKSWPR-NO-TRFSW
- 3.3.21 INTRUSION
- 3.3.22 IOSCFG-COPY-FAIL
- 3.3.23 LOGIN-FAIL-LOCKOUT
- 3.3.24 LOGIN-FAIL-ONALRDY
- 3.3.25 LOGIN-FAILURE-PSWD
- 3.3.26 LOGOUT-IDLE-USER
- 3.3.27 MANWKSWBK-NO-TRFSW
- 3.3.28 MANWKSWPR-NO-TRFSW
- 3.3.29 PM-TCA
- 3.3.30 PS
- 3.3.31 RMON-ALARM
- 3.3.32 RMON-RESET
- 3.3.33 SFTWDOWN-FAIL
- 3.3.34 USER-LOCKOUT
- 3.3.35 USER-LOGIN
- 3.3.36 USER-LOGOUT
- 3.3.37 WKSWBK
- 3.3.38 WKSWPR
- 3.3.39 WTR-SPAN
Transient Conditions
This chapter gives a description, entity, SNMP number, and trap for each commonly encountered Cisco ONS 15454 transient condition.
Alarms can occur even in those cards that are not explicitly mentioned in the Alarm sections. When an alarm is raised, refer to its clearing procedure.
3.1 Transients Indexed By Alphabetical Entry
Table 3-1 alphabetically lists all ONS 15454 transient conditions and their entity, SNMP number, and SNMP trap.
Note 
The CTC default alarm profile might contain conditions that are not currently implemented but are reserved for future use.
3.2 Trouble Notifications
The ONS 15454 system reports trouble by using standard condition characteristics that follow the rules in Telcordia GR-253 and graphical user interface (GUI) state indicators.
The ONS 15454 uses standard Telcordia categories to characterize levels of trouble. The system reports trouble notifications as alarms and reports status or descriptive notifications (if configured to do so) as conditions in the CTC Alarms window. Alarms typically signify a problem that you need to remedy, such as a loss of signal. Conditions do not necessarily require troubleshooting.
3.2.1 Condition Characteristics
Conditions include any problem detected on an ONS 15454 shelf. They can include standing or transient notifications. You can retrieve a snapshot of all currently raised conditions on the network, node, or card in the CTC Conditions window or by using the RTRV-COND commands in TL1.
Note Some cleared conditions are found on the History tab.
For a comprehensive list of conditions, refer to the Cisco ONS SONET TL1 Command Guide.
3.2.2 Condition States
The History tab state (ST) column indicates the disposition of the condition, as follows:
•A raised (R) event is active.
•A cleared (C) event is no longer active.
•A transient (T) event is automatically raised and cleared in CTC during system changes such as user login, log out, and loss of connection to node view. Transient events do not require user action.
3.3 Transient Conditions
This section lists in alphabetical order all the transient conditions encountered in Software Release 7.2. The description, entity, SNMP number, and SNMP trap accompany each condition.
3.3.1 ADMIN-DISABLE
The Disable Inactive User (ADMIN-DISABLE) condition occurs when the administrator disables the user or the account is inactive for a specified period.
This transient condition does not result in a standing condition.
3.3.2 ADMIN-DISABLE-CLR
The Disable Inactive Clear (ADMIN-DISABLE-CLR) condition occurs when the administrator clears the disable flag on the user account.
This transient condition does not result in a standing condition.
3.3.3 ADMIN-LOCKOUT
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.
3.3.4 ADMIN-LOCKOUT-CLR
The Admin Lockout Clear (ADMIN-LOCKOUT-CLR) condition occurs when the administrator unlocks a user account or the lockout time expires.
This transient condition does not result in a standing condition.
3.3.5 ADMIN-LOGOUT
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.
3.3.6 ADMIN-SUSPEND
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.
3.3.7 ADMIN-SUSPEND-CLR
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.
3.3.8 AUD-ARCHIVE-FAIL
The Archive of Audit Log Failed (AUD-ARCHIVE-FAIL) condition occurs when the software cannot 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 when trying to archive. The user must log in again with correct user name, password, and FTP server details.
This transient condition does not result in a standing condition.
3.3.9 AUTOWDMANS
The Automatic WDM ANS Finish (AUTOWDMANS) condition indicates that an automatic node setup command has been initiated. It normally occurs when you replace DWDM cards; the condition is an indication that the system has regulated the card.
This transient condition does not result in a standing condition.
3.3.10 BLSR-RESYNC
The BLSR Multinode Table Update Completed (BLSR-RESYNC) condition might occur when you create or delete circuits on a bidirectional line switched ring (BLSR), change a ring topology (for example, add or delete a BLSR node), or change the BLSR circuit state and ring ID.
This transient condition does not result in a standing condition.
3.3.11 DBBACKUP-FAIL
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.
3.3.12 DBRESTORE-FAIL
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 TAC for assistance.
3.3.13 EFM-ERR-FRM
The EFM Link Monitoring - Errored Frame Event condition occurs when the number of error frames detected on the remote NE is equal to or greater than the specified threshold for a specified period, and the remote NE notifies local NE of the same. A period is specified by time interval.
This transient condition does not result in a standing condition.
3.3.14 EFM-FRM-PER
The EFM Link Monitoring - Errored Frame Period Event condition occurs when the number of errored frames detected on the remote NE is equal to or greater than the specified threshold for a specified period, and the remote NE notifies local NE of the same. A period is specified by the number of received frames.
This transient condition does not result in a standing condition.
3.3.15 EFM-FRM-SEC
The EFM Link Monitoring - Errored Frame Seconds Summary condition occurs when the number of errored frame seconds (a 1-second interval wherein at least one frame error was detected) on the remote NE crosses the configured threshold. The remote NE notifies local NE of the condition.
3.3.16 EFM-RLBK-FAIL
The EFM - Remote Loopback Request Failed condition occurs when a request fails. When the user triggers a remote loopback request on the local NE, the request is forwarded to the remote NE. If the remote NE does not respond to the request and the local NE times out, this condition notifies the user on local NE about the failure.
This transient condition does not result in a standing condition.
3.3.17 EFM-SYM-PER
The EFM Link Monitoring - Errored Symbol Period Event condition occurs when the symbol errors detected at the remote NE cross a configured threshold. This condition notifies the user onthe local NE of this threshold crossing.
This transient condition does not result in a standing condition.
3.3.18 FIREWALL-DIS
The Firewall Has Been Disabled (FIREWALL-DIS) condition occurs when you provision the firewall to Disabled.
This transient condition does not result in a standing condition.
3.3.19 FRCDWKSWBK-NO-TRFSW
The Forced Switch Back to Working Resulted in No Traffic Switch (FRCDWKSWBK-NO-TRFSW) condition occurs when you perform a Force Switch to the working port/card and the working port/card is already active.
This transient condition might result in a Force Switch (Ring or Span) standing condition for a BLSR.
3.3.20 FRCDWKSWPR-NO-TRFSW
The Forced Switch to Protection Resulted in No Traffic Switch (FRCDWKSWPR-NO-TRFSW) condition occurs when you perform a Force Switch to the protect port/card, and the protect port/card is already active.
This transient condition does not result in a standing condition.
3.3.21 INTRUSION
The Invalid Login Username (INTRUSION) condition occurs when you attempt to login with an invalid user ID.
This transient condition does not result in a standing condition.
3.3.22 IOSCFG-COPY-FAIL
The IOS Config Copy Failed (IOSCFG-COPY-FAIL) condition occurs on ML-Series Ethernet cards when the software fails to upload or download the Cisco IOS startup configuration file to or from an ML-Series card. This condition is similar to the "SFTWDOWN-FAIL" condition on page 3-9, but the IOSCFG-COPY-FAIL condition applies to ML-Series Ethernet cards rather than the TCC2/TCC2P card.
3.3.23 LOGIN-FAIL-LOCKOUT
The Invalid Login-Locked 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.
3.3.24 LOGIN-FAIL-ONALRDY
The Security: Invalid Login-Already Logged On (LOGIN-FAIL-ONALRDY) condition occurs when you attempt to login to 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.
3.3.25 LOGIN-FAILURE-PSWD
The Invalid Login-Password (LOGIN-FAILURE-PSWD) condition occurs when you attempt to login with an invalid password.
This transient condition does not result in a standing condition.
3.3.26 LOGOUT-IDLE-USER
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.
3.3.27 MANWKSWBK-NO-TRFSW
The Manual Switch Back To Working Resulted in No Traffic Switch (MANWKSWBK-NO-TRFSW) condition occurs when you perform a Manual switch to the working port/card and the working port/ card is already active.
This transient condition does not result in a standing condition.
3.3.28 MANWKSWPR-NO-TRFSW
The Manual Switch to Protect Resulted in No Traffic Switch (MANWKSWPR-NO-TRFSW) condition occurs when you perform a Manual switch to the protect port/card and the protect port/card is already active.
This transient condition results in a BLSR Manual Switch (Span or Ring) standing condition.
3.3.29 PM-TCA
The Performance Monitor Threshold Crossing Alert (PM-TCA) condition occurs when network collisions cross the rising threshold for the first time.
3.3.30 PS
The Protection Switch (PS) condition occurs when the traffic switches from a working/active card to a protect/standby card.
3.3.31 RMON-ALARM
The RMON Threshold Crossing Alarm (RMON-ALARM) condition occurs when the remote monitoring variable crosses the threshold.
3.3.32 RMON-RESET
The RMON Histories and Alarms Reset Reboot (RMON-RESET) condition occurs when the time-of-day settings on the TCC2/TCC2P card are increased or decreased by more than five seconds. This invalidates all the history data and remote monitoring (RMON) must restart. It can also occur when you reset a card.
3.3.33 SFTWDOWN-FAIL
The Software Download Failed (SFTDOWN-FAIL) condition occurs when the system fails to download the required software.
An incorrect input that points to the wrong place or file, network issues, or a bad (corrupt) package can cause this failure. Retrying the operation with the correct name/location will usually succeed. If network issues persist, you must contact the network lab support. If the package is corrupt, contact Cisco TAC.
3.3.34 USER-LOCKOUT
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.
3.3.35 USER-LOGIN
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.
3.3.36 USER-LOGOUT
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.
3.3.37 WKSWBK
The Switched Back to Working (WKSWBK) condition occurs when traffic switches back to the working port/card in a non-revertive protection group.
This transient condition does not result in a standing condition.
3.3.38 WKSWPR
The Switched to Protection (WKSWPR) condition occurs when traffic switches to the protect port/card in a non-revertive protection group. This transient condition does not result in a standing condition. The (WKSWPR) is raised as a standing condition in a revertive protection group.
The Switched to Protection (WKSWPR) condition also occurs after the protection switch in a 1+1 non-revertive protection group as a transient condition. When the protection group is changed to revertive, the (WKSWPR) is not raised as a standing condition or as a new transient condition. However, after a protection switch in a 1:1 protection group, the user will not be allowed to configure the protection group from non-revertive to revertive.
3.3.39 WTR-SPAN
The Span is in Wait To Restore State (WTR-SPAN) condition occurs when a BLSR switches to another span due to a Signal Failure-Span command or a fiber is pulled from a four-fiber BLSR configuration. The condition is raised until the WaitToRestore (WTR) period expires.
This transient condition clears when the BLSR returns to a normal condition or the IDLE state.
Feedback