So i need to run a restart of all the hosts in the cluster (wow) i never saw that one comming...!
I will put a change in to give it a go.
So there were no other steps or steps ive missed etc..
Yes i am indeed familiar with the article you link its somewhat light.... 🙂 any idea when the procedd documentaon may be finished so i can integrate our VSC deployments with our CA certificate servers..
Are you sure you signed in to the Support site? It's a rather lengthy KB. But if you are not signed in you only see the first two sentences.
I haven't done a lot with CA-signed certs myself. In my case, I needed to regenerate the self-signed certs as they had expired. Once I did that, I could not get the VASA Provider to register with ESXi. I was running 6.5.0 which seemed to have some bugs with these processes. In my case it was fixed by restarting ESXi. But that may be a blunt approach; I might also have tried just restarting vvold and hostd.
I still suggest contacting Support. They have a broader range of experience on this than I do.
No, the VP just registered with VC after that. I thought your registration problem was with VP, not VSC.
I am sorry you are having these problems. In my experience with 6.5.0 I have had a number of problems with VMware software, especially related to VP/VVols. Registration must be another one of these problem areas as I have seen articles from Cormac Hogan (which helped our largest VVol-using customer) as well as a VMware KB on troubleshooting VP registration. Flash is the one that is my biggest problem. 🙂
If you let me know your case number I will keep an eye on it.
So while the VSC is registered in vCenter and we can reach the portal to register \ de-register the VSC is giving the exact same issue as linked above if you check server side. So my original post could just be a symptom.
vCenter does not show the entries for NetApp under storage providers.