By default, when a user assigns a filter policy to a LAG endpoint, the system allocates
the same user-configured rate limit policer value for each FP of the LAG.
The shared policer feature changes this default behavior. When configured to
true, the filter policy can only be assigned to endpoints of the
same LAG and the configured rate limit policer value is shared between the LAG complexes
based on the number of active ports in the LAG on each complex.
The formula to identify the policer value assigned to each FP complex is the
following:
- for same-speed LAGs
filter
entry rate limit policer value per FP = (configured rate limit) * (number of
active ports in the LAG for this FP) / (number of active ports in the
LAG)
- for mixed-speed LAGs and LAGs with a user-configured
hash-weight
filter entry rate limit policer value per FP
= (configured rate limit) * (sum of the weights of all active ports for this
FP) / (sum of the weights of all active ports in the
LAG)
The shared policer feature is supported for IPv4 and IPv6 filter policies with the
template or exclusive scope, in ingress and egress directions.
Note:
- Rate limit policer entries embedded in template or exclusive filters follow the
shared policer setting from that filter.
- SR-a and VSR do not support the shared policer feature.
- Configuration combinations with LAG per-link-hash,
per-fp-egr-queuing,
per-fp-sap-instance, link-map-profile,
adapt-qos port-fair, and ESM do not support the shared
policer feature.