HP Insight Dynamics – VSE 6.
© 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.
Table of Contents 1 Introduction......................................................................................................................7 2 System requirements.......................................................................................................9 HP Systems Insight Manager.................................................................................................................9 Compatibility with HP-UX Bastille and other network firewalls................................
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.........................................................
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..............................................
List of Examples 3-1 3-2 3-3 6 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 32–bit Windows system......................................................
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.
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. HP Systems Insight Manager ID-VSE for Integrity version 6.2 runs under HP Systems Insight Manager (HP SIM) Version 6.0 or later.
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.
Table 3-2 Checklist for upgrading ID-VSE for Integrity on an HP-UX CMS Task Information □ Make a backup of the ID-VSE for Integrity database. Appendix B (page 43) □ Perform the upgrade preinstallation steps. “Before upgrading from a previous version” (page 15) □ Upgrade HP SIM and ID-VSE for Integrity on the CMS. “Install the software on the CMS” (page 16) □ If HP SIM was upgraded, launch HP SIM and run the First Time Wizard and the Discovery processes.
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.
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.
NOTE: This step can be performed within HP SIM by selecting the managed systems to configure, then selecting Configure→Configure 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.
a. b. c. d. e. f. g. 3. 4. 5. Select Tasks & Logs→View All Scheduled Tasks from the Capacity Advisor menu bar. Select the task from the list Collect Capacity Advisor Data. Click Edit. Click Schedule. 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.
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 system reboots after the installation. 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.
# /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.
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 Options→First Time Wizard... from the HP SIM menu bar.
e. Configure Managed Systems Configure managed systems as they are discovered, by configuring WBEM and WMI, SNMP, SSH access, and trust relationship. f. WMI Mapper Proxy To retrieve managed system information on Windows systems, enter the mapper proxy system host name and port number. The user name 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. 4. 20 g.
Install Insight Dynamics agent software and configure managed systems Managed systems require some setup before Insight Dynamics can properly identify them, retrieve data from them, and perform management operations on them. Managed system setup includes the installation of agent software or configuration of agentless data collection, installation of licenses, and configuration of options specific to the management capabilities intended for use on the system.
Procedure 3-8 Manual installation of HP-UX agents 1. 2. 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.
After upgrading from a previous version HP SIM upgrade If you upgraded HP SIM, follow any postinstallation instructions described in the HP SIM documentation. Make sure that you have installed all required HP-UX or application patches. Stop and restart HP SIM by executing the following commands on the CMS: # /opt/mx/bin/mxstop # /opt/mx/bin/mxstart It might take several minutes for HP SIM to restart completely.
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" • 3. 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”.
during RHEL installation, or install it later from your RHEL distribution media through the YaST Control Center. Preparing a ProLiant SUSE Linux managed system This section provides instructions on how to prepare a ProLiant system running SUSE Linux Enterprise Server 9 or 10 to be a managed system in ID-VSE for Integrity. Both x86 and x64 (AMD64/EM64T) platforms running these SUSE Linux versions are shipped with OpenWBEM, which is not supported by ID-VSE for Integrity.
Additional configuration steps If your Linux system is not an HP SIM managed system yet, refer to the “Setting Up Managed Systems” section of the HP Systems Insight Manager 6.0 Installation and User Guide available at http://www.hp.com/go/hpsim. This document also contains information on how to configure WBEM credentials for a Linux system. At this point users can install VSE Agents onto the Linux managed systems, necessary for Insight Dynamics.
4 Configure ID-VSE for Integrity After installation, you must perform additional steps to configure ID-VSE for Integrity for your environment. For a description of these steps, see the sections that follow. IMPORTANT: ID-VSE for Integrity does not operate correctly until you complete these postinstallation configuration steps. You must perform these steps even when you reinstall or update an existing installation.
Toolbox Required Authorizations gWLM Monitor 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. VCEM Full Access Authorize this toolbox to allow full access to HP Virtual Connect Enterprise Manager software. This authorization permits viewing and modifying the VCEM configuration.
• • • • 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.
be restricted to specific managed systems, HP recommends using the other authorizations described earlier, which provide more granular host-based authorization. Toolbox Systems Authorized gWLM Monitor CMS Role: legacy Global Workload Manager administrator This authorization is maintained for backward compatibility with gWLM version 1. This user is able to manage any system in the data center with gWLM version A.01.
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.
5 Support and other resources Contacting HP Information to collect before contacting HP Be sure to have the following information available before you call contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP technical support Use the following methods to contact HP technical support: • In the United States, see the Custom
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. Command references (manpages) Insight Dynamics and related products include manpages for HP-UX and Linux systems and command reference pages for Microsoft Windows systems.
Reference page Description gwlmagent(1M) Global Workload Manager (gWLM) agent gwlmplace(1M) Place a process in a gWLM workload gwlmsend(1M) Send metric data to gWLM for use in a custom policy gwlmsslconfig(1M) gwlmimportkey(1M) gwlmexportkey(1M) Secure network communications for Global Workload Manager gwlmstatus(1M) Display status for the managed node's agent, SRD, and license Manager utild(1M) (HP-UX) system utilization data collection daemon utild(8) (Linux) system utilization data collect
Reference page Description mxnode(1M) Add, modify, identify, remove, or list nodes in Systems Insight Manager mxstart(1M) Start Systems Insight Manager and the TomCat webserver mxstatus(1M) Display or return (via exit code) the current ready/not-ready state of Systems Insight Manager mxstop(1M) Stop Systems Insight Manager and the TomCat webserver mxuser(1M) Add, modify, remove, or list users in Systems Insight Manager Support and other resources
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=pa
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.
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: 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.
vseinitconfig -b -d /var/backups/2009-09-01 Here is the same command, using the long form of options: vseinitconfig --backup --dir=/var/backups/2009-09-01 The following command performs the unconfigure operation, removing Insight Dynamics 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.
B Back up the CMS configuration The upgrade process is not reversible. To revert to a previous installation of the software, you must restore the previous CMS configuration as well as any remote databases used by the software. Therefore, HP recommends that you make a backup of your current installation before upgrading the software. Back up your existing CMS configuration prior to upgrading the software The upgrade process is not reversible.
C Removing ID-VSE for Integrity Use Procedure C-1 to completely remove ID-VSE for Integrity from an HP-UX CMS. Procedure C-1 Remove ID-VSE for Integrity 1. 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.
Index A agent, 19, 20 installation, 21 amgr_remote_config certificate exchange example, 31 authorizations, 27 B backup VSE database, 15, 16 Bastille, 9 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 D database, 15, 17 backup, 15, 16 restore, 15, 16 demo license, 23 discovery (see HP SIM, discovery) documentation, 33 F Fair-Sha
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, 1
