Specifications

Resource Error Recovery Scenario
This operation will fail if there is no backup interface configured for this instance. If the specified
resource instance is currently in service, the move will be implemented by using the ipaction
remove operation to un-configure the IP address on the current interface, and ipaction restore
to configure it on the backup interface. Following the move, the execute_broadcast_ping
function will be used to verify the operation of the address on the new interface, and if successful, the
interface values will be swapped in the IP resource instance INFO field. If the specified IP resource
instance is out-of-service when this command is executed, the primary and backup interface values
will simply be swapped in the INFO field.
The lkipbu utility also provides an option for retrieving the currently defined primary and backup
interfaces for a specified IP resource instance along with the state of the resource on the primary
interface (up or down). This capability is specified via the -s option using the following syntax:
lkipbu [-d machine] -s -t tag
The output will be similar to the following:
IP address: 172.17.106.10
Netmask: 255.255.252.0
Primary interface: eth0 (up)
Backup interface: eth1
Refer to the lkipbu(8) man page for further detail.
Resource Error Recovery Scenario
LifeKeeper provides a real-time daemon monitor, lkcheck, to check the status and health of
LifeKeeper-protected resources. For each in-service resource, lkcheck periodically calls the
quickCheck script for that resource type. The quickCheck script performs a quick health check of
the resource, and if the resource is determined to be in a failed state, the quickCheck script calls the
event notification mechanism, sendevent.
The following figure illustrates the recovery process tasks when lkcheck initiates the process:
SteelEye Protection Suite for Linux57