Discovery updating same hostname with incorrect IP

[Shraddha Dube]

Hi Community,

We are facing an issue in our prod instance related to ServiceNow Discovery and CMDB IP updates.

For a particular hostname, Discovery is updating different IPs across two CIs classes incorrect Ip for Linux server and correct IPs for Oracle cluster node, DNS Name, Router interfaces.

When we run quick discovery using the correct IP, Discovery completes successfully. Under Discovery status, IP is getting updated using Unix classifier, but in CMDB - the oracle cluster node and other class related to this shows correct IP, but Linux server class shows different (incorrect) Ip.

According to discovery status the CI should always update with the correct IP with same hostname under Linux server class and stop updating with alternate IPs for the same.

could anyone confirm if this is expected behavior due to multiple interfaces and explain us why Discovery is updating the same hostname with different IPs?

Note- We are part of the Discovery support team and cannot modify core rules in prod instances and this issue occurs only for 6 -7 hostnames, not all

Can anyone please help us understand the exact root cause and the recommended configuration or property setup to ensure only valid IPs update the Linux server class?

Thanks in advance!!