[c-nsp] Asymmetric routing

Capron, Mathew mcapron at aimnetsolutions.com
Thu May 11 09:28:17 EDT 2006



I believe the rpf check would fail at the router at which the asymetric
routing starts.  Since the Mcast join will come from one direction and
the the RPF would point in a different direction for the source over the
other path.  A static mroute back over the original path for the source
should take care of this situation.
 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Phil Mayers
Sent: Thursday, May 11, 2006 5:36 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Asymmetric routing

Michael Robson wrote:
> Has anyone experienced asymmetric routing within their network
> that caused multicast RPF checks to fail and so break multicast?
> More generally, what are people doing design-wise on their networks
> , if anything, to avoid such problems on ever increasingly resilient,
> meshed networks?

Michael,

Could you be a bit more specific about the problem you're having? 
Assuming PIM-SM, this ought not to be a problem - the normal propagation

of joins towards a source should build a correct oif list.

What platform are you on?


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list