I think you actually tried to mention this blog series http://www.derekseaman.com/2013/10/vsphere-5-5-install-pt-1-introduction.html (if I am not wrong). But according to this thread Trouble getting VSAN 6 Storage Providers up and running , (if I acually understand their posts) it did not solved the problem (honestly, I did not tried derek's solution).One more information from me, my AD Domain controller and vcenter server are both on windows server 2012 R2. And according to this KB article VMware KB: ESXi 5.5 host in a VSAN cluster reports a warning alarm: Host vendor provider registration , there is still no resolution.
I found a solution for the "Host vendor provider registration" issue which is described in VMware KB: ESXi 5.5 host in a VSAN cluster reports a warning alarm: Host vendor provider registration. To work around this issue:
1. Disonnect the host from cluster.
2. Remove it from inventory.
3. Add the host directly to Datacenter.
Then I found that the alarm disappeared. I have 4 hosts in a cluster. All had same alarm and now all of them are gone
Someone dropped the ball, that should have been the first troubleshooting process. :(
Sorry, the alarm appears again after creating another culster and joining the hosts to the cluster
Are those clean fresh installed visors in the new clusters? Also, have you tried regenerating the storage SMS certificates?
There are two paths of least resistance that i can see.
First eliminate your existing vcenter server from the equation and see if the problem persists on a vanilla one. If problem persists, reset the vcenter server to vanilla, and do a clean ESXi install foreach host. Then see if the problem persists.
The second one would be jumping to vSphere 6, since I personally have yet to experience any "Storage Provider registration" problems.
I have tried all the way in last month to resolve this issue and at last my problem solved today.
I have tried with 4 ESXi host and windows 2012 R2 for vCenter VM OS.
First I tried with vsphere 5.5 u2 (RSXi hypervisor) and vcenter server 5.5 (windows); when the problem continues I upgraded to vsphere 6.0 and vcenter 6.0. But the problem still continues. Then I upgraded VSAN on-disk format from v1 (VSAN 5.5) to v2 (VSAN 6.0). Then it is solved.
Follow the link to change VSAN on-disk format - VMware KB: Upgrading the VMware Virtual SAN (VSAN) on-disk format version from 1 to 2.
N.B: Some people says that the problem is for vcenter OS version -Windows 2012 R2. They suggest that to use windows 2012 server instead of windows 2012 R2 server . But my findings is that , windows 2012 R2 is not a problem if you upgrader your ESXi, vcenter and VSAN to 6.0 version.