wg-multicast - Re: MSDP instability today
Subject: All things related to multicast
List archive
- From: Marshall Eubanks <>
- To: Matthew Davy <>, Al Adler <>,
- Subject: Re: MSDP instability today
- Date: Sun, 14 Jan 2001 13:25:36 -0500
- Organization: Multicast Technologies
Marshall Eubanks wrote:
>
> Matthew Davy wrote:
> >
> > We've seen at least two periods of massive instability with MSDP today.
> > One
> > around 01:30 EST and one around 12:10 EST. All of our routers reported
> > multiple CPUHOG errors relating to MSDP and were running out of memory.
> > My
> > first guess would be a loop or someone just sending a whole ton of SA's.
> >
> > Just wondering if anyone else saw this...
> >
> > - Matt
> >
> > --
> > --------------------
> > Matthew Davy
> >
> > 812-855-7728
> > Network Engineer
> > Indiana University
> > Abilene NOC
> > --------------------
>
> We have been getting lots of
>
> %PIM-6-SA_ENCAP_INVALID: Bad SA from RP 141.142.12.1
>
> messages. That IP is at the NCSA.
>
> Regards
> Marshall Eubanks
>
On the other hand, the Bad SA messages - last at Jan 14 13:05:13 -
previous at Jan 13 18:31:02
do not correlate in time with the CPUHOG messages :
multicasttech-2>show log | include CPUHOG
*Jan 14 01:32:30: %SYS-3-CPUHOG: Task ran for 2028 msec (97/69), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 01:32:58: %SYS-3-CPUHOG: Task ran for 3420 msec (91/49), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 01:33:15: %SYS-3-CPUHOG: Task ran for 4728 msec (99/35), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 01:33:33: %SYS-3-CPUHOG: Task ran for 3524 msec (73/37), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 01:34:03: %SYS-3-CPUHOG: Task ran for 2120 msec (54/29), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:12:40: %SYS-3-CPUHOG: Task ran for 2404 msec (25/1), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:15:43: %SYS-3-CPUHOG: Task ran for 2548 msec (17/14), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:15:53: %SYS-3-CPUHOG: Task ran for 2324 msec (13/9), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:16:06: %SYS-3-CPUHOG: Task ran for 2436 msec (15/13), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:16:29: %SYS-3-CPUHOG: Task ran for 4328 msec (55/24), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:16:40: %SYS-3-CPUHOG: Task ran for 2476 msec (12/9), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:16:58: %SYS-3-CPUHOG: Task ran for 2248 msec (31/20), process
= MSDP Process, PC = 60A20AC0.
*Jan 14 12:18:29: %SYS-3-CPUHOG: Task ran for 4432 msec (86/67), process
= MSDP Process, PC = 60A20AC0.
So the times are the same as for Matt. I do not see anything else weird
from here (yet).
Regards
Marshall Eubanks
Multicast Technologies, Inc.
10301 Democracy Lane, Suite 201
Fairfax, Virginia 22030
Phone : 703-293-9624 Fax : 703-293-9609
e-mail :
http://www.on-the-i.com
- Re: MSDP instability today, (continued)
- Re: MSDP instability today, Matthew Davy, 01/15/2001
- Re: MSDP instability today, Matthew Davy, 01/15/2001
- Norton Ghost Re: MSDP instability today, Philip Pishioneri, 01/15/2001
- Re: Norton Ghost Re: MSDP instability today, Matthew Davy, 01/16/2001
- Re: MSDP instability today, Matthew Davy, 01/15/2001
- Re: MSDP instability today, Bill Fenner, 01/15/2001
- Re: MSDP instability today, Matthew Davy, 01/15/2001
- Re: MSDP instability today, Bill Fenner, 01/15/2001
- Re: MSDP instability today, David Meyer, 01/14/2001
Archive powered by MHonArc 2.6.16.