04-07-2011 02:17 PM
Hello,
I have the following problem with rate-limit on aggregate interface:
04-07-2011 03:27 PM
You need to "apply" the policier using a firewall filter. What you did was to define the policier values but they are implemented via firwewall filter.
firewall {
family inet {
filter filter-example-1 {
term policer-example-term {
from {
protocol tcp; <your match condition that the traffic is tested on>
}
then {
policer 2300m-pipe; <your action to be taken for this traffic>
}
}
}
Note that the default behavior when using firewall filters is to reject ALL traffic that is not specifcally processed by the match / then clauses. So if you matched on a specific subnet cause that was what you were trying to throttle then you would also need a second term with a clause of accept to allow the remaining "non-matched" traffic to be processed.
IE:
term accept-other-traffic {
then accept;
}
}
}
04-08-2011 01:20 AM
Hi,
what exactly does not work and on which plattform? Your configuration with policer defined under logical unit is OK.
Kind Regards
Michael Pergament
04-13-2011 06:53 AM
Hi,
The router is Juniper MX960.
Everything works fine(rate-limit) if the traffic is not on aggragate interface. The customer doesn't use more then the speed in rate-limit.
If I set the rate-limit on aggregate interface the rate-limit doesn't work.
Thank you.
Best regards.