Deploying HP SIM 6.x on MSCS Clusters on Windows 2008 with SQL Server 2005 White Paper

Transcription

1 Deploying HP SIM 6.x on MSCS Clusters on Windows 2008 with SQL Server 2005 White Paper Subtitle Table of Contents Abstract... 2 Introduction... 2 Installing HP SIM on Windows 2008 failover cluster with SQL Server System infrastructure... 3 Storage configuration... 4 IP addresses... 4 Target audience... 5 Hardware and software requirements... 5 Setting up the failover environment... 5 Installing SNMP... 5 Activating the HP cluster MIB agents... 6 Activating the HP cluster MIB agents... 6 Installing the Microsoft SQL Server 2005 Enterprise Edition... 7 Installing a clustered instance of the Microsoft SQL Server 2005 Enterprise Edition on first node... 7 Installing HP SIM 6.x on the cluster Installing HP SIM 6.x on the primary system Installing HP SIM 6.x on the secondary system Adjusting the HP SIM 6.x data source name on the primary system Adding the HP SIM 6.x cluster resources Creating the HP SIM 6.x Generic Service Resource Creating the OpenSSH Services for HP SIM 6.x Generic Service Resource Creating the Pegasus WMI Mapper Services for HP SIM 6.x Generic Service Resource Creating the Version Control Repository Manager (VCRM) 6.x for HP SIM 6.x Generic Service Resource. 43 Bringing the virtual group containing the HP SIM 6.x resources online Validating the installation Troubleshooting For more information Microsoft cluster services Microsoft SQL Server 2005 Enterprise Edition HP SIM 6.x... 56

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

3 Figure 1: The relationship between HP SIM 6.x, SQL Server 2005, and the cluster disks Installing HP SIM on Windows 2008 failover cluster with SQL Server 2005 If you are installing HP SIM 6.x into an environment without a Microsoft SQL Server 2005 Enterprise Edition instance already installed, go to for steps to install a clustered named instance of Microsoft SQL Server 2005 Enterprise Edition. This named instance can host the HP SIM 6.x databases and any other production databases you might require in your environment. If an instance of Microsoft SQL Server 2005 Enterprise Edition already exists in your cluster, you can go to for steps to install HP SIM 6.x and the process to make it highly available. System infrastructure Figure 1 details how to configure a cluster for enhanced performance after all components are installed. With this configuration, you can distribute the load by designing each virtual group to work on a separate system. The primary system is for running the Microsoft SQL Server 2005 Enterprise Edition processor and handling remote Microsoft SQL Server commands. The secondary system is for running the HP SIM 6.x service and all the component services it requires. 3

4 Storage configuration Figure 1 displays the relationship between Microsoft SQL Server 2005 Enterprise Edition instances and HP SIM 6.x. 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 SIM 6.x database. The first shared disk contains the Microsoft SQL Server 2005 Enterprise Edition data file s. For the examples discussed in this paper, the drive is I:. The other shared disk contains the HP SIM 6.x program files. For the example discussed in this paper, this drive is F:. If you already practice separating your transaction log from your data files, you can enhance performance by specifying that the HP SIM 6.x transaction log be 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. HP SIM 6.x virtual server IP address and name Function: To act as the virtual server IP address and name for HP SIM 6.x event reception. You specify this name and address to connect to HP SIM 6.x through Microsoft Internet Explorer. Suggested action: All SNMP systems that report events to HP SIM 6.x should use this IP address and name for the location of the Event Consolidator, the SNMP trap destination. For the examples discussed in this paper, the IP address is MSCS cluster IP address/name Function: To act as the virtual server IP address and name for the MSCS software. Suggested action: MSCS management tools would use this address to get status and reconfigure the MSCS software. For the examples discussed in this paper, the IP address is Microsoft SQL Server 2005 virtual server IP address and name Function: To act as the virtual server IP address and name for the Microsoft SQL Server 2008 Enterprise Edition database software. This software is used to extract, manipulate, or back up the HP SIM 6.x database. Suggested action: The HP SIM 6.x ODBC data source uses this as the location where the HP SIM 6.x DSN points. In the examples discussed in this paper, the IP address is MSCS primary system IP address and name Function: To serve as the TCP/IP address and name of the specific Microsoft Windows server host. Suggested action: Any software that references system-specific functions uses this address to connect to this system. In the examples discussed in this paper, the IP address is MSCS secondary system IP address and name Function: To serve as the TCP/IP address and name of the specific Microsoft Windows server host. Suggested action: Any software that references system-specific functions uses this address to connect to this system. For the examples shown in this paper, the IP address is

5 Target audience This white paper is intended for users who have an excellent understanding of the following concepts and services: Basic clustering concepts Basic Windows 2003 services Basic Windows 2008 services Advanced TCP/IP and Domain Name System (DNS) network concepts In addition, readers must be familiar with installing and administering these products: Microsoft Windows 2003 Enterprise Server and MSCS Microsoft SQL Server 2005 Enterprise Edition, particularly named instances Microsoft Windows 2008 Enterprise Server and Windows 2008 Failover Clustering Hardware and software requirements This white paper discusses configuring and administrating a cluster using the following products, which use a two-system HP ProLiant cluster with each system satisfying all the hardware requirements for HP SIM 6.x. For best results, each system must meet the recommended memory and processor speed requirements. One free shared disk for the HP SIMO 6.x program files At least one free shared disk for Microsoft SQL Server 2005 Microsoft Windows 2003 Enterprise Server with Service Pack 1 Microsoft Cluster Services Microsoft Internet Explorer 6.0 with Service Pack 1 or later Simple Network Management Protocol (SNMP) Microsoft SQL Server 2005 Enterprise Edition with Service Pack 3 or greater HP SIM 6.x HP Management CD 7.1 or later and related ProLiant Support Packs Setting up the failover environment This section of the paper assumes that you log in to each of your cluster systems with the same administrator credentials that you are using to access all of the HP SIM 6.x and Microsoft SQL Server 2005 components that are being set up. Installing SNMP SNMP is a prerequisite for the HP SIM 6.x installation. The following section details how to install SNMP to the cluster systems intended to host HP SIM 6.x. 5

6 SNMP Services must be installed for Windows Insert the Microsoft Windows 2008 Enterprise Server CD into 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. If not selected by default, select Simple Network Management Protocol. 7. Click OK. The Windows Component Wizard window appears. 8. Click Next. Wait for the file copying to complete. 9. Click Finish. 10. Remove the CD. If you install SNMP after installing a Microsoft Windows operating system service pack, you must reinstall that service pack. 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 agents 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 SIM 6.x that these MIB agents be installed on your cluster to discover and identify itself as a cluster, as well as recognizing its systems as such. If your cluster was set up following the HP Systems Insight Manager 6.x Installation and Configuration guides that ship with the cluster, then the HP Management Agents and all the MIBs (including the HP Cluster MIB Agents) are installed on each system. Activating the HP cluster MIB agents 1. Select Start Settings Control Panel. 2. Double-click HP Management Agents. The HP Management Agents for Servers window appears. 3. Be sure the Services tab page window appears. 4. Double-click Clustering Information from the Inactive Agents list box to add it to the Active Agents list box. You might have 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 restart the management agents. 6

7 Installing the Microsoft SQL Server 2005 Enterprise Edition The Microsoft SQL Server 2005 Enterprise Edition is required for the installation of HP SIM 6.x to be highly available. If you already have an instance of Microsoft SQL Server Enterprise Edition installed, then you can create the HP SIM 6.x database and attach it to the existing server. This section assumes that you already have a working two-system cluster with at least two free logical drives, one for the Microsoft SQL Server 2005 data files and another for the HP SIM 6.x program files. Installing a clustered instance of the Microsoft SQL Server 2005 Enterprise Edition on first node 1. Insert the Microsoft SQL 2005 Extended Edition CD. You must have the SQL Server 2005 Installation setup window set to open automatically. 2. Click Install. The installation begins. The user license agreement appears. 3. Accept the license agreement, and then click Next. 4. The Prerequisites window appears if it is not installed. Click Install. Figure 2: Installing Prerequisites 7

8 Figure 3: Required components installed successfully 5. After Prerequisites is installed, click Next for SQL server 2005 installation. 8

9 Figure 4: Microsoft SQL Server 2005 Setup Figure 5: Cluster Node Configuration 6. Click Next. The Remote Account Information page appears. 9

10 Figure 6: Remote Account Information 7. After the configuration check is complete on all systems, a summary appears. Review any warning or error messages, and correct any issues until there are no messages in the Summary window. 10

11 Figure 7: System Configuration Check 8. Click Next. The Microsoft SQL server installation window appears. 9. Click Next. 10. Enter registration information, and then enter a valid product ID. 11. Select components to install in the Components to install window. Available components include Database services, Create SQL server Failover Cluster, Workstation components, books Online, and development tools. 11

12 Figure 8: Components to Install 12. Click Advanced to ensure that Management Tools is selected. The Management Tools option is not installed by default and must be selected. 13. Select Management Tools from client tools in the Feature selection window. 12

13 Figure 9: Feature selection 14. Click Next. The Instance name window appears. 15. Select Name Instance, and then enter one instance name. Common instance name is required to install HP SIM and fail over for HP SIM. 16. Click Next. 17. Enter the Virtual Server name (SQL-SRV). 13

14 Figure 10: Virtual Server Name 18. Click Next. The Virtual Server Configuration window appears. 19. Enter the Virtual Server IP address. 14

15 Figure 11: Virtual server information If the system you are installing on is a two node MSCS box with a private and public network, you must select public when assigning a new public IP address to the SQL 2005 Virtual Server IP address. This can be selected in the Network to use field on the Virtual Server Configuration window. 20. After you have entered the Client Access Point (CAP) information, click Next. The Cluster Group Selection window appears. 21. Select the Resource container that was configured in the failover Cluster Management plug-in. If there is more-than-one storage system is located in the group, then select the correct system from the list in the Cluster Group Configuration window. 15

16 Figure 12: Cluster Group Configuration 22. Click Next. The Cluster Node Configuration window appears. By default the installation program assumes that all nodes are part of the cluster. In this example, we have two nodes that must have SQL Server 2005 installed and participate as part of the SQL clustered instance. Be sure that in the selected nodes section, the second node of the cluster and in required node with localhost (current system) is displayed. 23. Click Next. The In Service account window appears. 24. Enter the user name and password for an account with permission to run the service. For example, the domain administrator account. 16

17 Figure 13: Service Account Do not select the Customize for each service account information checkbox. 25. Enter the group names to run different services in the Domain Groups for Clustered Services window. You must complete the remaining steps to enter the group names for services. Follow the steps and create one group in the domain and use the same group for all the services. 26. Under the Administrators group, create one group named sqlaccts in the domain. 27. Enter the group sqlaccts name for all the services. 17

18 Figure 14: Domain groups for clustered services 28. Click Next. The Authentication mode page appears. 29. Select Windows authentication mode. 30. Click Next. The Collation settings window appears. 31. By default Case-sensitive, for use with 1252 Character set is selected. If not, be sure to select the options. 18

19 Figure 15: Collation settings 32. Click Next in the Error and send Report Settings window. The Ready to Install window appears. 33. Verify that all selected components are displayed and then click Install. The Set Progress window appears where you can monitor the installation progress of each component on any of the nodes in the cluster by selecting the node from the dropdown list. After setup is complete, all of the components should have a green check beside them and show a status of Set Up Finished. If a reboot is required, then a message appears. Reboot the nodes one by one. If you are using Windows Server 2008 and a warning is shown after installation, then disable UAC in Windows 2008 after installation. 19

20 Figure 16: Program Compatibility Assistant If a reboot is required, it will be noted on the screen. Reboot the nodes one by one. SQL 2005 Service pack 2 should be installed for proper working of failover clustering in windows 2008 for better performance Installing HP SIM 6.x on the cluster After completing the installation of a Microsoft SQL Server 2005 Enterprise Edition instance or verification of the availability of an existing Microsoft SQL Server 2005 instance, y ou are ready to proceed with the installation of HP SIM 6.x. If you already have a Microsoft SQL Server 2005 instance, which you would like to use to host the HP SIM 6.x database (for HP SIM 6.x), perform the procedure for installing HP SIM 6.x,. Important: Before you begin, be sure you have all system and pre-installation requirements fulfilled. In addition, the Microsoft SQL Server 2005 service should be running. To be sure that you meet these requirements, see the HP Systems Insight Manager 6.x Installation and Configuration guides on the HP Management CD. 1. Ensure that both systems are running cluster services before installation. Also, be sure that the SQL server instance, to which you are installing the HP SIM 6.x database, is running. 2. Ensure that the cluster system that is to be installed with HP SIM 6.x owns the clustered disks. 3. Review the HP Systems Insight Manager 6.x Installation and Configuration guides to be sure that you have the right prerequisites for installation. 4. Review the HP Systems Insight Manager 6.x Release Notes. Installing HP SIM 6.x on the primary system 1. On the primary system, log in to Microsoft Windows as a user with administrator rights. 20

21 Be sure to log in with the same user name that you used to install the Microsoft SQL Server 2005 Enterprise Edition instance. Download the latest version of System Management Homepage (SMH) from &prodSeriesId= &prodNameId= &swEnvOID=1005&swLang=8&mode=2&taskId=135 &switem=mtx-84b4161b7cd3455fb34ac From the link specified select the appropriate sever and operating system and download the executable for SMH. SMH and later support clustering. 2. Start the installation of SMH by executing the downloaded setup file. For example, cp00xxxx.exe, where XXXX represents the number. The Welcome to the Setup Wizard for the System Management Homepage appears. a.click Next. The Operating System Groups page appears. b.create the appropriate groups, and then click Next. The User Access page appears. c. Select the appropriate options, and then click Next. The Trust mode page appears. d.select a trust mode, and then click Next. The IP Binding page appears. e. If required, configure the IP bindings. f. Click Next. The IP Restricted logins page appears. g. If required, configure the IP restricted logins. h. Click Next. The Summary page appears. i. Click Next. The SMH installation begins. j. Click Finish to complete the installation of SMH. 3. Edit the smhpd.xml file located in c:\hp\hpsmh\conf, and then add the following tag after the <localaccess-type>anonymous</localaccesstype> tag: <monitor-ip-changes>1</monitor-ip-changes> 4. Save the smhpd.xml file. 5. Restart the SMH service from the service console under Administrative tools. 6. Insert the HP Management CD. The CD includes an AutoRun feature that displays the ProLiant Essentials Foundation Pack-management CD window. If AutoRun is disabled on the primary system, go to D:\autorun.exe. If this is the first time you are installing from this version of the management CD, you must accept the license agreement for the CD. 7. Select Products. 8. Click the HP SIM 6.x- Windows Install link. The HP Systems Insight Manager Set up window appears. 9. Click Install. The Welcome to the HP Systems Insight Manager Installer window appears. 10. After completing the system inspection, the Database Configuration window appears. a.the Username field displays the user name that is logged in. b.enter the password in the Password field. c. The Domain field displays the user domain used to log into the system. 21

22 d.enter the name of the Microsoft SQL Server 2005 Enterprise Edition instance that you created. For this paper, HP-SIM-SQLSVR\HP_SIM_INSTANCE is used. If the credentials specified cannot be validated, a message appears, stating You are not able to continue with the installation until the account information is validated. Be sure to close any application, such as Microsoft SQL Server Enterprise Edition Manager that connects to the Microsoft SQL Server 2005 Enterprise Edition instance being referenced here (HP-SIMSQLSVR\HP_SIM_INSTANCE in this paper). Otherwise, this step might hang.. Default port for SQL is If Named instance of SQL server is used, then dynamic port number should be given in port field for the SQL server. 11. In the Select Installation Type window, select Custom, and then click Next. 12. Click Custom. The Custom Install-Software Selection window appears. The Custom Install option enables you to specify installing on the desired shared disks (F: and I: in this paper). 13. Click Next. The Service Account Credentials window appears. The Username field displays the user name that is logged in. Enter the password in the Password field. The Domain field displays the user domain used to log in to the system. 14. Click Next. The Custom Install-Summary window appears. 15. Click Install. The installation of HP SIM 6.x and its dependent services is initiated. a,a new Welcome to the OpenSSH Services for HP Systems Insight Manager Setup Wizard window appears. Read the welcome message, which reminds you to close other applications. i. Click Next. The Select Destination Location window appears. ii.specify the desired directory to be on the local drive of the current system. In this paper, the default C:\Program Files\OpenSSH. iii. Click Next. The OpenSSH Service Log on as User window appears. The Username field displays the user name that is logged in. Enter the password in the Password field. The Domain field displays the user domain used to log into the system. 22

23 iv Click Next. The Ready to Install window appears. v. Click Install. The Installing window appears. A progress bar indicating files are being coped appears during the installation of this service. At the end, the Completing the OpenSSH Services Manager Setup Wizard window appears vi. Click Finish to close the Setup OpenSSH Services for HP Systems Insight Manager wizard window. b.a new Welcome to the Pegasus WMI Mapper V2.7.x Setup Wizard window appears. i. Click Next. The End-User License Agreement window appears. ii. Select I accept the terms in the License Agreement. iii. Click Next. The Choose Setup Type window appears. iv. Select Typical. The Ready to Install window appears. v. Click Install to continue to the Installing Pegasus WMI Mapper v2.7.x window. A progress bar indicating files are being copied appears during the installation of this service. WMI Mapper is installed in c:\program Files\The Open Group\WMI Mapper. At the end the Completing the Pegasus WMI Mapper v2.7.x Setup Wizard window appears. vi. Click Finish to exit the WMI Mapper setup wizard. c. A new Welcome to the HP Systems Insight Manager Setup Wizard window appears. i. Click Next. The Select Destination Directory window appears. ii. Specify the desired directory to be in the desired shared disk. For example, we are using F:\HPSIM in this paper. iii. Click Next. The Select Start Menu Folder window appears. iv. Specify the desired Start Menu Folder name or use the default setting. For example, the example uses HP Systems Insight Manager. v. Click Next. The Ready to Install window appears. vi. Click Install. The Installing window appears. A progress bar indicating files are being copied appears during the installation, which might take a few minutes. It might take a few more minutes with the Initializing HP Systems Insight Manager window appears. At the end, the Completing the HP Systems Insight Manager Setup Wizard window appears. vii. Click Finish to close the Setup HP Systems Insight Manager wizard window. 23

24 d.a new Remote Support Pack Installation window appears. i. Click Agree. ii. Click Next to proceed with the default path (c:\program Files\hp) on the Please specify where you would like the Remote Support Pack component to be installed page. iii. Click Yes in the Confirmation installation directory window. iv. Select the privacy settings that are appropriate for your environment, and then click Next. Figure 17: Remote Support Software Manager Initialization e. A new HP Package Setup: Version Control Repository Manager window appears. If the Version Control Repository Manager is already installed on your system, this window is not displayed. If you do not want to install the Version Control Repository Manager, click Close to omit this component. Go to step 13f. 24

25 i. Click Install to proceed to the Repository Directory window. 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 are using F:\VCRM. ii. Return to the Repository Directory window. iii. Click Browse. The Browse for Folder window appears. iv. Select the previously created directory in the desired shared drive that is part of your cluster. For this paper, we are using F:\VCRM. v. Click OK to close the Browse for Folder window and return to the Repository Directory window. Click Perform an initial repository population, if you have ProLiant Support Packs available. Alternatively, the repository can be populated later by copying the files to the repository directory. vi. Click Next. The Automatic Update window appears. vii.make the appropriate selections for automatic download of latest support packs directory from the HP website. viii. Click Finish. The HP ProLiant Setup: Version Control Repository Manager window appears. ix. Click Close. 22. Click Next from the Custom Install Status window on the HP Systems Insight Manager Installer window to close the window. 23. Click REGISTER LATER from the Registration window. 24. Select Yes, reboot system now in the Installation complete window, and then click Finish. 25. Click OK. 26. Shutdown the system. Installing HP SIM 6.x on the secondary system To have a clustered installation of HP SIM, the secondary system in the cluster must complete the installation process, 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 that you used on the primary system. Be sure that the secondary system owns all of the clustered disks. Important: Rename the existing HP SIM 6.x folder and all its installed components folders (such as PMP, VCRM, VMM, and SMP) from the shared disk. For this paper, we are using F:\HPSIM, F:\Performance Management Pack\, F:\Virtual Machine Management, F:\Server Migration Pack, and F:\VCRM) before you continue. Be sure to specify the same locations and same folder name on the shared disk as in the primary system installation. 25

26 To install the system: 1. At your secondary system, repeat steps 1-20 in the Installing HP SIM 6.x on the primary system section. 2. Select No, will reboot later. In the Installation complete window, click Finish. 3. Open ~\HP Systems Insight Manager\config\databaseprops file and note the database name specified against the keyword hp.database.databasename. 4. Shutdown the secondary system. Adjusting the HP SIM 6.x data source name on the primary system 1. Start the primary system. 2. Click Control Panel Administrative Tools Data Sources (ODBC). 3. Select System DSN. 4. Select Insight_v50_0 and click Configure. 5. Update the Database Description field, referring to the database name created on the secondary system. Use the database name noted in step 2 of the Installing HP SIM 6.x on the secondary system section. 6. Click Next. The Authentication mode selection window appears. 7. Click Next. The Microsoft SQL Server DSN Configuration window appears (Figure 14). 26

27 Figure 18: Server DSN Configuration 8. Select the database, which is created by the secondary system. Use the database name indicated in the Installing HP SIM 6.x on the secondary system section. 9. Click Next. 10. Click Finish to complete the configuration. A Summary window appears. 11. Click OK. The ODBC Data Source Administrator window appears. 12. Click OK. to close the ODBC Data Source Administrator window appears. Adding the HP SIM 6.x cluster resources To complete the installation of HP SIM 6.x to the cluster, several cluster resources must be created using Cluster Administrator. Creating the HP SIM 6.x Generic Service Resource 1. Start the primary system and log in to Windows as a user with administrator rights. 2. Start the secondary system. 3. Open the Cluster Administrator window, and then right click on the Services and Applications in the left pane of Failover Cluster Management window. Select Configure a Service or Application. 27

28 Figure 19: Failover Cluster Management 4. Under the High Availability Wizard Page, the Before you begin page appears. Click Next. 5. The Select Service or Application Page appears. Choose Generic Service from the menu, and then click Next. 28

29 Figure 20: Generic Service 6. The Select Service page appears. Select the HP System Insight Manager from the given services, and then click Next. 29

30 Figure 21: Select the service you want to use from the list 7. The Client Access Protocol window appears. Give the name of the HP SIM service as HPSIM_2008 (in this example)_and IP address of the HP SIM Service of the cluster, and then click Next. 30

31 Figure 22: Client Access Point 8. The Select Storage window appears. Select the storage on which HP SIM is installed and then click Next. 31

32 Figure 23: Select Storage 9. The Confirmation Page appears, detailing the selections you made in the previous windows. Click Next. 32

33 Figure 24:Confirmation window 10. The Configure High Availability window appears with the progress bar for configuring the service, and then the Summary Page appears. 33

34 Figure 25: Configure High Availability 11. Click Finish. The HP SIM service appears under Services and Applications. 34

35 Figure 26: Services and Applications Summary Creating the OpenSSH Services for HP SIM 6.x Generic Service Resource 1. Right click on HP SIM Service under Services and Application. Click Add a resource Generic service in the left pane of the Failover Cluster Management window. 35

36 Figure 27: Generic Service 2. The Select Service Page appears. Select Open SSH Service from the list, and then click Next. 36

37 Figure 28: Select the service you want to use from the list 3. The Confirmation Page appears and displays the default service name as Open SSHd service and parameters. Click Next. 37

38 Figure 29: You are ready to make a Generic Service 4. The Summary Page appears. Click Finish. Open SSH service appears under hpsim_sql

39 Figure 30: The new resource was successfully created and configured Creating the Pegasus WMI Mapper Services for HP SIM 6.x Generic Service Resource 1. Right-click HP SIM Service under Services and Application. Click Add a resource Generic service in the left pane of the Failover Cluster Management window. 39

40 Figure 31: Generic Service 2. The Select Service Page appears. Select Pegasus WMIMapper from the list, and then click Next. 40

41 Figure 32: Select Service 3. The Confirmation Page appears. It displays the default service name as Pegasus WMIMapper (WMIMapper) service and parameters. Click Next. 41

42 Figure 33: Confirmation 4. The Summary Page appears. Click Finish. Pegasus WMIMapper service appears under hpsim_sql

43 Figure 34: Summary 1. Right click the resource Pegasus WMI Mapper under the HP SIM Generic Service Resource and select Properties. 2. Select the General tab and delete the contents of the Startup Parameters that was added during the creation of the WMI Mapper Resource. Leave Startup Parameters blank. Creating the Version Control Repository Manager (VCRM) 6.x for HP SIM 6.x Generic Service Resource A VCRM generic service resource must be created if you opted to install the VCRM in step 8 of the Installing HP SIM 6.x on the primary system section. 1. Right-click HP SIM Service under Services and Application. Click Add a resource Generic service in the left pane of the Failover Cluster Management window. 43

44 Figure 35: Generic Service 2. The Select Service page appears. Select HP Version Control Repository Manager service from the list, and then click Next. 44

45 Figure 36: Select Service 3. The Confirmation Page appears. It displays the default service name as HP Version Control Repository Manager (cpqsrhmo) service and parameters. Click Next. 45

46 Figure 37: Summary 4. The Summary Page appears. Click Finish. Hp Version Control Repository Manager service is appears under hpsim_sql

47 Figure 38:Service 5. Right-click HP Version Control Repository Manager service, and then click the Properties link. 47

48 Figure 39: Summary of hpsim_sql The HP Version Control Repository Manager Properties page appears. 7. Click the dependencies tab, and then insert the dependency as the disk, which was chosen for HP SIM installation. Click Apply, and then click OK. 48

49 Figure 40: HP Version Control Repository Manager Properties Bringing the virtual group containing the HP SIM 6.x resources online 1. Right-click the HPSIM Service under Services and Applications in the left pane, and then select the Bring this service and application online from the menu. If configured properly, all resources come online. 49

50 Figure 41: Bring this service or application online 2. All services (HP System Insight Manager, Open SSH Server, Pegasus WMI Mapper (WMI Mapper), HP Version Control Repository Manager) come online automatically. 50

51 Figure 42: Summary of hpsim_sql The installation of HP SIM 6.x is complete. Validating the installation To be sure that the HP SIM 6.x service can be moved between both systems, perform the following steps from either one of the cluster systems: 1. Open the Cluster Administrator, and then connect to the cluster. 2. In the Cluster Administrator window, on the left pane, right-click the disk group containing the HP SIM 6.x program files. For example, HP SIM Disk Group is used in this paper. Select Move Group. Be sure that the group fails-over to the other system and that all of the HP SIM 6.x resources come online. 3. After the failover occurs on the second system, restart the System Management Homepage service manually on the second system. 4. After waiting a few minutes to ensure that the HP SIM 6.x service has restarted, go to the HP SIM 6.x service through a Web browser using the network name you specified when creating the HP SIM 6.x network name resource (W2K-CLUS-HPSIM in this paper). The URL specifies the virtual network name and the port of the HP SIM 6.x 51

52 You must specify the port 280 in the URL of your Web browser to connect to the HP SIM 6.x service. To learn more about connecting to HP SIM 6.x, refer to the HP Systems Insight Manager 6.x Technical Reference Guide. The HP SIM 6.x icon on the Windows desktop of each system was created by the installation of HP SIM 6.x as a handy shortcut for a regular standalone server only. This icon is no longer applicable at this point because the HP SIM 6.x is clustered. The icon should be deleted from the desktop of each system to avoid future confusion. 5. A security alert displays. Click OK. The Login window appears. 6. Be sure to log in with the appropriate username, password, and domain for your cluster. Figure 43: HP Systems Insight Manager Important: Clustering allows any system in the cluster to own the virtual group containing the HP SIM 6.x resources. With the creation of a virtual network 52

53 name and IP address specific to the HP SIM 6.x service, clients can connect to the service without knowing which system currently owns the virtual group. When browsing to the virtual name for HP SIM 6.x rather than the name of the server that owns the virtual group, a security certificate for HP SIM 6.x is sent to your browser. If your browser is configured to warn about invalid site certificates, a security alert displays when connecting to the HP SIM 6.x virtual server (which was created earlier in this paper). This alert indicates that the name you have connected to does not match the name on the certificate. This is because the name on the certificate is the name of the secondary system and not that of the virtual server. To learn more about the browser security alert, refer to the HP Systems Insight Manager 6.x Technical Reference Guide located on the HP Management CD (version 7.1 or greater). 7. After you have successfully logged in, the HP SIM 6.x home page appears as shown in Figure

54 Figure 44: HP SIM 6.x home page Important: Navigate to the Options Protocol Settings WMI Mapper Proxy. Check the Host list and ensure that the cluster virtual name is used instead of any of the system names (delete the system name, if it is used, and add the cluster virtual name). Navigate to Options Discovery. Select System Automatic Discovery task and click Edit. The Edit Discovery page appears. Take a look at the Ping inclusion ranges list box (on the left side of the right frame, near the bottom of the screen). Note that HP SIM 6.x automatically generates a range for each of the IP addresses the current system has. Because one of these ranges is based on the cluster heartbeat IP address (generally of the form ), that range would not be of any use, and you should remove it from the list in order to prevent future confusion. Be sure to click OK. 8. Return to the Cluster Administrator. 9. Repeat steps 2 through 6 in the HP SIM Installation Guide using the other system. 54

55 These steps are to ensure HPSIM is working after failover. 10. You can use the active system name to establish a command-line session to the cluster HP Systems Insight Manager service from a client system that has an OpenSSH client installed, using SSH. The only exception is when the disk group containing the HP SIM program files (HP SIM Disk Group in this paper) has failed-over to the other system. In this case, a failing message indicating WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED appears. When that happens, use the name of the other system instead. Troubleshooting This section is applicable only if PMP has been installed manually. Problem: Error during MSA tool execution. Solution: Execution of MSA tools might fail due to SSH key mismatch. For proper execution of MSA tools, perform the following: Make the primary system active and execute mxagentconfig to push the SSH key to primary system itself. Make secondary system active and execute mxagentconfig to push the SSH key to secondary system itself. Problem: Unable to Single Sign-On to client. Solution: Client should have the certificate/name of both cluster systems in it. If the Trust mode is Trust By Certificate on the client, then open the Web agent certificate, cert.pem file, from both the systems and import them into client Web agent. If the Trust mode is Trust By Name on the client, then include both the system names in trusted server name list. Problem: Unable to get the second system certificate when browsing to SMH Solution: Import the second system certificate on to the first system. 55

56 For more information Refer to the following for more information regarding the topics referenced in this paper. Microsoft cluster services Clustering basics Steps to setting up a Microsoft cluster HP ProLiant clusters Microsoft SQL Server 2005 Enterprise Edition System requirements White papers on SQL Server HP SIM 6.x Overview and features HP Systems Insight Manager quick specs HP Partitioning Continuum, HP, 2008 HP ENSAextended technical overview, HP, 2008 HP Utility Data Center Overview, HP, 2008 Technology for better business outcomes Copyright 2010 Hewlett-Packard Development Company, L.P. 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. Microsoft, Windows, and Windows Server are registered trademarks of Microsoft Corporation , August