Configuration gone after upgrage SFOS 19.0.0 to 19.0.1

Hello everybody,

yesterday I updated two Firewalls (XGS 126 and XG 125) from Version 19.0.0 to 19.0.1. After the upgrade both Firewalls has SFOS 19.0.1 firmware installed but lost their configuration. The problem was both firewalls are on remote site and lost all external connections (Sophos Central und VPN), so I can't reach the firewalls. Today we connect on site via serial console to the Firewalls, and I saw that Firmware 19.0.1 was installed, but (at minimum) the network configuration was gone. I made some tests:

- Booting the 19.0.0 Firmware the Firewall runs as expected. 

- Booting the 19.0.1 Firmware via Bootloader or via WebAdmin Firewall has no configuration.

On the other hand, I made the upgrade on serval firewalls without any problem (2x XG 125, 1x XGS 5500 HA, a Virtual and a Software Firewall). 

How can I remove the 19.0.1 Firmware from the non-working firewalls to get a 2nd try to upload the firmware again and install the 19.0.1?

Thanks,

Ben



Edited TAGs
[edited by: emmosophos at 10:28 PM (GMT -7) on 4 Aug 2022]
Parents
  • 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. 

Reply
  • 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. 

Children
No Data