“FEATURE REQUEST - Add the possibility to monitor nodes supporting a limited set of mibs (Ex. no sysdescr, no sysobjectid, no sysuptime)”

ipnoc

Case # 00233022 - Problem to add a node that only supports IF-MIB

Hello, I'm trying to add some nodes supporting only the IF-MIB (no sysdescr, no sysobjectid, no sysuptime) and as result I can't add them because of "SNMP test failed" as explained in your documentation here https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Knowledgebase_Articles/troubleshoot_SNMP_Node_-_SNMP_Test_Failed

The devices are accessible and I can read the IF-MIB with your SNMP MIB Browser.

My question is "Is it possible to add these devices in another way by bypassing the check on system MIB?"

Devices are from SEL (Schweitzer Engineering Laboratories) - type: SEL-2740S (see documentation in attach)

tigger2

I would like this enhancement as well, as it seems that some devices "support" SNMP, but just don't really follow the rules.  You still want to be able to poll them for data over SNMP.  If nothing else, if there was a used editable area where you could manually add a "SYSDESCR" and "SYSOBJECTID" to force Orion to recognize it that would be less than ideal, but maybe enough to force Orion to accept the device to add it and let you craft monitoring as you need it vs treating it like a "default SNMP enabled device" and auto pulling CPU/Mem/etc.

I had a device that the vendor stripped some "unnecessary" (sigh) MIB information from. Maybe this may help you get by for now?: Issues polling device, that does not have MIB-2 installed, with SNMP + ICMP: Orion node constantly flapping up/down

Basically, add the device as an IP address + ICMP polling only to get it into Orion, then switch the polling to ICMP + SNMP (maybe have to use SNMPv1?) , then create custom SNMP pollers to get the data you need.  It needs to be changed to ICMP + SNMP because this allows you to store the SNMP credentials in the node, which are used when creating custom pollers (e.g. you can't create custom pollers on an ICMP polled only device because the custom poller creator doesn't allow you to store the SNMP read string in the pollers). Alternatively, if you have SAM, you could maybe use SAM SNMP component to poll the OID's you need and not have to change the node polling type to "ICMP + SNMP"

...but, per the link above, there was the "device flapping up and down" issue encountered when doing the ICMP -> ICMP + SNMP switch trick, which required support to help with.  If I remember it was making some update to the SolarWinds database.

Also: This may be another workaround (a 10 year old post ) : Adding SNMPv1 Node

"I've gotten around this by adding a different known working SNMP device and then going back and changing the IP and Community to the non-working device and doing a rediscovery. Sometimes this works and sometimes not."