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. -- ++ytti _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
