CIs are discovered twice when one of the IP Addresses should be ignoredIssue When discovering CIs that have multiple IP Addresses, there is a corner case where the additional IP Address(es) should be ignored but are in fact NOT ignored, and the CI is discovered again. In some cases this can be an issue for the customer as it can put a larger load on the CI. In cases on Linux where PBRUN is used, it can crash the box.ReleaseAny And ALLCauseWhen you look at the devices tab, for the additional IP Addresses, you should see: Identified, Ignored Extra IP, but in this case you will see Updated CI, which means that the CI was Discovered again. The cause for this is that the customer may have duplicate environments(different networks) for the same CIs with the same IP Addresses, on the same CMDB. Essentially they may call one environment Prod and the other Test, but what happens is that when these CIs are discovered, they create Duplicate IP Address records that point to each CI. When discovery runs, this scenario is braking Discovery's ability to detect the Extra IP Address and it is not ignored and thus an additional discovery is run.ResolutionUltimately, the solution here is to NOT use the same exact IP Address on the duplicate environment. This will avoid the issue altogether. In some cases this may not be an option, at which point a business rule should be created for the cmdb_ci_ip_address table to avoid creating the duplicate record.