- 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 you proceed.
- Migrate VM’s off of host.
- Place host into maintenance mode.
- You want to use whatever the quickest method is to update the firmware, for VSAN's sake. Normally Dell FTP update if network available to configure.
- When you put a host into maintenance mode and choose the option to "ensure accessibility", it doesn't migrate all the components off but just enough so that the policies will be in violation. A timer starts when you power it off, and if the host isn't back in the VSAN cluster after 60 minutes, it begins to rebuild that host's data elsewhere in the cluster If you know it will take longer than 60min or where possible select full data migration.
- You can view the resync using the RVC command "vsan.resync_dashboard <cluster/host>"
- Change advanced settings required for PERC H730
- esxcfg-advcfg -s 100000 /LSOM/diskIoTimeout
- esxcfg-advcfg -s 4 /LSOM/diskIoRetryFactor
- Upgrade the lsi_mr3 driver. VUM is easy!
- Login to DRAC and perform firmware upgrade:
- Upgrade Backplane expander (BP13G+EXP 0:1)
- Firmware version 1.09 -> 3.03
- Upgrade DRAC H730 version
- 25.3.0.0016 -> 25.4.0.0017
- Login to lifecycle controller and set/verify BIOS configuration settings for controller
- Disk cache for non-raid = disabled
- Bios mode = pause on errors
- Controller mode = HBA (non-raid)
- After all hosts upgraded, verify VSAN cluster functionality and other prerequisites:
- Verify no stranded objects on VSAN datastores by running python script on each host.
- Verify persistent log storage for VSAN trace files.
- Verify advanced settings still set from task 3!
- Place each host into maintenance mode again.
- Upgrade ESXi host to 6.0U2.
- Upgrade the on-disk format to V3.
- This task runs for a very long time and has alot of sub-steps which takes place in the background. It also migrates the data off of each disk group to recreate as V3 . This has not impact on the VMs.
- This process is repeated for all disk groups.
- Verify all disk groups upgrade to V3.
Ran into some serious trouble and had a resync task that ran for over a week due to a VSAN 6.0 KB 2141386 which appears on heavy utilization storage utilization. Only way to fix this was to put host into maintenance mode with full data migration, destroy and recreate the disk group.
Also ALWAYS check the VMware HCL to make sure your firmware is compatible. I can never say this enough since it is super important.
This particular VSAN 6.0 was running with outdated firmware for both backplane and PERC H730. Also found that controller was set to RAID for disks in stead of non-raid (passthrough or HBA mode).
VMware as a kick@ass KB on best practices for Dell PERC H730 for VSAN implementation. Link provide below.