OSPF: Stuck in INIT

From: Daniel C. Young (danyoung99@xxxxxxxxxxxx)
Date: Sun Aug 05 2001 - 18:55:48 GMT-3


   
Scenario: OSPF over multipoint frame-relay; r5 as hub, r2 and r3 as spokes.
r5 and r3 form adjacencies, but r2 and r5 do not. It appears that r5 is not
receiving hellos from r2, although r2 receives them from r5.

r2#sh ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
170.10.245.5 100 INIT/ - 00:01:55 170.10.235.5 Serial0

r5#deb ip ospf adj
00:16:08: OSPF: Rcv hello from 170.10.245.5 area 0 from Serial0 170.10.235.5
00:16:08: OSPF: End of hello processing

r5#sh ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
170.10.243.3 0 FULL/ - 00:01:48 170.10.235.3 Serial0.1

r5#deb ip ospf adj
00:12:11: OSPF: Rcv hello from 170.10.243.3 area 0 from Serial0.1
170.10.235.3
00:12:11: OSPF: End of hello processing

[r2's config]
interface Serial0
 ip address 170.10.235.2 255.255.255.240
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-multipoint
 ip ospf priority 0
 no ip mroute-cache
 frame-relay map ip 170.10.235.2 102 broadcast
 frame-relay map ip 170.10.235.3 102 broadcast
 frame-relay map ip 170.10.235.5 102 broadcast
 frame-relay lmi-type ansi
end

[r3's config]
interface Serial0
 ip address 170.10.235.3 255.255.255.240
 no ip directed-broadcast
 encapsulation frame-relay
 ip ospf network point-to-multipoint
 ip ospf interface-retry 0
 ip ospf priority 0
 no ip mroute-cache
 no fair-queue
 frame-relay map ip 170.10.235.2 204 broadcast
 frame-relay map ip 170.10.235.3 204 broadcast
 frame-relay map ip 170.10.235.5 204 broadcast
 frame-relay lmi-type ansi
end

[r5's config]
interface Serial0.1 multipoint
 ip address 170.10.235.5 255.255.255.240
 no ip directed-broadcast
 ip ospf network point-to-multipoint
 ip ospf priority 100
 frame-relay map ip 170.10.235.2 401 broadcast
 frame-relay map ip 170.10.235.3 402 broadcast
 frame-relay map ip 170.10.235.5 402 broadcast
end

Normally, stuck-in-INIT states are caused by leaving out the 'broadcast'
parameter, but this is not the case. Further, if it was a misconfiguration
issue, r3 would also exhibit the same symptoms. IOS bug perhaps?

Regards,
Daniel

7 days and counting...
**Please read:http://www.groupstudy.com/list/posting.html



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:45 GMT-3