Re: OSPF neighbor problem

From: Hansang Bae (hbae@xxxxxxxxxx)
Date: Wed Jun 05 2002 - 22:27:01 GMT-3


   
At 12:44 AM 6/5/2002 -0700, Lab Candidate wrote:
>two routers r3 and r5 won't form ospf neighbors over ethernet intf's.
>it's stuck in exstart state. could anyone please help with any advice?
>
>r3-e0/0----------f0/0-r5
>
>r3:
>
>interface Ethernet0/0
> ip address 170.10.54.1 255.255.255.0
> full-duplex
>!
>router ospf 9
> router-id 3.3.3.3
> log-adjacency-changes
> area 2 virtual-link 5.5.5.5
> network 170.10.50.0 0.0.0.255 area 2
> network 170.10.54.0 0.0.0.255 area 2
> network 170.10.80.0 0.0.0.255 area 0
> neighbor 170.10.80.4
> neighbor 170.10.80.2
>!
>r3#sh ip os n
>
>Neighbor ID Pri State Dead Time Address Interface
>170.10.30.1 0 FULL/DROTHER 00:01:38 170.10.80.4 Serial0/1
>198.133.219.25 0 FULL/DROTHER 00:01:45 170.10.80.2 Serial0/1
>5.5.5.5 1 EXSTART/DR 00:00:37 170.10.54.2 Ethernet0/0
>r3#
>
>
>r5:
>
>interface FastEthernet0/0
> ip address 170.10.54.2 255.255.255.0
> duplex auto
> speed auto
>
>router ospf 9
> router-id 5.5.5.5
> log-adjacency-changes
> area 2 virtual-link 3.3.3.3
> network 170.10.40.0 0.0.0.255 area 3
> network 170.10.54.0 0.0.0.255 area 2
>!
>
>r5#sh ip os n
>
>Neighbor ID Pri State Dead Time Address Interface
>3.3.3.3 1 EXSTART/BDR 00:00:35 170.10.54.1 FastEthernet
0/0
>r5#
>
>
>==============debug=================
>
>r3#
>
>00:22:38: OSPF: Send DBD to 5.5.5.5 on Ethernet0/0 seq 0xDE7 opt 0x42 flag 0x7
 l

Flag is set to 0x7. So that means I, M, MS bits are set.

>00:22:43: OSPF: Send DBD to 5.5.5.5 on Ethernet0/0 seq 0xDE7 opt 0x42 flag 0x7
 l

Again, the flag is 0x7 and the sequence # is the same.

>00:22:53: OSPF: Send DBD to 5.5.5.5 on Ethernet0/0 seq 0xDE7 opt 0x42 flag 0x7
 l

Same here.

It seems both want to become the Master as they are setting the I, M, and MS bi
ts. So try getting rid of RIDs and use loopbacks instead. Keep it simple and
gradually make it more copmlicated until it breaks. Then use that info to do a
 bug search.

Good luck.

hsb



This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:26 GMT-3