On Mon, Oct 27, 2014 at 09:42:32PM -0400, Alex Laties wrote: > Hi all, > > We currently have a large production deployment using version bird 1.3.7 > for OSPF. > > We're seeing the following message pretty frequently in our logs: > > > dbdes - sequence mismatch neighbor 192.168.39.216 (full) > > The period between these messages is irregular. Sometimes these occur > within a few seconds of each other. Sometimes it can be a few hours between > these messages.
Hi
These messages are the result of receiving DBDES packets when a neighbor
adjacency is already established. This shouldn't happen in normal
operation, although i would guess it might happen in some circumstances
if the other side is hard restarted and became available again before the
other side notices it (by inactivity timer).
First, i would suggest to use latest version of BIRD.
Second, i would suggest enabling 'debug { events }' for OSPF protocol
to see what happens on boths sides immediately before the mismatch.
Are these messages appear just after the neighbor changed state to full
or after some time after the adjacency establishment?
Is the other side also BIRD?
Is the OSPF interface in broadcast or ptp mode?
Is this regular or some kind of unusual setting?
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: [email protected])
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
signature.asc
Description: Digital signature
