Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Professional Edition
-
None
Description
I'am not sure, but I think if the devices snmpengineid changes after reboot Observium is doing a re-discover for this device. Some devices are not providing such engineid to detect a reboot, but I noticed that observium is still able to detect it maybe with using the sysUpTime? If i'am wrong let me know.
My question is now if it would be possible to add an config option to force a re-discover based on that reboot event? Or any other option to trigger a re-discover i.e. matching syslog, eventlog for specific text strings?
Attachments
Activity
ouch.. very strange, I did not change this particular part of the code, but I will check.
Mike,
After this change I have all devices log "snmpEngineID changed: (id here)-> (id here) (probably the device was replaced). The device will be rediscovered." on every poller run!
Not had time yet to look closer, just saw it in the logs this morning.
Ok, just added force rediscovery if sysDescr and sysObjectId (both) changed in r10254.
Yes, 2 questions.
- Okay. That was unknown to me.
- Mhh...what do you mean exactly? What could go wrong if we trigger a rediscover after reboot?
- Ah ok! Maybe a different version of operation system could also trigger a re-discover not only if sysDescr/ObjectId changes?
Not fully understand (seems as 2 questions).
1. snmpengineid in normal cases not should be changed after reboot.
2. reboot state is very bad case for re-discover device, this can produce some race conditions..
3. main (possible) condition for force re-discovery is change multiple main params (ie sysDescr, sysObjectId)..
derp, devel mistake, fixed in r10255.