TIBCO LogLogic® Log Management Intelligence (LMI) Configuration and Upgrade Guide

(1)

TIBCO LogLogic®

Log Management Intelligence (LMI) Configuration and Upgrade Guide

Software Release 5.7.0 July 2016

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

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, Two-Second Advantage, and LogLogic 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.

TIBCO Software Inc. Confidential Information

(3)

Contents

|

ⁱⁱⁱ

Preface

The TIBCO LogLogic® Appliance-based solution enables you to capture and manage log data from all types of sources in your enterprise. TIBCO LogLogic Appliances install within 10 minutes and begin collecting and aggregating data from connected log sources immediately.

This document enables you to quickly set up your TIBCO LogLogic Appliance, and provides Software Upgrade instructions and descriptions of the Appliance hardware configurations.

Topics

• Related Documents, page vi

• Typographical Conventions, page vii

• Connecting with TIBCO Resources, page ix

(6)

vi

|

^vii

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled:

MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets.

Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommandPathName

Key

combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example:

Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other.

For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

(8)

viii

|

Typographical Conventions

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use

(9)

Preface

|

^ix

Connecting with TIBCO Resources

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO

community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access TIBCO Documentation

Documentation for this and other TIBCO products is available on the TIBCO Documentation site:

https://docs.tibco.com

Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, visit us at https://docs.tibco.com.

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support as follows:

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.

(10)

x

|

Connecting with TIBCO Resources

(11)

|

¹

Chapter 1 Appliance Software Configuration

After you install the new TIBCO LogLogic Appliance in its rack and it has power, set it up as described in this chapter. You can set up the Appliance either using the user interface via a web browser, or using the command line interface via a console connection.

Once the Appliance is running, you want to configure it for your specific needs. For more information, see the LogLogic User Guide or LogLogic Administration Guide.

To upgrade an existing Appliance, see Appliance Software Upgrade on page 9.

TIBCO LogLogic H4 Appliances come with an embedded SD card that contains an image of the Appliance software. This new feature facilitates reimaging the Appliance in case of critical hardware or software failure. For instructions on how to use the backup image for recovery, please contact TIBCO LogLogic support through the online support portal at:

https://support.tibco.com or through email: [email protected].

Topics

• Setting Up the Appliance with a Browser, page 2

• Setting Up the Appliance using the Console, page 5

By default on H4 LogLogic Appliances, the labeled iDRAC network interface will have an assigned static address, for example https://<IPv4address> or https://<IPv6Address>. 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.

(12)

2

|

Chapter 1 Appliance Software Configuration

Setting Up the Appliance with a Browser

To set up a LogLogic Appliance using the browser:

• Task A, Connecting the Appliance to a Network, page 2

• Task B, Logging in to the Appliance, page 2

• Task C, Configuring Log Source Auto-Identification, page 3

• Task D, Configuring Network Settings, page 3

• Task E, Setting the Time Zone and Time, page 3

Task A Connecting the Appliance to a Network

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

Task B Logging in to the Appliance To log in to the Appliance

1. Open 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).

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.

LogLogic recommends that you also create a secondary administrative account. You can do this now or later. To add more user accounts, see the Managing Users chapter in the LogLogic Administration Guide.

The Appliance’s Default IP Address is 10.0.0.11, which is assigned to the Eth0 port.

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 Task E, Setting the Time Zone and Time, page 3.

(13)

Setting Up the Appliance with a Browser

|

³

To change the admin password later, see the Setting User Preferences chapter in the LogLogic User Guide.

Task C Configuring Log Source Auto-Identification

1. From Administration > System Settings, opens the General tab.

2. Next to Auto-identify Log Sources, click Yes.

3. Click Update.

Task D Configuring Network Settings

1. Select the Administration > Network Settings menu.

2. Type in the appropriate network information, and then click Save.

3. For more information on network settings, see the Network Settings chapter in the LogLogic Administration Guide.

Task E Setting the Time Zone and Time

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.

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

(14)

4

|

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

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

6. Click OK to let the Appliance reboot for changes to take effect.

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

New settings do not go into effect until the Appliance is restarted.

(15)

Setting Up the Appliance using the Console

|

⁵

Setting Up the Appliance using the Console

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

Using the Console to Set Up the Appliance

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.

4. When prompted enter a new root password, then at the confirmation prompt re-enter the same password.

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.

At this point the toor account will become available.

For more information on CLI commands, see the LogLogic Administration Guide or type help at the command prompt.

The next two steps are only necessary when you are setting up the Appliance for the first time, if not then continue on to step 6.

Please ensure that you make a note of your root and toor passwords and store them in a safe location. Lost passwords can not be recovered.

(16)

6

|

6. Configure the network settings:

a. Set the Appliance IP address and interface network settings:

> set ip <ip address> <netmask> <gateway> <ifdev> [defaultgw]

If you are bonding two interfaces together, use interface-name to indicate bond0 or bond1.

Example:

> set ip 10.9.3.250 255.255.255.0 10.9.3.1 eth0 defaultgw b. Set the DNS server IP address:

> set dns <ip address>

Example:

> set dns 10.1.1.5 7. Set the local time zone.

> set timezone <Enter>

From the displayed menu, select the time zone where this Appliance is located.

8. Verify your settings:

> show changes 9. Save your changes:

> save

This updates the necessary files so that the network setting changes are permanent.

10. Select the network interface as the 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.

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:

New settings do not go into effect until the Appliance is restarted.

(17)

Setting Up the Appliance using the Console

|

⁷

> show current

15. (Highly recommended) Set up an NTP server, using the IP address or DNS name of the NTP server:

> set ntpserver <ip address>

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 a proper shutdown procedure. Failure to comply could cause a corrupted file system, loss of data or a failure to boot the Appliance.

(18)

8

|

(19)

|

⁹

Chapter 2 Appliance Software Upgrade

You can upgrade from Release 5.5.1with HF1, 5.6.0, 5.6.1, 5.6.2 to Release 5.6.3. After upgrading you must run the Post Upgrade Script rundbm which is under

/loglogic/bin/ directory. If you do not run the Post Upgrade Script, you will lose some of the reports data.

For information about a specific release, see the TIBCO LogLogic Log Management Intelligence (LMI) Release Notes for that release.

Topics

• IMPORTANT: Upgrade Warnings on page 10

• LMI/LSP Upgrade Support, page 11

• Upgrading in a High Availability Environment, page 18

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

(20)

10

|

Chapter 2 Appliance Software Upgrade

IMPORTANT: Upgrade Warnings

• For Enterprise Virtual Appliance (EVA) users upgrading from versions 5.4.0, 5.4.1 and 5.4.2, the virtual machine's guest OS type has to be changed to "Red Hat Enterprise Linux 5 (64-bit)" before upgrade can happen. The guest OS type can be changed by using VMware vSphere client:

a. Shutdown the EVA instance.

b. Open the VM setting editing window and right-click the VM and select the Edit setting option.

c. In the editing window click the Options tag.

d. In the Guest Operation System section select Red Hat Enterprise Linux 5 (64-bit) and click OK.

Users can now safely perform the 5.6.x upgrade.

• TIBCO LogLogic strongly recommends that you back up your data prior to performing an upgrade.

• To properly forward Check Point data, you must update both your inbound and outbound devices to the same release.

• If the source install is using an earlier version of LSP, it is required to first upgrade to supported LSP versions of release you want to upgrade to, provided by LMI/LSP matrix

• The Post Upgrade Script MUST be run on LX, MX, and ST Appliances after upgrading.

• If upgrading from version 5.3 to any version up to 5.4.2, the message routing rules will have the following changes:

Authentication and Encryption cannot be selected separately starting from version 5.3.1. If either Authentication or Encryption was set, the Enable Authentication and Encryption setting will be set after upgrade.

Please read all these warnings before upgrading to Release 5.6.3.

The user must wait at least 1 day after a software upgrade before doing a backup, otherwise the backed up log data will be inconsistent with the platform software.

(21)

IMPORTANT: Upgrade Warnings

|

¹¹

The Authentication and Encryption option is not available when forwarding messages with the UDP protocol starting from version 5.3.1. For details, refer to the Chapter 12 - Forwarding Logs to Other Appliances (Routing) in the LogLogic Administration Guide.

For encrypted forwarding to be possible, the authentication is now performed using the SSH protocol. The toor user of the upstream appliance must be authorized to login via SSH to the downstream appliance without entering a password. For details, refer to the Chapter 12 - Forwarding Logs to Other Appliances (Routing) in the LogLogic Administration Guide.

• Starting from version 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 version 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 in the Show Triggered Alerts page.

• After upgrade to 5.6.1, the following mysql errors will appear in

/var/log/sys.log. These errors can be safely ignored as the system will automatically correct them.

— [ERROR] Missing system table mysql.proxies_priv...

— [ERROR] Native table 'performance_schema'...

Log Source Package (LSP) Support

For details about which LSPs are compatible with the LogLogic Appliance software releases, refer to the latest TIBCO LogLogic Log Management Intelligence (LMI) Release Notes.

LMI/LSP Upgrade Support

For the available upgrade matrix for LMI/LSP, refer to the latest TIBCO LogLogic Log Management Intelligence (LMI) Release Notes.

(22)

12

|

Updating the Appliance

TIBCO LogLogic provides Appliance software upgrades through the Appliance user interface:

1. File Update—Download the update package (in .tar format) from the TIBCO Software Product Download Site or LogLogic Support website and use 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 extracted files are described below:

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

$ gunzip <filepath_healthcheck_package>

3. Healthcheck—Ensure that the appliance is ready for upgrade by running the

Healthcheck package before the upgrade. Use the following command to uncompress the package:

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

where, <filepath_healthcheck_package> is the correct file path. See step 8. on page 13.

Depending on the nature of the update, the Appliance might automatically reboot.

Table 2 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 TIBCO LogLogic Management Center (MC) software (required for upgrading LMI versions using the MC software).

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

(23)

Updating the Appliance

|

¹³

Using File Update

The bz2 and bz2.sig files are required to perform file update process. To extract these files, follow the process explained in the File Update section above.

To complete the upgrade process using File Update, you must have:

• Software download access to the TIBCO Software Product Download Site 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)

• For the following partitions, the available disk space must be:

“/” partition – 300MB

“/loglogic” partition – 5GB

• Null modem cable (if connecting to the Appliance using a console)

To Update the LogLogic Appliance Using File Update

4. Back up the data on the LogLogic Appliance. For more information on backing up your data, see the LogLogic Administration Guide.

5. Log in to the TIBCO LogLogic support website

https://support.tibco.com, and then download the latest software update that you want to apply to the Appliance.

6. Ensure the Appliance has sufficient available disk space to perform the upgrade (see the disk space requirement for partitions above). To verify the available disk space:

a. Log in to the Appliance using SSH and type the command: df -h.

b. Look at the available space under the Available column.

7. Connect to the TIBCO LogLogic Appliance from the CLI or shell login. Use the command line through the serial port with a null modem cable or using SSH.

TIBCO LogLogic recommends using 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 Using the Console to Set Up the Appliance on page 5.

8. Make sure that the system is ready for upgrade by running the healthcheck command healthcheck.sh with the correct path.

For example: ./healthcheck/healthcheck.sh or,

(24)

14

|

9. Log in to the TIBCO LogLogic Appliance you want to upgrade. You must log in as a user with Administrator privileges.

10. In the navigation menu, click Administration > File Update.

The File Update tab displays.

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

12. Click Update.

A status message appears at the top of the File Update tab after the update is complete.

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.

During the upgrade process, prior to 5.1, some unused files are left that misleads the

healthcheck command to show this prompt. If the post-upgrade process has been run through and this prompt still shows, you should type no to ignore the 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;

(25)

Updating the Appliance

|

¹⁵

13. After the Appliance reboots, run the Post Upgrade script. See The upgrade is complete. Appliance B is active, and Appliance A is standby. on page 22.

A message displayed on the dashboard 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.

(26)

16

|

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.

1. Log in to the Appliance CLI via SSH.

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) Help

4) Exit the Post Upgrade Process Enter choice:

4. The modify configuration menu appears. The example menu that follows is typical;

your menu items will depend on your Appliance configuration.

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:

Post Upgrade in an HA pair should be performed only on the Appliance in the “active” role.

To upgrade from LMI 5.4.x release to LMI 5.6.3 user has to first upgrade to 5.5.1 and above versions and run the post upgrade script.

During the upgrade procedure if the post upgrade script is not performed then data will be lost.

(27)

Running the Post Upgrade Script

|

¹⁷

5. Change the number of days to preserve for any of these logs that should not be set to seven days. For example, for MS Exchange:

a. Type 1.

b. Specify if you want to change the default value. If you type y, then enter the amount of pre-existing MS Exchange/authentication data, in days, that you want accessible on the Appliance after the upgrade. For example, if you want access to the past month’s MS Exchange 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 MS Exchange log sources, input a number of days to include the first collection of MS Exchange log information.

After entering the number of days, the module configuration menu appears again.

6. Repeat step 5 for each option necessary.

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 to “Monitor the Post Upgrade Process” — choice 5) below.

10. Type 5 to monitor the Post Upgrade Process.

The Configuration Menu appears:

1) Modify the above configuration 2) Start the Post Upgrade Process 3) Help

4) Exit the Post Upgrade Process 5) Monitor the Post Upgrade Process

By typing “5”, the user can monitor the Post Upgrade Process. Hit Ctrl-c to exit. The screen returns to the Configuration Menu listed above. When the user sees 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 4 to exit the post-upgrade script.

(28)

18

|

Upgrading in a High Availability Environment

If you have a High Availability (HA) Appliance environment, either an LX-to-LX or ST-to- ST configuration, you must use the following procedure to upgrade the Appliances.

HA is supported on MX3025, HF4 MX, and EVA (when HA is enabled by default).

Prerequisites

The following prerequisites must be met prior to starting the Upgrade Process on your HA Appliances.

• Both HA appliances must have the same hardware model and software version for them to function correctly.

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

Starting the Upgrade Process

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

• File update server, IP address 10.1.1.190

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 of 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 back).

At Step 6 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.

(29)

Upgrading in a High Availability Environment

|

¹⁹

To upgrade your HA environment

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 password:

logapp.

b. Run the following command:

set failover disable

The prompt returns “CHANGES HAVE NOT BEEN SAVED!”

c. Type save and then press enter.

save

3. Install the correct LSP version based on LSP LMI support matrix for the target LMI software.

4. Make sure that the system is ready for upgrade by running the healthcheck command healthcheck.sh with the correct path.

/loglogic/update/healthcheck/healthcheck.sh

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, see LMI/LSP Upgrade Support on page 11.

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

update-201410111812-full.tar.bz2 update-201410111812-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-201410111812-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.

(30)

20

|

8. On the Appliance A, disable the HA configuration.

logapp.

set failover disable

The prompt returns “CHANGES HAVE NOT BEEN SAVED!”

c. Type save and then press enter.

save

9. On Appliance B, set up the HA configuration.

logapp.

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

IP address of the peer Appliance:

10.20.0.44

10. On Appliance A, make sure that the system is ready for upgrade by running the healthcheck command healthcheck.sh with the correct path.

/loglogic/update/healthcheck/healthcheck.sh

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.

(31)

Upgrading in a High Availability Environment

|

²¹

11. Install the correct LSP version based on LSP LMI support matrix for the target LMI software.

12. 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, see LMI/LSP Upgrade Support on page 11.

The following files are examples of the update files that you need to copy:

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.

During the upgrade process, prior to 5.1, some unused files are left that misleads the

healthcheck command to show this prompt. If the post-upgrade process has been run through and this prompt still shows, you should type no to ignore the 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;

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

(32)

22

|

13. Log in to Appliance A and complete the update.

a. Open a web browser and log in to Appliance A.

b. In the navigation menu, click Administration > File Update.

The update-201410111812-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.

14. 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, on page 16.

15. On the Appliance A, set up the HA configuration.

logapp.

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

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

You must let Appliance A complete the upgrade process before syncing up to Appliance B.

Forcing fail-overs for the purpose of keeping one particular Appliance “active” is not recommended as it has no particular benefit and any fail-over event has the potential to cause some loss of data.