tmnxOesDbInvalid
TIMETRA-OES-MIB ·
.1.3.6.1.4.1.6527.3.1.3.98.0.5
Object
notification
[CAUSE] The tmnxOesDbInvalid notification may be raised under the
following conditions:
1) During initial installation, if the OES is not properly
commissioned;
2) The serial number in the database does not match that of the OES
either because the controller was replaced or the alarm card was
replaced;
3) A downgrade of OES software has occurred;
4) Equipment Controller is removed/reseated during a system process,
causing file corruption;
5) The database audit failed indicating some type of corruption of
the database.
[EFFECT] The OES is not in a normal operating mode. It does not have
the correct configuration and the state of its cards is unpredictable.
As a result, the OES will not boot normally and not all commands are
allowed.
[RECOVERY] A database corruption on the OES requires that the OES be
re-commissioned. The correct database is held in the host system so
it will be restored to the shelf once the existing database is cleared
and the host re-establishes communication with the OES.
Context
- MIB
- TIMETRA-OES-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.98.0.5- Type
- notification
- Status
- current
- Parent
- tmnxOesNotifications
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workNotifications 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::tmnxOesDbInvalid'
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::tmnxOesDbInvalid'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of