[quagga-dev 4185] Re: possible ospfd bug: in state ExStart with routers that are neither DR nor BDR

Andrew J. Schorr aschorr at telemetry-investments.com
Thu Jun 29 14:33:29 BST 2006


On Thu, Jun 29, 2006 at 07:54:10AM +0100, Paul Jakma wrote:
> In the absolute worst case, as a hack^defensive-programming, we can 
> set a timer on entering ExStart to generate an event to clear it if 
> it doesn't progress after some time, e.g. AdjOK? (which afaict would 
> be enough for your case for ti77 to set the 76 and 75 adjacencies to 
> 2-Way).

Yes, I guess that should work.

> What about ti77's view of what happened?

Yes, here's the log from ti77:

First, when the T3 bridge goes down at 19:14:27

2006/06/28 19:14:27 OSPF: AdjChg: Nbr 192.168.11.76 on eth0.19:192.168.167.77: 2-Way -> Down
2006/06/28 19:14:27 OSPF: ospfTrapNbrStateChange trap sent: 192.168.167.76 now Down/DROther
2006/06/28 19:14:27 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:14:27 OSPF: DR-Election[1st]: DR     192.168.167.79
2006/06/28 19:14:27 OSPF: AdjChg: Nbr 192.168.11.74 on eth0.19:192.168.167.77: 2-Way -> Down
2006/06/28 19:14:27 OSPF: ospfTrapNbrStateChange trap sent: 192.168.167.74 now Down/DROther
2006/06/28 19:14:27 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:14:27 OSPF: DR-Election[1st]: DR     192.168.167.79
2006/06/28 19:14:27 OSPF: AdjChg: Nbr 192.168.11.75 on eth0.19:192.168.167.77: 2-Way -> Down
2006/06/28 19:14:27 OSPF: ospfTrapNbrStateChange trap sent: 192.168.167.75 now Down/DROther
2006/06/28 19:14:27 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:14:27 OSPF: DR-Election[1st]: DR     192.168.167.79

And then the T3 comes back up:

2006/06/28 19:15:01 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:15:01 OSPF: DR-Election[1st]: DR     192.168.167.79
2006/06/28 19:15:01 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:15:01 OSPF: DR-Election[1st]: DR     192.168.167.79
2006/06/28 19:15:01 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:15:01 OSPF: DR-Election[1st]: DR     192.168.167.79
2006/06/28 19:15:01 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:15:01 OSPF: DR-Election[1st]: DR     192.168.167.79
2006/06/28 19:15:01 OSPF: Packet[DD]: Neighbor 192.168.11.75: Initial DBD from Slave, ignoring.
2006/06/28 19:15:01 OSPF: ospfTrapNbrStateChange trap sent: 192.168.167.74 now 2-Way/DROther
2006/06/28 19:15:01 OSPF: DR-Election[1st]: Backup 192.168.167.78
2006/06/28 19:15:01 OSPF: DR-Election[1st]: DR     192.168.167.79

I don't see anything helpful here, do you?  Except perhaps that
message about Initial DBD from Slave...

Thanks for your help,
Andy

P.S. I'll try to look at that maxage-flood stuff later, but I got caught
up with other quagga issues yesterday. :-)

P.P.S. Any thoughts on the log-adjacency-changes patch?  Would it be
OK to commit that?  Or should it wait until after 1.0?



More information about the Quagga-dev mailing list