2 editing cib.xml, 4 copying files, 5 starting heartbeat – HP StorageWorks Scalable File Share User Manual
Page 36: 6 monitoring failover pairs

5.2.3.2 Editing cib.xml
The haresources2cib.py script places a number of default values in the cib.xml file that
are unsuitable for HP SFS G3.0-0.
•
By default, a server fails back to the primary node for that server when the primary node
returns from a failure. If this behavior is not desired, change the value of the
default-resource-stickiness attribute from 0 to INFINITY. Below is a sample of the line in
cib.xml
containing this XML attribute:
name="default-resource-stickiness" value="0"/> • To provide Lustre servers adequate start-up time, the default action timeout must be name="default-action-timeout" value="20s"/>> • By default, stonith is not enabled. Enable stonith by changing the attribute shown below name="stonith-enabled" value="false"/> 5.2.4 Copying Files The ha.cf, haresources, authkeys, and cib.xml files must be copied to the nodes in the , group haclient. The /etc/ha.d/authkeys file must be readable and writable only by root (mode 0600). Files ending in .sig or .last must be removed from /var/lib/heartbeat/crm before 5.2.5 Starting Heartbeat HP recommends that you start the Lustre file system manually, and verify proper file system command to mount all the Lustre file system components on their respective servers, and also to mount the file system on clients. When proper file system behavior has been verified, . After all the files are in place, starting Heartbeat with service heartbeat start starts the . 5.2.6 Monitoring Failover Pairs Use the crm_mon command to monitor resources in a failover pair. For details, see the crm_mon Sample crm_mon output is below. In this example there are two nodes which are Lustre OSSs, ============ 36 Using HP SFS Software
increased from "20s" to "600s". Below is a sample of the line containing this XML attribute:
from false to true:
failover pair. The authkeys, ha.cf, and haresources files go in /etc/ha.d. The cib.xml
file must be copied to /var/lib/heartbeat/crm/cib.xml and must be owned by user
hacluster
starting Heartbeat after a reconfiguration. Otherwise, the last cib.xml file is used, rather than
the new one.
behavior on sample clients before attempting to start the file system using Heartbeat. Use the
mount
unmount the file system manually using the umount command on all the clients and servers
and use Heartbeat to start and stop the file system as explained below and in
Lustre servers by mounting the corresponding file systems. After initial testing, Heartbeat should
be permanently enabled with chkconfig --add heartbeat, or chkconfig heartbeat
on
manpage.
and eight OSTs, four per node.
Last updated: Thu Sep 18 16:00:40 2008
Current DC: n4 (0236b688-3bb7-458a-839b-c19a69d75afa)
2 Nodes configured.