FortiDDoS
Upgrading
FortiDDoS TP2/TP3 hardware takes longer to upgrade than x86-based
systems. Prepare your maintenance window to accommodate at least 20
minutes for the upgrade (most will not take this long but some may). In
some cases, you need to upgrade to an intermediate release before the
final upgrade (2 x 20 minutes). Plan accordingly, after you understand the
upgrade path from the table below. We strongly recommend that while
you can upgrade via GUI, you also connect to the console port, which will
provide status messages during the upgrade process, while the GUI is
offline.
To track the progress of upgrade from any version, check the console.
While the back-end processes are initializing after an upgrade, a rotating
GIF of several icons is displayed on the browser until the system is ready
to accept login.
Clear your browser cache after upgrade to ensure new features are
displayed correctly once logged-in.
Prerequisites
l
The procedures explain the upgrade from 4.2.3 or higher. If your system is not at 4.2.3, refer to the
above and
follow the instructions.
l
Download the correct 5.3.0 firmware file for your model from the Fortinet Technical Support website:
https://support.fortinet.com/.
l
Check that the upgrade info file is available on your FortiDDoS system:
l
On the Dashboard page, click the CLI Console window to connect and see the command (#) prompt.
l
Enter:
f cat /var/log/upgrade_info.txt
l
Check that the X,Y,Z number you see looks like the current Release of the system (from the Dashboard
page. This file is needed to properly upgrade your system.
Example:
FI200B3914000071 # f cat /var/log/upgrade_info.txt
4,7,0FI200B3914000071 #
l
Back up your configuration before beginning this procedure:
l
If you later revert to an earlier firmware version, the active configuration is deleted, and you will want to restore
the configuration that worked well with the earlier version.
l
Attempting to use a system configuration from a newer firmware release on a downgraded firmware release
may have unexpected results.
l
Make a note of configuration items that are disabled in your active configuration. Configurations that are not
enabled are not preserved in the upgrade to 5.3.0. For example, if a custom HTTP service port, log remote port, or
event log port have been configured and then disabled in an earlier version, the configuration information is not
preserved in the upgrade to 5.3.0.
l
After upgrade you may need to regenerate system recommended Thresholds. Before upgrading, go to Protection
Profiles > Thresholds > Scalars and for each SPP, use the 'Save as CSV' in the top right corner of the GUI. This will
allow you to compare pre- or post-upgrade/new Recommended Threshold values.
l
You must have super user permission (user admin) to upgrade firmware.
12
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
