08-01-2017 07:49 AM
Thanks to @hdnhdn, @adamjb and others from this thread we identified critical bug in FW 1.9.7 + 1.9.7.betaX. When you have FW 22.214.171.124-unms or 1.9.7.alphaX and your device is connected to UNMS during your upgrade to 1.9.7 or (1.9.7.betaX) you can lose your device configuration. Device file config.boot could be cleaned (but device confguration will remain in device memory). Any subsequent device restart/upgrade will lead to loosing your device configuration completely.
There is a bug in device boot where in special order of events, network state and device configuration could UNMS connector prematurely access device configuration. We are fixing it right now and fix will be included in FW 1.9.7+hotfix.1 which will be released according to tests around 4.8.2017. We will bundle this FW to UNMS 0.9.1 which we will release day after. We are really sorry if you were affected with this issue. If you did this update, please check content of your /config/config.boot file. If this file doesn't include your configuration and there are only few lines with metadata you can enter CLI config mode and run save operation which will overwrite corrupted config.boot with working copy from memory.
08-01-2017 07:53 AM
08-01-2017 08:02 AM
@adamjbWere they successfully connected to UNMS? Problem is key exchange between UNMS and device which is performed during device boot.
08-01-2017 03:14 PM - edited 08-01-2017 03:15 PM
Does this affect all Edgerouter models or just some?
**EDIT** nevermind, i just logged into an er-pro and checked and see that nothing was there. Yikes!
Will doing a save fix the issue or will it re-appear again later?
08-01-2017 03:24 PM
10-18-2017 01:39 PM
thanks for the notice.
i just upgraded one er-x-sfp from 126.96.36.199 to 1.10.0alpha1 without issues and wanted to upgrade all routers in our network.
now i noticed on 7 (3 are important as uplink) routers we have 188.8.131.52unms running, all the others have v1.9.7+hotfix.2 running.
i understand that the reasons mentioned are worth removing 184.108.40.206unms but could you please provide it again so i may try an upgrade locally from 220.127.116.11unms to 1.10.0alpha1?
would like to go sure working upgrade before upgrading uplink sites remotely.
10-19-2017 04:09 AM
If you need it for testing purposes, you can download at
10-20-2017 08:50 AM
i tested upgrade 18.104.22.168unms -> 1.10.0alpha1 and seem to work fine on a local er-x-sfp router.
did the same on a (less important) remote site, worked also without issues, running 21hous stable atm, so i can confirm this is working well.