Skip to Content.
Sympa Menu

wg-multicast - Re: Junper Multicast Bug out on Abilene

Subject: All things related to multicast

List archive

Re: Junper Multicast Bug out on Abilene


Chronological Thread 
  • From: Tony Rimovsky <>
  • To: Stan Barber <>
  • Cc: Bert Rossi <>, Stan Barber <>, ,
  • Subject: Re: Junper Multicast Bug out on Abilene
  • Date: Mon, 7 Oct 2002 08:59:25 -0500

I can't say that for certain, no.

I do know that in at least various releases of JunOS circa 4.4, that
error message was appearing on Cisco's without causing any adverse
effects other than annoying log messages. I had a case open with
juniper about this which was closed in late 2001. Their statement at
the time was that JunOS4.4R3 should have eliminated the problem.

Then, last month while working on the iGrid network, I noticed that my
home site's MSDP peer (JunOS 5.5(something)) was causing these errors
on the iGrid MSDP peer, which was running IOS 12.1.13. We've changed
JunOS versions since then, and I haven't had any reports of the logs
persisting. As a result, I hadn't reported it to Juniper.

I thought that Tom Pusateri made some comments about the problem on
this list some time ago, but I can't find it in my archives.

/tsr




It is, of course, possible that this is something new.

On Fri, Oct 04, 2002 at 03:56:52PM -0500, Stan Barber wrote:
> To be clear, are you you are saying that the MSDP session resets we are
> seeing that are concurrent with this logging are incidental and not related?
>
> Tony Rimovsky wrote:
> >This has been an issue for a year or more. If I recall correctly,
> >this was caused when Cisco turned up the level of detail for PIM
> >logging. Juniper knows about it. The error does not effect multicast
> >performance and there is no reason to turn down your sessions.
> >
> >On Fri, Oct 04, 2002 at 01:54:51PM -0400, Bert Rossi wrote:
> >
> >>Thanks, Stan, we've shut down the session until we can get this fixed.
> >>
> >> -Bert
> >>
> >>
> >>>
> >>>We are having some MSDP problems that appears to be consistent with
> >>>a known Juniper bug.
> >>>
> >>>Here is the debug output from our Cisco's:
> >>>
> >>>Oct 4 09:56:01: MSDP: 198.32.236.61: Peer reset, other side reset
> >>>Oct 4 09:56:31: %MSDP-5-PEER_UPDOWN: Session to peer 198.32.236.61
> >>>going up
> >>>Oct 4 09:57:36: %PIM-6-SA_ENCAP_INVALID: Bad SA from RP 192.122.183.1
> >>>for
> >>>(207.75.164.93, 224.2.127.254); additional info = 450001D2 C830000
> >>>7E110000
> >>>1D2 53CE3730 53CE3730 5AEE 0
> >>>
> >>>
> >>>The RP is in merit. The source item is an internet2.edu device.
> >>
> >>
>
>
> --
> Stan | PGP Key ID: 55CB6421 | Opinions expressed are only mine.
> Olan | Phone: +1-713-793-0222 | Email:
>
> Barber | Fax: +1-208-445-2972 | http://www.academ.com/~sob




Archive powered by MHonArc 2.6.16.

Top of Page