SNMP Problem with VM Appliance

Hello Everyone,

I have a problem with SNMP queries on an appliance that controls our
wireless access points (Adtran/BlueSocket). Some information about our
installation:

OpenNMS Version:	20.0.1
Java Version:	1.8.0_141 Oracle Corporation
Java Virtual Machine:	25.141-b15 Oracle Corporation
Operating System:	Windows Server 2016 10.0 (amd64)

We are successfully monitoring SNMP for various devices, mostly VM based
Windows servers, but we have a pair of  'appliances' (pre-baked VMware
linux based servers provided by Adtran) that we run to manage our wireless
access points. We have turned on SNMP on those appliances and set the
OpenNMS system to monitor them but it always fails with the following
message:

The Node with Id: 88; ForeignSource: BlueSocket-Controllers;
ForeignId:1505495340989 has aborted for the following reason: Aborting
node scan : Agent failed while scanning the IP address tables :
java.lang.IllegalArgumentException: cannot convert 172.16.0.66 to an
InetAddress

Well, in all the references I can find in the forums to similar problems
the value being presented clearly ISN'T an IP address (e.g. "1") but this
seems valid to me. I dug a little deeper using snmpwalk. On this appliance
when I pull the IP address table I get this:

OID=.1.3.6.1.2.1.4.20.1.1.1, Type=OctetString, Value=172.16.0.66
OID=.1.3.6.1.2.1.4.20.1.2.1, Type=Integer, Value=1
OID=.1.3.6.1.2.1.4.20.1.3.1, Type=OctetString, Value=255.255.252.0
OID=.1.3.6.1.2.1.4.20.1.4.1, Type=Integer, Value=1
OID=.1.3.6.1.2.1.4.20.1.5.1, Type=Integer, Value=1500
Total: 5

Whereas a working Windows server gives me this:

OID=.1.3.6.1.2.1.4.20.1.1.127.0.0.1, Type=IpAddress, Value=127.0.0.1
OID=.1.3.6.1.2.1.4.20.1.1.172.16.0.10, Type=IpAddress, Value=172.16.0.10
OID=.1.3.6.1.2.1.4.20.1.2.127.0.0.1, Type=Integer, Value=1
OID=.1.3.6.1.2.1.4.20.1.2.172.16.0.10, Type=Integer, Value=5
OID=.1.3.6.1.2.1.4.20.1.3.127.0.0.1, Type=IpAddress, Value=255.0.0.0
OID=.1.3.6.1.2.1.4.20.1.3.172.16.0.10, Type=IpAddress, Value=255.255.252.0
OID=.1.3.6.1.2.1.4.20.1.4.127.0.0.1, Type=Integer, Value=1
OID=.1.3.6.1.2.1.4.20.1.4.172.16.0.10, Type=Integer, Value=1
OID=.1.3.6.1.2.1.4.20.1.5.127.0.0.1, Type=Integer, Value=65535
OID=.1.3.6.1.2.1.4.20.1.5.172.16.0.10, Type=Integer, Value=65535
Total: 10

Ignoring the loopback connection on the Windows server the difference
seems to be that it supplies the IP address in a field type of "IpAddress"
whereas the appliance uses "OctetString". This is assume is the root of
the problem. 

Given that I don't have any way to modify the appliance, is there anything
I can do on the OpenNMS end to try and make it accept the value? These
appliances tend to go into meltdown now and then so I'd love to get CPU
threshold monitoring working on them, but right now the SNMP poll just
fails. 

Thanks for any help!

Regards,
Mike Wells
Director of Technology
Town of Westford, MA

Tel : 978-399-2411



________________________________________________________________
All email messages and attached content sent from and to this email
account are public records unless qualified as an exemption under the [
http://www.sec.state.ma.us/pre/preidx.htm ]Massachusetts Public Records
Law.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss