•
Filter-specific—Shares the same parent policer across all the child policer instances
of the same filter. This mode is not supported on ACX routers.
•
Interface-specific—Shares the same parent policer across all the child policer instances
of the same logical interface. This mode is not supported on ACX routers.
You can include the aggregate global statement at the [edit firewall policer
policer-template-name] hierarchy level to define an aggregate policer to be shared or
applicable across all of the child policer instances in the router. You can include the
aggregate parent statement at the [edit firewall policer policer-template-name] hierarchy
level to define an aggregate policer as the parent policer. The following statement does
not take effect for aggregate policers: set firewall policer policer-template-name
filter-specific.
Consider a sample deployment in which an aggregate policer named P3 is configured.
P1 and P2 are child policers. T1, T2, T3, and T4 are terms. F1 and F2 are filters. Logical
interfaces, IFL1 and IFL2, are created on the underlying physical interfaces, IFD1 and IFD2
in this configuration. Interface address families are correspondingly created on the
interfaces as IFF1 and IFF2.
If you configure an interface-specific filter, term-specific child policer, and the aggregate
policer as the global policer, a single instance of P3 is created and associated with the
child policers, P1 and P2. Two instances each of P1 and P2 are created, one for T1 within
F1 and the other for T2 within F1. The two instances each of P1 and P2 are associated
with IFL1 and IFL2, which in turn are bound to IFD1 and IFD2.
If you configure an interface-specific filter, term-specific or filter-specific child policer,
and the aggregate policer is physical interface- specific policer, two instances of P3 are
created. One instance of P3 contains two child policer instances of P1. P1 contains the
filter F1 and term T1 to be applied to IFL1 and IFL2. The other instance of P3 contains two
child policer instances of P1. P1 contains F1 and T1 to be applied to another two logical
interfaces, IFL3 and IFL4.
If you configure an interface-specific filter, term-specific child policer, and
interface-specific aggregate policer, two instances of P3 are created. Each P3 instance
contains two P1 instances. One P1 instance contains F1 and T1 for IFF1 to be applied to
IFL1. The other P1 instance contains F2 for IFF2 to be applied to IFL1. The other P3 instance
contains two P1 instances. Here, one P1 contains F1 and T1 for IFF3 and the other P1
contains F2 and T1 for IFF4 to be applied on IFL2.
If you configure an interface-specific filter, term-specific child policer, and filter-specific
aggregate policer, two P3 instances are created. Each P3 contains two P1 instances. One
P1 contains P1, T1, F1 IFF1, applied to IFL1. The other P1 contains P1, T2, F1, IFF1, applied to
IFL1. The third P1 contains P1, T3, F2, IFF2, applied to IFL1. The last P1 contains P1, T4, F2,
IFF2, applied to IFL1.
Related
Documentation
Hierarchical Policers on ACX Series Routers Overview on page 920•
• Guidelines for Configuring Hierarchical Policers on ACX Routers on page 921
• Hierarchical Policer Modes on page 923
Copyright © 2017, Juniper Networks, Inc.930
ACX Series Universal Access Router Configuration Guide
To Next Page
Loading...
Need help?
General
