On 2016 Apr 04 (Mon) at 18:07:52 +0100 (+0100), Stuart Henderson wrote:
:On 2016/03/31 12:40, Peter Hessler wrote:
:> We see occasional bgpd deaths during boot. This is apparently caused by
:> a race with ospfd starting up.
:>
:> The underlying problem is we are reciving a CHANGE route message fo
On 2016/03/31 12:40, Peter Hessler wrote:
> We see occasional bgpd deaths during boot. This is apparently caused by
> a race with ospfd starting up.
>
> The underlying problem is we are reciving a CHANGE route message for an
> MPATH path, where the gateway doesn't match the route message. In our
We see occasional bgpd deaths during boot. This is apparently caused by
a race with ospfd starting up.
The underlying problem is we are reciving a CHANGE route message for an
MPATH path, where the gateway doesn't match the route message. In our
case, the prefix is assigned to a Connected (and Ba
Did anyone have any ideas about this?
On 2015/12/18 01:36, Stuart Henderson wrote:
> I updated a box running bgpd/ospfd/ospf6d earlier and ran into this when
> bgpd started at boot time:
>
> $ syslogc bgpd | cut -d' ' -f 3,5-
> 21:03:23 bgpd[2742]: startup
> 21:03:23 bgpd[2742]: rereading config
I updated a box running bgpd/ospfd/ospf6d earlier and ran into this when
bgpd started at boot time:
$ syslogc bgpd | cut -d' ' -f 3,5-
21:03:23 bgpd[2742]: startup
21:03:23 bgpd[2742]: rereading config
21:03:23 bgpd[8249]: route decision engine ready
21:03:23 bgpd[2742]: new ktable rdomain_0 for r
