I've no idea how you've managed to make it do that. Delete the device and re-add it.
adam. On 2018-01-09 09:48:20, Alberto Busso alberto@busso.net wrote: The device is a Mikrotik RB922UAGS-5HPacD routerboard, running RouterOS v. 6.40.4, but behaviour is the same with other versions I have.
On the Mikrotik user manual there is a cryptic statement about EngineID parameter that can be manually set in the SW configuration.
Note: engine-id field holds the suffix value of engine-id, usually SNMP clients should be able to detect the value, as SNMP values, as read from the router. However there is a possibility that this is not the case. In which case, the engine-ID value has to be set according to this rule: <engine-id prefix> + <hex-dump suffix>, so as an example, if you have set 1234 as suffix value you have to provide 80003a8c04 + 31323334, combined hex (the result) is 80003a8c0431323334
I tryied to set it manually as suggested (including both prefix and suffix), but still no answer. I am getting in touch with Mikrotik to understand. I agree this is weird.
Concering the added device behaviour, I was referring to the two screenshot in annex. After adding the device, even if I get the "failed" response, I can see it in the list. But when I click e.g. on the "All Devices" item in the drop down list, I get the other screen where it is stated that there are no devices. Note that the device seems added with the proper IP address, since if I try to add it again, I obtain an error stating that it is there already. I can only delete it with delete_device before adding again. This looks strange, since I was expecting to have nothing added after a failed add_device operation.
Alberto
Il 08-01-18 22:23, Adam Armstrong ha scritto:
You seem to have skillfully omitted the only useful piece of information:
What is this device you're trying to add which has no snmpEngineID, and what idiot manufacturer created it?
We don't use snmpEngineID as a unique id in the database, so I'm not really sure what the error you're seeing is coming from. You also don't say what you're clicking on or where, the error you get doesn't seem to make sense for clicking on a device name on the devices page. You need to be much, much clearer with what's happening.
adam. On 2018-01-08 20:59:57, Alberto Busso alberto@busso.net [mailto:alberto@busso.net] wrote: Hi all,
I am a new user of observium and I am doing some tests with few devices before deploying it on a wider network.
When I try to add my first device (with -d option), it only partially works.
In the log I have only this error:
CMD[/usr/bin/snmpget -v2c -c *** -Pu -OQv -m SNMP-FRAMEWORK-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'172.16.192.102':'161' snmpEngineID.0]
CMD EXITCODE[0] CMD RUNTIME[0.0324s] CMD EXITDELAY[10ms] STDOUT[ No Such Object available on this agent at this OID ] SNMP STATUS[FALSE] SNMP ERROR[#1000 - Failed response]
So, it seems I am not getting the EngineID object.
Then at the end of the log I have this:
SQL[INSERT INTO `devices` (`hostname`,`sysName`,`status`,`snmp_community`,`snmp_port`,`snmp_transport`,`snmp_version`,`os`,`snmpEngineID`,`location`,`sysContact`) VALUES ('172.16.192.102','Terlapini RB Sottotetto','1','public','161','udp','v2c','routeros','','Gussago','Elsy')] SQL RUNTIME[0.04079700s] Devices failed: 1.
So, it seems that the script will try to add the device but with an empty EngineID field. The result is that the device is added (e.g. I can see it in the device when accessing e.g. via web interface, but when I click on it, it does not show up in the list with a reply that there are no devices matching the search criterias).
I also noticed that if I try to add a second device with same EngineID problem, the SQL INSERT will fail with ' duplicate key' error. I have the impression that the EngineID is used as a unique key in the SQL DB and if it is empty this may cause problems.
Am I right? In this case, I have to understand why I cannot get the EngineID from the device.
Tnx
Alberto
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]