Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Virtualization Manager (VMAN) > Error in synchronizing VMan and VIM when Orion is part of a domain

Error in synchronizing VMan and VIM when Orion is part of a domain

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 830 Votes: 0 Revisions: 8


This article is about Linux network/DNS configuration.



If Orion is part of a domain, host names may not be resolved correctly, which could lead to synchronization issues between VMan and VIM.


If Virtualization Manager does not use automatic network configuration (DHCP), then the search domain must be specified in the /etc/resolv.conf file to be able to use short domain names as datasource addresses.
If DHCP is used, the DNS servers and the search domain is filled automatically, and the content of this configuration file can be overwritten with data received from the DHCP server.

Consider the following example:

If a host named "esxhost1" is in the "" domain, then the full domain name is "".

If you have the search domain specified in /etc/resolv.conf, then you can use "esxhost1" as an address because it will be resolved to the same IP address as the "" full domain name.

In some cases, if Orion is running in the "" domain, it will only store the host name of the ESX or Hyper-V host in its short form. If the short form is used in Orion, this will prevent the VMan-VIM integration from mapping the entity correctly when the full domain name is used in VMan, because the "esxhost1" name that is stored in Orion does not equal the "" name that is stored in Virtualization Manager.



To be able to use short names as datasource address, modify the /etc/resolv.conf file:

  1. Open /etc/resolv.conf in a text editor.
  2. Add the following line to the file: search <Domain Name> where <Domain Name> is the name of the domain the Orion system belongs to.

Repeat these steps for every domain you want to have as search domain.
This way, when the DNS client is presented with a host name, it will apply every search domain provided in the /etc/resolv.conf file to resolve the host name, in the order you added them.

You can achieve the same result for a small amount of selected servers. You can directly map a name to an IP address in the /etc/hosts file to map the short name of the server to an IP address.

Last modified