If you go to 206.220.231.55 and do "sh ip bgp neighbor" for the peer in question does it show that he is using a 3s keep alive? BGP is supposed to use the lower keep alive timer (exchanged as part of the open).
Daniel On Wednesday, December 9, 2015, Alexis Fasquel <[email protected]> wrote: > Hello everyone! > > I just updated a Quagga instance with the new master’s head and I’m having > trouble keeping a BGP session alive. > I believe that I was able to pin point the exact patch that causes the > issue. > > bgpd: Lower BGP's default keepalive/holdtime to 3s/9s > > http://git.savannah.gnu.org/cgit/quagga.git/commit/?h=volatile/patch-tracking/5/accepted&id=f89b09be92bed03b1e5add55dc14ef92e94c52e1 > > The distant instance of Quagga is running version 0.99.24 (Centos 6 on > both machines). Here are the logs: > > [alexis@route-reflector ~]$ sudo bgpd -f /etc/quagga/bgpd.conf -i > /home/quagga/bgpd.pid > 2015/12/09 18:15:41 BGP: Cannot bind path /var/run/bgpd.vty: Permission > denied > 2015/12/09 18:15:41 BGP: BGPd 0.99.25-dev starting: vty@2605, bgp@<all>:179 > pid 31069 > 2015/12/09 18:15:52 BGP: %ADJCHANGE: neighbor 206.220.231.55 Up > 2015/12/09 18:17:04 BGP: Vty connection from 127.0.0.1 > 2015/12/09 18:18:43 BGP: %NOTIFICATION: sent to neighbor 206.220.231.55 > 4/0 (Hold Timer Expired) 0 bytes > 2015/12/09 18:18:43 BGP: Notification sent to neighbor 206.220.231.55: > type 4/0 > 2015/12/09 18:18:43 BGP: %ADJCHANGE: neighbor 206.220.231.55 Down BGP > Notification send > 2015/12/09 18:18:54 BGP: stream_read_try: read failed on fd 13: Connection > reset by peer > 2015/12/09 18:18:54 BGP: 206.220.231.55 [Error] bgp_read_packet error: > Connection reset by peer > 2015/12/09 18:19:04 BGP: stream_read_try: read failed on fd 13: Connection > reset by peer > 2015/12/09 18:19:04 BGP: 206.220.231.55 [Error] bgp_read_packet error: > Connection reset by peer > 2015/12/09 18:19:23 BGP: %ADJCHANGE: neighbor 206.220.231.55 Up > > > Has anyone else experienced the same kind of issue? > > Regards, > Alexis > > > > > On 08 Dec 2015, at 20:19, Donald Sharp <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > > Updated accepted: > > Removed: > zebra: send new interface messages if ifindex changes > > And fixed the header lines for commits > > donald > > > On Tue, Dec 8, 2015 at 4:43 AM, Paul Jakma <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> On Mon, 7 Dec 2015, Donald Sharp wrote: >> >> Can you rephrase here? I am not sure what you are trying to say. >>> >> >> The 'topic' should be consistent. It's used for collating. "Same but >> different" topics makes it harder to mechanically collate - ditto for >> missing. >> >> I.e. maybe just fix the topics, or make the people who submit patches >> without appropriate topics fix them. ;) >> >> regards, >> -- >> Paul Jakma [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');> @pjakma Key ID: >> 64A2FF6A >> Fortune: >> We are all in the gutter, but some of us are looking at the stars. >> -- Oscar Wilde >> > > >
_______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
