show user-plane-service statistics drop-counter
The show user-plane-service statistics drop-counter command displays the packet drop statistics with the respective cause (drop reason) at instance-level and session-level.
The following is a sample output of this command:
[local]UPF1# show user-plane-service statistics drop-counter
Packet Drop Data Statistics:
-----------------------------------------------------
NAT packets processing failure
NAT on demand handling: 0
IP allocation is in progress: 0
ICMP Packet translation: 0
FIREWALL packets processing failure
Policy not found: 0
No Matching GX rule found: 0
Flow apply action
Discard: 0
Readdress Failure: 0
Packet exceeds the MTU size: 0
Failure in processing FAR Buffer packets: 0
FAR Apply Action Drop: 0
Traffic Steering Failure: 0
QER Gate Status Closed: 0
Content-filtering Discard Action: 0
IP Header Validation Failed: 0
ADF level failure
UL TEID/QFI key mismatch: 0
DL TFT mismatch: 0
DL QFI mismatch: 0
URL Blacklisting Discard Action: 0
DDN buffer overflow drop packets: 0
APN AMBR Packets Drop: 0
ITC Packets Drop: 0
ACL Drop: 0
CC Dropped Packets: 0
FastPath Misc Drops
Overload Protection: 0
Invalid Client: 0
Stream ID 0: 0
Invalid Stream ID: 0
NOTES:
-
For the show user-plane-service statistics drop-counter CLI command, the counters for the number of packets dropped due to various reasons will not be recovered post sessmgr recovery or ICSR (Inter-Chassis Session Recovery).
-
For the show subscribers user-plane-only callid callid_value drop-statistics CLI command, the counters for the number of packets dropped due to various reasons will be recovered post sessmgr recovery or ICSR.
-
The commands will not duplicate the counters that are captured at the session-level and instance-level.
-
The packets dropped due to "Quota Exhaust FAR Apply Action Drop" will be accumulated under "CC Dropped Packets" and not under the "FAR Apply Action Drop" counter.
-
The packets dropped under "Failure in processing FAR buffered packets" can be due to "no rule match", "teid not found", or other reasons. The respective counter will be incremented for such packets.