LKCLI – Maintenance Tasks

This section explains how to maintain the LifeKeeper-protected systems and resources.

Configuration

These instructions assume that the configuration is 2 nodes.

Maintaining a LifeKeeper Protected Machine

The maintenance tasks performed on target1 such as shutdown of the LifeKeeper protected machine, will have an impact on LifeKeeper and the resources.

Execute the command on target1.

1. Switch the active resource on target1 to target2

i. Check the status of all of the resources on target1. Make a note of the resource tag name if there is a resource with an ISP status.

[target1]# lkcli status -q
LOCAL    TAG            ID             STATE     PRIO  PRIMARY
target1  ip-10.1.6.100  ip-10.1.6.100  ISP          1  target1
 
MACHINE  NETWORK ADDRESSES/DEVICE     STATE     PRIO
target2  TCP     10.1.6.88/10.1.6.89  ALIVE        1

ii. Switch the resources that are ISP on target1 to target2 one by one. You can execute the command from target1 by using “--remote” option.

[target1]# lkcli resource restore --tag ip-10.1.6.100 --remote target2
BEGIN restore of "ip-10.1.6.100"
END successful restore of "ip-10.1.6.100"

iii. Make sure all the resources are OSU on target1.

[target1]# lkcli status -q
LOCAL    TAG            ID             STATE     PRIO  PRIMARY
target1  ip-10.1.6.100  ip-10.1.6.100  OSU          1  target1
 
MACHINE  NETWORK ADDRESSES/DEVICE     STATE     PRIO
target2  TCP     10.1.6.88/10.1.6.89  ALIVE        1

2. Stop LifeKeeper on target1. It does not stop the resource by running “-f” option.

[target1]# lkcli stop -f
Removed /etc/systemd/system/lifekeeper-graphical.target.requires/lifekeeper.service.
Removed    /etc/systemd/system/lifekeeper-multi-user.target.requires/lifekeeper.service.

3. Perform the necessary maintenance on target1.

4. Start LifeKeeper on target1.

[target1]# lkcli start
Created symlink /etc/systemd/system/lifekeeper-graphical.target.requires/lifekeeper.service → /usr/lib/systemd/system/lifekeeper.service.
Created symlink /etc/systemd/system/lifekeeper-multi-user.target.requires/lifekeeper.service → /usr/lib/systemd/system/lifekeeper.service.

5. Bring the resources in-service on target1, if desired.

[target1]# lkcli resource restore --tag ip-10.1.6.100
BEGIN restore of "ip-10.1.6.100"
END successful restore of "ip-10.1.6.100"

Refer to Maintaining a LifeKeeper Protected System.

Maintaining LifeKeeper Protected Resources

This section explains how to perform maintenance for specific resources only.

Execute the command on target1.

1. Switch the active resources on target1 to target2.

i. Check the status of all of the resources on target1. If there is a resource that has an ISP status, perform a switchover following the steps below.

[target1]# lkcli status -q
LOCAL    TAG            ID             STATE     PRIO  PRIMARY
target1  ip-10.1.6.100  ip-10.1.6.100  ISP          1  target1
 
MACHINE  NETWORK ADDRESSES/DEVICE     STATE     PRIO
target2  TCP     10.1.6.88/10.1.6.89  ALIVE        1

ii. Check the resource tag names on target2 which are ISP on target1.

[target1]# lkcli status -q --remote target2
LOCAL    TAG            ID             STATE     PRIO  PRIMARY
target2  ip-10.1.6.100  ip-10.1.6.100  OSU         10  target1
 
MACHINE  NETWORK ADDRESSES/DEVICE     STATE     PRIO
target1  TCP     10.1.6.89/10.1.6.88  ALIVE        1

iii. Switch the resources that are ISP on target1 to target2 one by one.

[target1]# lkcli resource restore --tag ip-10.1.6.100 --remote target2
BEGIN restore of "ip-10.1.6.100"
END successful restore of "ip-10.1.6.100"

iv. Make sure all the resources have an OSU status on target1.

[target1]# lkcli status -q
LOCAL    TAG            ID             STATE     PRIO  PRIMARY
target1  ip-10.1.6.100  ip-10.1.6.100  OSU          1  target1
 
MACHINE  NETWORK ADDRESSES/DEVICE     STATE     PRIO
target2  TCP     10.1.6.88/10.1.6.89  ALIVE        1

2. Perform maintenance for the resources that are OSU.

3. Bring the resources in-service on target1, if desired.

[target1]# lkcli resource restore --tag ip-10.1.6.100
BEGIN restore of "ip-10.1.6.100"
END successful restore of "ip-10.1.6.100"

Refer to Maintaining a Resource Hierarchy.

Changing the Resource Settings

This section explains how to change the IP resource settings. For other commands refer to LKCLI Subcommands for Each ARK.

These instructions assume you are using LifeKeeper v9.5.0.

1. Check the resource tag name that you want to change the setting for.

# lkcli status -q
LOCAL    TAG            ID             STATE     PRIO  PRIMARY
target1  ip-10.1.6.100  ip-10.1.6.100  ISP          1  target1
 
MACHINE  NETWORK ADDRESSES/DEVICE     STATE     PRIO
target2  TCP     10.1.6.88/10.1.6.89  ALIVE        1

2. Based on the tag name, check the resource type and current value. Refer to LKCLI Subcommands for Each ARK for more information.

# lkcli resource info --tag ip-10.1.6.100
---
app: comm
priority: 1
properties:
  device: ens192
  ipaddr: 10.1.6.100
  netmask: 255.255.255.0
  pinglist: ''
  realip: 0
  restoremode: Enabled
  srcaddr: 0
switchback: INTELLIGENT
tag: ip-10.1.6.100
typ: ip

3. Change the resource settings (example: `restoremode` will be Disabled at this time).

# lkcli resource config ip --tag ip-10.1.6.100 --restoremode Disabled
Performing restoremode change ...
 
restoremode change successful.

4. The resource settings have changed.

# lkcli resource info --tag ip-10.1.6.100
---
app: comm
priority: 1
properties:
  device: ens192
  ipaddr: 10.1.6.100
  netmask: 255.255.255.0
  pinglist: ''
  realip: 0
  restoremode: Disabled
  srcaddr: 0
switchback: INTELLIGENT
tag: ip-10.1.6.100
typ: ip