Thanks, Oliver! That explains exactly what we were seeing. We doing have a multicast AF enabled in our IGP on the affected routers, so now I understand why we needed the additional replication commands.
Thanks again, John On Fri, Mar 1, 2013 at 5:06 AM, Oliver Boehmer (oboehmer) < [email protected]> wrote: > > > On 01/03/2013 10:58, "Mikael Abrahamsson" <[email protected]> wrote: > > >On Fri, 1 Mar 2013, Christian Meutes wrote: > > > >> On 01.03.2013, at 10:01, Mikael Abrahamsson <[email protected]> wrote: > >> > >>> On Fri, 1 Mar 2013, Christian Meutes > >>> Do you have your sources addresses in IGP? > >> > >> Nope, BGP SAFI unicast. > > > >Well, your experience contradicts mine. I have had to solve issues with > >multicast not working and started working when the sources were put in > >SAFI multicast with as late software as XR 4.2.1. > > > >I'll defer to someone more knowledgable to explain how this really works. > > Once you enable the mcast AF in your IGP or BGP, IOS-XR will populate the > muRIB, and PIM will use this one for RPF (before it used the unicast > RIB/uRIB). This requires that all sources will be in the muRIB. This is > different from IOS where RPF would fall back to the unicast RIB, as > Michael described. > > The "rump always-replicate" command will replicate uRIB to muRIB, so we > effectively achieve the IOS behaviour. > > oli > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
