The private Lun that ESX points to for booting does not have enough space to store the COS vmdk. Is it okay to place the COS on a shared LUN that other ESX servers can see?
Hi,
no, it's not okay to use a shared LUN.
Check Fibre Channel SAN Configuration Guide, section Getting Ready for Boot from SAN.
Hope this helps a bit.
Greetings from Germany. (CET)
Hi,
no, it's not okay to use a shared LUN.
Check Fibre Channel SAN Configuration Guide, section Getting Ready for Boot from SAN.
Hope this helps a bit.
Greetings from Germany. (CET)
From looking at the guide i see that only each esx server needs a private lun for booting. Which is what I have. So other ESX servers cannot see the LUN being used for for booting each esx server. I do not see where it says that you cannot put the cos VMDK on a shared LUN that other ESX servers can see. The wizard allows you to do this. Myabe im missing something?
While putting the esxconsole.vmdk on a shared datastore would be technically possible, it would be a very bad idea, and I can't imagine that's a supported configuration. That opens up far too much room for human error affecting the COS of your ESX hosts.
-jk