Werk #7500: Being more robust against duplicat engineIDs when monitoring SNMPv3 devices
| Component | Inline SNMP | ||
| Title | Being more robust against duplicat engineIDs when monitoring SNMPv3 devices | ||
| Date | Jun 5, 2015 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
The engineID is defined to be a globally unique identifier of a SNMPv3 device, but it happens that users configure the same engineID multiple times for different devices, which made Check_MK only talk to one of them and reporting "No Response from host (Timeout 0/-24)" for the other devices. This has been changed now that Check_MK disregards the misconfiguration and works as usual.