Wednesday, November 21, 2018

Juniper redistribute between BGP/MPLS and OSPF

I am having issues redistributing routes between BGP and OSPF. In a lab environment this works perfectly, but in production not all routes are being redistributed.

We have 2 MX80's in DC1, and another 2 in DC2. The routers are arranged in a grid, with MPLS running on all the cross connects between the 4.

I have a L3 switch in DC1, which i am trying to redistribute the BGP/MPLS routes to via OSPF. The MX's in DC1 have the routes in their inet table, but when i check the OSPF database the routes are not present. THis is only affecting routes originating from DC2.

My Export policy into OSPF is as follows:

policy-statement MZ-MPLS-EXPORT {

from {

instance Atia-MZ-VRF;

protocol [ direct static local bgp mpls ];

}

then accept;

OSPF config:

ospf {

traffic-engineering;

export MZ-MPLS-EXPORT;

import MZ-MPLS-IMPORT;

reference-bandwidth 10g;

area
0.0.0.0 {

interface xe-0/0/2.20;

}

Sanitized section of the routing table:

10.20.0.0/24*[BGP/170] 5d 19:52:07, localpref 100, from
176.74.0.12

AS path: I, validation-state: unverified

> to
176.74.0.202 via xe-0/0/1.2002, label-switched-path to-cll-bgp0

to
176.74.0.5 via xe-0/0/0.2000, label-switched-path to-cll-bgp0

[BGP/170] 5d 19:51:44, localpref 100, from
176.74.0.121

AS path: I, validation-state: unverified

> to
176.74.0.202 via xe-0/0/1.2002, label-switched-path to-cll-bgp1

to
176.74.0.5 via xe-0/0/0.2000, label-switched-path to-cll-bgp1

10.20.2.0/24*[Direct/0] 60w3d 10:04:52

> via ge-1/1/9.4070

[BGP/170] 18w1d 22:18:16, localpref 100, from
176.74.0.9

AS path: I, validation-state: unverified

> to
176.74.0.202 via xe-0/0/1.2002, label-switched-path to-thn-bgp1

to
176.74.0.5 via xe-0/0/0.2000, label-switched-path to-thn-bgp1

Sanitized section of the OSPF database:

Extern
10.2.80.010.2.50.30x80000075 966 0x22 0x2e72 36

Extern *
10.20.2.010.2.50.20x80000074 1946 0x22 0xba24 36

Extern
10.20.2.010.2.50.30x80000075 851 0x22 0xb22a 36

If you notice the OSPF database is missing route to 10.20.0.0/24. This is one of the routes that originates in DC2. All DC2 routes are missing from the OSPF database, although they are in the routing table.

Any ideas? As i said, in GNS3 this works as i expect it to



No comments:

Post a Comment