
Booting from a CLARiiON storage system
This section discusses the procedure for booting the VMware ESX server and guest operating systems—
Windows, Linux, NetWare, and Solaris—from CLARiiON LUNs.
Booting ESX 4.0, 3.x, and ESX 2.5.x from CLARiiON LUNs with ESX
In ESX 4.0, 3.x, and 2.5 containing Fibre Channel HBAs zoned to a CLARiiON storage system, the service
console can boot from a CLARiiON LUN through the HBAs. To boot an ESX 2.5.x server from a LUN,
the HBAs must be shared between the service console and the virtual machines. In ESX 4.0 and 3.x, this is
not necessary because there is no concept of shared or dedicated HBAs. ESX 4.0 and 3.x support SAN boot
through Fibre Channel and iSCSI HBAs. SAN storage can be connected to VMware ESX 4.0 or 3.x
directly or through a switch.
There is no boot-from-SAN support for the VMware ESXi operating system image.
VMware ESX Server accesses LUNs through either a Fibre Channel or iSCSI HBA. If the ESX Server
machine has more than one HBA, all its HBAs must be the same model. The HBAs can be single or dual-
ported.
To boot through a LUN you must:
• Configure the BIOS settings for the Fibre Channel HBA to select the CLARiiON LUN as the boot
device.
• With ESX version 2.5, make sure that the boot LUN is /dev/sda and ID 0—the lowest-numbered
LUN visible to the ESX server. This is not necessary for ESX 4.0 and 3.x, since it uses the device
UUID for LUN identification.
• The internal SCSI de vice (controller) must be disabled for the CLARiiON LUN to map as
/dev/sda. Since the CLARiiON storage system consists of active/passive path configuration, the
lowest-numbered path to the boot LUN must be the active path.
• For ESX 2.5, install the VMware ESX Server software on the CLARiiON LUN using the boot-from-
SAN option. For ESX 3.x, when installing the server software, select the CLARiiON LUN from which
the operating system will boot.
Note: VMware ESX Server version 2.5 or later is supported for booting ESX over the SAN.
Booting guest operating systems on CLARiiON LUNs
Virtual machines can run on CLARiiON LUNs, as well as on internal disks. Virtual machines can boot
using both Fibre Channel and iSCSI CLARiiON storage. Booting virtual machines from shared storage is
also a requirement for VMware VMotion.
When booting virtual machines from a CLARiiON storage system, the LUNs are first presented to ESX.
LUNs presented to virtual machines are presented as “virtual” disks; to the virtual machine it appears that it
is accessing a physical disk. These disks are created when the virtual machine is created using a VMware
vCenter server or the Management User Interface (MUI). The operating system can be installed on these
“virtual” disks using a CD or ISO image. When the virtual machine is created, a configuration file with a
.vmx extension is also generated. This file contains the location of virtual disks, memory size, and some
basic hardware setup information (CD-ROM drive, floppy drive, network connections) for the virtual
machine.
Once the virtual machine is up and running, it is highly recommended that VMware Tools be installed on
each virtual machine. VMware Tools will optimize the use of the VMware ESX Server resources.
VMware Tools also provide a VGA device driver and a heartbeat mechanism for the virtual machine to
communicate with the VMkernel.
The procedure for connecting VMware ESX Server to the EMC CLARiiON storage system is found in the
Host Connectivity Guide for VMware ESX Server.
EMC CLARiiON Integration with
VMware ESX Server
Applied Technology 13
Comentarios a estos manuales