On Wed, 29 Apr 2015 11:02:09 +0200
Marko Cupać <marko.cu...@mimar.rs> wrote:

> On Tue, 28 Apr 2015 15:11:21 +0200
> Claudio Jeker <cje...@diehard.n-r-g.com> wrote:
> 
> > The "fatal in RDE: peer_up: bad state" bug is fixed in 5.7 IIRC. Not
> > sure if it was backported to 5.6. As a workaround you can disable
> > the graceful restart capability to not trigger that code path.
> 
> I was intending to upgrade on Friday anyway so no problem. In the
> meantime I updated to -stable, it's too early to say if it fixed it.

I am on 5.7 release + errata patches now, and bgpd crashed again:

May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sync error
May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sending 
notification: Header error, synchronization error
May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): graceful 
restart of IPv4 unicast, keeping routes
May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Established -> Idle, reason: Fatal error
May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Idle -> Connect, reason: Start
May  6 10:06:07 bgp1 bgpd[3820]: incremented the demote state of group 'carp'
May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Connect -> OpenSent, reason: Connection opened
May  6 10:06:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
OpenSent -> Active, reason: Connection closed
May  6 10:06:08 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sending 
notification: error in UPDATE message, attribute length wrong
May  6 10:06:08 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Active -> Idle, reason: Fatal error
May  6 10:06:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Idle -> Connect, reason: Start
May  6 10:06:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Connect -> OpenSent, reason: Connection opened
May  6 10:06:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
OpenSent -> Active, reason: Connection closed
May  6 10:08:07 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): graceful 
restart of IPv4 unicast, time-out, flushing
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Active -> Connect, reason: ConnectRetryTimer expired
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Connect -> OpenSent, reason: Connection opened
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
OpenSent -> OpenConfirm, reason: OPEN message received
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
OpenConfirm -> Established, reason: KEEPALIVE message received
May  6 10:08:38 bgp1 bgpd[31241]: fatal in RDE: peer_up: bad state
May  6 10:08:38 bgp1 bgpd[3820]: dispatch_imsg in main: pipe closed
May  6 10:08:38 bgp1 bgpd[3820]: decremented the demote state of group 'carp'
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): sending 
notification: Cease, administratively down
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 82.117.192.121 (sbb): state change 
Established -> Idle, reason: Stop
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 178.253.194.253 (orion): sending 
notification: Cease, administratively down
May  6 10:08:38 bgp1 bgpd[11681]: neighbor 178.253.194.253 (orion): state 
change Established -> Idle, reason: Stop
May  6 10:08:38 bgp1 bgpd[11681]: session engine exiting
May  6 10:08:40 bgp1 bgpd[3820]: kernel routing table 0 (Loc-RIB) decoupled
May  6 10:08:40 bgp1 bgpd[3820]: Terminating

I guess bug is not solved in 5.7 release then. Maybe 5.7 stable?

This issue is having really bad impact on my network. Both ISP links
are up and running, but - as bgpd dies - my firewall has no routes
which effectively stops the traffic flow with the Internet.

I have contacted ISPs and ask them to check if they are sending us bad
bgp packets. Regardless of that, I think bgpd shouldn't just shutdown
itself no matter what payload it gets?

Any help with this would be highly appreciated.
-- 
Marko Cupać
https://www.mimar.rs

Reply via email to