Skip to Content.
Sympa Menu

wg-multicast - Re: MSDP SA explosion - sasser worm?

Subject: All things related to multicast

List archive

Re: MSDP SA explosion - sasser worm?


Chronological Thread 
  • From:
  • To: Bill Owens <>
  • Cc:
  • Subject: Re: MSDP SA explosion - sasser worm?
  • Date: Tue, 4 May 2004 09:00:20 -0700 (PDT)


That's per peer. Per-source filter config (I believe...) should look like
this:

source 0.0.0.0/0 {
active-source-limit {
maximum 1000;
threshold 900;
}
}

..in the msdp config block of course. What I also noticed with the
per-source filtering in place, is that it logs which sources excede the
limit:

rtr> show msdp source
-snip-
128.178.25.195 /32 Dynamic 1000 900 36579
128.178.45.143 /32 Dynamic 1000 900 161785
128.178.54.64 /32 Dynamic 1000 900 36429
128.178.61.58 /32 Dynamic 1000 900 9817
128.178.67.167 /32 Dynamic 1000 900 118644
128.178.69.65 /32 Dynamic 1000 900 181518
128.178.78.121 /32 Dynamic 1000 900 67
128.178.85.17 /32 Dynamic 1000 900 225165
128.178.125.121 /32 Dynamic 1000 900 202427
-snip-

Greg

On Tue, 4 May 2004, Bill Owens wrote:

> On Tue, May 04, 2004 at 09:57:59AM -0400, Charles R. Anderson wrote:
> > JunOS 6.3 introduces per-source MSDP SA limits.
>
> It is in the docs as far back as 6.0, and our box running the latest
> patched 5.7 also has the command, though it isn't in the docs:
>
> group foo {
> peer 1.2.3.4 {
> local-address 1.2.3.5;
> active-source-limit {
> maximum 200;
> }
> }
> }
>
> Bill.
>




Archive powered by MHonArc 2.6.16.

Top of Page