Configuring two RRs in an MPLS core

Unanswered Question
Jan 19th, 2010
User Badges:

Hi All,

          Configuring a route-reflector in an MPLS core with two PEs is not a problem for me but when the RRs are two it becomes difficult.

Assuming we have two PEs with two P routers in the middle serving as RR1 and RR2, in addition to their normal global BGP peering wchich was made by their loopbacks and advertised into OSPF as the protocol in the core, do i still need to do anything before the VPNV4/IPV4 address-family?

Under the VPNV4 address-family on each RR, do i suppose to include each of the PE as neighbor or it's only suppose to peer with the other P-RR?.

I would be glad if anyone could help to resolve my concern on this issue.

Thanking you all in advance,

Olu

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Tue, 01/19/2010 - 14:13
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Olu,


each RR needs an iBGP session with the other RR.


There can be some differences with different IOS release, but BGP CLI with address families uses the following process



router bgp xx


! here definitions of neighbors and peer-groups

neigh other-RR-loop1 remote-as xx

neigh other-RR-loop1 update-source loop1

! definitions of peer-group for client

neigh myclients peer-group

neigh myclients remote-as xx

neigh myclients update-source loop1

neigh Pe1:loop1 peer-group myclients

neigh PE2:loop1 peer-group myclients


! inside each address-family commands are given for: activation, send-community, route-reflector-client if desired


address-family ipv4 unicast

neigh other-RR-loop1 activate

neigh other-RR-loop1 send-community

neigh myclients activate

neigh myclients route-reflector-client

neigh myclients send-community both

neigh Pe1:loop1 activate

neigh Pe2:loop1 activate


address-family vpnv4

neigh other-RR-loop1 activate

neigh other-RR-loop1 send-community both

[neigh myclients activate]

neigh myclients route-reflector-client

neigh myclients send-community both

neigh Pe1:loop1 activate

neigh Pe2:loop1 activate


you can have a route-reflector for address-family and you can decide what peer members you activate in each address-family

This provides great flexibility.


note: commands may not be correct I've prepared this example on the fly


Hope to help

Giuseppe

Actions

This Discussion