Troubleshooting Tip: How to view interface Transmitted and Received packet drops

[sahmed_FTNT]

Description	This article describes a packet drop issue which can cause significant impact on traffic. Higher packet drops may reduce speed and frequent freeze of internal and external applications.
Scope	All supported versions of OS.
Solution	For troubleshooting and log collection, use the following command: fnsysctl cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed fortilink: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 internal: 532373697 5966599 0 0 0 0 0 0 3066603487 4608525 0 0 0 0 0 0 naf.root: 0 0 0 0 0 0 0 0 152 2 0 0 0 0 0 0 npu0_vlink1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 wan2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 internal4: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 test: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 havdlink1: 152 2 0 0 0 0 0 0 152 2 0 0 0 0 0 0 tun_fgfm: 89094 418 0 0 0 0 0 0 86151 464 0 0 0 0 0 0 FGT-3rd Party: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 dmz: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 npu0_vlink0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 port_ha: 0 0 0 0 0 0 0 0 94 1 0 0 0 0 0 0 wan1: 4222075508 6957002 0 0 0 0 0 0 2051581437 7392824 0 0 0 0 0 0 internal3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 vsys_ha: 152 2 0 0 0 0 0 0 152 2 0 0 0 0 0 0 root: 4419506 41405 0 0 0 0 0 0 4419506 41405 0 0 0 0 0 0 havdlink0: 152 2 0 0 0 0 0 0 152 2 0 0 0 0 0 0 internal7: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 dummy0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 nturbo_tx: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 nturbo_rx: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 vsys_fgfm: 737998 6135 0 0 0 0 0 0 737998 6135 0 0 0 0 0 0 internal2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 internal6: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 l2t.root: 0 0 0 0 0 0 0 0 152 4 0 0 0 0 0 0 internal1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ssl.root: 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 modem: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 internal5: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The output above shows separate logs for Transmit and Receive, along with interface counter values like 'errors' and 'drop'. Also, to view details of the specific interface including speed, duplex and crc errors, use the following command: diagnose hardware deviceinfo nic abc <- abc is the interface name.