MICE route reflect hiccup last night?
Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened? Jan 9 03:41:41 192.168.0.85 BFD: Session DOWN for 206.108.255.1 on eth 2/2 Reason:Detection Time Expired Jan 9 03:41:41 192.168.0.85 BFD: Session UP for 206.108.255.1 on eth 2/2 Jan 9 03:41:41 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Rcv Notification:CEASE Message) Jan 9 03:41:41 192.168.0.85 BFD: Session DOWN for 206.108.255.1 on eth 2/2 Reason:Administratively Down Jan 9 03:41:41 192.168.0.85 BFD: Session DOWN for 2001:504:27::d1af:0:1 on eth 2/2 Reason:Detection Time Expired Jan 9 03:41:41 192.168.0.85 BGP: Peer 2001:504:27::d1af:0:1 DOWN (Rcv Notification:CEASE Message) Jan 9 03:42:36 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Jan 9 03:42:36 192.168.0.85 BFD: Session UP for 206.108.255.1 on eth 2/2 Jan 9 03:42:41 192.168.0.85 BGP: Peer 2001:504:27::d1af:0:1 UP (ESTABLISHED) Frank
On Tue, Jan 09, 2018 at 08:25:44PM +0000, Frank Bulk wrote:
Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened?
No, but your BFD session received.. 2018-01-09 03:41:40 <RMT> bfd1: Bad packet from 206.108.255.67 - invalid flags (248) That's all I've got related to it in the logs. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Thanks. This is why BFD can be so frustrating. So just one bad packet and the BFD session was torn down? Or three in a row? Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Tuesday, January 09, 2018 3:08 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE route reflect hiccup last night? On Tue, Jan 09, 2018 at 08:25:44PM +0000, Frank Bulk wrote:
Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened?
No, but your BFD session received.. 2018-01-09 03:41:40 <RMT> bfd1: Bad packet from 206.108.255.67 - invalid flags (248) That's all I've got related to it in the logs. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
It is set for missing 3 BFD updates will drop it, but I believe an error condition like "invalid flags (248)" is what caused the issue. I don't see any flags in RFC5880, I suspect source code reading would be next to see what BIRD thought of flags in BFD that aren't mentioned in the RFC. On Tue, Jan 09, 2018 at 10:07:17PM +0000, Frank Bulk wrote:
Thanks. This is why BFD can be so frustrating. So just one bad packet and the BFD session was torn down? Or three in a row?
Frank
-----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Tuesday, January 09, 2018 3:08 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE route reflect hiccup last night?
On Tue, Jan 09, 2018 at 08:25:44PM +0000, Frank Bulk wrote:
Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened?
No, but your BFD session received..
2018-01-09 03:41:40 <RMT> bfd1: Bad packet from 206.108.255.67 - invalid flags (248)
That's all I've got related to it in the logs.
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
participants (2)
-
Doug McIntyre -
Frank Bulk