VSAN: cannot add storage policy, VSAN option missing under "rule based on vendor specific capabilities"

[jkoebrunner]

Hey,

I have a problem with the final version of VSAN.

I have upgraded all my hosts to 5.5 Update 1 and I have configured the VSAN cluster successfully.

Unfortunately, when I try to add a storage policy, there is no "VSAN" option selectable under "rule based on vendor specific capabilities". It only shows "None".

Does anybody have a solution for this problem?

I did not have this issue with the beta version of VSAN.

Johannes

Update: what I have found is that when I try to resync the storage providers, the following error message appears:

[jkoebrunner]

UPDATE 2:

I think it is somehow related to the profile-driven storage service.

Find attached the log with connection errors to the esx hosts...

Hosts are fully reachable via DNS...

Also this alarm is shown in vCenter:

[arvinnd]

You can try following workarounds

Workaround: You can use one of the following options to resolve this issue:

• Restart the VMware vSphere Profile-Driven Storage Service.
• Move the host outside the cluster and add it back.
• If none of the storage providers are listed, when you navigate to the Storage Providers drop-down menu, move all the hosts to a new Virtual SAN enabled cluster.

This seems to be known issue in esx 5.5 u1

vCenter Server 5.5 Update 1 Release Notes

Let me know if this works for you

Thanks

Arvind

[esarakaitiscbts]

I am experiencing the same issue as well.

[arvinnd]

Did you try any of the workarounds mentioned above?

[ErkanTugral]

Hello,

I've experienced same problem with vsan config.

I've tried to all 3 workaround mentioned on Release Notes but nothing changed.

After long searching on Google I found a solution in vSphere 5.5 documentation. Manually adding storage providers solved problem. You can make following  steps to add storage provider:

Browse to the vCenter Server in the vSphere Web Client navigator.

1. Click the Manage tab, and click Storage Providers.
2. Click the Register a new storage provider icon.
3. Type connection information for the storage provider, including the name, URL, and credentials.
4. For the Virtual SAN storage provider, enter a separate URL for each host that participates in the cluster.

http://host_ip:8080/version.xml, where host_ip is the actual IP of the host.

Erkan

[konstantink2011]

Hello, Erkan.

I have the same problem and tried all scenarios but all of them were unsuccessful.

The following error is occurred when I try to manually add storage provider when I use "https" in URL:

The "Register new storage provider" operation failed for the entity with the following error message.

Unable to verify the authenticity of the specified host.

and the following error with "http" in URL:

The "Register new storage provider" operation failed for the entity with the following error message.

A problem was encountered while registering the provider.

Can you advise me what may be wrong?

Thanks,

Konstantin

[esarakaitiscbts]

It was a known issue, have you updated everything?

[konstantink2011]

Yes, everything is updated.

[ErkanTugral]

Hello Konstantin,

Which user name and password you use for related host while adding storage provider ? You have to use host's root account with password. You can find detailed link about same problem with same solution that I mentioned above.

http://tsmith.co/2014/vsan-storage-profile-missing/

Erkan

[cyphil]

Experienced the same situation.

Tried manually add storage providers as Erkan suggested. However got error.

Tried visit the URL http://[host-ip]:8080/version.xml in brower, returned 404-err in IE, or "no data received" in Firefox.

Not sure if any one can help.

Thanks,

Philip

[vThinkBeyondVM]

Hi Friend,

Please refer this post :How to add vendor-specific capabilities for more insight.

[cyphil]

Thanks  vickyvision2020 for you reply. Need fresh vCenter 5.5U1 installation to resolve!? Everything has to re-installed then?

[konstantink2011]

Only fresh installation of vCenter Server 5.5 u1 helps me. All other solutions doesn't work. 

[vThinkBeyondVM]

Yes , you will have to go for fresh installation. Please make sure while going for 5.5U1, you apply latest patch on that to avoid security heartbleed issue. This issue is resolved in latest patch on the top of VC 5.5u1

[ErkanTugral]

Hi Philip,

When you browse to mentioned URL you could see page like following screenshot. If you get 404 error or no data , clean installation of VC 5.5u1 simplest and quick solution to problem unfortunately. Because Vmware does not provide any solution on actual configuration.

Erkan

[cyphil]

Thanks Erkan, http://[ip]:8080/version.xml got 404 err httpS://[ip]:8080/version.xml can!

[cyphil]

Thanks all. Right, fresh installation of vCenter resolves the problem. But I wonder what could be the impact to end customer when vCenter is to be re-installed in production environment @_@ Hope that VMware would have an immediate fix for this.

[steveyoung]

I saw all the same symptoms and tried one of the workarounds. Didn't try manually adding storage providers. Ultimately, rebooting the vCenter server corrected the issue.

[dukcrzyeight]

Has anyone used the default certs on the ESXi hosts to enable vSAN? Also, is anyone using a Domain Controller when enabling vSAN? Not sure if my issue stems from there....