Trivial Description
Within snmpd you can define daemons to watch if them are running. Eg. with an entry
proc sshd
you declare sshd as a process to watch.
The results are organised in .1.3.6.1.4.1.2021.2.1 like this:
.1.3.6.1.4.1.2021.2.1.1.1 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.1.2 = INTEGER: 2
.1.3.6.1.4.1.2021.2.1.1.3 = INTEGER: 3
.1.3.6.1.4.1.2021.2.1.1.4 = INTEGER: 4
.1.3.6.1.4.1.2021.2.1.1.5 = INTEGER: 5
.1.3.6.1.4.1.2021.2.1.1.6 = INTEGER: 6
.1.3.6.1.4.1.2021.2.1.2.1 = STRING: sshd
.1.3.6.1.4.1.2021.2.1.2.2 = STRING: automount
.1.3.6.1.4.1.2021.2.1.2.3 = STRING: slurmd
.1.3.6.1.4.1.2021.2.1.2.4 = STRING: systemd-logind
.1.3.6.1.4.1.2021.2.1.2.5 = STRING: accounts-daemon
.1.3.6.1.4.1.2021.2.1.2.6 = STRING: cgrulesengd
.1.3.6.1.4.1.2021.2.1.3.1 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.3.2 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.3.3 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.3.4 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.3.5 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.3.6 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.4.1 = INTEGER: 0
.1.3.6.1.4.1.2021.2.1.4.2 = INTEGER: 0
.1.3.6.1.4.1.2021.2.1.4.3 = INTEGER: 0
.1.3.6.1.4.1.2021.2.1.4.4 = INTEGER: 0
.1.3.6.1.4.1.2021.2.1.4.5 = INTEGER: 0
.1.3.6.1.4.1.2021.2.1.4.6 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.5.1 = INTEGER: 3
.1.3.6.1.4.1.2021.2.1.5.2 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.5.3 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.5.4 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.5.5 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.5.6 = INTEGER: 1
.1.3.6.1.4.1.2021.2.1.100.1 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.100.2 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.100.3 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.100.4 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.100.5 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.100.6 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.101.1 = STRING:
.1.3.6.1.4.1.2021.2.1.101.2 = STRING:
.1.3.6.1.4.1.2021.2.1.101.3 = STRING:
.1.3.6.1.4.1.2021.2.1.101.4 = STRING:
.1.3.6.1.4.1.2021.2.1.101.5 = STRING:
.1.3.6.1.4.1.2021.2.1.101.6 = STRING:
.1.3.6.1.4.1.2021.2.1.102.1 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.102.2 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.102.3 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.102.4 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.102.5 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.102.6 = INTEGER: noError(0)
.1.3.6.1.4.1.2021.2.1.103.1 = STRING:
.1.3.6.1.4.1.2021.2.1.103.2 = STRING:
.1.3.6.1.4.1.2021.2.1.103.3 = STRING:
.1.3.6.1.4.1.2021.2.1.103.4 = STRING:
.1.3.6.1.4.1.2021.2.1.103.5 = STRING:
.1.3.6.1.4.1.2021.2.1.103.6 = STRING:
(Real world example)
Currently I add them myself for hosts where I know the order. but I think, it would be cool to add this to autodetection, it is a well know MIB and feature, with which you can detect problems quite easily when it is about daemons not opening an network port but are very important.
Mainly all below .1.3.6.1.4.1.2021.2.1.100 is very interesting: 0 is no error, 1 error. In .1.3.6.1.4.1.2021.2.1.101 you would have an associated error message of snmpd.
Would this be possible?
Attachments
Activity
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
Note, this comment is added automatically.
Done