Hi all, I'm facing a weird problem: we run BIRD with identical configuration on 2 different servers, both connected on the same peering lan. We had "Error: Neighbor lost" error message for all the IPv6 bgp speakers, on both machines, while the v4 deamon had no problems. Issuing a "kill -s HUP" didn't change anything, while shutting the deamon down and then re-starting it actually solved the problem. From the logfile I see that all the speakers went to "flush" state, then "stop", and then "start", but none of the sessions came up. Any clue on what could be the cause? TIA, Simone. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Stefan Jakob wrote:
Am 23.02.12 13:17, schrieb Simone Morandini:
Any clue on what could be the cause?
Can you please check, if your route for the peering lan is still on your interface?
do you mean if the route-servers lost connectivity towards the peering lan? After stopping and restarting the bird6 deamon everything went back to normal behavior, I'm not sure what triggered the error I was having...
Pls. provide Bird version and operating system descriptor.
we have a 1.2.3 (to be upgraded soon) and a 1.3.1, on Fedora. Thanks. Simone. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Am 23.02.12 15:13, schrieb Simone Morandini:
do you mean if the route-servers lost connectivity towards the peering lan? After stopping and restarting the bird6 deamon everything went back to normal behavior, I'm not sure what triggered the error I was having...
Yes. Since only IPv6 of your dual-stack setup got lost. I saw something similar with an expiration timer of the peering IPv6 route. ip -6 route | grep expire showed an expire for my prefix for the peering lan. Maybe there is a problem with your neighbor cache or something like this. Guess you also disabled all not needed/not intended IPv6 proc features like accepting IPv6 RAs and so on? /proc/sys/net/ipv6/conf/$INTERFACE/ I don't have any real clue regarding your problem, but IPv6 default settings is worth checking anyway. Rgds, Stefan
On Thu, Feb 23, 2012 at 03:13:12PM +0100, Simone Morandini wrote:
Stefan Jakob wrote:
Am 23.02.12 13:17, schrieb Simone Morandini:
Any clue on what could be the cause?
Can you please check, if your route for the peering lan is still on your interface?
do you mean if the route-servers lost connectivity towards the peering lan? After stopping and restarting the bird6 deamon everything went back to normal behavior, I'm not sure what triggered the error I was having...
Pls. provide Bird version and operating system descriptor.
we have a 1.2.3 (to be upgraded soon) and a 1.3.1, on Fedora.
I remembered that i fixed some bug related to neighbor cache and BGP that would cause something like if iface addresses are added and removed, i would suggest to update to newest version. -- 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."
participants (3)
-
Ondrej Zajicek -
Simone Morandini -
Stefan Jakob