5. run #kusu-genconfig hosts, you should see the new internal domain name in the output.

6. Run "kusu-addhost -u" to update configuration files.

7.Change the failover mode to automatic.

#kusu-failmode -m auto

4>How to change the HPC master from the master candidate host to the master host

Once failover occurs, the master fails over to the master candidate host.

However, once issues with the master host have been resolved, the master does not automatically switch back to the master host. You must manually change the HPC master from the master candidate host back to the master host.

1. Restart the heartbeat by running the following command on the master host or just reboot it:

#service kusuha-heartbeat restart

2. Switch the master from the master candidate host to the master host by running the following

command on the master candidate host:

# kusu-failto

3. Check that the master has successfully switched to the master host:

# kusu-failinfo

5> How to diagnose HA enabled cluster

a>. Run ‘# crm status’ to check heartbeat and pacemaker status on current installer node, the output should be like below:

[root@ma ~]# crm status

============

Last updated: Wed Jul 2 17:21:13 2014

Last change: Wed Jul 2 16:37:27 2014 via crmd on ma

Stack: openais

Current DC: ma - partition with quorum

Version: 1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558

2 Nodes configured, 2 expected votes

6 Resources configured.

============

Online: [ installer001 ma ]

Resource Group: KusuInstaller

ip1 (ocf::heartbeat:IPaddr2): Started ma

ip1arp (ocf::heartbeat:SendArp): Started ma

ip2 (ocf::heartbeat:IPaddr2): Started ma

ip2arp (ocf::heartbeat:SendArp): Started ma

dhcp (lsb:dhcpd): Started ma

lsflim (ocf::platform:lsflim): Started ma

===================================================

b>. Run ‘#kusu-failinfo’ to check fail mode and HA master, the output should be like below:

[root@ma ~]# kusu-failinfo

Installer node is currently set to: ma [Online]

Failover node is currently set to: installer001 [Online]

Failover mode is currently set to: Auto

KusuInstaller services currently running on: ma

c>. Run ‘#hpc-ha-tool status’ on current installer node to diagnose HA diagnostic, the output should be like below: (PS: please run '#kusu-failmode –m auto' to set to Auto mode first)

[root@ma ~]# hpc-ha-tool status

Testing HPC HA availability ... ok

Testing IBM Platform HPC HA configuration ... ok

Testing master failover host ... ok

Testing heartbeat status ... ok

Testing pacemaker status ... ok

Testing the IBM Platform HPC database ... ok

Testing float IP addresses ... ok

Testing NFS mount points ... ok

Testing HA key directories ... ok

Testing failover mode ... ok

Testing PMC daemon status ... ok

Testing LSF daemon status ... ok

Testing Kusu resource status ... ok

Testing isf-ac daemon status ... ok

HPC HA is ready.

6>Increase size of /var parition in standby node in a High Availability setup for HPC 3.2 (A KB article will be available soon)

7> HA enabled HPC cluster relay on NFS server, network and storage system, so please check these system first when you met with any HA related issues.

8>How to release ‘Locked’ status on master nodes when the failover mode is set to Auto. (A KB article will be available soon)

When we run ‘#kusu-failinfo’, we may see that the master node is “Locked” although the Failover mode is set to Auto like below: