HP StorageWorks XP Cluster Extension Software Administrator Guide (T1656-96035, April 2010)

The configuration example in Figure 9 on page 93 assumes the following information about the cluster:
There are four nodes in the cluster: Host1, Host2, Host3, and Host4.
There are two XP disk arrays with serial numbers 30047 and 30053.
The device group clxwebvgs is configured in the XP RAID Manager /etc/horcm101.conf
file.
XP Cluster Extension invokes the pre-executable script clxweb_pre_takeover.sh and the post-
executable script clxweb_post_takeover.sh. These files can be an executable script or a
program of your choice.
For RHCS, the configuration file /etc/opt/hpclx/conf/CLXXP.config is associated with
the RHCS service CLXWEB that is configured to use the XP Cluster Extension resource agent script.
RHCS invokes the resource agent script to start the CLXWEB service, which checks the disk pair
states before the volume groups vgweb and vghtdocs are activated and the web server is started.
The XP RAID Manager device group clxwebvgs includes all disks for the LVM volume groups
vgweb and vghtdocs. The sample CLXXP.config file shows the contents of the configuration
file with the described failover behavior.
For SLE HA, the XP Cluster Extension resource configuration file /etc/opt/hpclx/conf/
CLXXP.config is associated with the SLE HA resource CLXWEB. SLE HA invokes the resource
agent script, /usr/lib/ocf/resource.d/heartbeat/CLXXP, which checks the disk pair
states before the volume groups vgweb and vghtdocs are activated and the web server is started.
The XP RAID Manager device group clxwebvgs includes all disks for the LVM volume groups
vgweb and vghtdocs. The sample CLXXP.config file shows the contents of the configuration
file with the described failover behavior.
Sample configuration file:
COMMON
LogLevel info # values: error|info (optional)
APPLICATION CLXWEB # == service (RHCS) or resource group (SLE HA)
XPSerialNumbers 30047 30053
RaidManagerInstances 101
DeviceGroup clxwebvgs # raid manager device group
DC_A_Hosts Host1 Host2# systems in data center A
DC_B_Hosts Host3 Host4# systems in data center B
#optional parameter (only necessary if other than default)
FenceLevel data # values: data | never | async
ApplicationStartup resyncwait # values: fastfailback | resyncwait
AutoRecover yes # possible values: yes | no
DataLoseMirror no # possible values: yes | no
DataLoseDataCenter no # possible values: yes | no
PreExecScript /etc/opt/hpclx/clxweb_pre_takeover.sh
PostExecScript /etc/opt/hpclx/clxweb_post_takeover.sh
The ApplicationStartup object is set to RESYNCWAIT to configure the service (RHCS) or resource
group (SLE HA) to wait for a pair resynchronization in the event that the service (RHCS) or resource
group (SLE HA) fails over to an adoptive node.
The AutoRecover object is set to YES, which means that you use XP Cluster Extension capabilities
to automatically recover suspended disk pair states.
The DataLoseMirror object and DataLoseDataCenter object are set to NO, which means XP Cluster
Extension does not allow you to start the service (RHCS) or resource group (SLE HA) automatically
if the disk pair is suspended or a takeover operation leads to a suspended disk pair.
Configuring XP Cluster Extension for Linux94