Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, Release 8.5
Chapter 3, Transient Conditions
Downloads: This chapterpdf (PDF - 403.0KB) The complete bookPDF (PDF - 7.9MB) | Feedback

Transient Conditions

Table Of Contents

Transient Conditions

3.1  Transients Indexed By Alphabetical Entry

3.2  Trouble Notifications

3.2.1  Condition Characteristics

3.2.2  Condition States

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  DBBACKUP-FAIL

3.3.10  DBRESTORE-FAIL

3.3.11  EFM-ERR-FRM

3.3.12  EFM-FRM-PER

3.3.13  EFM-FRM-SEC

3.3.14  EFM-RLBK-FAIL

3.3.15  EFM-SYM-PER

3.3.16  FIREWALL-DIS

3.3.17  FRCDWKSWBK-NO-TRFSW

3.3.18  FRCDWKSWPR-NO-TRFSW

3.3.19  INTRUSION

3.3.20  INTRUSION-PSWD

3.3.21  LOGIN-FAIL-LOCKOUT

3.3.22  LOGIN-FAIL-ONALRDY

3.3.23  LOGIN-FAILURE-PSWD

3.3.24  LOGIN-FAILURE-USERID

3.3.25  LOGOUT-IDLE-USER

3.3.26  MANWKSWBK-NO-TRFSW

3.3.27  MANWKSWPR-NO-TRFSW

3.3.28  PM-TCA

3.3.29  PS

3.3.30  RMON-ALARM

3.3.31  RMON-RESET

3.3.32  SESSION-TIME-LIMIT

3.3.33  SFTWDOWN-FAIL

3.3.34  USER-LOCKOUT

3.3.35  USER-LOGIN

3.3.36  USER-LOGOUT

3.3.37  WORK-QUEUE-FULL

3.3.38  WKSWBK

3.3.39  WKSWPR

3.3.40  WRMRESTART


Transient Conditions


This chapter gives a description, entity, Simple Network Management Protocol (SNMP) number, and SNMP trap for each commonly encountered Cisco ONS 15310-CL and Cisco ONS 15310-MA transient condition.

3.1  Transients Indexed By Alphabetical Entry

Table 3-1 alphabetically lists all ONS 15310-CL and ONS 15310-MA 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.


Table 3-1 ONS 15310-CL and ONS 15310-MA Transient Condition Alphabetical List 

Transient Condition
Entity
SNMP Number
SNMP Trap

ADMIN-DISABLE

NE

5270

disableInactiveUser

ADMIN-DISABLE-CLR

NE

5280

disableInactiveClear

ADMIN-LOCKOUT

NE

5040

adminLockoutOfUser

ADMIN-LOCKOUT-CLR

NE

5050

adminLockoutClear

ADMIN-LOGOUT

NE

5020

adminLogoutOfUser

ADMIN-SUSPEND

NE

5340

suspendUser

ADMIN-SUSPEND-CLR

NE

5350

suspendUserClear

AUD-ARCHIVE-FAIL

EQPT

6350

archiveOfAuditLogFailed

DBBACKUP-FAIL

EQPT

3724

databaseBackupFailed

DBRESTORE-FAIL

EQPT

3726

databaseRestoreFailed

EFM-ERR-FRM

ML100T, ML1000, MLFX, ML2

6800

efmLinkMonitoringErroredFrameEvent

EFM-FRM-PER

ML100T, ML1000, MLFX, ML2

6810

efmLinkMonitoringErroredFramePeriodEvent

EFM-FRM-SEC

ML100T, ML1000, MLFX, ML2

6820

efmLinkMonitoringErroredFrameSecondsSummary

EFM-RLBK-FAIL

ML100T, ML1000, MLFX, ML2

6830

efmRemoteLoopbackRequestFailed

EFM-SYM-PER

ML100T, ML1000, MLFX, ML2

6790

efmLinkMonitoringErroredSymbolPeriodEvent

FIREWALL-DIS

NE

5230

firewallHasBeenDisabled

FRCDWKSWBK-NO-TRFSW

OCN

5560

forcedSwitchBackToWorkingResultedInNoTraffic
Switch

FRCDWKSWPR-NO-TRFSW

OCn

5550

forcedSwitchToProtectResultedInNoTrafficSwitch

INTRUSION

NE

5250

securityIntrusionDetUser

INTRUSION-PSWD

NE

5240

securityIntrusionDetPwd

LOGIN-FAIL-LOCKOUT

NE

5080

securityInvalidLoginLockedOutSeeAuditLog

LOGIN-FAIL-ONALRDY

NE

5090

securityInvalidLoginAlreadyLoggedOnSeeAuditLog

LOGIN-FAILURE-PSWD

NE

5070

securityInvalidLoginPasswordSeeAuditLog

LOGIN-FAILURE-USERID

NE

3722

securityInvalidLoginUsernameSeeAuditLog

LOGOUT-IDLE-USER

5110

automaticLogoutOfIdle
User

MANWKSWBK-NO-TRFSW

OCN

5540

manualSwitchBackToWorkingResultedInNoTraffic
Switch

MANWKSWPR-NO-TRFSW

OCN

5530

manualSwitchToProtectResultedInNoTrafficSwitch

PM-TCA

2120

performanceMonitorThresholdCrossingAlert

PS

EQPT

2130

protectionSwitch

RMON-ALARM

2720

rmonThresholdCrossing
Alarm

RMON-RESET

2710

rmonHistoriesAndAlarms
ResetReboot

SESSION-TIME-LIMIT

NE

6270

sessionTimeLimitExpired

SFTWDOWN-FAIL

EQPT

3480

softwareDownloadFailed

USER-LOCKOUT

NE

5030

userLockedOut

USER-LOGIN

NE

5100

loginOfUser

USER-LOGOUT

NE

5120

logoutOfUser

WORK-QUEUE-FULL

EQPT

   

WKSWBK

EQPT, OCN

2640

switchedBackToWorking

WKSWPR

2R, TRUNK, EQPT, ESCON, FC, GE, ISC, OCN, STSMON, VT-MON

2650

switchedToProtection

WRMRESTART

NE

2660

warmRestart


3.2  Trouble Notifications

The ONS 15310-CL and ONS 15310-MA systems report trouble by using standard condition characteristics that follow the rules in Telcordia GR-253 and graphical user interface (GUI) state indicators.

The ONS 15310-CL and ONS 15310-MA use 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 ONS 15310-CL and ONS 15310-MA shelves. 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 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 8.5. 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 AuditLog 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 using the correct user name, password, and FTP server details.

This transient condition does not lead to a standing condition.

3.3.9  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.10  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.

3.3.11  EFM-ERR-FRM

The EFM Link Monitoring - Errored Frame Event condition occurs when the number of error frames detected on the remote NE crosses the configured threshold for a configured period or time interval, and the remote NE notifies the local NE of the threshold crossing.

This transient condition does not result in a standing condition.

3.3.12  EFM-FRM-PER

The EFM Link Monitoring - Errored Frame Period Event condition occurs if the remote NE detects a specified number of errored frames which is above a configured threshold for a configured period (which is number of received frames). If so, the remote NE notifies the local NE of the exceeded threshold. This event is intended to notify user interfaces on the local NE.

3.3.13  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 for a configured period or time interval. The remote NE notifies the local NE of the threshold crossing.

3.3.14  EFM-RLBK-FAIL

The EFM - Remote Loopback Request Failed condition occurs when a prior 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 the local NE about the failure.

This transient condition does not result in a standing condition.

3.3.15  EFM-SYM-PER

The EFM Link Monitoring - Errored Symbol Period Event condition occurs when the symbol errors detected at the remote NE crosses a configured threshold. This condition notifies the user on the local NE of this state.

This transient condition does not result in a standing condition.

3.3.16  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.17  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.

3.3.18  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.19  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.

3.3.20  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.

3.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.

3.3.22  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.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.

3.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.

3.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.

3.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/card and the working port/ card is already active.

This transient condition does not result in a standing condition.

3.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/card and the protect port/card is already active.

This transient condition does not result in a standing condition.

3.3.28  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.29  PS

The Protection Switch (PS) condition occurs when the traffic switches from a working/active card to a protect/standby card.

3.3.30  RMON-ALARM

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

3.3.31  RMON-RESET

The RMON Histories and Alarms Reset Reboot (RMON-RESET) condition occurs when the time-of-day settings on the 15310-CL-CTX or CTX2500 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.

3.3.32  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.

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.

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) condition 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  WORK-QUEUE-FULL

The Work Queue Full(WORK-QUEUE-FULL) condition occurs when the netTask Queue in VxWorks has filled up and task operations for the card are postponed.

This transient condition does not result in a standing condition.

3.3.38  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.39  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.

3.3.40  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 database-restore and IP changes, or 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 15310-CL-CTX or CTX2500 card is powered up. The condition changes to COLD-START if the 15310-CL-CTX or CTX2500 card is restarted from a power loss.