Troubleshooting Tip: How to troubleshoot packet drops issue on FortiGate when IPS profile is enabled
| Description | This article describes the steps to collect troubleshooting data for packet drop issues on FortiGate firewalls, particularly when using IPS profiles. |
| Scope | FortiGate with IPS Engine build version 1040 or 1148. |
| Solution | To troubleshoot packet drops on FortiGate firewalls, open up 3 CLI windows in the FortiGate and follow these steps:
CLI Window 1: Collect debug logs: Run the debug flow and IPS debug to collect debug logs for the specific port and protocol.
To reset the debug:
diagnose debug reset
To enable the debug:
diagnose debug flow filter addr x.x.x.x <----- Input the client IP that is having an issue. diagnose debug enable
To stop the debug:
diagnose debug disable
For more details on additional filtering options on the debug flow, refer to this article : Technical Tip: How to filter for IP addresses and address ranges in debug flow
For more details on additional filtering options on IPS debug, refer to this article : Troubleshooting Tip: Collecting IPS engine related debugs
CLI Window 2: Capture the traffic flows: Use the sniffer command to capture traffic flows and identify any packet drops or anomalies.
diagnose sniffer packet any "host x.x.x.x and port x" 6 0 l <----- Input the specific client IP and port that is having an issue.
Note: If no traffic is seen on the capture, ensure that acceleration is disabled to appreciate the traffic on the sniffer:
config firewall policy edit 1 set auto-asic-offload disable end
CLI Window 3: Collect IPS engine information, interface statistics, and attempt to find the client session in the session table.
fnsysctl date
Clear the session when it ends:
Other troubleshooting considerations to narrow down the issue further :
Example(s) :
If further assistance is needed or for answers to inquiries, contact Fortinet Technical Support.
Related article: |
