Preparing to Upgrade the Appliance

Before starting the upgrade process, ensure that you have met the following requirements:

• Fulfill software and hardware requirements
• Verify disk space requirements
• Back up the appliance data
• Apply Hotfixes
• Configure Parameters
• Disable file system checks
• Download and extract the upgrade package
• Extract and run the health check script

Fulfill software and hardware requirements

Ensure that you fulfill the following requirements:

• Software download access to the eDelivery website or TIBCO Support site.

  If you do not have access, register at TIBCO Support site or contact Technical Support by email.

• Check which TIBCO LogLogic® Log Source Packages releases are compatible with LogLogic LMI. If the appliance is using an earlier version of LogLogic LSP, you must first upgrade to one of the supported LogLogic® LSP versions of the LogLogic LMI release to which you want to upgrade. See the LogLogic LMI-LogLogic LSP upgrade matrix in TIBCO LogLogic® Log Management Intelligence Release Notes.

  The LogLogic LSP documentation is available on the eDelivery website or TIBCO Support site after logging in.

• A null modem cable (if connecting to the appliance by using a console)

Verify disk space requirements

Verify that the appliance has sufficient available disk space to perform the upgrade:

1. Log in to the appliance through SSH and type the command: df -h.
2. Look at the available space under the Available column.

The available disk space for the following partitions must be:

• “/” partition: 100MB
• “/loglogic” partition: 10GB

Back up the appliance data

It is strongly recommended that you back up your data on the appliance before performing an upgrade.

You must wait at least one day after a software upgrade before performing a backup, otherwise the backed up log data is inconsistent with the platform software.

For more information, see the Backup and Restore section in the TIBCO LogLogic® Log Management Intelligence Administration Guide.

Apply Hotfixes

Apply the appropriate hotfixes:

Configure parameters

• Before starting the upgrade to version 6.2.1 or later, you must change the default value (public) of the Inbound Polling Community String field to any other string.
• Before upgrading to LogLogic LMI 6.1.0 or later, the CPU and memory of TIBCO LogLogic® Enterprise Virtual Appliance must be changed to match the minimum hardware requirements of LogLogic LMI. For more information, see the TIBCO LogLogic® Log Management Intelligence Enterprise Virtual Appliance Quick Start Guide.

Disable file system checks

Download and extract the upgrade package

Log in to the eDelivery website or TIBCO Support site and download the latest software update that you want to apply to the appliance.

1. Download the update package (in .tar format), TIB_loglmi_<version>_fileupgrade.tar
2. Connect to the appliance from the shell login as the toor user and the password that was created during Setting up the Appliance by Using the Console. Use the command line through the serial port with a null modem cable or by using SSH. It is recommended to use the serial port; by using SSH, the connection is lost after the final reboot but only temporarily.
3. Run the following command to extract all files into the destination directory /loglogic/update on the appliance:

   $ tar xf <filepath_update_package> -C /loglogic/update

   The package contains the following files:

   File name	Description
   bz2	The update file
   bz2.sig	The signature file for the upgrade file
   healthcheck.tar.gz	The health check utility tool
   mc-metadata	Files related to LogLogic® Management Center (required for upgrading LogLogic LMI versions by using LogLogic® Management Center)

   The bz2 and bz2.sig files are required to perform file update process.

Extract and run the health check script

$ tar zxvf <filepath_healthcheck_package> -C /loglogic/update

/loglogic/update/healthcheck/healthcheck.tar.gz

/loglogic/update/healthcheck/healthcheck.sh

Health Check Items

Scenarios when the health check script might fail and the workaround in each scenario are as follows:

use logappconfig
alter table oddsfieldtags drop FOREIGN KEY oddsfieldtags_ibfk_1;
alter table oddsfieldtags drop index msgPatternId;
alter table oddsfieldtags add index oddsfieldtags_ibfk_1(msgPatternId);
alter table oddsfieldtags add constraint oddsfieldtags_ibfk_1 FOREIGN KEY (msgPatternId) REFERENCES oddsmessagepattern(uuid) ON DELETE CASCADE;