marvinms
Enthusiast
Enthusiast

Rename host - Follow up

I have "successfully"

Remaned a host

Moved it to a different building

Added it to a different Cluster

Running VM's on it

I am working out getting esXpress to reconfigure to the new name and I just notice that in the anaconda..... file.

The IP and Name of the old server settings are still there, should I be concerned with this, or is this the Build time configuration and needed if I want to rebuild the host from this file.

Thanks,

0 Kudos
8 Replies
Troy_Clavell
Immortal
Immortal

what happens when you type hostname at the service console?

Here's a good KB that outlines some steps you may want to look at if you haven't seen it.

http://kb.vmware.com/kb/4309499

0 Kudos
marvinms
Enthusiast
Enthusiast

It returns the correct current name of the host.

I'll take a look at the document.

Thanks,

0 Kudos
RParker
Immortal
Immortal

You pretty much change the contents of one file on the ESX host. /etc/host Change the name of the previous host name to the new one.

run service mgmt-vmware restart

Done. You can use nano or vi to change that /etc/host file.

0 Kudos
kcollo
Contributor
Contributor

Rparker probably gave the best advice here. Most people seem to forget to change the hostname in /etc/hosts file. If that is not editied, you can normally get the ESX host up on the network, added to a new cluster, but normally have random issues with hostd. When I change a server, I also go into /etc/sysconfig/network and hard code the IP there. Informaiton can be found in either the KB or

http://blog.colovirt.com/2008/10/20/changing-vmware-esx-3-ip-and-hostname/

Kevin Goodman

kevin@colovirt.com

http://blog.colovirt.com

0 Kudos
Troy_Clavell
Immortal
Immortal

Smiley Happy

0 Kudos
kcollo
Contributor
Contributor

Maybe I should read my posts before hitting submit. I mean that Troy gave the best advice Smiley Wink

Kevin Goodman

kevin@colovirt.com

http://blog.colovirt.com

0 Kudos
marvinms
Enthusiast
Enthusiast

Thanks for the help.

I went through all the documented processes and changed all the files, but the VMKernel Default Gateway was still the old one.

Working with support we made that change in the GUI of the vswitch (unchecking the vmotion box) to make it take.

Thanks,

0 Kudos
Troy_Clavell
Immortal
Immortal

glad to see you got it resolved.

please consider the use of the "correct" or "helpful" buttons to award points

0 Kudos