OSPF problem: INT to DOWN, Neighbor Down: Dead timer expired

[MitsYara]

Hi guys, sorry for my bad English. I'm having a problem when running OSPF recently, the debug that I ran show this:

*Mar 9 09:31:23.770: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:31:33.478: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:31:43.298: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:31:46.270: OSPF-1 HELLO Gi0/1: Rcv hello from 172.24.127.248 area 5 172.24.254.54
*Mar 9 09:31:46.270: OSPF-1 HELLO Gi0/1: No more immediate hello for nbr 172.24.127.248, which has been sent on this intf 2 times
*Mar 9 09:31:53.294: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:32:02.962: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:32:12.270: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:32:22.082: OSPF-1 HELLO Gi0/1: Send hello to 224.0.0.5 area 5 from 172.24.254.53
*Mar 9 09:32:26.270: %OSPF-5-ADJCHG: Process 1, Nbr 172.24.127.248 on GigabitEthernet0/1 from INIT to DOWN, Neighbor Down: Dead timer expired

And what should I do to troubleshoot this problem? 

[Dennis Mink]

on the router that you have this log info from, can you actually ping 172.24.127.248?

[Richard Burts]

As I read the logs I believe that 172.24.127.248 is the router ID of the neighbor and that the connected interface address is 172.24.254.54. I suggest that it is more important to be able to ping the interface address than the router ID.

These logs show the router actively sending hello messages. It receives one hello message but not anything else and the dead timer expires. I would suggest that you look on the other router and see what is going on there. Is the other router receiving the hello messages from the first router? Does the other router think it is sending hello messages?

HTH

Rick

[Joseph W. Doherty]

Also double check all your OSPF interface and area parameters. If they don't all match, you won't get beyond the hello stage.

[Joseph W. Doherty]

Sorry - this was for another thread.

[Predrag Jovic]

Check filtering on interfaces and control plane filtering (if present).

Devices stuck in INIT phase means that device received OSPF hello from neighbor, but its own router-d can't be found in neighbor's hello packet. If device would stop receiving hellos and going back to DOWN state.