[j-nsp] sampled problem

[Yulianto Ko]

Hi Jonas,

I don't recall seeing this problem before.  I tried your config and I was
not able to reproduce it.
Can you try restarting sampled and see if it fixes the problem.  You can
also try deactivating the forwarding-options sampling config.
Also, check /var/log/sampled and see if there is anything that looks
suspicious.

Thanks,
Yulianto

On Wed, 25 Feb 2004, Jonas Frey (Probe Networks) wrote:

> Hi,
>
> ive setup sampling some time ago but have removed all sampling
> configurations since then. Now when i apply some packet filtering rule
> to an interface, the cpu usage of the RE jumps to 100%, all used up by
> sampled:
>   PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
>  9785 root      88  15 18460K 17896K RUN      5:04 96.29% 96.29% sampled
>
> I even have
> forwarding-options {
>     sampling {
>         disable;
>     }
> }
>
> but still the same effect.
>
> My filter rule looks like:
> firewall {
>     filter fw {
>         term term1 {
>             from {
>                 address {
>                     some-block-here/prefix;
>                 }
>             }
>             then {
>                 discard;
>             }
>         }
>         term term2 {
>             then accept;
>         }
>     }
> }
>
>
> Running JunOS 6.0R1.6.
>
> Regards,
> Jonas
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>