Specifications

File System Health Monitoring
Value Old New
uname Server1 Newserver1
comm path address 172.17.100.48 172.17.105.49
IP resource address 172.17.100.220 172.17.100.221
The following steps should be performed to make these changes.
1. Stop LifeKeeper on both Server1 and Server2 using the command:
/etc/init.d/lifekeeper stop-nofailover
2. Change the uname of Server1 to Newserver1 using the command:
hostname Newserver1
3. Create the file, /tmp/subs, with the content below, on both Newserver1 and Server2:
Server1=Newserver1
172.17.100.48=172.17.105.49
172.17.100.220=172.17.100.221
4. Verify that the changes specified will not have any unexpected side effects by examining the
output of running the following command on both servers:
$LKROOT/bin/lk_chg_value -Mvf /tmp/subs
5. Modify the LifeKeeper files by running the lk_chg_value command without the -M option on
both servers:
$LKROOT/bin/lk_chg_value -vf /tmp/subs
6. Restart LifeKeeper on both servers using the command:
/etc/init.d/lifekeeper start
Notes:
l To see the changes lk_chg_value will make without modifying any LifeKeeper files, use
the -M option. To see the files lk_chg_value is examining, use -v. To not modify tag
names, use the -T option. To not modify resource ids, use the -I option.
File System Health Monitoring
The File System Health Monitoring feature detects conditions that could cause LifeKeeper protected
applications that depend on the file system to fail. Monitoring occurs on active/in-service resources
(i.e. file systems) only. The two conditions that are monitored are:
l A full (or almost full) file system, and
l An improperly mounted (or unmounted) file system.
When either of these two conditions is detected, one of several actions might be taken.
SteelEye Protection Suite for Linux203