Migration to version 3.0 - via Endian Network

Versions 2.5

Applies to platform: UTM 2.5.X
Updated on: 30th of June 2014

This lesson guides you through the process of upgrading your Endian UTM Appliance from the 2.5.X to the 3.0 version Using Endian Network

Before starting the procedure, make sure:

  1. To read carefully all this document.
  2. To verify that your system is eligible for upgrade and satisfies the hardware requirements as described in this document.
  3. To have a full backup of the configuration of your Endian UTM Appliance.
  4. To allow access via SSH and via HTTPS to your appliance from Endian Network.

Warning: NEVER FORCE A REBOOT during the upgrade process!

If for any reason the upgrade process does not finish successfully or it seems to be stuck, DO NOT forcibly reboot your Endian UTM Appliance, but read the troubleshooting guide and apply the solutions provided therein.


The upgrade procedure to version 3.0 using Endian Network is very similar to the procedure used to upgrade from the 2.4 to 2.5

Frequently Asked Questions (FAQ)

  • My system has custom modifications. How will they be migrated?
    If your system has modifications that have been authorized or made by Endian, please open a support ticket with Endian and let us know about your customization so we can help you to get your system upgraded.
  • How to handle a system with a version older than 2.5?
    Please note that systems older than version 2.5 are not supported anymore. Systems running version 2.4 can be upgraded to version 2.5 (so can the unsupported version 2.3).

Warning: HA & Hotspot

If you have a pair of Endian devices configured in High Availability (HA), please do NOT perform the upgrade yourself and instead open a ticket with Endian support for assistance in migrating your appliances.
If you have hotspots configured as Master and Satellites, it is mandatory that all the systems run the same software version and therefore be migrated at the same time. If you have such a setup, it is suggested to open a ticket with Endian support for directions.

RAID Devices

For those appliances having RAID arrays, it is mandatory to check the integrity of the RAID array  and repair it if damaged. The status of the RAID array can be checked from the console: Look the content of the file /proc/mdstat, whose output looks like:

root@endian:~# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sdb2[1] sda2[0]
205760448 blocks [2/2] [UU]

md1 : active raid1 sdb1[1] sda1[0]
38435392 blocks [2/2] [UU]
unused devices: <none>

What is important is the [UU] string: Whenever you see the [UU] string, the array is correctly working, while the [_U] strings suggests that the array device is in a degraded state. In the later case, do not start the upgrade process, but follow this lesson and (if possible) repair the RAID array.

Disk Space

Check that your appliance has enough space on all partitions. Use the following command (a sample output is also provided):
root@endian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
ubi0:rootfs           463M  192M  271M  42% /
/dev/mmcblk0p4        5.8G  250M  5.2G   5% /var
/dev/mmcblk0p2         97M  6.6M   86M   8% /var/efw
/dev/mmcblk0p1        650M  100M  518M  17% /var/log
tmpfs                 252M     0  252M   0% /dev/shm
tmpfs                 252M   17M  236M   7% /tmp

It is important that all partitions (except /dev/shm) have enough space for the upgrade process to take place. The percentage displayed in the 4th column (Use%) of the output, should be less than 80%. For example, if the /var/log/ partition has only a small amount of space left, the upgrade process might not be logged in its entirety and daemons may stop wroking correctly if they can not write their output on log files.

Endian Netwok

If the system appears as offline on the Endian Network, issue the following command from the console:

root@endian:~# jobcontrol restart enclient
If your system does not yet feature jobcontrol, use the legacy command:
root@endian:~# restartenclient -fd

To make sure your system is properly synchronised with Endian Network, you can also issue the command:

root@endian:~# en-client -suv

How the Migration Works

The full procedure is divided in three steps:

Step 1: For maximum safety there should be a person physically near the system, who should:

  • Make a backup of the configuration, logs, log archives and database dump. You can either download the backup or put it on a USB Flash Drive.
  • Be able to operate on the system console in case of emergency.

Step 2: You have to:

  • Make sure that the system is online on Endian Network. Otherwise, the channel switch will not start immediately.
  • Ensure your system is up-to-date and has the latest packages installed .

Step 3: Endian Network will then:

  • Send an action to the system which starts the upgrade process immediately.
  • Update the system (this may take a long time depending on your Internet connection speed).
  • Migrate all configuration files to 3.0.
  • Reboot the system.
Following Along: The upgrade process can be followed
  • On the Endian UTM Appliance: Package by package in System > Updates (you may need to refresh the page).
  • On Endian network: On the upgrade log, that can be found after the process has been completed in the “Actions” section.
  • From the console, by looking at the upgrade log file, i.e., at the output of the command:
    root@endian:~# tail -f /var/log/efw-update

What Should I do If Something Goes Wrong?

After the upgrade, please check if the system is running as expected. If the process has not completed successfully, read the troubleshooting guide for the upgrade process. There you will find information and commands that you can use to resolve any issue that should arise during or after the upgrade process.

Have more questions? Submit a request


  • Avatar
    Lupoani Sánchez

    Hi, can confirm when is the release endina 3.0 fro endia mini.