HP Matrix Operating Environment Software - Manual (Page 49)

NOTE: The Virtual Connect Flex-10 Ethernet Module for c-Class BladeSystem is supported in
this release. Flex-10 technology increases the number of NICs per connection. If you move a
Virtual Connect logical server and you have a large number of networks configured, the servers
with Virtual Connect with Flex-10 are shown in the list of available targets with a soft error icon
indicating insufficient NICs. This error can be safely ignored.
Table 3-1 Servers with Virtual Connect filter criteria
Servers with Virtual Connect filter criteria
The source and target servers with Virtual Connect have the same:
• Portability group.
• Model and generation. For example, if your logical server is running on an HP
ProLiant BL460c G1, you can activate it only to another HP ProLiant BL460c G1.
• Virtual Connect domain group.
• Mezzanine card in the same mezzanine slot.
• Blade state (not running).
Best Fit
No Errors
• Compute resources on the target server with Virtual Connect 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 Memory.
(You can view these values using the Modify
→Logical Server... menu selection,
and clicking the Compute tab.)
• Different network interface name and mezzanine card.
• Different storage fabric name and mezzanine card.
Acceptable Fit
Classifiable Soft Errors
Unclassifiable Soft Errors
• Source and target hosts are not in the same Virtual Connect domain group.
• Target host does not have a valid enclosure.
• Target host 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.
Logical server operations 49