VirtuallyGhetto has a great post on configuring VSAN on a nested ESXi box by getting a VMDK to report itself as an SSD disk. However this doesn’t seem to work for Virtual Flash.
Here is my nested host showing an “SSD” drive
And VSAN also reporting it (since there are no other available local non-SSD it shows as ineligible)
But Virtual Flash doesn’t see the drive to add it.
Am I missing something or can Virtual Flash not be “faked out” for a nested host?
Edit:
Found it after tweets from William Lam and Duncan Epping
For whatever reason the VMDK attached to the nested host wasn’t flagged as local:
esxcli storage core device list -d mpx.vmhba1:C0:T0:L0 ... Is Local: false
Answer was:
esxcli storage nmp satp rule add -s VMW_SATP_LOCAL --device mpx.vmhba1:C0:T0:L0 --option="enable_local" esxcli storage core claiming unclaim --type device --device mpx.vmhba1:C0:T0:L0 esxcli storage core claimrule load esxcli storage core claimrule run esxcli storage core device list -d mpx.vmhba1:C0:T0:L0
Note from the documentation link above the “option” parameter is missing the “–“




There’s a later William Lam post (from VMworld Barcelona) where he provides the details necessary to get this to work [http://www.virtuallyghetto.com/2013/10/vmworld-barcelona-notsupported.html], the trick is to force the nested ESXi host not to use mpx.vmhba style addressing (disk.enableUUID = true)
Make sure you search in the VMware database to verify the drive is supported. Ours would sit at the Task “vcenter configure virtual flash” and never completing it.
http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vfrc
Not really needed for a nested ESXi host.
Pingback: VMware Link Collection | Life
Great readding