HP P6000 Cluster Extension Software Administrator Guide (5697-2274, November 2012)

cluster resource clx_fileshare /privprop
The following example changes the CSObjectPathA property for the resource clx_fileshare:
cluster resource clx_fileshare /privprop CSObjectPathA=
"HPEVA_ConsistencySet.InstanceID=""50001FE15002B5A0.6005-08b4-
0001-2b69-0000-6000-86a0-0000"""
To retrieve the values for CSObjectPathA and CSObjectPathB, you must create and configure a
UCF.cfg file for this DR group and run the clxconf -smis command. The values for both
objects are stored in the clxobjpaths.cfg file.
NOTE: This step is not necessary when using the Failover Cluster Management GUI.
The following example changes the name of the resource P6000 Cluster Extension
resource1 to P6000 Cluster Extension resource2:
cluster resource "P6000 Cluster Extension resource1" /ren:"P6000 Cluster Extension resource2"
Powershell cmdlets can also be used instead of cluster.exe to perform the same tasks. For
more information, see Microsoft documentation.
Setting P6000 Cluster Extension properties using a UCF
You can use a UCF to configure certain P6000 Cluster Extension properties .
Properties that you can configure in a UCF include:
• LogLevel
• ClusterNotifyCheckTime
• ClusterNotifyWaitTime
• DataSyncTimeout
• MergeCheckInterval
• StatusRefreshInterval
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 P6000 Cluster Extension resource offline.
2. Open the sample UCF.cfg file located in %ProgramFiles%\Hewlett-Packard\Cluster
Extension EVA\sample.
3. Update the file with the property values you want to use.
For more information on the available properties, see “User configuration file and EVA Cluster
Extension objects” (page 42).
4. Save the file and copy it to the following directory on all cluster nodes: %ProgramFiles%\
Hewlett-Packard\Cluster Extension EVA\conf.
5. Bring the P6000 Cluster Extension resource online.
Adding dependencies on a P6000 Cluster Extension resource
P6000 Cluster Extension Software must be the first resource in the resource chain of a MSCS
service or application. All resources that depend on the disk resource, such as a file share, and
all disk resources (physical disks), must be configured for dependency on the P6000 Cluster
Extension resource.
When adding dependencies:
• For Windows Server 2008/2008 R2/2012, use the Failover Cluster Management GUI, cluster
commands in the CLI, or the MMC for remote management.
• For Server Core or Hyper-V Server, use cluster commands in the CLI or the MMC.
Adding dependencies on a P6000 Cluster Extension resource 33