Knowledge Base

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

ESX host stops when shutting down with the Emulex BladeEngine 10Gb Ethernet Controller be2net driver loaded (1033052)

Symptoms

  • When performing a clean shutdown of an ESX host, the host stops at the step Please stand by while rebooting the system.
  • The issue occurs when a system is installed with Emulex Blade Engine 2 or Emulex Blade Engine 3 Dual-Port 10GbE Converged Network Controllers
  • Connection remains lost until the host is rebooted
  • Under heavy load, one or more of the vmnic adapters loses connectivity
  • Lines similar to the following are observed in the vmkernel/messages log:
vmkernel: 244:16:12:51.786 cpu8:4314)WARNING: LinNet: netdev_watchdog: NETDEV WATCHDOG: vmnic2: transmit timed out 
vmkernel: 244:16:12:51.786 cpu8:4314)BUG: warning at vmkdrivers/src26/vmklinux26/vmware/linux_net.c:3251/netdev_watchdog() (inside vmklinux)
  • This issue occurs when one of these drivers are installed:
    • Emulex Driver be2net Version 2.102.440.0
    • Emulex Driver be2net Version 2.102.486.0  
    • Emulex Driver be2net Version 2.102.518.0 

Resolution

Resolution

Emulex has provided an updated driver that resolves this issue, VMware ESX/ESXi 4.x Driver CD for Emulex BladeEngine 10Gb Ethernet Controller,  Version  2.102.554.0.

The new driver can be downloaded here.

Workaround

To workaround this issue without the latest driver version, manually unload the driver prior to shutdown or reboot.

To unload the driver, run the command:

# vmkload_mod -u be2net

Notes:

Tags

esx-stops-shutting-down-emulex-be2net-driver

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

  • 1 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)
  • 1 Ratings
Actions
KB: