HP EVA Cluster Extension Software Installation Guide

HP EVA Cluster Extension Software Installation Guide Abstract This guide contains detailed instructions for installing and removing HP EVA Cluster Extension Software in Windows and Linux environments. The intended audience has independent knowledge of related software and of the HP Enterprise Virtual Array and its software. HP Part Number: T3667-96104 Published: June 2012 Edition: Eighth

Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. 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 and Windows are U.S. registered trademarks of Microsoft Corporation. Java is a U.S. trademark of Sun Microsystems, Inc.

Contents 1 Preparing to install HP EVA Cluster Extension...5 Ideal environment...5 Network communication requirements...5 Data backup requirements...5 How HP EVA Cluster Extension Software interacts with its environment...6 Failover function...6 How HP EVA Cluster Extension utilizes vdisks...6 How HP EVA Cluster Extension stores information...6 General installation prerequisites...6 Environmental setup...7 Disk space and system memory requirements...7 Required firmware and software...8 2 Installing HP EVA Cluster Extension Software for Windows...9 Prerequisites...9 Pre-installation procedures...9 Checking the IP network setup and SAN configuration...9 Installing multipath software...10 Installing and configuring the JRE...10 Installing and configuring HP SMI-S EVA on all management servers...10 Configuring the HP P6000 (EVA) storage system...10 Creating hosts...10 Creating vdisks and adding a LUN presentation...11 Creating DR groups...12 Setting read-only mode and adding a LUN presentation to the destination vdisk...12 Installing MSCS on all nodes...12 Installing EVA Cluster Extension Software for Windows...13 Upgrading HP EVA Cluster Extension Software for Windows...16 Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2003)...17 Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2008/2008 R2)...19 Upgrading HP EVA Cluster Extension with HP P6000 (EVA) Command View upgrade...20 EVA Cluster Extension maintenance...20 Modifying the EVA Cluster Extension installation...21 Repairing the EVA Cluster Extension installation...21 Removing EVA Cluster Extension for Windows...22 Troubleshooting installation and maintenance problems...22 Registering the resource type and resource extension DLL manually...25 Unregistering the resource type and resource extension DLL manually...26 3 Installing EVA Cluster Extension Software for Linux...27 Prerequisites...27 Pre-installation procedures...27 Checking the IP network setup and SAN configuration...27 Configuring multipath software...28 Installing and configuring the HP SMI-S EVA server on all management servers...28 Configuring the HP P6000 (EVA) storage system...28 Creating hosts...28 Creating vdisks and adding a LUN presentation...28 Creating DR groups...29 Setting read-only mode and adding a LUN presentation to the destination vdisk...29 Configuring LVM...29 Contents 3

Installing and configuring the cluster software...30 Installing EVA Cluster Extension Software for Linux...30 Removing EVA Cluster Extension Software for Linux...31 4 Licensing...32 Retrieving a license key...32 Using AutoPass to retrieve permanent license keys...32 Using the clxautopass command-line utility...32 Installing the license...32 Importing a license key from a file...33 Using the EVA Cluster Extension registration tool (Windows only)...33 Removing an instant-on license key...33 5 Support and other resources...34 Contacting HP...34 Subscription service...34 New and changed information in this edition...34 Related information...34 White papers...35 HP websites...35 Typographic conventions...35 HP product documentation survey...36 Glossary...37 Index...40 4 Contents

1 Preparing to install HP EVA Cluster Extension This chapter provides information about general environment considerations and pre-installation requirements. Ideal environment The ideal configuration environment consists of at least five servers (two at each data center site and one as an arbitrator at a third site) with separate, redundant communications links for cluster heartbeats, client access, and HP P6000 (EVA) Continuous Access. All communications interfaces must be installed in pairs to serve as failover components, in order to prevent single points of failure. Network communication requirements When using HP EVA Cluster Extension, note the following: Network communications links and components between the dispersed data centers must be redundant and physically routed differently to prevent the backhoe issue that is created when all links between data centers are cut together. This redundancy and routing is especially important to prevent the split-brain syndrome that occurs when systems in both data centers form new clusters and allow access to both copies of the data. Using redundant and separately routed communications and components, you can configure the failover behavior so that the application service startup procedure stops if none of the remote cluster members can be reached. Alternative pathing software such as HP Secure Path for Windows operating systems must be used for host-to-storage connections. Linux clusters might have specific network latency requirements. For more information, see the SLE HA and RHCS documentation. Data backup requirements To ensure reliable data backup between the local (primary) and remote (secondary) storage systems, at least two HP P6000 (EVA) Continuous Access links must be available when the storage systems are connected to provide redundancy and protection against single points of failure. Although communications links can cover considerable distances, each network segment must be extended to the dispersed data center to maintain a heartbeat among all servers. For extended distances, you must purchase extender components to bundle the HP P6000 (EVA) Continuous Access links. Recommendation Use two systems at each site to give local application service failover procedures among local cluster systems priority over remote, more time-consuming failover procedures. When failing over, the software must reconfigure the storage systems to change the mirroring direction. At the remote Ideal environment 5

site, two systems should be available in case the primary failover system experiences a hardware or power failure. Windows: Using an MNS quorum requires an odd number of cluster nodes, with at least one system in a third location. Linux: For SLE HA and RHCS data backup requirements, see the SLE HA and RHCS documentation. CAUTION: HP EVA Cluster Extension works with one server at each location, with a single I/O path between the server and storage system, and a single link between storage systems. However, any configuration with a single point of failure is not considered highly available or disaster tolerant. HP does not support configurations with single points of failure; configurations with one system at each location are supported only if there are no single points of failure. How HP EVA Cluster Extension Software interacts with its environment This section describes the ways in which HP EVA Cluster Extension interacts with its in environment. Failover function HP EVA Cluster Extension Software requires cluster software to automatically fail over among systems on a local site or between sites. Because the software manipulates the application startup process before storage system vdisks are accessed, it must be integrated as the first resource (in the order of resources). The software must be installed on all servers in the cluster that can run the application service. How HP EVA Cluster Extension utilizes vdisks To write to HP P6000 (EVA) Continuous Access paired vdisks, you must make sure the paired vdisks are in read/write mode. DR group members (paired vdisks) are usually in read/write mode on the source (primary) vdisk only. The destination (secondary) vdisk is in read-only mode. In case of a failover, HP EVA Cluster Extension Software automatically changes the direction of the mirrored pair. A reboot of the server is not necessary. In case of a disaster, the storage system can have several different states for DR group members. HP EVA Cluster Extension Software determines whether those vdisks can be accessed and made available to the application service. How HP EVA Cluster Extension stores information HP EVA Cluster Extension stores information about the application environment in an internal object database and uses HP SMI-S EVA to gather information about the state of the associated DR group members. Information about the configured storage system environment and failover behavior is transferred either directly by the cluster software or by gathering it from the user configuration file. An internal object database provides the software with the format and default value of supported parameters. Vdisk states are stored in the internal object database, which uses a rule engine to process those DR group member states. The rule engine matches current DR group member states and configuration parameters with a defined rule, stores it in the database, and invokes predefined actions. Those actions prepare the DR group member vdisks to be enabled for access or stop the application service startup process if the matching rule requires a stop. General installation prerequisites This section describes general installation prerequisites for HP EVA Cluster Extension. 6 Preparing to install HP EVA Cluster Extension

Environmental setup Ensure that the following conditions are met before installing HP EVA Cluster Extension Software: HP P6000 (EVA) Continuous Access links (including extender hardware) are redundant and bidirectional. Alternate I/O paths between servers and the P6000 (EVA) storage system are set up. Cluster and client networks are redundant. Cluster nodes can communicate with each other (not required for Windows Server 2003). The latest supported software and firmware versions, fixes, FC adapter firmware, and driver versions for your servers and P6000 (EVA) storage systems are installed. The cluster nodes in your zoning configuration each recognize their respective (local) P6000 (EVA), but not the remote P6000 (EVA). Each management server recognizes both P6000 (EVA)s and can recognize each other. Figure 1 (page 7) shows a zoning example. Figure 1 Zoning example Disk space and system memory requirements Linux 10 MB for /opt/hpclxeva 10 MB for /etc/opt/hpclxeva 100 MB for /var/opt/hpclxeva 5 MB for /opt/ov Windows 50 MB for the HP EVA Cluster Extension installation directory (%ProgramFiles%\ Hewlett-Packard\Cluster Extension EVA) At least 25 MB of system memory General installation prerequisites 7

Required firmware and software For specific firmware and software versions, see the HP SPOCK website: http://www.hp.com/ storage/spock. 8 Preparing to install HP EVA Cluster Extension

2 Installing HP EVA Cluster Extension Software for Windows This chapter describes the installation of HP EVA Cluster Extension in MSCS environments with HP P6000 (EVA) disk arrays. This version of HP EVA Cluster Extension allows you to install, uninstall, modify, and repair HP EVA Cluster Extension on all of the nodes in a cluster by running the installer from one node in the cluster. This feature is not available for performing HP EVA Cluster Extension upgrade procedures. When upgrading, you must run the installation package separately on each cluster node. NOTE: For information on configuring HP EVA Cluster Extension in an MSCS environment, see the HP EVA Cluster Extension Software Administrator Guide. Prerequisites Before installing HP EVA Cluster Extension, perform the following tasks: 1. Check General installation prerequisites (page 6) to make sure your setup meets the general pre-installation requirements. 2. Perform the required Windows pre-installation procedures. For instructions, see Pre-installation procedures (page 9). 3. Download the HP EVA Cluster Extension Software installer. a. Browse to http://www.hp.com/go/softwaredepot > HP Storage > Storage Software. b. Follow the on-screen instructions to download the installer. Pre-installation procedures This section describes the procedures you must perform to prepare the data centers for HP EVA Cluster Extension installation and configuration. Perform these procedures before you install HP EVA Cluster Extension. 1. Checking the IP network setup and SAN configuration (page 9) 2. Installing multipath software (page 10) 3. Installing and configuring the JRE (page 10) 4. Installing and configuring HP SMI-S EVA on all management servers (page 10) 5. Configuring the HP P6000 (EVA) storage system (page 10) 6. Creating hosts (page 10) 7. Creating vdisks and adding a LUN presentation (page 11) 8. Creating DR groups (page 12) 9. Setting read-only mode and adding a LUN presentation to the destination vdisk (page 12) 10. Installing MSCS on all nodes (page 12) Checking the IP network setup and SAN configuration Verify that your IP network setup and SAN configuration meet the following requirements: For Windows Server 2003 only, MSCS requires that a single IP subnet be dispersed over all sites in a disaster-tolerant cluster setup. This enables the cluster to exchange heartbeat (alive) messages between all cluster nodes. HP EVA Cluster Extension requires a cluster environment in which one location failure will not cause the entire cluster to shut down. Prerequisites 9

In an MNS quorum cluster, all nodes must be distributed so that an equal number of nodes are located in the local and remote data centers and an additional node in a third location functions as a tiebreaker or arbitrator. The third location can be a separate room in a separate fire protection zone with separate power connections. The arbitrator node can act as a regular cluster node and can be connected to one of the storage systems. However, a connection to either storage system is not necessary for the node to act as a tiebreaker. SAN fabrics can be extended to allow for array-based data replication. Consult the HP P6000 (EVA) Continuous Access Implementation Guide and the HP SAN Design Reference Guide for supported SAN extension configuration and instructions on setting up your HP P6000 (EVA) Continuous Access environment. Installing multipath software Ensure the multipath software is installed on the cluster system before connecting the system to the second I/O path. See the HP SPOCK website (http://www.hp.com/storage/spock) for more information on multipath software support. Installing and configuring the JRE To install the product license using the HP AutoPass GUI, you must first install the JRE. See the AutoPass documentation for the latest supported JRE versions. NOTE: This step is required only if you want to use the AutoPass GUI to manage license keys. If you do not install the JRE, you can use the HP EVA Cluster Extension registration tool to install license keys. For more information about using the registration tool, see Using the EVA Cluster Extension registration tool (Windows only) (page 33). Installing and configuring HP SMI-S EVA on all management servers Install the HP SMI-S EVA server component on all of the management servers that run the HP P6000 (EVA) Command View software. Review the HP P6000 (EVA) Command View Installation Guide and the HP P6000 (EVA) Command View Release Notes to set the access properties. When you configure HP EVA Cluster Extension, you will need the following HP SMI-S information: HP SMI-S server name and IP address Port number; The default is 5989 with SSL enabled, and 5988 with SSL disabled. User name Password SSL use (yes or no) Configuring the HP P6000 (EVA) storage system For detailed information on configuring the HP P6000 (EVA) storage system, see the HP P6000 (EVA) Command View User Guide or the HP Storage System Scripting Utility Reference. You can also consult your HP service representative for further assistance, including help with creating a geographically dispersed cluster environment. Creating hosts Before you can assign disk storage to a cluster node, you must create a host entry for the locally connected server/node on each HP P6000 (EVA) storage system. 10 Installing HP EVA Cluster Extension Software for Windows

For detailed information, see the HP P6000 (EVA) Command View User Guide or the HP Storage System Scripting Utility Reference. Creating vdisks and adding a LUN presentation Create the storage (vdisks) for your application data using the SSSU or the HP P6000 (EVA) Command View GUI, and then present the vdisks to the cluster nodes connected to source P6000 (EVA) array. NOTE: Later in this installation process, you will create a LUN presentation for your remote destination vdisk and set the access mode property for the destination vdisk to read-only. See Setting read-only mode and adding a LUN presentation to the destination vdisk (page 12). For detailed instructions, see the HP HP P6000 (EVA) Command View User Guide or the HP Storage System Scripting Utility Reference. Pre-installation procedures 11

Creating DR groups Before you can use HP EVA Cluster Extension, you must create a DR group that includes your previously created vdisk(s). When you create the DR group with a local vdisk (or vdisks), a replica of the vdisk(s) on the remote destination storage system is created automatically. The disk pair is called a DR group member or copy set. When you create a DR group, note the following: Set Write mode to Synchronous or Asynchronous. Enhanced asynchronous mode is supported by HP EVA Cluster Extension for Windows 4.00.00 and later. For complete information on which write modes are supported on each version of controller software, see the HP Enterprise Virtual Array Compatibility Reference. For information on choosing a write mode, see the HP HP P6000 (EVA) Continuous Access Implementation Guide. Set Failsafe mode to either Disabled or Enabled. NOTE: Failsafe mode can be set to Enabled only when the Write mode is set to Synchronous. HP recommends that you do not enable Suspend mode when you create DR groups for use with HP EVA Cluster Extension. If the replication IO is suspended for a DR group (for example, through HP P6000 (EVA) Command View) during a Cluster Extension P6000 (EVA) resource failover, the Cluster Extension behavior is undefined. For detailed information, see the HP P6000 (EVA) Command View User Guide or the HP Storage System Scripting Utility Reference. Setting read-only mode and adding a LUN presentation to the destination vdisk To complete setup of HP P6000 (EVA) Continuous Access, perform these tasks: 1. Set access mode to read-only for the destination vdisk. You can either use HP P6000 (EVA) Command View GUI or SSSU to set this property. 2. Add a LUN presentation to your remote cluster node. NOTE: HP recommends that you use the same LUN for all servers in the cluster. This step assumes that you have created your remote host entry on the destination storage system as described in Creating hosts (page 10). For detailed instructions, see the HP P6000 (EVA) Command View User Guide or the HP Storage System Scripting Utility Reference. Installing MSCS on all nodes This section describes the steps for installing MSCS on the cluster nodes. 12 Installing HP EVA Cluster Extension Software for Windows

1. Before installing MSCS, create your disk configuration through the Disk Manager. If the disks are not visible, re-scan your disks in the Disk Manager. NOTE: You may need to shut down all but one server on the source storage system to successfully configure your disks in the Disk Manager. Errors may occur during partitioning and formatting because all servers that you present the same disk to on the local storage will compete for access to the disk. This will not happen after the cluster software is installed and you have formatted or partitioned the disk(s). In rare cases, certain FC drivers will show disk access errors in the event log (event ID 51) when the disk access is set to read-only. This can be ignored for read-only destination disks and should not occur after HP EVA Cluster Extension is installed. You must reboot the server(s) on the destination storage system or re-scan the disks in the Disk Manager before and after installing the cluster software, and when you add storage in read-only mode on the destination side. 2. Install MSCS on all cluster nodes. 3. Select Majority Node Set quorum as the cluster's quorum resource. Quorum disks as a quorum resource are not supported with HP EVA Cluster Extension Software. 4. Windows Server 2008/2008 R2 only: Run the Microsoft ClusPrep tool to validate your cluster. If the Failover Cluster Validation Report lists a failed storage test, you can ignore this error. For more information, see the following Microsoft TechNet document: http:// technet2.microsoft.com/windowsserver2008/en/library/ b153c638-ff53-4470-8b72-010046b8dcc61033.mspx?mfr=true. After the cluster software is installed, you can install HP EVA Cluster Extension Software on all cluster nodes that have an FC connection to the local or remote P6000 (EVA) and are used to access storage resources on the P6000 (EVA). For installation instructions, follow the procedure in Installing EVA Cluster Extension Software for Windows (page 13). If the system that acts as an arbitrator or tiebreaker is not connected to either P6000 (EVA), you do not need to install the software on that cluster node. Installing EVA Cluster Extension Software for Windows EVA Cluster Extension Software provides a standard InstallShield wizard for Windows. The setup program includes integration with MSCS and the generic software interface. The installer includes the following features: Resource DLL (clxevamscs.dll) Cluster administrator extension DLL (clxevamscsex.dll) CLI (clxevarun.exe) EVA Cluster Extension documentation You can use the CLI for custom cluster software integration. For example, you can write your own online and offline scripts using advanced DR group status checking options. NOTE: MSCS. Installing the CLI is not required if you are using HP EVA Cluster Extension Software with To install EVA Cluster Extension: 1. Make sure that the cluster service is running. 2. Make sure that the cluster management application is not running on the cluster nodes where you plan to install EVA Cluster Extension. NOTE: Failover Cluster Management is used on Windows Server 2008/2008 R2, and Cluster Administrator is used on Windows Server 2003. Installing EVA Cluster Extension Software for Windows 13

3. Run the installer by doing one of the following: Double-click the HP EVA Cluster Extension installation package. Run the HP EVA Cluster Extension installation package from the command prompt. This option is used for Server Core or Hyper-V Server installation. For more information about installing applications in a Server Core or Hyper-V Server environment, see your Microsoft documentation. The installer prompts you to check the HP SPOCK website (http://www.hp.com/storage/ spock) to verify that supported versions of the array firmware and other required software are installed. 4. Verify that the correct software is installed, and then click OK. 5. Follow the instructions to accept the license agreement, view the Readme file, and enter your identification. The Setup Type dialog box appears. 6. In the Setup Type dialog box, select one of the following options, and then click Next: Select Typical to install the resource DLL, cluster administrator extension DLL, and documentation. Select Compact to install only the resource DLL and cluster administrator extension DLL. Select Custom to select specific components to install. The Cluster node selection dialog box appears. 7. Select the cluster nodes for EVA Cluster Extension installation, and then click Next. The Choose Destination Location dialog box appears. 14 Installing HP EVA Cluster Extension Software for Windows

8. Accept the default location, or click Browse and specify a new destination. 9. Specify whether the installation directory will apply to all nodes selected for installation: If you want to use the same destination location for all nodes selected in the previous step, select the Use the same destination location for all the selected remote cluster nodes check box, and then click Next. If you do not want to use the same destination for all nodes selected in the previous step, do not select the Use the same destination location for all the selected remote cluster nodes check box, and click Next to continue. 10. Depending on your selection in the previous step, and your version of Windows, do one of the following: For Windows Server 2008/2008 R2, if you specified the same location for all cluster nodes, go to Step 12. If you specified that you will enter a different destination for each cluster node, the Remote Installation Location dialog box appears when you click Next in the previous step. Continue to Step 11. Installing EVA Cluster Extension Software for Windows 15

11. For all remote cluster nodes: Accept the default location or enter a new location, and then click Next. 12. The installer asks if you want to install a permanent license. Click Yes to install a permanent license. Follow the instructions in Licensing (page 32) to retrieve and install the license, and then click Finish. NOTE: You must perform the permanent license installation procedure separately on each cluster node. Cluster-wide installation does not install a permanent license on remote cluster nodes. TIP: To start the configuration tool at the end of the installation, select the Launch Configuration Tool check box before you click Finish. 13. To perform the required configuration steps, follow the instructions in the HP EVA Cluster Extension Software Administrator Guide. Upgrading HP EVA Cluster Extension Software for Windows This version of HP EVA Cluster Extension Software supports upgrading from version 2.01.00 or later. You can also upgrade HP EVA Cluster Extension concurrently with HP P6000 (EVA) Command View. Use one of the following procedures: Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2003) (page 17) Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2008/2008 R2) (page 19) Upgrading HP EVA Cluster Extension with HP P6000 (EVA) Command View upgrade (page 20) 16 Installing HP EVA Cluster Extension Software for Windows

Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2003) IMPORTANT: Perform the upgrade procedure on each node locally. HP EVA Cluster Extension does not support remote upgrades. 1. Download the HP EVA Cluster Extension Software from SUM. You can access SUM from the ITRC website: http://www.itrc.hp.com. 2. Verify that the new version of HP EVA Cluster Extension supports the version of HP P6000 (EVA) Command View that is installed on your management servers. Compatibility information is available on the HP SPOCK website: http://www.hp.com/storage/ spock. If you need to upgrade HP P6000 (EVA) Command View to support the new version of HP EVA Cluster Extension, use the procedure in Upgrading HP EVA Cluster Extension with HP P6000 (EVA) Command View upgrade (page 20). 3. Use the clxpmu.exe tool to capture and record the SMI-S configuration information for each P6000 (EVA) management server that is used with HP EVA Cluster Extension. Ensure that the SMI-S login information for each management server is available before you upgrade HP EVA Cluster Extension. After the upgrade, you must enter this information using the HP EVA Cluster Extension configuration tool. a. Open a command window and run clxpmu.exe. The clxpmu tool is available in the following directory: INSTALL_DIR\bin. The clxpmu selection dialog appears. Upgrading HP EVA Cluster Extension Software for Windows 17

NOTE: For more information on using this tool, see the CLI commands and utilities chapter in the HP EVA Cluster Extension Administrator Guide. b. Select (1) View existing entries. The Existing entries dialog appears. c. Save the information in the Existing entries window, and then close the clxpmu window. 4. Move all of the applications from the current node to another node. 5. Double-click the HP EVA Cluster Extension installation package, and follow the on-screen instructions. 6. When the installation is complete, select the Launch EVA CLX Configuration Tool check box, and then click Finish. TIP: You can also start the HP EVA Cluster Extension configuration tool by double-clicking the icon on the Desktop. 7. Use the HP EVA Cluster Extension configuration tool to add the management servers captured in Step 3, the disk arrays, and the cluster nodes that are used with your HP EVA Cluster Extension solution. You only need to perform this step on one cluster node. When you complete the configuration procedure on the first node, the configuration tool automatically copies the configuration information to the other cluster nodes. For instructions on using the configuration tool, see the Configuring HP EVA Cluster Extension section in the HP EVA Cluster Extension Administrator Guide. IMPORTANT: The value that you enter in the Host name (or IP address) box in the HP EVA Cluster Extension configuration tool must match the value that was originally configured for the Hostname using the clxpmu tool and HP EVA Cluster Extension 2.01.00 or later. 8. Restart the cluster service on the node. 9. Repeat this procedure for all other nodes that are running HP EVA Cluster Extension 2.01.00 or later. Resetting the DR group GUI display After the upgrade is complete, the HP EVA Cluster Extension resource configuration GUI displays a blank value for the DR group Write mode property for existing HP EVA Cluster Extension resources. HP EVA Cluster Extension will work as expected even though the Write mode is not displayed in the GUI. If you want to view the correct Write mode value in the GUI, perform the following procedure: 1. Open the HP EVA Cluster Extension resource configuration tool or the Parameters tab in Cluster Administrator or Failover Cluster Management. 2. Click Advanced Settings and record the configured values for Application Startup behavior, Failsafe mode override, and Use non-current data ok. 3. Click Browse and then click OK to reselect the DR group. 18 Installing HP EVA Cluster Extension Software for Windows

4. Click Advanced Settings and enter the values recorded in Step 2. NOTE: For instructions on using the resource configuration GUI, see the HP EVA Cluster Extension Administrator Guide. Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2008/2008 R2) IMPORTANT: Perform the upgrade procedure on each node locally. HP EVA Cluster Extension does not support remote upgrades. 1. Download the HP EVA Cluster Extension Software from SUM. You can access SUM from the ITRC website: http://www.itrc.hp.com. 2. Verify that the new version of HP EVA Cluster Extension supports the version of HP P6000 (EVA) Command View that is installed on your management servers. Compatibility information is available on the HP SPOCK website: http://www.hp.com/storage/ spock. If you need to upgrade HP P6000 (EVA) Command View to support the new version of HP EVA Cluster Extension, use the procedure in Upgrading HP EVA Cluster Extension with HP P6000 (EVA) Command View upgrade (page 20). 3. Move all of the applications from the current node to another node. 4. Double-click the HP EVA Cluster Extension installation package, and follow the on-screen instructions. 5. Restart the cluster service on the node. 6. Repeat this procedure for all other nodes that are running HP EVA Cluster Extension 2.01.00 or later. Upgrading HP EVA Cluster Extension Software for Windows 19

Resetting the DR group GUI display After the upgrade is complete, the HP EVA Cluster Extension resource configuration GUI displays a blank value for the DR group Write mode property for existing HP EVA Cluster Extension resources. HP EVA Cluster Extension will work as expected even though the Write mode is not displayed in the GUI. If you want to view the correct Write mode value in the GUI, perform the following procedure: 1. Open the HP EVA Cluster Extension resource configuration tool or the Parameters tab in Cluster Administrator or Failover Cluster Management. 2. Click Advanced Settings and record the configured values for Application Startup behavior, Failsafe mode override, and Use non-current data ok. 3. Click Browse and then click OK to reselect the DR group. 4. Click Advanced Settings and enter the values recorded in Step 2. NOTE: For instructions on using the resource configuration GUI, see the HP EVA Cluster Extension Administrator Guide. Upgrading HP EVA Cluster Extension with HP P6000 (EVA) Command View upgrade This section explains how to upgrade HP P6000 (EVA) Command View to support the new version of HP EVA Cluster Extension. NOTE: period. HP recommends that you perform this procedure during a scheduled network maintenance 1. In the first data center, move all of the cluster resources to a node in the second data center. 2. Upgrade HP P6000 (EVA) Command View on the management server in the first data center. Configure the same SMI-S user information being used with the existing version of HP EVA Cluster Extension. For instructions, see your HP P6000 (EVA) Command View documentation. 3. Upgrade HP EVA Cluster Extension on the cluster nodes in the first data center. For instructions, see Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2003) (page 17) or Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2008/2008 R2) (page 19). 4. In the second data center, move all of the cluster resources to a node in the first data center. 5. Upgrade HP P6000 (EVA) Command View on the management server in the second data center. Configure the same SMI-S user information being used with the existing version of HP EVA Cluster Extension. For instructions, see your HP P6000 (EVA) Command View documentation. 6. Upgrade HP EVA Cluster Extension on the cluster nodes in the second data center. For instructions, see Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2003) (page 17) or Upgrading from HP EVA Cluster Extension 2.01.00 or later (Windows Server 2008/2008 R2) (page 19). 7. Verify that the upgrade was successful by confirming that all of the configured cluster applications come online when moved to each of the possible owners (cluster nodes) of the application. EVA Cluster Extension maintenance After installation, you can modify, repair, or remove EVA Cluster Extension. In the Server Core or Hyper-V Server environment, the Control Panel Programs and Features function is not available. To perform maintenance operations in a Server Core or Hyper-V Server environment, run the HP EVA Cluster Extension installation package from the command prompt. HP recommends 20 Installing HP EVA Cluster Extension Software for Windows

saving a copy of the HP EVA Cluster Extension installation package in case it is needed for performing maintenance operations on Server Core or Hyper-V Server systems. Modifying the EVA Cluster Extension installation Once EVA Cluster Extension is installed, you can modify the installation by adding or removing components. 1. Start the EVA Cluster Extension InstallShield wizard: a. Depending on your version of Windows, do one of the following: For Windows Server 2003: Select Start Control Panel Add or Remove Programs. For Windows Server 2008/2008 R2: Select Start Control Panel Programs and Features. For Server Core or Hyper-V Server: Run the HP EVA Cluster Extension installation package from the command line. Continue to Step 2. b. Select HP EVA Cluster Extension. Click Change/Remove (Windows Server 2003) or Uninstall/Change (Windows Server 2008/2008 R2). The InstallShield maintenance window appears. 2. Select Modify, and then click Next. The Select Features window appears. 3. Select the check boxes next to the features you want to install, clear the check boxes next to the features you want to remove, and then click Next. The Cluster node selection window appears. 4. Select the cluster nodes to modify, and then click Next. The InstallShield wizard notifies you that remote maintenance is in progress. For each selected cluster node, the wizard notifies you that maintenance was successful or unsuccessful. 5. For each remote maintenance confirmation window, click OK. The Maintenance Complete window appears. 6. Click Finish to close the InstallShield wizard. Repairing the EVA Cluster Extension installation Once EVA Cluster Extension is installed, you can repair the installation. 1. Start the EVA Cluster Extension InstallShield wizard: a. Depending on your version of Windows, do one of the following: For Windows Server 2003: Select Start Control Panel Add or Remove Programs. For Windows Server 2008/2008 R2: Select Start Control Panel Programs and Features. For Server Core or Hyper-V Server: Run the HP EVA Cluster Extension installation package from the command line. Continue to Step 2. b. Select HP EVA Cluster Extension. Click Change/Remove (Windows Server 2003) or Uninstall/Change (Windows Server 2008/2008 R2). The InstallShield maintenance window appears. 2. Select Repair, and then click Next. The Cluster node selection window appears. 3. Select the cluster nodes to repair, and then click Next. The InstallShield wizard notifies you that remote maintenance is in progress. EVA Cluster Extension maintenance 21

4. For each remote maintenance confirmation window, click OK. The Maintenance Complete window appears. 5. Click Finish to close the InstallShield wizard. Removing EVA Cluster Extension for Windows 1. Make sure that the cluster management application is not running. Failover Cluster Management is used on Windows Server 2008/2008 R2, and Cluster Administrator is used on Windows Server 2003. 2. Start the EVA Cluster Extension InstallShield wizard: a. Depending on your version of Windows, do one of the following: For Windows Server 2003: Select Start Control Panel Add or Remove Programs. For Windows Server 2008/2008 R2: Select Start Control Panel Programs and Features. For Server Core or Hyper-V Server: Run the HP EVA Cluster Extension installation package from the command line. Continue to Step 3. b. Select HP EVA Cluster Extension. Click Change/Remove (Windows Server 2003) or Uninstall/Change (Windows Server 2008/2008 R2). The InstallShield maintenance window appears. 3. Select Remove, and then click Next. The InstallShield wizard prompts you to confirm the uninstall request. 4. Click Yes to confirm the request. The Cluster node selection window appears. 5. Select the cluster nodes for EVA Cluster Extension removal, and then click Next. The install wizard prompts you to save the clxevacfg file. This file contains information about the HP EVA Cluster Extension configuration. If you save the file, you could import it later to restore your HP EVA Cluster Extension configuration. 6. Do one of the following: Click Yes if you want to save the clxevacfg file. Enter a file name, and then click Save. Click No. 7. Click OK. The install wizard asks if you want to unregister the cluster resource type from all nodes in the cluster. HP recommends that you do not unregister the cluster resource type until you are uninstalling EVA Cluster Extension from the last node in the cluster. Do one of the following: If you have not unregistered the cluster resource type, and this is the last node in the cluster, click Yes. If you have unregistered the cluster resource type from one of the other cluster nodes, click No. The Uninstall Complete window appears. 8. Click Finish. Troubleshooting installation and maintenance problems This section helps you locate and identify installation and maintenance problems. The cluster-wide installation feature allows you to install EVA Cluster Extension on multiple nodes in a cluster by running the installer from one node in the cluster. Cluster-wide installation is no different than local installation on each individual node. 22 Installing HP EVA Cluster Extension Software for Windows

Cluster-wide installation can fail to obtain the remote installation status if a remote node becomes unreachable. This can happen if the network connection or remote cluster node fails. If this type of failure occurs, find the error code in the file %WINDIR%\CLXSetup_nodename.result, available on the unreachable node, and then locate the error in Table 1 (page 23). In addition to showing the results of the installation process, the.result file helps you identify the status of remote maintenance if cluster level maintenance (modify, repair, remove) fails. NOTE: If the.result file is not found on the remote cluster node, run the EVA Cluster Extension setup by logging on to the remote cluster node locally. If you receive an error similar to Another installation is already in progress, then stop the process IDriver.exe (and msiexec.exe), or reboot the node and rerun the EVA Cluster Extension setup locally. Example If you start a cluster-wide installation on Node1 of a 3-node cluster, with all nodes selected for installation, and the network connection to Node2 and Node3 is lost by Node1, then the cluster-wide installation process cannot get the status of the remote node installation. In this situation, use the %WINDIR%\CLXSetup_nodename.result file to obtain the remote node installation status. To check the.result file for the remote nodes, log on to Node2 and Node3, and access the file %WINDIR%\CLXSetup_nodename.result on each node. Compare the errors in the file to the information in Table 1 (page 23). NOTE: If cluster installation fails with the message Could not get the system drive for the cluster node... or Setup was unable to run the installation in remote machine..., confirm that the WMI service is running. To use the HP EVA Cluster Extension cluster-wide installation feature, the WMI service must be running. Table 1 Windows remote installation error codes ERROR code ERROR_INSTALLATION_SUCCESS ERROR_REMOVAL_SUCCESS ERROR_REPAIR_SUCCESS ERROR_MODIFY_SUCCESS ERROR_READ_INPUT_FILE_FAILED ERROR_INVALID_HANDLE SILENT_INPUT_FILE_CORRUPTED LOCAL_NODE_NAME_NOT_FOUND ERROR_CLXMSCS_REGISTER_FAILED Description Installation was successful on the local cluster node. EVA Cluster Extension was successfully removed from the local cluster node. EVA Cluster Extension was successfully repaired on the local cluster node. EVA Cluster Extension was successfully modified on the local cluster node. Setup failed on the local cluster node. The silent input file is corrupted. Setup failed on the local cluster node. Internal Error. Could not invoke the DLL. Setup failed on the local cluster node. The silent input file is corrupted or could not be found. Setup failed on the local cluster node. Could not find the local node name. Installation completed on the local cluster node. Setup was unable to register the resource type Cluster Extension EVA. Corrective action N/A N/A N/A N/A Run the setup on the local cluster node. Run the setup on the local cluster node. Run the setup on the local cluster node. Run the setup on the local cluster node. Register the resource type by running the following cluster command: cluster restype "Cluster Extension EVA" /create Troubleshooting installation and maintenance problems 23

Table 1 Windows remote installation error codes (continued) ERROR code ERROR_CLXMSCSEX_REGISTER_FAILED ERROR_INSTALLDIR_NOT_FOUND ERROR_CLUS_SERVICE_UNKNOWN ERROR_CLUS_SERVICE_NOT_RUNNING ERROR_PCF_CREATION_FAILED ERROR_AUTOPASS_INSTALL_FAILED ERROR_CLXAUTOPASS_INSTANTON_FAILED ERROR_AUTOPASS_REMOVAL_FAILED ERROR_RESOURCE_STATE_UNKNOWN ERROR_RESOURCE_EXISTS Description Installation completed on the local cluster node. Setup was unable to register the Cluster Extension EVA DLL. Setup failed on the local cluster node. Setup was not able to get the INSTALLDIR value. Setup failed on the local cluster node. Setup is not able to determine whether the cluster service is running. Setup failed on the local cluster node. The cluster service is not running. Please start the cluster service. Installation failed on the local cluster node. The PCF file could not be created. Use clxpcfgen.exe to create the PCF file. Setup completed on the local cluster node. The AutoPass package was not installed properly. EVA Cluster Extension will not function correctly until the AutoPass package is properly installed. Installation completed on the local cluster node. Setup was unable to run clxautopass.exe installinstanton on the local cluster node. Uninstall completed on the local cluster node. Setup was unable to run the msiexec.exe command. Uninstall failed on the local cluster node. Setup is not able to determine whether a Cluster Extension EVA resource is still running. Uninstall failed on the local cluster node. Setup is unable to remove the Cluster Extension EVA resource type. Cluster Extension EVA resource(s) are still configured in this cluster. Corrective action /dll:clxevamscs.dll /type:"cluster Extension EVA" Register the resource extension DLL by running the following cluster command: Cluster / regadminext:clxevamscsex.dll Run the setup on the local cluster node. Run the setup on the local cluster node. Start the cluster service on the local node and run the EVA Cluster Extension setup. Run the setup on the local cluster node. Check the eventlog for more information, and then run the EVA Cluster Extension setup with the repair option. Install the instant-on license on the local node by running the following command: clxautopass.exe installinstanton Make sure msiexec.exe can be executed, and then run the EVA Cluster Extension setup on the local cluster node. Run the setup on the local cluster node. Remove all Cluster Extension EVA-type resource(s) from this cluster, and then run the EVA Cluster Extension setup. 24 Installing HP EVA Cluster Extension Software for Windows

Table 1 Windows remote installation error codes (continued) ERROR code ERROR_RESOURCE_STATE_ONLINE ERROR_CLXMSCSEX_UNREGISTER_FAILED ERROR_PCF_REMOVAL_FAILED CLXUNSETPATH_FAILED ERROR_DELETE_EVENTLOG_DLL_FAILED ERROR_UNINSTALL_DRS_FILES_FAILED ERROR_DELETE_SHARED_FILES_FAILED Description Uninstall failed on the local cluster node. A Cluster Extension EVA resource is still online. Uninstall failed on the local cluster node. Setup was unable to unregister the EVA Cluster Extension extension DLL. Uninstall completed on the local cluster node. Setup was unable to delete the PCF file. Uninstall completed on the local cluster node. Could not unset the path variables. Uninstall completed on the local cluster node. Could not delete clxeventlog.dll from the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\SharedDlls Uninstall completed on the local cluster node. Could not delete clxevamscs.dll and clxevamscsex.dll from the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\SharedDlls Uninstall completed on the local cluster node. Could not delete an HP EVA Cluster Extension-related entry from the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\SharedDlls Corrective action Remove all Cluster Extension EVA-type resource(s) from this cluster, and then run the EVA Cluster Extension setup. Unregister the resource extension DLL by running the following cluster command: Cluster /unregadminext:clxevamscsex.dll Delete the file clxpcf from INSTALL_DIR\bin. Remove the environment variable HPCLX_PATH from the local cluster node. Delete the clxeventlog.dll from the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\SharedDlls Delete clxevamscs.dll and clxevamscsex.dll from the following registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\SharedDlls Delete clxevamscs.dll, clxevamscsex.dll, clxevaeventlog.dll, clxlibeay32.dll, clxpegclient.dll, clxpegcommon.dll, and clxssleay32.dll from the following registry entry, if they exist: HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\SharedDlls Registering the resource type and resource extension DLL manually If a problem occurs during installation, execute the following commands from the command line to register the resource type: Troubleshooting installation and maintenance problems 25

1. Confirm that the resource type is registered with MSCS by entering the following cluster command: cluster resourcetype If the resource type is registered, the output includes the following information: Display Name Cluster Extension EVA If the resource type is not registered: Resource Type Name Cluster Extension EVA a. Enter cluster resourcetype "Cluster Extension EVA" /CREATE /DLLNAME:clxevamscs.dll /TYPE:"Cluster Extension EVA". b. Run the cluster resourcetype command again to verify that the resource type is now registered. 2. Check whether the cluster administrator extension DLL is registered with MSCS to provide the Cluster Administrator GUI functionality by entering: cluster resourcetype "Cluster Extension EVA" /PROPERTIES If the DLL is registered, the output includes the following information: Windows Server 2003: M Cluster Extension EVA AdminExtensions {C977EFB9-B640-4E6C-9473-ECE586EC2074} Windows Server 2008/2008 R2, Server Core, or Hyper-V Server: M Cluster Extension EVA AdminExtensions {ADD4FC7D-6DF5-40FF-9371-BBFC8619393D} If the DLL is not registered: a. Enter cluster /REGADMINEXT:clxevamscsex.dll. b. Run the cluster resourcetype command again to verify that the DLL is now registered. Unregistering the resource type and resource extension DLL manually Enter the following command to unregister the resource extension DLL: cluster /UNREGADMINEXT:clxevamscsex.dll. Enter the following command to unregister the resource type: cluster resourcetype "Cluster Extension EVA" /delete. 26 Installing HP EVA Cluster Extension Software for Windows