All things related to multicast

[Tony Rimovsky <>]

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.
> 
>