Whats the use of this Discovery property "glide.discovery.enforce_ip_sync"

[Nik Amy]

Hi,

We are using Discovery. Can anyone tell me whats the use of this Discovery property "glide.discovery.enforce_ip_sync".

OOB that property is set to true. So whats happening in our case is that, when a machine is having multiple NIC's/IP's, then each time that machine is getting discovered, the IP is getting changed on the form which is confusing.

I would just like to understand in general:

1. Why OOB that property is set to TRUE as its changing the IP and is confusing

2. In general, when a machine is having multiple IP's, whats the best practice to capture the right IP address, and how.

 BR,

Nik

[anusha_narapura · Accepted solution]

Hi Nik,

glide.discovery.enforce_ip_sync (OOB value is ‘true’)
glide.discovery.exclude_ip_sync_classes(OOB value is ‘cmdb_ci_lb’)

You can add the specific CI table to the property glide.discovery.exclude_ip_sync_classes if you do not want to get your IP changed multiple times. for .e.g. if you want to do for N/W devices, add cmdb_ci_netgear to the property (Note: property values are comma separated list of values). Hope this helps!

Regards,

Anusha.

[Nik Amy]

Clear, thanks!

But still one question left in my mind.

OOB servicenow can use to set the Management IP address only for any CI.

Why does servicenow give that option of changing the IP address, rather it can just update them all in the related list when a CI has multiple IP's.

[arordeep]

We are facing the same issue with IP Switches and Routers, they keep on flip flopping between different IPs.

We have changed the values for below two properties:

glide.discovery.enforce_ip_sync to 'true'

glide.discovery.exclude_ip_sync_classes to 'cmdb_ci_lb,cmdb_ci_ip_switch,cmdb_ci_ip_router'

Still on discovering IP Router & IP Switches via Discovery schedule, they flip flop between different IPs.

Please advise, what else we can check?

[chuckm]

If you are using Pattern-based discovery for switches and routers, the issue might be caused by duplicate switch discoveries in the same discovery schedule. The issue is documented in this community article:

Duplicate Discovery of Switch in One Discovery Schedule

One of the issues caused by duplicate switch discovery is the flip flop between different IP addresses per item #4. The duplicate discoveries cause multiple issues:

1. The discovery schedule takes longer to complete.
2. The Discovery Log and ECC Queue fills up with additional messages from the duplicate discoveries.
3. Additional bandwidth is being used across the network.
4. The CI Audit History fills up with additional IP Address changes for each duplicate duplicate discovery.