Applications Systems
Cannot remove the orphaned/non-existing ESX hosts from the Virtualization Assets
The orphaned / non-existing hosts are still displayed or present in the Virtualization Assets even if it is deleted as a node.
First published date
Last published date
Overview
First Verify if they are ESX that have been decommissioned OR if are they still managed by a VCenter that VMAN is monitoring and they were just placed in a disconnected state.
Disconnecting a managed host does not remove it from vCenter Server it will only temporarily suspends all monitoring activities that vCenter Server performs. It will appear with a grey status in Orion.
If this is the case and we manually delete them in the VIM_Hosts table in the db, VMAN will rediscover them when it polls the VC where those host are still in and put them back.
Product section
Cause
Resolution
Even if the node entry is deleted as long as the ESX is still managed by the VCenter it will appear in the VMAN summary.
To remove the host you can either:
- Modify the service account used to add the VC to not have access to the specific ESX host
- Remove the ESX in vsphere.
If it still displayed even the conditions above are checked or done. Use the following steps below on the Orion Server:
- Go to the Database Manager then query VIM_Host
- Enable table editing and then delete the row of the target hosts.
- Check the Virtualization Summary if the hosts are still present
- Check the tables: vim_hosts, vim_vcenter, vim_datacenter
- Use VCenterID from vim_vcenter table to find all of the DataCenterIDs from the vim_datacenter table.
- Use the DataCenterIDs to get HostIDs from vim_hosts table
- Manually remove those hosts with those IDs from vim_hosts table
- Manually remove the datacenters with the VCenterID
- Manually remove the VCenter