Some random tips and observations on the initial VSAN setup:

1. vCenter will not accept a VSAN 6.2 license key until it is running 6.0U2.  Now that the VCSA admin portal is gone (thanks for that VMware), I followed this guide to patch the VCSA.
2. Use the ISO from VMware rather than a customized ISO (Dell, HP, etc.).  Either way, VIBs need to be replaced, so a customized ISO just overcomplicates things in my opinion.
3. After install, I replaced the following VIBs to match the HCL:

• Intel NVMe VIB from Intel
  • Unlike most VIB installs where the older version is removed, this one requires the default NVMe driver to be removed in order to go into effect, since the old and new VIB names do not match.  To remove the VMware VIB:
    • esxcli software vib remove -n nvme
• Intel SSD Datacenter Tool
  • This won’t work without the above Intel NVMe VIB running.  Once installed, it’s a pretty cool cli utility for managing firmware and getting heath info on the P3700 drive.
• lsi_mr3 from VMware
  • I’m still undecided on this one, but I’ve decided to follow the HCL despite being biased towards the megaraid_perc9 VIB.  Interestingly enough, there’s now a VMware KB that states the PERC H730 is not supported on VSAN 6.2.
• net-bnx2 and netbnx2x from VMware
  • This was suggested by Dell support since the default 6.0U2 drivers are out of date for the Broadcom/QLogic/whatever it is now card.

4. Don’t use VMFS5 formatting on disks that will be in VSAN.  I formatted a couple of drives to use as a temporary datastore for VIB installs and then spent a couple hours trying to erase the disks.  I couldn’t quite figure out what the issue was but I couldn’t unmount the disk because the filesystem was busy, even after a reboot.  All built in VMware utilities didn’t work.  I finally resorted to booting each host to a Windows Server 2012 ISO and removed all existing partitions to fix it.