[Xorp-users] Problems with Linux kernel and OSPF ???

[Aidan Walton]

Hi All,
I am using xorp in a production environment, admittedly a small one. I
operate a local WISP and xorp is running on my wireless nodes. I have a
very simple configuration and really I could probably get away with
static routing throughout the entire network, but I wanted to try xorp
and see just how stable it was. However as I expand the network I am
having second thoughts. It is not good at all when a network goes up in
smoke and I can't explain why or predict when and what the causes are.

The network has been in operation 24x7 for around 9 months. I am running
on a Linux kernel 2.6.18-4 and for the vast majority of the time I have
no issues. However now for the fourth time I see the same problem:

Suddenly the Linux kernel and the xorp rib become detached. Normally all
routes in the kernel match those that xorp is generating, receiving and
electing as active. I am running OSPF and the neighbour states remain
'full' throughout but if I am not mistaken I see ospf hellos only in one
direction (i.e nothing being transmitted from the router I suspect). The
lsdb of OSPF on the suspect and adjacent routers contain all the routes
but they are aging out slowly on the adjacent router. When I look at the
kernel routes those from OSPF have already vanished.

I can see the ospf process running on the offending router? and again I
can see the ospf lsdb intact and correct. When I restart xorp the system
recovers and the routes appear in the kernel again. I suspect a problem
with ospf. I tried enabling traceoptions on the ospf process, but in
fact I needed to restart all the xorp processes before this actually
became active. I now have this running so if/when it happens again I
might be able to offer some more information.

Does anyone have any experience of ospf begin unstable? any suggestions
how I might more effectively capture some logs from this event. I do not
see any options for logging the fea process. Is there anything I can
enable to help diagnose the issue?

Many thanks, and of course cheers for the code in the first place.
Aidan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071204/167fff1a/attachment.html