Professional Documents
Culture Documents
Copyright 2006-2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
Table of Contents
1 Introduction......................................................................................................................7 2 System requirements.......................................................................................................9
HP Systems Insight Manager.................................................................................................................9 Compatibility with HP-UX Bastille and other network firewalls..........................................................9 Additional requirements in the release notes and support matrix........................................................9
3 Installation.....................................................................................................................11
Overview checklist for installing ID-VSE for Integrity.......................................................................11 Overview checklist for upgrading ID-VSE for Integrity.....................................................................11 Prepare for installation.........................................................................................................................12 Preinstallation steps for Linux managed systems...........................................................................13 Preinstallation steps for Microsoft Windows managed systems....................................................14 Before upgrading from a previous version...........................................................................................15 Install the software on the CMS............................................................................................................16 Start and configure HP SIM..................................................................................................................18 Install Insight Dynamics agent software and configure managed systems.........................................21 Using managed system setup wizard.............................................................................................21 Privilege elevation...........................................................................................................................21 Alternate procedure for manual installation of agent software......................................................21 After upgrading from a previous version............................................................................................23 Postinstallation update of gWLM agents..............................................................................................24 Preparing a Red Hat Linux managed system.......................................................................................24 Preparing a ProLiant SUSE Linux managed system............................................................................25
Reference pages installed with agent software on managed systems.......................................34 Reference page installed on cell-based complexes....................................................................35 Reference pages installed on systems running HP Integrity Virtual Machines........................35 Selected HP Systems Insight Manager software reference pages..............................................35
A Command reference....................................................................................................37
vseinitconfig(1M)..................................................................................................................................38
Table of Contents
List of Tables
3-1 3-2 Checklist for installing ID-VSE for Integrity on an HP-UX CMS................................................11 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS..............................................12
List of Examples
3-1 3-2 3-3 Install the Utilization Provider on an HP-UX system...................................................................22 Install the HPVM Provider on a Red Hat Enterprise Linux 4 (Integrity) system.........................22 Install the Utilization Provider on a 32bit Windows system......................................................22
List of Examples
1 Introduction
This document describes the installation and configuration of HP Insight Dynamics - VSE suite for Integrity (ID-VSE for Integrity) . It is intended to be used by Insight Dynamics system administrators, Insight Dynamics application administrators, capacity planners, and other technical professionals involved with data center operations, administration, and planning. An understanding of HP-UX system administration concepts and procedures is assumed. Installing, updating, and configuring ID-VSE for Integrity involves performing the following tasks: Checking hardware and software requirements for ID-VSE for Integrity. Installing ID-VSE for Integrity on the CMS. Upgrading ID-VSE for Integrity from previous versions of the software. Installing agent software and WBEM providers on managed systems. Performing post-install or post-upgrade configurations of ID-VSE for Integrity. Backing up and restoring the ID-VSE for Integrity database. For an overview of ID-VSE for Integrity and key Insight Dynamics concepts and terminology see the HP Insight Dynamics 6.2 Getting Started Guide. For detailed information about supported hardware and software, see HP Insight Software 6.2 Support Matrix.
2 System requirements
The following sections provide a summary of the hardware and software requirements of ID-VSE for Integrity version 6.2 installed on a CMS running HP-UX. For detailed information about supported hardware and software, including requirements for a CMS running HP-UX or Microsoft Windows, see the HP Insight Software 6.2 Support Matrix.
10
3 Installation
Install HP SIM and ID-VSE for Integrity using Table 3-1. IMPORTANT: Starting with VSE Management Software version 4.0 (A.04.00.07.xx), licenses for ID-VSE for Integrity are managed in the HP SIM License Manager database on the CMS. When you upgrade an HP-UX CMS that has a previous version of ID-VSE for Integrity installed, any product licenses that were previously installed or scanned are automatically migrated to the License Manager database. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide.
IMPORTANT: The software includes a 90-day trial license for HP 9000 and HP Integrity managed systems. For details about ID-VSE http://h20293.www2.hp.com/portal/ for Integrity licenses, see the HP Insight Dynamics 6.2 Getting Started swdepot/ displayProductInfo.do?productNumber=vse Guide. Prepare for installation (page 12) Prepare for ID-VSE for Integrity installation by installing the required software and patches, establishing common WBEM user credentials on the CMS and managed systems, and completing preinstallation steps for Linux and Microsoft Windows managed systems. Install HP SIM and ID-VSE for Integrity on the CMS. If HP SIM was upgraded, launch HP SIM and run the First Time Wizard and the Discovery processes. Install the WBEM providers and other agent software on your managed systems. Configure ID-VSE for Integrity for your environment. IMPORTANT: ID-VSE for Integrity does not operate correctly until you complete these postinstallation configuration steps. You must perform these steps even when you are reinstalling or updating an existing installation. Install the software on the CMS (page 16) Start and configure HP SIM (page 18) Install Insight Dynamics agent software and configure managed systems (page 21) Configure ID-VSE for Integrity (page 27)
11
Table 3-2 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS
Task Make a backup of the ID-VSE for Integrity database. Perform the upgrade preinstallation steps. Upgrade HP SIM and ID-VSE for Integrity on the CMS. If HP SIM was upgraded, launch HP SIM and run the First Time Wizard and the Discovery processes. Information Appendix B (page 43) Before upgrading from a previous version (page 15) Install the software on the CMS (page 16) See Start and configure HP SIM (page 18).
As needed, update the WBEM providers and other agent software See Install Insight Dynamics agent on your managed systems. software and configure managed systems (page 21). Perform post-upgrade steps. After upgrading from a previous version (page 23)
The following setting must be enabled in your current zone: Internet OptionsSecurityCustom LevelMiscellaneousAllow script-initiated windows. This setting is enabled by default for the medium-low security level such as the local intranetzone. Establish common WBEM credentials on the CMS and on the managed systems to allow authenticated access to WBEM data. ID-VSE for Integrity uses WBEM connections to obtain information from the managed systems. To avoid having to maintain multiple WBEM user accounts and passwords, HP recommends that you use one of the following WBEM authentication models: Global Sign-In Credentials Global credentials apply to all systems and enable you to configure default, system-wide, protocol-wide credentials. To set global sign-in credentials select OptionsSecurityCredentialsGlobal Credentials from the HP SIM menu.. You must enter root (or Administrator) level user credentials for the sign-in credentials to be used by the Configure or Repair Agents feature. To list the current credentials for a system, select OptionsSecurityCredentialsSystem Credentials from the HP SIM menu.. WBEM Certificate-Based Authentication You can configure WBEM authentication for a single system or a selected set of systems by selecting OptionsSecurityCredentialsSystem Credentials from the HP SIM menu and using the advance settings WBEM/WMI tab. To authenticate through a certificate instead of using
12
Installation
a WBEM user account and password, select Use certificate instead. Online help for this option is available in HP SIM. Online help for certificates in general can be found in the HP SIM help system under the Networking and Security topic. NOTE: On all HP-UX managed systems, HP WBEM Services for HP-UX version A.02.05 or later is required in order to use certificate-based WBEM authentication. For more information about WBEM security configuration in HP SIM, see the HP white paper Understanding HP SIM 5.3 Security, available from the Information Library link at http:// www.hp.com/go/hpsim.
6. 7.
b.
c.
OpenSSH on Linux managed systems must be configured for use by HP SIM. Normally you can use the same procedure that is used to configure OpenSSH for HP SIM on HP-UX managed systems, as described in Install Insight Dynamics agent software and configure managed systems (page 21). However, if you are using SUSE Linux Enterprise Server 9, you must first manually configure OpenSSH to use password authentication.
Prepare for installation 13
IMPORTANT: SUSE Linux Enterprise Server 9 ships with SSH configured to use PAM authentication instead of password authentication. Password authentication is required in order for the mxagentconfig to configure OpenSSH for use by HP SIM. On managed systems running SUSE Linux Enterprise Server 9, change to password authentication using Procedure 3-2. Procedure 3-2 Configure SUSE Linux for password authentication 1. Configure the following lines in /etc/ssh/sshd_config on the managed system:
PasswordAuthentication yes #UsePAM yes
2. 3.
Retrieve the process ID of the running sshd from the file /var/run/sshd.pid. Restart sshd by executing the following command:
# kill -SIGHUP pid
where node-hostname is the name of the system as it is known by HP SIM. If the system administrator user account on your managed system is not Administrator, substitute your administrator user name in the preceding command. You can use multiple -n options to perform this operation on more than one managed system.
14
Installation
NOTE: This step can be performed within HP SIM by selecting the managed systems to configure, then selecting ConfigureConfigure or Repair Agents... from the HP SIM menu bar. On the Configure or Repair Settings page, select Configure secure shell (SSH) access. 4. If you are using Partition Manager to manage Windows systems, you must also create a user account named root on those Windows systems. Partition Manager uses this user name for remote execution of nPartition commands through OpenSSH. Add this user to the Administrators group in Windows, then add this user to OpenSSH using the sshuser command. To configure remote connections from the CMS using the root account, execute the following command on the CMS:
# mxagentconfig -a -n node-hostname -u root -p root-password
OpenSSH is now configured for connections from the CMS (with host-based authentication), using either the Administrator or root account. Partition Manager uses the root account for remote command execution.
2.
a. b. c. d. e. f. g. 3. 4. 5.
Select Tasks & LogsView All Scheduled Tasks from the Capacity Advisor menu bar. Select the task from the list Collect Capacity Advisor Data. Click Edit. Click Schedule. Check the Disable this task check box. Click Done. Verify that the task you just edited is in the list and now shows Task is Disabled in the Schedule column.
Log out of HP SIM. (Optional) Use the capcollect command to collect the latest Capacity Advisor data into the ID-VSE for Integrity database. For more information, see capcollect(1M). Make a Backup Make a backup of your existing ID-VSE for Integrity database. You can use this backup if you need to revert to the older version of the software. With this backup, you can restore your current configuration after reverting to the older version of the software. You cannot restore this backup after version A.6.2.0.* is installed. Previous versions of ID-VSE for Integrity used a database format that is incompatible with version A.6.2.0.*. For more information about backing up and restoring the ID-VSE for Integrity database and reverting to a backup from a previous version of the software, see vseinitconfig(1M). This manpage is included in this manual in Appendix A (page 37). For information about backing up the HP SIM database, refer to the HP white paper Backing up and restoring HP Systems Insight Manager data files in an HP-UX or Linux environment, available from the Information Library link at http://www.hp.com/go/hpsim.
6.
If you are upgrading to a new version of HP SIM, follow any upgrade preparation instructions provided with the new version of HP SIM. In particular, note that you might need to install additional patches.
After you complete the installation steps in the following sections, see After upgrading from a previous version (page 23) for additional steps that you should perform.
16
Installation
Procedure 3-5 Install or upgrade HP SIM and ID-VSE for Integrity 1. Enter the following command on the CMS:
# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file HPSIM-HP-UX VSEMgmt
IMPORTANT:
The actions that occur after system reboot depend on whether this is a new installation of HP SIM or an upgrade to an existing HP SIM installation. New installation of HP SIM Configure HP SIM by entering the following command on the CMS:
# mxinitconfig -a
The system automatically runs mxinitconfig after the reboot. This can take up to 20 minutes to complete. Do not attempt to run any HP SIM commands or Insight Dynamics management commands, or access HP SIM through the web interface at this time. Other steps might be required to complete the HP SIM upgrade. For example, you might need to reidentify all discovered systems to complete the database upgrade for existing systems in the database.
2.
(optional) If Oracle version 10g is installed on a server in your environment, you can configure HP SIM and ID-VSE for Integrity to use an Oracle database instead of the defaultPostgreSQL database for internal data management. For specific requirements for using Oracle with ID-VSE for Integrity, see HP Insight Software 6.2 Support Matrix. To configure HP SIM for Oracle, use the following steps: a. b. Ensure that Oracle 10g is installed and running on the Oracle server. Copy the file ojdbc14.jar from your Oracle 10g server to a location on your CMS. NOTE: Do not rename this file. It must be named ojdbc14.jar when it is installed by mxoracleconfig in the next step. c. Configure HP SIM by entering the following command on the CMS:
# mxoracleconfig [-h hostname] [-n port-number] \ -d database-name -u username -p password \ -j path-to-jar-file/ojdbc14.jar [-f]
For details about the mxoracleconfig command, see mxoracleconfig(1M). d. 3. Reinitialize HP SIM by entering the following command on the CMS:
# mxinitconfig -a
Run the msswinitconf -a command to configure Insight managed system setup wizard on the CMS:
# msswinitconfig -a
IMPORTANT: On an Integrity CMS the msswinitconfig command must be executed after installing the software and configuring HP SIM, but prior to executing vseinitconfig. An error message will be issued by vseinitconfig if this step has not been performed. You must run msswinitconfig before running managed system setup wizard for the first time. 4. Configure ID-VSE for Integrity by entering the following command:
Install the software on the CMS 17
# /opt/vse/bin/vseinitconfig -a
The vseinitconfig command logs status, errors, and exceptions to the file /var/opt/ vse/logs/vseinitconfig.log. Review the output of this command to ensure there are no errors. IMPORTANT: If you are upgrading from a previous version of ID-VSE for Integrity, the vseinitconfig command migrates any product licenses that were previously installed or scanned to the HP SIM License Manager database. Review the licensing information in the log file to make sure that it is correct. You may need to adjust the number of licensed cores using the vselicense command. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide. 5. 6. When vseinitconfig finishes, you are prompted to restart HP SIM. Type y and press Enter to restart HP SIM. (Optional) Execute the command catman to make sure that the ID-VSE for Integrity manpages can be listed by keyword using man -k. Enter the following command on the CMS:
# /usr/sbin/swinstall -x autoreboot=true \ -s path-to-depot-file VSEMgmt
Procedure 3-6 Install ID-VSE for Integrity using existing installation of HP SIM 1.
2.
The vseinitconfig command logs status, errors, and exceptions to the file /var/opt/ vse/logs/vseinitconfig.log. Review the output of this command to ensure there are no errors. IMPORTANT: If you are upgrading from a previous version of ID-VSE for Integrity, the vseinitconfig command migrates any product licenses that were previously installed or scanned to the HP SIM License Manager database. Review the licensing information in the log file to make sure that it is correct. You may need to adjust the number of licensed cores using the vselicense command. For more information about migrating previous licenses to the new license model, see vselicense(1M) and the HP Insight Dynamics 6.2 Getting Started Guide. 3. 4. When vseinitconfig finishes, you are prompted to restart HP SIM. Type y and press Enter to restart HP SIM. (Optional) Execute the command catman to make sure that the ID-VSE for Integrity manpages can be listed by keyword using man -k.
IMPORTANT: If you are reinstalling or updating an existing installation, you might have already performed the steps in the following sections. However, you might need to repeat some of these steps after reinstallation or upgrade. In particular, see Configure ID-VSE for Integrity (page 27). You need to repeat the postinstallation configuration steps listed there, including license management and Application Discovery certificate exchange.
18
Installation
Procedure 3-7 Start HP SIM and The First Time Wizard 1. Start a Web browser and make sure that it is not configured to block pop-up windows. Direct your web browser to the following URL:
http://server:280
2.
where server is the host name of your CMS. When launched for the first time after a new installation, HP SIM automatically displays the First Time Wizard. You can also run this wizard manually by selecting OptionsFirst Time Wizard... from the HP SIM menu bar. NOTE: You can view HP SIM help for this or any other window by clicking the in the upper right corner of the window. button
3.
Proceed through the screens of the First Time Wizard as follows: a. Introduction Screen Click Next to continue. b. Managed Environment Specifies all operating systems managed by the CMS. The selections made here configure HP SIM to show collections, tools, and reports only for managed environments that are selected. Discovery Discovery is the process of finding and identifying systems in the management domain so that they can be managed from the CMS by HP SIM. There are two discovery modes: automatic and manual. If you want discovery to be scheduled on an automatic basis, select Schedule and specify how often discovery should run. Whether or not you configure automatically scheduled discovery, run the discovery process manually as soon as you are finished with the First Time Wizard. You can run discovery manually by selecting OptionsDiscovery... from the HP SIM menu bar and then clicking Run Now. In either automatic or manual mode, you can specify IP ranges for a ping sweep (detection of systems by their response to a network ping), or you can specify individual systems by name or IP address. HP SIM uses WBEM, SNMP, SSH and SMH protocols for system identification. For example, HP SIM attempts to contact the WBEM nPartition, virtual partition, and virtual machine providers on a given system to determine the system type. HP SIM populates its system database with this information and creates relationship information such as the parent/child association between a VM Host and its virtual machines. Virtualization Manager uses both the system and relationship information when displaying Insight Dynamics resources. Until you install the Insight Dynamics agent software on the managed nodes, little information is available. For information about installing Insight Dynamics agent software, see Install Insight Dynamics agent software and configure managed systems (page 21). When you have finished configuring the discovery settings, click Next to continue. d. Credentials: System Automatic Discovery Use the wizard to set the sign-in credentials and the SNMP credentials for the System Automatic Discovery task. Sign-in Credentials ID-VSE for Integrity uses WBEM connections to obtain information from the managed systems. You must establish common WBEM credentials on the CMS and on the managed systems to allow authenticated access to WBEM data. For more information, see Prepare for installation (page 12). SNMP Credentials Configure the SNMP community name that is appropriate for your organization, or use the default value provided. Click Next to continue.
c.
19
e. f.
Configure Managed Systems Configure managed systems as they are discovered, by configuring WBEM and WMI, SNMP, SSH access, and trust relationship. WMI Mapper Proxy To retrieve managed system information on Windows systems, enter the mapper proxy system host name and port number. The user name and password credentials must be entered on the First Time Wizard Configure Managed Systems page. This page does not appear if you are not managing Windows systems. Privilege Elevation Privilege elevation allows you to specify a non-root login on managed systems and a command that can be used to acquire root privileges as needed. See also Privilege elevation (page 21) and the HP SIM help. E-mail If you do not want email notification of HP SIM events from the CMS, skip this step. Otherwise, specify the SMTP host and authentication (if required) to be used for email notifications. On an HP-UX CMS, you can usually use the CMS as the SMTP host. Also provide an email address to be used as the From portion of the email header. HP recommends the name hpsim@hostname. Click Next to continue. Summary Displays all First Time Wizard settings with the option to modify settings or to finish the First Time Wizard.
g.
h.
i. 4.
Run the HP SIM discovery process so that you can select managed nodes for the Insight Dynamics agent software installation in the next section. Do this even if you configured automatically scheduled discovery in the First Time Wizard. Select OptionsDiscovery... from the HP SIM menu bar, then click Run Now.
20
Installation
Privilege elevation
Some tools in HP Systems Insight Manager (SIM) are defined to run as root on HP-UX, Linux, and VMware ESX managed systems. However, root logins are not allowed in many customer environments. Instead, administrators may be required to use an individual login which is authorized to acquire root permissions as needed (for example, using su or sudo). In this case, you can configure privilege elevation in HP SIM. This feature allows you to specify a non-root login on managed systems and a command that can be used to acquire root privileges as needed. Privilege elevation can be configured in HP SIM as part of the First Time Wizard or by selecting OptionsSecurityPrivilege Elevation... from the HP SIM top menu. You will need to configure the selected user login on the managed system. Additional configuration may also be needed. For example, you may need to configure SSH access using ConfigureConfigure or Repair Agents..., and you may need to configure the managed system to allow host authentication for non-root users. For more information, see the HP SIM help.
21
Procedure 3-8 Manual installation of HP-UX agents 1. Copy the desired depot files (file.depot) from the depot directory on the CMS to /var/ tmp on the managed system. Or, if you are using a Software Distributor depot server, copy the depot files to the depot server. Install the desired depots using the swinstall command, as shown in the following example. If you are using a Software Distributor depot server, replace the source part of the command with the server location of the depot. Example 3-1 Install the Utilization Provider on an HP-UX system
# /usr/sbin/swinstall -s /var/tmp/up.depot UtilProvider
2.
3. 1. 2.
Repeat the previous step for each of the agents that you want to install. Copy the desired tar files (file.tar) from the depot directory on the CMS to /var/tmp on the managed system. Copy the agent installation script install-agent.sh from the CMS to /var/tmp on the managed system. On an HP-UX CMS, this script is located in /opt/vse/lbin. On a Windows CMS it is in install-path\lbin, where install-path is the directory where Insight Dynamics is installed (by default, this directory is C:\Program Files\HP\Virtual Server Environment). Install the agent software using the install-agent.sh script, as shown in the following example. Example 3-2 Install the HPVM Provider on a Red Hat Enterprise Linux 4 (Integrity) system
# cd /var/tmp # tar -xvf hp.com-hpvm.tar # rpm -U hpvm-4.1.0-1-rhel4.ia64.rpm
3.
4. 1. 2.
Repeat the previous step for each of the agents that you want to install. Copy the desired Windows install files (file.msi) from the depot directory on the CMS to C:\ on the managed system. Install the agent software using the msiexec command, as shown in the following example. Example 3-3 Install the Utilization Provider on a 32bit Windows system
C:\> c: C:\> cd \ C:\> msiexec /I WMIUtilProvider32.msi /norestart
This command installs the agent interactively using the GUI and does not perform a reboot after installation. To install the agent with no interaction (quiet mode) and without using the GUI, use the /qn option on the msiexec command. For information about other command options, use the /help option. 3. 1. 2. Repeat the previous step for each of the agents that you want to install. Copy the file setupva.exe from the depot directory on the CMS to the managed system. Run setupva.exe on the managed system to install vseassist. Procedure 3-1 Manual installation of vseassist command on Windows systems 1
22
Installation
It might take several minutes for HP SIM to restart completely. To verify that HP SIM has finished restarting, execute the following command on the CMS:
# /opt/mx/bin/mxuser -lt
This command lists the users defined in HP SIM. If an error is displayed, wait several minutes and try the command again. Reapply demo licenses to managed systems After upgrading to ID-VSE for Integrity version 6.0 any systems that previously had a temporary demonstration (demo) license applied must be explicitly licensed after the upgrade. To apply an ID-VSE for Integrity version 6.0 demo license to a managed system, use either Insight managed system setup wizard or the vselicense -t command. See Using managed system setup wizard (page 21) or the vselicense(1M) for more details. Verify gWLM communication and redeploy your SRDs If you are using gWLM, execute the following command on the CMS to verify that the CMS is configured properly and can communicate with installed agents:
# /opt/gwlm/bin/gwlm list
If the output of this command lists various policies, the CMS is configured properly. If not, error messages are displayed. Wait a few seconds and try the command again. If you still get errors, perform the actions recommended in the error messages. Once communication is verified, redeploy any SRDs. In addition, for partition-based SRDs, follow the procedure described next. Rediscover partition-based SRDs If you are using gWLM, and you have upgraded the gWLM agents in the partitions from gWLM A.02.xx to gWLM A.6.2.0.*, you cannot add other partitions in the same complex to the SRD if you have either of the following types of partition-based SRDs: A Virtual Partition SRD inside an nPartition An nPartition SRD using Instant Capacity Reestablish the SRD using Procedure 3-12. Procedure 3-12 Rediscover partition-based SRDs 1. With the SRD deployed, rediscover the SRD. For a virtual partition SRD, execute the following command:
# /opt/gwlm/bin/gwlm discover --type=vpar \ --file=/tmp/myfile.xml hosts
2.
In these commands, replace hosts with a space-separated list of the partitions in the SRD. Make the following adjustments to /tmp/myfile.xml, as described in gwlmxml(4): Ensure that the mode attribute for the sharedResourceDomain element is set to the desired value (Managed or Advisory):
mode="Managed"
Ensure that the interval attribute for the sharedResourceDomain element is set to the desired value:
After upgrading from a previous version 23
interval="x"
Ensure that the ticapMode attribute for the sharedResourceDomain element is set to all if gWLM should allocate Temporary Instant Capacity (TiCAP) when needed:
ticapMode="all"
Ensure that the workloadReference entries in the compartment definitions are correct, and adjust the names in the workload definitions themselves. For example, you might see host.OTHER.2 instead of host.OTHER.
3.
Because the SRD was already deployed, the new SRD definition is deployed on import, taking the place of the original SRD. Verify Capacity Advisor data migration If you are using Capacity Advisor, use the command capprofile -lt to verify that previously collected historical data has been migrated to the new ID-VSE for Integrity database. This command lists the workload profiles and the time range of the data stored in the database. For more information, see capprofile(1M). Restore scheduled Capacity Advisor tasks If you are using Capacity Advisor, restore each of your automatically scheduled Capacity Advisor data collection tasks using Procedure 3-13. Procedure 3-13 Restore scheduled Capacity Advisor tasks 1. 2. 3. 4. 5. 6. 7. Select Tasks & LogsView All Scheduled Tasks from the Capacity Advisor menu bar. Select the task from the list Collect Capacity Advisor Data. Click Edit. Click Schedule. Clear the Disable this task check box. Click Done. Verify that the task you just edited is in the list and now shows Periodic in the Schedule column, along with the date of the next collection.
2. 3.
24
Installation
during RHEL installation, or install it later from your RHEL distribution media through the YaST Control Center.
2.
Remove OpenWBEM and packages that depend on OpenWBEM through the YaST Control Center or another package management application.
Procedure 3-16 Download OpenPegasus WBEM Use the following steps to download OpenPegasus WBEM packages from the HP website. 1. 2. 3. Go to http://www.hp.com/. Enter OpenPegasus WBEM Services in the product search field and click the Search button. Click the link for the OpenPegasus version specific to ID-VSE for Integrity from the resulting list of products. NOTE: The product description indicates whether the selected OpenPegasus package is specific to ID-VSE for Integrity. 4. Click the Download button to download the package.
Procedure 3-17 Install OpenPegasus WBEM After downloading the OpenPegasus package, install it and start OpenPegasus WBEM Services on the system. 1. 2. Login to the Linux system as root and run the following command to install the package:
# rpm Uvh tog-pegasus-version.distro.arch.rpm
Start OpenPegasus WBEM Services by running the following command as the root user:
# /etc/init.d/tog-pegasus start
At this point the Linux managed system has OpenPegasus WBEM installed and configured. The next steps provide information on how to configure the CMS to enable VSE Agent Distributor for ID-VSE for Integrity agents.
25
26
Installation
All Tools
Monitor Tools
Capacity Advisor
VSE Monitor
27
Required Authorizations Authorize this toolbox on the CMS to allow view-only use of gWLM version A.01.x. For gWLM version A.02.00.00 or later, this toolbox is not used; authorize VSE Monitor instead. Authorize this toolbox to allow full access to HP Virtual Connect Enterprise Manager software. This authorization permits viewing and modifying the VCEM configuration. Authorize this toolbox to allow read-only access to HP Virtual Connect Enterprise Manager software. This authorization permits viewing but not modifying the VCEM configuration.
To specify the subset of systems that are authorized with All Tools, refer to Selecting and updating the authorized systems set (page 30).
28
Create, modify, and delete gWLM policies. Delete parked workloads. A workload is parked if its container assignment is set to None -- Park the workload in the Monitored Workload Definition Properties screen. Parking a workload allows you to retain its collected data while waiting to migrate the workload to a new system. Perform operations on logical servers, including activate, copy, create, deactivate, delete, drop, import, modify, or move a logical server, and manage logical server storage pools. Manipulate Application Discovery agent behavior and modify application template matching and event reporting.
Systems Authorized CMS and All Managed Systems CMS CMS and All Managed Systems CMS and All Managed Systems All Managed Systems Subset of All Managed Systems
Toolbox System Setup VSE All Tools Monitor Tools VSE Monitor Capacity Advisor All Tools
To specify the subset of systems that are authorized with All Tools, refer to Selecting and updating the authorized systems set (page 30).
29
be restricted to specific managed systems, HP recommends using the other authorizations described earlier, which provide more granular host-based authorization.
Toolbox gWLM Monitor Systems Authorized CMS
For detailed information about creating and updating authorizations, refer to the HP SIM online help.
Initiate certificate exchange by selecting Configure Insight Dynamics AgentsExchange AD Agent Certificates from the HP SIM top menu.
2. 3. 4.
Select the HP-UX systems where you want the exchange to occur using the HP SIM system selection list. Click Apply. Verify the system selection and click Next. A description is displayed of the action about to take place. When you are sure that you want to exchange certificates so that the Application Discovery agent can begin reporting data to the server, click Run now to complete the certificate exchange.
NOTE: If you find that you are unable to exchange certificates from within HP SIM, check the following: That you have the correct permissions associated with your login ID. That the targeted managed node is authorized to accept remote commands from HP SIM. To set the correct SSH configuration that authorizes the acceptance of remote commands, type the following command on the CMS:
mxagentconfig -a -n managed_system -u login -p password
where managed_system is the name of the target system for which you want to enable remote communication, login is the user name on the managed system, and password is the password of that user on the managed system.
and on Windows:
C:\Program Files\HP\Virtual Server Environment\bin\amgr_remot_config.bat -a -mx -n system_name
To configure multiple hosts, add -n system_name for each host to be configured. By default, amgr_remote_config uses Secure Shell (SSH) to complete this action securely across the network. -u option supported on HP-UX only: You might be prompted to provide a password for the specified user for each system login. You must supply the password in order to proceed. 3. Once the login is accomplished, the CMS sends its SSL certificate to the agent on the managed host, and the agent supplies its SSL certificate to the CMS. Application Discovery agents can now transfer data securely to the CMS, and the CMS can authenticate the transmission.
Have you recently restored or removed and reinstalled the CMS? : A restore or removal of the central management server also removes the certificate recognition previously established between Application Discovery server on the CMS and Application Discovery agents on managed nodes. This relationship must be re-established when the CMS is reinstalled or restored by completing the Application Discovery certificate exchange.
31
32
HP authorized resellers
For the name of the nearest HP authorized reseller, see the following sources: In the United States, see the HP U.S. service locator website at: http://www.hp.com/service_locator In other locations, see the Contact HP worldwide website at: http://welcome.hp.com/country/us/en/wwcontact.html
Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.com Include the document title and manufacturing part number in your message. All submissions become the property of HP.
Related information
The latest versions of manuals and white papers for Insight Dynamics and related products can be downloaded from the Insight Dynamicsinformation library: http://www.hp.com/go/insightdynamics/docs For more information about Insight Dynamics and related products and solutions, visit the following HP website: http://www.hp.com/go/insightdynamics/integrity
Contacting HP 33
This document does not cover installation on an HP ProLiant CMS running Microsoft Windows. For that information, see the HP Insight Software 6.2 Installation and Configuration Guide. For a description of system requirements for ID-VSE for Integrity, see HP Insight Software 6.2 Support Matrix.
Configure or unconfigure the Insight managed system setup wizard Overview of XML file structure for Global Workload Manager Help resolve Insight Dynamics configuration problems Configure or unconfigure the Insight Dynamics software Manage licenses to use (LTUs) on HP Integrity and HP 9000 systems
Reference page gwlmagent(1M) gwlmplace(1M) gwlmsend(1M) gwlmsslconfig(1M) gwlmimportkey(1M) gwlmexportkey(1M) gwlmstatus(1M) utild(1M) utild(8)
Description Global Workload Manager (gWLM) agent Place a process in a gWLM workload Send metric data to gWLM for use in a custom policy Secure network communications for Global Workload Manager
Display status for the managed node's agent, SRD, and license Manager (HP-UX) system utilization data collection daemon (Linux) system utilization data collection daemon
Description Add, modify, identify, remove, or list nodes in Systems Insight Manager Start Systems Insight Manager and the TomCat webserver Display or return (via exit code) the current ready/not-ready state of Systems Insight Manager Stop Systems Insight Manager and the TomCat webserver Add, modify, remove, or list users in Systems Insight Manager
36
A Command reference
37
vseinitconfig(1M)
NAME
vseinitconfig -- Configure or unconfigure Insight Dynamics
SYNOPSIS
Path (HP-UX): /opt/vse/bin/vseinitconfig Path (Windows): install-path\bin\vseinitconfig vseinitconfig [ -a | --initconfig ] [ -F | --clobber ] [ -q | --quiet ] [-x restart_sim= { true | false }] (Initial software configuration) vseinitconfig { -r | --unconfig } [ -F | --clobber ] [ -q | --quiet ] [-x restart_sim= { true | false }] (Unconfigure software for removal) vseinitconfig { -b | --backup } { -d path | --dir=path } (Backup the PostgreSQL database on HP-UX CMS) vseinitconfig { -s | --restore } { -d path | --dir=path } { -F | --clobber } (Restore the PostgreSQL database on HP-UX CMS)
DESCRIPTION
The vseinitconfig command performs initial configuration of Insight Dynamics on an HP Systems Insight Manager (SIM) Central Management Server (CMS). It can also be used to remove the existing configuration and to back up or restore Insight Dynamics database. (Backup and restore functions are only available on a CMS running HP-UX using the PostgreSQL database.). The vseinitconfig command is installed with Insight Dynamics on both HP-UX and Microsoft Windows CMS. This command performs four different functions on the CMS, corresponding to the four syntax options shown in the synopsis. With no options specified, the initial configuration function is performed. 1. Initial configuration after installing or updating Insight Dynamics on the CMS. This includes initial configuration of HP Insight Virtualization Manager software, HP Insight Global Workload Manager software for Integrity (gWLM), and HP Insight Capacity Advisor software, as well as initialization of the Insight Dynamics database. 2. Removal of Insight Dynamics menu items and actions from HP SIM and clearing of the Insight Dynamics database, in preparation for removal of Insight Dynamics. 3. Safe backup of the Insight Dynamics database to protect against loss of data (only on a CMS running HP-UX using the PostgreSQL database). 4. Safe restore of the Insight Dynamics database from a previous backup (only on a CMS running HP-UX using the PostgreSQL database).
Options
The vseinitconfig command recognizes the following options. Each option can be expressed in a long or short form. If no options are specified, the initial configuration function is performed. Perform the initial configuration of Insight Dynamics (this -a|--initconfig is also the default function performed if no option is specified). This action requires that HP SIM is running and configured with the mxinitconfig command. This command registers Insight Dynamics tools, toolboxes, and actions with HP SIM and initializes the Insight Dynamics database. On a Microsoft Windows CMS, vseinitconfig -a is automatically invoked by the installer. On an HP-UX CMS,
38 Command reference
you must execute the command after installing the software (see HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide). On an HP-UX CMS, the optional --clobber or -F option causes an existing Insight Dynamics database to be removed without being backed up first. If that option is not used, then an existing database will be upgraded from the previous version of Insight Dynamics. This does not apply to a Microsoft Windows CMS. NOTE: HP recommends backing up your entire CMS configuration before upgrading from a previous version of Insight Dynamics. For details about this and other upgrade considerations, see the Insight Dynamics installation guide (HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide or HP Insight Software 6.2 Installation and Configuration Guide), and review the notes in the description of the --restore option below. Clear any existing Insight Dynamics database without backing it up. For more information about how this option affects vseinitconfig, see the descriptions of the options -a|--initconfig and -r|--unconfig. Do not display any output. Do not prompt for HP SIM -q|--quiet restart after performing the initial configuration operation. You can view the console and error output in the log files. -x restart_sim={true|false} This option selects whether to automatically restart HP Systems Insight Manager after initial configuration of Insight Dynamics. It only applies in combination with the initial configuration option (-a or --initconfig) or the unconfigure option (-r or --unconfig). Use -x restart_sim=true to restart HP SIM without any further prompting after all of the Insight Dynamics applications are configured. There can be a delay of one or two seconds after vseinitconfig finishes execution before HP SIM is ready to respond to mx... commands. Use -x restart_sim=false to return immediately after all of the Insight Dynamics applications are configured, without restarting HP SIM. If this option is not used, you will be prompted whether to restart HP SIM after all of the Insight Dynamics applications are configured. -F|--clobber -r|--unconfig Remove the installed Insight Dynamics tools from HP SIM. The existing database and configuration information will not be removed unless the optional --clobber or -F option is used. Important: The optional --clobber or -F option causes an existing Insight Dynamicsdatabase to be removed without being backed up first. If you do not perform a backup of the Insight Dynamics database before executing this command, you will lose all of your Insight Dynamics data, including gWLM and Capacity Advisor configuration and historical data. On a Microsoft Windows CMS, vseinitconfig -r is automatically invoked by the installer. On an HP-UX CMS,
39
you must execute the command before removing the software (see HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide). -b|--backup Back up the Insight Dynamics database, including gWLM and Capacity Advisor data, to protect against loss of data. Insight Dynamics must be initialized before you can perform a backup. For information about initializing Insight Dynamics, see the earlier description of the --initconfig option. NOTE: This option is only available on a CMS running HP-UX using the PostgreSQL database. The backup is created in the directory specified by the -d or --dir option. This directory must be initially empty or must not yet exist. The backup created by this command contains only Insight Dynamics data. For information about backing up the HP SIM database, refer to the HP white paper Backing up and restoring HP Systems Insight Manager data files in an HP-UX or Linux environment, available from the Information Library link at http://www.hp.com/go/hpsim. If you are creating a backup in preparation for relocating the CMS, HP recommends that you first undeploy all shared resource domains (SRDs). This will make it easier to redeploy the SRDs after the CMS is moved. To ensure that your backup includes up-to-date historic data, you should also perform the following steps: 1. If you are using gWLM to manage any SRDs, execute the following command on the CMS:
gwlm history --flush
2.
If you use Capacity Advisor, execute the following command on the CMS:
capcollect
-s|--restore
Restore the Insight Dynamics database from the backup in the directory named by the -d or --dir option. Insight Dynamics must be initialized before you can perform a restore, therefore the --clobber or -F is also required in order to replace the database. For information about initializing Insight Dynamics, see the earlier description of the --initconfig option. NOTE: This option is only available on a CMS running HP-UX using the PostgreSQL database. HP SIM must be stopped when the restore operation is performed. To stop HP SIM, execute the command mxstop on the CMS. Use mxstart to restart HP SIM after the restore operation is finished.
40
Command reference
NOTE: If the CMS or managed systems have been modified between the backup and the restore (for example, changing hostnames or adding or removing processors), gWLM might not function as expected after the restore. NOTE: You cannot restore a backup that was created with a previous version of Insight Dynamics. Previous versions of the Insight Dynamics database may be incompatible with the current version. If you have not yet installed the current version of the software and you intend to restore from a previous backup, perform the restore first. Then install and initialize the new software. The initialization process upgrades the already-restored database to the current format. If you have already updated the software and you need to restore from a backup made by a previous version of the software, follow these steps: 1. Remove Insight Dynamics according to the instructions in the Insight Dynamics installation guide (HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide or HP Insight Software 6.2 Installation and Configuration Guide). 2. Reinstall the version of the software on which the backup was created, according to the installation instructions published with that release. 3. Restore the Insight Dynamics database from the backup. 4. Install the new version of Insight Dynamics according to the current installation guide. 5. Initialize the software as described in the earlier description of the --initconfig option. This upgrades the restored database to the new format.
RETURN VALUES
0 1 The command completed successfully; no errors were detected. An error occurred and the command did not complete successfully.
EXAMPLES
The following command performs initial configuration of Insight Dynamics and prompts whether to restart HP SIM after configuration is complete.
vseinitconfig -a
The following command performs initial configuration of Insight Dynamics, removes any existing Insight Dynamics database without backing it up, and restarts HP SIM automatically:
vseinitconfig -a -F -x restart_sim=true
The following command backs up the Insight Dynamics database to the directory /var/ backups/2009-09-01:
41
vseinitconfig -b -d /var/backups/2009-09-01
The following command performs the unconfigure operation, removing Insight Dynamics tools from HP SIM. The --clobber option causes the database information to be removed without making a backup:
vseinitconfig --unconfig --clobber
You can mix the short and long form options. For example, to restore the Insight Dynamics database from the directory /var/backups/2009-09-01, you can use the following command:
vseinitconfig --restore -d /var/backups/2009-09-01 -F
AUTHORS
vseinitconfig was developed by Hewlett-Packard Company.
FILES
The console (non-error) output from the vseinitconfig command is written to the following log file: HP-UX: /var/opt/vse/logs/vseinitconfig_output.log Windows: install-path\logs\vseinitconfig_output.log Errors and exceptions reported by vseinitconfig, are written to the following log file: HP-UX: /var/opt/vse/logs/vseinitconfig.log Windows: install-path\logs\vseinitconfig.log The default install-path on a Windows CMS is C:\Program Files\HP\Virtual Server Environment, but this directory can be changed at installation time.
SEE ALSO
gwlmcmsd(1M), gwlmsslconfig(1M), mxglobalsettings(1M), mxinitconfig(1M), mxstart(1M), mxstatus(1M), mxstop(1M), mxtool(1M), mxtoolbox(1M), mxuser(1M), HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide, HP Insight Software 6.2 Installation and Configuration Guide, HP Insight Dynamics 6.2 Getting Started Guide
42
Command reference
b. c. d.
Stop the running Application Discovery server by entering the following command:
/opt/amgr/bin/cms_stop
2.
Back up the gwlm remote database on the Oracle server using Oracle Enterprise Manager or Oracle Recovery Manager. This database is used by multiple ID-VSE for Integrity applications. e. Back up any remote database tables used by other SIM applications, if necessary. Other HP SIM applications may have their own specific backup requirements. See the documentation for those applications for specific instructions. f. Back up the HP SIM remote database using Oracle Enterprise Manager or Oracle Recovery Manager. The HP SIM remote database name begins with Insight_v, followed by a version number. Make a full backup of the CMS. Performing a full backup of an HP-UX server may require booting the server in a lower init state or stopping additional system services, so that all configuration files can be read in a stable condition. Consult your backup software documentation for specific requirements.
Procedure B-2 Restoring your CMS configuration from backup If you need to restore the CMS configuration that was saved using the preceding procedure, use the following sequence: 1. Restore the server files from the full backup. 2. Restore the remote database tables. 3. Restart the server.
43
44
5.
Remove the existing ID-VSE for Integrity configuration and database by executing the following command:
# /opt/vse/bin/vseinitconfig -r -F
6.
7.
Remove log files and other application files by executing the following commands:
# # # # rm rm rm rm -rf -rf -rf -rf /opt/vse /etc/opt/vse /var/opt/vse /opt/gwlm /etc/opt/gwlm /var/opt/gwlm /opt/amgr /etc/opt/amgr /var/opt/amgr /opt/hpwebadmin/webapps/vse.war
45
46
Index
A
agent, 19, 20 installation, 21 amgr_remote_config certificate exchange example, 31 authorizations, 27 HP-UX patches, 9, 12
I
Insight Dynamics agent software (see agent) installation CMS, 16 managed systems, 21
B
backup VSE database, 15, 16 Bastille, 9
L
LDAP, 12 license demo, 23 installation, 21 Linux managed systems, 13, 24, 25
C
Central Management Server (see CMS) certificates completing the exchange, 30 exchanging from the command line, 31 exchanging from within HP Systems Insight Manager software, 30 CMS requirements, 9 command reference pages, 34
M
managed system setup wizard, 21 managed systems installing VSE agent software, 21 Linux, 13 Microsoft Windows, 14 setup, 21 manpage, 34 manuals, 33 Microsoft Windows managed systems, 14 mxagentconfig enabling remote communication from HP Systems Insight Manager software, 31
D
database, 15, 17 backup, 15, 16 restore, 15, 16 demo license, 23 discovery (see HP SIM, discovery) documentation, 33
N
network firewalls, 9 NIS, 12
F
Fair-Share Scheduler (see FSS group) firewall, 9 FSS group, 24
O
OpenPegasus WBEM, 24, 25 OpenSSH (see ssh) Oracle, 17
G
global credentials, 12 Global Workload Manager (see gWLM) gWLM agent installation, 21
P
patches, 9 ping sweep, 19 privilege elevation, 20, 21 processor set (see PSET) provider (see agent) PSET, 24
H
HP Capacity Advisor (see Capacity Advisor) HP Global Workload Manager (see gWLM) HP Integrity VM (see Integrity VM) HP SIM, 12 discovery, 19, 20 finding Application Discovery from, 30 First Time Wizard, 18, 19 installation, 11, 12, 16 launching, 18 supported versions, 9 HP Systems Insight Manager (see HP SIM) HP Virtualization Manager (see Virtualization Manager)
R
release notes, 12 remote command execution, 21 requirements, 9 firewalls, 9 restore VSE database, 15, 16 root, 12
47
S
Secure Shell (see ssh) security, 12 SSL certificate exchange, 30 Shared Resource Domain (see SRD) SIM documentation, 33 toolboxes, 27 user authorizations, 27 SNMP, 19 SRD, 23, 24, 45 undeploy before upgrade, 15 ssh, 13, 14, 19 SSL certificate exchange, 30 swinstall command, 17, 18 Systems Insight Manager (see HP SIM)
T
tasks exchanging certificates for application discovery, 30, 31 toolbox, 27
U
user authorizations, 27
V
virtual machine, 19 Virtual Server Environment (see VSE) Virtualization Manager, 19 VM (see Integrity VM) VM Host, 19 vPars (see virtual partition) VSE documentation, 33 vseinitconfig command, 17, 18
W
WBEM, 19 authentication, 12 provider (see agent) white papers, 33
48
Index
49