VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Analysis of VASA Provider operations
This is the sequence of steps that takes places during VASA Provider registration. It
may be useful for future troubleshooting activities.
When the host is added to a Virtual SAN enabled cluster in vCenter Server, vCenter
Server will trigger auto registration of Virtual SAN Providers running on the host
with SMS, the Storage Management Service running on vCenter Server.
If this operation is successful, the new provider shows up in Storage Providers view
in the vSphere web client.
Regardless of whether the hosts are added to vCenter using DNS name or IP address,
vCenter always constructs an IP address based URL for Virtual SAN Provider.
The Resync Virtual SAN Providers workflow in SMS is invoked either when services
in vCenter server are restarted or users click on the resync button on Storage
Providers view in the vSphere web client.
This invokes the following steps to take place:
1. SMS finds which hosts are part of Virtual SAN enabled clusters. This
SMS query returns hostnames. If the hosts were added using a DNS
name, SMS query will return DNS names of these hosts. These DNS
names are then used by SMS to construct Virtual SAN provider URLs.
2. SMS queries already registered Virtual SAN provider. This SMS query
returns IP address based URLs for Virtual SAN providers as vCenter
Server auto registration always uses IP address based URLs.
3. To detect which providers need to be added or removed, SMS
compares URLs obtained in step (a) and (b). This then decides which
newly discovered providers, if any, needs to be registered.
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 181