1 Title: Being more robust against duplicat engineIDs when monitoring SNMPv3 devices
9 The engineID is defined to be a globally unique identifier of a SNMPv3 device, but it happens
10 that users configure the same engineID multiple times for different devices, which made
11 Check_MK only talk to one of them and reporting "No Response from host (Timeout 0/-24)" for
12 the other devices. This has been changed now that Check_MK disregards the misconfiguration