VMware Cloud Community
Isurfer
Contributor
Contributor
Jump to solution

Location of COS vmdk

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?

0 Kudos
1 Solution

Accepted Solutions
kastlr
Expert
Expert
Jump to solution

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)


Hope this helps a bit.
Greetings from Germany. (CEST)

View solution in original post

0 Kudos
3 Replies
kastlr
Expert
Expert
Jump to solution

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)


Hope this helps a bit.
Greetings from Germany. (CEST)
0 Kudos
Isurfer
Contributor
Contributor
Jump to solution

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?

0 Kudos
jjkrueger
VMware Employee
VMware Employee
Jump to solution

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

0 Kudos