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

3. In the configuration file (CLXXP.config), enter the appropriate values for:
• XPSerialNumbers
• RaidManagerInstances
• DeviceGroup
• DC_A_Hosts
• DC_B_Hosts
• ResyncMonitor
• FenceLevel
• DataLoseMirror
• DataLoseDataCenter
NOTE:
For more information about these values, see Chapter 8 on page 123.
For example:
APPLICATION CLXWEB
XPSerialNumbers 30060 30080
RaidManagerInstances 101
DeviceGroup vgnetscape
DC_A_Hosts sys1A sys2A
DC_B_Hosts sys1B sys2B
ResyncMonitor yes
FenceLevel never
DataLoseMirror yes
DataLoseDataCenter yes
IMPORTANT:
If you are using Device Mapper Multipath, configure the multipath_rescan.sh script
as a PostExecScript. For more information, see “Rescanning multipath devices” on page 106.
4. Copy the updated CLXXP.config file to the other cluster nodes.
Testing the service configuration
The procedure and commands in this section are based the sample configuration in “XP Cluster
Extension for Linux: Sample configuration” on page 93. Use this procedure as a guide for configuring
your environment.
1. Use the Cluster User Service Administration Utility (clusvcadm) to start the service on Host1.
#clusvcadm -e CLXWEB –m Host1
2. Verify that the service started successfully.
#clustat –s CLXWEB
3. Stop the service and verify that the service stopped successfully.
#clusvcadm –s CLXWEB Or #clusvcadm –d CLXWEB
Configuring XP Cluster Extension for Linux100