Ensure a valid forward and reverse DNS entry are created on the Domain Controller.
To change a node hostname in vRealize Operations Manager:
vRealize Operations Manager 6.0.x :
- Use the vRealize Operations Manager administrator interface to take the cluster offline.
- Log in to the console of the vRealize Operations Manager node.
- To prevent the vApp from updating the host file to the reverse DNS value when the node is restarted, remove the vami_setnetwork file by running this command:
rm /opt/vmware/etc/vami/flags/vami_setnetwork
- Change the hostname by running this command:
/opt/vmware/share/vami/vami_set_hostname new-hostname
- Restart the node.
- Use the vRealize Operations Manager administrator interface to bring the cluster online.
vRealize Operations Manager 6.1.x and later:
- Log in to the vRealize Operations Manager admin UI.
- Take the cluster offline.
- Log in to the node as root.
- Update the hostname by running this command:
$VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/bin/sethostname.py NewHostName
Where NewHostName is the hostname you want to use.
- Restart the node from vCenter.
- Use the vRealize Operations Manager admin UI to bring the cluster online.
Additional Information:
If the hostname was used when adding a node to the cluster, the entry needs to be updated in the
casa.db.script file
:
- Log in to VMware vRealize Operations Manager Master node as root through SSH or console.
- Stop the casa service, by running this command:
service vmware-casa stop
- Back up the casa.db.script file, by running this command:
cp /storage/db/casa/webapp/hsqldb/casa.db.script /tmp/casa.db.script.old
- Open /storage/db/casa/webapp/hsqldb/casa.db.script file using a text editor.
- Search for any instance of the old hostname in the ip_address field, and replace it with the new hostname.
- Save and exit the file.
- Start the casa service by running this command:
service vmware-casa start
- Repeat steps 1 to 7 on all Analytic nodes in the cluster.
For translated versions of this article, see: