Upgrading in a High Availability Environment

This section describes the procedure to upgrade appliances in high availability setup.

For upgrading a standalone appliance, see Upgrading a Standalone Appliance.

For detailed information about HA, see the TIBCO LogLogic® Log Management Intelligence Administration.

Prerequisites

The following prerequisites must be met before starting the upgrade process on your HA appliances.
  • Both HA appliances must have the same hardware model and software version.
  • Ensure that you have read Upgrade Considerations and have performed all tasks mentioned in Preparing to Upgrade the Appliance on each appliance.
  • Ensure that your HA environment is synchronized, by viewing the cluster status on the Dashboards > System Status page of the GUI. Ensure that there are no warning messages that appear on the System Status page.
  • If currently enabled in your HA environment, disable the following features on the active appliance:
    • Archiving:

      Note down all the archive configuration settings to help you when you reenable the archiving feature.

    • Advanced Features:

      Must be disabled from the CLI. Disabling Advanced Features automatically disables the Monthly Index, Advanced Aggregation, and Monitoring Console features.

Important:
  • Forcing failovers for the purpose of keeping one particular appliance “active” is not recommended, because it has no particular benefit and any failover event causes some loss of data - even if for a few seconds. If you want to force a failover, you must wait until the postupgrade process is complete.
  • The log data collected on appliance A after disabling HA is ignored while setting up HA on appliance A during initialization and syncing.
Note: The terms "active" and "standby" might suggest that these appliances are not equivalent in every respect. In fact, they must have identical capabilities for High Availability pairing to work. Therefore, for clarity during the upgrade process below, the original active appliance is referred to as "appliance A" and the original standby appliance is referred to as "appliance B" (even though their roles reverse and then revert).
This HA upgrade procedure uses the following example appliance information:
Appliance Appliance type IP address
Appliance A HA Active 10.20.0.44
Appliance B HA Standby 10.20.0.45
Public HA Public 10.20.0.46
Network Mask 255.255.255.0
Network Broadcast 10.20.0.255

Procedure

On appliance B:

  1. From the CLI, disable the HA configuration:
    1. From a command prompt, log in as the root user, and type the password.
    2. Run the following command to disable HA: 
      set failover disable
    3. When the prompt displays the message CHANGES HAVE NOT BEEN SAVED!, type save and then press Enter.
  2. Install the correct version of LogLogic LSP.
  3. Perform the GUI upgrade steps.
  4. After the appliance reboots, run the postupgrade script as described in Running the Postupgrade Script.

On appliance A:

  1. From the CLI, disable the HA configuration:
    1. From a command prompt, log in as the root user, and type the password.
    2. Run the following command to disable HA: 
      set failover disable
    3. When the prompt displays the message CHANGES HAVE NOT BEEN SAVED!, type save and then press Enter.

On appliance B:

  1. Set up HA configuration:
    1. From a command prompt, log in as the root user, and type the password.
    2. Run the following command to set up HA: 
      set failover configure
    3. Enter the IP addresses of the cluster: <HA_public_IP_address> <network_mask> <network_broadcast> bond0. For example: 
      10.20.0.46 255.255.255.0 10.20.0.255 bond0
    4. When prompted about this appliance being the destination of automatic migration:
      Enter N.

      Type the IP address of the peer appliance (appliance A): 10.20.0.44

    5. Follow the prompts. Make sure you type save when prompted.
      Wait until done is displayed on the CLI, indicating that the HA setup is successful on the appliance.
    At this point, appliance B has become the active appliance. As appliance A is no longer part of the HA pair, it is reported as "out of cluster" by appliance B.

On appliance A:

  1. Install the correct version of LogLogic LSP.
  2. Perform the GUI upgrade steps.
  3. After the appliance reboots, run the postupgrade script as described in Running the Postupgrade Script.
  4. After the upgrade process completes successfully, set up the HA configuration:
    1. From a command prompt, log in as the root user, and type the password.
    2. Run the following command to set up HA: 
      set failover configure
    3. Enter the IP addresses of the cluster: <HA_public_IP_address> <network_mask> <network_broadcast> bond0. For example: 
      10.20.0.46 255.255.255.0 10.20.0.255 bond0
    4. When prompted about this appliance being the destination of automatic migration:
      Enter Y.

      Type the IP address of the peer appliance (appliance B):

      10.20.0.45
    5. Follow the prompts. Make sure you type save when prompted.
      Wait until done is displayed on the CLI, indicating that the HA setup is successful on the appliance.

Result

The upgrade is complete. Appliance B is active and appliance A is standby.

What to do next

After upgrade is successful, perform the following tasks:
  • (Only for TIBCO LogLogic® LX1025R1 Appliance) Enable the swap file by performing the following steps:
    1. Login to the appliance through SSH as toor user.
    2. Run the following command: 
      $ /loglogic/scripts/enable_12g_swap_file.sh
  • Reenable the following features if you had disabled them before starting the upgrade process:
    • Archiving
      Important: Do not change any settings in the archive configuration while re-enabling the archive feature.
    • Advanced Features
      After enabling Advanced Features, you can explicitly enable the Monthly Index, Advanced Aggregation, and Monitoring Console - as applicable. In an HA environment, you can enable the Advanced Features, Advanced Aggregation, and Monitoring Console only from the CLI on the active appliance.
Next topic: Upgrading in an AWS Environment
Previous topic: Upgrading a Standalone Appliance