SNMP Traps: Service Startup Changes Made

The following traps are generated at service startup and indicate the various services changing state:

SNMP 1.3.6.1.2.1.88.2.0.1

2014-07-04 15:40:30 <server_IP> [UDP: [<server_IP>]:56005->[<snmp_server_IP>]]:
iso.3.6.1.2.1.1.3.0 = Timeticks: (8785393) 1 day, 0:24:13.93
iso.3.6.1.6.3.1.1.4.1.0 = OID: iso.3.6.1.2.1.88.2.0.1
iso.3.6.1.2.1.88.2.1.1.0 = STRING: "ProcessRestart"
iso.3.6.1.2.1.88.2.1.3.0 = STRING: <resource>
iso.3.6.1.2.1.88.2.1.5.0 = INTEGER: 1
iso.3.6.1.2.1.1.5.0 = STRING: "<hostname> "

The <resource> is any of the services listed when running app status for any node.

Severity levels, messages and resolution:

  • Info : ProcessRestart, ProcessStart

    Resolution: If this is an unexpected event, call Support should be called for further investigation. This trap can also be triggered as expected, when app start or system reboot is run.

  • Urgent : ProcessWarning

    Resolution: This trap should be seen when a process or service is being restarted or stopped. If this is an unexpected event, call Support should be called for further investigation.

  • Critical : ProcessStop, ProcessError

    Resolution: If this is an unexpected event, call Support should be called for further investigation. This trap can also be triggered as expected, when app stop or system reboot is run.

Example: ProcessRestart

  • Severity: Info
  • Message: ProcessRestart
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.22.21.124', 26069):
Var-binds:
1.3.6.1.2.1.1.3.0 = 6619
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 = ProcessRestart
1.3.6.1.2.1.88.2.1.3.0 = Applications are restarting
1.3.6.1.2.1.88.2.1.5.0 = 1
1.3.6.1.2.1.1.5.0 = UN1-192.22.21.124

Example: ProcessWarning

  • Severity: Urgent
  • Message: ProcessWarning
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.22.21.124', 50336):
Var-binds:
1.3.6.1.2.1.1.3.0 = 16212
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 = ProcessWarning
1.3.6.1.2.1.88.2.1.3.0 = mongodb:database has changed its state from \
                         stopped (not reachable) to running (not reachable)
1.3.6.1.2.1.88.2.1.5.0 = 1
1.3.6.1.2.1.1.5.0 = UN1-192.22.21.124

Example: ProcessStop

  • Severity: Critical
  • Message: ProcessStop
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.22.21.124', 43961):
Var-binds:
1.3.6.1.2.1.1.3.0 = 6286121
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 = ProcessStop
1.3.6.1.2.1.88.2.1.3.0 = Applications are stopping nginx
1.3.6.1.2.1.88.2.1.5.0 = 1
1.3.6.1.2.1.1.5.0 = UN1-192.22.21.124

Example: ProcessStart

  • Severity: Info
  • Message: ProcessStart
Notification message from (1, 3, 6, 1, 6, 1, 1):('192.22.21.124', 43961):
Var-binds:
1.3.6.1.2.1.1.3.0 = 6286121
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 = ProcessStop
1.3.6.1.2.1.88.2.1.3.0 = Applications are started nginx
1.3.6.1.2.1.88.2.1.5.0 = 1
1.3.6.1.2.1.1.5.0 = UN1-192.22.21.124