Embed Size (px)
Citation preview
VSE Management Software Version 4.0Installation and Update Guide for HP-UX
HP Part Number: T8671-90011Published: May 2008
© Copyright 2006-2008 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. HPshall not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are OpenGroup UNIX 95 branded products.
UNIX is a registered trademark of The Open Group.
Java is a US trademark of Sun Microsystems, Inc.
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.........................................................................................................9Intended Audience.................................................................................................................................9New and Changed Information in This Edition.....................................................................................9Typographic Conventions......................................................................................................................9Related Information................................................................................................................................9
VSE Management Software Websites..............................................................................................10Related Product Websites................................................................................................................10Manpages.........................................................................................................................................10Books................................................................................................................................................13
Publishing History................................................................................................................................13HP Encourages Your Comments..........................................................................................................14
1 Introduction...................................................................................................................15
2 System Requirements....................................................................................................17HP Systems Insight Manager................................................................................................................17Maximum Configuration......................................................................................................................17Hardware Requirements for the HP-UX CMS.....................................................................................18HP-UX Operating Systems Supported on the CMS.............................................................................18HP SIM Database Requirements...........................................................................................................19Additional Software Requirements on the HP-UX CMS......................................................................20Operating Systems Supported on Managed Systems..........................................................................21Additional Software Requirements on Managed Systems...................................................................21
WBEM Providers and Agent Software............................................................................................21Other Software and Services............................................................................................................24
Managed System Compartment Software............................................................................................26Compatibility with HP-UX Bastille and Other Network Firewalls......................................................27
VSE Management Software Network Communication Protocols..................................................27Firewall Settings on the CMS..........................................................................................................27Bastille Settings on the CMS............................................................................................................27Firewall Settings on Managed Systems...........................................................................................28Bastille Settings on the Managed System........................................................................................28
Additional Requirements in the Release Notes....................................................................................29
3 Installation.....................................................................................................................31Prepare for Installation.........................................................................................................................31
Preinstallation Steps for Linux Managed Systems..........................................................................32Preinstallation Steps for Microsoft Windows Managed Systems...................................................33
Before Upgrading from a Previous Version.........................................................................................34Install the Software on the CMS...........................................................................................................36Start and Configure HP SIM.................................................................................................................38Install VSE Agent Software on Managed Systems...............................................................................40
Configure Secure Shell (OpenSSH).................................................................................................40Install HP-UX VSE Agents..............................................................................................................40Install Linux VSE Agents.................................................................................................................41Install Windows VSE Agents...........................................................................................................42Alternate Procedure for Manual Installation of Agent Software....................................................42
After Upgrading from a Previous Version...........................................................................................43
Table of Contents 3
Postinstallation Update of gWLM Agents............................................................................................45
4 Configure VSE Management Software......................................................................47
A Command Reference...................................................................................................49vseinitconfig(1M)..................................................................................................................................50
B Removing the VSE Management Software................................................................55
Index.................................................................................................................................57
4 Table of Contents
List of Tables1 Manpages Installed with VSE Management Software on the CMS..............................................102 Manpages Installed with VSE Agent Software on Managed Systems..........................................113 Manpage Installed on Cell-Based Complexes...............................................................................114 Manpages Installed on Systems Running HP Integrity Virtual Machines...................................115 Selected HP Systems Insight Manager Manpages........................................................................122-1 Maximum VSE Configuration.......................................................................................................172-2 HP-UX CMS Hardware Requirements..........................................................................................182-3 HP-UX Operating Systems Supported on the CMS......................................................................182-4 Additional Software Requirements on the HP-UX CMS..............................................................202-5 Operating Systems Supported on Managed Systems...................................................................212-6 WBEM Providers and Agent Software..........................................................................................222-7 Additional Software Required on Managed Systems...................................................................242-8 Managed System Compartment Software....................................................................................26
5
6
List of Procedures2-1 Configure CMS for Managed DMZ Under HP-UX Bastille..........................................................282-2 Configure Managed System for Managed DMZ Under HP-UX Bastille......................................293-1 Installation Overview....................................................................................................................313-2 Download and Install Linux Management Software....................................................................323-3 Configure SUSE Linux for Password Authentication...................................................................333-4 Install and Configure OpenSSH for Windows..............................................................................343-5 Prepare for VSE Management Software Upgrade........................................................................353-6 Install or Upgrade HP SIM and VSE Management Software.......................................................363-7 Install VSE Management Software Using Existing Installation of HP SIM..................................373-8 Start HP SIM and The First Time Wizard.....................................................................................383-9 Configure OpenSSH for HP Systems Insight Manager................................................................403-10 Install HP-UX Managed System Software from the CMS.............................................................403-11 Install Linux Managed System Software from the CMS...............................................................413-12 Install Windows Managed System Software from the CMS.........................................................423-13 Manual Installation of HP-UX Agents..........................................................................................423-14 Manual Installation of Integrity Linux Agents.............................................................................433-15 Manual Installation of Windows Agents......................................................................................433-16 Rediscover Partition-Based SRDs..................................................................................................443-17 Restore Scheduled Capacity Advisor Tasks..................................................................................453-18 Update gWLM Agents After Updating the CMS..........................................................................45B-1 Remove the VSE Management Software.......................................................................................55
7
8
About This DocumentThis document describes system requirements and installation procedures for the HP VirtualServer Environment (VSE) Management Software for HP-UX. System administrators can usethis guide to install the VSE Management Software on an HP-UX Central Management Server(CMS), or upgrade from a previous version of the software. Installation of agent software onmanaged systems is also covered. This document is intended to be used along with the VSEManagement Software Version 4.0 Getting Started Guide, which provides an overview of the HPVirtual Server Environment, the VSE Management Software, and software configurationprocedures.
This document does not cover installation on an HP ProLiant CMS running Microsoft®Windows®. For that information, see the HP Insight Control Management Quick Setup Poster.
Intended AudienceThis document is intended to be used by VSE system administrators, VSE applicationadministrators, capacity planners, and other technical professionals involved with data centeroperations, administration, and planning. An understanding of HP-UX system administrationconcepts and procedures is assumed.
New and Changed Information in This EditionThis document has been updated for VSE Management Software version 4.0 (A.04.00.07). Thisrelease includes a new licensing model, support for a remote Oracle database, and updatedsystem requirements.
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 website 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 holddown the key labeled Ctrl 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 should 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 InformationThe latest versions of VSE Management Software manuals, as well as white papers and manualsfor related products, can be downloaded from the following website:http://docs.hp.com/en/vse.htmlThe following manuals are included on this site:
Intended Audience 9
• VSE Management Software Version 4.0 Getting Started Guide• VSE Management Software Version 4.0 Installation and Update Guide for HP-UX• HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes• Insight Dynamics - VSE for ProLiant Version 4.0 Release Notes• VSE Management Software Version 4.0 Support Matrix• HP Virtualization Manager Version 4.0 Getting Started Guide• HP Application Discovery Version 4.0 User's Guide• HP Global Workload Manager Version 4.0 User's Guide• HP Capacity Advisor Version 4.0 User's Guide• HP Integrity Virtual Machines Manager Version 3.5 Getting Started Guide• HP Integrity Virtual Machines Installation, Configuration, and Administration• HP Integrity Virtual Machines Release Notes
VSE Management Software WebsitesFor the latest information about the VSE Management Software, including software updates,alerts and important information, visit the following HP websites:• The VSE Management website (http://docs.hp.com/en/vsemgmt/)• The HP VSE Managed Node Software Update website (http://vsemgmt.external.hp.com)
Related Product WebsitesFor information about VSE solutions, reference architectures, success stories, and related products,visit the following HP websites:• HP Virtual Server Environment (http://hp.com/go/vse)• HP Virtual Server Environment Reference Architectures (http://hp.com/go/vsera)• Partition Manager Product Information (http://www.docs.hp.com/en/PARMGR2/)• HP Insight Control Management Software portfolio (http://www.hp.com/go/insightcontrol)• HP Server Migration Pack — Universal Edition (http://www.hp.com/go/migrate)• HP Virtual Connect Enterprise Manager (http://www.hp.com/go/vcem)• HP ProLiant Essentials Virtual Machine Management Pack (http://www.hp.com/go/
vmmanage)• HP Systems Insight Manager (http://hp.com/go/hpsim). Follow the “Information library”
link for access to manuals, release notes, white papers and other documents.
ManpagesThe VSE Management Software and related products include HP-UX manpages with detailsabout commands, file formats, and related information. The following tables list some of themanpages that are most relevant to the VSE Management Software.
Table 1 Manpages Installed with VSE Management Software on the CMS
DescriptionManpage
Configure Application Discovery certificates from the CMSamgr_remote_config(1M)
Collect Capacity Advisor data from systemscapcollect(1M)
Export OpenView Performance Agent (OVPA) system data from managed systemsand import into Capacity Advisor
capovpaextract(1M)
Import, export, display, invalidate and remove Capacity Advisor data for workloadsor systems
capprofile(1M)
Format of Capacity Advisor import and export filescapprofile(4)
10
Table 1 Manpages Installed with VSE Management Software on the CMS (continued)
DescriptionManpage
Generate reports of historical data or utilization trends based on the existingconfiguration or on a scenario
capreport(1m)
Format for capreport command-filecapreport(4)
Global Workload Manager command-line interfacegwlm(1M)
Overview of Global Workload Managergwlm(5)
Global Workload Manager (gWLM) daemongwlmcmsd(1M)
Produce advanced textual summary reports for workload resource utilizationgwlmreport(1M)
Secure network communications for Global Workload Managergwlmsslconfig(1M)gwlmimportkey(1M)gwlmexportkey(1M)
Overview of XML file structure for Global Workload Managergwlmxml(4)
Help Resolve VSE Management Software Configuration Problemsvseassist(1M)
Configure or unconfigure the VSE Management Softwarevseinitconfig(1M)
Manage VSE Management Software LTUs on HP Integrity and HP 9000 systemsvselicense(1M)
Table 2 Manpages Installed with VSE Agent Software on Managed Systems
DescriptionManpage
Control Application Discovery certificates from the managed nodeagent_config(1M)
Control or modify the operation of the Application Discovery agentamgrd(1M)
Global Workload Manager (gWLM) agentgwlmagent(1M)
Place a process in a gWLM workloadgwlmplace(1M)
Send metric data to gWLM for use in a custom policygwlmsend(1M)
Secure network communications for Global Workload Managergwlmsslconfig(1M)gwlmimportkey(1M)gwlmexportkey(1M)
Display status for the managed node's agent and SRDgwlmstatus(1M)
(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
DescriptionManpage
Start Partition Managerparmgr(1M)
Table 4 Manpages Installed on Systems Running HP Integrity Virtual Machines
DescriptionManpage
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)
Related Information 11
Table 4 Manpages Installed on Systems Running HP Integrity Virtual Machines (continued)
DescriptionManpage
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)
Table 5 Selected HP Systems Insight Manager Manpages
DescriptionManpage
Configure the agent to work with a CMSmxagentconfig(1M)
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)
12
BooksThe following book can be ordered from HP Books (http://www.hp.com/hpbooks):• The HP Virtual Server Environment: Making the Adaptive Enterprise Vision a Reality in Your
Datacenter, by Dan Herington and Bryan Jacquot, Prentice Hall, 2006.
Publishing History
Publication DateSupported Operating Systems1Software VersionManufacturingPart Number
May 2008CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterHP-UX 11i v3Microsoft Windows Server 2003 (32-bit). WindowsCMS installation is not covered in this document; seeHP Insight Control Management Quick Setup Posterinstead.Managed systems:HP-UX 11i v1, 11i v2, or 11i v3Microsoft Windows Server 2003 Enterprise EditionMicrosoft Windows Server 2003 Datacenter EditionRed Hat Enterprise Linux 4 update 2 or later for IntelItaniumRed Hat Enterprise Linux 5 for Intel ItaniumSUSE Linux Enterprise Server 9 Service Pack 2 orlater for Intel ItaniumSUSE Linux Enterprise Server 10 for Intel Itanium
A.04.00.07T8671–90011
September 2007CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterHP-UX 11i v3Managed systems:HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3Microsoft Windows Server 2003 Enterprise EditionMicrosoft Windows Server 2003 Datacenter EditionRed Hat Enterprise Linux 4 update 2 or later forIntel® Itanium®SUSE Linux Enterprise Server 9 Service Pack 2 orlater for Intel Itanium
A.03.00.01T2786-90157
June 2007CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterManaged systems:HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3Microsoft Windows Server 2003 Enterprise EditionMicrosoft Windows Server 2003 Datacenter EditionRed Hat Enterprise Linux 4 update 2 or later for IntelItaniumSUSE Linux Enterprise Server 9 Service Pack 2 orlater for Intel Itanium
A.03.00.00T2786–90101
Publishing History 13
Publication DateSupported Operating Systems1Software VersionManufacturingPart Number
February 2007CMS:HP-UX 11i v1 December 2004 or laterHP-UX 11i v2 September 2004 or laterManaged systems:HP-UX 11i v1, HP-UX 11i v2, HP-UX 11i v3Microsoft Windows Server 2003 Enterprise EditionMicrosoft Windows Server 2003 Datacenter EditionRed Hat Enterprise Linux 4 update 2 or later for IntelItaniumSUSE Linux Enterprise Server 9 Service Pack 2 orlater for Intel Itanium
A.02.50.00T2786-90071
September 2006CMS: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 IntelItaniumSUSE Linux Enterprise Server 9 Service Pack 2 orlater for Intel Itanium
A.02.50.00T2786-90030
1 For detailed information about supported hardware and software, see the VSE Management Software Version 4.0Support Matrix. Not all VSE Management Software products and features are available on all platforms.
HP Encourages Your CommentsYour comments and suggestions regarding product features will help us develop future versionsof the VSE Management Software. Use the following email address to send feedback directly tothe VSE Management Software development team: [email protected].
NOTE: HP cannot provide product support through this email address. To obtain productsupport, contact your HP Support Representative, your HP Services Representative, or yourauthorized HP reseller. For more information about support services, see the support websiteat http://www.hp.com/go/support.
For other ways to contact HP, see the Contact HP website at http://welcome.hp.com/country/us/en/contact_us.html.
14
1 IntroductionThis document describes the installation of the VSE Management Software Version 4.0 (A.04.00.07)on a entral Management Server (CMS) running HP-UX. This includes system requirements,installation of the software on the CMS, upgrading from previous versions of the software,installation of agent software and WBEM providers on managed systems, and backup and restoreof the VSE Management Software database.For an overview of VSE and the VSE Management Software, key VSE concepts and terminology,and postinstallation software configuration procedures, see theVSEManagement Software Version4.0 Getting Started Guide
15
16
2 System RequirementsThe following sections provide a summary of the hardware and software requirements of VSEManagement Software version 4.0 installed on a CMS running HP-UX. For detailed informationabout supported hardware and software, including requirements for a CMS running MicrosoftWindows, see the VSE Management Software Version 4.0 Support Matrix.
HP Systems Insight ManagerVSE Management Software version 4.0 runs under HP Systems Insight Manager (HP SIM) Version5.2 with Update 1 (C.05.02.01.00.x) or later. If you are currently using an earlier version of HPSIM, see “Before Upgrading from a Previous Version” (page 34) for the recommended upgradeprocedure.System requirements for HP SIM are defined in the HP Systems Insight Manager 5.2 Installationand Configuration Guide for HP-UX (http://docs.hp.com/en/418810-003/). Refer to that documentfor information about HP SIM requirements and dependencies. In particular, note that you mightneed to install HP-UX patches before you install HP SIM.In addition to the requirements imposed by HP SIM, the requirements for this release of the VSEManagement Software are described in the following sections.
Maximum ConfigurationVSE Management Software version 4.0 supports a maximum of 500 managed systems (stand-aloneservers, server blades, nPartitions, virtual partitions, and virtual machines). There may additionallybe up to 60 Shared Resource Domains (SRDs) managing the objects, and 500 Capacity Advisorscenarios to analyze the objects. Table 2-1 summarizes the maximum configuration supportedby the VSE Management Software.
Table 2-1 Maximum VSE Configuration
500Managed systems
60Shared Resource Domains
500Workloads
500Scenarios
100Workloads per scenario
Up to 3 concurrent sessions on HP-UX 11i v1(B.11.11)Up to 5 concurrent sessions on HP-UX 11i v2or HP-UX 11i v3
VSE Management Software user sessions concurrently logged in toHP SIM
HP Systems Insight Manager 17
Hardware Requirements for the HP-UX CMSInstall the VSE Management Software on a server that is reserved for use as a CMS. Do not usethis server to run other applications and services that are unrelated to HP SIM. Running additionalunnecessary applications on this server can significantly affect the performance of HP SIM andthe VSE Management Software. Table 2-2 lists the minimum hardware requirements for anHP-UX CMS.
Table 2-2 HP-UX CMS Hardware Requirements
All HP 9000 servers, HP Integrity servers, HP Integrity server blades, and HP Integrityvirtual machines with two or more cores. HP recommends 4 or more cores for the CMSfor configurations approaching the maximum VSE configuration shown in Table 2-1(page 17).
CPU
Minimum memory required:HP-UX 11i v1 3 GBHP-UX 11i v2 3 GBHP-UX 11i v3 4 GBMinimum memory required to support the maximum VSE configuration:HP-UX 11i v1 4 GBHP-UX 11i v2 4 GBHP-UX 11i v3 5 GB
Physical Memory
/ HP SIM requires 20 MB minimum./opt HP SIM requires 600 MB. The VSE Management Software
requires an additional 200 MB./var/opt Log files are stored in the directories /var/opt/amgr,
/var/opt/gwlm and /var/opt/vse/logs. These logsare not automatically trimmed.Capacity Advisor requires a maximum of 4 GB for every 100workloads to maintain 4 years of historic data. This data isstored in the directory /var/opt/vse. You can modify theamount of data retained in data collection by modifying thePROFILE_RETAIN_DAYS variable. For details, see the HPCapacity Advisor Version 4.0 User's Guide.
Database Storage Global Workload Manager requires at least 1 GB. If youintend to keep historical data, HP recommends allowing4 GB for every 100 workloads managed by gWLM. If you arenot interested in historical data, you can trim the historicaldatabase by using the following command:gwlm history --truncate
If you are using the default HP SIM PostgreSQL database,this space will be allocated in /var/opt. If you are usingOracle, this space will be allocated on the Oracle databaseserver.
Swap Space 4 GB total swap space for HP 9000 systems.5 GB total swap space for HP Integrity systems.
Disk Space
HP-UX Operating Systems Supported on the CMSTable 2-3 lists the versions of HP-UX that are supported on the CMS.
Table 2-3 HP-UX Operating Systems Supported on the CMS
December 2004 or laterHP-UX 11i v1
September 2004 or laterHP-UX 11i v2
Any releaseHP-UX 11i v3
18 System Requirements
HP SIM Database RequirementsBy default, HP SIM is configured to use a PostgreSQL database for its internal data management.If you have access to an Oracle version 10g server, you can configure the CMS to use an Oracledatabase instead of PostgreSQL.
NOTE: Only version 10g is supported for use with the VSE Management Software. HPrecommends that you install Oracle on a different server than the CMS. This allows betterperformance, because HP SIM and Oracle use different recommended kernel parameter settings.
The VSE Management Software manages its own internal data using whichever database softwareis configured for HP SIM. Each VSE CMS must be configured with its own database instance. Asingle database instance cannot support more than one CMS.Procedure 3-6 (page 36) includes an optional step to configure the CMS for Oracle duringinstallation of the VSE Management Software.For more information about configuring HP SIM to use an Oracle database, see the HP SystemsInsight Manager 5.2 Installation and Configuration Guide for HP-UX.
HP SIM Database Requirements 19
Additional Software Requirements on the HP-UX CMSTable 2-4 lists additional requirements that apply to software installed on the HP-UX CMS.
Table 2-4 Additional Software Requirements on the HP-UX CMS
RequirementsSoftware
The Java™ Runtime Environment (JRE 1.5) is required.Java Out of Box (JOOB) version 2.03 or later is required. JOOB is shipped with HP-UXas optional selectable software. Installation of JOOB requires a reboot.
Java
To allow OpenView Performance Agent access to the gWLM data theMeasureWare.PERFDSI fileset (version C.03.85 or later) must be installed. Thefollowing command lists the fileset 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 Pakversion C.03.85.00 or later.
gWLM Data Access fromOpenView PerformanceAgent
If the CMS is also a managed system, then all of the additional requirements formanaged systems apply to the CMS. For those requirements, see “Additional SoftwareRequirements on Managed Systems” (page 21) .
CMS as a managed system
20 System Requirements
Operating Systems Supported on Managed SystemsTable 2-5 lists the operating systems that are supported on managed systems with an HP-UXCMS. For more complete information about supported managed system types for both the HP-UXCMS and Microsoft Windows CMS, see the VSEManagement Software Version 4.0 Support Matrix.
Table 2-5 Operating Systems Supported on Managed Systems
NotesOperating System
The libc cumulative patch must be installed to use Application Discovery and gWLM:On HP-UX 11i v1: PHCO_37369On HP-UX 11i v2: PHCO_37228On managed systems running HP-UX 11i v1, the patch PHCO_30030 must be installedto use Application Discovery.On managed systems running HP-UX 11i v2, the memory patch PHSS_33349 must beinstalled to use Virtualization Manager and Capacity Advisor.A managed system running HP-UX 11i v2 within a virtual machine under HP IntegrityVM requires the following kernel patches:• PHKL_33752• PHKL_35174On rx8640 or rx7640 systems running HP-UX 11i v2, kernel patch PHKL_35174 mustbe installed to manage nPartitions and virtual partitions with gWLM.The patches listed above might have additional patch dependencies and might besuperseded by more recent patches.Logical servers are not supported on HP-UX managed systems.
HP-UX 11i v1HP-UX 11i v2HP-UX 11i v3
Microsoft Windows Server 2003 Enterprise EditionMicrosoft Windows Server 2003 Datacenter Edition
NOTE: Systems running Microsoft Windows can only be managed by gWLM as HPIntegrity virtual machines.
64-bit Microsoft Windowsfor Integrity
Supported with Windows CMS only. These systems cannot be managed from an HP-UXCMS.
NOTE: Systems running Microsoft Windows cannot be managed by gWLM.
32-bit Microsoft Windows
Red Hat Enterprise Linux 4 update 2 or later for Intel ItaniumRed Hat Enterprise Linux 5 for Intel ItaniumSUSE Linux Enterprise Server 9 Service Pack 2 or later for Intel ItaniumSUSE Linux Enterprise Server 10 for Intel Itanium
NOTE: Systems running Linux cannot be managed by gWLM.
64-bit Linux for Integrity
32-bit Linux systems are only supported with Windows CMS. These systems cannotbe managed from an HP-UX CMS.
NOTE: Systems running Linux cannot be managed by gWLM.
32-bit Linux
Only supported with Windows CMS (requires HP Virtual Machine Management Pack).These systems cannot be managed from an HP-UX CMS.
VMWare ESX and MicrosoftVirtual Server (MSVS)virtual machines and VMHosts
Additional Software Requirements on Managed SystemsThis section discusses requirements for software that can or must be installed on systems managedby the VSE Management Software.
WBEM Providers and Agent SoftwareTable 2-6 lists the WBEM providers and other agents that are required by the VSE ManagementSoftware. These components are installed using the process described in “Install VSE Agent
Operating Systems Supported on Managed Systems 21
Software on Managed Systems” (page 40). HP recommends that you follow this process to installthe latest versions of the agent software. Do not assume that earlier versions of the providersand agents will work correctly with this release of the VSE Management Software.
Table 2-6 WBEM Providers and Agent Software
RequirementsSoftware
The Utilization Provider version 1.7 (A.01.07) or later is required on all VSE managedsystems. It provides utilization data for Virtualization Manager and Capacity Advisor.Use the process described in “Install VSE Agent Software on Managed Systems”(page 40) to install the latest version of the Utilization Provider.
Utilization Provider
The AD agent version 3.1.00.01 or later is required on all systems that are managed byApplication Discovery. Use the process described in “Install VSE Agent Software onManaged Systems” (page 40) to install the latest version of the AD agent.
Application DiscoveryAgent
The Application Discovery WBEM Provider version 3.1.00.01 or later is required on allsystems that are managed by Application Discovery. Use the process described in“Install VSE Agent Software on Managed Systems” (page 40) to install the latest versionof the WBEM provider.
Application DiscoveryWBEM Provider
The gWLM agent is required on all systems that are managed by gWLM. This releaseof gWLM works with earlier versions of the gWLM agent. Changes introduced withgWLM version A.04.00.07 enable you to perform the following tasks. You cannot deploySRDs that use these features on managed systems using earlier versions of the gWLMagent.• Create conditional policies that depend on time-based conditions• Create conditional policies that depend on file-based conditions• Create custom policies that scale metrics you provide to generate requests for CPU
resources for your workloads• Create SRDs from members of a Global Instant Capacity (GiCAP) group1
HP recommends installing the latest version of the gWLM agent, using the processdescribed in “Install VSE Agent Software on Managed Systems” (page 40).
gWLM Agent
Install this software on HP-UX managed systems even if the system does not usenPartitions.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.HP-UX 11i v3 Requires version B.31.01.07.01 or later.Use the process described in “Install VSE Agent Software on Managed Systems”(page 40) to install the latest version of the nPartition Provider.
nPartition Provider
22 System Requirements
Table 2-6 WBEM Providers and Agent Software (continued)
RequirementsSoftware
VM Provider version 1.20 or later must be installed on HP Integrity VM host systems.Earlier versions of the VM Provider can be used on individual virtual machines. Installedversions of HP Integrity VM, VM Provider, and VMGuestLib must be compatible. Donot mix different versions of these components on the same system.Use the process described in “Install VSE Agent Software on Managed Systems”(page 40) to install the latest version of the VM Provider.
VM 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 andthe VSE Management software do not discover and display virtual partitions correctly.The vPar Provider that is included with the VSE Management software fixes thisproblem. 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 Providerwhen used with WBEM version A.02.00.09. This problem does not occur with theHP-UX 11i v3 (B.11.31) vPar Provider.You can fix this problem by executing the following command on each system wherethe vPar Provider is 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 versionof the vPar Provider and install the version delivered with the VSE Managementsoftware (or forcibly reinstall the VSE Management Software version).
vPar Provider
1 For information about supported versions of iCAP and GiCAP, see “Managed System Compartment Software”(page 26).
Additional Software Requirements on Managed Systems 23
Other Software and ServicesTable 2-7 lists requirements that apply to other software installed on managed systems.
Table 2-7 Additional Software Required on Managed Systems
RequirementsSoftware
WBEM is required on managed systems to support the visualization and configurationfeatures of Virtualization Manager and the collection of utilization data for CapacityAdvisor. Without WBEM, only gWLM is functional.On managed systems running HP-UX 11i v1 or HP-UX 11i v2, HP WBEM Services forHP-UX version A.02.00.11 or later must be installed. For managed systems runningHP-UX 11i v3, HP WBEM Services for HP-UX version A.02.05 or later is required. Usingearlier versions of WBEM can generate cimserver errors, including timeouts inVirtualization Manager and VM Manager, and messages such as “CIM failure” and“Connection Refused”. You can install these versions of WBEM on managed systemsfrom the CMS using the Configure VSE Agents menu. For more information, see“Install VSE Agent Software on Managed Systems” (page 40).
NOTE: If you want to use certificate-based WBEM authentication, you must installWBEM version A.02.05 or later on HP-UX managed systems, including systems runningHP-UX 11i v1 or HP-UX 11i v2. You can download the latest version of HP WBEMServices for HP-UX from the HP Software Depot website at http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=WBEMSvcs. For moreinformation about WBEM authentication options, see “Prepare for Installation”.On Linux managed systems you must install tog-pegasus version 2.5 or later andthe HP Integrity Essentials Foundation Pack for Linux Management CD. For moreinformation, see “Preinstallation Steps for Linux Managed Systems” (page 32).
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 SystemManagement Homepage (HP SMH). LDAP-UX Version B.03.xx prevents HP SIM andthe VSE Management Software from reading required WBEM data.The latest version of LDAP-UX Integration for HP-UX is available from Software Depotat http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=J4269AA.
LDAP
OpenSSH version 4.40 or later is required on managed systems in order to install theVSE agent software from HP SIM, create monitored workloads, and execute commandson managed systems remotely from the CMS. Remote command execution is used byPartition Manager, VM Manager, and the capovpaextract command.OpenSSH for HP-UX managed systems is provided by HP-UX Secure Shell. Thissoftware can be downloaded from http://software.hp.com, and is also available on theHP-UX OE/AR media releases. It is installed by default.OpenSSH must be configured for use by HP SIM. For more information, see “InstallVSE Agent Software on Managed Systems” (page 40).On Windows managed systems, OpenSSH is not installed by default, but it can beinstalled from the HP Smart Setup installation media (version 4.5 or later). You mustmanually configure OpenSSH for use with HP SIM. For more information, see“Preinstallation Steps for Microsoft Windows Managed Systems” (page 33).On Linux systems, OpenSSH is usually installed by default, or it can be installed fromthe Linux distribution media. However, you might need to manually configure OpenSSHfor use with HP SIM. For more information, see “Preinstallation Steps for LinuxManaged Systems” (page 32).For more information about configuring OpenSSH for use with HP SIM, see the HPwhite paper Secure Shell (SSH) in HP SIM 5.0, available from the Information Library linkat http://hp.com/go/hpsim.
OpenSSH
24 System Requirements
Table 2-7 Additional Software Required on Managed Systems (continued)
RequirementsSoftware
OpenSSL is required on managed systems in order to enable the Application Discoveryagent software to send application information to the CMS.The latest version of OpenSSL software for HP-UX is available from Software Depotat http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=OPENSSL11I. On Linux systems, OpenSSLis usually installed by default, or it can be installed from the Linux distribution media.To avoid a number of known security vulnerabilities, the version of OpenSSL on amanaged system should be later than 0.9.7l for the 0.9.7 branch, or later than 0.9.8d forthe 0.9.8 branch.For the latest information about OpenSSL, including security advisories, see http://www.openssl.org/news.
NOTE: This link refers to an external website outside of the HP web. Hewlett-Packardis not responsible for the information at this site.
OpenSSL
Installed versions of HP Integrity VM, VM Provider, and VMGuestLib must becompatible. Do not mix different versions of these components on the same system. Inaddition, HP Integrity VM might require additional HP-UX patches installed on theVM Host and on virtual machines. For more information, see the HP Integrity VirtualMachines Release Notes.
HP Integrity VM
HP Serviceguard version 11.16 or later is supported by Virtualization Manager.Monitored workloads can be associated with a Serviceguard cluster and package. IfHP Serviceguard Manager is installed on the CMS, systems that are contained inServiceguard clusters can be viewed through Serviceguard Manager with a click fromVirtualization Manager.The HP Serviceguard WBEM provider requires privileged access. If you use aServiceguard cluster that is not configured for SNMP or you are not using the SNMPServiceguard provider, then you must configure a privileged WBEM user account onall managed systems in the Serviceguard cluster.
HP Serviceguard
If you are using gWLM, Instant Capacity, or vPars on an HP-UX managed system, theinterrupt-balancing daemon intrbald might improve performance. On HP-UX 11iv2, this software is available by installing patches PHKL_36288, PHKL_36490, andPHCO_36079. On HP-UX 11i v3, it is included with the March 2008 (or later)FEATURE11i bundle, or you can install patches PHKL_36778, PHKL_36779, andPHCO_37478.
NOTE: The patches listed above might have additional patch dependencies andmight be superseded by more recent patches.For more information, see intrbald(1M).
Interrupt-balancing daemon(intrbald)
Additional Software Requirements on Managed Systems 25
Managed System Compartment SoftwareTable 2-8 lists the supported versions of the products that provide the compartments that gWLMmanages. A system managed by gWLM must have at least one of these products installed.
Table 2-8 Managed System Compartment Software
RequirementsSoftware
Instant Capacity version 8.02 or later (but not including version 9.0 or later) is requiredto simulate CPU movement between GiCAP group members.
nPartitions
vPars version A.03.01.05 or later is supported. However, vPars version A.03.04 or lateris strongly recommended due to potential stability issues. With vPars versions earlierthan version A.03.04, a race condition can occur when gWLM migrates CPU resourcesrapidly. In rare cases, this can cause the virtual partition to crash. It can also producea panic. For more information about this problem, see theHPVirtual Server EnvironmentManagement for Integrity Version 4.0 Release Notes (section entitled “Rare Incompatibilitywith Virtual Partitions”).The following tunable kernel parameters must be configured as specified:max_thread_proc at least 256nkthread 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, install patchesPHKL_33052, PHKL_33604, and PHKL_33605.
NOTE: These patches might have additional patch dependencies and might besuperseded by more recent patches.The following tunable kernel parameters must be configured as shown:max_thread_proc at least 256nkthread max_thread_proc + the number of threads needed by all
the other processes on the system
Virtual machines
For HP-UX 11i v1, you must download and install the following free products fromhttp://software.hp.com:• HP-UX Processor Sets• The HP-UX 11i Version 1 Quality PackThis software is already included in HP-UX 11i v2 and HP-UX 11i v3.
Processor sets (psets)
ThePRM-Sw-Krn.PRM-KRN fileset must be installed. The following command displaysthe fileset information if it is installed on the system. Any version of the fileset isacceptable.# /usr/sbin/swlist PRM-Sw-Krn.PRM-KRN
If this fileset is not installed, it is available for installation as part of the bundlePRMKernelSW, which is available from Software Depot (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 PHKL_33052, PHKL_33604, PHKL_33605.
CAUTION: A system panic will result if you attempt to deploy an SRD based on FSSgroups on a system without these patches.
NOTE: These patches might have additional patch dependencies and might besuperseded by more recent patches.The following tunable kernel parameters must be configured as shown:max_thread_proc at least 256nkthread max_thread_proc + the number of threads needed by all
the other processes on the system
Fair-Share Scheduler (FSS)
26 System Requirements
Compatibility with HP-UX Bastille and Other Network FirewallsNetwork firewall software such as HP-UX Bastille might block the communication protocolsused by the VSE Management Software. If your CMS or VSE managed systems use firewallsoftware, follow the configuration guidelines in the following sections.
VSE Management Software Network Communication ProtocolsThe VSE Management Software retrieves real-time and historical utilization data from managedsystems and their associated applications using the following network communication protocols.• The SSH-2 (secure shell) protocol is used to install the VSE agent software from the CMS to
support the visualization and configuration features of Virtualization Manager, and to collectutilization data for Capacity Advisor.
• Web-Based Enterprise Management (WBEM) services are used to support the visualization andconfiguration features of Virtualization Manager and to collect utilization data for CapacityAdvisor.
• OpenSSL protocol is used to obtain application information from managed systems forApplication Discovery.
HP SIM uses additional communication protocols between the CMS and managed systems toprovide real-time system status and WBEM indications, and for basic communication betweenthe web-based applications and the end user.If you are using firewall software such as HP-UX Bastille on the CMS or on managed systems,the firewall must be configured so that it does not block the required network communication.The following sections present detailed configuration instructions for HP-UX Bastille. Othernetwork firewall software must be similarly configured.Additional information about HP SIM secure data transmission and related issues can be foundin the manuals and white papers available from the “Information library” link at http://hp.com/go/hpsim.
Firewall Settings on the CMSThe following set of protocols should be allowed through firewalls between the CMS and themanaged systems.Communication Between the CMS and Managed Nodes• The Internet Control Message Protocol ICMPv4 Type 8 (Echo), the ping protocol.• HTTPS over port 5989, used by WBEM.• HTTPS over port 2381, used by web agents.• SSH-2 over port 22, used by the Distributed Task Facility (DTF).• OpenSSL over port 9143, used by Application Discovery.• Global Workload Manager uses ports 9617 and 9618 on the CMS. Refer to the
“Communications Ports” section of the HP Global Workload Manager Version 4.0 User's Guidefor information about changing the default ports.
Communication Between the CMS and the Web Browser• HTTP over port 280 (initial communication)• HTTPS over port 50000 (subsequent user interface communication)
Bastille Settings on the CMSIf Bastille/Install-Time Security is used to secure the CMS, use the “Managed DMZ” level forinitial lockdown. To configure the CMS for Managed DMZ, use Procedure 2-1. For additionalinformation, see bastille(1M).
Compatibility with HP-UX Bastille and Other Network Firewalls 27
Procedure 2-1 Configure CMS for Managed DMZ Under HP-UX Bastille1. Copy the configuration file /etc/opt/sec_mgmt/bastille/MANDMZ.config to
/etc/opt/sec_mgmt/bastille/config.
NOTE: In some versions of HP-UX Bastille, the MANDMZ.config file might be located ina subdirectory under /etc/opt/sec_mgmt/bastille/.
2. Add the following rules to the top of the file/etc/opt/sec_mgmt/bastille/ipf.customrules.
NOTE: Lines shown ending in “\” should be combined with the following line and enteredas a single line.
# Custom CMS firewall rules# Allow pingpass in quick proto icmp from any to any icmp-type 8 \keep state
# Allow HTTP on port 280 for inbound HP SIM connectionspass in quick proto tcp from any to any port = 280# Allow HTTPS on port 50000 for inbound HP SIM connectionspass in quick proto tcp from any to any port = 50000
# Global Workload Manager uses ports 9617 and 9618 to# communicate with remote agentspass in quick proto tcp from any to any port = 9617 \flags S keep state keep fragspass in quick proto tcp from any to any port = 9618 \flags S keep state keep frags
# Application Discovery uses OpenSSL on port 9143pass in quick proto tcp from any to any port = 9143 \flags S keep state keep frags
3. Run the Bastille configuration engine by entering the following command:
# /opt/sec_mgmt/bastille/bin/bastille -b
Firewall Settings on Managed SystemsThe following set of protocols should be allowed through the firewall:• The Internet Control Message Protocol ICMPv4 Type 8 (Echo), the ping protocol. Both
inbound and outbound ping are needed for SIM discovery and system status.• HTTPS over port 5989, used by WBEM.• HTTPS over port 2381, used by web agents.• SSH-2 over port 22, used by the Distributed Task Facility (DTF).• Global Workload Manager uses port 9617 on managed nodes. Refer to the “Communications
Ports” section of the HP Global Workload Manager Version 4.0 User's Guide for informationabout changing the default ports.
Bastille Settings on the Managed SystemIf Bastille/Install-Time Security is used to secure the managed system,, use the “Managed DMZ”level for initial lockdown. To configure a managed system for Managed DMZ, use Procedure 2-2.For additional information, see bastille(1M).
28 System Requirements
Procedure 2-2 Configure Managed System for Managed DMZ Under HP-UX Bastille1. Copy the configuration file /etc/opt/sec_mgmt/bastille/MANDMZ.config to
/etc/opt/sec_mgmt/bastille/config.
NOTE: In some versions of HP-UX Bastille, the MANDMZ.config file might be located ina subdirectory under /etc/opt/sec_mgmt/bastille/.
2. Add the following rules to the top of the file/etc/opt/sec_mgmt/bastille/ipf.customrules.
NOTE: Lines shown ending in “\” should be combined with the following line and enteredas a single line.
# Custom HP SIM Managed System firewall rules# Allow pingpass in quick proto icmp from any to any icmp-type 8 \keep state
# Global Workload Manager uses port 9617 to# communicate with the CMSpass in quick proto tcp from any to any port = 9617 \flags S keep state keep frags
3. Run the Bastille configuration engine by entering the following command:
# /opt/sec_mgmt/bastille/bin/bastille -b
Additional Requirements in the Release NotesFor additional requirements and installation notes, see the following documents:• HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes• HP Integrity Virtual Machines Release NotesThe latest versions of these documents can be dowloaded from http://docs.hp.com/en/vse.html.
Additional Requirements in the Release Notes 29
30
3 InstallationInstall HP SIM and the VSE Management Software using Procedure 3-1.
IMPORTANT: Starting with VSE Management Software version 4.0 (A.04.00.07.xx), licenses forVSE Management Software are now managed in the HP SIM License Manager database on theCMS. When you upgrade an HP-UX CMS that has a previous version of the VSE ManagementSoftware installed, any product licenses that were previously installed or scanned areautomatically migrated to the License Manager database. For more information about migratingprevious licenses to the new license model, see vselicense(1M) and the VSE Management SoftwareVersion 4.0 Getting Started Guide.
Procedure 3-1 Installation Overview1. Obtain the VSE Management Software installation package. It is available as a single
download from the Software Depot website at http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=vse. The software includes a 90-day trial licensefor HP 9000 and HP Integrity managed systems. For details about VSE Management Softwarelicenses, see the VSE Management Software Version 4.0 Getting Started Guide.
2. Prepare for VSE Management Software installation by installing the required software andpatches, establishing common WBEM user credentials on the CMS and managed systems,and completing preinstallation steps for Linux and Microsoft Windows managed systems.See “Prepare for Installation”.
3. If you are upgrading from a previous version of the VSE Management Software, performthe upgrade preinstallation steps as described in “Before Upgrading from a Previous Version”(page 34).
4. Install HP SIM and the VSE Management Software on the CMS. See “Install the Softwareon the CMS” (page 36).
5. Launch HP SIM and run the First Time Wizard and the Discovery processes. See “Start andConfigure HP SIM” (page 38).
6. Install the WBEM providers and other agent software on your managed systems. See “InstallVSE Agent Software on Managed Systems” (page 40).
7. If you upgraded from a previous version of the VSE Management Software, perform theupgrade postinstallation steps as described in “After Upgrading from a Previous Version”(page 43).
8. Configure the VSE Management Software for your environment. See “Configure VSEManagement Software” (page 47).
IMPORTANT: The VSE Management Software does not operate correctly until you completethese postinstallation configuration steps. You must perform these steps even when you arereinstalling or updating an existing installation.
Prepare for InstallationFor a description of HP SIM patch requirements, see theHPSystems InsightManager 5.2 Installationand Configuration Guide for HP-UX.Verify that your CMS and managed systems meet the VSE Management Software systemrequirements described in “System Requirements” (page 17).Look for any updates to the requirements or installation instructions in the HP Virtual ServerEnvironmentManagement for Integrity Version 4.0 Release Notes. The latest version of this doccumentcan be downloaded from http://docs.hp.com/en/vse.html.
Prepare for Installation 31
Establish common WBEM credentials on the CMS and on the managed systems to allowauthenticated access to WBEM data. The VSE Management Software uses WBEM connectionsto obtain information from the managed systems. To avoid having to maintain multiple WBEMuser accounts and passwords, HP recommends that you use one of the following WBEMauthentication models.1. Single WBEM user account 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 rootprivileges and should not have a login shell associated with it. Use NIS, LDAP, or othertechniques to maintain a single password for this user name across all of your systems. Enterthis user name and password during the HP SIM First Time Wizard or by selectingOptions→Protocol Settings→Global Protocol Settings from the HP SIM menu.
IMPORTANT: Even though the WBEM user account information is configured as a globaldefault, HP SIM remembers the credentials that previously succeeded for each managedsystem, and tries the same credentials in subsequent WBEM exchanges. If the password forthe WBEM account is changed, the previously successful user name and password is nolonger valid. However, if your network includes storage systems managed through WBEM,authentication via the same expired WBEM credentials might be attempted multiple times.In some network environments, these repeated authentication requests using an expiredpassword can cause the WBEM user account to be locked out.To fix this problem, select your managed systems and change the WBEM passwordinformation using Options→Protocol Settings→System Protocol Settings instead ofusing Global Protocol Settings. This updates the entry for each selected system, so thatHP SIM does not attempt to use the expired password before falling back to global settings.If your network environment requires frequent password changes and locks out user accountsafter multiple failed password attempts, WBEM certificate-based authentication might bea better choice.
2. WBEM Certificate-Based Authentication You can configure WBEM authentication for asingle system or a selected set of systems by selecting Options→Protocol Settings→SystemProtocol Settings from the HP SIM menu. To authenticate through a certificate instead ofusing a WBEM user account and password, select Use certificate instead. Online help forthis option is available in HP SIM. Online help for certificates in general can be found in theHP SIM help system under the Networking and Security topic.
NOTE: On all HP-UX managed systems, HP WBEM Services for HP-UX version A.02.05or later is required in order to use certificate-based WBEM authentication.
For more information about WBEM security configuration in HP SIM, see the HP white paperUnderstanding HP Systems Insight Manager security, available from the Information Library link athttp://hp.com/go/hpsim.
Preinstallation Steps for Linux Managed SystemsOn managed systems running Red Hat Enterprise Linux, disable SELinux to avoid conflictswith the WBEM providers and agent software.In order for Linux managed systems to be correctly discovered by HP SIM, you must installWBEM and the required WBEM providers from the HP Integrity Essentials Foundation Pack forLinux Management CD. Download and install the contents of this CD using Procedure 3-2.Procedure 3-2 Download and Install Linux Management Software1. On the HP Open Source and Linux website at http://hp.com/go/integritylinux, click the
Software & Drivers link.
32 Installation
2. Under the section Support for your products, select the option Download drivers andsoftware (and firmware).
3. In the same section, enter your server product information in the product field (for example,“integrity rx7620 servers”) and press Enter. The support center page for your serveris displayed.
4. Under Select operating system, click the link that corresponds to your Linux OS version.The Download drivers and software page for your server is displayed.
5. Click the Software - Support Pack link to jump to the correct section of the page.6. Click Download under the Software - Support Pack section to download the tar file.7. Install the software according to the instructions included in the docs directory contained
in the tar file.8. Make sure that the tog-pegasus package is installed and running on the system.9. On Red Hat Enterprise Linux, you might need to modify the file
/etc/Pegasus/access.conf to allow WBEM access using your designated WBEM username and password. Perform the following steps to configure this file. In this example, yourdesignated 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 canuse the same procedure that is used to configure OpenSSH for HP SIM on HP-UX managedsystems, as described in “Install VSE Agent Software on Managed Systems” (page 40). However,if you are using SUSE Linux Enterprise Server 9, you must first manually configure OpenSSHto use password authentication.
IMPORTANT: SUSE Linux Enterprise Server 9 ships with SSH configured to use PAMauthentication instead of password authentication. Password authentication is required in orderfor the mxagentconfig to configure OpenSSH for use by HP SIM.
On managed systems running SUSE Linux Enterprise Server 9, change to password authenticationusing Procedure 3-3.Procedure 3-3 Configure SUSE Linux for Password Authentication1. Configure the following lines in /etc/ssh/sshd_config on the managed system:
PasswordAuthentication yes #UsePAM yes
2. Retrieve the process id of the running sshd from the file /var/run/sshd.pid.3. Restart sshd by executing the following command:
# kill -SIGHUP pid
where pid is the sshd process id.
Preinstallation Steps for Microsoft Windows Managed SystemsOn Windows managed systems OpenSSH is not installed by default, but it can be installed fromthe HP Smart Setup installation media (version 4.5 or later). Use Procedure 3-4 to install OpenSSH
Prepare for Installation 33
and configure it for use with HP SIM. You can then install the VSE agent software andWMI/WBEM providers from HP SIM using the procedure described in “Install VSE AgentSoftware on Managed Systems” (page 40).Procedure 3-4 Install and Configure OpenSSH for Windows1. Follow the instructions in the HP Smart Setup CD to install OpenSSH Services on the
Windows managed system. During installation you must specify the user name and passwordfor the account that runs the OpenSSH service. The Administrator account is typicallyused for this.
NOTE: During installation, OpenSSH automatically imports your local user accounts intoits password file. If additional accounts are added later, you must reinstall OpenSSH or usethe sshuser command to import the new user account information into OpenSSH.
2. Reboot the Windows managed system to enable SSH communication.3. Configure OpenSSH for use with HP SIM by executing the following command on the CMS:
# mxagentconfig -a -n node-hostname -u Administrator -p password
where node-hostname is the name of the system as it is known by HP SIM. If the systemadministrator user account on your managed system is not Administrator, substituteyour administrator user name in the preceding command. You can use multiple -n optionsin order to perform this operation on more than one managed system.
NOTE: This step can be performed within HP SIM by selecting the managed systems toconfigure, then selecting Configure→Configure or Repair Agents... from the HP SIMmenu bar. On the Configure or Repair Settings page, select Configure secure shell (SSH)access.
4. If you are using Partition Manager to manage Windows systems, you must also create auser account named root on those Windows systems. Partition Manager uses this username for remote execution of nPartition commands through OpenSSH. Add this user to theAdministrators group in Windows, then add this user to OpenSSH using the sshusercommand.To configure remote connections from the CMS using theroot account, execute the followingcommand on the CMS :# mxagentconfig -a -n node-hostname -u root -p root-password
OpenSSH is now configured for connections from the CMS (with host-based authentication),using either the Administrator or root account. Partition Manager uses the root accountfor remote command execution.
Before Upgrading from a Previous VersionThis section describes the steps you must perform before upgrading from an earlier version ofVSE Management Software to version A.04.00.07. This process converts an existing VSEManagement Software database, including historical profile data, to the new version databaseformat. Any historical profile data that you want to migrate to the new database format must beinstalled in the currently running installation on the CMS.
34 Installation
IMPORTANT: Starting with VSE Management Software version 4.0 (A.04.00.07.xx), licenses forVSE Management Software are now managed in the HP SIM License Manager database on theCMS. When you upgrade an HP-UX CMS that has a previous version of the VSE ManagementSoftware installed, any product licenses that were previously installed or scanned areautomatically migrated to the License Manager database. For more information about migratingprevious licenses to the new license model, see vselicense(1M) and the VSE Management SoftwareVersion 4.0 Getting Started Guide.
Make a backup The upgrade process is not reversible. It can only be undone by removingversion A.04.00.07 and reinstalling the older version. Make a backup of your VSE ManagementSoftware database before upgrading the software, in case you need to revert to the previousversion. You can use this backup to restore your current configuration after reverting to theprevious version of the software.Use Procedure 3-5 to prepare for the upgrade.
NOTE: You can also use this procedure to upgrade from gWLM version A.02.xx to VSEManagement Software version A.04.00.07. In this case, you can ignore the steps that concernexisting versions of other VSE Management Software (for example, Capacity Advisor).After upgrading, be sure to follow the instructions in “After Upgrading from a Previous Version”(page 43). In particular, see the issue described in “Rediscover Partition-Based SRDs” (page 44).
Procedure 3-5 Prepare for VSE Management Software Upgrade1. If you are using gWLM, undeploy all shared resource domains (SRDs) and stop using the
existing version, including the command-line interface. You can continue running the gWLMdaemons (gwlmcmsd and gwlmagent) and the WBEM service and provider daemons.
2. Stop using the version of Capacity Advisor that is already installed, including thecommand-line interface. If necessary, use the following substeps to disable each automaticallyscheduled Capacity Advisor data collection task:a. Select 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 check box.f. Click Done.g. Verify that the task you just edited is in the list and now shows Task is Disabled
in the Schedule column.3. Log out of HP SIM.4. (Optional) Use the capcollect command to collect the latest Capacity Advisor data into
the VSE Management Software database. For more information, see capcollect(1M).5. Make a backup Make a backup of your existing VSE Management Software database.
You can use this backup if you need to revert to the older version of the software. With thisbackup, you can restore your current configuration after reverting to the older version ofthe software. You cannot restore this backup after version A.04.00.07 is installed. Previousversions of the VSE Management Software used a database format that is incompatible withversion A.04.00.07.For more information about backing up and restoring the VSE Management Softwaredatabase and reverting to a backup from a previous version of the software, seevseinitconfig(1M). This manpage is included in this manual in Appendix A (page 49).
Before Upgrading from a Previous Version 35
For information about backing up the HP SIM database, refer to the HP white paper Backingup and restoring HP Systems Insight Manager data files in an HP-UX or Linux environment,available from the Information Library link at http://hp.com/go/hpsim.
6. If you are upgrading to a new version of HP SIM, follow any upgrade preparation instructionsprovided with the new version of HP SIM. In particular, note that you might need to installadditional patches.
After you complete the installation steps in the following sections, see “After Upgrading froma Previous Version” (page 43) for additional steps that you should perform.
Install the Software on the CMSUse Procedure 3-6 to install HP SIM version 5.2 with Update 1 (C.05.02.01.00.x) and the VSEManagement Software on the CMS. If you have already installed this version of HP SIM, youcan use Procedure 3-7 instead.Procedure 3-6 Install or Upgrade HP SIM and VSE Management Software1. Enter the following command on the CMS:
# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file HPSIM-HP-UX VSEMgmt
IMPORTANT: The system reboots after the installation.
The actions that occur after system reboot depend on whether this is a new installation ofHP SIM or an upgrade to an existing HP SIM installation.New installation of HP SIM Configure HP SIM by entering the following command
on the CMS:# mxinitconfig -a
Upgrade of an existing installationof HP SIM
The system automatically runs mxinitconfig afterthe reboot. This can take up to 20 minutes to complete.Do not attempt to run any HP SIM commands or VSEmanagement commands, or access HP SIM throughthe web interface at this time.Other steps might be required to complete the HP SIMupgrade. For example, you might need to reidentifyall discovered systems to complete the databaseupgrade for existing systems in the database.
2. (optional) If Oracle version 10g is installed on a server in your environment, you can configureHP SIM and the VSE Management Software to use an Oracle database instead of thedefaultPostgreSQL database for internal data management. For specific requirements forusing Oracle with the VSE Management Software, see “HP SIM Database Requirements”(page 19).To configure HP SIM for Oracle, use the following steps:a. Ensure that Oracle 10g is installed and running on the Oracle server.b. Copy the file ojdbc14.jar from your Oracle 10g server to a location on your CMS.
NOTE: Do not rename this file. It must be named ojdbc14.jar when it is installedby mxoracleconfig in the next step.
c. Configure HP SIM by entering the following command on the CMS:
36 Installation
# mxoracleconfig [-h hostname] [-n port-number] \ -d database-name -u username -p password \ -j path-to-jar-file/ojdbc14.jar [-f]
For details about the mxoracleconfig command, see mxoracleconfig(1M).
d. Reinitialize HP SIM by entering the following command on the CMS:# mxinitconfig -a
3. Configure the VSE Management Software by entering the following command:# /opt/vse/bin/vseinitconfig -a
The vseinitconfig command logs status, errors, and exceptions to the file/var/opt/vse/logs/vseinitconfig.log. Review the output of this command toensure there are no errors.
IMPORTANT: If you are upgrading from a previous version of the VSE ManagementSoftware, thevseinitconfig command migrates any product licenses that were previouslyinstalled or scanned to the HP SIM License Manager database. Review the licensinginformation in the log file to make sure that it is correct. You may need to adjust the numberof licensed cores using the vselicense command. For more information about migratingprevious licenses to the new license model, see vselicense(1M) and the VSE ManagementSoftware Version 4.0 Getting Started Guide.
4. When vseinitconfig finishes, you are prompted to restart HP SIM. Type “y” and pressEnter to restart HP SIM.
5. (Optional) Execute the command catman to make sure that the VSE Management Softwaremanpages can be listed by keyword using man -k.
Procedure 3-7 Install VSE Management Software Using Existing Installation of HP SIM1. Enter the following command on the CMS:
# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file VSEMgmt
2. Configure the VSE Management Software by entering the following command:# /opt/vse/bin/vseinitconfig -a
The vseinitconfig command logs status, errors, and exceptions to the file/var/opt/vse/logs/vseinitconfig.log. Review the output of this command toensure there are no errors.
IMPORTANT: If you are upgrading from a previous version of the VSE ManagementSoftware, thevseinitconfig command migrates any product licenses that were previouslyinstalled or scanned to the HP SIM License Manager database. Review the licensinginformation in the log file to make sure that it is correct. You may need to adjust the numberof licensed cores using the vselicense command. For more information about migratingprevious licenses to the new license model, see vselicense(1M) and the VSE ManagementSoftware Version 4.0 Getting Started Guide.
3. When vseinitconfig finishes, you are prompted to restart HP SIM. Type “y” and pressEnter to restart HP SIM.
4. (Optional) Execute the command catman to make sure that the VSE Management Softwaremanpages can be listed by keyword using man -k.
Install the Software on the CMS 37
IMPORTANT: If you are reinstalling or updating an existing installation, you might have alreadyperformed the steps in the following sections. However, you might need to repeat some of thesesteps after reinstallation or upgrade. In particular, see “Configure VSE Management Software”(page 47). You need to repeat the postinstallation configuration steps listed there, includinglicense management and Application Discovery certificate exchange.
Start and Configure HP SIMAfter installation, use Procedure 3-8 to start HP SIM and run the First Time Wizard to finish theconfiguration process.Procedure 3-8 Start HP SIM and The First Time Wizard1. Start a Web browser and make sure that it is not configured to block pop-up windows. Direct
your web browser to the following URL:http://server:280
where server is the host name of your CMS.2. When launched for the first time after a new installation, HP SIM automatically displays
the First Time Wizard. You can also run this wizard manually by selecting Options→FirstTime Wizard... from the HP SIM menu bar.
NOTE: You can view HP SIM help for this or any other window by clicking the buttonin the upper right corner of the window.
3. Proceed through the screens of the First Time Wizard as follows:a. Introduction screen: Click Next to continue.
b. WBEM screen: The VSE Management Software uses WBEM connections to obtaininformation from the managed systems. You must establish common WBEM credentialson the CMS and on the managed systems to allow authenticated access to WBEM data.For more information, see “Prepare for Installation”. When you have finished configuringthe WBEM settings, click Next to continue.
c. SNMP screen: Configure the SNMP community name that is appropriate for yourorganization, or use the default value provided. Click Next to continue.
d. Discovery screen: Discovery is the process of finding and identifying systems in themanagement domain so that they can be managed from the CMS by HP SIM. There aretwo discovery modes: automatic and manual. If you want discovery to be scheduledon an automatic basis, select Schedule and specify how often discovery should run.Whether or not you configure automatically scheduled discovery, run the discoveryprocess manually as soon as you are finished with the First Time Wizard. You can rundiscovery manually by selecting Options→Discovery... from the HP SIM menu barand then clicking Run Now.In either automatic or manual mode, you can specify IP ranges for a ping sweep(detection of systems by their response to a networkping), or you can specify individualsystems by name or IP address. HP SIM uses WBEM, SNMP, SSH and SMH protocolsfor system identification. For example, HP SIM attempts to contact the WBEM nPartition,virtual partition, and virtual machine providers on a given system to determine thesystem type. HP SIM populates its system database with this information and createsrelationship information such as the parent/child association between a VM Host andits virtual machines.Virtualization Manager uses both the system and relationship information whendisplaying VSE resources. Until you install the VSE agent software on the managed
38 Installation
nodes, little information is available. For information about installing VSE agent software,see “Install VSE Agent Software on Managed Systems” (page 40).When you have finished configuring the discovery settings, click Next to continue.
e. Users screen: On 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 authorizedcapabilities of each user. For more information, see the HP Systems Insight Manager 5.2Installation and Configuration Guide for HP-UX.It is not necessary to set up any users now. After you complete the First Time Wizard,you must configure user authorizations to allow access to the VSE Management Softwaretools. This topic is discussed in the VSE Management Software Version 4.0 Getting StartedGuide. Click Next to continue.
f. E-mail screen: If you do not want email notification of HP SIM events from the CMS,skip this step. Otherwise, specify the SMTP host and authentication (if required) to beused for email notifications. On an HP-UX CMS, you can usually use the CMS as theSMTP host. Also provide an email address to be used as the “From” portion of the emailheader. HP recommends the name hpsim@hostname. Click Next to continue.
g. Event Handling screen: If you do not want alerts from the CMS, skip this step.Otherwise, specify which events will cause alerts to be sent, and the email address towhich alerts should be sent. Click Next to continue.
h. Summary screen: Review your selections and click Finish to continue, or clickPrevious to go back and correct your earlier selections.
i. Finish screen: To exit the First Time Wizard, click Close.
4. 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 automaticallyscheduled discovery in the First Time Wizard. Select Options→Discovery... from the HPSIM menu bar, then click Run Now.
Start and Configure HP SIM 39
Install VSE Agent Software on Managed SystemsThe VSE Management Software relies on WBEM providers and other agent software installedon the managed systems. You can install these products on managed systems from the CMSusing the Configure VSE Agents menu.
Configure Secure Shell (OpenSSH)In order to install software from the CMS to managed systems, OpenSSH must be installed onthe managed systems and configured for use by HP SIM. Use Procedure 3-9 to configure OpenSSHfor HP SIM. This step can also be done from the command line using the mxagentconfigcommand. For more information, see mxagentconfig(1M).
NOTE: Preinstallation steps are required for Linux and Microsoft Windows managed systems.For more information, see the following sections:• “Preinstallation Steps for Linux Managed Systems” (page 32)• “Preinstallation Steps for Microsoft Windows Managed Systems” (page 33)
Procedure 3-9 Configure OpenSSH for HP Systems Insight Manager1. Select the systems to configure, and choose Configure→Configure or Repair Agents...
from the HP SIM menu. The Configure or Repair Settings page is displayed.2. Log in using a privileged account that is available on each of the selected managed systems.
Without privileged SSH access, you cannot create monitored workloads on managed systems.
IMPORTANT: The privileged account used for SSH access requires a valid shell and logindirectory on HP-UX managed systems. It is used to log in and execute commands on themanaged system. In contrast, the account used for WBEM user access does not require loginaccess. HP recommends that you use different accounts for SSH and WBEM access. For moreinformation about configuring a WBEM user account, see “Prepare for Installation” (page 31).
3. Select Configure secure shell (SSH) access. For details about this screen, see the HP SIMonline help.
For detailed information about configuring SSH for use with HP SIM, seeo the HP white paperSecure Shell (SSH) in HP SIM 5.0, available from the Information Library link at http://hp.com/go/hpsim.
Install HP-UX VSE AgentsFollow the steps in Procedure 3-10 to install the VSE agents and providers to HP-UX managedsystems from the CMS. This procedure allows you to select the individual agent software thatyou want to install. If you prefer to install the agent software manually, see “Alternate Procedurefor Manual Installation of Agent Software” (page 42).
IMPORTANT: When you upgrade an existing version of the gWLM agent, processes placed ina PSET or FSS group by gwlmplace are moved to the default PSET or default FSS group. Youcan avoid this behavior by placing applications in workloads when you define the workloads.For more information, see gwlmplace(1M).
Procedure 3-10 Install HP-UX Managed System Software from the CMSPrerequisite OpenSSH must be installed on the managed systems and configured for use byHP SIM. For more information, see “Configure Secure Shell (OpenSSH)”.1. Select your HP-UX managed systems, then select Configure→Configure VSE
Agents→Install HP-UX VSE Agents... from the HP SIM menu. Click Run Now to start theinstallation. A table of available HP-UX agent software is displayed, with default selectionsalready applied.
40 Installation
2. You can accept the defaults or modify the selections. Not all products need to be installedon all systems. For example, it is not necessary to install the Virtual Machines Providerexcept on VM Host servers and virtual machines. However, there is no harm in installingthe agents and providers on managed systems that do not require them. To select or clearall software choices, check the box in the table header. To select or clear a specific component,check the box next to that component.
IMPORTANT: Some of the products available for selection require the managed system tobe rebooted after installation. This is indicated in the Requires Reboot? column. If youselect a product that requires a reboot, the managed system is automatically rebooted whenthe software installation completes. The default selections do not include any software thatrequires a reboot.
3. When you have selected the software that you want to install, click OK. The selected softwarewill be installed on each of the managed systems that were previously selected. HP SIMdisplays the progress and results of the installation in the Task Results screen. Review theoutput for error messages before continuing.If any of the selected software requires a reboot after installation, the managed system isrebooted automatically.
4. Select the systems that you want to manage with gWLM, and selet Configure→ConfigureVSE Agents→Start gWLM Agent... from the HP SIM menu bar to start the gWLM agenton the selected systems.
5. (Optional) To manage systems with Application Discovery, you must exchange certificateswith the CMS. You can perform this step now or after installation.is complete. For instructionsfor completing this step, see “Complete the Certificate Exchange for Application Discovery”in the VSE Management Software Version 4.0 Getting Started Guide.
6. Run the HP SIM discovery process again. This will allow HP SIM to retrieve additionalinformation about the systems where agent software has been installed. SelectOptions→Identify Systems... from the HP SIM menu, then click Run Now.
Install Linux VSE AgentsFollow the steps in Procedure 3-11 to install the VSE agents and providers to Linux managedsystems from the CMS. This procedure allows you to select the individual agent software thatyou want to install. If you prefer to install the agent software manually, see “Alternate Procedurefor Manual Installation of Agent Software” (page 42).Procedure 3-11 Install Linux Managed System Software from the CMSPrerequisite OpenSSH must be installed on the managed systems and configured for use byHP SIM. For more information, see “Configure Secure Shell (OpenSSH)” (page 40).1. Select your Linux managed systems, then select Configure→Configure VSE Agents→Install
Integrity Linux Agents... from the HP SIM menu bar. Click Run Now to start the installation.A table of available Linux agent software is displayed, with default selections already applied.
2. You can accept the defaults or modify the selections. To select or clear all software choices,check the box in the table header. To select or clear a specific component, check the box nextto that component.
3. When you have selected the software that you want to install, click OK. The selected softwareis installed on each of the managed systems that were previously selected. HP SIM displaysthe progress and results of the installation in the Task Results screen. Review the output forerror messages before continuing.
4. Run the HP SIM discovery process again. This allows HP SIM to retrieve additionalinformation about the systems on which agent software has been installed. SelectOptions→Identify Systems... from the HP SIM menu bar, then click Run Now.
Install VSE Agent Software on Managed Systems 41
Install Windows VSE AgentsFollow the steps in Procedure 3-12 to install the VSE agents and providers to Microsoft Windowsmanaged systems from the CMS. This procedure allows you to select the individual agent softwarethat you want to install. If you prefer to install the agent software manually, see “AlternateProcedure for Manual Installation of Agent Software” (page 42).Procedure 3-12 Install Windows Managed System Software from the CMSPrerequisite OpenSSH must be installed on the managed systems and configured for use byHP SIM. For more information, see “Configure Secure Shell (OpenSSH)” (page 40).1. Select your Windows managed systems and select Configure→Configure VSE
Agents→Install Windows VSE Agents... from the HP SIM menu bar. Click Run Now tostart the installation. A table of available Windows agent software is displayed, with defaultselections already applied.
2. You can accept the defaults or modify the selections. To select or clear all software choices,check the box in the table header. To select or clear a specific component, check the box nextto that component.
3. When you have selected the software that you want to install, click OK. The selected softwarewill be installed on each of the managed systems that were previously selected. HP SIMdisplays the progress and results of the installation in the Task Results screen. Review theoutput for error messages before continuing.
NOTE: Windows systems must be rebooted after installation of the VSE agent software.
4. Run the HP SIM discovery process again. This allows HP SIM to retrieve additionalinformation about the systems on which agent software has been installed. SelectOptions→Identify Systems... from the HP SIM menu, then click Run Now.
Alternate Procedure for Manual Installation of Agent SoftwareIf you do not want to use the procedures described above, you can selectively install the agentsrequired for managed systems from the depots and installation packages that are installed inthe depot directory on the CMS with the VSE Management Software. On an HP-UX CMS, thisdirectory is /var/opt/vse/depot. Use Procedure 3-13 to manually install the agent software.Procedure 3-13 Manual Installation of HP-UX Agents1. Copy the desired depot files (file.depot) from the depot directory on the CMS to
/var/tmp on the managed system. Or, if you are using a Software Distributor depot server,copy the depot files to the depot server. To determine which depots you need, and whichbundles within those depots should be installed, use the swlist command, as shown inExample 3-1. If you are using a Software Distributor depot server, replace the source partof the command with the server location of the depot.
Example 3-1 List the Bundles in the Utilization Provider Depot
# /usr/sbin/swlist -s /var/tmp/up.depot -a software_spec
42 Installation
2. Install the desired bundles from the depots using the swinstall command, as shown inExample 3-2. In this example, UtilProvider is the bundle being installed from theup.depot file. If you are using a Software Distributor depot server, replace the source partof the command with the server location of the depot.
Example 3-2 Install the Utilization Provider on an HP-UX System
# /usr/sbin/swinstall -s /var/tmp/up.depot UtilProvider
Enter the corresponding swinstall command for each of the depots that you want toinstall.
Procedure 3-14 Manual Installation of Integrity Linux Agents1. Copy the desired tar files (file.tar) from the depot directory on the CMS to /var/tmp
on the managed system.2. Copy the agent installation script install-agent.sh from the CMS to /var/tmp on the
managed system. On an HP-UX CMS, this script is located in /opt/vse/lbin.3. Install the agent software using the install-agent.sh script, as shown in the following
example.
Example 3-3 Install the Utilization Provider on a Linux System
# cd /var/tmp# sh install-agent.sh hp-utilprovider.tar
4. Repeat the previous step for each of the agents that you want to install.Procedure 3-15 Manual Installation of Windows Agents1. Copy the desired Windows install files (file.cab) from the depot directory on the CMS
to C:\ on the managed system.2. Copy the agent installation script install-agent.bat from the CMS to C:\ on the
managed system. On an HP-UX CMS, this script is located in /opt/vse/lbin.3. Install the agent software using the install-agent.bat script, as shown in the following
example.
Example 3-4 Install the Utilization Provider on a 32–bit Windows System
C:\> c:C:\> cd \C:\> install-agent WMIUtilProvider.cab
4. Repeat the previous step for each of the agents that you want to install.
After Upgrading from a Previous VersionHP SIM Upgrade If you upgraded HP SIM, follow any postinstallation instructions describedin the HP SIM documentation. Make sure that you have installed all required HP-UX or applicationpatches.Stop and restart HP SIM by executing the following commands on the CMS:# /opt/mx/bin/mxstop# /opt/mx/bin/mxstart
It might take several minutes for HP SIM to restart completely. To verify that HP SIM has finishedrestarting, execute the following command on the CMS:# /opt/mx/bin/mxuser -lt
After Upgrading from a Previous Version 43
This command lists the users defined in HP SIM. If an error is displayed, wait several minutesand try the command again.Verify gWLM Communication and Redeploy Your SRDs If you are using gWLM, execute thefollowing command on the CMS to verify that the CMS is configured properly and cancommunicate with installed agents:# /opt/gwlm/bin/gwlm list
If the output of this command lists various policies, the CMS is configured properly. If not, errormessages are displayed. Wait a few seconds and try the command again. If you still get errors,perform the actions recommended in the error messages.Once communication is verified, redeploy any SRDs. In addition, for partition-based SRDs, followthe procedure described next.Rediscover Partition-Based SRDs If you are using gWLM, and you have upgraded the gWLMagents in the partitions from gWLM A.02.xx to gWLM A.04.00.07, you cannot add other partitionsin the same complex to the SRD if you have either of the following types of partition-based SRDs:• A Virtual Partition Srd Inside An Npartition• An nPartition SRD using Instant CapacityReestablish the SRD using Procedure 3-16.Procedure 3-16 Rediscover Partition-Based SRDs1. With the SRD deployed, rediscover the SRD. For a virtual partition SRD, execute the following
command:# /opt/gwlm/bin/gwlm discover --type=vpar \ --file=/tmp/myfile.xml hosts
For an nPartition-based SRD, execute the following command:# gwlm discover --type=npar \ --file=/tmp/myfile.xml hosts
In these commands, replace hosts with a space-separated list of the partitions in the SRD.2. Make the following adjustments to /tmp/myfile.xml, as described in gwlmxml(4):
• Ensure that the mode attribute for the sharedResourceDomain element is set to thedesired value (Managed or Advisory):mode="Managed"
• Ensure that the interval attribute for the sharedResourceDomain element is setto the desired value:interval="x"
• Ensure that the ticapMode attribute for the sharedResourceDomain element is setto all if gWLM should allocate Temporary Instant Capacity (TiCAP) when needed:ticapMode="all"
• Ensure that theworkloadReference entries in the compartment definitions are correct,and adjust the names in the workload definitions themselves. For example, you mightsee “host.OTHER.2” instead of “host.OTHER”.
3. Import the file to re-create the SRD:# gwlm import
Because the SRD was already deployed, the new SRD definition is deployed on import,taking the place of the original SRD.
Verify Capacity Advisor Data Migration If you are using Capacity Advisor, use the commandcapprofile -lt to verify that previously collected historical data has been migrated to thenew VSE Management Software database. This command lists the workload profiles and thetime range of the data stored in the database. For more information, see capprofile(1M).
44 Installation
Restore Scheduled Capacity Advisor Tasks If you are using Capacity Advisor, restore each ofyour automatically scheduled Capacity Advisor data collection tasks using Procedure 3-17.Procedure 3-17 Restore Scheduled Capacity Advisor Tasks1. Select Tasks & Logs→View All Scheduled Tasks from the Capacity Advisor menu bar.2. Select the task from the list Collect Capacity Advisor Data.3. Click Edit.4. Click Schedule.5. Clear the Disable this task check box.6. Click Done.7. Verify that the task you just edited is in the list and now shows Periodic in the Schedule
column, along with the date of the next collection.
Postinstallation Update of gWLM AgentsIf you update the VSE Management Software on the CMS to version A.04.00.07 without updatingthe gWLM agent software on some of your managed systems, update those agents as soon as itis convenient to do so. Use Procedure 3-18 to update the agents.Procedure 3-18 Update gWLM Agents After Updating the CMS1. Undeploy the SRDs that are managing systems where agents are going to be upgraded. Stop
using the existing version of gWLM, including the command-line interface. You can continuerunning the gWLM daemons (gwlmcmsd and gwlmagent) and the WBEM service andprovider daemons.
2. Install and start the agents as described in “Install VSE Agent Software on Managed Systems”(page 40).
3. For any partition-based SRDs, follow the steps described in “Rediscover Partition-BasedSRDs” (page 44). For SRDs based on PSETs, FSS groups, or virtual machines, redeploy thoseSRDs.
Postinstallation Update of gWLM Agents 45
46
4 Configure VSE Management SoftwareAfter installation, you must perform additional steps to configure the VSE Management Softwarefor your environment. For a description of these steps, see the VSE Management Software Version4.0 Getting Started Guide. The latest version of this document can be downloaded from http://docs.hp.com/en/vse.html.
IMPORTANT: The VSE Management Software does not operate correctly until you completethese postinstallation configuration steps. You must perform these steps even when you reinstallor update an existing installation.
47
48
A Command Reference
49
vseinitconfig(1M)NAMEvseinitconfig -- Configure or unconfigure the VSE Management Software
SYNOPSISPath (HP-UX): /opt/vse/bin/vseinitconfigPath (Windows): install-path\bin\vseinitconfigvseinitconfig [ -a | --initconfig ] [ -F | --clobber ] [ -q | --quiet ][-x restart_sim= { true | false }](Initial software configuration)vseinitconfig { -r | --unconfig } [ -F | --clobber ] [ -q | --quiet ](Unconfigure software for removal)vseinitconfig { -b | --backup } { -d | --dir=path }(Backup the PostgreSQL database on HP-UX CMS)vseinitconfig { -s | --restore } { -d | --dir=path } { -F | --clobber }(Restore the PostgreSQL database on HP-UX CMS)
DESCRIPTIONThevseinitconfig command performs initial configuration of the Virtual Server Environment(VSE) Management Software on an HP Systems Insight Manager (SIM) Central ManagementServer (CMS). It can also be used to remove the existing configuration and to back up or restorethe VSE Management Software database. (Backup and restore functions are only available on aCMS running HP-UX using the PostgreSQL database.). The vseinitconfig command isinstalled with the VSE Management Software on both HP-UX and Microsoft® Windows® CMS.This command performs four different functions on the CMS, corresponding to the four syntaxoptions shown in the synopsis. With no options specified, the initial configuration function isperformed.1. Initial configuration after installing or updating the VSE Management Software on the CMS.
This includes initial configuration of HP Virtualization Manager, HP Global WorkloadManager (gWLM), and HP Capacity Advisor, as well as initialization of the VSE ManagementSoftware database.
2. Removal of the VSE Management Software menu items and actions from HP SIM andclearing of the VSE Management Software database, in preparation for removal of the VSEManagement Software.
3. Safe backup of the VSE Management Software database to protect against loss of data (ona CMS running HP-UX using the PostgreSQL database).
4. Safe restore of the VSE Management Software database from a previous backup (on a CMSrunning HP-UX using the PostgreSQL database).
OptionsThe vseinitconfig command recognizes the following options. Each option can be expressedin a long or short form.If no options are specified, the initial configuration function is performed.-a|--initconfig Perform the initial configuration of the VSE Management
Software (this is also the default function performed if nooption is specified). This action requires that HP SIM isrunning and configured with the mxinitconfigcommand. This command registers the VSE ManagementSoftware tools, toolboxes, and actions with HP SIM andinitializes the VSE Management Software database.On an HP-UX CMS, the optional --clobber or -F optioncauses an existing VSE Management Software database to
50 Command Reference
be removed without being backed up first. If that optionis not used, then an existing database will be upgradedfrom the previous version of the VSE ManagementSoftware. This does not apply to a Microsoft WindowsCMS.
NOTE: Before upgrading from a previous version of theVSE Management Software, see the VSE ManagementSoftware Version 4.0 Installation and Update Guide for HP-UXand the following description of the --restore optionfor important information.
-F|--clobber Clear any existing VSE Management Software databasewithout backing it up. For more information about howthis option affects vseinitconfig, see the descriptionsof the options -a|--initconfig and -r|--unconfig.
-q|--quiet Do not display any output. Do not prompt for HP SIMrestart after performing the initial configuration operation.You can view the console and error output in the log files.
-x restart_sim={true|false} This option selects whether to automatically restart HPSystems Insight Manager after initial configuration of theVSE Management Software. It is only applicable incombination with the initial configuration option (-a or--initconfig).Use -x restart_sim=true to restart HP SIM withoutany further prompting after all of the VSE Managementapplications are configured. There can be a delay of oneor two seconds after vseinitconfig finishes executionbefore HP SIM is ready to respond to mx... commands.Use-x restart_sim=false to return immediately afterall of the VSE Management applications are configured,without restarting HP SIM.If this option is not used, you will be prompted whetherto restart HP SIM after all of the VSE Managementapplications are configured.
-r|--unconfig Remove the installed VSE Management Software toolsfrom HP SIM. The existing database and configurationinformation will not be removed unless the optional--clobber or -F option is used.Important: The optional --clobber or -F option causesan existing VSE Management Software database to beremoved without being backed up first. If you do notperform a backup of the VSE Management Softwaredatabase before executing this command, you will lose allof your VSE Management Software data, including gWLMand Capacity Advisor configuration and historical data.
-b|--backup Back up the VSE Management Software database, includinggWLM and Capacity Advisor data, to protect against lossof data. The VSE Management Software must be initializedbefore you can perform a backup. For information aboutinitializing the VSE Management Software, see the earlierdescription of the --initconfig option.
51
NOTE: This option is only available on a CMS runningHP-UX using the PostgreSQL database.
The backup is created in the directory specified by the -dor --dir option. This directory must be initially empty ormust not yet exist.The backup created by this command contains only theVSE Management Software data. For information aboutbacking up the HP SIM database, refer to the HP whitepaper Backing up and restoring HP Systems Insight Managerdata files in an HP-UX or Linux environment, available fromthe InformationLibrary link athttp://hp.com/go/hpsim.If you are creating a backup in preparation for relocatingthe CMS, HP recommends that you first undeploy allshared resource domains (SRDs). This will make it easierto redeploy the SRDs after the CMS is moved. To ensurethat your backup includes up-to-date historic data, youshould also perform the following steps:1. If you are using gWLM to manage any SRDs, execute
the following command on the CMS:gwlm history --flush
2. If you use Capacity Advisor, execute the followingcommand on the CMS:
capcollect
-s|--restore Restore the VSE Management Software database from thebackup in the directory named by the -d or --dir option.The VSE Management Software must be initialized beforeyou can perform a restore, therefore the --clobber or -Fis also required in order to replace the database. Forinformation about initializing the VSE ManagementSoftware, see the earlier description of the --initconfigoption.
NOTE: This option is only available on a CMS runningHP-UX using the PostgreSQL database.
HP SIM must be stopped when the restore operation isperformed. To stop HP SIM, execute the commandmxstopon the CMS. Use mxstart to restart HP SIM after therestore operation is finished.
52 Command Reference
NOTE: If the CMS or managed systems have beenmodified between the backup and the restore (for example,changing hostnames or adding or removing processors),gWLM might not function as expected after the restore.
NOTE: You cannot restore a backup that was createdwith an older version of the VSE Management Software.The structure of the database used by older versions of theVSE Management Software is incompatible with the currentversion. If you have not yet installed the current versionof the software and you intend to restore from an olderversion backup, perform the restore first. Then install andinitialize the new software. The initialization processupgrades the already-restored database to the new format.If you have already updated the software and you need torestore from an older version backup, follow these steps:1. Remove the VSE Management Software. For
instructions, see the VSEManagement Software Version4.0 Installation and Update Guide for HP-UX.
2. Reinstall the older version of the VSE ManagementSoftware according to the installation instructionspublished with that release.
3. Restore the VSE Management Software database fromthe older version backup.
4. Install the VSE Management Software versionA.04.00.07. For installation instructions, see the VSEManagement Software Version 4.0 Installation andUpdateGuide for HP-UX.
5. Initialize the software as described in the earlierdescription of the --initconfig option. Thisupgrades the restored database to the new format.
Removing and Reinstalling VSEIf the VSEMgmt product is removed and reinstalled, collection of Capacity Advisor data canmiss some data on the CMS. To avoid this, back up the VSE Management Software databasebefore removing VSE, and restore the database after it is reinstalled.
RETURN VALUES0 The command completed successfully; no errors were detected.1 An error occurred and the command did not complete successfully.
EXAMPLESThe following command performs initial configuration of the VSE Management Software,performs a backup of the VSE Management Software database if a previous version exists,upgrades the database if necessary, and prompts whether to restart HP SIM after configurationis complete.vseinitconfig -a
The following command performs initial configuration of the VSE Management Software, removesany existing VSE Management Software database without backing it up, and restarts HP SIMautomatically:vseinitconfig -a -F -x restart_sim=true
Here is the same command, using the long form of options:vseinitconfig --initconfig --clobber -x restart_sim=true
53
The following command backs up the VSE Management Software database to the directory/var/backups/2008-04-01:vseinitconfig -b -d /var/backups/2008-04-01
Here is the same command, using the long form of options:vseinitconfig --backup --dir=/var/backups/2008-04-01
The following command performs the unconfigure operation, removing the VSE ManagementSoftware tools from HP SIM. The --clobber option causes the database information to beremoved without making a backup:vseinitconfig --unconfig --clobber
You can mix the short and long form options. For example, to restore the VSE ManagementSoftware database from the directory /var/backups/2008-04-01, you can use the followingcommand:vseinitconfig --restore -d /var/backups/2008-04-01 -F
AUTHORSvseinitconfig was developed by Hewlett-Packard Company.
FILESThe console (non-error) output from the vseinitconfig commandis written to the followinglog file:HP-UX: /var/opt/vse/logs/vseinitconfig_output.logWindows: install-path\logs\vseinitconfig_output.log
Errors and exceptions reported by vseinitconfig, are written to the following log file:HP-UX: /var/opt/vse/logs/vseinitconfig.logWindows: install-path\logs\vseinitconfig.log
SEE ALSOgwlmcmsd(1M), gwlmsslconfig(1M), mxinitconfig(1M), mxstart(1M), mxstop(1M), mxtoolbox(1M),mxuser(1M), VSE Management Software Version 4.0 Installation and Update Guide for HP-UX, VSEManagement Software Version 4.0 Getting Started Guide
54 Command Reference
B Removing the VSE Management SoftwareUse Procedure B-1 to completely remove the VSE Management Software from an HP-UX CMS.Procedure B-1 Remove the VSE Management Software1. Make sure that HP SIM is running.2. Use gWLM to undeploy all deployed SRDs.3. Delete all monitored workloads.4. Stop the gWLM agent daemon, if it is running on the CMS, by executing the following
command:# /opt/gwlm/bin/gwlmagent --stop
5. Remove the existing VSE Management Software configuration and database by executingthe following command:# /opt/vse/bin/vseinitconfig -r -F
6. Remove the VSE Management Software by executing the following command:# /usr/sbin/swremove VSEMgmt T2743AA gWLM-Agent \ vseAssist AppDiscCMS AppDiscAgent PRMSIMTools
7. Remove log files and other application files by executing the following commands:# rm -rf /opt/vse /etc/opt/vse /var/opt/vse# rm -rf /opt/gwlm /etc/opt/gwlm /var/opt/gwlm# rm -rf /opt/amgr /etc/opt/amgr /var/opt/amgr# rm -rf /opt/hpwebadmin/webapps/vse.war
55
56
Index
Aagent, 21, 38, 39
installation, 40ssh requirement, 24
Bbackup VSE database, 35Bastille, 27
CMS configuration, 27managed systems configuration, 28
books, 13
CCapacity Advisor
Java requirements, 20ssh requirement, 24WBEM requirement, 24
Central Management Server (see CMS)CMS
as managed system, 20requirements, 17, 18, 20
comments to HP, 14compartment software, 26
Ddatabase, 18, 19, 34, 36
backup, 35restore, 35
discovery (see HP SIM, discovery)documentation, 9
FFair-Share Scheduler (see FSS group)feedback to HP, 14firewall, 27
CMS configuration, 27managed systems configuration, 28
FSS group, 26, 40, 45
GGlobal Workload Manager (see gWLM)gWLM
agent installation, 40compartment software, 26Java requirements, 20requirements, 18
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 Integrity VM (see Integrity VM)
HP SIM, 24, 32discovery, 38, 39First Time Wizard, 38installation, 31, 36launching, 38supported versions, 17
HP Systems Insight Manager (see HP SIM)HP-UX, 21
patches, 17, 21, 26, 31
Iinstallation
CMS, 36managed systems, 40
Integrity VM, 23, 25
JJava, 20
LLDAP, 24, 32Linux, 18, 21Linux managed systems, 32
Mmanaged systems
installing VSE agent software, 40Linux, 32Microsoft Windows, 33requirements, 21, 24
manpages, 10manuals, 9Microsoft Windows, 18, 21Microsoft Windows managed systems, 33
Nnetwork
communication protocols used by VSE ManagementSoftware, 27
firewalls, 27NIS, 32
OOpenSSH (see ssh)OpenSSL, 25operating systems
CMS, 18managed systems, 21
Oracle, 18, 19, 36
Ppatches, 17, 21, 26ping sweep, 38PostgreSQL, 18, 19processor set (see PSET)provider (see agent)
57
PSET, 26, 40, 45
Rrelease notes, 31requirements, 17
CMS, 18, 20firewalls, 27gWLM, 18, 26managed systems, 21, 24maximum configuration, 17
restore VSE database, 35root, 32
SSecure Shell (see ssh)security, 32service and support, 14Serviceguard, 25Shared Resource Domain (see SRD)SIM
documentation, 9SNMP, 38SRD, 17, 44, 45, 52, 55
undeploy before upgrade, 35ssh, 24, 27, 33, 34, 38, 40
configuring on managed systems, 40SSL, 25swinstall command, 36, 37Systems Insight Manager (see HP SIM)
Uuser authorization, 39
Vvirtual machine, 25, 38virtual partition
provider, 23Virtual Server Environment (see VSE)Virtualization Manager, 38
ssh requirement, 24WBEM requirement, 24
VM (see Integrity VM)VM Host, 25, 38VM Provider
required version, 23vPar Provider
required version, 23vPars (see virtual partition)VSE
books, 13documentation, 9
VSE agent software (see agent)vseinitconfig command, 37
WWBEM, 38
authentication, 32required version, 24
WBEM provider (see agent)
websites, 10white papers, 9
58 Index
