tmnxOesDbUnsync

TIMETRA-OES-MIB · .1.3.6.1.4.1.6527.3.1.3.98.0.7

Object

notification

[CAUSE] The tmnxOesDbUnsync notification is generated when the active 
and standby Equipment Controllers are not in sync.
          
[EFFECT] The OES does not have redundancy protection between the two 
Equipment Controller cards. If a switchover were to occur, then the 
database of the newly active controller might not reflect the latest 
configuration.
          
[RECOVERY] Proceed as follows to clear the Database Unsynchronization 
alarm:
  1) Perform a warm reset of the standby controller;
  2) If step 1 does not clear the alarm condition, then contact the 
     next level of technical support for help.

Context

MIB: TIMETRA-OES-MIB
OID: .1.3.6.1.4.1.6527.3.1.3.98.0.7
Type: notification
Status: current
Parent: tmnxOesNotifications
Groups: 1

Net-SNMP examples

How SNMP and these commands work

Notifications are emitted by an agent; they cannot be read with snmpget or walked.

Inspect the notification definition

/usr/bin/snmptranslate -Pud -Ir -Td -m 'TIMETRA-OES-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-OES-MIB::tmnxOesDbUnsync'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-OES-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-OES-MIB::tmnxOesDbUnsync'

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.