HP 3PAR Cluster Extension Software Administrator Guide Abstract This guide contains detailed instructions for configuring and troubleshooting HP 3PAR Cluster Extension Software in Windows and Linux environments. The intended audience has independent knowledge of related software and of the HP 3PAR storage system and its software.
© 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.
Contents 1 HP 3PAR Cluster Extension features...............................................................7 Integration into cluster software (Graphical user interface)..............................................................7 CLI for easy integration..............................................................................................................7 Disaster tolerance through geographical dispersion.......................................................................
failover policy...............................................................................................................20 failback policy..............................................................................................................20 Configuration tool (clx3parconfig.exe) for Windows...............................................................20 HP 3PAR InForm Management Console or HP 3PAR InForm CLI ...............................................20 IP network considerations........
Timing considerations for Windows Clustering............................................................................42 Bouncing service or application................................................................................................43 Creating array password file....................................................................................................43 Administration..................................................................................................................
Sample configuration file.........................................................................................................72 5 CLI commands and utilities........................................................................73 CLI commands.......................................................................................................................73 clx3PARrun.......................................................................................................................
1 HP 3PAR Cluster Extension features HP 3PAR Cluster Extension offers protection against application downtime due to a fault, failure, or site disaster by extending a local cluster between data centers over metropolitan distance. HP 3PAR Cluster Extension reinstates critical applications at a remote site within minutes of an adverse event, integrating your open-system clustering software and HP 3PAR Remote Copy to automate failover and failback between sites.
Figure 1 Physical replication using HP 3PAR Remote Copy HP 3PAR Remote Copy-mirrored disks have a read/write-enabled primary (local) disk and a read-only secondary (remote) disk. Current cluster software products cannot distinguish between read-only and write-enabled disks, and cannot enable disk access if the disk is not write-enabled during the server boot process.
Fully Automatic Failover and Failback Automated failover and failback reduces the complexity involved in a disaster recovery situation. It is protection against the risk of downtime, whether planned or unplanned.
1-to-1 configuration When setting up a one-to-one configuration (see Figure 2 (page 10)), consider the following: • Cluster nodes are split between two or more geographically dispersed data center sites and use redundant, diversely routed network connections for intra-cluster communications. Those links must be as reliable as possible to prevent false failover operations or split-brain situations.
N-to-1 and 1-to-N configurations NOTE: The restrictions outlined in “1-to-1 configuration” (page 10) also apply to N-to-1 configurations. When setting up an N-to-1 or 1-to-N configuration (see Figure 3 (page 11)), consider the following: • HP 3PAR Cluster Extension uses the unit of Remote Copy volume groups as the failover unit. This means all virtual volumes or members of a Remote Copy volume group will be failed over if the cluster software moves disk access from one cluster node to another.
Figure 4 Relationship of primary versus secondary volume groups on primary and backup storage servers Remote Copy pairs Remote Copy configurations are based on the relationship between a storage system pair, also known as the Remote Copy pair. Within this pair, the primary storage system is the system that holds the volumes that are copied to a backup or secondary storage system, also known as a remote storage system.
Synchronous replication Using synchronous mode, all write requests from the server are first transferred to the remote storage system. After each I/O has been mirrored in the cache area of the remote storage system, it is acknowledged to the local storage system. The write request is then acknowledged to the server. User configuration file HP 3PAR Cluster Extension provides a user configuration file to customize failover behavior.
MNS or Node Majority quorum in Windows Clustering An MNS is a single quorum resource that allows you to build clusters with nodes that are geographically separated. In an MNS cluster, unlike in a quorum disk cluster, data is stored on multiple disks across the cluster. The MNS resource ensures that the cluster's configuration data is stored locally on the nodes and that it is kept consistent across the different disks.
NOTE: File Share Witness support: • Windows Server 2003 (Service Pack 1 and later) supports only two node clusters when using File Share Witness. • Windows Server 2003 Service Pack 2 supports MNS with File Share Witness by default. • When using Microsoft Windows Server 2003 Service Pack 1 (SP1)-based server cluster or Windows Server 2003 R2-based server cluster, you must apply a Microsoft patch to support MNS with File Share Witness. See your Microsoft documentation for more information.
There are three types of resource constraints: • Resource location: Defines the nodes on which a resource can run, cannot run, or is preferred to be run. • Resource colocation: Defines which resources can or cannot run together on a node. • Resource order: Defines the sequence of actions for resources running on a node. Resource operation attribute SLE HA does not monitor resource health by default. To enable this feature, add the monitor operation to the resource definition.
Disk monitoring For the situations in which disk access is lost or read/write protection is in effect due to storage fencing, application monitoring agents, file system agents, or LVM resource agents detect the IO failure. HP 3PAR Cluster Extension does not monitor the disk access status. RHCS cluster setup considerations Quorum In RHCS, the quorum is based on a simple voting majority of the defined nodes in a cluster. To re-form successfully, a majority of all possible votes is required.
A failover domain can have the following characteristics: • Unrestricted: Specifies that the subset of members is preferred, but the cluster service assigned to this domain can run on any available member. • Restricted: The cluster service is allowed to run only on a subset of failover domain members. • Unordered: The member on which the cluster service runs is chosen from the available list of failover domain members with no preference order.
HP Serviceguard for Linux cluster setup considerations Quorum In general, the algorithm for cluster re-formation requires a cluster quorum of a strict majority (that is, more than 50%) of the nodes previously running. Although a cluster quorum of more than 50% is generally required, exactly 50% of the previously running nodes may re-form as a new cluster provided that the other 50% of the previously running nodes do not re-form.
failover packages The failover package is the most common type of package. It runs on one node at a time. If a failure occurs, it can switch to another node listed in its configuration file. If switching is enabled for several nodes, the package manager will use the failover policy to determine where to start the package. HP 3PAR Cluster Extension supports only failover packages. failover policy It specifies how Serviceguard decides where to start the package, or restart it if it fails.
2 Configuring HP 3PAR Cluster Extension for Windows After installing HP 3PAR Cluster Extension, use the configuration tool to define the HP 3PAR Cluster Extension setup configuration. Use Cluster Administrator (Windows Server 2003), Failover Cluster Management (Windows Server 2008/2008 R2), or cluster commands in the CLI to add and configure resources. Integrating HP 3PAR Cluster Extension with MSCS To integrate HP 3PAR Cluster Extension with MSCS: 1.
Defining the HP 3PAR configuration information using the GUI To define configuration information using the GUI: 1. Open the configuration tool. For instructions, see “Starting the HP 3PAR Configuration Tool” (page 21) 2. 22 Click Add in the Array Configuration section to open the Add Array dialog box.
3. 4. 5. Enter the Array Network Name. Click Browse to select the password file. Click Connect to connect to the array. The array details (Array Name, Array Serial Number, Array Model, and Array ID) and the array target information appears on the Add Array dialog box. NOTE: If the Remote Copy link is down between the array and the defined targets, Cluster Extension will not be able to obtain the target array information. The value in the target array ID will be NA and a warning message is displayed.
NOTE: You must create or copy the array password file on all cluster nodes used by Cluster Extension. Ensure that the appropriate path is reflected in the configuration information of each node. During configuration, you will be prompted to confirm if you want to copy the configuration file on all cluster nodes. If you choose to copy the HP 3PAR Cluster Extension configuration file automatically, the same password file location is retained on all cluster nodes.
Exporting configuration settings using the GUI 1. Open the configuration tool. For instructions, see “Starting the HP 3PAR Configuration Tool” (page 21). 2. 3. 4. Click Export. When prompted, choose a save location, enter a file name, and then click Save. Click OK to save and close the configuration tool. Exporting configuration settings using the CLI 1. 2. Open a command window. Enter clx3PARconfig EXPORT /FILE=filepath, where filepath specifies the save location and file name.
See “Adding HP 3PAR Cluster Extension resource using the Microsoft CLI cluster commands” (page 26)for instructions. CAUTION: Do not use the following characters in Cluster Extension resource names: \ / : * ? " < > |. Using these characters might affect the creation of the resourcename.online file, which is used for the HP 3PAR Cluster Extension resource health check mechanism.
Configuring more than one resource in a service or application To create more than one HP 3PAR Cluster Extension resource in a service or application: 1. Create two (or more) Remote Copy volume groups and create a resource for each Remote Copy volume group. 2. Make every physical disk resource in the cluster service or application depend on both (all) resources within the cluster service or application.
When configuring HP 3PAR Cluster Extension resources, note the following: • If the Cluster Administrator or Failover Cluster Management GUI is used to configure a HP 3PAR Cluster Extension resource, configuring the resource using a user configuration file (UCF file) is not required. • HP 3PAR Cluster Extension creates a file called resource_name.online to indicate that the HP 3PAR resource is online on the local node.
Table 1 Setting resource properties and values in the GUI (continued) Property Format Description Value for a particular Remote CLI: 60000 milliseconds Copy volume (Default) group.Decreasing this value allows faster resource failure detection but also consumes more system resources. Set this value in the Advanced Policies tab of the resource properties window in Failover Cluster Management, or in the Advanced tab of the resource properties window in Cluster Administrator.
Table 1 Setting resource properties and values in the GUI (continued) Property Format If a resource fails, attempt Integer restart on current node – Period for restarts (Windows Server 2008/2008 R2) RestartPeriod (Windows Server 2003) RestartPeriod (CLI) Pending timeout (GUI) Integer PendingTimeout (CLI) Description Value Determines the amount of time for restart.
Table 2 Service or application properties and values Property Format Description Value GUI: Failback (Prevent failback or Allow failback) Integer Prevents automatic failback of a service or application to its primary system. Transfer the service or application back manually after the failure has been recovered. This allows recovery of all possible failure sources and pair resynchronization (if necessary) while the application service is still running.
Management for Windows Server 2008/2008 R2) or the standalone resource configuration utility in Server Core or Hyper-V Server. TIP: For information on managing HP 3PAR Cluster Extension resources from a remote management station through the MMC, see“Setting HP 3PAR Cluster Extension resource properties using the MMC ” (page 36) . Using Cluster Administrator to set resource properties (Windows Server 2003) To set resource properties for Windows Server 2003, use the Cluster Administrator GUI:. 1.
Using the resource configuration tool to set resource properties (Server Core and Hyper-V Server) To set resource properties for Server Core or Hyper-V Server, use the HP 3PAR Cluster Extension resource configuration tool. When using the resource configuration tool: • You must run the tool on a Server Core or Hyper-V cluster node. You cannot run the tool on a remote management station. • You cannot use the resource configuration tool to add or delete a resource.
b. c. d. 2. 3. 4. Select a cluster node from the Pre-Configured host list. Assign the cluster node to a data center selected from the Data center list. Click OK to save and close the window. To remove a cluster node, select the node, and then click Remove. To modify a cluster node, select the node, and then click Modify. Click Apply to finish your modifications and leave the window open, or OK to save your changes and close the Properties window.
2. 3. Select a volume group, and then click OK. Click Apply to finish your modifications and keep the window open, or click OK to save your changes and then close the Properties window. Changing Remote Copy volume group settings The cluster software resource configuration GUI and the resource configuration tool displays the Remote Copy volume group name, replication mode, and replication status.
6. 7. Click OK to save your changes and close the Advanced settings window. Click Apply to save your changes and leave the window open, or click OK to save your changes and close the Properties window. Configuring takeover actions Pre-executables and post-executables can be defined to be executed before or after HP 3PAR Cluster Extension invokes its takeover functions. Use the cluster software Parameters tab or the resource configuration tool to add or remove pre/post executable scripts. 1.
The following example sets the UseNonCurrentDataOk property for the resource clx_fileshare to NO: cluster resource clx_fileshare /privprop UseNonCurrentDataOk=NO For more information on the available properties, see “User configuration file and HP 3PAR Cluster Extension objects” (page 65).
3. 4. Click the Dependencies tab, and then click Modify. Add the resource to the Dependencies list. 5. Click OK to save your changes. Adding dependencies using Failover Cluster Management (Windows Server 2008/2008 R2) You can add dependencies with the GUI on a local node or by using the MMC to run the Failover Cluster Management application. 1. Open Failover Cluster Management. 2. Select a service or application that has HP 3PAR Cluster Extension resource. 3. Double-click a disk in the summary pane. 4.
Adding dependencies using the CLI The cluster commands in this section can be used with Windows Server 2003, Windows Server 2008/2008 R2, Server Core, or Hyper-V Server.
Figure 6 Resource tree for service or application CLX_SHARE HP 3PAR Cluster Extension is configured as a single resource to enable read/write access to the physical disk resource used for the CLX_SHARE cluster group. The physical disk resource depends on the HP 3PAR Cluster Extension resource and can be brought online only when the HP 3PAR Cluster Extension resource is already online.
C:\>cluster resource CLX_FILESHARE /prop 10. For Windows Server 2008/2008 R2 only: a. Click the Policies tab of the Failover Cluster Management Properties window. b. For the HP 3PAR Cluster Extension resource property response to resource failure, select If resource fails, do not restart. 11. Bring the service or application online on host3_DCB, and verify that the resource and all other CLX_SHARE service or application resources are brought online. 12.
When deleting resources: • For Windows Server 2008/2008 R2, use the GUI or CLI. • For Server Core or Hyper-V Server, use the CLI or the MMC. • For Windows Server 2003, use the GUI or CLI. For more information on deleting resources, see your Microsoft documentation. Using Hyper-V Live Migration with HP 3PAR Cluster Extension Live migration is a managed failover of VM resources.
In general, because the failover environment is dispersed into two (or more) data centers, the failover time cannot be expected to be the same as that in a single data center with a single shared disk device. Therefore, the following values of the HP 3PAR Cluster Extension resource and the service or application using that resource, must be adjusted, based on failover tests performed to verify the proper configuration setup: FailoverPeriod, RestartPeriod, PendingTimeout, LookAlive, and IsAlive.
Remote management of HP 3PAR Cluster Extension resources in a cluster You can use the MMC with Failover Cluster Management to manage clusters and configure HP 3PAR Cluster Extension resources.
Hyper-V Live Migration log entries In the HP 3PAR Cluster Extension log file (clxmscs.log), live migration messages include the prefix CLX_LM to help you differentiate live migration issues from HP 3PAR Cluster Extension log messages. For example: [10/12/09 20:13:02][2136][CLX_LM: CLXVMDISK04-App01][INFO] CLX detected that Live Migration for VM "Virtual Machine VM04" has begun.
3 Configuring HP 3PAR Cluster Extension for Linux HP 3PAR Cluster Extension supports integration with the following cluster software for Linux: • “Configuring HP 3PAR Cluster Extension with RHCS” (page 48) • “Configuring HP 3PAR Cluster Extension with SLE HA” (page 55) • “Configuring HP 3PAR Cluster Extension with HP Serviceguard on Linux” (page 58) NOTE: For a list of HP 3PAR Cluster Extension versions and the cluster software versions they support, see the HP SPOCK website: http://www.hp.
the LVM volume groups vgweb and vghtdocs are activated and the web server is started. The HP 3PAR Remote Copy volume group clxwebdrg includes all virtual volumes for the LVM volume groups vgweb and vghtdocs. The sample CLX3PAR.config file shows the contents of the configuration file with the described failover behavior. For SLE HA, the configuration file /etc/opt/hpclx3par/conf/CLX3PAR.config is associated with the SLE HA resource CLXWEB. SLE HA invokes the resource agent script /usr/lib/ocf/ resource.
failover operation to succeed at the destination site when the data at the destination site might not be current. On setting the value to No the resource will not come online at the destination site since the data might not be current. • The service (RHCS), package (HP Serviceguard), or resource group (SLE HA) is configured to wait for a volume group merge or full copy by setting the ApplicationStartup value to RESYNCWAIT.
The executable clx3PARlxcs is called by HP 3PAR Cluster Extension before volume group activation. This checks the status of a Remote Copy volume group associated with a volume group configured for use with an RHCS service. If necessary, HP 3PAR Cluster Extension takes appropriate actions to allow access to the volume group's physical disks before attempting to activate and mount the logical volume on a cluster node. Configuration overview 1. 2. Create an RHCS shared resource.
6. 7. 8. Select Script in the Select a Resource Type box. Enter CLX3PAR in the Name box. Enter /usr/share/cluster/clx3par.sh in the File (with path) box. 9. Click OK. 10. Select File > Save to save the configuration changes. The service configuration in /etc/cluster/cluster.conf is updated. 11. Click Send to Cluster to propagate the cluster configuration to the other cluster nodes.
5. Click Add a Service. The Add a Service page appears. 6. Enter the service name in the Service name box. IMPORTANT: The service name must match the name that is defined for the APPLICATION property in the HP 3PAR Cluster Extension configuration file CLX3PAR.config. 7. 8. 9. Select a failover domain. For information about the failover domain requirements, see Failover domains . Select Relocate for the recovery policy.
11. Click Submit. Conga saves the configuration information and updates all of the other cluster nodes. NOTE: To add additional resources to the service, use the Add a child feature. Using system-config-cluster to create a service To create a HP 3PAR Cluster Extension service using system-config-cluster: 1. Start the Cluster Configuration tool. 2. Click the Cluster Configuration tab. 3. Expand the Managed Resources tree. 4. Select Services. The Service properties page appears. 5. Click Create a Service.
7. Click Add a Shared Resource to this service. The Resource Configuration dialog box appears. 8. 9. Select CLX3PAR in the Select a Resource Type menu, and then click OK. To add additional resources to the service, select the HP 3PAR Cluster Extension resource and click Attach a new Private Resource to the Selection. Select the resource to be configured and provide the required resource agent parameters. 10. Click Close to close the Service Management window. 11.
3. In the configuration file (CLX3PAR.config), enter the appropriate values for: • DC_A_InServStorage_SerNum • DC_B_InServStorage_SerNum • RCVolumeGroupA • RCVolumeGroupB • DC_A_Hosts • DC_B_Hosts See “User configuration file” (page 65) for more information. For example: COMMON #LogLevel info APPLICATION CLXWEB #DC_A_InServStorage_SerNum 1302871 #DC_B_InServStorage_SerNum 1302835 #RCVolumeGroupA CLX_VG #RCVolumeGroupB CLX_VG.
c. d. Verify that the Remote Copy volume group is in source mode on the remote storage system. Stop the service and verify that the service stopped successfully. #clusvcadm –d CLXWEB 6. After verifying that the CLXWEB service can be moved with RHCS and that the software performs automatic failover of the Remote Copy volume group on each cluster node, start the service on its primary cluster node.
1. 2. 3. Create the configuration file. For instructions, see “Creating the HP 3PAR Cluster Extension configuration file” (page 56) Create a HP 3PAR Cluster Extension resource using the SLE HA GUI. Use the procedure for “Creating a HP 3PAR Cluster Extension resource for Pacemaker” (page 56) Test the configuration. For instructions, see “Testing the configuration” (page 58) Creating the HP 3PAR Cluster Extension configuration file Create the HP 3PAR Cluster Extension configuration file.
3. Add HP 3PAR Cluster Extension as a primitive group's first resource. NOTE: The resource hierarchy depends on the order in which resources are added. Always add HP 3PAR Cluster Extension resources as the first resource in a group. 4. 5. 6. 7. Select the following options for the HP 3PAR Cluster Extension resource: Name Value Class ocf Provider heartbeat Type CLX3PAR Configure the instance attributes for the resource by selecting the app parameter.
10. Set the operation defaults to control failover behavior. To specify that when a resource fails, the resources attempts to restart on the same node or another node in the cluster, use the following settings: Name Value requires nothing on-fail restart timeout 30 11. Set the migration-threshold value. This value defines the number of failures that can occur on a node before the node becomes ineligible to host the resource and the resource fails over to another node.
appropriate actions to allow access to the volume group's physical disks before attempting to activate and mount the logical volume on a cluster node. Information on the latest version of HP Serviceguard for Linux is available at http://www.hp.com/ info/sglx. For more information on cluster package configuration with HP Serviceguard for Linux, see Managing HP Serviceguard for Linux on the HP High Availability website http://docs.hp.com/ en/ha.html.
5. In the CLX configuration file (CLX3PAR.config), enter the appropriate values for: • DC_A_InServStorage_SerNum • DC_B_InServStorage_SerNum • RCVolumeGroupA • RCVolumeGroupB • DC_A_Hosts • DC_B_Hosts See “User configuration file” for more information. For example COMMON #LogLevel info APPLICATION CLXWEB #DC_A_InServStorage_SerNum 1302871 #DC_B_InServStorage_SerNum 1302835 #RCVolumeGroupA CLX_VG #RCVolumeGroupB CLX_VG.
12. After creating the mount points for the shared directories on all configured nodes, start the package on Host2. The volume groups will be imported automatically during the first package start on each system. #cmrunpkg –n Host2 CLXWEB 13. Transfer the package to the remote data center nodes and verify that the Remote Copy volume group is in destination mode on the remote storage system. 14.
cmrunpkg –v –n cluster_node package_name Where cluster_node is the name of the cluster node running the package, and package_name is the name of the package. The following commands enable and start the Serviceguard package, CLXWEB. #cmmodpkg –e -n Host1 CLXWEB #cmrunpkg –v –n Host1 CLXWEB Halting an HP Serviceguard for Linux package If there is a maintenance stop of the package, you must disable package switching.
fail to come online when the host OS does not detect the LU permission change. As a workaround, configure the HP 3PAR Cluster Extension script multipath_rescan.sh as a PostExecScript to rescan the disks before they are brought online. Configuring the rescan script The multipath rescan script is available in the directory /opt/hpclx3par/sample/ multipath_rescan.sh. To configure the script to run as a PostExecScript: 1. Copy the multipath_rescan.
brw-rw---- 1 root disk 253, 17 Nov 18 12:42 mpath18p1 3. Run the multipath -ll command to view the multipath device names and SCSI ID for your volume groups for Red Hat Enterprise Linux. [root@ Node1 ~]# multipath -ll mpath18 (350002ac0192e0f50) dm-9 3PARdata,VV [size=5.0G][features=0][hwhandler=0][rw] \_ round-robin 0 [prio=2][active] \_ 1:0:0:8 sdh 8:112 [active][ready] \_ 1:0:1:8 sdp 8:240 [active][ready] In the above example mpath18 needs to be put in the multipath_rescan.sh file.
4 User configuration file and HP 3PAR Cluster Extension objects Objects (also called properties in this document) define the HP 3PAR storage system environment and failover/failback behavior. You can customize HP 3PAR Cluster Extension objects in the user configuration file or in the cluster software. User configuration file For the CLI implementation of HP 3PAR Cluster Extension, the user configuration file UCF.cfg is used to configure application service-specific information. UCF.
string A name, which can include alphabetic and numeric characters and underscores; for example, an application startup value list A list of space-separated strings, for example, a list of host names (lists of numbers are stored as lists of strings) Text that is a comment starts with the pound (#) symbol and continues until the end of the line. Comments can start on a new line or be part of a line specifying an object.
COMMON objects The COMMON section is used to set the environment of HP 3PAR Cluster Extension. The COMMON tag can appear in the configuration file only once. The COMMON object does not require any value. Objects of the type COMMON can appear only one time. Those objects must be placed after the COMMON tag in the configuration file. If the default values fit your environment, there is no need to specify them in the file.
APPLICATION Format Tag Description Distinguishes between general and application-specific objects. Specify the name of the application service. The format of its value is equivalent to a string value. ApplicationDir Format String Description Specifies the directory where HP 3PAR Cluster Extension searches for application-specific files, such as the force flag or online file.
If the ApplicationStartup resource property is set to FASTFAILBACK, and the FailoverThreshold value is set to a number higher than the current number of clustered systems for the service or application, the service or application will restart on configured nodes until one of the following conditions is met: • The resource is brought online in the remote data center. • The resource failed because the FailoverThreshold value has been reached.
ClusterNotifyWaitTime Format Integer Description Specifies the amount of time that HP 3PAR Cluster Extension will monitor for VM live migration state changes. Default value 5 seconds DC_A_Hosts (Required) Format List Description This space-separated list defines the cluster nodes in data center A. DC_B_Hosts (Required) Format List Description This space-separated list defines the cluster nodes in data center B.
Valid values YES NO (default) PostExecScript (Optional) Format String Description Specifies an executable with its full path name to be invoked after the failover action or failover procedure. You can include environment variables in path names. Do not specify arguments to be passed to the executable. PreExecScript (Optional) Format String Description Specifies an executable with its full path name to be invoked before the failover action or failover procedure.
HP3PARCLICommandTimeout Format Integer Description Specifies timeout value (in seconds) for HP 3PAR storage system command execution. The timeout value is used whenever HP 3PAR Cluster Extension communicates with the HP 3PAR storage system. If the storage system is not responding within the configured timeout value, the command will time out and returns an error to the application. Default value 90 seconds Sample configuration file The following is a sample UCF.
5 CLI commands and utilities Using its CLI and command-line utilities, HP 3PAR Cluster Extension can be integrated with almost any cluster software for Windows operating systems.
Related information • clx3PARrun expects only the app_name parameter, which uniquely identifies an application service in the APPLICATION section of the user configuration file. • To force a Remote Copy volume group failover, use the –forceflag option. CAUTION: The forceflag option is an emergency switch used to manually activate your virtual volume.
Installing HP 3PAR InForm Command Line Interface (CLI) HP 3PAR Cluster Extension communicates with the HP 3PAR storage system using the HP 3PAR InForm Command Line Interface (CLI). Ensure that you install the supported version of HP 3PAR Command Line Interface (CLI) on a host where Clx3PARrun can be used. Creating and configuring the user configuration file The CLI expects as an argument the name configured as the APPLICATION tag value.
and the number of remote Copy volume groups managed by HP 3PAR storage systems, the online operation could time out. This can also happen if clx3PARrun is used in a script or called by another program or 3PAR storage system IP cannot be reached. • In the UCF.cfg file, if the ApplicationStartup attribute is set to RESYNCWAIT, HP 3PAR Cluster Extension tries to resynchronize virtual volumes and waits until the Remote Copy volume group is in a synced state.
7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. DC B host (server) names Replication mode Local replication role Remote replication role Remote copy link status Failsafe policy Remote Copy volume group status Remote Copy volume group virtual volume status AutoRecover Application directory path (ApplicationDir object) Log file location (LogDir object) Pre-executables and post-executables must supply a return code. The return code is used to determine whether a failover function is called.
CAUTION: Operating system scripts and/or batch files return 0 if the program was successfully executed. To return a different value, use the following line as the last statement in your pre- or post-executable: Windows batch file: exit /b exitcode.
6 Troubleshooting To troubleshoot problems with HP 3PAR Cluster Extension, one must understand HP 3PAR Remote Copy environments. See the Remote Copy User's Guide for more information on Remote Copy configuration and volume group states. See the HP 3PAR Cluster Extension log for any cluster specific information. However, it always keeps its own log files in its default log location.
Log facility The logging module of HP 3PAR Cluster Extension provides log messages to the cluster software as well as to the HP 3PAR Cluster Extension log file. The HP 3PAR Cluster Extension log file includes disk status information and is located by default in this directory: Windows %ProgramFiles%\Hewlett-Packard\Cluster Extension 3PAR\log\ Linux /var/opt/hpclx3par/log If you need to clear and reset the log file, for example to reduce disk space usage, archive the log file and then delete it.
Line 1: The process begins for a Cluster Extension resource CLX03 using HP 3PAR Cluster Extension version number 2.00.00. Line 2: Cluster Extension internal configuration file version. Line 3 - 5: The warning message for a temporary license. Line 6: The host name where a Cluster Extension resource is being brought online in the data center (A or B). Line 7: The remote data center nodes status. Line 8-28 : Configuration details of the Cluster Extension resource before failover.
Sample log file Line 1: The process begins for a Cluster Extension resource CLX03 using HP 3PAR Cluster Extension version number 2.00.00. Line 2: Cluster Extension internal configuration file version. Line 3 - 5: The warning message for a temporary license. Line 6: The host name where a Cluster Extension resource is being brought online in the data center (A or B). Line 7: The remote data center nodes status. Line 8-28 : Configuration details of the Cluster Extension resource before failover.
Line 33: Creating CLX_application_name.online file to check resource health. Line 34: End of the Cluster Extension execution process. HP 3PAR storage system log or sysmgr log A task, identified by task IDs is generated for each operation in the 3PAR storage system. Task manager commands provides information regarding the tasks in the system. For more information, see Managing Tasks section in HP 3PAR CLI Administrator’s Manual.
When HP 3PAR Cluster Extension is integrated into the cluster software, an error message string and integer value are displayed. For the CLI, a return code is displayed. For more information, see “CLI commands” (page 73). Log files Log files assist you in locating and identifying problems. Timestamps, component IDs, and message IDs are included. • HP 3PAR Cluster Extension-related messages are logged by MSCS to the file %ClusterLog% for Windows 2003.
Failover error handling Windows Cluster automatically fails over resource groups if the system where resource group is running on becomes unavailable. This is part of the cluster functionality. Also, this means that if a problem occurs with the HP 3PAR storage system, a resource group online process will be stopped. The behavior of HP 3PAR Cluster Extension is highly configurable.
Resource disk failure when HP 3PAR Cluster Extension is online In a cluster resource group, if the Cluster Extension resource is online but dependent disk resource is failing: • Ensure that the fibre channel connectivity between the servers and the storage systems is up and running. • Verify that the disk resource is dependent to the Cluster Extension resource.
NOTE: Host persona setting varies based on the Windows operating system installed on the cluster nodes, For more information, see the HP 3PAR Implementation Guide. no_fail_wrt_on_err settings The no_fail_wrt_on_err policy apply only to synchronous Remote Copy. The no_fail_wrt_on_err group policy (default policy) allows writes to a primary Remote Copy volume group even though the link between the systems in the Remote Copy pair is broken.
installed on the system. For the supported JRE version refer to Cluster Extension SPOCK. In case the GUI is not working due to environmental issues related to JRE, CLI can be used to perform the licensing specific operations like install and uninstall. The FC link is down (RHCS) In RHCS, the detection of a storage outage due to failure of all paths to the storage depends on the monitoring capability of resources configured in the RHCS service.
HP 3PAR Target arrays not configured with Remote Copy Links Sometimes CLX Configuration Tool is not able to add an array even through the password file exists and PATH variable is set properly for the HP 3PAR Inform CLI and you can execute HP 3PAR Inform CLI command locally. The root cause for this problem is that the HP 3PAR Inform CLI command showrcopy for this array does not show any target information (in case if target array is not configured).
7 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Typographic conventions Table 4 Document conventions Convention Element Blue text: Table 4 (page 91) Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
Glossary 3PAR Remote Copy A product that allows you to copy virtual volumes from one HP 3PAR storage system to another. CLI Command-line interface. An interface comprised of various commands which are used to control operating system responses. cluster A group of controller nodes connected via the same storage server backplane. The nodes in a cluster operate as a unified system, separate from any other clusters that may share the same service processor. CLX Cluster Extension.
Index Symbols 3PAR Cluster Extension components, 11 features, 7 integration, 7 3PAR Remote Copy support for 3PAR Cluster Extension, 11 volume groups, 12 A APPLICATION description, 67 ApplicationDir description, 68 ApplicationStartup description, 68 AutoFailbackType description, 31 B Basic Resource Health Check Interval description, 29 C CLI configuration, 7 ClusterNotifyCheckTime description, 69 UCF requirement, 37 ClusterNotifyWaitTime description, 70 UCF requirement, 37 clx3PARrun command, 73 command l
I R importing configuration information, 24 integration with cluster software, 7 IsAlivePollInterval description, 28 RCVolumeGroupA description, 70 RCVolumeGroupB description, 70 related documentation, 90 remote management, 28, 36 Windows Server 2008/2008 R2, 44 resources bringing online, 41 deleting for MSCS, 41 properties (CLI), 36 properties (UCF), 37 taking offline, 41 Response to resource failure description, 29 RestartAction description, 29 RestartPeriod description, 30 RestartThreshold description
DC_A_Hosts, 70 DC_B_Hosts, 70 FASTFAILBACK value, 69 PostExecCheck, 70 PostExecScript, 71 PreExecScript, 71 RCVolumeGroupA, 70 RCVolumeGroupB, 70 requirements, 13 RESYNCWAIT value, 69 ResyncWaitTimeout, 71 sample, 72 V volume groups, 12 W websites HP , 90 product manuals, 90 Windows Cluster changing resource names, 27 95
