[quagga-users 8037] Re: Quagga / ospfv2 (version 0.99.6) - Reduceconvergence time

Laverdiere,Phil Phil_Laverdiere at securecomputing.com
Thu Feb 15 13:43:03 GMT 2007

Given that the dr/bdr election occurs quickly, take a look at a packet trace
for the exchange.  Look at the database exchange packets as well as the lsa
refresh and lsupdate packets.  Perhaps something is not quite right causing
a retransmit or two.


  -----Original Message-----
From: quagga-users-bounces at lists.quagga.net
[mailto:quagga-users-bounces at lists.quagga.net] On Behalf Of Preben Myrvoll
Sent: Thursday, February 15, 2007 5:23 AM
To: Gobbledegeek
Cc: quagga-users at lists.quagga.net
Subject: [quagga-users 8035] Re: Quagga / ospfv2 (version 0.99.6) -
Reduceconvergence time

Hi -

I'm still using Quagga 0.99.6 :-)

* changing to - "timers throttle spf 10 100 5000" - Did not do anything 
(and I've tried various options spf like "100 100 1000").
* Using link-detect does not alter anything (as you pointed out)
* Seting up point-to-point on interfaces in the 11.0.x.x made the ping 
go through after 10 seconds (for both) ( and yes i saw that there was no 
DR/BDR election ;-). With this setup I see that the routers now wait 10 
seconds before sending the second Link State Update (and thus the ping 
in both directions go through after 10+ seconds)

Then ting is - The actual DR - BDR election happens quite fast (with 1 - 
2 seconds). The dead-intervall is still 2 and the hello-interval is 1. 
But the actual LSA exchange / and LSA refresh continues after this, and 
it seems like its the LSA Update/refresh that actually causes the - 
after 5 seconds - DR to be able to ping the BDR, and then 5 seconds 
later the BDR can ping the DR (I'm still talking about pinging the 
"outer addresses" - and with out the point-to-pont) <--- eth1| OSPF Router and Machine A| eth0 ---> 
<--- eth1| OSPF Router and Machine B| eth0 --->
- Machine A have ip on eht1 and on eth0
- Machine B has ip on eth0 and on eth0

BTW: What did you mean by:
( Idon't see a point in making RouterDeadInterval less than dead time).

Thanks again

More information about the Quagga-users mailing list