VSE Management Software Installation and Update Guide

HP Part Number: T2786-90030 Published: 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, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

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

1 Introduction.............................................................................................11 2 System Requirements.................................................................................13

Operating Systems Supported on the CMS...............................................................................................13 Additional Software Requirements on the CMS.........................................................................................13 Operating Systems Supported on Managed Systems..................................................................................14 Additional Software Requirements on Managed Systems............................................................................14 Additional Requirements for Using gWLM on Managed Systems.................................................................15 Managed System Compartment Software............................................................................................16 Additional requirements in the release notes.............................................................................................16

3 Installation...............................................................................................17
Preparing For Installation.......................................................................................................................17 Pre-Installation Steps for Linux Managed Systems..................................................................................17 Pre-Installation Steps for Windows Managed Systems...........................................................................18 Before Upgrading From a Previous Version...............................................................................................19 Installing the Software on the CMS..........................................................................................................20 Launching HP SIM.................................................................................................................................21 Installing VSE Agent Software on Managed Systems..................................................................................23 After Upgrading From a Previous Version.................................................................................................24

4 VSE Management Software Configuration...................................................27 Command Reference....................................................................................29

vseinitconfig(1M)..................................................................................................................................30

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

Table of Contents

List of Tables
1 2 3 4 5 2-1 2-2 2-3 2-4 2-5 2-6 Manpages Installed with VSE Management Software on the CMS...............................................................8 Manpages Installed with VSE Agent Software on Managed Systems............................................................8 Manpage Installed on Cell-Based Complexes............................................................................................8 Manpages Installed on Systems Running HP Integrity Virtual Machines.........................................................8 Selected HP SIM Manpages...................................................................................................................9 Operating Systems Supported on the CMS.........................................................................................13 Additional Software Requirements on the CMS...................................................................................13 Operating Systems Supported on Managed Systems............................................................................14 Additional Software Requirements on Managed Systems......................................................................14 Additional Requirements for Using gWLM on Managed Systems...........................................................15 Managed System Compartment Software...........................................................................................16

About This Document

This 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 Management Software 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 used along with the VSE Management Software Quick Start Guide, which provides an overview of the HP Virtual Server Environment (VSE), the VSE Management Software, and software configuration procedures.

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

Typographic Conventions
This document uses the following typographic conventions.

Book Title Linked Title http://www.hp.com Command user input computer output Enter

term variable value

find(1)

Title of a book or other document. Title that is a hyperlink to a book or other document. A Web site address that is a hyperlink to the site. Command name or qualified command phrase. Commands and other text that you type. Text displayed by the computer. 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 labeled Ctrl while pressing the A key. Defined use of an important word or phrase. The name of an environment variable, for example PATH or errno. A value that you may replace in a command or function, or information in a display that represents several possible values. HP-UX manpage. In this example, find is the manpage name and 1 is the manpage section.

Related Information
A 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 Information CD. 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 Notes

The 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 relevant to the VSE Management Software.
Intended Audience 7

Table 1 Manpages Installed with VSE Management Software on the CMS

capcollect(1M) capovpaextract(1M) capprofile(1M) capprofile(4) gwlm(1M) gwlm(5) gwlmcmsd(1M) gwlmagent(1M) gwlmsslconfig(1M) gwlmimportkey(1M) gwlmexportkey(1M) gwlmplace(1M) gwlmreport(1M) gwlmsend(1M) gwlmxml(4) vseinitconfig(1M) vselicense(1M)
Collect Capacity Advisor data from systems Export OpenView Performance Agent (OVPA) system data from managed systems and import into Capacity Advisor Import, export, display, invalidate and remove Capacity Advisor data for workloads or systems Format of Capacity Advisor import and export files Global Workload Manager Overview of Global Workload Manager Global Workload Manager (gWLM) daemons

Secure network communications for Global Workload Manager

Place a process in a gWLM workload Produce advanced textual summary reports for workload resource utilization Send metric data to gWLM for use in a custom policy Overview of XML file structure for Global Workload Manager Configure or unconfigure the VSE Management Software Install or remove licenses for VSE Management Software products

Table 2 Manpages Installed with VSE Agent Software on Managed Systems

utild(1M) utild(8)
UPService.pdf (HP-UX) System utilization data collection daemon (Linux) System utilization data collection daemon (Windows) Utilization Provider Service (document installed in \Program Files\Hewlett-Packard\UtilProvider\doc)

Table 3 Manpage Installed on Cell-Based Complexes

parmgr(1M)
Start Partition Manager

Table 4 Manpages Installed on Systems Running HP Integrity Virtual Machines

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

About This Document

Table 5 Selected HP SIM Manpages

mxauth(1M) mxinitconfig(1M) mxnode(1M) mxuser(1M)
Add, remove, or list authorizations in HP SIM Perform initial configuration of the CMS Add, modify, identify, remove, or list nodes in HP SIM Add, modify, remove, or list users in HP SIM

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 other documents.) 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 History
Manufacturing Part Number Supported Operating Systems T2786-90030 Edition Publication Date September 2006 CMS: 1.0 HP-UX 11i v1 December 2004 or later HP-UX 11i v2 September 2004 or later Managed systems: HP-UX 11i v1, HP-UX 11i v2 Microsoft Windows Server 2003 Enterprise Edition Microsoft Windows Server 2003 Datacenter Edition Red Hat Enterprise Linux 4 update 2 or later for Intel Itanium SUSE Linux Enterprise Server 9 Service Pack 2 or later for Intel Itanium

HP Encourages Your Comments

Your comments and suggestions regarding product features will help us develop future versions of the Virtual Server Environment Management Software. Use the following e-mail address to send feedback directly to the 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, contact your HP Support Representative, your HP Services Representative, or your authorized HP reseller. For more information 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

10

1 Introduction
This document describes the installation of the VSE (Virtual Server Environment) Management Software version A.02.50.00. This includes system requirements, installation of the software on the Central Management Server (CMS), upgrading from previous versions, installation of agent software and WBEM providers on managed 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 Server Environment (VSE) and the VSE Management Software, key VSE concepts and terminology, and post-installation software configuration procedures.

11

12

2 System Requirements
The VSE Management Software runs under HP Systems Insight Manager version 5.00.01.00 or later. HP recommends 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 User Guide (http://docs.hp.com/en/5991-4498/). Refer to that document for the complete requirements for the Central Management Server (CMS) and managed systems. In particular, note that you may need to install HP-UX patches before you install HP SIM. IMPORTANT: If you are currently using an earlier version of HP SIM, please refer to Before Upgrading From 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 Management Software are detailed in the following sections.

Operating Systems Supported on the CMS

Table 2-1 Operating Systems Supported on the CMS
HP-UX 11i v1 HP-UX 11i v2 December 2004 or later. Patch PHSS_34338 must be installed. September 2004 or later. Patch PHSS_34339 must be installed.

Systems running Linux or Microsoft Windows are not currently supported.

Additional Software Requirements on the CMS

Table 2-2 Additional Software Requirements on the CMS
Java The Java Run-time Environment (JRE 1.4.2) is required by Capacity Advisor and gWLM. If you want 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 optional selectable software. Installation of JOOB will require a reboot. Disk Space for gWLM To use gWLM you will need 1 GB of available disk space in /var/opt/. If you intend to keep historical data, HP recommends allowing 4 GB for every 100 workloads managed by gWLM. If you are not interested in historical data, you can trim the historical database by using the command: # gwlm history --truncate

gWLM Data Access from OpenView Performance Agent

To allow OpenView Performance Agent access to the gWLM data the MeasureWare.PERFDSI fileset (version C.03.85 or later) must be installed. The following command lists the file if it is installed on 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 version C.03.85.00 or later.

CMS as managed system

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

Operating Systems Supported on the CMS

13

Operating Systems Supported on Managed Systems

Table 2-3 Operating Systems Supported on Managed Systems
HP-UX 11i v1 HP-UX 11i v2 (HP-UX 11i v2 Update 2 if the system will be managed with gWLM) Microsoft Windows Memory patch PHSS_33349 must be installed in order to use Virtualization Manager and Capacity Advisor.

Microsoft Windows Server 2003 Enterprise Edition Microsoft Windows Server 2003 Datacenter Edition NOTE: Systems running Microsoft Windows cannot be managed by this release of gWLM.

Linux

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

Additional Software Requirements on Managed Systems

Table 2-4 Additional Software Requirements on Managed Systems
WBEM WBEM is required on managed systems to support the visualization and configuration features of Virtualization 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 be installed. Earlier versions of WBEM may generate cimserver errors, including timeouts in Virtualization Manager and VM Manager, and messages such as CIM failure and Connection Refused. The latest 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 Foundation Pack for Linux Management CD. Refer to Pre-Installation Steps for Linux Managed Systems (page 17) for details. LDAP 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 reading required WBEM data. The latest version of LDAP-UX Integration for HP-UX can be obtained from HP Software Depot at http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=J4269AA. OpenSSH 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 by default. It must be configured for use by HP SIM. This is covered in Installing VSE Agent Software on Managed Systems (page 23). On Windows managed systems OpenSSH is not installed by default, but it can be installed from the HP Smart Setup installation media (version 4.5 or later). You will also have to manually configure OpenSSH 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 Linux distribution 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 paper Secure Shell (SSH) in HP SIM 5.0, available from the Information Library link at http://www.hp.com/ go/hpsim. WBEM Providers and Agent Software The WBEM providers and other agents required by the VSE Management Software will be installed during the installation process described in this document. HP recommends that you follow this process to install the latest versions of the agent software. The following entries in this table describe specific issues with earlier provider versions. VM Provider version 1.20 or later must be installed on VM Host systems. Earlier versions of the VM Provider can be used on guest Virtual Machines.

VM Provider

14

System Requirements

vPar Provider

The vPar provider that was included with the March 2006 release of HP-UX 11i v2 (B.11.23) does not work properly. With the March 2006 version installed, HP SIM and the VSE Management software do not discover and display virtual partitions correctly. The vPar provider that is included with the VSE Management software fixes this problem. However, it presents the same version number as the March 2006 version. The same problem exists with the HP-UX 11i v1 (B.11.11) version of the vPar provider when used with WBEM version A.02.00.09. You can fix this problem by executing the following command on each system where the vPar provider 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 vPar provider and install the version delivered with the VSE Management software (or forcibly reinstall the VSE Management Software version).

Additional Requirements for Using gWLM on Managed Systems

Table 2-5 Additional Requirements for Using gWLM on Managed Systems
Java 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 or later. IMPORTANT: Installing gWLM will automatically overwrite existing Java 1.4.x installations with Java 1.4.2. There are a number of security fixes and other improvements in version 1.4.2 that gWLM makes use of. Do not use gWLM with Java 1.4.0 or Java 1.4.1. Patch PHKL_35174 Linux Managed Systems On rx8640 or rx7640 systems running HP-UX 11i v2, patch PHKL_35174 must be installed in order to manage nPartitions and virtual partitions. 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 gWLM agent software will fail. To determine if these libraries have been installed, execute the following command to display the installed version: $ rpm -qa | grep compat If the libraries are not installed, install the corresponding package from your Linux operating system CD. nPartition Provider Install this software on HP-UX managed systems even if the system does not use nPartitions. Installing the VSE agent software from the CMS using the procedure described in Installing VSE Agent Software on Managed Systems (page 23) will ensure that all of the required providers, including the 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. Supported processors Memory Disk space HP 9000 (PA-RISC 2.0) or HP Integrity (IA-64) 2 GB minimum 25 MB available in /opt/

Additional Requirements for Using gWLM on Managed Systems

15

Managed System Compartment Software

Table 2-6 Managed System Compartment Software lists the supported versions of the products that provide the compartments that gWLM manages. A managed system must have at least one of these products installed. Table 2-6 Managed System Compartment Software
nPartitions Virtual Partitions Instant Capacity v7 or later is required to simulate CPU movement. vPars version A.03.01.05 or later. The following tunable kernel parameters must be configured as shown: max_thread_proc at least 768 nkthread max_thread_proc + the number of threads needed by all the other processes on the system Virtual machines HP Integrity Virtual Machines version A.02.00 or later. For HP-UX 11i v2 Update 2, install patches PHKL_32518, PHKL_33052, PHKL_33604, and PHKL_33605. The following tunable kernel parameters must be configured as shown: max_thread_proc at least 768 nkthread max_thread_proc + the number of threads needed by all the other processes on the system Processor Sets (psets) 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. Fair-Share Scheduler (FSS) The PRM-Sw-Krn.PRM-KRN fileset must be installed. The following command lists the fileset if it is installed 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 is available 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 deploy an 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 other processes on the system

Additional requirements in the release notes

Refer to the following documents for additional requirements and installation notes:

VSE Management Software Release Notes HP Integrity Virtual Machines Release Notes

These documents are available on the HP Instant Information CD. The latest versions can also be downloaded from http://docs.hp.com/en/hplex.html.

16

System Requirements

3 Installation
Use 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 download from Software Depot at http://h20293.www2.hp.com/portal/swdepot/ displayProductInfo.do?productNumber=vse. The software includes a 90-day trial license. For more information about VSE Management Software licenses, refer to the VSE Management Software Quick Start Guide. 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 completing pre-installation steps for Linux and Microsoft Windows managed systems. See Preparing For Installation. If you are upgrading from a previous version of the VSE Management Software, perform the upgrade pre-installation steps as described in Before Upgrading From a Previous Version (page 19). Install HP SIM and the VSE Management Software on the CMS. See Installing the Software on the CMS. Launch HP SIM and run the First Time Wizard and the Discovery process. See Launching HP SIM (page 21). Install the WBEM providers and other agent software on your managed systems. See Installing VSE Agent Software on Managed Systems (page 23). If you upgraded from a previous version of the VSE Management Software, perform the upgrade post-installation steps as described in After Upgrading From a Previous Version (page 24). Configure the VSE Management Software for your environment by defining user authorizations and activating licenses. See VSE Management Software Configuration (page 27).

2.

3. 4. 5. 6. 7. 8.

Preparing For Installation

Refer to the HP Systems Insight Manager 5.0 Installation and User Guide (Installation Overview and Requirements 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 requirements described in System Requirements (page 13). Check the VSE Management Software Release Notes for any updates to the requirements or installation instructions. This document is available on the HP Instant Information CD. The latest version can also be downloaded from http://docs.hp.com/en/hplex.html. Create a common WBEM user account on the CMS and managed systems. The VSE Management Software uses WBEM connections to obtain information from the managed systems. You must establish common WBEM credentials on the CMS and on the managed systems to allow authenticated access to WBEM data. HP recommends that you assign a user name that is the same on all your servers and is reserved for use by WBEM. For security reasons, this user name should not have root privileges and should not have a login shell associated with it. Use NIS, LDAP, or other techniques to maintain a single password for this user name across all of your systems. You must enter this user name and password during initial setup of HP SIM. Refer to Launching HP SIM (page 21). For more information about WBEM security configuration in HP SIM, refer to the HP white paper Understanding HP Systems Insight Manager security, available from the Information Library link at http://www.hp.com/ go/hpsim.

Pre-Installation Steps for Linux Managed Systems

On managed systems running Red Hat Enterprise Linux, disable SELinux to avoid conflicts with the WBEM providers and agent software. In order for Linux managed systems to be correctly discovered by HP SIM, you must install WBEM and required WBEM providers from the HP Integrity Essentials Foundation Pack for Linux Management CD. You can download the contents of this CD in tar format using the following procedure: 1. 2. Visit the Web site http://www.hp.com/go/integritylinux. 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, integrity rx7620 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 Download drivers 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 to configure this file. In this example, your designated WBEM user name is assumed to be wbemuser. a. Look for the following line in this file: -: ALL EXCEPT pegasus:wbemNetwork b. Change this line to either of the following options: # Allow access only from user 'wbemuser': -: ALL EXCEPT wbemuser pegasus:wbemNetwork # Allow access by all users: +: ALL EXCEPT :wbemNetwork c. If tog-pegasus is not running, start it by executing the following command: # /etc/init.d/tog-pegasus start

OpenSSH on Linux managed systems must be configured for use by HP SIM. Normally you can use the same procedure that is used to configure OpenSSH for HP SIM on HP-UX managed systems. This is covered in Installing VSE Agent Software on Managed Systems (page 23). However, if you are using SuSE Linux Enterprise 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 instead of password authentication. Password authentication is required in order for the mxagentconfig to configure OpenSSH for use by HP SIM. On managed systems running SuSE Linux Enterprise Server 9, change to password authentication using the following procedure: 1. Configure the following lines in /etc/ssh/sshd_config on the managed system: PasswordAuthentication yes #UsePAM yes 2. 3. Retrieve the process id (pid) of the running sshd from the file /var/run/sshd.pid. Restart sshd by executing the following command: # kill -SIGHUP pid

Pre-Installation Steps for Windows Managed Systems

On Windows managed systems OpenSSH is not installed by default, but it can be installed from the HP Smart Setup installation media (version 4.5 or later). Use the following procedure to install OpenSSH and configure 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 that will run the OpenSSH service. The Administrator account is typically used for this. NOTE: During installation, OpenSSH automatically imports your local user accounts into its password file. If additional accounts are added later, you must re-install OpenSSH or use the sshuser command to import the new user account information into OpenSSH. 2. 3. Reboot the Windows managed system to enable SSH communication. Configure OpenSSH for use with HP SIM by executing the following command on the CMS: # mxagentconfig -a -n node-hostname -u Administrator -p Administrator-password where node-hostname is the name of the system as it is known by HP SIM. If the system administrator user account on your managed system is not Administrator, substitute your administrator user name in the command above. You can use multiple -n options in order to perform this operation on more than one managed system. NOTE: If you are using HP SIM version 5.00.02.00 or later, this step can be performed within HP SIM by selecting the managed systems to configure, then choosing Configure Configure or Repair Agents... from the HP SIM menu bar. At the Configure or Repair Settings page, select Configure secure shell (SSH) access. For earlier versions of HP SIM, you must manually execute the mxagentconfig command, as described above. 4. If you are using Partition Manager to manage Windows systems, you must also create a user account named root on those Windows systems. Partition Manager uses this user name for remote execution of nPartition commands through OpenSSH. Add this user to the Administrators group in Windows, then add this user to OpenSSH using the sshuser command. Execute the following command on the CMS to configure remote connections from the CMS using the root 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 the Administrator or root accounts. Partition Manager will use the root account for remote command execution.

Before Upgrading From a Previous Version

This section describes the steps you must perform before upgrading an existing installation of VSE Management Software version A.02.00.00 to version A.02.50.00. This process will convert an existing VSE Management Software database, including historical profile data, to the new version A.02.50.00 database format. Any historical profile data that you want to migrate to the new database format must be installed in the currently running 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 and reinstalling the previous version. In case you find it necessary to revert to the previous version, you must make a backup of your VSE Management Software database before upgrading the software. You can use this 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 Management Software version A.02.50.00. In this case, the steps below that concern existing versions of other VSE Management 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 stop using the existing version, including the command-line interface. It is okay to continue running the gWLM daemons gwlmcmsd and gwlmagent) and the WBEM service and provider daemons. Stop using the version of Capacity Advisor that is already installed, including the command-line interface. If necessary, use the following substeps to disable each automatically scheduled Capacity Advisor data collection task: 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. Log out from HP Systems Insight Manager. (Optional) Use the capcollect command to collect the latest Capacity Advisor data into the VSE Management Software database. Refer to capcollect(1M) for details. 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 revert to the previous version of the software. With this backup, you can restore your current configuration after reverting to the previous version of the software. You will not be able to restore this backup when version A.02.50.00 is installed. The structure of the VSE Management Software version A.02.00.00 database is incompatible with version A.02.50.00. For detailed information about backing up and restoring the VSE Management Software database and reverting to a backup from a previous version of the software, refer to vseinitconfig(1M). This manpage is included below in the Command Reference (page 29). 7. 8. 9. Make a backup of the HP SIM database, so that both databases can be restored together. Refer to the HP SIM documentation for information about backing up the HP SIM database. If you are upgrading to a new version of HP SIM, follow any upgrade preparation instructions provided with the new version of HP SIM. In particular, note that you may need to install additional patches. Execute the following command on the CMS to shut down the CMS server daemons: # /opt/mx/bin/mxstop

2.

3. 4. 5.

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

Installing the Software on the CMS

Use 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 version A.02.50.00. If you are currently running HP SIM version 5.00.01.00 and you choose not to upgrade HP SIM, use the following command instead:
20 Installation

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

NOTE: 2.

The system reboots after the installation.

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 several minutes 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 no errors.

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 there are no errors.

4.

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

Launching HP SIM
After 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 is configured to block pop-ups, then the First Time Wizard will not be automatically displayed after you launch HP 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 menu bar. NOTE: You can view help for this wizard (or any other window in HP SIM) by clicking the the upper right corner of the window. button in

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

Introduction screen:
Click Next to continue.

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

3.

SNMP screen:
Configure the SNMP community name that is appropriate for your organization, or use the default value provided. 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 can be managed from the CMS by HP SIM. There are two discovery modes: automatic and manual. If you want discovery to be scheduled on an automatic basis, select Schedule and specify how often discovery is run. Whether or not you configure automatically scheduled discovery, you should run the discovery process manually as soon as you are finished with the First Time Wizard. Discovery can be run manually by choosing 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 systems by their response to a network ping), or you can specify individual systems by name or IP address. HP SIM uses WBEM, SNMP, SSH and SMH protocols for system identification. For example, HP SIM attempts to contact the WBEM nPartition, Virtual Partition, and Virtual Machine providers on a given system to determine if the system is any of these types. HP SIM populates its system database with this information and creates relationship information such as the parent/child association between a VM Host and its virtual machines. Virtualization Manager uses both the system and relationship information when displaying VSE resources. However, at this point you have not installed the VSE agent software on the managed nodes, so little information will be available until you have finished that step. Refer to Installing VSE Agent Software on 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 of user-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 will have to configure user authorizations to allow access to the VSE Management Software tools. This is discussed in the VSE Management Software Quick Start Guide. Click Next when you are ready to continue.

6.

E-mail screen:
Skip this step if you do not want e-mail notification of HP SIM events from the CMS. Otherwise, specify the SMTP host and authentication (if required) to be used to send e-mail. On an HP-UX CMS, you can usually 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 alerts to 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 your earlier 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 agent software installation in the next section. Do this even if you configured automatically scheduled discovery in the First Time Wizard. Choose Options Discovery... from the HP SIM menu bar, then click Run Now.

22

Installation

Installing VSE Agent Software on Managed Systems

The VSE Management Software relies on WBEM providers and other agent software in order to obtain data from 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 do not 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 each managed 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, as described 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 described in 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. 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 Configure or Repair Agents... from the HP SIM menu bar. At the Configure or Repair Settings page, select Configure secure shell (SSH) access. This step can also be done manually using the mxagentconfig command. Refer to mxagentconfig(1M) for more information. This procedure will also configure OpenSSH on Linux managed if you have first performed the pre-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 or later. Otherwise, you must manually configure OpenSSH as decribed in Pre-Installation Steps for Windows Managed Systems (page 18). For detailed information about configuring SSH for use with HP SIM, refer to the HP white paper Secure Shell (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 VSE Agents Install Unix-Linux VSE Agents... from the HP SIM menu bar. Click Run Now to start the 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 gWLM agent, all agents within an SRD must be upgraded at the same time. You cannot combine A.01.x and A.02.x agents in a single SRD. NOTE: If you are upgrading the version of gWLM on systems where gWLM is already managing psets or FSS groups, any processes that were placed using the gwlmplace command are moved to the default pset or default FSS group. You can avoid this behavior by placing applications in workloads when you define the workloads. 4. Select your Windows managed systems and choose Configure Configure VSE Agents Install Windows VSE Agents... from the HP SIM menu bar. Click Run Now to start the installation. Review the output for error messages before continuing.

2.

Installing VSE Agent Software on Managed Systems

23

NOTE: 5.

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

Select the systems that you want to manage with gWLM, and choose Configure Configure VSE Agents Start gWLM Agent... from the HP SIM menu bar to start the gWLM agent on the selected systems. NOTE: You can configure the gWLM agent to start automatically whenever the system is booted by executing 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 been installed. This will cause HP SIM to update its information about these systems. Select the affected systems and 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 managed systems from the /var/opt/vse/depot/vseagent.depot file. This file was installed on the CMS with the VSEMgmt bundle, as described in Installing the Software on the CMS (page 20). It contains all of the VSE Management Software agents. The bundles in this depot can be copied to a Software Distributor depot server, 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 use to install individual agents from this depot. If you are using a Software Distributor depot server, replace the source 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 managed systems, you can individually install the /var/opt/vse/depot/*.msi files by double-clicking the files that you want to install.

After Upgrading From a Previous Version

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

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 try the command again. Verify gWLM Communication If you are using gWLM, execute the following command on the CMS to verify that the CMS is configured properly and can communicate with installed agents: # /opt/gwlm/bin/gwlm list If the output of this command lists various policies, the CMS is configured properly. Othewise, you will get error messages. Wait a few seconds and try the command again. If you still get errors, take the actions suggested by the error messages. Rediscover Partition-Based SRDs If 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 Capacity and you have upgraded the gWLM agents in the partitions from gWLM A.01.x to gWLM A.02.50.00, you will not be able to add other partitions in the same complex to the SRD. Use the following procedure on the CMS 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. 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 desired value (Managed or Advisory): mode="Managed"

2.

Ensure that the interval attribute for the sharedResourceDomain element is set to the desired value: interval="x"

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

Ensure that the workloadReference entries in the compartment definitions are correct, and adjust the names in the workload definitions themselves. For example, you 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 place of the original SRD. Verify Capacity Advisor data Migration If you are using Capacity Advisor, use the command capprofile -lt to verify that previously collected historical data has been migrated to the new VSE Management Software database. This command should list the workload profiles and the time range of the data stored in the database. Refer to capprofile(1M) for details. Restore Scheduled Capacity Advisor Tasks If you are using Capacity Advisor, follow the steps below to restore each of your automatically scheduled Capacity Advisor data collection tasks: 1. 2. 3. 4. 5. 6. 7. Choose Tasks & Logs View All Scheduled Tasks? from the Capacity Advisor menu bar. Select the task from the list Collect Capacity Advisor Data ?. Click Edit. Click Schedule. Uncheck the Disable this task checkbox. Click Done. Verify that the task you just edited is in the list and now shows Periodic in the Schedule column, along with the date of the next collection.

26

Installation

4 VSE Management Software Configuration

After installation, you need to perform two additional steps in order to properly configure the VSE Management Software for your environment. These steps are described in detail in the VSE Management Software Quick Start Guide. This document is available on the HP Instant Information CD. The latest version can also be downloaded from http://docs.hp.com/en/hplex.html. 1. 2. Configure user authorizations for access to the VSE Management Software tools. Refer to the chapter named Configuring User Authorizations for details. 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)
NAME
vseinitconfig -- Configure or unconfigure the VSE Management Software

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

DESCRIPTION
The 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 can also be used to remove the existing configuration and to back up or restore the VSE Management Software database. With no arguments, the initial configuration function is performed. The HP Virtual Server Environment (VSE) is an integrated server offering that provides a flexible computing environment, helping you to maximize use of your server resources. HP VSE Management Software provides the visualization, configuration, workload policy, and capacity planning tools to optimize the system resources in your VSE. The vseinitconfig command is installed on the Central Management Server (CMS) with the VSE Management Software. This command performs four different functions on the CMS, corresponding to the four 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 Global Workload Manager (gWLM) and HP Integrity Essentials Capacity Advisor, as well as initialization of the VSE Management Software database. Removal of the VSE Management Software menu items and actions from HP SIM and clearing of the VSE Management Software database. This option is automatically invoked during removal of the VSE Management Software. Safe backup of the VSE Management Software database to protect against loss of data. Safe restore of the VSE Management Software database from a previous backup.

2.

3. 4.

Options
The vseinitconfig command recognizes the following options. Each option can be expressed in a long or short form, in order to provide compatibility with corresponding options in the related commands mxinitconfig(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 also the default function performed if no option is specified). This action requires that HP SIM has been configured with the mxinitconfig command and HP SIM must be running. This command registers the VSE Management Software tools, toolboxes, and actions with HP SIM, and also initializes the VSE Management Software database. The optional --clobber or -F option will cause an existing VSE Management Software database to be removed without being backed up first. Otherwise, if the database already exists it will be upgraded from the previous version of the VSE Management Software. NOTE: Before upgrading from a previous version of the VSE Management Software, refer to the VSE Management Software Installation and Update Guide, and to the description of the --restore option below for important 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 backup should be performed before executing this step, or you will lose all of your VSE Management Software data, 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 that can be executed at a later time when HP SIM is running. This script will remove the VSE Management Software tools, toolboxes, actions, and online help from HP SIM. -b --backup Back up the VSE Management Software database, including gWLM and Capacity Advisor data, to protect against loss of data. The VSE Management Software must be initialized before you can perform a backup. Refer to the earlier description of the --initconfig option for information about initializing the VSE Management Software. The backup is created in the directory specified by the -d or --dir option. This directory must be initially empty or must not yet exist. The backup created by this command only contains the VSE Management Software data. HP recommends that you also create a backup of the HP SIM database at the same time, so that both databases can be restored together. Refer to the HP SIM manuals or online help for information about backing up the HP SIM database. NOTE: If you are using gWLM, undeploy all Shared Resource Domains (SRDs) before performing a backup, if possible. To ensure that the latest gWLM data is included in the backup, issue the following command before 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 VSE Management Software. HP recommends that you also restore the HP SIM database at the same time. Both databases should be backed up and restored together. Refer to the HP SIM manuals or online help for information about restoring the HP SIM database. NOTE: If you are using gWLM, undeploy all Shared Resource Domains (SRDs) after restoring the database from backup, 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 the restore. 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 with version A.02.50.00. If you have not yet installed version A.02.50.00 software and you intend to restore from 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 version A.02.00.00 backup, follow these steps: 1. 2. 3. 4. 5. Uninstall the VSE Management Software. For uninstallation instructions, refer to the VSE Management Software Installation and Update Guide. Reinstall version A.02.00.00 according to the installation instructions published with that release. Restore your VSE Management Software database from the version A.02.00.00 backup. Install the VSE Management Software version A.02.50.00. For installation instructions, refer to the VSE Management Software Installation and Update Guide. 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 VSE

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

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

EXAMPLES
Perform initial configuration of the VSE Management Software, perform a backup of the Management Software database if a previous version exists, and upgrade the database, including upgrades from gWLM version 1.x if necessary: vseinitconfig -a Perform initial configuration of the VSE Management Software, removing any existing VSE Management Software 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

AUTHORS
vseinitconfig was developed by Hewlett-Packard Company.

FILES
/var/opt/vse/logs/vseinitconfig.log Errors and exceptions reported by vseinitconfig are logged here.

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

A Uninstalling The VSE Management Software

Use 1. 2. 3. the following procedure to remove the VSE Management Software from the CMS. Use gWLM to undeploy all deployed SRDs. Delete all monitored workloads. Stop the gWLM daemon running on the CMS by executing the following command: # /opt/gwlm/bin/gwlmcmsd --stop Stop the gWLM agent daemon if it is running on the CMS by executing the following command: # /opt/gwlm/bin/gwlmagent --stop

4.

5.

(Optional) Remove any VSE License To Use (LTU) bundles installed on the CMS, for example, to remove the VSE Suite for HP-UX 11i, execute the following command: # /usr/sbin/swremove T2786AC
Remove the VSE Management Software by executing the following command: # /usr/sbin/swremove VSEMgmt Remove the gWLM agent by executing the following command: # /usr/sbin/swremove T2743AA

6.

7.

33

34

Index
A
agent, 22 installation, 23 ssh requirement, 14 Linux, 1314

M
managed system installation, 23 Microsoft Windows, 1314 mxinitconfig, 21

C
Capacity Advisor Java requirements, 13 ssh requirement, 14 WBEM requirement, 14 Central Management Server (see CMS) CMS as managed system, 13 requirements, 13 comments to HP, 9

N
NIS, 17

O
OpenSSH (see ssh) operating systems CMS, 13 managed systems, 14

D
discovery (see SIM, discovery)

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

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

R
release notes, 17 requirements, 13 root, 17

G
Global Workload Manager (see gWLM) gWLM agent, 24 agent installation, 23 Java requirements, 13 managed system requirements, 15

S
security, 17 service and support, 9 Shared Resource Domain (see SRD) SIM, 1314, 17 discovery, 2122 documentation, 7 First Time Wizard, 21 installation, 17, 20 launching, 21, 23 SNMP, 2122 SRD undeploy before upgrade, 20 ssh, 14, 2223 swinstall, 20 Systems Insight Manager (see SIM)

H
HP 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, 17 required patches, 1314

I
installation HP-UX CMS, 20 managed systems, 23

T
typographic conventions, 7

U
user authorization, 22

J
Java, 13

V
virtual machine, 22 virtual partition provider, 15 Virtual Server Environment (see VSE)
35

L
LDAP recommended version, 14

Virtualization Manager, 22 ssh requirement, 14 WBEM requirement, 14 VM Host, 22 VM Provider required version, 14 vPar provider required version, 15 vPars (see virtual partition) VSE documentation, 7 requirements, 13 VSE agent software (see agent) vseinitconfig, 21

W
WBEM, 17, 2122 required version, 14 WBEM provider (see agent)

36

Index