Problem to receive an announcement in BIRD.

[Maria Jan Matějka]

On September 1, 2018 11:23:40 PM GMT+02:00, Marcio <marciovinicius.santos at uniriotec.br> wrote:
>  Dear,
> 
> I have a topology with many ASes using BIRD except one. This AS(called
> SDNRTR) is using a SDN technology and it is programmed to announce
> some
> prefixes. When it announces, some of it neighbors(BIRD ASes) are
> rejecting
> the announcement. Follow the line in BIRD logs.
> 
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR: Got UPDATE
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR > added [best] 10.3.1.0/24
> unicast
> 2018-09-01 21:21:08.000 <TRACE> kernel1 < replaced 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR < rejected by protocol
> 10.3.1.0/24
> unicast
> 2018-09-01 21:21:08.000 <TRACE> R8 < replaced 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.000 <TRACE> R8: Sending UPDATE
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR: Got UPDATE
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR > removed [replaced]
> 10.3.1.0/24
> unicast
> 2018-09-01 21:21:08.000 <TRACE> kernel1 < replaced 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR < added 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.000 <TRACE> R8 < rejected by protocol 10.3.1.0/24
> unicast
> 2018-09-01 21:21:08.000 <TRACE> R8 < removed 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.000 <TRACE> SDNRTR: Sending UPDATE
> 2018-09-01 21:21:08.000 <TRACE> R8: Sending UPDATE
> 2018-09-01 21:21:08.001 <TRACE> R8: Got UPDATE
> 2018-09-01 21:21:08.001 <TRACE> R8 > removed [sole] 10.3.1.0/24
> unicast
> 2018-09-01 21:21:08.001 <TRACE> kernel1 < removed 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.001 <TRACE> SDNRTR < removed 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.001 <TRACE> SDNRTR: Sending UPDATE
> 2018-09-01 21:21:08.001 <TRACE> R8: Got UPDATE
> 2018-09-01 21:21:08.001 <TRACE> R8 > added [best] 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.001 <TRACE> kernel1 < added 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.001 <TRACE> SDNRTR < added 10.3.1.0/24 unicast
> 2018-09-01 21:21:08.001 <TRACE> R8 < rejected by protocol 10.3.1.0/24
> unicast
> 
> It is showing "rejected by protocol". Do you know what it means? How
> could
> i solve this trouble?

R8 added best route, it was exported to others and BIRD also tries to export the best route to the source protocol itself (R8 for now). It is normal behavior and I don't see any problem there.

Maria