Vmware

During the installation, if an esxupdate patch is available, the utility updates itself. If the initrd and driver

configurations require changes, the changes are made after all bulletins are installed.

For information on installing bulletins, see “Install Bulletins on an ESX 4.1 Host” on page 16. For information

on checking for patch dependencies, see “Scanning for Applicable Bulletins” on page 11.

Install Bulletins on an ESX 4.1 Host

The installation process is recorded in the esxupdate.log file. By default, this file is located in the

/var/log/vmware directory.

To install bulletins on an ESX host

1 Verify that the host has enough disk space to perform the installation.

See “Verifying Disk Space” on page 14.

2 From the service console, log on to the ESX 4.1 host as user root.

If you do not have direct access to the ESX 4.1 host, connect remotely to the service console using ssh.

3 If the depot is not on the ESX 4.1 host, type the following command to enable an outgoing connection for

the service console.

esxcfg-firewall --allowOutgoing

4 Scan the desired bulletins to determine if they are applicable.

See “To scan for applicable bulletins” on page 12.

5 Run esxupdate update command.

 To install all applicable bulletins in the depot:

esxupdate -m <metadataURL> update

 To install specific bulletins in the depot:

esxupdate -m <metadataURL> -b <Bulletin1> update

 To install all applicable bulletins in a bundle zip:

esxupdate --bundle <rollupBundleZipURL> update

6 If necessary, reboot the system.

7 Run the esxupdate query command to verify the installation was a success.

See “Verifying Bulletin Installations” on page 16.

8 When you are done accessing the depot, reset the service console firewall to high security:

esxcfg-firewall --blockOutgoing

Verifying Bulletin Installations

This command lets you verify all installed bulletins were installed correctly, that none were missing or had

the wrong version number.

To verify bulletin installations

1 If necessary, log on to the ESX 4.1 host as user root.

If you do not have direct access to the ESX 4.1 host, connect remotely to the service console using ssh.

2 If the depot is not on the ESX 4.1 host, type the following command to enable an outgoing connection for

the service console.

esxcfg-firewall --allowOutgoing

...