FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
otsaggos
Staff
Staff
Article Id 337400
Description

This article describes which logs to gather when dealing with NP6 packet drop issues.

 

FortiGate with NP6 processors include the following:

FortiGate-300E, 301E 400E, 401E, 500E,501E, 600E, 601E, 800D, 900D, 1000D, 1500D, 1500D-DC, 1500DT, 1100E, 1101E 2000E 2200E  2201E 2500E  3000D 3100D 3200D 3300E 3400E and 3401E 3600E 3601E 3700D 3960E 3980E  5001E 5001E1 6000F series, 7030E 7040E 7060E FIM-7901E FIM-7904E FIM-7910E FIM-7920E FPM-7620E FPM-7630E.

Scope

FortiGate v7.4.x, FortiGate v7.6.x.

Solution

In higher-end FortiGate units with multiple NP6 chips, packet drops may be associated with a specific NP6 chip. To identify the problematic NP6 chip:

 

  1. Determine the ingress and egress interfaces for the traffic experiencing drops, and check possible high memory or CPU consumption that might cause the packet drop:

 

   get sys performance status

diagnose hardware devinfo nic <port>

 

  1. Use the following command to view NP6 port mappings:

 

diagnose npu np6 npu-feature <----- Show NPU feature and status.

get hardware npu np6 port-list

diagnose npu np6 port-list

 

  1. Check drop statistics for the NP6 chip with these commands:

 

diagnose npu np6 dce <np6_id>           <----- Shows non-zero sub-engine drop counters.
diagnose npu np6 anomaly-drop <np6_id>  <----- Shows L3/L4 anomaly check drop counters.
diagnose npu np6 hrx-drop <np6_id>      <----- Shows host interface drop counters.
diagnose npu np6 sse-stats <np6_id>     <----- Shows hardware session statistics (Useful to identify session-drift and PBA leak problem.
diagnose npu np6 session-stats <np6_id> <-----Shows session offloading statistics.
diagnose npu np6 xgmac-stats <np6_id>   <----- Shows tx and rx counters in NP6

 

  1. Run these commands multiple times. The initial output may include cumulative data from when the counters were last reset, which could include drops not related to the current issue. Discard the first output and use the results from the second run onward to accurately identify drop counters. Perform this during the issue period for accuracy.
  2. To get a clearer view of changes, reset the counters and check again with:

 

diagnose npu np6 sse-stats-clear <np6_id>     <----- Clears session statistics counters.
diagnose npu np6 session-stats-clear <np6_id> <----- Clears session offloading statistics.
diagnose npu np6 xgmac-stats-clear <np6_id>   <----- Clears traffic counters.