vSphere web client and esxcli command may hang when there are too many disks attached to Broadcom controllers

Products

• VMware vSphere ESXi

Issue/Introduction

This article provides resolution and workaround, regarding the issue related to vSphere web client and esxcli command hang issue caused by the long time to get devices' location info.

Symptoms:

When there are too many disks inserted on the server beside Broadcom controllers, the esxcli command and vSphere web client maybe hang and timeout without no response.

Environment

VMware vSphere ESXi 7.0.x

Cause

The vSphere web client and esxcli command can get the devices' location info through lsuv2-lsiv2-drivers-plugin. And the operation need several seconds to complete and return.

When there are too many disks, it will take long time and it will lead the vSphere web client and esxcli command hang and timeout. (The length of non-response time is proportional to the number of devices.)

Resolution

This issue is fixed in 7.0U3 release.
Upgrade ESXi to 7.0 U3 to fix this issue.

Workaround:

The workaround should only be implemented if you are unable to upgrade to ESXi 7.0U3 at this time.

Remove the lsuv2-lsiv2-drivers-plugin through command to workaround this issue:

• localcli software vib remove -n lsuv2-lsiv2-drivers-plugin (reboot is required)