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
Understanding workload types
The term “workload” applies to each of the following distinct but closely related concepts in the
Insight Dynamics software:
• Monitored workload A workload that can be monitored by Virtualization Manager but
has no policy associated with it. Monitored workloads do not belong to an SRD and are not
managed by Global Workload Manager (gWLM).
For information about creating and modifying monitored workloads, see “Creating monitored
workloads” (page 31).
• Managed workload A workload that belongs to an SRD and is managed by Global
Workload Manager (gWLM). A managed workload has a policy assigned to it. You can
change a monitored workload into a managed workload by assigning a policy to it. Select
the check box next to the workload in either the Visualization View or the Workload View,
then choose Policy→Apply gWLM Policy.... To complete this action, you will be required
to create a new SRD. For more information on creating an SRD on gWLM, see the HP Insight
Global Workload Manager 6.0 Software: User Guide.
NOTE: A system may contain monitored workloads or managed workloads, but may not
contain both types of workloads.
• Whole-OS workload The set of all processes running on a system (for example, server,
nPartition, virtual partition, or virtual machine). The utilization metrics displayed for the
whole-OS workload allow you to monitor the total resource utilization on the system. The
whole-OS workload is not displayed as a workload in the Visualization View, but it is
represented by the compartment for the system. It appears in the Workload View, where
you can click the workload name to display the Workload Definition Properties screen. From
that screen, you can modify the workload name and description but you cannot define any
Workload Definition Criteria for the whole-OS workload.
NOTE: In the current release of the Insight Dynamics software (A.6.0.0.*), the whole-OS
workload is the only type of workload that is supported on systems running Microsoft
Windows or Linux.
• OTHER workload Whenever there are user-defined workloads on a system, Virtualization
Manager creates a special workload named “system-name.OTHER”. This workload accounts
for all processes on the system that do not match any of the user-defined workload definitions.
It is displayed like any other workload, except that you can only modify its name and
description, and you can only delete it when no other workloads remain on the system.
Under most circumstances, the “OTHER” workload is automatically deleted when the last
user-defined workload on the system is removed.
The OTHER workload is also created on Integrity VM hosts; it is not created for Microsoft
virtual servers or ESX. This workload accounts for all manageable resources that are not
allocated to any virtual machine on that host. This workload cannot be deleted.
NOTE: Global Workload Manager tracks processes in the “OTHER” workload differently
than Virtualization Manager and Capacity Advisor. For more information on how gWLM
tracks processes, see the HP Insight Global Workload Manager 6.0 Software: User Guide.
Creating monitored workloads
You can create monitored workload definitions from the either the Visualization View or the
Workload View, as follows:
Visualization View
Using the workload view 31