Hi Alexander! Here some additional information do you requested. On a other server (same OS) I running a BIRD 1.3.11 with OSPFv2, OSPFv3 and a BGP Peering with Full-Prefix-Table. That works fine. --- BIRD configuration --- #log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug }; router id 8X.2X.32.210; #protocol direct { // Commented out for testing purposes # interface "vlan*"; #} protocol kernel { learn; persist; scan time 20; import all; export all; } protocol device { scan time 10; } protocol ospf activezone { rfc1583compat yes; area 0.0.0.0 { interface "vlan3" { cost 10; type broadcast; }; interface "vlan2" { cost 10; type broadcast; passwords { password "totaly secret ;-)" { id 1; }; }; authentication cryptographic; }; }; export all; import all; } Am 09.10.2013 09:25, schrieb Alexander V. Chernikov:
Did this happen with quagga?
No! Quagga works fine but I think BIRD is more powerful (Filtering).
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?
Yes! The "arpresolv" messages are an result of starting BIRD daemon.
Can you provide bird config (at least direct/ospf protocol parts) and describe network topology?
See above.
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) ?
route get 8X.2X.32.211 route to: <hostname> destination: 8X.2X.32.192 mask: 255.255.255.224 interface: vlan2 flags: <UP,DONE> recvpipe sendpipe ssthresh rtt,msec mtu weight expire 0 0 0 0 1500 1 0 Thanks + Regards, Markus