Hi,
please don't say it is obvious, it is not obvious because there is no reference to what safiware needs updating.
For current version pease see signature.
Ian
This thread was automatically locked due to age.
There should be an alert in Central itself. Check the Central console about the appliance affected.
Basically this means, one of your firewall has an old version running, which will be not supported due the EOL Announcement earlier this year: see: https://community.sophos.com/sophos-xg-firewall/b/blog/posts/end-of-life-eol-announcement-for-sophos-xg-firewall-os-firmware-v17-5
Great, I rolled back to the previous version of V18.5.1 and broke the CM registration. Tried to reregister and that failed. Also the heartbeat service is still broken. Rolled forward and the registration restored automatically and heartbeat is still broken.
Also the GUI is not updating correctly or quickly, so which of the firmware updates broke my XG.
Looks like I might need to rebuild the XG, what a pain. Not happy.
Ian
Update:- 5 minutes after rollback the CM registration failed.
Hi DeveshhM,
I will via a PM. I am in the middle of building a replacement int with all new hardware and use the latest ISO. I will be building all the configuration using exported components from the current XG and usng different network setup.
Pease let me know when you have finished your examination and if you want me to wait before implementing then new XG?
Ian