[j-nsp] Ex Series Bandwidth Policer

[Dave Diller]

On May 19, 2009, at 6:02 PM, masood at nexlinx.net.pk wrote:

> The way you have done it, bandwidth will be shared among multiple
> interfaces. Adding filter-specific knob to the policer will make them
> unique.

The documentation doesn't seem to indicate that "policer will by  
default be shared among multiple interfaces" is the case, unless EX is  
different from mainline in it's implementation of a long-standing knob.

http://www.juniper.net/techpubs/en_US/junos9.5/information-products/topic-collections/config-guide-policy/policy-configuring-multifield-classifiers-for-policing.html#id-11064174

---
When you configure the filter-specific statement, a single policer set  
is created for the entire filter. All traffic matching the terms of  
the firewall filter with the action policer goes through that single  
policer. The default is a term-specific policer in which a single  
policer set is created for each term within the filter. All traffic  
matching the terms of the firewall filter with the action policer goes  
through the part of the policer that is specific to that term.
---

So this knob just widens the scope from one term to the whole filter  
so that you can police multiple terms/types of traffic in one  
aggregate token bucket, and has nothing to do with sharing policers  
amongst multiple interfaces.

-dd