Upgrading in a High Availability Environment

The process of upgrading your appliances in a High Availability (HA) appliance environment is different.

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

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.
  • Verify the disk requirements, as described in Verify disk space requirements.
  • Load and extract the upgrade files, as described in Preparing to Upgrade the Appliance
  • Ensure that your HA environment is synchronized, by viewing the cluster status on the System Status page of the web GUI. Ensure that there are no warning messages that appear on the Dashboards > System Status page.
  • If currently enabled on your HA setup, 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 between Step 1 and Step 8 on appliance A is ignored at Step 11 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 in order 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

  1. On the Appliance B, disable the HA configuration from the CLI:
    1. Open 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 LogLogic LSP version based on LogLogic LSP - LogLogic LMI support matrix for the target LogLogic LMI software.
    See the TIBCO LogLogic® Log Source Packages Release Notes, which is available on the eDelivery website or TIBCO Support site after logging in.
  3. Make sure that the system is ready for upgrade, extract the health check package and run the health check command healthcheck.sh with the correct path. See the Health Check section.
  4. Make sure that the update files (bz2 and bz2.sig) are downloaded and are available in the /loglogic/update directory on the Appliance B. For details of the upgrade matrix, see TIBCO LogLogic® Log Management Intelligence Release Notes.

    The following files are examples of the update files you need:

    • update-<timestamp>-full.tar.bz2
    • update-<timestamp>-full.tar.bz2.sig
  5. Log in to Appliance B and complete the update.
    1. Open a web browser and log in to the Appliance B.
    2. In the navigation menu, click Administration > File Update.
    3. The update-<timestamp>-full.tar.bz2 is displayed in the Select File box.
    4. Click the Update button. You might need to wait about 30 - 40 minutes for the update to complete. You can watch the progress on the File Update page.
  6. After Appliance B reboots, you must run the postupgrade Script. For post upgrade steps, follow the steps as described in Running the Postupgrade Script.
  7. (Optional) If you want to update the SSL signature algorithm to sha2, run the script: /loglogic/tomcat/conf/cert_utils/certgen.sh.
  8. After the upgrade process completes successfully on appliance B, set up the HA configuration on appliance A by performing the following steps:
    1. From the 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.
  9. On Appliance B, set up the HA configuration.
    1. Open 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. Follow the prompts. Make sure you type save when prompted. The following example IP addresses are as noted at the beginning of this section:
      Public IP address of the cluster: 
 
      10.20.0.46 255.255.255.0 10.20.0.255 bond0

      When prompted about this appliance being the destination of automatic migration, enter N.

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

      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.
    Wait until done is displayed on the CLI, indicating that the HA setup is successful on appliance B.
  10. On appliance A, perform the steps Step 2 to Step 7.
  11. After the upgrade process completes successfully on appliance A, set up the HA configuration on appliance B by performing the following steps:
    1. Open 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. Follow the prompts. Make sure you type save when prompted. The following example IP addresses are as noted at the beginning of this section:

      Public IP address of the cluster: 
 

      10.20.0.46 255.255.255.0 10.20.0.255 bond0
      When prompted about this appliance being the destination of automatic migration, enter Y.

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

    Wait until done is displayed on the CLI, indicating that the HA setup is successful on appliance A.

Result

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

What to do next

After upgrade is successful, 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 HA mode, you can enable the Advanced Features only from the CLI on the active appliance.
Next topic: Recovering from Failed Migration
Previous topic: Running the Postupgrade Script