Network Management

Duplicate IP addresses causing nodes to be mapped as VMs in the SolarWinds Platform

If there is a router or a switch, for example, and the polling IP address matches the IP address of a virtual machine found on one of the VM hosts monitored in the SolarWinds Platform that device may be seen as a VM. The SolarWinds IVIM plugin maps virtual machines to their host based on the VM Mapping Order. By default, IP address is used for this task. Duplicate combination of IP address.

First published date

10/22/2018 7:46 PM

Last published date

3/26/2025 11:32 PM

Overview

If there is a router or a switch, for example, and the polling IP address matches the IP address of a virtual machine found on one of the VM hosts monitored in the SolarWinds Platform, that device may be seen as a VM.  

The mapping algorithm works with the list of potential candidates of Nodes that can be mapped to a specific VM. The list of candidates is created from many sources like all IP addresses of VM and Node, all MAC addresses of VM and Node, all DNSNames of VM, and Nodes.

Product section

Network Performance Monitor

Cause

The SolarWinds IVIM plugin maps virtual machines to their host based on the VM Mapping Order. By default, the IP address is used for this task. 

If we have the Same IP address (which may be on a secondary NIC) on a Virtual Machine and a Node, we may see incorrect mapping.

This issue also applies to VMAN.

Resolution

To Update settings 

  1. Access to the Advanced Configuration http://<SolarWinds hostname or ip address>/Orion/Admin/AdvancedConfiguration/Global.aspx 
    • https://support.solarwinds.com/SuccessCenter/s/article/Advanced-Configuration-access-in-Orion-Platform
  2. Search VMMappingOrder and then change the order to MAC,IP,HOSTNAME:
  3. Click save to apply the changes.
  4. Restart all services from the SolarWinds Platform Service Manager.
  5. Go to Start > All Programs > SolarWinds Platform > Database Manager.
  6. If your SolarWinds Platform database is not listed in the left pane, complete the following steps:
    1. Click Add Orion Server.
  7. Expand your SolarWinds database in the left pane.
  8. Right click the VIM_VirtualMachines table, and then click Query Table.
  9. Replace the default query with the query listed below and click Execute query.
    --START--
    
    Update VIM_VirtualMachines
    SET NodeID = NULL
    
    --END--
    
    -- 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.

     

  10. The NodeIDs will repopulate and mapped using the MAC addresses instead of IP addresses. This should be complete within 20 minutes.

Note: If the resolution above doe not fix the issue, kindly follow the procedure below.

1. Please go to the /Orion/admin/advancedconfiguration/global.aspx and change the VMMappingOrder to only MAC:
 

image.png

2. Then delete and re-add the physical server. It should be working fine after that procedure.