Study guide
1.6 System Logging, Diagnostics & Troubleshooting Tools
Fortinet FCP - FortiGate 7.6 Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About the Fortinet FCP FortiGate Administrator Exam (FCP_FGT_AD-7.6) How to Study and Prepare for FortiOS 7.6 Certification
2 Chapter 1: Deployment & System Configuration
1.1 Initial Configuration, GUI/CLI Management & Admin Profiles 1.2 FortiGuard Services, Licensing & Firmware Upgrades 1.3 Virtual Domains (VDOMs) & System Operation Modes 1.4 Fortinet Security Fabric & Device Integration 1.5 High Availability (FGCP) Configuration & Election 1.6 System Logging, Diagnostics & Troubleshooting Tools 1.7 FortiGate CNF, FortiGate VM in Public Cloud & FortiSASE Administration
3 Chapter 2: Firewall Policies & NAT
2.1 Firewall Policy Matching & Object Management 2.2 Source Network Address Translation (SNAT) & IP Pools 2.3 Destination NAT (DNAT), Virtual IPs (VIPs) & Central NAT
4 Chapter 3: Content Inspection & Security Profiles
3.1 Flow-Based vs Proxy-Based Inspection Modes 3.2 Antivirus & FortiSandbox Integration 3.3 Intrusion Prevention System (IPS) Configuration 3.4 Web Filtering & Static URL Management 3.5 Application Control & Traffic Shaping 3.6 DNS Filtering & Botnet C&C Protection
5 Chapter 4: Authentication & FSSO
4.1 Local & Remote Authentication (LDAP, RADIUS, 2FA) 4.2 Fortinet Single Sign-On (FSSO) Architecture & Modes
6 Chapter 5: Routing & SD-WAN
5.1 Static Routing, Policy Routes & Reverse Path Forwarding 5.2 SD-WAN Architecture, Performance SLAs & Balancing Rules
7 Chapter 6: SSL VPN & IPsec VPN
6.1 SSL VPN Web Mode & Tunnel Mode Configuration 6.2 IPsec VPN Phase 1 & Phase 2 Fundamentals 6.3 Advanced IPsec Topologies (Hub-and-Spoke & ADVPN)
8 Chapter 7: SSL/SSH Inspection
7.1 SSL Certificate Inspection vs Deep SSL/SSH Inspection 7.2 CA Certificates, Port Handling & Inspection Exemptions
1.6 System Logging, Diagnostics & Troubleshooting Tools
Key Takeaways Explain This Topic AI
FortiOS categorizes log events into three broad types: Traffic Logs (session flow metrics), Event Logs (system/operational state changes), and Security Logs (security profile detections).
Log severity levels range from 0 (Emergency - system unusable) down to 7 (Debug - verbose diagnostic data).
The packet sniffer command diagnose sniffer packet <interface> '<filter>' <level> <count> <timestamp> captures live network traffic; level 6 displays headers, payload, and absolute timestamps.
Inspecting stateful session details requires configuring filters via diagnose sys session filter <parameter> before displaying active connections with diagnose sys session list.
Real-time control plane and data plane packet flow tracing is executed using the diagnose debug flow trace start <count> command suite.
Last updated: July 2026
System Logging, Diagnostics & Troubleshooting Tools
Effective network security administration and incident response depend on comprehensive event logging and real-time command-line diagnostic capabilities. FortiOS 7.6 provides a sophisticated logging framework alongside granular CLI troubleshooting tools that allow administrators to inspect packet flows, diagnose session drop causes, monitor SPU/CPU performance, and trace control plane protocols.
FortiOS Logging Architecture & Event Classifications
FortiOS organizes log messages into a structured hierarchy divided into three main Log Types :
1. Traffic Logs
Record network session connection events traversing the firewall.
Forward Traffic Logs : Sessions allowed or denied by IPv4/IPv6 firewall policies.
Local Traffic Logs : Administrative management traffic terminating on or originating from FortiGate interfaces (e.g., HTTPS GUI, SSH, PING).
Multicast / Violation Logs : Traffic matching multicast policies or dropped due to network protocol violations.
2. Event Logs
Record system operational events, configuration changes, and administrative actions.
System Events : Administrator logins, interface status changes, HA failovers, firmware upgrades, and resource alerts.
User / Router / VPN Events : Authentication events, dynamic routing neighbor state changes, and IPsec/SSL VPN tunnel status.
3. Security Logs
Record events generated by FortiOS Security Profiles during content inspection.
Contains detailed alerts from Antivirus, Intrusion Prevention System (IPS), Web Filter, Application Control, DNS Filter, File Filter, and DLP.
Log Severity Levels
Every log entry in FortiOS is tagged with an official Syslog-compliant Severity Level ranging numerically from 0 to 7.
Severity Level Name Numeric Code Operational Meaning & Example Event
Emergency emergency 0 System is unusable. (e.g., Immediate hardware failure impending).
Alert alert 1 Action must be taken immediately. (e.g., FortiGuard subscription expired).
Critical critical 2 Critical system condition. (e.g., HA cluster node lost/unreachable).
Error error 3 Error operational condition. (e.g., IPS engine process crash).
Warning warning 4 Warning condition. (e.g., High memory usage threshold breached > 80%).
Notification notification 5 Normal but significant condition. (e.g., Administrative user login success).
Information information 6 Informational message. (e.g., Security policy rule modification committed).
Debug debug 7 Verbose diagnostic output. (e.g., Detailed packet flow trace logs).
Remote Log Storage Destinations
To prevent flash storage degradation and satisfy regulatory compliance retention mandates, logs should be forwarded to remote collectors: # Configuring central FortiAnalyzer logging destination via CLI
- config log fortianalyzer setting
- set status enable
- set server 10.10.10.100
- set mode real-time
- set enc-algorithm high
- set upload-option real-time
- end
- Packet Sniffing: diagnose sniffer packet
FortiOS includes an on-box packet capture tool analogous to tcpdump . It captures packets passing through network interfaces at Layer 2/3.
- Syntax
- diagnose sniffer packet <interface> '<pcap_filter>' <verbose_level> <count> <timestamp>
- Verbose Output Levels
Level 1 : Print header of packets (Src IP, Dst IP, Ports, TCP flags).
Level 2 : Print header and packet payload data in hex format.
Level 3 : Print header and packet payload data in hex and ASCII format.
Level 4 : Print interface name and header of packets.
Level 5 : Print interface name, header, and packet payload in hex/ASCII.
Level 6 : Print interface name, header, payload in hex/ASCII, and absolute timestamp .
Practical Sniffer Commands # Capture 10 packets on any interface matching destination IP 192.168.1.50 and HTTP port 80 with timestamps
diagnose sniffer packet any 'host 192.168.1.50 and port 80' 6 10 a
- # Capture ICMP ping packets traversing port1
- diagnose sniffer packet port1 'icmp' 4 20 l
- Stateful Session Table Inspection
The FortiOS kernel maintains a stateful session table tracking active TCP, UDP, and ICMP connections. Inspecting active sessions is essential for diagnosing NAT issues, policy drops, and routing mismatches.
- Filtering and Inspecting Sessions # Step 1: Clear existing filters and define source IP filter
- diagnose sys session filter clear
- diagnose sys session filter src 10.0.1.100
- diagnose sys session filter dport 443
- # Step 2: Print filtered active session list details
- diagnose sys session list
- # Step 3: Clear all sessions matching current filter (Use with caution!)
- diagnose sys session clear
- Packet Flow Tracing: diagnose debug flow
When a packet is dropped unexpectedly, diagnose debug flow reveals the internal step-by-step decision processing of the FortiOS kernel—including policy matching, route lookups, NAT transformations, and Security Profile evaluations.
- Execution Sequence # Step 1: Reset debug filters and define target IP filter
- diagnose debug reset
- diagnose debug flow filter addr 192.168.1.100
- diagnose debug flow filter port 443
- # Step 2: Enable console display output and set trace packet count limit
- diagnose debug flow show console enable
- diagnose debug flow trace start 10
- # Step 3: Enable global debug engine
- diagnose debug enable
- # Step 4: After capturing output, disable debug engine
- diagnose debug disable
- Core System Status & Network Diagnostics # Test network reachability from specific source interface IP
- execute ping-options source 10.0.1.99
- execute ping 8.8.8.8
- # Trace network hop paths to target IP
- execute traceroute 1.1.1.1
- # Display global performance status (CPU, Memory, Session creation rate)
- get system performance status
- FortiOS Diagnostic & Troubleshooting Command Matrix
Diagnostic Tool Command Primary Operational Purpose Typical Troubleshooting Scenario
diagnose sniffer packet Layer 2/3 live packet capture Verifying if packets reach an interface or leave proper VLANs.
diagnose sys session list Inspect stateful session table Verifying NAT IP translations, session timeouts, and SPU offload flags.
diagnose debug flow Kernel packet processing trace Determining exact firewall rule drops, route lookup failures, or reverse path drops.
get system performance status CPU, Memory & Session rate monitor Investigating high resource utilization, conserv mode, or SPU overload.
execute ping-options Custom ICMP reachability testing Testing IP connectivity sourcing traffic from specific internal interface subnets.