HP 6100 HP StorageWorks MPX200 - Simplified Cost-Effective Virtualization De - Page 8

D2, and RDM C is created on Vdisk D3. VM1 is installed in RDM A, VM2 in RDM B, and VM3

Get HP 6100 PDF manuals and user guides View all HP 6100 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 8 highlights

Figure 3: Implementation Option 2 The physical EVA Vdisks volume is configured as the RDM volume. In this option, only one Vdisk is used to create the RDM volume. Thus, RDM A is created on Vdisk D1, RDM B is created on Vdisk D2, and RDM C is created on Vdisk D3. VM1 is installed in RDM A, VM2 in RDM B, and VM3 in RDM C. Microsoft Windows guest OS is installed in every VM. Microsoft's software iSCSI initiator is configured in every VM. The software iSCSI initiator in the VM is configured to connect to MPX200. The Vdisk D4 is presented to the iSCSI initiator in VM1, Vdisk D5 is presented to the iSCSI initiator in VM2, Vdisk D6 is presented to the iSCSI initiator in VM3. Because the VM has direct ownership of its LUNs, it has the flexibility of managing those LUNs it wants. The iSCSI EVA Vdisks in the guest OS can be configured with the native file system of the guest OS, and the application and data can be stored there. The basic configuration would have one LUN defined for each guest OS that is managed by the hypervisor and contains the VM's boot image. The hypervisor would also run its own iSCSI initiator. As the VM is installed in a single Vdisk RDM volume, chances of any VMs sharing it is eliminated; hence, this configuration is desirable for high-performance applications, while the VMs benefit from owning and managing its LUNs.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
Figure 3
: Implementation Option 2
The physical EVA Vdisks volume is configured as the RDM volume. In this option, only one Vdisk is
used to create the RDM volume. Thus, RDM A is created on Vdisk D1, RDM B is created on Vdisk
D2, and RDM C is created on Vdisk D3. VM1 is installed in RDM A, VM2 in RDM B, and VM3 in
RDM C. Microsoft Windows guest
OS is installed in every VM. Microsoft’s software iSCSI initiator
is configured in every VM. The software iSCSI initiator in the VM is configured to connect to
MPX200. The Vdisk D4 is presented to the iSCSI initiator in VM1, Vdisk D5 is presented to the
iSCSI initiator in VM2,
Vdisk D6 is presented to the iSCSI initiator in VM3. Because the VM has
direct ownership of its LUNs, it has the flexibility of managing those LUNs it wants. The iSCSI EVA
Vdisks in the guest OS can be configured with the native file system of the guest OS, and the
application and data can be stored there.
The basic configuration would have one LUN defined for each guest OS that is managed by the
hypervisor and contains the VM’s boot image. The hypervisor would also run its own iSCSI
initiator. As the VM is installed in a single Vdisk RDM volume, chances of any VMs sharing it is
eliminated; hence, this configuration is desirable for high-performance applications, while the
VMs benefit from owning and managing its LUNs.