Firmware Update v12.2.5.1

notempty

Dieser Artikel bezieht sich auf eine nicht mehr aktuelle Version!

notempty

Der Artikel für die neueste Version steht hier

notempty

Zu diesem Artikel gibt es bereits eine neuere Version, die sich allerdings auf eine Reseller-Preview bezieht

---

---

| Indicates that this is a new version. }}

| Indicates that this is the previous version and a rollback can be performed }}

We recommend clearing the browser cache after the update.

No factory reset may be performed during the dry run.

| }}

Description of the update process on the UTM

Last adaption: 01.2023 (12.2.5.1)

New:

• Section Troubleshooting revised

notempty

This article refers to a Resellerpreview

12.1 11.8.11 11.7 11.6.11

Access: UTM-IP:Port or UTM-URL:Port
Port as configured at Network / Appliance Settings / Webserver
Default-Port: 11115
i.e.: https://utm.ttt-point.de:11115
Default: https://192.168.175.1:11115 → Extras →Firmware Updates

---

Introduction

• In order for the UTM to receive updates, it must be able to reach the Internet and DNS resolution must work.
• The UTM checks every 120 minutes whether a new update is available on the update servers.
• Due to the high number of UTMs that want to download an update, they are distributed over a certain period of time.
  This distribution is carried out by the update servers.
• The update will then be downloaded automatically.
  Activation is not automatic, it must be confirmed manually.
• The UTM always downloads a complete firmware image for the corresponding version.
• For cluster devices: Please wait until both devices have the same version for updating.

Update detection

Update notification

If the UTM has detected a new version on the update servers and has been completely downloaded, a message is displayed on the administration interface with the next login. If the message is confirmed with Yes, a forwarding to the menu → Extras →Firmware Updates takes place.

Start update

Update to v12 Update to v12 The → Extras →Firmware Updates menu displays available versions. An update to the 12.x is only possible with a version 11.8.14 or higher
Installed version
Version	The currently running version	Update to Version 12.x
Status	Active
Available version
Version	Installable version An update to version 12.x is only offered from version 11.8.14 onwards. This ensures that the latest version from series 11 (with e.g. current security patches) is installed during a rollback. 11.4.x → 11.8.14 → 12.1.1 11.8.x → 11.8.14 → 12.1.1 11.8.14 → 12.1.1
Status	Newer version
Start dry run
The update process must be confirmed again with Yes, the system will reboot and boot with the new version. This process may take a few minutes.
Update up to version 11.8.13 Update up to version 11.8.13 The → Extras →Firmware Updates menu displays available versions.
Installed version
Version	The currently running version	Update possible until version 11.8.13
Status	Active
Available version
Version	Installable version
Status	Newer version
Start dry run	Start update process
The update process must be confirmed again with Yes, the system will reboot and boot with the new version. This process may take a few minutes.
Update up to version 11.7.15 Update up to version 11.7.15 The → Extras →Firmware Updates menu displays available versions.
Active version	The currently running version	Firmware Update bis Version 11.7.15
Available version	Installable version Please pay special attention to the symbol behind the version number.
	* gibt an, dass es sich dabei um eine neue Version handelt.
	† gibt an, dass es sich um die vorherige Version handelt und ein Rollback durchgeführt werden kann
With a click on Activate, the update process (if necessary the rollback process) is started.
The update process must be confirmed again with Yes, the system will reboot and boot with the new version. This process may take a few minutes.
Complete update Acceptance of License Agreement and Privacy Policy
After the update and a re-login to the administration web interface, the license agreement is displayed. This must be signed Accept. If you decline Decline the previous version will be reactivated.		Accept Eula
The privacy policy is displayed. This must be signed Accept. If you decline Decline the previous version will be reactivated.		Accept privacy policy
Changelog
The changelog with the most important changes is displayed. With Yes, it can already be specified that this version will be used during the next startup. With Ask again later, the previous version will be used initially when restarting.		Changelog
Dry run
Under → Extras →Firmware Updates you can use the Finalize dry run or the ✖ Cancel dry run.		Finalize dry run
Rollback
Under → Extras →Firmware Updates you can perform a rollback to the last installed version.		Rollback
Installed version
Version	The currently running version
Status	Active
Available version
Version	Installable version
Status	Older versions If a Newer version has already been found, a rollback is only possible via CLI.
Start dry run	Start rollback Configuration changes in the active version are reset in the process.

---

Troubleshooting

The system does not boot with the new firmware version

If the system does not boot properly after a restart, a reboot can re-enable the previous version.
The reboot can be done via the CLI (system reboot), the web interface (if accessible under → Configuration →Restart or by pressing the power switch at the back of the case.

Certain features do not behave as desired after the update

If the UTM does not work as desired after the update, a rollback can be performed.

If proper operation has not yet been confirmed, proceed as described above.

Otherwise under → Extras →Firmware updates in the section

Available version

activate the Older version with Start dry run .

Please create a support ticket with an error description as detailed as possible. → how to make a ticket

A new version is not downloaded automatically

• A valid license is required.
• The time of the system must not deviate too much.
• The update server is not accessible. e.g. due to a too large packet size (MTU), this must be adjusted if necessary.
• The automatic update process is distributed over a certain period of time for load distribution (see Changelog): Planned rollout period.
• Update does not load and the following error message can be seen in the log:
  2023-01-09T09:51:17.302+01:00|spupdater|22223|downloading do-update.sh: failed
  Additionally, the configuration cannot be saved or a new configuration cannot be created.
  Solution:
  • Check storage space
  • Check the writability of the partition/hard disk.

Erreichbarkeit des Support-Servers prüfen

Aus der root-Shell heraus lässt sich folgender Befehl ausführen
root@fw:~# curl update-001.v12.utm.spnoc.de

Ergebnis	Description
curl: (6) Could not resolve host: update-001.v12.utm.spnoc.de	DNS Problem
curl: (7) Error	Failed to connect() to host or proxy TCP Verbindung schlägt Fehl. Falsche Route, Verbindung wird durch eine andere Firewall blockiert o.ä.