IP switches location changes whenever mid server runs every month

[chandan2212]

Hi Team ,

There are two ip switches are there in the class (ip switch ) whenever mid server run on every month , company name changes every time and this is happen only two records in the IP switch(cmdb_ci_ip_switch).

Can you tell why the location are changes whenever the mid server runs on every month.

Thanks and Regards,

Chandan 

[Swapna Abburi]

Hi @chandan2212 

Please check if the location of ip switch getting updated with the location set in the corresponding discovery schedule? 

[Bhimashankar H · Accepted solution]

Hi @chandan2212 ,

It seems the root cause typically lies in how servicenow discovery updates the CMDB based on most recent scanned data.

There might be multiple causes but you can check the following quick once.

1. Data Variability: Only two switches might have ambiguous or intermittent SNMP/system data, or they're on overlapping subnets/VLANs, making their actual location/company unclear during Discovery runs.

2. Overlapping IP Ranges: If you have multiple Discovery schedules or IP ranges assigned to different MID Servers or locations, the switches could sometimes appear to "belong" to one location/company and sometimes another, depending on which MID Server or schedule discovers them at the time

3. Manual Updates Overwritten: Any manual change to company/location fields gets overwritten by automated Discovery on the next run if those fields are set by the Discovery process.

4. Switch Movement or Network Changes: If the network physically or logically reassigns a switch to a new location/company (through routing, VLAN configuration, etc.), Discovery may reflect this change every time, but only for those switches with ambiguous identification data

Check the discovery patterns, Review IP range assignment, configure reconciliation rules, Lock down the critical fields.

The location or company name on just two IP switch records is changing each month because ServiceNow Discovery is re-evaluating and updating those fields with each scan, likely due to inconsistent identification or overlapping configuration. Review Discovery configurations, assigned IP ranges, and reconciliation rules to diagnose and resolve repeated company/location changes

Thanks,
Bhimashankar H

-------------------------------------------------------------------------------------------------
If my response points you in the right directions, please consider marking it as 'Helpful' & 'Correct' Thanks!

[Bhimashankar H]

Hi @chandan2212 ,

I hope you saw my reply. 

If my response points you in the right directions, please consider marking it as 'Helpful' & 'Correct'. It will help future readers as well having similar kind of questions and close the thread.

Thanks,
Bhimashankar H