Details
Major Description
Not an Observium bug but F5's.
After upgrading from rev 5572 to 5768 one of our two F5 load balancers were showing 'snmp down' in Observium. Running a poller with debug, I can see one of the SNMP gets returns "No Such Object".
In the output below, the RO string and hostnames were updated for security purposes. somef5-01 responds correctly while somef5-02 does not, despite running the same F5 code.
This appears to be an F5 bug: http://support.f5.com/kb/en-us/solutions/public/15000/000/sol15064.html
I'd hate to have to take an outage to upgrade our F5s for this problem. Is there any workaround in Observium or code modification to compensate for F5's fail SNMP code?
snmpget -v2c -c '<snip>' -Oqtnv -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'somef5-01':'161' .1.3.6.1.2.1.1.2.0 .1.3.6.1.2.1.1.3.0
.1.3.6.1.4.1.3375.2.1.3.4.22
755890666
root@observium01:/opt/observium# snmpget -v2c -c '<snip>' -Oqtnv -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'somef5-02':'161' .1.3.6.1.2.1.1.2.0 .1.3.6.1.2.1.1.3.0
No Such Object available on this agent at this OID
755950560