hp proliant essentials virtual machine management pack ...h10032.valid license from hp required for...

HP ProLiant Essentials Virtual Machine Management Pack

User Guide

July 2005 (Third Edition) Part Number 380094-003

Product Version 1.11

© Copyright 2004, 2005 Hewlett-Packard Development Company, L.P.

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.

Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Linux is a U.S. registered trademark of Linus Torvalds. Oracle is a registered US trademark of Oracle Corporation, Redwood City, California.

HP ProLiant Essentials Virtual Machine Management Pack User Guide

July 2005 (Third Edition) Part Number 380094-003 Product Version 1.11

HP ProLiant Essentials Virtual Machine Management Pack User Guide iii

Contents

About this guide Where to go for additional help.................................................................................................................. vii

Website ................................................................................................................................................ vii Telephone numbers............................................................................................................................. viii

Chapter 1 Introduction Overview ................................................................................................................................................... 1-1 Infrastructure ............................................................................................................................................. 1-1 HP Systems Insight Manager console integration..................................................................................... 1-2

Chapter 2 Requirements HP SIM CMS ............................................................................................................................................ 2-1 Virtual machine host ................................................................................................................................. 2-2 Virtual machine guest................................................................................................................................ 2-2

Chapter 3 Installation and configuration Virtual Machine Management Pack installation ....................................................................................... 3-1

Installing from the Management CD .................................................................................................. 3-1 Installing from the download website................................................................................................. 3-4 Installation locations ........................................................................................................................... 3-5 Installed components .......................................................................................................................... 3-5

Post-installation configuration tasks.......................................................................................................... 3-6 Installing OpenSSH ............................................................................................................................ 3-6 Configuring OpenSSH........................................................................................................................ 3-6 Deploying the VMM agent ................................................................................................................. 3-7 Installing Microsoft Virtual Server Additions or VMware Tools....................................................... 3-8

Virtual Machine Management Pack upgrade ............................................................................................ 3-9 Upgrading the VMM agent................................................................................................................. 3-9

Chapter 4 Licensing Overview ................................................................................................................................................... 4-1 Free licenses .............................................................................................................................................. 4-1 Licensing preparation ................................................................................................................................ 4-1 Licensing options ...................................................................................................................................... 4-2

Contents

iv HP ProLiant Essentials Virtual Machine Management Pack User Guide

Licensing virtual machine hosts.................................................................................................................4-2 Adding licenses ...................................................................................................................................4-2 Applying licenses to virtual machine hosts .........................................................................................4-3

Chapter 5 Using the Virtual Machine Management Pack Accessing the Virtual Machine Management Pack console ......................................................................5-1

The Virtual Machine Management Pack homepage............................................................................5-2 The Virtual Machine Management Pack host console ........................................................................5-3 The Virtual Machine Management Pack guest console ......................................................................5-4

Using the Virtual Machine Management Pack console .............................................................................5-6 Starting or resuming a virtual machine guest ......................................................................................5-7 Shutting down or stopping a virtual machine guest ............................................................................5-7 Pausing a virtual machine guest ..........................................................................................................5-8 Resetting or restarting a virtual machine guest ...................................................................................5-8 Copying a virtual machine guest .........................................................................................................5-9 Moving a virtual machine guest ........................................................................................................5-10 Backing up a virtual machine guest...................................................................................................5-11 Creating a virtual machine guest template ........................................................................................5-12 Launching the virtual machine remote console.................................................................................5-12 Restarting the VMM agent ................................................................................................................5-13 Restoring a virtual machine guest .....................................................................................................5-13 Deploying a virtual machine guest template .....................................................................................5-14

Viewing Virtual Machine Management Pack logs ..................................................................................5-15 Event log............................................................................................................................................5-15 Running task log................................................................................................................................5-17 Scheduled VM backups.....................................................................................................................5-18

Appendix A Troubleshooting Installation ................................................................................................................................................A-3

The Virtual Machine Management Pack cannot be installed on a virtual machine ...........................A-3 In an environment using multiple HP SIM CMSs, the Virtual Machine Management Pack can only be installed on one CMS......................................................................................................A-3 “Installed, refer to hpvmm.log for the installation status” appears during installation ......................A-3 “HP SIM service or SQL service is not running. Cancel the installation.” appears during installation...............................................................................................................................A-3 The Virtual Machine Management Pack 1.11 cannot be installed over a newer version...................A-4 Uninstalling the Virtual Machine Management Pack and Server Migration Pack.............................A-4 "The process cannot access the file because it is being used by another process" message appears during uninstallation..............................................................................................................A-7

Configuration ............................................................................................................................................A-7 Virtual Machine Management Pack menu items are not removed from the HP SIM toolbar with the Virtual Machine Management Pack uninstallation ..............................................................A-7 The Virtual Machine Management Pack might not detect virtual machines located on mapped network drives ....................................................................................................................................A-7 Configuring the Virtual Machine Management Pack with a firewall.................................................A-8 Virtual machine hosts cannot be licensed ..........................................................................................A-9

Contents

HP ProLiant Essentials Virtual Machine Management Pack User Guide v

VMM agent ............................................................................................................................................ A-10 VMM agent installation fails ........................................................................................................... A-10 VMM agent registration fails on VMware ESX Server virtual machine host ................................. A-10 VMM agent registration fails on virtual machine host configured with multiple IP addresses....... A-11 The virtual machine host must be re-registered if the IP address or name of the virtual machine host is changed................................................................................................................................. A-12 “Agent Registration failed” appears in the HP SIM task log after upgrading the VMM agent....... A-13

The Virtual Machine Management Pack console................................................................................... A-13 Virtual machine host and guests do not appear in the Virtual Machine Management Pack console .................................................................................................................................... A-13 The Virtual Machine Management Pack console does not display the system name, system IP address, and operating system.......................................................................................................... A-13 Critical status is displayed for a virtual machine host in the Virtual Machine Management Pack console .................................................................................................................................... A-14 A blank page appears when launching the Virtual Machine Management Pack console from HP SIM ................................................................................................................................... A-14 The status displayed in the left pane of the Virtual Machine Management Pack console does not match the status displayed in the right pane .................................................................................... A-14 Virtual machine status is not updated .............................................................................................. A-14 Virtual machine guest information becomes inaccessible in the Virtual Machine Management Pack console............................................................................................................... A-15 A virtual machine host appears in the Virtual Machine Management Pack console multiple times .................................................................................................................................. A-15 The Virtual Machine Management Pack console displays “No virtualization layer available for this host”..................................................................................................................................... A-15

Virtual Machine Management Pack functions ....................................................................................... A-15 Using a virtual machine host not managed by the Virtual Machine Management Pack as a template/backup repository.............................................................................................................. A-15 “HTTP ERROR: 500 Internal Server Error” appears during a Virtual Machine Management Pack move or copy operation..................................................................................... A-15 The Virtual Machine Management Pack cannot move virtual machines with certain disk types.... A-16 Virtual machine files are not deleted after a move .......................................................................... A-16 Virtual machine devices might not be available after a copy or move ............................................ A-16 A shutdown or restart operation fails or does not complete............................................................. A-16 Launching the remote console from the Virtual Machine Management Pack console might fail ... A-16

HP SIM console integration ................................................................................................................... A-17 The HP SIM console does not identify a server as a virtual machine host ...................................... A-17 The HP SIM console does not discover a virtual machine host or guest ......................................... A-17 The HP SIM console identifies a virtual machine guest as an Unknown or Unmanaged device .... A-18 Linux virtual machine guest association is not displayed in the HP SIM console........................... A-18 The Virtual Machine Management Pack version displayed in HP SIM is incorrect ....................... A-18

Additional resources............................................................................................................................... A-19

Glossary

Index

HP ProLiant Essentials Virtual Machine Management Pack User Guide vii

About this guide

This user guide provides step-by-step instructions for installing and using the HP ProLiant Essentials Virtual Machine Management Pack.

Where to go for additional help

In addition to this guide, the following information sources are available.

For additional information about Virtual Machine Management Pack, refer to:

• http://www.hp.com/go/vmm

• HP ProLiant Essentials Virtual Machine Management Pack Quick Setup Poster

• HP ProLiant Essentials Virtual Machine Management Pack 1.11 and Server Migration Pack 1.11 Support Matrix

For additional information about Server Migration Pack, refer to:

• http://www.hp.com/go/smp

• HP ProLiant Essentials Server Migration Pack Quick Setup Poster

• HP ProLiant Essentials Server Migration Pack User Guide

For additional information about HP Systems Insight Manager, refer to:

• http://www.hp.com/go/hpsim

• HP Systems Insight Manager Installation and User Guide

• HP Systems Insight Manager Help Guide

Website

Information about Virtual Machine Management Pack and the latest updates is available at http://www.hp.com/servers/go/vmm.

http://www.hp.com/wildginger

http://www.hp.com/go/vmm


http://www.hp.com/go/smp

http://www.hp.com/servers/manage

http://www.hp.com/go/hpsim



http://www.hp.com/servers/go/vmm

About This Guide

viii HP ProLiant Essentials Virtual Machine Management Pack User Guide

Telephone numbers

For the name of your nearest HP authorized reseller:

• In the United States, call 1-800-345-1518.

• In Canada, call 1-800-263-5868.

For HP technical support:

• In North America:

— Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored.

— If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website at http://www.hp.com.

• Outside North America, call the nearest HP Technical Support Phone Center. For telephone numbers for worldwide Technical Support Centers, refer to the HP website at http://www.hp.com/support.

http://www.hp.com/

http://www.hp.com/

http://www.hp.com/support

HP ProLiant Essentials Virtual Machine Management Pack User Guide 1-1

1 Introduction

Overview

The HP ProLiant Essentials Virtual Machine Management Pack adds virtual machine management capability within HP System Insight Manager (HP SIM) 4.2 SP2 or later.

The Virtual Machine Management Pack provides the following benefits:

• Integration with the HP SIM console to manage the virtual machine environment

• Simplified deployment and operation of virtual machines with Microsoft® Virtual Server and VMware

• Reduced cost and complexity in server consolidation projects

• Faster response times to changing business demands

Virtual Machine Management (VMM) Pack 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 contemporary virtualization software platforms and industry-standard servers.

The Virtual Machine Management Pack is integrated completely within HP SIM to provide ease of use, installation, and maintenance. All requirements and practices for proper operation of HP SIM must be observed for the Virtual Machine Management Pack. For detailed information about requirements for and using HP SIM, refer to the HP Systems Insight Manager Installation and User Guide.

Infrastructure

The Virtual Machine Management Pack includes the following components, which are installed and set up during the Virtual Machine Management Pack installation:

• Virtual Machine Management Service—Resides on the HP SIM server and controls the internal functions of the Virtual Machine Management Pack.

• Virtual Machine Management Pack Console—As the user interface for the Virtual Machine Management Pack, provides access to the virtual machine monitoring and control functions. The GUI can be accessed locally or remotely using industry-standard Web browsers.

Introduction

1-2 HP ProLiant Essentials Virtual Machine Management Pack User Guide

• Virtual Machine Management Agent—Provided with the Virtual Machine Management Pack installation, is distributed to managed hosts from the user interface.

• HP ProLiant Essentials Server Migration Pack—Used to perform physical-to-virtual (P2V) migration or virtual-to-virtual (V2V) migration of virtual machines managed in the Virtual Machine Management Pack console using the Server Migration Pack integrated console.

IMPORTANT: Server Migration Pack has additional licensing requirements. For additional information, refer to the HP ProLiant Essentials Server Migration Pack User Guide.

HP Systems Insight Manager console integration

The Virtual Machine Management Pack installs and runs on the HP SIM Central Management Server (CMS). The Virtual Machine Management Pack displays the status of virtual machine hosts and guests in the HP SIM console. The virtual machine host and guest status information is displayed in the VM column, shown circled in the following figure.

The association between virtual machine hosts and guests is displayed in the systems list. Click the System Name entry to view additional details about the respective virtual machine hosts and guests.

Introduction


The status of the virtual machine hosts and guests is depicted using the color-coded icons listed in Table 1-1 and Table 1-2. Table 1-1: Virtual machine host icons

Icon Status

The virtual machine host is licensed and is currently communicating with the Virtual Machine Management Pack.

The virtual machine host is licensed but is not currently communicating with the Virtual Machine Management Pack.

The VMM agent is installed on the server, but the server is not a virtual machine host.

The VMM agent is installed on the virtual machine host, but the host is not licensed.

No icon

The VMM agent is not installed on this server.

Table 1-2: Virtual machine guest icons

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 the Virtual Machine Management Pack.

The virtual machine guest is in a state requiring 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.

Click any of the icons to display additional information for the system.


2 Requirements

This chapter lists the hardware and software required for each component in the Virtual Machine Management Pack environment to successfully run the Virtual Machine Management Pack.

A Virtual Machine Management Pack environment consists of the following components:

• HP SIM Microsoft Windows®-based CMS

• Virtual machine hosts

• Virtual machine guests

HP SIM CMS

The HP SIM CMS must meet the following requirements to successfully use Virtual Machine Management Pack. Requirements listed here are specifically for the Virtual Machine Management Pack and are independent of requirements for HP SIM. For specific hardware and software requirements for HP SIM, refer to the HP Systems Insight Manager Installation and User Guide.

• HP SIM 4.2 SP2 or later with OpenSSH and Windows Management Instrumentation (WMI) Mapper installed. HP SIM must be installed on a Windows physical server. The Virtual Machine Management Pack does not support HP SIM operating on a virtual server or on a server running a Linux or HP-UX operating system.

• At least 155 MB of available disk space.

• Network connections configured properly to be managed by the Virtual Machine Management Pack. Verify the configuration by pinging the virtual machine host from the CMS and vice versa using the primary IP address.

NOTE: This version of the Virtual Machine Management Pack does not support HP SIM database implementations using Oracle®.

For browser support information for viewing the HP SIM console from a remote location, refer to the HP Systems Insight Manager Installation and User Guide located at http://www.hp.com/go/hpsim.

http://www.hp.com/servers/manage

http://www.hp.com/go/hpsim

Requirements


Virtual machine host

Table 2-1 lists the requirements for virtual machine hosts. Table 2-1: Virtual machine host requirements

Component Requirement

Microsoft Virtual Server 2005

VMware ESX Server Virtualization technology*

VMware GSX Server (installed on a Windows system only)

VMM agent

SSH or OpenSSH installed, enabled, and configured for HP SIM Services Insight Manager Agents for VMware ESX Server, available from http://www.hp.com/solutions/vmware

Available disk space 65 MB for VMM agent (100 MB during installation)

Network connection Configured properly to be managed by the Virtual Machine Management Pack. Verify the configuration by pinging the virtual machine host from the CMS and vice versa using the primary IP address.

IP addresses If DHCP is used on the VMware ESX Server host, the Microsoft DNS server might not map the host name to DHCP-generated IP addresses. HP recommends creating static IP address.

* For specific software versions, refer to the HP ProLiant Essentials Virtual Machine Management Pack 1.11 and Server Management Pack 1.11 Support Matrix.

Virtual machine guest

For supported operating systems on virtual machine guests, refer to the specific virtualization technology installed on the virtual machine host.

• For Microsoft Virtual Server, refer to http://www.microsoft.com/windowsserversystem/virtualserver.

• For VMware, refer to http://www.vmware.com.

NOTE: For improved management of Microsoft Windows NT®, install the WMI CORE on the virtual machine guest. Refer to http://www.microsoft.com/downloads/release.asp?releaseid=18490.

http://www.hp.com/solutions/vmware

http://www.microsoft.com/windowsserversystem/virtualserver

http://www.vmware.com/

http://www.microsoft.com/downloads/release.asp?releaseid=18490


3 Installation and configuration

This chapter provides detailed information required to successfully install and configure the Virtual Machine Management Pack.

These instructions assume that all hardware and software requirements have been met. Refer to Chapter 2 of this guide to ensure that all requirements have been met before attempting to install the Virtual Machine Management Pack.

Virtual Machine Management Pack installation

IMPORTANT: You must have administrative rights in HP SIM and access to the HP SIM database to install the Virtual Machine Management Pack. HP recommends performing a typical HP SIM installation.

IMPORTANT: HP SIM and HP SIM and HP SIM will be restarted at the end of the Virtual Machine Management Pack installation. HP SIM and Microsoft SQL Server must be running to successfully install the Virtual Machine Management Pack.

The Virtual Machine Management Pack can be installed from either the HP website or the HP Management CD.

Installing from the Management CD

The Virtual Machine Management Pack can be installed at the same time as HP SIM 4.2 SP2 or later, or installed separately. To install the Virtual Machine Management Pack:

1. Insert the HP Management CD into the CD-ROM drive of the HP SIM CMS. An autorun menu appears.

2. Read the license agreement displayed by the autorun. If you agree to the terms of the license agreement, click Agree to continue.

Installation and configuration


3. If installing the Virtual Machine Management Pack at the same time as HP SIM 4.2 SP2 or later, click Install located under HP Systems Insight Manager. Refer to the HP Systems Insight Manager Installation and User Guide to complete the installation, selecting Virtual Machine Management Pack for installation.

NOTE: The Virtual Machine Management Pack is included with both a typical and custom installation of HP SIM 5.0 or later. To install the Virtual Machine Management Pack with previous versions of HP SIM, you must perform a custom installation.

If installing the Virtual Machine Management Pack separately, click Install located under HP ProLiant Essentials Virtual Machine Management Pack.



4. At the Virtual Machine Management Pack welcome screen, click Next.

5. Enter the HP SIM account credentials, and click Next.



6. Click Finished when the Virtual Machine Management Pack installation completes. The Virtual Machine Management Pack installation does not require a reboot.

Installing from the download website 1. Download the Virtual Machine Management Pack from http://www.hp.com/go/vmm. 2. Double-click HPVMM.exe to start the installation.

3. Follow the on-screen instructions, entering your user specific information when prompted.

http://www.hp.com/servers/proliantessentials/vmm


http://www.hp.com/anhinga




Installation locations

Table 3-1 lists the default installation locations for the Virtual Machine Management Pack and HP SIM.

NOTE: The Virtual Machine Management Pack is always installed under the same installation directory as HP SIM.

Table 3-1: Default installation locations

Component Default installation location

Virtual Machine Management Pack C:/Program Files/HP/Virtual Machine Management Pack

HP SIM C:/Program Files/HP/Systems Insight Manger

Installed components

The Virtual Machine Management Pack installs the following menu items to the HP SIM toolbar:

• Tools>Integrated Consoles>Virtual Machine Management Pack

• Deploy

— Virtual Machine Management Pack

— Deploy Linux Agent

— Deploy Windows Agent

— Upgrade Agent (installed with a Virtual Machine Management Pack upgrade installation)

— License Manager>Virtual Machine Host License Wizard

• Configure>Virtual Machine Management Pack

— Register Virtual Machine Host

— Unregister Virtual Machine Host

• Help>HP Virtual Machine Management Pack on hp.com



Post-installation configuration tasks

Perform the procedures in the following sections before attempting to use the Virtual Machine Management Pack.

IMPORTANT: These configuration steps must be performed before using the Virtual Machine Management Pack.

1. Log in to HP SIM from the Administrator account.

2. Select Options>Protocol Settings>Global Protocol Settings, and configure the Web Based Enterprise Management (WBEM) credentials to enable access to target systems. If some target systems use individual administrator credentials, configure WBEM credentials using System Protocol Settings.

3. Perform a discovery of virtual machine hosts and guests to allow the Virtual Machine Management Pack to access target systems in the network.

NOTE: For information about performing basic HP SIM tasks, refer to the HP Systems Insight Manager Installation and User Guide.

Installing OpenSSH

OpenSSH provides secure communications between the virtual machine host and the CMS by encrypting online traffic to eliminate network-level attacks. You must install OpenSSH on Windows hosts before the VMM agent can be deployed from the CMS.

To install OpenSSH on Windows virtual machine hosts:

1. Select Deploy>Deploy Drivers, Firmware, and Agents>Install OpenSSH.

2. Click the HP SIM help icon ( ), and follow the on-screen instructions to complete the installation.

Configuring OpenSSH

If OpenSSH is already installed, it must be configured on both Windows and Linux virtual machine hosts. Configure OpenSSH using the MxAgentConfig command. From the command prompt, enter:

mxagentconfig –a -n <hostname> -u <username> -p <password>

or mxagentconfig (HP SIM 4.2 SP2 only)

For more information about the MxAgentConfig command, go to the HP SIM online help and search for keywords “Getting started using the command line interface commands.”



Deploying the VMM agent

The VMM agent must be deployed to a virtual machine host before the host can be licensed.

IMPORTANT: OpenSSH must be configured properly and running on both the HP SIM CMS and the selected target virtual machine hosts to deploy the VMM agent.

To deploy the VMM agent to Windows virtual machine hosts:

1. Select Deploy>Virtual Machine Management Pack>Deploy Windows Agent. The Deploy Windows Agent page displays.

2. Select the target Windows virtual machine hosts by selecting the checkbox next to the appropriate systems.

3. Click Apply Selections.

4. Verify that the correct target hosts appear in the list. Click Change Targets if it is necessary to reselect target hosts.

5. Click Run Now to deploy the Windows agent immediately.

6. View task results in the VMM task logs. This task must complete successfully for HP SIM to properly identify this system as a virtual machine host.

To deploy the VMM agent to VMware ESX Server hosts:

NOTE: The VMware ESX Server host uses the VMM Linux agent.

1. Select Deploy>Virtual Machine Management Pack>Deploy Linux Agent. The Deploy Linux Agent page displays.

2. Select the target Linux virtual machine hosts by selecting the checkbox next to the appropriate systems.


4. Verify that the correct target hosts appear in the list. Click Change Targets if it is necessary to reselect target hosts.

5. Click Run Now to deploy the Linux agent immediately.

6. View task results in the VMM task logs. This task must complete successfully for HP SIM to properly identify this system as a virtual machine host.



Installing Microsoft Virtual Server Additions or VMware Tools

Microsoft Virtual Server Additions or VMware Tools must be installed on virtual machine guests before a shutdown or reset can be successfully performed. Complete the following procedures before performing a shutdown or reset from the Virtual Machine Management Pack console.

NOTE: Microsoft Virtual Server Additions and VMware Tools are also required to perform certain Microsoft Virtual Server 2005 and VMware tasks.

Installing Microsoft Virtual Server Additions

IMPORTANT: Be sure the virtual machine guests are started before installing software.

1. Open the Microsoft Virtual Server Administration website.

2. Select Configure in the Virtual Machines field of the Virtual Server Administration homepage. A list of virtual machines guests displays.

3. Select the appropriate virtual machine guests. The virtual machine guest configuration details display.

4. Click Install Virtual Machine Additions.

5. Select the Install Virtual Machine Additions checkbox, and click OK.

For additional information, refer to http://www.microsoft.com/windowsserversystem/ virtualserver.

Installing VMware Tools

Both VMware ESX Server and VMware GSX Server tools can be installed on VMware virtual machine guests from the VMware Management Interface.

IMPORTANT: Be sure the virtual machine guests are started before installing software.

1. Access the VMware interface at http://IP address:8222/vmware/en.

2. Log in to the VMware Management Interface.

3. Select the appropriate virtual machine guest, and open the remote console.

4. From the selected virtual machine console, right-click the selected virtual machine guest.

5. Select Install VMware Tools.

For additional information, refer to http://www.vmware.com/support/ws45/doc/ new_guest_tools_ws.html.



http://www.vmware.com/support/ws45/doc/new_guest_tools_ws.html

http://www.vmware.com/support/ws45/doc/new_guest_tools_ws.html



Virtual Machine Management Pack upgrade

IMPORTANT: HP SIM must be restarted to perform the Virtual Machine Management Pack upgrade.

To upgrade the Virtual Machine Management Pack, refer to the steps in the “Virtual Machine Management Pack installation” section.

Upgrading the VMM agent

IMPORTANT: Upgrading the Virtual Machine Management Pack from version 1.00 to version 1.10 temporarily unregisters the VMM agent. This process deletes all associated information from the database, including all HP SIM associations and scheduled task data.

NOTE: The Virtual Machine Management Pack 1.11 console is compatible with both the VMM 1.10 and 1.11 agent.

After a Virtual Machine Management Pack upgrade is installed, upgrade the VMM agent on all of the previously managed virtual machine hosts. To upgrade the VMM agent:

1. Select Deploy>Virtual Machine Management Pack>Upgrade Agent.

2. Click Run Now to deploy the agent immediately, or click Schedule to deploy the agent at a designated time.

After upgrading, these virtual machine hosts appear in the Virtual Machine Management Pack console.


4 Licensing

Overview

This chapter provides information about licensing servers for use with the Virtual Machine Management Pack.

IMPORTANT: Server Migration Pack licenses are separate and independent from the Virtual Machine Management Pack licenses. For additional information about Server Migration Pack licensing, refer to the HP ProLiant Essentials Server Migration Pack User Guide.

IMPORTANT: The VMM agent must be deployed to virtual machine hosts before licenses can be applied. For information about deploying the VMM agent, refer to Chapter 3 of this guide.

Free licenses

Five fully functional 60-day trial licenses are provided with the Virtual Machine Management Pack for evaluation purposes. These licenses are available after the Virtual Machine Management Pack is installed and can be applied to systems from the Virtual Machine Management Pack License Wizard.

Licensing preparation

The Virtual Machine Management Pack License Wizard applies licenses to virtual machine hosts. The managed hosts must be identified as virtual machine hosts in HP SIM before licenses can be deployed, which requires that the VMM agent be installed on the hosts. For information about deploying the VMM agent, refer to Chapter 3 of this guide.

Before licensing servers for the Virtual Machine Management Pack, verify that the servers have a supported operating system and the VMM agent installed.

For more information about discovering and updating the server list in HP SIM, refer to the HP Systems Insight Manager Installation and User Guide. For information about supported operating systems, refer to the HP ProLiant Essentials Virtual Machine Management Pack 1.11 and Server Migration Pack 1.11 Support Matrix.

Licensing


Licensing options

The following options are available for purchasing licenses:

ProLiant Essentials Virtual Machine Management Pack Single-Server License—For use with a single server, this option contains one kit with a unique license activation key and documentation.

ProLiant Essentials Virtual Machine Management Pack Flexible-Quantity License—For use with multiple servers, this option can be used to purchase multiple licenses with a single activation key. The quantity ordered of this part number is the quantity of licenses included in the kit in the form of a corresponding activation key. Use the same key to activate all licenses in the actual quantity ordered. For a given order, one kit is delivered with the activation key and documentation.

ProLiant Essentials Virtual Machine Management Pack Tracking License—For use with signed and implemented Activation Key Agreements only, this option entitles the deployment of additional product licenses under the terms of the existing Activation Key Agreement.

For additional information or to purchase licenses, refer to http://h18013.www1.hp.com/products/servers/proliantessentials/license/licenseops.html.

Licensing virtual machine hosts

IMPORTANT: The Virtual Machine Management Pack does not support license deployment from the HP SIM License Manager.

IMPORTANT: You must have HP SIM administrative rights to add or deploy license keys.

The Virtual Machine Management Pack License Wizard can be used to manage licenses. The Virtual Machine Management Pack License Wizard displays all available keys, as well as the key details and summary status.

Adding licenses 1. From the console toolbar, select Deploy>License Manager>Virtual Machine Host

License Wizard.

IMPORTANT: The Virtual Machine Management Pack License Wizard menu only appears after HP SIM has identified at least one system as a virtual machine host.

2. Select the target virtual machine hosts to license by selecting the checkbox next to the systems.

IMPORTANT: Only HP SIM-identified virtual machine hosts can be selected for licensing.


http://h18013.www1.hp.com/products/servers/proliantessentials/license/licenseops.html

Licensing


4. Verify that the correct target hosts appear in the list, click Change Targets if it is necessary to reselect target hosts, and then click Next.

5. Click Add Key to enter one or more new key strings, which can be cut and pasted as one string into any of the subfields, and then click OK.

NOTE: If the license key is not valid or is a duplicate of a key already existing, an error message appears.

Applying licenses to virtual machine hosts

IMPORTANT: After a license is applied to a specific server, the license cannot be removed or transferred to another server.

1. From the console toolbar, select Deploy>License Manager> Virtual Machine Host License Wizard.

2. Select the target virtual machine hosts to license by selecting the checkbox next to the systems.

IMPORTANT: Only HP SIM-identified virtual machine hosts can be selected for licensing.


4. Verify that the correct target hosts appear in the list, click Change Targets if it is necessary to reselect target hosts, and then click Next.

5. Select the target hosts by selecting the checkbox next to the systems, and click Apply License.

6. Click Next.

7. Click Run Now to run the Identify Systems task, which establishes association in HP SIM between the virtual machine hosts and guests.

If the Identify Systems task is not successfully completed at this time, run the task manually by selecting Options>Identify Systems from the HP SIM console.


5 Using the Virtual Machine Management Pack

Accessing the Virtual Machine Management Pack console

The Virtual Machine Management Pack provides central management and control for virtual machines with Microsoft Virtual Server 2005, VMware GSX Server, or VMware ESX Server. The Virtual Machine Management Pack console is an integrated console within HP SIM.

The Virtual Machine Management Pack console also detects virtual machine status changes initiated by other supported virtualization technology consoles. These status changes are indicated by the status icon in the Virtual Machine Management Pack console.

To access the Virtual Machine Management Pack console, select Tools> Integrated Consoles>Virtual Machine Management Pack. The Virtual Machine Management Pack console displays in a new browser window.

Using the Virtual Machine Management Pack


The left frame of the Virtual Machine Management Pack console displays a tree of virtual machine hosts and guests and links to Virtual Machine Management Pack logs.

The Virtual Machine Management Pack homepage

The right frame of the Virtual Machine Management Pack console displays the Virtual Machine Management Pack homepage. This page displays all virtual machine hosts managed by the Virtual Machine Management Pack and the following information for each host:

NOTE: The Virtual Machine Management Pack homepage can be accessed at any time by clicking Home in the left pane of the Virtual Machine Management Pack console.

• VMM status—The status of the virtual machine host depicted using color-coded icons

• Host name—The system name of the virtual machine host

• System address—The IP address of the virtual machine host

• Operating system—The name and version of the operating system installed on the virtual machine host

• Model—The virtual machine host system model

• Virtualization—The virtualization technology installed on the virtual machine host

• Free CPU—The amount of free processor cycles on the virtual machine host

• Free memory—The percentage of free memory on the virtual machine host

• Free storage—The amount of free storage on the virtual machine host



By default, the list is sorted by the host name. The list can be sorted by all columns. The currently sorted column is highlighted and displays an arrow indicating the sort order, either ascending or descending.

Unlicensed virtual machine hosts do not display a value in the Free CPU, Free Memory, or Free Storage fields. These fields will display “unlicensed.”

The host console for a selected virtual machine host can be displayed in the right frame by clicking the Host Name entry.

The virtualization technology management interface console can be launched by clicking the Virtualization entry.

Select a virtual machine host or guest in the left frame to display specific information for that host or guest in the right frame. Select a VMM log under the Logs directory to display the event log, running task log, or scheduled VM backups.

The Virtual Machine Management Pack host console

The Virtual Machine Management Pack host console displays the following virtual machine host performance information in both text and graphical format:

• Processor % • Storage capacity (free/total) • Memory (free/total) • Storage capacity used % • Memory usage % • Storage throughput • Network throughput



Performance data is collected every minute. Total and available memory and storage values are calculated during the most recent data collection.

The numbers to the right of the graphs show the most recent data collected in the last minute. Graphical data depicts performance for the previous 60 minutes.

The host console also displays information for each of its virtual machine guests, including a thumbnail view of the console for each virtual machine guest that is currently running. Clicking the thumbnail view launches the remote console for the virtual machine guest.

The Virtual Machine Management Pack guest console

The Virtual Machine Management Pack guest console displays basic information for the virtual machine guest, including a thumbnail view of the console. The guest console also displays the following virtual machine guest information in both text and graphical format. The type of performance information collected by the Virtual Machine Management Pack varies according to the virtualization product installed as indicated. Table 5-1: Guest console performance information

Performance information Virtualization product

Processor % All supported virtualization products

Memory (free/total) VMware ESX Server

Memory usage % VMware ESX Server

Network throughput VMware ESX Server and Microsoft Virtual Server 2005

Storage throughput VMware ESX Server and Microsoft Virtual Server 2005



The following configuration information displays:

• VM host • Virtual disk • Virtualization • CD/DVD drive • Configuration file • Floppy drive • Configuration folder • Network card • Memory • Total file size • Virtual disk name • Virtual disk size

Performance data is collected from the supported virtualization product every minute.

The numbers to the right of the graphs indicate the most recent data collected in the last minute. Graphical data depicts performance for the previous 60 minutes.



Using the Virtual Machine Management Pack console

Various tasks can be performed from the Virtual Machine Management Pack console, as described in the following sections. You must have administrative rights to perform the following tasks.

The following icons appear on the Virtual Machine Management Pack console. Using these icons, licensed virtual machine guests can be started, resumed, shut down, stopped, paused, reset, and restarted. Table 5-2: Console icons

Icons Function

Start/resume

Shutdown/stop

Pause

Reset/restart

In addition, the following tasks can be initiated from the Manage and Launch action menus on the guest console:

• Copy Virtual Machine

• Move Virtual Machine

• Create VM Template

• Create VM Backup

• Remote Console

The following tasks can be initiated from the Manage action menu on the host console:

• Restart VMM Agent

• Deploy VM Template

• Restore VM



Starting or resuming a virtual machine guest

NOTE: A virtual machine guest can only be started or resumed if it is currently stopped, shut down, or paused.

1. Select either the virtual machine host or the virtual machine guest in the left pane.

2. If the virtual machine host is selected, click the Start icon next to the virtual machine guest in the Virtual Machine Information field.

If the virtual machine guest is selected, click the Start icon in the right pane.

If the virtual machine guest is currently stopped or paused, the guest is started or resumed. If the virtual machine guest is currently suspended to disk (only possible with Microsoft Virtual Server 2005), selecting Resume Virtual Machine Guest restores the virtual machine guest to the previous state and powers on the virtual machine guest.

When the power-on process is complete, the status is updated to Normal ( ). The Start icon is disabled, and the Shutdown/Stop, Pause, and Reset icons are enabled.

If a virtual machine guest becomes stuck during the start process, the Virtual Machine Management Pack displays “User Interaction” and the status is updated to Major ( ).

Shutting down or stopping a virtual machine guest

NOTE: A virtual machine guest can only be shut down if it is currently powered on and either the Microsoft Virtual Server Additions or the VMware Tools are installed on the virtual machine guest.


2. If the virtual machine host is selected, click the Shutdown/Stop icon next to the virtual machine guest in the Virtual Machine Information field.

If the virtual machine guest is selected, click the Shutdown/Stop icon in the right pane.

3. Select either Stop VM or Shut down VM when prompted. Selecting Stop VM powers off the virtual machine guest immediately without saving the current state. Selecting Shut down VM shuts down the virtual machine operating system and then powers off the virtual machine guest.

CAUTION: Unsaved data is lost if you select Stop VM.

The virtual machine status is updated to Disabled ( ). The Stop, Pause, and Reset icons are disabled, and the Start icon is enabled.


Pausing a virtual machine guest

NOTE: A virtual machine guest can only be paused if it is currently powered on and running.


2. If the virtual machine host is selected, click the Pause icon next to the virtual machine guest in the Virtual Machine Information field.

If the virtual machine guest is selected, click the Pause icon in the right pane.

3. For VMware virtual machine guests, click Suspend VM when prompted.

For Microsoft Virtual Server 2005 virtual machine guests, select Suspend to disk or Pause VM when prompted. Selecting Suspend to disk saves the current state and then pauses the virtual machine guest. Selecting Pause VM suspends the virtual machine guest without discarding the state.

The virtual machine status is updated to Disabled ( ). The Stop, Pause, and Reset icons are disabled, and the Start icon is enabled.

Resetting or restarting a virtual machine guest 1. Select either the virtual machine host or the virtual machine guest in the left pane.

2. If the virtual machine host is selected, click the Reset icon next to the virtual machine guest in the Virtual Machine Information field.

If the virtual machine guest is selected, click the Reset icon in the right pane.

3. Select either Reset or Restart when prompted. Selecting Reset powers off and then powers on the virtual machine guest. Selecting Restart shuts down the virtual machine operating system and then powers off and powers on the virtual machine guest.

CAUTION: Unsaved data is lost if you select Reset.

When the reset or restart is complete, the virtual machine status is updated to Normal ( ). The Start icon is disabled, and the Shutdown/Stop, Pause, and Reset icons are enabled.




Copying a virtual machine guest

IMPORTANT: A virtual machine guest must be stopped before copying. You must have administrative rights to perform a move operation.

Virtual machine guests can be copied from an existing virtual machine host to a new host when the same virtualization technology exists on both the source and target host servers.

NOTE: To perform a V2V migration, which involves migrating a virtual machine guest to a virtual machine host with a different virtualization technology, refer to the HP ProLiant Essentials Server Migration Pack User Guide.

1. Select the virtual machine guest in the left pane, and click Copy Virtual Machine in the Manage action menu. The source information appears.

2. View the source machine details and settings, and click Next. A list of licensed virtual machine hosts appears.

3. Review the resources of the available hosts, and select an appropriate target virtual machine host on which to copy the selected virtual machine guest. Click Next.

4. 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 must be empty.

IMPORTANT: Microsoft requires that each virtual machine guest have a unique virtual machine name. If virtual machine disks or configuration files already exist with the designated name, an error will occur and the copy operation will fail.

IMPORTANT: 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.

5. Click Next.

6. Confirm the displayed details of the copy operation, and click Confirm.

When the copy is complete, the new virtual machine guest is registered to the target virtual machine host. The virtual machine status guest status is Disabled ( ). Start the copied virtual machine guest from the Virtual Machine Management Pack console as necessary.

NOTE: The virtual network connections on the new virtual machine guest might have to be manually reconfigured, and the host name of the copied guest might have to be changed.



Moving a virtual machine guest

IMPORTANT: A virtual machine guest must be stopped before moving. You must have administrative rights to perform a move operation.

Virtual machine guests can be moved from an existing virtual machine host to a new host when the same virtualization technology exists on both the source and target hosts.

NOTE: To perform a V2V migration, which involves migrating a virtual machine guest to a virtual machine host with a different virtualization technology, refer to the HP ProLiant Essentials Server Migration Pack User Guide.

1. Select the virtual machine guest in the left pane, and click Move Virtual Machine in the Manage action menu. The source information appears.

2. View the source machine details and settings, and click Next. A list of licensed virtual machine hosts appears.

3. Review the resources of the available hosts, and select an appropriate target virtual machine host on which to move the selected virtual machine guest. Click Next.

4. Specify a name for the target virtual machine guest being moved or accept the default selection, and specify the target path for the virtual machine guest and the disk. The target folder must be empty.

IMPORTANT: Microsoft requires that each virtual machine guest have a unique virtual machine name. If virtual machine disks or configuration files already exist with the designated name, an error will occur and the move operation will fail.


5. Click Next.

6. Confirm the displayed details of the move operation, and click Confirm.

When the move is complete, the new virtual machine guest is registered to the target virtual machine host. The virtual machine status guest status is Disabled ( ). Start the moved virtual machine guest from the Virtual Machine Management Pack console as necessary.

NOTE: The Virtual Machine Management Pack does not delete virtual machine guest files after a move.

NOTE: The virtual network connections on the moved virtual machine guest might have to be manually reconfigured.



Backing up a virtual machine guest

IMPORTANT: A virtual machine guest must be stopped or suspended before a backup can be performed. If a backup is scheduled on a virtual machine guest that is currently started, the guest is suspended and then restarted after the backup is complete. You must have administrative rights to perform a backup.

The Virtual Machine Management Pack enables you to perform an immediate backup of a virtual machine guest or schedule a recurring backup on a daily or weekly basis.

1. Select the virtual machine guest in the left pane, and click Create VM Backup in the Manage action menu.

2. View the source machine details and settings, and click Next.

3. Backups can be performed either one time, daily, weekly, or immediately. Select Perform Backup Now to execute the backup immediately, or select the type of backup to schedule a time to run either a one-time backup or regular backups.

If a backup is already scheduled for the virtual machine guest, click Disable Scheduled Backup to modify or cancel the scheduled backup

4. Click Next. A list of licensed virtual machine hosts appears.

NOTE: If there are other operations currently in progress, such as a copy, a backup will not be performed immediately. The backup will automatically be queued to run after any pending operations are complete.

5. Review the resources of the available hosts, and select an appropriate target virtual machine host on which the backup will be stored. Click Next.

6. Specify the target path for the virtual machine backup, and click Next. Each backup is stored in a separate subdirectory within the selected location.


NOTE: If a virtual machine host is unregistered or no longer managed by the Virtual Machine Management Pack, the backup information for the virtual machine guests associated with that host is permanently removed from the Virtual Machine Management Pack console. The backup files, including disk files, are retained in the designated location and can be manually deleted if necessary.

7. Confirm the displayed details of the backup operation, and click Confirm.



Creating a virtual machine guest template

IMPORTANT: A virtual machine guest must be stopped before it can be used to create a template. You must have administrative rights to create a template.

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. Any existing virtual machine guest on a licensed host can be used to create a template.

NOTE: A template does not contain the serial number (UUID) and MAC address of the virtual machine guest used to create the template.

1. Select the virtual machine guest from which to create a template in the left pane, and click Create VM Template in the Manage action menu. The source information appears.

2. View the source machine details and settings, and click Next.

3. Enter a name for the template or accept the default selection, and enter a description, if desired. Click Next. A list of licensed virtual machine hosts appears.

4. Review the resources of the available hosts, and select an appropriate target virtual machine host where the template will be stored, and click Next.


5. Specify the target path for the virtual machine template, and click Next. The target folder must be empty.

6. Confirm the displayed details of the operation, and click Confirm.

Launching the virtual machine remote console

IMPORTANT: Microsoft Virtual Server 2005 remote console is only supported with Microsoft Internet Explorer browsers.

IMPORTANT: VMware Management Interface must be installed on VMware GSX Server virtual machine hosts to launch the remote console.

IMPORTANT: If you are launching a remote console from a VMware host, VMware Remote Console application must be installed on the system from which you are launching remote console.

To launch a remote console for the virtualization layer installed on a virtual machine host, select a virtual machine guest in the Virtual Machine Management Pack console, and click Remote Console in the Launch menu. The remote console displays in a separate browser window.



Restarting the VMM agent

It might become necessary to restart the VMM agent on the virtual machine host in various situations, including:

• The virtualization technology was installed on the host after the VMM agent was installed.

• Virtual machine guest information becomes inaccessible in the Virtual Machine Management Pack console.

To restart the VMM agent:

1. Select a virtual machine host from the left pane of the console.

2. Click Restart VMM agent in the Manage action menu.

3. Click Yes when prompted to confirm selection.

Restoring a virtual machine guest

The Virtual Machine Management Pack enables you to restore a virtual machine guest using a previously created backup.


2. Click Restore VM Backup in the Manage action menu. A list displays the available backups created from the virtualization technology on the selected host.

3. Select a backup from the list of available backups, or click Browse to manually search for a virtual machine backup. Click Next.

4. Verify the backup information displayed, select a location to restore the backup, and click Next. The backup can be restored to the original virtual machine host and location or to a different host and location.


5. Confirm the displayed details of the restore operation, and click Confirm to restore the backup.

If the virtual machine guest being restored already exists on the selected host, the existing virtual machine guest is stopped and unregistered. All files on the existing guest are overwritten with the backup files, and the guest is registered again.



Deploying a virtual machine guest template

The Virtual Machine Management Pack enables you to deploy a previously created virtual machine template to create a new virtual machine guest. A virtual machine template is an image of a complete virtual machine operating system, configuration, and all relevant virtual disk information needed to create and register a new virtual machine on a virtual machine host with the same virtualization technology.

NOTE: A template does not contain the serial number (UUID) and MAC address of the virtual machine guest used to create the template.


2. Click Deploy VM Template in the Manage action menu. A list displays the available templates created from the virtualization technology on the selected host.

3. Select a template from the list of available templates, or click Browse to manually search for a virtual machine template. Click Next.

4. Verify the template information displayed, and click Next.

5. Select the target virtual machine host where the template will be deployed, and click Next.

6. Select the target virtual machine host directory location, and then click Next. The target folder must be empty.


7. Modify the name of the virtual machine guest and the memory size as necessary, and click Next.

8. Click Confirm. The disk files are copied to target directory on the selected host, and the new virtual machine guest is registered to the target virtual machine guest with a new serial number (UUID) and MAC address.



Viewing Virtual Machine Management Pack logs

The Virtual Machine Management Pack console provides access to the following log files.

Event log

To view all the events that have been run on all Virtual Machine Management Pack-managed virtual machine hosts and guests:

1. Select Tools>Integrated Console>Virtual Machine Management Pack. The Virtual Machine Management Pack console displays in a new browser window.

2. In the left frame of the Virtual Machine Management Pack console, expand the Logs directory, and click Event Log. The event log appears in the right frame.



To view events that have been run on a selected virtual machine host:


2. In the left frame of the Virtual Machine Management Pack console, select the appropriate virtual machine host. The recent events are displayed in the right pane. Click show Event Log to display all events run on the host.

The following information is displayed for each event:

• Type—Color-coded icons indicating if an event completed successfully or failed

• Time—When the event started

• Category—The classification of the event

• User—Who initiated the event

• Host—The virtual machine host included in the event

• VM—The virtual machine included in the event

• Message—A brief description of the event and the result

To filter the event list, select from the dropdown list next to View. The event list can be filtered to display:

• All events

• Only errors

• Only errors and warnings

• Only today’s events

To delete events from the event log, select the checkbox next to the appropriate events, and click Delete selected events.



Running task log

To view any tasks currently running on all Virtual Machine Management Pack-managed virtual machine hosts and guests:


2. In the left frame of the Virtual Machine Management Pack console, expand the Logs directory, and click Running Task Log. The running task log appears in the right frame.

To view all tasks currently running on a selected virtual machine host:


2. In the left frame of the Virtual Machine Management Pack console, select the appropriate virtual machine host. Information for the selected host is displayed in the right pane, including any currently running tasks.

The following information is displayed for each running task:

• Status

• Description

• Progress

• Time remaining

• Cancel



Scheduled VM backups

To access the Scheduled VM backup log from the left frame of the Virtual Machine Management Pack console, expand the Logs directory and click Scheduled VM Backups. The scheduled VM backups appear in the right frame.

Scheduled VM Backups displays the following information about any pending backup:

• VM host

• Virtual machine

• Next run

• Schedule

HP ProLiant Essentials Virtual Machine Management Pack User Guide A-1

A Troubleshooting

This section identifies and provides solutions for commonly encountered issues, as well as answers to frequently asked questions. The following topics are included:

• Installation — The Virtual Machine Management Pack cannot be installed on a virtual machine — In an environment using multiple HP SIM CMSs, the Virtual Machine Management

Pack can only be installed on one CMS — “Installed, refer to hpvmm.log for the installation status” appears during installation — “HP SIM service or SQL service is not running. Cancel the installation.” appears

during installation — The Virtual Machine Management Pack 1.11 cannot be installed over a later version — Uninstalling the Virtual Machine Management Pack and Server Migration Pack — "The process cannot access the file because it is being used by another process"

message appears during uninstallation

• Configuration — Virtual Machine Management Pack menu items are not removed from the HP SIM

toolbar with the Virtual Machine Management Pack uninstallation — The Virtual Machine Management Pack might not detect virtual machines located on

mapped network drives — Configuring the Virtual Machine Management Pack with a firewall — Virtual machine hosts cannot be licensed

• VMM agent — The VMM agent installation fails — VMM agent registration fails on VMware ESX Server virtual machine host — VMM agent registration fails on virtual machine host configured with multiple

IP addresses — The VMM agent registration must be reinitialized if the IP address or name of the

virtual machine host is changed — VMM agent registration fails

— “Agent Registration failed” appears in the HP SIM task log after upgrading the VMM agent

Troubleshooting

A-2 HP ProLiant Essentials Virtual Machine Management Pack User Guide

• The Virtual Machine Management Pack console — Virtual machine host and guests do not appear in the Virtual Machine Management

Pack console — The Virtual Machine Management Pack console does not display the system name,

system IP address, and operating system — Critical status is displayed for a virtual machine host on the Virtual Machine

Management Pack console — A blank page appears when launching the Virtual Machine Management Pack

console from HP SIM — The status displayed in the left pane of the Virtual Machine Management Pack

console does not match the status displayed in the right pane — Virtual machine status is not updated — Virtual machine guest information becomes inaccessible in the Virtual Machine

Management Pack console — A virtual machine host appears in the Virtual Machine Management Pack console

multiple times — The Virtual Machine Management Pack console displays “No Virtualization Layer

Available for this Host”

• Virtual Machine Management Pack functions — Using a virtual machine host not managed by the Virtual Machine Management Pack

as a template/backup repository — “HTTP Error: 500 Internal Server Error” appears during a Virtual Machine

Management Pack move or copy operation — The Virtual Machine Management Pack cannot move virtual machines with certain

disk types — Virtual machine files are not deleted after a move — Virtual machine devices might not be available after a copy or move — A shutdown or restart operation fails or does not complete — Launching the remote console from the Virtual Machine Management Pack console

might fail

• HP SIM console integration — The HP SIM console does not identify a server as a virtual machine host — The HP SIM console does not discover a virtual machine host or guest — The HP SIM console identifies a virtual machine guest as an Unknown or

Unmanaged device — Linux virtual machine guest association is not displayed in the HP SIM console — The Virtual Machine Management Pack version displayed in HP SIM is incorrect

• Additional resources

Troubleshooting


Installation

The Virtual Machine Management Pack cannot be installed on a virtual machine

Virtualization is a technique that is frequently used to consolidate several separate servers with low utilization into separately booted partitions with the goal of achieving higher utilization of the whole. HP SIM has significant CPU, memory, storage, and network requirements. The addition of the Virtual Machine Management Pack increases the system requirements and resource utilization. Installing and running the Virtual Machine Management Pack on virtual machines is not supported because workload and traffic on other virtual machines can prevent the Virtual Machine Management Pack from functioning properly. Other partitions could also be prevented from meeting performance or response requirements.

In an environment using multiple HP SIM CMSs, the Virtual Machine Management Pack can only be installed on one CMS

HP SIM manages devices by polling them periodically, receiving traps, and dynamically connecting to run tasks, such as software updates or scripts. A device can be polled by one or more instances of HP SIM. The Virtual Machine Management Pack requires a more persistent connection be maintained with the virtual machine host and the virtual machine guests. Multiple instances of the Virtual Machine Management Pack cannot be used to control the same set of hosts and guests. HP SIM and the Virtual Machine Management Pack are multi-user capable, so multiple instances are not required to provide concurrent access to the HP SIM and Virtual Machine Management Pack consoles.

“Installed, refer to hpvmm.log for the installation status” appears during installation

This message appears during both typical and custom installations of HP SIM. Any issues occurring during a typical installation do not prompt onscreen messages to be displayed. Reviewing the hpvmm.log is the only method to determine the installation status of a typical installation.

“HP SIM service or SQL service is not running. Cancel the installation.” appears during installation

If this message appears either in the hpvmm.log during a typical HP SIM installation or onscreen during a custom installation:

1. Ensure that the HP SIM service is running.

2. Ensure that SQL service is running.

3. Verify that the HP SIM CMS is accessible by connecting to http://HPSIM CMS:280.

http://localhost:280/

Troubleshooting


The Virtual Machine Management Pack 1.11 cannot be installed over a newer version

The Virtual Machine Management Pack 1.11 does not function properly when installed after a newer version of the Virtual Machine Management Pack has been installed.

Uninstalling the Virtual Machine Management Pack and Server Migration Pack

Use either of the following methods to uninstall the Virtual Machine Management Pack. The Virtual Machine Management Pack uninstallation automatically prompts for Server Migration Pack uninstallation.

Refer to the following guidelines to successfully uninstall the Virtual Machine Management Pack and Server Migration Pack:

• Close all Server Migration Pack and Virtual Machine Management Pack screens before attempting uninstallation.

• HP recommends removing any scheduled Virtual Machine Management Pack/Server Migration Pack tasks in HP SIM before uninstalling the Virtual Machine Management Pack/Server Migration Pack. To remove scheduled task in HP SIM:

a. Select Tasks and Logs>View All Scheduled Tasks.

b. Select the tasks related to the Virtual Machine Management Pack/Server Migration Pack from the list of scheduled tasks.

c. Click Delete.

• HP SIM uninstallation also removes the Virtual Machine Management Pack and Server Migration Pack.

• HP SIM and Microsoft SQL Server must be running to successfully uninstall the Virtual Machine Management Pack.

• If the Virtual Machine Management Pack is uninstalled and reinstalled, you must redeploy the VMM agent to the virtual machine hosts.

Uninstalling with the Virtual Machine Management Pack uninstaller shortcut menu

1. Select Start>Programs>HP Virtual Machine Management Pack> Uninstall HP VMM.

2. Click Yes when prompted to confirm the uninstallation.

Uninstalling from the control panel

1. Select Add or Remove Programs.

2. Select HP Virtual Machine Management Pack (remove only)>Change/Remove.


Troubleshooting


Uninstalling the Server Migration Pack

If the Server Migration Pack exists, the VMM uninstaller prompts for Server Migration Pack uninstallation before uninstalling Virtual Machine Pack.

Clicking Yes when prompted to confirm the Server Migration Pack uninstallation will uninstall both the Server Migration Pack and Virtual Machine Management Pack.

Clicking No when prompted to confirm the Server Migration Pack uninstallation only uninstalls the Virtual Machine Management Pack. However, the Server Migration Pack will not be fully functional without the Virtual Machine Management Pack.

To uninstall the Server Migration Pack from the control Panel:

1. Select Add or Remove Programs.

2. Select HP Server Migration Pack (remove only)>Change/Remove.


IMPORTANT: HP recommends selecting Yes when prompted to uninstall the Server Migration Pack before a Virtual Machine Management Pack uninstallation.

Troubleshooting


Uninstalling the VMM agent

To uninstall the VMM agent from the Windows virtual machine hosts:

1. From the Control Panel, select Add or Remove Programs.

2. Select HP VMM Agent (remove only)>Change/Remove.


To uninstall the VMM agent from the VMware ESX Server virtual machine hosts, run the following command at the command prompt:

rpm –e hpvmmagent

Hiding the VM column in the HP SIM console

The Virtual Machine Management Pack uses the VM column in the HP SIM console to identify virtual machine status. If the Virtual Machine Management Pack has been uninstalled, virtual machine status information is no longer updated in the HP SIM console. To hide the column from the console after the Virtual Machine Management Pack has been uninstalled:

1. Click Customize in the top right corner of the All Systems frame.

2. Select VM from the Displayed Columns field, and click (<<).

3. Click OK.

Troubleshooting


"The process cannot access the file because it is being used by another process" message appears during uninstallation

This message might appear during an integrated uninstallation of HP SIM, which also uninstalls the Virtual Machine Management Pack and Server Migration Pack. A Server Migration Pack uninstallation message has been blocked by the Virtual Machine Management Pack message. To prevent this issue, be sure to respond to the Server Migration Pack uninstallation message before the Virtual Machine Management Pack uninstallation is started.

Configuration

Virtual Machine Management Pack menu items are not removed from the HP SIM toolbar with the Virtual Machine Management Pack uninstallation

If any Virtual Machine Management Pack tasks have been scheduled in HP SIM using the HP SIM task scheduler, the corresponding Virtual Machine Management Pack menu item might not be removed from the HP SIM toolbar with the uninstallation of the Virtual Machine Management Pack.

To remove the scheduled tasks in HP SIM:

a. Select Tasks and Logs>View All Scheduled Tasks.

b. Select the tasks related to the Virtual Machine Management Pack from the list of scheduled tasks.

c. Click Delete.

To remove the menu items manually, run the following command from the command prompt at the CMS:

mxtool -r –t “VMM menu item”

where VMM menu item is the Virtual Machine Management Pack menu item displayed in HP SIM toolbar. For example, enter the following command if the Deploy Windows Agent menu item remains in the HP SIM toolbar after uninstalling the Virtual Machine Management Pack:

mxtool –r –t “Deploy Windows Agent”

The Virtual Machine Management Pack might not detect virtual machines located on mapped network drives

The Virtual Machine Management Pack cannot locate virtual machines stored on mapped network drives if the service does not have access to the network shares.

Troubleshooting


Configuring the Virtual Machine Management Pack with a firewall

When managing virtual machine hosts behind a firewall, the firewall must be configured to allow the Virtual Machine Management Pack traffic through the firewall. The Virtual Machine Management Pack uses the following ports:

• Communication between browsers and the VMM Web Service uses HTTPS over port 50010.

• Communication between the VMM Web Service and the VMM Service (both on the HP SIM CMS) uses SSL over port 1124.

• Communication between the VMM Service and VMM agent (on virtual machine hosts) uses SSL over ports 1125 and 1126.

• Communication between the VMM agent during a virtual machine move or copy operation uses SSL over port 1126.

Troubleshooting


Virtual machine hosts cannot be licensed

A virtual machine host can only be licensed with the Virtual Machine Management Pack if it is identified in HP SIM as a virtual machine host. To verify proper identification, click the System Name entry in the HP SIM console. Refer to the System Subtype entry (highlighted in the following figure) to verify the system is identified as a virtual machine host.

If HP SIM does not recognize the virtual machine host, manually run an Identify Systems event by selecting Options>Identify Systems.

Troubleshooting


VMM agent

VMM agent installation fails

The VMM agent installation might fail:

• If there is not enough available disk space on the target host server. The VMM agent requires 100 MB of available disk space on the virtual machine host server to successfully install.

• With the MxAuthentication Failed message. From the DOS prompt on the HP SIM CMS:

a. Enter: mxagentconfig -r -n <Host IP address>

b. Enter: mxagentconfig –a -n <hostname> -u <username> -p <password>

or mxagentconfig (HP SIM 4.2 SP2 only)

c. Enter the host name, user name, and password when prompted.

d. Click Connect to verify a successful connection.

VMM agent registration fails on VMware ESX Server virtual machine host

If the VMM agent registration fails on a VMware ESX Server virtual machine host, the VMware ESX Server host might not be correctly connected to the network. To verify, execute the following command from the VMware ESX Server console.

hostname --ip-address

If the command prints 127.0.0.1, the network is not correctly configured for the VMware ESX Server. To resolve, edit /etc/hosts, and move the external name of the local machine to a new line beginning with its external IP address. For example, if the name of the machine is “volley” and its external IP address is 63.93.12.85, the resulting file will be similar to this example:

127.0.0.1 localhost.localdomain localhost 63.93.12.85 volley.vmware.com volley

Restart the VMware ESX Server network.

IMPORTANT: If DHCP is used on the VMware ESX Server host, the Microsoft DNS server might not map the host name to DHCP-generated IP addresses. HP recommends creating static IP address.

Troubleshooting


To register the agent from the HP SIM toolbar menu:

1. Select Configure>Virtual Machine Management Pack> Register Virtual Machine Host.

2. Select the target VMware ESX Server virtual machine host to register by selecting the checkbox next to the system.


4. Verify that the correct target host appears in the list, and click Change Targets if it is necessary to reselect the target host. Click Next.

5. Click Run Now to register the host immediately.

To register the agent from the command prompt:

Enter: cd /D [VMM installation location]\bin vmcli -registerAgent vmm://IP_address

where IP_address is the IP address of the virtual machine host.

VMM agent registration fails on virtual machine host configured with multiple IP addresses

The Virtual Machine Management Pack always uses the primary IP address of the virtual machine host to communicate between the CMS and the virtual machine hosts.

If the virtual machine host has more than one IP addresses configured and the primary IP address cannot be reached by the CMS, the Virtual Machine Management Pack cannot register and manage the virtual machine host. Refer to the following example:

Virtual machine host “VMHost1” has two IP addresses with the following configuration order:

1. 192.168.1.1 (Primary) 2. 172.16.101.30 (Secondary)

The CMS has IP address: 172.16.101.29

The CMS can ping only the secondary network configuration of the virtual machine host. If you attempt to register the virtual machine host from the HP SIM console toolbar or by using the following command:

cd /D [VMM installation location]\bin vmcli -registerAgent vmm://172.16.101.30

Troubleshooting


The following error occurs: Agent registration failed – 170.16.101.30

java.rmi.connect Exception: Connection refused to host: 192.168.1.1; nested exception is: java.net.connect Exception: Connection time out: Connect".

This connection time-out occurs because the VMM agent registration is attempting to bind itself to the primary IP address of the virtual machine host, which in this case is 192.168.1.1. This IP address cannot be reached by the CMS.

To resolve this issue, re-order the network connections in the virtual machine host and verify that the virtual machine host primary IP address can be pinged from the CMS. Restart the VMM agent service on the virtual machine host and attempt the virtual machine host registration again.

IMPORTANT: If DHCP is used on the VMware ESX Server host, the Microsoft DNS server might not map the host name to DHCP-generated IP addresses. HP recommends creating static IP address.

The virtual machine host must be re-registered if the IP address or name of the virtual machine host is changed

To unregister and re-register the virtual machine host from the HP SIM toolbar menu:

CAUTION: Unregistering a virtual machine host permanently removes all information from the Virtual Machine Management Pack database pertaining to the virtual machine guests located on this host, including backup information.

1. Select Configure>Virtual Machine Management Pack> Unregister Virtual Machine Host.

2. Select the target virtual machine host to unregister by selecting the checkbox next to the system.



5. Click Run Now to unregister the host immediately.

6. After the host has been unregistered, select Configure>Virtual Machine Management Pack>Register Virtual Machine Host.

7. Repeat the previous steps 2 through 5 to register the host again.

Troubleshooting


To unregister and re-register the virtual machine host from the command prompt:

1. Enter: cd /D [VMM installation location]\bin vmcli -unregisterAgent vmm://IP_address

where IP_address is the IP address of the previous virtual machine host.

2. Enter: cd /D [VMM installation location]\bin vmcli -registerAgent vmm://IP_address

where IP_address is the IP address of the new virtual machine host.

“Agent Registration failed” appears in the HP SIM task log after upgrading the VMM agent

After upgrading the VMM agent, the following message might appear in the HP SIM task log:

Registering Agent Agent registration failed! – hostname

where hostname is the virtual machine host name. To resolve this issue, register the virtual machine host manually. From the HP SIM toolbar, select Configure>Virtual Machine Management Pack>Register Virtual Machine Host.

The Virtual Machine Management Pack console

Virtual machine host and guests do not appear in the Virtual Machine Management Pack console

• If the virtual machine host and guests were previously accessible in the Virtual Machine Management Pack console and display an Information icon in the HP SIM console, verify that the host is still licensed. If the host was originally licensed with a demo license, the license might have expired. License the host with a permanent license.

• If the virtualization technology was installed on the host after the VMM agent was installed, click Restart VMM Agent on the Virtual Machine Management Pack host console.

The Virtual Machine Management Pack console does not display the system name, system IP address, and operating system

The Virtual Machine Management Pack 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 the Virtual Machine Management Pack console, verify that the virtual machine guest has been discovered by HP SIM. If the guest has not been discovered, perform an Automatic Discovery of the undiscovered virtual machine hosts and guests from the HP SIM console by selecting Options>Discovery.

Troubleshooting


Critical status is displayed for a virtual machine host in the Virtual Machine Management Pack console

Critical status might display when a virtual machine host is unavailable. Ping the host to determine if communication is established. If communication does not exist, the virtual machine host no longer exists. To remove the host from console from the HP SIM toolbar menu:

1. Select Configure>Virtual Machine Management Pack>Unregister Virtual Machine Host.

2. Select the target virtual machine host to unregister by selecting the checkbox next to the system.



5. Click Run Now to unregister the host immediately.

To unregister the virtual machine host from the command prompt, enter the following command:

cd /D [VMM installation location]\bin vmcli -unregisterAgent vmm://IP_address

where IP_address is the IP address of the virtual machine host.

A blank page appears when launching the Virtual Machine Management Pack console from HP SIM

This condition occurs when the CMS name link is not resolved correctly on the network. 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. In addition, be sure to include this link as a trusted site in the Internet Explorer browser security settings.

The status displayed in the left pane of the Virtual Machine Management Pack console does not match the status displayed in the right pane

The left pane of the Virtual Machine Management Pack console is automatically updated every minute. The right pane is updated every minute or when the Virtual Machine Management Pack detects a status change. To synchronize the information displayed on the console, refresh the browser window.

Virtual machine status is not updated

Virtual machine status might not be updated because the Virtual Machine Management Pack is unable to communicate with the HP SIM database. Restart the Virtual Machine Management Pack service to correct this issue.

Troubleshooting


Virtual machine guest information becomes inaccessible in the Virtual Machine Management Pack console

Virtual machine guest information might become inaccessible in the Virtual Machine Management Pack console after a period. Restart the VMM agent on the virtual machine host, and manually run an Identify Systems event on the virtual machine guests by selecting Options>Identify Systems.

A virtual machine host appears in the Virtual Machine Management Pack console multiple times

Redeploying the VMM agent to a virtual machine host with multiple IP addresses might register the virtual machine host more than once with different IP addresses. The host appears twice in the Virtual Machine Management Pack console, one licensed and one unlicensed. Unregister the unlicensed host to resolve.

The Virtual Machine Management Pack console displays “No virtualization layer available for this host”

After rebooting the virtual machine host, the Virtual Machine Management Pack console might display “No Virtualization Layer Available for this Host.” To resolve this issue, manually restart the VMM agent from the virtual machine host.

Virtual Machine Management Pack functions

Using a virtual machine host not managed by the Virtual Machine Management Pack as a template/backup repository

The Virtual Machine Management Pack relies on the transport mechanisms in the VMM agent. Therefore, virtual machine transfers can only occur on virtual machine hosts managed by the Virtual Machine Management Pack. To overcome this limitation, map a network drive from a Virtual Machine Management Pack virtual machine host to the unmanaged virtual machine host where you want to store templates or backups.

“HTTP ERROR: 500 Internal Server Error” appears during a Virtual Machine Management Pack move or copy operation

This error can occur when the network is busy during the move or copy operation and can be corrected by refreshing the browser.

Troubleshooting


The Virtual Machine Management Pack cannot move virtual machines with certain disk types

The Virtual Machine Management Pack does not move or copy virtual machines with the following disk types when installed with the indicated virtualization technology.

Disk type Virtualization technology

Linked disk

Differencing disk Microsoft Virtual Server 2005

VMware ESX Server Physical (RAW) disk

VMware GSX Server

Virtual machine files are not deleted after a move

The Virtual Machine Management Pack does not delete virtual machine guest files after a move, allowing the virtual machine guest to be restored on the source host, if required.

Virtual machine devices might not be available after a copy or move

If virtual machine devices are not available after a move or copy, manually reconfigure the virtual network connections on the moved or copied virtual machine guest.

A shutdown or restart operation fails or does not complete

Microsoft Virtual Server Additions or VMware Tools must be installed on virtual machine guests before a shutdown or reset can be successfully performed. To install Microsoft Virtual Server Additions or VMware Tools, refer to Chapter 3.

Launching the remote console from the Virtual Machine Management Pack console might fail

• VMware GSX Server—Verify that the VMware Management Interface software is installed by verifying that the VMware Management Interface directory exists within the VMware installation directory. For information, refer to the VMware Knowledge Base Answer ID 793 at http://www.vmware.com/support/kb.

Also, verify that the VMware GSX Server Web port is 8222, the default port. If not, update the Web port in the Virtual Machine Management Pack configuration setting:

a. In the C:\Program Files\HP\Virtual Machine Management Pack\bin directory, locate the hpvmm.conf file.

b. Modify the port number specified in the VMwaregsxport to the default port.

c. Save the file, and restart the Virtual Machine Management Pack services.

http://www.vmware.com/support/kb

Troubleshooting


• VMware ESX Server—Verify that the VMware ESX Server Web port is 80, the default port. If not, update the Web port in the Virtual Machine Management Pack configuration setting:


b. Modify the port number specified in the VMwareesxport to the default port.


• Microsoft Virtual Server 2005—Verify that the Microsoft Virtual server Web port is 1024, the default port. If not, complete the following steps to update the Microsoft Virtual Server 2005 Web port in the Virtual Machine Management Pack configuration setting.


b. Modify the port number specified in the MSVSPort to the default port number.


NOTE: All virtual machine host port numbers will be changed when the configuration setting is modified.

HP SIM console integration

The HP SIM console does not identify a server as a virtual machine host

To verify proper system identification in HP SIM, click the System Name entry. Refer to the System Subtype entry to verify the system is identified as a virtual machine host.

If HP SIM does not recognize the virtual machine host, manually run an Identify Systems event on the virtual machine guests by selecting Options>Identify Systems.

The HP SIM console does not discover a virtual machine host or guest 1. On a Windows 2003 virtual machine host, select Services>SNMP Properties.

2. Click the Security tab.

3. Add the HP SIM CMS IP address to the Accept SNMP Packets from these hosts field.

4. Enter the user name and password in the Default WBEM Settings field.

5. From the HP SIM console, select Options>Discovery.

6. In the Discovery configuration field, deselect the Use discovery filters checkbox, and click Save.

7. Perform a discovery of the undiscovered virtual machine hosts and guests.

NOTE: For information about performing basic HP SIM tasks, refer to the HP Systems Insight Manager Installation and User Guide.

Troubleshooting


The HP SIM console identifies a virtual machine guest as an Unknown or Unmanaged device

1. Select Services on the virtual machine guest, and verify that Windows Management Instrumentation service is listed and started.

NOTE: To install WMI on Windows NT virtual machine guests, refer to http://www.microsoft.com/downloads/release.asp?releaseid=18490.

2. From the HP SIM CMS Control Panel, select Add or Remove Programs, and verify that Pegasus WMI Mapper 2.0 is installed.

3. Select Services on the HP SIM CMS, and verify that Pegasus WMI Mapper service is listed and started.

4. From the HP SIM console, select Options>Protocol Settings>Global Protocol Settings, and verify that the correct user name and password are entered.

5. Verify that no virtual machine guest host names begin with the underscore character.

6. Run an Identify Systems event on the virtual machine guests by selecting Options>Identify Systems.

Linux virtual machine guest association is not displayed in the HP SIM console

HP SIM identifies Linux virtual machine hosts system type as Unknown. Therefore, the association between the host and guest cannot be displayed in the HP SIM console.

The Virtual Machine Management Pack version displayed in HP SIM is incorrect

After upgrading from HP SIM 4.2 with Virtual Machine Management Pack 1.00/1.10 to HP SIM 5.0 with Virtual Machine Management Pack 1.11, the incorrect version might be displayed when Help>About HP Systems Insight Manager is selected from the HP SIM toolbar.

To find the correct version number, select Start>Control Panel>Add/Remove Programs> Virtual Machine Management Pack>Support Information Link.

http://www.microsoft.com/downloads/release.asp?releaseid=18490

Troubleshooting


Additional resources

The HP ProLiant Servers Troubleshooting Guide provides simple procedures for resolving common problems, as well as a comprehensive course of action for fault isolation and identification, error message interpretation, issue resolution, and software maintenance.

To obtain the guide, refer to any of the following sources, and then select the HP ProLiant Servers Troubleshooting Guide.

• 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 the appropriate server.

http://www.hp.com/support

http://www.docs.hp.com/

HP ProLiant Essentials Virtual Machine Management Pack User Guide Glossary-1

Glossary

CMS HP SIM Central Management Server

ESX VMware’s Red Hat Linux-based host operating system that provides a virtual machine solution.

GSX VMware’s Windows- or Linux-based host operating system that provides a virtual machine solution.

guest operating system A reference to a distinct operating system instance running in a virtual machine.

host operating system A reference to the operating system that is the foundation for a virtual machine.

HP SIM HP Systems Insight Manager

legacy operating system An older operating system, often incompatible with up-to-date hardware. Virtual machines allow legacy operating system to run on new hardware.

SMP HP ProLiant Essentials Server Migration Pack

total estimated transport volume The total volume, consisting of several disks plus configuration files

virtual machine Emulates a complete hardware system from processor to network card in a self-contained, isolated software environment, enabling the simultaneous operation of otherwise incompatible systems.

Glossary

Glossary-2 HP ProLiant Essentials Virtual Machine Management Pack User Guide

virtualization The representation of hardware through software. Virtual machines are an example of virtualization, as are virtual memory and virtual disks.

Virtual Server Microsoft’s host operating system that provides a virtual machine solution.

VMM HP ProLiant Essentials Virtual Machine Management Pack

HP ProLiant Essentials Virtual Machine Management Pack User Guide Index-1

Index

A

adding licenses 4-2 additional help resources vii administration

configure settings 3-6 licensing 4-1

agents deployment A-10 Insight Manager Agents for VMware ESX

Server 2-2 Linux agent deployment 3-7 uninstalling A-6 VMM agent deployment 3-7 VMM agent requirements 2-2 Windows agent deployment 3-7

B

backing up a virtual machine guest 5-11 browser

support 2-1 synchronizing A-14

C

Central Management Server configuration 3-6 requirements 2-1

components installed 3-5 requirements 2-1

configuration MxAgentConfig 3-6 OpenSSH 3-6 SNMP properties A-17 Systems Insight Manager 3-6 troubleshooting A-7 Virtual Machine Management Pack 3-6 VMware ESX Server A-10

console accessing 5-1 accessing the remote console 5-12 browser support 2-1 customizing A-6 guest performance information 5-4 host performance information 5-3 integration 1-2 overview 5-1 remote A-16 system identification 4-3, A-9, A-17 Virtual Machine Management Pack A-13

copying a virtual machine guest 5-9 creating a virtual machine guest template 5-12, 5-14 credentials

Systems Insight Manager 3-6 Web Based Enterprise Management 3-6

D

discovery in Systems Insight Manager 3-6, A-17 disk space, requirements 2-1

E

error messages A-1

F

FAQs A-1 firewall A-8 first-time installation, Virtual Machine Management

Pack 3-1 flexible-quantity license 4-2 free license 4-1

G

global protocol settings 3-6 guest

icons 1-3 requirements 2-2

Index

Index-2 HP ProLiant Essentials Virtual Machine Management Pack User Guide

H

hardware requirements 2-1 help resources vii host

icons 1-3 requirements 2-2

HP authorized reseller viii HP ProLiant Essentials Virtual Machine Management

Pack See Virtual Machine Management Pack HP SIM See Systems Insight Manager

I

icons HP SIM 1-3 Virtual Machine Management Pack 5-6

identification in Systems Insight Manager 4-3, A-9, A-17

installation file location 3-5 Microsoft Virtual Server Additions 3-8 troubleshooting A-3 uninstalling A-4 Virtual Machine Management Pack 3-1 VMware Tools 3-8

L

license adding 4-2 applying 4-3 free 4-1 options 4-2 preparation 4-1 purchasing 4-2 troubleshooting A-9

Linux agent, deployment 3-7

M

Microsoft Virtual Server accessing remote console 5-12 Additions 3-8 requirements 2-2

Microsoft Windows NT, requirements 2-2 moving a virtual machine guest 5-10 MxAgentConfig 3-6 MxAuthentication A-10

O

OpenSSH configuration 3-6 requirements 2-1

P

pausing a virtual machine guest 5-8 purchasing licenses 4-2

R

remote console 5-12 requirements

Central Management Server 2-1 disk space 2-1 operating systems 2-2 Systems Insight Manager 2-1 virtual machine guest 2-2 virtual machine host 2-2 Virtual Machine Management Pack 2-1 virtualization technology 2-2

resetting a virtual machine guest 5-8 restarting a virtual machine guest 5-8 resuming a virtual machine guest 5-7

S

server, requirements 2-1 settings, protocol 3-6 shutting down a virtual machine guest 5-7 single-server license 4-2 SMNP properties A-17 software requirements 2-1 starting a virtual machine guest 5-7 status column

icons 1-3 removing A-6

stopping a virtual machine guest 5-7 system protocol settings 3-6 Systems Insight Manager

accessing target systems 3-6 configuration 3-6 console integration 1-2 customizing A-6 discovery 3-6, A-17 file location 3-5 icons 1-3 identify systems 4-3, A-9, A-17 requirements 2-1 toolbar 3-5

T

telephone numbers viii tracking license 4-2 troubleshooting A-1

Index

HP ProLiant Essentials Virtual Machine Management Pack User Guide Index-3

U

uninstalling A-4 Virtual Machine Management Pack A-4 VMM agent A-6

upgrading Virtual Machine Management Pack 3-9 VMM agent 3-9

V

virtual machine guest backing up 5-11 copying 5-9, A-16 creating template 5-12, 5-14 discovery 3-6, A-17 icons 1-3 Microsoft Virtual Server Additions

installation 3-8 moving 5-10, A-16 pausing 5-8 requirements 2-2 resetting 5-8 restarting 5-8, A-16 resuming 5-7 shutting down 5-7, A-16 starting 5-7 stopping 5-7 VMware Tools installation 3-8

virtual machine host discovery 3-6, A-17 icons 1-3 requirements 2-2 VMM agent deployment 3-7

Virtual Machine Management Pack accessing console 5-1 accessing the remote console 5-12 configuration 3-6 console icons 5-6 file location 3-5 guest console 5-4 host console 5-3 infrastructure 1-1 installing 3-1 overview 1-1 toolbar 3-5 uninstallation A-4 upgrading 3-9 VM column 1-2

VMM agent deployment 3-7, A-10 registration A-10, A-12 requirements 2-2 restarting A-13 uninstalling A-6 upgrading 3-9

VMware accessing remote console 5-12 ESX Server configuration A-10 requirements 2-2 Tools 3-8

W

Web Based Enterprise Management credentials 3-6 website vii, viii Windows agent, deployment 3-7 Windows Management Instrumentation (WMI) 2-1,

2-2

hp proliant essentials virtual machine management pack ...h10032.valid license from hp required for...

Documents