[Euro-ix-rs-vwg] New release 1.2.0
Mikhail A. Grishin
magr at ripn.net
Thu Jan 28 16:26:38 CET 2010
Ondrej Zajicek пишет:
> On Thu, Jan 28, 2010 at 04:40:54PM +0300, Mikhail A. Grishin wrote:
>> We found that "Finite state machine error" problem is not related to
>> your patches. It randomly occurs on our production server at the time of
>> daemon startup :((
>> The problem is occurs on small number of peers.
>> (2 or 3 or 4 from ~280)
>> Some problem peers are the same at next startup, some - not.
>> On test server with small number of active peers (and same config) we
>> doesn't see this issue.
>> What can be done? Right now we see the problem on pure 1.2.0 release...
> This might be a buggy version of firmware in the neighbor, as well as
> some strange bug in BIRD.
>> About "UPDATE message immediately after it sent OPEN" - we ask one of
>> our customers (which hit that problem) to collect debug from his side.
>> See the attachments (3 files).
> I can't find the KEEPALIVE message in the log, but i don't know Cisco
> enough to be sure (perhaps it just does not log it).
> The best thing would be to run on route server:
> tcpdump -i eth0 -s 0 -v -n ip host 192.168.1.1 > logfile
See attach (dump with another peer, 22.214.171.124, R34485x1)
As far as I see, the first one from 126.96.36.199 (18:15:06.785501) is
Update, the second one (18:15:06.788230) is Keepalive
But why at another daemon run the session is up with the same peer?
Direction of session establishing make sense?
> (with appropriate network device and IP address of one of problematic
> and send me that logfile.
Mikhail A. Grishin E-mail: magr at ripn.net
Phone: +7 (495) 737-0685 MSK-IX & Russian Institute for Public Networks
Phone: +7 (499) 192-9179 Network Operations Center
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the Bird-users