Configuration and Upgrade Guide

TIBCO LogLogic® Log Management Intelligence

TIBCO LogLogic® Enterprise Virtual Appliance

Software Release 6.2 March 2018

Two-Second Advantage® 2

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDER SEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH, THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITH TIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES, AND INDEMNITIES. DOWNLOAD AND USE THESE ITEMS IS SOLELY AT YOUR OWN DISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDING TO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THE FOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, the TIBCO logo, Two-Second Advantage, TIB, Information Bus, Rendezvous, and TIBCO Rendezvous are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright © 2002-2018 TIBCO Software Inc. All rights reserved.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 3

Contents

TIBCO Documentation and Support Services ...... 4 Appliance Software Configuration ...... 5 Setting Up the Appliance with a Browser ...... 5 Connecting the Appliance to a Network ...... 5 Logging in to the Appliance ...... 5 Configuring Network Settings ...... 6 Setting the Time Zone and Time ...... 6 Setting up the Appliance Using the Console ...... 7 Appliance Software Upgrade ...... 9 IMPORTANT: Upgrade Warnings ...... 9 LogLogic LSP Support ...... 10 Updating the Appliance ...... 10 Updating the TIBCO LogLogic® Appliance Using File Update ...... 10 Running the Post Upgrade Script ...... 12 Upgrading in a High Availability Environment ...... 13 Recovering from Failed Migration ...... 17 Recovering the stDataFiles table using Scripts ...... 17

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 4

TIBCO Documentation and Support Services

How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly in HTML and PDF formats. The TIBCO Product Documentation website is updated frequently and is more current than any other documentation included with the product. To access the latest documentation, visit https:// docs.tibco.com.

Product-Specific Documentation

The following documents for this product can be found on the TIBCO Documentation site on the ® TIBCO LogLogic documentation page:

® ● TIBCO LogLogic Log Management Intelligence Release Notes ® ● TIBCO LogLogic Log Management Intelligence Administration Guide ® ● TIBCO LogLogic Log Management Intelligence Configuration and Upgrade Guide ® ● TIBCO LogLogic Log Management Intelligence Enterprise Virtual Appliance Quick Start Guide ® ● TIBCO LogLogic Log Management Intelligence Hardware Installation Guide ® ● TIBCO LogLogic Log Management Intelligence Log Source Report Mapping Guide ® ● TIBCO LogLogic Log Management Intelligence SSD Hardware Field Installation Guide ® ● TIBCO LogLogic Log Management Intelligence Syslog Alert Message Format Quick Reference Guide ® ● TIBCO LogLogic Log Management Intelligence User Guide ® ● TIBCO LogLogic Log Management Intelligence Web Services API Implementation Guide ® ● TIBCO LogLogic Log Management Intelligence XML Import/Export Entities Reference Guide

How to Contact TIBCO Support

You can contact TIBCO Support in the following ways:

● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

● For accessing the Support Knowledge Base and getting personalized content about products you are interested in, visit the TIBCO Support portal at https://support.tibco.com.

● For creating a Support case, you must have a valid maintenance or support contract with TIBCO. You also need a user name and password to log in to https://support.tibco.com. If you do not have a user name, you can request one by clicking Register on the website.

How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matter experts to share and access their collective experience. TIBCO Community offers access to Q&A forums, product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, and tools that extend and enable customers to gain full value from TIBCO products. In addition, users can submit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to https://community.tibco.com.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 5

Appliance Software Configuration

® After you install the new TIBCO LogLogic appliance in its rack and power it up, set up the appliance either using the GUI via a web browser, or using the CLI via a console connection. Once the appliance is running, you want to configure it for your specific needs. For more information, ® ® see the TIBCO LogLogic Log Management Intelligence User Guide or TIBCO LogLogic Log Management Intelligence Administration Guide. To upgrade an existing appliance, see Appliance Software Upgrade. LogLogic LMI H4, H4R1, and H4R2 appliances come with an embedded SD card that contains an image of the appliance software. This new feature facilitates re-imaging the appliance in case of critical hardware or software failure. For instructions on how to use the backup image for recovery, please contact TIBCO support through the online support portal at: https://support.tibco.com or through email: [email protected]. By default on H4, H4R1, and H4R2 LogLogic LMI appliances, the labeled iDRAC network interface will have an assigned static address, for example https:// or https://. By connecting the iDRAC network interface to a network infrastructure, the iDRAC web interface will become available via HTTPS, at https://192.168.0.120 as well as telnet and SSH to the same default IP. Setting Up the Appliance with a Browser ® You must follow a series of steps to set up a TIBCO LogLogic appliance using a browser.

1. Connecting the Appliance to a Network 2. Logging in to the Appliance 3. Configuring Network Settings 4. Setting the Time Zone and Time

Connecting the Appliance to a Network

Procedure

● Connect the appliance to a network where you can access a 10.0.0.x network address using a class “C” subnet mask (255.255.255.0).

The appliance’s default IP address is 10.0.0.11, which is assigned to the Eth0 port.

Logging in to the Appliance

Procedure

1. Open an Internet browser on your workstation and connect to the appliance by entering https:// 10.0.0.11 in the browser address line. 2. Accept the certificate. A login screen appears.

3. Enter the default user name (admin) and password (admin). The appliance displays the End User License Agreement (EULA).

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 6

4. Accept the EULA. The appliance asks you to enter a new password, which must be at least six characters long and contain at least one number. 5. Enter a new password.

What to do next

A warning message may be displayed indicating the time on the appliance is not set or synchronized. You can ignore this warning. For more information, see Setting the Time Zone and Time. It is good practice to also create a secondary administrative account. You can do this now or later.

® ● To add more user accounts, see the Managing Users section in the TIBCO LogLogic Log Management Intelligence Administration Guide. ® ● To change the admin password later, see the Setting User Preferences section in the TIBCO LogLogic Log Management Intelligence User Guide.

Configuring Network Settings

® For more information on network settings, see the Network Settings section in the TIBCO LogLogic Log Management Intelligence Administration Guide.

Procedure

1. Select the Administration > Network Settings menu. 2. Type in the appropriate network information, and then click Save.

Setting the Time Zone and Time You must set the time zone for your appliance, so that the system functions correctly.

Procedure

1. From Administration > System Settings , select the Time tab. 2. Select the appropriate Time Zone from the Time Zone drop-down menu. 3. Select Update Time to define how to synchronize your local time. 4. Select how to update the appliance time:

● (Recommended) Select NTP Server to enter a Hostname or IP address for your NTP server. This is the time server with which you want to synchronize your local time.

— If you have multiple appliances connected together, you must set up a common external NTP server for all appliances to ensure that the time on all appliances is synchronized. Ideally, this is the same NTP server used by the entire data center.

— If you have no access to an external NTP server, you can use the appliance running as a Management Station as the common NTP server. All appliances must have their time settings in sync.

— It is important to have an NTP server set up for a single appliance as well.

● Select Specify Time and manually enter the system time (MMDDhhmmYY.ss).

You must set the time for your appliance. If not, the system will not function correctly.

5. Click Update to save your changes. The appliance prompts you that an immediate reboot is required.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 7

6. Click OK to let the appliance reboot for changes to take effect. New settings do not go into effect until the appliance is restarted.

Setting up the Appliance Using the Console To set up a LogLogic appliance using the console, you will need the NULL modem cable shipped with the appliance, and compatible terminal software.

® For more information on CLI commands, see the TIBCO LogLogic Log Management Intelligence Administration Guide or type help at the command prompt.

Procedure

1. Using a laptop or other terminal device, connect the NULL modem cable to the serial port (COM1) located at the back of the appliance. 2. Open your terminal software. Use the following communication settings: 9600 baud, Null, 8 bit, 1 parity

3. In the terminal program, log in as user root with password logapp. If you are setting up the appliance for the first time, perform the next two steps. Otherwise, continue on to step 6. 4. When prompted to enter a new root password, re-enter the same password at the confirmation prompt. It is recommended to choose a suitable password based on the standard guidelines for strong password security, however the system will accept both weak and strong passwords. 5. When prompted enter a new toor password, then confirm your password. Please ensure that you make a note of your root and toor passwords and store them in a safe location. Lost passwords cannot be recovered.

At this point the toor account becomes available. 6. Configure the network settings: a) Set the appliance IP address and interface network settings: > set ip

If you are bonding two interfaces together, use interface-name to indicate bond0 or bond1. For example: > set ip 10.9.3.250 255.255.255.0 10.9.3.1 eth0

b) Set the DNS server IP address: > set dns

Example: > set dns 10.1.1.5

7. Set the local time zone. > set timezone From the displayed menu, select the time zone where this appliance is located. 8. Verify your settings: > show changes 9. Save your changes: > save

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 8

This updates the necessary files so that the network setting changes are permanent. New settings do not go into effect until the appliance is restarted.

10. Select the network interface defaultgw. 11. Select the IP address to use to generate the BlueCoat certificate: > 0 This will generate the BlueCoat certificate for the interface configured above. It is not necessary to select an interface for a BlueCoat certificate if you do not have any BlueCoat ProxySG device in your network, or if you do have BlueCoat ProxySG devices but you do not use LogLogic LMI to collect the logs from those devices. 12. View the new network settings to verify they are correct: > show current 13. Restart the network interface: > network restart 14. Check the network settings using the command: > show current 15. (Highly recommended) Set up an NTP server, using the IP address or DNS name of the NTP server: > set ntpserver 16. Either reboot or halt the appliance.

● To reboot the appliance, type: > system reboot

● To halt the appliance, type: > system halt

● Wait approximately 2 minutes for the appliance to cease operation before removing power.

● When powering down the appliance it is important to follow any of the proper shutdown procedures: — The system halt command

— The standard Linux shutdown procedure

— Reboot commands Failure to comply could cause a corrupted file system, loss of data, or a failure to boot the appliance.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 9

Appliance Software Upgrade

You can upgrade to Release 6.2.0 from Release 6.1.0 or 6.1.1. Before upgrading, you must run the health check package. After upgrading, you must run the Post Upgrade Script rundbm, which is under the /loglogic/bin/ directory. If you do not run the Post Upgrade Script, you might lose some of the reports data. ® For information about a specific release, see the TIBCO LogLogic Log Management Intelligence Release Notes for that release. IMPORTANT: Upgrade Warnings Please read all these warnings before upgrading to Release 6.2.0. You must wait at least 1 day after a software upgrade before performing a backup, otherwise the backed up log data will be inconsistent with the platform software.

● It is strongly recommended that you back up your data prior to performing an upgrade. ® ● If you are upgrading a High Availability (HA) setup to TIBCO LogLogic Log Management ® Intelligence version 6.2.0 using TIBCO LogLogic Management Center version 2.1.1, you must apply ® the following hotfixes before starting the LogLogic LMI upgrade process:

— MC 2.1.1-HF-LLCE-2322-2469

— LMI HF LMI-6.1.0_5.7.0_5.6.3_5.6.2-HF-MCAgent-2317-2357: required when upgrading from ® LogLogic LMI version 6.1.0 to version 6.2.0 For more information on these hotfixes, see the corresponding hotfix ReadMe files.

● To properly forward CheckPoint data, you must update both your inbound and outbound devices to the same release. ® ● If the existing installation is using an earlier version of TIBCO LogLogic Log Source Packages, it is ® required to first upgrade to one of the supported LogLogic LSP versions of the release to which you want to upgrade to. For the upgrade matrix, refer to the LogLogic LMI - LogLogic LSP matrix in ® the TIBCO LogLogic Log Management Intelligence Release Notes.

● The Post Upgrade Script must be run on LX, MX, ST, and LogLogic EVA appliances after upgrading.

● Starting from release 5.3.1, when scheduling a replay, if you select Authentication and Encryption options, type the CLI command system keycopy on the ST appliance and follow the instructions displayed on the screen to add the public key to the LX appliance.

● Starting from release 5.4, the Show Triggered Alerts page may not display the original alert message

even after you disable the Data Privacy mode using the lock icon for the current user session. However, if you turn off the Data Privacy option using the Administration > System Settings > General tab, the original alert message will be displayed on the Show Triggered Alerts page.

● 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.

— To prevent running a file system check during upgrade, run the CLI command system fsck disable. After the upgrade process is complete, run the CLI command system fsck enable to re-enable the check if needed. For more information on the fsck command, see the TIBCO ® LogLogic Log Management Intelligence Administration Guide.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 10

LogLogic LSP Support For details about which LogLogic LSP releases are compatible with the LogLogic appliance software ® releases, refer to the LogLogic LMI-LogLogic LSP upgrade matrix in TIBCO LogLogic Log Management Intelligence Release Notes.

Updating the Appliance You can upgrade appliance software through the appliance user interface.

Procedure

1. File Update—Download the update package (in .tar format) from the TIBCO Software Product Download website or TIBCO Support website, and use the following command to extract all files into the destination directory /loglogic/update on the appliance: $ tar xf -C /loglogic/update The following section describes the extracted files:

Update Package Details

Files Description

bz2 The update file.

bz2.sig The signature file for the upgrade file.

healthcheck.tar.gz The healthcheck utility tool.

® mc-metadata Files related to the LogLogic Management Center software (required for upgrading LogLogic LMI versions using the ® LogLogic Management Center software).

2. Extract the contents of the .gz archive using the gunzip command:

$ gunzip 3. Healthcheck—Ensure that the appliance is ready for upgrade by running the Healthcheck package before the upgrade. Use the following command to extract the package contents: $ tar xf -C /loglogic/update

where, is the correct file path. See step 5 in the section Updating the TIBCO LogLogic® Appliance Using File Update.

Do not install the Healthcheck package under the /loglogic/tmp folder.

Result

After the Healthcheck is successful, the appliance is ready for an upgrade.

Updating the TIBCO LogLogic® Appliance Using File Update The bz2 and bz2.sig files are required to perform file update process.

Prerequisites

To extract these files, follow the process as explained in the File Update section. To complete the upgrade process using File Update, you must have:

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 11

● Software download access to the TIBCO Software Product Download website or https:// support.tibco.com (if you do not have access, register at https://support.tibco.com or contact Technical Support by email or phone)

● The available disk space for the following partitions:

— “/” partition: 100MB

— “/loglogic” partition: 3GB

● Null modem cable (if connecting to the appliance using a console)

Procedure

® 1. Back up the data on the TIBCO LogLogic appliance. For more information on backing up your ® data, see the TIBCO LogLogic Log Management Intelligence Administration Guide. 2. Log in to the TIBCO Support website https://support.tibco.com, and then download the latest software update that you want to apply to the appliance. 3. Verify that the appliance has sufficient available disk space to perform the upgrade (see the disk space requirement for partitions explained previously): a) Log in to the appliance using SSH and type the command: df -h. b) Look at the available space under the Available column. 4. Connect to the LogLogic appliance from the CLI or shell login. Use the command line through the serial port with a null modem cable or using SSH. It is recommended to use the serial port; using SSH, the connection is lost after the final reboot.

The default user is toor, login using the toor password which was created during Setting up Appliance Using the Console. 5. Make sure that the system is ready for upgrade by running the healthcheck command healthcheck.sh with the correct path. For example: /loglogic/update/healthcheck/ healthcheck.sh

1. During this process, if system finds any inconsistencies, the console displays the message: Ignore the inconsistency?[yes/no]: Type no to stop the process and go back and fix the issue before you proceed. You can run the healthcheck command multiple times until you fix all inconsistencies. If you type yes, all inconsistencies will be ignored and you can proceed. 2. During this process, the console may prompt the following message to warn you about unconverted report data from previous upgrade process: There is report data on the system that was not converted after the last upgrade. Do you want to convert this data now? [yes/no]:Type yes to exit the healthcheck command at this point and run the rundbm command to complete the post-upgrade process from the previous upgrade. Otherwise, type no to ignore this warning and proceed. 3. During this process, the healthcheck may fail with the following error, Schema consistency checking failed. If this occurs use the following workaround. In mysql: 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;

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 12

® 6. Log in to the TIBCO LogLogic appliance you want to upgrade. You must log in as a user with Administrator privileges. 7. In the navigation menu, click Administration > File Update . The File Update tab is displayed. 8. From the Select File drop-down menu, select the appropriate software update. If you do not see any files in the list, verify that the update files are added to the /loglogic/update directory. 9. Click Update. A status message appears at the top of the File Update tab after the update is complete. 10. After the appliance reboots, run the Post Upgrade script.

11. (Optional) If you want to update the SSL signature algorithm to sha2, run the script: /loglogic/ tomcat/conf/cert_utils/certgen.sh.

Result

A message displayed on the webpage informs you that the update is in progress. When the process completes, you are redirected to the Login page. The new software release number will be displayed on the top right corner of the System Status page.

Running the Post Upgrade Script After you upgrade an appliance to a new software release and the appliance reboots, you must run the Post Upgrade Script, rundbm. If the post upgrade script is not run during the upgrade procedure, some of the parsed reports data might be lost. The affected report types are different from one LogLogic LMI version to another.

Procedure

1. Log in to the appliance via SSH, using the toor user. 2. Go to the CLI scripts directory: $ cd /loglogic/bin 3. Run the Post Upgrade Script: $ ./rundbm The configuration menu appears, as follows: Configuration Menu: 1) Modify the above configuration 2) Start the Post Upgrade Process 3) Check system tables integrity 4) Help 5) Exit the Post Upgrade Process

Enter choice: 4. The modify configuration menu appears. The following example menu is typical: 1) module_5410000_wwwlog 2) module_5410000_i5OSAudit 3) module_5410000_stats 4) module_5410000_ids 5) Return to Configuration Menu 6) Help Enter 1-6:

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 13

Your menu items will depend on your appliance configuration. If there is no data to be converted, your menu might appear as follows: 1) Return to Configuration Menu 2) Help Enter 1-2: 5. Change the number of days to preserve for any of these logs that should not be set to seven days. For example, for BlueCoat: a) Type 1. b) Specify if you want to change the default value. If you type y, then enter the amount of pre- existing BlueCoat/wwwlog data, in days, that you want accessible on the appliance after the upgrade. For example, if you want access to the past month’s BlueCoat data, enter 31. The default setting is 7, which converts the previous week. The higher number of days you enter, the longer the post-upgrade process takes to complete. To preserve the ability to search on all log data collected from BlueCoat log sources, input a number of days to include the first collection of BlueCoat log information. After entering the number of days, the module configuration menu appears again. 6. You must repeat step 5 for each option. 7. Type 5 to go back to Configuration Menu. 8. Type 2 to start the Post Upgrade Process on Appliance A. The conversion time for the Post Upgrade Process depends on the amount of data to be migrated. 9. After typing 2 to start the Post Upgrade Process, the appliance returns you to the configuration menu immediately, with the additional option, Monitor the Post Upgrade Process — see choice 6) in step 10. 10. Type 6 to monitor the Post Upgrade Process. The configuration menu appears: 1) Modify the above configuration 2) Start the Post Upgrade Process 3) Check system tables integrity 4) Help 5) Exit the Post Upgrade Process 6) Monitor the Post Upgrade Process

By typing 6, you can monitor the Post Upgrade Process. Press Ctrl+C to exit. The screen then returns to the Configuration Menu. When you see the following message during monitoring, the Post Upgrade Process is complete. 2014-10-11 20:10:37,818 - dbmLogger - INFO: ** All migrations complete! 11. Type 3 to check the integrity of system tables. The configuration menu appears: 1) Check stDataFiles integrity 2) Return to Configuration Menu Enter 1 or 2:

Type 1 to check the integrity of stDataFiles and check the console output. If there is any error or exception on the console output, follow the console instructions to check the log files and recover tables as per Recovering from Failed Migration. 12. Type 5 to exit the post-upgrade script.

Upgrading in a High Availability Environment The process of upgrading your appliances in a High Availability (HA) appliance environment is different. ® For details 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.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 14

● Both HA appliances must have the same hardware model and software version.

● Validate the disk requirements, as described in File Update.

● Load and extract the upgrade files, as described in Updating the Appliance

● The Active and Standby Appliances must be in sync. Ensure that there are no warning messages that appear on the Dashboards > System Status page.

If the HA cluster was configured with the archive feature, disable it before the upgrade process. The log data collected between step 2 and step 9 on appliance A will be ignored at step 17 during initialization and syncing. 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 will always be referred to as “Appliance A” and the original standby appliance will always be referred to as “Appliance B” (even though their roles will reverse and then revert). At step 10 in the upgrade process, Appliance B will become the active appliance temporarily, and Appliance A will become the standby appliance temporarily. At the conclusion of the upgrade process, the roles of the two appliances will revert back to their original assignments, although that is not necessary for successful HA operation. This HA upgrade procedure uses the following example appliance information:

● Appliance A: HA Active, IP address 10.20.0.44

● Appliance B: HA Standby, IP address 10.20.0.45

● Public: HA Public, IP address 10.20.0.46

● Network Mask, IP address 255.255.255.0

● Network Broadcast, IP address 10.20.0.255

Procedure

1. Ensure that your HA environment is synchronized. 2. On the Appliance B, disable the HA configuration. a) Open a command prompt and log in using username: root and type the password. b) Run the following command: set failover disable

The prompt returns CHANGES HAVE NOT BEEN SAVED!. c) Type save and then press enter. 3. Install the correct LogLogic LSP version based on LogLogic LSP - LogLogic LMI support matrix for the target LogLogic LMI software. 4. Make sure that the system is ready for upgrade by running the healthcheck command healthcheck.sh with the correct path. For example: /loglogic/update/healthcheck/healthcheck.sh

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 15

5. 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 to copy:

● update--full.tar.bz2

● update--full.tar.bz2.sig 6. Log in to Appliance B and complete the update. a) Open a web browser and log in to the Appliance B. b) In the navigation menu, click Administration > File Update . c) The update--full.tar.bz2 is displayed in the Select File box. d) Click the Update button. You might need to wait about 30 - 40 minutes for the update to complete. 7. After you upgrade Appliance B and the appliance reboots, you must run the Post Upgrade Script. For post upgrade steps, follow the steps as described in Running the Post Upgrade Script.

8. (Optional) If you want to update the SSL signature algorithm to sha2, run the script: /loglogic/ tomcat/conf/cert_utils/certgen.sh. 9. On the Appliance A, disable the HA configuration. a) Open a command prompt and log in using username: root and type the password. b) Run the following command: set failover disable

The prompt returns CHANGES HAVE NOT BEEN SAVED! c) Type save and then press enter. 10. On Appliance B, set up the HA configuration. a) Open a command prompt and log in using username: root and type the password. b) Run the following command: set failover configure

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 16

c) 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: 10.20.0.44 At this point Appliance B has become the active appliance. Appliance A is no longer part of the HA pair, and thus is reported “missing” by Appliance B. If the HA cluster was configured with the archive feature, disable it before the upgrade process. 11. Install the correct LogLogic LSP version based on LogLogic LSP - LogLogic LMI support matrix for the target LogLogic LMI software.

Both Appliance A and Appliance B should now be on the same LogLogic LSP version.

12. On Appliance A, make sure that the system is ready for upgrade by running the healthcheck command healthcheck.sh with the correct path. For example: /loglogic/update/healthcheck/healthcheck.sh

13. Make sure that the update files (bz2 and bz2.sig) are downloaded and are available in the / loglogic/update directory on the Appliance A. For details of the upgrade matrix, see TIBCO ® LogLogic Log Management Intelligence Release Notes. The following files are examples of the update files that you need to copy:

● update--full.tar.bz2

● update--full.tar.bz2.sig 14. Log in to Appliance A and complete the update. a) Open a web browser and log in to Appliance A.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 17

b) In the navigation menu, click Administration > File Update . The update--full.tar.bz2 is displayed in the Select File box. c) Click Update. You might need to wait 30 - 40 minutes for the update to complete. 15. After you upgrade Appliance A and the appliance reboots, you must run the Post Upgrade Script. For post upgrade steps, follow the steps as described in Running the Post Upgrade Script. You must let Appliance A complete the upgrade process before syncing up with Appliance B.

16. (Optional) If you want to update the SSL signature algorithm to sha2, run the script: /loglogic/ tomcat/conf/cert_utils/certgen.sh. 17. On the Appliance A, set up the HA configuration. a) Open a command prompt and log in using username: root and type the password. b) Run the following command: set failover configure c) 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: 10.20.0.45 18. If the HA cluster was configured with the archive feature and you disabled it before the upgrade process (in step 9), re-enable it now.

Result

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

● Forcing failovers for the purpose of keeping one particular appliance “active” is not recommended, because it has no particular benefit and any failover event has the potential to cause some loss of data.

● After the upgrade is successful, in HA mode, you can enable Advanced Features and Monthly Index only through the CLI on the master node.

Recovering from Failed Migration Starting with release 6.1.0, LogLogic LMI provides a way to recover stDataFiles and indexFiles tables if a failure occurs during the upgrade process. Some data from these tables might be lost during the recovery process, because restore operations can only guarantee the integrity of the system up to the last backed up state. For the stDataFiles table, LogLogic LMI tries to recover missing records along with next system cleansing process. However, for the indexFiles table, there is no way to recover missing records. To retry migration after a migration failure, perform the following steps:

Recovering the stDataFiles table using Scripts

To improve performance and storage efficiency on queries, the stDataFiles table is partitioned. The partitioning is performed during a new installation as well as when upgrading to LogLogic LMI 6.2.0. It is possible to recover stDataFiles table if the partitioning fails during the upgrade process.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide 18

Procedure

1. To restore stDataFiles backup, run the command: /loglogic/scripts/dbPartitioner/revert_stDataFiles_Partition 2. To run the partition process again, run the command: /loglogic/scripts/dbPartitioner/build_partition This command is executed during the upgrade process and must not be run manually unless there an exception in the normal flow. 3. To remove the backup table that is created during partitioning, run the command:. /loglogic/scripts/dbPartitioner/remove_stDataFiles_logical_backup

After this command is executed, there is no way to restore stDataFiles to its state before the partitioning started.

TIBCO LogLogic® Log Management Intelligence Configuration and Upgrade Guide