This document is the System SNMP MIB module for the Nokia
SROS device. The System MIB module defines SNMP objects to
manage and provision system features.
Copyright 2003-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
This SNMP MIB module (Specification) embodies Nokia's
proprietary intellectual property. Nokia retains
all title and ownership in the Specification, including any
revisions.
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
This Specification is supplied `as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
[CAUSE] The stiDateAndTimeChanged notification is generated when the
time on the system is explicitly set.
[EFFECT] The time on the system is being changed.
[RECOVERY] No recovery is necessary.
tmnxConfigDelete
.1.3.6.1.4.1.6527.3.1.3.1.0.10
A tmnxConfigDelete notification is generated when an existing row
entry in one of the MIB tables is deleted. It can be used by the NMS
to trigger maintenance polls of the configuration information.
tmnxStateChange
.1.3.6.1.4.1.6527.3.1.3.1.0.11
A tmnxStateChange notification is generated when there is a change in
either the administrative or operational state of a MIB table entry.
tmnxModuleMallocFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.12
A tmnxModuleMallocFailed notification is generated when a request to
allocate memory from a particular module fails because the memory
module is short on memory and cannot support the size that was
requested.
tmnxTrapDropped
.1.3.6.1.4.1.6527.3.1.3.1.0.13
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.
ssiSyncConfigOK
.1.3.6.1.4.1.6527.3.1.3.1.0.14
The ssiSyncConfigOK event is generated when the synchronization of
configuration files between the primary and secondary CPMs finishes
without errors.
ssiSyncConfigFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.15
The ssiSyncConfigFailed event is generated when the synchronization of
configuration files between the primary and secondary CPMs is stopped
due to errors. The tmnxSyncFailureReason will state reason for
failure.
ssiSyncBootEnvOK
.1.3.6.1.4.1.6527.3.1.3.1.0.16
The ssiSyncBootEnvOK event is generated when the synchronization of
boot environment files between the primary and secondary CPMs finishes
without errors.
ssiSyncBootEnvFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.17
The ssiSyncBootEnvFailed event is generated when the synchronization
of boot environment files between the primary and secondary CPMs is
stopped due to errors. The tmnxSyncFailureReason will state reason for
failure.
sntpTimeDiffExceedsThreshold
.1.3.6.1.4.1.6527.3.1.3.1.0.18
The sntpTimeDiffExceedsThreshold event is generated when the time
differential between the system and the SNTP server is more than 10
seconds. In this case the system clock is not automatically adjusted.
tacplusServerOperStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.19
The tacplusServerOperStatusChange notification is generated when the
operational status of a TACACS+ server has transitioned either from
'up' to 'down' or from 'down' to 'up'.
This object was made obsolete in the 5.0 release.
ssiSaveConfigSucceeded
.1.3.6.1.4.1.6527.3.1.3.1.0.2
The save config succeeded event is generated when the saving of
configuration finishes without errors.
tacplusOperStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.20
The tacplusOperStatusChange notification is generated when the
tacplusOperStatus has transitioned either from 'up' to 'down' or from
'down' to 'up'
tmnxSnmpdError
.1.3.6.1.4.1.6527.3.1.3.1.0.21
The tmnxSnmpdError notification is generated when the SNMP daemon
detects an error condition.
tmnxSsiMismatch
.1.3.6.1.4.1.6527.3.1.3.1.0.22
The tmnxSsiMismatch notification is generated by a system with
redundant CPM cards after the processing of the bootup
configuration has completed when ssiSyncMode has a value of 'none'
and sbiPersist has a value of 'true'. This can result in SNMP
indexes having different values following a system failover.
tmnxSnmpdStateChange
.1.3.6.1.4.1.6527.3.1.3.1.0.23
The tmnxSnmpdStateChange notification is generated whenever there is a
change in either the administrative or operational state of the SNMP
agent.
ssiRedStandbySyncing
.1.3.6.1.4.1.6527.3.1.3.1.0.24
The ssiRedStandbySyncing notification is generated when
synchronization of redundancy information onto the standby
CPM is started. tmnxChassisNotifyHwIndex identifies the
standby CPM.
ssiRedStandbyReady
.1.3.6.1.4.1.6527.3.1.3.1.0.25
The ssiRedStandbyReady notification is generated when the
synchronization of redundancy information onto the standby CPM
has completed. 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. tmnxChassisNotifyHwIndex
identifies the standby CPM.
ssiRedStandbySyncLost
.1.3.6.1.4.1.6527.3.1.3.1.0.26
The ssiRedStandbySyncLost notification is generated when the active
CPM looses communication with the standby CPM.
tmnxChassisNotifyHwIndex identifies the lost standby CPM.
ssiRedSwitchover
.1.3.6.1.4.1.6527.3.1.3.1.0.27
The ssiRedSwitchover notification is generated when the standby
CPM detects that the active CPM has failed and the standby prepares
to take over as the new active CPM. tmnxChassisNotifyHwIndex
identifies the new active CPM.
ssiRedCpmActive
.1.3.6.1.4.1.6527.3.1.3.1.0.28
The ssiRedCpmActive notification is generated following a
redundancy switchover when the new active CPM has completed
its audit and is ready to accept management commands via CLI
or SNMP SET requests. tmnxChassisNotifyHwIndex identifies
the new active CPM.
ssiRedSingleCpm
.1.3.6.1.4.1.6527.3.1.3.1.0.29
The ssiRedSingleCpm notification is generated by a system with
a chassis with two CPM slots when the active CPM cannot 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 notification is
generated. tmnxChassisNotifyHwIndex identifies the singleton CPM.
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)'.
ssiSaveConfigFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.3
The save config failed event is generated when the saving of
configuration is stopped due to errors.
persistencyClosedAlarmRaised
.1.3.6.1.4.1.6527.3.1.3.1.0.30
The persistencyClosedAlarmRaised notification is generated when the
system is unable to store persistency data (e.g. because the device is
inaccessible, or full).
persistencyClosedAlarmCleared
.1.3.6.1.4.1.6527.3.1.3.1.0.31
The persistencyClosedAlarmCleared notification is generated when the
output device used to store the persistence data is available for use
again.
tmnxSntpOperChange
.1.3.6.1.4.1.6527.3.1.3.1.0.32
The tmnxSntpOperChange notification is generated whenever there is a
change in the operational state of SNTP.
tmnxSysTimeSet
.1.3.6.1.4.1.6527.3.1.3.1.0.33
The tmnxSysTimeSet notification is generated whenever system time is
set by NTP, SNTP, SNMP, Real Time Clock(RTC) or if it was set
manually.
tmnxFtpClientFailure
.1.3.6.1.4.1.6527.3.1.3.1.0.34
The tmnxFtpClientFailure notification is generated when a file
transfer operation initiated by the FTP client fails.
tacplusInetSrvrOperStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.35
The tacplusInetSrvrOperStatusChange notification is generated when the
operational status of a TACACS+ server has transitioned either from
'up' to 'down' or from 'down' to 'up'.
radiusInetServerOperStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.36
The radiusInetServerOperStatusChange notification is generated when
the operational status of a Radius server has transitioned either from
'up' to 'down' or from 'down' to 'up'.
persistencyEventReport
.1.3.6.1.4.1.6527.3.1.3.1.0.37
The persistencyEventReport notification is generated when a
client-specific persistence event occurs (e.g. the start and
completion of a recover action after system startup).
sbiBootConfigFailFileError
.1.3.6.1.4.1.6527.3.1.3.1.0.38
The sbiBootConfigFailFileError notification is generated when
sbiBootConfigFailScript file cannot be accessed.
sbiBootConfigOKFileError
.1.3.6.1.4.1.6527.3.1.3.1.0.39
The sbiBootConfigOKFileError notification is generated when
sbiBootConfigOKScript file cannot be accessed.
sbiBootConfig
.1.3.6.1.4.1.6527.3.1.3.1.0.4
The sbiBootConfig notification is generated upon completion of the
configuration phase following a system reboot.
sbiBootLiConfig
.1.3.6.1.4.1.6527.3.1.3.1.0.40
The sbiBootLiConfig notification is generated upon completion of
the Lawful Intercept (LI) configuration phase following a system
reboot. This notification is generated periodically, about once
an hour.
This event is generated only from the LI context.
persistenceRestoreProblem
.1.3.6.1.4.1.6527.3.1.3.1.0.41
The persistenceRestoreProblem notification is generated when an error
is detected while processing a persistence record.
tmnxSysRollbackStarted
.1.3.6.1.4.1.6527.3.1.3.1.0.42
[CAUSE] The tmnxSysRollbackStarted notification is generated when the
user initiates a revert of the rollback checkpoint file specified by
tmnxSysRollbackIndex and tmnxSysRollbackFileType. The value of
tmnxLogExecRollbackOpIndex indicates the row entry in the
TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this rollback revert
operation.
[EFFECT] The specified file is executed and system configuration may
change.
[RECOVERY] There is no recovery required for this notification.
tmnxSysRollbackStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.43
[CAUSE] The tmnxSysRollbackStatusChange notification is
generated upon the completion of a rollback revert as specified
by tmnxSysRollbackIndex and tmnxSysRollbackFileType. The value
of tmnxLogExecRollbackOpIndex indicates the row entry in the
TIMETRA-LOG-MIB::tmnxLogExecRollbackOpTable for this rollback
revert operation.
[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.
tmnxSysRollbackSaveStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.44
[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.
tmnxSysRollbackFileDeleteStatus
.1.3.6.1.4.1.6527.3.1.3.1.0.45
[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.
ssiSyncRollbackOK
.1.3.6.1.4.1.6527.3.1.3.1.0.46
[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.
ssiSyncRollbackFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.47
[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.
ssiSyncCertOK
.1.3.6.1.4.1.6527.3.1.3.1.0.48
[CAUSE] The ssiSyncCertOK event is generated when the
synchronization of certificate files between the primary
and secondary CPMs finishes without errors.
[EFFECT] Certificate files are synchronized.
[RECOVERY] No recovery is necessary.
ssiSyncCertFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.49
[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] Certificate files are not synchronized.
[RECOVERY] The user should try to determine the cause of the failure
and can attempt synchronizing the files again.
sbiBootSnmpd
.1.3.6.1.4.1.6527.3.1.3.1.0.5
The sbiBootSnmpd notification is generated upon completion of the SNMP
daemon initialization following a system reboot. Some system
configuration and initialization errors may result in the SNMP daemon
being suspended.
persistencyFileSysThresRaised
.1.3.6.1.4.1.6527.3.1.3.1.0.50
The persistencyFileSysThresRaised notification is generated when the
filesystem reaches 90 percent occupation.
persistencyFileSysThresCleared
.1.3.6.1.4.1.6527.3.1.3.1.0.51
The persistencyFileSysThresCleared notification is generated when the
filesystem drops below 90 percent occupation.
tmnxSysExecStarted
.1.3.6.1.4.1.6527.3.1.3.1.0.52
[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.
tmnxSysExecFinished
.1.3.6.1.4.1.6527.3.1.3.1.0.53
[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.
tmnxSysRollbackSaveStarted
.1.3.6.1.4.1.6527.3.1.3.1.0.54
[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.
tmnxSysRollbackDeleteStarted
.1.3.6.1.4.1.6527.3.1.3.1.0.55
[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.
tmnxSysNvsysFileError
.1.3.6.1.4.1.6527.3.1.3.1.0.56
[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.
sysDNSSecFailedAuthentication
.1.3.6.1.4.1.6527.3.1.3.1.0.57
[CAUSE] The sysDNSSecFailedAuthentication notification is generated
when a DNS response PDU is received with an unset AD-bit and
sysDNSSecAdValidation is set to 'true (1)'.
[EFFECT] This notification is informational only. The message will
vary depending on the state of sysDNSSecRespCtrl.
[RECOVERY] There is no recovery required for this notification.
tmnxConfigConflict
.1.3.6.1.4.1.6527.3.1.3.1.0.58
A tmnxConfigConflict notification is generated when a configuration
attribute associated with a row entry in a MIB table is in conflict
with another attribute.
It can be used by the NMS to trigger maintenance polls of the
configuration information.
tmnxSysLicenseInvalid
.1.3.6.1.4.1.6527.3.1.3.1.0.59
[CAUSE] The tmnxSysLicenseInvalid notification is generated when the
license becomes invalid for the reason specified in
tmnxSysLicenseErrorReason.
[EFFECT] The CPM or system will reboot at the end of the time
remaining, as specified by tmnxSysLicenseTimeLeft and
tmnxSysLicenseErrorAction.
[RECOVERY] Configure a valid license file location and file name,
given the value of tmnxSysLicenseErrorReason.
radiusServerOperStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.6
The radiusServerOperStatusChange notification is generated when the
operational status of a RADIUS server has transitioned either from
'up' to 'down' or from 'down' to 'up'.
This object was made obsolete in the 5.0 release.
tmnxSysLicenseExpiresSoon
.1.3.6.1.4.1.6527.3.1.3.1.0.60
[CAUSE] The tmnxSysLicenseExpiresSoon notification is generated when
the license is due to expire soon.
[EFFECT] The system will reboot at the end of the time remaining, as
specified by tmnxSysLicenseTimeLeft.
[RECOVERY] Configure a valid license file location and file name.
tmnxSysVsdServerAvailable
.1.3.6.1.4.1.6527.3.1.3.1.0.63
[CAUSE] The tmnxSysVsdServerAvailable notification is generated when
system discover a new VSD server.
[EFFECT] System will use this information to establish communication
with new VSD server as needed.
[RECOVERY] None needed.
tmnxSysVsdServerUnavailable
.1.3.6.1.4.1.6527.3.1.3.1.0.64
[CAUSE] The tmnxSysVsdServerAvailable notification is generated when
system loses connection to VSD.
[EFFECT] System will use this information and stop communication with
this VSD server as needed.
[RECOVERY] None needed.
tmnxSysXmppServerFunctional
.1.3.6.1.4.1.6527.3.1.3.1.0.65
[CAUSE] The tmnxSysXmppServerFunctional notification is generated when
system discover a new XMPP server.
[EFFECT] System will use this information to establish communication
with new XMPP server as needed.
[RECOVERY] None needed.
tmnxSysXmppServerNotFunctional
.1.3.6.1.4.1.6527.3.1.3.1.0.66
[CAUSE] The tmnxSysXmppServerNotFunctional notification is generated
when system can not communicate with XMPP server.
[EFFECT] Communication with XMPP server will stop.
[RECOVERY] Check to see why XMPP server has stopped communicating.
tmnxSysLicenseValid
.1.3.6.1.4.1.6527.3.1.3.1.0.67
[CAUSE] The tmnxSysLicenseValid notification is generated once after
the system boots up and the license is determined by the system to be
valid.
[EFFECT] The system is running with the license specified in
tmnxSysLicenseName.
[RECOVERY] No recovery.
tmnxSysBaseMacAddressNotSet
.1.3.6.1.4.1.6527.3.1.3.1.0.68
[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.
tmnxSmLaunchStartFailed
.1.3.6.1.4.1.6527.3.1.3.1.0.69
[CAUSE] The tmnxSmLaunchStartFailed notification is generated when the
launch start fails because of one of the following reasons:
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.
radiusOperStatusChange
.1.3.6.1.4.1.6527.3.1.3.1.0.7
The radiusOperStatusChange notification is generated when the
radiusOperStatus has transitioned either from 'up' to 'down' or from
'down' to 'up'
tmnxEhsHandlerInvoked
.1.3.6.1.4.1.6527.3.1.3.1.0.70
[CAUSE] The tmnxEhsHandlerInvoked notification is generated when the
following checks pass: 1. A check to see if a event trigger is present
for a particular log event based on the log event application-id and
event-id/event name. 2. Evaluation of the log filter associated with
the trigger-entry.
[EFFECT] This may create a run entry to execute scripts.
[RECOVERY] No recovery is necessary.
tmnxEhsDroppedByMinDelay
.1.3.6.1.4.1.6527.3.1.3.1.0.71
[CAUSE] The tmnxEhsDroppedByMinDelay is generated when two consecutive
executions of script policy specified by the same event handler entry
occurs within the time period specified by tmnxEhsHEntryMinDelay.
[EFFECT] The value of tmnxEhsHEntryStatsErrMinDelay gets incremented.
[RECOVERY] No recovery is necessary.
tmnxSysAppStats24HrsAvailable
.1.3.6.1.4.1.6527.3.1.3.1.0.72
[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
.1.3.6.1.4.1.6527.3.1.3.1.0.73
[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.
tmnxSysLicenseActivated
.1.3.6.1.4.1.6527.3.1.3.1.0.75
[CAUSE] The tmnxSysLicenseActivated notification is generated each
time a license is activated by the system.
[EFFECT] The system is running with the license specified in
tmnxSysLicenseName.
[RECOVERY] No recovery.
tmnxSysStandbyLicensingError
.1.3.6.1.4.1.6527.3.1.3.1.0.76
[CAUSE] The tmnxSysStandbyLicensingError notification is generated
when a licensing issue has been detected by the standby. The reason is
specified in tmnxSysLicenseErrorReason.
[EFFECT] The Standby CPM may not synchronized and may be put into a
failed state depending on the failure.
[RECOVERY] Ensure a valid license file location and file name,
given the value of tmnxSysLicenseErrorReason. Reset the Standby CPM or activate
a valid license.
tmnxSysStandbyLicensingReady
.1.3.6.1.4.1.6527.3.1.3.1.0.77
[CAUSE] The tmnxSysStandbyLicensingReady notification is generated
when a licensing has been successfully activated by the standby.
[EFFECT] Any licensing errors detected by the Standby CPM are cleared.
[RECOVERY] None.
tmnxSysMgmtIfModeChangeStart
.1.3.6.1.4.1.6527.3.1.3.1.0.78
[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.
tmnxSysMgmtIfModeChangeComplete
.1.3.6.1.4.1.6527.3.1.3.1.0.79
[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.
tmnxConfigModify
.1.3.6.1.4.1.6527.3.1.3.1.0.8
A tmnxConfigModify notification is generated when a configuration
attribute associated with a row entry in a MIB table is modified. It
can be used by the NMS to trigger maintenance polls of the
configuration information.
tmnxSysMgmtIfModeChangeFailure
.1.3.6.1.4.1.6527.3.1.3.1.0.80
[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.
tmnxSysAppLicenseInsufficient
.1.3.6.1.4.1.6527.3.1.3.1.0.81
[CAUSE] The tmnxSysAppLicenseInsufficient notification is generated periodically
when licensing for an application is detected to be insufficient. The details
of the error is specified in tmnxSysLicenseErrorReason.
This notification cannot be suppressed.
[EFFECT] Notification generated periodically while the application
remains in this condition.
[RECOVERY] Activate a system license containing sufficient license
entitlements for this application.
tmnxSysMgmtIfLiIncorrectFormat
.1.3.6.1.4.1.6527.3.1.3.1.0.82
[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
tmnxSysMgmtIfLiCfgNotEncrypted
.1.3.6.1.4.1.6527.3.1.3.1.0.83
[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
tmnxSysLicenseUpdateRequired
.1.3.6.1.4.1.6527.3.1.3.1.0.84
[CAUSE] The tmnxSysLicenseUpdateRequired notification is generated once after
the system boots up and the license is determined by the system to be valid, but
requires to be updated to the correct software version.
[EFFECT] The system will use the license until it is updated.
[RECOVERY] Update and activate the updated license.
tmnxEqOperStateChange
.1.3.6.1.4.1.6527.3.1.3.1.0.85
[CAUSE] The tmnxEqOperStateChange notification is generated when a
change occurred in the operational state on the piece of hardware.
[EFFECT] If the state has changed to out of service, then all ports
and services associated with the module change to out of service and
traffic is impacted.
[RECOVERY] Investigation is required to determine the cause of the
change.
stiDateAndTimeChanging
.1.3.6.1.4.1.6527.3.1.3.1.0.86
[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.
tmnxSysSwFabFailRecStarted
.1.3.6.1.4.1.6527.3.1.3.1.0.87
[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.
tmnxSysSwFabFailRecCompleted
.1.3.6.1.4.1.6527.3.1.3.1.0.88
[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.
tmnxSysSwFabFailRecAborted
.1.3.6.1.4.1.6527.3.1.3.1.0.89
[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.
tmnxConfigCreate
.1.3.6.1.4.1.6527.3.1.3.1.0.9
A tmnxConfigCreate notification is generated when a new row entry is
created in one of the MIB tables. It can be used by the NMS to trigger
maintenance polls of the configuration information.
tmnxSysSwFabFailRecDetected
.1.3.6.1.4.1.6527.3.1.3.1.0.90
[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 fabric 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] If the automatic switch fabric recovery process is
disabled, then contact Nokia support to determine if it should be
enabled for this router. Otherwise, no recovery is necessary.