FortiGate Inf 08 Diagnostics
FortiGate Inf 08 Diagnostics
Diagnostics
FortiOS 7.0
© Copyright Fortinet Inc. All rights reserved. LastLast
Modified:
Modified:
Saturday,
Saturday,
August
August
19, 19,
20232023
Lesson Overview
General Diagnosis
Debug Flow
Objectives
• Identify your network’s normal behavior
• Monitor for abnormal behavior, such as traffic spikes
• Diagnose problems at the physical and network layers
3
Before a Problem Occurs
• Know what normal is (baseline): Abnormal
• CPU usage
• Memory usage
• Traffic volume
• Traffic directions
• Protocols and port numbers
• Traffic pattern and distribution
• Why?
• Abnormal behavior is difficult to identify,
unless you know, relatively, what normal is
Now
Baseline (Average)
Normal Range
port2
• Include cables, ports, and physical network 192.168.3.1/30
devices
• Show relationships at Layer 1 and Layer 2 port1
192.168.1.2/30
• Logical diagrams:
wan1
• Include subnets, routers, logical devices 192.168.1.1/30
port1 port2
• Show relationships at Layer 3 10.0.10.1/24 192.168.2.1/24
Web server
192.168.2.2/24
port4
• Tools:
• Security Fabric
• Dashboard
• SNMP
• Alert email
• Logging/Syslog/FortiAnalyzer
• CLI debug commands
Traffic spikes
FortiGate Interface
Connecting device IP address
and MAC address
General Diagnosis
Debug Flow
Objectives
• Diagnose connectivity problems using the debug flow
13
Debug Flow
• Shows what the CPU is doing, step-by-step, with the packets
• If a packet is dropped, it shows the reason
• Multi-step command
1. Define a filter: diagnose debug flow filter <filter>
2. Enable debug output: diagnose debug enable
3. Start the trace: diagnose debug flow trace start <xxx> Repeat number
4. Stop the trace: diagnose debug flow trace stop
Destination NAT
id=2 line=2733 msg="DNAT 10.200.1.1:49886->10.0.1.10:49886"
General Diagnosis
Debug Flow
Objectives
• Diagnose resource problems, such as high CPU or memory
usage
• Diagnose memory conserve mode
• Diagnose fail-open session mode
19
Slowness
• High CPU usage
• High memory usage
end
• off :All new sessions with content scanning enabled are not passed
• pass (default): All new sessions pass without inspection
• one-shot: Similar to pass in that traffic is not inspected. However, it will keep bypassing the AV proxy even
after leaving conserve mode. Administrators must either change this setting, or restart the unit, to restart the AV
scanning
General Diagnosis
Debug Flow
Objectives
• Format the flash memory
• Load a firmware image from the BIOS menu
• Run hardware tests
• Display crash log information
30
Access to BIOS Menu
FGT60D (18:34-05.05.2021)
Ver:04000005 BIOS version. Options in the BIOS
Serial number:FG60DXXXXXXXX menu depend on the version.
RAM activation
Total RAM: 512MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done. Press any key at this
Zeroing IRQ settings...Done. prompt to enter the BIOS
Verifying PIRQ tables...Done. menu.
Enabling Interrupts...Done.
Boot up, boot device capacity: 122MB.
Press any key to display configuration menu...
......
Enter G,F,B,I,Q,or H:
.....
© Fortinet Inc. All Rights Reserved. 37
Crash Logs
• Inspect crash logs for debugging purposes
• Any time a process closes, it is recorded as killed
• Some are normal (for example, closing scanunit to update definitions)
• Entering:
12: 2021-04-06 14:10:16 logdesc="Kernel enters conserve mode" service=kernel
conserve=on free="127962
13: 2021-04-06 14:10:16 pages" red="128000 pages" msg="Kernel enters conserve
mode"
• Exiting:
14: 2021-04-06 14:19:55 logdesc="Kernel leaves conserve mode" service=kernel
conserve=exit
15: 2021-04-06 14:19:55 free="192987 pages" green="192000 pages" msg="Kernel
leaves conserve mode"
General Diagnosis
Debug Flow