On Wed, Jul 22, 2015 at 05:50:09PM +0100, Bernardo Figueiredo wrote:
Hello,
When restarting some routers at the institution I work, sometimes bird doesn't start announcing any routes until we either restart bird or restart When this happens: ... "bird> show ospf (...) Area networks: 10.3.0.0/16 Advertise 10.0.0.0/16 Advertise (...)
I think that even though when bird first starts it shouldn't immediately start announcing(because it didn't see that the interfaces ip addresses), it should after 10 seconds when it scans again, because then the interfaces are already fully configured. ... So, my question is, shouldn't the Device protocol scan update see that the ip addresses of an interface have changed and if so, start announcing the route.
Hello BIRD Device protocol generally does not have problems with noticing new addresses. Most likely it could be problem with BIRD OSPF protocol not activating the interfaces / areas. Could you also report results of 'show interfaces' and 'show ospf interfaces' when it works and when it does not? Does help just restarting the OSPF protocol (birdc restart ospf1)? -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."