EIGRP Neighbor Adjacency Troubleshooting
Short answer
B Adding the network 10.1.2.192 command on the hub router enables its interface to participate in EIGRP, resolving the adjacency issue.
Question
Key Takeaways
The core concept is configuring the network command on the hub router to properly advertise the spoke interface's subnet for EIGRP neighbor discovery.
This question addresses EIGRP neighbor adjacency issues, specifically the 'Neighbor not yet found' error, and identifies the correct network statement configuration to resolve it.
Common mistake: Learners often mistakenly believe that configuring the network command on the spoke side is sufficient, or they look for advanced commands like 'eigrp-peer', which are not standard for basic adjacency establishment in this context.
Expert Analysis
Why the Answer Is Correct
The 'Neighbor not yet found' message indicates that while packets are being exchanged, the router does not recognize the peer as a valid neighbor because the receiving interface is not included in an active EIGRP process. The solution is to ensure the hub router has a network statement covering the spoke's IP address (10.1.2.192). By adding 'network 10.1.2.192' on the hub, the interface connected to the spoke becomes part of the EIGRP domain, allowing it to accept and process Hello packets from the spoke, thus establishing adjacency.
Why the Other Options Are Wrong
Option A is incorrect because simply configuring the spoke does not guarantee the hub will recognize it if the hub's interface isn't enabled for EIGRP. Option C ('eigrp-peer') is not a standard IOS command for establishing dynamic EIGRP adjacencies over a broadcast medium; EIGRP relies on multicast Hellos and network statements. Option D ('connected') is not a valid EIGRP configuration command.
Community Comment Notes
Community members frequently cite Cisco documentation explaining that 'Neighbor not yet found' means the router sees traffic but doesn't recognize the sender as a valid neighbor due to configuration mismatches or missing network statements. One user noted that this type of question can be ambiguous without seeing the full exhibit, but the consensus aligns with enabling the hub's interface for EIGRP.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always check both sides of the link when troubleshooting routing adjacencies. If one side is sending Hellos but the other isn't reciprocating neighbors, verify that the receiving interface is included in the routing protocol's network statement.
Frequently Asked Questions
What does 'Neighbor not yet found' mean in EIGRP?
Why configure the network command on the hub instead of the spoke?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 4
-
XBfoundX 👍 5How the heck you can understand what should be right there? This question is absurd.
-
Pietjeplukgeluk 👍 3Not sure, but i feel that some context of the question is missing. Please correctly if i am wrong.
-
NLFluke 👍 2 Answered BThe 'Neighbor not yet found' means that you are receiving updates, queries, or replies from an EIGRP router on this link, but the router does not recognize the sender as a valid neighbor https://www.cisco.com/c/en/us/support/docs/ip/enhanced-interior-gateway-routing-protocol-eigrp/118974-technote-eigrp-00.html
-
Sammy3637 👍 1 Answered Bbased on assumption which is a trend with Cisco exam question , i will go with B
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All 300-410 Questions
Access 159 questions with complete answers and detailed explanations.
View Full 300-410 Practice Test →