BGP Problem (Two ISPs)

[CSCO12001340]

Hello !
I am having trouble with my iBGP routes. I am really confused how to set it up properly. Can anyone tell me about the wrong configurations related to my topology ?  (ISP-1 CORE and ISP-2 CORE are Route Reflectors)

*** This topology should work without any interruption. For Example if Branch-x-isp-1 loses the iBGP neighborship with ISP-Core-RR , traffic should continue from the Banch-x-isp-2 router.

ISP-1 CORE RR CONFIG

router bgp 65000
bgp log-neighbor-changes
bgp redistribute-internal

neighbor 172.16.0.64 remote-as 65000
neighbor 172.16.0.64 route-reflector-client
neighbor 172.16.0.64 next-hop-self
neighbor 172.16.0.64 default-originate

neighbor 172.16.0.72 remote-as 65000
neighbor 172.16.0.72 route-reflector-client
neighbor 172.16.0.72 next-hop-self
neighbor 172.16.0.72 default-originate

neighbor 172.16.110.110 remote-as 65000
neighbor 172.16.110.110 route-reflector-client
neighbor 172.16.110.110 next-hop-self

ISP-2 CORE RR CONFIG

neighbor 172.16.110.101 remote-as 65000
neighbor 172.16.110.101 route-reflector-client
neighbor 172.16.110.101 next-hop-self

neighbor 172.29.51.209 remote-as 65000
neighbor 172.29.51.209 route-reflector-client
neighbor 172.29.51.209 next-hop-self
neighbor 172.29.51.209 default-originate

neighbor 172.29.60.27 remote-as 65000
neighbor 172.29.60.27 route-reflector-client
neighbor 172.29.60.27 next-hop-self
neighbor 172.29.60.27 default-originate

BRANCH-X-ISP-1

router bgp 65001
bgp log-neighbor-changes
bgp redistribute-internal
network 10.10.50.0 mask 255.255.255.0
neighbor 10.10.50.11 remote-as 65000
neighbor 10.10.50.11 route-reflector-client
neighbor 10.10.50.11 next-hop-self
neighbor 172.16.0.40 remote-as 65000
neighbor 172.16.0.40 next-hop-self

neighbor 172.16.0.40 route-reflector-client
neighbor 172.16.0.40 route-map LOCAL-PREF in (Sets LP to 600)

BRANCH-X-ISP-2

router bgp 65001
bgp log-neighbor-changes
bgp redistribute-internal
network 10.10.50.0 mask 255.255.255.0
neighbor 10.10.50.10 remote-as 65000
neighbor 10.10.50.10 route-reflector-client
neighbor 10.10.50.10 next-hop-self
neighbor 172.27.107.220 remote-as 65000
neighbor 172.27.107.220 next-hop-self

neighbor 172.27.107.220 route-reflector-client
neighbor 172.27.107.220 route-map LOCAL-PREF in (Sets LP to 500)

BRANCH-Y-ISP-1

router bgp 65000
bgp log-neighbor-changes
bgp redistribute-internal
network 10.10.60.0 mask 255.255.255.0
neighbor 10.10.60.11 remote-as 65000
neighbor 10.10.60.11 route-reflector-client
neighbor 10.10.60.11 next-hop-self
neighbor 172.16.0.40 remote-as 65000
neighbor 172.16.0.40 next-hop-self

neighbor 172.16.0.40 route-reflector-client
neighbor 172.16.0.40 route-map LOCAL-PREF in

BRANCH-Y-ISP-2

router bgp 65000
bgp log-neighbor-changes
bgp redistribute-internal
network 10.10.60.0 mask 255.255.255.0
neighbor 10.10.60.10 remote-as 65000
neighbor 10.10.60.10 route-reflector-client
neighbor 10.10.60.10 next-hop-self
neighbor 172.27.107.220 remote-as 65000
neighbor 172.27.107.220 next-hop-self

neighbor 172.27.107.220 route-reflector-client

[CSCO12001340]

Hello,

When I do it, ISP1 and ISP2 Cores are sharing routes with each other and that is what i don't want.

[paul driver]

Hello

---

@CSCO12001340 wrote:

Hello,

When I do it, ISP1 and ISP2 Cores are sharing routes with each other and that is what i don't want.

---

They need to for residency ? -  as if either if the branches lose connectivity to their one of the two ISP core it will be redundant

res

Paul

[CSCO12001340]

Hello Paul,

To avoid routing loops, I am using BGP Cluster ID already right ?

I am trying to do the same solution. If branches lose connectivity to ISP-1, they should go ahead by using ISP-2. So they should receive routes from both RRs.

Now I can see only ISP-1 routes on CoreISP1 and only ISP-2 routes on COREISP2. What I want is see both of them on both Cores and I can manipulate the routes by local preference or sth like that to choose between them.

[paul driver]

Hello
Correct but dont forget local preference can be used only to prefer the exit path of the RR ASN not within it.

RR are basically is used to cut done on the amount of fully meshed peering required between IBGP peers but from your branch ISP you should be seeing routes from either ISP rtrs.

Just reviewed your OP and I am not so sure you even require RR, Your Core ISP rtrs are in a different ASN then the branch rtrs which means you wont even be able to have RR.

My initial suggestion focused on RR hence the example i posted shown all rtr ( core/branch) all in the same ASN, but your topology doesn't show this, So maybe its a totally different approach is required?

Can you please confirm this?

res

Paul

[CSCO12001340]

Hello Paul,

Thanks for your help, you are great. 

My Cores are in same AS, there is a mistype I think.