Shall we start this new thread with the looks and feels of XG v18 MR-3?
There is a feature request to allow control of the Control Center message notifications. The request is asking for
Best regards Martin ;-)
Sophos UTM Certified Engineer v9.7Sophos XG Certified Architect v18.0Homelab: 2 x SG210 XG v18 (HA A/P) - 3xAPX530 - 1 x SG210 v9.7 - 1 x UTM 220 v9.7 - 1 x SG135 v9.7 (All Fullguard Plus licenses)
Still not possible to get rid of theese? - 6 and 7 MONTHS old messages??
I was also hoping since Sophos Connect 2.0 is out that there will be no old SSL VPN client.
So fas so good in lab environment.
I hope not, we have 200 customers using "old sslvpn" planning migration is in process :-D
I'm unable to upgrade MR3. this pops up when I try to upgrade:
Firmware downgrade also replaces the current configuration with the earlier one. An upgrade replaces it with the default configuration. For details, go to the online help.
As far as I can read, it's going to repalce current config with defaults.
Tested with two different XG210 setups. Both of them in HA. Updated single XG86 without a broblem. All this mentioned setups are/were running 18.0.1 MR-1.
Hi, good start.
installed and running okay. Bug that was supposed to be fixed in this version.IMAP scanning has not been fixed, still the same issue that imap rejects the CA that is acceptable by smtp/s scanning.
Ian, do you have a Jira ID I can reference so I can take a look at status?
Thank you Jarno for your feedback. This is the known issue (NC-60615) - already fixed in the next MR.
This *false alarm* alert message appears when XG is running in HA cluster; one uploads the next firmware (like you uploaded MR3); And later boots with the uploaded firmware. If one upload & boot together with the new firmware, this false alert won't appear.
While resolving this issue in NC-60615, we have also made the alert message more meaningful and easier to understand. The existing message is confusing.
For MR3 - we request you to ignore this alert and move further, it will migrate the configuration properly. We are also updating the known issue list with this behavior.
Thanks again for your feedback.