ESXi lost connection to vVol datastore

Products

• VMware vSphere ESXi

Issue/Introduction

• ESXi hosts experienced a datastore outage due to a Pure Storage vVol container going offline.
• The vvold.log recorded continuous retry failures during the outage window, proving the host could not reach the array's VASA Provider (VP):

Er(163) VVold[2098680]: [Originator@6876 sub=Default IpcCtx=2098677-40 OpId=HB-host-2032@#######-#######-########-#-####] VasaOp::DoRetry [#6104321]: No available best VP for array (com.purestorage:#######-####-####-####-#######65fe), retrying all VPs with force connect!

• The vobd.log indicates that the vVol container has gone offline.

In(14) vobd[2097572]:  [VvolCorrelator] 21663451047881us: [vob.vvol.container.offline] VVol container (vvol:###########-############) has gone offline: isPEAccessible (False), isVPAccessible (False).

Environment

VMware ESXi Version: 8.0.x

 

Cause

Connectivity disruption between the ESXi host and the Pure Storage VASA Provider (VP).

 

Resolution

Engage storage array vendor to investigate the management network path between the ESXi hosts and the Pure Storage VASA provider to resolve the connectivity disruption.

Additional Information

The VASA provider was down due to a connectivity issue between the ESXi hosts and the storage array. As a result of this disruption, the protocol endpoint became inaccessible, which led to an outage during the affected period.

The connectivity between the ESXi hosts and the storage array needs to be thoroughly reviewed to help prevent recurrence of this issue.