Please feel free to provide feedback and would to add to my list with your experiences.
- The VSAN on-disk metadata upgrade is equivalent to doing a SAN array firmware upgrade and therefore requires a good backup and recovery strategy to be in place before we can proceed.
- Enough resources => 3 node cluster!
- If 3 or less node cluster then unable to evacuate the disk groups
- Run RVC command: > vsan.ondisk_upgrade –allow-reduced-redundancy
- Requirement of 6 GB of RAM inside a host with 6.0U2 running VSAN. (for lab environment)
- Each host should contain a minimum of 32 GB of memory to accommodate for the maximum number of 5 disk groups and maximum number of 7 capacity devices per disk group.
- Verify no stranded objects on VSAN datastores before disk format upgrade.
- VM swap object left behind
- Locked CBT file
- Broken snapshot disk chain
- Run python SCRIPT to find and fix stranded objects.
- Verify the storage controller on the host is compatible
- Verify the storage controller is set to pass-through or HBA mode for RAID.
- Verify the storage controller has caching disabled.
- Open VMWARE HCL and verify that your firmware is up date for all server components.
- Persistent logging folder for VSAN trace file and rest (USB or SD-card ESXi install)
- I do recommend you install vRealize Log insight for syslog collection, after all its free for up to 25 OSI)
- Hybrid requires at least 1 x 1GB connection
- Flash requires at least 1 x 10GB connection
- Layer 2 multicast must be enabled on the physical switch
- Each ESXi host in the cluster must have a vmkernel port