02-24-2009 06:28 AM
02-24-2009 10:53 PM
By not correctly rate limiting, exactly what do you mean by that? Also how do you have your policer and firewall filters configured? Given that PC on 7.7.7.x network gets policed correctly, that implies that policers work properly for that subnet (as opposed to traffic from L3 switch). Could it be that your policer did not include 2.x.x.x network?
-Richard
02-25-2009 04:27 AM
Hello! Thanks for your help.
Sorry, I made bad description of my issue. I have forgotten to attach configuration.
Also i've attached conf.file to this post.
admin@j6350-dl# run show firewall
Filter: FILTER
Policers:
Name Packets
POLICER-IN-TERM-IN 7928
POLICER-OUT-TERM-OUT 72694
Filter: __default_bpdu_filter__
02-26-2009 05:24 PM
Can you confirm what IP your traffic is from? Reason I ask is in your routing-options, I see you have static route for 2.0.0.0/8. But your firewall filter terms are for 2.0.0.0/24. Can you verify you meant /24 and not /8?
-Richard
02-26-2009 11:23 PM
Hello, Richard!!
Thanks a lot for your attention to my trouble!!
Yes, my test PC was in /24 network.
This issue solved.
In this test region no latest version of JunOS-ES was installed.
I have upgraded JunOS-ES to Release [9.4R1.8] and this issue was solved.
But in production network corresponding trouble not solved yet. Now I do not know why.
Because we configuring all filters and polisers exactly as in this test region, but policing no work.
So I need some time for detailed research, and describe this issue in production network.
I hope, you do not abandon me in this trouble :-) Thanks!!