HP StorageWorks Scalable File Share - Manual (Page 49)

The destination host name is optional but it is important to note that if it is not specified,
crm_resource
forces the resource to move by creating a rule for the current location with the
value -INFINITY. This prevents the resource from running on that node again until the constraint
is removed with crm_resource -U.
If you cannot start a resource on a node, check that node for values of -INFINITY in /var/lib/
heartbeat/crm/cib.xml
. There should be none. For more details, see the crm_resource
manpage. See also http://www.linux-ha.org/Heartbeat .
5.2.8 Things to Double-Check
Ensure that the following conditions are met:
• The .sig and .last files should be removed from /var/lib/heartbeat/crm when a
new cib.xml is copied there. Otherwise, Heartbeat ignores the new cib.xml and uses the
last one.
• The /var/lib/heartbeat/crm/cib.xml file owner should be set to hacluster and the
group access permission should be set to haclient. Heartbeat writes cib.xml to add status
information. If cib.xml cannot be written, Heartbeat will be confused about the state of
other nodes in the failover group and may power cycle them to put them in a state it
understands.
• The /etc/ha.d/authkeys file must be readable and writable only by root (mode 0600).
• The host names for each node in /etc/ha.d/ha.cf must be the value that is returned
from executing the hostname or uname -n command on that node.
5.2.9 Things to Note
• When Heartbeat starts, it waits for a period to give its failover peer time to boot and get
started. This time is specified by the init_dead parameter in the ha.cf file (60 seconds
in the example ha.cf file). Consequently, there may be an unexpected time lag before
Heartbeat starts Lustre the first time. This process is quicker if both nodes start Heartbeat
at about the same time.
• Heartbeat uses iLO for STONITH I/O fencing. If a Heartbeat configuration has two nodes
in a failover pair, Both nodes should be up and running Heartbeat. If a node boots, starts
Heartbeat, and does not see Heartbeat running on the other node in a reasonable time, it
will power-cycle it.
5.3 Starting the File System
After the file system has been created, it can be started. At the low level, this is achieved by using
the mount command to mount the various file system server components that were created in
the creation section. However, since the system has been configured to use Heartbeat, use
Heartbeat commands to start the file system server components. This process requires you to
use the HP recommended configuration with the MGS and MDS nodes as a failover pair, and
additional pairs of OSS nodes where each pair has access to a common set of MSA2000 storage
devices.
This procedure starts with the MGS node booted but the MDS node down.
1. Start the Heartbeat service on the MGS node:
# service heartbeat start
After a few minutes,the MGS mount is active with df.
2. Boot the MDS node.
3. Start the Heartbeat service on the MDS node:
# service heartbeat start
After a few minutes, the MDS mount is active with df.
5.3 Starting the File System 49