This article explains how to resolve the OSPF neighbor issue where your OSPF is stuck in INIT stated.
OSPF uses multicast IP 18.104.22.168 to send HELLO to its neighbor(s).
Sometimes, the multicast packets can get dropped between the source and destination, when this happens, the other side will not receive the HELLO packets, and as such will not be able to get pass the INIT state.
Just for clarity sake, these are the states OSPF routers pass through to form neighbors:
Full State (OSPF became fully operational)
Until the neighbors are in FULL State, your network won’t function.
So, neighbor routers get stuck in INIT state when an OSPF router failed to receive its neighbor HELLO packets. These can be caused due to a couple of reasons.
Below are some common causes and suggested solutions.
Commands that can help you troubleshoot OSPF stuck in INIT state.
Note: Take this from both neighbors.
#get router info ospf interface
# get router info ospf interface
portX is up, line protocol is up
Internet Address 192.168.X.Y/30, Area 0.0.0.0, MTU 1500
Process ID 0, VRF 0, Router ID 192.168.X.Y, Network Type POINTOPOINT, Cost: 1
Transmit Delay is 1 sec, State Point-To-Point
Timer intervals configured, Hello 10.000, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:08
Neighbor Count is 0, Adjacent neighbor count is 0
Crypt Sequence Number is 7900942
Hello received 14467 sent 75124, DD received 780 sent 906 <<<<<< HELLOs are being dropped.
LS-Req received 78 sent 261, LS-Upd received 27423 sent 376
LS-Ack received 298 sent 24409, Discarded 0
Cryptographic authentication enabled <<<< Authentication configured
Sending SA: Key 1
#diag sniffer packet any 'host 22.214.171.124' 4
Sample of 1-way HELLOs:
Line 26: 2.523359 portX out 192.168.X.Y -> 126.96.36.199: ip-proto-89 60