Interesting that the RPF fail happens on R5 since it is in the same domain as the BB router and seems to be directly connected per your diagram. It seems as if this is not an MSDP issue because the mcast is being dropped at R5 before it even sends the SA over the MSDP to the other side.
Can you give us a more detailed diagram with information like the interface numbers and subnet information? It might be easier to debug your error messages then. Thanks! On Thu, Apr 1, 2010 at 12:31 PM, Robert Simmons <[email protected]> wrote: > When running a ping from BB3 to 226.1.1.1 I receive the following messages on > R5: > > *Mar 1 02:57:52.719: IP(0): s=150.100.255.254 (FastEthernet0/1) d=226.1.1.1 > id=41, ttl=254, prot=1, len=114(100), RPF lookup failed for source or RP > *Mar 1 02:57:54.719: IP(0): s=150.100.255.254 (FastEthernet0/1) d=226.1.1.1 > id=42, ttl=254, prot=1, len=114(100), RPF lookup failed for source or RP > *Mar 1 02:57:56.719: IP(0): s=150.100.255.254 (FastEthernet0/1) d=226.1.1.1 > id=43, ttl=254, prot=1, len=114(100), RPF lookup failed for source or RP > *Mar 1 02:57:58.707: IP(0): s=150.100.255.254 (FastEthernet0/1) d=226.1.1.1 > id=44, ttl=254, prot=1, len=114(100), RPF lookup failed for source or RP > *Mar 1 02:58:00.703: IP(0): s=150.100.255.254 (FastEthernet0/1) d=226.1.1.1 > id=45, ttl=254, prot=1, len=114(100), RPF lookup failed for source or RP > *Mar 1 02:58:02.683: IP(0): s=150.100.255.254 (FastEthernet0/1) d=226.1.1.1 > id=46, ttl=254, prot=1, len=114(100), RPF lookup failed for source or RP > > I'm running PIM debugging, MSDP detail debugging & Debug ip mpacket (turned > off mroute-cache on all pim enabled interfaces) > > > On Apr 1, 2010, at 12:17 PM, Joe Astorino wrote: > >> Sorry Rob, I overlooked the fact that you were configuring the default >> peer. Where is the message you are getting coming from? A debug or ? >> >> On Thu, Apr 1, 2010 at 12:02 PM, Robert Simmons <[email protected]> wrote: >>> Well what is the purpose of the msdp default peer command? >>> On Apr 1, 2010, at 11:51 AM, Joe Astorino wrote: >>> >>>> That is what the mcast address family was designed to do : ) >>>> >>>> >>>> Sent from my Verizon Wireless BlackBerry >>>> >>>> Regards, >>>> >>>> Joe Astorino - CCIE #24347 >>>> Sr. Technical Instructor - IPexpert >>>> Mailto: [email protected] >>>> Telephone: +1.810.326.1444 >>>> Live Assistance, Please visit: www.ipexpert.com/chat >>>> eFax: +1.810.454.0130 >>>> >>>> IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, >>>> Audio Tools, Online Hardware Rental and Classroom Training for the Cisco >>>> CCIE (R&S, Voice, Security & Service Provider) certification(s) with >>>> training locations throughout the United States, Europe, South Asia and >>>> Australia. Be sure to visit our online communities at >>>> www.ipexpert.com/communities and our public website at www.ipexpert.com >>>> >>>> -----Original Message----- >>>> From: Robert Simmons <[email protected]> >>>> Date: Thu, 1 Apr 2010 11:49:55 >>>> To: <[email protected]> >>>> Subject: [OSL | CCIE_RS] Multicast Interdomain Routing >>>> >>>> Experts, >>>> >>>> I'm playing around with some different multicast scenarios and I thought >>>> it was possible to make MCast Interdomain Routing without using mBGP >>>> between the MSDP Peers. >>>> >>>> Here's what I have: >>>> >>>> Cat2---Cat4---R5---BB3 >>>> >>>> Full reachability exist between all routers. >>>> >>>> Domain 1 (Cat2 & Cat4) >>>> - pim sparse on all relevant interfaces >>>> - Cat4 is bsr-candidate and rp-candidate for group 226.0.0.0/8 >>>> - Cat2 loopback0 has ip igmp-join for 226.1.1.1 >>>> - Both routers able to ping 226.1.1.1 >>>> - bsr-border is configured on the link between Cat4 & R5 >>>> - msdp peer & default peer command is configured for loopback IP address >>>> of R5 >>>> >>>> Domain 2 (R5 & BB3) >>>> - pim sparse on all relevant interfaces >>>> - R5 is bsr-candidate and rp-candidate for group 225.0.0.0/8 >>>> - BB3 loopback0 has ip igmp-join for 225.1.1.1 >>>> - Both routers able to ping 225.1.1.1 >>>> - bsr-border is configured on the link between R5 & Cat4 >>>> -msdp peer & default peer command is configured for the loopback IP >>>> address of Cat4 >>>> >>>> >>>> When I try to ping any of the groups from the other Domain I get the >>>> following message: >>>> >>>> RPF lookup failed for source or RP >>>> >>>> Is the only way to get around this is to configure mBGP between the RPs?? >>>> >>>> Thanks >>>> >>>> -Rob >>>> _______________________________________________ >>>> For more information regarding industry leading CCIE Lab training, please >>>> visit www.ipexpert.com >>> >>> >> >> >> >> -- >> Regards, >> >> >> >> Joe Astorino - CCIE #24347 >> Sr. Technical Instructor - IPexpert >> Mailto: [email protected] >> Telephone: +1.810.326.1444 >> Live Assistance, Please visit: www.ipexpert.com/chat >> eFax: +1.810.454.0130 >> >> IPexpert is a premier provider of Self-Study Workbooks, Video on >> Demand, Audio Tools, Online Hardware Rental and Classroom Training for >> the Cisco CCIE (R&S, Voice, Security & Service Provider) >> certification(s) with training locations throughout the United States, >> Europe, South Asia and Australia. Be sure to visit our online >> communities at www.ipexpert.com/communities and our public website at >> www.ipexpert.com > > -- Regards, Joe Astorino - CCIE #24347 Sr. Technical Instructor - IPexpert Mailto: [email protected] Telephone: +1.810.326.1444 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE (R&S, Voice, Security & Service Provider) certification(s) with training locations throughout the United States, Europe, South Asia and Australia. Be sure to visit our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
