wg-multicast - Re: MSDP instability today
Subject: All things related to multicast
List archive
- From: Marshall Eubanks <>
- To: Matthew Davy <>
- Cc: Bill Fenner <>,
- Subject: Re: MSDP instability today
- Date: Mon, 15 Jan 2001 09:39:53 -0500
- Organization: Multicast Technologies
We see something similar :
*Jan 15 06:42:34: %SYS-3-CPUHOG: Task ran for 3116 msec (148/130),
process = MSDP Process, PC = 60A20AC0.
*Jan 15 06:43:01: %SYS-3-CPUHOG: Task ran for 2036 msec (13/3), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 06:43:13: %SYS-3-CPUHOG: Task ran for 2864 msec (21/2), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 06:45:46: %SYS-3-CPUHOG: Task ran for 2212 msec (68/42), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 06:56:03: %SYS-3-CPUHOG: Task ran for 2060 msec (21/5), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 06:56:14: %SYS-3-CPUHOG: Task ran for 4728 msec (30/2), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 07:01:17: %SYS-3-CPUHOG: Task ran for 3400 msec (74/21), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 08:55:30: %SYS-3-CPUHOG: Task ran for 2368 msec (28/12), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 08:57:37: %SYS-3-CPUHOG: Task ran for 2248 msec (51/10), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 08:57:57: %SYS-3-CPUHOG: Task ran for 4056 msec (191/174),
process = MSDP Process, PC = 60A20AC0.
*Jan 15 08:58:16: %SYS-3-CPUHOG: Task ran for 2488 msec (16/1), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 09:00:55: %SYS-3-CPUHOG: Task ran for 2296 msec (57/1), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 09:01:06: %SYS-3-CPUHOG: Task ran for 3720 msec (24/6), process
= MSDP Process, PC = 60A20AC0.
*Jan 15 09:01:19: %SYS-3-CPUHOG: Task ran for 2488 msec (138/67),
process = MSDP Process, PC = 60A20AC0.
*Jan 15 09:01:29: %SYS-3-CPUHOG: Task ran for 2664 msec (47/8), process
= MSDP Process, PC = 60A20AC0.
and a bunch more of these
Jan 15 08:31:42: %PIM-6-SA_ENCAP_INVALID: Bad SA from RP 141.142.12.1
Are you sure about the timing ?
Matthew Davy wrote:
>
> Actually, I believe the router originating the problem is a Juniper.
>
> BTW- We just got hit with another storm between 09:00 and 09:20 EST.
> I shut down the MSDP session with the customer I think has the
> problem, but I'm not sure if they're multihomed...
>
> - Matt
--
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
- MSDP instability today, Matthew Davy, 01/14/2001
- Re: MSDP instability today, Marshall Eubanks, 01/14/2001
- Re: MSDP instability today, Matthew Davy, 01/14/2001
- Re: MSDP instability today, Bill Fenner, 01/14/2001
- Re: MSDP instability today, Greg Shepherd, 01/14/2001
- Re: MSDP instability today, Matthew Davy, 01/14/2001
- Re: MSDP instability today, Greg Shepherd, 01/14/2001
- Re: MSDP instability today, Matthew Davy, 01/14/2001
- Re: MSDP instability today, Matthew Davy, 01/15/2001
- Re: MSDP instability today, Marshall Eubanks, 01/15/2001
- Re: MSDP instability today, Marshall Eubanks, 01/15/2001
- Re: MSDP instability today, Marshall Eubanks, 01/15/2001
- Re: MSDP instability today, Matthew Davy, 01/15/2001
- Re: MSDP instability today, Marshall Eubanks, 01/15/2001
- Re: MSDP instability today, Al Adler, 01/15/2001
- 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, Marshall Eubanks, 01/15/2001
- Re: MSDP instability today, Greg Shepherd, 01/14/2001
- Re: MSDP instability today, Bill Fenner, 01/14/2001
- Re: MSDP instability today, Matthew Davy, 01/14/2001
- Re: MSDP instability today, Marshall Eubanks, 01/14/2001
- Re: MSDP instability today, Bill Fenner, 01/15/2001
Archive powered by MHonArc 2.6.16.