3 configuration files – HP StorageWorks Scalable File Share User Manual
Page 47
3.
Heartbeat uses one or more of the network interfaces to send Heartbeat messages using IP
multicast. Each failover pair of nodes must have IP multicast connectivity over those
interfaces. HP SFS G3.2-0 uses eth0 and ib0.
4.
Each node of a failover pair must have mount-points for all the Lustre servers that might
be run on that node; both the ones it is primarily responsible for and those which might fail
over to it. Ensure that all the mount-points are present on all nodes.
5.
Heartbeat uses iLO for STONITH and requires the iLO IP address or name, and iLO login
and password for each node. Each node in a failover pair must be able to reach the iLO
interface of its peer over the network.
5.2.2 Generating Heartbeat Configuration Files Automatically
Because the version of lustre_config contained in Lustre 1.8 does not produce correct
Heartbeat V2.1.3 configurations, the -t hbv2 option should not be used. The lustre_config
script does however correctly add failover information to the mkfs.lustre parameters (allowing
clients to failover to a different OSS) if the failover NIDs are specified in the CSV file.
The HP SFS G3.2-0 software tarball includes the
/opt/hp/sfs/scripts/gen_hb_config_files.pl
script which is used to generate
Heartbeat configuration files for all the nodes from the lustre_config CSV file. The
gen_hb_config_files.pl
script must be run on a node where Heartbeat is installed. An
additional CSV file of iLO and other information must be provided. A sample is included in the
HP SFS G3.2-0 software tarball at /opt/hp/sfs/scripts/ilos.csv. For more information,
run gen_hb_config_files.pl with the -h switch. The Text::CSV Perl module is required
by gen_hb_config_files.pl.
5.2.3 Configuration Files
Four files are required to configure Heartbeat. These files can be automatically generated and
distributed by the gen_hb_config_files.pl script (including the edits to cib.xml described
later) using the recommended command:
# gen_hb_config_files.pl -i ilos.csv -v -e -x -c testfs.csv
Descriptions of the Heartbeat configuration files in the remainder of this section are included
for reference and further understanding, or so they can be generated by hand if necessary. For
more information, see
Use of the gen_hb_config_files.pl script is recommended.
•
/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.
5.2 Configuring Heartbeat
47