
ESX hosts) for VMotion with VMFS volumes create a single storage group for all ESX servers in a farm or
cluster since LUNs may be assigned different Host LUN numbers if separate storage groups are created.
For additional information, see EMC Knowledgebase cases emc151686 and emc153719.
Starting with the VMware ESX Server 3.5 latest patch version, LUNs are identified by their LUN NAA (WWNs),
thus the requirement that the Host LUN numbers (HLU) must match across storage groups for VMotion is no
longer valid.
VMotion with RDM volumes
In order to perform VMotion with RDM volumes, the following prerequisites must be met:
• Both the RDM LUN and the VMFS volume that contains the mapping file must be shared by both
ESX servers.
• VMFS volumes must be in public access mode. This mode allows the volume to be accessed by
multiple ESX servers.
• The RDM LUN must have the same host LUN number on the source and destination ESX servers.
This can be set when adding LUNs to the storage group in Navisphere Manager.
• RDM volumes in both physical and virtual compatibility mode are supported with VMotion.
When using RDM volumes, the recommendation is to create a single storage group since LUNs may be
assigned different Host LUN numbers if separate storage groups are created.
Initially, swap files for virtual machines had to be stored on shared storage for VMotion. VMware
Infrastructure 3 (ESX Server 3.5 hosts and VMware vCenter 2.5 or later) now allows swap files to be
stored on local storage during VMotion migrations for virtual machines. For virtual machines with swap
files on local storage, when local storage is the destination during a VMotion migration or a failover, the
virtual machine swap file is re-created. The creation time for the virtual machine swap file depends on
either local disk I/O, or on how many concurrent virtual machines are starting due to an ESX Server host
failover with VMware HA.
If you have an AX4 system running Navisphere Express attached to a VMware ESX server (not VMware
ESX Server 3.5 and later), you can use Navisphere CLI to implement VMotion. Ensure that the Host LUN
number is consistent across all ESX servers using the storagegroup command. Your other option is to set
the LVM.Disallowsnapshot and LVM.EnableResignature parameter to 0 on all the ESX servers or LUNs
participating in VMotion/DRS/VMware HA for ESX 4.0 and/or 3.x servers.
EMC CLARiiON Integration with
VMware ESX Server
Applied Technology 35
Kommentare zu diesen Handbüchern