Upgrading Lighthouse requires incremental upgrades to each quarterly release version. For example if your Lighthouse is currently on 19.Q2.x and you would like to upgrade it to 20.Q2.0, you will first upgrade it to 19.Q3.0, then 20.Q1.0, and finally 20.Q2.0.
With version 20.Q3.0 , Lighthouse has undergone a significant disk restructuring and moved to Linux Logical Volume Management (LVM). This requires that a backup of your 20.Q2.0/1 version be taken, and applied to a clean install of Lighthouse 20.Q3.0.
To upgrade Lighthouse
A Lighthouse appliance’s system can be upgraded using a xxx.lh_upg image file, each release is available here, in a folder based on the version number:
AWS requires .aws.lh_upg and Microsoft Azure requires.azure.lh_upg.
NOTE: Due to disk restructuring, there are no lh_upg files for 20.Q3.0. To support the improvements required for disk management, this version of Lighthouse requires a new 20.Q3 virtual machine to be deployed and a configuration backup and restore from at least 20.Q2.0 onto the new virtual machine. From this release onwards, the supported upgrade path will be from the last major release (or patch release of that major release) only. This will generally be from the previous quarter.
Although upgrades do not overwrite existing configurations or user files, you should perform a Configuration Backup prior to upgrading.
Once the upgrade is complete, the Lighthouse instance reboots and is unavailable during the reboot process.
Lighthouse is using Logical Volume Management (LVM) for the disks to support expanding the available disk space for the Lighthouse virtual machine, as well as enable other benefits of LVM such as snapshot and restore functionality.
Upgrading from pre-LVM Lighthouse to LVM Lighthouse
NOTE: You cannot directly upgrade from pre-LVM Lighthouse to LVM based Lighthouse. In order to upgrade. You must have the previous release, 20.Q2.x, installed before upgrading to 20.Q3.
You need to:
- Perform a configuration backup of your pre-LVM primary Lighthouse.
- Unenroll any secondary Lighthouse instances from your primary Lighthouse.
- Perform another configuration backup of your pre-LVM primary Lighthouse. This configuration will be imported into the LVM based Lighthouse.
- Shut down the 20.Q2.x Lighthouse before continuing these steps.
- Deploy a new LVM based Lighthouse and do so such that it will have all the same IP addresses and hostnameas the old Lighthouse for nodes and any secondary Lighthouse instances to connect back to.
- Import your pre-LVM configuration, the one with the secondary Lighthouses removed, into the new primary Lighthouse.
- Confirm nodes successfully connect to the new primary Lighthouse.
- Deploy new LVM based secondary Lighthouse instances and make sure their external endpoint addresses are correct.
- Enroll the new secondaries, one by one, to the new primary Lighthouse
Upgrading LVM Lighthouse to LVM Lighthouse
To upgrade a Lighthouse instance’s system using the Lighthouse UI:
- Select SETTINGS > SYSTEM > System Upgrade.
- Select the Upgrade Method, either Fetch image from HTTP/HTTPS Server or Upload Image.
If upgrading via Fetch image from HTTP/HTTPS Server:
- Enter the URL for the system image in the Image URL text-entry field.
- Click Perform Upgrade.
Or if upgrading via Upload Image:
- Click the Choose file
- Navigate to the directory containing the system-upgrade-image.lh_upg
- Select the system-upgrade-image.lh_upg file and press Return.
- Click Perform Upgrade.
NOTE: The Advanced Options section, which expands to present an Upgrade Options text-entry field, should only be used if a system upgrade is being performed as part of an Opengear Support call.
Once the upgrade has started, the System Upgrade page displays feedback as to the state of the process.
A system upgrade attempt returns the error System version was not higher than the current version if the selected image file is not a more recent version than the installed version.
Article is closed for comments.