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?
>From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Doug McIntyre
>Sent: Tuesday, January 09, 2018 3:08 PM
>To: [log in to unmask]
>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 22.214.171.124 - invalid flags (248)
>That's all I've got related to it in the logs.
>Doug McIntyre <[log in to unmask]>
> ~.~ ipHouse ~.~
> Network Engineer/Provisioning/Jack of all Trades
Doug McIntyre <[log in to unmask]>
~.~ ipHouse ~.~
Network Engineer/Provisioning/Jack of all Trades