Troubleshooting Tip: Increasing error counters on DROP_IHP1_PKTCHK counter for NP6 and NP6xlite devices

[Nivedha]

Description	This article discusses how to troubleshoot increasing error counters on the DROP_IHP1_PKTCHK counter for NP6 and NP6xlite devices.
Scope	FortiGate NP6 and NP6xlite devices.
Solution	If a packet is dropped by the NP6 or Np6xlite process, run the 'diagnose npu np6/np6xlite dce <int>' command to verify which register is dropping the packet: Firewall-01 # diagnose npu np6xlite dce 0 DROP_IHP1_PKTCHK:0000000000000810[5b] DROP_TPE_SHAPER :0000000001113178[94] STAT_EHP1_INCR_FRAG:0000000000000018[a7] The 'drop_ihp1_pktchk' counter refers to the number of dropped IP packets at the IHP1 level. This counter indicates the quantity of IP packets that were not successfully processed and were therefore dropped at this specific processing level within the NP6 processor. The IHP1 level in NP6 refers to the first level of processing within the NP6 processor. It is responsible for handling and processing incoming IP packets before further processing occurs in subsequent levels within the NP6 architecture. The IHP1 level in the NP6 processor may drop packets due to various reasons, such as: Overload: If the incoming traffic exceeds the processing capacity of the IHP1 level, packets may be dropped to prevent system overload. Configuration Issues: Misconfigurations in the traffic shaping rules or policies can lead to packet drops at the IHP1 level. Resource Constraints: Insufficient resources or memory allocation for processing packets at the IHP1 level can result in dropped packets. Traffic Shaping: If the traffic shaper is overloaded or misconfigured, it may cause packets to be dropped at the IHP1 level. To address packet drops at the IHP1 level, it is essential to review the configuration, monitor system resources, and optimize traffic shaping policies.