Using HP Insight Software from a Highly Available Central Management Server with Microsoft Cluster Service

ManualsBrandsHP ManualsSoftwareHP Matrix Operating Environment w/Insight Control 24x7 Supp 1 Server Lic

Using HP Insight Software from a Highly Available Central

Management Server with Microsoft Cluster Service

Abstract.............................................................................................................................................. 3

Introduction......................................................................................................................................... 3

Getting started .................................................................................................................................... 5

Target audience............................................................................................................................... 6

Hardware and software requirements................................................................................................. 6

System infrastructure......................................................................................................................... 7

Storage configuration ....................................................................................................................... 7

IP addresses .................................................................................................................................... 7

Setting up the failover environment ........................................................................................................ 8

Installing Insight software prerequisites ............................................................................................... 8

Installing the ProLiant Support Pack .................................................................................................... 9

Activating the HP cluster MIB agents ............................................................................................... 9

Installing the Microsoft SQL Server 2005 Enterprise Edition................................................................... 9

Installing Insight software components on the cluster .............................................................................. 13

Installing Insight software components on the primary system .............................................................. 13

Installing Insight software components on the secondary system........................................................... 14

Adjusting the HP SIM data source name on the primary system ........................................................... 15

Adding the Insight software cluster resources ........................................................................................ 16

Naming Insight software resource groups ......................................................................................... 16

Creating the Insight software physical disk resource ........................................................................... 17

Creating the HP SIM IP address resource .......................................................................................... 17

Creating the HP SIM network name resource..................................................................................... 18

Creating the HP SIM generic service resource ................................................................................... 18

Creating the OpenSSH Services generic service resource ................................................................... 18

Creating the Pegasus WMI Mapper generic service resource .............................................................. 18

Other Insight software components................................................................................................... 19

Version Control Repository Manager ............................................................................................ 19

Virtual Machine Management Pack .............................................................................................. 19

Proliant Essentials Performance Management Pack ......................................................................... 19

Virtual Server Environment Management Software.......................................................................... 19

Summary of Insight software cluster resources.................................................................................... 19

Bringing the virtual group containing the Insight software resources online............................................ 20

Summary of content (36 pages)

PAGE 1
Using HP Insight Software from a Highly Available Central Management Server with Microsoft Cluster Service Abstract.............................................................................................................................................. 3 Introduction......................................................................................................................................... 3 Getting started ...................................................................................
PAGE 2
Additional Configuration Steps ........................................................................................................ 21 Server Migration Pack/Universal Edition ....................................................................................... 21 Validating the Installation.................................................................................................................... 21 Appendix A —Sample cluster resources creation script ..........................................
PAGE 3
Abstract This white paper is intended to assist IT professionals in installing HP Insight software from the HP Insight Control Management DVD v2.30 on a Microsoft® Windows®-based Central Management Server (CMS) to create a highly available environment. The CMS on ProLiant may be configured in a Microsoft Cluster Service (MSCS) implementation on two nodes.
PAGE 4
servers, Modular Storage Array storage, and VMware and Microsoft Virtual Server virtual machines, ensuring server workloads run at peak performance levels.  HP ProLiant Essentials Vulnerability and Patch Management Pack (VPM)—Vulnerability and patch tool that integrates comprehensive vulnerability assessment and advanced patch management into HP SIM to identify and resolve security vulnerabilities quickly and reliably in Microsoft Windows and Linux environments.
PAGE 5
The majority of the databases used by the Insight software reside on a Microsoft SQL Server 2005 virtual server, which is also clustered. Other data files are stored on the shared disk.  The relationship between the Microsoft SQL Server 2005 Enterprise Edition instances and Insight software is shown in Figure 1.
PAGE 6
The maximum number of nodes supported in a cluster varies depending on operating system version and type of storage. For details, refer to the article “Maximum number of supported nodes in a cluster” (navigate to http://support.microsoft.com, and search for “Maximum number of supported nodes in a cluster”). This whitepaper documents a two node cluster.
PAGE 7
– One free shared disk for the Insight software program files – At least one free shared disk for Microsoft SQL Server 2005 – Microsoft Windows Server 2003 R2 Enterprise Edition with Service Pack 2 – Microsoft Cluster Service – Microsoft Internet Explorer 6.0 – Simple Network Management Protocol (SNMP) – Microsoft SQL Server 2005 Enterprise Edition – HP Insight Control Management DVD 2.30 – HP Management CD (version 7.
PAGE 8
1. MSCS cluster IP address and 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 140.110.240.62. 2. HP SIM virtual server IP address and name Function: To act as the virtual server IP address and name for HP SIM event reception.
PAGE 9
Installing the ProLiant Support Pack Install all appropriate components from the ProLiant Support Pack (PSP) relevant to your system. Be sure to include the component “HP Insight Management Agents for Windows Server 2003”. Activating the HP cluster MIB agents The HP Cluster MIB Agents provide information about your cluster through SNMP. It is a prerequisite for HP SIM 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.
PAGE 10
6. When the Instance Name window appears, enter a name for this database instance. By default, Default instance is selected and clients connect to the server by the server name. You must deselect Default instance and enter a name in the Instance name field, as shown in Figure 2. For this example, a named instance of a Microsoft SQL Server 2005 virtual server called VSE_INSTANCE has been installed. Clients connect to the server through the name VSE-SQLSVR\VSE_INSTANCE. Figure 2.
PAGE 11
Figure 3. The Virtual Server Name window 8. When the Virtual Server Configuration window appears, enter the IP address for the new virtual server. This address must be unique. Be sure that the Public network is selected in the Network To Use field. In this example, the IP Address 140.110.240.63 was used. There is no need to assign the private LAN address. 9.
PAGE 12
Figure 4. The Cluster Group Selection window 10. When the Cluster Node Configuration window appears, ensure that each node of the cluster appears as either the Required node or in the Selected nodes list. 11. Follow instructions to complete the MS SQL Server setup process. 12. The Setup Progress window appears. Refer to setup error logs, if necessary. Log files can be found in the Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files directory of the local boot disk.
PAGE 13
Microsoft SQL Server 2005 disk: SQL IP Address, SQL Network Name, SQL Server, SQL Server Agent, SQL Server Fulltext. Be sure that the new Microsoft SQL Server virtual server is running by connecting to it through the Microsoft SQL Server Management Studio.
PAGE 14
MS SQL Server 2005 may automatically assign a TCP/IP port number to the SQL Server instance. The port number is required to install Insight software components. Generally, the Insight Control Manager installer will automatically determine the SQL Server port number. However, the TCP/IP port of the SQL Server instance may be determined by following these steps: a. Run SQL Server Configuration Manager b. Expand SQL Server 2005 Network Configuration in the left panel c.
PAGE 15
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. It is recommended to shutdown the primary node. 1. Shutdown the primary node. 2. On the secondary system, rename the existing HP ICM installation folder with all its installed components folders on the shared disk. For this paper, the shared disk V:\ is used.
PAGE 16
Figure 5. Adjusting the data source name on the primary system Adding the Insight software cluster resources To complete the installation of HP ICM to the cluster, several cluster resources must be created using Cluster Administrator. This can be accomplished by either running the HA-VSE configuration scripts or by following the next steps. Naming Insight software resource groups 1. Power the primary system on, and log in to Windows as Administrator. 2. Power the secondary system on. 3.
PAGE 17
Figure 6. The Cluster Resource Groups. Creating the Insight software physical disk resource 1. In the Cluster Administrator window, right click the HA VSE Group from the left pane and select New->Resource from the dropdown menu. 2. The New Resource window appears. 3. In the Name field, enter “HA-VSE Disk” and select Physical Disk from the Resource type dropdown menu. 4. Click Next. The Possible Owners window appears. Be sure that the two systems in your cluster are listed in the Possible Owners pane.
PAGE 18
4. In the TCP/IP Address Parameters window, enter the unique IP address to use for connecting to the HP SIM service. This IP address (in this white paper, 140.110.240.64) is the one associated with the network name resource, and may be used by clients to connect to the service, regardless of which system currently owns the group. Select Public network and enable NetBIOS settings, if it is not enabled by default. Creating the HP SIM network name resource 1.
PAGE 19
Other Insight software components Depending upon which other Insight software components were selected for installation, create the required cluster resources, as described in the following sections. Version Control Repository Manager VCRM is not a cluster-aware application. HP does not support a configuration in which it automatically fails over. Virtual Machine Management Pack  Create a resource, selecting Generic Service as the Resource type, and specifying “hpvmmsvc” as the Service Name.
PAGE 20
HA-VSE WMI Service Generic Service HA-VSE Disk “WMI Mapper” HA-VSE VMM Service Generic Services HA-VSE Disk “hpvmmsvc” HA-VSE PMP Service Generic Services HA-VSE Disk “HP Performance Management Pack” HA-VSE PMP Tools Generic Services HA-VSE Disk “HP PMP Tools” HA-VSE AD Service Generic Services HA-VSE Disk “AppDisc” HA-VSE gWLM Service Generic Services HA-VSE Disk “HP Global Workload Manager CMS” HA-VSE LSA Controllers Service Generic Services HA-VSE Disk “HP LSA Controllers” HA-
PAGE 21
Figure 7. Cluster Administrator: Cluster resources in the HA-VSE Group The cluster installation of HP ICM is now complete. The following section discusses how to validate your cluster installation of HP ICM. Additional Configuration Steps Server Migration Pack/Universal Edition  SMP/UE stores its license keys in the Windows registry. Therefore, apply the SMP/UE license on each node of the cluster.  Edit the SMP/UE ~\bin\mmweb.
PAGE 22
2. In the Cluster Administrator window, on the left pane, right-click on the disk group containing the Insight software components program files. For example, the name HA-VSE Group was used in this paper. Select Move Group. Be sure that the group fails over to the other system, and that all of the HA-VSE Group cluster resources come online. 3.
PAGE 23
These steps are to ensure Insight software components are working after failover. You should be able to 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.
PAGE 24
Appendix A —Sample cluster resources creation script This appendix includes a Microsoft Windows Script Host file that may be copied (e.g. cut and pasted), customized for your environment, and then executed to create the required HA VSE cluster resources. Also included are two VBScript script files containing common definitions and functions used by the cluster resources creation script. Follow these steps to create the required cluster resources: 1. Create the files HA-VSE_defines.vbs, HA-VSE_common.
PAGE 25
HA-VSE_defines.vbs The HA-VSE_defines.vbs script file contains global definitions used by the cluster resources creation script. The values in the file must be customized for your environment before executing the cluster resources creation script, HA-VSE_script.wsf. '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' ' HA-VSE_defines.vbs ' ' Contains global definitions. ' Change the values here for local implementation. ' ' © Copyright 2008 Hewlett-Packard Development Company, L.P.
PAGE 26
HA-VSE_common.vbs The HA-VSE_common.vbs script file contains global data and common functions used by the cluster resources creation script, HA-VSE_script.wsf. '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' ' HA-VSE_common.vbs ' ' Contains global data and common functions. ' ' © Copyright 2008 Hewlett-Packard Development Company, L.P.
PAGE 27
' Dereferences global objects. Used with cluConnect. ' Set objCluster = Nothing End Function ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Public Sub cluEnumNodes(cluster, nodes) ' ' Purpose: list all nodes configured in cluster definition. ' If no cluster name, then "this cluster" is default. ' Dim objNode ReDim nodes(0) Dim n n = 0 for each objNode in cluster.Nodes nodes(n) = objNode.
PAGE 28
"' in state '" & objMySvc.State &_ "' on node " & hostName Exit Function Else Err.Raise(999) Exit Function End if Next End If 'WScript.Echo "Exit verify Svc:" & objMySvc 'DEBUG End Function Public Function WMIconnect( hostName, objWMI ) On Error Resume Next Dim objLocator, objService Set objLocator = CreateObject("WbemScripting.SWbemLocator") Set objWMI = objLocator.ConnectServer(hostName, "root\cimv2",,,,,128) ' if Err.Number <> 0 then WScript.Echo "Err Connect: " & Err.Number & Err.
PAGE 29
HA-VSE_script.wsf The HA-VSE_script.wsf file contains the cluster resources creation script. It includes a job that determines if prerequisite conditions for creating the HA-VSE cluster resources are satisfied, and a job that creates the required HA-VSE cluster resources.