- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2019 10:51 AM
Hello,
We've been facing an issue with AIX server where the IP address is being wiped out or IP Firewalls IP being added in the field. We run discovery every week and discovery writing the correct IP address to the server record but next day IP being wiped out or IP Firewall's IP being set in the filed and when I check the updated by it says 'system'. Please check the below screenshot, in this case 10.7.97.102 is the actual server IP. Does this happened to anyone, please let me know if anyone ever experienced and how to solve this issue. Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2019 10:01 AM
I found a system property called "glide.discovery.exclude_ip_sync_classes". On the property page add the CI class to the comma separated value list, IP won't get changed/ cleared off according to the NIC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2019 10:01 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2020 08:27 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2020 08:35 AM
arordeep,
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. I documented the issue 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:
- The discovery schedule takes longer to complete.
- The Discovery Log and ECC Queue fills up with additional messages from the duplicate discoveries.
- Additional bandwidth is being used across the network.
- The CI Audit History fills up with additional IP Address changes for each duplicate duplicate discovery.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2021 08:44 PM