Deploying Virtual Connect Enterprise Manager on Microsoft Cluster Service Abstract ........................................................................................................................................ 3 Introduction ................................................................................................................................... 3 Getting started ..............................................................................................................................
HA-VCEM_script.wsf.................................................................................................................. 42 Sample output from prerequisites check step .................................................................................. 47 Sample output from cluster resources creation step .......................................................................... 47 References...........................................................................................................
Abstract This white paper is intended to assist IT professionals in installing HP Virtual Connect Enterprise Manager (VCEM) 1.0 in a Microsoft Cluster Service (MSCS) configuration on two nodes. Using Microsoft Windows Server 2003 Enterprise Edition with HP Virtual Connect Enterprise Manager 1.0 can be a simple way of achieving redundancy, availability, load balancing, and failover capability from this powerful management software.
The HP Virtual Connect Enterprise Manager database, the repository for all management information used by HP Virtual Connect Enterprise Manager, resides on a Microsoft SQL Server 2005 virtual server, which is also clustered. • The relationship between the Microsoft SQL Server 2005 Standard Edition instances and HP Virtual Connect Enterprise Manager is shown in Figure 1.
Configuring a Server Cluster under Windows Server 2003”) for step-by-step instructions for cluster installation, configuration and installation testing. Note: 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”).
Refer to the HP Virtual Connect Enterprise Manager User Guide and the HP Virtual Connect Enterprise Manager Support Matrix for details on the hardware and software installation requirements for Virtual Connect Enterprise Manager. System infrastructure Figure 1details how to configure a cluster for enhanced performance once all components are installed. With this configuration, load is distributed by designating each virtual group to work on a separate system.
• Suggested action: All SNMP devices that report their events to HP Virtual Connect Enterprise Manager 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 140.110.240.64. 3. 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 2005 Standard Edition database software.
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. IMPORTANT: If you install SNMP service after installing a Microsoft Windows Operating System Service Pack, you must reinstall that Service Pack.
Installing a clustered instance of the Microsoft SQL Server 2005 Standard Edition 1. On the primary system, log into Microsoft Windows as a domain user with administrator rights. 2. From the Run menu on any system in the cluster, enter comclust and press the Enter key. Wait for the command to complete. Then run comclust on the remaining system in the cluster. This executable sets up the MSDTC, a component for use in the cluster. 3.
14. Name this 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. Figure 2. The Instance Name window Note: For this example, we have installed a named instance of a Microsoft SQL Server 2005 virtual server called HP_VCEM_INSTANCE. Clients connect to the server through the name HP-VCEMSQLSVR\HP_VCEM_INSTANCE. 15. Click Next.
16. Enter the name of the new virtual server. In this example, the name HP-VCEM-SQLSVR was used, as shown in Figure 3. Figure 3. The Virtual Server Name window 17. Click Next. The Virtual Server Configuration window appears. 18. 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. 19. Click Next. The Cluster Group Selection window appears.
20. Select the cluster group where the Microsoft SQL Server 2005 program files are to be saved, by selecting the group name, as shown in Figure 4. Figure 4. The Cluster Group Selection window IMPORTANT: Do not use the cluster quorum disk, the disk containing your cluster’s quorum files (in Figure 4, 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 appears if you select the quorum disk.
26. Enter the same domain account information you entered previously to ensure connectivity. 27. Click Next. The Domain Groups for Clustered Services window appears. 28. Enter the name of the existing DomainName\GroupName for each clustered service being installed. 29. Click Next. The Authentication Mode window appears. 30. Select Mixed Mode for the Authentication Mode.
2. Ensure that the cluster system that is to be installed with HP Virtual Connect Enterprise Manager owns the clustered disks. If the cluster system that is to be installed does not currently own all cluster resources, in Cluster Administrator, one at a time select each resource group not currently owned by the system, and select the Move Group menu option to move the resource group to the system that is to be installed. 3.
3. To install the VCEM product, in the Run menu, enter setup\setup.exe, specifying the drive letter of the DVD-ROM drive containing the VCEM DVD. The Welcome window appears, as shown in Figure 5. Ensure that the specified conditions are met. Figure 5.
4. Click Next. The Installation directory window appears, as shown in Figure 6. Enter the location in which to install VCEM. The location should be a cluster disk in its own group, separate from the cluster group containing the quorum disk and the group containing the disk used by SQL Server. In this example, V:\Program Files\HP was used. Figure 6.
5. Click Next. The Service account credentials window appears, as shown in Figure 7. The Username field displays the name of the user who is logged in. Enter the password in the Password field. The Domain field displays the domain used to log in to the system. Figure 7. The Service account credentials window 6. Click Next. The Database configuration window appears, as shown in Figure 8. The Username field displays the name of the user who is logged in. Enter the password in the Password field.
a) Run SQL Server Configuration Manager b) Expand SQL Server 2005 Network Configuration in the left panel c) Select Protocols for InstanceName in the left panel, where InstanceName is a placeholder for the named instance of SQL Server 2005 d) Double-click TCP/IP in the right panel e) In the Protocol tab, note the value of the Listen All item f) In the IP Addresses tab: o If the value of Listen All is yes, the TCP/IP port number for this instance of SQL Server 2005 is the value of the TCP Dynamic Ports i
Figure 8.
7. Click Next. The Basic settings for HP Systems Insight Manager window appears, as shown in Figure 9. Entering account credentials to be used to access and discover systems is recommended. Figure 9.
8. Click Next. The Discovery settings for HP Systems Insight Manager window appears, as shown in Figure 10. The discovery step is optional and may be skipped by leaving the IP ranges field blank. Figure 10.
9. Click Next. The Installation summary window appears, as shown in Figure 11. An estimate of the total installation time required is provided. Figure 11. The Installation summary window 10. Click Install. A warning appears that the server will automatically reboot during installation, and that it will be necessary to log back in to complete the installation after the reboot.
11. Click Yes to continue with the installation. Log into the system again, once it has restarted. The Installation status window appears, as shown in Figure 12. Wait until installation of all selected components is complete. Note: A progress bar indicating overall installation progress appears during the installation. Individual indicators also display the installation status of each component. Figure 12.
12. Click Next. The Installation finished! Window appears, as shown in Figure 13. Figure 13. The Installation finished! window 13. Click Close to exit the Installer. Installing HP Virtual Connect Enterprise Manager on the secondary system To deploy a clustered installation of HP Virtual Connect Enterprise Manager, the installation process must be completed on the second system in the cluster as well, with a few differences in the procedure to account for the existing program files on the cluster disk.
IMPORTANT: Be sure that the secondary system owns all of the clustered disks. Since installation will result in an automatic reboot, it is recommended to shut down the primary system before beginning the installation on the secondary system, to prevent the cluster resources from being failed over to the primary system upon the reboot. VERY IMPORTANT: Rename the existing HP Virtual Connect Enterprise Manager folder and all its installed components folders (such as Systems Insight Manager) on the shared disk.
7. Click Next. The database selection window appears, as shown in Figure 14. Select the database, which is created by the secondary system. Use the database name (corresponding to the hp.Database.databaseName keyword) recorded in step 2 of Installing HP Virtual Connect Enterprise Manager on the Secondary system, above. 8. Click Next. The final Microsoft SQL Server DSN Configuration window appears. 9. Click Finish to complete the configuration. A summary window appears. 10. Click OK. 11.
Naming the HP Virtual Connect Enterprise Manager and SQL Server groups 1. Power the primary system on, and log in to windows as administrator. 2. Power the secondary system on. 3. Open the Cluster Administrator tool from the primary system and confirm that the primary system owns all the cluster resources. Ensure that the Cluster Service is running on the secondary system (select the Start Cluster Service menu option if it is not running). 4.
1. In the Cluster Administrator window, select the HP VCEM Group from the left pane. In the right pane, right click anywhere and select New → Resource from the dropdown menu. 2. The New Resource window appears. 3. In the Name field, enter HP VCEM IP Address and select IP Address from the Resource type dropdown menu, as shown in Figure 16. 4. Click Next. Figure 16. The New Resource window: Creating the VCEM IP Address 5. The Possible Owners window appears.
9. Enter the unique IP address to use to connect to the HP Virtual Connect Enterprise Manager service. This IP address (in this example, 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 check the box to enable NetBIOS, if it is not enabled by default. 10. Click Finish. A confirmation window appears. 11. Click OK.
3. Click Next. The Possible Owners window appears. Be sure that the two systems in your cluster are listed in the Possible owners pane. 4. Click Next. The Dependencies window appears. Select the shared disk in the HP VCEM group, and add it to the Resource dependencies list. In this example, Disk V: was added as a dependency. 5. Click Next. The Generic Service Parameters window appears. 6. In the Service name field enter HP Systems Insight Manager which is the service name for HP SIM, as shown in Figure 17.
3. Click Next. The Possible Owners window appears. Be sure that the two systems in your cluster are listed in the Possible owners pane. 4. Click Next. The Dependencies window appears. Select the shared disk in the HP VCEM group, and add it to the Resource dependencies list. In this example, Disk V: was added as a dependency. 5. Click Next. The Generic Service Parameters window appears. 6. In the Service name field enter OpenSSHd, which is the service name for the OpenSSH, as shown in Figure 18.
2. From the New Resource window, in the Name field, enter WMI Mapper Service and select Generic Service from the Resource type dropdown menu. 3. Click Next. The Possible Owners window appears. Be sure that the two systems in your cluster are listed in the Possible owners pane. 4. Click Next. The Dependencies window appears. Do not specify any dependencies for this service. 5. Click Next. The Generic Service Parameters window appears. 6.
Bringing the virtual group containing the HP Virtual Connect Enterprise Manager resources online In the Cluster Administrator window, right-click on the HP VCEM Group in the left pane, and select Bring Online from the dropdown menu. If configured properly, all resources should come online, as shown in Figure 20. Figure 20. Cluster Administrator: Cluster resources in the HP VCEM Group The installation of HP Virtual Connect Enterprise Manager is now complete.
http://HP-VCEM-SVR:280 specifies the virtual network name and the port of the HP Virtual Connect Enterprise Manager virtual server. Note: You must always specify the port 280 in the URL of your Web browser to connect to the HP Virtual Connect Enterprise Manager virtual server. To learn more about connecting to HP Virtual Connect Enterprise Manager, refer to the HP Virtual Connect Enterprise Manager User Guide.
7. After you have successfully logged in, the HP Virtual Connect Enterprise Manager home page appears, as shown in Figure 21. Figure 21. The HP Virtual Connect Enterprise Manager home page Note: 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: The purpose pf these steps is to ensure that HP VCEM is working after failover. 10. You should be able to use the active system name to establish a command-line session to the cluster HP SIM service from a client system that has an OpenSSH client installed, using SSH. For example, an mxversion or mxgetdbinfo -a command may be issued to verify a command-line session connection has been established.
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 HP VCEM 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-VCEM_defines.vbs, HA-VCEM_common.
HA-VCEM_defines.vbs The HA-VCEM_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-VCEM_script.wsf. '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' ' HA-VCEM_defines.vbs ' ' Contains global definitions. ' Change the values here for local implementation. ' ' © Copyright 2007 Hewlett-Packard Development Company, L.P.
HA-VCEM_common.vbs The HA-VCEM_common.vbs script file contains global data and common functions used by the cluster resources creation script, HA-VCEM_script.wsf. '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' ' cluCommon.vbs ' ' Contains global data and common functions. ' ' © Copyright 2007 Hewlett-Packard Development Company, L.P.
' ' 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.
Err.Raise(999) Exit Function End if Next End If 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.Description ErrorCheck "ConnectServer", Err.Description exit function end if objWMI.Security_.
HA-VCEM_script.wsf The HA-VCEM_script.wsf file contains the cluster resources creation script. It includes a job that determines if prerequisite conditions for creating the HA-VCEM cluster resources are satisfied, and a job that creates the required HA-VCEM cluster resources.
