[quagga-users 10067] 0.99.10 ospf neighbor stuck in state loading
sclark at netwolves.com
Tue Oct 28 14:18:23 GMT 2008
Is there some way to determine what is left in the "Link state request list" when quagga
hangs in the Loading state?
We have a number, greater than 50, remote sites connected back to a two cisco systems on
different ds3 from different providers
that are running ospf over gre/vpn. We are having trouble with one site where quagga
is getting stuck in :
Neighbor ID Pri State Dead Time Address Interface RXmtL RqstL DBsmL
172.16.10.45 1 Loading/DROther 30.524s 10.255.13.213 gre1:10.255.13.214 0 2 0
172.16.10.47 1 Loading/DROther 34.442s 10.255.14.213 gre2:10.255.14.214 0 2 0
The cisco systems show the adjacency as full. My question is how to I go about debugging this problem?
I understand that the quagga side is missing some part of its database that is suppose to be sent
from the cisco, if I do a 'sh ip os database' I see a lot of the database, how do I tell what quagga is
We were first using 0.99.6 and had the same problem.
Quagga-users mailing list
Quagga-users at lists.quagga.net
More information about the Quagga-users