vVol Datastore is Inaccessible

Products

• VMware vSphere ESXi

Issue/Introduction

Protocol end points is missing in vCenter UI.





vvold.log

2025-06-09T08:01:09.435Z Wa(164) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] VasaSession::GetEndPoint: failed to get endpoint, err=Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections., using default.Changing session state:TransportError
2025-06-09T08:01:09.435Z In(166) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] VasaSession::Initialize url is empty
2025-06-09T08:01:09.435Z Wa(164) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] VasaSession::DoSetContext: Empty VP URL for VP (NetApp-VP)!
2025-06-09T08:01:09.435Z In(166) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] VasaSession::Initialize: Failed to establish connection https://#.#.#.#:9083/version.xml, NetApp-VP

2025-06-09T08:12:40.821Z Wa(164) VVold[2126734]: [Originator@6876 sub=Default OpId=Session] VasaSession::GetEndPoint: failed to get endpoint, err=Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections., using default.Changing session state:TransportError
2025-06-09T08:12:45.823Z In(166) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] GetEndPoint: with url https://#.#.#.#:9083/version.xml
2025-06-09T08:12:45.830Z Wa(164) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] VasaSession::GetEndPoint: failed to get endpoint, err=Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections., using default.Changing session state:TransportError
2025-06-09T08:12:50.833Z In(166) VVold[2126707]: [Originator@6876 sub=Default OpId=Session] GetEndPoint: with url https://#.#.#.#:9083/version.xml

Environment

VMware vSphere ESXi 8.X

Cause

 VASA Provider showing OFFLINE.

Resolution

Please contact your storage vendor for further assistance.

Additional Information

Troubleshooting check points:

• ProtocolEndpoint and VASA is needed for vVol storage connectivity
• Protocol Endpoint should be available
• Storage VASA Provider shows OFFLINE
• Certificate is healthy
• vVol necessary services has already been restarted