SNMPv3 devices have an engine identifier, which is used when polling the device and for determining the source of a trap. Devices with duplicate engineIDs are not compliant with the SNMPv3 standard.
However, some manufacturers do repeat engineIDs. How ENA handles duplicate engineIDs depends on which zone the duplicate engineID is in:
- ENA does not support duplicate engine IDs in the same zone - if you add a device to management that has the same engine identifier as another device in the same zone, ENA will not take it under management and the Inventory page will show a red cross icon under the Added column.
- ENA does support duplicate engine IDs in different zones - if you add a device to management that has the same engine identifier as another device in another zone, it will be taken under management.
If the engineID changes to a duplicate of another in the same zone after the device has been taken under management, ENA will raise a SNMPv3 Duplicate Engine ID event. You should consider reconfiguring one of the devices with a new unique engineID.