Вы находитесь на странице: 1из 50

HP Insight Dynamics VSE 6.

2: Integrity CMS Installation and Configuration Guide

HP Part Number: T8671-9101 1 Published: October 2010

Copyright 2006-2010 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. Acknowledgments HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Table of Contents
1 Introduction......................................................................................................................7 2 System requirements.......................................................................................................9
HP Systems Insight Manager.................................................................................................................9 Compatibility with HP-UX Bastille and other network firewalls..........................................................9 Additional requirements in the release notes and support matrix........................................................9

3 Installation.....................................................................................................................11
Overview checklist for installing ID-VSE for Integrity.......................................................................11 Overview checklist for upgrading ID-VSE for Integrity.....................................................................11 Prepare for installation.........................................................................................................................12 Preinstallation steps for Linux managed systems...........................................................................13 Preinstallation steps for Microsoft Windows managed systems....................................................14 Before upgrading from a previous version...........................................................................................15 Install the software on the CMS............................................................................................................16 Start and configure HP SIM..................................................................................................................18 Install Insight Dynamics agent software and configure managed systems.........................................21 Using managed system setup wizard.............................................................................................21 Privilege elevation...........................................................................................................................21 Alternate procedure for manual installation of agent software......................................................21 After upgrading from a previous version............................................................................................23 Postinstallation update of gWLM agents..............................................................................................24 Preparing a Red Hat Linux managed system.......................................................................................24 Preparing a ProLiant SUSE Linux managed system............................................................................25

4 Configure ID-VSE for Integrity...................................................................................27


Configuring user authorizations..........................................................................................................27 Role: ID operator, application administrator, or capacity planner.................................................28 Role: ID system administrator.........................................................................................................28 Role: ID senior system administrator..............................................................................................28 Role: senior capacity planner...........................................................................................................29 Role: storage administrator.............................................................................................................29 Role: legacy Global Workload Manager operator...........................................................................29 Role: legacy Global Workload Manager administrator...................................................................30 Selecting and updating the authorized systems set........................................................................30 Complete the certificate exchange for Application Discovery.............................................................30 Using HP SIM to complete certificate exchange.............................................................................30 Completing certificate exchange from the command line..............................................................31

5 Support and other resources.......................................................................................33


Contacting HP.......................................................................................................................................33 Information to collect before contacting HP...................................................................................33 How to contact HP technical support.............................................................................................33 HP authorized resellers...................................................................................................................33 Documentation feedback.................................................................................................................33 Related information..............................................................................................................................33 Command references (manpages)...................................................................................................34 Reference pages installed on the CMS.......................................................................................34
Table of Contents 3

Reference pages installed with agent software on managed systems.......................................34 Reference page installed on cell-based complexes....................................................................35 Reference pages installed on systems running HP Integrity Virtual Machines........................35 Selected HP Systems Insight Manager software reference pages..............................................35

A Command reference....................................................................................................37
vseinitconfig(1M)..................................................................................................................................38

B Back up the CMS configuration..................................................................................43


Back up your existing CMS configuration prior to upgrading the software........................................43

C Removing ID-VSE for Integrity...................................................................................45 Index.................................................................................................................................47

Table of Contents

List of Tables
3-1 3-2 Checklist for installing ID-VSE for Integrity on an HP-UX CMS................................................11 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS..............................................12

List of Examples
3-1 3-2 3-3 Install the Utilization Provider on an HP-UX system...................................................................22 Install the HPVM Provider on a Red Hat Enterprise Linux 4 (Integrity) system.........................22 Install the Utilization Provider on a 32bit Windows system......................................................22

List of Examples

1 Introduction
This document describes the installation and configuration of HP Insight Dynamics - VSE suite for Integrity (ID-VSE for Integrity) . It is intended to be used by Insight Dynamics system administrators, Insight Dynamics application administrators, capacity planners, and other technical professionals involved with data center operations, administration, and planning. An understanding of HP-UX system administration concepts and procedures is assumed. Installing, updating, and configuring ID-VSE for Integrity involves performing the following tasks: Checking hardware and software requirements for ID-VSE for Integrity. Installing ID-VSE for Integrity on the CMS. Upgrading ID-VSE for Integrity from previous versions of the software. Installing agent software and WBEM providers on managed systems. Performing post-install or post-upgrade configurations of ID-VSE for Integrity. Backing up and restoring the ID-VSE for Integrity database. For an overview of ID-VSE for Integrity and key Insight Dynamics concepts and terminology see the HP Insight Dynamics 6.2 Getting Started Guide. For detailed information about supported hardware and software, see HP Insight Software 6.2 Support Matrix.

2 System requirements
The following sections provide a summary of the hardware and software requirements of ID-VSE for Integrity version 6.2 installed on a CMS running HP-UX. For detailed information about supported hardware and software, including requirements for a CMS running HP-UX or Microsoft Windows, see the HP Insight Software 6.2 Support Matrix.

HP Systems Insight Manager


ID-VSE for Integrity version 6.2 runs under HP Systems Insight Manager (HP SIM) Version 6.0 or later. If you are currently using an earlier version of HP SIM, see Before upgrading from a previous version (page 15) for the recommended upgrade procedure. NOTE: When updating to HP SIM 6.0 or later, you must also update to ID-VSE for Integrity version 6.0 or later. ID-VSE for Integrity version 4.x is not compatible with HP SIM 6.0. System requirements for HP SIM are defined in the HP Systems Insight Manager 6.0 Installation and Configuration Guide for HP-UX (available at http://www.hp.com/go/hpsim). Refer to that document for information about HP SIM requirements and dependencies. In particular, note that you might need to install HP-UX patches before you install HP SIM. In addition to the requirements imposed by HP SIM, the requirements for this release of ID-VSE for Integrity are described in the HP Insight Software 6.2 Support Matrix.

Compatibility with HP-UX Bastille and other network firewalls


Network firewall software such as HP-UX Bastille might block the communication protocols used by ID-VSE for Integrity. If your CMS or Insight Dynamics managed systems use firewall software, follow the port configuration guidelines in the HP Insight Software 6.2 Support Matrix.

Additional requirements in the release notes and support matrix


For additional requirements and installation notes, see the following documents: HP Insight Dynamics 6.2 Release Notes HP Integrity Virtual Machines Release Notes HP Insight Software 6.2 Support Matrix The latest versions of these documents can be downloaded from http://www.hp.com/go/ insightdynamics/docs.

HP Systems Insight Manager

10

3 Installation
Install HP SIM and ID-VSE for Integrity using Table 3-1. IMPORTANT: Starting with VSE Management Software version 4.0 (A.04.00.07.xx), licenses for ID-VSE for Integrity are managed in the HP SIM License Manager database on the CMS. When you upgrade an HP-UX CMS that has a previous version of ID-VSE for Integrity installed, any product licenses that were previously installed or scanned are automatically migrated to the License Manager database. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide.

Overview checklist for installing ID-VSE for Integrity


Use Table 3-1 for an overview of the installation process for ID-VSE for Integrity on an HP-UX CMS. Table 3-1 Checklist for installing ID-VSE for Integrity on an HP-UX CMS
Task Obtain ID-VSE for Integrity installation package. Information ID-VSE for Integrity is available as a single download from the Software Depot website:

IMPORTANT: The software includes a 90-day trial license for HP 9000 and HP Integrity managed systems. For details about ID-VSE http://h20293.www2.hp.com/portal/ for Integrity licenses, see the HP Insight Dynamics 6.2 Getting Started swdepot/ displayProductInfo.do?productNumber=vse Guide. Prepare for installation (page 12) Prepare for ID-VSE for Integrity installation by installing the required software and patches, establishing common WBEM user credentials on the CMS and managed systems, and completing preinstallation steps for Linux and Microsoft Windows managed systems. Install HP SIM and ID-VSE for Integrity on the CMS. If HP SIM was upgraded, launch HP SIM and run the First Time Wizard and the Discovery processes. Install the WBEM providers and other agent software on your managed systems. Configure ID-VSE for Integrity for your environment. IMPORTANT: ID-VSE for Integrity does not operate correctly until you complete these postinstallation configuration steps. You must perform these steps even when you are reinstalling or updating an existing installation. Install the software on the CMS (page 16) Start and configure HP SIM (page 18) Install Insight Dynamics agent software and configure managed systems (page 21) Configure ID-VSE for Integrity (page 27)

Overview checklist for upgrading ID-VSE for Integrity


Use Table 3-2 for an overview of the upgrade process for ID-VSE for Integrity on an HP-UX CMS.

Overview checklist for installing ID-VSE for Integrity

11

Table 3-2 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS
Task Make a backup of the ID-VSE for Integrity database. Perform the upgrade preinstallation steps. Upgrade HP SIM and ID-VSE for Integrity on the CMS. If HP SIM was upgraded, launch HP SIM and run the First Time Wizard and the Discovery processes. Information Appendix B (page 43) Before upgrading from a previous version (page 15) Install the software on the CMS (page 16) See Start and configure HP SIM (page 18).

As needed, update the WBEM providers and other agent software See Install Insight Dynamics agent on your managed systems. software and configure managed systems (page 21). Perform post-upgrade steps. After upgrading from a previous version (page 23)

Prepare for installation


For a description of HP SIM patch requirements see the HP Systems Insight Manager 6.0 Installation and Configuration Guide for HP-UX, available from the Information Library link at http:// www.hp.com/go/hpsim. Verify that your CMS and managed systems meet ID-VSE for Integrity system requirements described in System requirements (page 9). Look for any updates to the requirements or installation instructions in the HP Insight Dynamics 6.2 Release Notes. The latest version of this document can be downloaded from the Insight Dynamics information library at http://www.hp.com/go/insightdynamics/docs. NOTE: HP SIM displays a message on the login page as follows if the browser configuration is not correct for HP SIM menus:
Your browser's zone security settings are not compatible with the HP SIM popup menu.

The following setting must be enabled in your current zone: Internet OptionsSecurityCustom LevelMiscellaneousAllow script-initiated windows. This setting is enabled by default for the medium-low security level such as the local intranetzone. Establish common WBEM credentials on the CMS and on the managed systems to allow authenticated access to WBEM data. ID-VSE for Integrity uses WBEM connections to obtain information from the managed systems. To avoid having to maintain multiple WBEM user accounts and passwords, HP recommends that you use one of the following WBEM authentication models: Global Sign-In Credentials Global credentials apply to all systems and enable you to configure default, system-wide, protocol-wide credentials. To set global sign-in credentials select OptionsSecurityCredentialsGlobal Credentials from the HP SIM menu.. You must enter root (or Administrator) level user credentials for the sign-in credentials to be used by the Configure or Repair Agents feature. To list the current credentials for a system, select OptionsSecurityCredentialsSystem Credentials from the HP SIM menu.. WBEM Certificate-Based Authentication You can configure WBEM authentication for a single system or a selected set of systems by selecting OptionsSecurityCredentialsSystem Credentials from the HP SIM menu and using the advance settings WBEM/WMI tab. To authenticate through a certificate instead of using

12

Installation

a WBEM user account and password, select Use certificate instead. Online help for this option is available in HP SIM. Online help for certificates in general can be found in the HP SIM help system under the Networking and Security topic. NOTE: On all HP-UX managed systems, HP WBEM Services for HP-UX version A.02.05 or later is required in order to use certificate-based WBEM authentication. For more information about WBEM security configuration in HP SIM, see the HP white paper Understanding HP SIM 5.3 Security, available from the Information Library link at http:// www.hp.com/go/hpsim.

Preinstallation steps for Linux managed systems


On managed systems running Red Hat Enterprise Linux, disable SELinux to avoid conflicts with the WBEM providers and agent software. In order for Linux managed systems to be correctly discovered by HP SIM, you must install WBEM and the required WBEM providers from the HP Integrity Essentials Foundation Pack for Linux Management CD. Download and install the contents of this CD using Procedure 3-1. Procedure 3-1 Download and install Linux management software 1. 2. 3. On the HP Open Source and Linux website at http://hp.com/go/integritylinux, click the HP Integrity Essentials Foundation Pack for Linux link. Click the Download for HP Integrity Essentials Foundation Pack for Linux link. Click the HPIEFPL - Support Pack link. The HP Integrity Essentials Foundation Pack for Linux - Support Pack page has installation requirements and instructions. 4. 5. Click Receive for Free and select the appropriate software specification. After entering information in the required fields, click Next to download the software. Install the software according to the instructions included on the HP Integrity Essentials Foundation Pack for Linux - Support Pack page or in the docs directory contained in the tar file. Make sure that the tog-pegasus package is installed and running on the system. On Red Hat Enterprise Linux, you might need to modify the file /etc/Pegasus/ access.conf to allow WBEM access using your designated WBEM user name and password. Perform the following steps to configure this file. In this example, your designated WBEM user name is assumed to be wbemuser. a. Look for the following line in this file:
-: ALL EXCEPT pegasus:wbemNetwork

6. 7.

b.

Change this line to either of the following options:


# Allow access only from user 'wbemuser': -: ALL EXCEPT wbemuser pegasus:wbemNetwork # Allow access by all users: +: ALL EXCEPT :wbemNetwork

c.

If tog-pegasus is not running, start it by executing the following command:


# /etc/init.d/tog-pegasus start

OpenSSH on Linux managed systems must be configured for use by HP SIM. Normally you can use the same procedure that is used to configure OpenSSH for HP SIM on HP-UX managed systems, as described in Install Insight Dynamics agent software and configure managed systems (page 21). However, if you are using SUSE Linux Enterprise Server 9, you must first manually configure OpenSSH to use password authentication.
Prepare for installation 13

IMPORTANT: SUSE Linux Enterprise Server 9 ships with SSH configured to use PAM authentication instead of password authentication. Password authentication is required in order for the mxagentconfig to configure OpenSSH for use by HP SIM. On managed systems running SUSE Linux Enterprise Server 9, change to password authentication using Procedure 3-2. Procedure 3-2 Configure SUSE Linux for password authentication 1. Configure the following lines in /etc/ssh/sshd_config on the managed system:
PasswordAuthentication yes #UsePAM yes

2. 3.

Retrieve the process ID of the running sshd from the file /var/run/sshd.pid. Restart sshd by executing the following command:
# kill -SIGHUP pid

where pid is the sshd process ID.

Preinstallation steps for Microsoft Windows managed systems


On Windows managed systems OpenSSH is not installed by default, but it can be installed from the HP Smart Setup installation media (version 4.5 or later). Use Procedure 3-3 to install OpenSSH and configure it for use with HP SIM. You can then install the Insight Dynamics agent software and WMI/WBEM providers from HP SIM using the procedure described in Install Insight Dynamics agent software and configure managed systems (page 21). Procedure 3-3 Install and configure OpenSSH for Windows 1. Follow the instructions in the HP Smart Setup CD to install OpenSSH Services on the Windows managed system. During installation you must specify the user name and password for the account that runs the OpenSSH service. The Administrator account is typically used for this. NOTE: During installation, OpenSSH automatically imports your local user accounts into its password file. If additional accounts are added later, you must reinstall OpenSSH or use the sshuser command to import the new user account information into OpenSSH. 2. 3. Reboot the Windows managed system to enable SSH communication. Configure OpenSSH for use with HP SIM by executing the following command on the CMS:
# mxagentconfig -a -n node-hostname -u Administrator -p password

where node-hostname is the name of the system as it is known by HP SIM. If the system administrator user account on your managed system is not Administrator, substitute your administrator user name in the preceding command. You can use multiple -n options to perform this operation on more than one managed system.

14

Installation

NOTE: This step can be performed within HP SIM by selecting the managed systems to configure, then selecting ConfigureConfigure or Repair Agents... from the HP SIM menu bar. On the Configure or Repair Settings page, select Configure secure shell (SSH) access. 4. If you are using Partition Manager to manage Windows systems, you must also create a user account named root on those Windows systems. Partition Manager uses this user name for remote execution of nPartition commands through OpenSSH. Add this user to the Administrators group in Windows, then add this user to OpenSSH using the sshuser command. To configure remote connections from the CMS using the root account, execute the following command on the CMS:
# mxagentconfig -a -n node-hostname -u root -p root-password

OpenSSH is now configured for connections from the CMS (with host-based authentication), using either the Administrator or root account. Partition Manager uses the root account for remote command execution.

Before upgrading from a previous version


This section describes the steps you must perform before upgrading from an earlier version of ID-VSE for Integrity to version A.6.2.0.*. This process converts an existing ID-VSE for Integrity database, including historical profile data, to the new version database format. Any historical profile data that you want to migrate to the new database format must be installed in the currently running installation on the CMS. IMPORTANT: Starting with VSE Management Software version 4.0 (A.04.00.07.xx), licenses for ID-VSE for Integrity are managed in the HP SIM License Manager database on the CMS. When you upgrade an HP-UX CMS that has a previous version of ID-VSE for Integrity installed, any product licenses that were previously installed or scanned are automatically migrated to the License Manager database. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide. Make a backup The upgrade process is not reversible. It can only be undone by removing version A.6.2.0.* and reinstalling the older version. Make a backup of your ID-VSE for Integrity database before upgrading the software, in case you need to revert to the previous version. You can use this backup to restore your current configuration after reverting to the previous version of the software. Use Procedure 3-4 to prepare for the upgrade. NOTE: You can also use this procedure to upgrade from gWLM version A.02.xx to ID-VSE for Integrity version A.6.2.0.*. In this case, you can ignore the steps that concern existing versions of other ID-VSE for Integrity (for example, Capacity Advisor). After upgrading, be sure to follow the instructions in After upgrading from a previous version (page 23). In particular, see the issue described in Rediscover partition-based SRDs (page 23). Procedure 3-4 Prepare for ID-VSE for Integrity upgrade 1. If you are using gWLM, undeploy all shared resource domains (SRDs) and stop using the existing version, including the command-line interface. You can continue running the gWLM daemons (gwlmcmsd and gwlmagent) and the WBEM service and provider daemons. Stop using the version of Capacity Advisor that is already installed, including the command-line interface. If necessary, use the following substeps to disable each automatically scheduled Capacity Advisor data collection task:
Before upgrading from a previous version 15

2.

a. b. c. d. e. f. g. 3. 4. 5.

Select Tasks & LogsView All Scheduled Tasks from the Capacity Advisor menu bar. Select the task from the list Collect Capacity Advisor Data. Click Edit. Click Schedule. Check the Disable this task check box. Click Done. Verify that the task you just edited is in the list and now shows Task is Disabled in the Schedule column.

Log out of HP SIM. (Optional) Use the capcollect command to collect the latest Capacity Advisor data into the ID-VSE for Integrity database. For more information, see capcollect(1M). Make a Backup Make a backup of your existing ID-VSE for Integrity database. You can use this backup if you need to revert to the older version of the software. With this backup, you can restore your current configuration after reverting to the older version of the software. You cannot restore this backup after version A.6.2.0.* is installed. Previous versions of ID-VSE for Integrity used a database format that is incompatible with version A.6.2.0.*. For more information about backing up and restoring the ID-VSE for Integrity database and reverting to a backup from a previous version of the software, see vseinitconfig(1M). This manpage is included in this manual in Appendix A (page 37). For information about backing up the HP SIM database, refer to the HP white paper Backing up and restoring HP Systems Insight Manager data files in an HP-UX or Linux environment, available from the Information Library link at http://www.hp.com/go/hpsim.

6.

If you are upgrading to a new version of HP SIM, follow any upgrade preparation instructions provided with the new version of HP SIM. In particular, note that you might need to install additional patches.

After you complete the installation steps in the following sections, see After upgrading from a previous version (page 23) for additional steps that you should perform.

Install the software on the CMS


Use Procedure 3-5 to install HP SIM version 6.0 or later and ID-VSE for Integrity on the CMS. If you have already installed this version of HP SIM, you can use Procedure 3-6 instead.

16

Installation

Procedure 3-5 Install or upgrade HP SIM and ID-VSE for Integrity 1. Enter the following command on the CMS:
# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file HPSIM-HP-UX VSEMgmt

IMPORTANT:

The system reboots after the installation.

The actions that occur after system reboot depend on whether this is a new installation of HP SIM or an upgrade to an existing HP SIM installation. New installation of HP SIM Configure HP SIM by entering the following command on the CMS:
# mxinitconfig -a

Upgrade of an existing installation of HP SIM

The system automatically runs mxinitconfig after the reboot. This can take up to 20 minutes to complete. Do not attempt to run any HP SIM commands or Insight Dynamics management commands, or access HP SIM through the web interface at this time. Other steps might be required to complete the HP SIM upgrade. For example, you might need to reidentify all discovered systems to complete the database upgrade for existing systems in the database.

2.

(optional) If Oracle version 10g is installed on a server in your environment, you can configure HP SIM and ID-VSE for Integrity to use an Oracle database instead of the defaultPostgreSQL database for internal data management. For specific requirements for using Oracle with ID-VSE for Integrity, see HP Insight Software 6.2 Support Matrix. To configure HP SIM for Oracle, use the following steps: a. b. Ensure that Oracle 10g is installed and running on the Oracle server. Copy the file ojdbc14.jar from your Oracle 10g server to a location on your CMS. NOTE: Do not rename this file. It must be named ojdbc14.jar when it is installed by mxoracleconfig in the next step. c. Configure HP SIM by entering the following command on the CMS:
# mxoracleconfig [-h hostname] [-n port-number] \ -d database-name -u username -p password \ -j path-to-jar-file/ojdbc14.jar [-f]

For details about the mxoracleconfig command, see mxoracleconfig(1M). d. 3. Reinitialize HP SIM by entering the following command on the CMS:
# mxinitconfig -a

Run the msswinitconf -a command to configure Insight managed system setup wizard on the CMS:
# msswinitconfig -a

IMPORTANT: On an Integrity CMS the msswinitconfig command must be executed after installing the software and configuring HP SIM, but prior to executing vseinitconfig. An error message will be issued by vseinitconfig if this step has not been performed. You must run msswinitconfig before running managed system setup wizard for the first time. 4. Configure ID-VSE for Integrity by entering the following command:
Install the software on the CMS 17

# /opt/vse/bin/vseinitconfig -a

The vseinitconfig command logs status, errors, and exceptions to the file /var/opt/ vse/logs/vseinitconfig.log. Review the output of this command to ensure there are no errors. IMPORTANT: If you are upgrading from a previous version of ID-VSE for Integrity, the vseinitconfig command migrates any product licenses that were previously installed or scanned to the HP SIM License Manager database. Review the licensing information in the log file to make sure that it is correct. You may need to adjust the number of licensed cores using the vselicense command. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide. 5. 6. When vseinitconfig finishes, you are prompted to restart HP SIM. Type y and press Enter to restart HP SIM. (Optional) Execute the command catman to make sure that the ID-VSE for Integrity manpages can be listed by keyword using man -k. Enter the following command on the CMS:
# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file VSEMgmt

Procedure 3-6 Install ID-VSE for Integrity using existing installation of HP SIM 1.

2.

Configure ID-VSE for Integrity by entering the following command:


# /opt/vse/bin/vseinitconfig -a

The vseinitconfig command logs status, errors, and exceptions to the file /var/opt/ vse/logs/vseinitconfig.log. Review the output of this command to ensure there are no errors. IMPORTANT: If you are upgrading from a previous version of ID-VSE for Integrity, the vseinitconfig command migrates any product licenses that were previously installed or scanned to the HP SIM License Manager database. Review the licensing information in the log file to make sure that it is correct. You may need to adjust the number of licensed cores using the vselicense command. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide. 3. 4. When vseinitconfig finishes, you are prompted to restart HP SIM. Type y and press Enter to restart HP SIM. (Optional) Execute the command catman to make sure that the ID-VSE for Integrity manpages can be listed by keyword using man -k.

IMPORTANT: If you are reinstalling or updating an existing installation, you might have already performed the steps in the following sections. However, you might need to repeat some of these steps after reinstallation or upgrade. In particular, see Configure ID-VSE for Integrity (page 27). You need to repeat the postinstallation configuration steps listed there, including license management and Application Discovery certificate exchange.

Start and configure HP SIM


After installation, use Procedure 3-7 to start HP SIM and run the First Time Wizard to finish the configuration process.

18

Installation

Procedure 3-7 Start HP SIM and The First Time Wizard 1. Start a Web browser and make sure that it is not configured to block pop-up windows. Direct your web browser to the following URL:
http://server:280

2.

where server is the host name of your CMS. When launched for the first time after a new installation, HP SIM automatically displays the First Time Wizard. You can also run this wizard manually by selecting OptionsFirst Time Wizard... from the HP SIM menu bar. NOTE: You can view HP SIM help for this or any other window by clicking the in the upper right corner of the window. button

3.

Proceed through the screens of the First Time Wizard as follows: a. Introduction Screen Click Next to continue. b. Managed Environment Specifies all operating systems managed by the CMS. The selections made here configure HP SIM to show collections, tools, and reports only for managed environments that are selected. Discovery Discovery is the process of finding and identifying systems in the management domain so that they can be managed from the CMS by HP SIM. There are two discovery modes: automatic and manual. If you want discovery to be scheduled on an automatic basis, select Schedule and specify how often discovery should run. Whether or not you configure automatically scheduled discovery, run the discovery process manually as soon as you are finished with the First Time Wizard. You can run discovery manually by selecting OptionsDiscovery... from the HP SIM menu bar and then clicking Run Now. In either automatic or manual mode, you can specify IP ranges for a ping sweep (detection of systems by their response to a network ping), or you can specify individual systems by name or IP address. HP SIM uses WBEM, SNMP, SSH and SMH protocols for system identification. For example, HP SIM attempts to contact the WBEM nPartition, virtual partition, and virtual machine providers on a given system to determine the system type. HP SIM populates its system database with this information and creates relationship information such as the parent/child association between a VM Host and its virtual machines. Virtualization Manager uses both the system and relationship information when displaying Insight Dynamics resources. Until you install the Insight Dynamics agent software on the managed nodes, little information is available. For information about installing Insight Dynamics agent software, see Install Insight Dynamics agent software and configure managed systems (page 21). When you have finished configuring the discovery settings, click Next to continue. d. Credentials: System Automatic Discovery Use the wizard to set the sign-in credentials and the SNMP credentials for the System Automatic Discovery task. Sign-in Credentials ID-VSE for Integrity uses WBEM connections to obtain information from the managed systems. You must establish common WBEM credentials on the CMS and on the managed systems to allow authenticated access to WBEM data. For more information, see Prepare for installation (page 12). SNMP Credentials Configure the SNMP community name that is appropriate for your organization, or use the default value provided. Click Next to continue.

c.

Start and configure HP SIM

19

e. f.

Configure Managed Systems Configure managed systems as they are discovered, by configuring WBEM and WMI, SNMP, SSH access, and trust relationship. WMI Mapper Proxy To retrieve managed system information on Windows systems, enter the mapper proxy system host name and port number. The user name and password credentials must be entered on the First Time Wizard Configure Managed Systems page. This page does not appear if you are not managing Windows systems. Privilege Elevation Privilege elevation allows you to specify a non-root login on managed systems and a command that can be used to acquire root privileges as needed. See also Privilege elevation (page 21) and the HP SIM help. E-mail If you do not want email notification of HP SIM events from the CMS, skip this step. Otherwise, specify the SMTP host and authentication (if required) to be used for email notifications. On an HP-UX CMS, you can usually use the CMS as the SMTP host. Also provide an email address to be used as the From portion of the email header. HP recommends the name hpsim@hostname. Click Next to continue. Summary Displays all First Time Wizard settings with the option to modify settings or to finish the First Time Wizard.

g.

h.

i. 4.

Run the HP SIM discovery process so that you can select managed nodes for the Insight Dynamics agent software installation in the next section. Do this even if you configured automatically scheduled discovery in the First Time Wizard. Select OptionsDiscovery... from the HP SIM menu bar, then click Run Now.

20

Installation

Install Insight Dynamics agent software and configure managed systems


Managed systems require some setup before Insight Dynamics can properly identify them, retrieve data from them, and perform management operations on them. Managed system setup includes the installation of agent software or configuration of agentless data collection, installation of licenses, and configuration of options specific to the management capabilities intended for use on the system. All of these steps are performed by the Insight managed system setup wizard. In some cases, you may prefer to manually install agents or other required software, such as WBEM or SSH, instead of allowing the managed system setup wizard to install the latest version (the wizard will only update existing versions if the existing version is not supported by Insight Dynamics). For information about manual installation of agent software, see Alternate procedure for manual installation of agent software (page 21). IMPORTANT: If you are upgrading an existing version of the gWLM agent, you must upgrade the gWLM agent on all systems in an SRD at the same time. You cannot run different versions of the gWLM agent within a single SRD.

Using managed system setup wizard


To start the managed system setup wizard, select ConfigureManaged System Setup Wizard... from the HP SIM top menu. Help is available in each step of the wizard. See also Insight Managed System Setup Wizard 6.2 Getting Started Guide. IMPORTANT: Before running managed system setup wizard the target managed systems must be fully discovered and should have valid credentials stored within HP SIM. You can discover systems using the HP SIM Discovery page. To access this page select OptionsDiscovery... from the HP SIM top menu.

Privilege elevation
Some tools in HP Systems Insight Manager (SIM) are defined to run as root on HP-UX, Linux, and VMware ESX managed systems. However, root logins are not allowed in many customer environments. Instead, administrators may be required to use an individual login which is authorized to acquire root permissions as needed (for example, using su or sudo). In this case, you can configure privilege elevation in HP SIM. This feature allows you to specify a non-root login on managed systems and a command that can be used to acquire root privileges as needed. Privilege elevation can be configured in HP SIM as part of the First Time Wizard or by selecting OptionsSecurityPrivilege Elevation... from the HP SIM top menu. You will need to configure the selected user login on the managed system. Additional configuration may also be needed. For example, you may need to configure SSH access using ConfigureConfigure or Repair Agents..., and you may need to configure the managed system to allow host authentication for non-root users. For more information, see the HP SIM help.

Alternate procedure for manual installation of agent software


Agent software can be found in the depots and installation packages that are installed in the depot directory on the CMS. On an HP-UX CMS, this directory is /var/opt/vse/depot. On a Windows CMS the directory is install-path\depot, where install-path is the directory where Insight Dynamics is installed (by default, this directory is C:\Program Files\HP\ Virtual Server Environment). Use the following procedures to manually install the agent software.

Install Insight Dynamics agent software and configure managed systems

21

Procedure 3-8 Manual installation of HP-UX agents 1. Copy the desired depot files (file.depot) from the depot directory on the CMS to /var/ tmp on the managed system. Or, if you are using a Software Distributor depot server, copy the depot files to the depot server. Install the desired depots using the swinstall command, as shown in the following example. If you are using a Software Distributor depot server, replace the source part of the command with the server location of the depot. Example 3-1 Install the Utilization Provider on an HP-UX system
# /usr/sbin/swinstall -s /var/tmp/up.depot UtilProvider

2.

3. 1. 2.

Repeat the previous step for each of the agents that you want to install. Copy the desired tar files (file.tar) from the depot directory on the CMS to /var/tmp on the managed system. Copy the agent installation script install-agent.sh from the CMS to /var/tmp on the managed system. On an HP-UX CMS, this script is located in /opt/vse/lbin. On a Windows CMS it is in install-path\lbin, where install-path is the directory where Insight Dynamics is installed (by default, this directory is C:\Program Files\HP\Virtual Server Environment). Install the agent software using the install-agent.sh script, as shown in the following example. Example 3-2 Install the HPVM Provider on a Red Hat Enterprise Linux 4 (Integrity) system
# cd /var/tmp # tar -xvf hp.com-hpvm.tar # rpm -U hpvm-4.1.0-1-rhel4.ia64.rpm

Procedure 3-9 Manual installation of Linux agents

3.

4. 1. 2.

Repeat the previous step for each of the agents that you want to install. Copy the desired Windows install files (file.msi) from the depot directory on the CMS to C:\ on the managed system. Install the agent software using the msiexec command, as shown in the following example. Example 3-3 Install the Utilization Provider on a 32bit Windows system
C:\> c: C:\> cd \ C:\> msiexec /I WMIUtilProvider32.msi /norestart

Procedure 3-10 Manual installation of Windows agents

This command installs the agent interactively using the GUI and does not perform a reboot after installation. To install the agent with no interaction (quiet mode) and without using the GUI, use the /qn option on the msiexec command. For information about other command options, use the /help option. 3. 1. 2. Repeat the previous step for each of the agents that you want to install. Copy the file setupva.exe from the depot directory on the CMS to the managed system. Run setupva.exe on the managed system to install vseassist. Procedure 3-1 Manual installation of vseassist command on Windows systems 1

22

Installation

After upgrading from a previous version


HP SIM upgrade If you upgraded HP SIM, follow any postinstallation instructions described in the HP SIM documentation. Make sure that you have installed all required HP-UX or application patches. Stop and restart HP SIM by executing the following commands on the CMS:
# /opt/mx/bin/mxstop # /opt/mx/bin/mxstart

It might take several minutes for HP SIM to restart completely. To verify that HP SIM has finished restarting, execute the following command on the CMS:
# /opt/mx/bin/mxuser -lt

This command lists the users defined in HP SIM. If an error is displayed, wait several minutes and try the command again. Reapply demo licenses to managed systems After upgrading to ID-VSE for Integrity version 6.0 any systems that previously had a temporary demonstration (demo) license applied must be explicitly licensed after the upgrade. To apply an ID-VSE for Integrity version 6.0 demo license to a managed system, use either Insight managed system setup wizard or the vselicense -t command. See Using managed system setup wizard (page 21) or the vselicense(1M) for more details. Verify gWLM communication and redeploy your SRDs If you are using gWLM, execute the following command on the CMS to verify that the CMS is configured properly and can communicate with installed agents:
# /opt/gwlm/bin/gwlm list

If the output of this command lists various policies, the CMS is configured properly. If not, error messages are displayed. Wait a few seconds and try the command again. If you still get errors, perform the actions recommended in the error messages. Once communication is verified, redeploy any SRDs. In addition, for partition-based SRDs, follow the procedure described next. Rediscover partition-based SRDs If you are using gWLM, and you have upgraded the gWLM agents in the partitions from gWLM A.02.xx to gWLM A.6.2.0.*, you cannot add other partitions in the same complex to the SRD if you have either of the following types of partition-based SRDs: A Virtual Partition SRD inside an nPartition An nPartition SRD using Instant Capacity Reestablish the SRD using Procedure 3-12. Procedure 3-12 Rediscover partition-based SRDs 1. With the SRD deployed, rediscover the SRD. For a virtual partition SRD, execute the following command:
# /opt/gwlm/bin/gwlm discover --type=vpar \ --file=/tmp/myfile.xml hosts

For an nPartition-based SRD, execute the following command:


# gwlm discover --type=npar \ --file=/tmp/myfile.xml hosts

2.

In these commands, replace hosts with a space-separated list of the partitions in the SRD. Make the following adjustments to /tmp/myfile.xml, as described in gwlmxml(4): Ensure that the mode attribute for the sharedResourceDomain element is set to the desired value (Managed or Advisory):
mode="Managed"

Ensure that the interval attribute for the sharedResourceDomain element is set to the desired value:
After upgrading from a previous version 23

interval="x"

Ensure that the ticapMode attribute for the sharedResourceDomain element is set to all if gWLM should allocate Temporary Instant Capacity (TiCAP) when needed:
ticapMode="all"

Ensure that the workloadReference entries in the compartment definitions are correct, and adjust the names in the workload definitions themselves. For example, you might see host.OTHER.2 instead of host.OTHER.

3.

Import the file to re-create the SRD:


# gwlm import

Because the SRD was already deployed, the new SRD definition is deployed on import, taking the place of the original SRD. Verify Capacity Advisor data migration If you are using Capacity Advisor, use the command capprofile -lt to verify that previously collected historical data has been migrated to the new ID-VSE for Integrity database. This command lists the workload profiles and the time range of the data stored in the database. For more information, see capprofile(1M). Restore scheduled Capacity Advisor tasks If you are using Capacity Advisor, restore each of your automatically scheduled Capacity Advisor data collection tasks using Procedure 3-13. Procedure 3-13 Restore scheduled Capacity Advisor tasks 1. 2. 3. 4. 5. 6. 7. Select Tasks & LogsView All Scheduled Tasks from the Capacity Advisor menu bar. Select the task from the list Collect Capacity Advisor Data. Click Edit. Click Schedule. Clear the Disable this task check box. Click Done. Verify that the task you just edited is in the list and now shows Periodic in the Schedule column, along with the date of the next collection.

Postinstallation update of gWLM agents


If you update ID-VSE for Integrity on the CMS to version A.6.2.0.* without updating the gWLM agent software on some of your managed systems, update those agents as soon as it is convenient to do so. Use Procedure 3-14 to update the agents. Procedure 3-14 Update gWLM agents after updating the CMS 1. Undeploy the SRDs that are managing systems where agents are going to be upgraded. Stop using the existing version of gWLM, including the command-line interface. You can continue running the gWLM daemons (gwlmcmsd and gwlmagent) and the WBEM service and provider daemons. Install and start the agents as described in Install Insight Dynamics agent software and configure managed systems (page 21). For any partition-based SRDs, follow the steps described in Rediscover partition-based SRDs (page 23). For SRDs based on PSETs, FSS groups, or virtual machines, redeploy those SRDs. To determine if PSETs (HP-UX processor sets, the PROCSETS bundle) is installed use the swlist ProcessorSets command.

2. 3.

Preparing a Red Hat Linux managed system


OpenPegasus is required for Insight Dynamics of Linux systems. Red Hat (RHEL) distributions include OpenPegasus, but this is not installed by default. Either manually select OpenPegasus

24

Installation

during RHEL installation, or install it later from your RHEL distribution media through the YaST Control Center.

Preparing a ProLiant SUSE Linux managed system


This section provides instructions on how to prepare a ProLiant system running SUSE Linux Enterprise Server 9 or 10 to be a managed system in ID-VSE for Integrity. Both x86 and x64 (AMD64/EM64T) platforms running these SUSE Linux versions are shipped with OpenWBEM, which is not supported by ID-VSE for Integrity. OpenPegasus is the supported WBEM Services for ID-VSE for Integrity. Because OpenPegasus WBEM Services cannot be installed when OpenWBEM is present on the system, the following procedures describe how to remove OpenWBEM, install OpenPegasus WBEM Services, and deploy the ID-VSE for Integrity agents required for managing the SUSE Linux system. If the managed system is already running OpenPegasus 2.5 or greater then no action is required. Procedure 3-15 Remove OpenWBEM OpenWBEM must be removed from the system before installing OpenPegasus WBEM onto a ProLiant managed system running SUSE Linux Enterprise Server 9 or 10. Use the following procedure to remove OpenWBEM. 1. Before removing OpenWBEM, stop the OpenWBEM CIM Daemon.
# /etc/init.d/owcimomd stop Shutting down OpenWBEM CIMOM Daemon

2.

Remove OpenWBEM and packages that depend on OpenWBEM through the YaST Control Center or another package management application.

Procedure 3-16 Download OpenPegasus WBEM Use the following steps to download OpenPegasus WBEM packages from the HP website. 1. 2. 3. Go to http://www.hp.com/. Enter OpenPegasus WBEM Services in the product search field and click the Search button. Click the link for the OpenPegasus version specific to ID-VSE for Integrity from the resulting list of products. NOTE: The product description indicates whether the selected OpenPegasus package is specific to ID-VSE for Integrity. 4. Click the Download button to download the package.

Procedure 3-17 Install OpenPegasus WBEM After downloading the OpenPegasus package, install it and start OpenPegasus WBEM Services on the system. 1. 2. Login to the Linux system as root and run the following command to install the package:
# rpm Uvh tog-pegasus-version.distro.arch.rpm

Start OpenPegasus WBEM Services by running the following command as the root user:
# /etc/init.d/tog-pegasus start

At this point the Linux managed system has OpenPegasus WBEM installed and configured. The next steps provide information on how to configure the CMS to enable VSE Agent Distributor for ID-VSE for Integrity agents.

Preparing a ProLiant SUSE Linux managed system

25

Additional configuration steps


If your Linux system is not an HP SIM managed system yet, refer to the Setting Up Managed Systems section of the HP Systems Insight Manager 6.0 Installation and User Guide available at http://www.hp.com/go/hpsim. This document also contains information on how to configure WBEM credentials for a Linux system. At this point users can install VSE Agents onto the Linux managed systems, necessary for Insight Dynamics. Refer to Install Insight Dynamics agent software and configure managed systems (page 21) for instructions on how to install HP WBEM Providers onto Linux managed systems.

26

Installation

4 Configure ID-VSE for Integrity


After installation, you must perform additional steps to configure ID-VSE for Integrity for your environment. For a description of these steps, see the sections that follow. IMPORTANT: ID-VSE for Integrity does not operate correctly until you complete these postinstallation configuration steps. You must perform these steps even when you reinstall or update an existing installation.

Configuring user authorizations


Users must be authorized in HP SIM in order to run the ID-VSE for Integrity tools. To configure user authorizations, you must be logged into HP SIM as a user with Full Configuration Rights. Refer to mxuser(1M) for information about viewing and setting configuration rights. Choose OptionsSecurityUsers and Authorizations from the HP SIM menu bar. Use the tabs to view and change the toolbox authorizations for each user. For detailed information about creating and updating authorizations, refer to the HP SIM online help. The following table defines the authorization provided by each of the toolboxes associated with ID-VSE for Integrity. The sections that follow present examples showing how to configure authorizations based on the user's role. NOTE: If your CMS is also a managed system, then any authorizations required on managed systems will also be required on the CMS.
Toolbox System Setup Required Authorizations Authorize this toolbox on the CMS to allow use of the Insight managed system setup wizard. Authorize this toolbox on each managed system that will be configured using the managed system setup wizard. This is a master toolbox that applies to all tools installed in HP SIM. Authorize this toolbox on selected systems for users whose role requires administrative authority on those systems. Refer to the following sections for examples. ID-VSE for Integrity users should have this authorization on the CMS and All Managed Systems. Otherwise, they will not have access to HP SIM monitoring tools such as the System Page or Property Pages. Authorize this toolbox on managed systems to allow use of Capacity Advisor on those systems. Authorize this toolbox on the CMS to allow users to edit data with the Profile Editor. Authorize this toolbox on managed systems to allow users to view and manage those systems using Virtualization Manager, Global Workload Manager, Capacity Advisor, and VM Manager. This toolbox also allows users to manage application and process data collection using Application Discovery. Authorize on the CMS only if the CMS will also be a managed system. ID-VSE for Integrity users should have this authorization on the CMS and All Managed Systems. Otherwise, they will not be able to use the ToolsVSE Management... action on the HP SIM menu bar or VSE Management product menus. Authorize this toolbox on the CMS to allow view-only use of Application Discovery. Authorize this toolbox on the CMS to manage storage pools and storage tags. Authorize this toolbox on the CMS to allow users to view and manage systems using gWLM version A.01.x. For gWLM version A.02.00.00 or later, this toolbox is not used; authorize VSE All Tools instead.

All Tools

Monitor Tools

Capacity Advisor

VSE All Tools

VSE Monitor

VSE Storage gWLM All Tools

Configuring user authorizations

27

Toolbox gWLM Monitor

Required Authorizations Authorize this toolbox on the CMS to allow view-only use of gWLM version A.01.x. For gWLM version A.02.00.00 or later, this toolbox is not used; authorize VSE Monitor instead. Authorize this toolbox to allow full access to HP Virtual Connect Enterprise Manager software. This authorization permits viewing and modifying the VCEM configuration. Authorize this toolbox to allow read-only access to HP Virtual Connect Enterprise Manager software. This authorization permits viewing but not modifying the VCEM configuration.

VCEM Full Access VCEM Read Only

Role: ID operator, application administrator, or capacity planner


With these authorizations, you can view all Integrity and HP 9000 servers in the management domain. You can examine the configuration of all managed systems through Virtualization Manager, Partition Manager, Application Discovery, and Virtual Machines Manager. You can define and view a logical server using Virtualization Manager. You can view real-time application data through Application Discovery, real-time and historical data through gWLM, and historical data through Capacity Advisor. You cannot make any configuration changes to the managed systems or Application Discovery components, or edit Capacity Advisor data with the Profile Editor.
Toolbox Monitor Tools VSE Monitor Capacity Advisor Systems Authorized CMS and All Managed Systems CMS and All Managed Systems All Managed Systems

Role: ID system administrator


These authorizations provide all of the capabilities of the ID Operator role but also allow you to change the configuration of specific managed systems. On systems authorized with the All Tools toolbox, you can perform all of the following functions: Create, modify, and delete nPartitions, virtual machines, and gWLM shared resource domains. Install software and perform other system administration tasks offered through HP SIM.
Toolbox System Setup Monitor Tools VSE Monitor Capacity Advisor All Tools Systems Authorized CMS and All Managed Systems CMS and All Managed Systems CMS and All Managed Systems All Managed Systems Subset of All Managed Systems

To specify the subset of systems that are authorized with All Tools, refer to Selecting and updating the authorized systems set (page 30).

Role: ID senior system administrator


These authorizations provide all of the capabilities of the ID system administrator role. In addition, the VSE All Tools authorization on the CMS allows you to perform all of the following functions:

28

Configure ID-VSE for Integrity

Create, modify, and delete gWLM policies. Delete parked workloads. A workload is parked if its container assignment is set to None -- Park the workload in the Monitored Workload Definition Properties screen. Parking a workload allows you to retain its collected data while waiting to migrate the workload to a new system. Perform operations on logical servers, including activate, copy, create, deactivate, delete, drop, import, modify, or move a logical server, and manage logical server storage pools. Manipulate Application Discovery agent behavior and modify application template matching and event reporting.
Systems Authorized CMS and All Managed Systems CMS CMS and All Managed Systems CMS and All Managed Systems All Managed Systems Subset of All Managed Systems

Toolbox System Setup VSE All Tools Monitor Tools VSE Monitor Capacity Advisor All Tools

To specify the subset of systems that are authorized with All Tools, refer to Selecting and updating the authorized systems set (page 30).

Role: senior capacity planner


These authorizations provide all of the capabilities of the VSE Operator role. In addition, the Capacity Advisor authorization on the CMS allows you to edit and delete profile data.
Toolbox Monitor Tools VSE Monitor Capacity Advisor Systems Authorized CMS and All Managed Systems CMS and All Managed Systems CMS and All Managed Systems

Role: storage administrator


This authorization allows a storage administrator to perform operations on storage pool entries without enabling any other Insight Dynamics operations.
Toolbox VSE Storage Systems Authorized CMS

Role: legacy Global Workload Manager operator


This authorization is maintained for backward compatibility with gWLM version 1. This user is able to view real-time and historical reports for any system in the data center that is managed by gWLM version A.01.x. This user is not authorized to use Virtualization Manager, Partition Manager, Virtual Machines Manager, or Capacity Advisor. Because this authorization cannot

Configuring user authorizations

29

be restricted to specific managed systems, HP recommends using the other authorizations described earlier, which provide more granular host-based authorization.
Toolbox gWLM Monitor Systems Authorized CMS

Role: legacy Global Workload Manager administrator


This authorization is maintained for backward compatibility with gWLM version 1. This user is able to manage any system in the data center with gWLM version A.01.x, but is not authorized to use Virtualization Manager, Partition Manager, Virtual Machines Manager, or Capacity Advisor. Because this authorization cannot be restricted to specific managed systems, HP recommends using the other authorizations described earlier, which provide more granular host-based authorization.
Toolbox gWLM All Tools Systems Authorized CMS

Selecting and updating the authorized systems set


When you create an HP SIM authorization, you can select the individual authorized systems, or you can specify a named collection of systems. If the authorization is based on a named collection, it will be applied to the systems that are currently in that collection when the authorization is created. If additional systems are later added to that collection or removed from it, you should update the authorization to match the changed collection. Use the following procedure to update a user's authorizations: 1. 2. 3. Choose OptionsSecurityUsers and Authorizations from the HP SIM menu bar. Select the Authorizations tab. Select an authorization that was based on a named collection and click Update. Confirm that you want to make the indicated changes by clicking Update Contents.

For detailed information about creating and updating authorizations, refer to the HP SIM online help.

Complete the certificate exchange for Application Discovery


NOTE: The information in this help topic applies only in the situation where Application Discovery Version 4.0 agents (or older) are running on managed nodes in the monitored network. Application Discovery Version 4.1 agent and server do not require SSL certificate exchange for secure data transmission. Application Discovery uses Secure Sockets Layer (SSL) certificates to authenticate and secure data transmission between version 4.0 (and older) Application Discovery agents and the Application Discovery server. Once Application Discovery components are installed, the accompanying certificate information for Application Discovery server and for Application Discovery agent must be exchanged to allow the server and agents to recognize legitimate transmissions. Certificate exchange can be done from within HP Systems Insight Manager software (HP SIM) or from the command line on the central management server.

Using HP SIM to complete certificate exchange


1.
30

Initiate certificate exchange by selecting Configure Insight Dynamics AgentsExchange AD Agent Certificates from the HP SIM top menu.

Configure ID-VSE for Integrity

2. 3. 4.

Select the HP-UX systems where you want the exchange to occur using the HP SIM system selection list. Click Apply. Verify the system selection and click Next. A description is displayed of the action about to take place. When you are sure that you want to exchange certificates so that the Application Discovery agent can begin reporting data to the server, click Run now to complete the certificate exchange.

NOTE: If you find that you are unable to exchange certificates from within HP SIM, check the following: That you have the correct permissions associated with your login ID. That the targeted managed node is authorized to accept remote commands from HP SIM. To set the correct SSH configuration that authorizes the acceptance of remote commands, type the following command on the CMS:
mxagentconfig -a -n managed_system -u login -p password

where managed_system is the name of the target system for which you want to enable remote communication, login is the user name on the managed system, and password is the password of that user on the managed system.

Completing certificate exchange from the command line


From the command line, you can exchange certificates with one or more managed hosts. 1. 2. Log in as a privileged user on the system hosting the CMS. (See Configuring user authorizations (page 27) for tool access information.) Assuming installation to default directories, enter the following command on HP-UX:
/opt/amgr/bin/amgr_remote_config -a -mx -n system_name -u root

and on Windows:
C:\Program Files\HP\Virtual Server Environment\bin\amgr_remot_config.bat -a -mx -n system_name

To configure multiple hosts, add -n system_name for each host to be configured. By default, amgr_remote_config uses Secure Shell (SSH) to complete this action securely across the network. -u option supported on HP-UX only: You might be prompted to provide a password for the specified user for each system login. You must supply the password in order to proceed. 3. Once the login is accomplished, the CMS sends its SSL certificate to the agent on the managed host, and the agent supplies its SSL certificate to the CMS. Application Discovery agents can now transfer data securely to the CMS, and the CMS can authenticate the transmission.

Have you recently restored or removed and reinstalled the CMS? : A restore or removal of the central management server also removes the certificate recognition previously established between Application Discovery server on the CMS and Application Discovery agents on managed nodes. This relationship must be re-established when the CMS is reinstalled or restored by completing the Application Discovery certificate exchange.

Complete the certificate exchange for Application Discovery

31

32

5 Support and other resources


Contacting HP
Information to collect before contacting HP
Be sure to have the following information available before you call contact HP: Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable)

How to contact HP technical support


Use the following methods to contact HP technical support: In the United States, see the Customer Service / Contact HP United States website for contact options: http://welcome.hp.com/country/us/en/contact_us.html In the United States, call 1-800-HP-INVENT (1-800-474-6836) to contact HP by telephone. This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls might be recorded or monitored. In other locations, see the Contact HP Worldwide website for contact options: http://welcome.hp.com/country/us/en/wwcontact.html

HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources: In the United States, see the HP U.S. service locator website at: http://www.hp.com/service_locator In other locations, see the Contact HP worldwide website at: http://welcome.hp.com/country/us/en/wwcontact.html

Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.com Include the document title and manufacturing part number in your message. All submissions become the property of HP.

Related information
The latest versions of manuals and white papers for Insight Dynamics and related products can be downloaded from the Insight Dynamicsinformation library: http://www.hp.com/go/insightdynamics/docs For more information about Insight Dynamics and related products and solutions, visit the following HP website: http://www.hp.com/go/insightdynamics/integrity
Contacting HP 33

This document does not cover installation on an HP ProLiant CMS running Microsoft Windows. For that information, see the HP Insight Software 6.2 Installation and Configuration Guide. For a description of system requirements for ID-VSE for Integrity, see HP Insight Software 6.2 Support Matrix.

Command references (manpages)


Insight Dynamics and related products include manpages for HP-UX and Linux systems and command reference pages for Microsoft Windows systems. These pages provide details about commands, file formats, and related information. The following tables list reference pages related to Insight Dynamics.

Reference pages installed on the CMS


Reference page capagentlesscfg(1M) capcustombenchmark(1M) capcustombenchmark(4) capcollect(1M) capovpaextract(1M) cappmpextract capprofile(1M) capprofile(4) gwlm(1M) gwlm(5) gwlmcmsd(1M) gwlmreport(1M) gwlmsslconfig(1M) gwlmimportkey(1M) gwlmexportkey(1M) msswinitconfig(1M) gwlmxml(4) vseassist(1M) vseinitconfig(1M) [p. 38] vselicense(1M) Description Set advanced options for Capacity Advisor agentless data collection, and view a list of systems configured for agentless data collection Configure Capacity Advisor benchmark CPU scaling to normalize collected data Format of Capacity Advisor custom benchmark database files Collect Capacity Advisor data from systems Export HP Performance Agent (formerly HP OpenView Performance Agent, or OVPA) system data from managed systems and import into Capacity Advisor Export HP Performance Management Pack (PMP) system data from specified managed systems and import the data into Capacity Advisor (Windows CMS only) Import, export, display, invalidate and remove Capacity Advisor data for workloads or systems Format of Capacity Advisor import and export files Global Workload Manager Overview of Global Workload Manager Global Workload Manager (gWLM) daemon Produce advanced textual summary reports for workload resource utilization Secure network communications for Global Workload Manager

Configure or unconfigure the Insight managed system setup wizard Overview of XML file structure for Global Workload Manager Help resolve Insight Dynamics configuration problems Configure or unconfigure the Insight Dynamics software Manage licenses to use (LTUs) on HP Integrity and HP 9000 systems

Reference pages installed with agent software on managed systems


Reference page agent_config(1M) amgrd(1M) 34 Support and other resources Description Control Application Discovery certificates from the managed node Control or modify the operation of the Application Discovery agent

Reference page gwlmagent(1M) gwlmplace(1M) gwlmsend(1M) gwlmsslconfig(1M) gwlmimportkey(1M) gwlmexportkey(1M) gwlmstatus(1M) utild(1M) utild(8)

Description Global Workload Manager (gWLM) agent Place a process in a gWLM workload Send metric data to gWLM for use in a custom policy Secure network communications for Global Workload Manager

Display status for the managed node's agent, SRD, and license Manager (HP-UX) system utilization data collection daemon (Linux) system utilization data collection daemon

Reference page installed on cell-based complexes


Reference page parmgr(1M) Description Start Partition Manager

Reference pages installed on systems running HP Integrity Virtual Machines


Reference page hpvm(5) hpvmclone(1M) hpvmcollect(1M) hpvmconsole(1M) hpvmcreate(1M) hpvmdevmgmt(1M) hpvminfo(1M) hpvmmodify(1M) hpvmmigrate(1M) hpvmnet(1M) hpvmremove(1M) hpvmstart(1M) hpvmstatus(1M) hpvmstop(1M) Description About HP Integrity Virtual Machines Create a cloned copy of an Integrity virtual machine Collect crash dumps, logs, system status, and configuration on guests and the Integrity VM Host Connect to the console of an Integrity virtual machine Create a new Integrity virtual machine Manage the Integrity VM device database Display information about the Integrity VM environment Rename or modify the attributes of an Integrity virtual machine Move a virtual machine to another Integrity VM Host system Configure virtual network devices Remove an Integrity virtual machine Start an Integrity virtual machine Display status of one or more Integrity virtual machines Stop an Integrity virtual machine

Selected HP Systems Insight Manager software reference pages


Reference page mxagentconfig(1M) mxauth(1M) mxglobalsettings(1M) mxinitconfig(1M) Description Configure the agent to work with a CMS Add, remove, or list authorizations in Systems Insight Manager Manage global settings in Systems Insight Manager Perform initial configuration of the server Related information 35

Reference page mxnode(1M) mxstart(1M) mxstatus(1M) mxstop(1M) mxuser(1M)

Description Add, modify, identify, remove, or list nodes in Systems Insight Manager Start Systems Insight Manager and the TomCat webserver Display or return (via exit code) the current ready/not-ready state of Systems Insight Manager Stop Systems Insight Manager and the TomCat webserver Add, modify, remove, or list users in Systems Insight Manager

36

Support and other resources

A Command reference

37

vseinitconfig(1M)
NAME
vseinitconfig -- Configure or unconfigure Insight Dynamics

SYNOPSIS
Path (HP-UX): /opt/vse/bin/vseinitconfig Path (Windows): install-path\bin\vseinitconfig vseinitconfig [ -a | --initconfig ] [ -F | --clobber ] [ -q | --quiet ] [-x restart_sim= { true | false }] (Initial software configuration) vseinitconfig { -r | --unconfig } [ -F | --clobber ] [ -q | --quiet ] [-x restart_sim= { true | false }] (Unconfigure software for removal) vseinitconfig { -b | --backup } { -d path | --dir=path } (Backup the PostgreSQL database on HP-UX CMS) vseinitconfig { -s | --restore } { -d path | --dir=path } { -F | --clobber } (Restore the PostgreSQL database on HP-UX CMS)

DESCRIPTION
The vseinitconfig command performs initial configuration of Insight Dynamics on an HP Systems Insight Manager (SIM) Central Management Server (CMS). It can also be used to remove the existing configuration and to back up or restore Insight Dynamics database. (Backup and restore functions are only available on a CMS running HP-UX using the PostgreSQL database.). The vseinitconfig command is installed with Insight Dynamics on both HP-UX and Microsoft Windows CMS. This command performs four different functions on the CMS, corresponding to the four syntax options shown in the synopsis. With no options specified, the initial configuration function is performed. 1. Initial configuration after installing or updating Insight Dynamics on the CMS. This includes initial configuration of HP Insight Virtualization Manager software, HP Insight Global Workload Manager software for Integrity (gWLM), and HP Insight Capacity Advisor software, as well as initialization of the Insight Dynamics database. 2. Removal of Insight Dynamics menu items and actions from HP SIM and clearing of the Insight Dynamics database, in preparation for removal of Insight Dynamics. 3. Safe backup of the Insight Dynamics database to protect against loss of data (only on a CMS running HP-UX using the PostgreSQL database). 4. Safe restore of the Insight Dynamics database from a previous backup (only on a CMS running HP-UX using the PostgreSQL database).

Options
The vseinitconfig command recognizes the following options. Each option can be expressed in a long or short form. If no options are specified, the initial configuration function is performed. Perform the initial configuration of Insight Dynamics (this -a|--initconfig is also the default function performed if no option is specified). This action requires that HP SIM is running and configured with the mxinitconfig command. This command registers Insight Dynamics tools, toolboxes, and actions with HP SIM and initializes the Insight Dynamics database. On a Microsoft Windows CMS, vseinitconfig -a is automatically invoked by the installer. On an HP-UX CMS,
38 Command reference

you must execute the command after installing the software (see HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide). On an HP-UX CMS, the optional --clobber or -F option causes an existing Insight Dynamics database to be removed without being backed up first. If that option is not used, then an existing database will be upgraded from the previous version of Insight Dynamics. This does not apply to a Microsoft Windows CMS. NOTE: HP recommends backing up your entire CMS configuration before upgrading from a previous version of Insight Dynamics. For details about this and other upgrade considerations, see the Insight Dynamics installation guide (HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide or HP Insight Software 6.2 Installation and Configuration Guide), and review the notes in the description of the --restore option below. Clear any existing Insight Dynamics database without backing it up. For more information about how this option affects vseinitconfig, see the descriptions of the options -a|--initconfig and -r|--unconfig. Do not display any output. Do not prompt for HP SIM -q|--quiet restart after performing the initial configuration operation. You can view the console and error output in the log files. -x restart_sim={true|false} This option selects whether to automatically restart HP Systems Insight Manager after initial configuration of Insight Dynamics. It only applies in combination with the initial configuration option (-a or --initconfig) or the unconfigure option (-r or --unconfig). Use -x restart_sim=true to restart HP SIM without any further prompting after all of the Insight Dynamics applications are configured. There can be a delay of one or two seconds after vseinitconfig finishes execution before HP SIM is ready to respond to mx... commands. Use -x restart_sim=false to return immediately after all of the Insight Dynamics applications are configured, without restarting HP SIM. If this option is not used, you will be prompted whether to restart HP SIM after all of the Insight Dynamics applications are configured. -F|--clobber -r|--unconfig Remove the installed Insight Dynamics tools from HP SIM. The existing database and configuration information will not be removed unless the optional --clobber or -F option is used. Important: The optional --clobber or -F option causes an existing Insight Dynamicsdatabase to be removed without being backed up first. If you do not perform a backup of the Insight Dynamics database before executing this command, you will lose all of your Insight Dynamics data, including gWLM and Capacity Advisor configuration and historical data. On a Microsoft Windows CMS, vseinitconfig -r is automatically invoked by the installer. On an HP-UX CMS,
39

you must execute the command before removing the software (see HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide). -b|--backup Back up the Insight Dynamics database, including gWLM and Capacity Advisor data, to protect against loss of data. Insight Dynamics must be initialized before you can perform a backup. For information about initializing Insight Dynamics, see the earlier description of the --initconfig option. NOTE: This option is only available on a CMS running HP-UX using the PostgreSQL database. The backup is created in the directory specified by the -d or --dir option. This directory must be initially empty or must not yet exist. The backup created by this command contains only Insight Dynamics data. For information about backing up the HP SIM database, refer to the HP white paper Backing up and restoring HP Systems Insight Manager data files in an HP-UX or Linux environment, available from the Information Library link at http://www.hp.com/go/hpsim. If you are creating a backup in preparation for relocating the CMS, HP recommends that you first undeploy all shared resource domains (SRDs). This will make it easier to redeploy the SRDs after the CMS is moved. To ensure that your backup includes up-to-date historic data, you should also perform the following steps: 1. If you are using gWLM to manage any SRDs, execute the following command on the CMS:
gwlm history --flush

2.

If you use Capacity Advisor, execute the following command on the CMS:
capcollect

-s|--restore

Restore the Insight Dynamics database from the backup in the directory named by the -d or --dir option. Insight Dynamics must be initialized before you can perform a restore, therefore the --clobber or -F is also required in order to replace the database. For information about initializing Insight Dynamics, see the earlier description of the --initconfig option. NOTE: This option is only available on a CMS running HP-UX using the PostgreSQL database. HP SIM must be stopped when the restore operation is performed. To stop HP SIM, execute the command mxstop on the CMS. Use mxstart to restart HP SIM after the restore operation is finished.

40

Command reference

NOTE: If the CMS or managed systems have been modified between the backup and the restore (for example, changing hostnames or adding or removing processors), gWLM might not function as expected after the restore. NOTE: You cannot restore a backup that was created with a previous version of Insight Dynamics. Previous versions of the Insight Dynamics database may be incompatible with the current version. If you have not yet installed the current version of the software and you intend to restore from a previous backup, perform the restore first. Then install and initialize the new software. The initialization process upgrades the already-restored database to the current format. If you have already updated the software and you need to restore from a backup made by a previous version of the software, follow these steps: 1. Remove Insight Dynamics according to the instructions in the Insight Dynamics installation guide (HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide or HP Insight Software 6.2 Installation and Configuration Guide). 2. Reinstall the version of the software on which the backup was created, according to the installation instructions published with that release. 3. Restore the Insight Dynamics database from the backup. 4. Install the new version of Insight Dynamics according to the current installation guide. 5. Initialize the software as described in the earlier description of the --initconfig option. This upgrades the restored database to the new format.

Removing and Reinstalling VSE


If Insight Dynamics is removed and reinstalled, collection of Capacity Advisor data can miss some data on the CMS. To avoid this, back up the Insight Dynamics database before removing Insight Dynamics, and restore the database after it is reinstalled.

RETURN VALUES
0 1 The command completed successfully; no errors were detected. An error occurred and the command did not complete successfully.

EXAMPLES
The following command performs initial configuration of Insight Dynamics and prompts whether to restart HP SIM after configuration is complete.
vseinitconfig -a

The following command performs initial configuration of Insight Dynamics, removes any existing Insight Dynamics database without backing it up, and restarts HP SIM automatically:
vseinitconfig -a -F -x restart_sim=true

Here is the same command, using the long form of options:


vseinitconfig --initconfig --clobber -x restart_sim=true

The following command backs up the Insight Dynamics database to the directory /var/ backups/2009-09-01:
41

vseinitconfig -b -d /var/backups/2009-09-01

Here is the same command, using the long form of options:


vseinitconfig --backup --dir=/var/backups/2009-09-01

The following command performs the unconfigure operation, removing Insight Dynamics tools from HP SIM. The --clobber option causes the database information to be removed without making a backup:
vseinitconfig --unconfig --clobber

You can mix the short and long form options. For example, to restore the Insight Dynamics database from the directory /var/backups/2009-09-01, you can use the following command:
vseinitconfig --restore -d /var/backups/2009-09-01 -F

AUTHORS
vseinitconfig was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATED


July 2010

FILES
The console (non-error) output from the vseinitconfig command is written to the following log file: HP-UX: /var/opt/vse/logs/vseinitconfig_output.log Windows: install-path\logs\vseinitconfig_output.log Errors and exceptions reported by vseinitconfig, are written to the following log file: HP-UX: /var/opt/vse/logs/vseinitconfig.log Windows: install-path\logs\vseinitconfig.log The default install-path on a Windows CMS is C:\Program Files\HP\Virtual Server Environment, but this directory can be changed at installation time.

SEE ALSO
gwlmcmsd(1M), gwlmsslconfig(1M), mxglobalsettings(1M), mxinitconfig(1M), mxstart(1M), mxstatus(1M), mxstop(1M), mxtool(1M), mxtoolbox(1M), mxuser(1M), HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide, HP Insight Software 6.2 Installation and Configuration Guide, HP Insight Dynamics 6.2 Getting Started Guide

42

Command reference

B Back up the CMS configuration


The upgrade process is not reversible. To revert to a previous installation of the software, you must restore the previous CMS configuration as well as any remote databases used by the software. Therefore, HP recommends that you make a backup of your current installation before upgrading the software.

Back up your existing CMS configuration prior to upgrading the software


The upgrade process is not reversible. To revert to a previous installation of the software, you must restore the previous CMS configuration as well as any remote databases used by the software. Therefore, HP recommends that you make a backup of your current installation before upgrading the software. Procedure B-1 Backing up your HP ID-VSE for Integrity CMS configuration To make a complete backup of your HP ID-VSE for Integrity configuration, perform the following steps: 1. Back up the remote database tables. If you are using the default PostgreSQL database, skip this step. This step only applies if you are using a remote Oracle database. To back up the remote database, use the following steps: a. Stop the running gWLM daemon by entering the following command:
gwlmcmsd --stop

b. c. d.

Stop the running Application Discovery server by entering the following command:
/opt/amgr/bin/cms_stop

Stop HP SIM by entering the following command:


/opt/mx/bin/mxstop

2.

Back up the gwlm remote database on the Oracle server using Oracle Enterprise Manager or Oracle Recovery Manager. This database is used by multiple ID-VSE for Integrity applications. e. Back up any remote database tables used by other SIM applications, if necessary. Other HP SIM applications may have their own specific backup requirements. See the documentation for those applications for specific instructions. f. Back up the HP SIM remote database using Oracle Enterprise Manager or Oracle Recovery Manager. The HP SIM remote database name begins with Insight_v, followed by a version number. Make a full backup of the CMS. Performing a full backup of an HP-UX server may require booting the server in a lower init state or stopping additional system services, so that all configuration files can be read in a stable condition. Consult your backup software documentation for specific requirements.

Procedure B-2 Restoring your CMS configuration from backup If you need to restore the CMS configuration that was saved using the preceding procedure, use the following sequence: 1. Restore the server files from the full backup. 2. Restore the remote database tables. 3. Restart the server.

Back up your existing CMS configuration prior to upgrading the software

43

44

C Removing ID-VSE for Integrity


Use Procedure C-1 to completely remove ID-VSE for Integrity from an HP-UX CMS. Procedure C-1 Remove ID-VSE for Integrity 1. Make sure that HP SIM is running. 2. Use gWLM to undeploy all deployed SRDs. 3. Delete all monitored workloads. 4. Stop the gWLM agent daemon, if it is running on the CMS, by executing the following command:
# /opt/gwlm/bin/gwlmagent --stop

5.

Remove the existing ID-VSE for Integrity configuration and database by executing the following command:
# /opt/vse/bin/vseinitconfig -r -F

6.

Remove ID-VSE for Integrity by executing the following command:


# /usr/sbin/swremove VSEMgmt T2743AA gWLM-Agent \ vseAssist AppDiscServer AppDiscCMS AppDiscAgent PRMSIMTools

7.

Remove log files and other application files by executing the following commands:
# # # # rm rm rm rm -rf -rf -rf -rf /opt/vse /etc/opt/vse /var/opt/vse /opt/gwlm /etc/opt/gwlm /var/opt/gwlm /opt/amgr /etc/opt/amgr /var/opt/amgr /opt/hpwebadmin/webapps/vse.war

45

46

Index
A
agent, 19, 20 installation, 21 amgr_remote_config certificate exchange example, 31 authorizations, 27 HP-UX patches, 9, 12

I
Insight Dynamics agent software (see agent) installation CMS, 16 managed systems, 21

B
backup VSE database, 15, 16 Bastille, 9

L
LDAP, 12 license demo, 23 installation, 21 Linux managed systems, 13, 24, 25

C
Central Management Server (see CMS) certificates completing the exchange, 30 exchanging from the command line, 31 exchanging from within HP Systems Insight Manager software, 30 CMS requirements, 9 command reference pages, 34

M
managed system setup wizard, 21 managed systems installing VSE agent software, 21 Linux, 13 Microsoft Windows, 14 setup, 21 manpage, 34 manuals, 33 Microsoft Windows managed systems, 14 mxagentconfig enabling remote communication from HP Systems Insight Manager software, 31

D
database, 15, 17 backup, 15, 16 restore, 15, 16 demo license, 23 discovery (see HP SIM, discovery) documentation, 33

N
network firewalls, 9 NIS, 12

F
Fair-Share Scheduler (see FSS group) firewall, 9 FSS group, 24

O
OpenPegasus WBEM, 24, 25 OpenSSH (see ssh) Oracle, 17

G
global credentials, 12 Global Workload Manager (see gWLM) gWLM agent installation, 21

P
patches, 9 ping sweep, 19 privilege elevation, 20, 21 processor set (see PSET) provider (see agent) PSET, 24

H
HP Capacity Advisor (see Capacity Advisor) HP Global Workload Manager (see gWLM) HP Integrity VM (see Integrity VM) HP SIM, 12 discovery, 19, 20 finding Application Discovery from, 30 First Time Wizard, 18, 19 installation, 11, 12, 16 launching, 18 supported versions, 9 HP Systems Insight Manager (see HP SIM) HP Virtualization Manager (see Virtualization Manager)

R
release notes, 12 remote command execution, 21 requirements, 9 firewalls, 9 restore VSE database, 15, 16 root, 12

47

S
Secure Shell (see ssh) security, 12 SSL certificate exchange, 30 Shared Resource Domain (see SRD) SIM documentation, 33 toolboxes, 27 user authorizations, 27 SNMP, 19 SRD, 23, 24, 45 undeploy before upgrade, 15 ssh, 13, 14, 19 SSL certificate exchange, 30 swinstall command, 17, 18 Systems Insight Manager (see HP SIM)

T
tasks exchanging certificates for application discovery, 30, 31 toolbox, 27

U
user authorizations, 27

V
virtual machine, 19 Virtual Server Environment (see VSE) Virtualization Manager, 19 VM (see Integrity VM) VM Host, 19 vPars (see virtual partition) VSE documentation, 33 vseinitconfig command, 17, 18

W
WBEM, 19 authentication, 12 provider (see agent) white papers, 33

48

Index

49