Deploying HP Systems Insight Manager 4.2 on MSCS Clusters

Transcription

1 Deploying HP Systems Insight Manager 4.2 on MSCS Clusters Abstract... 3 Introduction... 3 Getting started... 4 Node infrastructure... 4 Storage configuration... 5 IP addresses... 5 Target audience... 6 Hardware and software requirements... 6 Setting up the Failover environment... 6 Installing the Simple Network Management Protocol... 6 Activating the HP cluster MIB agents... 7 Installing the Microsoft SQL Server 2000 Enterprise Edition... 7 Installing a clustered instance of the Microsoft SQL Server 2000 Enterprise Edition... 8 Installing HP Systems Insight Manager 4.2 on the cluster Installing HP Systems Insight Manager 4.2 on the primary node Installing HP Systems Insight Manager 4.2 on the secondary node Adjust the HP Systems Insight Manager 4.2 data source name on the primary node Upgrading Insight Manager 7 SP2.3 Cluster to HP Systems Insight Manager 4.2 Cluster Upgrading Primary Node Upgrading Secondary Node Adjust the HP Systems Insight Manager 4.2 data source name on the Primary node Adding the HP Systems Insight Manager 4.2 cluster resources Naming the HP Systems Insight Manager 4.2 and SQL Server disk groups Creating the HP Systems Insight Manager 4.2 IP address resource Creating the HP Systems Insight Manager 4.2 network name resource Creating the HP Systems Insight Manager 4.2 generic service resource Creating the OpenSSH Services for HP Systems Insight Manager 4.2 generic service resource Creating the Pegasus WMI Mapper generic service resource Creating the PMP Services for HP Systems Insight Manager 4.2 generic service resource Creating the PMP tools Services for HP Systems Insight Manager 4.2 generic service resource Creating the Version Control Repository Manager 4.2 (VCRM) generic service resource... 33

2 Creating the Virtual Machin Management Pack generic service resource Creating the Virtual Machin Management web service generic service resource Bringing the virtual group containing the HP Systems Insight Manager 4.2 resources online Troubleshooting Validating the installation For more information Microsoft cluster services Microsoft SQL Server 2000 Enterprise Edition HP Systems Insight Manager

3 Abstract This white paper is intended to assist IT professionals in installing HP Systems Insight Manager 4.2 in a Microsoft Cluster Server configuration. Using Microsoft Windows 2000 Advanced Server with HP Systems Insight Manager 4.2 can be a simple way of obtaining redundancy and failover capability from this powerful management software. Introduction HP Systems Insight Manager 4.2 offers the ability to run in a Microsoft Windows 2000 Advanced Server clustered environment, using Microsoft SQL Server 2000 Enterprise Edition on an HP ProLiant cluster. By installing HP Systems Insight Manager 4.2 as a clustered application, this versatile and simple management product can also be highly available. Additionally, by distributing the load for Microsoft SQL Server 2000 and HP Systems Insight Manager 4.2 on separate nodes, you can take advantage of maximum efficiency. This white paper describes the steps to install a highly available clustered version of HP Systems Insight Manager 4.2 on a ProLiant cluster running Windows 2000 Advanced Server. The HP Systems Insight Manager 4.2 database, the repository for all management information used by HP Systems Insight Manager 4.2, will reside on a Microsoft SQL Server 2000 virtual server, which is also clustered. The relationship between the Microsoft SQL Server 2000 Enterprise Edition instances and HP Systems Insight Manager 4.2 is shown in Figure 1. HP Systems Insight Manager 4.2 connects to the database using the network name of the Microsoft SQL Server 2000 instance that owns the HP Systems Insight Manager 4.2 Database. A named instance of Microsoft SQL Server 2000 has a virtual server within the cluster, with a network name and an IP address for which clients connect. HP Systems Insight Manager 4.2 will have its own network name and IP address. Clients who wish to browse to the HP Systems Insight Manager 4.2 service can do so by using the unique name or IP Address for HP Systems Insight Manager 4.2 in the cluster.

4 Figure 1. The relationship between HP Systems Insight Manager 4.2, SQL Server 2000, and the cluster disks Getting started If you are installing HP Systems Insight Manager 4.2 into an environment without a Microsoft SQL Server 2000 Enterprise Edition instance already installed, go to Installing the Microsoft SQL Server 2000 Enterprise Edition, for steps to install a clustered named instance of Microsoft SQL Server 2000 Enterprise Edition. This named instance can host the HP Systems Insight Manager 4.2 databases and any other production databases you might need in your environment. If an instance of Microsoft SQL Server 2000 Enterprise Edition already exists in your cluster, you can go to Installing HP Systems Insight Manager 4.2 on the cluster for steps to install HP Systems Insight Manager 4.2 and the process to make it highly available. If Insight Manger 7 is running in your cluster, go to Upgrading Insight Manager 7 SP2.3 Cluster to HP Systems Insight Manager 4.2 Cluster for steps to upgrade the Insight Manager 7 to HP Systems Insight Manager 4.2 in a cluster. Node infrastructure Figure 1 details how to configure a cluster for enhanced performance once all components are installed. With this configuration, you can distribute the load by designating each virtual group to work on a separate node. The primary node is for running the Microsoft SQL Server 2000 Enterprise Edition processor and handling remote Microsoft SQL Server commands. The purpose of the secondary node is to run the HP Systems Insight Manager 4.2 service and all the component services it requires.

5 Storage configuration Figure 1 displays the relationship between Microsoft SQL Server 2000 Enterprise Edition instances and HP Systems Insight Manager 4.2. At least two logical drives must be available in the shared storage if your infrastructure does not have Microsoft SQL Server installed to which you can attach the HP Systems Insight Manager 4.2 database. The first shared disk contains the Microsoft SQL Server 2000 Enterprise Edition data files (for the examples discussed in this paper, this drive is I:). The other shared disk will contain the HP Systems Insight Manager 4.2 program files (for the examples discussed in this paper, this drive is F:). Note: If you already practice separating your transaction log from your data files, you can enhance performance by specifying that the HP Systems Insight Manager 4.2 transaction log is installed to a separate disk. IP addresses Microsoft Cluster Services (MSCS) requires that all virtual servers in a cluster have a unique static IP address. For the configuration described in this paper, five unique IP addresses are required. 1. HP Systems Insight Manager 4.2 virtual server IP name and address Function: To act as the virtual server IP name and address for HP Systems Insight Manager 4.2 event reception. Users specify this name and address to connect to HP Systems Insight Manager 4.2 through Internet Explorer. Suggested action: All SNMP devices that report their events to HP Systems Insight Manager 4.2 should use this IP name and address for the location of the Event Consolidator, the SNMP Trap Destination. In the examples discussed in this paper, the IP address is MSCS cluster IP name/address Function: To act as the virtual server IP name and address for the MSCS software. Suggested action: MSCS management tools would use this address to get status and reconfigure the MSCS software. In the examples discussed in this paper, the IP address is Microsoft SQL Server 2000 virtual server IP name and address Function: To act as the virtual server IP name and address for the Microsoft SQL Server 2000 Enterprise Edition database software. This software is used to extract, manipulate, or back up the HP Systems Insight Manager 4.2 database. Suggested action: The HP Systems Insight Manager 4.2 ODBC data source uses this as the location where the HP Systems Insight Manager 4.2 DSN points. In the examples discussed in this paper, the IP address is MSCS primary node IP name and address Function: To serve as the TCP/IP name and address of the specific Microsoft Windows server host. Suggested action: Any software that references node-specific functions uses this address to connect to this node. In the examples discussed in this paper, the IP address is MSCS secondary node IP name and address Function: To serve as the TCP/IP name and address of the specific Microsoft Windows server host.

6 Suggested action: Any software that references node-specific functions uses this address to connect to this node. In the examples shown in this paper, the IP address is Target audience It is assumed that readers of this document have an excellent understanding of the following concepts and services: Basic clustering concepts Basic Microsoft Windows 2000 services Advanced TCP/IP and DNS network concepts In addition, readers must be familiar with installing and administering these products: Microsoft Windows 2000 Advanced Server and MSCS Microsoft SQL Server 2000 Enterprise Edition, particularly named instances Hardware and software requirements This document discusses configuring and administering a cluster using the following products: A two-node HP ProLiant cluster with Each node satisfying all the hardware requirements for HP Systems Insight Manager 4.2 Note: For best results, each node should meet the recommended memory and processor speed requirements. One free shared disk for the HP Systems Insight Manager 4.2 program files At least one free shared disk for Microsoft SQL Server 2000 Microsoft Windows 2000 Advanced Server with Service Pack 3 or later Microsoft Cluster Services Microsoft Internet Explorer 6.0 with Service Pack 1 or later Simple Network Management Protocol (SNMP) Microsoft SQL Server 2000 Enterprise Edition with Service Pack 3. HP Systems Insight Manager 4.2 HP Management CD (version 7.1) and related ProLiant Support Packs Note: About Windows 2003 To Install HPSIM 4.2 on Windows 2003 cluster, refer Microsoft Knowledge Base article # concerning Virtual Server on a 2003 Cluster. Setting up the Failover environment Note: This section of the white paper assumes that you log into each of your cluster nodes with the same administrator credentials that you are using to access all the HP Systems Insight Manager 4.2 and Microsoft SQL Server 2000 components that are being set up. Installing the Simple Network Management Protocol SNMP is a prerequisite for the HP Systems Insight Manager 4.2 installation. The following section details how to install SNMP to the cluster nodes intended to host HP Systems Insight Manager 4.2.

7 1. Insert the Windows 2000 Advanced Server CD into the CD-ROM drive of the target server. 2. Select Start Settings Control Panel. 3. Click Add/Remove Programs. 4. Click Add/Remove Windows Components. 5. Select Management and Monitoring Tools in the Windows Component Wizard window. 6. Click Details. Then select Simple Network Management Protocol. 7. Click Close. The Windows Component Wizard window is displayed. 8. Click Next. Wait for the file copying to complete. 9. Click Finish. 10. Remove the Windows 2000 Advanced Server CD. IMPORTANT: If you install SNMP service after installing a Microsoft Windows Operating System Service Pack, you must reinstall that Service Pack. Note: Upgrading the HP Management Agents or adding new hardware does not change the existing agent configuration. You must manually enable any new hardware-related or cluster-related agent to activate it. Activating the HP cluster MIB agents The HP Cluster MIB Agents provide information about your cluster through SNMP. It is a prerequisite for the HP Systems Insight Manager 4.2 that these MIB agents be installed on your cluster to discover and identify itself as a cluster, as well as recognizing its nodes as such. If your cluster was setup following the user guide that ships with the cluster itself, the HP Management Agents and all the MIBs (including the HP Cluster MIB Agents) should already be installed on each node. To activate the HP Cluster MIB Agents on each node: 1. Select Start Settings Control Panel. 2. Double-click HP Management Agents. The HP Management Agents for Servers window is displayed. 3. Be sure the Services tab page window is displayed. 4. Under the Inactive Agents: list box on the right-hand side, double-click Clustering Information to add it to the Active Agents: list box on the left-hand side. Note: You may need to scroll down to the bottom of the Active Agents: list box to ensure and verify that Clustering Information has been added to the list. 5. Click OK to apply the update. 6. Click Yes to reboot the system. Installing the Microsoft SQL Server 2000 Enterprise Edition The Microsoft SQL Server 2000 Enterprise Edition is required for the installation of HP Systems Insight Manager 4.2 to be highly available. If you already have an instance of Microsoft SQL Server 2000 Enterprise Edition installed, you can create the HP Systems Insight Manager 4.2 database and attach it to the existing server. Note: This section of the white paper assumes that you already have a working two-node cluster with at least two free logical drives: one for the Microsoft SQL Server 2000 data files and another for the HP Systems Insight Manager 4.2 program files.

8 Installing a clustered instance of the Microsoft SQL Server 2000 Enterprise Edition 1. From the Run menu on any node in the cluster, type comclust and press the Enter key. Wait for the command to complete. Then run comclust on the remaining node in the cluster. This executable sets up the MSDTC, a component for use in the cluster. 2. Insert the Microsoft SQL Server 2000 Enterprise Edition CD into the server that currently owns all the shared disks in the cluster. Note: This server is referred to as the primary node for the remainder of this section. 3. At the Run menu, enter D:\english\ent\autorun.exe (where D: is the drive letter of your CD-ROM drive.) Note: You may skip this step if the AutoRun feature is enabled on your primary node. 4. Select SQL Server 2000 Components. 5. Select Install Database Server. The Welcome window is displayed. 6. Click Next. The Computer Name window is displayed. 7. Enter the name of your new virtual server. For this example, we have used the name HP-SIM- SQLSVR, as shown in figure Click Next. Figure 2. The Computer Name window 9. Enter user information for your company. Click Next. 10. Review the License Agreement. You must accept the License Agreement before you can install Microsoft SQL Server 2000 Enterprise Edition.

9 11. Click Yes to accept the License Agreement. The Failover Clustering window is displayed. 12. Enter an IP address for your new virtual server. This address must be unique. Be sure that the public network is selected in the Network To Use field. 13. Click Next. For this example, we used the IP Address In the Cluster Disk Selection window, select the cluster disk where the Microsoft SQL Server 2000 program files is to be saved, by selecting the disk drive letter as shown in Figure Click Next. The Cluster Management window is displayed Figure 3. The Cluster Disk Selection window IMPORTANT: Do not use the cluster quorum disk, the disk containing your cluster s quorum files (in Figure 3 the quorum disk is Disk Q: in the cluster group, the first group in the list) because the quorum disk must be treated as a special resource. A warning message is displayed if you select the quorum disk. For more information, see the Quorum Disk Selection Warning topic in the SQL Server 2000 books online. When you use a small cluster, the quorum disk may be the only choice available. Use the quorum disk only for testing purposes or to explore failover clustering. Never use the quorum group for production purposes. 16. Be sure that the two nodes of your cluster are displayed in the Configured Nodes window. 17. Click Next. The Remote Information window is displayed. 18. Enter the Username, Password, and Domain for a user account with access to all cluster resources. 19. Click Next. The Instance Name window is displayed.

10 20. Name this instance. By default, Default is selected and clients connect to the server by the server name. You must deselect Default and enter a name in the Instance name field, as shown in Figure 4. Click Next. Figure 4. The Instance Name window Note: For this example, we have installed a named instance of a Microsoft SQL Server 2000 virtual server called HP-SIM-INSTANCE. Clients will then connect to the server via the name HP-SIM- SQLSVR\HP-SIM-INSTANCE. 21. Select Typical installation at the Setup Type window. Be sure that the drive letter of the destination folder for your data files matches the drive you chose in step Click Next. The Services Accounts window is displayed. Enter the same domain account information you entered previously to ensure connectivity. 23. Click Next. The Authority Mode window is displayed. 24. Select Mixed mode for the Authentication mode and enter the password for the sa account. This enables the sa account, as well as Microsoft Windows authenticated users, access to the clustered virtual SQL Server. 25. Click Next. The Start Copying Files window is displayed. 26. Click Next. The Choose Licensing Mode window is displayed. Choose your licensing mode and enter the number of licenses you have. 27. Click Continue. A message is displayed indicating Setup is performing required operations on Cluster Nodes. This may take a few minutes. Following the licensing portion of setup, the installation performs required actions on the cluster nodes. This process takes approximately 30 minutes. The Setup Complete window is displayed.

11 28. Click Finish. No reboot of your servers is necessary. 29. You will need to verify the installation of the Microsoft SQL Server 2000 Enterprise Edition resources using Cluster Administrator. Do so by opening Cluster Administrator from the Start Programs Administrative Tools Cluster Administrator menu. You should see the following resources in the disk group containing your Microsoft SQL Server 2000 disk: Microsoft SQL IP Address, Microsoft SQL Network Name, Microsoft SQL Server, Microsoft SQL Server Agent, Microsoft SQL Server Full Text. Be sure that the new Microsoft SQL Server virtual server is running by connecting to it through the Microsoft SQL Server Enterprise Manager. Note: HP Systems Insight Manager 4.2 requires a minimum Service Pack for SQL Server Update your SQL Server 2000 installation with Service Pack 3 before installing HP Systems Insight Manager 4.2. Be sure to follow any reboot instructions at the end of the Service Pack installation. Installing HP Systems Insight Manager 4.2 on the cluster After completing the installation of a Microsoft SQL Server 2000 Enterprise Edition instance or verification of the availability of an existing Microsoft SQL Server 2000 instance, you are ready to proceed with the installation of HP Systems Insight Manager 4.2. If you already have a Microsoft SQL Server 2000 instance, you would like to use to host the HP Systems Insight Manager 4.2 Database (for HP Systems Insight Manager 4.2), follow the instructions below for installing HP Systems Insight Manager 4.2, but please note the additional comments throughout this section that relate to your particular setup. IMPORTANT: Before you begin, make sure you have all system and preinstallation requirements fulfilled. In addition, the Microsoft SQL Server service should be running. To be sure that you meet these requirements, refer to the HP Systems Insight Manager User Guide located on the HP Management CD. 1. Ensure that both nodes are up and running cluster services before installation. Also, be sure that the SQL Server instance to which you will install the HP Systems Insight Manager 4.2 Database is running. 2. Ensure that the cluster node that is to be installed with HP Systems Insight Manager 4.2 owns the clustered disks. 3. Read the HP Systems Insight Manager User Guide to make sure that you have the right prerequisites for installation. 4. Read the HP Systems Insight Manager Release Notes. Installing HP Systems Insight Manager 4.2 on the primary node 1. On the primary node, log into Microsoft Windows as a user with administrator rights. Note: Be sure to log in with the same user id that you used to install the Microsoft SQL Server 2000 Enterprise Edition instance. 2. Insert the HP Management CD into the CD-ROM drive. The CD has an AutoRun feature that displays the Proliant Essentials Foundation Pack-management CD window. If AutoRun is not enabled on the primary node, go to D:\autorun.exe. If this is the first time you are installing from this version of the HP Management CD, you must first to accept the license agreement for the HP Management CD. 3. Click Install or Upgrade Management Products to proceed. 4. Click the HP Systems Insight Manager 4.2-Windows Install link. The Welcome to the HP Systems Insight Manager Installer window. 5. Click Install. The Select Installation Type window is displayed.

12 6. Click Custom. The Custom Install Software Selection window is displayed. Note: The Custom Install option allows you to specify installing on the desired shared disks (F: and I: in the examples discussed in this paper). 7. Click Next. The Custom Install Summary window is displayed. 8. Click Install. The installation of HP Systems Insight Manager 4.2 and its dependent services is initiated. a. Welcome to the Setup Wizard for the System Management Homepage is displayed. i. Click Next. Operating System Groups page is displayed. ii. iii. iv. Create appropriate groups and click on Next. User Access page is displayed. Select appropriate options and click Next. Trust mode page is displayed. Select a trust mode and click Next. v. IP Binding page is displayed. Configure IP bindings if required and click Next. vi. vii. viii. IP Restricted logins page is displayed. Configure IP Restricted logins if required and click Next. Click Next on Summary screen. Installation will be started at this time and Summary information screen will be displayed once the installation is completed. Click on Finish button to complete the installation of System management Home Page. b. A new Welcome to the OpenSSH Services for HP Systems Insight Manager Setup Wizard dialog window is displayed. Note: Read the welcome message, which will remind you to close other applications. i. Click Next. The Select Destination Location window is displayed. ii. iii. iv. Specify the desired directory to be on the local drive of the current node (In the example discussed in this paper we have chosen the default C:\Program Files\OpenSSH) Click Next. The Ready to Install window is displayed. Click Install. The Installing window is displayed. Note: A progress bar indicating files are being copied is displayed during the installation of this service. At the end, the Completing the OpenSSH Services for HP Systems Insight Manager Setup Wizard window is displayed. v. Select No, I will restart the computer later. vi. Click Finish to close the Setup OpenSSH Services for HP Systems Insight Manager wizard dialog window. c. A new Welcome to the Pegasus WMI Mapper V2.0 Setup Wizard dialog window is displayed. i. Click Next. The End-User License Agreement window is displayed. ii. Select I accept the terms in the License Agreement.

13 iii. iv. Click Next. The Choose Setup Type window is displayed. Select Custom and click Next. The Ready to Install window is displayed. v. Click Install to proceed to the Installing Pegasus WMI Mapper v2.0 screen. Note: A progress bar indicating files are being copied is displayed during the installation of this service. WMI Mapper will be installed on C:\Program Files\The Open Group\WMI Mapper. At the end, the Completing the Pegasus WMI Mapper v2.0 Setup Wizard window is displayed. vi. Click Finish to exit the WMI Mapper setup wizard. d. A new Welcome to the HP Systems Insight Manager Setup Wizard dialog window is displayed. Note: Read the welcome message, which will remind you to close other applications. i. Click Next. The Information window is displayed. ii. Click Next. The Database Configuration window is displayed. iii. iv. 1. The Username field displays the user name that is logged in. 2. Enter the password in the Password field. 3. The Domain field displays the user domain that you have logged in with. 4. Enter the name of the Microsoft SQL Server 2000 Enterprise Edition instance that you created. Refer Installing a Clustered Instance of the Microsoft SQL Server 2000 Enterprise Edition ( HP-SIM- SQLSVR\HP-SIM-INSTANCE in the examples discussed in this paper). Note: If the credentials specified cannot be validated, a message is displayed stating this. You are not able to continue with the installation until the account information is validated. Note: Be sure to close any application, such as Microsoft SQL Server Enterprise Manager, that connects to the Microsoft SQL Server 2000 Enterprise Edition instance being referenced here (HP- SIM-SQLSVR\HP-SIM-INSTANCE in this paper); otherwise this step may hang. Click Next. The Select Destination Directory window is displayed. Specify the desired directory to be in the desired shared disk (F:\ HPSIM in this paper). v. Click Next. The Select Start Menu Folder window is displayed. vi. vii. viii. Specify the desired Start Menu Folder name or stay with the default setting. (HP Systems Insight Manager in this paper). Click Next. The Ready to Install window is displayed. Click Install. The Installing window is displayed. Note: A progress bar indicating files are being copied is displayed during the installation, which may take a few minutes.

14 ix. Note: It may take a few more minutes when the Initializing HP Systems Insight Manager dialog is displayed. At the end, the Completing the HP Systems Insight Manager Setup Wizard screen is displayed. Click Finish to close the Setup HP Systems Insight Manager wizard dialog window. x. e. A message box displays, which gives a warning message As part of the PMP installation HPSIM service must be stopped and restarted, Click OK to continue. A new Welcome to the HP Performance Management Pack Setup Wizard dialog window is displayed. i. Click Next to proceed to Database configuration screen. 1. The Username field displays the user name that is logged in. 2. Type in the correct password in the Password field. 3. The Domain field is already filled in with the user domain that you logged in with. The Data base server name field also displays the database name you had entered during the HP Systems Insight Manager installation. ii. Click Next to proceed to Installing screen. Note: If the credential specified cannot be validated, a message is displayed stating this. You will not be able to continue with the installation until the account information is validated. Note: Once the copy process is complete, if your system does not have Webbased agents installed, the Web-based Management Setup Wizard is displayed. You must enter a non-blank password and a confirmation password. This password becomes the administrator account password for all Web-based agents installed on your system. Click Next to continue. Note: A progress bar indicating Creating PMP database is displayed. A folder Performance Management Pack will be created in the same location where you have installed HP Systems Insight Manager (F:\ Performance Management Pack in this white paper) and PMP is installed in it. At the end, Completing the HP Performance Management Pack setup Wizard dialog box is displayed. Click Finish to exit the setup. f. A new HP Package Setup: Version Control Repository Manager dialog window is displayed. Note: If the Version Control Repository Manager is already installed on your system, this dialog window is not displayed. i. Click Install to proceed to the next screen. ii. Note: If you do not want to install the Version Control Repository Manager, click Close to skip this component. You can move on to step 8g. Click Install to proceed to the Repository Directory screen. From a separate Windows Explorer window, create the desired directory in the desired shared drive that is part of your cluster (for this paper we have chosen F:\VCRM). Return to the Repository Directory screen of the Version Control Repository Manager Setup window. Click Browse to open the Browse for Folder dialog box.

15 iii. iv. Select the previously created directory in the desired shared drive that is part of your cluster (for this paper we have chosen F:\VCRM). Click OK to close the Browse for Folder dialog box and return to the Repository Directory screen of the Version Control Repository Manager Setup dialog window. Click Perform an initial repository population, if you have Proliant Support Packs available. Alternatively, the Repository can be populated at later point of time by copying the files to the repository folder. Click Next. The Automatic Update window is displayed. Make the appropriate selections for automatic download of latest support packs directly from HP web site. v. Click Finish. The HP ProLiant Setup: Version Control Repository Manager dialog window is displayed. vi. Click Close. g. A message box is displayed which gives a warning message As part of the VMM installation, HPSIM must be stopped and restarted. Click OK to continue. i. Welcome to the HP Virtual Machine Management Pack Setup Wizard is displayed. Click Next to continue. ii. iii. iv. Database configuration page is displayed. Enter the password and click Next to continue. HP Virtual Machine Management Pack will be installed at this time. Completing the HP Virtual Machine Management pack setup wizard page will be displayed after the installation. Clcik Finish to complete the installation. A help page is displayed for configuring System Management Homepage for VCA authentication. Close this window. 9. Click Finished at the Custom Install Status window of the HP Systems Insight Manager Installer window to close it. 10. Click Finish in the Pre-installation/Installation/Post-Installation window. 11. A message Please reboot your system to complete your HP Systems Insight Manager installation is displayed. 12. Click OK. 13. Shutdown the current node. Installing HP Systems Insight Manager 4.2 on the secondary node In order to have a clustered installation of HP Systems Insight Manager, the second node in the cluster must complete the installation process as well, with a few differences in the procedure to account for the existing program files on the cluster disk. IMPORTANT: Be sure to specify the same user credentials and path information as used on the primary node. IMPORTANT: Be sure that the secondary node owns all the clustered disks. VERY IMPORTANT: You must either delete or rename existing HPSIM and PMP folders (For this white paper, it is F:\HPSIM and F:\Perforamnce Management Pack\) before proceeding further. Be sure to specify the same locations on the same-shared disk as in the primary node installation.

16 1. At your secondary node, repeat steps 1-12 in Installing HP Systems Insight Manager 4.2 on the primary node with respect to the secondary node. 2. Open ~\HP Systems Insight manager\config\database.props file and note down the database name specified against the keyword hp.database.databasename. 3. Shutdown the Secondary node. Adjust the HP Systems Insight Manager 4.2 data source name on the primary node a. Bring up primary node. b. Click Control Panel->Administrative Tools->Data Sources (ODBC). c. Select System DSN. d. Select Insight_v42_0 and click Configure. e. Update the Database Description referring to the database name created on first node Note: Use the database name noted in step 2 of Installing HP Systems Insight Manager 4.2 on the Secondary node. f. Click Next. The authentication mode selection window is displayed. g. Click Next. The database selection window is displayed. (As shown in Figure 5.) h. Select the database, which is created by the secondary node. Use the database name indicated in Installing HP Systems Insight Manager 4.2 on the Secondary node.) i. Click Next. j. Click Finish to complete the configuration. A summary window is displayed. k. Click OK. The ODBC Data Source Administrator window is displayed. l. Click OK to close ODBC Data Source Administrator window.

17 Figure 5. Adjusting the HP Systems Insight Manager 4.2 data source name on the primary node Go to Adding the HP Systems Insight Manager 4.2 cluster resources Upgrading Insight Manager 7 SP2.3 Cluster to HP Systems Insight Manager 4.2 Cluster. Note: This section assumes that Insight Manager 7 SP2.3 is running in the failover mode in a two node Microsoft Windows 2000 advanced server cluster environment, and these servers meet the prerequisites detailed in the Hardware And Software Requirements. For more details, please refer HP Systems Insight Manager User Guide and HP Systems Insight Manager Release Notes located on the HP Management CD. Upgrading Primary Node 1. On the primary node, log into Microsoft Windows as a user with administrator rights. Note: Be sure to log in with the same user id that you used to install the Microsoft SQL Server 2000 Enterprise Edition instance. 2. Open the Cluster Administrator tool and delete the cluster resources created for IM7, VCRM and PPA. 3. Shutdown the secondary node. 4. Make sure that primary node owns all cluster resources.

18 5. Keep a copy of the existing Insight Manager 7 and Proliant Performance Analyzer folder from the shared disk on which HPSIM and PPA are installed. 6. Start the IM7, PPA, and VCRM services manually. 7. Insert the HP Management CD into the CD-ROM drive. The CD has an AutoRun feature that displays the Proliant Essentials Foundation Pack-management CD window. If AutoRun is not enabled on the primary node, go to D:\autorun.exe. If this is the first time you are installing from this version of the HP Management CD, you must first to accept the license agreement for the HP Management CD. 8. Click Install or Upgrade Management Products. 9. Click the HP Systems Insight Manager 4.2-Windows Install link. The Welcome to the HP Systems Insight Manager Installer window is displayed. 10. A warning message is displayed as shown in Figure 6. Click OK to continue Figure Welcome to HP Performance Management Pack Data migration tool setup wizard screen opens. a. Click Next to continue. The Select Destination Directory window is displayed. b. Select the default path and click Next. The Default Path is C:\Program Files\HP\Performance Management Pack Data Migration Tool. HP Performance Management Pack Data migration tool window is displayed. c. Click Next. The HP Performance Management Pack 2.1 Data Export window is displayed. d. Be sure that logged data is selected. Click Next. The data is exported. e. Click Next to continue after export is completed. f. Click Finish to complete HP Performance Management Pack Data export. 12. The HP Systems Insight Manager Data Migration tool for Insight Manager 7 window is displayed. a. Click Next. The User-Defined Insight Manager 7 Data Export window is displayed. b. Click Next. The Data Migration Tool exports the user-defined data to the System Insight Manager data Migration tool folder. c. Click Next after export is completed. The Disable Insight Manager screen? window is displayed. d. Select In-Place migration. e. Click Next to continue. f. Click Finish to complete Insight Manager 7 data export. The Welcome to the HP Systems Insight Manager Installer window is displayed. 13. Click Install to begin HP Systems Insight Manager installation. The Select Installation Type window is displayed.

19 14. Select Custom. Be sure that all the components are selected on the Custom Install- Software Selection window. 15. Click Next to continue. 16. Welcome to the Setup Wizard for the System Management Homepage is displayed. i. Click Next. Operating System Groups page is displayed. ii. iii. iv. Create appropriate groups and click on Next. User Access page is displayed. Select appropriate options and click Next. v. Trust mode page is displayed. Select a trust mode and click Next. vi. vii. viii. ix. IP Binding page is displayed. Configure IP bindings if required and click Next. IP Restricted logins page is displayed. Configure IP Restricted logins if required and click Next. Click Next on Summary screen. Installation will be started at this time and Summary information screen will be displayed once the installation is completed. Click on Finish button to complete the installation of System management Home Page. 17. Click Install to begin the installation. The Welcome to the OpenSSH Services for HP Systems Insight Manager Setup Wizard window is displayed. Note: Read the welcome message, which will remind you to close other applications. a. Click Next. The Select Destination Location window is displayed. b. Specify the desired directory to be on the local drive of the current node (for this paper we have chosen the default C:\Program Files\OpenSSH) c. Click Next. The Ready to Install window is displayed. d. Click Install. The Installing window is displayed. Note: A progress bar indicating files are being copied is displayed during the installation of this service. At the end, Completing the OpenSSH Services for HP Systems Insight Manager Setup Wizard window is displayed. e. Select No, I will restart the computer later. f. Click Finish to close the Setup OpenSSH Services for HP Systems Insight Manager wizard window. 18. A new Welcome to the Pegasus WMI Mapper V2.0 Setup Wizard window is displayed. a. Click Next. The End-User License Agreement window is displayed. b. Select I accept the terms in the License Agreement. c. Click Next. The Choose Setup Type window is displayed. d. Select Custom and click Next. The Ready to Install window is displayed. e. Click Install. The Installing Pegasus WMI Mapper v2.0 window is displayed. Note: A progress bar indicating files are being copied is displayed during the installation of this service. At the end, the Completing the Pegasus WMI Mapper v2.0 Setup Wizard window is displayed.

20 f. Click Finish to exit the WMI Mapper setup wizard. 19. A new Welcome to the HP Systems Insight Manager Setup Wizard dialog window is displayed. Note: Read the welcome message, which reminds you to close other applications. a. Click Next. The Information window is displayed. b. Click Next. The Database Configuration window is displayed. i. The Username field displays the user name that is logged in. ii. iii. iv. Enter the password in the Password field. The Domain field displays the user domain that is logged in. Enter the name of the Microsoft SQL Server 2000 Enterprise Edition instance that you created in the section HP-SIM-SQLSVR\HP-SIM- INSTANCE in this paper. Note: A message is displayed if the credentials specified cannot be validated. You are unable to continue with the installation until the account information is validated. Note: Be sure to close any application, such as Microsoft SQL Server Enterprise Manager, that connects to the Microsoft SQL Server 2000 Enterprise Edition instance being referenced here (HP-SIM-SQLSVR\HP-SIM-INSTANCE in this paper); otherwise this step might hang. c. Click Next. The Select Destination Location window is displayed. d. Specify the desired directory name in the desired shared disk for HP Systems Insight Manager 4.2 installation. (F:\ HPSIM in this white paper). e. Click Next. The Select Start Menu Folder window is displayed. f. Specify the desired Start Menu Folder name or stay with the default setting. (HP Systems Insight Manager in this paper). g. Click Next. The Ready to Install window is displayed. h. Click Install. The Installing window is displayed. Note: A progress bar indicating files are being copied is displayed during the installation, which may take a few minutes. Note: It may take a few more minutes when the Initializing HP Systems Insight Manager dialog is displayed. At the end, the Completing the HP Systems Insight Manager Setup Wizard window is displayed. i. Click Finish to close the Setup HP Systems Insight Manager wizard window. 20. A message box displays a warning message As part of the PMP installation HPSIM service must be stopped and restarted, Click OK to continue. a. A new Welcome to the HP Performance Management Pack Setup Wizard window is displayed. b. Click Next. The Database configuration window is displayed. c. The username and domain name fields display the username and domain name that are logged in. The database server name also displays the database name assigned during the HP Systems Insight Manager 4.2 installation. d. Enter the password in Password field.

21 e. Click Next. The Installing window is displayed. Note: Once the copy process is complete, if your system does not have Web-based agents installed, the Web-based Management dialog box is displayed. You must enter a non-blank password and a confirmation password. This password becomes the administrator account password for all Web-based agents installed on your system. Click Next to continue. Note: A progress bar indicating Creating PMP database is displayed. A folder Performance Management Pack is created in the same location where you have installed HP Systems Insight Manager (F:\ Performance Management Pack in this white paper) and PMP will be installed in it. At the end, Completing the HP Performance Management Pack setup Wizard dialog box is displayed. Click Finish to exit the setup. 21. A new HP Package Setup: Version Control Repository Manager window is displayed. Note: If the Version Control Repository Manager is already installed on your system, this dialog window is not displayed. a. Click Install. Note: If you do not want to install the Version Control Repository Manager, click Close to skip this component, and proceed to step 22. b. Click Install. The Repository Directory window is displayed. i. From a separate Windows Explorer window, create the desired directory in the desired shared drive that is part of your cluster (for this paper we have chosen F:\VCRM). ii. iii. Return to the Repository Directory window of the Version Control Repository Manager Setup window. Click Browse to open the Browse for Folder dialog box. 1. Select the previously created directory in the desired shared drive that is part of your cluster (for this paper we have chosen F:\VCRM). 2. Click OK to close the Browse for Folder dialog box and return to the Repository Directory screen of the Version Control Repository Manager Setup window. iv. Click Perform an initial repository population, if you have ProLiant Support Packs available. Alternatively, the Repository can be populated at later point of time by copying the files to the repository folder. c. Click Next. The Automatic Update window is displayed. d. Make the appropriate selections for automatic download of latest support packs directly from HP web site. e. Click Finish. 22. A message box is displayed which gives a warning message As part of the VMM installation, HPSIM must be stopped and restarted. Click OK to continue. a. Welcome to the HP Virtual Machine Management Pack Setup Wizard is displayed. Click Next to continue. b. Database configuration page is displayed. Enter the password and click Next to continue.

22 c. HP Virtual Machine Management Pack will be installed at this time. Completing the HP Virtual Machine Management pack setup wizard page will be displayed after the installation. Clcik Finish to complete the installation. d. A help page is displayed for configuring System Management Homepage for VCA authentication. Close this window 23. The HP Systems Insight Manager Data Migration Tool for Insight Manager 7 is displayed. a. Click Next. The User-defined Insight Manager 7 Data Import window is displayed. b. Click Next to continue. The User-defined data is imported. c. Click Next. A warring message is displayed regarding authorization and tools. d. Click OK. The Performance Pack 2.1 data Migration Tool is displayed. Figure Click Next. 25. Select Logged data and click Next to start the installation. This starts the PMP 2.1 data import. 26. Click Next after completing the PMP data import. The Custom Install Status is displayed. 27. Click Finished. The Pre-installation/Installation/Post-Installation window is displayed. 28. Click Finish. A message is displayed, Please reboot your system to complete your HP Systems Insight Manager installation. 29. Click OK. 30. Keep IM7 and PPA (which have been taken from shared disk during Step-5 execution of upgrade section) folders in to shared disk. 31. Open ~\HP Systems Insight manager\config\database.props file and note down the database name specified against the keyword hp.database.databasename. 32. Shutdown the Primary node. Upgrading Secondary Node 1. Power On the Secondary node, log into Microsoft Windows as a user with administrator rights. Note: Be sure to log in with the same user id that you used to install the Microsoft SQL Server 2000 Enterprise Edition instance. 2. Make sure that Secondary node owns all the cluster resources. 3. Uninstall Performance Management Pack. Select PMP Uninstall option from Start menu -> Program Files-> Performance Management Pack -> PMP Uninstall. This may not remove

23 complete PMP components from installed folder. Remove PMP 2.1 folder from the shared disk manually. 4. Keep a copy of HP Systems Insight manager and Performance Management Pack folders, which have been created during the primary node upgrade, and remove those folders from the shared disk. 5. Repeat the steps 7 through 29 on secondary node. The screens described in previous steps are not displayed. 6. Open ~\HP Systems Insight manager\config\database.props file and note down the database name specified against the keyword hp.database.databasename. 7. Shutdown the Secondary node. 8. Adjust the HP Systems Insight Manager 4.2 data source name on the Primary node a. Bring up the primary node b. Click Control Panel->Administrative Tools->Data Sources (ODBC). c. Select System DSN. d. Select Insight_v42_0 and click Configure. e. Update the Database Description referring to the database name created on first node Note: Use the database name noted in step 6 of Upgrading Secondary node. f. Click Next. The authentication mode selection window is displayed. g. Click Next. The database selection window is displayed. h. Select the database, which is created by secondary node. Use the database name noted in step 6 of Upgrading Secondary node. i. Click Next. j. Click Finish to complete the configuration. k. Click OK. The summary screen is displayed. l. Click OK to close ODBC Data Source Administrator window.

24 Figure 8. Adjusting the HP Systems Insight Manager 4.2 data source name on the primary node 9. Go to Adding the HP Systems Insight Manager 4.2 cluster resources Adding the HP Systems Insight Manager 4.2 cluster resources To complete the installation of HP Systems Insight Manager 4.2 to the cluster, several cluster resources must be created using Cluster Administrator. Naming the HP Systems Insight Manager 4.2 and SQL Server disk groups 1. Power on Primary node and login to windows as administrator. 2. Power on the Secondary node. 3. Open Cluster administrator tool and confirm that Primary node owns all the cluster resources. 4. In the Cluster Administrator window a minimum of three disk groups are displayed: Cluster Group and the two groups that contain your HP Systems Insight Manager 4.2 program files and the Microsoft SQL Server program files.

25 Figure 9. The Cluster Administrator window a. Rename the group containing your Microsoft SQL Server 2000 instance program files to an appropriate one. In the examples discussed in this paper, it is called HP SIM SQL Disk Group. b. Rename the group containing your HP Systems Insight Manager 4.2 program files to an appropriate one. In the examples discussed in this paper, it is called HP SIM Disk Group. Note: It is not necessary to the functionality of HP Systems Insight Manager to change the names of these disk groups. If you used a pre-existing installation of Microsoft SQL Server 2000, the disk group containing these program files would be likely to already have an appropriate name. Creating the HP Systems Insight Manager 4.2 IP address resource Note: The disk group containing the HP Systems Insight Manager 4.1 program files could also be used for other programs, but for the purposes of this paper HP Systems Insight Manager 4.1 is the only application installed to the disk. 1. In the Cluster Administrator window, select the HP SIM Disk Group from the left pane. In the right pane, right click anywhere and select New Resource from the drop-down menu. 2. The New Resource window is displayed. 3. In the Name field, enter HP SIM IP Address and select IP Address from the Resource type drop-down menu, as shown in Figure Click Next.

26 Figure 10. The New Resource window 5. The Possible Owners window displays. Be sure that the two nodes in your cluster are listed in the Possible Owners pane. 6. Click Next. The Dependencies window is displayed. 7. Specify the other resources in this disk group that a new resource depends on. An IP address in cluster services does not need to establish any dependencies. 8. Click Next. The TCP/IP Address Parameters window is displayed. Note: Dependencies are resources that must be brought online by the cluster service first. Since the IP address resource you are creating here does not depend on any other resource, you need not specify any dependencies. When creating the resource for the HP Systems Insight Manager 4.2 network name, this IP address resource is specified as a dependency. 9. Enter the unique IP address to use for connecting to the HP Systems Insight Manager 4.2 service. This is the IP address (In this white paper ) that the network name resource associates with, and clients can use it to connect to the service, regardless of which server node the group is owned by. 10. Click Finish. A Resource Creation Confirmation window is displayed. 11. Click OK.