HP Virtualization Manager with Logical Server Manager 6.2 User Guide

◦ Import
◦ Power on and off
◦ Online move
◦ Unmanage
• Network:
— Create an Integrity VM virtual machine logical server using Accelerated Virtual I/O
(AVIO) network devices. The Integrity VM Host administrator must create all required
virtual switches that will be used by Integrity VM guests before managing the Integrity
VM Host.
— The vSwitch name can be a maximum of 8 characters. (This restriction is important if
you intend to manage Integrity VM logical servers and cross-technology logical servers
[ESX virtual machine and Virtual Connect logical servers], because, for cross-technology
logical servers, at least one network in the Virtual Connect domain group must be
named identically to a vSwitch on the ESX Host.)
Requirements for Virtual Connect logical servers
• Firmware for ProLiant blades only in a Virtual Connect Domain Group
— Virtual Connect Manager 3.15 or higher
— HP BladeSystem Onboard Administrator 3.10 or higher. See “Configuring HP SIM with
Onboard Administrator credentials” for important information.
HP BladeSystem Onboard Administrator 3.15 or higher is required for FCoE (Fibre
Channel over Ethernet) and BL680 G7 blade support.
— HP Integrated Lights-Out (iLO2) for ProLiant 2.00 or higher
— Latest available firmware update for your server blade BIOS
• Firmware for Integrity blades only, or a combination of ProLiant and Integrity blades in a
Virtual Connect Domain Group
— Virtual Connect Manager 3.15 or higher
— HP BladeSystem Onboard Administrator 3.10 or higher. See “Configuring HP SIM with
Onboard Administrator credentials” for important information.
HP BladeSystem Onboard Administrator 3.15 or higher is required for FCoE (Fibre
Channel over Ethernet) and BL680 G7 blade support.
— HP Integrated Lights-Out (iLO2) for ProLiant 2.00 or higher
— HP Integrated Lights-Out (iLO2) for Integrity 3.15 or higher
— Latest available firmware update for your server blade BIOS
See the HP BladeSystem Firmware compatibility chart for more information.
• Storage You can activate a Virtual Connect blade logical server only if you specified shared
(SAN) storage as your storage configuration when you created the logical server.
Logical server management requires that the operating system boots only from SAN, and
does not support any operating system that boots from a non-SAN disk.
A virtual machine host that is running on a server with Virtual Connect with a SAN boot
disk can be managed as a Virtual Connect logical server.
Logical server management leverages Virtual Connect Enterprise Manager and Virtual Connect
Manager to provide Virtual Connect based functionality. HP recommends that you are familiar
with these technologies. See http://www.hp.com/go/vcem and http://www.hp.com/go/
bladesystem/virtualconnect for more information.
58 Managing logical servers