mirrors/cheat-sheets
1
0
Fork 0
mirror of https://github.com/yuriskinfo/cheat-sheets.git synced 2025-12-21 21:33:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

ongoing additions, changes, and fixes

Browse Source
This commit is contained in:
Yuri Slobodyanyuk
2021-01-12 09:37:31 +00:00
parent 3d026a96d3
commit 9625555171
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
Fortigate-debug-diagnose-complete-cheat-sheet.adoc
View File

@@ -397,3 +397,32 @@ a|View the kernel routing table (FIB). This is the list of resolved routes actua
|===
== Fortianalyzer logging debug
.Verify and debug sending logs from Fortigate to Fortianalyzer
[cols=2, options="header"]
|===
|Command
|Description
|*get log fortianalyzer setting*
|Show active Fortianalyzer related settings on Fortigate.
|*config log fortianalyzer*
|Complete Fortianalyzer configuration on CLI, as GUI configuring is usually not enough for it to work.
|*get log fortianalyzer filter*
|Verify if any log sending filtering is being done, look for values of `filer` and `filter-type`. If there are any filters, it means not all logs are sent to FAZ.
|*exec log fortianalyzer test-connectivity*
|Verify that Fortigate communicates with Fortianalyzer. Look at the statistics in `Log: Tx & Rx` line - it should report increasing numbers, and make sure the status is `Registration: registered`.
|*exec telnet <IP of Fortianalyzer> 514*
|Test connectivity to port 514 on the Fortianalyzer. If pings are allowed between them, you can also try pinging.
|*diagnose sniffer packet any 'port 514' 4*
|Run sniffer on Fortigate to see if devices exchange packets on port 514. Click in GUI on `Test Connectivity` to initiate connection.
|===