Interesting. The problem I was seeing had to do with a default route learned via BGP and redistributed via OSPF not being redistribute properly *sometimes* and changes in system timing resulted in changes of behaviors (from very rare to all the time). I think I have a reliable way to reproduce so plan on trying to run it to ground post IETF... Lou On 3/27/2017 3:24 PM, Mike Tancsa wrote:
On 3/27/2017 3:15 PM, Lou Berger wrote:
I thought I was referring to a https://bugzilla.quagga.net/show_bug.cgi?id=870 but in rereading the description that the problem I've been looking into is only impacting v4 so is probably a different one... FYI, I see this as well on ipv4 prefixes with Quagga 1.2.1. Not sure if its the same bug or not in bugID 870, but similar behaviour as well as the problem router showing a positive number in the OutQ in the bgp summary. One other thing I noticed-- If on my problematic router, I bring up all my ibgp peers first, and then bring up my external peers, my ibgp peers see close to 120K prefixes (which they should). If for some reason, an ibgp peer gets reset, after that, they will only see a subset of peers (20K). In the mean time, the peers that have not lost their initial session, will slowly over a period of days start to loose the amount of prefixes they should be seeing.
---Mike
On 3/27/2017 2:13 PM, Martin Winter wrote:
I’ll join.
PS: Which “1.x v4 BGP issue” ? (Pointer?) Quagga 1.x BGP issue?
- Martin
On 27 Mar 2017, at 4:40, Lou Berger wrote:
Anyone interested in meeting up this week? How about continuing the traditional Thursday lunchtime in the hotel lobby?
Lou
PS I'd be happy to discuss the 1.x v4 BGP issue that some have reported...
_______________________________________________ frr mailing list frr@lists.nox.tf https://lists.nox.tf/listinfo/frr
_______________________________________________ frr mailing list frr@lists.nox.tf https://lists.nox.tf/listinfo/frr