Why R1 and R2 OSPF Hello/Dead Timer Mismatch Blocks Adjacency

Configure and verify single area OSPFv2 Interpret the components of routing table
Answer Correct answer: D — R1 and R2's hello and dead timers do not match, so OSPF cannot establish an adjacency on their common Ethernet link.

A network administrator is troubleshooting the OSPF configuration of routers R1 and R2. The routers cannot establish an adjacency relationship on their common Ethernet link. [sampleXML/xmlfile-321_1.png] The graphic shows the output of the show ip ospf interface e0 command for routers R1 and R2. Based on the information in the graphic, what is the cause of this problem?

  1. The OSPF area is not configured properly.
  2. The priority on R1 should be set higher.
  3. The cost on R1 should be set higher.
  4. The hello and dead timers are not configured properly. Correct Answer
  5. A backup designated router needs to be added to the network.
  6. The OSPF process ID numbers must match.

Community Insight

The exam tests your knowledge that OSPF neighbors must agree on hello and dead timers to form an adjacency; the trap is that the same graphic also shows duplicate interface IP addresses, a defect no option covers, so you must pick the timer mismatch.

When two OSPFv2 routers cannot form an adjacency on a shared Ethernet link, the 'show ip ospf interface' output reveals which neighbor parameters must match. In this scenario, the hello and dead intervals on R1 and R2 differ, which is the listed cause of the failed adjacency.

Choosing A (improper OSPF area) or B (raise R1 priority): both routers are in area 0, and priority only influences DR election, not adjacency formation.

Community Discussion (16 comments)

carlalap 👍 1 Selected: D
R1: Hello = 5 sec, Dead = 20 sec R2: Hello = 10 sec, Dead = 40 sec These mismatched timers prevent R1 and R2 from becoming OSPF neighbors.
arias 👍 2 Selected: D
Hello and dead timers need to match
Portcullis 👍 2 Selected: D
The hello and dead timers do not match. The answer is not A.
cd1c33b 👍 3 Selected: A
How much are we paying for these 3rd world questions that are not accurate?
Ineng 👍 3
Not in the options but both IP of the interfaces are the same. Plus hello and dead timer are different.
MonsieurP 👍 2
What about IP addresses on both e0 interfaces of the 2 routers? Is it correct both be the same?
DoBronx 👍 4
Both have same IP, both are DR, shame on cisco
ScorpionNet 👍 1
D is right because the hello and dead interval needs to match in order to maintain neighbor adjacency
dipanjana1990 👍 3
First of all both the routers have same IP address. As well as both belong to same area 0 yet both of them are DR. How come its possible? There are more than 1 reason for these two routers to form ospf neighborship, let alone adjacency. But since there are some parameters which are need to matched in order to form ospf neighborship and timers mismatch is one of them. Thus, option D is correct.
Belinda 👍 1
The hello timer, dead and wait time differs on both routers, thereby causing the adjacency not to form
Belinda 👍 1
The hello timer interval differs on both router which is the reason why the adjacency did form a relationship.
CiscoTerminator 👍 2
Anyone notice that before we even talk about OSPF, the two routers have the same IP address. Definitely an error there.
Cisna 👍 2
The good thing is, its not part of the multiple choices
4guysgaming 👍 2
I also don't see a BDR. The output even says no backup Designated Router on this network?
Micah7 👍 5
Agreed- same IP address. This was the first thing I noticed as well, but of course did not see it as an answer option so had to move on to another possibility
Talloo 👍 72
By the way, the interfaces on both routers have the same IP address

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Option D is correct because OSPF requires the hello and dead intervals to match between neighbors for a bidirectional adjacency to form. When the timers on R1 and R2's common Ethernet link disagree, the routers reject each other's hello packets and never progress beyond the INIT state. The 'show ip ospf interface' output in the graphic exposes this mismatch directly, and several community members — including arias and Portcullis — confirmed that "The hello and dead timers do not match" while rejecting option A.

Why the Other Options Are Wrong

Option A is wrong because both interfaces display area 0, so the area is configured correctly and mismatched areas would instead appear as an area mismatch. Option B is wrong because priority affects only DR/BDR election and does not prevent adjacency; on a broadcast link with priority 0 both routers can still become neighbors. Option C is wrong because OSPF cost influences path selection, not neighbor establishment, and lowering or raising it has no bearing on adjacency. Option E is wrong because a BDR is optional and its absence does not block neighbor relationships. Option F is wrong because the OSPF process ID is a local-only value that need not match between routers.

Community Comment Notes

Several learners flagged that the graphic also shows both e0 interfaces using the same IP address and both routers acting as DR — as Talloo put it, "the interfaces on both routers have the same IP address" — which is a genuine defect but is not among the answer choices. As cd1c33b complained, the item is "not accurate," and Micah7 noted that with the correct issue absent from the options testers "had to move on to another possibility." Among the available choices, the hello and dead timer mismatch (D) is the only technically valid OSPF adjacency blocker.

Official Reference

Exam Strategy

Read the 'show ip ospf interface' output for the adjacency prerequisites checklist: area, network type, hello/dead timers, authentication, and subnet mask. Remember that a duplicate IP on both ends is never an option choice, so pick the mismatch that does appear in the options.

Frequently Asked Questions

Why is option D the best answer when both routers also share the same IP address?

A duplicate IP is a real fault visible in the output, but it is not offered as a choice. Among the listed options, only the hello and dead timer mismatch can be read from the output and blocks adjacency.

Do OSPF process IDs and priority need to match between neighbors?

No. The process ID is local to each router, and priority only decides DR/BDR election on a broadcast segment. Neither is required to match for an adjacency to form.

More 200-301 FAQ →

Related Analysis

Practice All 200-301 Questions

Access 220 questions with complete answers and detailed explanations.

View Full 200-301 Practice Test →

← Back to 200-301 Study Guide