|
|
Table Of Contents
4.1 Transients Indexed By Alphabetical Entry
4.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 15454 transient condition.
Note
Unless otherwise specified, ONS 15454 refers to both ANSI and ETSI shelf assemblies.
4.1 Transients Indexed By Alphabetical Entry
Table 4-1 alphabetically lists all ONS 15454 transient conditions and their entity, SNMP number, and SNMP trap.
Note
4.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.
4.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 Transaction Language One (TL1).
Note
For a comprehensive list of conditions, refer to the Cisco ONS SONET TL1 Command Guide and the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Command Guide.
4.2.2 Condition States
The History tab state (ST) column indicates the disposition of the condition, as follows:
•
•
•
4.3 Transient Conditions
This section lists in alphabetical order all the transient conditions encountered in Software Release 8.0. The description, entity, SNMP number, and SNMP trap accompany each condition.
4.3.1 ADMIN-DISABLE
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.
4.3.2 ADMIN-DISABLE-CLR
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.
4.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.
4.3.4 ADMIN-LOCKOUT-CLR
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.
4.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.
4.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.
4.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.
4.3.8 AUD-ARCHIVE-FAIL
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.
4.3.9 AUTOWDMANS
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.
4.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) or multiplex section-shared protection ring (MS-SPRing), change a ring topology (for example, add or delete a BLSR/MS-SPRing node), or change the BLSR/MS-SPRing circuit state and ring ID.
This transient condition does not result in a standing condition.
4.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. Contact the Cisco Technical Assistance Center (TAC) for assistance; see the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xxxiii as needed.
4.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 Cisco TAC for assistance. See the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xxxiii as needed.
4.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.
4.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.
4.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.
4.3.16 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 or card and the working port or card is already active.
This transient condition might result in a Force Switch (Ring or Span) standing condition for a BLSR or MS-SPRing.
4.3.17 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 or card, and the protect port or card is already active.
This transient condition does not result in a standing condition.
4.3.18 INTRUSION
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.
4.3.19 INTRUSION-PSWD
The Security Intrusion Attempt Detected (INTRUSION -PSWD) condition occurs when you attempt to log in with an invalid password.
This transient condition does not result in a standing condition.
4.3.20 IOSCFG-COPY-FAIL
The Cisco 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 4-9, but the IOSCFG-COPY-FAIL condition applies to ML-Series Ethernet cards rather than the TCC2/TCC2P card.
4.3.21 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.
4.3.22 LOGIN-FAIL-ONALRDY
The Security: Invalid Login-Already 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.
4.3.23 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.
4.3.24 LOGIN-FAILURE-USERID
The Invalid Login-Username (LOGIN-FAILURE-USERID) condition occurs when a user login (CTC, Cisco Transport Manager [CTM], or TL1) 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.
4.3.25 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.
4.3.26 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 or card and the working port or card is already active.
This transient condition does not result in a standing condition.
4.3.27 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 or card and the protect port or card is already active.
This transient condition results in a BLSR or MSSP Manual Switch (Span or Ring) standing condition.
4.3.28 MSSP-RESYNC
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.
4.3.29 PM-TCA
The Performance Monitoring Threshold Crossing Alert (PM-TCA) condition occurs when network collisions cross the rising threshold for the first time.
4.3.30 PS
The Protection Switch (PS) condition occurs when traffic switches from a working/active card to a protect/standby card.
4.3.31 RMON-ALARM
The Remote Monitoring Threshold Crossing Alarm (RMON-ALARM) condition occurs when the remote monitoring (RMON) variable crosses the threshold.
4.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 RMON must restart. It can also occur when you reset a card.
4.3.33 SESSION-TIME-LIMIT
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.
4.3.34 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. See the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section on page xxxiii for details.
4.3.35 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, Obtaining Support, and Security Guidelines" section on page xxxiii for details.
4.3.36 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.
4.3.37 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.
4.3.38 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.
4.3.39 WKSWBK
The Switched Back to Working (WKSWBK) condition occurs when traffic switches back to the working port or card in a nonrevertive protection group.
This transient condition does not result in a standing condition.
4.3.40 WKSWPR
The Switched to Protection (WKSWPR) condition occurs when traffic switches to the protect port or card in a nonrevertive protection group.
This transient condition does not result in a standing condition.
4.3.41 WRMRESTART
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 TCC2/TCC2P card is powered up. The condition changes to COLD-START if the TCC2/TCC2P card is restarted from a physical reseat or a power loss.
4.3.42 WTR-SPAN
The Span is in Wait To Restore State (WTR-SPAN) condition occurs when a BLSR or MS-SPRing switches to another span due to a Signal Failure-Span command or a fiber is pulled from a four-fiber BLSR/MS-SPRing configuration. The condition is raised until the WaitToRestore (WTR) period expires.
This transient condition clears when the BLSR/MS-SPRing returns to a normal condition or the IDLE state.
Posted: Mon Oct 29 01:43:27 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
