[quagga-dev 16625] Re: Weird BGP Behavoiur

[Richard J Palmer]

HI All

Sorry for the break on this BUT I have been working on the routers in
the background...

I can confirm that this issue is now occurring on other servers here
an SEEMS to be any release after 0.99.24

I have now managed to compile the latest versions (1.2.1) and this
does not help

I am using the latest slackware distribution and kernel Linux 4.4.38
(it happens on earlier kernels too)
As before the router *starts* OK but then the OutQ for some sessions
(typically those with a lot of prefixes / internal peers)

I am more than happy to help with resolving the core as this is
causing real issues. I do have a background in c coding (though I have
noot touched quagga itself)

Is someone able to help please ?

Richard



Richard Palmer | Director | Merula Limited
Company Registered in England and Wales No. 3243995
5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS
Phone [phone] | Support 0845 330 0666

--- Original message ---
Subject: Weird BGP Behavoiur
Date: Sunday, 05/03/2017 12:40 AM
Hi
I am seeing odd behavour on one of our quagga boxes here and I am
looking for some help
We have approx 6 Quagga servers which are installed on Supermicro
Servers with 8G RAM each. RAM usage is low and CPU usage is generally
low.
BGP router identifier a.b.c.d, local AS number 12345
RIB entries 1186136, using 127 MiB of memory
Peers 330, using 2929 KiB of memory
Peer groups 5, using 160 bytes of memory
217.146.96.73 4 4234 702 587 0 0 0 01:36:32
1459
Which is sending / receiving... However with some sessions which I am
1.2.3.4 4 23454 100 672 0 0 630540 01:36:40
1
2.3.4.5 4 23454 100 668 0 0 630555 01:36:40
1
9.8.7.6 4 12345 100 661 0 0 530342 01:36:41
3
5.6.3.2 4 12345 18551 1364 0 0 525874 01:36:43
95301
You will see the 'OutQ' Colum is HUGE and does not decrease. I can't
see any errors - IF I run sh ip bgp 8.8.8.8 for example it will show
the route is being advertised to a peer router - BUT the remote router
does not have the prefix prsumably as it i stuck in the queue.
From what I can see this is the only router seeing this - all have
the same kernel & quagga version. I have tried upgrading the kernel
(all are Linux 3.10.17 based on slakeware and with Intel e1000 NICs)
and the Quagga version (to 1.1)
I can't see anything being logged on the linux logs OR the quagga logs
- happy to look at anything that will help
Can someone point out what I have done stupid here ?
Thanks in advance
Richard Palmer | Director | Merula Limited
Company Registered in England and Wales No. 3243995
5 Avro Court, Huntingdon, Cambridgeshire, PE29 6XS
Phone [phone] | Support 0845 330 0666