Upgrading in an AWS Environment

In an AWS environment, you can upgrade LogLogic EVA from version 6.3.0 or 6.3.1 to version 6.4.0 by running a cross-version migration script.

Before you begin

Before you start the upgrade procedure, you must meet the following requirements:

  1. Deploy a new instance of LogLogic EVA 6.4.0 in AWS. LogLogic LSP 36.1.0 is automatically installed with it.

    For instructions, see the Deploying LogLogic EVA on AWS section in TIBCO LogLogic® Enterprise Virtual Appliance Quick Start.

  2. The status of the following Advanced Features options (enabled or disabled) on the source instance and the new 6.4.0 instance must be identical:
    • Advanced Features
    • Advanced Aggregation
    • Monitoring Console
  3. The version of LogLogic LSP on both LogLogic EVA instances must be identical. Therefore, on your existing LogLogic EVA instance, you must upgrade the LogLogic LSP to version 36.1.0, because LogLogic EVA 6.4.0 is compatible with LogLogic LSP 36.1.0.

    For instructions about upgrading LogLogic LSP, see TIBCO LogLogic® Log Source Packages 36.1.0 Installation and Upgrade.

Perform the following procedure on the source LogLogic EVA instance (version 6.3.0 or 6.3.1) and the destination LogLogic EVA (6.4.0) instance - as indicated.
    Procedure
  1. On the destination instance:
    1. Log in as the toor user.
    2. Extract the SSH public key from the file /root/.ssh/id_rsa.pub and display it on the console by running the following command: 
      $ cat /root/.ssh/id_rsa.pub
    3. Copy the SSH public key displayed on the console.
  2. On the source instance:
    1. Log in as the toor user.
    2. Ensure that the file /root/.ssh/authorized_keys exists. If not, create the file by running the following commands: 
      $ touch /root/.ssh/authorized_keys
$ chmod 600 /root/.ssh/authorized_keys
    3. Insert the SSH public key of the destination instance (from step 1b) into the /root/.ssh/authorized_keys file by running the following command: 
      $ echo 'SSH_public_key' >> /root/.ssh/authorized_keys

      where SSH_public_key is the SSH public key from step 1b.

    4. Insert the SSH public key of the source instance into the /root/.ssh/authorized_keys file by running the following command: 
      $ cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys
  3. On the destination instance:
    1. Log in as the toor user.
    2. Run the following migration script: 
      $ /loglogic/scripts/crossversion_migration/migrate.sh -v <source_version> -s <IP_address_source_instance>

      where:

      • <source_version> can be either v630 or v631.
      • <IP_address_source_instance> must be the IP address of the source instance.

      For example: 

      $ /loglogic/scripts/crossversion_migration/migrate.sh -v v631 -s 192.0.2.4
    3. After the destination appliance reboots, remove the old finger print of the destination instance by running the following command:
      $ ssh-keygen -f ~/.ssh/known_hosts -R <address_to_destination_instance>
    4. Log in as the toor user.
ResultAll data and configuration settings from the source instance are migrated to the LogLogic EVA 6.4.0 destination instance.

The password of the 6.4.0 appliance GUI is set identical to the password of the source appliance. However, the password of the toor user remains unchanged after migration.