Deploying HP SIM 5.x on MSCS clusters on Windows 2008 with SQL Server 2008 Table of Contents Abstract.............................................................................................................................................. 3 Introduction......................................................................................................................................... 3 System infrastructure ...........................................................................................
For more information.......................................................................................................................... 72 Microsoft cluster services................................................................................................................. 72 Microsoft SQL Server 2008 Enterprise Edition ................................................................................... 72 HP SIM 5.x ................................................................................
Abstract This white paper is intended to assist IT professionals in installing HP Systems Insight Manager (HP SIM) 5.x in a Microsoft Cluster Server configuration. Microsoft Windows 2008 Enterprise Server with HP SIM 5.x can be a simple way of obtaining redundancy and failover capability from this powerful management software. Introduction HP SIM 5.
Figure 1: The relationship between HP SIM 5.x, SQL Server 2008, and the cluster disks 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 g roup to work on a separate system. The primary system is for running the Microsoft SQL Server 2008 Enterprise Edition processor and handling remote Microsoft SQL Server commands.
Note: If you already practice separating your transaction log from your data files, you can enhance performance by specifying that the HP SIM 5.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. 1. HP SIM 5.x virtual server IP address and name.
– 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 2008 Enterprise Server and Windows 2008 Failover Clustering – Microsoft SQL Server 2008 Enterprise Server, particularly named instances Hardware and software requirements This paper discusses configuring and administrating a cluster using the followin
5. Select Management and Monitoring Tools in the Windows Component Wizard window. 6. Click Details. Then select Simple Network Management Protocol if it is not selected by default. 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. Note: If you install SNMP after installing a Microsoft Windows operating system service pack, yo u must reinstall that service pack.
Installing Microsoft SQL Server 2008 in a failover cluster environment on the primary system 1. Insert the Microsoft 2008 Extended Edition CD into your CD-ROM drive. This paper assumes that the SQL Server 2008 Installation setup window opens automatically. Figure 2: SQL Server Installation Center 2. Click Installation in the left pane. 3. Click New SQL Server failover cluster installation.
Figure 3: Selecting installation option 4. The Setup Support Rules window appears. This checks that all pre-requisites for installation are met and displays detailed report of the status of each rule.
Figure 4: Setup Support Rules window 5. The Installation Wizard installs SQL Server pre-requisites if they are not installed, including: o .NET Framework 3.5 SP1 o SQL Server Native Client o SQL Server Setup Support Files Click Install to install pre-requisites. 6. The System Configuration Checker verifies the system status of your computer before setup continues. After this check is complete, click Next. 7.
Figure 52: Setup Support Rules window 8. Click Next. The Product Key window appears.
Figure 6: Product Key window 9. Select either Specify a free edition or Enter the product key. If you gave a PID key for a production version of the product, enter the information and click Next. The License Term window appears.
Figure 7: License Terms window 10. Accept the licensing terms and conditions and click Next. The Feature Selection page appears. To end setup, click Cancel. 11. Select the components for installation. A description for each component group appears after you select the feature name. You can select any combination of components, but only the Database Engine and Analysis Services support failover clustering. Other components fun on a single failover cluster node.
Figure 8: Feature Selection window Note: To specify a custom directory for shared components, enter the path in the Shared feature directory field. To change the installation path for shared components, either update the path name in the field or click Browse to navigate to the installation directory. The default installation path is c:\Program Files\Microsoft SQL Server\. 12. Click Next. The Instance Configuration window appears.
Figure 9: Instance Configuration 13. Specify whether to install a default or a named instance: Instance ID suffix – by default, the instance name is used as the Instance ID suffix. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID suffix is MSSQLSERVER.
Figure 10: Disk Space Requirements window 15. The Cluster Resource Group window appears. From the Cluster Resource Group window, specify the location that the SQL Server virtual server resources will be located. To specify the SQL Server cluster resource group name, select one of the following: o Specify an existing group from the SQL Server cluster resource group name dropdown box. o Enter the name of a new group to create. The name Available storage is not a valid group name.
Figure 11: Cluster Resource Group window 16. Click Next. The Cluster Disk Selection window appears.
Figure 12: Cluster Disk Selection window Select the shared cluster disk resource for your SQL Server failover cluster. The cluster disk is location where the SQL Server data will be placed. Only one disk can be specified. Quorum disk cannot be used because it is already in use. If you select the group containing the cluster quoru m resource, a warning appears. HP recommends that you do not install the cluster quorum resource.
Figure 13: Cluster Network Configuration window SQL Server Failover Cluster Network Name – This is the name used to identify your failover cluster instance on the network. Network – Specify the IP type and IP address for your failover cluster instance. Disable the IPV6 IP Type. Select IPV4 address, unselect DHCP, and enter the valid IP address and subnet mask for the SQL Cluster Service. 18. Click Next. The Cluster Security Policy window appears.
Figure 14: Cluster Security Policy window From this page, specify global or local domain groups for clustered services. All resource permissions are controlled by domain-level groups that include SQL Server service accounts as group members. On Windows Server 2008, specify domain groups for SQL Server services. If you are installing an SQL Server 2008 Failover Cluster Instance in a Windows 2000 mixed node domain, you must use domain global groups for SQL Server Clustered Services. 19. Click Next.
Figure 15: Server Configuration window Service Accounts tab - Specify login accounts for SQL Server services. The actual services that are configured here depend on the features you selected to install. You can assign the same login account to all SQL Server services or you can configure each service account individually. You can also specify whether services start automatically, start manually, or are disabled.
Figure 16: Database Engine Configuration window 21. On the Account Provisioning tab, in the Authentication Mode section, select Windows Authentication or Mixed Node Authentication for your instance of SQL Server. If you select Mixed Node Authentication, you must provide a strong password for the built-in SQL Server system administrator account. After a system establishes a successful connection to SQL Server, the security mechanism is the same for both Windows Authentication and Mixed Node. 22.
Figure 17: Data Directories tab Note: Select the root directory as the shared SQL cluster disk. 24. On the FILESTREAM tab, enable FILESTREAM for your instance of SQL Server. 25. Click Next. The Analysis Services Configuration window appears.
Figure 18: Analysis Services Configuration window 26. On the Account Provisioning tab, specify users or accounts that will have administrator permissions for Analysis Services. You must specify at least one system administrator. To add the account that is running SQL Server Setup, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services.
Figure 19: Error and Usage Reporting window Specify the type of reporting services installation to create. Options include: o Native mode default configuration o SharePoint mode default configuration o Unconfigured Reporting Services installation Click Next. The Cluster Installation Rules page appears. 28. The System Configuration Checker runs an additional set of rules to validate the computer configuration with the SQL Server features you have specified.
Figure 20: Ready to Install window 29. Click Install. The Installation Progress window appears and provides installation status of each component on any node in the cluster by selecting the node from the dropdown list.
Figure 21: Installation Progress window 30. After installation, the Complete window provides a link to the summary log for the installation and other important notes. To complete the SQL Server installation process, click Close.
Figure 22: Complete window If a reboot is required, it will be noted on the screen and the nodes are rebooted one at a time. Installing SQL Server 2008 on the secondary system The SQL Server Installation Wizard enables you to install an SQL Server failover cluster on a single node. Setup operations for SQL Server failover clustering have changed for SQL Server 2008. T o install or upgrade an SQL Server failover cluster, you must run the setup program on each node of the failover cluster.
not available from the Microsoft Download Center. The .NET Framework 2.0 SP2 is located in the drive_letter:\ia64\redist\2.0\ folder and the filename is NetFx20SP2_ia64.exe. On x86 and x64 platforms, you must install the .NET Framework 3.5 SP1. This includes SQL Server 2008 Express Edition. Although you might receive a message that the .NET Framework 2.0 SP2 is required for SQL Server 2008 Express Edition, the .NET Framework 2.0 SP2 is currently not available publicly for these platforms. 2.
Figure 24: Adding a node to a SQL Server failover cluster 5. The Setup Support Rules window appears, which checks that all pre-requisites for installation are met and displays detailed report of the status of each rule.
Figure 25: Setup Support Rules window 6. The Installation Wizard installs SQL Server pre-requisites if they are not installed, including: o .NET Framework 3.5 SP1 o SQL Server Native Client o SQL Server Setup Support Files Click Install to install pre-requisites. 7. The System Configuration Checker verifies the system status of your computer before setup continues. After this check is complete, click Next. 8.
Figure 26: Setup Support Rules window 9. Click Next. The Product Key window appears.
Figure 27: Product Key window 10. Select either Specify a free edition or Enter the product key. If you gave a PID key for a production version of the product, enter the information and click Next. The License Term window appears.
Figure 28: Product Key window 11. Accept the licensing terms and conditions and click Next. The Cluster Node Configuration window appears. To end setup, click Cancel.
Figure 29: Cluster Node Configuration window 12. Click Next. The Error and Usage Reporting window appears. 13. Click Next. The Add Node Rules window appears. 14. Click Next. The Ready to Add Node window appears. 15. Click Install. The Add Node Progress window appears and displays the progress of adding the node.
Figure 30: Add Node Progress window 16. Click Finish. The new SQL node is added to the SQL Server failover cluster.
Figure 31: Complete window Installing HP SIM 5.x on the cluster After completing the installation of a Microsoft SQL Server 2008 Enterprise Edition instance or verification of the availability of an existing Microsoft SQL Server 2008 instance, you are ready to proceed with the installation of HP SIM 5.x. If you already have a Microsoft SQL Server 2008 instance, which you would like to use to host the HP SIM 5.x database (for HP SIM 5.x), follow the instructions below for installing HP SIM 5.
Note: Be sure to log in with the same user name that you used to install the Microsoft SQL Server 2008 Enterprise Edition instance. 2. Download the latest version of System Management Homepage (SMH) from http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTyp eId=15351&prodSeriesId=1121486&prodNameId=3288144&swEnvOID=1005&swLang=8&mode=2&task Id=135&swItem=MTX-84b4161b7cd3455fb34ac57586 .
instance being referenced here (HP-SIM-SQLSVR\HP_SIM_INSTANCE in this paper). Otherwise, this step might hang. 12. In the Select Installation Type window, select Custom, and then click Next. 13. Click Custom. The Custom Install-Software Selection window appears. Note: The Custom Install option enables you to specify installing on the desired shared disks (F: and I: in this paper). 14. Click Next. The Service Account Credentials window appears. a.
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 stay with the default setting. For example, we are using HP Systems Insight Manager in this paper. v. Click Next. The Ready to Install window appears. vi. Click Install. The Installing window appears.
ix. Click Close. Note: HP Performance Management Pack (PMP) is not bundled with HP SIM 5.2 or greater. If installing manually, complete the following steps. f. From the Management CD, select the Product tab, and then click HP Performance Management Pack Install link. A warning message appears, stating As part of the PMP installation, HP SIM service must be stopped and restarted. Click OK to continue. A new Welcome to the HP Performance Management Pack Setup Wizard window appears. i. Click Next.
iv. After the VMM installation is complete, the Completing the HP Virtual Machine Management Pack setup wizard page appears. Click Finish to complete the installation. Note: The Server Migration Pack (SMP) and VMM were previously installed as Virtualization Management software. The SMP name has changed to HP Server Migration Pack – Universal Edition Application. i. From the Management CD click Product tab and click HP Server Migration Pack Install.
4. Select Insight_v50_0 and click Configure. Figure 32: ODBC Data Source Administrator 5. Update the Database Description field, referring to the database name created on the secondary system. Note: Use the database name noted in step 2 of the Installing HP SIM 5.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 5). 8.
Figure 33: Adjusting the HP SIM 5.x data source name on the primary system 13. Go to the Adding the HP SIM 5.x cluster resources section. To complete the installation of HP SIM 5.x to the cluster, several cluster resources must be created using Cluster Administrator. Adjusting the HP SIM 5.x data source name on the primary system 1. Start the primary system. 2. Click Control PanelAdministrative ToolsData Sources (ODBC). 3. Select System DSN. 4. Select Insight_v50_0 and click Configure. 5.
Adding the HP SIM 5.x cluster resources To complete the installation of HP SIM 5.x to the cluster, several cluster resources must be created using Cluster Administrator. Creating the HP SIM 5.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 right-click Services and Applications. 4. Select Configure a Service or Application. 5.
Figure 34: High Availability Wizard window 6. Click Next. The Select Service or Application window appears.
Figure 35: Select Service or Application window 7. Select Generic Service from the dropdown menu. 8. Click Next. The Select Service window appears.
Figure 36: Select Service window 9. Select HP Systems Insight Manager and click Next. The Client Access Point window appears.
Figure 37: Client Access Point window 10. Enter the name of the HP SIM service, as HPSIM_2008 in this case, and the IP address of the HP SIM service of the cluster. Click Next. The Select Storage window appears.
Figure 38: Select Storage window 11. Select the storage on which HP SIM is installed. Click Next. The Confirmation window appears listing all the details you have selected in previous windows.
Figure 39: Confirmation window 12. Click Next. The Configure High Availability window appears, followed by the Summary window.
Figure 40: Summary window Creating the OpenSSH Services for HP SIM 5.x Generic Service Resource 1. In the Failover Cluster Management software, right-click the HP SIM service under Services and Applications. 2. Click Add a resourceGeneric Service.
Figure 41: Generic Service selection 3. In the Select Service window, select OpenSSH Server.
Figure 42: Select Service window 4. Click Next. The Confirmation window appears and displays the default service name and parameters.
Figure 43: Confirmation window 5. Click Next. The Summary window appears.
Figure 44: Summary window 6. Click on Finish. The OpenSSH service appears under HPSIM_2008. Creating the Pegasus WMI Mapper Services for HP SIM 5.x Generic Service Resource 7. In the Failover Cluster Management software, right-click the HP SIM service under Services and Applications. 8. Click Add a resourceGeneric Service. The Select Service window appears. 9. Select Pegasus WMI Mapper.
Figure 45: Selecting Pegasus WMI Mapper 10. Click Next. The Confirmation window appears.
Figure 46: Confirmation window 11. Click Next. The Summary window appears.
Figure 47: Summary window 12. Click Finish. Pegasus WMI Mapper appears under HPSIM_2008. Creating the Version Control Repository Manager (VCRM) 5.x for HP SIM 5.x Generic Service Resource You must create the VCRM generic service resource, if you opted to install VCRM in the Installing HP SIM 5.x on the primary system section. 1. In the Failover Cluster Management software, right-click the HP SIM service under Services and Applications. 2. Click Add a resourceGeneric Service.
Figure 48: Select Service window 3. In the Select Service window, select HP Version Control Repository Manager.
Figure 49: Select Service window 4. Click Next. The Confirmation window appears and displays the default the service name as HP Version Control Repository Manager (cpqsrhmo) and parameters.
Figure 50: Confirmation window 5. Click Next. The Summary window appears.
Figure 51: Summary window 6. Click Finish. 7. Right-click HP Version Control Repository Manager and select Properties.
Figure 52: Selecting Properties 8. The HP Version Control Repository Manager properties page appears. 9. Select the Dependencies tab and insert the dependency as the disk which you have selected for HP SIM installation. Click Apply, and then OK.
Figure 53: HP Version Control Repository Manager Properties window Bringing the virtual group containing the HP SIM 5.x resources online 1. In the Failover Cluster Management software, right-click the HP SIM service under Services and Applications. 2. Select Bring this service and application online from the dropdown menu. If configured properly, all resources should come online.
Figure 54: Bringing services and applications online window All the services (HP System Insight Manager, Open SSH Server, Pegasus WMI Mapper (WMI Mapper), HP Version Control Repository Manager) come online automatically.
Figure 55: Summary showing services and applications coming online The installation is now complete. Validating the installation To be sure that the HP SIM 5.x service can be moved between both systems, perform the followi ng steps from either one of the cluster systems: 1. Open the Cluster Administrator and connect to the cluster. 2. In the Cluster Administrator window, on the left pane, right-click on the disk group containing the HP SIM 5.x program files.
Note: The HP SIM 5.x icon on the Windows desktop of each system was created by the installation of HP SIM 5.x as a handy shortcut for a regular standalone server only. This icon is no longer applicable at this point because the HP SIM 5.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 56: The HP SIM 5.x home page Note: Navigate to OptionsDiscovery. 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 5.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 10.0.0.
indicating WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED appears. When that happens, simply use the name of the other system instead.
Troubleshooting Note: 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: 1. Make the primary system active and execute mxagentconfig to push the SSH key to primary system itself. AND 2. Make secondary system active and execute mxagentconfig to push the SSH key to secondary system itself.
For more information Refer to the following for more information regarding the topics referenced in this paper. Microsoft cluster services Clustering basics www.microsoft.com/windows2000/technologies/clustering/default.asp Steps to setting up a Microsoft cluster www.microsoft.com/windows2000/techinfo/planning/server/clustersteps.asp HP ProLiant clusters http://h18000.www1.hp.com/solutions/enterprise/highavailability/microsoft/index.html Microsoft SQL Server 2008 Enterprise Edition System requirements www.
