Hi,
We have a problem with the Ethernetbox from Messpc. We created a node for the Ethernetbox and we got the message that the device is not capable with snmp in the object properties. Is there a way to set the value from "isSNMP" manually to true?
Best regards
Hi!
isSNMP attribute set automatically when server is able to communicate with the node over SNMP. Check that device responds to SNMP. You can use nxsnmpget/nxsnmpwalk command line tools for diagnostic. Check that correct SNMP community is set in node's communication properties.
Best regards,
Victor
Hi,
Thanks for the reply. We tested it with the tools, but the host doesn't answer(request timed out). However we tested it with the mibbrowser from ireasoning and with the snmptester from the Paessler AG. We got the values with both tools. We used the snmptester on the server where we installed netxms as well as on a client. We also used an other ethernetbox, but the same problem occurred. The problem occured after the update from the netxms version 1.0.7 to 1.2.7.
Edit: We installed Netxms (V1.2.7) on an other Server but the result was the same.
Best regards
So, version 1.0.7 was working? That means some bug in NetXMS SNMP library. Is it possible to send me captured packets sent between NetXMS and ethernetbox? Also, is it possible that ethernetbox responds from IP address different then IP address used for request?
Best regards,
Victor
Hi,
I send you the captured packets. It contains captured packets from the snmptester (first one) and from nxsnmpget (second one).
Best regards
Hi!
I see that snmptester uses SNMP version 1. Is it possible that device does not support SNMP version 2c? Can you try to run nxsnmpget with -v1 option?
Best regards,
Victor
Hello,
The -v1 option worked, but we selected in the node properties communication snmpv1.
Best regards
Can you please do configuration poll on that device from console and send me the output?
Best regards,
Victor
Here is the output:
[06-Jun-2013 14:09:00] Sending poll request to server...
[06-Jun-2013 14:09:00] Poll request accepted
[06-Jun-2013 14:09:00] Starting configuration poll for node test sensorbox
[06-Jun-2013 14:09:00] Checking node's capabilities...
[06-Jun-2013 14:09:00] Checking SNMP...
[06-Jun-2013 14:09:56] Capability check finished
[06-Jun-2013 14:09:56] Checking interface configuration...
[06-Jun-2013 14:09:56] eUnable to get interface list from node
[06-Jun-2013 14:09:56] w Interface "unknown" is no longer exist
[06-Jun-2013 14:09:56] Interface configuration check finished
[06-Jun-2013 14:09:56] Checking node name
[06-Jun-2013 14:09:56] Node name is OK
[06-Jun-2013 14:09:56] Finished configuration poll for node test sensorbox
[06-Jun-2013 14:09:56] Node configuration was not changed after poll
[06-Jun-2013 14:09:56] Poll completed successfully
Best regards
Another possible problem could be if device does not support standard MIBs. NetXMS server tries to retrieve OIDs .1.3.6.1.2.1.1.2.0 and .1.3.6.1.2.1.1.1.0 to check if device can respond to SNMP. If device does not support system MIB for some reason then server will not be able to detect SNMP agent on it. Can you check that device responds to these OIDs?
Best regards,
Victor
The device responded to both requests however it replied with null.
Best regards
That's the problem, server expects correct response here. Is there any standard MIBs this device supports? Anything under .1.3.6.1.2.1.1 or .1.3.6.1.2.1.2?
Best regards,
Victor
There aren't any standard MIBs. It begins under .1.3.6.1.4.1.14848:
http://www.messpc.de/MIB/betternetworks_ethernetbox.mib (http://www.messpc.de/MIB/betternetworks_ethernetbox.mib)
Best regards
Hello,
Is there a way to avoid this expectation of the standard MIBs?
Best regards
Hi!
Not without changing the server code. I've added a feature request for 1.2.8 release: https://www.radensolutions.com/chiliproject/issues/291 (https://www.radensolutions.com/chiliproject/issues/291).
Best regards,
Victor
Thanks for considering our problem for the 1.2.8 release.
Best regards