I have already completed that section of the lab and read the DSG. I applied all the deltas from my solution to make it just like the DSG but still no joy. Very very irritating. Do you see that something is wrong?
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]> From: Max Pierson [mailto:[email protected]] Sent: Tuesday, January 18, 2011 2:37 PM To: Baldwin, Patrick A. Cc: CCIE_RS OnlineStudyList Subject: Re: [OSL | CCIE_RS] IP PIM BSR Ok, so I was getting desperate and that calls for desperate measures. I checked out the Solutions Guide. It is a next-hop bgp issue but there's a little more going on than just the next-hop info. I can give the answers if u like since I cheated ;) I'd first say to check your interface configs on R5 and R2, make sure your sourcing stuff from your loopbacks and you have your routing protocols AD set correctly. On Tue, Jan 18, 2011 at 2:11 PM, Baldwin, Patrick A. <[email protected]<mailto:[email protected]>> wrote: Thanks for looking at this, two sets of eyes are always better. R5#sh ip bgp BGP table version is 14, local router ID is 192.0.0.5 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * 192.0.0.1/32<http://192.0.0.1/32> 192.0.245.4 0 47 11314 i *>i 192.0.12.1 0 100 0 11314 i r>i192.0.0.2/32 192.0.0.2 0 100 0 i * i192.0.0.4/32 192.0.245.4 0 100 0 47 i * 192.0.245.4 0 0 47 i * 192.0.237.7 100 0 (23) 47 i *> 192.0.57.7 0 47 i *> 192.0.0.5/32<http://192.0.0.5/32> 0.0.0.0 0 32768 i * i192.0.0.6/32 192.0.245.4 0 100 0 47 69 i * 192.0.245.4 0 47 69 i * 192.0.237.7 100 0 (23) 47 69 i *> 192.0.57.7 0 47 69 i * i192.0.0.7/32 192.0.245.4 0 100 0 47 i * 192.0.245.4 0 47 i * 192.0.237.7 100 0 (23) 47 i *> 192.0.57.7 0 0 47 i * i192.0.0.9/32 192.0.245.4 0 100 0 47 69 i * 192.0.245.4 0 47 69 i * 192.0.237.7 100 0 (23) 47 69 i *> 192.0.57.7 0 47 69 i * 192.0.0.13/32<http://192.0.0.13/32> 192.0.245.4 0 47 11314 i *>i 192.0.12.1 0 100 0 11314 i * 192.0.0.14/32<http://192.0.0.14/32> 192.0.245.4 0 47 11314 i *>i 192.0.12.1 0 100 0 11314 i * 192.0.0.21/32<http://192.0.0.21/32> 192.0.245.4 0 47 11314 i *>i 192.0.12.1 0 100 0 11314 i *> 192.0.0.23/32<http://192.0.0.23/32> 192.0.235.23 0 100 0 (23) i *> 192.0.0.52/32<http://192.0.0.52/32> 0.0.0.0 0 32768 i R5#sh ip ro Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route Gateway of last resort is not set O E1 192.0.12.0/24<http://192.0.12.0/24> [110/2270] via 192.0.52.2, 01:03:14, Serial0/2/0 O E1 192.0.46.0/24<http://192.0.46.0/24> [110/4446] via 192.0.57.7, 01:06:32, FastEthernet0/1.57 O E1 192.14.13.0/24<http://192.14.13.0/24> [110/2270] via 192.0.52.2, 01:03:14, Serial0/2/0 O 192.0.47.0/24<http://192.0.47.0/24> [110/2] via 192.0.57.7, 01:06:32, FastEthernet0/1.57 O E1 192.0.211.0/24<http://192.0.211.0/24> [110/2270] via 192.0.52.2, 01:03:14, Serial0/2/0 O E1 192.13.14.0/24<http://192.13.14.0/24> [110/2270] via 192.0.52.2, 01:03:14, Serial0/2/0 C 192.0.25.0/24<http://192.0.25.0/24> is directly connected, FastEthernet0/0 O E1 192.0.127.0/24<http://192.0.127.0/24> [110/7778] via 192.0.57.7, 01:06:33, FastEthernet0/1.57 O E1 192.0.129.0/24<http://192.0.129.0/24> [110/4446] via 192.0.57.7, 01:06:33, FastEthernet0/1.57 O E1 192.0.212.0/24<http://192.0.212.0/24> [110/2270] via 192.0.52.2, 01:03:15, Serial0/2/0 192.0.245.0/24<http://192.0.245.0/24> is variably subnetted, 2 subnets, 2 masks C 192.0.245.0/24<http://192.0.245.0/24> is directly connected, Serial0/1/0 O 192.0.245.2/32<http://192.0.245.2/32> [110/48] via 192.0.52.2, 01:03:15, Serial0/2/0 C 192.0.57.0/24<http://192.0.57.0/24> is directly connected, FastEthernet0/1.57 O E1 192.0.131.0/24<http://192.0.131.0/24> [110/2270] via 192.0.52.2, 01:03:15, Serial0/2/0 O E1 192.0.79.0/24<http://192.0.79.0/24> [110/4446] via 192.0.57.7, 01:06:33, FastEthernet0/1.57 C 192.0.235.0/24<http://192.0.235.0/24> is directly connected, FastEthernet0/1.235 O E1 192.0.112.0/24<http://192.0.112.0/24> [110/7778] via 192.0.57.7, 01:06:33, FastEthernet0/1.57 192.0.52.0/24<http://192.0.52.0/24> is variably subnetted, 2 subnets, 2 masks C 192.0.52.0/24<http://192.0.52.0/24> is directly connected, Serial0/2/0 C 192.0.52.2/32<http://192.0.52.2/32> is directly connected, Serial0/2/0 192.0.0.0/32<http://192.0.0.0/32> is subnetted, 14 subnets B 192.0.0.1 [200/0] via 192.0.12.1, 01:03:09 O 192.0.0.2 [110/49] via 192.0.52.2, 01:03:16, Serial0/2/0 B 192.0.0.4 [20/0] via 192.0.57.7, 01:05:20 C 192.0.0.5 is directly connected, Loopback0 B 192.0.0.6 [20/0] via 192.0.57.7, 01:05:20 B 192.0.0.7 [20/0] via 192.0.57.7, 01:05:20 B 192.0.0.9 [20/0] via 192.0.57.7, 01:05:20 O E1 192.0.0.11 [110/7778] via 192.0.57.7, 01:06:35, FastEthernet0/1.57 O E1 192.0.0.12 [110/7778] via 192.0.57.7, 01:06:35, FastEthernet0/1.57 B 192.0.0.13 [200/0] via 192.0.12.1, 01:03:09 B 192.0.0.14 [200/0] via 192.0.12.1, 01:03:09 B 192.0.0.21 [200/0] via 192.0.12.1, 01:03:09 B 192.0.0.23 [200/0] via 192.0.235.23, 01:05:20 C 192.0.0.52 is directly connected, Loopback52 192.0.69.0/24<http://192.0.69.0/24> is variably subnetted, 2 subnets, 2 masks O E1 192.0.69.6/32<http://192.0.69.6/32> [110/7778] via 192.0.57.7, 01:06:35, FastEthernet0/1.57 O E1 192.0.69.0/24<http://192.0.69.0/24> [110/4446] via 192.0.57.7, 01:06:35, FastEthernet0/1.57 O E1 192.0.117.0/24<http://192.0.117.0/24> [110/7778] via 192.0.57.7, 01:06:36, FastEthernet0/1.57 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]> From: Max Pierson [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, January 18, 2011 2:10 PM To: Baldwin, Patrick A. Cc: [email protected]<mailto:[email protected]> Subject: Re: [OSL | CCIE_RS] IP PIM BSR Ok, only thing left I can think of is next-hop info. What does you BGP config / table look like?? Since RPF is using that as it's check, next-hop info must be right. On Tue, Jan 18, 2011 at 2:03 PM, Baldwin, Patrick A. <[email protected]<mailto:[email protected]>> wrote: Looks right to me R5#sh ip pim ne PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, S - State Refresh Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode 192.0.235.23 FastEthernet0/1.235 01:03:07/00:01:36 v2 1 / DR S 192.0.52.2 Serial0/2/0 00:55:44/00:01:43 v2 1 / S P 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]> From: Max Pierson [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, January 18, 2011 2:02 PM To: Baldwin, Patrick A. Cc: [email protected]<mailto:[email protected]> Subject: Re: [OSL | CCIE_RS] IP PIM BSR 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]<mailto:[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]<mailto:[email protected]> From: Max Pierson [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, January 18, 2011 1:41 PM To: Baldwin, Patrick A. Cc: [email protected]<mailto:[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]<mailto:[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<http://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]<mailto:[email protected]> From: Max Pierson [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, January 18, 2011 12:43 PM To: Baldwin, Patrick A. Cc: [email protected]<mailto:[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]<mailto:[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<http://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<http://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]<mailto:[email protected]>> _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com<http://www.ipexpert.com> _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
