HA node selection branches in to the six sub-menus:

Login

        Like manipulate cluster, user must login first before using HA node sub-menus to do something on HA nodes through Web-based Cluster Management Tool. The purpose of Login procedure is to testify the identification of users who will make operations on the cluster and give relevant permissions corresponding to users' authority.

        Typing in your user name and password if the administrators configure them for you. If not, contact the administrator to configure them and set the cluster access authority to you.

Install HA software on nodes

        HA node needs two HA software as the based-HA support software. They are "Heartbeat" software and "mon" software. This sub-menu helps user to copy both of them from ClusterProbe server to selected HA nodes, and install them on HA nodes.

        Make sure that both of them have properly installed on HA nodes you want before you try to configure them.

        There are four steps to copy or install HA software packages.

            step 1: Select "mon" or "Heartbeat" to Copy/Install

            step 2:  Select files

                You would see the following figures:

            step 3: Select nodes you want to install HA software

                You can choose multiple nodes in cluster.

            Step 4:   Confirm page

                In this web page, system gets the confirm information including selected packet name and selected node names. Clicking Finish button means copy/install selected packet to/on selected nodes.

                You can also make decision on whether show details of result.

Config HA software on nodes

        There are four configure files for HA software. Three of them are for "Heartbeat" and and mon.cf is for "mon".

            ha.cf

            authkeys

            haresources

            mon.cf

• Set Current node

        You can set the current node by typing node name on Current node field and clicking OK button. After clicking , current node would be set to be the under lined part of this page. 

          Attention: if the current node field is: No Current Node, you should set one before you continue to configure HA software.

• Configuring heartbeat

• ha.cf
  There are three files you will need to configure before starting up heartbeat.   First, is ha.cf.   It tells heartbeat what types of media paths to use and how to configure them.

serial /dev/ttyS0

                         Replace /dev/ttyS0 with the appropriate dev file for your required serial heartbeat.

          udp

              Specifies to use an udp heartbeat over the 10x eth1 interface (replace with eth0, eth1, or whatever you use).

     udpport 694

              Use port number 694 for udp. This is the default, and the official registered port    number.

          keepalive 2

              Sets the time between heartbeats to 2 seconds.

          deadtime 10

              Node is pronounced dead after 10 seconds.

          hopfudge 1    

               Optional.  For ring topologies, number of hops allowed in addition to the number of nodes in the cluster.

       

     baud 19200

              Speed at which to run the serial line (bps).

          watchdog /dev/watchdog

               Optional.  The watchdog function provides a way to have a system that is still minimally functioning, but not providing a heartbeat, reboot itself after a minute of being sick.  This could help to avoid a scenario where the machine recovers its heartbeat after being pronounced dead.  If that happened and a disk mount failed over, you could have two nodes mounting a disk simultaneously. If you wish to use this feature, then in addition to this line, you will need to load the "softdog" kernel module and create the actual device file.  To do this, first type "insmod softdog" to load the module. Then, type "grep misc /proc/devices" and note the number it reports (should be 10).  Next, type "cat /proc/misc | grep watchdog" and note that number (should be 130).  Now you can create the device file with that info typing,"mknode /dev/watchdog c 10 130".

          nice_failback on

            Optional.  For those familiar with Tru64 Unix, heartbeat acts as if in "favored member" mode.  The master holds all the resources until a failover, at which time the slave takes over.  Once the master comes back online, it will take everything back from the slave.  This option will prevent the master node from re-acquiring cluster resources after a failover.

      node node1name.csis.hku.hk

           Hostname of machine in cluster as described by `uname -a`.

 

      node node2name.csis.hku.hk

           Hostname of machine in cluster as described by `uname -a`.

               If you want to configure them manually, you can find them in the /etc/ha.d directory in     HA nodes.The ha.cf in the source directory contains all the various options you can use, I'll go through it line by line...

• authkeys

        This file to configure determines your authentication keys.  There are three types of authentication methods available:   crc, md5, and sha1.

If your heartbeat runs over a secure network, such as the crossover cable in our example, you'll want to use crc.  This is the cheapest method from a resources perspective.  If the network is insecure, but you're either not very paranoid or concerned about minimizing CPU resources, use md5.  Finally, if you want the best authentication without regard for CPU resources, use sha1.  It's the hardest to crack.

After you making your decision, just click OK button. :)

• haresources
  

This file specifies the services for the cluster and who the default owner is.
Node name , IPAddress and HA Application you type here would be recorded as HA resources.

• Configure Mon

• mon.cf

cfbasedir

    Configure files are in this directory. (The full path where all the config files can be found.)

alertdir

dir is the full path to the alert scripts. This is the value set by the -a command-line parameter.

Multiple alert paths may be specified by separating them with a colon. All paths must be absolute.

When the configuration file is read, all alerts referenced from the configuration will be looked up in each of these paths, and the full path to the first instance of the alert found is stored in a hash. This hash is only generated upon startup or after a "reset" command, so newly added alert scripts will not be recognized until a "reset" is performed.

mondir

    Monitor files are in this directory.Monitor files would be executed in monitor scripts. "mon" runs applications monitor every n second according to the configuration of HA applications.

dir is the full path to the monitor scripts. This value may also be set by the -s command-line parameter.

Multiple alert paths may be specified by separating them with a colon. All paths must be absolute.

When the configuration file is read, all monitors referenced from the configuration will be looked up in each of these paths, and the full path to the first instance of the monitor found is stored in a hash. This hash is only generated upon startup or after a "reset" command, so newly added monitor scripts will not be recognized until a "reset" is performed.

maxproc

           The Max number of process mon can monitor.

histlength

num is the the maximum number of events to be retained in history list. The default is 100. This value may also be set by the -k command-line parameter.

randstart

When the server starts, normally all services will not be scheduled until the interval defined in the respective service section. This can cause long delays before the first check of a service, and possibly a high load on the server if multiple things are scheduled at the same intervals. This option is used to randomize the scheduling of the first test for all services during the startup period, and immediately after the reset command. If randstart is defined, the scheduled run time of all services of all watch groups will be a random number between zero and randstart seconds.

• Set Heartbeat for Halt,Reboot when installing HA software(only once)

If you want heartbeat to run on startup, what to do will differ on your distribution.   For Red Hat , you will need to place links to the startup script in the appropriate init level directories.  I have heartbeat start last and only care about the 0(halt),6(reboot), 3(text-only), 5(X) run levels.

On click this, you may run the following command as root:

    cd /etc/rc.d/rc0.d ; ln -s ../init.d/heartbeat K01heartbeat
    cd /etc/rc.d/rc3.d ; ln -s ../init.d/heartbeat S99heartbeat
    cd /etc/rc.d/rc5.d ; ln -s ../init.d/heartbeat S99heartbeat
   cd /etc/rc.d/rc6.d ; ln -s ../init.d/heartbeat K01heartbeat

Attention: You  run it on one HA node only once!

For heartbeat details, you can see the GetStart help page of Heartbeat.

For mon detail, you can see the mon help page of Mon.

Config HA node pair

• check current node pairs in cluster

        Show current node pairs in cluster.

• Add node pair & Delete node pair

        Add or Delete node pair from cluster. Cluster still includes the nodes of the node pair.

Monitor HA nodes

Selecting this option pops up the Cluster HA node real-time Status panel.

This panel shows you the real-time status of HA nodes in cluster by retrieving cluster status from ClusterProbe and generating the status picture dynamically.

Manipulate HA nodes

First , if the Current node filed is "No Current Node", you should first set the current node and click OK button. The following processes are functioned on current node.