Home

Changing the IP address, default gateway, and hostname of the Service Console in ESX

webmaster's picture

This article provides steps to change the Service Console IP address, gateway address, and hostname on an ESXi 4.x.

Note: ESX 4.0 Update 2 introduces a new tool that simplifies the process of creating or restoring networking in the ESX service console. For more information, see Configuring or restoring networking from the ESX service console using console-setup (1022078).

Note: To change the IP network information on an ESXi host, see Configuring the ESXi Management Network from the direct console (1006710).

 

Changing settings from the physical or remote console connection

Changing the IP for the Service Console must be done from the physical console or through a remote console session. If you make changes through a network connection such as SSH, network connectivity to the Service Console disconnects because the Service Console's network interface changes.

  1. Run this command to set the IP address:

    [root@server root]# esxcfg-vswif -i a.b.c.d -n w.x.y.z vswif0

    where a.b.c.d is the IP address and w.x.y.z is the subnet mask.

    Note: In this example, vswif0 is the Service Console adapter that is the interface to which you are applying the IP address change.
     

  2. Open the /etc/hosts file with a text editor and modify it so that it reflects the correct IP address and hostname.

    Note: You are required to edit files on an ESX host. For more information, see Editing files on an ESX host using vi or nano (1020302).

    Note: You may also need to verify and change the file /etc/vmware/esx.conf file for the hostname and IP address.
     

  3. To change the default gateway address and the hostname, edit the /etc/sysconfig/network file and change the GATEWAY and HOSTNAME parameters to the proper values.
     
  4. For the changes to take effect, restart the network service with the command:

    [root@server root]# service network restart

    Note: If you are required to edit the hostname, then you must reboot the host.

    Note: This command breaks any current network connections to the Service Console, but virtual machines continue to have network connection. If the ESX host is managed by VirtualCenter or vCenter Server, you may have to remove and re-add the host to the inventory. For more information, see ESX not working properly in VirtualCenter after IP address change (1005633).

Note: Making changes to IP and DNS server settings can have a negative impact on the normal operation of ESX/ESXi, particularly in HA clustered environments. For more information, see Identifying issues with and setting up name resolution on ESX/ESXi Server (1003735).

Note: If the changed IP does not persist across a reboot, try deleting and recreating the Service Console vswif management interface. For more information, see Recreating Service Console networking from the command line (1000266).

Changing the hostname without rebooting

To dynamically change the hostname, run the command:

[root@server root]# hostname newname

Note: This command creates a temporary hostname change. This change is lost when the system is rebooted.

Changing the DNS server settings

To change the DNS server settings, update the nameserver IPs and search domain in the /etc/resolv.conf file.

Changing settings in VMware vSphere or Infrastructure Client

To change the hostname, domain, DNS servers, and default gateway in VMware vSphere or Infrastructure Client:

  1. Highlight the ESX host and click the Configuration tab.
  2. Click DNS and Routing.
  3. Click Properties.
  4. To change the hostname, domain, and DNS servers, click the DNS Configuration tab and enter the appropriate values.

    Note: Disable VMware High Availability if you do not want virtual machines to failover during the hostname IP change.
     

  5. To change the default gateway, click the Routing tab and enter the appropriate value.
  6. Reboot the ESX host for the changes to take effect.
  7. Reconnect the ESX host to vCenter Server with the new IP address.

Generating new certificates for the ESX host

The ESX host generates certificates the first time the system is started. Under certain circumstances, it might be required to force the host to generate new certificates. Typically new certificates only need to be generated if the hostname is changed or the certificates are deleted accidentally.

Each time you restart the vmware-hostd process, the mgmt-vmware script searches for existing certificate files (rui.crt and rui.key). If the files cannot be found, new certificate files are generated.

To generate new certificates:

  1. Put the host into Maintenance Mode.
     
  2. In the directory /etc/vmware/ssl, back up any existing certificates by renaming them with these commands:

    [root@server root]# mv /etc/vmware/ssl/rui.crt /etc/vmware/ssl/orig.rui.crt
    [root@server root]# mv /etc/vmware/ssl/rui.key /etc/vmware/ssl/orig.rui.key

    Note: If you are regenerating certificates because you accidentally deleted them, you do not have to rename them.
     

  3. Reboot your host to allow it to begin using the new certificate, or restart the host services:
    1. Restart hostd using this command:

      service mgmt-vmware restart
       

    2. Restart vmkauthd using this command:

      service vmware-vmkauthd restart
       

  4. Exit Maintenance Mode.
     
  5. Confirm that the ESX host successfully generated new certificates by running this command and comparing the time stamps of the new certificate files with orig.rui.crt and orig.rui.key:

    [root@server root]# ls -la /etc/vmware/ssl/rui*

Notes:

Contacto: 
webmaster