Your multicast table shows that you have no RPF neighbors. Thats why it's failing. Now to figure out why you have no RPF neighbors on your mcast routes. I'd take a look at your interfaces involved to make sure they all have the appropriate PIM statements and check "sho ip pim neighbors".
On Tue, Jan 18, 2011 at 1:42 PM, Baldwin, Patrick A. <[email protected]>wrote: > See if this helps: BTW, I have completely erased this router and reloaded > it with minimal config but the problem persists. > > > > > > R5#sh ip mro > > IP Multicast Routing Table > > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - > Connected, > > L - Local, P - Pruned, R - RP-bit set, F - Register flag, > > T - SPT-bit set, J - Join SPT, M - MSDP created entry, > > X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, > > U - URD, I - Received Source Specific Host Report, > > Z - Multicast Tunnel, z - MDT-data group sender, > > Y - Joined MDT-data group, y - Sending to MDT-data group, > > V - RD & Vector, v - Vector > > Outgoing interface flags: H - Hardware switched, A - Assert winner > > Timers: Uptime/Expires > > Interface state: Interface, Next-Hop or VCD, State/Mode > > > > (*, 239.0.0.5), 00:37:54/00:02:23, RP 0.0.0.0, flags: SJCL > > Incoming interface: Null, RPF nbr 0.0.0.0 > > Outgoing interface list: > > Loopback0, Forward/Sparse, 00:37:54/00:02:23 > > > > (*, 224.0.1.40), 00:41:54/00:02:27, RP 0.0.0.0, flags: DPL > > Incoming interface: Null, RPF nbr 0.0.0.0 > > Outgoing interface list: Null > > > > R5# > > *Jan 18 19:45:33.763: PIM-BSR(0): bootstrap (192.0.0.23) on non-RPF path > FastEthernet0/1.235 or from non-RPF neighbor 192.0.235.23 discarded > > R5# > > > > > > > > Patrick A. Baldwin (Alex) > > Network Engineering > Colsa Corp., HOSC Contract > NASA , Marshall Space Flight Center* > * > (Office:* **(*256) 544-2089 > ÊFax:* *(256) 544-8629 > *E-mail: [email protected] > > > > *From:* Max Pierson [mailto:[email protected]] > *Sent:* Tuesday, January 18, 2011 1:41 PM > > *To:* Baldwin, Patrick A. > *Cc:* [email protected] > *Subject:* Re: [OSL | CCIE_RS] IP PIM BSR > > > > That does look right, what does your mcast routing table look like?? sho ip > mroute > > > > On Tue, Jan 18, 2011 at 12:48 PM, Baldwin, Patrick A. < > [email protected]> wrote: > > Thanks for your response Max, > > > > The route is to 235.23 so it appears correct to me. > > > > R5#sh ip ro 192.0.0.23 > > Routing entry for 192.0.0.23/32 > > Known via "bgp 52", distance 200, metric 0 > > Tag 23, type internal > > Last update from 192.0.235.23 01:22:27 ago > > Routing Descriptor Blocks: > > * 192.0.235.23, from 192.0.235.23, 01:22:27 ago > > Route metric is 0, traffic share count is 1 > > AS Hops 0 > > Route tag 23 > > > > > > Patrick A. Baldwin (Alex) > Network Engineering > Colsa Corp., HOSC Contract > NASA , Marshall Space Flight Center* > *(Office:* **(*256) 544-2089 > ÊFax:* *(256) 544-8629 > *E-mail: [email protected] > > > > *From:* Max Pierson [mailto:[email protected]] > *Sent:* Tuesday, January 18, 2011 12:43 PM > *To:* Baldwin, Patrick A. > *Cc:* [email protected] > *Subject:* Re: [OSL | CCIE_RS] IP PIM BSR > > > > Look at your debug a little closer. When you do a "sho ip route > 192.0.0.23", what does the next hop interface show up as?? > > On Tue, Jan 18, 2011 at 11:32 AM, Baldwin, Patrick A. < > [email protected]> wrote: > > Does anyone know if there is a bug in 12.4(24)T4 that would cause a router > to ignor BSR messages when RPF clearly is satisfied? > > > R5#sh ip rpf 192.0.0.23 > RPF information for ? (192.0.0.23) > RPF interface: FastEthernet0/1.235 > RPF neighbor: ? (192.0.235.23) > RPF route/mask: 192.0.0.23/32 > RPF type: mbgp > RPF recursion count: 0 > Doing distance-preferred lookups across tables > R5# > *Jan 18 17:33:19.255: PIM-BSR(0): bootstrap (192.0.0.23) on non-RPF path > FastEthernet0/1.235 or from non-RPF neighbor 192.0.235.23 discarded > R5# > *Jan 18 17:33:53.791: PIM-BSR(0): Build v2 Candidate-RP advertisement for > 192.0.0.52 priority 0, holdtime 150 > *Jan 18 17:33:53.791: PIM-BSR(0): Candidate RP's group prefix 224.0.0.0/4 > *Jan 18 17:33:53.791: PIM-BSR(0): no bootstrap router address > > > Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version > 12.4(24)T4, RELEASE SOFTWARE (fc2) > Technical Support: http://www.cisco.com/techsupport > Copyright (c) 1986-2010 by Cisco Systems, Inc. > Compiled Fri 03-Sep-10 05:38 by prod_rel_team > > If I am missing something......please please tell me. I'm almost out of > hair to pull. > > Patrick A. Baldwin (Alex) > Network Engineering > Colsa Corp., HOSC Contract > NASA , Marshall Space Flight Center > *Office: (256) 544-2089 > ÊFax: (256) 544-8629 > *E-mail: [email protected]<mailto:[email protected]> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
