The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter gives a description, entity, Simple Network Management Protocol (SNMP) number, and trap for each commonly encountered Cisco ONS 15600 SDH transient condition.
Table 3-1 alphabetically lists all ONS 15600 SDH 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.
The ONS 15600 SDH reports trouble by using standard condition characteristics that follow the rules in ITU-T G.784 and graphical user interface (GUI) state indicators.
The ONS 15600 SDH uses standard ITU 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.
Conditions include any problem detected on an ONS 15600 SDH 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 Some cleared conditions are found on the History tab.
For a comprehensive list of conditions, refer to the Cisco ONS 15454 and Cisco ONS 15600 SDH TL1 Command Guide.
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, logout, and loss of connection to node view. Transient events do not require user action.
This section lists in alphabetical order all the transient conditions encountered in Software Release 9.0. The description, entity, SNMP number, and SNMP trap accompany each condition.
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.
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.
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 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 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.
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.
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.
The TSC Switched to Alternate Ethernet Port (ETHERNET-PORT-SWITCH) condition 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 SDH and the router or switch.
The Exercising Ring Successfully (EXERCISING-RING) condition occurs whenever you issue an Exercise-Ring command from CTC or Transaction Language 1 (TL1). This condition indicates that a command is being executed. You must issue another command to clear the exercise and the condition.
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.
The Invalid Login Username (INTRUSION) condition occurs when you attempt to log in with an invalid user ID.
This transient condition does not result in a standing condition.
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.
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.
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.
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 MS-SPRing Multi-Node Table Update Completed (MSSP-RESYNC) condition occurs when a node receives all relevant information such as payload, path state, Routing Information Protocol (RIP), cross-connect tables, and cross-connect VT tables from the other nodes in the ring. This condition is raised on all nodes in the ring while a node is added or a circuit is provisioned. This transient condition will not be cleared and is seen in the History tab of CTC.
You must check this condition on all the nodes and then remove the Forced Ring Switch commands.
The Performance Monitor Threshold Crossing Alert (PM-TCA) condition occurs when network collisions cross the rising threshold for the first time.
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.
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 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.
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.