The ZIP also contains versions of the tools that will make this process a bit easier. This has been updated to support the latest version of FreeNAS. The main firmware file in this ZIP is P20.
The default sas2flsh.exe and sas2flash.efi in this new ZIP file are p5 which allows you to pretty much overwrite/downgrade any firmware. the difference between the old and new ZIP file is the sas2flsh and sas2flash versions. So I’m not sure why I retyped all of this instead of just updating the ZIP file in the old guide.
So this guide will be the update to my first guide… without double checking everything I’m pretty sure it’s almost identical except for the link to the ZIP file. To avoid issues, I think it's better to just stick with the HCL.WARNING: If you have an Integrated, Mini or Mini Mono Perc H310 do NOT try to crossflash with these steps. There's another variant which is supported though (MZ7KM480HAHP & MZ7KM480HMHQ).
The minimum from a practical perspective should be 4 nodes.The Samsung Pro is also not supported. With 3 nodes, when you reboot a host you are putting your vSAN cluster in a degraded state. The minimum from a practical perspective should be 4 nodes. VSAN is going to consume some CPU resources, so make sure 12 cores per host is enough if vSAN is chewing up 10% With 3 hosts you're going to want 10GbE switching Get an Intel NIC like i350 if you need 1GbE or X540 or X550 for 10GbE. You probably want SAS SSD for your cache tier instead of SATA SSD.īroadcom sucks.
850 Pro is listed as 150TB write endurance, while most vSAN cache drives are going to have many PB of endurance. But I doubt it, as it has much lower write endurance than typical drives used with vSAN. Samsung Pro doesn't look like it's supported at all (unless it's under some other part number I can't find). Pretty sure I recall StorageNinja say this as well. I don't see any SATA drives supported since ESXi 5.5 with vSAN. PERC H200 (last supported in ESXi 5.5) - Link Not unless you plan on running ESXi 5.5 forever.