HP 3PAR StoreServ Cluster Extension Software Administrator Guide Abstract This guide contains detailed instructions for configuring and troubleshooting HP 3PAR StoreServ Cluster Extension Software in Microsoft Windows environments. 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 HP 3PAR StoreServ Cluster Extension features.................................................6 Integration into cluster software (Graphical User Interface).............................................................6 CLI for easy integration..............................................................................................................6 Disaster tolerance through geographical dispersion.......................................................................
Configuring HP 3PAR StoreServ Cluster Extension resources..........................................................30 Setting Microsoft cluster-specific resource and service or application properties...............................31 Setting HP 3PAR StoreServ Cluster Extension-specific resource properties........................................34 Setting HP 3PAR StoreServ Cluster Extension resource properties using the GUI..........................
Restrictions for customized implementations...........................................................................65 Cluster Extension Cmdlets for CSV and Virtual Machine Management...........................................65 Pre-execution and post-execution programs................................................................................74 Pre-execution return codes...................................................................................................75 Post-execution return codes..
1 HP 3PAR StoreServ Cluster Extension features HP 3PAR StoreServ 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 StoreServ 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.
Figure 2 1-to-1 configuration N-to-1 and 1-to-N configurations NOTE: The restrictions outlined in “1-to-1 configuration” (page 9) 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: 10 • HP 3PAR StoreServ Cluster Extension uses the unit of Remote Copy volume groups as the failover unit.
Figure 3 N-to-1 and 1-to-N configuration Processes and components For Windows Clustering (MSFC), HP 3PAR StoreServ Cluster Extension is shipped as a resource DLL. The installation of HP 3PAR StoreServ Cluster Extension also includes a CLI for custom HP 3PAR Remote Copy integration. Customized solutions for failover application services must implement HP 3PAR StoreServ Cluster Extension through the CLX CLI (clx3PARrun.exe) prior to the disk activation procedure on the server.
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 StoreServ Cluster Extension provides a user configuration file to customize failover behavior.
Node Majority quorum in Windows Clustering The Node Majority resource ensures that the cluster's configuration data is stored locally on the nodes and that it is kept consistent across the different disks. This allows cluster topologies where the nodes do not need shared access to a quorum disk. (Number of nodes in the cluster/2) +1 This ensures that more than 50% of the nodes will have an up-to-date copy of the configuration information.
Cluster Shared Volume for Windows Server 2012 Cluster Shared Volume is a feature of Microsoft Failover Cluster which allows all nodes in the cluster with the ability to directly access the same volume without changing ownership of the disk resource. The result of the feature is that all nodes in a cluster can use the same volume to host actively running Virtual Machines at the same time. CSV manages storage access differently than regular clustered disks.
3PAR StoreServ Cluster Extension supports CSV disk on Windows Server 2012 in addition to non CSV disk support. Configuration of CSV disk for CLX is similar to configuration of normal disk for CLX support. Since the CSV role is hidden and not seen in Failover Cluster GUI, CLX has provided PowerShell Cmdlets to configure Cluster Extension 3PAR resource for the CSV disk. See “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 65) on how to configure CSV disk for CLX.
2 Configuring HP 3PAR StoreServ Cluster Extension After installing HP 3PAR StoreServ Cluster Extension, use the configuration tool to define the HP 3PAR StoreServ Cluster Extension setup configuration. Use Failover Cluster Management (Windows Server 2008/2008 R2/2012), or cluster commands in the CLI or Microsoft Failover Cluster PowerShell Cmdlets to add and configure resources.
Configuring HP 3PAR StoreServ Cluster Extension After installation, you must define the configuration setup using the HP 3PAR StoreServ Cluster Extension Configuration Tool. You can configure HP 3PAR StoreServ Cluster Extension with the GUI or the CLI. Use the following instructions for the GUI. For instructions on performing HP 3PAR StoreServ Cluster Extension configuration tasks with the CLI, see “Defining the HP 3PAR StoreServ configuration information using the GUI” (page 19).
To start the HP 3PAR StoreServ Cluster Extension configuration tool: • For Windows Server 2008/2008 R2: Double-click the HP 3PAR StoreServ CLX Configuration Tool icon on the desktop, or select Start→All Programs→Hewlett-Packard→HP 3PAR StoreServ Cluster Extension Software→HP 3PAR StoreServ Cluster Extension Configuration Tool.
3. 4. Enter the Array Network Name. If you have a password file, click Browse to select the password file and navigate to Step 5. If you don’t have a password file, select I don’t have a password file radio button and click Generate to open HP 3PAR StoreServ password file generator dialog box.
Provide the required information and click Generate to generate a new HP 3PAR StoreServ password file for the given array. • User: HP 3PAR user • Password: HP 3PAR password for the given user. • Password file name: The name of the password file that will be generated on clicking Generate button. This is an optional parameter; the default value will be _.pwd. • Password file path: The windows directory where the HP 3PAR StoreServ password file needs to be created.
If an array certificate that you are trying to cache as an exception file has already expired, then CLX will not allow you to add the array certificate as an exception. This behavior is shown in the following figure. As a result, the password file is not generated. 5. Click Connect to connect to the array. If the array certificate is not cached as an exception file, then the Connect operation prompts you to add the certificate as an exception as described in the previous step.
8. Select the servers that are possible owners of the HP 3PAR StoreServ Cluster Extension-managed disks, and click OK. NOTE: See the Microsoft Windows Clustering documentation for more information about possible owners.
9. Click OK. You will be prompted to confirm if you want to automatically copy the configuration file on all the cluster nodes used by Cluster Extension. 1. If you select Yes, the configuration information is automatically copied to all cluster nodes used by Cluster Extension. 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.
If the location of the exception file is same across all the failover cluster nodes, then save the CLX configuration data for all the CLX nodes. However, if the location of the exception file is not same across all the failover cluster nodes, then save the CLX configuration data on the local node only. • To verify the connectivity between array and cluster nodes, select one or more configured HP 3PAR StoreServ Storage and click Connection Test.
Importing configuration settings using the CLI 1. 2. Open a command window. Enter clx3PARconfig IMPORT /FILE=filepath, where filepath specifies the file location and name. Importing CLX configuration prior to version 3.02.00 If TPDNOCERTPROMPT environment variable is set, then remove the TPDNOCERTPROMPT environment variable before starting HP 3PAR StoreServ Cluster Extension configuration tool. Once the CLX configuration is complete, you can set the TPDNOCERTPROMPT environment variable again.
4. Click Connect. If the certificate is not currently cached in the failover cluster node, then you are prompted to save the exception file as shown.
You must perform these steps for all the arrays that are configured. NOTE: The exception file is not copied to all the failover cluster nodes irrespective of whether you select Yes or No. You must generate the exception file in every failover cluster node. The same Windows user must login to all the failover cluster nodes and cache the certificate on all the failover cluster nodes. The location of the exception file must be same for all the CLX configured arrays.
◦ Cluster commands in CLX nodes ◦ Microsoft Failover Cluster PowerShell Cmdlets. For Server Core or Hyper-V Server also, cluster commands and PowerShell Cmdlets can be used as mentioned in the first bullet. 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 StoreServ Cluster Extension resource health check mechanism.
Example: This command adds an HP 3PAR StoreServ Cluster Extension resource called clx_fileshare to the CLX_SHARE service or application. Add-ClusterResource -Name "clx_fileshare" -Group “CLX_SHARE” -ResourceType "Cluster Extension 3PAR" Configuring more than one resource in a service or application To create more than one HP 3PAR StoreServ 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.
directory specified by the ApplicationDir resource property. If the resource is taken offline, this file is deleted. • Windows Server 2008 only: If a HP 3PAR StoreServ Cluster Extension resource is not configured, the resource icon in the Failover Cluster Management GUI shows the message not configured next to the resource status. • The HP 3PAR StoreServ Cluster Extension resource must be the first resource for all other disk resources.
Table 1 Setting resource properties and values in the GUI Property Format Description Thorough Resource Health Check Interval ) Integer Used to poll “Alive” state for GUI: 01:00 mm:ss (Default) the resource. Also used by CLI: 60000 milliseconds HP 3PAR StoreServ Cluster (Default) Extension to perform HP 3PAR Remote Copy start operations if auto_recover policy is set for a particular Remote Copy volume group.
Table 1 Setting resource properties and values in the GUI (continued) Property Format Description Value Windows Clustering (MSFC)” (page 48). Set this value in the Policies tab of the resource properties window in Failover Cluster Management. HP 3PAR StoreServ Cluster Extension requirements for service or application properties are described in Table 2 (page 33). If no specific value is required, the default value is listed.
Table 2 Service or application properties and values (continued) Property Format Description Value If this value is set to a number higher than the current number of clustered systems for the cluster group, the service or application will continue to restart until either the FailoverThreshold value or the FailoverPeriod timeout value is reached. Setting HP 3PAR StoreServ Cluster Extension-specific resource properties Changes to resource properties take effect when the resource is brought online again.
4. Make the necessary parameter changes, and then click OK. Using Failover Cluster Management to set resource properties of a CLX resource on which a CSV disk is dependant (Windows Server 2012) In case of a CSV disk, it is possible to create a CLX resource in the CSV group and make CSV disk dependent on the CLX resource. After creating the CLX resource in the CSV group, the CLX resource does not appear in the Windows Server 2012 Failover Cluster Manager GUI.
4. Make the necessary parameter changes, and then click OK. NOTE: HP 3PAR StoreServ CLX Settings tab in the properties window of a CSV disk is visible only if that CSV disk is dependant on a "Cluster Extension 3PAR" resource. Alternatively, you can also use HP 3PAR StoreServ Resource Configuration Tool (Clx3PARResConfig.exe) to configure the CLX resource on which the CSV is dependent.
1. 2. 3. Open a command window and enter CLX3PARRESCONFIG.EXE. Select the resource you want to change in the 3PAR CLX resource menu. Make the necessary parameter changes, and then click OK. NOTE: In Server Core and Hyper V Server, you can only use the CLX3PARRESCONFIG.EXE as the GUI is not present. Configuring cluster node data center assignments To configure cluster node data center assignments from the cluster software Parameters tab or the resource configuration tool: 1. To add a cluster node: a.
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 click OK to save your changes and close the Properties window.
Selecting a volume group Use the cluster software Parameters tab or the resource configuration tool to select the Remote Copy volume group containing the disk that will be managed by the HP 3PAR StoreServ Cluster Extension resource. 1. Click Browse. 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.
Use this dialog box to configure the Remote Copy volume group behavior. 2. 3. • The settings in the Replication link up scenario section affect the failover behavior when the HP 3PAR Remote Copy link is up. • The settings in the Replication link down scenario section affect the failover behavior when the HP 3PAR Remote Copy link is down. Select RESYNCWAIT or FASTFAILBACK for the ApplicationStartup behavior. If you selected RESYNCWAIT in Step 2, set the RESYNCWAIT timeout value. • 4. 5. 6. 7.
see “Remote management of HP 3PAR StoreServ Cluster Extension resources in a cluster” (page 49) and your Microsoft documentation. Setting HP 3PAR StoreServ Cluster Extension resource properties using the CLI The cluster commands in this section can be used with Windows server core and non server core environments. The Windows cluster default properties for a resource can be changed using the following command: cluster resource /privprop [
• ClusterNotifyWaitTime • StatusRefreshTime • HP3PARCLICommandTimeout • HP3PARCLIRetryCount IMPORTANT: If you plan to use the default values for these properties, no UCF is required. To configure properties using a UCF: 1. Take the HP 3PAR StoreServ Cluster Extension resource offline. 2. Open the sample UCF.cfg file located in %ProgramFiles%\Hewlett-Packard\Cluster Extension 3PAR\sample. 3. Update the file with the property values you want to use.
6. Click OK to add the selected dependency. Adding dependencies using the CLI The cluster commands in this section can be used with Server Core or Hyper-V Server.
Configuration of HP 3PAR StoreServ CLX for CSV disk on Windows Server 2012 Configuration of CLX resource for the CSV disk is a two steps process. This is almost similar to the configuration of CLX for non CSV disk. • Creation of CLX resource in the CSV Role CSV disk resides in its own role in the Failover Cluster. CSV disk is visible in the Failover Cluster Manager GUI but the role in which the CSV disk resides is not visible.
Figure 5 Service or application example Figure 6 Resource tree for service or application CLX_SHARE HP 3PAR StoreServ 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 StoreServ Cluster Extension resource and can be brought online only when the HP 3PAR StoreServ Cluster Extension resource is already online.
1. 2. 3. 4. 5. 6. 7. 8. Log in to the host3_DCB system with the Administrator account. Create the file share service or application with all previously mentioned resources and its dependencies, except the HP 3PAR StoreServ Cluster Extension resource on host3_DCB. Create a new resource of type HP 3PAR StoreServ Cluster Extension and add systems host2_DCA, host3_DCB and host4_DCB to its possible owners.
To bring resources online: • Use Failover Cluster GUI or Cluster CLI or Microsoft PowerShell Cmdlets. • For Server Core or Hyper-V Server, use the CLI or the MMC or Microsoft PowerShell Cmdlets. For more information on using this command, see your Microsoft documentation. Taking a resource offline Resources are usually taken offline automatically when the service or application is taken offline. Taking a resource offline causes resources that depend on that resource to go offline.
Using Hyper-V Live Migration with HP 3PAR StoreServ Cluster Extension Live migration is a managed failover of VM resources. Live migration should be performed when all of the solution constituents are in a healthy state, all the servers and systems are running, and all the links are up. Ensure that the underlying infrastructure is in a healthy state before performing live migration.
PendingTimeout value. Microsoft Cluster provides two properties to adjust state change recognition or resolution: • IsAlive • LookAlive NOTE: For Windows Server 2008/2008 R2/2012, the IsAlive and LookAlive properties are replaced by the Thorough Resource Health Check Interval and Basic Resource Health Check Interval properties.
about the Parameters tab, see “Setting HP 3PAR StoreServ Cluster Extension resource properties using the MMC ” (page 40). • When you install HP 3PAR StoreServ Cluster Extension into a Windows Server 2008/2008 R2/2012 environment, the resource extension DLL is registered by default, which prevents you from configuring a HP 3PAR StoreServ Cluster Extension resource from a remote management station.
TIP: Archive the log files before deleting them. Hyper-V Live Migration log entries In the HP 3PAR StoreServ Cluster Extension log file (clxmscs.log), live migration messages include the prefix CLX_LM to help you differentiate live migration issues from HP 3PAR StoreServ 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.
2. 3. 4. 5. To create a Cluster Extension 3PAR cluster resource in the hidden CSV role, CLX has provided PowerShell Cmdlet to perform the required operation. For more information, see “Cluster Extension Cmdlets for CSV and Virtual Machine Management” (page 65) Once the Cluster Extension 3PAR resource is created in the CSV role, configure the CLX Resource private properties.
3. The cluster node which owns the CSV disk fails or the CSV disk fails and the CSV disk moves to a node in the same datacenter or CSV disk is moved manually to a node in the same datacenter: In this scenario, since the CSV disk is moved to a node in the same datacenter, all the VMs continue to run on their respective cluster nodes. There will not be any change in the ownership for the VMs. 4.
3 User configuration file and HP 3PAR StoreServ Cluster Extension objects Objects (also called properties in this document) define the HP 3PAR StoreServ Storage environment and failover/failback behavior. You can customize HP 3PAR StoreServ Cluster Extension objects in the user configuration file or in the cluster software. User configuration file For the CLI implementation of HP 3PAR StoreServ Cluster Extension, the user configuration file UCF.
Specifying object values You do not need to change the default settings unless you want to change the degree of protection for your Remote Copy volume group members. If you change an object, you may need to change additional objects as well. For example, if RESYNCWAIT has been specified for the ApplicationStartup object, the ResyncWaitTimeout object must be specified. Objects are supported according to the requirements or capabilities of the cluster software, as indicated in Table 3 (page 55).
If the default values fit your environment, there is no need to specify them in the file. COMMON Format Tag Description Distinguishes between general (common) and application-specific objects. LogDir Format String Description (Optional) Defines the path to the HP 3PAR StoreServ Cluster Extension log file. Default value %ProgramFiles%\Hewlett-Packard\Cluster Extension 3PAR\log LogLevel Format String Description (Optional) Defines the logging level used by HP 3PAR StoreServ Cluster Extension.
The APPLICATION object requires the name of the application service as its value. The objects specified after an APPLICATION tag must appear only once per application. As with COMMON objects, APPLICATION objects have predefined default values. HP 3PAR StoreServ Cluster Extension uses the following rules to define objects: • If you use the default value, you do not need to specify the object.
If a resynchronization is ordered, HP 3PAR StoreServ Cluster Extension monitors the progress of the copy process. If the application service was running on a secondary HP 3PAR StoreServ Storage without a replication link, a large number of records may need to be copied. If the copy process takes longer than the configured application startup timeout value, the application startup will fail.
Description Specifies how often HP 3PAR StoreServ Cluster Extension will check for VM live migration state changes. Default value 10 seconds ClusterNotifyWaitTime Format Integer Description Specifies the amount of time that HP 3PAR StoreServ 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.
procedure. That information will be passed to the post-executable. In case of a remote data center failure, it could be time consuming to gather that information, especially if your post-executable does not need any Remote Copy volume group status information. The arguments passed to the post-executable will include only the local disk status if the PostExecCheck object is set to NO.
If a HP 3PAR Remote Copy link goes down, and the resource is moved to the remote data center: Valid values • Setting this value to YES means that, regardless of whether or not the data is current in the remote data center, the resource will come online. • Setting this value to NO means that the resource will not come online on the remote data center since data might not be current.
4 CLI commands and utilities Using its CLI and command-line utilities, HP 3PAR StoreServ Cluster Extension can be integrated with almost any cluster software.
# clx3PARrun -forceflag my-exchange 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.
For detailed procedures, see the HP 3PAR InForm Management Console User Guide or the HP 3PAR InForm CLI Administrator’s Manual. Installing HP 3PAR Command Line Interface (CLI) HP 3PAR StoreServ Cluster Extension communicates with the HP 3PAR StoreServ Storage using the HP 3PAR 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.
HP 3PAR StoreServ Storage and the settings in the UCF.cfg file, you must evaluate the following considerations: • HP 3PAR StoreServ Cluster Extension uses HP 3PAR Command Line Interface (CLI) to communicate with the HP 3PAR StoreServ Storage, depending on the settings of HP 3PAR command timeout property, and the number of Remote Copy volume groups managed by HP 3PAR StoreServ Storage, the online operation could time out.
Another way to unload the CLX PowerShell Snap-In is to run the PowerShell script RemoveClx3PARCmdletsSnapIn.ps1 located at \bin directory. NAME: Add-CSVDependencyOnCLX3PAR SYNOPSIS: Adds a cluster resource of type "Cluster Extension 3PAR" to the list of resources and makes the given cluster shared volume dependent on this cluster resource (CLX resource), using AND as the connector, within a Failover Cluster. Existing dependencies will remain in the list.
Does not accept input objects. OUTPUTS: Does not return object. NOTES: CSV resource has to be offline while trying to add the dependency. The Confirm parameter and the Force switch parameter are provided. The cmdlet performs the operations irrespective of the storage array type of CSV. Online help for the cmdlet is not supported. Example 1 C:\PS>Add-CSVDependencyOnCLX3PAR This command first finds out all the cluster shared volumes in the cluster.
Created the resource "CLX_3PAR_Cluster Disk 2" in CSV Owner Group: "0f145465-1186-4bbb-b9e2-2fde4cb1127d" Added the dependency of CSV: "Cluster Disk 2" on "Cluster Extension 3PAR" type resource: "CLX_3PAR_Cluster Disk 2" Resource of type "Cluster Extension 3PAR" to be created with Name: "CLX_3PAR_Cluster Disk 3" in CSV Owner Group: "a71654bf-6c77-42c1-95dd-025ea8c4f225" Created the resource "CLX_3PAR_Cluster Disk 3" in CSV Owner Group: "a71654bf-6c77-42c1-95dd-025ea8c4f225" Added the dependency of CSV: "Clu
"Cluster Extension 3PAR" type resource. If it is not present, a new resource of type "Cluster Extension 3PAR" is created and CSV resource is made dependent on it. While creating the dependency, CSV resource should be offline, else dependency is not created. PS C:> Add-CSVDependencyOnCLX3PAR -CSVDiskName "Cluster Disk 1" Logs will be generated with default "info" log level. For changing the logging level, configure LogLevel parameter in UCF.
"Virtual Machine Configuration" resource is already dependent on the CLX resource, the cmdlet moves to the next VM configuration on a CSV. In the absence of dependency on the existing CLX resource the cmdlet creates a dependency of "Virtual Machine Configuration" resource in the VM role on resource of type "Cluster Extension 3PAR for VM Management".
If virtual machine configuration is already dependent on "Cluster Extension 3PAR for VM Management", then the cmdlet moves to the next virtual machine configuration on a CSV. However if there is no existing dependency on "Cluster Extension 3PAR for VM Management" but resource of this type is already existing in the VM role, virtual machine configuration resource is made dependent on the existing "Cluster Extension 3PAR for VM Management" type resource.
cluster shared volume, it tries to make each virtual machine configuration resource dependent on resource of type "Cluster Extension 3PAR for VM Management". If virtual machine configuration is already dependent on "Cluster Extension 3PAR for VM Management", then the cmdlet moves to the next virtual machine configuration on the provided CSV.
SYNOPSIS: Gets the list of virtual machines which reside on a cluster shared volume. SYNTAX: Get-VMOnClusterSharedVolumeListForCLX3PAR [-CSVDiskName [] DESCRIPTION: This cmdlet tries to get the list of all virtual machines which reside on a CSV. If the CSV name is specified, then the virtual machines which reside on that particular CSV are only listed.
Total virtual machines in the cluster on cluster shared volumes: 1 Total virtual machines in the cluster: 1 Example 2 C:\PS>Get-VMOnClusterSharedVolumeListForCLX3PAR -CSVDiskName "Cluster Disk 1" In this example, the cmdlet lists all the virtual machines which reside on CSV "Cluster Disk 1" PS C:\> Get-VMOnClusterSharedVolumeListForCLX3PAR -CSVDiskName "Cluster Disk 1" Cmdlet Log Location: C:\Program Files\Hewlett-Packard\Cluster Extension 3PAR\log\CLXCmdlet.
14. 15. 16. 17. 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. Pre-execution return codes Pre-execution return code Text Description 0 PRE_OK_TAKEOVER Pre-executable OK and failover action allowed.
5 Troubleshooting To troubleshoot problems with HP 3PAR StoreServ 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 StoreServ Cluster Extension log for any cluster specific information. However, it always keeps its own log files in its default log location.
HP 3PAR StoreServ Cluster Extension logs The logging module of HP 3PAR StoreServ Cluster Extension provides log messages to the cluster software and to the HP 3PAR StoreServ Cluster Extension log file. The HP 3PAR StoreServ Cluster Extension log file includes Remote copy volume group status information. By default, the HP 3PAR StoreServ Cluster Extension log file is located in the %ProgramFiles%\ Hewlett-Packard\Cluster Extension 3PAR\log\ directory.
Line 31: The encoded Cluster Extension execution path. Line 32: Online status of Cluster Extension resources. Line 33: Creating .online file to check resource health. Line 34: End of the Cluster Extension execution process. HP 3PAR StoreServ Storage log or sysmgr log A task, identified by task IDs is generated for each operation in the 3PAR StoreServ Storage. Task manager commands provides information regarding the tasks in the system.
When HP 3PAR StoreServ 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 62). Log files Log files assist you in locating and identifying problems. Timestamps, component IDs, and message IDs are included. • HP 3PAR StoreServ Cluster Extension-related messages are logged by MSFC to the file cluster.log in the location %windir%\Cluster\Reports.
check the status of the Remote Copy volume group and its member virtual volumes and decide whether it is safe to continue or not. HP 3PAR StoreServ Cluster Extension services, resources, or resource groups return a data center error and fail the resource if the Remote Copy volume group status indicates that the problem experienced locally would not be solved on another system connected to the same HP 3PAR StoreServ Storage.
Also, the physical disk must be connected to the primary datacenter storage array as soon as the storage array is brought back online. Another way to avoid this situation is to configure the CLX preexec script which does the rescan of the disks. The preexec script can be configured in CLX as DiskRescanDiskpart.bat in the same Windows folder and having the following line in this script.
• Using HP 3PAR StoreServ Management GUI, verify that the virtual volume is having read/write access on HP 3PAR StoreServ Storage where Cluster Extension resource is online. • Rescan disks using Disk Management. Cluster Extension and HP 3PAR Command Line (CLI) install/upgrade While installing or upgrading HP 3PAR Command Line Interface (CLI), the environment variable Path will be updated with the CLI install directory.
Remote Copy and 3PAR Virtual Domains Remote Copy checks HP 3PAR Virtual Domains (domains) on the remote system to ensure that the virtual volume is mirrored to the same domain name as the local domain name. The domain needs to be called a correct domain name. For more information on domains, see the HP 3PAR Concepts Guide and for instructions on setting up domains, see the HP 3PAR CLI Administrator’s Manual.
15.32.75.13 3parArrayB CLX resource fails to come online or CLX resource configuration fails This section is applicable only if 3PAR CLI and 3PAR OS are running either 3.1.2 MU3 P16, 3.1.1 MU3 P27, 2.3.1 MU5 P35, or later versions. If there is a mismatch of the array certificate stored in the 3PAR StoreServ Storage, and the exception file for that array stored locally on the failover cluster node, then you cannot configure the CLX resource or the CLX resource fails to come online or fails.
6 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 86) 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 StoreServ Storage 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 Integration, 6 Processes and components, 11 3PAR Remote Copy, 11 Volume groups, 12 3PAR StoreServ Cluster Extension Features, 6 A Adding HP 3PAR StoreServ Cluster Extension resource, 28 Adding dependencies using CLI, 43 using Failover Cluster Management, 42 using PowerShell, 43 Administration, 49 APPLICATION objects, 56 ApplicationDir description, 57 ApplicationStartup description, 57 AutoFailbackType Description, 33 B Basic Resource Health Check Interval Description,
description, 56 Hyper-V Live Migration, 48 Hyper-V Live Migration log enteries, 51 I Importing Configuration information, 25 Integration CLI, 6 with cluster software, 6 IsAlivePollInterval Description, 32 L Live migration, 48, 51 LogDir description, 56 LogLevel description, 56 UCF requirement, 41 LooksAlivePollInterval Description, 32 M Microsoft Management Console, 31 Mirrored disks Automated redirection, 7 P PendingTimeout Description, 32 Post-execution programs, 74 Return codes, 75 PostExecCheck desc
W Websites HP , 85 Product manuals, 85 90 Index
