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-200803216-UG: Update to VMware-esx-drivers-net-tg3 (1003991)

Details

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

 

Download Size:
96.79 KB
Download Filename:
ESX350-200803216-UG.zip
md5sum:
f5789dfd07e64c783611c60d0ad53d67
Product Versions ESX Server 3.5
Patch Classification Update
Supersedes None
Requires None
Virtual Machine Migration or Reboot Required Yes
ESX Server Host Reboot Required Yes
PRs Fixed

239035

Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-drivers-net-tg3
Related CVE numbers N/A


Summary

Updates the VMware-esx-drivers-net-tg3 driver to use the latest RPM naming convention.

Solution

Symptoms

The convention for naming driver RPMs has changed to the format VMware-esx-drivers-<driver-name>-350.<version>-<build #>.<arch>.rpm. For example, VMware-esx-drivers-net-tg3-350.3.43b.1vmw-00000.i386.rpm.

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: