Configuration gone after upgrage SFOS 19.0.0 to 19.0.1

Thank you all for reporting this issue. 

We have confirmed this is a bug, and we'll fix it in an upcoming new build for v19.0 MR1.

This issue affects devices which has 'set vpn conn-remove-on-failover non-tcp' executed on the backend prior to the upgrade to MR1. Unfortunately the migration to MR1 does not handle this case properly, and would fall back to factory default settings. 

If you cannot wait for the new MR1 build, and need to upgrade to MR1 right away, you can: 

Log into Advanced shell in the CLI

Execute psql -U nobody -d corporate -Atc "DELETE FROM tblclientservices WHERE servicekey = 'vpn_flush_conn_failover'

Upgrade to MR1 as normal through UI

After upgrading to MR1, you do not need to re-run 'set vpn conn-remove-on-failover non-tcp' as this parameter is already set to non-tcp by default in MR1. 

Thank you all for reporting this issue. 

We have confirmed this is a bug, and we'll fix it in an upcoming new build for v19.0 MR1.

This issue affects devices which has 'set vpn conn-remove-on-failover non-tcp' executed on the backend prior to the upgrade to MR1. Unfortunately the migration to MR1 does not handle this case properly, and would fall back to factory default settings. 

If you cannot wait for the new MR1 build, and need to upgrade to MR1 right away, you can: 

Log into Advanced shell in the CLI

Execute psql -U nobody -d corporate -Atc "DELETE FROM tblclientservices WHERE servicekey = 'vpn_flush_conn_failover'

Upgrade to MR1 as normal through UI

After upgrading to MR1, you do not need to re-run 'set vpn conn-remove-on-failover non-tcp' as this parameter is already set to non-tcp by default in MR1. 

Hi,

I updated some firewalls from 19.0.0 to 19.0.1-365 without manually removing the database entry. It runs smoothly without any problems.

thanks,

Ben

Thank you for the confirmation Ben, yes with MR1 build #365 we have fixed this issue, and you can upgrade without manually removing entry from DB first. 

Hi!
I tried to update my Sophos XG to SFOS 19.0.1 MR-1-Build365 and still config error. Is tere a plan to release proper update in near future?

Thanks,

Mar

V19.0 MR1 build 365 resolves the issue described above, and we have had no further report of migration issues. 

can you describe the error/issue you’re seeing? What version are you upgrading from? 

Hello,

I have partial the same issue. I came fron the latest 18.5 version and after the upgrade only the first two interfaces (from 4) came up. After I connected to the first interface with the standard Ip 172.16.16.16 I saw that the other 2 ports are not anymore configured and it is disabled. Also the rules are gone.

If you need more Information, ask me.

Regards Kay-Uwe

What was the version of v18.5 you upgraded from? Did you upgrade directly to v19.0 MR1 build 365? Did all configuration disappear from your system (i.e. it got factory reset)? 

Is there a support case open for this, if so what's the ID? 

It was the 18.5.4 Mr4 418. The config gone except the login data and the Rule Group.

There is no support case opened, because it is the "home" version.

What version did you upgrade to? 

to 19.0.1 MR-1-Build365

If you encounter the same issue as above, all of your config would be reset, not just some. Is it possible for you to enable remote support access, so we can log in and take a look at your device? 

PM me the support access ID once you have it enabled. 

Thanks!