vVol datastores are inaccessible due to Transport Errors.

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

vVol datastores are inaccessible.

In the vvold logs we see errors related to ESXi and VASA provider / SAN connectivity.

2025-06-02T15:20:15.022Z In(166) VVold[2099065]: [Originator@6876 sub=Default] VasaSession::InitSoap: https://10.##.###.8:8084/vasa session state (TransportError) - recreating soap
2025-06-02T15:20:31.704Z Er(163) VVold[2099065]: [Originator@6876 sub=Default] VasaSession::DoSetContext: setContext for VP <controller_name>-ct0 (url: https://10.##.###.8:8084/vasa) failed [connectionState: TransportError]: TRANSPORT_FAULT (Timeout / connect failed in tcp_connect())
2025-06-02T15:20:46.712Z In(166) VVold[3623930]: [Originator@6876 sub=Default OpId=Session] VasaSession::InitSoap: https://10.##.###.8:8084/vasa session state (TransportError) - recreating soap
2025-06-02T15:21:03.385Z Er(163) VVold[3623930]: [Originator@6876 sub=Default OpId=Session] VasaSession::DoSetContext: setContext for VP <controller_name>-ct0 (url: https://10.##.###.8:8084/vasa) failed [connectionState: TransportError]: TRANSPORT_FAULT (Timeout / connect failed in tcp_connect())

Environment

VMware vSphere (All Versions)

Cause

The communication between ESXi and the SAN/VASA Provider was blocked by the firewall.

Resolution

The firewall rule should be modified to allow communication from the ESXi host IP addresses to the VASA Provider / SAN controller IP addresses over port 8084.