Hi, I have indeed some peering links on this router (10 I think) I have found last night and today that the problem is gone when I shut one specific peering session. The moment I shut that peering session all updates come in on the other iBGP peers. When I keep that session up the iBGP peers don't receive any updates (except for withdrawls). When I shut a different eBGP peering session, the result is not the same. I'm now trying to get in touch with that peering partner to find out what kind of router they are using and what version of the BGP software on that router. Debugging logs and PCAP file are send to Martin.
Jan Hugo Prins On 11/17/2016 04:23 PM, Mike Tancsa wrote: > On 11/16/2016 5:34 PM, jan hugo prins wrote: >> I don't think this is a memory issue. At least not system base memory. >> My router has 32G of memory, can't imagine that I filled that memory. >> I actually have stats that tell me I don't live under any kind of memory >> pressure, except when it is something inside the daemon. > Yeah, I was thinking more some internal allocation too. Thinking back > to when it originally happened, I am wondering if it started when I > added a few new peers. On your box where you see the issue, do you have > many peers configured ? > > I also see the problem crop up right away when my external peers go > down. There was a scheduled outage at the IX the other night, so all the > eBGP learned routes were withdrawn. When the eBGP peers came back up > back up, almost none of the routes that were learned from my eBGP peers > were propagated to my iBGP peers. I had to do a soft clear out on the > peer group for my iBGP peers to see the routes, and even then, it really > is just a subset of what should be sent. tcpdump confirmed, they were > never pushed out the physical interface. > > ---Mike > > _______________________________________________ Quagga-users mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-users
