SNMP Trap: NTP Status

A trap is generated if NTP is not configured.

Identification

  • The originating IP / hostname is used to identify the system generating the traps

  • The NMS is responsible for associating traps with each managed system, along with clearing of alarms and escalation to the relevant system operator

  • The trap OID is generic for various SNMP events monitored by the system

  • The SNMP system name is included as part of the variable binding to assist identification:

.iso.org.dod.internet.mgmt.mib-2.system.sysName.0 = standalone

Trap OID

.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotifications.mteTriggerFired

Variable Bindings - NTP not configured.

  • .iso.org.dod.internet.mgmt.mib-2.system.sysUpTime.0 = 2 minutes (12065)

  • snmpTrapOID = mteTriggerFired

  • .iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotificationObjects.mteHotTrigger.0 = ‘ERROR: No ntp configured for <server info>’

  • .iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIBNotificationPrefix. dismanEventMIBNotificationObjects.mteHotValue.0 = 1

  • .iso.org.dod.internet.mgmt.mib-2.system.sysName.0 = standalone

Severity:

  • Critical: WARNING: The ntp daemon has stopped on <server>

  • Urgent:

    • ERROR: No ntp configured for <server>

    • WARNING: The ntp offset exceeds 1 second on <server>

Example: Critical

Mar 19 15:25:21 robot-sl snmptrapd[1214]:
2019-03-19 15:25:21 <UNKNOWN>
[UDP: [192.168.100.3]:7564->[192.168.100.25]:162]:
#012iso.3.6.1.2.1.1.3.0 = Timeticks: (599782) 1:39:57.82
#011iso.3.6.1.6.3.1.1.4.1.0 = OID: iso.3.6.1.2.1.88.2.0.1
#011iso.3.6.1.2.1.88.2.1.1.0 = STRING: "WARNING: The ntp daemon has stopped on VOSS-192.168.100.3"
#011iso.3.6.1.2.1.88.2.1.3.0 = STRING: "Run
  'app start services:time' to restart ntpd"
#011iso.3.6.1.2.1.88.2.1.5.0 = INTEGER: 1
#011iso.3.6.1.2.1.1.5.0 = STRING: "VOSS"

Example: Urgent

Mar 20 12:21:24 robot-sl snmptrapd[1214]:
2019-03-20 12:21:24 <UNKNOWN>
[UDP: [192.168.100.3]:11256->[192.168.100.25]:162]:
#012iso.3.6.1.2.1.1.3.0 = Timeticks: (421144) 1:10:11.44
#011iso.3.6.1.6.3.1.1.4.1.0 = OID: iso.3.6.1.2.1.88.2.0.1
#011iso.3.6.1.2.1.88.2.1.1.0 = STRING: "ERROR: No ntp configured for VOSS-192.168.100.3"
#011iso.3.6.1.2.1.88.2.1.3.0 = STRING: "It is mandatory that the ntp is configured.
  To configure ntp use the following command: network ntp <server1> <server2>"
#011iso.3.6.1.2.1.88.2.1.5.0 = INTEGER: 1
#011iso.3.6.1.2.1.1.5.0 = STRING: "VOSS"

Example: Urgent

Notification message from (1, 3, 6, 1, 6, 1, 1):('192.29.22.122', 51983):
Var-binds:
1.3.6.1.2.1.1.3.0 = 242825
1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.2.1.88.2.0.1
1.3.6.1.2.1.88.2.1.1.0 = WARNING: The ntp offset exceeds 1 second on  UN1-192.29.22.122-192.29.22.122
1.3.6.1.2.1.88.2.1.3.0 = ntp offset exceeds 1 second Current ntp offset value: 2
1.3.6.1.2.1.88.2.1.5.0 = 1
1.3.6.1.2.1.1.5.0 = UN1-192.29.22.122