VSAN Health Check VIB Installation & vSphere ROBO/Essentials Plus

I was talking with a fellow VMware guy, Matt Lydy, at VMworld Barcelona and he brought something to my attention around the Virtual SAN 6.x Health Check Plug-in. Matt is a Technical Account Manager in Ohio. I had the pleasure of working the VMware booth with him at VMworld US. He mentioned that the Health Check plugin requires Dynamic Resource Scheduling (DRS). I was pretty sure this wasn’t correct, but upon further conversation, he specified that DRS is required for the automatic installation. At that point a lightbulb went off. It certainly does.

Health Check Plug-in
Virtual SAN licensing/use isn’t limited by any supported edition of VMware vSphere (vSphere Hypervisor free isn’t supported for obvious reasons). Pre vSphere 6.0 Update 1, the Health Check plug-in had to be manually installed in vCenter. With 6.0 Update 1, it is automatically included. If the Health Check VIB is already installed on a host, the service is automatically enabled. If the VIB isn’t installed, to enable this service, hosts must be put in maintenance mode/VMs evacuated, VIB installed, each host rebooted and taken out of maintenance mode in a sequential fashion. Again, this is an automatic process. When maintenance mode is initiated for a host, DRS migrates workloads off of the host.

What happens if DRS (with automated movement) isn’t enabled? An error is thrown, as hosts can’t be automatically evacuated. For customers that have licensing that includes DRS, simply enabling the service takes care of this requirement. But what about those that have all of the other features, but don’t have DRS? I’m specifically thinking about those with vSphere ROBO (Standard/Advanced) and Essentials Plus. The Health Check gui will handle the automated process of installing the VIB, but only if DRS is licensed. If it isn’t licensed, it won’t install the VIB.How to install the Health Check VIB
The Health Check VIB can be installed manually a couple different ways. Update Manager is one, but isn’t included in these editions. It can be installed by enabling SSH to a host, and manually installing the vib from either a URL or by a local/shared path. That’s easy, but manual, and requires enabling SSH, installing the vib from the command line, then disabling SSH.

I chose to put both of the Install and Remove actions into a single module, rather than having to execute this as a script. A couple differences (and bear with me, my PowerShell is rusty over the past 5 years) are:

I create a “vibs” folder on the vsanDatastore – Had trouble uploading directly to the root of the Virtual SAN datastore

I changed the PowerCLI command that performs the action of “esxcli software vib install” – This is because I’m using a .zip and not a .vib

Hi Jase,
any idea how to do this with vSAN 6.6?
I have a mismatch between the version on vCenter (newer) and the hosts (older).
The VMware site doesn’t appear to have the vib available under ‘VMware Virtual SAN Tools, Plug-ins and Appliances’ anymore.

vSphere 5.5 End of General Support

-248Days-12Hours-53Minutes00Seconds

Disclaimer

Any views or opinions expressed here are strictly my own. While I am a blogger who works for VMware, I am solely responsible for all content published here. This is a personal blog, not a VMware blog. Content published here is not read, reviewed, or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware or any of its divisions, subsidiaries, or business partners.

Any of my code, configuration references, or suggestions, should be researched and verified in a lab environment before attempting in a production environment.

Agreement to use any of my code or recommendations, removes me from any liability as such.