On Thu, Jan 28, 2010 at 12:54:03PM +0300, Mikhail A. Grishin wrote:
First of all, thank you for patch and for fast respond!
After applying both patches (date patch and well-known communities) on production server, we got some strange errors:
Jan 28 12:02:04 msk-rsm2 bird: R34485x1: Error: Finite state machine error Jan 28 12:02:17 msk-rsm2 bird: R13174x1: Error: Finite state machine error Jan 28 12:02:28 msk-rsm2 bird: R3218x1: Error: Finite state machine error Jan 28 12:02:30 msk-rsm2 bird: R41842x1: Error: Finite state machine error Jan 28 12:03:09 msk-rsm2 bird: R34485x1: Error: Finite state machine error Jan 28 12:03:26 msk-rsm2 bird: R41842x1: Error: Finite state machine error Jan 28 12:03:29 msk-rsm2 bird: R13174x1: Error: Finite state machine error Jan 28 12:03:37 msk-rsm2 bird: R3218x1: Error: Finite state machine error
What does it mean?
This error messages mean that BIRD received BGP messages (packets) that were unexpected with regard to the current state of the BGP session. According to the debug log you sent, it seems that the neighbor sent UPDATE message immediately after it sent OPEN message, but it should send KEEPALIVE message first. I have no idea how such problem might be caused by these patches. Is this problem related to just a small number of neighbors and other neighbors work well? -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."