HP 3PAR StoreServ Cluster Extension Software Installation Guide Abstract This guide contains detailed instructions for installing and removing HP 3PAR StoreServ Cluster Extension Software. The intended audience has independent knowledge of related software and of the HP 3PAR StoreServ Storage and its software.
© Copyright 2013 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.
Contents 1 Preparing to install HP 3PAR StoreServ Cluster Extension..................................5 Ideal environment.....................................................................................................................5 Network communication requirements.........................................................................................5 Storage replication link requirements...........................................................................................
Applying Device based permanent license keys in clustered environment...................................25 Applying Device based permanent license keys in non-clustered environment.............................26 Removing license key..............................................................................................................27 4 Support and other resources......................................................................28 Contacting HP...................................................
1 Preparing to install HP 3PAR StoreServ 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 a pair of HP 3PAR StoreServ Storage with Remote Copy configuration.
How HP 3PAR StoreServ Cluster Extension Software interacts with its environment This section describes the ways in which HP 3PAR StoreServ Cluster Extension interacts with its environment. Failover function HP 3PAR StoreServ Cluster Extension Software requires cluster software to automatically fail over among systems on a local site or between sites.
Disk space and system memory requirements • 50 MB for the HP 3PAR StoreServ Cluster Extension installation directory (%ProgramFiles%\ Hewlett- Packard\Cluster Extension 3PAR) • At least 25 MB of system memory Required firmware and software For specific firmware and software versions, see the HP SPOCK website: http://www.hp.com/ storage/spock.
2 Installing HP 3PAR StoreServ Cluster Extension Software This chapter describes the installation of HP 3PAR StoreServ Cluster Extension Software in Microsoft clustering environments with HP 3PAR StoreServ Storage. NOTE: • You can install, uninstall, modify, and repair HP 3PAR StoreServ Cluster Extension on all of the nodes in a cluster by running the installer from one node in the cluster.
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 array-based data replication. See the HP StorageWorks SAN Design Reference Guide and the HP 3PAR Remote Copy Users Guide for supported SAN extension configuration and instructions on setting up your HP 3PAR Remote Copy environment.
HP recommends that you run HP 3PAR Host Explorer software on hosts connected to HP 3PAR StoreServ Storage. When a host is created on a HP 3PAR StoreServ Storage, unassigned WWNs are presented to the storage system. If the Host Explorer agents are not running on the attached hosts, the storage system cannot determine the WWNs assigned to the hosts, and you must manually assign each WWN to a host.
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. Enable Microsoft Failover Cluster feature on all nodes and create the failover cluster using the nodes. NOTE: For Windows Server 2012, Failover Cluster Command Interface feature (cluster.exe) is not installed by default when Failover Cluster feature is enabled.
3. 4. Run the installer by doing one of the following: • Double-click the HP 3PAR StoreServ Cluster Extension installation package. • Run the HP 3PAR StoreServ Cluster Extension installation package from the command prompt. This option is used for Server Core or Hyper-V Server installation. See Microsoft documentation for more information on installing applications in a Server Core or Hyper-V Server environment.
7. 8. Accept the default location, or click Browse and specify a new destination. 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.
HP 3PAR StoreServ Cluster Extension maintenance Modifying the 3PAR StoreServ Cluster Extension installation Once 3PAR StoreServ Cluster Extension is installed, you can modify the installation by adding or removing components. 1. Start the 3PAR StoreServ Cluster Extension InstallShield wizard: a. Depending on your version of Windows, do one of the following: b. • Select Start→Control Panel→Programs and Features.
2. Start the 3PAR StoreServ Cluster Extension InstallShield wizard: a. Depending on your version of Windows, do one of the following: b. • Select Start→Control Panel→Programs and Features. • For Server Core or Hyper-V Server: Run the 3PAR StoreServ Cluster Extension installation package from the command line. Continue to Step 3. Select HP 3PAR StoreServ Cluster Extension . Click Uninstall/Change. The InstallShield maintenance window appears. 3. Select Remove, and then click Next.
NOTE: If the .result file is not found on the remote cluster node, run the HP 3PAR StoreServ 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) using task manager, or reboot the node and rerun the HP 3PAR StoreServ Cluster Extension setup locally.
Table 1 Windows remote installation error codes (continued) ERROR code Description Corrective action ERROR_INVALID_HANDLE Setup failed on the local cluster node. Run the setup on the local cluster node. Internal Error. Could not invoke the DLL. SILENT_INPUT_FILE_CORRUPTED Setup failed on the local cluster node. Run the setup on the local cluster node. The silent input file is corrupted or could not be found. LOCAL_NODE_NAME_NOT_FOUND Setup failed on the local cluster node.
Table 1 Windows remote installation error codes (continued) ERROR code Description Corrective action ERROR_AUTOPASS_REMOVAL_FAILED Uninstall completed on the local cluster Make sure msiexec.exe can be node. executed, and then run the HP 3PAR StoreServ Cluster Extension setup on Setup was unable to run the the local cluster node. msiexec.exe command. ERROR_RESOURCE_STATE_UNKNOWN Uninstall failed on the local cluster node. Run the setup on the local cluster node.
Table 1 Windows remote installation error codes (continued) ERROR code Description Corrective action type Cluster Extension 3PAR for VM Management. For more information, see “Registering the resource type and resource extension DLL manually” (page 19) ERROR_3PAR_VMMGMT_CMDLET_REGISTER_FAILED Installation completed on cluster node. Register the CLX Cmdlet DLL. For more Setup was unable to register CLX 3PAR information, see “Registering the CLX Cmdlets DLL.
PowerShell Cmdlets can also be used to perform the above steps. To check if the resource extension DLL is registered, run the following command: (Get-ClusterResourceType "Cluster Extension 3PAR").AdminExtensions If the resource extension DLL is registered, the output will show the GUID of the admin extension as shown {C977EFB9-B640-4E6C-9473-ECE586EC2074} If resource extension DLL is not registered 1. Run the command regsvr32 c:\windows\system32\clx3parmscsex.dll. Run this command on all the cluster nodes.
If the Cmdlet is not registered, then you have to manually register the Cmdlet DLL using the following command from the CLX product bin directory: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe CLX3PARCmdlets.dll Unregistering the CLX PowerShell Cmdlet DLL manually [Windows Server 2012 only] If a problem occurs during uninstallation, execute the following commands from the command line on all the cluster nodes to unregister the PowerShell Cmdlets DLL. Check if Cmdlet is registered or not.
Upgrading from HP 3PAR Cluster Extension 3.0X.00 (Windows Server 2012) IMPORTANT: Before starting the upgrade procedure, save the HP 3PAR StoreServ Cluster Extension configuration file, if it exists. You can save the file by using the Export feature in the HP 3PAR StoreServ Cluster Extension configuration tool. For instructions on saving the file, see the HP 3PAR StoreServ Cluster Extension Administrator Guide.
configuration. If you choose this step, then you must follow this procedure for every array on all the failover cluster nodes. Configuring CLX after upgrading to 3.02.
3 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.
of hosts to which the storage devices are connected. For example, if the failover Cluster has [Nh] number of nodes that have CLX software installed and connected to [Na] number of storage devices, you must procure only [Na] number of device based permanent licenses – one for each storage device. Using a particular CLX utility, you can import these licenses in all the nodes of the cluster at once.
that, if you run this tool from any one of the cluster nodes with the following option, permanent license in all other cluster nodes will be imported automatically. Usage: ClxDeviceLicenseRegistration[.exe] {[-f >] | [-s ]} [. . .] Options: • -f : Import the device based permanent licenses using multiple license files.
Removing license key 1. Start AutoPass, located in the product's bin directory: clxautopass -ovlicensemgr 2. 3. Click Remove License Key. Select any installed license key, and then click Remove.
4 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Typographic conventions Table 2 Document conventions Convention Element Blue text: Table 2 (page 29) Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
Glossary CLI Command-line interface. An interface comprised of various commands which are used to control operating system responses. DLL Dynamic-link library. failover A role-reversal process where the backup Remote Copy volume group is converted to the primary Remote Copy volume group. FC Fibre Channel. A network technology primarily used for storage networks. GUI Graphical User Interface.
Index registration tool (Windows Server 2008/2008 R2/ 2012), 25 removing license key, 27 retrieving license keys, 24 A adding LUN presentations, 10 AutoPass command-line utility, 25 AutoPass license program, 24 C clxautopass command-line utility, 25 Configuring HP 3PAR StoreServ Storage, 9 contacting HP, 28 conventions document, 29 text symbols, 29 creating virtual volumes, 10 volume groups, 10 creating hosts, 9 D document conventions, 29 related information, 28 documentation HP website, 28 H help obtai
