Hi Remi, Sorry I didn't see your email sooner, Gmail decided to classify it as spam..
> I move this over to bugs@ which feels more appropriate to me. Chances that > a bgpd developer sees it is higher. > > Somehow there where two identical paths and bgpd could not figure out > which one to prefer. The 13 steps bgpd goes through to find the best are > listed in the bgpd man page. That is the conclusion we arrived at as well. > Do you have a pcap file with the bgp traffic or an mrt dump? (see dump in > man bgpd.conf). This could answer the question why you had two identical > path. > We haven't got any dumps from when the problem happened. Would there still be a point now that the RS is stable? > Showing your config and your regular bgpctl commands could also help with > analyzing the problem. bgpctl command is as follows, it checks for the number of non-established peers: bgpctl show | grep ' 00:0' | grep -v "/" | wc -l Slightly censored bgpd.conf: https://pastebin.com/mqjpjHCx On the other RS we added "announce restart no" to the configuration as was advised earlier, just to see if that would be the difference in case of another problem. Best regards, Pietro
