Jon Simola wrote:
quoted text
> On Fri, Aug 8, 2008 at 2:17 AM, clifford bailey
> <bailey.clifford@googlemail.com> wrote:
>
>   
>> Finally my ospf config:
>>     
>
>   
>> hello-interval 1
>> router-dead-time 2
>>     
>
> Those timings might be a little agressive for VMs to handle, as
> missing a single hello
> could cause all sorts of excitement with the default SPF timer values.
>
>   
Thanks for that Jon. I tried dropping to 5 and 10, instead of 1 and 2 
also swapped to real machines rather than vms, and am still getting odd 
behaviour. I removed a link, added it back in, and now although traffic 
is being passed, one interface is sticking in the EXSTA/OTHER state:

root@firewall1:/root>ospfctl show neigh
ID              Pri State        DeadTime Address         Iface     Uptime
10.0.0.159    1   2-WAY/OTHER  00:00:06 10.0.0.214    em7       -  
10.0.0.248    128 FULL/BCKUP   00:00:09 10.0.0.209    em7       02:07:24
10.0.0.249    128 FULL/DR      00:00:06 10.0.0.210    em7       02:07:24
10.0.0.157    128 FULL/OTHER   00:00:08 10.0.0.42     em0       02:07:12
10.0.0.156    128 FULL/OTHER   00:00:06 10.0.0.41     em0       02:07:12
10.0.0.159    1   EXSTA/OTHER  00:00:06 10.0.0.44     em0       -  


Messages file from the time:

Aug 27 16:02:24 firewall01 ospfd[4241]: interface em0 up
Aug 27 16:02:27 firewall01 ospfd[4241]: interface em7 up
Aug 27 16:03:44 firewall01 ospfd[4241]: nbr_adj_timer: failed to form 
adjacency wi
th 10.0.0.159
Aug 27 16:04:44 firewall01 ospfd[4241]: nbr_adj_timer: failed to form 
adjacency wi
th 10.0.0.159

Any other ideas? Could it be that the relationship between router-dead 
time and hello-interval is wrong? The default is 4 to 1, I've changed to 
2 to 1, could that be a problem?
Thanks,


Cliff.