HP Matrix Operating Environment 7.3 and 7.3 Update 1 Logical Server Management User Guide

Using logical servers within the Matrix OE visualization provides the following benefits:
• Allows you to use a common interface and management tools for both virtual machines and
servers with Virtual Connect.
• Allows you to deploy resources only when needed. For example, some applications are needed
only during parts of a business cycle.
• Increases business agility and flexibility by decoupling business processing from physical
hardware, allowing you to respond to rapid changes in demand.
• Reduces downtime required for physical system maintenance, whether planned or unplanned.
• Allows for server consolidation and improved server utilization, which help to maximize limited
compute resources.
Each logical server that you create, or define, includes the following information:
• Identity information including a unique name, description, portability group, architecture on
which the logical server is to be created, and OS (to help ensure suitable storage configuration).
• Compute resources, including number of CPU cores, CPU frequency, and amount of memory
• Storage configuration
See “Logical server requirements” (page 23) for supported logical server storage.◦
◦ Multiple datastores are supported for a variety of VMware ESXi and Hyper-V
environments. All storage volumes for an Integrity VM virtual machine must use the same
datastore, and Hyper-V Linked Clone disks must use the same datastore.
◦ Virtual Connect logical server storage is supported using SAN storage. These logical
servers require 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 logical
server.)
NOTE: When creating logical servers from Matrix OE visualization, local disk is not
supported. However, if using Matrix infrastructure orchestration, there is a mechanism
for local disk support via manual file edits to provide local disk information. For more
information, see “Modifying physical servers with local disk information” (page 75). HP
recommends logical servers with operating system booting from SAN, and data disks in
the SAN (for maximum flexibility as the logical server moves from one Virtual Connect
system to another).
◦ Storage pool entries allow you to access storage without being concerned with where or
how that storage is physically located. You can configure storage pool entries manually
on the logical servers screens, or by using HP Storage Provisioning Manager.
• Network configuration. Logical server management supports the selection of networks from a
predefined set supported by hypervisors or Virtual Connect.
Creating and activating logical servers does not include:
• Operating system provisioning. Before you can fully utilize an activated logical server, you
must install the operating system, and the operating system must be loaded with standard
provisioning tools. If the server with Virtual Connect or virtual machine has been provisioned
with an operating system, activating the logical server boots it. (A VM guest or server with
Virtual Connect does not need to be provisioned with an operating system before it is imported.)
• Information such as the IP address. This is available as an attribute of the Systems Insight
Manager node, and is created and maintained independently of the logical server.
Using logical servers in Matrix OE visualization 7