Unable to create a new vVOL datastore and existing vVOL datastores are reported as inaccessible in vSphere UI.
search cancel

Unable to create a new vVOL datastore and existing vVOL datastores are reported as inaccessible in vSphere UI.

book

Article ID: 413188

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • vVOL datastore reported as inaccessible in vSphere UI.
  • Administrator is unable to create a new vVOL datastore.
  • VASA provider is online in vCenter. 
  • Datastore seen as inaccessible in vCenter

 Also the datastore summary page reports the following warning :

vSphere HA failed to create a vVol configuration for this datastore and therefore will not be able to protect virtual machines on the datastore until the problem is resolved. Error: (vim.fault.InaccessibleDatastore) 

 

 

Environment

VMware vSphere ESXi 8.X

Cause

vVOL datastore becomes inaccessible as the ESXi host does not have network connectivity to the VASA provider.

  • Ping the VASA from the VC.

<user>@<VCSA>[ / ]# ping  <VASA provider IP>
PING  <VASA provider IP> ( <VASA provider IP>) 56(84) bytes of data.
64 bytes from <VASA provider IP>: icmp_seq=1 ttl=59 time=0.898 ms
64 bytes from <VASA provider IP>: icmp_seq=2 ttl=59 time=2.18 ms
64 bytes from <VASA provider IP>: icmp_seq=3 ttl=59 time=0.735 ms

...
--- <VASA provider IP> ping statistics ---
39 packets transmitted, 39 received, 0% packet loss, time 38846ms
rtt min/avg/max/mdev = 0.654/0.784/2.181/0.231 ms

 

  • From an ESXi host verify the status of the VASA provider.

In the output below the VASA status is reported to be offline due to TransportError [Connection timed out]

localcli storage vvol vasaprovider list

<VASA Provider Name>:
   VP Name: <VASA Provider Name>
   URL: https://###.##.##.###/virtualization/version.xml
   Status: Offline: TransportError [Connection timed out]
   VASA Version: 4
   Max Concurrent Operations: 4
   Arrays:
         Arrays:
            ArrayId: NetApp.clustered.##############################################
            Is Active: true
            Priority: 240

   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

 

  • Ping the VASA provider from the ESXi host.

ping <VASA provider IP>
PING <VASA provider IP> (<VASA provider IP>): 56 data bytes

--- <VASA provider IP> ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

 

In the ESXi: /var/log/vvold.log the host reports it is unable to reach the VASA provider.

####-##-##T##:##:##.###Z Wa(164) VVold[2100367]: [Originator@6876 sub=IO.Connection OpId=Session] Failed to connect; <io_obj p:0x000000fdec6a2b30, h:13, <TCP '###.##.###.## : 50480'>, <TCP <VASA provider IP> : 443'>>, e: 110(Connection timed out), duration: 75011msec
####-##-##T##:##:##.###Z In(166) VVold[2100367]: [Originator@6876 sub=IO.Connection OpId=Session] Failed to shutdown socket; <io_obj p:0x000000fdec6a2b30, h:13, <TCP '###.##.###.## : 50480'>, <TCP '<VASA provider IP> : 443'>>, e: 104(shutdown: Connection reset by peer [system:104])
####-##-##T##:##:##.###Z Wa(164) VVold[2100367]: [Originator@6876 sub=HttpConnectionPool-000000 OpId=Session] Failed to get pooled connection; <cs p:000000fdec698050, TCP:<VASA provider IP>:443>, (null), duration: 75012msec, N7Vmacore15SystemExceptionE(Connection timed out)
####-##-##T##:##:##.###Z Wa(164) VVold[2100343]: --> [context]zKq7AVICAgAAAP////8LdnZvbGQAAPPJR2xpYnZtYWNvcmUuc28AAEhrLQCMsi0Az7MtALW6LQD/wC0AHtssAOD/LABLUFIBUngAbGlicHRocmVhZC5zby4wAAI/Ug9saWJjLnNvLjYA[/context]
####-##-##T##:##:##.###Z In(166) VVold[2100367]: [Originator@6876 sub=IO.Http OpId=Session] Set user agent error; state: 1, (null), N7Vmacore15SystemExceptionE(Connection timed out)
####-##-##T##:##:##.###Z In(166) VVold[2100343]: --> [context]zKq7AVICAgAAAP////8LdnZvbGQAAPPJR2xpYnZtYWNvcmUuc28AAEhrLQCMsi0Az7MtALW6LQD/wC0AHtssAOD/LABLUFIBUngAbGlicHRocmVhZC5zby4wAAI/Ug9saWJjLnNvLjYA[/context]
####-##-##T##:##:##.###Z Wa(164) VVold[2100354]: [Originator@6876 sub=Default OpId=Session] VasaSession::GetEndPoint: failed to get endpoint, err=Connection timed out, using default.Changing session state:TransportError
####-##-##T##:##:##.###Z In(166) VVold[2100354]: [Originator@6876 sub=Default OpId=Session] VasaSession::Initialize url is empty
####-##-##T##:##:##.###Z Wa(164) VVold[2100354]: [Originator@6876 sub=Default OpId=Session] VasaSession::DoSetContext: Empty VP URL for VP (<VASA Provider Name>)!
####-##-##T##:##:##.###Z Er(163) VVold[2100354]: [Originator@6876 sub=Default OpId=Session] VP node is not set, ignoring stats
####-##-##T##:##:##.###Z In(166) VVold[2100354]: [Originator@6876 sub=Default OpId=Session] VasaSession::Initialize: Failed to establish connection https://<VASA provider IP>/virtualization/version.xml, <VASA Provider Name>
####-##-##T##:##:##.###Z In(166) VVold[2100354]: [Originator@6876 sub=Default OpId=Session] ScheduleEventPollLocked: <VASA Provider Name> Unable to cancel timer, bailing out.
####-##-##T##:##:##.###Z In(166) VVold[2100403]: [Originator@6876 sub=Default OpId=Session] GetEndPoint: with url https://<VASA provider IP>/virtualization/version.xml
####-##-##T##:##:##.###Z Er(163) VVold[2100367]: [Originator@6876 sub=IO.Http OpId=Session] User agent failed to send request; (null), N7Vmacore15SystemExceptionE(Connection timed out)

Resolution

Please review the network routing to ensure the ESXi host can communicate to the VASA provider.

Powered by Wolken Software