Considered options 1 and 2 but was looking for a way to keep Peering happening 
strictly between the edge and cores. #3 did exactly that, thanks!

Chris Wright
Network Administrator

From: Eric Flanery [mailto:[email protected]]
Sent: Friday, January 27, 2017 11:30 AM
To: Chris Wright; Mikrotik Users
Subject: RE: OSPF & BGP

If Core1 is IP routing the packets, then it needs an IP route to the 
destination. Recursive lookup does not alter the packets, so the OSPF routes on 
Core1 don't help.

Three quick ways to make this work:


1.       Enable reflection on Edge, and make Core1 and Core2 reflector clients, 
and make sure Edge doesn't set next-hop-self. This will cause Core1 and Core2 
to receive each other's routes by way of their sessions to Edge.

2.       Setup an iBGP session between Core1 and Core2. They will then receive 
each other's routes directly.

3.       Enable LDP on the interfaces used for OSPF. This will avoid an IP 
lookup on Core1, forwarding via MPLS labels instead.

What will be best for you depends on what you are trying to accomplish.

--Eric

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Chris Wright via 
Mikrotik-users
Sent: Friday, January 27, 2017 11:13 AM
To: Mikrotik Users
Subject: [Mikrotik Users] OSPF & BGP

I'm  poking at getting BGP on top of OSPF running so I can connect BGP peers 
using their loopback addresses and running into what seems to be a small hiccup 
with my lab. Three routers in a line. Cores 1 and 2 are BGP peered to the Edge 
loopback, all in the same AS.

Edge                                      Core1                                 
   Core2
10.255.255.1/32 (O)         10.255.255.2/32 (O)         10.255.255.3/32 (O)
10.10.0.1/24 (BGP)          10.10.1.1/24 (BGP)          10.10.2.1/24 (BGP)

All three routers can ping each other's loopback address. BGP routes are being 
advertised and received. My problem is that although the Edge has a BGP route 
for 10.10.2.0/24 recursive via 10.255.255.3, it gets stuck in a routing loop 
between itself and Core1. Core 1 does not have a route for 10.10.2.0/24 because 
it is not BGP peered with Core2. Must it be?

Chris Wright
Network Administrator

_______________________________________________
Mikrotik-users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/mikrotik-users

Reply via email to