Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware ESX Server 3.5, Patch ESX350-200803207-UG: Update to VMware-esx-drivers-scsi-qla2300-v707_vmw (1003702)

Details

Release Date: 10 APR 2008
Document Last Updated: 10 APR 2008

 

Download Size:
1 MB
Download Filename:
ESX350-200803207-UG.zip
md5sum:
9d29b39fc1a0dd34967d114bee0bb55e
Product Versions ESX Server 3.5
Patch Classification Update
Supersedes None
Requires ESX350-200803211-UG
Virtual Machine Migration or Reboot Required Yes
ESX Server Host Reboot Required Yes
PRs Fixed

233638

Affected Hardware All devices using the VMware-esx-drivers-scsi-qla2300-v707_vmw
Affected Software
RPMs Included VMware-esx-drivers-scsi-qla2300-v707_vmw
Related CVE numbers N/A


Summary

Updates the qla2300 driver to VMware-esx-drivers-scsi-qla2300-v707_vmw-7.8.32.

Solution

Symptoms

There are no symptoms available for the updates provided by this patch.

Deployment Considerations

None.

Patch Download and Installation

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

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 the the esxupdate tool from the command line of the host. For more information on using esxupdate to manage patches on ESX Server 3.5 hosts, see the ESX Server 3 Patch Management Guide.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: