Knowledge Base

Summaries and Symptoms

Issues fixed in this patch (and their relevant symptoms, if applicable) include:

• The esxcfg-auth command now works correctly when NIS options are specified, following the -p option. (PR 253428)
  
  
• The Kerberos 5 options of the esxcfg-auth command now work as expected. (PR 249668)
  
  
• The esxupdate command now shows an accurate error message when a required file is missing on the FTP/HTTP depot. (PR 239398)

  Symptoms: The following message displays:

  ERROR: XML Processing Error: no element found: line 1, column 0

  The correct message should be:

  ERROR: File does not exist: <path>/contents.xml

• The esxupdate command now has a --help option. (PR 255897)
  
  
• Updates to the vm-support script, which is used by VMware Technical Support to collect logs and other configuration files from ESX Server hosts to assist in troubleshooting problems with their systems.
  
  
  • The vm-support script now collects old_cores only with the -a option. (PR 253318)
    
    
  • The vm-support script now collects data from /var/lib/iscsi. (PR 249054)
    
    
  • Fixed a typographic error in the output message for vm-support –X. (PR 256414)
    
    
  • The vm-support script now collects the contents of the aam directory. (PR 223277)
    
    
  • The vm-support script now collects the vpxa.cfg file. (PR 229414)
    

Deployment Considerations

None

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.