Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESX/ESXi Express Patch or debug driver rollback instructions (1031240)

Last Updated: 6/23/2016Categories: TroubleshootingTotal Views: 36190Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This article provides the concepts, procedure, and commands generally useful for rollback situations. For illustration, VMware released Express Patch for ESX/ESXi 4.1 is used. For more information about the patch, see VMware ESX 4.1 Patch Release ESX410-201011001 (1029400) or VMware ESXi 4.1 Patch Release ESXi 410-201011001 (1029401).

If you are running a debug driver (bnx2x), you must roll back to the ESX/ESXi 4.1 GA version of the driver before applying the Express Patch. This driver is manually installed because it is not part of the GA package. If you did not manually install this driver, you can ignore this article.

ESX

Run this command to check which version of the driver you are currently using:

# rpm -qa | grep -i bnx2x

If the output contains the word debug, you must remove this driver and install the ESX/ESXi 4.1 GA driver. For more information, see Rollback procedure for ESX in the Resolution section.

The output might be similar to:

vmware-esx-drivers-net-bnx2x-400.1.54.1.v41.1- debug7vmw.0.0.00000.x86_64.rpm

ESXi

Run this command to check which version of the driver you are currently using:

# esxupdate query --v | grep -i bnx2x

If the output contains the word debug, see the Rollback procedure for ESXi section in the Resolution section.

The output might be similar to:

vmware-esx-drivers-net-bnx2x_400.1.54.1.v41.1- debug7vmw.0.0.00000

Note: If you are running ESX 4.1 GA (build# 260247), you can install the Express Patch without performing any other actions. The KB article VMware ESX/ESXi 4.1 host with Broadcom bnx2x (in-box driver version 1.54.1.v41.1-1vmw) experiences a loss of network connectivity and a purple diagnostic screen (1029368) provides a workaround to disable IPv6 Checksum. If you implement this workaround, you do not have to re-enable IPv6 Checksum before installing the Express Patch. There boot step during the patch installation automatically resets IPv6 Checksum back to its default enabled state.

Resolution

Rollback procedure for ESX

To remove the debug driver, run the command:

# rpm -e name_of_the_driver_rpm

For example:

# rpm -e vmware-esx-drivers-net-bnx2x-400.1.54.1.v41.1-debug7vmw.0.0.00000.x86_64.rpm

To install the ESX 4.1 GA version:

Run the command:

# rpm -Uvh --force --nodeps vmware-esx-drivers-net-bnx2x-400.1.54.1.v41.1-1vmw.0.0.260247.x86_64.rpm

Reboot for the changes to take effect. Run the commands:

# esxcfg-boot -b
# reboot

Rollback procedure for ESXi

ESXi permits only one level of rollback. If you reboot your host successfully after applying the debug driver and did not perform any additional ESXi software updates, you can rollback to the previous state. If you completed additional ESXI software updates since applying the debug driver, then you must re-install ESXi.

To rollback to the previous state:

Reboot the ESXi 4.1 host.

Press Shift+r when the screen displays Loading VMware Hypervisor.

Press Y to continue.

Press Enter. The host rolls back to the previous state.

Note: Press ESC to view the log.PressESC again to return to this screen.

To confirm that the bnx2x driver of ESX/ESXi 4.1 GA is installed and that the debug driver vib is uninstalled, run the command:

~ # esxupdate query --v | grep -i bnx2x
deb_vmware-esx-drivers-net-bnx2x_400.1.54.1.v41.1-1vmw.0.0.260247 installed <YYYY-MM-DD>T<time>+00:00
deb_vmware-esx-drivers-net-bnx2_400.2.0.7d-2vmw.0.0.260247 installed <YYYY-MM-DD>T<time>+00:00
deb_vmware-esx-drivers-scsi-bnx2i_400.1.8.11t5.rc2.8.1-3vmw.0.0.260247 installed <YYYY-MM-DD>T<time>+00:00
cross_vmware-esx-drivers-net-bnx2x_400.1.54.1.v41.1-debug7vmw.0.0.00000 uninstalled <YYYY-MM-DD>T<time>.404870+00:00
~ # </time></time></time></time>

Note: In ESXi 5.5 and later, use this command to display vibs installed:

esxcli software vib list | grep -i bnx2x

This command displays bnx2x drivers installed.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Related Information

ESX/ESXi Express Patch またはデバッグ ドライバのロールバック手順

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant