Portal Home > Knowledgebase > VMware Knowledge Base > VMware ESX 3.5, Patch ESX350-200904402-SG: Updates ESX Scripts

VMware ESX 3.5, Patch ESX350-200904402-SG: Updates ESX Scripts

Details

Release Date: April 29, 2009 

Download Size: 
336 KB 
Download Filename: 
ESX350-200904402-SG.zip 
md5sum: 
627df36ab637a99cfc6f5ec6ac04c9c7 


Product VersionsESX 3.5
Build158874
Also see KB 1001179.
Patch ClassificationSecurity
Supersedes

ESX350-200802403-BG 
ESX350-200803208-UG 
ESX350-200804408-BG 
ESX350-200805502-BG 
ESX350-200806202-UG 
ESX350-200808202-UG 
ESX350-200808408-BG 
ESX350-200810202-UG 
ESX350-200811402-SG 
ESX350-200901402-SG 
ESX350-200903202-UG

RequiresN/A
Host Reboot RequiredNo
Virtual Machine Migration or Shutdown RequiredNo
PRs Fixed336284 252894 293881
Affected HardwareQLogic FC HBAs
Affected SoftwareN/A
RPMs IncludedVMware-esx-scripts
Related CVE numbersN/A

Solution

Summaries and Symptoms

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

  • Fixes an issue where two rescans are required to discover a new LUN connected to a Qlogic Fibre Channel HBA. This is due to a rescan timing issue between VMkernel and Qlogic Fibre Channel driver.
  • A new feature allows the esxcfg-firewall command to block host access to the ports of the service console. The new options IpruleAdd and IpruleDel support this feature. The updated manpage for this feature is available from bundle ESX350-200904409-BG.
  • Fixes an issue where inputting the incorrect command format to open multiple ports might cause esxcfg-firewall to fail. After this fix is applied, you must reset the esxcfg-firewall settings to default with the following command:
    esxcfg-firewall -resetDefaults
    If you input the incorrect command format to open multiple ports after the fix is applied, esxcfg-firewall might display an error message similar to the following:
    ERROR: PortSanityCheck: bad port specification, '40-1500'

Deployment Considerations

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

Based on VMware KB 1010127

Also Read

Language: