Coexistance of RR and direct iBGP Peering

Answered Question
Sep 12th, 2010
User Badges:

Hi all,


Is it possible to have both direct iBGP peering between PEs and between PEs-RR ?

I am looking for a solution for a subset PEs who can continue communication amongst themselves, even if they don't have reachability with the RR for route updates. If direct peering and RR can coexist, then RR to be preferred as the best source for route updates and direct peeering update as the next alternative, in case PE losts its connectivity with the RR.


Any hint/suggestion would be of great help.

Correct Answer by Giuseppe Larosa about 6 years 8 months ago

Hello Sabut,


no routing loops should occur as BGP advertisements reflected by RR servers contain the cluster-list attribute and BGP originator attribute


direct BGP peering will provide a direct non-reflected advertisement that will be chosen over advertisements with a non null cluster list.


As noted by Laurent by using the cluster-id you can provide redundancy at the BGP RR server level with two RRS serving the same set of client PE nodes.


This is the typical setup in SP networks.


Eventually, different RRS are used for family ipv4 unicast and VPNv4 and also the VPNV4 space can be partitioned in multiple sub spaces served by different RRS (as a way to get better scalability)


Hope to help

Giuseppe

Correct Answer by Laurent Aubert about 6 years 8 months ago

Hi,


Yes it will work but the update received from the RR may not be the one selected as best (but it doesn't really matter anyway)


You could also provide redundancy at the RR level which will maintain constitancy in your BGP PE config. It will also provide backup for all your PE's.



HTH


Laurent.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Laurent Aubert Sun, 09/12/2010 - 14:25
User Badges:
  • Cisco Employee,

Hi,


Yes it will work but the update received from the RR may not be the one selected as best (but it doesn't really matter anyway)


You could also provide redundancy at the RR level which will maintain constitancy in your BGP PE config. It will also provide backup for all your PE's.



HTH


Laurent.

baradasabut Mon, 09/13/2010 - 10:31
User Badges:

Hi Laurnet,


Thanks for the input. Is there any possiblity of routing loops because of direct peering and RR coexistance. If yes, what steps are suggested to avoid the same.


Sabut

Correct Answer
Giuseppe Larosa Mon, 09/13/2010 - 12:42
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Sabut,


no routing loops should occur as BGP advertisements reflected by RR servers contain the cluster-list attribute and BGP originator attribute


direct BGP peering will provide a direct non-reflected advertisement that will be chosen over advertisements with a non null cluster list.


As noted by Laurent by using the cluster-id you can provide redundancy at the BGP RR server level with two RRS serving the same set of client PE nodes.


This is the typical setup in SP networks.


Eventually, different RRS are used for family ipv4 unicast and VPNv4 and also the VPNV4 space can be partitioned in multiple sub spaces served by different RRS (as a way to get better scalability)


Hope to help

Giuseppe

Actions

This Discussion