Operating Environment Software Manual

Table 4-1 Servers with Virtual Connect filter criteria
Servers with Virtual Connect filter criteria
The source and target servers Virtual Connect have the same
• Portability group
• Model and generation
• FCoE capability
• Virtual Connect domain group
• Mezzanine card in the same mezzanine slot
• Blade state (not running)
Best Fit
No Errors
• Compute resources on the target blade are not greater than or equal to the values you
specified when you created or modified the logical server. These values include
Number of Cores, CPU Frequency, and Amount of Memor y.
• Different network interface name and mezzanine card
• Different storage fabric name and mezzanine card
• You are attempting to move a logical server from a physical to virtual system or a
virtual to physical system and the source logical server has never been activated
on a target of this platform type.
Acceptable Fit
Classifiable Soft Errors
Unclassifiable Soft Errors
Examples of rejected filter criteria
• Source and target server blades are not in the same Virtual Connect domain group
• Target server blade does not have a valid enclosure
• Source and target server blades do not have the same FCoE capability
• Target server blade is not licensed
• Blade state is running
• Onboard Administrator authorization error
• Blade controller fault
Rejected
Hard Errors
Moving ESX, Hyper-V, and HP Integrity virtual machine logical servers
If you are moving a logical server from one virtual machine to another, the following restrictions
apply.
• You can move virtual machine logical servers within a set of hypervisors of the same type
(ESX, Hyper-V, Integrity VM). You cannot move virtual machine logical servers from one
type of hypervisor to another type.
• For non-live moves, HP recommends that you shut down the virtual machine on which the
logical server was activated before you move it. Otherwise, the virtual machine will be
ungracefully shut down and powered off.
A shutdown is not necessary if your virtual machine is configured for live migration, and
you are moving the logical server within the same ESX cluster using VMware VMotion.
• For non-live moves, moving a logical server shuts down the source virtual machine and
removes the virtual machine definition. The target virtual machine is powered on, by default.
If the source virtual machine is powered off, you can uncheck the Power On the VM or the
Blade checkbox to keep the target virtual machine powered off after the move.
• An HP Integrity virtual machine must be powered on before you can perform a live move.
• When you power on an ESX virtual machine that was moved to a new location, a VMware
message appears, asking you if you want to create a new UUID (Logical) for the virtual
machine, or keep the old one. Select Keep, then click OK to continue powering on the virtual
machine.
• You can move ESX virtual machine logical servers among multiple clusters, as long as the
clusters are contained in one VMware vCenter.
• There may be a delay in the population of possible target hosts if the CMS and vCenter are
in different network domains (subnets). Similarly, if you are moving the logical server using
drag and drop, there may be a delay before the hosts appear as valid targets.
Logical server operations 51