What could be the cause of this problem?

You have just completed an OSPF implementation. While executing your verification plan, you
determine that R1 is not able to establish full OSPF adjacency with R2. The show ip ospf neighbor
command output on R1 shows that R2 is stuck in the INIT state.
What could be the cause of this problem?

You have just completed an OSPF implementation. While executing your verification plan, you
determine that R1 is not able to establish full OSPF adjacency with R2. The show ip ospf neighbor
command output on R1 shows that R2 is stuck in the INIT state.
What could be the cause of this problem?

A.
DR and BDR election errors between R1 and R2.

B.
The R2 router has not received the OSPF hello packets from the R1 router.

C.
Mismatched interface maximum transmission unit (MTU) configuration between the R1 and R2.

D.
Mismatched OSPF hello interval configuration between the R1 and R2.

E.
Corrupted LSAs exchanges between the R1 and R2.

Explanation:
When a router receives an OSPF Hello from a neighbor, it sends the Hello packet by including that
neighbor’s router ID in the Hello packet. If the neighbor does not receive this packet (means that it
doesn’t see itself in this packet), it will be stuck in INIT state. INIT state can be understood as a
one-way Hello. An example of a router stuck in INIT state is shown below:



Leave a Reply 0

Your email address will not be published. Required fields are marked *