On Thu, Jan 28, 2010 at 06:26:38PM +0300, Mikhail A. Grishin wrote:
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, 193.232.246.198, R34485x1)
As far as I see, the first one from 193.232.246.198 (18:15:06.785501) is Update, the second one (18:15:06.788230) is Keepalive
Yes, that is pretty clear.
But why at another daemon run the session is up with the same peer? Direction of session establishing make sense?
Perhaps direction, or perhaps the different daemon is less strict with regard to state changes and accept this even if it is contrary to the BGP specification. -- 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."