EIGRP Neighbor Down: AS Mismatch
Two routers share a working link and ping each other, but no EIGRP neighbor ever appears, and neither router logs a single message about it. Find the setting that keeps them apart.
What you'll practise
- Bring up a point-to-point EIGRP adjacency between two routers
- Read show ip eigrp neighbors and verify neighbor state
- Understand the EIGRP Autonomous System requirement
- Correct a mismatched AS number on an EIGRP router instance
- Verify adjacency and EIGRP-learned loopback reachability
Set it up
- 1
Have the node image ready
Images are not included. The file expects your own licensed copy of:
L3-ADVENTERPRISEK9-M-15.4-2T.bin
If your copy has a different name, open each node's Edit dialog after importing and pick your image from the list.
- 2
Copy it to the server and fix permissions
Replace
<your-server>with the IP address or hostname of your EVE-NG or PNETLab server.$ scp eigrp-neighbor-as-mismatch-lab.unl root@<your-server>:/opt/unetlab/labs/ # then, logged in to the server: $ /opt/unetlab/wrappers/unl_wrapper -a fixpermissions - 3
Open it and start the nodes
The canvas notes list the objectives, and the workbook walks through the fix.
Free to use and share under CC BY 4.0. Please credit LabFabric with a link to this page.