You can download firmware patches from the Downloads page.

The Verification File field appears if the Update Verification Options field is set to Required or Optional in System Configuration > Miscellaneous Options > WUI Settings (this is set to Required by default).

By default, the integrity of a patch or add-on is verified at install time. This is done without the use of a secondary XML verification file.

Setting the Update Verification Options to Required or Optional allows the use of a secondary XML verification file to be uploaded at the same time as you are uploading a patch or add-on, which allows you to verify the digital signatures used to sign the update file archive. The patch/add-on will not be installed if the patch cannot be verified against the XML file.

If you are upgrading a LoadMaster to version 7.2.51 or above and it is set to require validation, you must supply one of the two XML verification files supplied with this release:

  • 7.2.<release/build number>.RELEASE.PATCH-64-MULTICORE-preV7.2.51.0.checksum.xml: Use this file when upgrading to a LoadMaster running a release that is prior to LMOS 7.2.51.
  • 7.2.<release/build number>.RELEASE.PATCH-64-MULTICORE.checksum.xml: Use this file when repeating an upgrade to a LoadMaster that is already running 7.2.51.0 or above and you want to repeat the upgrade process.

If the Update Verification Options drop-down list is set to Required it is not possible to upgrade to LoadMaster firmware 7.2.51 or above. It is also not possible to downgrade from 7.2.51 to a version previous to that. To workaround this, set the Update Verification Options field to Optional or No verification file - deprecated before downgrading or upgrading between the specified versions.

Note:

When updating LoadMaster hardware, starting with 7.2.54.5, you can only update a hardware LoadMaster with an image that supports the boot method used by the hardware. The newer NG models (introduced in 2023) use the UEFI boot method, while earlier models use the BIOS boot method. If you attempt to update a hardware appliance with an updated image that doesn’t support the boot method used by the appliance, the update process stops and the following message is displayed:

The system cannot be updated with the provided image, which is not supported on the hardware platform on which you are attempting to install it.

All LoadMaster -NG hardware models (introduced in 2023) require UEFI-capable patches, and so cannot be updated with any patch earlier than 7.2.54.6, or between 7.2.55.0 and 7.2.59.1 (inclusive).

For more information, refer to the knowledge base article: LoadMaster Firmware Upgrade Path.

Upgrading to 7.2.61 or above (legacy WAF removal)

If you upgrade from a LoadMaster version prior to 7.2.61, during the upgrade any legacy WAF-enabled Virtual Services get converted to use the OWASP WAF with the default values configured. During upgrade, you get notified with a warning message that indicates the list of Virtual Services and SubVSs that have legacy WAF enabled. To continue to use the legacy WAF functionality, click Cancel (to remain on the previous version) or click OK to proceed with the LoadMaster firmware version upgrade. For more details, refer to the following section: Converting from Legacy WAF to OWASP WAF of WAF Feature description document.

When you upgrade to 7.2.61, legacy WAF functionality is removed from the LoadMaster. If you downgrade from 7.2.61 or above to a version below 7.2.61, legacy WAF will not be restored.

Update Machine

Note: You cannot directly downgrade from version 7.2.62 (or above) to any release version earlier than 7.2.61. If you try to, an error message appears that says "Invalid software update". To downgrade to a version earlier than 7.2.61, first downgrade to 7.2.61 and then downgrade again.

After you have downloaded the firmware you can unzip it. You can then browse to the file and upload the firmware directly onto the LoadMaster. The firmware will be unpacked and validated on LoadMaster. If the patch is validated successfully you will be asked to confirm the release information. To complete the update you will need to reboot the appliance. This reboot can be deferred if needed.

Note: A checksum file is provided inside the zipped firmware download. Note that this checksum file matches the firmware file itself (contained within the zip file). It does not match the zipped download. The checksum available for download on the Progress Kemp website matches the zipped firmware download.

Update Cluster

Note: The Update Cluster option will only be available on LoadMasters which have a clustering license. To add the clustering feature to your license, please contact a Progress Kemp representative. For further information on clustering, refer to the LoadMaster Clustering Feature Description.

The firmware on all LoadMasters in a cluster can be updated using the shared IP address by clicking the Update Cluster button. For step-by-step instructions on how to perform a cluster-wide software update, refer to the LoadMaster Clustering Feature Description.

Restore Software

If you have completed an update of LoadMasters firmware you can use this option to revert to the previous build.

Installed Addon Packages

Add-on packages can be installed in the LoadMaster. Add-on packages provide features that are additional to those already included in the LoadMaster. We plan on creating further add-on packages in the future.

Note: Progress Kemp only support add-on packages that can be downloaded from the LoadMaster Add-on Packages page.
Note: If an add-on package of the same name is uploaded, the existing one will be overwritten/updated.
Note: The Verification File field appears if the Display Verify Update Option is selected in System Configuration > Miscellaneous Options > WUI Settings (this is enabled by default). By default, the integrity of a patch or add-on is verified at install time. This is done without the use of a secondary XML verification file.
Note: If an installed add-on package cannot be started, the text will display in red and the hover text will show that the package could not be started.

How to Install an Add-On Package

Follow these steps to install an add-on package on a standalone unit or on two units configured into an High Availability (HA) pair. If you are using clustering, perform this procedure on each unit in the cluster as if it was a standalone unit:
  1. Download the add-on package and the associated XML verification file from the LoadMaster Add-on Packages page. The XML verification file checksum refers to the add-on package itself, not the zip archive. Unzip the add-on package before proceeding.
  2. If the LoadMaster to which you are applying the add-on is not in HA mode, skip this step. Otherwise, if you have a pair of LoadMasters configured into HA mode, apply the add-on first to the standby unit:
    1. Log into the current standby unit using that unit's IP administrative IP address.
    2. Go to Local Administration > Update Software.
    3. Under Install new Addon Package click the Choose File button next to Addon Package File.

    4. Browse to the add-on package file downloaded in step 1, select the file, and click Open.
    5. Click the Choose File button next to Verification File.
    6. Browse to the add-on package verification file downloaded in step 1, select the file, and click Open.
    7. Click Install Addon Package.
    8. After the installation is finished, go to System Configuration > System Administration > System Reboot and click the Reboot button. The unit will return to standby mode after the reboot completes.
  3. For a standalone/clustered unit, or the active unit in an HA pair, log into the administrative interface of the unit; or, for an HA pair, log into the shared IP address (which connects to the unit currently in active mode).
  4. Go to System Configuration > System Administration > Update Software.
  5. Under Install new Addon Package click the Choose File button next to Addon Package File.

  6. Browse to the add-on package file downloaded in step 1, select the file, and click Open.
  7. Click the Choose File button next to Verification File.
  8. Browse to the add-on package verification file downloaded in step 1, select the file, and click Open.
  9. Click Install Addon Package.
  10. After the installation is finished, go to System Configuration > System Administration > System Reboot and click the Reboot button. If this is the active unit in an HA pair, the system will either assume the standby role after the reboot or will attempt to assume the active role, depending on the configuration of the unit.