Filter
Top Products
HeartBeat
56 Avaya IP Telephone File Server Application Reference Guide
Configuration File: ha.cf
The ha.cf file is the HeartBeat main configuration file consisting of a configuration parameters
list. A sample follows:
bcast eth1
keepalive 2
warntime 10
deadtime 30
initdead 120
udpport 694
nice_failback on
node EY-FTP1 ## This is your server 1
node EY-FTP2 ## This is your server 2
ping 192.168.38.1 ## This is a pingable address
The “node” definitions allow HeartBeat to identify the two servers that form the High Availability
cluster. The last entry is how HeartBeat confirms its network connectivity. If the “ping” fails to
operate correctly, HeartBeat assumes that although it is functioning correctly, it has lost
connectivity to the network. In this case, HeartBeat proceeds to interchange to the other node/
server.
Configuration File: haresources
This file contains information about the resources to be enabled or disabled by HeartBeat when
a node mode change is detected. A node change might be a change from slave to master or
from master to slave. It is mandatory that this file be identical on both servers.
Here is a sample:
EY-FTP1 192.168.38.130 mv_ipteld mv_watchdogd
The first entry: “EY-FTP1”defines the default master server. This definition allows HeartBeat to
stop and start gracefully without causing potential conflicts or ambiguous modes.
The second entry: “192.168.38.130” is the “shared” IP address. In this case, “192.168.38.130”
is not configured to be assigned to either server, but is dynamically assigned by the HeartBeat
application.
The third entry is the name of a script file to run when the state of a server changes. This entry
is executed with the “start” parameter on a change to master, and a “stop” on a change to slave.
In this situation, the “mv_ipteld” script starts and stops the MV_IPTelD and MV_WatchDog
daemons.