SYSTEM
mdCommitInProgress
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2120 |
Event name | mdCommitInProgress |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
Commit by $userName$ ($interface$) from $srcAddr$ is taking longer than expected - $reason$. |
Cause | The mdCommitInProgress event is generated when a commit that is in progress on a model-driven interface is taking longer than expected to finish. |
Effect | Additional commands may not be entered while the commit is in progress, and the session that issued the commit will wait until it finishes. |
Recovery | No recovery is necessary. |
mdCommitSucceeded
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2121 |
Event name | mdCommitSucceeded |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
Commit to $regionName$ by $userName$ ($interface$) from $srcAddr$ succeeded. |
Cause | The mdCommitSucceeded event is generated when a commit succeeded. |
Effect | The commit succeeded. |
Recovery |
No recovery is necessary. |
mdSaveCommitHistoryFailed
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2087 |
Event name | mdSaveCommitHistoryFailed |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.91 |
Default severity | major |
Source stream |
main |
Message format string | $regionName$ commit history file write failed: $fileName$ |
Cause | Saving the commit history file failed because of an error. |
Effect | The commit history file was not saved. |
Recovery | Identify the cause of the failure and save the configuration to save the commit history. |
persistenceRestoreProblem
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2041 |
Event name | persistenceRestoreProblem |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.41 |
Default severity |
minor |
Source stream | main |
Message format string | Problem occurred while processing persistence record for $tmnxPersistencyClient$ - $tmnxPersistencyNotifyMsg$ |
Cause | The persistenceRestoreProblem notification is generated when an error is detected while processing a persistence record. |
Effect | N/A |
Recovery | N/A |
persistencyClosedAlarmCleared
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2031 |
Event name | persistencyClosedAlarmCleared |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.31 |
Default severity |
major |
Source stream | main |
Message format string | Persistency-file on Card $tmnxPersistenceAffectedCpm$ for $tmnxPersistencyClient$ on device $tmnxPersistencyFileLocator$ is re-opened.$tmnxPersistencyNotifyMsg$ |
Cause | The output device used to store the persistence data is available for use again. |
Effect | N/A |
Recovery | N/A |
persistencyClosedAlarmRaised
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2030 |
Event name | persistencyClosedAlarmRaised |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.30 |
Default severity |
major |
Source stream | main |
Message format string | Persistency-file on Card $tmnxPersistenceAffectedCpm$ for $tmnxPersistencyClient$ on device $tmnxPersistencyFileLocator$ is closed. Persistency across system reboot is no longer guaranteed. $tmnxPersistencyNotifyMsg$ |
Cause | The system was unable to store persistency data (e.g. because the storage device is inaccessible, or full)." |
Effect | N/A |
Recovery | N/A |
persistencyEventReport
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2037 |
Event name | persistencyEventReport |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.37 |
Default severity |
warning |
Source stream | main |
Message format string | persistency event: $tmnxPersistencyNotifyMsg$ |
Cause | The system reported a subscriber management persistence event (e.g. the start and completion of a recovery action after system startup). |
Effect | N/A |
Recovery | N/A |
persistencyFileSysThresCleared
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2051 |
Event name | persistencyFileSysThresCleared |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.51 |
Default severity |
major |
Source stream | main |
Message format string | Filesystem on Card $tmnxPersistenceAffectedCpm$ for $tmnxPersistencyClient$ on device $tmnxPersistencyFileLocator$ has dropped below threshold level of 90 percent. $tmnxPersistencyNotifyMsg$ |
Cause | The persistencyFileSysThresCleared notification is generated when the filesystem drops below 90 percent occupation. |
Effect | N/A |
Recovery | N/A |
persistencyFileSysThresRaised
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2050 |
Event name | persistencyFileSysThresRaised |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.50 |
Default severity |
major |
Source stream | main |
Message format string | Filesystem on Card $tmnxPersistenceAffectedCpm$ for $tmnxPersistencyClient$ on device $tmnxPersistencyFileLocator$ has reached threshold level of 90 percent. $tmnxPersistencyNotifyMsg$ |
Cause | The persistencyFileSysThresRaised notification is generated when the filesystem reaches 90 percent occupation. |
Effect | N/A |
Recovery | N/A |
sbiBootConfig
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2004 |
Event name | sbiBootConfig |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.4 |
Default severity |
major |
Source stream | main |
Message format string | Bootup configuration complete. Configuration status: $sbiConfigStatus$. SNMP Persistent Indexes status: $sbiPersistStatus$. System configured with persistent indexes: $sbiPersistIndex$. |
Cause | The configuration phase following a system reboot has completed. |
Effect | N/A |
Recovery | No recovery is necessary. |
sbiBootConfigFailFileError
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2038 |
Event name | sbiBootConfigFailFileError |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.38 |
Default severity |
major |
Source stream | main |
Message format string | Unable to access the boot-bad-exec file $sbiBootConfigFailScript$ |
Cause | The bootup failed script file is not accessible. |
Effect | N/A |
Recovery | No recovery is necessary. |
sbiBootConfigOKFileError
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2039 |
Event name | sbiBootConfigOKFileError |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.39 |
Default severity |
major |
Source stream | main |
Message format string | Unable to access the boot-good-exec file $sbiBootConfigOKScript$ |
Cause | The bootup configuration OK script file was not accessible. |
Effect | N/A |
Recovery | No recovery is necessary. |
sbiBootMdReadCommitHistoryFailed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2088 |
Event name | sbiBootMdReadCommitHistoryFailed |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.92 |
Default severity |
major |
Source stream | main |
Message format string | $regionName$ commit history file read failed: $fileName$ |
Cause | Reading the commit history file failed because of an error. |
Effect | The commit history file was not read. |
Recovery |
Identify the cause of the failure and reboot the system. |
sbiBootSnmpd
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2005 |
Event name | sbiBootSnmpd |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.5 |
Default severity |
major |
Source stream | main |
Message format string | SNMP daemon initialization complete. System configured with persistent SNMP indexes: $sbiPersistIndex$. SNMP daemon administrative status: $sbiSnmpdAdminStatus$. SNMP daemon operational status: $sbiSnmpdOperStatus$. |
Cause | The SNMP daemon initialization completed following a system reboot. Some system configuration and initialization errors might have resulted in the SNMP daemon being suspended. |
Effect | N/A |
Recovery | No recovery is necessary. |
schedActionFailure
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2101 |
Event name | schedActionFailure |
SNMP notification prefix and OID |
DISMAN-SCHEDULE-MIB.schedTraps.1 |
Default severity | major |
Source stream | main |
Message format string |
Schedule "$schedName$" created by "$schedOwner$" failed with error: $schedFailureText$ |
Cause | The invocation of a scheduled script-policy failed. |
Effect | N/A |
Recovery | N/A |
smScriptAbort
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2102 |
Event name | smScriptAbort |
SNMP notification prefix and OID |
DISMAN-SCRIPT-MIB.smTraps.1 |
Default severity | major |
Source stream | main |
Message format string |
The $tmnxSmRunExtAuthType$ operation failed or was aborted with error: $smRunError$. Run # $smRunIndex$ of script-policy "$smLaunchName$" created by owner "$smLaunchOwner$" was executed with the user account " $tmnxSmRunExtUserName$". |
Cause | A running script terminated with an smRunExitCode not equal to `noError'. |
Effect | N/A |
Recovery | N/A |
smScriptException
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2104 |
Event name | smScriptException |
SNMP notification prefix and OID |
DISMAN-SCRIPT-MIB.smTraps.3 |
Default severity | minor |
Source stream | main |
Message format string |
The $tmnxSmRunExtAuthType$ operation completed with an exception: $smRunError$. Run #$smRunIndex$ of script-policy " $smLaunchName$" created by owner "$smLaunchOwner$" was executed with the user account "$tmnxSmRunExtUserName$" |
Cause | A script run completed with an error. This event can be used by scripts to notify other management applications about script errors. This event is not automatically generated by the Script MIB implementation. It is the responsibility of the executing script or the runtime system to emit this notification where it is appropriate to do so. |
Effect | N/A |
Recovery | N/A |
smScriptResult
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2103 |
Event name | smScriptResult |
SNMP notification prefix and OID | DISMAN-SCRIPT-MIB.smTraps.2 |
Default severity | minor |
Source stream |
main |
Message format string | The $tmnxSmRunExtAuthType$ operation completed with the result: $smRunResult$. Run #$smRunIndex$ of script-policy "$smLaunchName$" created by owner "$smLaunchOwner$" was executed with the user account " $tmnxSmRunExtUserName$". |
Cause | A script run completed. This event can be used by scripts to notify other management applications about results \ produced by the script. This event is not automatically generated by the Script MIB implementation. It is the responsibility of the executing script to emit this notification where it is appropriate to do so. |
Effect | N/A |
Recovery | N/A |
sntpTimeDiffExceedsThreshold
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2018 |
Event name | sntpTimeDiffExceedsThreshold |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.18 |
Default severity |
major |
Source stream | main |
Message format string | Time differential between the SNTP server $sntp_ip_address$ and the system exceeds 10 seconds |
Cause | The time differential between the system and the SNTP server was more than 10 seconds. In this case the system clock was not automatically adjusted. |
Effect | N/A |
Recovery | N/A |
socket_bind_failed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2016 |
Event name | socket_bind_failed |
SNMP notification prefix and OID |
N/A |
Default severity | critical |
Source stream | main |
Message format string |
Could not bind to a socket |
Cause | A socket bind failed. There may be no sockets left in the system. |
Effect | Cannot start new telnet/ftp sessions. |
Recovery |
Shutdown tasks that are consuming sockets. |
socket_conn_accept_failed
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2017 |
Event name | socket_conn_accept_failed |
SNMP notification prefix and OID | N/A |
Default severity |
critical |
Source stream | main |
Message format string | Could not accept a new connection |
Cause | A socket connection attempt failed. There may be no sockets left in the system. |
Effect | Cannot start new telnet/ftp sessions. |
Recovery |
Shutdown tasks that are consuming sockets. |
ssiSaveBackgroundConfigFailed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2113 |
Event name | ssiSaveBackgroundConfigFailed |
SNMP notification prefix and OID |
N/A |
Default severity | major |
Source stream | main |
Message format string |
Complete configuration file background write failed: $fileName$ $reason$ |
Cause | A background complete configuration save was initiated by the system to aggregate incremental saved configuration file. |
Effect | The complete configuration file could not be saved. |
Recovery | Identify the cause of the failure and save the configuration. |
ssiSaveBackgroundConfigSucceeded
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2112 |
Event name | ssiSaveBackgroundConfigSucceeded |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
Complete configuration file saved in the background to: $fileName$ |
Cause | A background complete configuration save was initiated by the system to aggregate incremental saved configuration files. |
Effect | The complete configuration file was saved. |
Recovery | No recovery is necessary. |
ssiSaveConfigFailed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2003 |
Event name | ssiSaveConfigFailed |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.3 |
Default severity |
major |
Source stream | main |
Message format string | Configuration file write failed: $fileName$ $reason$ |
Cause | Saving the configuration failed because of an error. |
Effect | The configuration was not saved. |
Recovery |
Identify the cause of the failure and save the configuration. |
ssiSaveConfigSucceeded
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2002 |
Event name | ssiSaveConfigSucceeded |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.2 |
Default severity |
warning |
Source stream | main |
Message format string | Configuration file saved to: $fileName$ |
Cause | Saving the configuration succeeded. |
Effect |
The configuration was saved. |
Recovery | No recovery is necessary. |
ssiSaveIncrementConfigFailed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2111 |
Event name | ssiSaveIncrementConfigFailed |
SNMP notification prefix and OID |
N/A |
Default severity | major |
Source stream | main |
Message format string |
Incremental configuration file write failed: $fileName$ $reason$ |
Cause | An incremental configuration save was initiated. |
Effect | The incremental configuration file could not be saved. |
Recovery | Identify the cause of the failure and save the configuration. |
ssiSaveIncrementConfigSucceeded
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2110 |
Event name | ssiSaveIncrementConfigSucceeded |
SNMP notification prefix and OID |
N/A |
Default severity | warning |
Source stream | main |
Message format string |
Incremental configuration file saved to: $fileName$ |
Cause |
An incremental configuration save was initiated. |
Effect |
The incremental configuration file was saved. |
Recovery | No recovery is necessary. |
ssiSyncBootEnvFailed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2015 |
Event name | ssiSyncBootEnvFailed |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.17 |
Default severity |
critical |
Source stream | main |
Message format string | Synchronization of boot environment files failed - $tmnxSyncFailureReason$ |
Cause | The synchronization of boot environment files was stopped due to errors. |
Effect | Boot environment files were not synchronized. |
Recovery | No recovery is necessary. |
ssiSyncBootEnvOK
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2014 |
Event name | ssiSyncBootEnvOK |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.16 |
Default severity |
warning |
Source stream | main |
Message format string | Boot environment files have been successfully synchronized |
Cause | The synchronization of boot environment files finished without errors. |
Effect | Boot environment files were synchronized. |
Recovery | No recovery is necessary. |
ssiSyncCertFailed
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2049 |
Event name | ssiSyncCertFailed |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.49 |
Default severity |
major |
Source stream | main |
Message format string | Synchronization of certificate file(s) failed - $tmnxSyncFailureReason$ |
Cause | The ssiSyncCertFailed event is generated when the synchronization of certificate files between the primary and secondary CPMs is stopped due to errors. The tmnxSyncFailureReason will state the reason for the failure. |
Effect | Cert files are not synchronized. |
Recovery |
The user should try to determine the cause of the failure and can attempt synchronizing the files again. |
ssiSyncCertOK
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2048 |
Event name | ssiSyncCertOK |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.48 |
Default severity |
warning |
Source stream | main |
Message format string | Cert file(s) have been successfully synchronized |
Cause | The ssiSyncCertOK event is generated when the synchronization of certificate files between the primary and secondary CPMs finishes without errors. |
Effect | Cert files are synchronized. |
Recovery |
No recovery is necessary. |
ssiSyncConfigFailed
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2013 |
Event name | ssiSyncConfigFailed |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.15 |
Default severity | critical |
Source stream |
main |
Message format string | Synchronization of configuration files failed - $tmnxSyncFailureReason$ |
Cause | The synchronization of configuration files was stopped due to errors. |
Effect | Configuration files were not synchronized. |
Recovery | No recovery is necessary. |
ssiSyncConfigOK
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2012 |
Event name | ssiSyncConfigOK |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.14 |
Default severity | warning |
Source stream |
main |
Message format string | Configuration files have been successfully synchronized |
Cause | The synchronization of configuration files finished without errors. |
Effect | Configuration files are synchronized. |
Recovery |
No recovery is necessary. |
ssiSyncRollbackFailed
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2047 |
Event name | ssiSyncRollbackFailed |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.47 |
Default severity | critical |
Source stream |
main |
Message format string | Synchronization of rollback file(s) failed - $tmnxSyncFailureReason$ |
Cause | The ssiSyncRollbackFailed event is generated when the synchronization of rollback files between the primary and secondary CPMs is stopped due to errors. The tmnxSyncFailureReason will state the reason for the failure. |
Effect | Rollback files are not synchronized. |
Recovery |
The user should try to determine the cause of the failure and can attempt synchronizing the files again. |
ssiSyncRollbackOK
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2046 |
Event name | ssiSyncRollbackOK |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.46 |
Default severity |
warning |
Source stream | main |
Message format string | Rollback file(s) have been successfully synchronized |
Cause | The ssiSyncRollbackOK event is generated when the synchronization of rollback files between the primary and secondary CPMs finishes without errors. |
Effect | Rollback files are synchronized. |
Recovery |
No recovery is necessary. |
stiDateAndTimeChanged
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2001 |
Event name | stiDateAndTimeChanged |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.1 |
Default severity | warning |
Source stream |
main |
Message format string | Date and time on the system is $stiDateAndTime$ |
Cause | The stiDateAndTimeChanged notification is generated when the time on the system is explicitly set. |
Effect | The time on the system has been modified. |
Recovery | No recovery is necessary. |
stiDateAndTimeChanging
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2081 |
Event name | stiDateAndTimeChanging |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.86 |
Default severity |
warning |
Source stream | main |
Message format string | Date and time on the system is changing from $stiDateAndTime$ |
Cause | The stiDateAndTimeChanging notification is generated when the time on the node is explicitly set. It is raised before the time is changed so that the time of the change can be related to the original timescale. It shall be followed by the stiDateAndTimeChanged notification. |
Effect | The time on the system is being changed. |
Recovery | No recovery is necessary. |
tMirrorLiXIfLicenseInvalid
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2086 |
Event name | tMirrorLiXIfLicenseInvalid |
SNMP notification prefix and OID |
TIMETRA-MIRROR-MIB.tMirrorNotifications.30 |
Default severity |
minor |
Source stream | main |
Message format string | TCP LI license invalid; please remove x-interface configuration$tMirrorLiNotifyLongDescription$ |
Cause | The system sends a tMirrorLiXIfLicenseInvalid notification when x-interfaces configuration is made while the system license does not support such configuration. |
Effect | The values of the objects tMirrorLiX1OperState, tMirrorLiX1OperState and tMirrorLiX1OperState remain 'outOfService'. |
Recovery | Remove any X-interfaces configuration. |
tmnxConfigConflict
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2058 |
Event name | tmnxConfigConflict |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.58 |
Default severity |
warning |
Source stream | main |
Message format string | $tmnxNotifyObjectName$ configuration conflict |
Cause | A configuration attribute associated with a row entry in a MIB table is in conflict with another attribute. This event can be used by the NMS to trigger maintenance polls of the configuration information. |
Effect | N/A |
Recovery | No recovery is necessary. |
tmnxConfigCreate
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2007 |
Event name | tmnxConfigCreate |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.9 |
Default severity |
warning |
Source stream | change |
Message format string | $tmnxNotifyObjectName$ managed object created |
Cause | A new row entry was created in one of the MIB tables. This event can be used by an NMS to trigger maintenance polls of the configuration information. Although this log event is primarily associated with classic management interfaces (for example, Classic CLI or SNMP), it is also generated when configuration changes are committed using model driven interfaces (for example, MD-CLI or NETCONF). |
Effect | N/A |
Recovery | No recovery is necessary. |
tmnxConfigDelete
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2008 |
Event name | tmnxConfigDelete |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.10 |
Default severity |
warning |
Source stream | change |
Message format string | $tmnxNotifyObjectName$ managed object deleted |
Cause | A existing row entry in one of the MIB tables was deleted. This event can be used by an NMS to trigger maintenance polls of the configuration information. Although this log event is primarily associated with classic management interfaces (for example, Classic CLI or SNMP), it is also generated when configuration changes are committed using model driven interfaces (for example, MD-CLI or NETCONF). |
Effect | N/A |
Recovery | No recovery is necessary. |
tmnxConfigModify
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2006 |
Event name | tmnxConfigModify |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.8 |
Default severity |
warning |
Source stream | change |
Message format string | $tmnxNotifyObjectName$ configuration modified |
Cause | A configuration attribute associated with a row entry in a MIB table was modified. This event can be used by an NMS to trigger maintenance polls of the configuration information. Although this log event is primarily associated with classic management interfaces (for example, Classic CLI or SNMP), it is also generated when configuration changes are committed using model driven interfaces (for example, MD-CLI or NETCONF). |
Effect | N/A |
Recovery | No recovery is necessary. |
tmnxEhsDroppedByMinDelay
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2070 |
Event name | tmnxEhsDroppedByMinDelay |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.71 |
Default severity |
minor |
Source stream | main |
Message format string | The $tmnxSmRunExtAuthType$ operation failed with a min delay violation error: Mindelay = $tmnxEhsHEntryMinDelay$ is greater than Mindelay Interval: $tmnxEhsHEntryMinDelayInterval$. The script policy " $tmnxEhsHEntryScriptPlcyName$" created by the owner "$tmnxEhsHEntryScriptPlcyOwner$" was executed with cli-user account " $tmnxSmRunExtUserName$". |
Cause | The tmnxEhsDroppedByMinDelay is generated when two consecutive executions of script policy specified by this Ehs event handler entry occurs within the time period specified by tmnxEhsHEntryMinDelay. |
Effect | The value of tmnxEhsHEntryStatsErrMinDelay gets incremented. Execution of the script policy stops. |
Recovery | No recovery is necessary. |
tmnxEhsHandlerInvoked
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2069 |
Event name | tmnxEhsHandlerInvoked |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.70 |
Default severity |
minor |
Source stream | main |
Message format string | Ehs handler :"$tmnxEhsHandlerName$" with the description : " $tmnxEhsHandlerDescription$" was invoked by the cli-user account "$tmnxSmRunExtUserName$". |
Cause | The tmnxEhsHandlerInvoked notification is generated when the log event for a particular application-id and event-id/event name invokes EHS and creates a run Entry. |
Effect | EHS might create a run entry to execute scripts. |
Recovery | No recovery is necessary. |
tmnxFtpClientFailure
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2034 |
Event name | tmnxFtpClientFailure |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.34 |
Default severity |
minor |
Source stream | main |
Message format string | Ftp client operation for destination $tmnxFtpFailureDestAddress$ failed with error message $tmnxFtpFailureMsg$ |
Cause | A file transfer operation initiated by the FTP client failed. |
Effect | N/A |
Recovery | N/A |
tmnxLastSystemRebootAdmin
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2114 |
Event name | tmnxLastSystemRebootAdmin |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.74 |
Default severity |
minor |
Source stream | main |
Message format string | A reboot was administratively triggered at $tmnxLastSystemRebootTime$ by user $tmnxLastSystemRebootUser$ from $tmnxLastSystemRebootUserAddress$ |
Cause |
The tmnxLastSystemRebootAdmin notification is generated when the reason for the last system reboot (as indicated by tmnxLastSystemRebootReason) was 'admin (1)'. |
Effect | No effect. |
Recovery |
No recovery is necessary. |
tmnxModuleMallocFailed
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2010 |
Event name | tmnxModuleMallocFailed |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.12 |
Default severity | major |
Source stream |
main |
Message format string | Memory allocation request for $tmnxModuleMallocSize$ bytes from module $tmnxMemoryModule$ failed |
Cause |
A request to allocate memory from a particular module failed because the memory module was short on memory and could not support the size that was requested. |
Effect | N/A |
Recovery | N/A |
tmnxRedCpmActive
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2028 |
Event name | tmnxRedCpmActive |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.28 |
Default severity |
critical |
Source stream | main |
Message format string | New active CPM card $cpmSlotName$ is ready to accept CLI configuration commands and SNMP SET requests. |
Cause | Following a redundancy switchover the new active CPM has completed its audit and is ready to accept management commands via CLI or SNMP SET requests. |
Effect | N/A |
Recovery | N/A |
tmnxRedSingleCpm
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2029 |
Event name | tmnxRedSingleCpm |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.29 |
Default severity |
critical |
Source stream | main |
Message format string | The active CPM card $cpmSlotName$ is operating in singleton mode. There is no standby CPM card. |
Cause | In a system with a chassis with two CPM slots the active CPM could not detect a standby CPM in the chassis. When the operating state of TIMETRA-CHASSIS-MIB::tmnxCpmCardRedundant for the active CPM card transitions to a value of 'singleton (1)', this event is generated. When the active CPM later detects a standby CPM in the chassis, the ssiRedStandbySyncing event will be generated followed by a ssiRedStandbyReady event to indicate clearing of the CPM singleton state. The value of tmnxCpmCardRedundant will then transition to 'redundantActive (2)'." |
Effect | N/A |
Recovery | N/A |
tmnxRedStandbyReady
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2025 |
Event name | tmnxRedStandbyReady |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.25 |
Default severity |
major |
Source stream | main |
Message format string | Redundancy synchronization with standby CPM card $cpmSlotName$ has completed. Standby CPM is ready. |
Cause | The synchronization of redundancy information onto the standby CPM has completed. |
Effect | The standby CPM is now ready to take over control of the system if the active CPM fails or a manual switchover command is issued. |
Recovery | N/A |
tmnxRedStandbySyncing
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2024 |
Event name | tmnxRedStandbySyncing |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.24 |
Default severity | major |
Source stream |
main |
Message format string | Redundancy synchronization with standby CPM card $cpmSlotName$ is in progress. |
Cause | Synchronization of redundancy information onto the standby CPM was started. tmnxChassisNotifyHwIndex identifies the standby CPM. |
Effect | N/A |
Recovery | N/A |
tmnxRedStandbySyncLost
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2026 |
Event name | tmnxRedStandbySyncLost |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.26 |
Default severity |
critical |
Source stream | main |
Message format string | Redundancy synchronization with standby CPM card $cpmSlotName$ has been lost. |
Cause | The active CPM lost communication with the standby CPM. |
Effect | N/A |
Recovery | N/A |
tmnxRedSwitchover
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2027 |
Event name | tmnxRedSwitchover |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.27 |
Default severity |
critical |
Source stream | main |
Message format string | Redundancy switchover from CPM card $cpmSlotName$ because $ssiRedFailoverReason$. |
Cause | The standby CPM detected that the active CPM has failed. |
Effect | The standby CPM prepared to take over as the new active CPM. |
Recovery | N/A |
tmnxSmLaunchStartFailed
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2068 |
Event name | tmnxSmLaunchStartFailed |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.69 |
Default severity | minor |
Source stream |
main |
Message format string | Launch of $tmnxSmRunExtAuthType$ operation failed with error: $smLaunchError$. The script policy "$tmnxEhsHEntryScriptPlcyName$" created by the owner "$tmnxEhsHEntryScriptPlcyOwner$" was executed with cli-user account " $tmnxSmRunExtUserName$" |
Cause | The tmnxSmLaunchStartFailed notification is generated when the launch start fails because : 1. The values of smLaunchScriptOwner and smLaunchScriptName don't have an existing entry in the smScriptTable. 2. The value of smScriptOperStatus is not 'enabled'. 3. The smScriptSource value is NULL. 4. The value of smLaunchOperStatus object in smLaunchTable is not 'enabled'. 5. The check to see if the run Index is already in use fails. 6. The number of currently executing scripts invoked from this smLaunchTable entry is greater than smLaunchMaxRunning. |
Effect | The result is indicated by incrementing the value of tmnxEhsHEntryStatsErrLaunch. |
Recovery | No recovery is necessary. |
tmnxSnmpdStateChange
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2023 |
Event name | tmnxSnmpdStateChange |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.23 |
Default severity |
major |
Source stream | main |
Message format string | The SNMP agent has changed state. Administrative state is $sbiSnmpdAdminStatus$ and operational state is $sbiSnmpdOperStatus$. |
Cause | There was a change in either the administrative or operational state of the SNMP agent. |
Effect | N/A |
Recovery | N/A |
tmnxSntpOperChange
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2032 |
Event name | tmnxSntpOperChange |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.32 |
Default severity |
major |
Source stream | main |
Message format string | SNTP's operational status is $sntpOperStatus$ |
Cause | There was a change in the operational state of SNTP. |
Effect | N/A |
Recovery | N/A |
tmnxSssiMismatch
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2022 |
Event name | tmnxSssiMismatch |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.22 |
Default severity |
major |
Source stream | main |
Message format string | Synchronization between CPMs is disabled therefore persistent SNMP index files may not be in sync |
Cause | In a system with redundant CPM cards, upon completion of the bootup configuration synchronization was 'disabled' but the boot options file (bof) specifies the system is to be booted with persistent SNMP indexes. |
Effect | Boot environment files are not synchronized. Following a system failover, SNMP indexes may not have the same values. |
Recovery | Enable synchronization. |
tmnxStateChange
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2009 |
Event name | tmnxStateChange |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.11 |
Default severity | warning |
Source stream |
change |
Message format string | Status of $tmnxNotifyObjectName$ changed administrative state: $tmnxNotifyRowAdminState$, operational state: $tmnxNotifyRowOperState$ |
Cause | A change occurred in either the administrative or operational state of a MIB table entry. |
Effect | N/A |
Recovery | No recovery is necessary. |
tmnxSysAppStats24HrsAvailable
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2071 |
Event name | tmnxSysAppStats24HrsAvailable |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.72 |
Default severity |
warning |
Source stream | main |
Message format string | New rows are available in the tmnxSysAppStats24HrsTable containing values collected at $tmnxSysNotifAppStatsTime$ for application $tmnxSysNotifAppStatsApplication$ type $tmnxSysNotifAppStatsType$ |
Cause | The system generates the tmnxSysAppStats24HrsAvailable notification when new rows are available in the tmnxSysAppStats24HrsTable. The value of tmnxSysNotifAppStatsTime indicates the time the system collected the values in the new rows. A non-zero value of tmnxSysNotifAppStatsApplication indicates the application; a zero value of tmnxSysNotifAppStatsApplication indicates that new values are available for all active applications. A non-zero value of tmnxSysNotifAppStatsType indicates the type of statistics; a zero value of tmnxSysNotifAppStatsType indicates that new values are available for all active types. |
Effect | None. |
Recovery | No recovery is necessary. |
tmnxSysAppStatsWeekAvailable
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2072 |
Event name | tmnxSysAppStatsWeekAvailable |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.73 |
Default severity |
warning |
Source stream | main |
Message format string | New rows are available in the tmnxSysAppStatsWeekTable containing values collected at $tmnxSysNotifAppStatsTime$ |
Cause | The system generates the tmnxSysAppStatsWeekAvailable notification when new rows are available in the tmnxSysAppStatsWeekTable. The value of tmnxSysNotifAppStatsTime indicates the time the system collected the values in the new rows. |
Effect | None. |
Recovery | No recovery is necessary. |
tmnxSysBaseMacAddressNotSet
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2067 |
Event name | tmnxSysBaseMacAddressNotSet |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.68 |
Default severity |
major |
Source stream | main |
Message format string | System base MAC address is not set. Using generated value of $tmnxChassisBaseMacAddress$ which may not be unique. |
Cause | The tmnxSysBaseMacAddressNotSet notification is generated once after the system boots up and the value of sbiSystemBaseMacAddress is all zeroes. |
Effect | The system software is using the base MAC address specified in tmnxChassisBaseMacAddress which may not be unique. |
Recovery | Configure sbiSystemBaseMacAddress to a value other than all zeroes. |
tmnxSysDyingGasp
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2090 |
Event name | tmnxSysDyingGasp |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.93 |
Default severity |
critical |
Source stream | main |
Message format string | System is going down |
Cause |
The tmnxSysDyingGasp notification is sent when the system goes down due to power loss. The system attempts to send this trap using the power remaining in the dying gasp capacitor. |
Effect | System goes down. |
Recovery |
Restore power at site. |
tmnxSysExecFinished
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2053 |
Event name | tmnxSysExecFinished |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.53 |
Default severity | major |
Source stream |
main |
Message format string | Possible messages:
|
Cause | The tmnxSysExecFinished notification is generated upon the completion of the execution of a CLI command file or execution of 'vsd' configuration messages is completed. The value of tmnxSysExecScript indicates the command file when the value of tmnxLogExecRollbackOpType is 'exec' or an empty string when the value of tmnxLogExecRollbackOpType is 'vsd'. The value of tmnxLogExecRollbackOpIndex indicates the row entry in TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this CLI 'exec' or 'vsd' operation. |
Effect | The effect is that the entry for the specified tmnxLogExecRollbackOpIndex won't be updated, and no further notifications will be added to the specified index in the logger. |
Recovery | When the value of tmnxSysExecResult is 'none' or 'success', no recovery is required. When the value is 'fail', the system may be left in an inconsistent state and the user should try to determine the reason for the failure. The user can attempt a recovery by manually entering CLI commands to reverse the failed configuration. The user can attempt a recovery by performing a rollback revert to a known good checkpoint. The user can attempt a recovery by rebooting the system with the bof pointing to a saved configuration file." |
tmnxSysExecStarted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2052 |
Event name | tmnxSysExecStarted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.52 |
Default severity |
major |
Source stream | main |
Message format string | Possible messages:
|
Cause | The tmnxSysExecStarted notification is generated when the user initiates a CLI 'exec' operation to process a file of SROS CLI commands or processing of 'vsd' configuration messages have been initiated. The value of tmnxSysExecScript indicates the command file when the value of tmnxLogExecRollbackOpType is 'exec' or an empty string when the value of tmnxLogExecRollbackOpType is 'vsd'. The value of tmnxLogExecRollbackOpIndex indicates the row entry in TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this CLI 'exec' or 'vsd' operation. |
Effect | All change notifications generated after the generation of this notification and before the tmnxSysExecFinished will be logged in the TIMETRA-LOG-MIB::tmnxLogExecRollbackEventEntry. Once the tmnxSysExecFinished notification is triggered, a Network Management System (NMS) is able to walk the aforementioned log table to retrieve the list of all objects that have been modified during this transaction. |
Recovery | There is no recovery required for this notification. |
tmnxSysHttpRdrOutOfSeqLimitExc
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2091 |
Event name | tmnxSysHttpRdrOutOfSeqLimitExc |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.94 |
Default severity |
warning |
Source stream | main |
Message format string | More than 10 out-of-sequence TCP packets received for TCP connection $tmnxSysAdditionalInfo$ |
Cause | The notification tmnxSysHttpRdrOutOfSeqLimitExc is sent when the value of the object tmnxSysHttpRdrCpmOptimizedMode is equal to 'true' and, for any given HTTP relay TCP connection, the number of - TCP sync packets (receive direction) or - TCP data packets (transmit direction) received out-of-sequence exceeds the limit of 10. |
Effect | The out-of-sequence packets received for that connection are dropped. |
Recovery | The root cause in the network must be found and fixed. |
tmnxSysMgmtIfLiCfgNotEncrypted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2080 |
Event name | tmnxSysMgmtIfLiCfgNotEncrypted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.83 |
Default severity |
minor |
Source stream | main |
Message format string | li.cfg has failed to load at bootup, system expected the li.cfg to be encrypted |
Cause | The tmnxSysMgmtIfLiCfgNotEncrypted notification is generated when the Lawful Intercept (LI) configuration file is not encrypted. |
Effect | The Lawful Intercept (LI) configuration file is not loaded during the boot. |
Recovery | Reboot with the correct Lawful Intercept (LI) configuration file |
tmnxSysMgmtIfLiIncorrectFormat
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2079 |
Event name | tmnxSysMgmtIfLiIncorrectFormat |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.82 |
Default severity |
minor |
Source stream | main |
Message format string | LI config failed to load. The LI config is in the format '$sbiPrimaryConfigFileFormatType' and can only load if it matches the format of the primary configuration file '$sbiLiConfigFileFormatType' |
Cause | The tmnxSysMgmtIfLiIncorrectFormat notification is generated when a format (classic or model-driven) of the Lawful Intercept (LI) configuration file does not match primary configuration file format. |
Effect | The Lawful Intercept (LI) configuration file is not loaded during the boot. |
Recovery | Reboot with the correct Lawful Intercept (LI) configuration file |
tmnxSysMgmtIfModeChangeComplete
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2077 |
Event name | tmnxSysMgmtIfModeChangeComplete |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.79 |
Default severity |
major |
Source stream | main |
Message format string | Management interface configuration mode change to $tmnxSysMgmtIfWriteMode$ has completed. |
Cause | The tmnxSysMgmtIfModeChangeComplete notification is generated when a management interface configuration mode change request is complete. |
Effect | Switching modes between any configuration mode will lock the configuration datastores from operator input until the mode switch has completed. Once this event is triggered the configuration datastores are unlocked for operator input. |
Recovery | None. |
tmnxSysMgmtIfModeChangeFailure
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2078 |
Event name | tmnxSysMgmtIfModeChangeFailure |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.80 |
Default severity |
major |
Source stream | main |
Message format string | Management interface configuration mode change failed. The system is now in $tmnxSysMgmtIfWriteMode$ mode |
Cause | The tmnxSysMgmtIfModeChangeFailure notification is generated when a management interface configuration mode change request fails to complete. |
Effect | Switching modes between any configuration mode will lock the configuration datastores from operator input until the mode switch has completed. When this event is triggered the mode change is declared unsuccessful; the effective configuration mode will be indicated in this notification. The configuration datastores are unlocked for operator input. |
Recovery | None. |
tmnxSysMgmtIfModeChangeStart
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2076 |
Event name | tmnxSysMgmtIfModeChangeStart |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.78 |
Default severity |
major |
Source stream | main |
Message format string | A management interface configuration mode change (reason $tmnxSysMgmtIfWriteSwitchReason$) from $tmnxNotifySysMgmtIfOriginalMode$ to $tmnxSysMgmtIfWriteMode$ was initiated. |
Cause | The tmnxSysMgmtIfModeChangeStart notification is generated when a management interface configuration mode change request is sent. |
Effect | Switching modes between any configuration mode will lock the configuration datastores from operator input until the mode switch has completed. |
Recovery | None. |
tmnxSysNvsysFileError
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2056 |
Event name | tmnxSysNvsysFileError |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.56 |
Default severity | minor |
Source stream |
main |
Message format string | Failure to $tmnxSysFileErrorType$ file $fileName$ |
Cause | The tmnxSysNvsysFileError notification is generated when there is a failure in accessing the nvsys file as specified by tmnxSysFileErrorType. |
Effect | The specified nvsys file operation is unsuccessful. |
Recovery | The user should investigate why the failure occurred. A failure can indicate a problem with the compact flash. |
tmnxSysRollbackDeleteStarted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2055 |
Event name | tmnxSysRollbackDeleteStarted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.55 |
Default severity |
minor |
Source stream | main |
Message format string | Rollback delete of file $fileName$ started |
Cause | The tmnxSysRollbackDeleteStarted notification is generated when the user initiates a rollback delete as specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. |
Effect | The specified configuration file is deleted. |
Recovery | There is no recovery required for this notification. |
tmnxSysRollbackFileDeleteStatus
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2045 |
Event name | tmnxSysRollbackFileDeleteStatus |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.45 |
Default severity |
minor |
Source stream | main |
Message format string | Rollback deletion of file $fileName$ $result$ |
Cause | The tmnxSysRollbackFileDeleteStatus notification is generated upon the completion of a rollback file delete as specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. |
Effect | The result is indicated by the value of tmnxSysRollbackFileDeleteResult. |
Recovery | When the value of tmnxSysRollbackFileDeleteResult is none, inProgress or success no recovery is required. When the value is failed, the user should try to determine the reason for the failure. The user can attempt a recovery by deleting the file again. |
tmnxSysRollbackSaveStarted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2054 |
Event name | tmnxSysRollbackSaveStarted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.54 |
Default severity |
minor |
Source stream | main |
Message format string | Rollback save of file $fileName$ started |
Cause | The tmnxSysRollbackSaveStarted notification is generated when the user initiates a rollback save as specified by tmnxSysRollbackFileType. |
Effect | The specified configuration file is saved. |
Recovery | There is no recovery required for this notification. |
tmnxSysRollbackSaveStatusChange
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2044 |
Event name | tmnxSysRollbackSaveStatusChange |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.44 |
Default severity |
major |
Source stream | main |
Message format string | Rollback save of file $fileName$ $result$ |
Cause | The tmnxSysRollbackSaveStatusChange notification is generated upon the completion of a rollback save as specified by tmnxSysRollbackFileType. |
Effect | The result is indicated by value of tmnxSysRollbackSaveResult. |
Recovery | When the value of tmnxSysRollbackSaveResult is none, inProgress or success no recovery is required. When the value is failed, the user should try to determine the reason for the failure. The user can attempt a recovery by attempting the rollback save again. |
tmnxSysRollbackStarted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2042 |
Event name | tmnxSysRollbackStarted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.42 |
Default severity |
major |
Source stream | main |
Message format string | Rollback revert of file $fileName$ started |
Cause | The tmnxSysRollbackStarted notification is generated when the user initiates a revert of the rollback checkpoint file specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. |
Effect | The specified file is executed and system configuration may change. |
Recovery | There is no recovery required for this notification. |
tmnxSysRollbackStatusChange
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2043 |
Event name | tmnxSysRollbackStatusChange |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.43 |
Default severity |
critical |
Source stream | main |
Message format string | Rollback revert of file $fileName$ $result$ |
Cause | The tmnxSysRollbackStatusChange notification is generated upon the completion of a rollback revert as specified by tmnxSysRollbackIndex and tmnxSysRollbackFileType. |
Effect | The result is indicated by the value of tmnxSysRollbackResult. |
Recovery | When the value of tmnxSysRollbackResult is none, inProgress or success no recovery is required. When the value is failed, the user should try to determine the reason for the failure. The user can attempt a recovery by reverting back to a known good checkpoint. The user may reboot the system with the bof pointing to a saved configuration file. |
tmnxSysSwFabFailRecAborted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2084 |
Event name | tmnxSysSwFabFailRecAborted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.89 |
Default severity |
major |
Source stream | main |
Message format string | Automatic switch fabric failure recovery aborted |
Cause | The tmnxSysSwFabFailRecAborted notification is generated when the automatic switch fabric recovery process was aborted. |
Effect | This may have been due to a problem with one of the SFMs resetting and may have left the router with reduced switch fabric capacity. |
Recovery | Check to ensure all SFMs are fully operational. For any SFMs that are not operational, investigate manual recovery. |
tmnxSysSwFabFailRecCompleted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2083 |
Event name | tmnxSysSwFabFailRecCompleted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.88 |
Default severity |
cleared |
Source stream | main |
Message format string | Automatic switch fabric failure recovery completed |
Cause | The tmnxSysSwFabFailRecCompleted notification is generated when the automatic switch fabric recovery process has completed successfully. |
Effect | The switch fabric has been returned to normal operation. |
Recovery | No recovery is necessary. |
tmnxSysSwFabFailRecDetected
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2085 |
Event name | tmnxSysSwFabFailRecDetected |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.90 |
Default severity |
major |
Source stream | main |
Message format string | Automatic switch fabric failure recovery triggered |
Cause | The tmnxSysSwFabFailRecDetected notification is generated when a condition has been detected within the router that might be resolved by the running of the automatic switch fabric recovery process. |
Effect | If the automatic switch faric recovery process is enabled and all the required prerequisites are met, then the recovery process will start. If the automatic process is enabled but the recovery does not start, then the prerequisite conditions should be checked to determine what needs to be corrected to allow the process to run. |
Recovery | No recovery is necessary. |
tmnxSysSwFabFailRecStarted
Property name | Value |
---|---|
Application name |
SYSTEM |
Event ID | 2082 |
Event name | tmnxSysSwFabFailRecStarted |
SNMP notification prefix and OID |
TIMETRA-SYSTEM-MIB.tmnxSysNotifications.87 |
Default severity |
major |
Source stream | main |
Message format string | Automatic switch fabric failure recovery started |
Cause | The tmnxSysSwFabFailRecStarted notification is generated when the router has initiated an automatic switch fabric recovery process based on detecting frequent failures to multiple IOM/XCMs. Such multiple failures could be caused by issues on the SFM so this process involves the sequential reset of the SFMs to attempt to clear the cause of the failures. |
Effect | The router shall operate at reduced switch fabric capacity while each individual SFM is reset in turn. |
Recovery | This process will run until all the SFMs have been processed. No recovery is necessary. |
tmnxTrapDropped
Property name | Value |
---|---|
Application name | SYSTEM |
Event ID |
2011 |
Event name | tmnxTrapDropped |
SNMP notification prefix and OID | TIMETRA-SYSTEM-MIB.tmnxSysNotifications.13 |
Default severity | major |
Source stream |
main |
Message format string | Possible messages:
|
Cause | A tmnxTrapDropped notification is generated when a trap is dropped for the reason specified by the reason code. The tmnxTrapDroppedEntryID identifies the table entry associated with the dropped trap. A nonzero value of the object tmnxTrapDroppedCount indicates the number of traps dropped for the current flow of traps, identified by the values of tmnxDroppedTrapID, tmnxTrapDroppedReasonCode and tmnxTrapDroppedEntryID. |
Effect | N/A |
Recovery | N/A |