tmnxOesNtpOutOfSync
TIMETRA-OES-MIB ·
.1.3.6.1.4.1.6527.3.1.3.98.0.10
Object
notification
[CAUSE] The tmnxOesNtpOutOfSync notification is generated when NTP time
on the OES is not synchronized to the host router. The host router must
have NTP enabled and have recovered time from external time sources
(NTP to PTP). If there is no NTP time source for the router, it will
not serve time to the OES. In addition, once the NE is power cycled,
it takes approximately 20-30 minutes to initialize. Thereafter, time
synchronization will be completed, with a maximum delay time of 2-3
minutes.
[EFFECT] Timestamp of each event occurring on the OES may not be
exactly aligned with the host router.
[RECOVERY] Ensure the host router has NTP configured and a reachable
time source. Allow 40 minutes for the condition to clear.
Context
- MIB
- TIMETRA-OES-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.98.0.10- 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::tmnxOesNtpOutOfSync'
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::tmnxOesNtpOutOfSync'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of