How to manage duplicate IP addresses

Hello Teppo,

Thanks for the update. I spoke to the Product Manager for that PowerPack and they explained the intent behind the event policy is that the daily maintenance checks the IPs in the message collector's databases to check for duplicate devices. SL1 uses the secondary IP addresses for devices to match SNMP trap and Syslog messages if the primary IP is not in the trap or syslog packet. If there are duplicate IPs, it can cause issues with matching the message to the correct device. 

As the IPs are associated with interfaces, you cannot delete them from SL1. To address this, please select one of the following options:

1. Move one of these firewalls to a different CUG with a different message collector; or limit the MC collector's CUG membership so that the firewalls are not aligned to the same message collector.
2. Remove the IP from one of the devices using SQL and uncheck the Scan All IPs option for that device so that it does not return.
3. Suppress this event on the device, assuming the SNMP trap and syslog issue I described above is not a concern for these particular devices.

Antonio Andres

Principal Technical Support Engineer | ScienceLogic