Feedback
Table Of Contents
3.1 Transients Indexed By Alphabetical Entry
3.2.1 Condition Characteristics
Transient Conditions
This chapter gives a description, entity, Simple Network Management Protocol (SNMP) number, and trap for each commonly encountered Cisco ONS 15600 transient condition.
3.1 Transients Indexed By Alphabetical Entry
Table 3-1 alphabetically lists all ONS 15600 transient conditions and their entity, SNMP number, and SNMP trap.
Note
The Cisco Transport Controller (CTC) default alarm profile might contain conditions that are not currently implemented but are reserved for future use.
3.2 Trouble Notifications
The ONS 15600 reports trouble by using standard condition characteristics that follow the rules in Telcordia GR-253 and graphical user interface (GUI) state indicators.
The ONS 15600 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 15600 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 Transaction Language One (TL1).
Note
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:
•
•
•
3.3 Transient Conditions
This section lists in alphabetical order all the transient conditions encountered in Software Release 9.1 and 9.2.1. 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 AUTH-FAIL
The Remote Authentication Fail - See Audit Log (AUTH-FAIL) condition indicates that an attempt to validate a login remotely has failed.
This transient condition does not result in a standing condition.
3.3.9 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.
3.3.10 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. Contact the Cisco Technical Assistance Center (Cisco TAC) for assistance; see the "Obtaining Documentation and Submitting a Service Request" section on page xxxi as needed.
3.3.11 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 Cisco TAC for assistance. See the "Obtaining Documentation and Submitting a Service Request" section on page xxxi as needed.
3.3.12 ETHERNET-PORT-SWITCH
The TSC Switched to Alternate Ethernet Port (ETHERNET-PORT-SWITCH) occurs when an alternate Ethernet port becomes active. If it occurs after startup, it means that the backplane Ethernet connection that was active is not active anymore. Onsite technical support must check the connection between the ONS 15600 and the router or switch.
3.3.13 EXERCISING-RING
The Exercising Ring Successfully (EXERCISING-RING) condition occurs whenever you issue an Exercise-Ring command from CTC or TL1. This condition indicates that a command is being executed. You must issue another command to clear the exercise and the condition.
3.3.14 EXERCISING-SPAN
The Exercising Span Successfully (EXERCISING-SPAN) condition occurs whenever you issue an Exercise-Span command from CTC or TL1. This condition indicates that a command is being executed.
3.3.15 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.16 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.17 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.18 LOGIN-FAIL-ONALRDY
The Security: Invalid Login-Already Logged On (LOGIN-FAIL-ONALRDY) condition occurs when you attempt to log into a node where you already have an existing session and a Single-User-Per-Node (SUPN) policy exists.
This transient condition does not result in a standing condition.
3.3.19 LOGIN-FAILURE-PSWD
The Invalid Login-Password (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.
3.3.20 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.21 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.22 SWFTDOWNFAIL
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. See the "Obtaining Documentation and Submitting a Service Request" section on page xxxi for details.
3.3.23 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.24 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.25 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.26 WKSWBK
The Switched Back to Working (WKSWBK) condition occurs when traffic switches back to the working port/card in a nonrevertive protection group.
This transient condition does not result in a standing condition.
3.3.27 WKSWPR
The Switched to Protection (WKSWPR) condition occurs when traffic switches to the protect port/card in a nonrevertive protection group.
This transient condition does not result in a standing condition.
