VASA vVol provider is offline with a transport error after a host reboot or upgrade

Products

• VMware vSphere ESXi

Issue/Introduction

VASA provider shows no PE device, from "esxcli storage vvol protocolendpoint list" output

VvolFileSystemImpl: In vvold returned container-info,:  cid ########-####-####-####-############ is not associated with any storage array.

 

VASA provider shows a transport error from "esxcli storage vvol vasaprovider list" output, but there are no signs of FC transport related issues and the VASA provider version.xml is reachable

PROVIDER_HOSTNAME:
   VP Name: PROVIDER_HOSTNAME
   URL: https://10.X.X.X:8084/version.xml
   Status: Offline: TransportError [Cannot connect to VP, status code=400, status message=Bad Request]
   VASA Version: 4
   Max Concurrent Operations: 4
   Arrays:
         Arrays:
            ArrayId: com.purestorage:########-####-####-####-############
            Is Active: true
            Priority: 210

   VirtualHost:
      VirtualHost:
         IP:
         Port: 0
         SNI:
   API Batch Size:
      APIBatchSize:
         BindVirtualVolume: 10
         Default: 1024
         GetTaskUpdateEx: 16
         QueryVirtualVolumeInfo: 1024
         SnapshotVirtualVolume: 10
         SpaceStatsVirtualVolume: 1024
         UnbindVirtualVolume: 16
         UpdateVirtualVolumeMetdataEx: 1024

 

The same transport error is also shown in vvold.log

2025-10-29T22:23:01.574Z Wa(164) VVold[2102297]: [Originator@6876 sub=Default OpId=Session] VasaSession::DoSetContext: Empty VP URL for VP (PROVIDER_HOSTNAME)!
2025-10-29T22:23:01.574Z In(166) VVold[2102297]: [Originator@6876 sub=Default OpId=Session] VasaSession::Initialize: Failed to establish connection https://10.X.X.X:8084/version.xml, PROVIDER_HOSTNAME
2025-10-29T22:23:01.574Z In(166) VVold[2102309]: [Originator@6876 sub=Default OpId=Session] TimedInit: Returning session state: TransportError vpid PROVIDER_HOSTNAME
2025-10-29T22:23:01.574Z Er(163) VVold[2102309]: [Originator@6876 sub=Default OpId=Session] Initialize: Unable to init session to VP PROVIDER_HOSTNAME state: 3

 

FC transport issues should be investigated following the KB below, however if none are found the transport error can indicate the VASA provider and vCenter services are not aligned

Troubleshooting fibre channel storage connectivity

Environment

7.0

8.0

Resolution

Stop the VMware vSphere Profile-Driven Storage Service (vmware-sps) on vCenter, restart the VASA provider services, & start the vmware-sps service to align VASA service states.  Refer to the following KB on restart vCenter services:

Stopping, Starting or Restarting VMware vCenter Server Appliance services