LogicalRouterPortCounters
Provides the statistics for a logical router port since the time it was created. The statistics will be reset on edge reboot or edge dataplane restart. It includes the following counters for the port:
- Incoming packet count.
- Outgoing packet count.
- Dropped packet count.
- Error/Failure reason for the dropped packet.
{
"blocked_packets": 0,
"dad_dropped_packets": 0,
"destination_unsupported_dropped_packets": 0,
"dropped_packets": 0,
"firewall_dropped_packets": 0,
"frag_needed_dropped_packets": 0,
"ipsec_dropped_packets": 0,
"ipsec_no_sa_dropped_packets": 0,
"ipsec_no_vti_dropped_packets": 0,
"ipsec_pol_block_dropped_packets": 0,
"ipsec_pol_err_dropped_packets": 0,
"ipv6_dropped_packets": 0,
"kni_dropped_packets": 0,
"l4port_unsupported_dropped_packets": 0,
"malformed_dropped_packets": 0,
"no_arp_dropped_packets": 0,
"no_linked_dropped_packets": 0,
"no_mem_dropped_packets": 0,
"no_receiver_dropped_packets": 0,
"no_route_dropped_packets": 0,
"non_ip_dropped_packets": 0,
"proto_unsupported_dropped_packets": 0,
"redirect_dropped_packets": 0,
"rpf_check_dropped_packets": 0,
"service_insert_dropped_packets": 0,
"total_bytes": 0,
"total_packets": 0,
"ttl_exceeded_dropped_packets": 0
}The total number of packets blocked on the port. This could be due to either port is operatively down or blocked. The port can be blocked due to admin-down, backplane port is in standby SR (internal operational state is down) etc. It also includes drops when a tunnel port receives packet with local VTEP which is not the assigned one. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped because source IP is not assigned to the logical port. For IPv6 address, it could be due to DAD (Duplicate Address Detection) status of the IP is not in ASSIGNED state. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped because the destination address in the packet - broadcast, multicast, loopback or reserved address - is not supported on the port. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped on the port since the time the logical router port was created. This will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to firewall rules or firewall state mismatch (For example, the expected sequence number in TCP window was not received). The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped because they could not be fragmented when their size was larger than the port MTU due to DF bit set in them. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of IPSec packets dropped on the port since the time the logical router port was created. This will be reset on edge reboot or edge dataplane restart.
The total number of IPSec packets dropped due to missing security association. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of IPSec packets dropped due to missing Virtual tunnel interface (VTI) in the security association. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of IPSec packets dropped due to a discard policy configured for the traffic. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of IPSec packets dropped due to policy lookup failure for the packets in the security policy database. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of IPv6 packets dropped on the port since the time the logical router port was created. This will be reset on edge reboot or edge dataplane restart.
The total number of packets that the DPDK kernel NIC interface failed to send to the linux kernel. For example BGP packets, Load balancer etc. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped for having an unknown/unsupported L4 port (TCP or UDP) and destination IP which is owned by the logical router ports including the loopback port. For example, if we receive a UDP packet whose port does not map to the expected port of BFD, AppHA, IPSec or DHCP, then we drop it. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of malformed packets dropped on the port due to IP checksum error by IP checksum verification or the physical NIC (vmxnet3 for VM or other NIC for BM) marks the IP checksum error. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to incomplete ARP resolution of the next-hop. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped because the port did not have a linked peer port. For example, the logical router port is not connected to a segment port. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to insufficient memory. One such example is the mBuf pool memory. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to absence of the receiver. This could happen when the protocol is not supported by the logical router, or the corresponding tunnel does not exist. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped because no route exists for the IP destination of the packets. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of non-IP packets dropped because only IP packets are allowed on the port. For example spanning tree BPDU packets. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped because the known protocols such as ARP, ICMP, DHCP cannot be decoded/fully supported. Also, when the ether-type is MPLS but the IP version is not 4 nor 6. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to redirection of packet to Kernel NIC Interface(KNI) failed. This could be due to either the redirected interface is a non-KNI interface or we could not fetch the mapping KNI interface for the UUID of the redirected interface. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to RPF check failure. It is applicable to both unicast and multicast. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.
Total number of service insertion packets dropped.
The total number of bytes transferred since the time the logical router port was created. This will be reset on edge reboot or edge dataplane restart.
The total number of packets transferred since the time the logical router port was created. This will be reset on edge reboot or edge dataplane restart.
The total number of packets dropped due to exceeded TTL. The counts are from the time the logical router port was created and will be reset on edge reboot or edge dataplane restart.