HP Insight Control virtual machine management 6.0

HP Insight Control virtual machine
management 6.0
User Guide
HP Part Number: 380094-403
Published: January 2010
Edition: 12
© Copyright 2004, 2010 Hewlett-Packard Development Company, L.P.
Legal Notices
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Microsoft, Windows, Windows NT, Hyper-V, and Windows XP are U.S. registered trademarks of Microsoft Corporation.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
VMware, ESX Server, vCenter Server, and VMotion are trademarks of VMware, Inc.
Red Hat Enterprise Linux is a registered trademark of Red Hat, Inc. in the U.S. and other countries.
SLES is a registered trademark of Novell, Inc. in the United States and other countries.
Table of Contents
About this document......................................................................................9
Intended audience..................................................................................................................................9
Related documents..................................................................................................................................9
HP encourages your comments.................................................................................................................9
1 Introduction.............................................................................................11
HP Insight Control virtual machine management........................................................................................11
Infrastructure.........................................................................................................................................11
HP Systems Insight Manager console integration.......................................................................................12
Agentless Management.........................................................................................................................13
2 HP Insight Control virtual machine management licensing..............................15
Licensing HP Insight Control virtual machine management through the Insight Control license manager............15
Licensing standalone Insight Control virtual machine management...............................................................15
Adding standalone licenses....................................................................................................................15
Applying standalone licenses..................................................................................................................16
3 Using HP Insight Control virtual machine management..................................17
Registering virtual machine hosts.............................................................................................................17
Configuring VMware vCenter servers ......................................................................................................17
Configuring the xapi port for Citrix XenServer...........................................................................................18
Configuring WMI Mapper proxy server settings for Microsoft Hyper-V server................................................18
Configuring Insight Control virtual machine management on a Microsoft Cluster Server..................................18
Unregistering virtual machine hosts..........................................................................................................18
Updating the HP SIM certificate on CMS..................................................................................................19
Insight Control virtual machine management interface overview..................................................................19
Virtual machine host..............................................................................................................................19
Virtual machine guest............................................................................................................................21
Configured and unconfigured virtual machines..........................................................................................22
Configured.....................................................................................................................................22
Unconfigured..................................................................................................................................22
Using Insight Control virtual machine management controls and tools..........................................................23
Starting or resuming a virtual machine guest.......................................................................................26
Shutting down or stopping a virtual machine guest...............................................................................26
Suspending or pausing a virtual machine guest...................................................................................26
Resetting or restarting a virtual machine guest......................................................................................27
Launching remote access..................................................................................................................27
Launching Remote Console................................................................................................................27
Launching Remote Desktop................................................................................................................28
Launching SCVMM..........................................................................................................................29
Microsoft Hyper-V Server Host System page....................................................................................29
Microsoft Hyper-V Server Guest System page..................................................................................29
Launching VC.......................................................................................................................................29
VMware ESX Server Host System page...............................................................................................30
vCenter Server information................................................................................................................30
Copying a virtual machine guest........................................................................................................30
SUSE Linux scenario....................................................................................................................31
Moving a virtual machine guest.........................................................................................................32
Moving virtual machine guests.....................................................................................................32
Creating a virtual machine guest template...........................................................................................34
Migrating virtual machine guest templates and backups........................................................................34
Deploying a virtual machine guest template.........................................................................................35
Table of Contents
3
Deleting a virtual machine guest template...........................................................................................36
Creating a virtual machine guest backup............................................................................................36
Restoring a virtual machine guest backup............................................................................................37
Restoring the most recent virtual machine guest backup.........................................................................38
Recovering virtual machines of a failed host on a VMware ESX Server, Citrix XenServer or Microsoft Hyper-V
R2 server........................................................................................................................................38
Removing an alternate virtual machine host on a VMware ESX Server, Citrix XenServer, or Microsoft Hyper-V
R2 server........................................................................................................................................39
Launching vCenter...........................................................................................................................39
Setting or removing the performance threshold....................................................................................39
Configuring the polling frequency for virtual machine status checks..............................................................39
Setting the alternate virtual machine host..................................................................................................40
Handling prefailure events......................................................................................................................40
Prerequisites....................................................................................................................................40
Handling automatic prefailure events..................................................................................................41
Handling automatic prefailure events using the vCenter Server DRS cluster enabled in the vCenter Server....41
Handling semi-automatic prefailure events with the vCenter Server DRS cluster enabled in the vCenter
Server............................................................................................................................................41
Handling automatic prefailure events using the Set Alternate host feature.................................................41
Handling semi-automatic events using the Set Alternate host feature........................................................42
Handling automatic prefailure events using the Set Alternate host feature.................................................42
Handling semi-automatic events using the Set Alternate host feature........................................................42
Failed host recovery..............................................................................................................................42
Setting up the recovery feature................................................................................................................43
Creating a CriticalVmHost collection.......................................................................................................44
Scheduling the recovery of virtual machines of failed hosts.........................................................................44
VMware ESX Server Guest System page...................................................................................................46
Performance information........................................................................................................................46
Displaying virtual machine host performance information...........................................................................47
Virtual machine host performance......................................................................................................47
Virtual machine performance.............................................................................................................47
Threshold settings.............................................................................................................................48
Displaying virtual machine guest performance..........................................................................................48
Virtual machine performance.............................................................................................................48
Resource allocation...............................................................................................................................49
Threshold settings.............................................................................................................................49
Performance color codes........................................................................................................................49
Multisystem aware tools available...........................................................................................................50
4 Troubleshooting........................................................................................51
Troubleshooting....................................................................................................................................51
Installation...........................................................................................................................................51
In an environment using multiple instances of HP SIM CMS, Insight Control virtual machine management
can only be installed on one CMS.....................................................................................................51
System starting improperly or installation fails to proceed......................................................................51
Some menus do not appear in the toolbars.........................................................................................52
After upgrade, virtual machine host registration completes successfully without discovering the vCenter
server and without vCenter credentials................................................................................................52
Uninstalling Insight Control virtual machine management......................................................................52
VMMclient.jar, commons-cli-1.0.jar, or org.mortbay.jetty.jar files fail to copy............................................52
Mouse does not work properly after Microsoft Hyper-V server installation................................................52
Configuration.......................................................................................................................................53
Insight Control virtual machine management host registration fails..........................................................53
Virtual machine host registration CRA fails when selected with "Install Linux PSP or ESX agents" for VMware
ESX 3.5 U4.....................................................................................................................................53
Performance information does not appear for Citrix XenServer host and virtual machines...........................53
Insight Control virtual machine management items are not removed from the HP SIM toolbar with Insight
Control virtual machine management uninstallation..............................................................................53
4
Table of Contents
Insight Control virtual machine management might not detect virtual machines located on mapped network
drives.............................................................................................................................................53
Configuring Insight Control virtual machine management to manage virtual machine hosts behind a
firewall...........................................................................................................................................54
Microsoft DNS Server might not map the host name to DHCP-generated IP addresses...............................54
Virtual machine hosts are in different subnets.......................................................................................54
Insight Control virtual machine management controls.................................................................................54
Virtual machine host and guest icons do not appear in Insight Control virtual machine management...........54
Insight Control virtual machine management does not display the system name, system IP address, and
operating system..............................................................................................................................55
Critical status appears for a virtual machine host in Insight Control virtual machine management................55
A blank page appears when you launch Insight Control virtual machine management from HP SIM............55
Virtual machine status is not updated..................................................................................................56
Virtual machine guest information becomes inaccessible from Insight Control virtual machine
management...................................................................................................................................56
A virtual machine host appears in Insight Control virtual machine management multiple times....................56
A virtual machine guest appears in VMware vCenter Server multiple times..............................................56
Live Move fails after SAN move.........................................................................................................56
VMotion fails because virtual machine host names are mismatched in HP SIM and vCenter Server.............56
Virtual machine host experiences extremely slow response time..............................................................56
Insight Control virtual machine management demo licensing..................................................................57
If the same backup is restored multiple times, then the Restore Virtual Machine from backup operation
fails...............................................................................................................................................57
Recovery of virtual machine fails with incompatible hardware configurations...........................................57
An error occurs when you click Remote Desktop...................................................................................57
VMM Pack functions..............................................................................................................................57
Stop VM task does not perform as expected on Xen on RHEL 5.4 x86 virtual machine hosts......................57
Error message Unknown to VMM appears when performing the copy operation on a virtual machine.........57
Transport operation fails after restarting Insight Control virtual machine management................................57
Copied or moved Xen virtual machine guest does not start on the destination host....................................58
Handle virtual machine host prefailure events task does not progress......................................................58
HTTP ERROR: 500 Internal Server Error message appears during a Insight Control virtual machine
management move or copy operation................................................................................................58
Insight Control virtual machine management cannot move virtual machines with certain disk types.............58
Virtual machine files are not deleted after a move................................................................................58
Virtual machine devices might not be available after a copy or move.....................................................58
A shutdown or restart operation fails or does not complete....................................................................58
Launching the remote console from Insight Control virtual machine management console might fail.............59
Some Insight Control virtual machine management operations dependent on vCenter Server do not complete
or are completed without confirmation................................................................................................59
Orphan managed systems created in the CMS....................................................................................59
Failed host recovery on master Citrix XenServer host of the HA disabled resource pool fails.......................59
Insight Control virtual machine management does not display Quick Move option for HA configured Microsoft
Hyper-V server virtual machines in the Move wizard.............................................................................60
Prefailure alerting reports errors for Citrix XenServer resource pool.........................................................60
Hyper-V R2 host virtual machines recovered on alternate host using Failed Host Recovery cannot be powered
on.................................................................................................................................................60
HP SIM console integration....................................................................................................................60
The virtual machine guest is not listed on the HP SIM All Systems page...................................................60
Certain Insight Control operations cannot be performed on a virtual machine..........................................60
The HP SIM console does not identify a server as a virtual machine host.................................................60
The HP SIM console does not discover a virtual machine host or guest....................................................60
HP SIM console identifies a virtual machine guest as an unknown or unmanaged device...........................61
The virtual machine is discovered as an unmanaged system..................................................................61
Uninstalling or retiring an HP SIM CMS..............................................................................................61
Hardware............................................................................................................................................62
Re-entering the server serial number and product ID ............................................................................62
Additional resources.........................................................................................................................62
Table of Contents
5
5 Support and other resources......................................................................63
Contacting HP......................................................................................................................................63
Information to collect before contacting HP..........................................................................................63
How to contact HP technical support..................................................................................................63
Registering for software technical support and update service................................................................63
HP authorized resellers.....................................................................................................................64
Documentation feedback..................................................................................................................64
Related information...............................................................................................................................64
A Virtual machine events..............................................................................65
Viewing virtual machine events...............................................................................................................65
Insight Control virtual machine management events...................................................................................66
Insight Control virtual machine management Events..............................................................................66
Error list...............................................................................................................................................67
B vCenter and VMware ESX Server host events................................................77
C Customizing virtual machines.....................................................................81
HP SIM permissions...............................................................................................................................81
Creating a system collection..............................................................................................................81
Glossary....................................................................................................83
Index.........................................................................................................85
6
Table of Contents
List of Tables
1-1
1-2
1-3
3-1
3-2
3-3
3-4
3-5
3-6
A-1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
A-10
B-1
Virtual machine host icons displayed in the VM column........................................................................12
Virtual machine guest icons displayed in the VM column......................................................................13
vCenter Server status icons displayed in the VM column.......................................................................13
vCenter Server status icons...............................................................................................................17
Icons and tasks...............................................................................................................................23
Supported Insight Control virtual machine management features in various virtualization layers.................24
Supported data transfer features in various virtualization layers.............................................................24
Supported template features in various virtualization layers...................................................................25
Supported backup features in various virtualization layers.....................................................................25
Virtual Machine Management events.................................................................................................66
ConfigureVirtual MachineRegister Virtual Machine .............................................................................67
Deploy Virtual Machine Copy Virtual Machine ..................................................................................68
Deploy Virtual Machine Move Virtual Machine ..................................................................................69
Deploy Virtual Machine Handle VM host Prefailure Events ...................................................................70
Deploy Virtual Machine Backups Create Virtual Machine Backup .........................................................71
Deploy Virtual Machine Backups Restore Last Virtual Machine Backup ..................................................72
Configure Virtual Machine Unregister Virtual Machine Host .................................................................73
Configure Virtual Machine Set Alternate Virtual Machine Host .............................................................74
Configure Virtual Machine Set Performance Thresholds .....................................................................75
vCenter and VMware ESX Server host events......................................................................................77
7
8
About this document
Intended audience
This document is intended to be used by technical professionals who will be using HP Insight Control virtual
machine management.
Related documents
For more information about HP Insight Control virtual machine management, see:
•
http://www.hp.com/go/insightcontrol/docs
•
http://www.hp.com/go/vmmanage
•
HP Insight Software Getting Started Guide
•
HP Insight Software Installation and Configuration Guide
•
HP Insight Software Preinstallation Worksheet
•
HP Insight Software Quick Installation Guide
•
HP Insight Control Support Matrix
•
HP Insight Software Release Notes
For additional information about HP SIM, see:
•
http://www.hp.com/go/hpsim
•
HP Systems Insight Manager User Guide
•
HP Systems Insight Manager Help Guide
HP encourages your comments
Your comments and suggestions regarding product features will help us develop future editions of Insight
Control virtual machine management. For contact information, see chapter 5.
Intended audience
9
10
1 Introduction
HP Insight Control virtual machine management
HP Insight Control virtual machine management adds virtual machine management capability within
HP Systems Insight Manager (HP SIM) 6.0 or later. Insight Control virtual machine management provides
the following benefits:
•
Integration with the HP SIM console to manage the virtual machine environment
•
VMware, Citrix XenServer, Microsoft Hyper-V server, and Xen on SUSE Linux Enterprise Server (SLES)
and Red Hat Enterprise Linux (RHEL) supported from a single management software
•
Reduced cost and complexity in server consolidation projects
•
Faster response times to changing business demands
Insight Control virtual machine management provides tracking, monitoring, and control functions for organizing
an effective virtualized environment. HP leverages key industry alliances to provide best-in-class management
capability across most virtualization software platforms and industry standard servers.
Infrastructure
Insight Control virtual machine management is integrated completely within HP SIM to provide ease of use,
installation, and maintenance. All requirements and practices for operation of HP SIM must be observed for
Insight Control virtual machine management.
For more information about VMware ESX Server, see http://www.hp.com/go/vmware. For more information
about Citrix XenServer, see http://www.hp.com/go/citrix..For more information about requirements for
and using HP SIM, see the Managing Microsoft Windows Server 2008 Hyper-V with HP Insight Software
white paper at http://h18004.www1.hp.com/products/servers/software/microsoft/virtualization.
Insight Control virtual machine management includes the following components, which you install and set
up during software installation:
•
Insight Control virtual machine management—Installed on the HP SIM Central Management Server
(CMS). Provides access to the virtual machine monitoring and control functions, accessible locally or
remotely using industry standard web browsers.
•
Agent-less Insight Control virtual machine management—Includes VMware ESXi Server 3.0x, 3.5, and
4.0, VMware ESX 3.5 and 4.0, Citrix XenServer, Xen on SLES, Xen on RHEL, and Microsoft Hyper-V
server.
HP Insight Control virtual machine management
11
HP Systems Insight Manager console integration
Insight Control virtual machine management installs and runs on the HP SIM CMS. After you install Insight
Control virtual machine management, the VM column appears on the HP SIM console, enabling you to view
the status of virtual machine hosts and guests.
The association between virtual machine hosts and guests appears in the System(s) list. To view additional
details about virtual machine hosts and guests, in the System Name column, click an entry.
The color-coded icons listed in the following tables indicate the status of the virtual machine hosts and guests.
Table 1-1 Virtual machine host icons displayed in the VM column
Icon
Status
The virtual machine host is licensed and is communicating with Insight Control virtual machine management.
The virtual machine host is licensed but is not communicating with Insight Control virtual machine management.
The virtual machine host is licensed but is not currently monitored by Insight Control virtual machine management.
The virtual machine host is registered with Insight Control virtual machine management but is not licensed.
The virtual machine host is not registered with Insight Control virtual machine management.
12
Introduction
Table 1-2 Virtual machine guest icons displayed in the VM column
Icon
Status
The virtual machine guest is associated with a licensed virtual machine host, and the guest is started.
The virtual machine guest is associated with a licensed virtual machine host, but the host is not communicating with
Insight Control virtual machine management.
The virtual machine guest is in a state that requires user attention.
The virtual machine guest is associated with a licensed virtual machine host, but the guest is not started.
The virtual machine guest is not associated with a licensed virtual machine host.
The VM column also displays vCenter Server status. To navigate to the vCenter Server credentials user
interface, select either of the following:
•
Options→VMware vCenter Settings.
•
Options→Discovery, and then select Configure vCenter settings.
Table 1-3 vCenter Server status icons displayed in the VM column
Icon
Status
The vCenter Server credentials were set. However, currently Insight Control virtual machine management is unable to
connect to the vCenter Server because the service is stopped or the credentials have changed.
The vCenter Server credentials are set and Insight Control virtual machine management can connect to the vCenter
Server.
To display additional information for the system, click an icon.
Agentless Management
Insight Control virtual machine management (6.0) is completely agentless and no longer requires deploying
an agent to manage the ESX 3.0.x and ESX 3.5 hosts. If you are upgrading an existing version of virtual
machine management, then HP recommends stopping the virtual machine management agents that were
deployed earlier on the ESX hosts.from the setup.
NOTE: Refer the “Migrating virtual machine guest templates and backups” section before stopping the
virtual machine management agents. All templates and backups that were created using previous versions
of Insight Control virtual machine management must be converted to templates and backups compatible with
Insight Control virtual machine management 6.0. These conversions require older Insight Control virtual
machine management Agents to be running on the managed nodes.
To stop the virtual machine management agents, perform the following steps:
•
Verify whether the hpvmmcntsvc service is running on the ESX host by executing the following command
on the ESX host console: service hpvmmcntsvc status.
•
If the hpvmmcntsvc VMM service is running, then stop the service by executing the following command:
service hpvmmcntsvc stop.
Agentless Management
13
14
2 HP Insight Control virtual machine management licensing
Licensing HP Insight Control virtual machine management through the
Insight Control license manager
NOTE:
Insight Control virtual machine management 6.0 works only with HP SIM 6.0.
HP Insight Control virtual machine management (previously known as HP ProLiant Essentials Virtual Machine
Management Pack) can be installed with HP Systems Insight Software (HP SIM) 6.0.
To add or deploy license keys, you must have HP SIM administrative rights.
The standard procedure for licensing Insight Control virtual machine management is to purchase and apply
HP Insight Control suite licenses. For more information or to purchase licenses, see http://www.hp.com/go/
insightcontrol.
For more information, see the HP Insight Software V6.0 Getting Started Guide.
Licensing standalone Insight Control virtual machine management
Insight Control virtual machine management 6.0 works only with HP SIM 6.0.
To add or deploy license keys, you must have HP SIM administrative rights.
The standard procedure for licensing Insight Control virtual machine management is to purchase and apply
HP Insight Software licenses. For more information about acquiring Insight Software licenses, see the HP
Insight Software Installation and Configuration Guide.
If you attempt to license a server or UUID that does not have the correct serial number, then the licensing
process might not succeed. To verify the license key is not consumed, select Deploy→License
Manager→Manage Licenses. The host is licensed only when a valid serial number or UUID is detected
by HP SIM and Insight Control virtual machine management.
Adding standalone licenses
HP does not sell Insight Control virtual machine management standalone licenses. If your licenses were
purchased earlier and remain valid, you can add the the licenses.
1.
2.
3.
4.
5.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Click Add Licenses.... The Add License: section appears.
Enter one of the following:
•
The key string by typing it into the five fields as individual characters (five per field). The cursor
advances to the next field when the current field is full as you enter the key code starting from the
left-most box.
•
The key by pasting the entire key into one of the five input fields. For example, if you received a
key as text in an e-mail.
Click Process. The Key details: page appears.
Click Add Licenses Now to add the new licenses to the database. If the licenses are added successfully,
they are listed in the Product License Information section. An error message appears if the key is
invalid, and that license information is not added to the database.
If the license addition is successful, a new page appears displaying the product the key belongs to.
The table is refreshed with the newly added license row selected.
6.
Click Back if the licenses displayed is not the product license you wanted added. The Add License
section appears.
Licensing HP Insight Control virtual machine management through the Insight Control license manager
15
Applying standalone licenses
1.
2.
3.
4.
To access License Manager, select Deploy→License Manager.... The Product License Information
table appears.
Select a product, and then click Manage Licenses... The Manage License page appears.
Select the License Category you want to assign, and then click Assign License(s).... The Assign
Licenses section appears.
Select target systems, and then click Assign License Now.
NOTE:
You can hold the SHIFT key to select multiple systems.
NOTE: A system presently or previously licensed with a demo key may not be re-licensed with another
demo key.
If a selected product has not been registered with License Manager, the following message is displayed:
License Manager cannot process licenses for the selected product for one of two possible reasons:
For products where licensing information is managed by Systems Insight Manager, the Assigning
Licenses page appears. Select one or more systems from this list and click Assign License Now. The
page refreshes and shows the updated license status. Select additional systems to make more assignments,
or reselect License Manager to refresh the page.
For products that require the license to be delivered to the actual target, the License Assignment
Results table appears and reports the status of the assignment process for each target. There might
be a delay in sending license data to some targets. You can continue with other Systems Insight Manager
activities during the license assignment process.
5.
16
To remove an assigned license, reselect Manage Licenses. The assigned licenses appear. Select the
license category you want to remove, and then select Un-Assign Licenses.
HP Insight Control virtual machine management licensing
3 Using HP Insight Control virtual machine management
This chapter provides an overview of server virtualization management using the Insight Control virtual
machine management feature of Insight Control Environment.
You can perform all Insight Control virtual machine management operations with either operator or
administrator rights.
Registering virtual machine hosts
Configuring VMware vCenter servers
Insight Control 6.0 supports multiple VMware vCenter Servers. The VMware vCenter credentials are required
to register VMware ESX hosts in the vCenter Server with Insight Control 6.0. HP recommends providing the
credentials of the user who is part of the Administrator role in vCenter Server.
To navigate to the VMware vCenter Server credentials user interface, select either of the following:
•
Click Options, then VMware vCenter Settings.
•
Click Optionsthen Discovery, then select select Configure vCenter settings.
To configure a new VMware vCenter, click New and provide the user credentials. Enter the credentials that
were configured on the VMware vCenter Server Web Service page during the VMware vCenter Server
installation.
NOTE: System Name/Address is either the VMware vCenter server hostname or IP address and port is
the VMware vCenter Server web service port. The default port is 443. The User Name follows the domain
account format – DOMAIN/administrator.
When you click OK, the new VMware vCenter credentials are set and connection status is displayed.
Table 3-1 vCenter Server status icons
Icon
Status
Registering virtual machine hosts
17
The vCenter Server credentials were set. However, currently Insight Control virtual machine management is unable to
connect to the vCenter Server because the service is stopped or the credentials have changed.
The vCenter Server credentials are set and Insight Control virtual machine management can connect to the vCenter Server.
To display additional information for the system, click an icon.
Configuring the xapi port for Citrix XenServer
Insight Control virtual machine management provides a configurable parameter called CitrixXapisslport.
This parameter keeps the port that Insight Control virtual machine management uses to control or manage
the Citrix XenServer. The default port is 443.
Configuring WMI Mapper proxy server settings for Microsoft Hyper-V
server
Insight Control virtual machine management uses WMI Mapper proxy bundled with HP SIM to manage the
Microsoft Hyper-V server virtualization layer. If the WMI Mapper proxy is installed on the server where
HP SIM 6.0 is installed, no additional configuration is required in Insight Control virtual machine management.
If the WMI Mapper proxy is installed outside the CMS, add the following configuration entry in the Insight
Control virtual machine management configuration file located at <HP Insight Control virtual
machine management installation directory on CMS>/bin/hpvmm.conf for Insight Control
virtual machine management to manage Microsoft Hyper-V servers.
WMIProxyServer = <IP address of the server where WMI Mapper proxy is installed>
By default, the WMI Mapper proxy port used by Insight Control virtual machine management is 5989. If
the WMI Mapper proxy service is run on a different port, add the following configuration entry in the Insight
Control virtual machine management configuration file located at <HP Insight Control virtual
machine management installation directory on CMS>/bin/hpvmm.conf.
WMIProxyPort = <Proxy port number>
After any changes to the hpvmm.conf file, for the changes to take effect, you must restart the Insight Control
virtual machine management service on the CMS.
You can set the WMI Mapper proxy for the CMS through the HP SIM user interface by selecting
Options→Protocol Settings→WMI Mapper Proxy. You can also add the system name.
Configuring Insight Control virtual machine management on a Microsoft
Cluster Server
Insight Control virtual machine management supports high availability on a Microsoft Cluster Server. HP SIM
and Insight Control virtual machine management must be installed on the cluster nodes. For more information,
see the white paper at http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/
deploying_MSCSclusters.pdf.
Unregistering virtual machine hosts
CAUTION: Unregistering a virtual machine host permanently removes all information from Insight Control
virtual machine management database, including backup information.
To unregister the virtual machine host:
1.
2.
3.
4.
18
On the HP SIM All Systems page, select the virtual machine host.
From the HP SIM menu, select Configure→Virtual Machine→Unregister Virtual Machine Host.
Verify that the correct target host appears in the list. To add targets click Add Targets, or to remove
targets, click Remove Targets, and then click Next.
To unregister the host immediately, click Run Now, and type Yes.
Using HP Insight Control virtual machine management
Updating the HP SIM certificate on CMS
Insight Control virtual machine management uses a Systems Insight Manager certificate for all its
communication with Systems Insight Manager. Should changes be made to the Systems Insight Manager
certificate, you must restart the Insight Control virtual machine management service to use the updated
certificate.
Insight Control virtual machine management interface overview
Insight Control virtual machine management provides central management and control for virtual machines
hosted on Microsoft Hyper-V server, VMware ESX Server, Citrix XenServer, or Xen on RHEL or SLES.
Insight Control virtual machine management detects virtual machine status changes initiated by other supported
virtualization management consoles. The System Status icons on the HP SIM System Page indicate these
status changes. To access the System Page, click the system name in the HP SIM console. If Microsoft
Hyper-V server is used, the Launch SCVMM button appears. If VMware ESX Server is used, the Launch
vCenter button appears.
The left frame of the HP SIM console displays a node navigational tree. A list of the virtual machine hosts
and their virtual machine guests appears in the Systems→Shared→Systems by Type directory.
To display all virtual machine hosts and guests managed by Insight Control virtual machine management in
the HP SIM console, expand the Systems→Shared→Systems by Type directory in the navigational tree,
and then click All Virtual Machine Hosts or All Virtual Machines.
Virtual machine host
Depending on the host configuration, additional details might appear in addition to those listed. To display
the following information for the host, click a virtual machine host in the HP SIM console, and then click the
System tab.
If Microsoft Microsoft Hyper-V server is used, then the Launch SCVMM button appears.
Updating the HP SIM certificate on CMS
19
•
•
•
Virtual Machine Host Configuration Details
•
Virtualization—The type of virtualization software installed
•
Alternate Host for—The alternate host information, only if it is set
•
Storage details—The disk space information
Virtual machines—A list of virtual machines associated with the virtual machine host
•
Status—Icon describing the status of the virtual machine
•
State—Text describing the state of the virtual machine
•
VM name—The name of the virtual machine
•
System IP address—The IP address of the virtual machine
•
System OS name—The operating system name of the virtual machine
•
Legend—Link that displays the VMM Status Icon Legend window
•
VM control—Controls that enable you to launch the Remote Desktop and the Remote Console, as
well as start, stop, reset, and pause the virtual machine. For Microsoft Hyper-V server, the Launch
SCVMM button appears. For VMware ESX Server, the Launch vCenter button appears. Click the
appropriate button to launch the hypervisor-specific management console.
Disk partitions—A list of how the disk is separated, its capacity, and percentages of used and available
space
NOTE: For Microsoft Hyper-V server, the Disk name column shows the volume GUID assigned to the
disk volume that has no drive letter.
NOTE: For Citrix XenServer, a forward slash (/) is added at the beginning of the storage repository
name in the Disk partition column.
NOTE: For Xen on Red Hat Enterprise Linux or SLES, the value shown under the %Used column reports
the actual usable space in the machine.
•
20
vCenter Server information—Displays the hierarchy for the host as seen in vCenter Server for VMware
ESX server.
Using HP Insight Control virtual machine management
Virtual machine guest
Depending on the guest configuration, additional details might appear. To display the following configuration
information for the host or guest, click a virtual machine guest in the HP SIM console, and then click the
System tab. Information appears only for the virtual machine guests that are fully configured.
•
Virtual machine controls—Controls that enable you to launch the Remote Desktop/Remote VNC and
the VM Console, as well as start, stop, reset, and pause virtual machines.
For Microsoft Hyper-V server, the Launch SCVMM button appears. For VMware ESX Server, the Launch
vCenter button appears. Press the appropriate button to launch the hypervisor-specific management
console.
•
Virtual machine configuration details
•
VM host—The system name of the virtual machine host
•
Virtualization—The virtualization technology installed on the virtual machine host
•
Alternate host—The failover host set by the user if it is set for the VM
•
Configuration file—The name and location of the configuration file
•
Configuration folder—The name and location of the configuration folder
•
Memory—The amount of memory on the virtual machine host
•
Virtual NIC—The type of virtual disk displaying the location, mode, and capacity
•
Virtual disk—The type of virtual disk
•
CD/DVD ROM—Details about the drive
When the host CD/DVD drive is selected while adding a CD/DVD drive to a Microsoft Hyper-V
server virtual machine, a lengthy string (for example,
IDE\CDROMTEAC_DW-224E-V________C.CA__\53C5E1CB00.0.0) might appear in the
Virtual Machine configuration details. This string varies based on the type of CD/DVD drive
attached. This string does not affect functionality.
•
•
Floppy drive—Identity of the floppy drive
Virtual machine backups—Information about the backups for the virtual machine
•
Source host—The host source name
•
Source path—The source path
•
Configuration file—The configuration file name
Virtual machine guest
21
•
•
Virtualization layer—The virtualization technology installed on the virtual machine host
•
Backup repository—The virtual machine host where the backup locates
•
Backup repository location—The physical location of the backup repository
•
Date—The date of the last backup
Virtual machine disk partition—A list of virtual machines controlled by the host
•
Disk name—The name of the disk
•
Capacity—The capacity of the disk
•
%Used—The percentage of disk space used
•
%Available—The percentage of disk available space used
NOTE: For Citrix XenServer and VMware ESX, Partition, Format, and Type information might not be
available.
For Citrix XenServer %Used and %Available information might not be available.
▲
Backup details—Details about the most recent backup of the virtual machine, such as source host IP
address, source path, configuration file, virtualization layer, and backup repository
To view completed events involving the selected host or guest, click the Events tab.
Configured and unconfigured virtual machines
NOTE:
This section applies only to Citrix XenServer.
Configured and unconfigured virtual machine hosts can appear in HP SIM CMS and have the following
attributes.
Configured
Configured virtual machines meet at least one of the following criteria:
•
Proper providers have been installed and the credentials are saved in HP SIM.
•
HP SIM can discover and identify the guest operating system running inside the virtual machine host
and with the virtual machine serial number.
•
Proper virtual machine host to virtual machine guest association appears.
•
Full Insight Control virtual machine management functionality is available.
•
Turning off the virtual machine host does not change its status as a configured virtual machine.
•
If the virtual machine host is deleted using the HP SIM interface, then the virtual machine host becomes
unconfigured until HP SIM rediscovers it.
Unconfigured
Unconfigured virtual machines meet at least one of the following criteria:
•
Have never been powered on.
•
Have no guest operating system installed.
•
Do not have proper providers installed.
•
Have credentials unknown to HP SIM.
Unconfigured virtual machines have the following limitations:
22
•
Permissions cannot be assigned to them.
•
Schedules cannot be defined.
•
Tools such as creating virtual machine backups, setting performance alerts, setting failover host, or
moving virtual machines are limited.
Using HP Insight Control virtual machine management
Unconfigured virtual machines can create templates.
Using Insight Control virtual machine management controls and tools
You can perform various tasks using Insight Control virtual machine management controls, available from
the HP SIM host or virtual machine System Page, as described in the following sections.
NOTE: The time to complete a virtual machine operation that involves file transfers takes longer when
Network Attached Storage (NAS) volumes are used because Insight Control virtual machine management
shares a network connection with NAS. Be sure separate networks are set up for Insight Control virtual
machine management and NAS.
The following Insight Control virtual machine management tasks appear on the HP SIM host or guest System
Page. Use these tasks to start, resume, shut down, stop, pause, reset, or restart licensed virtual machine
guests.
Table 3-2 Icons and tasks
Icon
Function
Start/resume
Shutdown/stop
Pause
Reset/restart
The following tasks can be initiated from the HP SIM toolbar:
•
Starting or resuming a virtual machine guest
•
Shutting down or stopping a virtual machine guest
•
Suspending or pausing a virtual machine guest
•
Resetting or restarting a virtual machine guest
•
Copying a virtual machine guest
•
Moving a virtual machine guest
•
Creating a virtual machine guest template
•
Deploying a virtual machine guest template
•
Migrating virtual machine guest templates and backups
•
Deleting a virtual machine guest template
•
Creating a virtual machine guest backup
•
Restoring a virtual machine guest backup
•
Restoring the most recent virtual machine guest backup
•
Recovering virtual machines of a failed host on a VMware ESX Server, Citrix XenServer or Microsoft
Hyper-V R2 server
•
Setting the alternate virtual machine host
•
Removing an alternate virtual machine host on a VMware ESX Server, Citrix XenServer, or Microsoft
Hyper-V R2 server
•
Setting or removing the performance threshold
•
Handling prefailure events
•
???
•
Unregistering virtual machine hosts
Using Insight Control virtual machine management controls and tools
23
•
vCenter Server information
•
vCenter and VMware ESX Server host events
The following tasks can be initiated for a virtual machine from the VM Host System or VM Guest System
page:
•
Launching Remote Console
•
Launching Remote Desktop
•
Launching vCenter
•
Launching SCVMM
The following tasks can be initiated from the VM Host System page:
•
Launching SCVMM
•
Launching vCenter
The following are miscellaneous tasks:
▲
Updating the HP SIM certificate on CMS
The following tables list supported features for various virtualization layers.
Table 3-3 Supported Insight Control virtual machine management features in various virtualization layers
Features
VMware ESX
3.0
"HP
HP
integrated
integrated
ESXi/VMware ESXi/VMware
ESX 3.5
ESX 4.0
Virtual
machine host
registration
✓
✓
Virtual
machine
discovery
✓
✓
Microsoft
Hyper-V R1
server
Microsoft
Hyper-V R2
server
HP
integrated
XenServer/Citrix
XenServer
Xen
distribution
on RHEL
Xen
distribution on
SLES
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
Table 3-4 Supported data transfer features in various virtualization layers
Data transfer VMware ESX
features
3.0
24
"HP
HP
integrated
integrated
ESXi/VMware
VMware
ESX 3.5
ESXi/VMware
ESX 4.0
Microsoft
Hyper-V R1
server
Microsoft
Hyper-V R2
server
HP
integrated
Citrix
XenServer/Citrix
XenServer
Xen
distribution
on RHEL
Xen
distribution on
SLES
Copy virtual
machine
✓
✓
✓
✓
✓
✓
✓
✓
Move virtual
machine
✓
✓
✓
✓
✓
✓
✓
✓
SAN move
virtual
machine
✓
✓
✓
X
✓
✓
X
X
Live move
virtual
machine
✓
✓
✓
X
✓
✓
X
X
Quick move
virtual
machine
—
—
—
✓
✓
—
—
—
Using HP Insight Control virtual machine management
Table 3-5 Supported template features in various virtualization layers
Template
features
VMware ESX
3.0
"HP
HP
integrated
integrated
ESXi/VMware
VMware
ESX 3.5
ESXi/VMware
ESX 4.0
Microsoft
Hyper-V R1
server
Microsoft
Hyper-V R2
server
HP
integrated
Citrix
XenServer/Citrix
XenServer
Xen
distribution
on RHEL
Xen
distribution on
SLES
Create
template
from virtual
machine
✓
✓
✓
✓
✓
✓
X
X
Deploy
template as
virtual
machine
✓
✓
✓
✓
✓
✓
X
X
Table 3-6 Supported backup features in various virtualization layers
Backup
feature
VMware ESX
3.0
"HP
HP
integrated
integrated
ESXi/VMware
VMware
ESX 3.5
ESXi/VMware
ESX4.0
Microsoft
Hyper-V R1
server
Microsoft
Hyper-V R2
server
HP
integrated
Citrix
XenServer/Citrix
XenServer
Xen
distribution
on RHEL
Xen
distribution on
SLES
Create
backup for
virtual
machine
✓
✓
✓
✓
✓
✓
X
X
Restore
backup for
virtual
machine
✓
✓
✓
✓
✓
✓
X
X
Performance
metrics
collection
✓
✓
✓
✓
✓
✓
X
X
Set
performance
threshold
✓
✓
✓
✓
✓
✓
X
X
Events
collection
X
✓
✓
X
X
✓
X
X
Failed host
recovery
(FHR)
✓
✓
✓
X
✓
✓
X
X
Prefailure
alert
handling
(PFA)
X
✓
✓
X
✓
✓
X
X
Upgrading a
virtual
machine
guest
template
(applicable
for VMware
ESX only)
✓
✓
✓
X
X
X
X
X
Deleting a
virtual
machine
guest
template
✓
✓
✓
✓
✓
✓
X
X
Migrating a
virtual
machine
guest
backup
✓
✓
✓
X
X
X
X
X
Using Insight Control virtual machine management controls and tools
25
Starting or resuming a virtual machine guest
You can start or resume a virtual machine guest if it is stopped, shut down, or paused. Starting a virtual
machine might take a few minutes.
1.
2.
3.
4.
On the HP SIM All Systems page, select the virtual machine guest to be started.
From the HP SIM toolbar, select Tools→Virtual Machine→Start Virtual Machine.
Verify the target system, and then click Next. Virtual machine source information appears.
Verify the details, and then click Schedule or Run Now.
To start or resume a virtual machine guest from the virtual machine host or guest System page:
1.
2.
3.
Click the Start icon ( ).
Verify the target system, and then click OK when prompted.
If the virtual machine guest is stopped or paused, then you can start or resume the guest by clicking the
Start icon.
When the power-up process is complete, the status updates to Normal ( ). The Start icon is disabled, and
the Shutdown/Stop, Pause, and Reset icons are enabled.
If a virtual machine guest does not respond during the start process, Insight Control virtual machine
management displays User Interaction Required, and the status updates to Major ( ).
Shutting down or stopping a virtual machine guest
You can shut down a virtual machine guest only if it is currently powered up and hypervisor-specific guest
tools are installed. Microsoft Hyper-V Integration Components, VMware Tools, or XenServer Tools for Citrix
XenServer are installed on the virtual machine guest. Integration Components for Microsoft Hyper-V, VMware
Tools for VMware ESX, or XenServer Tools for Citrix XenServer.
When using a Citrix XenServer in a HA-enabled resource pool, unprotect the virtual machine host before
stopping or suspending the virtual machine guest.
If hypervisor-specific guest tools are installed, an additional prompt appears.
1.
2.
3.
Select Stop VM or Shutdown VM when prompted.
When you select Stop VM, the virtual machine guest powers down immediately without saving the
current state.
When you select Shutdown VM, the virtual machine operating system shuts down, and the virtual
machine guest powers down.
To shut down or stop a virtual machine guest:
1.
2.
3.
4.
On the HP SIM All Systems page, select the virtual machine guest.
From the HP SIM toolbar, select Tools→Virtual Machine→Stop Virtual Machine.
Verify the target system, and then click Next. Virtual machine source information appears.
Verify the details, and then click Schedule or Run Now.
CAUTION:
If you shut down or stop a virtual machine guest, unsaved data is lost.
To shut down or stop a virtual machine guest from the virtual machine host or guest System page:
1.
2.
Click the Shutdown/Stop icon ( ).
To confirm, click OK when prompted.
When the shutdown or stop process is complete, the status updates to Disabled ( ). The Stop, Pause, and
Reset icons are disabled, and the Start icon is enabled.
NOTE: Protected virtual machines in a HA-enabled resource pool cannot be stopped or suspended from
Insight Control virtual machine management 6.0.
Suspending or pausing a virtual machine guest
You can suspend a virtual machine guest only if it is currently powered up and running.
When you select Pause VM, the virtual machine execution is suspended, but the virtual machine state in
the virtual machine host memory is retained.
26
Using HP Insight Control virtual machine management
When using a Citrix XenServer in a HA-enabled resource pool, unprotect the virtual machine host before
stopping or suspending the virtual machine guest.
To suspend a virtual machine guest:
1.
2.
3.
4.
On the HP SIM All Systems page, select the virtual machine guest to be suspended or paused.
From the HP SIM toolbar, select Tools→Virtual Machine→Suspend Virtual Machine.
Verify the target system, and then click Next. Virtual machine source information appears.
Verify the details, and then click Schedule or Run Now.
To suspend a virtual machine guest from the virtual machine host or guest System page:
1.
2.
Click the Pause icon ( ).
Verify the target system, and then click OK when prompted.
When the suspend-to-disk or pause process is complete, the status updates to Disabled ( ). The Start icon
is enabled, and the Shutdown/Stop, Pause, and Reset icons are disabled.
NOTE: When an Citrix XenServer virtual machine is in a suspended state you cannot perform the copy,
move, create template, and backup virtual machine operations.
Suspending a virtual machine guest is not supported for hosts using Xen on RHEL or Xen on SLES.
Resetting or restarting a virtual machine guest
A virtual machine guest can be restarted only if it is currently powered up and hypervisor-specific guest tools
are installed (Microsoft Hyper-V Integration Components, VMware Tools for VMware ESX, or XenServer tools
for Citrix XenServer).
For the Microsoft Hyper-V server virtual machine guest, the Hyper-V Integration Components are installed.
Restarting a virtual machine guest is not supported for for Xen on RHEL and Xen on SLES.
When you select Reset, the virtual machine guest powers down and then powers up. When you select
Restart, the virtual machine operating system shuts down and powers down, and the virtual machine guest
powers up.
To reset or restart a virtual machine guest:
1.
2.
3.
4.
On the HP SIM All Systems page, select the virtual machine guest to be reset.
From the HP SIM toolbar, select Tools→Virtual Machine→Restart Virtual Machine.
Verify the target system, and then click Next. Virtual machine source information appears.
Verify the details, and then click Schedule or Run Now.
CAUTION:
If you select Reset, unsaved data is lost.
To reset or restart a virtual machine guest from the virtual machine host or guest System page:
1.
2.
Click the Reset/Restart icon ( ).
Verify the target system, and then click OK when prompted.
When the reset or restart process is complete, the status updates to Normal ( ). The Start icon is disabled,
and the Shutdown/Stop, Pause, and Reset icons are enabled.
Launching remote access
Insight Control virtual machine management provides direct access to the virtualization technology interface.
The following sections provide detailed information on the type of virtualization technology installed,
depending on the virtual machine host and the operating system installed on the virtual machine guest.
Launching Remote Console
For VMware ESX, you must install VMware Virtual Machine Console on the client server.
Using Insight Control virtual machine management controls and tools
27
For VMware ESX, Insight Control virtual machine management directs you to the VMware ESX Server
management website so that you can download VMware Virtual Infrastructure Client.
Launching Remote Desktop
The Remote Desktop for a virtual machine can be launched from the Virtual Machines section of the VM Host
System page, or the VM Control section of the VM Guest System page in HP SIM.
The Remote Desktop option is enabled for a virtual machine guest if:
28
•
The guest has a supporting operating system installed.
•
The virtual machine has been identified in HP SIM with a valid IP address.
•
The virtual machine is running.
Using HP Insight Control virtual machine management
Launching SCVMM
IMPORTANT:
To use the Launch SCVMM feature, you must be using a 64-bit browser.
You can access the System Center Virtual Machine Manager (SCVMM) client from the Virtual Machine
Host or Guest System page within Insight Control instead of launching SCVMM separately.
NOTE:
Launch SCVMM is applicable for the Microsoft Hyper-V server.
Microsoft Hyper-V Server Host System page
When using a Microsoft Hyper-V Server, from the Host System page, click Launch SCVMM.
Microsoft Hyper-V Server Guest System page
When using a Microsoft Hyper-V Server, from the Guest System page, click Launch SCVMM.
Launching VC
You can access the vCenter (VC) client from the Virtual Machine Host or System Page within Insight Control
virtual machine management instead of launching VC separately.
Launching VC
29
VMware ESX Server Host System page
When using a VMware ESX Server, from the Host System page, click Launch vCenter.
vCenter Server information
The vCenter Server Information displays the hierarchy for the host as it appears in vCenter Server. This feature
is supported only on registered VMware ESX hosts and their virtual machines. To view information, vCenter
Server must be running and vCenter Server credentials must be available in Insight Control virtual machine
management.
Copying a virtual machine guest
You can copy virtual machine guests from an existing virtual machine host to a new host when the same
virtualization technology exists on both the source and target host servers.
Before you can copy a virtual machine guest, you must stop or pause it.
30
Using HP Insight Control virtual machine management
1.
2.
3.
4.
On the HP SIM All Systems page, select the virtual machine guest to be copied.
From the HP SIM toolbar menu, select Deploy→Virtual Machine→Copy Virtual Machine.
Verify the target system, and then click Next. Virtual machine source information appears.
From the list of authorized registered hosts, select the target virtual machine host, and then click Next.
NOTE: For virtual machines using VMware ESX, the default target location name is entered automatically
when you enter the name of the target virtual machine host.
5.
6.
Review the resources of all available hosts, select an appropriate target virtual machine host, and then
click Next.
Specify a name for the target virtual machine guest being copied or accept the default selection, and
specify the target path for the virtual machine guest and the disk. The target folder on the virtual machine
host must be empty.
Ensure that a unque name is given for the target virtual machine. If virtual machine disks or configuration
files exist with the designated name, then an error occurs, and the copy operation fails.
NOTE: For volumes that have no drive letter assigned on the Microsoft Hyper-V server virtual machine
host, use the volume GUID path for the target path.
7.
8.
9.
Verify that adequate available disk space exists on the target virtual machine host to accommodate the
total transport volume, which consists of several disks and configuration files.
Click Next.
Verify the displayed details of the copy operation, and then click Run Now.
When the copy is complete, the new virtual machine guest is registered to the target virtual machine
host. The virtual machine guest status is Disabled ( ). Start the copied virtual machine guest using Insight
Control virtual machine management as necessary, and then discover the virtual machine guest in HP SIM
.
10. (Optional) You might have to reconfigure the virtual network connections on the new virtual machine
guest. You also might have to change the host name of the copied virtual machine guest.
The Task Results page for a virtual machine move or copy involving either Xen on RHEL or Xen on SLES does
not display the remaining time for operation completion.
SUSE Linux scenario
By default, SUSE Linux implements persistent device names for network devices, which associates a specific
MAC address to a Linux network device. This can be observed by the names and contents of the
/etc/sysconfig/network/ifcfg-eth-* files. This results in a failed network configuration when a
SUSE Linux virtual machine guest is assigned a different MAC address.
Since a virtual machine copy changes the UUID and the MAC address, copying a SUSE Linux virtual machine
results in networking issues , because these persistent network names are no longer valid and the new devices
are not automatically enabled.
Novell has identified this as an issue and provided a solution document at http://www.novell.com/support/
documentLink.do?externalID=3048119.
To address this issue when copying SUSE Linux virtual machine guests to any virtual machine guest before
copying the virtual machine guest, perform the following:
1.
2.
3.
Clear the udev configuration for the network devices.
Rename the Ethernet configuration files.
Change network configurations to not use udev.
NOTE: Copy destinations for Linux Xen guests are limited based on the virtualization mode of the guest.
For fully-virtualized guests, only destination hosts with the same hardware virtualization modes as the source
Launching VC
31
are listed. For para-virtualized guests, only destination hosts running the same kernel are listed. Note that
hardware virtualization must be enabled in the BIOS for some virtual machine hosts.
NOTE: Virtual machines in a paused state are not valid for the copy operation on VMware ESXi and Citrix
XenServer virtual machine hosts.
Moving a virtual machine guest
Moving virtual machine guests
Only virtual machine guests created using simple file storage can be moved.
You can move the virtual machines hosted on VMware ESX Server,VMware Server, Citrix XenServer, and
Microsoft Hyper-V server using the following options:
•
Move—The virtual disk is copied to the host. You must stop the virtual machine for this move operation
type.
•
SAN Move—The virtual disk is not copied to the target host. The target host accesses the virtual disks
using storage area network (SAN) connectivity. You must stop the virtual machine for this move operation
type. SAN Moves cannot be performed using Xen on RHEL or SLES.
SAN Move is also supported on Microsoft Hyper-V R2 servers.
•
Live Move—The powered-up virtual machine is moved using VMware VMotion Technology for VMware
ESX systems and Citrix XenMotion Technology for Citrix XenServer virtual machines. Live Move is also
supported on Microsoft Hyper-V R2 servers.
•
Quick Move—The Microsoft Hyper-V server virtual machine is moved using the Microsoft Quick Migration
technology. (Applicable only for Microsoft Hyper-V server.)
When performing a Live Move, if the CMS and vCenter Server are in different networks, a delay might occur
when the list of possible target hosts is created.
Other notes:
•
To minimize the occurrence of orphan managed systems, the name of the virtual machine in Citrix
XenServer host must be the same as the node name of the virtual machine discovered in CMS.
•
Insight Control virtual machine management supports Quick Move when a Microsoft Hyper-V server
virtual machine is configured for high availability (HA) in a Microsoft Hyper-V server failover cluster.
•
Insight Control virtual machine management supports SAN Move of virtual machines on a shared
storage in resource pool environments for Citrix XenServer.
To move a virtual machine guest:
1.
2.
3.
On the HP SIM All Systems page, select the virtual machine guest to be moved.
From the HP SIM toolbar, select Deploy→Virtual Machine→Move Virtual Machine.
Verify the source virtual machine, and then click Next.
If a quick move is initiated, a message appears indications to power down the virtual machine and
ensure it is HA enabled and part of the cluster before proceeding.
4.
32
Select the target virtual machine host from the list of authorized licensed hosts, and then click Next.
Using HP Insight Control virtual machine management
NOTE: For virtual machines using VMware ESX, you cannot set the target folder. The default name
and path are used.
If the selected virtual machine is associated with a VMware ESX Server and:
•
The virtual machine is currently running, a Live Move for VMware ESX Server using VMware
VMotion Technology is performed.
•
The virtual machine is stopped, SAN Move or Move appears in the Move Type column. If the
target host is in a SAN, a SAN Move can be performed.
A SAN move involving Microsoft Hyper-V servers must meet the following prerequisites:
•
The source and destination hosts must be Microsoft Hyper-V servers.
•
The virtual machine host can be in off, suspend, or pause state.
•
The virtual machine host must not be HA enabled.
•
The virtual machine configuration and .vhd files must be stored in cluster shared volumes.
•
The virtual machine host must not have an RDM disk attached to it.
To perform a Live Move, you must configure VMware vCenter Server settings. For more information,
see the "Configuring VMware vCenter Server" topic in the of the HP Insight Software Installation and
Configuration Guide.
A Live Move involving Microsoft Hyper-V servers must meet the following prerequisites:
5.
•
The source and destination virtual machine hosts must be Microsoft Hyper-V servers.
•
The virtual machine host must be HA enabled.
•
The virtual machine host must be running.
Specify a name for the target virtual machine guest or accept the default selection, and then specify the
target path for the virtual machine guest and the disk. The target folder on the virtual machine host must
be empty.
Microsoft requires that each virtual machine guest has a unique virtual machine name. If virtual machine
disks or configuration files exist with the designated name, then an error occurs, and the move operation
fails.
6.
7.
8.
Verify that adequate available disk space exists on the target virtual machine host to accommodate the
total transport volume, consisting of several disks and configuration files.
Click Next.
Verify the displayed details of the move operation, and then click Run Now.
When the move is complete, the new virtual machine guest is registered to the target virtual machine host.
The virtual machine guest status is Disabled ( ). Start the moved virtual machine guest using Insight Control
virtual machine management as necessary.
Insight Control virtual machine management does not delete virtual machine files after a move. For errors
that might occur after performing a move or SAN move, see the A virtual machine guest appears in VMware
vCenter Server multiple times topic in the Troubleshooting section. For errors that might occur after performing
a Live Move, see the Live Move fails after SAN move topic in the Troubleshooting section.
You might need to reconfigure the virtual network connections on the moved virtual machine guest.
The Task Results page for a virtual machine move or copy involving either Xen on RHEL or Xen on SLES does
not display the remaining time for operation completion.
NOTE: Moving a virtual machine or restoring a virtual machine from backup in Citrix XenServer will change
the virtual machine UUID, BIOS ID, and MAC address.
NOTE: Move destinations for Linux Xen guests are limited based on the virtualization mode of the guest.
For fully-virtualized guests, only destination hosts with the same hardware virtualization modes as the source
Launching VC
33
are listed. For para-virtualized guests, only destination hosts running the same kernel are listed. Note that
hardware virtualization must be enabled in the BIOS for some virtual machine hosts.
NOTE: For volumes that have no drive letter assigned on the Microsoft Hyper-V server virtual machine host,
use the volume GUID path for the target path.
NOTE:
Live Move is not supported on Xen on RHEL and XEN on SLES.
Creating a virtual machine guest template
NOTE: For virtual machines hosted on Citrix XenServer, VMware ESX, and Microsoft Hyper-V server, the
compress disk option and selective inclusion of disk option are not available.
NOTE:
For Xen on RHEL or SLES, you cannot perform the virtual machine guest template operation.
A template is an image of a complete virtual machine guest, including the operating system, configuration,
and all relevant virtual machine disk information needed to create and register a new virtual machine on a
host with the same virtualization technology. You can use any existing virtual machine guest on a licensed
host to create a template.
A template does not contain the serial number (UUID) and MAC address of the virtual machine guest that
creates the template. For VMware ESX Server machines, the template created will be VMware-native and is
visible in vCenter Server.
1.
2.
3.
4.
5.
6.
7.
Before you can create a template, you must stop or pause the virtual machine guest.
From the HP SIM toolbar, select Deploy→Virtual Machine→Templates→Create Virtual Machine
Template.
Verify all the virtual machines appear in the Select Source Virtual Machine section, then click Next.
Review the resources of the available hosts, select an appropriate target virtual machine host where the
template is to be stored, and then click Next.
Enter a name for the template or accept the default selection, and enter a description.
Select which disks to include in the template. You must select the operating system and boot disks. This
step is not valid for VMware ESX Server virtual machine hosts.
Specify the target path for the virtual machine template, and then click Next. The target folder on the
virtual machine must be empty.
After clicking Next, there is no option to select a disk. The disk selection is possible only when you are
entering the template name and its description.
8.
Verify the displayed details of the operation, and then click Run Now.
NOTE: For virtual machines hosted on Citrix XenServer, VMware ESX, and Microsoft Hyper-V server, the
compress disk option and selective inclusion of disk option are not available.
NOTE:
For Xen on RHEL or SLES, you cannot perform the virtual machine guest template operation.
Migrating virtual machine guest templates and backups
Insight Control virtual machine management 6.0 manages all flavors of VMware ESX hypervisor in agent-less
fashion. If you are upgrading from a previous version, all templates and backups that wre created using
previous versions of Insight Control virtual machine management must be converted to templates and backups
that are compatible with Insight Control virtual machine management 6.0.
Insight Control virtual machine management 6.0 uses native VMware templates. After an Insight Control
virtual machine management upgrade, you must convert all the older templates on VMware ESX virtual
machine hosts to VMware hypervisor-specific templates.
34
Using HP Insight Control virtual machine management
To make these conversions, your setup must meet the following prerequisites:
•
Template or backup migration on the VMM Agent-based VMware ESX virtual machine host requires
VMM Agents to be running on the managed nodes. Otherwise, you cannot perform a migration.
•
To migrate all the templates on the specified VMware ESX virtual machine host, the vCenter Server
credentials must be entered and the host must be associated with the vCenter Server.
•
Before migrating the template or backup on the VMM Agent-based virtual machine hosts, ensure that
enough space is available on the disk on the VMware ESX virtual machine host to decompress the
template or backup virtual disks.
Template or backup migration on the Insight Control virtual machine management Agent-based VMware
ESX virtual machine host requires older Insight Control virtual machine management Agents to be running
on the managed nodes. Otherwise, you cannot perform a migration.
To deploy the Insight Control virtual machine management certificate onto the Agent-based VMware ESX
virtual machine hosts, before performing either a template or backup migration.
1.
Click Deploy→Deploy Drivers, Firmware and Agents→Deploy VMM Agent Certificates – ESX
menu.
If the virtual machine host is a a VMware ESX host and is Agent-based, page 1 of this menu performs
a target verification.
2.
From page 2, click Run Now. The task results page displays the certificate deployment job results.
To perform the migration:
1.
2.
3.
4.
Select a VMware ESX host on which the migration is to be performed.
Depending on what you are migrating, select either of the following:
•
If you are migrating a template, from the HP SIM menu, select Deploy→Virtual
Machine→Templates→Upgrade Templates on ESX.
•
If you are migrating a backup, from the HP SIM menu, select Deploy→Virtual
Machine→Backups→Upgrade Backups on ESX.
Insight Control virtual machine management verifies that the virtual machine host is VMware ESX and
that it contains older templates or backups. To proceed, click Next.
Insight Control virtual machine management displays a list of available templates or backups to upgrade.
Select the templates or backups that you wish to upgrade, and then click Run Now. To see the job
results and log file links for each migration, see the task results page.
NOTE:
Migrating backups on Agent-less VMware ESX virtual machine hosts is not required.
Insight Control virtual machine management is agentless and does not require an agent to be deployed on
the VMware ESX 3.0.x and 3.5 virtual machine hosts. HP recommends that you stop any agents from the
setup by ensuring that the hpvmmct service is not running on the ESX hosts.
To verify that the service is running, execute the following command on the VMware ESX server console:
service hpvmmcntsvc status
If Insight Control virtual machine management is running, execute the following command to stop the service:
service hpvmmcntsvc stop
Deploying a virtual machine guest template
Insight Control virtual machine management enables you to deploy a previously created virtual machine
template to create a virtual machine guest. A virtual machine template is an image of a complete virtual
machine operating system, configuration, and all relevant virtual disk information. The template is needed
to create and register a new virtual machine on a virtual machine host with the same virtualization technology.
A template does not contain the serial number (UUID) and MAC address of the virtual machine guest used
to create the template.
1.
2.
From the HP SIM toolbar, select Deploy→Virtual Machine→Templates→ Deploy Virtual Machine
Template.
Select a template, and then click Next.
Launching VC
35
3.
4.
5.
6.
Select the target virtual machine host, and then click Next.
Select the target virtual machine host directory location.
Specify the name of the virtual machine guest, memory size, and target file as necessary, and then click
Next. The target folder must be empty.
Verify the details, and click Run Now, or to deploy the template later, click Schedule.
NOTE: When you schedule a job for an operation in Insight Control virtual machine management, selecting
Periodic Scheduling for the Deploy Virtual Machine Template operation might result in unexpected behavior.
NOTE:
For Xen on RHEL or SLES, you cannot perform the deploying virtual machine guest template operation.
NOTE: For volumes that have no drive letter assigned on the Microsoft Hyper-V server virtual machne host,
use the volume GUID path for the target path.
Deleting a virtual machine guest template
NOTE:
For Xen on RHEL and SLES, you cannot perform the delete virtual machine guest template operation.
A virtual machine template is an image of a complete virtual machine with operating system, configuration,
and all relevant virtual disk information. Insight Control virtual machine management enables you to delete
a previously created virtual machine template as follows.
1.
2.
3.
From the HP SIM toolbar, select Deploy→Virtual Machine→Templates→Delete Virtual Machine
Template.
Select the templates to be deleted, and then click Run Now.
To delete the virtual machine is selected, type YES.
Creating a virtual machine guest backup
You cannot perform backup and template tasks from VMware ESXi 3i, VMware ESX 4.0, and VMware ESXi
4.0, and VMware ESXi 3 to VMware ESX 3.x hosts. Backup and template tasks are not allowed from VMware
ESX 3.x hosts to VMware ESXi 3i, VMware ESX 4.0, and VMware ESXi 4.0 guests.
Performing a backup requires administrative rights. If you perform a backup on a virtual machine guest that
is running, the guest is suspended and then restored to a running state after the backup is complete.
Insight Control virtual machine management enables you to perform an immediate backup of a virtual
machine guest, schedule a single backup, or schedule a recurring backup on a daily or weekly basis. The
Create Virtual Machine Backup screen enables you to view and delete all available backups.
1.
2.
3.
4.
5.
6.
On the HP SIM All Systems page, select the virtual machine guest to backup.
From the HP SIM toolbar, select Deploy→Virtual Machine→Backups→ Create Virtual Machine
Backup.
Verify the target system, and then click Next.
Verify the source virtual machine details, and then review the resources of the available virtual machine
hosts.
Verify that adequate available disk space exists on the target virtual machine host to accommodate the
total transport volume, which consists of several disks and configuration files.
Select the target host, and then click Next.
The target repository must be on the same virtualization layer.
7.
8.
36
Specify where the backup files are to be placed on the virtual machine host, and then click Next. For
a VMware ESX server virtual machine that is powered up, choose one of the following:
•
Perform the backup while the virtual machine is running. During the backup operation, disk changes
are written to a new redo log and applied when the backup completes.
•
Pause the virtual machine for the duration of the backup operation and resume processing when
the backup completes. By default, the backup is compressed.
Select Do not automatically delete backups or Maximum backups to retain.
Using HP Insight Control virtual machine management
9. Click Next.
10. Verify the backup details, and then click Schedule or Run Now.
If other operations such as a copy are in progress, then a backup is not performed immediately. The backup
is queued to run after any pending operations are complete.
If you unregister a virtual machine host, then it is no longer managed by Insight Control virtual machine
management, and the backup information for the virtual machine guest associated with that host are
permanently removed. The backup files, including disk files, are retained in the designated location. You
can manually delete them.
NOTE: Insight Control virtual machine management stores the backup for a virtual machine in Citrix
XenServer as a template with the name prefixed with hpbackup#.
NOTE:
ESX.
You cannot perform hot backups using Citrix XenServer, Microsoft Hyper-V server, and VMware
NOTE:
You cannot create backups using Xen on RHEL or SLES.
NOTE: For volumes that have no drive letter assigned on the Microsoft Hyper-V server virtual machine host,
use the volume GUID path for the target path.
Restoring a virtual machine guest backup
Verify sufficient free space equal to the size of the virtual machine is available before restoring a virtual
machine backup on Citrix XenServer.
For Xen on RHEL or SLES, you cannot restore a virtual machine backup.
For Microsoft Hyper-V server:
•
Information for data transfer size, transfer rate, and estimated time for transfer is not available on the
user interface.
•
Virtual machines are suspended automatically before a backup is performed.
•
Only the virtual machine files in the virtual machine path are copied.
•
Hot backup is not supported.
The entry in the Estimated Transfer Time field is used to calculate the time required to transfer the virtual
machine files from the backup location to the target host. This time might vary from the Actual Time taken
since there are configuration durations which are not included in the Estimated Transfer Time.
Insight Control virtual machine management enables you to restore a virtual machine guest using a previously
created backup. When you perform the following procedure, the selected backup is restored to the virtual
machine.
1.
2.
3.
4.
5.
6.
From the HP SIM toolbar, select Deploy→Virtual Machine→Backups→Restore Virtual Machine
from Backup.
Select the backup image, and then click Next.
From the list of authorized licensed hosts, select the target virtual machine host.
Verify that adequate available disk space exists on the target virtual machine host to accommodate the
total transport volume, which consists of several disks and configuration files.
Select a location for the configuration file and virtual machine drives on the designated host, and then
click Next.
Verify the restore details, and click Run Now.
Restoring a virtual machine guest backup using a memory state with incompatible hardware might produce
errors when the virtual machine is restored. If errors occur, with the virtual machine powered on, remove
the memory state to resolve the issue. The Host Virtualization software displays a screen enabling you to
make the appropriate selection to remove the memory state. Be sure that the source virtual machine and the
restored virtual machine are not registered in the landscape at the same time.
Launching VC
37
If the virtual machine guest being restored exists on the selected host, then one of the following must occur:
•
If a virtual machine guest with the same BIOS ID exists on the virtual machine host and is located in
the folder to where the backup is to be restored, then you must stop the existing virtual machine host.
Existing files are overwritten.
•
If a virtual machine guest with the same BIOS ID exists on the virtual machine host and the restore
location is different, then you must unregister the existing virtual machine host. The restore folder must
be empty before you restore the backup.
•
If a virtual machine guest with the same BIOS ID exists on a different virtual machine host, then a
warning appears. The restore folder must be empty before you restore the virtual machine guest.
Restoring the most recent virtual machine guest backup
NOTE:
For Xen on RHEL or SLES, you cannot restore most recent virtual machine backup.
Insight Control virtual machine management enables you to restore a virtual machine guest using the last
backup created. When you perform the following procedure, the most recent backup is restored to the virtual
machine.
1.
2.
3.
4.
On the HP SIM All Systems page, select the virtual machine guest.
From the HP SIM toolbar, select Deploy→Virtual Machine→Backups→ Restore Last Virtual Machine
Backup.
Verify the source virtual machine host, and then click Next.
Verify the restore details, and click Run Now, or to restore the backup later, click Schedule.
Recovering virtual machines of a failed host on a VMware ESX Server, Citrix XenServer
or Microsoft Hyper-V R2 server
For Microsoft Hyper-V servers, virtual machines on failed hosts must meet the following requirements to be
recovered on alternate hosts:
•
The virtual machine must not be highly enabled.
•
The virtual machine configuration and disk files must be on cluster shared volumes.
•
The virtual machine must not have passed through disk(RDM disk) attached to it.
For Microsoft Hyper-V server, the highly available virtual machines are recovered by the Microsoft Failover
clustering feature in Microsoft Hyper-V.
Recovering virtual machines of a failed host enables virtual machines of a specified failed virtual machine
host to be recovered on defined alternate virtual machine hosts.
To recover a virtual machine of a failed host:
1.
2.
3.
4.
5.
If the virtual machines remain on the recovery servers, then you must set a new alternate virtual machine
host. For more information, see the Setting the alternate virtual machine host section.
On the HP SIM All Systems page, select the failed VMware ESX Server virtual machine host.
From the HP SIM toolbar, select Deploy→Virtual Machine→Recover VMs of Failed Host.
Click Next.
To recover the virtual machine now, click Run Now, or to perform the recovery later, click Schedule.
When you schedule Insight Control virtual machine management tasks, the Schedule option in HP SIM
does not work reliably because Insight Control virtual machine management might not be activated
when HP SIM is activated.
Scheduled tasks are evaluated every minute. The maximum time delay between the scheduled time of
an event and when the event is performed is 59 seconds.
38
Using HP Insight Control virtual machine management
Removing an alternate virtual machine host on a VMware ESX Server, Citrix XenServer,
or Microsoft Hyper-V R2 server
1.
2.
3.
On the HP SIM All Systems page, select the virtual machine.
From the HP SIM toolbar, select Configure→Virtual Machine→Set Alternate Virtual Machine Host.
Select Remove the alternate host definition, and then click Run Now.
Launching vCenter
The VMware Management Interface must be installed on a client server or CMS. If you are launching vCenter
from a VMware host, then you must install VMware Remote Console application on a client server or CMS.
The Launch vCenter option is enabled if:
•
The virtual machine is identified in HP SIM with a valid IP address.
•
The virtual machine is running.
The Launch vCenter option is disabled if the virtual machine guest operating system is unknown.
To launch vCenter:
1.
2.
From the HP SIM All Systems page, go to the host page, and then click the virtual machine guest
name. You can also launch vCenter by clicking the virtual machine guest name.
Click Launch vCenter.
For virtual machine guests on Xen hosts, the vCenter client (like the vCenter viewer or tight vCenter) must be
installed on the CMS.
The virtual machine is identified in HP SIM with a valid IP address.
The virtual machine is running.
The Launch vCenter option is disabled if the virtual machine guest operating system is unknown.
Setting or removing the performance threshold
Setting the performance threshold enables the trigger of an HP SIM event set for either virtual machine guests
or virtual machine hosts. If a designated threshold is reached, then a Major ( ) icon appears, and an event
is automatically generated in HP SIM.
To set or remove the performance threshold:
1.
2.
3.
4.
5.
6.
On the HP SIM All Systems page, select the virtual machine guest or virtual machine host.
From the HP SIM toolbar, select Configure→Virtual Machine→Set Performance Threshold.
Verify the virtual machine guest or virtual machine host, and then click Next.
Determine whether existing values and intervals must be added, updated, or removed by selecting
Add/Update or Remove.
Enter the appropriate values and intervals in the Processor Threshold, Memory Threshold, Network
Throughput Threshold, Storage Throughput Threshold, and Disk Utilization Threshold sections. Disk
utilization threholds are applicable only for virtual machine guests. Valid values include the following:
•
Value (Percent)—Enter the value as a percentage.
•
Interval (Minutes)—Enter the interval in minutes.
•
Value (KB)—Enter the value in kilobytes.
Click Run Now.
Configuring the polling frequency for virtual machine status checks
Insight Control virtual machine management provides a configurable parameter, VMConfigRefreshRate. This
parameter controls the frequency with which Insight Control virtual machine management checks for changes
in virtual machine configuration, such as number of NICs on the virtual machine, size of the hard disk, and
so on. Configuration changes on the virtual machines are updated by Insight Control virtual machine
management. The default polling frequency is 5 seconds.
Add the following configurable parameter in the hpvmm.conf file found in the CMS location <Insight Control
virtual machine management installation directory on CMS>/bin:
Configuring the polling frequency for virtual machine status checks
39
VMConfigRefreshRate=<< value in milli seconds >>
For example, VMConfigRefreshRate = 5000
The value of the parameter can be between 5 seconds and 5 minutes. Any values entered outside this range
are automatically adjusted to the max/min value of the range.
Because increasing the polling frequency also reduces the ability of Insight Control virtual machine
management to identify the changes in virtual machine status.
Setting the alternate virtual machine host
After virtual machines are successfully migrated to an alternate host after failed host recovery is performed,
the virtual machines might not be restored to the same state as they were before the migration. If Insight
Control virtual machine management records the last known state of the virtual machine when the host was
shutting down, then the powered off state of the virtual machine is recorded and the virtual machine is
migrated with the powered off state.
For Microsoft Hyper-V R2 servers, virtual machines must meet either of the following requirements for setting
an alternate virtual machine host:
•
The virtual machines must be created on clusters shared volumes.
•
••
The virtual machines on the host must be highly available and in running state.
1.
2.
3.
4.
On the HP SIM All Systems page, select the VMware ESX Server virtual machine.
From the HP SIM toolbar, select Configure→Virtual Machine→Set Alternate Virtual Machine Host.
Verify the source virtual machine, and then click Next.
Select the recovery hosts from the list of authorized licensed hosts, and then click Run Now.
If some Insight Control virtual machine management menu options do not appear, then verify that at least
one virtual machine guest has been properly discovered.
Handling prefailure events
For Xen on RHEL and SLES, prefailure events are not supported.
HP SIM can detect certain prefailure alerts and generate corresponding events. Insight Control virtual machine
management uses VMotion for VMware ESX, XenMotion for Citrix XenServer, and Live Move capability in
Microsoft Hyper-V R2 R2 servers as event handlers for these events, so that the virtual machine can be moved
to an alternate host before the system fails or is placed in maintenance mode.
The capability to detect prefailure alerts is supported in the following cases:
•
vCenter Server 2.5 and 4.0 platforms and for VMware ESX hosts and virtual machines that are on
shared storage
•
Citrix XenServer, XenServer host, and virtual machines that are on shared storage in a resource pool
•
For Microsoft Hyper-V R2 servers, virtual machines must be highly enabled and running to be moved
to alternate virtual machine hosts upon receiving the prefailure alerts
Prerequisites
Prerequisites For the prefailure events to work you must have a system collection created in HP SIM. To create
a System collection:
1. In the left Pane in HPSIM, under System and Event Collections then click Customize…
2. Select New....
3. Select Choose members individually
4. In the Choose from
menu, choose All Systems
5.
6.
40
.
Select the servers that have access to the same LUNs on shared storage.
Save the collection with an appropriate name, for example, Prefailure VMware ESX Collection, by
clicking Save as Collection
Using HP Insight Control virtual machine management
Xen on RHEL and SLES prefailure events are not supported.
Handling prefailure events is supported for virtual machines that are on shared storage.
Handling automatic prefailure events
1.
2.
3.
4.
5.
6.
7.
Select Deploy Virtual MachineHandle VM Host Prefailure Events.
In Step 1, select the target events. Select the PreFailure Events collection that has been created, then
click Apply.
Select Add System Filters….
Select the Option Collectionunder Add filters by selecting from:.
Select the system collection that has been created, as described in Prerequisites.
Click Apply, then Next. Confirm Detailsscreen appears.
To have the events automatically handled, click Schedule. The GUI for Step 2: Schedule Taskappears.
Set the schedule as needed.
Click Done, when the event that meets the criteria on the failed host occurs, and the virtual machines
are recovered to an alternate host or to place the host on maintenance mode.
Handling automatic prefailure events using the vCenter Server DRS cluster enabled
in the vCenter Server
Prerequisite: The ESX hosts must be in a cluster in VMware vCenter Server and DRS must be enabled on the
cluster.
Create a collection in SIM containing the ESX hosts that are in the DRS enabled cluster in vCenter.
Configure prefailure handling using the steps mentioned in “Handling automatic prefailure events.”
Anytime prefailure events are generated on any system in the System Collection Prefailure VMware ESX
Collection, this VMware ESX host is placed in maintenance mode in VMware vCenter Server. VMware
vCenter Server then moves all the virtual machines hosted on this VMware ESX system onto other hosts
available in the VMware Cluster.
Handling semi-automatic prefailure events with the vCenter Server DRS cluster enabled
in the vCenter Server
In semi-automatic mode of event handling, verify the SMTP settings in the Options Events Automatic Event
Handling Email Settings in HP SIM. When a prefailure event occurs, you are notified through email. When
you receive the email, perform the following steps to handle the prefailure events:
1. Select DeployVirtual MachineHandle VM Host Prefailure Events.
2. In Step 1, select the target events, then elect the PreFailure Events collection that has been created.
Click Apply.
3. Select Add System Filters….
4. Select the Option “Collectionunder Add filters by selecting from:.
5. Select the system collection that has been created. Perform the steps to create a collection as described
in the Prerequisites section
6. Click Apply, then click Next. The Step 2: Confirm Details Pagescreen appears.
7. 7. Click Run Now.
The virtual machines are recovered successfully on to the target host and the source host is placed on
maintenance mode.
Handling automatic prefailure events using the Set Alternate host feature
Prerequisite: The virtual machines must have an alternate virtual machine host set. To set alternate host, refer
to the section “Setting the alternate virtual machine host.”
Configure prefailure handling using the steps described in “Handling automatic prefailure events.”
Whenever any prefailure events are generated on any of the systems in the System Collection Prefailure
VMware ESX Collection, the virtual machines running on this host are recovered to the alternate host.
Handling prefailure events
41
Handling semi-automatic events using the Set Alternate host feature
In semi-automatic mode of event handling, verify the SMTP settings in the OptionsEventsAutomatic Event
HandlingEmail SettingsSystems Insight Manager. When a prefailure event occurs, you are notified through
email. When you receive the email, perform the following steps to handle the prefailure event:
1. Select DeployVirtual Machine HandleVM Host Prefailure Events.
2. In Step 1, select the target events, then select the PreFailure Events collection that has been created.
Click Apply.
3. Select Add System Filters….
4. Select the OptionCollectionunder Add filters by selecting from:.
5. Select the system collection that has been created. Perform the steps to create a collection described
in the Prerequisites section.
6. Click Apply, click Next. The Step 2: Confirm Details Page Appearsscreen appears.
7. Click Run Now.
The virtual machines are recovered successfully on to the target host from the source host.
Handling automatic prefailure events using the Set Alternate host feature
Whenever any prefailure events are generated on any of the systems in the System Collection Prefailure
VMware ESX Collection, the virtual machines running on this host are recovered to the alternate host.
Handling semi-automatic events using the Set Alternate host feature
In semi-automatic mode of event handling, ensure the SMTP settings in the Options→Events→Automatic
Event Handling→Email Settings in HP SIM. When a prefailure event occurs, you are notified through
email. When you receive the email, the following steps must be executed to handle the prefailure event:
Failed host recovery
The failed host recovery feature enables you to recover virtual machines of a failed Citrix XenServer host
and leverage the ability of Systems Insight Manager to detect hardware failures
VMware ESX Server
For VMware ESX virtual machines, use the failed host recovery feature if you do not use the VMware vCenter
High Availability (HA) solution.
IMPORTANT: In a setup where both the failed host recovery feature and VMware vCenter HA or VMware
Distributed Resource Scheduler (DRS) are configured, the results might be unpredictable because both
management tools try to control the same resource.
IMPORTANT: Do not configure both the failed host recovery feature and the VMware HA or VMware DRS
solution for the same VMware ESX hosts.
IMPORTANT: Do not configure both the failed host recovery feature and the VMware HA or VMware DRS
solution for the same VMware ESX hosts.
If the virtual machine being moved is part of the vCenter cluster, then a warning message appears.
When a failed host recovery process is being performed for virtual machines failing over to the alternate
hosts, the moved virtual machines might appear as Orphaned in the vCenter. If this occurs, delete the
orphaned nodes from vCenter.
In the failed host recovery procedure, the running virtual machine guest will be recovered as powered off
state in the target host. This is an expected behavior.
Citrix XenServer
The failed host recovery feature enables you to recover a failed Citrix XenServer host and leverage the ability
of HP SIM to detect hardware failures.
Do not configure both the failed host recovery feature and the Citrix XenServer HA for the same Citrix
XenServer hosts.
42
Using HP Insight Control virtual machine management
Microsoft Hyper-V
The failed host recovery feature enables you to recover a failed virtualchines of Hyper-V R2 server and
leverage the ability of Systems Insight Manager SIM to detect hardware failures. For Microsoft Hyper-V R2
Server, virtual machines on failed hosts must meet the following requirements to be recovered on alternate
hosts:
•
The virtual machine must not be highly enabled.
•
The virtual machine configuration and disk files must be on cluster shared volumes.
•
The virtual machine must not have passed through disk(RDM) disk attached to it.
NOTE: For Microsoft Hyper-V R2 Server, the highly available virtual machines will be recovered by the
Microsoft ailover clustering feature in Microsoft Hyper-V.
Setting up the recovery feature
1.
2.
3.
In HP SIM create a CriticalVmHost collection based on the system health parameters. For more
information, see Creating a CriticalVmHost collection.
Set the alternate host for your virtual machines so that you have defined alternate hosts appropriately.
For more information, see Setting the alternate virtual machine host.
Schedule the recovery of failed virtual machine hosts based on the collection and events.
Recovery actions do not occur on virtual machine hosts or virtual machines unless you have set an
alternate host set, even if those virtual machine hosts or virtual machines are included in the CriticalVmHost
collection. To schedule the recovery of virtual machines of failed hosts for any system that has turned
critical and is part of the CriticalVmHost collection:
1.
From the HP SIM toolbar, select Deploy→Virtual Machine→Recover VMs of Failed Host.
The Step 1: Select Target Systems screen appears.
2.
3.
From the Add targets by selecting from list, select CriticalVmHost.
Select Select “CriticalVmHost” itself as the target. Click Apply.
Setting up the recovery feature
43
Creating a CriticalVmHost collection
1.
To create a new collection, from the left pane of the HP SIM screen, click Customize, and then click
New. The New Collection screen appears.
2.
3.
Select Choose members by attributes.
Select the collection criteria as shown in the screen, and then save the collection as CriticalVmHost.
Scheduling the recovery of virtual machines of failed hosts
Recovery actions do not occur on virtual machine hosts or virtual machines unless you have set an alternate
host set, even if those virtual machine hosts or virtual machines are included in the CriticalVmHost collection.
To schedule the recovery of virtual machines of failed hosts for any system that has turned critical and is part
of the CriticalVmHost collection:
44
1.
From the HP SIM toolbar, select Deploy→Virtual Machine→Recover VMs of Failed Host. The Step
1: Select Target Systems screen appears.
2.
3.
From the Add targets by selecting from list, select CriticalVmHost.
Select Select “CriticalVmHost” itself as the target. Click Apply.
Using HP Insight Control virtual machine management
4.
Verify the failed VMware ESX Server host, and then click Next.
5.
Confirm your choices, and then click Schedule.
6.
You are prompted to schedule the task. Select When new systems or events are added to the
collection for Recover VMs of Failed Host. The following options are available under Schedule:
•
Periodically
•
Once
•
When new systems or events are added to the collection
•
When systems or events are removed from the collection
•
Not scheduled
Scheduling the recovery of virtual machines of failed hosts
45
7.
Click Done.
VMware ESX Server Guest System page
When using a VMware ESX Server, from the Guest System page, click Launch vCenter.
Performance information
These sections list information displayed on the Performance tab of the System Page for virtual machine
hosts and guests.
46
•
To determine virtual machine host capacity and virtual machine workload characteristics, use the
performance information.
•
To create alerts and log messages based on user-selectable performance values, use the threshold
settings.
Using HP Insight Control virtual machine management
Displaying virtual machine host performance information
1.
2.
From the HP SIM All Systems tab, select a virtual machine host.
Click the VM Performance tab.
The performance information feature can display activity for the most recent 1, 5, 15, 30, or 60 minutes. If
the amount of time requested exceeds the amount available, then all available information is reported.
Virtual machine host performance
The following performance information is provided for VMware ESX Server, Citrix XenServer, and Microsoft
Hyper-V server, except where noted:
NOTE:
clock.
For accurate performance information, synchronize the CMS clock and the virtual machine host
•
Processor utilization (x CPUs)—The processor utilization on the host, including utilization by the virtual
machines. The number of processor cores or threads on the virtual machine host is reported as x CPUs.
•
Virtual machine processor utilization—The processor consumption by all virtual machines on this host.
Processor resources consumed by a virtual machine before powering down the virtual machine are not
included.
•
Reserved capacity (All running virtual machines)—The sum of the Reserved System Capacity values for
all Microsoft Hyper-V server virtual machines currently powered up.
•
CPU min (All running virtual machines)—The sum of the CPU Min values for all virtual machines currently
powered up divided by the resources available on the host (VMware ESX Server only).
•
Memory utilization—The total amount of memory currently in use on the host. The utilization bar indicates
the memory utilization as a percentage of the physical memory configured.
•
Virtual machine memory—The total amount of memory currently in use by virtual machines executing
on the host. Memory consumed by a virtual machine before powering down the virtual machine is not
included. The utilization bar indicates the virtual machine memory as a percentage of the physical
memory configured.
•
Network throughput—Network traffic transmitted and received on this host. Virtual machine network
throughput is included for VMware ESX Server.
•
Network transmit throughput—Network traffic transmitted by this host. Virtual machine network
transmission throughput is included for VMware ESX Server. The utilization bar represents the transmission
percentage of the network throughput.
•
Network receive throughput—Network traffic received by this host. Virtual machine network receive
throughput is included for VMware ESX Server. The utilization bar represents the receive percentage
of the network throughput.
•
Storage throughput—Storage read and written by this host and all virtual machines on the host. This
utilization bar is always filled.
•
Storage read throughput—Storage read by this host and all virtual machines on the host. The utilization
bar represents the read percentage of storage throughput.
•
Storage write throughput—Storage written by this host and all virtual machines on the host. The utilization
bar represents the write percentage of storage throughput.
Virtual machine performance
The value averages displayed in this section are relative to the duration of the virtual machine host activity.
Resources consumed by a virtual machine before powering down the virtual machine are not included.
•
CPU—The CPU percentage consumed by the virtual machine relative to the total processor capacity of
the virtual machine host.
•
vCPU—The CPU percentage consumed by the virtual machine relative to its resource allocation
•
Memory—Physical host memory consumed by the virtual machine
Displaying virtual machine host performance information
47
•
Network—Network throughput for the virtual machine. The utilization bar indicates the virtual machine
network throughput as a percentage of the total network throughput on the virtual machine host
•
Storage—Storage throughput for the virtual machine. The utilization bar indicates the virtual machine
storage throughout as a percentage of the total storage throughput on the virtual machine host
Threshold settings
A threshold specific to a virtual machine hosts that can be evaluated.
•
State—The current state of this threshold. The state can be:
•
Unknown, indicating that the number of utilization samples available is less than the threshold
interval.
•
Normal, indicating that software utilization samples are available and the measured value is less
than or equal to the threshold value.
•
Exceeded, indicating that sufficient utilization samples are available and the measured value is
greater than the threshold value.
•
Threshold interval—The number of minutes of utilization data that must be available before the threshold
is evaluated
•
Threshold value—The maximum utilization value that provides a normal status
•
Measured interval—The number of minutes of utilization data averaged to calculate the measured value
•
Threshold value—The maximum utilization value that provides a normal status
Displaying virtual machine guest performance
1.
2.
3.
From the HP All Systems page, select a virtual machine guest.
Click the VM Peformance tab.
Select the appropriate time frame at the top of the screen for which to display information.
NOTE:
The VM Performance tab is not available for Xen on RHEL and SLES.
Virtual machine performance
The following performance information is provided for VMware ESX Server, Citrix XenServer, and Microsoft
Hyper-V server hosts, except where noted:
48
•
Virtual processor utilization (vCPU)—The CPU percentage consumed by the virtual machine relative to
the resource allocation. The Host Processor Utilization on 1 CPU value is reported.
•
Host processor utilization on x CPUs—The CPU percentage consumed by the virtual machine relative
to the number of physical processors (x) on which the virtual machine can execute .
•
Host processor utilization on all CPUs—The CPU consumed by this virtual machine, relative to the total
virtual machine host processors .
•
Memory utilization—The physical host memory used by this virtual machine. The utilization bar indicates
the virtual machine memory utilization as a percentage of the physical memory configured on the virtual
machine host.
•
Network throughput—The network traffic transmitted and received by this virtual machine. The utilization
bar indicates the virtual machine network throughput as a percentage of the total network throughput
on the virtual machine host.
•
Network transmit throughput—The network traffic transmitted by this virtual machine. The utilization
bar indicates the virtual machine network transmit throughput as a percentage of the total network
throughput on the virtual machine host.
•
Network receive throughput—The network traffic received by this virtual machine. The utilization bar
indicates the virtual machine network receive throughput as a percentage of the total network throughput
on the virtual machine host.
Using HP Insight Control virtual machine management
•
Storage throughput—The storage read and written by this virtual machine. The utilization bar indicates
the virtual machine storage throughput as a percentage of the total storage throughput on the virtual
machine host .
•
Storage read throughput—The storage read by this virtual machine. The utilization bar indicates the
virtual machine storage read throughput as a percentage of the total storage throughput on the virtual
machine host.
•
Storage write throughput—The storage written by this virtual machine. The utilization bar indicates the
virtual machine storage write throughput as a percentage of the total storage throughput on the virtual
machine host.
Resource allocation
The bars indicate the virtual machine allocation relative to the capacity available on the virtual machine
host.
NOTE:
•
•
Resource allocation is not available for Citrix XenServer, or Xen on RHEL or SLES.
VMware ESX Server virtual machines
•
CPU Min—The cpu.min value reported by VMware ESX
•
CPU Max—The cpu.max value reported by VMware ESX
•
CPU Shares—The cpu.shares value reported by VMware ESX
Microsoft Hyper-V server virtual machines
•
Reserved capacity—The reserved system capacity value reported by the virtual server relative to
1 CPU
•
Maximum capacity—The maximum system capacity value reported by the virtual server relative
to 1 CPU
•
Relative weight—The relative weight value reported by the virtual server
Threshold settings
Threshold of a virtual machine that can be evaluated. This will have information only if the threshold limit
has been set.
•
State—The current state of this threshold. The state can be:
•
Unknown, indicating that the number of utilization samples available is less than the threshold
interval.
•
Normal, indicating that sufficient utilization samples are available, and the measured value is less
than or equal to the threshold value
•
Exceeded, indicating that sufficient utilization samples are available, and the measured value is
greater than the threshold value
•
Threshold settings—Threshold of a virtual machine that can be evaluated
•
Threshold value—The maximum utilization value that provides a normal status
•
Measured interval—The number of minutes of utilization data that was averaged when calculating the
measured value
•
Measured value—The average utilization over the most recently measured interval (in minutes)
Performance color codes
The color codes on the Performance page indicate the percentage of a resource that has been consumed.
The colors of the utilization bar indicate the following conditions:
•
Blue—Indicates throughput.
•
Green—Indicates utilization is less than 70%.
Resource allocation
49
•
Yellow—Indicates utilization is between 70% and 80%.
•
Red—Indicates utilization is greater than 80%.
Multisystem aware tools available
Within HP SIM, you can run tools on multiple systems at once or multisystem aware tools. The following
Insight Control virtual machine management tools can be multisystem aware:
•
Starting virtual machine hosts
•
Stopping virtual machine hosts
•
Restarting virtual machine hosts
•
Pausing virtual machine hosts
•
Setting alternate host
•
Setting the performance threshold
•
Recovering failed hosts of a virtual machine hosts
•
Deploying an agent
•
Restoring last virtual machine backup
•
Defining new virtual machine host collections for all virtual machines
For more information on multisystem aware tools, see the HP SIM Technical Reference Guide at
http://www.hp.com/go/hpsim.
50
Using HP Insight Control virtual machine management
4 Troubleshooting
The Troubleshooting chapter is divided into the following sections. To access a section, click the link.
Troubleshooting
“Installation”
“Configuration”
“Insight Control virtual machine management controls”
“VMM Pack functions”
“HP SIM console integration”
“Hardware”
“Insight Control virtual machine management Events”
Installation
In an environment using multiple instances of HP SIM CMS, Insight Control virtual
machine management can only be installed on one CMS
HP SIM manages devices by polling them periodically, receiving traps, and connecting to run tasks, such
as software updates or scripts. A device can be polled by one or more instances of HP SIM.
Insight Control virtual machine management requires that a more persistent connection be maintained with
the virtual machine hosts and the virtual machine guests. Multiple instances of Insight Control virtual machine
management cannot be used to control the same set of hosts and guests.
HP SIM and Insight Control virtual machine management are multiuser capable, so multiple instances are
not required to provide concurrent access to HP SIM and Insight Control virtual machine management.
System starting improperly or installation fails to proceed
If the HP SIM or database services are not started properly, an installation fails to proceed, or a manual
uninstallation is required when HP SIM and database services are running, then the following message might
appear:
Systems Insight Manager or database service is not started properly.
Installation fails to proceed. Uninstall manually when HP SIM and database
services are running properly.
Insight Control virtual machine management installation and uninstallation require HP SIM and database
service to be running. To resolve the issue:
1.
2.
3.
From the Windows toolbar, select Start→Settings→Control Panel→ Administrative Tools→Services.
Be sure the HP SIM service has been started.
Select the database system. Be sure the database service is started.
4.
5.
Open Microsoft® Internet Explorer, and then enter http://CMS name or IP:280.
Be sure that the HP SIM console appears.
Uninstall Insight Control virtual machine management by using a method described in the “Uninstalling
Insight Control virtual machine management” section.
Troubleshooting
51
Some menus do not appear in the toolbars
After installation, not all menus related to Insight Control virtual machine management appear in the toolbar.
To resolve the issue:
1.
2.
3.
Discover a VM host and then verify menus in toolbar.
From a command prompt, verify that the menu exists by running mxtool. Some Menus have a required
filter.
Go to [VMM installation path\ToolsMenu] directory and execute following command : mxtool -a
–f vmmTools.xml.
After upgrade, virtual machine host registration completes successfully without
discovering the vCenter server and without vCenter credentials
This is an expected behavior of Insight Control virtual machine management Virtual machine hosts appear
as Critical, and the vCenter Server was not discovered. When you click the Critical icon, a message displays
saying that the vCenter Server was not discovered.
Uninstalling Insight Control virtual machine management
If HP SIM is uninstalled, then Insight Control virtual machine management is uninstalled. Insight Control virtual
machine management can also be uninstalled using either of the following methods:
•
Close all Insight Control virtual machine management screens. The screens must be closed before
attempting uninstallation.
•
If HP SIM is installed, then HP SIM and Microsoft SQL Server must be running to successfully uninstall
Insight Control virtual machine management.
Uninstalling using Add or Remove Programs
1.
2.
3.
From the Control Panel, double-click Add or Remove Programs.
Select Insight Control virtual machine management 6.0 (remove only).
When prompted to confirm the uninstallation, click Yes.
To uninstall the VMM Agent from the VMware ESX Server virtual machine hosts, run the following command:
rpm –e hpvmmagent
VMMclient.jar, commons-cli-1.0.jar, or org.mortbay.jetty.jar files fail to copy
During installation, if the VMMclient.jar, commons-cli-1.0.jar, or org.mortbay.jetty.jar
files exist, then the installer might be unable to replace these .jar files in the HP SIM lib folder. If this occurs,
remove the file.
1.
2.
3.
4.
5.
6.
From the Control Panel, select Administrative Tools.
Double-click Services.
Highlight HP Systems Insight Manager, and then click Stop the service.
Locate the appropriate .jar file, and then manually delete it.
Click Start the service.
Reattempt the Insight Control virtual machine management installation process.
Mouse does not work properly after Microsoft Hyper-V server installation
If the mouse stops working properly after installing a Microsoft Hyper-V server virtual machine operating
system, install Integrated Service components on the virtual machine. This option is available when you
connect a Microsoft Hyper-V server virtual machine integrated service setup disk, and click Action→Insert.
52
Troubleshooting
Configuration
Insight Control virtual machine management host registration fails
After installing HP SIM and Insight Control virtual machine management, the Connection to VMM
Service failed! message might appear when performing the following items:
•
After changing the Insight Control virtual machine management system password
•
After changing the HP SIM service password
To resolve this issue, you must change the service password of Insight Control virtual machine management
by performing the following:
1.
2.
3.
4.
5.
Select Control Panel→Administrative Tools→Services
In the list of services, search for HP Insight Control virtual machine management service.
Right-click on the service, and then click Properties.
Click the Log On tab, and then change the password.
Restart the service.
For registration to succeed, the packages with the correct architecture must be installed on Xen hosts. The
Insight Control Virtual Machine Manager Software cannot detect the architecture of the package installed,
so install the correct package on the host with the recommended architecture. Refer to ”Post-installation
configuration tasks” for more information.
Virtual machine host registration CRA fails when selected with "Install Linux PSP or
ESX agents" for VMware ESX 3.5 U4
After you have selected "Install Linux PSP or ESX agents" and Register Virtual Machine Host options in CRA
task for VMware ESX 3.5 U4 or later, the "VM host registration" task fails because the system shows as Not
Responding in vCenter. vCenter takes about five minutes for a system to reach a Normal status and therefore
fails when HP SIM tries to register the virtual machine host.
To resolve this issue, register the virtual machine host at a later time when the server is in a Normal state in
vCenter.
Performance information does not appear for Citrix XenServer host and virtual
machines
Ensure that the CMS clock and Citrix XenServer host clock are synchronized.
Insight Control virtual machine management items are not removed from the HP SIM
toolbar with Insight Control virtual machine management uninstallation
Be sure you can open the HP SIM page by entering http://CMS name:280 in Internet Explorer.
To remove the menu items, run the following command from the command prompt at the HP SIM CMS:
mxtool -r -t “VMM menu item”
where VMM menu item is the Insight Control virtual machine management menu item that appears in the
HP SIM toolbar.
Insight Control virtual machine management might not detect virtual machines located
on mapped network drives
If the service does not have access to the network shares, Insight Control virtual machine management cannot
locate virtual machines stored on mapped network drives.
Configuration
53
Configuring Insight Control virtual machine management to manage virtual machine
hosts behind a firewall
When managing virtual machine hosts behind a firewall, the firewall must be configured to enable Insight
Control virtual machine management traffic through the firewall. The following ports are used for:
•
Communication between browsers and the HP SIM Web Service uses HTTPS over port 50000.
•
Communication between the Web Service and the VMM Service (both on the HP SIM CMS) uses SSL
over port 40420, assigned with the Internet Assigned Numbers Authority (IANA).
•
Communication between the VMM Service and VMM Agent (on virtual machine hosts) uses SSL over
ports 1125 and 1126, assigned with the IANA.
•
Communication between the VMM Agents during a move or copy uses SSL over port 1126, assigned
with the IANA.
In addition to the standard ports, Insight Control virtual machine management also opens additional ports
dynamically. The free ports might be different at various instances of the agent, causing the exact port
numbers to be different.
Microsoft DNS Server might not map the host name to DHCP-generated IP addresses
If DHCP is used on the VMware ESX Server host, then the Microsoft DNS server might not map the host name
to DHCP-generated IP addresses. HP recommends creating a static IP address.
Virtual machine hosts are in different subnets
For Microsoft Hyper-V servers, the Unable to register the VM / Fail to share the
destination VM folder error message appears in the log file if either of the following occurs:
•
The source and destination Microsoft Hyper-V server hosts are in different subnets.
•
The destination folder on the virtual machine host cannot be shared.
Insight Control virtual machine management controls
Virtual machine host and guest icons do not appear in Insight Control virtual machine
management
If the virtual machine host and guests were previously accessible from Insight Control virtual machine
management and display an Information icon in the HP SIM console, verify that the host is licensed. If the
host was licensed with a demo license, then the license might have expired. Obtain a permanent license for
the host.
54
Troubleshooting
Insight Control virtual machine management does not display the system name, system
IP address, and operating system
NOTE: If Windows 2000 is the virtual machine guest operating system, WMI might be required for
installation.
Insight Control virtual machine management obtains the system name, IP address, and operating system
information from HP SIM. If the correct system name, IP address, and operating system name do not appear
in Insight Control virtual machine management, then verify that the virtual machine guest has been discovered
by HP SIM. If the guest has not been discovered, then perform an Automatic Discovery of the undiscovered
virtual machine hosts and guests from the HP SIM console by selecting Options→Discovery.
Virtual machines that you have installed, but that HP SIM has not discovered, have limited functionality. For
example, the following functions cannot be performed:
•
Copying a virtual machine guest
•
Moving a virtual machine guest
•
Backing up a virtual machine guest
•
Defining the performance threshold
•
Setting up a failed host recovery
•
Granting authorizations
The only operations that can be performed are creating templates. To enable full functionality, the virtual
machine must be discovered.
Critical status appears for a virtual machine host in Insight Control virtual machine
management
Critical status might appear when a virtual machine host is unavailable. A critical state for a virtual machine
host means that the virtual machine host has been licensed for Insight Control virtual machine management,
but is not currently communicating with Insight Control virtual machine management Service. This might be
caused by network connectivity errors or a power failure on the virtual machine host.
To determine if communication is established, ping the host. If communication does not exist, then the virtual
machine host no longer exists. To remove the host from the HP SIM toolbar:
1.
2.
3.
4.
5.
6.
7.
8.
From the HP SIM toolbar, select Configure→Virtual Machine→Unregister Virtual Machine Host.
Select the target virtual machine host to unregister.
Click Apply.
Verify that the correct target host appears in the list.
If necessary, to add targets, click Add Targets, or to remove targets, click Remove Targets,
Click Next.
To unregister the host immediately, click Run Now. You are prompted to confirm the unregistration.
The unregistration process begins after confirmation.
To unregister the virtual machine host from the command prompt, enter the Insight Control virtual machine
management installation folder\bin and enter the following command:
vmcli -unregisterAgent <IP_address>
where IP_address is the IP address of the previous virtual machine host.
A blank page appears when you launch Insight Control virtual machine management
from HP SIM
This condition occurs when the CMS name link is not resolved correctly on the network. To resolve this issue:
1.
2.
3.
Record the name used in the browser window.
Verify that this name is resolved on the network and is not being affected by any proxy settings in the
browser.
Be sure to include this link as a trusted site in the Internet Explorer browser security settings.
Insight Control virtual machine management controls
55
Virtual machine status is not updated
Virtual machine status might not be updated because Insight Control virtual machine management cannot
communicate with the HP SIM database. Restart Insight Control virtual machine management service to
resolve this issue.
Virtual machine guest information becomes inaccessible from Insight Control virtual
machine management
Virtual machine guest information might become inaccessible from Insight Control virtual machine management
after a period of time. To resolve this issue, run Identify Systems on the virtual machine host that is hosting
the virtual machine guest by clicking Options→Identify Systems.
A virtual machine host appears in Insight Control virtual machine management multiple
times
The virtual machine host might appear twice in Insight Control virtual machine management: once licensed
and once unlicensed.
If this issue occurs, unregister the unlicensed host.
A virtual machine guest appears in VMware vCenter Server multiple times
When you perform a regular move, SAN move, or failed host recovery, the virtual machine guest is
unregistered from the host, but the serial number of the virtual machine guest is still registered in VMware
vCenter Server. If the virtual machine guest is added again, then it might appear as a duplicate entry within
VMware vCenter Server. If a VMotion migration is performed, then the computer names can be duplicated.
This is a known issue with VMware vCenter Server 1.x when virtual machines are registered or unregistered
using VMware ESX CLI.
To resolve this issue, when you unregister a virtual machine guest from the host, it must also be unregistered
in VMware vCenter Server, or VMware vCenter Server 1.x must be upgraded to vCenter Server 2.x.
Live Move fails after SAN move
If a SAN move is performed with VMware vCenter Server managing the source and target hosts, then a
duplicate entry is created in VMware vCenter Server after the migration complete. An attempt to perform a
Live Move fails with the following error:
Live Move of VM [Virtual machine name] to [source virtual machine]. Live move
in progress Live move VM failed. VM changed state before it could be migrated.
To resolve this issue, delete the duplicate computer name from VMware vCenter Server, and then perform
the Live Move again.
VMotion fails because virtual machine host names are mismatched in HP SIM and
vCenter Server
Performing a VMotion can fail when HP SIM and vCenter Server discovers the virtual machine host name
with different capitalization. When the migration is performed the following error appears:
No, Live Move is not enabled. Stop the VM to enable other move options.
To resolve this issue, be sure both virtual machine hosts have the same name using the same capitalization.
This is a known issue with VMware vCenter Server 1.3. Mismatched virtual machine host entries do not exist
when using VMware vCenter Server 2.x.
Virtual machine host experiences extremely slow response time
If the virtual machine host on VMware ESX Servers is experiencing an extremely slow response time, then
increase the processor or memory resources for the operating system.
For more information on increasing operating system resources, see the VMware ESX Server manual at
http://www.vmware.com.
56
Troubleshooting
Insight Control virtual machine management demo licensing
A virtual machine host does not use a demo key if a purchased Insight Control virtual machine management
license key is present.
If the same backup is restored multiple times, then the Restore Virtual Machine from
backup operation fails
If the same backup is restored multiple times to different locations on the same virtual machine host, the
Restore Virtual Machine from Backup operation might fail. To resolve this issue, before selecting Restore
Virtual Machine from Backup function from the HP SIM toolbar, unregister or delete the virtual machine
guest that was restored earlier using the same backup from the virtual machine host.
Recovery of virtual machine fails with incompatible hardware configurations
The hardware and configuration of an alternate virtual machine host must be compatible with a virtual
machine to be recovered. If the alternate host hardware or configuration is not compatible, then you can
reconfigure the virtual machine after the Recover Virtual Machines of Failed Host operation has been
performed.
An error occurs when you click Remote Desktop
When you click Remote Desktop in the HP SIM Host System page using Internet Explorer browser, the
following error might appear:
Internet Explorer cannot download e.rdp?hostname=<host IP> from <host>.
Displaying Remote Desktop for the virtual machine requires the file remote.rdp to be downloaded. If the
Internet options are set to disable download of files, then this error occurs.
To resolve this issue:
1.
2.
3.
From the Internet Explorer browser, select Tools→Internet Options→Advanced.
Clear the Do not save encrypted pages to disk option.
Click Apply.
VMM Pack functions
Stop VM task does not perform as expected on Xen on RHEL 5.4 x86 virtual machine
hosts
On a Xen on RHEL 5.4 x86 virtual-machine host, a Stop operation perfomed on a Microsoft Windows virtual
machine guest, may not succeed. In such a case, VMM would display a timed-out message and would not
indicate a failure.
Error message Unknown to VMM appears when performing the copy operation on
a virtual machine
If the error message Unknown to VMM appears when performing the copy operation on a virtual machine,
ensure that the virtual machine exists on the host. If the virtual machine has been deleted from the host, but
the virtual machine node is still present in HP SIM, run the Identify Systems task on the virtual machine host
from Options→Identify Systems in HP SIM. If the virtual machine was manually discovered in HP SIM
using the IP address, then the virtual machine must be deleted from the HP SIM All Systems page.
Transport operation fails after restarting Insight Control virtual machine management
If you restart Insight Control virtual machine management after initiating the transport operation, the transport
operation will fail. However, the result of the transport operation on the virtual machine host is
hypervisor-dependent. This might require removing unwanted resources such as virtual machine files and
disks on the hypervisor.
VMM Pack functions
57
Copied or moved Xen virtual machine guest does not start on the destination host
When a Xen virtual machine guest is copied or moved to another host, Insight Control virtual machine
management attempts to convert the Xen bridge of the guest to match a bridge present on the destination.
When trying to start the virtual machine guest, the following error appears on the console:
Error: Device 0 (vif) could not be connected. Could not find bridge device
xenbr<#>
To resolve this issue, modify the configuration of the virtual machine guest to use an existing Xen bridge on
the destination system.
1.
List the existing bridges on the destination host using the command brctl show. If no Xen bridges
are created, create one with the /etc/xen/scripts/network-bridge script.
For example: /etc/xen/scripts/network-bridge start netdev=eth0 vifnum=0
2.
3.
4.
5.
6.
Dump the Xen virtual machine guest XML configuration to a file: virsh dumpxml GUEST_NAME >
guest.xml
Undefine the Xen virtual machine guest on the system: virsh undefine GUEST_NAME
Modify the Xen bridge in the configuration by editing the <source bridge='> XML tag.
Redefine the Xen virtual machine guest on the system: virsh define guest.xml
Start the Xen virtual machine guest.
Handle virtual machine host prefailure events task does not progress
For VMware ESX 3.x or VMware ESX 3.x hosts, when Deploy→Virtual Machine→Handle VM Host
Prefailure Events is selected, the virtual machine host is placed into maintenance mode in VMware vCenter
Server. To enter maintenance mode, all virtual machines must be powered down or migrated to other virtual
machine hosts. Manual intervention might be required to complete this task.
HTTP ERROR: 500 Internal Server Error message appears during a Insight
Control virtual machine management move or copy operation
This error can occur when the network is busy during the move or copy operation.
To resolve this issue, refresh the browser window.
Insight Control virtual machine management cannot move virtual machines with certain
disk types
Insight Control virtual machine management does not move or copy virtual machines with the following disk
types when installed with the indicated virtualization technology.
Unsupported disk types include the following:
•
Linked disk
•
Differencing disk
•
Physical (RAW) disk
Virtual machine files are not deleted after a move
Insight Control virtual machine management does not delete virtual machine guest files after a move, enabling
the virtual machine guest to be restored on the source host. This scenario occurs only with Xen virtual machine
hosts not in other hypervisors.
Virtual machine devices might not be available after a copy or move
Reconfigure the virtual network connections on the moved or copied virtual machine guest.
A shutdown or restart operation fails or does not complete
You must install VMware Tools on virtual machine guests before you can perform a shutdown or reset.
To install Microsoft Virtual Server Additions or VMware Tools, see the HP Insight Software Installation and
Configuration Guide.
58
Troubleshooting
Launching the remote console from Insight Control virtual machine management
console might fail
All virtual machine host port numbers are changed when you modify the configuration setting.
Verify the installation of VMware Management Interface software, indicated by the presence of the VMware
Management Interface directory within the VMware installation directory. For information, see the VMware
Knowledge Base Answer ID 793 at http://www.vmware.com/support/kb.
Also, verify that the Web port is 8222, the default port. If it is not, update the Web port in Insight Control
virtual machine management configuration setting:
1.
2.
3.
▲
In the C:\Program Files\HP\Insight Control virtual machine management\bin directory, locate the
hpvmm.conf file.
Modify the port number specified in the VMwaregsxport to the default port.
Save the file, and then restart Insight Control virtual machine management services.
VMware ESX Server—Verify that the VMware ESX Server Web port is 80, the default port. If it is not,
then update the Web port in Insight Control virtual machine management configuration setting:
1. In the C:\Program Files\HP\Insight Control virtual machine management\bin directory, locate
the hpvmm.conf file.
2. Modify the port number specified in the VMwareesxport to the default port.
3. Save the file, and then restart Insight Control virtual machine management services.
Some Insight Control virtual machine management operations dependent on vCenter
Server do not complete or are completed without confirmation
The following might occur when you try to perform some Insight Control virtual machine management
operations using VMware vCenter Server 2.5:
•
The operation does not complete.
•
The operation completes successfully, but a message confirming the operation is not sent to Insight
Control virtual machine management. As a result, the task is not identified as being completed on the
HP SIM Task page.
This issue has been resolved with VMware vCenter Server 2.5 Update 5. You should upgrade to this version.
Orphan managed systems created in the CMS
When you move a virtual machine on an Citrix XenServer, the unique identifier used to identify the system
often changes. This change in identifier causes a new managed system object to be created in the database,
and the hostname and IP address of that system must be moved to the new database object. However, there
are still uncleared events associated with the old database object, so it is renamed to the serial number of
the virtual machine so that you can still view these events. After you have viewed and cleared all the events
associated with the system, the events can be deleted from the database.
Workaround
Follow the naming restrictions for the complex that are outlined in the Naming Restrictions document and,
if using HP SIM 5.1.0.1 or later, read and follow the naming restrictions found in the DISCOVERY section
of the <HP SIM Installed Path>/doc/en/hpsim-readMe.pdf file. This .pdf file also discusses
some cases when orphan nodes cannot be prevented, and what you can do to prevent those that can be
prevented. For example, if you know a system subtype of a managed system is going to be changed (such
as converting a virtual partition to a virtual machine), delete the system from the CMS before the change,
and then re-add the system after the system has been reconfigured.
Failed host recovery on master Citrix XenServer host of the HA disabled resource
pool fails
Insight Control virtual machine management does not support failed host recovery on the master of the Citrix
Resource Pool unless a new master is selected, as documented in the Citrix XenServer Guide.
When the master host in a Citrix XenServer resource pools fails, login to the slave host that you want to
become the master, and execute the following commands:
VMM Pack functions
59
xe pool-emergency-transition-to-master
xe pool-recover-slaves
Insight Control virtual machine management detects the new master of the resource pool. You should now
invoke Recover VMs of Failed Host.
Insight Control virtual machine management does not display Quick Move option
for HA configured Microsoft Hyper-V server virtual machines in the Move wizard
Ensure the HA configured Microsoft Hyper-V server virtual machine is listed in the Microsoft Failover Cluster
Management tool.
Check whether domain credentials are provided in system sign-in credentials of HP SIM credentials
settings, and the Microsoft Hyper-V server host is registered properly. If the credentials are not entered, enter
them in the system sign-in credentials of HP SIM credentials settings and re-register the Microsoft Hyper-V
server host.
Prefailure alerting reports errors for Citrix XenServer resource pool
The following errors might occur:
Error: This operation cannot be performed because it would invalidate VM
failover planning such that the system would be unable to guarantee to restart
protected VMs after a Host failure.
This error indicates that your resource pool cannot put into maintenance mode as the resource pool contains
protected virtual machines. To unprotect the virtual machine, see the Citrix XenServer documentation, and
then try prefailure alerting.
Error: you attempted to run a VM on a host which doesn’t have access to an SR
needed by the VM. The VM has at least one VBD attached to a VDI in the SR.
This error indicates that your resource pool contains virtual machines in a running state that are not on the
shared storage in the resource pool. Stop the virtual machines, and then attempt prefailure alerts again.
Hyper-V R2 host virtual machines recovered on alternate host using Failed Host
Recovery cannot be powered on
Ensure the cluster shared volume(CSV) is accessible on the alternate host. Configure the network settings of
the virtual machine manually if not set.
HP SIM console integration
The virtual machine guest is not listed on the HP SIM All Systems page
Be sure the virtual machine is configured properly for HP SIM identification. For more information, see the
HP SIM Technical Reference Guide.
Certain Insight Control operations cannot be performed on a virtual machine
Be sure the virtual machine is configured properly for HP SIM identification. For more information, see the
HP SIM Technical Reference Guide.
For unconfigured virtual machines, you can create a template through the HP SIM menus.
The HP SIM console does not identify a server as a virtual machine host
To verify proper system identification in HP SIM, click the Server Name entry in the HP SIM console, and
then be sure that VM Host Details appear on the Identity screen.
If HP SIM does not recognize the virtual machine host, then run an Identify Systems event on the virtual
machine guests by selecting Options→Discovery.
The HP SIM console does not discover a virtual machine host or guest
An unconfigured virtual machine only appears in the VM Host System page. To resolve this issue:
60
Troubleshooting
1.
2.
3.
4.
5.
6.
7.
Replace SNMP properties by selecting Control Panel→Administrative Tools→Services, right click,
and then select Properties.
Click the Security tab.
Add the HP SIM CMS IP address to the Accept SNMP Packets from these hosts box.
In the Default WBEM Settings box, enter the user name and password.
From the HP SIM console, select Options→Discovery.
In the Discovery configuration box, clear the Use discovery filters checkbox, and then click Save.
Perform a discovery of the undiscovered virtual machine hosts and guests.
For information about performing basic HP SIM tasks, see the HP SIM Technical Reference Guide.
HP SIM console identifies a virtual machine guest as an unknown or unmanaged
device
To resolve this issue:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Verify that the correct IP address is assigned to the virtual machine guest and that the virtual machine
guest can be pinged from the HP SIM CMS.
Select Options→Protocol Settings→Global Protocol Settings, and then verify that the IP address
or name of the HP SIM CMS is listed.
On the System page of HP SIM CMS, verify that WBEM is listed in the Product
Description>Management Protocols box.
On the virtual machine guest, select Services, and then verify that WMI service is listed and started.
From the HP SIM CMS Control Panel, select Add or Remove Programs, and then verify that Pegasus
WMI Mapper 2.7 is installed.
On the HP SIM CMS, select Services, and then verify that Pegasus WMI Mapper service is listed and
started.
From the HP SIM console, select Options→Protocol Settings→Global Protocol Settings, and then
verify that the correct user name and password are entered.
Verify the Enable WBEM checkbox is selected.
Verify that the correct user name and password are entered in the Systems Sign-in credentials box
of the guest.
Verify that no virtual machine guest host names begin with the underscore character.
To perform an Identity Systems event on the virtual machine guests, select Options→Discovery.
On the HP SIM CMS, restart the WMI and WMI Mapper services. If the issue appears to be specific
to one virtual machine guest, then restart the WMI service on the specific virtual machine.
Uninstall and reinstall WMI Mapper.
To install WMI on Microsoft Windows NT virtual machine guests, see http://www.microsoft.com/downloads/
details.aspx?familyid=C174CFB1-EF67-471D-9277-4C2B1014A31E
The virtual machine is discovered as an unmanaged system
For VMware and Microsoft Virtual Server virtual machines only, a virtual machine might appear as unmanaged
when you perform a discovery. To resolve this issue:
1.
2.
3.
4.
5.
Log in to HP SIM.
Select to view a collection that shows the unmanaged systems.
Select the unmanaged systems.
Select Select Options→Identify Systems, and then click Run Now.
When identification is complete, return to step 2 to determine if any virtual machines are still listed as
unmanaged. If so, continue to perform steps 3 through 5 until all virtual machines are listed as managed.
After all virtual machines are managed, they remain in that state even if you perform a discovery again.
Uninstalling or retiring an HP SIM CMS
If you are uninstalling or retiring an HP SIM CMS, and you are moving HP SIM to a new CMS, then you
must unregister all virtual machine hosts that are registered to the HP SIM CMS before you perform the
uninstallation.
HP SIM console integration
61
To unregister virtual machine hosts, from the HP SIM toolbar, select Configure→Virtual Machine→Unregister
Virtual Machine Host
If the virtual machine hosts are not unregistered, then an error message appears when you attempt to register
the virtual machine host to the new HP SIM CMS.
If the original HP SIM CMS is not available, then register the virtual machine hosts to the new HP SIM CMS:
1.
2.
Restart the VMM Agents on the virtual machine host.
To register the virtual machine host on the new CMS, select Configure→Virtual Machine→Register
Virtual Machine Host
Hardware
Re-entering the server serial number and product ID
After replacing a system board, you must re-enter the server serial number and the product ID. Improperly
entering the serial number can consume an additional Insight Control license.
To avoid consuming an additional license, see the maintenance and service guide for your server platform
at http://www.docs.hp.com for information about re-entering the server serial number.
Additional resources
The HP ProLiant Servers Troubleshooting Guide provides procedures for resolving common problems, and
a comprehensive course of action for fault isolation and identification, error message interpretation, issue
resolution, and software maintenance.
To obtain the guide, see any of the following sources, and then select the HP ProLiant Servers Troubleshooting
Guide.
62
•
The server-specific Documentation CD
•
The Business Support Center at http://www.hp.com/support. You can find the guide by using the
navigation features on the HP website.
•
The Technical Documentation website at http://www.docs.hp.com. Select Enterprise Servers→
Workstations and Systems Hardware, and then select the appropriate server.
Troubleshooting
5 Support and other resources
Contacting HP
Information to collect before contacting HP
Be sure to have the following information available before you call contact HP:
•
Software product name
•
Hardware product model number
•
Operating system type and version
•
Applicable error message
•
Third-party hardware or software
•
Technical support registration number (if applicable)
How to contact HP technical support
Use the following methods to contact HP technical support:
•
In the United States, see the Customer Service / Contact HP United States website for contact options:
http://welcome.hp.com/country/us/en/contact_us.html
•
In the United States, call 1-800-HP-INVENT (1-800-474-6836) to contact HP by telephone. This service
is available 24 hours a day, 7 days a week. For continuous quality improvement, calls might be recorded
or monitored.
•
In other locations, see the Contact HP Worldwide website for contact options:
http://welcome.hp.com/country/us/en/wwcontact.html
Registering for software technical support and update service
Insight Control suites and select ProLiant Essentials software products include one year of 24 x 7 HP Software
Technical Support and Update Service. This service provides access to HP technical resources for assistance
in resolving software implementation or operations problems.
The service also provides access to software updates and reference manuals, either in electronic form or on
physical media as they are made available from HP. Customers who purchase an electronic license are
eligible for electronic updates only.
With this service, Insight Control and ProLiant Essentials customers benefit from expedited problem resolution
as well as proactive notification and delivery of software updates. For more information about this service,
see the following website:
http://www.hp.com/services/insight
There are two methods for registering:
•
If you received a license entitlement certificate, automated registration for this service takes place upon
online redemption of the license certificate/key.
•
If the license information you received for your product instructs you to register for Software Technical
Support and Update Service, you must follow the instructions in order to be eligible for telephone
support and product updates.
How to use your software technical support and update service
After you have registered, you will receive a service contract in the mail containing the Customer Service
phone number and your Service Agreement Identifier (SAID). You need your SAID when you call for technical
support. Using your SAID, you can also go to the Software Update Manager (SUM) web page to view your
contract online and elect electronic delivery for product updates.
Contacting HP
63
Warranty information
HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty
applies to all Insight Control Management, HP Systems Insight Manager, and ProLiant Essentials products.
HP worldwide customer service contact numbers
HP worldwide customer service contact numbers are available at the following website:
http://welcome.hp.com/country/us/en/wwcontact_us.html
HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources:
•
In the United States, see the HP U.S. service locator website at:
http://www.hp.com/service_locator
•
In other locations, see the Contact HP worldwide website at:
http://welcome.hp.com/country/us/en/wwcontact.html
Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, send a
message to:
docsfeedback@hp.com
Include the document title and manufacturing part number in your message. All submissions become the
property of HP.
Related information
The latest versions of manuals and white papers for HP Insight Control and related products can be
downloaded from the HP Web:
▲
Documents for HP Insight Control and related software can be found at
http://www.hp.com/go/insightdynamics/docs.
For more information about HP Insight Control and related products and solutions, visit the following HP
website:
▲
64
HP Insight Control: http://h18013.www1.hp.com/products/servers/management/index.html
Support and other resources
A Virtual machine events
Viewing virtual machine events
To view all events related to Insight Control virtual machine management, expand the Events→Shared
directory in the left pane of the HP SIM console. Expand All Virtual Machine Management Events.
To view events for a particular virtual machine host or guest, click the host or guest in the HP SIM console,
and then click the Events tab. To view details about a specific event, click the Event Type entry.
To view all completed HP SIM events, from the HP SIM toolbar, click Tasks and Logs→View Task Results.
To view all HP SIM scheduled tasks, click Tasks and Logs→View All Scheduled Tasks.
Viewing virtual machine events
65
Insight Control virtual machine management events
Insight Control virtual machine management Events
Insight Control virtual machine management creates events in HP SIM. These events can be viewed with all
HP SIM events in the Events list.
The following table lists the events created by Insight Control virtual machine management components.
Table A-1 Virtual Machine Management events
66
Event type
Description
Virtual Machine Copy
The virtual machine has copied information.
Virtual Machine Create Template
The virtual machine has created template information.
Abort Virtual Machine Copy
Insight Control virtual machine management did not complete copying a virtual machine.
Finish Virtual Machine Copy
Insight Control virtual machine management has finished copying a virtual machine.
Virtual Machine Suspend
The virtual machine has suspended information.
Virtual Machine Shutdown
The virtual machine has shutdown information.
Virtual Machine Move
The virtual machine has moved information.
Virtual Machine Backup
The virtual machine has backed up information.
Virtual Machine Answer Question
The virtual machine has answered question information.
Virtual Machine FastMove
The virtual machine has recorded FastMove information.
Virtual Machine Deactivate Template
The virtual machine has deactivated a template.
Added a Virtual Machine
A virtual machine has been added from the virtual machine host.
Virtual Machine Guest Threshold
The virtual machine has registered a guest processor event from another machine.
Virtual Machine Restore
The virtual machine has restored information from another machine.
Begin Virtual Machine Copy
Insight Control virtual machine management has begun copying a virtual machine.
Recover Virtual Machine
Virtual machine information has been recovered.
Abort Virtual Machine Move
Insight Control virtual machine management did not complete moving a virtual machine.
Virtual Machine Host Threshold
The virtual machine has registered a host processor event.
Virtual Machine Template
Virtual machine template information has been created.
Virtual Machine Control
Virtual machine control information has been created.
Recover All Virtual Machines
All virtual machine information has been recovered.
Virtual Machine Activate Template
The virtual machine activated the template information.
Virtual Machine Stop
The virtual machine stopped information.
Virtual Machine Start
The virtual machine started information.
Begin Virtual Machine Move
Insight Control virtual machine management has begun moving a virtual machine.
Finish Virtual Machine Move
Insight Control virtual machine management has finished moving a virtual machine.
Virtual Machine Pause
The virtual machine has paused information.
Removed a Virtual Machine
A virtual machine has been removed.
Virtual Machine Reset
The virtual machine has reset information.
Virtual Machine Resume
The virtual machine has resumed information.
Virtual Machine Restart
The virtual machine has restarted.
Virtual Machine Deploy Template
The virtual machine has deployed template information.
Entering Standby Mode Event
This event is received when user manually puts the host in Standby mode. Insight Control
virtual machine management does not listen to this event.
Virtual machine events
Event type
Description
Drs Entering Standby Mode Event
Set the node attribute to disable HP SIM monitoring.
Entered Standby Mode Event
This event is received when you manually put the host in Standby mode. Insight Control
virtual machine management does not listen to this event.
Drs Entered Standby Mode Event
No action occurs as the host is still not in Standby mode. Insight Control virtual machine
management does not listen to this event.
Exiting Standby Mode Event
This event is received when you manually power on the host that is in Standby mode.
Insight Control virtual machine management does not listen to this event.
Drs Exiting Standby Mode Event
No action occurs as the host has not exited from Standby mode. Insight Control virtual
machine management does not listen to this event.
Exited Standby Mode Event
This event is received when user manually powers on the host that is in Standby mode.
Insight Control virtual machine management does not listen to this event.
Drs Exited Standby Mode Event
Set the node attribute to enable its monitoring by HP SIM.
Exit Standby Mode Failed Event
This event is received when you manually power on the host that is in Standby mode.
Insight Control virtual machine management does not listen to this event.
Drs Exit Standby Mode Failed Event
Set the node attribute to enable its monitoring by HP SIM only if the node monitoring is
suspended for that host.
Virtual Machine Host entering standby
mode
The virtual machine host is entering the DPM-initiated Standby mode.
Host entered standby mode.
The virtual machine host has entered the DPM-initiated Standby mode.
Virtual Machine Host exiting standby mode The virtual machine host has failed to exit from the DPM-initiated Standby mode.
failed
Virtual Machine Host exited standby mode The virtual machine host has exited from the DPM-initiated Standby mode successfully.
Error list
The following tables contain error messages that might appear when performing certain menu selections
from HP SIM. To view the table displaying the error message, cause, and solution, press CTRL, and then
click a menu selection.
Table A-2 Configure→Virtual Machine→Register Virtual Machine
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the VMware ESX virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System..
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
A machine was selected without SSH installed
or with an older version of SSH installed. SSH
1.0 or later is required.
To configure and deploy SSH, see the HP SIM
Technical Reference Guide.
No, not allowed by tool definition. The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the VMware ESX virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System..
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
Error list
67
Table A-3 Deploy→ Virtual Machine→ Copy Virtual Machine
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Copying a virtual
machine guest section.
No, not allowed by tool definition. To run Identify system:
The machine selected has not been 1. Select the Windows virtual machine host.
discovered as a server by HP SIM 2. Select Options→Identify System.
.
For more information, see the HP SIM Technical
Unknown or unmanaged appears Reference Guide.
on the HP SIM System Page.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest.
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Copying a virtual
machine guest section.
No, VM <virtual machine name>
must be off or paused.
A running virtual machine guest was selected.
Stop or pause the virtual machine guest.
To stop a virtual machine guest, see the Shutting
down or stopping a virtual machine guest
section.
To pause a virtual machine guest, see the
Suspending or pausing a virtual machine guest
section.
68
Virtual machine events
Table A-4 Deploy→ Virtual Machine→ Move Virtual Machine
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest.
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Copying a virtual
machine guest section.
No, not allowed by tool definition. The machine selected has not been discovered
as a server by HP SIM.
Unknown or unmanaged appears on the
HP SIM System Page.
To run Identify system:
1. Select the Windows virtual machine host.
2. Select Options→Identify System.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest.
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Copying a virtual
machine guest section.
Error list
69
Table A-5 Deploy→ Virtual Machine→ Handle VM host Prefailure Events
Error message
Cause
Solution
No, not a VMware ESX Host.
The machine selected is not a VMware ESX
Server.
Select a VMware ESX Server.
No, View Details. When you click
View Details, the following
message appears:
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
For more information, see the Recovering virtual
machines of a failed host on a VMware ESX
Server, Citrix XenServer or Microsoft Hyper-V
R2 server section.
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host by HP SIM.
1. Select the virtual machine host.
Virtual Machine Host does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine host.
For more information, see the Recovering virtual
machines of a failed host on a VMware ESX
Server, Citrix XenServer or Microsoft Hyper-V
R2 server section.
No, not allowed by tool definition. The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host by HP SIM.
1. Select the virtual machine host.
Virtual Machine Host does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine host.
For more information, see the Recovering virtual
machines of a failed host on a VMware ESX
Server, Citrix XenServer or Microsoft Hyper-V
R2 server section.
70
Virtual machine events
Table A-6 Deploy→ Virtual Machine→ Backups→ Create Virtual Machine Backup
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest.
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Creating a virtual
machine guest backup section.
No, not allowed by tool definition. The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest.
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Creating a virtual
machine guest backup section.
Error list
71
Table A-7 Deploy→ Virtual Machine→ Backups→ Restore Last Virtual Machine Backup
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine guest by HP SIM.
1. Select the virtual machine guest.
Virtual Machine Guest does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine guest.
For more information, see the Restoring a virtual
machine guest backup section.
72
Virtual machine events
Table A-8 Configure→ Virtual Machine→ Unregister Virtual Machine Host
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host by HP SIM.
1. Select the virtual machine host.
Virtual Machine Host does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine host.
For more information, see the Unregistering
virtual machine hosts section.
No, not allowed by tool definition. The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host by HP SIM.
1. Select the virtual machine host.
Virtual Machine Host does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine host.
For more information, see the Unregistering
virtual machine hosts section.
Error list
73
Table A-9 Configure→ Virtual Machine→ Set Alternate Virtual Machine Host
Error message
Cause
Solution
No, not a VMware ESX Virtual
Machine.
The machine selected is not a VMware ESX
Server virtual machine guest.
Select a VMware ESX Server virtual machine
guest.
For more information, see the Setting the
alternate virtual machine host section.
No, View Details. When you click
View Details, the following
message appears:
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host by HP SIM.
1. Select the virtual machine host.
Virtual Machine Host does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine host.
For more information, see the Setting the
alternate virtual machine host section.
No, not allowed by tool definition. The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
3. For more information, see the HP SIM
Technical Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host by HP SIM.
1. Select the virtual machine host.
Virtual Machine Host does not appear 2. Select Options→Identify System.
as the system subtype on the machine system
For more information, see the HP SIM Technical
page.
Reference Guide.
Select a virtual machine host.
For more information, see the Setting the
alternate virtual machine host section.
74
Virtual machine events
Table A-10 Configure→ Virtual Machine→ Set Performance Thresholds
Error message
Cause
No, View Details. When you click
View Details, the following
message appears:
The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine host.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
This tool cannot run on
<server> as it does not
pass the conditions
required for running it.
Solution
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host or a virtual machine 1. Select the virtual machine host.
guest by HP SIM.
2. Select Options→Identify System.
Neither Virtual Machine Host nor
For more information, see the HP SIM Technical
Virtual Machine Guest appears as the Reference Guide.
system subtype on the machine system page.
Select a virtual machine host or virtual machine
guest.
For more information, see the Setting or
removing the performance threshold section.
No, not allowed by tool definition. The machine selected has not been discovered To run Identify system:
as a server by HP SIM.
1. Select the Windows virtual machine.
Unknown or unmanaged appears on the
2. Select Options→Identify System.
HP SIM System Page.
For more information, see the HP SIM Technical
Reference Guide.
The machine selected has not been discovered To run Identify system:
as a virtual machine host or a virtual machine 1. Select the virtual machine host.
guest by HP SIM.
2. Select Options→Identify System.
Neither Virtual Machine Host nor
For more information, see the HP SIM Technical
Virtual Machine Guest appears as the Reference Guide.
system subtype on the machine system page.
Select a virtual machine host or virtual machine
guest.
For more information, see the Setting or
removing the performance threshold section.
Error list
75
76
B vCenter and VMware ESX Server host events
The following table lists how various events from VMware vCenter 3.x and later and are received and
handled using Insight Control virtual machine management 6.0.
Table B-1 vCenter and VMware ESX Server host events
Event type
Description
EnteredMaintenanceModeEvent
This event records that the host has entered maintenance mode. A host in this mode has no
running virtual machines and no provisioning operations are occurring.
ExitMaintenanceModeEvent
This event records that the host is no longer in maintenance mode.
HostAddedEvent
This event records the addition of a host to vCenter.
HostConnectedEvent
This event records a successful host connection.
HostDasDisabledEvent
This event records when High Availability (HA) has been disabled on a host.
HostDasEnabledEvent
This event records when HA has been enabled on a host.
HostDisconnectedEvent
This event records a disconnection from a host.
HostRemovedEvent
This event records the removal of a host from vCenter.
HostShutdownEvent
This event records the shutdown of a host.
VmClonedEvent
This event records the completion of a virtual machine cloning operation.
VmConnectedEvent
This event records that a virtual machine is connected.
VmCreatedEvent
This event records that a virtual machine was successfully created.
VmDeployedEvent
This event records the completion of a virtual machine deployment operation.
VmDisconnectedEvent
This event records that a virtual machine disconnected.
VmGuestRebootEvent
This is a virtual machine guest reboot request event.
VmGuestShutdownEvent
This is a virtual machine guest shutdown request event.
VmGuestStandbyEvent
This is a virtual machine guest standby request event.
VmMigratedEvent
This event records a virtual machine migration.
DrsVmMigrateEvent
This event records a virtual machine migration that was recommended by DRS.
VmOrphanedEvent
This event records a virtual machine for which no host is responsible.
VmPoweredOffEvent
This event records when a virtual machine finished powering off.
VmPoweredOnEvent
This event records when a virtual machine finished powering on.
VmReconfiguredEvent
This event records a reconfiguration of the virtual machine.
VmRegisteredEvent
This event records that a virtual machine was successfully registered.
VmRelocateSpecEvent
This event is the base event for relocate and clone base events.
VmRelocatedEvent
This event records the completion of virtual machine relocation.
VmRemovedEvent
This event records a virtual machine removed from vCenter management.
VmRenamedEvent
This event records the renaming of a virtual machine.
VmResourcePoolMovedEvent
This event records when a virtual machine is moved from one resource pool to another.
VmResourceReallocatedEvent
This event records a change in resource allocation of a virtual machine.
VmSuspendedEvent
This event records when a virtual machine finished suspending.
ResourcePoolCreatedEvent
This event records when a new resource pool is created.
ResourcePoolDestroyedEvent
This event records when a resource pool is destroyed.
ResourcePoolMovedEvent
This event records when a resource pool is moved.
ResourcePoolReconfiguredEvent
This event records when a resource pool configuration is changed.
77
Event type
Description
ResourceViolatedEvent
This event records when a conflict with a resource configuration of a resource pool is detected.
Entering Standby Mode Event
This event is received when user manually puts the host in Standby mode. Insight Control virtual
machine management does not listen to this event.
Drs Entering Standby Mode Event
Set the node attribute to disable HP SIM monitoring.
Entered Standby Mode Event
This event is received when you manually put the host in Standby mode. Insight Control virtual
machine management does not listen to this event.
Drs Entered Standby Mode Event
No action occurs as the host is still not in Standby mode. Insight Control virtual machine
management does not listen to this event.
Exiting Standby Mode Event
This event is received when you manually power on the host that is in Standby mode. Insight
Control virtual machine management does not listen to this event.
Drs Exiting Standby Mode Event
No action occurs as the host has not exited from Standby mode. Insight Control virtual machine
management does not listen to this event.
Exited Standby Mode Event
This event is received when user manually powers on the host that is in Standby mode. Insight
Control virtual machine management does not listen to this event.
Drs Exited Standby Mode Event
Set the node attribute to enable its monitoring by HP SIM.
Exit Standby Mode Failed Event
This event is received when you manually power on the host that is in Standby mode. Insight
Control virtual machine management does not listen to this event.
Drs Exit Standby Mode Failed Event
Set the node attribute to enable its monitoring by HP SIM only if the node monitoring is
suspended for that host.
Virtual Machine Host entering
standby mode
The VM Host is entering the DPM-initiated Standby mode.
Host entered standby mode.
The VM Host has entererd the DPM-initiated Standby mode.
Virtual Machine Host exiting standby The VM Host has failed to exit from the DPM-initiated Standby mode.
mode failed
78
Virtual Machine Host exited standby
mode
The VM Host has exited from the DPM-initiated Standby mode successfully.
vmmControl
This event records virtual machine control information.
vmmAnswer
This event records virtual machine answer question information.
vmmPause
This event records virtual machine pause information.
vmmReset
This event records virtual machine reset information.
vmmRestart
This event records virtual machine restart information.
vmmSnapshot
This event records virtual machine create snapshot information.
vmmResume
This event records virtual machine resume information.
vmmShutdown
This event records virtual machine shutdown information.
vmmStart
This event records virtual machine start information.
vmmStop
This event records virtual machine stop information.
vmmSuspend
This event records virtual machne suspend information.
vmmBackup
This event records virtual machine backup information
vmmCopy
This event records virtual machine copy information
vmmCreateTemplate
This event records virtual machine create template information.
vmmDeployTemplate
This event records virtual machine deploy template information.
vmmCreateLinkedClone
This event records virtual machine create linked clone information.
vmmFastmove
This event records virtual machine SAN move information.
vmmLivemove
This event records virtual machine LiveMove Information.
vmmQuickmove
This event records virtual machine QuickMove Information.
vCenter and VMware ESX Server host events
Event type
Description
vmmMove
This event records virtual machine move information.
vmmRestore
This event records virtual machine restore information.
vmmTemplate
This event records virtual machine template information.
vmmLinkedClone
This event records virtual machine linked clone information.
vmmActivateTemplate
This event records virtual machine activate template information.
vmmDeactivateTemplate
This event records virtual machine deactivate template information.
vmmRecoverVM
This event records recover virtual machine information.
vmmRecoverAllVMs
This event records recover all virtual machines information.
vmmMigrate
This event records VirtualCenter virtual machine migration information.
vmmCustomize
This event records virtual machine customization information.
vmmIdentifyServer
This event records HP SIM identification information.
vmmRegisterHost *
This event records virtual machine host registration information (* indicates that the event is
not being generated currently).
vmmUnregisterHost *
This event records virtual machine host unregistration information (* indicates that the event
is not being generated currently).
NodeExists
A node cannot be created in HP SIM because a node with the same name already exists.
vmmVMThreshold
Virtual machine guest processor event.
vmmHostThreshold
Virtual machine host processor event.
vmmVMCpuThreshold
Virtual machine guest processor threshold event.
vmmHostCpuThreshold
Virtual machine host processor threshold event.
vmmVMMemoryThreshold
Virtual machine guest memory utilization threshold event.
vmmHostMemoryThreshold
Virtual machine host memory utilization threshold event.
vmmVMDiskThreshold
Virtual machine guest disk utilization threshold event.
vmmHostDiskThreshold
Virtual machine host disk utilization threshold event.
vmmVMNetworkThruputThreshold
Virtual machine guest network throughput threshold event.
vmmHostNetworkThruputThreshold
Virtual machine host network throughput threshold event.
vmmVMStorageThruputThreshold
Virtual machine guest storage throughput threshold event.
vmmHostStorageThruputThreshold
Virtual machine host storage throughput threshold event.
vmmVMDiskUtilizationThreshold
Virtual machine guest disk utilization threshold event.
vmmAdd
A virtual machine has been added.
vmmRemove
A virtual machine has been removed.
vmmAbortCopy
Insight Control virtual machine management did not complete copying a virtual machine.
vmmFinishCopy
Insight Control virtual machine management has finished copying a virtual machine.
vmmBeginCopy
Insight Control virtual machine management has begun copying a virtual machine.
vmmAbortMove
Insight Control virtual machine management did not complete moving a virtual machine.
vmmFinishMove
Insight Control virtual machine management has finished moving a virtual machine.
vmmBeginMove
Insight Control virtual machine management has begun moving a virtual machine.
vmmAbortLinkedClone
Insight Control virtual machine management did not complete creating linked clone of the
virtual machine.
vmmFinishLinkedClone
Insight Control virtual machine management has finished creating Linked Clone of the virtual
machine.
79
80
Event type
Description
vmmBeginLinkedClone
Insight Control virtual machine management has begun creating Linked Clone of the virtual
machine.
vmmEdit
Insight Control virtual machine management has changed the VM configuration
vmmUnregisterVM
This event reports that Insight Control virtual machine management has unregistered virtual
machines or any exceptions.
vCenter and VMware ESX Server host events
C Customizing virtual machines
HP SIM permissions
For operations that involve two operating systems, authorization must be granted on both systems. For
example, to permit a virtual machine to be copied to another host, authorization to copy virtual machines
must be granted on both the virtual machine and the destination virtual machine host.
As with any HP SIM tool, you can authorize users to use a tool on a certain system. For example, a user
might be allowed to start and stop virtual machines in a training lab while being restricted from using other
tools on those virtual machines.
Because unconfigured virtual machines are not listed in the All Systems table, it is not possible to assign
authorizations on those virtual machines. To run tools on unconfigured virtual machines, the user must have
the appropriate authorization on the virtual machine host.
For more information on permissions in HP SIM, see the HP SIM Technical Reference Guide.
Creating a system collection
HP SIM enables you to create system collections based on system properties, such as system type, product
model, operating system version, or contact information. You can use this feature to organize your virtual
machines into one or multiple collections to simplify access and organization.
IMPORTANT:
You must have administrative rights in HP SIM to create system collections.
To set up system properties for a single system, on the System Page Tools and Links tab, click Edit
System Properties.
To set up system properties for multiple systems, select Options→System Properties→Set System
Properties.
HP SIM permissions
81
82
Glossary
Citrix XenServer
A server virtualization platform that offers near bare-metal virtualization performance for virtualized
server and client operating systems. Citrix XenServer uses the Xen hypervisor to virtualize each
server on which it is installed, enabling each to host multiple Virtual Machines simultaneously
with guaranteed performance.
CMS
HP SIM Central Management Server.
guest operating
system
A distinct operating system instance running in a virtual machine.
host operating
system
An operating system that is the foundation for a virtual machine.
HP SIM
HP Systems Insight Manager.
legacy operating
systems
An older operating system, often incompatible with current hardware. Virtual machines permit a
legacy operating system to run on new hardware.
resource pool
A resource pool is a collection of multiple similar XenEnterprise servers that are connected together
in a unified pool of resources. These connected servers share remote storage and common
networking connections. A resource pool enables for XenMotion (Live Migration) of virtual
machines, shared configurations, and automatic placement of virtual machines.
total estimated
transport volume
The total volume, consisting of several disks and configuration files.
virtual machine
(VM)
The emulation of a complete hardware system from processor to network card in a self contained,
isolated software environment, enabling the simultaneous operation of otherwise incompatible
systems.
virtualization
A method of grouping computing resources together that allows them to be accessed in ways
that provide benefits over the original configuration. Virtualized resources generally improve
computing power and data storage.
VMM
HP Insight Control virtual machine management.
VMware ESX
Server
The VMware Red Hat Linux-based host operating system that provides a virtual machine solution.
83
84
Index
providing feedback, 64
reporting errors in, 64
A
accessing System Page, 17
adding licenses, 15
Agentless Management, 13
B
blank page appears when launching Insight Control virtual
machine management from HP SIM, 55
C
central management server
retiring, 61
uninstalling, 61
Citrix XenServer
configuring xapi port, 18
CMS (see central management server)
color codes, performance, 49
commons-cli-1.0.jar file fails to copy, 52
components, Insight Control virtual machine management,
11
configuration
SNMP properties, 60
troubleshooting, 53, 62
configured virtual machine hosts, 22
configuring
polling frequency for virtual machine status checks, 39
VMware vCenter servers, 17
WMI Mapper proxy, 18
xapi port, 18
console integration for HP SIM, 60
controls, Insight Control virtual machine management, 23
copied Xen virtual machine guest does not start on the
destination host, 58
copying virtual machine guests
Linux, 30
Windows, 30
creating
critical VM host collection, 44
system collection, 81
virtual machine guest backups, 36
virtual machine guest templates, 34
critical status displays for a virtual machine host, 55
customer service contact numbers, 64
customizing virtual machines, 81
D
database server not started properly, 51
deleting
virtual machine guests, 36
demo licensing troubleshooting, 57
deploying
virtual machine guests, 35
discovery
HP SIM, 60
documentation
E
error list, 67
error message "Unknown to VMM" appears when
performing copy operation on virtual machine, 57
error messages, 51
events
automatic handling of, 42
Insight Control virtual machine management, 66
setting up prefailure, 42
vCenter, 77
Virtual Machine Management, 67
VMware ESX Server, 77
F
failed host recovery, 42
fails on Citrix XenServer, 59
FAQs, 51
feedback
email address for documentation, 64
firewalls, 54
H
handling prefailure events
task does not progress, 58
hardware
troubleshooting, 62
host
licensing, 15
host registration fails, 53
HP authorized resellers, 64
HP SIM
documentation, 64
HP SIM console
integration, 12
remote, 59
HP Systems Insight Manager
console integration, 60
console system identification, 60
discovery, 60
events, 65, 66
icons, 12
identify systems, 60
overview, 11
permissions, 81
HP technical support, 63
I
icons, 12
identification in HP SIM, 60
Insight Control virtual machine management
configuring on a Microsoft Cluster Server, 18
controls, 23
tools, 23
85
Insight Control virtual machine management installed on
only one CMS, 51
installation
fails to proceed, 51
troubleshooting, 51
uninstalling, 52
L
launching
remote access, 27
Remote Console, 27
Remote Desktop, 28
System Center Virtual Machine Manager, 29
vCenter, 29, 39
licenses
adding, 15
overview, 15
troubleshooting demo licenses, 57
virtual machine host, 15
licensing
Insight Control virtual machine management, 15
licensing Insight Control virtual machine management
through the Insight Control license manager, 15
Linux
copying virtual machine guests, 30
moving virtual machine guests, 32
resuming virtual machine guests, 26
shutting down virtual machine guests, 26
starting virtual machine guests, 26
stopping virtual machine guests, 26
Live Move fails after a SAN move, 56
orphan managed systems created in the CMS, 59
overview
Insight Control virtual machine management, 11
licensing, 15
P
performance information does not appear, 53
performance threshold
removing, 39
setting, 39
permissions in HP SIM, 81
polling frequency, 39
ports
configuring, 54
troubleshooting, 59
prefailure events, 42
product ID, re-entering, 62
Q
Quick Move option not displayed in Move wizard, 60
R
menus do not appear in toolbar, 52
Microsoft Cluster Server, configuring Insight Control virtual
machine management, 18
Microsoft DNS Server does not map the host name to
DHCP-generated IP addresses, 54
Microsoft Hyper-V Server
Guest System page, 29
Host System page, 29
Microsoft Hyper-V server
configuring WMI Mapper proxy, 18
Microsoft Hyper-V server hosts fail to register, 54
migrating
virtual machine guest templates, 34
virtual machine guests, 34
mouse stops working after installation, 52
moved Xen virtual machine guest does not start on the
destination host, 58
moving virtual machine guests
Linux, 32
Windows, 32
multisystem aware tools, 50
re-entering
product ID, 62
server serial numbers, 62
recovering virtual machines of a failed host, 38
recovery
failed hosts, 42
scheduling for virtual machine of failed hosts, 44
setting up feature, 43
register
for technical support and update service, 63
remote access, launching, 27
Remote Console, launching, 27
Remote Desktop
error occurs when clicked, 57
launching, 28
removing
performance threshold, 39
virtual machine hosts, 39
reporting documentation errors
email address, 64
resetting virtual machine guests, 27
resource allocation, 49
restarting
virtual machine guests, 27
restoring
most recent virtual machine guest backups, 38
using a backup fails, 57
virtual machine guest backups, 37
resuming virtual machine guests
Linux, 26
Windows, 26
retiring CMS, 61
O
S
operations complete without confirmation using vCenter
Server 2.5, 59
org.mortbay.jetty.jar file fails to copy, 52
SAID agreement, 63
scheduling
recovery of virtual machine hosts, 44
M
86
Index
SCVMM (see System Center Virtual Machine Manager)
server
re-entering serial number, 62
Set Alternate host feature
handling automatic prefailure events, 42
handling semi-automatic prefailure events, 42
setting
performance threshold, 39
virtual machine host, 40
setting up
prefailure events, 42
recovery feature, 43
shutting down virtual machine guests
Linux, 26
Windows, 26
slow response time on virtual machine host, 56
SNMP properties, 60
starting virtual machine guests
Linux, 26
Windows, 26
status column icons, 12
stopping virtual machine guests
Linux, 26
Windows, 26
support service, 63
suspending virtual machine guests, 26
System Center Virtual Machine Manager, launching, 29
system collection, creating, 81
system information not displayed, 55
System Page
accessing, 17
overview, 17
System tab
virtual machine guest, 21
virtual machine host, 19
T
technical support service, 63
threshold settings, 49
tools, Insight Control virtual machine management, 23
transport operation fails after restarting Insight Control
virtual machine management, 57
troubleshooting, 51
blank page appears when launching Insight Control
virtual machine management from HP SIM, 55
commons-cli-1.0.jar file fails to copy, 52
configuration, 62
copied Xen virtual machine guest does not start on the
destination host, 58
critical status displays in Insight Control virtual machine
management, 55
demo licensing, 57
error message "Unknown to VMM" appears when
performing copy operation on virtual machine, 57
error occurs when Remote Desktop is clicked, 57
failed host recovery on Citrix XenServer fails, 59
handling virtual machine host prefailure events task does
not progress, 58
hardware, 61, 62
HP SIM console integration, 60
inability to perform certain functions, 60
Insight Control virtual machine management, 54
Insight Control virtual machine management can only
be installed on one CMS, 51
Insight Control virtual machine management does not
detect virtual machines on mapped drives, 53
Insight Control virtual machine management does not
display system information, 55
Insight Control virtual machine management functions,
57
Insight Control virtual machine management host
registration fails, 53
Insight Control virtual machine management items not
removed from HP SIM toolbar with uninstallation, 53
internal service error during move or copy operation,
58
Live Move fails after SAN move, 56
menu selection errors, 67
menus not appearing, 52
Microsoft DNS Server does not map the host name to
a DHCP-generated IP addresses, 54
Microsoft Hyper-V server hosts fail to register, 54
mouse does not work after installation, 52
moved Xen virtual machine guest does not start on the
destination host, 58
moving virtual machines with certain disk types, 58
operations do not complete using vCenter Server 2.5,
59
org.mortbay.jetty.jar file fails to copy, 52
orphan managed systems created in the CMS, 59
performance information does not appear for Citrix
XenServer and virtual machines, 53
product ID, 62
Quick Move option not displayed in Move wizard, 60
recovery of virtual machine because of incompatible
hardware configurations, 57
restore from backup fails, 57
serial number, 62
slow response time, 56
transport operation fails after restarting Insight Control
virtual machine management, 57
uninstalling using Add or Remove Programs, 52
virtual host or guest not discovered, 60
virtual machine discovered as unmanaged, 61
virtual machine guest appears multiple times, 56
virtual machine guest information is inaccessible from
Insight Control virtual machine management, 56
virtual machine guest is not listed on HP SIM All Systems
page, 60
virtual machine host, 60
virtual machine host appears multiple times, 56
virtual machine status is not updated, 56
virtual machine unknown, 61
VMMclient.jar file fails to copy, 52
VMotion fails, 56
troubleshooting functions, 57
87
U
unable to move virtual machines with certain disk types,
58
unconfigured virtual machine hosts, 22
uninstalling
CMS, 61
items not removed from HP SIM toolbar, 53
using the Add or Remove Programs, 52
uninstalling does not remove items from HP SIM toolbar,
53
unregistering virtual machine hosts, 18
updating HP SIM certificate on Insight Control virtual
machine management, 19
V
VC (see vCenter)
vCenter (see virtual network computing)
launching, 29
vCenter Server
information, 30
viewing, 30
virtual machine guest appears multiple times, 56
vCenter servers, configuring, 17
viewing virtual machine events, 65
virtual machine devices
unavailable after a copy, 58
unavailable after a move, 58
virtual machine guest information is inaccessible, 56
virtual machine guests
appear multiple times in VMware vCenter Server, 56
copying, 58
copying Linux, 30
copying Windows, 30
creating backups, 36
creating templates, 34, 35, 36
deleting, 36
deploying, 35
discovered as unknown, 61
discovered as unmanaged, 61
discovery, 60
icons, 12
information is inaccessible, 56
migrating, 34
mismatched in HP SIM and vCenter Server, 56
moving, 58
moving Linux, 32
moving Windows, 32
not listed on HP SIM All Systems page, 60
recovering from a failed host, 38
resetting, 27
restarting, 27, 58
restoring backups, 37
restoring most recent backup, 38
resuming Linux, 26
resuming Windows, 26
shutting down, 58
shutting down Linux, 26
shutting down Windows, 26
starting Linux, 26
88
Index
starting Windows, 26
stopping Linux, 26
stopping Windows, 26
suspending, 26
System tab, 21
viewing events, 65
viewing performance, 48
virtual machine hosts,
appear multiple times in Insight Control virtual machine
management, 56
configured, 22
critical status displays, 55
customizing, 81
discovery, 60
experience slow response time, 56
icons, 12
licensing, 15
performance, 47
removing, 39
scheduling recovery, 44
setting, 40
System tab, 19
unconfigured, 22
unregistering, 18
virtual machines
performance information does not display, 53
polling frequency, 39
status is not updating, 56
virtual machines not detected on mapped drives, 53
virtual network computing, launching, 39
VM column, Insight Control virtual machine management,
12
VMM Agent
restarting, 54
VMMclient.jar file fails to copy, 52
vmmsimtools.jar file fails to copy, 52
VMotion fails because of mismatched names, 56
VMware ESX Server
Guest System page, 46
Host System page, 30
VSE
documentation, 64
W
warranty information, 64
websites
HP authorized resellers, 64
HP technical support, 63
WMI Mapper proxy, configuring, 18
X
xapi port, configuring, 18
Download PDF
Similar pages