- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2021 10:50 PM - edited 12-08-2021 12:58 AM
Do we need to consider both Route Reflectors and Next Hop self while Planning for IBGP Peerings?
Solved! Go to Solution.
- Labels:
-
Routing Protocols
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2022 02:32 AM - edited 05-08-2022 02:35 AM
Hi @Harold Ritter thanks for your information. I am also tring to modify the refelected route's local-preference on RR outgoing direction, now I know that RR outgoing NEXT_HOP, AS_PATH, LOCAL_PREF and MED modification has been ignored due to the loop prevention. Here I have a question, what if I modify the attribute on the RR incoming direction, will it also potentially cause a loop (refer to the attached diagram, it seems that modify on the incoming or outgoing has the same effect to the whole network)? Should we avoid any route attribute modification on RR for loop prevention consideration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2022 04:51 AM
what want to achieve here? why looking for modify ? is RRC is EBGP also?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2021 04:08 AM
Yes you can, next-hop-self don't make loop since the RR add originate router to prefix learn from client and this prevent loop inside iBGP with RR.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2021 04:57 AM - edited 12-08-2021 08:02 AM
Hello
@MHM Cisco World wrote:
Yes you can, next-hop-self don't make loop since the RR add originate router to prefix learn from client and this prevent loop inside iBGP with RR.
The loop prevention in RR design as far as I understand is performed by the Cluster-list/originator id's, Originator id prevent loops within its as single cluster and a cluster id it works when you have multiple RR, just like the path sequence verification in the AS Path, So if a router see its own cluster id in any bgp update then its discarded.
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2021 11:22 AM - edited 12-08-2021 11:32 AM
As I know non-client client and RR can make eBGP with outer AS.
https://blog.ipspace.net/2014/04/changes-in-ibgp-next-hop-processing.html
this article talk a little about neighbor next-hop-self all <- which use specifically for RR.

- « Previous
-
- 1
- 2
- Next »