Using the Universal Device Poller with net-snmp proxy

bchristensen

Hello,

I'm trying to attach a custom poller to a Ubuntu server that is using net-snmp's proxy ability to merge two snmp services together.  Essentially, we have written a custom MIB database for one of our internal applications, and are serving our custom OID's through the net-snmp service that is already running on each Ubuntu server:

Example from snmpd.conf
proxy -v2c -c public 127.0.0.1:1088 1.3.6.1.4.1.28867

What this does is tell net-snmp to proxy all requests for the 1.3.6.1.4.1.28867 OID to localhost:1088.  Snmpwalk testing from the Orion server succeeds just fine and we get back the correct text data from the application.  However, when creating a customer poller, Orion has tagged all our Ubuntu servers as "net-snmp" devices and therefore returns a "The OID is not supported" error when testing.  I believe this is because the custom poller first verifies the OID against it's internal database of net-snmp MIBs before sending the GET request and does not find a match for this custom OID.  

Has anyone found a way around this issue?  Does Orion support any way of adding our custom MIB file into the net-snmp MIB database, as a work around?  Any help is appreciated, 

Thanks!

chris.lapoint

What this does is tell net-snmp to proxy all requests for the 1.3.6.1.4.1.28867 OID to localhost:1088.  Snmpwalk testing from the Orion server succeeds just fine and we get back the correct text data from the application.  However, when creating a customer poller, Orion has tagged all our Ubuntu servers as "net-snmp" devices and therefore returns a "The OID is not supported" error when testing.  I believe this is because the custom poller first verifies the OID against it's internal database of net-snmp MIBs before sending the GET request and does not find a match for this custom OID.

I've confirmed with dev that this is not the way the UnDP works.  It will cheerfully poll any SNMP OID regardless of whether it's in the MIB database.   They suggested testing the OID in question using another tool (e.g., net-snmp CLI tools or SW Toolset) or just use Wireshark to watch our UnDP test it.