nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Component react.community-search had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.

Issue with VSC Appliance v 7.1 with vMware 6.5

OldGreyBeard

Hi All

Looking for a little advice before i log a case as we are flat out of ideas.

We have multiple environments with 8020s running On-Tap 9.1 each has a vCenter and each has an instance of the VSC Appliance (7.1) installed.

However 2 of these have the same problem which i cannot bottom out.

They both see the storage arrays (as they should.)

They both see all volumes (as they should.)

However when the box is checked "Enable VASA Provider" is sellected it waits for a while and then spits out an error that there is an issue with a certificate.

vCenter registration of the VASA provider failed. An invalid HTTPS certificate was detected and rejected by the VASA provider 185 Seconds ago.

Please regenerate your vCenter Storage monitoriong Service Certificate and then re-try registration.

Ive looked all through vCenter and cannot find an expired certificate or a cert for Sto (these certs are issued from our CA Cert Server)

So far I have..

De-registered and re-registered the VSC

De-registered and re-registered the VSC and confirmed Folders are removed from the vCenter

Manually de registered the VSC and re-registered with vcenter reboot

Deregistered the VSC Regenerated the VSC appliance certs and re-registered with vCenter

All to no avail, i have no idea where it is looking for these certs..

Any Ideas ...?

Find more posts tagged with

VMware

Comments

konnerth

When I last regenerated (self-signed) virtual appliance certificates, I had to restart ESXi and vCenter services to reconnect everything.

You are probably familiar with this KB for CA-signed certs.

https://kb.netapp.com/app/answers/answer_view/a_id/1075654

Otherwise you might contact Support for assistance.

---Karl

OldGreyBeard

Hi there Karl

Many thanks for the reply.

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..

cheers

Paul

konnerth

Hi Paul,

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.

---Karl

OldGreyBeard

Hi there

Have restarted the VVOLD and HOSTD services without sucess.

Following the restart did you then need to de-register and re-register the VSC ..??

I have a support case open.

The VSC is a tiresome buggy POS.....

Paul

pandar1

@OldGreyBeard Just following up to see if you got a solution for your issue.