Trivial Description
Hello Team,
I wanted to add some AFFIRMED equipment to Observium but they are not recognized, after checking I can't find AFFIRMED in the list of mibs.
How can I do to add support and mibs of my AFFIRMED devices to Observium ?
Regards,
–
Yassine
Attachments
Activity
Hello,
Here the result of the two commands, and you can find attached the myagent.snmpwalk file :
root@prd-mon-observium-pa2-01 ~ |
$ pwd
|
/root
|
|
|
root@prd-mon-observium-pa2-01 ~ |
$ snmpwalk -v2c -c affirmed --hexOutputLength=0 -ObentxU 10.200.200.10 .1 > myagent.snmpwalk |
/opt/observium/mibs/rfc: No such file or directory
|
Failed to parse MIB file /opt/observium/mibs/net-snmpError in packet.
|
Reason: (genError) A general failure occured
|
Failed object: .1.3.6.1.4.1.37963.10.3.1.5.3.3.7.1.1.3.36.0 |
|
|
root@prd-mon-observium-pa2-01 ~ |
$ snmpwalk -v2c -c affirmed --hexOutputLength=0 -ObentxU 10.200.200.10 .1.3.6.1.4.1 >> myagent.snmpwalk |
/opt/observium/mibs/rfc: No such file or directory
|
Failed to parse MIB file /opt/observium/mibs/net-snmp
|
Error in packet.
|
Reason: (genError) A general failure occured
|
Failed object: .1.3.6.1.4.1.37963.10.3.1.5.3.3.7.1.1.3.36.0 |
I add also some vendor MIB files to the ticket.
Regards,
[^myagent.snmpwalk]
[^Affirmed_MIBs.7z]
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.
Basic os detect added in r12441.