09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

Known issue with VASA Providers in version 5.5<br />

There was an issue with VASA storage providers disconnecting from vCenter Server,<br />

resulting in no Virtual SAN capabilities being visible when you try to create a VM<br />

Storage Policy. Even a resynchronization operation fails to reconnect the storage<br />

providers to vCenter. This seems to be predominantly related to vCenter servers<br />

which were upgraded to vCenter 5.5U1 and not newly installed vCenter servers.<br />

The symptoms are described in the vCenter 5.5 U1b release notes as follows:<br />

Under certain conditions, Virtual SAN storage providers might not be created<br />

automatically after you enable Virtual SAN on a cluster<br />

When you enable Virtual SAN on a cluster, Virtual SAN might fail to automatically<br />

configure and register storage providers for the hosts in the cluster, even after you<br />

perform a resynchronization operation.<br />

vCenter 5.5 U1b, released in June 2014, resolves the issue.<br />

If the Virtual SAN storage providers become disconnected, with the latest releases of<br />

Virtual SAN one simply needs to do a resynchronization operation. To<br />

resynchronize, click the synchronize icon in the Storage Providers tab, found under<br />

vCenter Servers > vCenter > Manage, as shown below.<br />

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 / 1 8 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!