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
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Comment |
[ 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).. ] |
| Comment |
[ 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).. ] |