You can view the count of dropped data packets for each data protocol by using the netstat -s command. The count of dropped packets might increase when DNS advertises the management IP address to data clients, or data traffic is blocked on e0M, or misconfiguration of static route.
system1> netstat -s ip: 4066350 total packets received 0 bad header checksums 0 with size smaller than minimum 0 with size larger than maximum 0 with data size< data length 0 with header length< data size 0 with data length< header length 0 with bad options 0 with incorrect version number 0 packets with spoofed source address 0 packets arrived on wrong port 0 fragments received the last 2 src addr that send fragments: 0.0.0.0 0.0.0.0 0 fragments dropped (dup or out of space) 0 malformed fragments dropped 0 overlapping fragments discarded 0 fragments dropped after timeout the last 2 src addr that have fragment time out: 0.0.0.0 0.0.0.0 0 packets dropped, too many fragments the last 2 src addr that sent too many fragments: 0.0.0.0 0.0.0.0 0 packets dropped, reassembly queue overflow 0 packets reassembled ok 3958788 packets for this host 0 packets for unknown/unsupported protocol 0 packets forwarded 4986 packets not forwardable 0 redirects sent 3057658 packets sent from this host 0 packets sent with fabricated ip header 0 output packets dropped due to no bufs, etc. 0 output packets discarded due to no route 0 output datagrams fragmented 0 fragments created 0 datagrams that can't be fragmented 498 filtered packets dropped 0 packets dropped due to vfiler mismatch 0 packets forwarded by source interface