This guide helps to do a check of VSAN requirements before and after deployment. VMware engineers used this document internally first in order to validate the VSAN requirements before hitting the “enable VSAN” checkbox. It allows some head scratching on “why am I getting this error?”.
If you go through and successfully validate all the points in the pre-deployment TAB, then you're ready to go. The document allows helping for VSAN deployments and verification points.
There are two tabs:
- Pre-Install – contains VSAN network, storage and cluster verification list
- Post-Install – the same with addition of RVC (ruby vsphere console) and VSAN Observer
Screenshot from the guide showing the network part (including the PowerCLI command line – right bottom). You can click to enlarge.
Quote from vSphere blog:
This guide began as an internal collection of the most common Virtual SAN deployment troubleshooting scenarios. After receiving a number of requests from our customers, we have decided to publish this guide publicly as well.
The Virtual SAN 5.5 Validation Guide is a collection of common gotchas and recommended practices in spreadsheet form for easy reference and checkoff during the deployment process. There are two sections to this guide, the first section contains validation steps for common issues that can occur during the install process. The second section contains validation steps potentially required during post-install activities. Where possible, it contains both manual steps (vCenter Web Client actions) and CLI steps (RVC, ESXCLI, PowerCLI). These CLI steps can readily be translated into script form for easy automation.
I quickly fired up a PowerCLI console and checked my VSAN lab environment. Here is the shot just to give you an idea… Checking queue depth of my storage adapter (600 after the firmware update – not supported of course, but it works – see details in my post here).
It's an spreadsheet document which will get further updated in the future.
Source: VMware vSphere blog