Correct an ESXi host mapped to the wrong SolarWinds Platform node in VMAN

An ESXi host can appear under the wrong SolarWinds Platform node in VMAN when its VMkernel IP address matches an IP address assigned to another monitored node. The host summary may then display the unrelated node or show incorrect CPU or memory capacity.

Use this procedure only when the symptoms and IP-address check support this mapping issue. Before changing the database, identify the affected ESXi host and verify the conflicting IP address and the host’s record in dbo.VIM_Hosts.

VMAN associated the ESXi host with the wrong SolarWinds Platform node in the dbo.VIM_Hosts table because the host’s VMkernel IP address matched an IP address on another monitored node.

1. Confirm that the affected ESXi host is displayed under the wrong SolarWinds Platform node and that its VMkernel IP address matches an IP address assigned to another monitored node.

2. Back up the SolarWinds Platform database before making any changes.

3. In Database Manager, locate the affected ESXi host’s record in dbo.VIM_Hosts. Verify the record against the host name and management/VMkernel IP details, and note its HostID.

   Important: Do not run the update unless the IP conflict is confirmed and the affected HostID is verified. If either is uncertain, investigate further before changing the database.

4. Open a new query against the SolarWinds Platform database. Replace <HostID> with the verified ID for the affected host, then run:

    -- Scripts are not supported under any SolarWinds support program or service.
    -- Scripts are provided AS IS without warranty of any kind. SolarWinds further
    -- disclaims all warranties including, without limitation, any implied warranties
    -- of merchantability or of fitness for a particular purpose. The risk arising
    -- out of the use or performance of the scripts and documentation stays with you.
    -- In no event shall SolarWinds or anyone else involved in the creation,
    -- production, or delivery of the scripts be liable for any damages whatsoever
    -- (including, without limitation, damages for loss of business profits, business
    -- interruption, loss of business information, or other pecuniary loss) arising
    -- out of the use of or inability to use the scripts or documentation.
   
    UPDATE dbo.VIM_Hosts
    SET NodeID = NULL
    WHERE HostID = <HostID>;

5. In the virtualization settings, select the affected ESXi host. When prompted to manage it as a node, select its management IP address.

6. Allow up to two hours for the association to refresh. Confirm that the ESXi host is associated with the correct SolarWinds Platform node and that its summary displays the expected node and capacity information.