[Xorp-hackers] OSPF Failures

Tim Durack tdurack@gmail.com
Wed, 14 Dec 2005 21:30:34 -0500


------=_Part_19534_14780805.1134613834185
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I "fixed" the problem by commenting out ospf/routing_table.cc line 465:

    // xxx XLOG_ASSERT(0 =3D=3D _entries.count(area));

This might not be the correct way to fix things, but it works for me...

Tim:>


On 12/7/05, Tim Durack <tdurack@gmail.com> wrote:
>
> Looks like OSPF crashes right after router receives following LSA:
>
> LS age 3600 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link
> State ID 10.1.0.13 Advertising Router 10.0.0.1 LS sequence number
> 0x80000001 LS checksum 0xdc45 length 32
> Link State Acknowledgement Packet:
>         Version 2
>         Type 5
>         Router ID 10.1.0.2
>         Area ID 0.0.0.0
>         Auth Type 0
>
>         LS age 3600 Options  0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x=
2
> Link State ID 10.1.0.13 Advertising Router 10.0.0.1 LS sequence number
> 0x80000001 LS checksum 0xdc45 length 32
> [ 2005/12/07 13:26:52  FATAL xorp_ospfv2:4320 OSPF +465 routing_table.cc
> add_entry ] Assertion (0 =3D=3D _entries.count(area)) failed
>
> Maybe related to some of the other outstanding OSPF bugs.
>
> Tim:>
>
> On 12/5/05, Tim Durack <tdurack@gmail.com> wrote:
> >
> > On 12/5/05, Mike Horn <caddisconsulting@yahoo.com> wrote:
> > >
> > >  Hi Tim,
> > >
> > > Take a look at XORP bug 383, your issue looks similar but is for
> > > different LSA type, however I think it may have the same root cause. =
 Before
> > > the crash did you lose your neighbor adjacency and then reestablish i=
t?  Atanu,
> > > should a new bug be entered or do you think 383 covers this issue as =
well?
> > >
> >
> > The adjacency had just been brought up, after starting xorp_rtrmgr and
> > loading the config.
> > It seems to happen randomly to all four of the routers in my lab setup.
> >
> > Also Tim, there are a number of known issues with the current OSPF code=
,
> > > it might be worth quickly perusing the bug database to see what you m=
ight
> > > run into in a test environment.
> > >
> >
> > I know XORP is still very much beta, but it shows a lot of promise.
> > I'm using it in a Xen laptop based router lab, to teach and test variou=
s
> > routing protocols and configurations.
> >
> >  -mike
> > >
> > >  ------------------------------
> > > *From:* xorp-hackers-admin@icir.org [mailto:
> > > xorp-hackers-admin@icir.org] *On Behalf Of *Tim Durack
> > > *Sent:* Monday, December 05, 2005 11:26 AM
> > > *To:* xorp-users@xorp.org; xorp-hackers@xorp.org
> > > *Subject:* [Xorp-hackers] OSPF Failures
> > >
> > > I have created a basic network of four XORP routers, meshed together
> > > (gre tunnels built outside of XORP.)
> > > All the adjacencies come up, but OSPF is randomly dying with the
> > > following error:
> > >
> > > [ 2005/12/05 13:08:23  FATAL xorp_ospfv2:4327 OSPF +465
> > > routing_table.cc add_entry ] Assertion (0 =3D=3D _entries.count(area)=
) failed
> > > [ 2005/12/05 13:08:23  INFO xorp_rtrmgr:4322 RTRMGR +668
> > > module_manager.cc killed ] Module abnormally killed: ospf4
> > > [ 2005/12/05 13:08:23  WARNING xorp_rtrmgr:4322 XrlFinderTarget +406
> > > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handlin=
g
> > > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command fai=
led
> > > Target "ospfv2" does not exist or is not enabled.
> > > [ 2005/12/05 13:08:23 INFO xorp_rib RIB ] Received death event for
> > > protocol ospfv2 shutting down -------
> > > OriginTable: ospf
> > > IGP
> > > next table =3D Redist:ospf
> > > [ 2005/12/05 13:08:23 INFO xorp_rib RIB ] Received death event for
> > > protocol ospfv2 shutting down -------
> > > OriginTable: ospf
> > > IGP
> > > next table =3D Redist:ospf
> > > [ 2005/12/05 13:08:23 INFO xorp_rib RIB ] Received death event for
> > > protocol ospfv2 shutting down -------
> > > OriginTable: ospf
> > > IGP
> > > next table =3D Redist:ospf
> > > [ 2005/12/05 13:08:23 INFO xorp_rib RIB ] Received death event for
> > > protocol ospfv2 shutting down -------
> > > OriginTable: ospf
> > > IGP
> > > next table =3D Redist:ospf
> > >
> > >
> > > Not sure why this is happening. I have attached the configs in case i=
t
> > > helps.
> > >
> > > Tim:>
> > >
> > >
> >
>

------=_Part_19534_14780805.1134613834185
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I &quot;fixed&quot; the problem by commenting out ospf/routing_table.cc lin=
e 465:<br>
<br>
&nbsp;&nbsp;&nbsp; // xxx XLOG_ASSERT(0 =3D=3D _entries.count(area));<br>
<br>
This might not be the correct way to fix things, but it works for me...<br>
<br>
Tim:&gt;<br>
<br><br><div><span class=3D"gmail_quote">On 12/7/05, <b class=3D"gmail_send=
ername">Tim Durack</b> &lt;<a href=3D"mailto:tdurack@gmail.com">tdurack@gma=
il.com</a>&gt; wrote:</span><blockquote class=3D"gmail_quote" style=3D"bord=
er-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-l=
eft: 1ex;">
Looks like OSPF crashes right after router receives following LSA:<br>
<br>
LS age 3600 Options&nbsp; 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2
Link State ID <a href=3D"http://10.1.0.13" target=3D"_blank" onclick=3D"ret=
urn top.js.OpenExtLink(window,event,this)">10.1.0.13</a> Advertising Router=
 <a href=3D"http://10.0.0.1" target=3D"_blank" onclick=3D"return top.js.Ope=
nExtLink(window,event,this)">
10.0.0.1</a> LS sequence number
0x80000001 LS checksum 0xdc45 length 32<br>
Link State Acknowledgement Packet:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Version 2<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type 5<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Router ID <a href=3D"http://10.1=
.0.2" target=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,t=
his)">10.1.0.2</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Area ID <a href=3D"http://0.0.0.=
0" target=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,this=
)">0.0.0.0</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Auth Type 0<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LS age 3600 Options&nbsp;
0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x2 Link State ID <a href=3D"http=
://10.1.0.13" target=3D"_blank" onclick=3D"return top.js.OpenExtLink(window=
,event,this)">10.1.0.13</a>
Advertising Router <a href=3D"http://10.0.0.1" target=3D"_blank" onclick=3D=
"return top.js.OpenExtLink(window,event,this)">10.0.0.1</a> LS sequence num=
ber 0x80000001 LS checksum
0xdc45 length 32<br>
[ 2005/12/07 13:26:52&nbsp; FATAL xorp_ospfv2:4320 OSPF +465
routing_table.cc add_entry ] Assertion (0 =3D=3D _entries.count(area))
failed<br><br>
Maybe related to some of the other outstanding OSPF bugs.<br><span class=3D=
"sg">
<br>
Tim:&gt;</span><div><span class=3D"e" id=3D"q_1080732c5ac47524_2"><br>
<br><div><span class=3D"gmail_quote">On 12/5/05, <b class=3D"gmail_senderna=
me">Tim Durack</b> &lt;<a href=3D"mailto:tdurack@gmail.com" target=3D"_blan=
k" onclick=3D"return top.js.OpenExtLink(window,event,this)">tdurack@gmail.c=
om</a>
&gt; wrote:</span><blockquote class=3D"gmail_quote" style=3D"border-left: 1=
px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"=
>
<span>On 12/5/05, <b class=3D"gmail_sendername">Mike Horn</b> &lt;<a href=
=3D"mailto:caddisconsulting@yahoo.com" target=3D"_blank" onclick=3D"return =
top.js.OpenExtLink(window,event,this)">caddisconsulting@yahoo.com</a>&gt; w=
rote:
</span><div><span><span class=3D"gmail_quote"></span><blockquote class=3D"g=
mail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
 0pt 0pt 0.8ex; padding-left: 1ex;">
<span>




<div align=3D"left" dir=3D"ltr"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Hi Tim,</font></span></div>
<div align=3D"left" dir=3D"ltr"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2"></font></span>&nbsp;</div>
<div align=3D"left" dir=3D"ltr"><span><font color=3D"#0000ff" face=3D"Arial=
" size=3D"2">Take a look at XORP bug 383, your issue looks similar but=20
is for different LSA type, however I think it may have the same root=20
cause.&nbsp; Before the crash did you lose your neighbor adjacency and then=
=20
reestablish it?&nbsp; </font></span><span><font color=3D"#0000ff" face=3D"A=
rial" size=3D"2">Atanu, should a new bug be entered or do you=20
think 383 covers this issue as well?</font></span></div></span></blockquote=
></span><div><br>
The adjacency had just been brought up, after starting xorp_rtrmgr and load=
ing the config.<br>
It seems to happen randomly to all four of the routers in my lab setup.<br>
</div><span><br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px=
 solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><=
span><div align=3D"left" dir=3D"ltr"><span><font color=3D"#0000ff" face=3D"=
Arial" size=3D"2">


Also Tim, there are a number of known issues with the=20
current OSPF code, it might be worth quickly perusing the bug database to s=
ee=20
what you might run into in a test environment.</font></span></div></span></=
blockquote></span><div><br>
I know XORP is still very much beta, but it shows a lot of promise.<br>
I'm using it in a Xen laptop based router lab, to teach and test various ro=
uting protocols and configurations.<br>
</div><div><span><br><blockquote class=3D"gmail_quote" style=3D"border-left=
: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1e=
x;"><span><div align=3D"left" dir=3D"ltr">
<span><font color=3D"#0000ff" face=3D"Arial" size=3D"2">
-mike</font></span></div><br>
<div align=3D"left" dir=3D"ltr" lang=3D"en-us">
<hr>
<font face=3D"Tahoma" size=3D"2"><b>From:</b> <a href=3D"mailto:xorp-hacker=
s-admin@icir.org" target=3D"_blank" onclick=3D"return top.js.OpenExtLink(wi=
ndow,event,this)">xorp-hackers-admin@icir.org</a>=20
[mailto:<a href=3D"mailto:xorp-hackers-admin@icir.org" target=3D"_blank" on=
click=3D"return top.js.OpenExtLink(window,event,this)">xorp-hackers-admin@i=
cir.org</a>] <b>On Behalf Of </b>Tim=20
Durack<br><b>Sent:</b> Monday, December 05, 2005 11:26 AM<br><b>To:</b>=20
<a href=3D"mailto:xorp-users@xorp.org" target=3D"_blank" onclick=3D"return =
top.js.OpenExtLink(window,event,this)">xorp-users@xorp.org</a>; <a href=3D"=
mailto:xorp-hackers@xorp.org" target=3D"_blank" onclick=3D"return top.js.Op=
enExtLink(window,event,this)">


xorp-hackers@xorp.org</a><br><b>Subject:</b> [Xorp-hackers]=20
OSPF Failures<br></font><br></div>
<div></div></span><div><span>I have created a basic network of four XORP ro=
uters, meshed together=20
(gre tunnels built outside of XORP.)<br>All the adjacencies come up, but OS=
PF is=20
randomly dying with the following error:<br><br>[ 2005/12/05 13:08:23&nbsp;=
=20
FATAL xorp_ospfv2:4327 OSPF +465 routing_table.cc add_entry ] Assertion (0 =
=3D=3D=20
_entries.count(area)) failed<br>[ 2005/12/05 13:08:23&nbsp; INFO=20
xorp_rtrmgr:4322 RTRMGR +668 module_manager.cc killed ] Module abnormally=
=20
killed: ospf4<br>[ 2005/12/05 13:08:23&nbsp; WARNING xorp_rtrmgr:4322=20
XrlFinderTarget +406 ../xrl/targets/finder_base.cc handle_finder_0_2_resolv=
e_xrl=20
] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Comman=
d=20
failed Target &quot;ospfv2&quot; does not exist or is not enabled.<br>[ 200=
5/12/05=20
13:08:23 INFO xorp_rib RIB ] Received death event for protocol ospfv2 shutt=
ing=20
down -------<br>OriginTable: ospf<br>IGP<br>next table =3D Redist:ospf<br>[=
=20
2005/12/05 13:08:23 INFO xorp_rib RIB ] Received death event for protocol o=
spfv2=20
shutting down -------<br>OriginTable: ospf<br>IGP<br>next table =3D=20
Redist:ospf<br>[ 2005/12/05 13:08:23 INFO xorp_rib RIB ] Received death eve=
nt=20
for protocol ospfv2 shutting down -------<br>OriginTable: ospf<br>IGP<br>ne=
xt=20
table =3D Redist:ospf<br>[ 2005/12/05 13:08:23 INFO xorp_rib RIB ] Received=
 death=20
event for protocol ospfv2 shutting down -------<br>OriginTable:=20
ospf<br>IGP<br>next table =3D Redist:ospf<br><br><br>Not sure why this is=
=20
happening. I have attached the configs in case it=20
helps.<br><br>Tim:&gt;<br><br>

</span></div></blockquote></span></div></div><br>

</blockquote></div><br>

</span></div></blockquote></div><br>

------=_Part_19534_14780805.1134613834185--