Hello,

I’m having this problem with BIRD refusing to import a specific route into the routing table. This is strange because this is the session with the neighbor is not new and all of his other prefixes work fine. This is a newly added prefix.

What I see:

bird> show route all 185.200.156.0/22

185.200.156.0/22   via 185.1.40.2 on eth1 [as41059 2017-05-11] * (100) [AS61437i

        Type: BGP unicast univ

        BGP.origin: IGP

        BGP.as_path: 41313 16154 61437

        BGP.next_hop: 185.1.40.2

        BGP.med: 100

        BGP.local_pref: 70

        BGP.community: (0,42) (0,3856) (0,5483) (0,6939) (0,8400) (0,13335) (0,15169) (0,15958) (0,34772) (15169,13200) (16154,10000) (41059,2) (41059,65007) (41313,2) (49401,8877) (49401,49401)

        BGP.ext_community: (ro, 0, 197216)

bird> sh route protocol as16154 all

185.200.156.0/22   via 185.1.40.12 on eth0 [as16154 2017-05-12] * (100) [AS61437i

        Type: BGP unicast univ

        BGP.origin: IGP

        BGP.as_path: 16154 61437

        BGP.next_hop: 185.1.40.12

        BGP.local_pref: 100

        BGP.community: (15169,13300) (16154,10000) (41313,6699) (65000,208)

For some reason the prefix is not installed in the master routing table even though it’s accepted from the neighbor. We use IN-filtering based on queries with irr tool and those queries are correct – the prefix is correctly announced.

From the above I can see that the neighbor prefix is learned after the first one (same prefix, learned from another path).

I’ve cleared the bgp session with the neighbor without any change of the behavior.   

Is there a way to clear the route from the master routing table?

I’d appreciate if someone can give me advice on the matter.

Best regards,

Lyubo