Any Virtual SAN Pre-flight Check mojo?

[justinbennett]

Upgraded Virtual SAN from 6.0 to 6.1 on our ESXi hosts. I've updated the vCenter server today - but we're running Virtual SAN and vSphere standard edition without DRS. I get the following error post upgrade in the Manage -> Virtual SAN -> Health page:

Anyone have any mojo to resolve this? I applied a trial license in the past to get around this, but it's long expired.

PS: Here's the Monitor -> Virtual SAN -> Health Check too, when trying to click Enable:

[CHogan]

Check out the health check guide for 6.1 - http://www.vmware.com/files/pdf/products/vsan/VMware-Virtual-SAN-Health-Check-Guide-6.1.pdf

If you do not have DRS, you cannot do the automated, rolling install.

Instead, you will have to manually install the VIBs using esxcli or VUM.

HTH

Cormac

[justinbennett]

"...

2.3 VIB Installation Methods

As mentioned a number of times already, please note that with the release of ESXi

6.0U1, the health check VIB is bundled with ESXi. Therefore there is no need to push

out the VIB from vCenter server, which is still a necessary step with ESXi 6.0.

..." pg 21

I have already rolled out the updates to ESXi via the VIBs. The health check plug in was installed, but this check in the vCenter GUI won't detect it's already there. This is similar to what I went through in vs 6.0.0, except I had installed the health check plugin separately.

[CHogan]

Is the version of VC also upgraded?

[justinbennett]

Yes.

[CHogan]

IIRC, all you need to do was hit the "Retry" button and the VIBs should get discovered.

There should be no need to go through the install process - can you verify that is what you tried, and what caused the pre-flight checks to pop up.

[justinbennett]

Sorry for not clarifying sooner, but that was what I tried shown in the first screenshot. I tried multiple times.

Thank you,

Justin

[CHogan]

It should be as simple as that Justin. I would open a case with GSS, and see if they can figure out why that is not working via the logs.

[justinbennett]

I have an existing case, SR 16866232601. I'll add this to it and report back any information gathered.

-Justin

[justinbennett]

I have an existing case for our Virtual SAN issues open since last Wednesday for our initial crash - and now 2 sub sequential crashes - SR 16866232601.

I haven't heard back from anyone for a week even though I keep adding notes and calling on duty managers for escalation. I performed this upgrade in the dark to try and stem off any more issues and I'm just looking for some help.

As a customer, this whole experience has felt awful. Might as well be sitting here with Wilson:

... not that this is your fault, I'm just venting.

[CHogan]

Someone should have reached out to you by now (hopefully)

[zdickinson]

Good morning Cormac, I would say that his vSAN support experience is not unique.  I have often found response times and availability of vSAN trained engineers to be spotty.  I'm told "the person" who knows vSAN is not available.  There are posts in this forum that echo this.  Thank you, Zach.

[CHogan]

Thanks Zach - we hear you. There are already plans underway to improve on this, which were kicked off late last year. Watch this space.

[zdickinson]

Great to hear, I definitely believe in the product and can't wait to see where it goes.  The price/performance as allowed us to stretch the IT dollar further than ever and take on some additional projects. 

Also, I will say that the problems I have run into have either been caused by a third party or me.  Thank you, Zach.

[justinbennett]

Yes, someone has been helping. Thank you! Logs have been captured and I'll let you know what escalation brings of this issue.