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.

Creating custom firewall rules in VMware ESXi 5.0

webmaster's picture
There is a defined set of firewall rules for ESXi 5.0 for Incoming and Outgoing connections on either TCP, UDP, or both.
You may be required to open the firewall for the defined port on TCP or UDP that is not defined by default in Firewall Properties under Configuration > Security Profile on the vSphere Client.
This article provides instructions on creating custom firewall rules in ESXi 5.0 via the command line.
Note: Custom firewall rules can be created only for those ports that are defined by default in the Firewall Properties under Security Profile on the vSphere Client.


By default, there is a set of predefined firewall rules that can be enabled/disabled for the ESXi host from the vSphere Client.

These firewall services can be enabled/disabled for the defined ports (UDP/TCP) from the vSphere Client. However, if you need to enable the service on a protocol that is not defined, you must create new firewall rules from the command line.

For example, the DNS Client service can be enabled/disabled only on UDP port 53.

To enable DNS for TCP:

Cloning and converting virtual machine disks with vmkfstools in ESXi 4.1

webmaster's picture

This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another.

The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk (.vmdk) format into another.

Note: The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats.

To convert a virtual machine disk from one type to another:

Convertir máquina Virtual desde servidor VMWare ESXi 4.1 a WMWare Workstation 10

webmaster's picture

Explicamos paso a paso como convertir una máquina Virtual desde un servidor VMWare ESXi 4.1 a WMWare Workstation 10 utilizando el VMware vCenter Converter Standalone Client.

En nuestro caso teníamos la necesidad de instalar una máquina virtual windows XP Professional SP3 en nuestra estación de trabajo local que es un Ubuntu Desktop 13.04 utilizando el nuevo WMWare Workstation 10 que habiamos instalado para entornos virtuales y esa máquina virtual ya la teníamos instalada y corriendo perfectamente en uno de nuestros servidores VMware ESXi 4.1, asi que la mejor forma era convertir la maquina para que pudiese ser leida en un entorno WMWare Workstation 10 y después trasladarla a nuetro Ubuntu Desktop 13.4

A través de Vsphere Client accedemos a la administración de nuestro VMware Server ESX 4.1 y vemos las máquinas alojadas en el mismo comprobando su estado.

Instalar VMWare Workstation 10 en Ubuntu 13.04 Desktop

webmaster's picture

Explicamos los pasos a seguir pata instalar la versión de Vmware workstation 10 que funciona a la maravilla en Ubuntu 13.04 Desktop después de que nos bajáramos de nuestro repositorio Wmware ESXi 4.1 una imagen de Windows XP Professional 32 bits SP3 y nos diera bastante problemas al intentarla correr en Oracle VirtualBox 4.2 instalada en nuestra máquina.

Disabling and enabling VMware Web Access on an ESX host

webmaster's picture

This article provides steps to disable VMware Web Access services and prevent the login user interface from appearing via http and https. It also provides steps to enable VMware Web Access services once again in the future.
Note: This procedure does not affect other access methods such as via the VMware Infrastructure or vSphere Client or through the APIs.


To disable VMware Web Access:

   1. Log in as root to the ESX host using an SSH client.
   2. Run this following command to stop the VMware Web Access service:

      service vmware-webAccess stop

   3. To prevent the service from starting again upon reboot, run the command:

      chkconfig –-level 345 vmware-webAccess off

   4. After disabling the Web Access service you can browse the index page of the ESX host and download the VMware Infrastructure or vSphere Client from it, but you cannot log into Web Access from the page.

To enable VMware Web Access:

   1. Log in as root to the ESX host using an SSH client.