[j-nsp] instance-specific filters for VPLS BUM/flood filtering

[Christopher E. Brown]

And I have tested and seen exactly the opposite with 10.4R10 in both
MX80 and all trio MX960.


Create a policer and a vpls filter that matches unknown ucast, bcast and
mcast.

Apply to VPLS forwarding table in 2 instances

...

Two filter instances, but one shared policer.


On 11/6/12 12:00 AM, Saku Ytti wrote:
> On (2012-11-05 10:44 +0100), Sebastian Wiesinger wrote:
> 
>> And there I'm missing a instance-specific knob. The only reference I
>> find to "instance-specific" is this:
>>
>> | To enable this higher precedence on BPDU packets, an instance-specific
>> | BPDU precedence filter named default_bpdu_filter is automatically
>> | attached to the VPLS DMAC table
> 
> Your questions is valid. For interfaces you need 'interface-specific' so
> that policers in filter are not shared.
> 
> However for some reason, in VPLS routing-instance forwarding-options the
> filter policers are instance-specific, so if your policer says 5Mbps, each
> instance where it is applied gets 5Mbps. Tested in MX960 11.4R5. I don't
> quite understand why it is like this, or where it is documented.
> 
> I would have expected they are shared. As if you use forwarding-options
> filters to limit IP options, and apply same filter to main instance and
> routing-instances, then the policer is shared, so 5Mbps IP options is
> shared amongst all routing-instances and global instance. Tested in 10.4R2
> or so.
> 
> Does not seem consistent, and I fear if it is intended feature or not, as
> I've not found documentation.
> 


-- 
------------------------------------------------------------------------
Christopher E. Brown   <chris.brown at acsalaska.net>   desk (907) 550-8393
                                                     cell (907) 632-8492
IP Engineer - ACS
------------------------------------------------------------------------