HP StorageWorks Scalable File Share User Manual
Page 46
# gen_hb_config_files.pl -i ilos.csv -v -e -x testfs.csv
Descriptions are included here for reference, or so they can be generated by hand if necessary.
For more information, see
•
/etc/ha.d/ha.cf
Contains basic configuration information.
•
/etc/ha.d/haresources
Describes the resources (in this case file systems corresponding to Lustre servers) managed
by Heartbeat.
•
/etc/ha.d/authkeys
Contains information used for authenticating clusters. It should be readable and writable
by root only.
•
/var/lib/heartbeat/crm/cib.xml
Contains the Heartbeat V2.1.3 Cluster Information Base. This file is usually generated from
ha.cf
and haresources. It is modified by Heartbeat after Heartbeat starts. Edits to this
file must be completed before Heartbeat starts.
The haresources files for both members of a failover pair (Heartbeat cluster) must be identical.
The ha.cf files should be identical.
You can generate the simple files ha.cf, haresources, and authkeys by hand if necessary.
One set of ha.cf with haresources is needed for each failover pair. A single authkeys is
suitable for all failover pairs.
ha.cf
The /etc/ha.d/ha.cf file for the example configuration is shown below:
use_logd yes
deadtime 10
initdead 60
mcast eth0 239.0.0.3 694 1 0
mcast ib0 239.0.0.3 694 1 0
node node5
node node6
stonith_host * external/riloe node5 node5_ilo_ipaddress ilo_login ilo_password 1 2.0 off
stonith_host * external/riloe node6 node6_ilo_ipaddress ilo_login ilo_password 1 2.0 off
crm yes
The ha.cf files are identical for both members of a failover pair. Entries that differ between
failover pairs are as follows:
mcast
An HP SFS G3.1-0 system consists of multiple Heartbeat clusters. IP multicast groups
are used in the privately administered IP multicast range to partition the internode
cluster traffic. The final octet (3 in the previous example) must be different for each
failover pair. The multicast group addresses specified here must not be used by other
programs on the same LAN. (In the example, the value 694 is the UDP port number,
1
is the TTL, and 0 is boilerplate.)
node
Specifies the nodes in the failover pair. The names here must be the same as that
returned by hostname or uname -n.
stonith_host
Each of these lines contains a node name (node5 and node6 in this case), the IP
address or name of the iLO, and the iLO login and password between some boilerplate.
haresources
The /etc/ha.d/haresources file for the example configuration appears as follows:
node5 Filesystem::/dev/mapper/mpath1::/mnt/ost8::lustre
node5 Filesystem::/dev/mapper/mpath2::/mnt/ost9::lustre
node5 Filesystem::/dev/mapper/mpath3::/mnt/ost10::lustre
node5 Filesystem::/dev/mapper/mpath4::/mnt/ost11::lustre
node6 Filesystem::/dev/mapper/mpath7::/mnt/ost12::lustre
46
Using HP SFS Software