I have a small 3 host cluster with vSAN enabled. Everything works as expected (so far) except Storage profile. This is a lab environment. ESXi and vCenter are clean installs from the latest versions (5.5.0 2d).
I've tried to resync in the Storage Provides tab of vCenter and I get this result:
And I see this happening in the thick client:
I have tried to regenerate the SSL certs as detailed here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=207807...
I have tried the fixes mentioned here: http://tsmith.co/2014/vsan-storage-profile-missing/
I have tried removing hosts from the cluster, bringing them back, resyncing, restarting the Storage Driven Profile service and VirtualCenter Server service. I get the same results as above.
I am able to access the xml file when connecting to: https://192.168.20.101:8080/version.xml and it looks like this:
[code]<vasa-provider><supported-versions><!-- <version id="1" serviceLocation="/ivp/services/vasaService" />
--><version id="2" serviceLocation="/vasa/services/vasaService"/></supported-versions></vasa-provider>[/code]
I cannot access the version.xml file if I try only with http://, I have to use secure.
When I try to add a storage provider manually I get this:
I click yes and get this:
Not sure where to go from here or what else to try. Can anyone else think of something?
Additionally, I have the "Host vendor provider registration has failed" error on all three hosts. I have restarted the vsanvpd service on all of the hosts as per this (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=210501...)
>> (5.5.0 2d).
can you provide more detail on the build/buildno. is this 5.5 Update 1|2 ?
there were some issues on this regard which were addressed in 5.5 update 2
you may also want to check the vCenter sps.log to see what the actual reason for the failure...
This is vc55ep6 and vsphere esxi bits would be 55update2
Have filed an SR ? i would request to file an SR with complete vc-support bundles to get to the root of this issue.
I am running 5.5U2 and see this same issue. I have an open support case, they said its because the VASA Provider service on the esx hosts keeps crashing.
Your hosts should answer on port 8080. When I observe this problem, my hosts are not listening on port 8080 anymore. So I restart the service, and everything is back to normal.
Do a /etc/init.d/vsanvpd status to see if its dead or alive on your hosts.
My name is xxx and I was taking a look at the email you had sent in regarding your support ticket. Looks like you found the main issue. Port 8080 between vCenter and the ESXi host is important to VASA. Instead of having to reboot the ESXi host, can your run the following command via command line?
This is the VASA Provider Daemon.