An engineer is troubleshooting why neighbor adjacency between two routers running OSPFv2 over a serial link is stuck in the "INIT" state. Both routers have the routing protocol enabled on their interfaces and are in area 0. The interfaces are active with IP addresses in the same subnet. What is the most likely cause of this issue?
The routers are configured with different process IDs
The hello and dead timers are mismatched between the routers
The network types on the serial interfaces are mismatched
There is a password mismatch due to authentication settings
When a neighbor remains in the INIT state, the local router is receiving OSPF hello packets from its peer, but the peer is not acknowledging the local router by listing its router ID in its own hellos. One of the most frequent reasons for this one-way communication is that authentication is enabled on only one side or the passwords differ. The router that expects authentication silently drops the non-authenticated hellos it receives, so the peer never learns about them and never lists the local router in its hello packets, leaving the session in INIT.
By contrast, mismatched hello/dead timers, MTU problems, or network-type mismatches normally prevent either side from accepting the other's hellos at all, so no neighbor ID is entered and the session stays in the DOWN state or never appears in the table.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are hello and dead timers in OSPF?
Open an interactive chat with Bash
How do you check and configure OSPF timers on a Cisco router?
Open an interactive chat with Bash
What is the impact of password mismatches in OSPF?
Open an interactive chat with Bash
Cisco CCNA 200-301
IP Connectivity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access