Setting up the Software to Replace an HA Pair

You can replace an existing HA pair with a new HA pair without interrupting log collection..

Prerequisites

All four appliances must be running the exact same version of the LogLogic software. The failover membership cannot be established if there is a mismatch in software releases between the nodes. If you must upgrade an appliance, see the TIBCO LogLogic® Log Source Packages Configuration Guides for the release to which you are upgrading.

The last digit of the appliances’ IP addresses cannot be the same, because the final digit is used as the failover node ID.

In this procedure:

  • Appliance A - current active node (10.1.1.71)
  • Appliance B - current standby node (10.1.1.72)
  • Appliance C - new active node (new 10.1.1.72)
  • Appliance D - new standby node (new 10.1.1.71)

Procedure

  1. Ensure that appliances C and D use the same NTP server as appliances A and B.
    1. Log in to the GUI web server using the private IP address of the appliance.
    2. Configure the appliance time through the Administration > System Settings > Time tab.
      Note: Changing NTP settings on the active appliance in an HA pair reboots both appliances in the pair.
  2. Shut down the current standby node, appliance B, without changing the failover configuration on the current active node, appliance A.
  3. From the CLI, through a serial console, log in to appliance C.
  4. Configure appliance C with the private IP address that appliance B was using: 
    set ip private-ip-address netmask gateway [ifdev] [defaultgw]
    For example, using 10.1.1.72 as the private IP address and 10.1.1.1 as the gateway: 
    > set ip 10.1.1.72 255.255.255.0 10.1.1.1 bond0
New interface settings:
ip 10.1.1.72 255.255.255.0 10.1.1.1 
CHANGES HAVE NOT BEEN SAVED!
> save
    Note: If you configure more than one interface in the set ip command, make sure the subnets do not overlap.
  5. Set failover on appliance C so it automatically migrates data from appliance A and then synchronizes with appliance A to become its standby node. For example, using 10.1.1.177 as the public IP address and 10.1.1.71 as the private IP address of the other appliance: 
    > set failover configure
Enter the public Ip address for the HA partner pair in the form <ip> <netmask> <broadcast> <ifdev>:
10.1.1.177 255.255.255.0 10.1.1.255 bond0
Should this appliance be the destination of automatic migration: Y
Enter the Ip address of the peer appliance in the form <ip>: 10.1.1.71
CHANGES HAVE NOT BEEN SAVED!
>
  6. Save the changes to apply the new configuration: 
    > save
Writing changes to disk...
Generating new SSL certificate...
Generating RSA private key, 1024 bit long modulus...
STOPPING MASTER TASK..............................(ok)
[writing new cluster configuration]
STARTING MASTER TASK...(ok)
done.
>

    When the migration and failover configuration completes, the appliance GUI System Status dashboard displays: 

    failover: master 
appliance-A (ok) - standby 
appliance-C (ok)
  7. After resynchronization completes, shut down appliance A.
    Due to the resulting failover, appliance C becomes the active node, and reports the other node as missing. On the GUI of appliance C, the System Status dashboard displays: 
    failover: master appliance-C (wait) - standby appliance-A (unavailable)
  8. From the CLI, through a serial console, log in to appliance D.
  9. Configure appliance D with the private IP address that appliance A was using. 
    set ip private-ip-address netmask gateway [ifdev] [defaultgw]
> set ip 10.1.1.71 255.255.255.0 10.1.1.1 bond0
New interface settings:
ip 10.1.1.71 255.255.255.0 10.1.1.1 
CHANGES HAVE NOT BEEN SAVED!
  10. Set failover on appliance D so it automatically migrates data from appliance C and then synchronizes with appliance C to become its standby node. For example, using 10.1.1.177 as the public IP address and 10.1.1.72 as the IP address of the peer appliance: 
    > set failover configure
Enter the public Ip address for the HA partner pair in the form <ip> <netmask> <broadcast> <ifdev>: 
10.1.1.177 255.255.255.0 10.1.1.255 bond0
Should this appliance be the destination of automatic migration: Y
Enter the Ip address of the peer appliance in the form <ip> <netmask> <broadcast> <ifdev>: 10.1.1.72
CHANGES HAVE NOT BEEN SAVED!
>
  11. Save the changes to apply the new configuration: 
    > save
Writing changes to disk...
Generating new SSL certificate...
Generating RSA private key, 1024 bit long modulus...
STOPPING MASTER TASK..............................(ok)
[writing new cluster configuration]
STARTING MASTER TASK...(ok)
done.
>

    When the migration and failover configuration completes, System Status dashboard on the appliance GUI displays: 

    failover: master appliance-C (ok) - standby appliance-D (ok)

Result

The failover is now set up and both new appliances are synchronizing their data.