OSPF negotiation delay

From: Bell, Mark (Houston) (m.bell@xxxxxxxxxx)
Date: Tue Oct 03 2000 - 17:34:51 GMT-3


   
When I configure OSPF over a frame relay cloud using OSPF "non-broadcast"
interfaces, it takes a long time for OSPF to form adjacencies. I enabled
"log-adjacency-changes" under the OSPF process at the hub site and got the
output shown in the attachment. As you can see, there is a very long delay
between the 2WAY and EXSTART states. I have been told by two knowledgeable
engineers that it should not take this long for the adjacencies to form.

During this time, there is absolutely nothing going on relating to OSPF
because I have done a "debug ip ospf packet" on r5 and saw nothing. R5 is
the hub router and static neighbors are defined. The remote routers have
"ip ospf priority 0" configured on their WAN interfaces. Static frame relay
map statements with the broadcast parameter are defined on all three
routers. I configured OSPF on the Ethernet interface on this router and the
other router on the same segment. The adjacency across the Ethernet
interface forms in a matter of seconds. What would cause the adjacency over
the WAN interface to take so long to form?

----------------------------------------------
Kenneth Mark Bell, CCNP, NNCSE
Network Engineer II m.bell@wilcom.com
Williams Communications Solutions
t: (713) 307-7254 p: (713) 912-2276

r5#clear ip ospf proc
Reset ALL OSPF processes? [no]: yes
r5#
*Mar 1 02:06:57 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from FULL to 2WAY, Reset Adjacency
*Mar 1 02:06:57 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from FULL to 2WAY, Reset Adjacency
*Mar 1 02:06:57 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from 2WAY to DOWN, Neighbor Down
*Mar 1 02:06:57 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 0.0.0.0 on Serial0/0.1 f
rom DOWN to ATTEMPT, NBMA Start
*Mar 1 02:06:57 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from 2WAY to DOWN, Neighbor Down
*Mar 1 02:06:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 0.0.0.0 on Serial0/0.1 f
rom DOWN to ATTEMPT, NBMA Start
*Mar 1 02:06:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 0.0.0.0 on Serial0/0.1 f
rom ATTEMPT to ATTEMPT, Start
*Mar 1 02:06:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 0.0.0.0 on Serial0/0.1 f
rom ATTEMPT to ATTEMPT, Start
*Mar 1 02:06:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 0.0.0.0 on Serial0/0.1 f
rom ATTEMPT to ATTEMPT, Start
*Mar 1 02:06:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 0.0.0.0 on Serial0/0.1 f
rom ATTEMPT to ATTEMPT, Start
*Mar 1 02:06:59 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from ATTEMPT to INIT, Received Hello
*Mar 1 02:06:59 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from INIT to 2WAY, 2-Way Received
*Mar 1 02:07:02 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from ATTEMPT to INIT, Received Hello
*Mar 1 02:07:02 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from INIT to 2WAY, 2-Way Received
*Mar 1 02:08:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from 2WAY to EXSTART, AdjOK?
*Mar 1 02:08:58 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from 2WAY to EXSTART, AdjOK?
*Mar 1 02:09:18 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from EXSTART to EXCHANGE, Negotiation Done
*Mar 1 02:09:18 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from EXSTART to EXCHANGE, Negotiation Done
*Mar 1 02:09:18 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from EXCHANGE to LOADING, Exchange Done
*Mar 1 02:09:18 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.30.97 on Serial0
/0.1 from LOADING to FULL, Loading Done
*Mar 1 02:09:18 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from EXCHANGE to LOADING, Exchange Done
*Mar 1 02:09:23 UTC: %OSPF-5-ADJCHG: Process 100, Nbr 172.168.100.6 on Serial0
/0.1 from LOADING to FULL, Loading Done



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:23 GMT-3