HP Insight Dynamics – VSE 6.2: IntegrityCMS Installation and Configuration Guide

HP Part Number: T8671-91011Published: 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, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor'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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPshall 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 OpenGroup UNIX 95 branded products. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Inteland Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoftand Windows are U.S. registered trademarks of Microsoft Corporation.

Table of Contents

1 Introduction......................................................................................................................7

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

3 Installation.....................................................................................................................11Overview checklist for installing ID-VSE for Integrity.......................................................................11Overview checklist for upgrading ID-VSE for Integrity.....................................................................11Prepare for installation.........................................................................................................................12

Preinstallation steps for Linux managed systems...........................................................................13Preinstallation steps for Microsoft Windows managed systems....................................................14

Before upgrading from a previous version...........................................................................................15Install the software on the CMS............................................................................................................16Start and configure HP SIM..................................................................................................................18Install Insight Dynamics agent software and configure managed systems.........................................21

Using managed system setup wizard.............................................................................................21Privilege elevation...........................................................................................................................21Alternate procedure for manual installation of agent software......................................................21

After upgrading from a previous version............................................................................................23Postinstallation update of gWLM agents..............................................................................................24Preparing a Red Hat Linux managed system.......................................................................................24Preparing a ProLiant SUSE Linux managed system............................................................................25

4 Configure ID-VSE for Integrity...................................................................................27Configuring user authorizations..........................................................................................................27

Role: ID operator, application administrator, or capacity planner.................................................28Role: ID system administrator.........................................................................................................28Role: ID senior system administrator..............................................................................................28Role: senior capacity planner...........................................................................................................29Role: storage administrator.............................................................................................................29Role: legacy Global Workload Manager operator...........................................................................29Role: legacy Global Workload Manager administrator...................................................................30Selecting and updating the authorized systems set........................................................................30

Complete the certificate exchange for Application Discovery.............................................................30Using HP SIM to complete certificate exchange.............................................................................30Completing certificate exchange from the command line..............................................................31

5 Support and other resources.......................................................................................33Contacting HP.......................................................................................................................................33

Information to collect before contacting HP...................................................................................33How to contact HP technical support.............................................................................................33HP authorized resellers...................................................................................................................33Documentation feedback.................................................................................................................33

Related information..............................................................................................................................33Command references (manpages)...................................................................................................34

Reference pages installed on the CMS.......................................................................................34

Table of Contents 3

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

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

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

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

Index.................................................................................................................................47

4 Table of Contents

List of Tables3-1 Checklist for installing ID-VSE for Integrity on an HP-UX CMS................................................113-2 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS..............................................12

5

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

6 List of Examples

1 IntroductionThis document describes the installation and configuration of HP Insight Dynamics - VSE suitefor Integrity (ID-VSE for Integrity) . It is intended to be used by Insight Dynamics systemadministrators, Insight Dynamics application administrators, capacity planners, and othertechnical professionals involved with data center operations, administration, and planning. Anunderstanding of HP-UX system administration concepts and procedures is assumed.Installing, updating, and configuring ID-VSE for Integrity involves performing the followingtasks:• 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 terminologysee the HP Insight Dynamics 6.2 Getting Started Guide.For detailed information about supported hardware and software, see HP Insight Software 6.2Support Matrix.

7

8

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

HP Systems Insight ManagerID-VSE for Integrity version 6.2 runs under HP Systems Insight Manager (HP SIM) Version 6.0or later. If you are currently using an earlier version of HP SIM, see “Before upgrading from aprevious 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 Integrityversion 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 Installationand Configuration Guide for HP-UX (available at http://www.hp.com/go/hpsim). Refer to thatdocument for information about HP SIM requirements and dependencies. In particular, notethat 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-VSEfor Integrity are described in the HP Insight Software 6.2 Support Matrix.

Compatibility with HP-UX Bastille and other network firewallsNetwork firewall software such as HP-UX Bastille might block the communication protocolsused by ID-VSE for Integrity. If your CMS or Insight Dynamics managed systems use firewallsoftware, follow the port configuration guidelines in the HP Insight Software 6.2 Support Matrix.

Additional requirements in the release notes and support matrixFor 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 MatrixThe latest versions of these documents can be downloaded from http://www.hp.com/go/insightdynamics/docs.

HP Systems Insight Manager 9

10

3 InstallationInstall 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 forID-VSE for Integrity are managed in the HP SIM License Manager database on the CMS. Whenyou upgrade an HP-UX CMS that has a previous version of ID-VSE for Integrity installed, anyproduct licenses that were previously installed or scanned are automatically migrated to theLicense Manager database. For more information about migrating previous licenses to the newlicense model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide.

Overview checklist for installing ID-VSE for IntegrityUse Table 3-1 for an overview of the installation process for ID-VSE for Integrity on an HP-UXCMS.

Table 3-1 Checklist for installing ID-VSE for Integrity on an HP-UX CMS

InformationTask

ID-VSE for Integrity is available as a singledownload from the Software Depot website:http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=vse

Obtain ID-VSE for Integrity installation package.

IMPORTANT: The software includes a 90-day trial license for HP9000 and HP Integrity managed systems. For details about ID-VSEfor Integrity licenses, see theHP Insight Dynamics 6.2 Getting StartedGuide.

□

“Prepare for installation” (page 12)Prepare for ID-VSE for Integrity installation by installing therequired software and patches, establishing common WBEM usercredentials on the CMS and managed systems, and completingpreinstallation steps for Linux and Microsoft Windows managedsystems.

□

“Install the software on the CMS” (page 16)Install HP SIM and ID-VSE for Integrity on the CMS.□

“Start and configure HP SIM” (page 18)If HP SIM was upgraded, launch HP SIM and run the First TimeWizard and the Discovery processes.

□

“Install Insight Dynamics agent softwareand configure managed systems” (page 21)

Install the WBEM providers and other agent software on yourmanaged systems.

□

“Configure ID-VSE for Integrity” (page 27)Configure ID-VSE for Integrity for your environment.

IMPORTANT: ID-VSE for Integrity does not operate correctlyuntil you complete these postinstallation configuration steps. Youmust perform these steps even when you are reinstalling orupdating an existing installation.

□

Overview checklist for upgrading ID-VSE for IntegrityUse Table 3-2 for an overview of the upgrade process for ID-VSE for Integrity on an HP-UXCMS.

Overview checklist for installing ID-VSE for Integrity 11

Table 3-2 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS

InformationTask

Appendix B (page 43)Make a backup of the ID-VSE for Integrity database.□

“Before upgrading from a previousversion” (page 15)

Perform the upgrade preinstallation steps.□

“Install the software on the CMS” (page 16)Upgrade HP SIM and ID-VSE for Integrity on the CMS.□

See “Start and configure HP SIM”(page 18).

If HP SIM was upgraded, launch HP SIM and run the First TimeWizard and the Discovery processes.

□

See “Install Insight Dynamics agentsoftware and configure managed systems”(page 21).

As needed, update the WBEM providers and other agent softwareon your managed systems.

□

“After upgrading from a previous version”(page 23)

Perform post-upgrade steps.□

Prepare for installationFor a description of HP SIM patch requirements see theHPSystems InsightManager 6.0 Installationand 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 requirementsdescribed in “System requirements” (page 9).Look for any updates to the requirements or installation instructions in the HP Insight Dynamics6.2 Release Notes. The latest version of this document can be downloaded from the InsightDynamics 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 configurationis 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: InternetOptions→Security→Custom Level→Miscellaneous→Allow script-initiated windows.This setting is enabled by default for the “medium-low” security level such as the “localintranet”zone.

Establish common WBEM credentials on the CMS and on the managed systems to allowauthenticated access to WBEM data. ID-VSE for Integrity uses WBEM connections to obtaininformation from the managed systems. To avoid having to maintain multiple WBEM useraccounts and passwords, HP recommends that you use one of the following WBEM authenticationmodels:• 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 credentialsselect Options→Security→Credentials→Global Credentials from the HP SIM menu..You must enter root (or Administrator) level user credentials for the sign-in credentialsto be used by the Configure or Repair Agents feature.To list the current credentials for a system, select Options→Security→Credentials→SystemCredentials from the HP SIM menu..

• WBEM Certificate-Based Authentication You can configure WBEM authentication for asingle system or a selected set of systems by selectingOptions→Security→Credentials→System Credentials from the HP SIM menu and usingthe 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 thisoption is available in HP SIM. Online help for certificates in general can be found in the HPSIM help system under the Networking and Security topic.

NOTE: On all HP-UX managed systems, HP WBEM Services for HP-UX version A.02.05or 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 paperUnderstanding HP SIM 5.3 Security, available from the Information Library link at http://www.hp.com/go/hpsim.

Preinstallation steps for Linux managed systemsOn managed systems running Red Hat Enterprise Linux, disable SELinux to avoid conflictswith the WBEM providers and agent software.In order for Linux managed systems to be correctly discovered by HP SIM, you must installWBEM and the required WBEM providers from the HP Integrity Essentials Foundation Pack forLinux Management CD. Download and install the contents of this CD using Procedure 3-1.Procedure 3-1 Download and install Linux management software1. On the HP Open Source and Linux website at http://hp.com/go/integritylinux, click the HP

Integrity Essentials Foundation Pack for Linux link.2. Click the Download for HP Integrity Essentials Foundation Pack for Linux link.3. Click the HPIEFPL - Support Pack link.

The HP Integrity Essentials Foundation Pack for Linux - Support Pack page has installationrequirements and instructions.

4. Click Receive for Free and select the appropriate software specification.After entering information in the required fields, click Next to download the software.

5. Install the software according to the instructions included on the HP Integrity EssentialsFoundation Pack for Linux - Support Pack page or in the docs directory contained in the tarfile.

6. Make sure that the tog-pegasus package is installed and running on the system.7. 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 andpassword. Perform the following steps to configure this file. In this example, your designatedWBEM user name is assumed to be wbemuser.a. Look for the following line in this file:

-: ALL EXCEPT pegasus:wbemNetwork

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 canuse the same procedure that is used to configure OpenSSH for HP SIM on HP-UX managedsystems, as described in “Install Insight Dynamics agent software and configure managedsystems” (page 21). However, if you are using SUSE Linux Enterprise Server 9, you must firstmanually configure OpenSSH to use password authentication.

Prepare for installation 13

IMPORTANT: SUSE Linux Enterprise Server 9 ships with SSH configured to use PAMauthentication instead of password authentication. Password authentication is required in orderfor the mxagentconfig to configure OpenSSH for use by HP SIM.

On managed systems running SUSE Linux Enterprise Server 9, change to password authenticationusing Procedure 3-2.Procedure 3-2 Configure SUSE Linux for password authentication1. Configure the following lines in /etc/ssh/sshd_config on the managed system:

PasswordAuthentication yes #UsePAM yes

2. Retrieve the process ID of the running sshd from the file /var/run/sshd.pid.3. Restart sshd by executing the following command:

# kill -SIGHUP pid

where pid is the sshd process ID.

Preinstallation steps for Microsoft Windows managed systemsOn Windows managed systems OpenSSH is not installed by default, but it can be installed fromthe HP Smart Setup installation media (version 4.5 or later). Use Procedure 3-3 to install OpenSSHand configure it for use with HP SIM. You can then install the Insight Dynamics agent softwareand WMI/WBEM providers from HP SIM using the procedure described in “Install InsightDynamics agent software and configure managed systems” (page 21).Procedure 3-3 Install and configure OpenSSH for Windows1. 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 passwordfor the account that runs the OpenSSH service. The Administrator account is typicallyused for this.

NOTE: During installation, OpenSSH automatically imports your local user accounts intoits password file. If additional accounts are added later, you must reinstall OpenSSH or usethe sshuser command to import the new user account information into OpenSSH.

2. Reboot the Windows managed system to enable SSH communication.3. 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 systemadministrator user account on your managed system is not Administrator, substituteyour administrator user name in the preceding command. You can use multiple -n optionsto 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 toconfigure, then selecting Configure→Configure or Repair Agents... from the HP SIMmenu 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 auser account named root on those Windows systems. Partition Manager uses this username for remote execution of nPartition commands through OpenSSH. Add this user to theAdministrators group in Windows, then add this user to OpenSSH using the sshusercommand.To configure remote connections from the CMS using theroot account, execute the followingcommand 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 accountfor remote command execution.

Before upgrading from a previous versionThis section describes the steps you must perform before upgrading from an earlier version ofID-VSE for Integrity to version A.6.2.0.*. This process converts an existing ID-VSE for Integritydatabase, including historical profile data, to the new version database format. Any historicalprofile data that you want to migrate to the new database format must be installed in the currentlyrunning installation on the CMS.

IMPORTANT: Starting with VSE Management Software version 4.0 (A.04.00.07.xx), licenses forID-VSE for Integrity are managed in the HP SIM License Manager database on the CMS. Whenyou upgrade an HP-UX CMS that has a previous version of ID-VSE for Integrity installed, anyproduct licenses that were previously installed or scanned are automatically migrated to theLicense Manager database. For more information about migrating previous licenses to the newlicense 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 removingversion A.6.2.0.* and reinstalling the older version. Make a backup of your ID-VSE for Integritydatabase before upgrading the software, in case you need to revert to the previous version. Youcan use this backup to restore your current configuration after reverting to the previous versionof 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-VSEfor Integrity version A.6.2.0.*. In this case, you can ignore the steps that concern existing versionsof 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 upgrade1. 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 gWLMdaemons (gwlmcmsd and gwlmagent) and the WBEM service and provider daemons.

2. Stop using the version of Capacity Advisor that is already installed, including thecommand-line interface. If necessary, use the following substeps to disable each automaticallyscheduled Capacity Advisor data collection task:

Before upgrading from a previous version 15

a. Select Tasks & Logs→View All Scheduled Tasks from the Capacity Advisor menubar.

b. Select the task from the list Collect Capacity Advisor Data.c. Click Edit.d. Click Schedule.e. Check the Disable this task check box.f. Click Done.g. Verify that the task you just edited is in the list and now shows Task is Disabled

in the Schedule column.3. Log out of HP SIM.4. (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).5. 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 thisbackup, you can restore your current configuration after reverting to the older version ofthe software. You cannot restore this backup after version A.6.2.0.* is installed. Previousversions of ID-VSE for Integrity used a database format that is incompatible with versionA.6.2.0.*.For more information about backing up and restoring the ID-VSE for Integrity databaseand 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 Backingup 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 instructionsprovided with the new version of HP SIM. In particular, note that you might need to installadditional patches.

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

Install the software on the CMSUse 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 Integrity1. 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 ofHP 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 installationof HP SIM

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

2. (optional) If Oracle version 10g is installed on a server in your environment, you can configureHP SIM and ID-VSE for Integrity to use an Oracle database instead of the defaultPostgreSQLdatabase for internal data management. For specific requirements for using Oracle withID-VSE for Integrity, see HP Insight Software 6.2 Support Matrix.To configure HP SIM for Oracle, use the following steps:a. Ensure that Oracle 10g is installed and running on the Oracle server.b. 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 installedby 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. Reinitialize HP SIM by entering the following command on the CMS:# mxinitconfig -a

3. Run the msswinitconf -a command to configure Insight managed system setup wizardon the CMS:# msswinitconfig -a

IMPORTANT: On an Integrity CMS the msswinitconfig command must be executedafter installing the software and configuring HP SIM, but prior to executingvseinitconfig.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 firsttime.

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 areno errors.

IMPORTANT: If you are upgrading from a previous version of ID-VSE for Integrity, thevseinitconfig command migrates any product licenses that were previously installedor scanned to the HP SIM License Manager database. Review the licensing information inthe log file to make sure that it is correct. You may need to adjust the number of licensedcores using the vselicense command. For more information about migrating previouslicenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 GettingStarted Guide.

5. When vseinitconfig finishes, you are prompted to restart HP SIM. Type “y” and pressEnter to restart HP SIM.

6. (Optional) Execute the command catman to make sure that the ID-VSE for Integritymanpages can be listed by keyword using man -k.

Procedure 3-6 Install ID-VSE for Integrity using existing installation of HP SIM1. Enter the following command on the CMS:

# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file VSEMgmt

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 areno errors.

IMPORTANT: If you are upgrading from a previous version of ID-VSE for Integrity, thevseinitconfig command migrates any product licenses that were previously installedor scanned to the HP SIM License Manager database. Review the licensing information inthe log file to make sure that it is correct. You may need to adjust the number of licensedcores using the vselicense command. For more information about migrating previouslicenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 GettingStarted Guide.

3. When vseinitconfig finishes, you are prompted to restart HP SIM. Type “y” and pressEnter to restart HP SIM.

4. (Optional) Execute the command catman to make sure that the ID-VSE for Integritymanpages can be listed by keyword using man -k.

IMPORTANT: If you are reinstalling or updating an existing installation, you might have alreadyperformed the steps in the following sections. However, you might need to repeat some of thesesteps 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 licensemanagement and Application Discovery certificate exchange.

Start and configure HP SIMAfter installation, use Procedure 3-7 to start HP SIM and run the First Time Wizard to finish theconfiguration process.

18 Installation

Procedure 3-7 Start HP SIM and The First Time Wizard1. 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

where server is the host name of your CMS.2. 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 Options→FirstTime Wizard... from the HP SIM menu bar.

NOTE: You can view HP SIM help for this or any other window by clicking the buttonin the upper right corner of the window.

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. Theselections made here configure HP SIM to show collections, tools, and reports only formanaged environments that are selected.

c. Discovery Discovery is the process of finding and identifying systems in themanagement domain so that they can be managed from the CMS by HP SIM. There aretwo discovery modes: automatic and manual. If you want discovery to be scheduledon an automatic basis, select Schedule and specify how often discovery should run.Whether or not you configure automatically scheduled discovery, run the discoveryprocess manually as soon as you are finished with the First Time Wizard. You can rundiscovery manually by selecting Options→Discovery... from the HP SIM menu barand 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 networkping), or you can specify individualsystems by name or IP address. HP SIM uses WBEM, SNMP, SSH and SMH protocolsfor system identification. For example, HP SIM attempts to contact the WBEM nPartition,virtual partition, and virtual machine providers on a given system to determine thesystem type. HP SIM populates its system database with this information and createsrelationship information such as the parent/child association between a VM Host andits virtual machines.Virtualization Manager uses both the system and relationship information whendisplaying Insight Dynamics resources. Until you install the Insight Dynamics agentsoftware on the managed nodes, little information is available. For information aboutinstalling Insight Dynamics agent software, see “Install Insight Dynamics agent softwareand 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 credentialsand the SNMP credentials for the System Automatic Discovery task.Sign-in Credentials ID-VSE for Integrity uses WBEM connections to obtaininformation from the managed systems. You must establish common WBEM credentialson 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 foryour organization, or use the default value provided.Click Next to continue.

Start and configure HP SIM 19

e. Configure Managed Systems Configure managed systems as they are discovered, byconfiguring WBEM and WMI, SNMP, SSH access, and trust relationship.

f. WMI Mapper Proxy To retrieve managed system information on Windows systems,enter the mapper proxy system host name and port number. The user name andpassword credentials must be entered on the First Time Wizard Configure ManagedSystems page.This page does not appear if you are not managing Windows systems.

g. Privilege Elevation Privilege elevation allows you to specify a non-root login onmanaged systems and a command that can be used to acquirerootprivileges as needed.See also “Privilege elevation” (page 21) and the HP SIM help.

h. E-mail If you do not want email notification of HP SIM events from the CMS, skipthis step. Otherwise, specify the SMTP host and authentication (if required) to be usedfor email notifications. On an HP-UX CMS, you can usually use the CMS as the SMTPhost. Also provide an email address to be used as the “From” portion of the emailheader. HP recommends the name hpsim@hostname. Click Next to continue.

i. Summary Displays all First Time Wizard settings with the option to modify settingsor to finish the First Time Wizard.

4. Run the HP SIM discovery process so that you can select managed nodes for the InsightDynamics agent software installation in the next section. Do this even if you configuredautomatically scheduled discovery in the First Time Wizard. Select Options→Discovery...from the HP SIM menu bar, then click Run Now.

20 Installation

Install Insight Dynamics agent software and configure managed systemsManaged systems require some setup before Insight Dynamics can properly identify them,retrieve data from them, and perform management operations on them. Managed system setupincludes the installation of agent software or configuration of agentless data collection, installationof licenses, and configuration of options specific to the management capabilities intended foruse 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 asWBEM 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 InsightDynamics). For information about manual installation of agent software, see “Alternate procedurefor manual installation of agent software” (page 21).

IMPORTANT: If you are upgrading an existing version of the gWLM agent, you must upgradethe gWLM agent on all systems in an SRD at the same time. You cannot run different versionsof the gWLM agent within a single SRD.

Using managed system setup wizardTo start the managed system setup wizard, select Configure→Managed System Setup Wizard...from the HP SIM top menu. Help is available in each step of the wizard. See also Insight ManagedSystem Setup Wizard 6.2 Getting Started Guide.

IMPORTANT: Before running managed system setup wizard the target managed systems mustbe fully discovered and should have valid credentials stored within HP SIM. You can discoversystems using the HP SIM Discovery page. To access this page select Options→Discovery...from the HP SIM top menu.

Privilege elevationSome 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 customerenvironments. Instead, administrators may be required to use an individual login which isauthorized 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-rootlogin on managed systems and a command that can be used to acquireroot privileges as needed.Privilege elevation can be configured in HP SIM as part of the First Time Wizard or by selectingOptions→Security→Privilege Elevation... from the HP SIM top menu. You will need toconfigure the selected user login on the managed system. Additional configuration may also beneeded. For example, you may need to configure SSH access using Configure→Configure orRepair Agents..., and you may need to configure the managed system to allow host authenticationfor non-root users. For more information, see the HP SIM help.

Alternate procedure for manual installation of agent softwareAgent software can be found in the depots and installation packages that are installed in thedepot directory on the CMS. On an HP-UX CMS, this directory is /var/opt/vse/depot. Ona Windows CMS the directory isinstall-path\depot, whereinstall-path is the directorywhere Insight Dynamics is installed (by default, this directory is C:\Program Files\HP\Virtual Server Environment). Use the following procedures to manually install the agentsoftware.

Install Insight Dynamics agent software and configure managed systems 21

Procedure 3-8 Manual installation of HP-UX agents1. 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, copythe depot files to the depot server.

2. Install the desired depots using the swinstall command, as shown in the followingexample. If you are using a Software Distributor depot server, replace the source part of thecommand 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

3. Repeat the previous step for each of the agents that you want to install.Procedure 3-9 Manual installation of Linux agents1. Copy the desired tar files (file.tar) from the depot directory on the CMS to /var/tmp

on the managed system.2. 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 aWindows CMS it is ininstall-path\lbin, whereinstall-path is the directory whereInsight Dynamics is installed (by default, this directory isC:\Program Files\HP\VirtualServer Environment).

3. Install the agent software using the install-agent.sh script, as shown in the followingexample.

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

4. Repeat the previous step for each of the agents that you want to install.Procedure 3-10 Manual installation of Windows agents1. Copy the desired Windows install files (file.msi) from the depot directory on the CMS

to C:\ on the managed system.2. Install the agent software using the msiexec command, as shown in the following example.

Example 3-3 Install the Utilization Provider on a 32–bit Windows system

C:\> c:C:\> cd \C:\> msiexec /I WMIUtilProvider32.msi /norestart

This command installs the agent interactively using the GUI and does not perform a rebootafter installation. To install the agent with no interaction (quiet mode) and without usingthe GUI, use the /qn option on the msiexec command. For information about othercommand options, use the /help option.

3. Repeat the previous step for each of the agents that you want to install.Procedure 3-11 Manual installation of vseassist command on Windows systems1. Copy the file setupva.exe from the depot directory on the CMS to the managed system.2. Run setupva.exe on the managed system to install vseassist.

22 Installation

After upgrading from a previous versionHP SIM upgrade If you upgraded HP SIM, follow any postinstallation instructions describedin the HP SIM documentation. Make sure that you have installed all required HP-UX or applicationpatches.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 finishedrestarting, 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 minutesand try the command again.Reapply demo licenses to managed systems After upgrading to ID-VSE for Integrity version6.0 any systems that previously had a temporary demonstration (demo) license applied must beexplicitly licensed after the upgrade. To apply an ID-VSE for Integrity version 6.0 demo licenseto a managed system, use either Insight managed system setup wizard or the vselicense -tcommand. See “Using managed system setup wizard” (page 21) or the vselicense(1M) for moredetails.Verify gWLM communication and redeploy your SRDs If you are using gWLM, execute thefollowing command on the CMS to verify that the CMS is configured properly and cancommunicate with installed agents:# /opt/gwlm/bin/gwlm list

If the output of this command lists various policies, the CMS is configured properly. If not, errormessages 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, followthe procedure described next.Rediscover partition-based SRDs If you are using gWLM, and you have upgraded the gWLMagents in the partitions from gWLM A.02.xx to gWLM A.6.2.0.*, you cannot add other partitionsin 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 CapacityReestablish the SRD using Procedure 3-12.Procedure 3-12 Rediscover partition-based SRDs1. 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

In these commands, replace hosts with a space-separated list of the partitions in the SRD.2. 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 thedesired value (Managed or Advisory):mode="Managed"

• Ensure that the interval attribute for the sharedResourceDomain element is setto the desired value:

After upgrading from a previous version 23

interval="x"

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

• Ensure that theworkloadReference entries in the compartment definitions are correct,and adjust the names in the workload definitions themselves. For example, you mightsee “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 commandcapprofile -lt to verify that previously collected historical data has been migrated to thenew ID-VSE for Integrity database. This command lists the workload profiles and the time rangeof 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 ofyour automatically scheduled Capacity Advisor data collection tasks using Procedure 3-13.Procedure 3-13 Restore scheduled Capacity Advisor tasks1. Select Tasks & Logs→View All Scheduled Tasks from the Capacity Advisor menu bar.2. Select the task from the list Collect Capacity Advisor Data.3. Click Edit.4. Click Schedule.5. Clear the Disable this task check box.6. Click Done.7. 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 agentsIf you update ID-VSE for Integrity on the CMS to version A.6.2.0.* without updating the gWLMagent software on some of your managed systems, update those agents as soon as it is convenientto do so. Use Procedure 3-14 to update the agents.Procedure 3-14 Update gWLM agents after updating the CMS1. 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 continuerunning the gWLM daemons (gwlmcmsd and gwlmagent) and the WBEM service andprovider daemons.

2. Install and start the agents as described in “Install Insight Dynamics agent software andconfigure managed systems” (page 21).

3. For any partition-based SRDs, follow the steps described in “Rediscover partition-basedSRDs” (page 23). For SRDs based on PSETs, FSS groups, or virtual machines, redeploy thoseSRDs.To determine if PSETs (HP-UX processor sets, the PROCSETS bundle) is installed use theswlist ProcessorSets command.

Preparing a Red Hat Linux managed systemOpenPegasus is required for Insight Dynamics of Linux systems. Red Hat (RHEL) distributionsinclude 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 YaSTControl Center.

Preparing a ProLiant SUSE Linux managed systemThis section provides instructions on how to prepare a ProLiant system running SUSE LinuxEnterprise 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 Servicesfor ID-VSE for Integrity.Because OpenPegasus WBEM Services cannot be installed when OpenWBEM is present on thesystem, the following procedures describe how to remove OpenWBEM, install OpenPegasusWBEM Services, and deploy the ID-VSE for Integrity agents required for managing the SUSELinux system. If the managed system is already running OpenPegasus 2.5 or greater then noaction is required.Procedure 3-15 Remove OpenWBEMOpenWBEM must be removed from the system before installing OpenPegasus WBEM onto aProLiant managed system running SUSE Linux Enterprise Server 9 or 10. Use the followingprocedure 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 ControlCenter or another package management application.

Procedure 3-16 Download OpenPegasus WBEMUse the following steps to download OpenPegasus WBEM packages from the HP website.1. Go to http://www.hp.com/.2. Enter “OpenPegasus WBEM Services” in the product search field and click the Search

button.3. 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 isspecific to ID-VSE for Integrity.

4. Click the Download button to download the package.

Procedure 3-17 Install OpenPegasus WBEMAfter downloading the OpenPegasus package, install it and start OpenPegasus WBEM Serviceson the system.1. Login to the Linux system as root and run the following command to install the package:

# rpm –Uvh tog-pegasus-version.distro.arch.rpm

2. 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. Thenext steps provide information on how to configure the CMS to enable VSE Agent Distributorfor ID-VSE for Integrity agents.

Preparing a ProLiant SUSE Linux managed system 25

Additional configuration stepsIf your Linux system is not an HP SIM managed system yet, refer to the “Setting Up ManagedSystems” section of the HP Systems Insight Manager 6.0 Installation and User Guide available athttp://www.hp.com/go/hpsim. This document also contains information on how to configureWBEM credentials for a Linux system.At this point users can install VSE Agents onto the Linux managed systems, necessary for InsightDynamics. 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 IntegrityAfter installation, you must perform additional steps to configure ID-VSE for Integrity for yourenvironment. For a description of these steps, see the sections that follow.

IMPORTANT: ID-VSE for Integrity does not operate correctly until you complete thesepostinstallation configuration steps. You must perform these steps even when you reinstall orupdate an existing installation.

Configuring user authorizationsUsers must be authorized in HP SIM in order to run the ID-VSE for Integrity tools. To configureuser 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. ChooseOptions→Security→Users and Authorizations from the HP SIM menu bar. Use the tabs toview and change the toolbox authorizations for each user. For detailed information about creatingand updating authorizations, refer to the HP SIM online help.The following table defines the authorization provided by each of the toolboxes associated withID-VSE for Integrity. The sections that follow present examples showing how to configureauthorizations based on the user's role.

NOTE: If your CMS is also a managed system, then any authorizations required on managedsystems will also be required on the CMS.

Required AuthorizationsToolbox

Authorize this toolbox on the CMS to allow use of the Insight managed system setupwizard. Authorize this toolbox on each managed system that will be configured usingthe managed system setup wizard.

System Setup

This is a master toolbox that applies to all tools installed in HP SIM. Authorize thistoolbox on selected systems for users whose role requires administrative authority onthose systems. Refer to the following sections for examples.

All Tools

ID-VSE for Integrity users should have this authorization on the CMS and All ManagedSystems. Otherwise, they will not have access to HP SIM monitoring tools such as theSystem Page or Property Pages.

Monitor Tools

Authorize this toolbox on managed systems to allow use of Capacity Advisor on thosesystems. Authorize this toolbox on the CMS to allow users to edit data with the ProfileEditor.

Capacity Advisor

Authorize this toolbox on managed systems to allow users to view and manage thosesystems using Virtualization Manager, Global Workload Manager, Capacity Advisor,and VM Manager. This toolbox also allows users to manage application and processdata collection using Application Discovery. Authorize on the CMS only if the CMSwill also be a managed system.

VSE All Tools

ID-VSE for Integrity users should have this authorization on the CMS and All ManagedSystems. Otherwise, they will not be able to use the Tools→VSE Management... actionon the HP SIM menu bar or VSE Management product menus. Authorize this toolboxon the CMS to allow view-only use of Application Discovery.

VSE Monitor

Authorize this toolbox on the CMS to manage storage pools and storage tags.VSE Storage

Authorize this toolbox on the CMS to allow users to view and manage systems usinggWLM version A.01.x. For gWLM version A.02.00.00 or later, this toolbox is not used;authorize VSE All Tools instead.

gWLM All Tools

Configuring user authorizations 27

Required AuthorizationsToolbox

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 Monitorinstead.

gWLM Monitor

Authorize this toolbox to allow full access to HP Virtual Connect Enterprise Managersoftware. This authorization permits viewing and modifying the VCEM configuration.

VCEM Full Access

Authorize this toolbox to allow read-only access to HP Virtual Connect EnterpriseManager software. This authorization permits viewing but not modifying the VCEMconfiguration.

VCEM Read Only

Role: ID operator, application administrator, or capacity plannerWith these authorizations, you can view all Integrity and HP 9000 servers in the managementdomain. You can examine the configuration of all managed systems through VirtualizationManager, Partition Manager, Application Discovery, and Virtual Machines Manager. You candefine and view a logical server using Virtualization Manager. You can view real-time applicationdata through Application Discovery, real-time and historical data through gWLM, and historicaldata through Capacity Advisor. You cannot make any configuration changes to the managedsystems or Application Discovery components, or edit Capacity Advisor data with the ProfileEditor.

Systems AuthorizedToolbox

CMS and All Managed SystemsMonitor Tools

CMS and All Managed SystemsVSE Monitor

All Managed SystemsCapacity Advisor

Role: ID system administratorThese authorizations provide all of the capabilities of the ID Operator role but also allow you tochange the configuration of specific managed systems. On systems authorized with the All Toolstoolbox, 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.

Systems AuthorizedToolbox

CMS and All Managed SystemsSystem Setup

CMS and All Managed SystemsMonitor Tools

CMS and All Managed SystemsVSE Monitor

All Managed SystemsCapacity Advisor

Subset of All Managed SystemsAll Tools

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

Role: ID senior system administratorThese 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 aworkload allows you to retain its collected data while waiting to migrate the workload to anew 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 matchingand event reporting.

Systems AuthorizedToolbox

CMS and All Managed SystemsSystem Setup

CMSVSE All Tools

CMS and All Managed SystemsMonitor Tools

CMS and All Managed SystemsVSE Monitor

All Managed SystemsCapacity Advisor

Subset of All Managed SystemsAll Tools

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

Role: senior capacity plannerThese authorizations provide all of the capabilities of the VSE Operator role. In addition, theCapacity Advisor authorization on the CMS allows you to edit and delete profile data.

Systems AuthorizedToolbox

CMS and All Managed SystemsMonitor Tools

CMS and All Managed SystemsVSE Monitor

CMS and All Managed SystemsCapacity Advisor

Role: storage administratorThis authorization allows a storage administrator to perform operations on storage pool entrieswithout enabling any other Insight Dynamics operations.

Systems AuthorizedToolbox

CMSVSE Storage

Role: legacy Global Workload Manager operatorThis authorization is maintained for backward compatibility with gWLM version 1. This user isable to view real-time and historical reports for any system in the data center that is managedby gWLM version A.01.x. This user is not authorized to use Virtualization Manager, PartitionManager, 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 authorizationsdescribed earlier, which provide more granular host-based authorization.

Systems AuthorizedToolbox

CMSgWLM Monitor

Role: legacy Global Workload Manager administratorThis authorization is maintained for backward compatibility with gWLM version 1. This user isable to manage any system in the data center with gWLM version A.01.x, but is not authorizedto use Virtualization Manager, Partition Manager, Virtual Machines Manager, or CapacityAdvisor. Because this authorization cannot be restricted to specific managed systems, HPrecommends using the other authorizations described earlier, which provide more granularhost-based authorization.

Systems AuthorizedToolbox

CMSgWLM All Tools

Selecting and updating the authorized systems setWhen you create an HP SIM authorization, you can select the individual authorized systems, oryou 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 iscreated. If additional systems are later added to that collection or removed from it, you shouldupdate the authorization to match the changed collection.Use the following procedure to update a user's authorizations:1. Choose Options→Security→Users and Authorizations from the HP SIM menu bar.2. Select the Authorizations tab.3. 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 onlinehelp.

Complete the certificate exchange for Application Discovery

NOTE: The information in this help topic applies only in the situation where ApplicationDiscovery 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 forsecure data transmission.

Application Discovery uses Secure Sockets Layer (SSL) certificates to authenticate and securedata transmission between version 4.0 (and older) Application Discovery agents and theApplication Discovery server. Once Application Discovery components are installed, theaccompanying certificate information for Application Discovery server and for ApplicationDiscovery agent must be exchanged to allow the server and agents to recognize legitimatetransmissions.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 exchange1. Initiate certificate exchange by selecting Configure →Insight Dynamics Agents→Exchange

AD Agent Certificates from the HP SIM top menu.

30 Configure ID-VSE for Integrity

2. Select the HP-UX systems where you want the exchange to occur using the HP SIM systemselection list. Click Apply.

3. Verify the system selection and click Next.4. 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 reportingdata 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 thefollowing:• 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 enableremote communication, login is the user name on the managed system, and password isthe password of that user on the managed system.

Completing certificate exchange from the command lineFrom the command line, you can exchange certificates with one or more managed hosts.1. Log in as a privileged user on the system hosting the CMS. (See “Configuring user

authorizations” (page 27) for tool access information.)2. 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 securelyacross 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 managedhost, and the agent supplies its SSL certificate to the CMS. Application Discovery agentscan 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 recognitionpreviously established between Application Discovery server on the CMS and ApplicationDiscovery agents on managed nodes. This relationship must be re-established when the CMS isreinstalled or restored by completing the Application Discovery certificate exchange.

Complete the certificate exchange for Application Discovery 31

32

5 Support and other resourcesContacting HP

Information to collect before contacting HPBe 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 supportUse 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 resellersFor 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 feedbackHP welcomes your feedback. To make comments and suggestions about product documentation,send a message to:docsfeedback@hp.comInclude the document title and manufacturing part number in your message. All submissionsbecome the property of HP.

Related informationThe latest versions of manuals and white papers for Insight Dynamics and related products canbe downloaded from the Insight Dynamicsinformation library:http://www.hp.com/go/insightdynamics/docsFor more information about Insight Dynamics and related products and solutions, visit thefollowing 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 ConfigurationGuide.For a description of system requirements for ID-VSE for Integrity, see HP Insight Software 6.2Support Matrix.

Command references (manpages)Insight Dynamics and related products include manpages for HP-UX and Linux systems andcommand reference pages for Microsoft Windows systems. These pages provide details aboutcommands, file formats, and related information. The following tables list reference pages relatedto Insight Dynamics.

Reference pages installed on the CMS

DescriptionReference page

Set advanced options for Capacity Advisor agentless data collection, and view a list ofsystems configured for agentless data collection

capagentlesscfg(1M)

Configure Capacity Advisor benchmark CPU scaling to normalize collected datacapcustombenchmark(1M)

Format of Capacity Advisor custom benchmark database filescapcustombenchmark(4)

Collect Capacity Advisor data from systemscapcollect(1M)

Export HP Performance Agent (formerly HP OpenView Performance Agent, or OVPA)system data from managed systems and import into Capacity Advisor

capovpaextract(1M)

Export HP Performance Management Pack (PMP) system data from specified managedsystems and import the data into Capacity Advisor (Windows CMS only)

cappmpextract

Import, export, display, invalidate and remove Capacity Advisor data for workloadsor systems

capprofile(1M)

Format of Capacity Advisor import and export filescapprofile(4)

Global Workload Managergwlm(1M)

Overview of Global Workload Managergwlm(5)

Global Workload Manager (gWLM) daemongwlmcmsd(1M)

Produce advanced textual summary reports for workload resource utilizationgwlmreport(1M)

Secure network communications for Global Workload Managergwlmsslconfig(1M)gwlmimportkey(1M)gwlmexportkey(1M)

Configure or unconfigure the Insight managed system setup wizardmsswinitconfig(1M)

Overview of XML file structure for Global Workload Managergwlmxml(4)

Help resolve Insight Dynamics configuration problemsvseassist(1M)

Configure or unconfigure the Insight Dynamics softwarevseinitconfig(1M) [p. 38]

Manage licenses to use (LTUs) on HP Integrity and HP 9000 systemsvselicense(1M)

Reference pages installed with agent software on managed systems

DescriptionReference page

Control Application Discovery certificates from the managed nodeagent_config(1M)

Control or modify the operation of the Application Discovery agentamgrd(1M)

34 Support and other resources

DescriptionReference page

Global Workload Manager (gWLM) agentgwlmagent(1M)

Place a process in a gWLM workloadgwlmplace(1M)

Send metric data to gWLM for use in a custom policygwlmsend(1M)

Secure network communications for Global Workload Managergwlmsslconfig(1M)gwlmimportkey(1M)gwlmexportkey(1M)

Display status for the managed node's agent, SRD, and license Managergwlmstatus(1M)

(HP-UX) system utilization data collection daemonutild(1M)

(Linux) system utilization data collection daemonutild(8)

Reference page installed on cell-based complexes

DescriptionReference page

Start Partition Managerparmgr(1M)

Reference pages installed on systems running HP Integrity Virtual Machines

DescriptionReference page

About HP Integrity Virtual Machineshpvm(5)

Create a cloned copy of an Integrity virtual machinehpvmclone(1M)

Collect crash dumps, logs, system status, and configuration on guests and the IntegrityVM Host

hpvmcollect(1M)

Connect to the console of an Integrity virtual machinehpvmconsole(1M)

Create a new Integrity virtual machinehpvmcreate(1M)

Manage the Integrity VM device databasehpvmdevmgmt(1M)

Display information about the Integrity VM environmenthpvminfo(1M)

Rename or modify the attributes of an Integrity virtual machinehpvmmodify(1M)

Move a virtual machine to another Integrity VM Host systemhpvmmigrate(1M)

Configure virtual network deviceshpvmnet(1M)

Remove an Integrity virtual machinehpvmremove(1M)

Start an Integrity virtual machinehpvmstart(1M)

Display status of one or more Integrity virtual machineshpvmstatus(1M)

Stop an Integrity virtual machinehpvmstop(1M)

Selected HP Systems Insight Manager software reference pages

DescriptionReference page

Configure the agent to work with a CMSmxagentconfig(1M)

Add, remove, or list authorizations in Systems Insight Managermxauth(1M)

Manage global settings in Systems Insight Managermxglobalsettings(1M)

Perform initial configuration of the servermxinitconfig(1M)

Related information 35

DescriptionReference page

Add, modify, identify, remove, or list nodes in Systems Insight Managermxnode(1M)

Start Systems Insight Manager and the TomCat webservermxstart(1M)

Display or return (via exit code) the current ready/not-ready state of Systems InsightManager

mxstatus(1M)

Stop Systems Insight Manager and the TomCat webservermxstop(1M)

Add, modify, remove, or list users in Systems Insight Managermxuser(1M)

36 Support and other resources

A Command reference

37

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

SYNOPSISPath (HP-UX): /opt/vse/bin/vseinitconfigPath (Windows): install-path\bin\vseinitconfigvseinitconfig [ -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)

DESCRIPTIONThe vseinitconfig command performs initial configuration of Insight Dynamics on an HPSystems Insight Manager (SIM) Central Management Server (CMS). It can also be used to removethe existing configuration and to back up or restore Insight Dynamics database. (Backup andrestore 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 andMicrosoft® Windows® CMS.This command performs four different functions on the CMS, corresponding to the four syntaxoptions shown in the synopsis. With no options specified, the initial configuration function isperformed.1. Initial configuration after installing or updating Insight Dynamics on the CMS. This includes

initial configuration of HP Insight Virtualization Manager software, HP Insight GlobalWorkload Manager software for Integrity (gWLM), and HP Insight Capacity Advisorsoftware, as well as initialization of the Insight Dynamics database.

2. Removal of Insight Dynamics menu items and actions from HP SIM and clearing of theInsight 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 CMSrunning HP-UX using the PostgreSQL database).

4. Safe restore of the Insight Dynamics database from a previous backup (only on a CMSrunning HP-UX using the PostgreSQL database).

OptionsThe vseinitconfig command recognizes the following options. Each option can be expressedin a long or short form.If no options are specified, the initial configuration function is performed.-a|--initconfig Perform the initial configuration of Insight Dynamics (this

is also the default function performed if no option isspecified). This action requires that HP SIM is running andconfigured with the mxinitconfig command. Thiscommand registers Insight Dynamics tools, toolboxes, andactions with HP SIM and initializes the Insight Dynamicsdatabase.On a Microsoft Windows CMS, vseinitconfig -a isautomatically 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 andConfiguration Guide).On an HP-UX CMS, the optional --clobber or -F optioncauses an existing Insight Dynamics database to beremoved without being backed up first. If that option isnot used, then an existing database will be upgraded fromthe previous version of Insight Dynamics. This does notapply to a Microsoft Windows CMS.

NOTE: HP recommends backing up your entire CMSconfiguration before upgrading from a previous versionof Insight Dynamics. For details about this and otherupgrade considerations, see the Insight Dynamicsinstallation guide (HP Insight Dynamics 6.2 Integrity CMSInstallation and Configuration Guide or HP Insight Software6.2 Installation and Configuration Guide), and review thenotes in the description of the --restore option below.

-F|--clobber Clear any existing Insight Dynamics database withoutbacking it up. For more information about how this optionaffectsvseinitconfig, see the descriptions of the options-a|--initconfig and -r|--unconfig.

-q|--quiet Do not display any output. Do not prompt for HP SIMrestart 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 HPSystems Insight Manager after initial configuration ofInsight Dynamics. It only applies in combination with theinitial configuration option (-a or --initconfig) or the“unconfigure” option (-r or --unconfig).Use -x restart_sim=true to restart HP SIM withoutany further prompting after all of the Insight Dynamicsapplications are configured. There can be a delay of oneor two seconds after vseinitconfig finishes executionbefore HP SIM is ready to respond to mx... commands.Use-x restart_sim=false to return immediately afterall of the Insight Dynamics applications are configured,without restarting HP SIM.If this option is not used, you will be prompted whetherto restart HP SIM after all of the Insight Dynamicsapplications are configured.

-r|--unconfig Remove the installed Insight Dynamics tools from HP SIM.The existing database and configuration information willnot be removed unless the optional --clobber or -Foption is used.Important: The optional --clobber or -F option causesan existing Insight Dynamicsdatabase to be removedwithout being backed up first. If you do not perform abackup of the Insight Dynamics database before executingthis command, you will lose all of your Insight Dynamicsdata, including gWLM and Capacity Advisor configurationand historical data.On a Microsoft Windows CMS, vseinitconfig -r isautomatically invoked by the installer. On an HP-UX CMS,

39

you must execute the command before removing thesoftware (see HP Insight Dynamics 6.2 Integrity CMSInstallation and Configuration Guide).

-b|--backup Back up the Insight Dynamics database, including gWLMand Capacity Advisor data, to protect against loss of data.Insight Dynamics must be initialized before you canperform a backup. For information about initializingInsight Dynamics, see the earlier description of the--initconfig option.

NOTE: This option is only available on a CMS runningHP-UX using the PostgreSQL database.

The backup is created in the directory specified by the -dor --dir option. This directory must be initially empty ormust not yet exist.The backup created by this command contains only InsightDynamics data. For information about backing up the HPSIM database, refer to the HP white paper Backing up andrestoring HP Systems Insight Manager data files in an HP-UXor Linux environment, available from the Information Librarylink at http://www.hp.com/go/hpsim.If you are creating a backup in preparation for relocatingthe CMS, HP recommends that you first undeploy allshared resource domains (SRDs). This will make it easierto redeploy the SRDs after the CMS is moved. To ensurethat your backup includes up-to-date historic data, youshould 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 followingcommand on the CMS:

capcollect

-s|--restore Restore the Insight Dynamics database from the backupin the directory named by the -d or --dir option. InsightDynamics must be initialized before you can perform arestore, therefore the --clobber or -F is also required inorder to replace the database. For information aboutinitializing Insight Dynamics, see the earlier descriptionof the --initconfig option.

NOTE: This option is only available on a CMS runningHP-UX using the PostgreSQL database.

HP SIM must be stopped when the restore operation isperformed. To stop HP SIM, execute the commandmxstopon the CMS. Use mxstart to restart HP SIM after therestore operation is finished.

40 Command reference

NOTE: If the CMS or managed systems have beenmodified 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 createdwith a previous version of Insight Dynamics. Previousversions of the Insight Dynamics database may beincompatible with the current version. If you have not yetinstalled the current version of the software and you intendto restore from a previous backup, perform the restorefirst. Then install and initialize the new software. Theinitialization process upgrades the already-restoreddatabase to the current format.If you have already updated the software and you need torestore from a backup made by a previous version of thesoftware, 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 andConfiguration Guide or HP Insight Software 6.2Installation and Configuration Guide).

2. Reinstall the version of the software on which thebackup was created, according to the installationinstructions published with that release.

3. Restore the Insight Dynamics database from thebackup.

4. Install the new version of Insight Dynamics accordingto the current installation guide.

5. Initialize the software as described in the earlierdescription of the --initconfig option. Thisupgrades the restored database to the new format.

Removing and Reinstalling VSEIf Insight Dynamics is removed and reinstalled, collection of Capacity Advisor data can misssome data on the CMS. To avoid this, back up the Insight Dynamics database before removingInsight Dynamics, and restore the database after it is reinstalled.

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

EXAMPLESThe following command performs initial configuration of Insight Dynamics and prompts whetherto restart HP SIM after configuration is complete.vseinitconfig -a

The following command performs initial configuration of Insight Dynamics, removes any existingInsight 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 toolsfrom HP SIM. The --clobber option causes the database information to be removed withoutmaking a backup:vseinitconfig --unconfig --clobber

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

AUTHORSvseinitconfig was developed by Hewlett-Packard Company.

DOCUMENT LAST UPDATEDJuly 2010

FILESThe console (non-error) output from the vseinitconfig command is written to the followinglog 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 defaultinstall-path on a Windows CMS isC:\Program Files\HP\Virtual ServerEnvironment, but this directory can be changed at installation time.

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

42 Command reference

B Back up the CMS configurationThe upgrade process is not reversible. To revert to a previous installation of the software, youmust restore the previous CMS configuration as well as any remote databases used by thesoftware. Therefore, HP recommends that you make a backup of your current installation beforeupgrading the software.

Back up your existing CMS configuration prior to upgrading the softwareThe upgrade process is not reversible. To revert to a previous installation of the software, youmust restore the previous CMS configuration as well as any remote databases used by thesoftware. Therefore, HP recommends that you make a backup of your current installation beforeupgrading the software.Procedure B-1 Backing up your HP ID-VSE for Integrity CMS configurationTo make a complete backup of your HP ID-VSE for Integrity configuration, perform the followingsteps: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 theremote database, use the following steps:a. Stop the running gWLM daemon by entering the following command:

gwlmcmsd --stop

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

c. Stop HP SIM by entering the following command:/opt/mx/bin/mxstop

d. Back up thegwlm remote database on the Oracle server using Oracle Enterprise Manageror Oracle Recovery Manager. This database is used by multiple ID-VSE for Integrityapplications.

e. Back up any remote database tables used by other SIM applications, if necessary. OtherHP SIM applications may have their own specific backup requirements. See thedocumentation for those applications for specific instructions.

f. Back up the HP SIM remote database using Oracle Enterprise Manager or OracleRecovery Manager. The HP SIM remote database name begins with “Insight_v”, followedby a version number.

2. Make a full backup of the CMS. Performing a full backup of an HP-UX server may requirebooting the server in a lower init state or stopping additional system services, so that allconfiguration files can be read in a stable condition. Consult your backup softwaredocumentation for specific requirements.

Procedure B-2 Restoring your CMS configuration from backupIf you need to restore the CMS configuration that was saved using the preceding procedure, usethe 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 IntegrityUse Procedure C-1 to completely remove ID-VSE for Integrity from an HP-UX CMS.Procedure C-1 Remove ID-VSE for Integrity1. 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 thefollowing 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 -rf /opt/vse /etc/opt/vse /var/opt/vse# rm -rf /opt/gwlm /etc/opt/gwlm /var/opt/gwlm# rm -rf /opt/amgr /etc/opt/amgr /var/opt/amgr# rm -rf /opt/hpwebadmin/webapps/vse.war

45

46

Index

Aagent, 19, 20

installation, 21amgr_remote_config

certificate exchange example, 31authorizations, 27

Bbackup VSE database, 15, 16Bastille, 9

CCentral Management Server (see CMS)certificates

completing the exchange, 30exchanging from the command line, 31exchanging from within HP Systems Insight Manager

software, 30CMS

requirements, 9command

reference pages, 34

Ddatabase, 15, 17

backup, 15, 16restore, 15, 16

demo license, 23discovery (see HP SIM, discovery)documentation, 33

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

Gglobal credentials, 12Global Workload Manager (see gWLM)gWLM

agent installation, 21

HHP Capacity Advisor (see Capacity Advisor)HP Global Workload Manager (see gWLM)HP Integrity VM (see Integrity VM)HP SIM, 12

discovery, 19, 20finding Application Discovery from, 30First Time Wizard, 18, 19installation, 11, 12, 16launching, 18supported versions, 9

HP Systems Insight Manager (see HP SIM)HP Virtualization Manager (see Virtualization Manager)

HP-UXpatches, 9, 12

IInsight Dynamics agent software (see agent)installation

CMS, 16managed systems, 21

LLDAP, 12license

demo, 23installation, 21

Linux managed systems, 13, 24, 25

Mmanaged system setup wizard, 21managed systems

installing VSE agent software, 21Linux, 13Microsoft Windows, 14setup, 21

manpage, 34manuals, 33Microsoft Windows managed systems, 14mxagentconfig

enabling remote communication from HP SystemsInsight Manager software, 31

Nnetwork

firewalls, 9NIS, 12

OOpenPegasus WBEM, 24, 25OpenSSH (see ssh)Oracle, 17

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

Rrelease notes, 12remote command execution, 21requirements, 9

firewalls, 9restore VSE database, 15, 16root, 12

47

SSecure Shell (see ssh)security, 12

SSL certificate exchange, 30Shared Resource Domain (see SRD)SIM

documentation, 33toolboxes, 27user authorizations, 27

SNMP, 19SRD, 23, 24, 45

undeploy before upgrade, 15ssh, 13, 14, 19SSL

certificate exchange, 30swinstall command, 17, 18Systems Insight Manager (see HP SIM)

Ttasks

exchanging certificates for application discovery, 30, 31

toolbox, 27

Uuser authorizations, 27

Vvirtual machine, 19Virtual Server Environment (see VSE)Virtualization Manager, 19VM (see Integrity VM)VM Host, 19vPars (see virtual partition)VSE

documentation, 33vseinitconfig command, 17, 18

WWBEM, 19

authentication, 12provider (see agent)

white papers, 33

48 Index

49