- My View
When I view the CI for a virtual machine I get several host ESX servers related to the VM. The discovery not remove old relationships. Shouldn't a vCenter discovery just leave the current ESX host relationship? Has anyone else seen this or have a solution.
Build tag: glide-helsinki-03-16-2016__patch9-hotfix0a-03-17-2017
The following is what the documentation states:
When a vCenter CI, such as a virtual machine, is removed, the ServiceNow instance marks it as "stale" in the CMDB, using either of these procedures:
- When Discovery runs, it creates an audit record in the CMDB Health Result [cmdb_health_result] table for the missing CI and marks the CI "stale".
- If the ServiceNow instance is configured to collect vCenter events, the system can also create a "stale" audit record for the CI in the CMDB Health Result [cmdb_health_result] table from the VmRemovedEvent event, without having to run Discovery.
I hope this helps!
It's not that the CI is removed, but the CI relationship between the VM and the ESX host has changed and the old relationships are not removed.