Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > ESX hosts are not correctly assigned under a vCenter after synchronizing VMan and IVIM

ESX hosts are not correctly assigned under a vCenter after synchronizing VMan and IVIM

Updated: 3-29-2017

Issue

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.

Environments

  • Virtualization Manager (VMAN)
  • Integrated Virtual Infrastructure Monitor (IVIM)
  • Virtual Infrastructure Monitor (VIM)

Cause

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.

Resolution

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.

  1. In the Orion Web Console, go to Settings > Virtualization Settings > VMware Settings, and disable polling for the duplicated standalone ESX hosts.
  2. Wait until a few polls are completed to make sure that all virtual machines are moved under hosts assigned to a vCenter.
  3. Delete the stand-alone ESX hosts.

The virtual machine statistics will be polled through the vCenter.

Last modified

Tags

Classifications

Public