Thank you Claudio!

I didn't even think of that, as these Route Reflectors are completely
out-of-band and not in the path of routing at all.
Of course they wouldn't work without having a route to the nexthop :-)

I'm much more versed in troubleshooting BGP on IOS, but with all the
work you just put into OpenBGPD I wanted to put it to the task.

Thanks so much for your help! It is working now:
================================================
RR$ bgpctl show ip bgp nei 100.92.127.37 out
flags: * = Valid, > = Selected, I = via IBGP, A = Announced,
       S = Stale, E = Error
origin validation state: N = not-found, V = valid, ! = invalid
origin: i = IGP, e = EGP, ? = Incomplete

flags ovs destination          gateway          lpref   med aspath origin
I*>     N rd 1234:5678 172.29.20.0/24 100.92.127.101     100     0 i
================================================

On Thu, Dec 20, 2018 at 5:49 PM Claudio Jeker <cje...@diehard.n-r-g.com> wrote:
>
> On Thu, Dec 20, 2018 at 04:52:34PM -0500, Henry Bonath wrote:
> > Hello, I am having an issue with some route-reflectors I set up to try
> > to support a new MPLS backbone.
> > The majority of the MPLS Routers are Cisco IOS, with some of the PE
> > devices running OpenBSD.
> > The Route Reflectors are OpenBSD 6.4. The route reflectors are not
> > neighbors of each other.
> >
> > Here is my config:
> > ================================================
> > ASN="1234"
> > AS $ASN
> > router-id 172.16.16.211
> >
> > group "IBGP" {
> >         remote-as $ASN
> >         announce IPv4 vpn
> >         route-reflector 172.16.16.211
> >         local-address 172.16.16.211
> >         neighbor 100.92.64.0/18 {
> >         }
> >
> > }
> > # IBGP: allow all updates to and from our IBGP neighbors
> > allow from any
> > allow to any
> >
> > ================================================
> >
> > On the reflectors themselves, if I issue a "bgpctl show rib" I do see
> > VPNv4 routes, and "bgpctl show summary" I see that I am receiving
> > prefixes:
> > ================================================
> > RR$ bgpctl show rib
> > flags: * = Valid, > = Selected, I = via IBGP, A = Announced,
> >        S = Stale, E = Error
> > origin validation state: N = not-found, V = valid, ! = invalid
> > origin: i = IGP, e = EGP, ? = Incomplete
> >
> > flags ovs destination          gateway          lpref   med aspath origin
> > I       N rd 1234:5678 10.25.80.0/24 100.92.127.20      100     0 ?
> > I       N rd 1234:5678 172.29.20.0/24 100.92.127.101     100     0 i
> > ================================================
>
> These routes are not valid (*) is missing. Which does result in them not
> being selected and because of that not reflected. At least I would look
> into that. Normally this is cause because the nexthop is not valid. Maybe
> you need to add the IGP routes or in the worst case use 'nexthop qualify
> via default'.
>
> > If I do the same on a PE, it shows Zero prefixes received from either
> > route reflector:
> > ================================================
> > PE$ bgpctl show rib
> > flags: * = Valid, > = Selected, I = via IBGP, A = Announced,
> >        S = Stale, E = Error
> > origin validation state: N = not-found, V = valid, ! = invalid
> > origin: i = IGP, e = EGP, ? = Incomplete
> >
> > flags ovs destination          gateway          lpref   med aspath origin
> > I*>     N rd 1234:5678 10.25.80.0/24 100.92.127.20      100     0 ?
> > AI*>    N rd 1234:5678 172.29.20.0/24 rd 0:0 0.0.0.0     100     0 i
> > [hbonath@hb-mplspe-01]:~$ bgpctl show summ
> > Neighbor                   AS    MsgRcvd    MsgSent  OutQ Up/Down  
> > State/PrfRcvd
> > bgp-rr-02               1234         41         42     0 00:19:08      0
> > bgp-rr-01               1234         41         42     0 00:19:08      0
> > ================================================
> >
> > What am I missing here? Does it have to do with the flags that the
> > Route-Reflector is showing?
> > Thanks in advance!
> >
>
> --
> :wq Claudio
>

Reply via email to