CA UIM discovery_server is discovered the dual origin for the VMware Virtual Center/ESX Server.
It may be because of the fail over, DR. Environment or duplicate MAC addresses appearing on the network
CA UIM v8.5 & Later VMware probe 6.51
Follow the below step:
Upgrade the Robot from 7.63 to 7.80
Upgrade the VMware probe from 6.51 to 6.60
Override the origin on the VMware probe's robot/hub to match the other origin.
sing Raw Configure, add the following to the <setup> section of theVMware probe config:
prevent_vcenter_correlation = true
Deactivate the VMware probe
Delete all the files from \nimsoft\niscache\ on the VMware probe robot, just in case there is leftover data with the old origin
Use the discovery_server callback "remove_master_devices_by_cskeys" to delete the affected machinesfrom discovery (or possibly clear it all out) . You can find the cskey from cm_computer_system table.
Activate the VMware probe so it will publish all its discovery data
Configure the discovery_server probe with excluded_ip_addresses
Restart discovery_server so this change takes effect.
The VMware probe will republish its topology data which will include a unique internal ID for the vcenters, so the discovery_server will not correlate with other vcenter.
The Nimsoft VMware monitoring probe has the capability of handling all the common monitoring and data collection tasks on VMware VC/ESXServers. The probe collects and stores data and information from the monitored system at customizable intervals.