After integrating Virtualization Manager with IVIM/VIM, ESX hosts are duplicated and not correctly assigned under vCenters. The issue occurs with ESX hosts which have different hostnames in Virtualization Manager and IVIM/VIM. Prior to resolving, SolarWinds recommends backing up your database, and creating a snapshot if your database is on a VM.
The issue occurs if the Host Identification as displayed in the Host Configuration page of the vSphere Client is not the same as the hostname under which the host was added to the vCenter.
In this case, a duplicate host is created, and most of the virtual machines will be switching in the Orion Web Console between the host located under the vCenter and the duplicate host located outside the vCenter.
The issue mainly occurs when ESX hosts are polled directly, which is not recommended.
Warning: The following workaround may lead to losing historical data of the monitored virtualization entities (hosts and virtual machines). Before carrying out this procedure, make sure that you back up your database.
The virtual machine statistics will be polled through the vCenter.