Re: ospfd not resyncing
On Wed, Apr 09, 2008 at 11:41:51AM +0100, Paul Civati wrote: In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Claudio Jeker) writes: Please send some more infos. What version are you useing (did you test -current). Please show the config and necessary ospfctl output. The last time I have issues like this was some time ago with point-to-point links and that got fixed some time ago. There seems something in common with your setups that others usually don't have. 4.2-RELEASE - not tried -current because this is for a production system. Hmm. could you try a -current ospfd. I have a feeling that rev. 1.64 of rde_spf.c may help you: Change the way nexthops are calculated on the root level. Instead of looking from the target back and trying to figure the nexthop out, the link is searched in the interface list and the info from the matiching interface is used. This should solve the nexthop issues with setups having multiple point-to-point links between two routers as reported on misc@ some time ago. tested and OK norby@ Btw. the change should apply to a 4.2 ospfd, just download the diff from: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/ospfd/rde_spf.c.diff?r1=1.63r2=1.64 -- :wq Claudio
Re: ospfd not resyncing
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Claudio Jeker) writes:
Please send some more infos. What version are you useing (did you test
-current). Please show the config and necessary ospfctl output. The last
time I have issues like this was some time ago with point-to-point links
and that got fixed some time ago. There seems something in common with
your setups that others usually don't have.
4.2-RELEASE - not tried -current because this is for a production
system.
Next time it happens I will try and grab copies of the database.
Our config is really simple.. note that em3 has lots of vlan
and carp interfaces associated with it.
This ospfd talks to the loopback interface on a JunOS box.
auth-type crypt
auth-md n xxx
auth-md-keyid n
redistribute connected set metric 50
area 0.0.0.0 {
interface em2
interface em3 { passive }
interface em1 { passive }
}
-Paul-
Re: ospfd not resyncing
Linden Varley [EMAIL PROTECTED] wrote: Bringing up an old-topic here, but just letting everyone know I have the exact same problem. It occurs quite often. Surely we can't be the only two people seeing this issue? It's quite fundamental to ospfd working properly.. -Paul-
Re: ospfd not resyncing
On Wed, Apr 09, 2008 at 09:53:58AM +0100, Paul Civati wrote: Linden Varley [EMAIL PROTECTED] wrote: Bringing up an old-topic here, but just letting everyone know I have the exact same problem. It occurs quite often. Surely we can't be the only two people seeing this issue? It's quite fundamental to ospfd working properly.. Please send some more infos. What version are you useing (did you test -current). Please show the config and necessary ospfctl output. The last time I have issues like this was some time ago with point-to-point links and that got fixed some time ago. There seems something in common with your setups that others usually don't have. -- :wq Claudio
Re: ospfd not resyncing
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Paul Civati) writes: This ospfd talks to the loopback interface on a JunOS box. For sake of clarity, over a normal ethernet interface, no PtP. -Paul-
Re: ospfd not resyncing
OpenBSD 4.2, with three routers running ospfd. Two links out of one
router connecting to the other two routers. (em1 and em3 in this case)
ospfd.conf
===
# macros
password=xxx
# global configuration
router-id 0.0.0.1
redistribute connected
redistribute static
redistribute default
auth-key $password
auth-type simple
hello-interval 5
# areas
area 0.0.0.5 {
interface em0 {
passive
}
interface em1 {
}
interface em2 {
passive
}
interface em3 {
}
interface em4 {
passive
}
interface em5 {
passive
}
}
==
router1# ospfctl show neighbor
ID Pri StateDeadTime Address Iface Uptime
0.0.0.3 1 FULL/DR 00:00:37 192.168.253.3 em3 3d04h09m
0.0.0.2 1 FULL/DR 00:00:37 192.168.255.2 em1 3d04h09m
router2# ospfctl show neighbor
ID Pri StateDeadTime Address Iface Uptime
0.0.0.3 1 FULL/DR 00:00:35 192.168.254.3 em3 3d04h19m
0.0.0.1 1 FULL/BCKUP 00:00:35 192.168.255.1 em1 3d04h11m
router3# ospfctl show neighbor
ID Pri StateDeadTime Address Iface Uptime
0.0.0.2 1 FULL/BCKUP 00:00:36 192.168.254.2 em3 3d04h19m
0.0.0.1 1 FULL/BCKUP 00:00:36 192.168.253.1 em1 3d04h10m
Not sure what other information would be helpful. Thought I might have
to assign a metric to each interface but I don't think that will do
anything as each interface is for a route to a separate network.
Cheers
Claudio Jeker wrote:
On Wed, Apr 09, 2008 at 09:53:58AM +0100, Paul Civati wrote:
Linden Varley [EMAIL PROTECTED] wrote:
Bringing up an old-topic here, but just letting everyone know
I have the exact same problem. It occurs quite often.
Surely we can't be the only two people seeing this issue?
It's quite fundamental to ospfd working properly..
Please send some more infos. What version are you useing (did you test
-current). Please show the config and necessary ospfctl output. The last
time I have issues like this was some time ago with point-to-point links
and that got fixed some time ago. There seems something in common with
your setups that others usually don't have.
Re: ospfd not resyncing
Bringing up an old-topic here, but just letting everyone know I have the exact same problem. It occurs quite often. One of my links goes down, the routes change, but when the link comes back up the routes don't go back to the default lower-cost one and I have to restart ospfd in order to force it. It seems like a simple issue but wondered why it happens. I'm glad its not just me! Paul Civati wrote: I have a fairly simple set-up, where I have ospfd announcing a few routes to a Juniper router. Twice now, when the Juniper has been unreachable and has then come back on-line, the ospf routes have not reconverged on the Juniper end. It has taken a restart of the OSPF on the Juniper to resync the routes.. I've not tried restarting the ospfd's on the OpenBSD end but I presume that would also solve the issue. I suppose it's plausible this is a JunOS bug, and I'll look into that, but wondered if this is a known issue? OpenBSD/ospfd 4.2 RELEASE. -Paul-
ospfd not resyncing
I have a fairly simple set-up, where I have ospfd announcing a few routes to a Juniper router. Twice now, when the Juniper has been unreachable and has then come back on-line, the ospf routes have not reconverged on the Juniper end. It has taken a restart of the OSPF on the Juniper to resync the routes.. I've not tried restarting the ospfd's on the OpenBSD end but I presume that would also solve the issue. I suppose it's plausible this is a JunOS bug, and I'll look into that, but wondered if this is a known issue? OpenBSD/ospfd 4.2 RELEASE. -Paul-
