EIGRP Neighbor Adjacency Troubleshooting
Refer to the exhibit. Which configuration command establishes an EIGRP neighbor adjacency between the hub and 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.
Community Insight
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.
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.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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
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?
It means the router receives EIGRP packets but doesn't recognize the sender as a valid neighbor, often because the receiving interface isn't enabled for EIGRP.
Why configure the network command on the hub instead of the spoke?
The hub must have its interface enabled to receive and process Hellos from the spoke. If the hub's interface isn't in the network statement, it won't form an adjacency regardless of the spoke's config.
Related Analysis
Practice All 300-410 Questions
Access 159 questions with complete answers and detailed explanations.
View Full 300-410 Practice Test →