Filter
Top Products
Controlling HeartBeat
Issue 1 July 2006 57
Configuration File: authkeys
This file controls how the two servers in the High Availability cluster control access to each
other. The following file shows a simple mechanism.
auth 2
2 crc
!
Important:
Important: If this file does not have suitable permissions, authentication fails. A typical
recommendation is “600" which only allows “root” to read or write to the file.
Controlling HeartBeat
The heartbeat Daemon can be controlled exactly like any other Linux daemon. Use the
following syntax to control the Daemon from the command line:
/etc/init.d/heartbeat [status|start|stop]
By default, HeartBeat logs to “/var/log/ha-log”. Use this log to check for errors. To simulate
interchange between the two servers, stop the primary server that uses this command:
/etc/init.d/heartbeat stop
The key point here is that since the IP address in the file must be the same as the far end of the
link, this file cannot be the same on both ends. For example, Server A needs to have the IP
address of Server B and vice-versa.
HeartBeat gives priority to the primary server and will activate it as soon as possible. Just
restart heartbeat to revert to normal operation.
/etc/init.d/heartbeat start
!
Important:
Important: To control the cluster, use only the HeartBeat controls described here. Do not
manually start or stop the Avaya IP Telephone File Server Application and /or
MV_WatchDog daemons.