Fortinet FortiDDoS Series How to use

FortiDDoS and FortiDDoSCM5.3.0
Release Notes

FORTINET DOCUMENTLIBRARY
http://docs.fortinet.com
FORTINETVIDEOGUIDE
http://video.fortinet.com
FORTINETBLOG
https://blog.fortinet.com
CUSTOMERSERVICE&SUPPORT
https://support.fortinet.com
http://cookbook.fortinet.com/how-to-work-with-fortinet-support/
FORTIGATECOOKBOOK
http://cookbook.fortinet.com
FORTINETTRAININGSERVICES
http://www.fortinet.com/training
FORTIGUARDCENTER
http://www.fortiguard.com
ENDUSER LICENSE AGREEMENT
http://www.fortinet.com/doc/legal/EULA.pdf
FEEDBACK
Email: [e-mail]
Tuesday, February 4, 2020
FortiDDoS & FortiDDoSCM 5.3.0 Release Notes
Revision 1

TABLEOFCONTENTS
Change Log 4
Introduction 5
Introduction to FortiDDoS 5
Introduction to FortiDDoS Central Manager (FortiDDoS-CM) 5
What’s new 6
Image checksums 7
FortiDDoS 8
Hardware support 9
Updating firmware on HA cluster 10
Upgrading 11
Section 1: Upgrading using GUI 14
Section 2:Upgrading via CLI 16
Section 3:Upgrading via BIOS 18
Sample console log 20
Downgrading 23
Factory reset 25
Resolved issues 26
Common Vulnerabilities 27
Known issues 28
FortiDDoS-CM 31
Introduction to FortiDDoS-CM 32
Special Notes for CM 33
What’s new in FortiDDoS-CM 34
FortiDDoS-CM hardware support 35
Installing FortiDDoS-CM 36
Upgrading FortiDDoSCM 37
Downgrading FortiDDoS-CM 39
Resolved issues in FortiDDoS-CM 41
Common Vulnerabilities 41
Known issues in FortiDDoS-CM 42

Change Log
Change Log
Date Change Description
01/07/2020 Initial version of FortiDDoS 5.3.0 Release notes.
4 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Introduction Introduction to FortiDDoS
Introduction
This section provides an overview of FortiDDoS and FortiDDoS Central Manager
Introduction to FortiDDoS
Introduction to FortiDDoS Central Manager
Introduction to FortiDDoS
This document provides a list of new features and known issues for FortiDDoS 5.3.0 build 0204, including ASIC
Version: 5300098 Date: Dec 4, 2019.
FortiDDoS is a network behavior anomaly (NBA) prevention system that detects and blocks network attacks that
are characterized by excessive use of network resources. These attacks are known as Distributed Denial of
Service (DDoS) attacks.
For additional documentation, please visit: http://docs.fortinet.com/fortiddos
Introduction to FortiDDoS Central Manager (FortiDDoS-CM)
This document provides a list of new features and known issues for FortiDDoS-CMVM 5.3.0 build 0204
FortiDDoS-CM is designed to manage multiple FortiDDoS appliances with shared management attributes.
For specific FortiDDoS-CM information, proceed to the section - FortiDDoS-CM
For additional documentation, please visit: http://docs.fortinet.com/fortiddos
5 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

What’s new
What’s new
FortiDDoS 5.3.0 release includes the following new features and enhancements:
Automated Distress ACL: Distress ACL allows complex Layer 3 and Layer 4 ACLs to be configured that will
block those parameters to the full bandwidth of all front panel ports, offloading the SPUs for very large attacks.
Until Release 5.3.0, these ACLs were configured manually. In 5.3.0, the application of these ACLs can be
automatically triggered via the SPP Switching/Signaling Threshold. Data rates higher than the signaling threshold
will generate an internal list of the Top Attacks and the Layer3/4 attributes of these attacks will be configured
automatically as Distress ACLs. These ACLs are monitored every 30 seconds for continued drops. When drops
fall below a low threshold the ACL is retained but disabled. If later monitoring determines the ACL is required
again it is re-enabled. Traffic not matching these ACLs continues to be processed by the SPUs for additional
mitigation. Drops associated with the automatic Distress ACLs will be shown on the Aggregate Drop Graph, the
matching Distress ACL Monitor graph and will be reported in Attack Logs.
DNSRcode Thresholds To improve DNS Response Flood mitigation with asymmetric traffic and/or where
encrypted DNS is present, Thresholds can be added as follows:
- DNS Response Code - No Error - Threshold applied to DNS R-Code 0, good Responses
- DNS Response Code - Error - Threshold applied to all DNS R-Codes from 1-15, error Responses
Note, these thresholds are not automatically learned and are not adaptive. They require manual setting by
observation of the DNS R-code Monitor graphs.
Traffic and Drops for all R-codes is seen in the Monitor Graphs for DNS R-codes.
Distress ACL drop graphs are reorganized: - The aggregate of all Distress ACL drops will be shown in
Monitor > Aggregate Drops
- Drops for each Distress ACL will be shown in Monitor > Distress ACL Drops
NTPReflection Attack For E-Series only, Protection Profiles > Service Config > NTP Reflection ACL will include
both NTP Monlist and Mode 6 responses.
Bypass Status on E-series Added Optical Bypass Status "LEDs" to E-Series dashboard
ACLSearch User can Query system via GUI (Log & Report > Diagnostics > ACL Search) the determine if an
IPv4 address is present in:
- IP Reputation
- Geo-location
- Blacklisted IPv4 Address
- Any global or SPP IP or subnet ACL
- Any Do Not Track / Track and Allow ACL
Note: This function is not available via the FortiDDoS Central Mangement GUI. You must login directly to the
appliance to use it.
6 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Image checksums
Image checksums
To verify the integrity of the firmware file, use a checksum tool to compute the firmware file’s MD5 checksum.
Compare it with the checksum indicated by Fortinet. If the checksums match, the file is intact.
MD5 checksums for software releases are available from Fortinet Customer Service & Support:
https://support.fortinet.com
Customer Service & Support image checksum tool
After logging in to the web site, in the menus at the top of the page, click Download, and then click Firmware
Image Checksums.
Alternatively, near the bottom of the page, click the Firmware Image Checksums button. (The button appears
only if one or more of your devices have a current support contract.) In the Image File Name field, enter the
firmware image file name including its extension, then click Get Checksum Code.
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
7

FortiDDoS
FortiDDoS
This section includes the following topics specific to FortiDDoS release 5.3.0:
Hardware support
Updating firmware on HA cluster
Upgrading
Section 1: Upgrading using GUI
Section 2:Upgrading via CLI
Section 3:Upgrading via BIOS
Sample console log
Downgrading
Factory reset
Resolved issues
Common Vulnerabilities
Known issues
For topics specific to FortiDDoS Central Manager, see FortiDDoS-CM.
8 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Hardware support FortiDDoS
Hardware support
This release supports the following hardware models:
lFortiDDoS 1500E
lFortiDDoS 2000E
lFortiDDoS 200B
lFortiDDoS 400B
lFortiDDoS 600B
lFortiDDoS 800B
lFortiDDoS 900B
lFortiDDoS 1000B
lFortiDDoS 1000B-DC
lFortiDDoS 1200B
lFortiDDoS 2000B
lFortiDDoS 2000B-USG
NOTE: FortiDDoS A series models are not supported.
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
9

FortiDDoS Updating firmware on HA cluster
Updating firmware on HA cluster
Note the following before upgrade:
lUpgrading FortiDDoS requires at least one reboot of each appliance and can be disruptive of network traffic
depending on fail-open/closed conditions and RSTP/BGP settings of surrounding switches. This procedure
assumes production traffic on the Master appliance with an upgrade of the Slave appliance first. This procedure can
be reversed – move traffic to the Slave, upgrade the master, revert traffic and upgrade the Slave.
lIf both devices are carrying production traffic (each appliance is on one leg of an asymmetric traffic environment),
ensure both devices support fail-open and perform in a maintenance window.
lDo not modify any configuration settings when systems are in Standalone Mode. Any configuration changes may
cause the Slave unit to reboot when returning to the HA pair.
To update the firmware of an HA cluster:
1. Verify that the cluster node members are powered on and available.
2. Log into the web UI of the Master node with an account whose access profile contains Read and Write
permissions in the Maintenance and HA categories.
3. Backup the configuration.
4. Go to System > High Availability and note or take a screenshot of all settings on this page.
5. Change the HA mode from Active-Passive to Standalone.
6. Repeat steps 2-4 on the Slave system.
Note: Having both systems in Standalone mode is important for this procedure.
7. On the Slave system, follow the upgrade procedure as instructed in the Release Note upgrading section. (This
assumes that the traffic is currently on the Master system.)
8. Once the Slave system is upgraded, leave the Slave in Standalone Mode and move traffic to the Slave.
9. On the Master system, follow the upgrade procedure as instructed in the Release Note Upgrading section.
10. When upgrade of the Master system is complete, while still connected to the Master, go to System > High
Availability. Confirm or set all HA settings that you retrieved from Step 4. Ensure that the Device priority is set to a
higher priority (lower number) than what you have recorded for the Slave system. Then change the Master system
Configured HA Mode to 'Active-Passive'.
11. Revert traffic to the Master system.
12. On the Slave appliance, go to System > High Availability. Confirm all settings from those you recorded in Step 4
and confirm or set the Device Priority to a lower priority (higher number) than the Master system. Then change
Configured HA Mode to 'Active-Passive'.
13. Depending on what Release you are upgrading from, new configuration information may be available on the
Master system that is not in the Slave. When the Slave sees this configuration mismatch, it will reboot in order to
synchronize its configuration with the Master. This is normal and will only occur once. Once both units are
synchronized, changes in the Master are synchronized to the Slave without further reboots.
10 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Upgrading FortiDDoS
Upgrading
Supported upgrade paths For B-series:
Use the following instructions to upgrade to FortiDDoS 5.3.0.
Steps Current Release Upgrade method Upgrade path
1 <4.1.5 BIOS ONLY 1. Upgrade to 4.1.5.
2. Upgrade to 4.2.3. Follow Step 2.
3. Upgrade to 5.3.0. Follow Step 3.
Refer to section 3for detailed upgrade
procedure.
2 4.1.5 to 4.2.2 GUI/CLI/BIOS 1. Upgrade to 4.2.3.
2. Upgrade to 5.3.0. Follow Step 3.
3 4.2.3 to 5.2.0 GUI/CLI/BIOS 1. Upgrade directly to 5.3.0.
Refer to sections 1, 2 or 3for detailed upgrade
procedure.
Supported upgrade paths For E-series:
Use the following instructions to upgrade to FortiDDoS 5.3.0.
Steps Current Release Upgrade method Upgrade path
1 5.0.0 to 5.2.0 GUI/CLI/BIOS 1. Upgrade directly to 5.3.0.
Refer to sections 1, 2 or 3 detailed
upgrade procedure.
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
11

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
lThe procedures explain the upgrade from 4.2.3 or higher. If your system is not at 4.2.3, refer to the table above and
follow the instructions.
lDownload the correct 5.3.0 firmware file for your model from the Fortinet Technical Support website:
https://support.fortinet.com/.
lCheck that the upgrade info file is available on your FortiDDoS system:
lOn the Dashboard page, click the CLI Console window to connect and see the command (#) prompt.
lEnter: f cat /var/log/upgrade_info.txt
lCheck 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 #
lBack up your configuration before beginning this procedure:
lIf 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.
lAttempting to use a system configuration from a newer firmware release on a downgraded firmware release
may have unexpected results.
lMake 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.
lAfter 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.
lYou must have super user permission (user admin) to upgrade firmware.
12 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Upgrading FortiDDoS
IMPORTANT:
lReleases 4.1.6, 4.1.8, 4.2.0, 4.5.0 and 4.7.0 included improvements to System Recommended Thresholds and
Threshold ranges. If you upgraded from any version lower than 4.7.0, take the following additional steps after the
upgrade to 5.3.0 has completed and the system has restarted:
lIf you upgraded from any Release lower than 4.2.0: If you have DNS server(s), create a DNS SPP and SPP
Policies to place the server IP(s) inside the DNS SPP. Set all DNS anomalies ON for that SPP. Leave that SPP in
learning mode (no Thresholds and in Detection mode only) for as long as possible (recommended period is one
week). After one week, run the Traffic Statistics and set System Recommended Thresholds. Then run for several
days with Thresholds set to look for false-positives and tune if needed. Check for the volume of Anomalies. It
should be a few per 5-minute reporting cycle. If there are many, remove DNS Anomalies and contact Fortinet
Support.
lIf you upgraded from any Release betwen 4.2.0 and 5.0.0: For every other SPP, about one week after the
upgrade, run Traffic Statistics and set System Recommended Thresholds. This will create Thresholds that were not
included in earlier Releases. Review the new Thresholds against the saved Threshold CSVs. Note: Review the TCP
and UDP port thresholds from 1-9999. These may be higher in 5.1.0. This is design-intent. Ignore ports above
10,000. After the new System Recommended Thresholds have been set, it is recommended that the SPPs affected
be placed in Detection Mode for a few days to check for false-positives and tune if needed. If in doubt, contact
Fortinet Support for assistance.
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
13

FortiDDoS Section 1: Upgrading using GUI
Section 1: Upgrading using GUI
Ensure that you have read the general Upgrading section before you start an upgrade.
Note: You can upgrade directly to FortiDDoS 5.3.0 via GUI from any version above 4.2.3.
For any version below 4.2.3, you MUST upgrade to 4.2.3 and then to 5.3.0.
For this upgrade, you must use Partition 2. The following figure shows the user interface for managing firmware.
To install firmware:
1. Go to System >Maintenance >Backup & Restore tab.
2. Under Firmware Upgrade/Downgrade, in the row for Partition 2, click the Upload and Reboot icon to display the
upload file controls.
3. Use the upload file controls to select the firmware image file.
4. Click OK to upload the file, install the firmware, and restart the system. Always use Partition 2 for upgrades even if
Partition 2 is showing a newer Release than Partition 1. From 4.2.3, partition choices will not be shown.
WARNING:The upgrade takes several (as long as 15) minutes – longer for larger systems and
the system will reboot once or twice depending on the Release. During this time, there is no progress
indicator on the GUI. FortiDDoS must write register information to each TP2 which takes considerably longer
than loading firmware as in most x86-based systems. This is only a factor during the upgrade. Once installed,
the TP2 firmware is persistent and will only change with a further upgrade. It is very important the system
not be disturbed or power cycled during this process. A power cycle will result in an unusable system
14 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Section 1: Upgrading using GUI FortiDDoS
that must be returned to factory for repair. Ideally, leave the system for 20 minutes. If the system has NOT
recovered in that time, contact Fortinet Support. It is highly recommended to connect to the Console port
during an upgrade, even if using the GUI. The Console will display progress messages when the GUI is
unresponsive during the upgrade.
5. Clear your browser cache to avoid potential issues that can be caused by caching.
During upgrade, the console will show upgrade progress information if a terminal is connected to it. See the
Sample console log for reference.
6. Login and from Dashboard, confirm that the firmware version is correct.
From the GUI-based Console, SSH or Console, access the command line and follow these steps:
a. Enter: diagnose debug rrd_cmd_check
The console will display the percentage (%) checked messages which may scroll off the screen depending on your
access method. Allow this to complete. The system will return one of the following messages on success/failure:
lRRD commands check successful
The upgrade was successful. Proceed with other actions. No further checks are required.
lRRD commands check failed
The upgrade failed to create some database. Proceed to next step.
b. Enter: diagnose debug rrd_cmd_recreate
c. Enter ywhen confirmation is requested.
The Console will display the messages below, if successful:
100% complete
Created rrd cmd files
If any error message occurs during this process, contact Fortinet Support. If the 100% Complete message is
seen, proceed to other actions.
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
15

FortiDDoS Section 2:Upgrading via CLI
Section 2:Upgrading via CLI
Ensure that you have read the general Upgrading section before you start an upgrade.
Note: You can upgrade directly to FortiDDoS 5.3.0 via CLI from any version above 4.1.5. For any version below
4.1.5, you MUST upgrade to 4.1.5 and then to 5.3.0.
To install firmware:
1. Connect your management computer to the FortiDDoS console port using an RJ-45-to-DB-9 serial cable or a null-
modem cable. Use the following terminal settings:
Speed (Baud Rate): 9600 Data Bits: 8 Stop Bits: 1 Parity: None
2. Initiate a connection to the CLI and log in as the user admin.
3. Use an Ethernet cable to connect FortiDDoS mgmt1 to the TFTP server directly, or connect it to the same subnet
as the TFTP server.
4. If necessary, start the TFTP server.
5. Enter the following command to transfer the firmware image to the FortiDDoS system:
execute restore image tftp <filename_str> <tftp_ipv4>
where:
l<filename_str> is the name of the firmware image file
l<tftp_ipv4> is the IP address of the TFTP server.
For example, if the firmware image file name is FDD_200B-v5.3.0-build0204-FORTINET.out and
the IP address of the TFTP server is 172.30.153.105, enter:
FI900B3915000043 # execute restore image tftp FDD_200B-v5.3.0-build0204-
FORTINET.out 172.30.153.105
This operation will replace the current firmware version!
Do you want to continue? (y/n)y
Connect to tftp server 172.30.153.105 ...
Please wait...
##################################################################################
####################
Get image from tftp server OK.
Verifying the integrity of the firmware image.
The following message appears:
This operation will replace the current firmware version!
Do you want to continue? (y/n)
6. Type y.
The system gets the image from the TFTP server, installs the firmware, and restarts. See the Sample
console log for reference.
16 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Section 2:Upgrading via CLI FortiDDoS
WARNING:The upgrade takes several (as long as 15) minutes – longer for larger systems and
the system will reboot once or twice depending on the Release. (See the progress examples from the
console output below). FortiDDoS must write register information to each TP2 which takes considerably
longer than loading firmware as in most x86-based systems. This is only a factor during the upgrade. Once
installed, the TP2 firmware is persistent and will only change with a further upgrade. It is very important
the system not be disturbed or power cycled during this process. A power cycle will result in an
unusable system that must be returned to factory for repair. Ideally, leave the system for 20 minutes. If the
system has NOT recovered in that time, contact Fortinet Support.
To verify that the firmware was successfully installed, login and run get system status, confirming the
version information is correct:
Version: FortiDDoS-200B v5.3.0,build0204,190912
TP2ASIC Version: 5300098 Date: Apr 22, 2019
IP Reputation DB: Not enabled
Domain Reputation DB: Not enabled
Serial-Number: FI200B3914000081
BIOS version: 04000001
Log disk: Capacity 62 GB, Used 978 MB ( 1.52%), Free 62 GB
RRD disk: Capacity 369 GB, Used 165 GB (44.82%), Free 203 GB
Hostname: FDD-169
HA configured mode: active-passive
HA effective mode: Master
Distribution: International
License Type: -
Uptime: 0 days 0 hours 37 minutes
Last reboot: Thu Apr 25 15:35:18 PDT 2019
System time: Thu Apr 25 16:25:00 PDT 2019
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
17

FortiDDoS Section 3:Upgrading via BIOS
Section 3:Upgrading via BIOS
lThe system configuration will be lost when upgrading via BIOS. For this reason,
BIOS upgrade should only be used for:
a. Upgrading new systems that have not been put in service.
b. When continuity of the system configuration is not important.
lBackup your configuration before starting a BIOS upgrade. It is not recommended to
attempt to restore the system configuration but it can be done by editing the
configuration. This is useful only for maintaining administrative information. Please
contact FortiCare TAC for further information.
Ensure that you have read the general Upgrading section before you start an upgrade.
Note: You can upgrade directly to FortiDDoS 5.3.0 via BIOS from any version.
To upgrade the firmware:
1. Download the new firmware image.
2. Copy the file to a location you can access from the FortiDDoS appliance using TFTP.
3. Connect to the FortiDDoS appliance console.
4. Reboot the system and, when prompted, press any key to display the BIOS configuration menu.
5. Select option G so that the system can get the new firmware image from the TFTP server and load it when it
reboots.
The following example shows the CLI sequence:
FI-1KBXXXXXXXXX # execute reboot
This operation will reboot the system ! Do you want to
continue? (y/n) y
System is rebooting... The system is going down NOW !!
Please stand by while rebooting the system.
FortiDDoS-1000B (20:41-06.12.2018)
Ver:04000001
Serial number:FI1KBXXXXXXXXXX
RAM activation
CPU(00:000306a9 bfebfbff): MP initialization
CPU(01:000306a9 bfebfbff): MP initialization
CPU(02:000306a9 bfebfbff): MP initialization
CPU(03:000306a9 bfebfbff): MP initialization
CPU(04:000306a9 bfebfbff): MP initialization
CPU(05:000306a9 bfebfbff): MP initialization
CPU(06:000306a9 bfebfbff): MP initialization
CPU(07:000306a9 bfebfbff): MP initialization
Total RAM: 8192MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Boot up, boot device capacity: 15272MB.
18 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.

Section 3:Upgrading via BIOS FortiDDoS
Press any key to display configuration menu...
... <----------------------------------------------- Press any key
[G]: Get firmware image from TFTP server.
[F]: Format boot device.
[B]: Boot with backup firmware and set as default.
[I]: Configuration and information.
[Q]: Quit menu and continue to boot with default firmware.
[H]: Display this list of options.
Enter Selection [G]: <---------------------------- Press 'g'
Please connect TFTP server to Ethernet port "MGMT".
Enter TFTP server address [192.168.1.168]: 192.168.1.168 <---- enter TFTP server IP
Enter local address [192.168.1.188]: 192.168.1.188 <--- Enter FortiDDoS IP
Enter firmware image file name [image.out]: FDD_1000B-v5.3.0-build0204-FORTINET.out <---
Enter Image Name
MAC:085B0E9F061C
#########################################################################
Total 76694566 bytes data downloaded.
Verifying the integrity of the firmware image.
Total 204800kB unzipped.
Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?d <------ Press
'd'
Programming the boot device now.
..........................................................................................
..........................................................................................
.................
Reading boot image 2791231 bytes.
Initializing FortiDDoS...
System is started.
16. Set the management port IP address and gateway IP address using the console.
17. If you saved and edited the configuration file, restore it using the CLI or web UI.
18. If you did not save a configuration file, you must reconfigure the user accounts and system options.
19. If you have restored a configuration file, go to Protection Profiles > Factory Reset and reset every SPP in use to
factory defaults (Learning Mode).
20. Treat the upgrade like a new installation with Learning mode for 1 week, creating Traffic Statistics Reports and
setting System Recommended Thresholds for each SPP and so on.
FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.
19

FortiDDoS Sample console log
Sample console log
Sample console log while upgrading from 5.0.0 to 5.3.0:
FI200B3914000035 # execute restore image tftp FDD_200B-v5.3.0-build0204-FORTINET.out
172.30.153.105
This operation will replace the current firmware version!
Do you want to continue? (y/n)y
Connect to tftp server 172.30.153.105 ...
Please wait...
#####################################################################################
#######################
Get image from tftp server OK.
Verifying the integrity of the firmware image.
FI200B3914000035 #
FI200B3914000081 #
The system begins to upgrade ...
Firmware upgrade in progress ...
New image: FI200B-5.3.0-FW-build0204-180612
Done. 2
The system is going down NOW !!
Please stand by while rebooting the system.
FortiDDoS-200B (20:41-06.12.2018)
Ver:04000001
Serial number:FI200B3914000081
RAM activation
CPU(00:000306a9 bfebfbff): MP initialization
CPU(01:000306a9 bfebfbff): MP initialization
CPU(02:000306a9 bfebfbff): MP initialization
CPU(03:000306a9 bfebfbff): MP initialization
CPU(04:000306a9 bfebfbff): MP initialization
CPU(05:000306a9 bfebfbff): MP initialization
CPU(06:000306a9 bfebfbff): MP initialization
CPU(07:000306a9 bfebfbff): MP initialization
Total RAM: 8192MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
20 FortiDDoS 5.3.0 Release Notes
Fortinet Technologies Inc.