HP StorageWorks EVA Cluster Extension Software installation guide

This guide contains detailed instructions for installing and removing HP StorageWorks EVA Cluster Extension Software in Microsoft Cluster Service and HP Serviceguard environments. The intended audience has independent knowledge of related Windows or Linux software and of the HP StorageWorks Enterprise Virtual Array and its software.

Part number: T3667-96008 Second edition: November 2008

Legal and notice information Copyright 2006, 2008 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, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Java is a US trademark of Sun Microsystems, Inc.

Contents
1 Environment and pre-installation requirements ........................................ 5
Environment considerations .......................................................................................................... Ideal environment ................................................................................................................. Network communication requirements ..................................................................................... Data backup requirements ..................................................................................................... How EVA Cluster Extension Software interacts with its environment .................................................... Failover function ................................................................................................................... How EVA Cluster Extension utilizes vdisks ................................................................................ How EVA Cluster Extension stores information .......................................................................... Pre-installation requirements ......................................................................................................... Environmental setup .............................................................................................................. Required disk space and system memory ................................................................................. Software versions and supported features ...................................................................................... 5 5 5 5 6 6 6 6 7 7 7 8

2 Installing EVA Cluster Extension for Windows ........................................ 9

Prerequisites for Windows ............................................................................................................ 9 Pre-installation procedures ........................................................................................................... 9 Step 1: Check the IP network setup and SAN configuration ....................................................... 9 Step 2: Install multipath software .......................................................................................... 10 Step 3: Install and configure Java Runtime Environment (JRE) ................................................... 10 Step 4: Install and configure the HP SMI-S EVA server on all management servers ...................... 10 Step 5: Configure the HP EVA storage system ......................................................................... 10 Step 6: Create hosts ........................................................................................................... 11 Step 7: Create vdisks and add a LUN presentation ................................................................. 11 Step 8: Create Data Replication (DR) groups .......................................................................... 11 Step 9: Set read-only mode and add a LUN presentation to the destination vdisk ........................ 11 Step 10: Install MSCS on all nodes ....................................................................................... 12 Installing EVA Cluster Extension Software for Windows .................................................................. 12 Installing EVA Cluster Extension for Windows Server 2003 ...................................................... 13 Installing EVA Cluster Extension for Windows Server 2008 ...................................................... 15 Registering the resource type and resource extension DLL manually .................................................. 15 Upgrading the software ............................................................................................................ 16 Removing EVA Cluster Extension for Windows Server 2003 ........................................................... 17 Removing the EVA Cluster Extension Software resource type ..................................................... 17 Removing EVA Cluster Extension Software ............................................................................. 17 Removing EVA Cluster Extension for Windows Server 2008 ........................................................... 18 Removing the EVA Cluster Extension Software resource type ..................................................... 18 Uninstalling EVA Cluster Extension Software ........................................................................... 18

3 Installing in HP Serviceguard for Linux environments ............................. 21

Pre-installation procedures ......................................................................................................... Step 1: Check the IP network setup and SAN configuration ..................................................... Step 2: Configure the HBA driver(s) for multipath failover ......................................................... Step 3: Install and configure the HP SMI-S EVA server on all management servers ...................... 21 21 22 22

EVA Cluster Extension Software installation guide

Step 4: Configure the HP EVA storage system ......................................................................... 22 Step 5: Create hosts ........................................................................................................... 22 Step 6: Create vdisks and add a LUN presentation ................................................................. 22 Step 7: Create Data Replication (DR) groups .......................................................................... 23 Step 8: Set read-only mode and add a LUN presentation to the destination vdisk ....................... 23 Step 9: Configure the Logical Volume Manager ...................................................................... 23 Step 10: Install and configure HP Serviceguard for Linux on all cluster nodes ............................. 24 Installing EVA Cluster Extension Software for Linux ........................................................................ 24 Removing EVA Cluster Extension Software for Linux ....................................................................... 25

4 Licensing ......................................................................................... 27
Retrieving a license key .............................................................................................................. Using AutoPass to retrieve permanent license keys ......................................................................... clxautopass command line utility ................................................................................................. Installing the license ........................................................................................................... Importing a license key from a file ........................................................................................ EVA Cluster Extension registration tool (Windows 2008 only) ......................................................... 27 27 27 28 28 28

5 Reference ........................................................................................ 29
Related documentation .............................................................................................................. HP technical support ................................................................................................................. Subscription service .................................................................................................................. HP web sites ............................................................................................................................ Documentation feedback ........................................................................................................... 29 29 29 30 30

Glossary ............................................................................................ 31 Index ................................................................................................. 33

1 Environment and pre-installation requirements

This chapter provides information about general environment considerations and pre-installation requirements.

Environment considerations
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 Continuous Access EVA. All communications interfaces must be installed in pairs to serve as failover components, in order to prevent single points of failure.

Network communication requirements

Network communications require that alternative pathing software for host-to-storage connections such as HP StorageWorks Secure Path for Windows operating systems be used. 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 both data center's systems 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.

Data backup requirements

To ensure reliable data backup between the primary and remote storage systems, at least two Continuous Access EVA 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 Continuous Access EVA 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 site, two systems should be available in case the primary failover system experiences a hardware or power failure.

EVA Cluster Extension Software installation guide

 Windows: Using an Majority Node Set (MNS) quorum requires an odd number of cluster nodes, with at least one system in a third location. For HP Serviceguard for Linux, the quorum server is not a cluster node and should reside in a location separate from either data center. CAUTION: EVA Cluster Extension Software works with only one system at each location, with a single I/O path between the server and the storage system and a single link between storage systems. However, those configurations are not considered highly available, nor are they disaster tolerant. Therefore, configurations with single points of failure are not supported by HP.

How EVA Cluster Extension Software interacts with its environment

Failover function
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 virtual disks (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 in the cluster.

How EVA Cluster Extension utilizes vdisks

To write to Continuous Access EVA 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, 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. EVA Cluster Extension Software determines whether those vdisks can be accessed and made available to the application service.

How EVA Cluster Extension stores information

EVA Cluster Extension stores information about the application environment in an internal object database and uses HP Storage Management Initiative Specification (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.

Environment and pre-installation requirements

Pre-installation requirements
Environmental setup
Ensure that the following conditions are met before installing EVA Cluster Extension Software: Continuous Access EVA links (including extender hardware) are redundant and configured to be bidirectional. Alternate I/O paths between servers and the EVA storage system are set up. Cluster and client networks are redundant. Cluster nodes can communicate with each other (not required for Windows 2003). The latest supported software and firmware versions, fixes, FC adapter firmware, and driver versions for your servers and EVA storage systems are installed. The cluster nodes in your zoning configuration each recognize their respective (local) EVA, but not the remote EVA. Each management server recognizes both EVAs and can recognize each other. The following figure shows a zoning example.

Required disk space and system memory

Ensure the following minimum amount of disk space is available:

Linux
5 MB for /opt/hpclxeva 1 MB for /etc/opt/hpclxeva 100 MB for /var/opt/hpclxeva

Windows
50 MB in %ProgramFiles%\Hewlett-Packard\Cluster Extension EVA At least 25 MB of system memory.

EVA Cluster Extension Software installation guide

Software versions and supported features

For specific firmware and software versions, see HP StorageWorks EVA Cluster Extension Software compatibility reference.

Environment and pre-installation requirements

2 Installing EVA Cluster Extension for Windows

This chapter describes the installation of EVA Cluster Extension in MSCS environments with the HP EVA family of storage systems. NOTE: For information on configuring EVA Cluster Extension in an MSCS environment, see the HP StorageWorks EVA Cluster Extension Software administrator guide.

Prerequisites for Windows

Prior to installation, perform the following tasks: Make sure you have met the Pre-installation requirements on page 7. Install and configure MSCS.

Pre-installation procedures
Complete the following configuration procedures for the local primary and remote secondary sites: Step Step Step Step Step Step Step Step Step Step 1: Check the IP network setup and SAN configuration, page 9. 2: Install multipath software, page 10. 3: Install and configure Java Runtime Environment (JRE) , page 10. 4: Install and configure the HP SMI-S EVA server on all management servers, page 10. 5: Configure the HP EVA storage system, page 10. 6: Create hosts, page 11. 7: Create vdisks and add a LUN presentation, page 11. 8: Create Data Replication (DR) groups, page 11. 9: Set read-only mode and add a LUN presentation to the destination vdisk, page 11. 10: Install MSCS on all nodes, page 12.

Step 1: Check the IP network setup and SAN configuration

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. EVA Cluster Extension requires a cluster environment in which one location failure will not cause the entire cluster to shut down.

EVA Cluster Extension Software installation guide

 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 center and an additional node in a third location functions as a tie-breaker 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 tie-breaker. SAN fabrics can be extended to allow for array-based data replication. Consult the HP StorageWorks Continuous Access EVA implementation guide and the SAN Design Guide for supported SAN extension configuration and instructions on setting up your HP Continuous Access EVA environment. EVA Cluster Extension Software works in dispersed data center environments with a separation distance of up to 500 km or a round-trip latency of up to 20 milliseconds.

Step 2: Install multipath software

You must use multipath software to take advantage of the I/O path failover feature, a feature that is not available with Windows operating systems. Install the multipath software on the cluster system before connecting the system to the second I/O path. Depending on the array model, use HP Secure Path or HP MPIO Full Featured DSM (Device Specific Module) for Windows. For more information, see the HP StorageWorks EVA Cluster Extension Software compatibility reference.

Step 3: Install and configure Java Runtime Environment (JRE)

To install the product license through the OpenView AutoPass graphical user interface (GUI), you must first install the Java Runtime Environment (JRE). See the AutoPass documentation for the latest supported JRE versions.

Step 4: Install and configure the HP SMI-S EVA server on all management servers
Install the HP SMI-S EVA server component on all of the management servers that run the HP Command View EVA software. Review the HP StorageWorks Command View EVA installation guide and HP StorageWorks Command View EVA release notes to set the access properties. When you configure 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 Secure Sockets Layer (SSL) enabled, and 5988 with SSL disabled. User name Password SSL use (yes or no)

Step 5: Configure the HP EVA storage system

For detailed information on configuring the HP EVA storage system, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks 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.

10

Installing EVA Cluster Extension for Windows

Step 6: Create 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 EVA storage system. For detailed information, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 7: Create vdisks and add a LUN presentation

Create the storage (vdisks) for your application data using the Storage System Scripting Utility (SSSU) or the Command View EVA GUI, and then present the vdisks to the cluster nodes connected to that EVA array. NOTE: Later in this installation process, you will have to create a LUN presentation for your remote destination vdisk and set the access mode property for the destination vdisk to read-only. See Step 9: Set read-only mode and add a LUN presentation to the destination vdisk on page 11. For detailed instructions, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 8: Create Data Replication (DR) groups

Before you can use 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(s), 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: Select either Disabled or Enabled to set the Failsafe mode. EVA Cluster Extension supports either mode. However, there are failover scenarios in which EVA Cluster Extension will not be able to successfully fail over if Failsafe mode is enabled. When this happens, EVA Cluster Extension will log messages to indicate that it has encountered such a scenario. Set the Write mode to Synchronous. For detailed information, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 9: Set read-only mode and add a LUN presentation to the destination vdisk
The final steps of the HP Continuous Access EVA setup are to 1. 2. Set access mode to read-only for the destination vdisk. You can set this property only by using SSSU. Add a LUN presentation to your remote cluster node.

EVA Cluster Extension Software installation guide

11

NOTE: HP recommends that you use the same LUN number 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 Step 6: Create hosts on page 11. For detailed instructions, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 10: Install MSCS on all nodes

1. Before installing MSCS, create your disk configuration through the Disk Manager. If the disks are not visible, rescan 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 after 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 EVA Cluster Extension is installed. You must also reboot the server(s) on the destination storage system or rescan the disks in the Disk Manager prior to and after installing the cluster software and at any later time that you add storage in read-only mode on the destination side. 2. 3. 4. Install Microsoft Cluster Service on all cluster nodes. Select Majority Node Set quorum as the cluster's quorum resource. Quorum disks as a quorum resource are not supported with EVA Cluster Extension Software. Windows Server 2008 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 EVA Cluster Extension Software on all cluster nodes that have a FC connection to the local or remote HP EVA and are used to access storage resources on the HP EVA. If the system that acts as an arbitrator or tie-breaker is not connected to either HP 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.

12

Installing EVA Cluster Extension for Windows

Use this procedure to install the following components: Resource DLL (clxevamscs.dll) Cluster administrator extension DLL (clxevamscsex.dll) Command line interface (CLI) (clxevarun.exe) You can use the CLI for custom cluster software integration. For example, you can write your own online and offline scripts using the advanced DR group status checking options. NOTE: Installing the CLI is not required if you are using EVA Cluster Extension Software with MSCS.

CAUTION: The installation adds a resource type DLL to MSCS. The associations with this resource type DLL are lost if the cluster software is removed. Every new installation, removal, or reinstallation of MSCS requires running the Repair Cluster resource type setup program. For more information, see the EVA Cluster Extension Software administrator guide.

Installing EVA Cluster Extension for Windows Server 2003

1. 2. 3. 4. 5. 6. Log in to the cluster node with your administrator account. Make sure that the cluster service is running. Make sure that the Cluster Administrator application is not running. Browse to http://www.hp.com/go/softwaredepot. Click Storage and NAS in the product category list. Locate and download the self-extracting install package to a local directory on the cluster node, and then double-click the install package to start the installation. The installer prompts you to check the compatibility reference to verify that you are running supported versions of the array firmware and other required software. 7. 8. Verify that the correct software is installed, and then click OK. Follow the instructions to enter your identification and select the program installation location.

EVA Cluster Extension Software installation guide

13

9.

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 without documentation. Select Custom to select specific components to install. The Custom setup allows the option of installing only the CLX cluster administrator DLL on a management server. This enables you to run the Cluster Administrator GUI and manage the resources from a management host without requiring a separate license for this node.

10. In the Enter SMI-S IP address, login, and password dialog box, enter the login name and password for SMI-S, which may be different from the actual host login name and password. For Port #, accept the default at this point. Do not overwrite. This is the number of the HP SMI-S connection port. Whether or not SSL is selected determines the default port number.

11. Click Add Next to clear the window and complete the dialog box for additional EVA management servers.

14

Installing EVA Cluster Extension for Windows

12. When you have added all desired EVA management servers, click Save/Finish. 13. Complete the license process. See Chapter 4 on page 27 for detailed procedures.

Installing EVA Cluster Extension for Windows Server 2008

1. 2. 3. 4. 5. 6. Make sure that the cluster service is running. Make sure that the Failover Cluster Management application is not running. Browse to http://www.hp.com/go/softwaredepot. Click Storage and NAS in the product category list. Locate and download the installation package to a local directory on the cluster node. Extract the installation package to a folder, and then double-click setup.exe. The installer prompts you to check the compatibility reference to verify that you are running supported versions of the array firmware and other required software. 7. 8. 9. Verify that the correct software is installed, and then click OK. Follow the instructions to accept the license agreement, enter your identification, and select the program installation location. 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 without documentation. Select Custom to select specific components to install. The Custom setup allows the option of installing only the CLX cluster administrator DLL on a management server. This enables you to run the Cluster Administrator GUI and manage the resources from a management host without requiring a separate LTU for this node. 10. Click Yes when the installer asks if you want to install a permanent license. Follow the instructions in Chapter 4 on page 27 to retrieve and the license, and then click Finish. TIP: To start the configuration tool at the end of the installation, select the Configuration Tool check box before you click Finish. 11. Restart the cluster service on all of the cluster nodes. This step is required to complete the AutoPass licensing process. 12. After installation, configure EVA Cluster Extension on all cluster nodes. To perform the required configuration steps, follow the instructions in Configuring EVA Cluster Extension (Windows Server 2008 only) in the administrator guide.

Registering the resource type and resource extension DLL manually

If a problem occurs during installation, execute the following commands from the MSCS command line to register the resource type.

EVA Cluster Extension Software installation guide

15

1.

Check whether the resource type is registered with MSCS by entering: \cd %SystemRoot%\system32 cluster resourcetype If the resource type is registered, the output includes the following information:
Display Name Cluster Extension EVA Resource Type Name Cluster Extension EVA

If the resource type is not registered: a. b. 2. Enter cluster resourcetype "Cluster Extension EVA" /CREATE /DLLNAME:clxevamscs.dll /TYPE:"Cluster Extension EVA". Run the cluster resourcetype command again to verify that the resource type is now registered.

Check whether the 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:
T Resource Type Name SR Cluster Extension EVA DllName Value clxevamscs.dll

If the DLL is not registered: a. b. Enter cluster /REGADMINEXT:clxevamscsex.dll. Run the cluster resourcetype command again to verify that the DLL is now registered.

Upgrading the software

NOTE: This section applies to Windows Server 2003 only. There is no upgrade procedure for EVA Cluster Extension Software for Windows Server 2008 because this is the first release supporting Windows Server 2008. This section explains how to upgrade to the latest version of EVA Cluster Extension Software without losing SMI-S user configuration and resource type configuration information, and without any application downtime. This procedure assumes that you first upgrade the software and then upgrade your version of HP Command View EVA. 1. 2. Move all the applications from the current node to any other node. Remove the software from the current node. Do not unregister the resource type. a. b. c. d. 3. 4. Click Start > Control Panel > Add or Remove Programs. Click Cluster Extension EVA, and then click Change/Remove. Click Yes to save the SMI-S configuration file. When asked whether to unregister the resource type, click No.

Install the latest version of the software. Repeat steps 13 for all other nodes where the software has been installed.

16

Installing EVA Cluster Extension for Windows

Removing EVA Cluster Extension for Windows Server 2003

Removing the EVA Cluster Extension Software resource type
To remove the EVA Cluster Extension resource type from the system, you must first remove the individual EVA Cluster Extension resources. For instructions about how to remove resources, see the Microsoft Cluster documentation. 1. Before you can remove the EVA Cluster Extension resource type from the system, stop the resource groups or switch the resource groups that contain an EVA Cluster Extension resource to another system. Remove the node from the list of possible owners and from the node name list of the EVA Cluster Extension resource. Select the Add/Remove Programs utility from the Control Panel. In the Change or Remove Programs pane, select HP StorageWorks EVA Cluster Extension. In the setup maintenance Welcome dialog, select Modify to remove only the resource type while leaving other components installed. Ensure that Cluster Resource Type is not checked, then click Next. Select Remove to remove all EVA Cluster Extension components. For more information, see the EVA Cluster Extension administrator guide.

2. 3. 4. 5. 6. 7.

Removing EVA Cluster Extension Software

1. 2. 3. 4. 5. Stop all Cluster Administrator programs. Select Start > Control Panel > Add or Remove Programs. Select Cluster Extension EVA and click Change/Remove. Select Remove and click Next. Choose one of the following options: Click Yes to unregister the EVA Cluster Extension resource type from Microsoft Cluster Administrator. The resource type will not be available to the other nodes in the cluster. Click No if you do not want to unregister the resource type from Microsoft Cluster Administrator. The resource type will still be available to the other nodes in the cluster. NOTE: Microsoft Cluster Service must be installed and running for setup to unregister the EVA Cluster Extension resource type. If you unregister the resource type, but Microsoft Cluster Service is not installed and running, a message appears indicating that setup was not able to determine if Microsoft Cluster Service is running. 6. 7. Click Yes if you want to delete the file clxsmiscfg file; otherwise, click No. Click Finish.

EVA Cluster Extension Software installation guide

17

Removing EVA Cluster Extension for Windows Server 2008

Removing the EVA Cluster Extension Software resource type
To remove the EVA Cluster Extension resource type from the system, you must first remove the individual EVA Cluster Extension resources. See the Microsoft Cluster documentation for instructions about how to remove resources. 1. Take the services and applications containing EVA Cluster Extension resources offline or move them to another cluster node. NOTE: Cluster Administrator on Windows Server 2003 uses the term Groups. This term changed to Services and Applications in Failover Cluster Management for Windows Server 2008. In this guide, the term Services and Applications is used interchangeably with Groups. 2. 3. 4. 5. Remove the node from the list of possible owners and from the node name list of the resource. Run the EVA Cluster Extension installation program. Select Modify to remove the resource type while leaving other components installed. Deselect HP StorageWorks EVA Cluster Extension, and then click Next. The installer asks if you want to unregister the resource type.

6. 7.

If this is the last cluster node with EVA Cluster Extension installed, click Yes. Otherwise, click No. Click Finish in the Maintenance Complete dialog box.

Uninstalling EVA Cluster Extension Software

1. 2. Run the EVA Cluster Extension installation program. Select Remove, and then click Next. The InstallShield wizard prompts you to confirm the uninstall request.

18

Installing EVA Cluster Extension for Windows

3.

Click Yes to confirm the uninstall request. The install wizard asks if you want to save the C:\Program Files\Hewlett-Packard\Cluster Extension EVA\bin\clxevacfg file. This file contains information about the EVA Cluster Extension configuration. If you save the file, you could import it to restore your EVA Cluster Extension configuration. Do one of the following: Click Yes if you want to save the file. Enter a file name, and then click Save. Click No if you do not want to save the file. 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.

4.

5.

Do one of the following: If you have not uninstalled EVA Cluster Extension from all of the other cluster nodes, click No. If you have uninstalled EVA Cluster Extension from all of the other cluster nodes, click Yes. Click Finish.

6.

EVA Cluster Extension Software installation guide

19

20

Installing EVA Cluster Extension for Windows

3 Installing in HP Serviceguard for Linux environments

This chapter describes how to install the EVA Cluster Extension Software in a Linux environment. The software provides integration with HP Serviceguard for Linux clustering software, as well as a standalone application that can be used for non-Serviceguard storage solutions. Prior to installation, perform the following tasks: Ensure that you have met the Pre-installation requirements on page 7. Install and configure HP Serviceguard for Linux on each cluster node. Install Serviceguard Quorum Server on a non-cluster host. Check the certification matrix for the latest HP Serviceguard for Linux support information (http:/ /www.hp.com/info/sglx). Ensure you have the latest supported software and firmware versions, fixes, FC adapter firmware, and driver versions.

Pre-installation procedures
Complete the following configuration procedures for the local primary and remote secondary sites: Step 1: Check the IP network setup and SAN configuration, page 21. Step 2: Configure the HBA driver(s) for multipath failover, page 22. Step 3: Install and configure the HP SMI-S EVA server on all management servers, page 22. Step 4: Configure the HP EVA storage system, page 22. Step 5: Create hosts, page 22. Step 6: Create vdisks and add a LUN presentation, page 22. Step 7: Create Data Replication (DR) groups, page 23. Step 8: Set read-only mode and add a LUN presentation to the destination vdisk, page 23. Step 9: Configure the Logical Volume Manager, page 23. Step 10: Install and configure HP Serviceguard for Linux on all cluster nodes, page 24.

Step 1: Check the IP network setup and SAN configuration

HP Serviceguard for Linux 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. Several virtual LAN (VLAN) technologies that can stretch single subnets over long distance connections are available. For example, Wave Division Multiplexer (WDM) and its variations can be used to extend several different protocols (including IP and Fibre Channel) over large distances (100 km and more). Ask your network equipment provider and your HP sales representative for detailed information. In an HP Serviceguard for Linux cluster you will need to configure an additional Quorum Server. For details, see the latest edition of Managing HP Serviceguard for Linux.

EVA Cluster Extension Software installation guide

21

Step 2: Configure the HBA driver(s) for multipath failover

Configure the HBA driver(s) for multipath failover using the HBA manufacturer's instructions. Load balancing impacts multipath performance. To ensure optimal load balancing, see the installation and configuration procedures in your multipath software documentation, and the Configuring hosts and Optimizing Performance sections of the HP StorageWorks Continuous Access EVA implementation guide.

Step 3: Install and configure the HP SMI-S EVA server on all management servers
Install the HP SMI-S EVA server component on all of the management servers that run the HP Command View EVA software. Review the HP StorageWorks Command View EVA installation guide and HP StorageWorks Command View EVA release notes to set the access properties. When you configure the software, you will need the following HP SMI-S information: HP SMI-S server name and IP address Port number. The default is 5989 with Secure Sockets Layer (SSL) enabled, and 5988 with SSL disabled. User name Password SSL use (yes or no)

Step 4: Configure the HP EVA storage system

For detailed information on configuring the HP EVA storage system, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks 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.

Step 5: Create 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 EVA storage system. For detailed information, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 6: Create vdisks and add a LUN presentation

Create the storage (vdisks) for your application data using the Storage System Scripting Utility (SSSU) or the Command View EVA GUI, and then present the vdisks to the cluster nodes connected to that EVA array.

22

Installing in HP Serviceguard for Linux environments

NOTE: Later in this installation process, you will have to create a LUN presentation for your remote destination vdisk and set the access mode property for the destination vdisk to read-only. You can set this property only by using SSSU. See Step 8: Set read-only mode and add a LUN presentation to the destination vdisk on page 23. For detailed instructions, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 7: Create Data Replication (DR) groups

Before you can use 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(s), 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: Select either Disabled or Enabled to set the Failsafe mode. EVA Cluster Extension supports either mode. However, there are failover scenarios in which EVA Cluster Extension will not be able to successfully fail over if Failsafe mode is enabled. When this happens, EVA Cluster Extension will log messages to indicate that it has encountered such a scenario. Set the Write mode to Synchronous. For detailed information, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 8: Set read-only mode and add a LUN presentation to the destination vdisk
The final steps of the HP Continuous Access EVA setup are to 1. 2. Set access mode to read-only for the destination vdisk. You can set this property only by using SSSU. Add a LUN presentation to your remote cluster node.

NOTE: HP recommends that you use the same LUN number 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 Step 6: Create hosts on page 11. For detailed instructions, see the HP StorageWorks Command View EVA user guide or the HP StorageWorks Storage System Scripting Utility reference.

Step 9: Configure the Logical Volume Manager

Each shared data disk is within its own DR group and resides on an HP EVA that is mirrored to the remote data center using HP Continuous Access EVA. To access the disks within the DR groups that

EVA Cluster Extension Software installation guide

23

are in read/write mode, the source side of the DR group must be in the local (currently active) data center. To make each disk accessible to the nodes located in the remote data center on a host with its disks on the source side of the DR group: 1. 2. 3. Create volume groups, logical volumes, and file systems on the source system for all HP Serviceguard for Linux cluster packages. Use Command View EVA to switch the DR mode of the destination side of the DR groups to source to make the shared disks accessible. Import volume groups and logical volumes on the remote nodes after creating the mount points on each node using vgscan.

Step 10: Install and configure HP Serviceguard for Linux on all cluster nodes
See the HP Serviceguard for Linux Version Release Notes for detailed installation procedures.

Installing EVA Cluster Extension Software for Linux

EVA Cluster Extension Software provides an installation script for Linux. This script installs the software with HP Serviceguard for Linux and a standalone CLI. Use this procedure to install the following components: HP Serviceguard for Linux integration executable (clxevamcsg) CLI (clxevarun) To install the software: 1. 2. 3. 4. 5. Log in as root. Browse to http://www.hp.com/go/softwaredepot. Click Storage and NAS in the product category list. Locate and download the compressed installation script file (for example, T4393-10504_hpclxeva_v1.02.00.tar.gz) to a temporary directory on your system. Uncompress and extract the contents of this downloaded file to the hpclxeva_version directory (created during extraction) by running the following command: # tar xvfz installation_script_filename.tar.gz 6. Change to the hpclxeva_version directory using the following command: # cd hpclxeva_version 7. Run the install script. # ./INSTALL When the installation process begins, you will be asked if you want to configure the EVA host management information. If you choose to do so, you will be prompted to enter the information at this time. If you decline, you can enter this information later using the installed password management utility clxpmu (see the HP StorageWorks EVA Cluster Extension Software administrator guide for more information).

24

Installing in HP Serviceguard for Linux environments

8.

After installation, read the /opt/hpclxeva/docs/README.ReleaseNotes file. Repeat steps 16 on each system that will run HP Serviceguard for Linux with EVA Cluster Extension Software. NOTE: For post-installation configuration, see the HP StorageWorks EVA Cluster Extension Software administrator guide.

Removing EVA Cluster Extension Software for Linux

There are two procedures available for removing EVA Cluster Extension Software: To use the uninstall script located in the /opt/hpclxeva/bin directory, run the following command: # /opt/hpclxeva/bin/CLX_UNINSTALL This will remove all files and reset all environment variables installed by the installation script. To manually remove the software using rpm, run the following command: # rpm e clxeva

EVA Cluster Extension Software installation guide

25

26

Installing in HP Serviceguard for Linux environments

4 Licensing
This chapter explains how to obtain and install the product license keys. A license key is required to use all of the product features. The License Entitlement Certificate provides instructions on how to obtain a license key. In the meantime, a temporary, instant-on license key is available so that you can immediately start using all of the features. The instant-on key is valid for 60 days from the first use. Upon expiration of the instant-on license key, the features will be disabled; you must obtain a permanent license key to continue using the features.

Retrieving a license key

When you purchase this product, you receive a License Entitlement Certificate. You will need information from this certificate to retrieve and enter your license keys. You can use any of the following methods to request a license key. Obtain a license key from http://webware.hp.com. Use AutoPass to retrieve permanent license keys. See Using AutoPass to retrieve permanent license keys on page 27. Fax the Password Request Form that came with your License Entitlement Certificate. See the certificate for fax numbers in your area. Call or e-mail the HP Password Center. See the certificate for telephone numbers in your area or e-mail addresses.

Using AutoPass to retrieve permanent license keys

1. Start AutoPass, located in the product's bin directory: clxautopass -ovlicensemgr AutoPass requires that a Java Runtime Environment (JRE) and/or SDK be installed on the cluster node. See the AutoPass documentation for the latest supported JRE versions. 2. Take one of the following actions: If you have an Internet connection, click Retrieve/Install License Key If you installed the product on a system that does not have an Internet connection, click Retrieve License Key through Email/Fax. When you receive the license key in e-mail, start AutoPass and click Install/Restore License Key. After installing the permanent license keys, restart the product so the license will be recognized. You can restart the product by restarting the MSCS or the agent in VCS environments.

3.

clxautopass command line utility

In addition to using the clxautopass command to start AutoPass, you can also use the command at the CLI to install the instant-on license and import a password from the license key file.

EVA Cluster Extension Software installation guide

27

Installing the license

If the installation process failed to install the license, use the you can use the CLI instead. First repair any conditions that may have caused the license installation to fail, and then run the following command to install the license: clxautopass -installinstanton

Importing a license key from a file

When you receive the license key file by e-mail, import the license key by running the following command: clxautopass -addpasswords <license file path> where <license file path> is the full (absolute) path name to the license key file. This command is equivalent to using the Install/Restore License Key from file option in AutoPass.

EVA Cluster Extension registration tool (Windows 2008 only)

In addition to using the AutoPass GUI and CLI, you can install a license key with the EVA Cluster Extension registration tool. 1. 2. 3. 4. Select Start > All Programs > Hewlett-Packard > HP StorageWorks EVA CLX Registration Tool. Click Browse. Browse to your license key file, and then click Install License. Click Close when you are done installing license keys.

28

Licensing

5 Reference
Related documentation
The following documents and web sites provide related information: HP StorageWorks EVA Cluster Extension Software administrator guide HP StorageWorks EVA Cluster Extension Software compatibility reference HP StorageWorks Continuous Access EVA implementation guide HP StorageWorks Command View EVA user guide HP StorageWorks Command View EVA online help (accessible from the HP Command View EVA user interface) HP StorageWorks Enterprise Virtual Array updating product software HP StorageWorks SAN design guide Managing HP Serviceguard for Linux HP Serviceguard for Linux. See the HP High Availability web site: http://docs.hp.com/en/ha.html and the HP Serviceguard for Linux ProLiant cluster web site: http://www.hp.com/info/sglx You can find the HP documents from the Manuals page of the HP Business Support Center web site: http://www.hp.com/support/manuals In the Storage section, click Storage software and then select a product.

HP technical support
For worldwide technical support information, see the HP support web site: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions

Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business web site:

EVA Cluster Extension Software installation guide

29

http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources.

HP web sites
For additional information, see the following HP web sites: http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/support/manuals

Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to storagedocsFeedback@hp.com. All submissions become the property of HP.

30

Reference

Glossary
CA CLI CV EVA HP StorageWorks Continuous Access EVA. CA lets you create and maintain duplicate copies of local logical volumes on a remote storage system. Command line interface. HP StorageWorks Command View Enterprise Virtual Array, a software product for managing EVA arrays. Command View runs on a Windows-based management workstation. A volume on the storage system that accepts HP Continuous Access or HP Business Copy control operations that are then executed by the storage system. Custom volume size. CVS devices (OPEN-x CVS) are custom volumes configured using array management software to be smaller than normal fixed-size OPEN system volumes. See also VSC A named group of disks selected from all the available disks in an array. One or more virtual disks can be created from a disk group. Data replication group. A named group of virtual disks selected from one or more disk groups to replicate to the same destination, fail over together if a member virtual disk fails, and preserve write order within the group. Enterprise Virtual Array. An HP StorageWorks disk array product that allows pooled disk capacity to be presented to hosts as one or more variably sized physical devices. An EVA consists of disks, controllers, cables, power supplies, and controller software. Storage system, virtual array, and storage array are other names for an EVA. See also virtual disk An operation that reverses replication direction so that the destination becomes the source and the source becomes the destination. Failovers can be planned or unplanned and can occur between DR groups, managed sets, fabrics or paths, and array controllers. Fibre Channel. Host bus adapter. A periodic synchronization signal issued by cluster software or hardware to indicate that a node is an active member of the cluster. A computer that runs user applications and uses (or potentially uses) one or more virtual disks that are created and presented by the array controller. A server on which HP StorageWorks Enterprise Virtual Array (EVA) management software is installed, including HP Command View EVA and HP Replication

command device CVS

disk group DR group

EVA

failover

FC HBA heartbeat host management server

EVA Cluster Extension Software installation guide

31

Solutions Manager, if used. A dedicated management server runs EVA management software exclusively. Other management servers include general-purpose servers, HP ProLiant Storage Server models, and the Storage Management Appliance. When there are multiple management servers in a SAN, two active instances of HP Command View EVA are allowed, but each array will only be managed by one instance. The active management server actively manages the array, while the standby management server takes control of the array if there is a failure on the active management server. There can be only one active management server at a time for any given management zone in a SAN. port A physical connection that allows data to pass between a host and the storage system. The number of ports on an EVA storage system depends on the number of supported I/O slots and the number of ports available per I/O adapter. The EVA family of storage systems supports Fibre Channel (FC) ports as well as other port types. Ports are named by port group and port letter, such as CL1-A, where CL1 is the port group, and A is the port letter. Data center location that owns the cluster group (quorum resource). In MSCS: A cluster resource that has been configured to control the cluster, maintaining essential cluster data and recovery information. In the event of a node failure, the quorum acts as a tie-breaker and is transferred to a surviving node to ensure that data remains consistent within the cluster. In HP Serviceguard for Linux: a cluster resource that provides tie-breaking services to prevent split-brain syndrome. Red Hat package manager. Small computer system interface. Location of the mirror copy of the quorum disk pair in the data center. A state of data corruption that can occur if a cluster is re-formed as subclusters of nodes at each site, and each subcluster assumes authority, starting the same set of applications and modifying the same data. An EVA. See also EVA and virtual array Terabytes. General term for an EVA. See also virtual disk Variable disk capacity that is defined and managed by the array controller and presentable to hosts as a disk. Volume size customization. See also CVS World Wide Name. A unique identifier assigned to a Fibre Channel device.

primary site quorum

RPM SCSI secondary site split-brain syndrome storage system TB virtual array virtual disk VSC WWN

32

Glossary

Index
A
AutoPass command line utility, 27 AutoPass license program, 27

H
HBA drivers Serviceguard, 22 help obtaining, 29 HP technical support, 29 HP SMI-S EVA Linux, 22 Windows, 10

C
cautions resource type DLL in MSCS, 13 clxautopass command line utility, 27

D
data backup requirements, 5 disk space requirement, 7 document related documentation, 29 documentation HP web site, 29 providing feedback, 30 DR groups creating, 11, 23

I
installation EVA Cluster Extension Linux, 24 Windows, 12 installation prerequisites MSCS, 9 Serviceguard, 21 instant-on license, 27

E
EVA Cluster Extension failover function, 6 installation Linux, 24 Windows, 12 internal database, 6 pre-installation requirements, 7 removing Linux, 25 Windows, 17 supported features, 8 supported versions, 8 upgrading Windows, 16 vdisks, 6

J
Java Runtime Environment MSCS, 10

L
licensing, 27 installing license keys, 27 registration tool (Windows 2008), 28 retrieving license keys, 27, 27

M
memory requirement, 7 MSCS installation, 12 multipath software MSCS, 10 Serviceguard, 22

F
failover, 6

N
network requirements, 5

EVA Cluster Extension Software installation guide

33

P
permanent license key, 27 pre-installation procedures MSCS, 9 create hosts, 11 DR groups, 11 EVA storage system, 10 HP SMI-S EVA, 10 installing MSCS, 12 IP network, 9 Java Runtime Environment, 10 multipath software, 10 SAN configuration, 9 vdisks, 11, 11 Serviceguard, 21 create hosts, 22 DR groups, 23 EVA storage system, 22 HBA drivers, 22 HP SMI-S EVA, 22 installing Serviceguard, 24 IP network, 21 Logical Volume Manager, 23 SAN configuration, 21 vdisks, 22, 23 pre-installation requirements, 7 data backup, 5 disk space and memory, 7 environment, 5 environmental setup, 7 network, 5

U
upgrading EVA Cluster Extension Windows, 16

V
vdisks, 6 creating, 11, 22 LUN presentation, 11, 23 presenting, 11, 22 setting read-only mode, 11, 23 versions supported software, 8

W
web sites HP , 30 HP Subscriber's Choice for Business, 29 product manuals, 29 Windows Server 2008 removing EVA Cluster Extension, 18

R
related documentation, 29 removing EVA Cluster Extension Linux, 25 Windows, 17 resource DLL registering manually, 15 Resource type registering manually, 15 retrieving license keys, 27

S
Subscriber's Choice, HP, 29

T
technical support HP, 29

34