On Fri, Sep 05, 2008 at 02:59:47PM -0700, andrew fresh wrote:
> The problem I am seeing is that if I don't specify a router-id in
> ospfd.conf, then if the highest IP on a peer router changes the automatic
> Router ID, the session fails to start with a "failed to form adjacency with
> <old ID>" error.

I see this from some fallout of a bug I discovered:

/etc/ospfd.conf:
    router-id 34.193.28.3
    area 0.0.0.0 {
            interface em3 {
            }
    }

int em3 has 4 (inclusive) neighbours:

ID              Pri State        DeadTime Address         Iface Uptime
228.94.64.2     1   FULL/DR      00:00:37 200.89.217.12   em3 1d12h24m
34.193.28.2     1   FULL/BCKUP   00:00:35 200.89.217.2    em3 1d12h24m
200.89.217.37   1   2-WAY/OTHER  00:00:37 200.89.217.11   em3       -

here is "200.89.217.37":

!
router ospf 10
 router-id 228.94.64.1
 log-adjacency-changes
 redistribute connected subnets
 redistribute static subnets
 passive-interface GigabitEthernet0/0.200
 passive-interface GigabitEthernet0/1.3
 passive-interface GigabitEthernet0/1.102
 passive-interface GigabitEthernet0/1.255
 network 200.89.217.8 0.0.0.7 area 0
 network 200.89.217.32 0.0.0.7 area 0
 network 200.89.219.0 0.0.0.255 area 0
 network 228.94.65.0 0.0.0.255 area 0
 network 228.94.64.0 0.0.15.255 area 0
 network 101.146.142.0 0.0.0.127 area 0
 network 101.146.142.128 0.0.0.127 area 0
 network 34.193.28.0 0.0.3.255 area 0
 default-information originate always
!

200.89.217.37 is now 228.94.64.1 and I get this in the logs (after I
`clear ip ospf proc'):

Nov 19 12:56:33 hadrian ospfd[26460]: nbr_adj_timer: failed to form adjacency 
with 200.89.217.37

however if I change another router-id within the mesh, I can hang the
entire OS:

rtfree: 0xd99fd004 not freed (neg refs)
rtfree: 0xd99fd004 not freed (neg refs)
rtfree: 0xd99fd004 not freed (neg refs)
rtfree: 0xd99fd004 not freed (neg refs)

It needs a hard reset.

A limitation of my routes?
13:08 hadrian:~# ospfctl sh f|wc -l
      99 
13:08 hadrian:~# 

> 
> Here is a description of how to repeat the problem as well as log messages.
> If there is any more information I should gather, let me know.

You should send-pr.

In fact I will now.

-- 
 020 7729 4797
 http://blog.playlouder.com/

Reply via email to