[Xorp-hackers] OSPF Failures

Mike Horn caddisconsulting@yahoo.com
Mon, 5 Dec 2005 12:00:30 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_02A3_01C5F993.80289860
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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 it?  Atanu, should
a new bug be entered or do you think 383 covers this issue as well?
 
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 might run
into in a test environment.
 
-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 == _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 ] Handling
method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed
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 = 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 = 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 = 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 = Redist:ospf


Not sure why this is happening. I have attached the configs in case it
helps.

Tim:>



------=_NextPart_000_02A3_01C5F993.80289860
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Tim,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>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 =
class=3D667315318-05122005><FONT=20
face=3DArial color=3D#0000ff size=3D2>Atanu, should a new bug be entered =
or do you=20
think 383 covers this issue as well?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>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 see=20
what you might run into in a test environment.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D667315318-05122005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>-mike</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> xorp-hackers-admin@icir.org=20
[mailto:xorp-hackers-admin@icir.org] <B>On Behalf Of </B>Tim=20
Durack<BR><B>Sent:</B> Monday, December 05, 2005 11:26 AM<BR><B>To:</B>=20
xorp-users@xorp.org; xorp-hackers@xorp.org<BR><B>Subject:</B> =
[Xorp-hackers]=20
OSPF Failures<BR></FONT><BR></DIV>
<DIV></DIV>I have created a basic network of four XORP routers, meshed =
together=20
(gre tunnels built outside of XORP.)<BR>All the adjacencies come up, but =
OSPF 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_resolve_xrl=20
] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 =
Command=20
failed Target "ospfv2" does not exist or is not enabled.<BR>[ 2005/12/05 =

13:08:23 INFO xorp_rib RIB ] Received death event for protocol ospfv2 =
shutting=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 ospfv2=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 =
event=20
for protocol ospfv2 shutting down -------<BR>OriginTable: =
ospf<BR>IGP<BR>next=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></BODY></HTML>

------=_NextPart_000_02A3_01C5F993.80289860--