tag:blogger.com,1999:blog-5968686435283454526.post2446438323923505653..comments2024-03-10T21:40:55.615-07:00Comments on Jeff Kronlage's CCIE Study Blog: iBGP Route-Reflector Loop Preventionbrbcciehttp://www.blogger.com/profile/14586635047530183862noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5968686435283454526.post-73343384998965569842016-04-03T14:28:05.809-07:002016-04-03T14:28:05.809-07:00You did a very good job on this write up, thank yo...You did a very good job on this write up, thank you.William Nellishttps://www.blogger.com/profile/03778539742383447063noreply@blogger.comtag:blogger.com,1999:blog-5968686435283454526.post-29359856398532018312014-06-16T18:00:00.335-07:002014-06-16T18:00:00.335-07:00You're going to have to help me out with the t...You're going to have to help me out with the topology a little more. Normally, a route reflector is advertising routes only within a single AS. Perhaps there's a VRF not picture here (Assuming so with MPLS mentioned), but I'm curious why we have a router in AS 1234 passing routes to an AS in 111 and expecting them to be passed back to 1234? That doesn't sound like route reflection, it sounds like traditional eBGP, and yes, 1234 -> 111 ->1234 would not be accepted simply because eBGP will not accept routes with its own AS in it. I suspect I'm missing something from your topology?brbcciehttps://www.blogger.com/profile/14586635047530183862noreply@blogger.comtag:blogger.com,1999:blog-5968686435283454526.post-35580480570101478132014-06-16T14:46:15.165-07:002014-06-16T14:46:15.165-07:00Jeff,
I have a unique situation, and would like ...Jeff,<br /><br /> I have a unique situation, and would like your thoughts on it. A customer is advertising a default route with an AS path of 65160 1234 within the L3PVN (AS1234 happens to be the AS of PE that they are connected to). <br /><br />The route reflector sees AS 1234 in the path and does not advertise it to other route reflector clients in AS1234..is that expected behavior?<br /><br />=============================<br /><br /><br /><br /><br /><br />Customer RD : 2:2<br />Route Reflector: 192.168.1.10 < This Route reflector client is in AS 1234<br />Local AS: 111 <br />PE that the customer is peered to: 10.10.10.10 (This PE is in AS1785) <br /><br /><br />Output below from route reflector in AS 111<br /><br />2:2:0.0.0.0/0 (2 entries, 0 announced)<br /> BGP /-101<br /> Route Distinguisher: 2:2<br /> Next hop type: Indirect<br /> Address: 0x28b00e20<br /> Next-hop reference count: 2<br /> Source: 192.168.1.10<br /> Protocol next hop: 10.10.10.10<br /> Push 464<br /> Indirect next hop: 2 no-forward<br /> State: <br /> Local AS: 111 Peer AS: 1234<br /> Age: 3d 6:34:32 Metric: 0 Metric2: 87766<br /> Task: BGP_111.192.168.1.10+62122<br /> AS path: 65160 1234 I (Originator) (Looped: 1234)<br /> Cluster list: 192.168.1.10<br /> Originator ID: 10.10.10.10<br /> Communities: target:2:2<br /> VPN Label: 464<br /> Localpref: 100<br /> Router ID: 192.168.1.10<br /> Indirect next hops: 1<br /> Protocol next hop: 10.10.10.10 Metric: 87766<br /> Push 464<br /> Indirect next hop: 2 no-forward<br /> Indirect path forwarding next hops: 2<br /> Next hop type: Router<br /> Next hop: 98.21.127.41 via ge-2/2/0.0<br /> Next hop: 98.21.127.43 via ge-2/2/1.0<br /> 10.10.10.10/32 Originating RIB: inet.3<br /> Metric: 87766 Node path count: 1<br /> Forwarding nexthops: 2<br /> Nexthop: 98.21.127.41 via ge-2/2/0.0<br /> Nexthop: 98.21.127.43 via ge-2/2/1.0<br /><br /><br />Debottymhttps://www.blogger.com/profile/13848325025941247880noreply@blogger.com