What is the proper LUN Masking configuration for LUNs presented to an ESX
Host when using the Boot from SAN option?
A.
The Boot LUN and datastore LUNS should be masked so that only one ESX Host can
see the LUNs
B.
The Boot LUN and datastore LUNS should be masked so that all ESX Hosts can see
the LUNs
C.
The Boot LUN should be masked so that only one ESX Host can see the LUN, while
the datastore LUNS should be masked so that all ESX Hosts can see the LUNs
D.
The Boot LUN should be masked so that all ESX Hosts can see the LUN, while the
datastore LUNS should be masked so that only one ESX Host can see the LUNs
Explanation:
iSCSI SAN Configuration Guide, page 14, 52.
Boot LUNs should only be visible to the server using that LUN to boot. No other server
or system on the SAN should be permitted to see that boot LUN.
ESX/ESXi and SAN Use Cases.
You can perform a number of tasks when using ESX/ESXi with SAN. Using ESX/ESXi
in conjunction with SAN is effective for the following tasks:
Maintenance with zero downtime
When performing an ESX/ESXi host or infrastructure maintenance, use VMware DRS or
VMotion to migrate virtual machines to other servers. If shared storage is on the SAN,
you can perform maintenance without interruptions to the user.
Load balancing
Use VMotion or VMware DRS to migrate virtual machines to other hosts for load
balancing. If shared storage is on a SAN, you can perform load balancing without
interruption to the user.
To enable this functionality, shares storage is required – hence the datastore LUNS
should be masked so that all ESX Hosts can see the LUNs