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
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 back).
At step 9 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.
Upgrading in a High Availability Environment
|
19• Network Mask, IP address 255.255.255.0
• Network Broadcast, IP address 10.20.0.255
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 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.
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.
For example: /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-<timestamp>-full.tar.bz2 update-<timestamp>-full.tar.bz2.sig
If the HA cluster was configured with the archive feature, disable it before the upgrade process.
20
|
Chapter 2 Appliance Software Upgrade6. 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-<timestamp>-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, on page 16.
8. 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.
save
Upgrading in a High Availability Environment
|
219. 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
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.
• 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.
22
|
Chapter 2 Appliance Software UpgradeFor example: /loglogic/update/healthcheck/healthcheck.sh
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:
update-<timestamp>-full.tar.bz2 update-<timestamp>-full.tar.bz2.sig
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;
Both Appliance A and Appliance B should now be on the same LSP version.
Upgrading in a High Availability Environment
|
2313. 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-<timestamp>-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.
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
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 with 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.
24