Cloud firmware upgrade -- On-premises mode

Zyxel_Stanley
Posts: 1,386
Zyxel Employee





This tutorial introduces how to upgrade the the firmware to resolve the App-Patrol signature issue.
Note:
USG20(W)-VPN/ATP100(W)/ATP200/ATP500/ATP700/ATP800
USG FELX100(W)/ USG FELX200/ USG FELX500/ USG FELX700
2. No matter which App-Patrol version is installed on your device. You can follow this scenario to upgrade firmware.
3. If your App-Patrol version is V1.0.0.20220310.0 And your device in service normally. Please DO NOT reboot device before upgrading the firmware.
Scenario#1-- Firmware upgrade procedure
1. Login
to your device by WebGUI first, and then login to Web Console.
Enter Command:
packet-trace
extension-filter -w /db/etc/app_patrol/.md5sumAnd click Ctrl + C to stop the packet-trace

2. Go to Maintenance > File
Manager > Firmware Management. Upgrade the firmware ZLD5.21 pacth1 to
standby partition.
Scenario#2 -- The Device can not boot up successfully
If you installed App Patrol signature V1.0.0.20220310.0, and your device can not boot up successfully. You can follow the recovery steps.
Scenario#3 -- The Device still can not be recovered by Scenario#2
If your device still can not be recovered by the recovery steps in scenario#2, you can follow database recovery steps to flush error data from your system as default unit.
Tagged:
0
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 154 Nebula Ideas
- 103 Nebula Status and Incidents
- 5.9K Security
- 307 USG FLEX H Series
- 284 Security Ideas
- 1.5K Switch
- 78 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 256 Service & License
- 397 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.7K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 77 Security Highlight