Prepare to Upgrade Lighthouse

While upgrading Lighthouse is a simple process, the following tasks are best practices to ensure a successful upgrade.

  • Read the release notes, in particular any known issues or special requirements for the new version

  • Provide a sufficiently large maintenance window to start and complete the upgrade. Larger networks and more complex configurations will take more time. You can run q-stat to check the job queue status.

  • Download the correct upgrade image.
    The current release can be found here: Opengear FTP

    Archived releases are available here: Archives Opengear FTP

  • Verify the image integrity by checking against SHASUMS. For example, on Linux
    $ sha1sum lighthouse-24.02.0.lh_upg 0f52c30a212566030a1742b6e3d5bf9316d89abd lighthouse-24.02.0.lh_upg

  • Before starting the upgrade, generate a Technical Support Report. This can assist Opengear support with diagnosing upgrade issues.

  • Use the df command to display disk usage by filesystem.
    root@lighthouse:~# df /mnt/data/

  • Ensure that you have enough disk space in /mnt/data. If you have less than 20% disk space available, clean up unnecessary files, or add disk space (see Adding Disk Space to Lighthouse). If disk space is added to the primary instance, add additional space all secondary instances also.

  • Take a Configuration Backup on the Primary Lighthouse. This can be used to restore the system in the event of failure during upgrade.

  • Do not make any configuration changes during the upgrade process (includes secondary upgrades).

  • Consider taking a Virtual Machine backup. If the Lighthouse storage has been increased (by adding additional physical volumes to LVM) then these must be included in the backup, and all storage volumes must be in sync.

  • You can also consider running some technical checks before starting the upgrade to check job queues, memory, temporary filesystem (tmpfs), database integrity, and multiple instance status.