Search This Site

myTemplate

A Real World Template Design for Joomla

Login to VirtualVCP

In order to leave comments, please log in.





Lost Password?
No account yet? Register

Vi-Pedia Virtualization Wiki

Virtualization Wiki

RSS Feeds

Support VirtualVCP

Information and Resources on this site are 100% free, however it costs money to run this site. Please help support this site by giving a donation.

Patching ESX 3.5 Using esxupdate PDF Print E-mail
User Rating: / 4
PoorBest 
Written by Rynardt Spies   
Wednesday, 18 June 2008

Just a quick guide to patching a standalone ESX 3.5 Server using esxupdate from the service console:

Download all available patches to your local computer from the following link: (ALSO DOWNLOAD THE FILE CALLED contents.zip)

VMWare Patch Download Page

Decide where to place the patches in a partition with enough space to accommodate the patches on the target ESX Server. It is not recommended to use the root ( / ) partition at all. A good strategy is to create a directory called updates under the /var partition.

To do so, log onto the service console of the ESX Server as the root user. Then do:
mkdir /var/updates

Using a utility like Veeam FastSCP, copy all downloaded patches to the newly created directory on the ESX Server.

One all the patches have been copied to the ESX Server, log on to the service console of the ESX Server as the root user.

Browse to the directory where the patches reside:
cd /var/updates

Now we need to unzip all the .ZIP files. Now, there should be quite a few files, so it would be painful to unzip them one-by-one, so we are going to use a "for" loop to do the trick for us.

To unzip all the .ZIP files in one go, execute the following command. MAKE SURE YOU ARE IN THE DIRECTORY WHERE THE ZIP FILES RESIDE! ALSO MAKE SURE TO TYPE THE COMMAND EXACTLY AS BELOW, EVEN WITH THE x_file!
for x_file in *.zip; do unzip $x_file; done

This command will unzip all the zip files, each in its own directory, except for contents.zip, which will be unziped into the directory where the command was executed from. In this case /var/updates.

Now, in order to perform patching operations on an ESX Server, the server needs to be in "Maintenance Mode". This means that all Virtual Machines on the server will have to be powered off.

Make sure all Virtual Machines are powered off, then place the ESX Server in Maintenance Mode. You can do this using the Virtual Infrastructure Client or by simply executing the following command from the service console: (Must be run as the root user. Note that as far as I'm aware, this command is not supported by VMware Support but does work perfectly well):
vimsh -n -e /hostsvc/maintenance_mode_enter

Once the ESX Server is in Maintenance Mode, we can start esxupdate and apply the patches:
cd /var/updates
esxupdate -d /var/updates/ scan
esxupdate -d /var/updates/ update

 

After the patches are applied to the server, the server will reboot. To exit Maintenance mode, run the following command:
vimsh -n -e /hostsvc/maintenance_mode_exit

** This is only a basic guide to patching an ESX Server from the service Console using a local patch repository with esxupdate. For more information on ESXUPDATE and patch management, refer to the VMware ESX Server 3 Patch Management Guide available here

**Please report any error in this document here

 

Comments
RSS
Carlos  - No luck with esxupdate   |2009-04-02 20:13:44
it did not create a content.xml at /var/updates


[root@host145 updates]# pwd
/var/updates
[root@host145 updates]# ls
ESX350-200901401-SG ESX350-200901402-SG
ESX350-200901401-SG.zip ESX350-200901402-SG.zip




[root@host145 updates]# for x_file in *.zip; do unzip $x_file; done
Archive: ESX350-200901401-SG.zip
creating: ESX350-200901401-SG/
inflating: ESX350-200901401-SG/VMware-esx-backuptools-3.5.0-143128.i386.rpm
inflating: ESX350-200901401-SG/VMware-esx-vmkernel-3.5.0-143128.i386.rpm
inflating: ESX350-200901401-SG/VMware-esx-vmx-3.5.0-143128.i386.rpm
inflating: ESX350-200901401-SG/VMware-hostd-esx-3.5.0-143128.i386.rpm
inflating: ESX350-200901401-SG/descriptor.xml
creating: ESX350-200901401-SG/headers/
extracting: ESX350-200901401-SG/headers/VMware-esx-backuptools-0-3.5.0-143128.i386.hdr
extracting: ESX350-200901401-SG/headers/VMware-esx-vmkernel-0-3.5.0-143128.i386.hdr
extracting: ESX350-200901401-SG/headers/VMware-esx-vmx-0-3.5.0-143128.i386.hdr
extracting: ESX350-200901401-SG/headers/VMware-hostd-esx-0-3.5.0-143128.i386.hdr
inflating: ESX350-200901401-SG/headers/header.info
inflating: ESX350-200901401-SG/headers/contents.xml
inflating: ESX350-200901401-SG/headers/contents.xml.sig
inflating: ESX350-200901401-SG/contents.xml
inflating: ESX350-200901401-SG/contents.xml.sig
Archive: ESX350-200901402-SG.zip
creating: ESX350-200901402-SG/
inflating: ESX350-200901402-SG/VMware-esx-scripts...
Rynardt Spies  - No Luck With ESXUPDATE     |2009-04-02 20:15:58
You need to download contents.zip from the patch download page as well in order for ESXUPDATE to work in this way.
Only registered users can write comments!

3.26 Copyright (C) 2008 Compojoom.com / Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved."

 
< Prev