next-hop announcement/withdrawal process

[Sargun Dhillon]

Have you looked at putting a protocol device per route, and then
having a filter per prefix, so only one of the protocol instances will
be restarted? Another alternative would be to use something like
ExaBGP, which might be a little better suited for this, and have it
peer with BIRD, and have that peer with the opposing device.

On Sun, Aug 3, 2014 at 5:12 PM, Pavlos Parissis
<pavlos.parissis at gmail.com> wrote:
> On 04/08/2014 02:01 πμ, Eric Cables wrote:
>> Try this:
>>
>> protocol device {
>>     scan time 10;   # Scan interfaces every 10 seconds
>>     primary "lo" 127.0.0.1;
>> }
>>
>>
>
> I read the doc about this and I don't see how it could help me.
> Nevertheless, I gave it a try but it didn't have any effect, see
> below the log.
>
> Thanks,
> Pavlos
>
>
> 02:06:33 <INFO> Reconfiguration requested by SIGHUP
> 02:06:33 <INFO> Reconfiguring
> 02:06:33 <TRACE> direct1: Reconfigured
> 02:06:33 <INFO> Reloading protocol direct1
> 02:06:33 <INFO> Restarting protocol direct1
> 02:06:33 <TRACE> direct1: Shutting down
> 02:06:33 <TRACE> direct1: State changed to flush
> 02:06:33 <TRACE> bgp_peer1: Reconfigured
> 02:06:33 <TRACE> bgp_peer2: Reconfigured
> 02:06:33 <INFO> Reconfigured
> 02:06:33 <TRACE> direct1 > removed [sole] 192.168.200.1/32 dev lo
> 02:06:33 <TRACE> bgp_peer2 < removed 192.168.200.1/32 dev lo
> 02:06:33 <TRACE> bgp_peer1 < removed 192.168.200.1/32 dev lo
> 02:06:33 <TRACE> direct1 > removed [sole] 192.168.200.2/32 dev lo
> 02:06:33 <TRACE> bgp_peer2 < removed 192.168.200.2/32 dev lo
> 02:06:33 <TRACE> bgp_peer1 < removed 192.168.200.2/32 dev lo
> 02:06:33 <TRACE> direct1: State changed to down
> 02:06:33 <TRACE> direct1: Starting
> 02:06:33 <TRACE> direct1: Connected to table master
> 02:06:33 <TRACE> direct1: State changed to feed
> 02:06:33 <TRACE> bgp_peer2: Sending UPDATE
> 02:06:33 <TRACE> bgp_peer1: Sending UPDATE
> 02:06:33 <TRACE> direct1 < primary address 127.0.0.0/8 on interface lo added
> 02:06:33 <TRACE> direct1 < secondary address 192.168.200.1/32 on
> interface lo added
> 02:06:33 <TRACE> direct1 > filtered out 192.168.200.1/32 dev lo
> 02:06:33 <TRACE> direct1 < secondary address 192.168.200.2/32 on
> interface lo added
> 02:06:33 <TRACE> direct1 > added [best] 192.168.200.2/32 dev lo
> 02:06:33 <TRACE> bgp_peer2 < added 192.168.200.2/32 dev lo
> 02:06:33 <TRACE> bgp_peer1 < added 192.168.200.2/32 dev lo
> 02:06:33 <TRACE> direct1 < primary address 192.168.80.0/20 on interface
> eth0 added
> 02:06:33 <TRACE> direct1: State changed to up
> 02:06:33 <TRACE> bgp_peer2: Sending UPDATE
> 02:06:33 <TRACE> bgp_peer1: Sending UPDATE
>
>