FortiDDoS
FortiDDoS protects from both known and zero day attacks with very low latency. It’s easy to deploy and manage, and includes comprehensive reporting and analysis tools.
arleniscg
Staff
Staff
Article Id 307361
Description

This article describes how to connect FortiDDoS to FortiAnalyzer and troubleshoot connectivity issues.

Scope FortiDDoS, FortiAnalyzer.
Solution

Section 1: FortiDDoS and FortiAnalyzer firmware compatibility.

 

As a General Rule, FortiAnalyzer must run a firmware release integrable with FortiDDoS. 

 

Note: For more detail, see the 'Compatibility with FortiDDoS' document for FortiAnalyzer: FortiDDoS.

 

For the lab example, FortiAnalyzer v7.2.0 and FortiDDoS v6.6.3 have been used.

 

FortiAnalyzer v7.2.0:

 

FAZ.png

 

FortiDDoS v6.6.3:

FDD.png

 

Section 2: Verify FortiAnalyzer configuration on the FortiDDoS.

 

From FortiAnalyzer, test the connectivity to FortiDDoS (FortiDDoS's IP in the lab: 192.168.91.55).

 

FAZ ping.png

 

Configure FortiAnalyzer in FortiDDoS:

 

FDD conf FAZ.png

 

Go to FortiAnalyzer and authorize the FortiDDoS:

 

Auth FDD on FAZ.png

 

Auth FDD on FAZ2.png

 

Auth FDD on FAZ3.png

 

Auth FDD on FAZ4.png

 

Section 3: Verify FortiDDoS and FortiAnalyzer connectivity.

 

Create a test NTP profile and delete them on FortiDDoS to generate logs to FortiAnalyzer:  

 

Capture logs:

 

Run on the FortiAnalyzer CLI: 

 

diag sniffer packet any ' port 514 and host 192.168.91.55' 3

 

Run on the FortiDDoS CLI:

 

diag sniffer packet any ' port 514 ' 3

 

Create an NTP profile test and delete it on the FortiDDoS.

 

test FAZ to FDD.png

 

test FAZ to FDD2.png

 

FortiAnalyzer will show the related logs from FortiDDoS:

 

test FAZ to FDD3.png

 

test FAZ to FDD4.png