HP Virtualization Manager 6.0 Software with Logical Server Management User Guide
Table Of Contents
- HP Insight Virtualization Manager 6.0 Software with Logical Server Management: User Guide
- Table of Contents
- 1 Introduction
- 2 Getting started with Virtualization Manager
- 3 Working with logical servers
- Using logical servers in Virtualization Manager
- New features in logical servers
- Understanding logical servers as they appear in visualization perspectives
- Logical server operations
- Authorizations, requirements, and configuration
- Logical server requirements
- Configuring and registering VMware vCenter
- Configuring VMware vSphere client settings for browsing datastore
- Configuring HP SIM with Onboard Administrator credentials
- Configuring HP SIM for SAN storage validation
- Configuring Extensible Server & Storage Adapter (ESA)
- Configuring Storage Provisioning Manager (SPM)
- LSMUTIL database utility
- 4 Defining storage for logical servers
- 5 Troubleshooting
- Navigation tips
- User preferences tips
- Performance tips
- Problems with meters collecting data
- Search button displays error page
- Displaying empty, hidden resource pools
- Errors accessing single sign-on iLO or Onboard Administrator
- Recovery after logical server operation failures
- Troubleshooting an inoperable logical server
- Correcting problems powering on a logical server
- Logical server operations cannot be cancelled
- Logical Server Automation service fails to start if TCP layer ports are in use
- Use portable WWNs and MAC addresses for Virtual Connect domain groups
- Do not use valid host name as logical server name
- Oversubscribing the number of networks
- Insufficient NICs error when activating or moving logical servers (Virtual Connect Flex-10 support)
- Use caution when renaming or moving a Virtual Connect domain group
- Deactivate or move logical servers before replacing blade
- Unmanaging a logical server using a storage pool entry may result in an inconsistent state
- Synchronize clocks on the CMS, managed systems, and VMware vCenter
- Ensure VM Hosts use fully qualified host names
- VM Hosts must be in same vCenter for ESX virtual machine logical server moves
- VM displayed without association in Virtualization Manager perspectives after deactivation
- Moving logical servers when the CMS and vCenter are in different network domains
- Changing the IP address of a VM Host after logical server discovery prevents the VM Host from appearing as an activation and move target
- Creating and managing logical servers on Microsoft Windows Hyper-V Server 2008
- 6 Advanced features
- 7 Support and other resources
- Index
• 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,
and operating system on which the logical server is to be created.
• Compute resources, including number of CPU cores, CPU frequency, and amount of memory.
• Storage configuration.
ESX and Hyper-V virtual machine logical server storage is supported using the Virtual
Machine File System (VMFS), DAS, iSCSI, or SAN datastores.
Storage for an imported HP Integrity Virtual Machines logical server storage must be a SAN
datastore.
Virtual Connect logical server storage is supported using shared (SAN) storage. These logical
servers require that the operating system boots only from SAN, and do 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.)
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, or
by using the HP Storage Provisioning Manager.
• Network configuration. Logical server management supports 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 HP SIM node, and
is created and maintained independently of the logical server.
New features in logical servers
Following are the new features in Logical Server Management for this release.
• Expanded technology support
— Architecture: HP Integrity virtual machines
Import, online move, unmanage, and power on and off an HP Integrity virtual machine.
(You cannot perform any other operations on an HP Integrity virtual machine logical
server in this release.)
Integrity VM now supports an additional provider, the Integrity VM Virtualization
Provider. The Integrity VM Virtualization Provider, used with the logical servers feature
in Insight Dynamics, enables virtual to virtual migration.
38 Working with logical servers