Recovery Steps for USG FLEX/ATP Series Application Patrol Signature Issue
I have a device still on V5.00(ABUJ.2)
but the update notes recommend upgrading to "ZLD5.10 C0 or later version first before upgrading to ZLD5.20"
Is your documented procedure even *SAFE* for ANY unit more than one version behind ?
For me, the recovery process described here worked, thank god.
Step 9 was not necessary. My ATP 500 connected to Nebula again and downloaded the full config without having to manually remove and add it again. I will now not touch my installation until 13:00 UTC and hope for the best.
I am aware that I used tough words yesterday, and I want to thank everyone at Zyxel Support and Engineering who is working to solve this issue.
But after you fixed it, please do review how this happened and make sure we do not end up in such a situation again. It really is a no-go. I was fortunate, not everybody will have had the means to organise a serial cable and software ASAP, as this method of access is not really standard anymore these days. And perhaps, in the age of easy-to-use Nebula & Co. not everyone will have the required skills anymore, either.
So, please make sure there is a very good review and lessons learned from this incident. And thank you for otherwise very great products.1
Hi everyone, could you confirm whether today's forced update will cause any of the Firewalls to reboot automatically? Just we have quite a few in live / working environments using VPN's....All the best - Adam0
for On-Premise / Standalone = NO
for Nebula Cloud = Yes, 5 Minute downtime around 2PM GMT +10
Would of been good to do this OOH's surely ... but it is what it is - thanks for letting me know :-(
After update to ZL5.21 no access to internet possible?
Does your device is to boot up successfully?
You can drop private message to me if you need further help.0
@Zyxel_Stanley and @Zyxel_Emily
If the newly released 184.108.40.20620316.0 signature is updated on devices that are affected by the signature and not rebooted, will the device be fixed? Or, if the devices before the 5.21p1 firmware (for example 5.02 - 5.10-5.20 firmware) that did not receive the signature dated March 10 before and were not affected by the problem, update the signature dated March 16, is it a problem that the device is rebooted?0
- 8.4K All Categories
- 1.6K Nebula
- 71 Nebula Ideas
- 57 Nebula Status and Incidents
- 4.5K Security
- 226 Security Ideas
- 981 Switch
- 46 Switch Ideas
- 872 WirelessLAN
- 22 WLAN Ideas
- 5.1K Consumer Product
- 157 Service & License
- 280 News and Release
- 97 Success Stories
- 59 Security Advisories
- 13 Education Center
- 579 FAQ
- 262 Nebula FAQ
- 160 Security FAQ
- 76 Switch FAQ
- 74 WirelessLAN FAQ
- 7 Consumer Product FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 69 About Community
- 46 Security Highlight