Hierarchical Policer Configuration Overview
Hierarchically rate-limits Layer 2 ingress traffic for all protocol families. Cannot be applied to egress traffic, Layer 3 traffic, or at a specific protocol level of the interface hierarchy.
Supported on the following interfaces:
-
Ethernet interfaces on Gigabit Ethernet Intelligent Queuing 2 (IQ2) and Ethernet Enhanced IQ2 (IQ2E) PICs.
-
MX Series routers with MPC or DPC.
Table 1 describes the hierarchy levels at which you can configure and apply hierarchical policers.
Policer Configuration |
Layer 2 Application |
Key Points |
|---|---|---|
| Hierarchical Policer | ||
Aggregate and premium policing components of a hierarchical policer: [edit firewall]
hierarchical-policer policer-name {
aggregate {
if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
}
then {
discard;
forwarding-class class-name;
loss-priority supported-value;
}
}
premium {
if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
}
then {
discard;
}
}
}
|
Option A—Apply directly to Layer 2 input traffic on a physical interface: [edit interfaces]
interface-name {
layer2-policer {
input-hierarchical-policer policer-name;
}
}
|
Hierarchically rate-limit Layer 2 ingress traffic for all protocol families and logical interfaces configured on a physical interface. Include the Note:
If you apply a hierarchical policer at a physical interface, you cannot also apply a hierarchical policer to any of the member logical interfaces. |
Option B—Apply directly to Layer 2 input traffic on a logical interface. [edit interfaces]
interface-name {
unit unit-number {
layer2-policer {
input-hierarchical-policer policer-name;
}
}
}
|
Hierarchically rate-limit Layer 2 ingress traffic for all protocol families configured on a specific logical interface. Include the Note:
You must configure at least one protocol family for the logical interface. |
|