[prev in list] [next in list] [prev in thread] [next in thread]
List: bird-users
Subject: OSPF sequence mismatch occurring regularly
From: Alex Laties <agl () tumblr ! com>
Date: 2014-10-28 1:42:32
Message-ID: CA+uGLU2-WJb2XPS=+x6RTXBJ578PCUJ4KZxwauzLMp3Cd0iAsQ () mail ! gmail ! com
[Download RAW message or body]
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.
As a result of these mismatches, we see the following on our router (as an
example):
> RPD_OSPF_NBRDOWN: OSPF neighbor 192.168.39.203 (realm ospf-v2 vlan.612
area 0.0.0.51) state changed from Full to Down due to InActiveTimer (event
reason: neighbor was inactive and declared dead)
On the bright side, nodes that are in the DOWN state are able to transition
to EXSTART, then FULL.
I'd like to better understand what's occurring here and what would be the
steps to fix this.
Our config looks like:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# Configure logging
log "/var/log/bird.log" all;
# Override router ID
router id 192.168.39.203;
# Turn on global debugging of all protocols
debug protocols all;
# This pseudo-protocol watches all interface up/down events.
protocol direct {
interface "-eth*", "*"; # Restrict network interfaces it works with
}
# This pseudo-protocol performs synchronization between BIRD's routing
tables and the kernel.
protocol kernel {
export all;
}
# This pseudo-protocol watches all interface up/down events.
protocol device {
scan time 10; # Scan interfaces every 10 seconds
}
# Static routes (again, there can be multiple instances, so that you
# can disable/enable various groups of static routes on the fly).
protocol static {
# Advertising custom domain IP
route 192.168.41.30/32 via 192.168.39.203;
}
# Talk OSPF back to the MX80s to advertise the /32
protocol ospf {
import all;
export filter {
ospf_metric1 = 1000;
if source = RTS_STATIC then accept; else reject;
};
area 0.0.0.51 {
nssa;
interface "lo*" {
stub;
};
interface "eth*" {
hello 1;
dead count 3;
authentication simple;
password "sample";
};
};
}
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I personally have very little experience with bird and configuring OSPF and
would appreciate any help.
Thanks,
-Alex Laties
[Attachment #3 (text/html)]
<div dir="ltr">Hi all,<div><br></div><div>We currently have a large production \
deployment using version bird 1.3.7 for OSPF.</div><div><br></div><div>We're \
seeing the following message pretty frequently in our \
logs:</div><div><br></div><div>> dbdes - sequence mismatch neighbor 192.168.39.216 \
(full)<br></div><div><br></div><div>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.</div><div><br></div><div>As a result of these \
mismatches, we see the following on our router (as an \
example):</div><div><br></div><div>> <span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">RPD_OSPF_NBRDOWN: \
OSPF neighbor 192.168.39.203 (realm ospf-v2 vlan.612 area 0.0.0.51) state changed \
from Full to Down due to InActiveTimer (event reason: neighbor was inactive and \
declared dead)</span></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px"><br></span></div><div><font \
color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px">On the bright side, nodes that are in the \
DOWN state are able to transition to EXSTART, then \
FULL.<br></span></font></div><div><font color="#333333" face="Arial, \
sans-serif"><span style="font-size:14px;line-height:20px"><br></span></font></div><div><font \
color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px">I'd like to better understand what's \
occurring here and what would be the steps to fix this.</span></font></div><div><font \
color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px"><br></span></font></div><div><font \
color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px">Our config looks \
like:</span></font></div><div><font color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px">>>>>>>>>>>>&g \
t;>>>>>>>>>>>>>>>>>>>>> \
>>>>>>>>>>>>>>>>>>></span></font></div><div><font \
color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px"><div style># Configure logging</div><div \
style>log "/var/log/bird.log" all;</div><div style><br></div><div style># \
Override router ID</div><div style>router id 192.168.39.203;</div><div \
style><br></div><div style># Turn on global debugging of all protocols</div><div \
style>debug protocols all;</div><div style><br></div><div style># This \
pseudo-protocol watches all interface up/down events.</div><div style>protocol direct \
{</div><div style> interface "-eth*", "*"; # Restrict network \
interfaces it works with</div><div style>}</div><div style><br></div><div style># \
This pseudo-protocol performs synchronization between BIRD's routing tables and \
the kernel.</div><div style>protocol kernel {</div><div style> export \
all;</div><div style>}</div><div style><br></div><div style># This pseudo-protocol \
watches all interface up/down events.</div><div style>protocol device {</div><div \
style> scan time 10; # Scan interfaces every 10 seconds</div><div \
style>}</div><div style><br></div><div style># Static routes (again, there can be \
multiple instances, so that you</div><div style># can disable/enable various groups \
of static routes on the fly).</div><div style>protocol static {</div><div style> # \
Advertising custom domain IP</div><div style> route <a \
href="http://192.168.41.30/32">192.168.41.30/32</a> via 192.168.39.203;</div><div \
style>}</div><div style><br></div><div style># Talk OSPF back to the MX80s to \
advertise the /32</div><div style>protocol ospf {</div><div style> import \
all;</div><div style> export filter {</div><div style> ospf_metric1 = \
1000;</div><div style> if source = RTS_STATIC then accept; else \
reject;</div><div style> };</div><div style><br></div><div style> area 0.0.0.51 \
{</div><div style> nssa;</div><div style> interface "lo*" \
{</div><div style> stub;</div><div style> };</div><div style> \
interface "eth*" {</div><div style> hello 1;</div><div style> \
dead count 3;</div><div style> authentication simple;</div><div style> \
password "sample";</div><div style> };</div><div style> };</div><div \
style>}</div></span></font></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20p \
x">>>>>>>>>>>>>>>>>>>>>> \
;>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>></span><font \
color="#333333" face="Arial, sans-serif"><span \
style="font-size:14px;line-height:20px"><br></span></font></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px"><br></span></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">I \
personally have very little experience with bird and configuring OSPF and would \
appreciate any help.</span></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px"><br></span></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Thanks,</span></div><div><span \
style="color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">-Alex \
Laties</span></div><div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic