Tag :: Rate Limiting

Control Plane Policing (CoPP) classifies control plane traffic into different classes (e.g., IGMP, LLDP, PTP, OSPF) and applies rate limiting per class using queues shaping. However, when multiple flows within the same CoPP class share a single queue, a single high-rate flow can consume the entire allocated bandwidth for that class, starving other legitimate flows.

Control Plane Policing (CoPP) classifies control plane traffic into protocol classes (e.g., IGMP, LLDP, BGP) and applies rate limiting per class using queue shaping. On supported platforms, all control plane traffic for a given protocol class is directed to a single queue regardless of the ingress port. As a result, a high-rate flow from a single port or host can consume the entire bandwidth allocated to that class, starving legitimate control plane traffic arriving on other ports.

Rate limiting of mirrored traffic provides support to control the rate of mirrored traffic that can egress the switch. This feature can be applied to both regular port mirroring and encapsulated mirroring (e.g., mirroring to GRE tunnel), depending on the platform.

This feature enables policer (using policy-map) on a VTEP to rate limit traffic per VLAN/VNI. The policer can be applied in both input and output directions to rate limit decapsulated and encapsulated VXLAN traffic, respectively. Prior to EOS-4.32.0F, the policers are not applicable on multicast traffic through the VTEP. For platforms supporting rate limiting of both bridged and routed encapsulated traffic, the rate limiting would be done on common policer limits.