Infrastructure Navigator lose configured hostname after a reboot

November 20, 2013 — 2 Comments

I found this error last week during a deployment in a customer. The vCenter Infrastructure Navigator appliance does not maintain its configured hostname after a reboot, it gets reset to the default localhost.localdom value.


Setting it again in the administration web interface doesn’t solve problem, it will be lost again after the next reboot.

The problem is in the vami_set_hostname script, it has a HOSTNAME variable set to localhost.localdom and if it fails to make the reverse lookup of the hostname from the IP address using the host command it will be set to the default value.


To fix this edit that file, it can be found on /opt/vmware/share/vami, and set the value of the variable to your hostname. After that reboot the appliance to check that everything works as expected.



2 responses to Infrastructure Navigator lose configured hostname after a reboot


    Or, set the PTR record, correct?

Trackbacks and Pingbacks:

  1. Installing and configuring VMware Infrastructure Navigator 5.8 « DefinIT - January 15, 2014

    […] If you want to change the hostname for the appliance, you can’t use the hostname command, or edit the /etc/HOSTNAME or /etc/hosts files – they will not persist across reboots. There’s a script that runs when the appliance reboots that checks the reverse DNS lookup for the primary IP address, and sets the hostname accordingly. If the script can’t see a DNS entry for the IP it will rename it to localhost.localdomain. (Credit to Juan Rey for this info) […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s