VSE Management Software Installation andUpdate Guide

HP Part Number: T2786-90030Published: September 2006, Edition 1.0

© Copyright 2006 Hewlett-Packard Development Company, L.P.

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, 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. HP shallnot 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.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Table of Contents

About This Document.....................................................................................7Intended Audience..................................................................................................................................7Typographic Conventions.........................................................................................................................7Related Information.................................................................................................................................7Publishing History...................................................................................................................................9HP Encourages Your Comments................................................................................................................9

1 Introduction.............................................................................................11

2 System Requirements.................................................................................13Operating Systems Supported on the CMS...............................................................................................13Additional Software Requirements on the CMS.........................................................................................13Operating Systems Supported on Managed Systems..................................................................................14Additional Software Requirements on Managed Systems............................................................................14Additional Requirements for Using gWLM on Managed Systems.................................................................15

Managed System Compartment Software............................................................................................16Additional requirements in the release notes.............................................................................................16

3 Installation...............................................................................................17Preparing For Installation.......................................................................................................................17

Pre-Installation Steps for Linux Managed Systems..................................................................................17Pre-Installation Steps for Windows Managed Systems...........................................................................18

Before Upgrading From a Previous Version...............................................................................................19Installing the Software on the CMS..........................................................................................................20Launching HP SIM.................................................................................................................................21Installing VSE Agent Software on Managed Systems..................................................................................23After Upgrading From a Previous Version.................................................................................................24

4 VSE Management Software Configuration...................................................27

Command Reference....................................................................................29vseinitconfig(1M)..................................................................................................................................30

A Uninstalling The VSE Management Software................................................33

Index.........................................................................................................35

Table of Contents 3

4

List of Tables1 Manpages Installed with VSE Management Software on the CMS...............................................................82 Manpages Installed with VSE Agent Software on Managed Systems............................................................83 Manpage Installed on Cell-Based Complexes............................................................................................84 Manpages Installed on Systems Running HP Integrity Virtual Machines.........................................................85 Selected HP SIM Manpages...................................................................................................................92-1 Operating Systems Supported on the CMS.........................................................................................132-2 Additional Software Requirements on the CMS...................................................................................132-3 Operating Systems Supported on Managed Systems............................................................................142-4 Additional Software Requirements on Managed Systems......................................................................142-5 Additional Requirements for Using gWLM on Managed Systems...........................................................152-6 Managed System Compartment Software...........................................................................................16

5

6

About This DocumentThis document describes system requirements and installation procedures for the Virtual Server Environment(VSE) Management Software. System administrators can use this guide to install the VSE ManagementSoftware or upgrade from a previous version of the software. Installation of both Central Management Server(CMS) components and managed system components is covered. This document is intended to be usedalong with the VSE Management Software Quick Start Guide, which provides an overview of the HP VirtualServer Environment (VSE), the VSE Management Software, and software configuration procedures.

Intended AudienceThis document is intended to be used by VSE System Administrators, VSE Application Administrators, CapacityPlanners, and other technical professionals involved with data center operations, administration, and planning.An understanding of HP-UX system administration concepts and procedures is assumed.

Typographic ConventionsThis document uses the following typographic conventions.Book Title Title of a book or other document.Linked Title Title that is a hyperlink to a book or other document.http://www.hp.com A Web site address that is a hyperlink to the site.Command Command name or qualified command phrase.user input Commands and other text that you type.computer output Text displayed by the computer.Enter The name of a keyboard key. Note that Return and Enter both refer to the same

key. A sequence such as Ctrl+A indicates that you must hold down the key labeledCtrl while pressing the A key.

term Defined use of an important word or phrase.variable The name of an environment variable, for example PATH or errno.value A value that you may replace in a command or function, or information in a display

that represents several possible values.find(1) HP-UX manpage. In this example, “find” is the manpage name and “1” is the

manpage section.

Related InformationA copy of this document is installed on the CMS along with the VSE Management Software in the directory/opt/vse/doc. A more recent version of this document may be available on the HP Instant InformationCD. You can also download the latest version of this document from the following site:http://docs.hp.com/en/hplex.html

The following related documents can also be downloaded from the same site:

• VSE Management Software Quick Start Guide

• VSE Management Software Release Notes

• Getting Started with HP Integrity Essentials Global Workload Manager

• HP Integrity Essentials Global Workload Manager Administrator's Guide

• HP Integrity Essentials Capacity Advisor User's Guide

• Getting Started with HP Integrity Virtual Machines Manager

• HP Integrity Virtual Machines Installation, Configuration, and Administration

• HP Integrity Virtual Machines Release NotesThe VSE Management Software and related products include HP-UX manpages with details about commands,file formats, and related information. The following tables list some of the manpages that are most relevantto the VSE Management Software.

Intended Audience 7

Table 1 Manpages Installed with VSE Management Software on the CMS

Collect Capacity Advisor data from systemscapcollect(1M)

Export OpenView Performance Agent (OVPA) system data from managed systems and import intoCapacity Advisor

capovpaextract(1M)

Import, export, display, invalidate and remove Capacity Advisor data for workloads or systemscapprofile(1M)

Format of Capacity Advisor import and export filescapprofile(4)

Global Workload Managergwlm(1M)

Overview of Global Workload Managergwlm(5)

Global Workload Manager (gWLM) daemonsgwlmcmsd(1M)gwlmagent(1M)

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

Place a process in a gWLM workloadgwlmplace(1M)

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

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

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

Configure or unconfigure the VSE Management Softwarevseinitconfig(1M)

Install or remove licenses for VSE Management Software productsvselicense(1M)

Table 2 Manpages Installed with VSE Agent Software on Managed Systems

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

(Linux) System utilization data collection daemonutild(8)

(Windows) Utilization Provider Service (document installed in\Program Files\Hewlett-Packard\UtilProvider\doc)

UPService.pdf

Table 3 Manpage Installed on Cell-Based Complexes

Start Partition Managerparmgr(1M)

Table 4 Manpages Installed on Systems Running HP Integrity Virtual Machines

About Integrity Virtual Machineshpvm(5)

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

Collect crash dumps, logs, system status, and configuration on guests and the VM Hosthpvmcollect(1M)

Connect to the console of a virtual machinehpvmconsole(1M)

Create a new virtual machinehpvmcreate(1M)

Manage the Integrity VM device databasehpvmdevmgmt(1M)

Display information about the Integrity VM environmenthpvminfo(1M)

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

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

Configure virtual network deviceshpvmnet(1M)

Remove a virtual machinehpvmremove(1M)

Start a virtual machinehpvmstart(1M)

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

Stop a virtual machinehpvmstop(1M)

8 About This Document

Table 5 Selected HP SIM Manpages

Add, remove, or list authorizations in HP SIMmxauth(1M)

Perform initial configuration of the CMSmxinitconfig(1M)

Add, modify, identify, remove, or list nodes in HP SIMmxnode(1M)

Add, modify, remove, or list users in HP SIMmxuser(1M)

Additional related information can be found in the following documents and Web sites:

• Online help for HP Systems Insight Manager and the VSE Management Software products

• HP Systems Insight Manager 5.0 Installation and User Guide (http://docs.hp.com/en/5991-4498/)

• http://www.hp.com/go/hpsim (Follow the Information Library link for access to white papers and otherdocuments.)

• http://www.hp.com/go/vse (VSE news, events, and solutions)

• The HP Virtual Server Environment, by Dan Herington and Bryan Jacquot, Prentice Hall, 2006 (http://www.hp.com/hpbooks)

Publishing HistoryPublication DateEditionSupported Operating SystemsManufacturing Part Number

September 20061.0CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterManaged systems:HP-UX 11i v1, HP-UX 11i v2Microsoft® Windows® Server 2003 Enterprise EditionMicrosoft® Windows® Server 2003 Datacenter EditionRed Hat Enterprise Linux 4 update 2 or later for Intel®Itanium®SUSE Linux Enterprise Server 9 Service Pack 2 or later forIntel Itanium

T2786-90030

HP Encourages Your CommentsYour comments and suggestions regarding product features will help us develop future versions of the VirtualServer Environment Management Software. Use the following e-mail address to send feedback directly tothe VSE Management Software development team: vse@hpuxweb.fc.hp.com.

NOTE: HP cannot provide product support through this e-mail address. To obtain product support, contactyour HP Support Representative, your HP Services Representative, or your authorized HP reseller. For moreinformation about support services, see the support Web site at http://www.hp.com/go/support.

For other ways to contact HP, see the Contact HP Web site at http://welcome.hp.com/country/us/en/contact_us.html.

Publishing History 9

10

1 IntroductionThis document describes the installation of the VSE (Virtual Server Environment) Management Softwareversion A.02.50.00. This includes system requirements, installation of the software on the Central ManagementServer (CMS), upgrading from previous versions, installation of agent software and WBEM providers onmanaged systems, and backup and restoration of the VSE Management Software database.Please read the VSE Management Software Quick Start Guide for an overview of the HP Virtual ServerEnvironment (VSE) and the VSE Management Software, key VSE concepts and terminology, andpost-installation software configuration procedures.

11

12

2 System RequirementsThe VSE Management Software runs under HP Systems Insight Manager version 5.00.01.00 or later. HPrecommends upgrading to the current version of HP SIM when you install the VSE Management Software.System requirements for HP SIM are defined in the HP Systems Insight Manager 5.0 Installation and UserGuide (http://docs.hp.com/en/5991-4498/). Refer to that document for the complete requirements for theCentral Management Server (CMS) and managed systems. In particular, note that you may need to installHP-UX patches before you install HP SIM.

IMPORTANT: If you are currently using an earlier version of HP SIM, please refer to “Before UpgradingFrom a Previous Version” for the recommended upgrade procedure.

In addition to the requirements imposed by HP SIM, the requirements for this release of the VSE ManagementSoftware are detailed in the following sections.

Operating Systems Supported on the CMSTable 2-1 Operating Systems Supported on the CMS

December 2004 or later. Patch PHSS_34338 must be installed.HP-UX 11i v1

September 2004 or later. Patch PHSS_34339 must be installed.HP-UX 11i v2

Systems running Linux or Microsoft® Windows® are not currently supported.

Additional Software Requirements on the CMSTable 2-2 Additional Software Requirements on the CMS

The Java™ Run-time Environment (JRE 1.4.2) is required by Capacity Advisor and gWLM. If youwant to use long hostnames (longer than 64 characters), you must install JRE 1.4.2.07 or later.Java Out of Box (JOOB) version 2.03 or later is required. JOOB is shipped with HP-UX as optionalselectable software. Installation of JOOB will require a reboot.

Java

To use gWLM you will need 1 GB of available disk space in /var/opt/. If you intend to keephistorical data, HP recommends allowing 4 GB for every 100 workloads managed by gWLM. Ifyou are not interested in historical data, you can trim the historical database by using the command:# gwlm history --truncate

Disk Space for gWLM

To allow OpenView Performance Agent access to the gWLM data the MeasureWare.PERFDSIfileset (version C.03.85 or later) must be installed. The following command lists the file if it is installedon the system:# /usr/sbin/swlist MeasureWare.PERFDSI

If this fileset is not installed, it is available for install as part of HP GlancePlus/UX Pak versionC.03.85.00 or later.

gWLM Data Access fromOpenView Performance Agent

If the CMS is also a managed system, then all of the additional requirements for managed systemsapply to the CMS. Refer to “Additional Software Requirements on Managed Systems” (page 14)for those requirements.

CMS as managed system

Operating Systems Supported on the CMS 13

Operating Systems Supported on Managed SystemsTable 2-3 Operating Systems Supported on Managed Systems

HP-UX 11i v1

Memory patch PHSS_33349 must be installed in order to use Virtualization Manager and CapacityAdvisor.

HP-UX 11i v2(HP-UX 11i v2 Update 2 if thesystem will be managed withgWLM)

Microsoft Windows Server 2003 Enterprise EditionMicrosoft Windows Server 2003 Datacenter Edition

NOTE: Systems running Microsoft Windows cannot be managed by this release of gWLM.

Microsoft Windows

Red Hat Enterprise Linux 4 update 2 or later for Intel ItaniumSUSE Linux Enterprise Server 9 Service Pack 2 or later for Intel Itanium

Linux

Additional Software Requirements on Managed SystemsTable 2-4 Additional Software Requirements on Managed Systems

WBEM is required on managed systems to support the visualization and configuration features ofVirtualization Manager and the collection of utilization data for Capacity Advisor. Without WBEM,only gWLM is functional.On HP-UX managed systems HP WBEM Services for HP-UX version A.02.00.08 or later must beinstalled. Earlier versions of WBEM may generate cimserver errors, including timeouts in VirtualizationManager and VM Manager, and messages such as “CIM failure” and “Connection Refused”. Thelatest version of HP WBEM Services for HP-UX can be obtained from HP Software Depot at http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B8465BA.On Linux managed systems you must install tog-pegasus and the HP Integrity Essentials FoundationPack for Linux Management CD. Refer to “Pre-Installation Steps for Linux Managed Systems”(page 17) for details.

WBEM

If you use LDAP-UX, HP recommends using version B.04.00.xx. Previous versions (such as B.03.xx)deny WBEM authentication, as well as authentication to HP System Management Homepage (SMH).LDAP-UX Version B.03.xx prevents HP SIM and the VSE Management Software from readingrequired WBEM data.The latest version of LDAP-UX Integration for HP-UX can be obtained from HP Software Depot athttp://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=J4269AA.

LDAP

OpenSSH is required on managed systems in order to install the VSE agent software from HP SIM,create monitored workloads, and execute commands on managed systems remotely from the CMS.Remote command execution is used by Partition Manager, VM Manager, and capovpaextract(1M).OpenSSH for HP-UX managed systems is provided by HP-UX Secure Shell, which is installed bydefault. It must be configured for use by HP SIM. This is covered in “Installing VSE Agent Softwareon Managed Systems” (page 23).On 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). You will also have to manually configureOpenSSH for use with HP SIM. Refer to “Pre-Installation Steps for Windows Managed Systems”(page 18) for details.On Linux systems, OpenSSH is usually installed by default, or it can be installed from the Linuxdistribution media. However, you may need to manually configure OpenSSH for use with HP SIM.Refer to “Pre-Installation Steps for Linux Managed Systems” (page 17) for details.For detailed information about configuring SSH for use with HP SIM, refer to the HP white paperSecure Shell (SSH) in HP SIM 5.0, available from the Information Library link at http://www.hp.com/go/hpsim.

OpenSSH

The WBEM providers and other agents required by the VSE Management Software will be installedduring the installation process described in this document. HP recommends that you follow thisprocess to install the latest versions of the agent software. The following entries in this table describespecific issues with earlier provider versions.

WBEM Providers and AgentSoftware

VM Provider version 1.20 or later must be installed on VM Host systems. Earlier versions of the VMProvider can be used on guest Virtual Machines.

VM Provider

14 System Requirements

The vPar provider that was included with the March 2006 release of HP-UX 11i v2 (B.11.23) doesnot work properly. With the March 2006 version installed, HP SIM and the VSE Managementsoftware do not discover and display virtual partitions correctly. The vPar provider that is includedwith the VSE Management software fixes this problem. However, it presents the same version numberas the March 2006 version.The same problem exists with the HP-UX 11i v1 (B.11.11) version of the vPar provider when usedwith WBEM version A.02.00.09.You can fix this problem by executing the following command on each system where the vParprovider has been installed:# /opt/wbem/bin/cimmof -n root/cimv2/vpar \ /opt/vparprovider/mof/HPUX_VParLocalPartition.mof

Alternatively, on systems running HP-UX 11i v2 you can remove the installed version of the vParprovider and install the version delivered with the VSE Management software (or forcibly reinstallthe VSE Management Software version).

vPar Provider

Additional Requirements for Using gWLM on Managed SystemsTable 2-5 Additional Requirements for Using gWLM on Managed Systems

The Java Run-time Environment (JRE) version 1.4.2 or 1.5 is required. If both versions are installed,gWLM uses Java 1.4.2 by default. If you prefer to use Java 1.5, execute the following commands:# ln -sf /opt/java1.5/ /opt/gwlm/jre# chown -h root /opt/gwlm/jre# chgrp -h bin /opt/gwlm/jre

If you want to use long hostnames (longer than 64 characters), you must install JRE 1.4.2.07 orlater.

IMPORTANT: Installing gWLM will automatically overwrite existing Java 1.4.x installations withJava 1.4.2. There are a number of security fixes and other improvements in version 1.4.2 thatgWLM makes use of. Do not use gWLM with Java 1.4.0 or Java 1.4.1.

Java

On rx8640 or rx7640 systems running HP-UX 11i v2, patch PHKL_35174 must be installed inorder to manage nPartitions and virtual partitions.

Patch PHKL_35174

If you plan to use gWLM on a Linux system, the standard C++ “backward-compatibility” libraries(compat-libstdc++) must first be installed on the system. Otherwise, installation of the gWLMagent software will fail. To determine if these libraries have been installed, execute the followingcommand to display the installed version:$ rpm -qa | grep compat

If the libraries are not installed, install the corresponding package from your Linux operating systemCD.

Linux Managed Systems

Install this software on HP-UX managed systems even if the system does not use nPartitions. Installingthe VSE agent software from the CMS using the procedure described in “Installing VSE AgentSoftware on Managed Systems” (page 23) will ensure that all of the required providers, includingthe gWLM Agent, are installed.HP-UX 11i v1 requires version B.11.11.01.03.01.01 or later.HP-UX 11i v2 on HP 9000 requires version B.11.23.01.03.01.01 or later.HP-UX 11i v2 on HP Integrity requires version B.11.23.01.04 or later.

nPartition Provider

HP 9000 (PA-RISC 2.0) or HP Integrity (IA-64)Supported processors

2 GB minimumMemory

25 MB available in /opt/Disk space

Additional Requirements for Using gWLM on Managed Systems 15

Managed System Compartment SoftwareTable 2-6 “Managed System Compartment Software” lists the supported versions of the products thatprovide the compartments that gWLM manages. A managed system must have at least one of these productsinstalled.Table 2-6 Managed System Compartment Software

Instant Capacity v7 or later is required to simulate CPU movement.nPartitions

vPars version A.03.01.05 or later.The following tunable kernel parameters must be configured as shown:max_thread_proc at least 768nkthread max_thread_proc + the number of threads needed by all the other

processes on the system

Virtual Partitions

HP Integrity Virtual Machines version A.02.00 or later. For HP-UX 11i v2 Update 2, install patchesPHKL_32518, PHKL_33052, PHKL_33604, and PHKL_33605.

The following tunable kernel parameters must be configured as shown:max_thread_proc at least 768nkthread max_thread_proc + the number of threads needed by all the other

processes on the system

Virtual machines

For HP-UX 11i v1, you need to download and install the following free products from http://software.hp.com:• HP-UX Processor Sets• The HP-UX 11i Version 1 Quality Pack

This software is already included in HP-UX 11i v2.

Processor Sets (psets)

The PRM-Sw-Krn.PRM-KRN fileset must be installed. The following command lists the fileset if it isinstalled on the system. Any version of the fileset is acceptable.# /usr/sbin/swlist PRM-Sw-Krn.PRM-KRN

If this fileset is not installed, it is available for install as part of the bundle PRMKernelSW, which isavailable from http://software.hp.com.The following patches are required:HP-UX 11i v1 PHKL_30034, PHKL_30035, PHKL_31993, PHKL_31995,

PHKL_32061.HP-UX 11i v2 Update 2 PHKL_32518, PHKL_33052, PHKL_33604, PHKL_33605.

CAUTION: Your system will panic if these patches are not installed and you attempt to deployan SRD based on FSS groups.The following tunable kernel parameters must be configured as shown:max_thread_proc At least 192 on HP-UX 11i v1.

At least 768 on HP-UX 11i v2 Update 2.

nkthread max_thread_proc + the number of threads needed by all the otherprocesses on the system

Fair-Share Scheduler (FSS)

Additional requirements in the release notesRefer to the following documents for additional requirements and installation notes:

• VSE Management Software Release Notes• HP Integrity Virtual Machines Release NotesThese documents are available on the HP Instant Information CD. The latest versions can also be downloadedfrom http://docs.hp.com/en/hplex.html.

16 System Requirements

3 InstallationUse the following general steps to install HP SIM and the VSE Management Software.1. Obtain the VSE Management Software installation package. The software can be installed from the

HP-UX AR media by selecting the optional bundle VSEMgmt. It is also available as a single downloadfrom Software Depot at http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=vse. The software includes a 90-day trial license. For moreinformation about VSE Management Software licenses, refer to the VSE Management Software QuickStart Guide.

2. Prepare for VSE Management Software installation by installing the required software and patches,establishing a common WBEM user identity on the CMS and managed systems, and completingpre-installation steps for Linux and Microsoft Windows managed systems. See “Preparing For Installation”.

3. If you are upgrading from a previous version of the VSE Management Software, perform the upgradepre-installation steps as described in “Before Upgrading From a Previous Version” (page 19).

4. Install HP SIM and the VSE Management Software on the CMS. See “Installing the Software on theCMS”.

5. Launch HP SIM and run the First Time Wizard and the Discovery process. See “Launching HP SIM”(page 21).

6. Install the WBEM providers and other agent software on your managed systems. See “Installing VSEAgent Software on Managed Systems” (page 23).

7. If you upgraded from a previous version of the VSE Management Software, perform the upgradepost-installation steps as described in “After Upgrading From a Previous Version” (page 24).

8. Configure the VSE Management Software for your environment by defining user authorizations andactivating licenses. See “VSE Management Software Configuration” (page 27).

Preparing For InstallationRefer to the HP Systems Insight Manager 5.0 Installation and User Guide (Installation Overview andRequirements chapter) for detailed patch requirements for HP SIM and for patch installation instructions.Verify that your CMS and managed systems meet the VSE Management Software system requirementsdescribed in System Requirements (page 13).Check the VSE Management Software Release Notes for any updates to the requirements or installationinstructions. This document is available on the HP Instant Information CD. The latest version can also bedownloaded from http://docs.hp.com/en/hplex.html.Create a common WBEM user account on the CMS and managed systems. The VSE Management Softwareuses WBEM connections to obtain information from the managed systems. You must establish commonWBEM credentials on the CMS and on the managed systems to allow authenticated access to WBEM data.HP recommends that you assign a user name that is the same on all your servers and is reserved for use byWBEM. For security reasons, this user name should not have root privileges and should not have a loginshell associated with it. Use NIS, LDAP, or other techniques to maintain a single password for this user nameacross all of your systems. You must enter this user name and password during initial setup of HP SIM. Referto “Launching HP SIM” (page 21).For more information about WBEM security configuration in HP SIM, refer to the HP white paper UnderstandingHP Systems Insight Manager security, available from the Information Library link at http://www.hp.com/go/hpsim.

Pre-Installation Steps for Linux Managed SystemsOn managed systems running Red Hat Enterprise Linux, disable SELinux to avoid conflicts with the WBEMproviders and agent software.In order for Linux managed systems to be correctly discovered by HP SIM, you must install WBEM andrequired WBEM providers from the HP Integrity Essentials Foundation Pack for Linux Management CD. Youcan download the contents of this CD in tar format using the following procedure:1. Visit the Web site http://www.hp.com/go/integritylinux.2. Click on the Software & Drivers link.

Preparing For Installation 17

3. Under the section Support for your products, select the option Download drivers and software(and firmware).

4. In the same section, fill in your server product information in the product field (for example, “integrityrx7620 servers” and press Enter. The support center page for your server should be displayed.

5. Under Select operating system, click the link that corresponds to your Linux OS version. The Downloaddrivers and software page for your server should be displayed.

6. Click the Software - Support Pack link to jump to the correct section of the page.7. Click the Download button under the Software - Support Pack section to download the tar file.8. Install the software according to the instructions included in the docs directory contained in the tar

file.9. Make sure that the tog-pegasus package is installed and running on the system.10. On Red Hat Enterprise Linux, you may need to modify the file /etc/Pegasus/access.conf to allow

WBEM access using your designated WBEM user name and password. Follow the steps below toconfigure this file. In this example, your designated WBEM user name is assumed to be wbemuser.a. Look for the following line in this file:

-: ALL EXCEPT pegasus:wbemNetwork

b. Change this line to either of the following options:# Allow access only from user 'wbemuser':-: ALL EXCEPT wbemuser pegasus:wbemNetwork

# Allow access by all users:+: ALL EXCEPT :wbemNetwork

c. If tog-pegasus is not running, start it by executing the following command:# /etc/init.d/tog-pegasus start

OpenSSH on Linux managed systems must be configured for use by HP SIM. Normally you can use the sameprocedure that is used to configure OpenSSH for HP SIM on HP-UX managed systems. This is covered in“Installing VSE Agent Software on Managed Systems” (page 23). However, if you are using SuSE LinuxEnterprise Server 9, you must first manually configure OpenSSH to use password authentication.

IMPORTANT: SuSE Linux Enterprise Server 9 ships with SSH configured to use PAM authentication insteadof password authentication. Password authentication is required in order for the mxagentconfig to configureOpenSSH for use by HP SIM.

On managed systems running SuSE Linux Enterprise Server 9, change to password authentication using thefollowing procedure:1. Configure the following lines in /etc/ssh/sshd_config on the managed system:

PasswordAuthentication yes #UsePAM yes

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

# kill -SIGHUP pid

Pre-Installation Steps for Windows Managed SystemsOn Windows managed systems OpenSSH is not installed by default, but it can be installed from the HPSmart Setup installation media (version 4.5 or later). Use the following procedure to install OpenSSH andconfigure it for use with HP SIM. You can then install the VSE agent software and WMI/WBEM providers

18 Installation

from HP SIM using the procedure described in “Installing VSE Agent Software on Managed Systems”(page 23).1. Follow the instructions in the HP Smart Setup CD to install OpenSSH Services on the Windows managed

system. During installation you will need to specify the user name and password for the account thatwill run the OpenSSH service. The Administrator account is typically used for this.

NOTE: During installation, OpenSSH automatically imports your local user accounts into its passwordfile. If additional accounts are added later, you must re-install OpenSSH or use the sshuser commandto 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 Administrator-password

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

NOTE: If you are using HP SIM version 5.00.02.00 or later, this step can be performed within HPSIM by selecting the managed systems to configure, then choosing Configure ⇒ Configure or RepairAgents... from the HP SIM menu bar. At the Configure or Repair Settings page, select Configuresecure shell (SSH) access.For earlier versions of HP SIM, you must manually execute the mxagentconfig command, as describedabove.

4. If you are using Partition Manager to manage Windows systems, you must also create a user accountnamed “root” on those Windows systems. Partition Manager uses this user name for remote executionof nPartition commands through OpenSSH. Add this user to the Administrators group in Windows,then add this user to OpenSSH using the sshuser command.Execute the following command on the CMS to configure remote connections from the CMS using theroot account:# 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 theAdministrator or root accounts. Partition Manager will use the root account for remote commandexecution.

Before Upgrading From a Previous VersionThis section describes the steps you must perform before upgrading an existing installation of VSE ManagementSoftware version A.02.00.00 to version A.02.50.00. This process will convert an existing VSE ManagementSoftware database, including historical profile data, to the new version A.02.50.00 database format. Anyhistorical profile data that you want to migrate to the new database format must be installed in the currentlyrunning A.02.00.00 installation on the CMS.The upgrade process is not reversible. It can only be undone by uninstalling version A.02.50.00 andreinstalling the previous version. In case you find it necessary to revert to the previous version, you mustmake a backup of your VSE Management Software database before upgrading the software. You can usethis backup to restore your current configuration after reverting to the previous version of the software.Use the procedure below to prepare for the upgrade from version A.02.00.00 to version A.02.50.00.

NOTE: This procedure can also be used to upgrade from gWLM version A.01.x to VSE ManagementSoftware version A.02.50.00. In this case, the steps below that concern existing versions of other VSEManagement Software (for example, Capacity Advisor) can be ignored.

Before Upgrading From a Previous Version 19

After upgrading, be sure to follow the instructions in “After Upgrading From a Previous Version” (page 24).In particular, you need to be familiar with the issue described in “Rediscover Partition-Based SRDs” (page 25).

1. If you are using Global Workload Manager, undeploy all Shared Resource Domains (SRDs) and stopusing the existing version, including the command-line interface. It is okay to 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 the command-line interface.If necessary, use the following substeps to disable each automatically scheduled Capacity Advisor datacollection task:a. Choose Tasks & Logs ⇒ View All Scheduled Tasks? from the Capacity Advisor menu bar.b. Select the task from the list Collect Capacity Advisor Data ?.c. Click Edit.d. Click Schedule.e. Check the Disable this task checkbox.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 from HP Systems Insight Manager.4. (Optional) Use the capcollect command to collect the latest Capacity Advisor data into the VSE

Management Software database. Refer to capcollect(1M) for details.5. Execute the following command to collect the latest gWLM historical data into the VSE Management

Software database:# /opt/gwlm/bin/gwlm history --flush

6. Make a backup of your VSE Management Software database. This will be used if you need to revertto the previous version of the software. With this backup, you can restore your current configurationafter reverting to the previous version of the software. You will not be able to restore this backup whenversion A.02.50.00 is installed. The structure of the VSE Management Software version A.02.00.00database is incompatible with version A.02.50.00.For detailed information about backing up and restoring the VSE Management Software database andreverting to a backup from a previous version of the software, refer to vseinitconfig(1M). This manpageis included below in the “Command Reference” (page 29).

7. Make a backup of the HP SIM database, so that both databases can be restored together. Refer to theHP SIM documentation for information about backing up the HP SIM database.

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

9. Execute the following command on the CMS to shut down the CMS server daemons:# /opt/mx/bin/mxstop

You are now ready to install the software as described in the following sections. After you have completedthe installation steps, refer to “After Upgrading From a Previous Version” (page 24) for additional steps thatyou should perform.

Installing the Software on the CMSUse the following procedure to install HP SIM and the VSE Management Software on an HP-UX CMS.1. Install the software by executing the following command:

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

This command installs HP SIM version 5.00.02.00 and the VSE Management Software versionA.02.50.00. If you are currently running HP SIM version 5.00.01.00 and you choose not to upgradeHP SIM, use the following command instead:

20 Installation

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

NOTE: The system reboots after the installation.

2. Configure HP SIM by executing the following command:# /opt/mx/bin/mxinitconfig -a

This command performs HP SIM setup tasks, including database initialization. It typically takes severalminutes for the mxinitconfig command to complete. Errors and exceptions are logged to the file/var/opt/mx/logs/initconfig.log. Review the output of this command to ensure there are noerrors.

3. Configure the VSE Management Software by executing 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 thereare no errors.

4. (Optional) Execute the command catman to make sure that the VSE Management Software manpagescan be listed by keyword using man -k.

Launching HP SIMAfter installation, you need to launch HP SIM and run the First Time Wizard to finish the configuration process.Start a Web browser and make sure that it is not configured to block pop-up windows. If your browser isconfigured to block pop-ups, then the First Time Wizard will not be automatically displayed after you launchHP SIM. To launch HP SIM, direct your web browser to the following URL:http://server:280

where server is the host name of your CMS.When launched for the first time after a new install, HP SIM automatically displays the First Time Wizard.Otherwise, run this wizard manually by choosing Options ⇒ First Time Wizard... from the HP SIM menubar.

NOTE: You can view help for this wizard (or any other window in HP SIM) by clicking the button inthe upper right corner of the window.

The most important items to configure in the wizard are on the WBEM, Discovery, and Users screens.1. Introduction screen:

Click Next to continue.

2. WBEM screen:The VSE Management Software uses WBEM connections to obtain information from the managedsystems. You must establish common WBEM credentials on the CMS and on the managed systems toallow authenticated access to WBEM data. HP recommends the creation of a common user name andpassword for exclusive use by WBEM. Refer to “Preparing For Installation” (page 17). You should nowprovide the user name and password on this screen. If you prefer to specify passwords individually foreach managed system, refer to the HP Systems Insight Manager 5.0 Installation and User Guide forinstructions.

3. SNMP screen:Configure the SNMP community name that is appropriate for your organization, or use the default valueprovided. Click Next to continue.

Launching HP SIM 21

4. Discovery screen:Discovery is the process of finding and identifying systems in the management domain so that they canbe managed from the CMS by HP SIM. There are two discovery modes: automatic and manual. If youwant discovery to be scheduled on an automatic basis, select Schedule and specify how often discoveryis run.Whether or not you configure automatically scheduled discovery, you should run the discovery processmanually as soon as you are finished with the First Time Wizard. Discovery can be run manually bychoosing Options ⇒ Discovery... from the HP SIM menu bar and then clicking Run Now.In either automatic or manual mode, you can specify IP ranges for a ping sweep (detection of systemsby their response to a network ping), or you can specify individual systems by name or IP address. HPSIM uses WBEM, SNMP, SSH and SMH protocols for system identification. For example, HP SIMattempts to contact the WBEM nPartition, Virtual Partition, and Virtual Machine providers on a givensystem to determine if the system is any of these types. HP SIM populates its system database with thisinformation and creates relationship information such as the parent/child association between a VMHost and its virtual machines.Virtualization Manager uses both the system and relationship information when displaying VSE resources.However, at this point you have not installed the VSE agent software on the managed nodes, so littleinformation will be available until you have finished that step. Refer to “Installing VSE Agent Softwareon Managed Systems” (page 23).When you have finished configuring the discovery settings, click Next to continue.

5. Users screen:In this screen you can specify user names that are valid on the CMS. HP SIM provides a number ofuser-based security options to define the authorized capabilities of each user. For complete information,refer to the HP Systems Insight Manager 5.0 Installation and User Guide.It is not necessary to set up any users now. After you have completed the First Time Wizard, you willhave to configure user authorizations to allow access to the VSE Management Software tools. This isdiscussed in the VSE Management Software Quick Start Guide. Click Next when you are ready tocontinue.

6. E-mail screen:Skip this step if you do not want e-mail notification of HP SIM events from the CMS. Otherwise, specifythe SMTP host and authentication (if required) to be used to send e-mail. On an HP-UX CMS, you canusually use the CMS as the SMTP host. You should also provide an e-mail address to be used as the“From” portion of the e-mail header. HP recommends the name hpsim@hostname.Click Next to continue.

7. Event Handling screen:Skip this step if you do not want alerts from the CMS. Otherwise, specify which events will cause alertsto be sent, and the e-mail address to which alerts should be sent.Click Next to continue.

8. Summary screen:Review your selections and click Finish to continue; or, click Previous to go back and correct yourearlier selections.

9. Finish screen:Click Close to exit the First Time Wizard.

You should now run the HP SIM discovery process so that you can select managed nodes for the VSE agentsoftware installation in the next section. Do this even if you configured automatically scheduled discovery inthe First Time Wizard. Choose Options ⇒ Discovery... from the HP SIM menu bar, then click Run Now.

22 Installation

Installing VSE Agent Software on Managed SystemsThe VSE Management Software relies on WBEM providers and other agent software in order to obtain datafrom the managed systems. These components can be installed on your managed systems using HP SIM.Not all agents need to be installed on all systems. For example, if you want to use only gWLM and you donot require Virtualization Manager or Capacity Advisor, then you only need to install the gWLM agent.Similarly, it is not necessary to install the VM Provider except on VM Host servers and virtual machines.However, the following procedure provides an easy, consistent way to install the agent software on eachmanaged system by automatically installing all the agents and providers on each system.For an HP-UX managed system, this procedure installs all the products contained in/var/opt/vse/depot/vseagent.depot. This file is installed on the CMS with the VSEMgmt bundle,as described in “Installing the Software on the CMS” (page 20).For a Linux managed system, this procedure installs all the products contained in/var/opt/vse/depot/vseagent.tar. This file is installed on the CMS with the VSEMgmt bundle, asdescribed in “Installing the Software on the CMS” (page 20).For a Microsoft Windows managed system, this procedure installs all of the Windows installation packages/var/opt/vse/depot/*.msi. These files are installed on the CMS with the VSEMgmt bundle, as describedin “Installing the Software on the CMS” (page 20).1. Launch HP SIM by directing your Web browser to:

http://server:280

where server is the host name of your CMS.2. Make sure that the OpenSSH is installed and configured for HP SIM on each of your managed systems.

For HP-UX managed systems, select the systems to configure, and choose Configure ⇒ Configureor Repair Agents... from the HP SIM menu bar. At the Configure or Repair Settings page, selectConfigure secure shell (SSH) access. This step can also be done manually using the mxagentconfigcommand. Refer to mxagentconfig(1M) for more information.This procedure will also configure OpenSSH on Linux managed if you have first performed thepre-installation steps described in “Pre-Installation Steps for Linux Managed Systems” (page 17).This procedure will only work for Windows managed systems if you are using HP SIM version 5.1 orlater. Otherwise, you must manually configure OpenSSH as decribed in “Pre-Installation Steps forWindows Managed Systems” (page 18).For detailed information about configuring SSH for use with HP SIM, refer to the HP white paper SecureShell (SSH) in HP SIM 5.0, available from the Information Library link at http://www.hp.com/go/hpsim.

3. Select your HP-UX and Linux managed systems and choose Configure ⇒ Configure VSEAgents ⇒ Install Unix-Linux VSE Agents... from the HP SIM menu bar. Click Run Now to startthe installation. Review the output for error messages before continuing.

IMPORTANT: If you are upgrading managed systems that were using version A.01.x of the gWLMagent, all agents within an SRD must be upgraded at the same time. You cannot combine A.01.x andA.02.x agents in a single SRD.

NOTE: If you are upgrading the version of gWLM on systems where gWLM is already managingpsets or FSS groups, any processes that were placed using the gwlmplace command are moved tothe default pset or default FSS group. You can avoid this behavior by placing applications in workloadswhen you define the workloads.

4. Select your Windows managed systems and choose Configure ⇒ Configure VSE Agents ⇒ InstallWindows VSE Agents... from the HP SIM menu bar. Click Run Now to start the installation. Reviewthe output for error messages before continuing.

Installing VSE Agent Software on Managed Systems 23

NOTE: Windows systems must be rebooted after installation of the VSE agent software.

5. Select the systems that you want to manage with gWLM, and choose Configure ⇒ Configure VSEAgents ⇒ Start gWLM Agent... from the HP SIM menu bar to start the gWLM agent on the selectedsystems.

NOTE: You can configure the gWLM agent to start automatically whenever the system is booted byexecuting the following command on the managed system:

# /opt/gwlm/bin/gwlmagent --enable_start_on_boot

6. Run the HP SIM discovery process again on the managed systems where agent software has beeninstalled. This will cause HP SIM to update its information about these systems. Select the affected systemsand choose Options ⇒ Discovery... from the HP SIM menu bar, then click Run Now.

If you do not want to use this procedure, you can selectively install the agents required for HP-UX managedsystems from the /var/opt/vse/depot/vseagent.depot file. This file was installed on the CMS withthe VSEMgmt bundle, as described in “Installing the Software on the CMS” (page 20). It contains all of theVSE Management Software agents. The bundles in this depot can be copied to a Software Distributor depotserver, or the file can be copied to each managed node for selective installation.Assuming the depot file has been copied to /var/tmp, the following examples show the commands to useto install individual agents from this depot. If you are using a Software Distributor depot server, replace thesource part of these commands with the server location of the depot.Install the gWLM agent:# /usr/sbin/swinstall -s /var/tmp/vseagent.depot T2743AA

Install the Utilization Provider:# /usr/sbin/swinstall -s /var/tmp/vseagent.depot UtilProvider

Install the VM Provider:# /usr/sbin/swinstall -s /var/tmp/vseagent.depot VMProvider

Install the nPartition Provider:# /usr/sbin/swinstall -s /var/tmp/vseagent.depot nParProvider

Install the vPar Provider:# /usr/sbin/swinstall -s /var/tmp/vseagent.depot vParProvider

Similarly, you can individually install the RPM files that are included in/var/opt/vse/depot/vseagent.tar on Linux systems, using the rpm command. On Windows managedsystems, you can individually install the /var/opt/vse/depot/*.msi files by double-clicking the filesthat you want to install.

After Upgrading From a Previous VersionHP SIM UpgradeIf you upgraded HP Systems Insight Manager, follow any post-install instructions described in the HP SIMdocumentation. Make sure that you have installed all required HP-UX or application patches.Stop and restart HP SIM by executing the following commands on the CMS:# /opt/mx/bin/mxstop# /opt/mx/bin/mxstart

24 Installation

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

This command should list the users defined in HP SIM. If an error is displayed, wait several minutes and trythe command again.Verify gWLM CommunicationIf you are using gWLM, execute the following command on the CMS to verify that the CMS is configuredproperly and can communicate with installed agents:# /opt/gwlm/bin/gwlm list

If the output of this command lists various policies, the CMS is configured properly. Othewise, you will geterror messages. Wait a few seconds and try the command again. If you still get errors, take the actionssuggested by the error messages.Rediscover Partition-Based SRDsIf you are using gWLM and you have either of the following types of partition-based SRDs:

• a vPars-based SRD inside an nPartition

• an nPartition-based SRD using Instant Capacityand you have upgraded the gWLM agents in the partitions from gWLM A.01.x to gWLM A.02.50.00, youwill not be able to add other partitions in the same complex to the SRD. Use the following procedure on theCMS to re-establish the SRD:1. With the SRD deployed, re-discover the SRD. For a vPars-based 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 explained in gwlmxml(4):

• Ensure that the mode attribute for the sharedResourceDomain element is set to the desiredvalue (Managed or Advisory):mode="Managed"

• Ensure that the interval attribute for the sharedResourceDomain element is set to the desiredvalue:interval="x"

• Ensure that the ticapMode attribute for the sharedResourceDomain element is set to all ifgWLM should allocate Temporary Instant Capacity when needed:ticapMode="all"

• Ensure that the workloadReference entries in the compartment definitions are correct, andadjust the names in the workload definitions themselves. For example, you may have“host.OTHER.2” instead of “host.OTHER”.

3. Import the file to re-create the SRD:

After Upgrading From a Previous Version 25

# gwlm import --file=/tmp/myfile.xml --clobber

Because the SRD was already deployed, the new SRD definition is deployed on import, taking the placeof the original SRD.

Verify Capacity Advisor data MigrationIf you are using Capacity Advisor, use the command capprofile -lt to verify that previously collectedhistorical data has been migrated to the new VSE Management Software database. This command shouldlist the workload profiles and the time range of the data stored in the database. Refer to capprofile(1M) fordetails.Restore Scheduled Capacity Advisor TasksIf you are using Capacity Advisor, follow the steps below to restore each of your automatically scheduledCapacity Advisor data collection tasks:1. Choose 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. Uncheck the Disable this task checkbox.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.

26 Installation

4 VSE Management Software ConfigurationAfter installation, you need to perform two additional steps in order to properly configure the VSE ManagementSoftware for your environment. These steps are described in detail in the VSE Management Software QuickStart Guide. This document is available on the HP Instant Information CD. The latest version can also bedownloaded from http://docs.hp.com/en/hplex.html.1. Configure user authorizations for access to the VSE Management Software tools. Refer to the chapter

named Configuring User Authorizations for details.2. Activate permanent licenses before the end of the free trial period. Refer to the chapter named Activating

Licenses for details.

27

28

Command Reference

29

vseinitconfig(1M)NAMEvseinitconfig -- Configure or unconfigure the VSE Management Software

SYNOPSISPath: /opt/vse/bin/vseinitconfigvseinitconfig [ -a | --initconfig ] [ -F | --clobber ]vseinitconfig -r | --unconfigvseinitconfig { -b | --backup } { -d | --dir=path }vseinitconfig { -s | --restore } { -d | --dir=path } [ -F | --clobber ]

DESCRIPTIONThe vseinitconfig command performs initial configuration of the Virtual Server Environment (VSE)Management Software on an HP Systems Insight Manager (SIM) Central Management Server (CMS). It canalso be used to remove the existing configuration and to back up or restore the VSE Management Softwaredatabase. With no arguments, the initial configuration function is performed.The HP Virtual Server Environment (VSE) is an integrated server offering that provides a flexible computingenvironment, helping you to maximize use of your server resources. HP VSE Management Software providesthe visualization, configuration, workload policy, and capacity planning tools to optimize the system resourcesin your VSE.The vseinitconfig command is installed on the Central Management Server (CMS) with the VSEManagement Software. This command performs four different functions on the CMS, corresponding to thefour syntax options shown above.1. Initial configuration after installing or updating the VSE Management Software on the CMS. This includes

initial configuration of HP Integrity Essentials Virtualization Manager, HP Integrity Essentials GlobalWorkload Manager (gWLM) and HP Integrity Essentials Capacity Advisor, as well as initialization ofthe VSE Management Software database.

2. Removal of the VSE Management Software menu items and actions from HP SIM and clearing of theVSE Management Software database. This option is automatically invoked during removal of the VSEManagement Software.

3. Safe backup of the VSE Management Software database to protect against loss of data.4. Safe restore of the VSE Management Software database from a previous backup.

OptionsThe vseinitconfig command recognizes the following options. Each option can be expressed in a longor short form, in order to provide compatibility with corresponding options in the related commandsmxinitconfig(1M) and the gwlminitconfig command that was provided with gWLM version 1.x.If no options are specified the initial configuration function is performed.-a --initconfig

Either of these options performs the initial configuration of the VSE Management Software (this is alsothe default function performed if no option is specified). This action requires that HP SIM has beenconfigured with the mxinitconfig command and HP SIM must be running. This command registersthe VSE Management Software tools, toolboxes, and actions with HP SIM, and also initializes the VSEManagement Software database.The optional --clobber or -F option will cause an existing VSE Management Software database tobe removed without being backed up first. Otherwise, if the database already exists it will be upgradedfrom the previous version of the VSE Management Software.

NOTE:Before upgrading from a previous version of the VSE Management Software, refer to the VSE ManagementSoftware Installation and Update Guide, and to the description of the --restore option below forimportant information.

30

-F --clobber

Clear any existing VSE Management Software database without backing it up.-r --unconfig

Remove an existing VSE Management Software configuration and database.Important: this operation will delete the contents of the VSE Management Software database. A backupshould be performed before executing this step, or you will lose all of your VSE Management Softwaredata, including gWLM and Capacity Advisor configuration and historical data.If HP SIM is not running, a script named /opt/vse/cleanup_vsemgmt.sh will be generated thatcan be executed at a later time when HP SIM is running. This script will remove the VSE ManagementSoftware tools, toolboxes, actions, and online help from HP SIM.

-b --backup

Back up the VSE Management Software database, including gWLM and Capacity Advisor data, toprotect against loss of data. The VSE Management Software must be initialized before you can performa backup. Refer to the earlier description of the --initconfig option for information about initializingthe VSE Management Software.The backup is created in the directory specified by the -d or --dir option. This directory must beinitially empty or must not yet exist.The backup created by this command only contains the VSE Management Software data. HP recommendsthat you also create a backup of the HP SIM database at the same time, so that both databases can berestored together. Refer to the HP SIM manuals or online help for information about backing up the HPSIM database.

NOTE:If you are using gWLM, undeploy all Shared Resource Domains (SRDs) before performing a backup, ifpossible. To ensure that the latest gWLM data is included in the backup, issue the following commandbefore performing the backup:

gwlm history --flush

-s --restore

Restore the VSE Management Software database from the backup in the directory named by the -d or--dir option. The VSE Management Software must be initialized before you can perform a restore.Refer to the earlier description of the --initconfig option for information about initializing the VSEManagement Software.HP recommends that you also restore the HP SIM database at the same time. Both databases should bebacked up and restored together. Refer to the HP SIM manuals or online help for information aboutrestoring the HP SIM database.

NOTE:If you are using gWLM, undeploy all Shared Resource Domains (SRDs) after restoring the database frombackup, then redeploy them.

NOTE:If the CMS or managed systems have been modified between the backup and the restore (for example,changing hostnames or adding or removing processors), gWLM may not function as expected after therestore.

NOTE:You cannot restore a backup that was created with a previous version of the VSE Management Software.The structure of the VSE Management Software version A.02.00.00 database is incompatible withversion A.02.50.00. If you have not yet installed version A.02.50.00 software and you intend to restorefrom a version A.02.00.00 backup, perform the restore first. Then install and initialize the new software.The initialization process will upgrade the already-restored database to the new format.

31

If you have already installed version A.02.50.00 software and you need to restore from a versionA.02.00.00 backup, follow these steps:1. Uninstall the VSE Management Software. For uninstallation instructions, refer to the VSE Management

Software Installation and Update Guide.2. Reinstall version A.02.00.00 according to the installation instructions published with that release.3. Restore your VSE Management Software database from the version A.02.00.00 backup.4. Install the VSE Management Software version A.02.50.00. For installation instructions, refer to the

VSE Management Software Installation and Update Guide.5. Initialize the software as described in the earlier description of the --initconfig option. This

will upgrade the restored database to the new format.

Removing and Reinstalling VSEIf the VSEMgmt product is removed and reinstalled, collection of Capacity Advisor data can miss some dataon the CMS. To avoid this, back up the VSE Management Software database before removing VSE, andrestore 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.

EXAMPLESPerform initial configuration of the VSE Management Software, perform a backup of the ManagementSoftware database if a previous version exists, and upgrade the database, including upgrades from gWLMversion 1.x if necessary:vseinitconfig -a

Perform initial configuration of the VSE Management Software, removing any existing VSE ManagementSoftware database without backing it up:vseinitconfig -a -F

Same example, using long form of options:vseinitconfig --initconfig --clobber

Back up the VSE Management Software database to the directory /var/backups/2006-04-01:vseinitconfig -b -d /var/backups/2006-04-01

Same example, using long form of options:vseinitconfig --backup --dir=/var/backups/2006-04-01

AUTHORSvseinitconfig was developed by Hewlett-Packard Company.

FILES/var/opt/vse/logs/vseinitconfig.log

Errors and exceptions reported by vseinitconfig are logged here.

SEE ALSOgwlmcmsd(1M), gwlmsslconfig(1M), mxinitconfig(1M), mxtool(1M), mxtoolbox(1M), mxuser(1M), VSEManagement Software Quick Start Guide, VSE Management Software Installation and Update Guide

32

A Uninstalling The VSE Management SoftwareUse the following procedure to remove the VSE Management Software from the CMS.1. Use gWLM to undeploy all deployed SRDs.2. Delete all monitored workloads.3. Stop the gWLM daemon running on the CMS by executing the following command:

# /opt/gwlm/bin/gwlmcmsd --stop

4. Stop the gWLM agent daemon if it is running on the CMS by executing the following command:# /opt/gwlm/bin/gwlmagent --stop

5. (Optional) Remove any VSE License To Use (LTU) bundles installed on the CMS, for example, to removethe VSE Suite for HP-UX 11i, execute the following command:# /usr/sbin/swremove T2786AC

6. Remove the VSE Management Software by executing the following command:# /usr/sbin/swremove VSEMgmt

7. Remove the gWLM agent by executing the following command:# /usr/sbin/swremove T2743AA

33

34

Index

Aagent, 22

installation, 23ssh requirement, 14

CCapacity Advisor

Java requirements, 13ssh requirement, 14WBEM requirement, 14

Central Management Server (see CMS)CMS

as managed system, 13requirements, 13

comments to HP, 9

Ddiscovery (see SIM, discovery)

FFair-Share Scheduler (see FSS group)feedback to HP, 9FSS group, 23

GGlobal Workload Manager (see gWLM)gWLM

agent, 24agent installation, 23Java requirements, 13managed system requirements, 15

HHP Integrity Essentials Capacity Advisor (see Capacity

Advisor)HP Integrity Essentials Global Workload Manager (see

gWLM)HP Integrity Essentials Virtualization Manager (see

Virtualization Manager)HP Systems Insight Manager (see SIM)HP-UX, 14

patch, 13, 17required patches, 13–14

Iinstallation

HP-UX CMS, 20managed systems, 23

JJava, 13

LLDAP

recommended version, 14

Linux, 13–14

Mmanaged system

installation, 23Microsoft Windows, 13–14mxinitconfig, 21

NNIS, 17

OOpenSSH (see ssh)operating systems

CMS, 13managed systems, 14

Pping sweep, 22processor set (see pset)provider (see agent)pset, 23

Rrelease notes, 17requirements, 13root, 17

Ssecurity, 17service and support, 9Shared Resource Domain (see SRD)SIM, 13–14, 17

discovery, 21–22documentation, 7First Time Wizard, 21installation, 17, 20launching, 21, 23

SNMP, 21–22SRD

undeploy before upgrade, 20ssh, 14, 22–23swinstall, 20Systems Insight Manager (see SIM)

Ttypographic conventions, 7

Uuser authorization, 22

Vvirtual machine, 22virtual partition

provider, 15Virtual Server Environment (see VSE)

35

Virtualization Manager, 22ssh requirement, 14WBEM requirement, 14

VM Host, 22VM Provider

required version, 14vPar provider

required version, 15vPars (see virtual partition)VSE

documentation, 7requirements, 13

VSE agent software (see agent)vseinitconfig, 21

WWBEM, 17, 21–22

required version, 14WBEM provider (see agent)

36 Index