Specifications

Set Up TTY Connections
5. Perform any of the following optional configuration tasks:
l Set the Server Shutdown Strategy
l Configure the manual failover confirmation option
l Tune the LifeKeeper heartbeat
l Add the LifeKeeper GUI icon to your desktop toolbar
l Configure SNMP Event Forwarding via SNMP
l Configure Event Email Notification
l If you plan to use STONITH devices in your cluster, create the scripts to control
the STONITH devices and place them in the appropriate LifeKeeper events
directory.
6. SPS is now ready to protect your applications. The next step depends on whether you will be
using one of the optional SPS Recovery Kits:
l If you are using an SPSRecovery Kit, refer to the Documentation associated
with the kit for instructions on creating and extending your resource hierarchies.
l If you are using an application that does not have an associated Recovery Kit,
then you have two options:
l If it is a simple application, you should carefully plan how to create an
interface between your application and LifeKeeper.You may decide to
protect it using the Generic Application Recovery Kitincluded with the
LifeKeeper core.
Set Up TTY Connections
If you plan to use a TTY communications (comm) path for a LifeKeeper heartbeat, you need to set up
the physical connection for that heartbeat. Remember that multiple communication paths are required
to avoid false failover due to a simple communications failure. Two or more LAN-based (TCP) comm
paths should also be used.
Connect the TTY cable to the serial ports of each server to be used for the serial heartbeat.
1. Test the serial path using the following command:
/opt/LifeKeeper/bin/portio -r -p port -b baud
where:
l baud is the baud rate selected for the path (normally 9600)
l port is the serial port being tested on Server 1, for example /dev/ttyS0.
Server 1 is now waiting for input from Server 2.
2. Run command portio on Server 2. On the second system in the pair, type the following
command:
62Configuration