Knowledge Base

Summaries and Symptoms

Includes changes from the Jan. 30, 2009 release of patch ESX350-200901405-BG for ESX 3.5 Update 4. This patch was previously documented as follows:

• Changes to iSCSI LUN path policy were not persistent across reboot. This fix makes sure the multi-path configurations are refreshed after iSCSI volumes are discovered, so changes persist after rebooting the ESX system.
  
  Symptoms seen without this patch: Setting changes to pathing or policy preferences on the iSCSI software initiator return to their defaults after rebooting the ESX host. (Unlike iSCSI hardware initiator and fibre initiator settings, which are saved across reboots.)
  
  Note: If the path policy was manually configured by the user at anytime in the past, the next reboot after the patch is installed will set the path policy to the manually-configured value.
  
  
• If you customized the /etc/syslog.conf as described in the Basic System Administration guide, changes to the file were overwritten when you upgraded or patched the ESX system.
  
  The syslog.conf file was backed up only when syslog.conf.orig did not exist. This fix changes the backup file to syslog.conf.orig.<year_month_day_hour> so that the configuration file is always backed up.

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table, above.

Patch Download and Installation

See the VMware Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX Server 3.5 hosts.

To update ESX Server 3.5 hosts when not using Update Manager, download the most recent patch bundle from http://www.vmware.com/download/vi/vi3_patches_35.html and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 Patch Management Guide.