BIRD 1.3.11 (ports) on FreeBSD 9.1-p7

[Alexander V. Chernikov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09.10.2013 11:07, Markus Grundmann wrote:
> Good morning!
> 
> My name is Markus and I have an issue with the BIRD 1.3.11. Since I
> had switched from Quagga 0.9x.x to BIRD 1.3.11 I have more and more
> trouble in my network with OSPFv2. After some minutes or hours the
> ARP resolution doesn't work and tons of messages are logged by BIRD
> and the "kernel". All FreeBSD 9.1-p7 servers sending messages to
> their syslog
Did this happen with quagga?
> (see below).
> 
> Virtual servers are no longer reachable. What's the problem? The
> same messages are generated by OSPFv3 processes.
Em, "arpresolve" messages are generated by kernel. Are you talking
about "LSA disappeared" ones?
> 
> --- Some Logs --- arpresolve: can't allocate llinfo for
> 8X.2X.32.211 arpresolve: can't allocate llinfo for 8X.2X.32.211 
> arpresolve: can't allocate llinfo for 8X.2X.32.211 arpresolve:
> can't allocate llinfo for 8X.2X.32.211 arpresolve: can't allocate
> llinfo for 8X.2X.32.211 arpresolve: can't allocate llinfo for
> 8X.2X.32.211 arpresolve: can't allocate llinfo for 8X.2X.32.211 
> arpresolve: can't allocate llinfo for 8X.2X.32.211 [..] arpresolve:
> can't allocate llinfo for 8X.2X.32.211 arpresolve: can't allocate
> llinfo for 8X.2X.32.211 arpresolve: can't allocate llinfo for
> 8X.2X.32.211 arpresolve: can't allocate llinfo for 8X.2X.32.211 
> arpresolve: can't allocate llinfo for 8X.2X.32.211 arpresolve:
> can't allocate llinfo for 8X.2X.32.197 arpresolve: can't allocate
> llinfo for 8X.2X.32.211 arpresolve: can't allocate llinfo for
> 8X.2X.32.211 arpresolve: can't allocate llinfo for 8X.2X.32.211 
> arpresolve: can't allocate llinfo for 8X.2X.32.211 [..] arpresolve:
> can't allocate llinfo for 8X.2X.32.211 arpresolve: can't allocate
> llinfo for 8X.2X.32.211 arpresolve: can't allocate llinfo for
> 8X.2X.32.211 arpresolve: can't allocate llinfo for 8X.2X.32.211 
> arpresolve: can't allocate llinfo for 8X.2X.32.211

Can you provide bird config (at least direct/ospf protocol parts) and
describe network topology?
E.g. how the server can reach "8X.2X.32.211" or other addresses in dmesg.
What does output of "route get 8X.2X.32.211" show (when working
"normal" and when problem starts) ?
> 
> ### The server with the NFS service is running BIRD 1.3.11 (FreeBSD
> ports). ### Over 1000 messages will be logged.
> 
> $ dmesg | grep arpresolve | wc -l 1189
> 
> ### After a while some servers are not longer available because
> ARP resolution failed.
> 
> Oct  9 00:55:39 clarion kernel: newnfs server
> trinitron:/archiv/clarion: not responding
> 
> ### When I restart BIRD the ARP resolution will work again.
> 
> Custom Kernel: 9.1-RELEASE-p7 FreeBSD 9.1-RELEASE-p7 #4: Tue Sep 10
> 14:31:40 CEST 2013 amd64
> 
> 
> ### All OSPF neighbors sending tons of warnings! :-(
> 
> Oct  9 08:30:35 j bird: OSPF: LSA disappeared (Type: 0005, Id: 
> 10.82.206.193, Rt: 8X.2X.32.210) Oct  9 08:30:35 j bird: OSPF: LSA
> disappeared (Type: 0005, Id: 8X.2X.1.33, Rt: 8X.2X.32.210) Oct  9
> 08:30:35 j bird: OSPF: LSA disappeared (Type: 0005, Id: 
> 8X.2X.32.210, Rt: 8X.2X.32.210) Oct  9 08:30:35 j bird: OSPF: LSA
> disappeared (Type: 0005, Id: 8X.2X.32.216, Rt: 8X.2X.32.210) Oct  9
> 08:30:35 j bird: OSPF: LSA disappeared (Type: 0005, Id: 
> 8X.2X.32.217, Rt: 8X.2X.32.210) Oct  9 08:30:35 j bird: OSPF: LSA
> disappeared (Type: 0002, Id: 8X.2X.1.33, Rt: 8X.2X.32.210) Oct  9
> 08:30:35 j bird: OSPF: LSA disappeared (Type: 0002, Id: 
> 8X.2X.32.210, Rt: 8X.2X.32.210) Oct  9 08:30:40 j bird: OSPF: LSA
> disappeared (Type: 0005, Id: 10.82.206.193, Rt: 8X.2X.32.210) Oct
> 9 08:30:40 j bird: OSPF: LSA disappeared (Type: 0005, Id: 
> 8X.2X.1.33, Rt: 8X.2X.32.210) Oct  9 08:30:40 j bird: OSPF: LSA
> disappeared (Type: 0005, Id: 8X.2X.32.210, Rt: 8X.2X.32.210) Oct  9
> 08:30:40 j bird: OSPF: LSA disappeared (Type: 0005, Id: 
> 8X.2X.32.216, Rt: 8X.2X.32.210) Oct  9 08:30:40 j bird: OSPF: LSA
> disappeared (Type: 0005, Id: 8X.2X.32.217, Rt: 8X.2X.32.210) Oct  9
> 08:30:40 j bird: OSPF: LSA disappeared (Type: 0002, Id: 82.2X.1.33,
> Rt: 8X.2X.32.210) Oct  9 08:30:40 j bird: OSPF: LSA disappeared
> (Type: 0002, Id: 8X.2X.32.210, Rt: 8X.2X.32.210)
This is annoying, but harmless.
> 
> ### It's a little bit too much ;-)
> 
> grep "LSA disappeared" /var/log/messages|wc -l 3585
> 
> ### /var/log/messages on a other machine :-(
> 
> [..] Oct  9 05:02:19 clarion bird: OSPF: LSA disappeared (Type:
> 0005, Id: 0.0.0.0, Rt: 82.2X.32.193) Oct  9 05:02:24 clarion bird:
> OSPF: LSA disappeared (Type: 0002, Id: 8X.2X.32.193, Rt:
> 8X.2X.32.193) Oct  9 05:02:24 clarion bird: OSPF: LSA disappeared
> (Type: 0005, Id: 0.0.0.0, Rt: 82.2X.32.193) Oct  9 05:02:28 clarion
> bird: OSPF: LSA disappeared (Type: 0002, Id: 8X.2X.32.193, Rt:
> 8X.2X.32.193) Oct  9 05:02:59 clarion last message repeated 6
> times Oct  9 05:05:04 clarion last message repeated 25 times Oct  9
> 05:15:08 clarion last message repeated 121 times Oct  9 05:25:09
> clarion last message repeated 120 times Oct  9 05:35:08 clarion
> last message repeated 120 times Oct  9 05:45:10 clarion last
> message repeated 120 times Oct  9 05:55:11 clarion last message
> repeated 120 times Oct  9 06:05:10 clarion last message repeated
> 120 times Oct  9 06:15:10 clarion last message repeated 120 times 
> Oct  9 06:25:10 clarion last message repeated 120 times Oct  9
> 06:35:10 clarion last message repeated 120 times Oct  9 06:45:11
> clarion last message repeated 120 times Oct  9 06:55:12 clarion
> last message repeated 120 times Oct  9 07:05:12 clarion last
> message repeated 120 times Oct  9 07:15:13 clarion last message
> repeated 120 times Oct  9 07:25:14 clarion last message repeated
> 120 times Oct  9 07:35:15 clarion last message repeated 120 times 
> Oct  9 07:45:14 clarion last message repeated 120 times Oct  9
> 07:55:15 clarion last message repeated 120 times Oct  9 08:05:13
> clarion last message repeated 119 times [..]
> 
> 
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJVBO0ACgkQwcJ4iSZ1q2kHHgCfdhCedWyXnIMWpzy1cMFVmP6w
RG0AoID+kJ/9RIHQLyq3pEJWTgkJsBVJ
=oIIX
-----END PGP SIGNATURE-----