Step-by-Step Troubleshooting for EIGRP on Cisco Routers
Enhanced Interior Gateway Routing Protocol (EIGRP) is a powerful Cisco-developed routing protocol known for fast convergence, unequal-cost load balancing, and low overhead. But when EIGRP neighbors fail to form or routes suddenly disappear, downtime can cost serious money. This complete guide delivers a step-by-step EIGRP troubleshooting process on Cisco routers with practical commands, common problems, and proven solutions to restore connectivity fast.
Why EIGRP Troubleshooting Is a Must-Have Skill
EIGRP powers countless enterprise WANs, branch networks, and hybrid cloud environments. Understanding how to diagnose adjacency failures, stuck-in-active routes, and redistribution errors is essential for network engineers preparing for CCNA, CCNP ENCOR, or managing production infrastructure.
Step 1: Verify Physical and IP Connectivity
EIGRP runs directly over IP (protocol 88), so Layer 1 through Layer 3 must be healthy before anything else.
R1# show interfaces status
R1# ping 10.1.1.2
Check for interface errors, duplex mismatches, or administratively down ports before suspecting EIGRP itself.
Step 2: Check EIGRP Neighbor Relationships
Run this first when EIGRP issues strike:
R1# show ip eigrp interfaces
A healthy neighbor table shows the neighbor IP, interface, uptime, and hold time. If a neighbor is missing or flapping, the adjacency is broken.
Step 3: Validate EIGRP Configuration Parameters
EIGRP requires several parameters to match between neighbors. Any mismatch prevents adjacency.
R1# show running-config | section eigrp
Parameters that must match between EIGRP peers:
- Autonomous System (AS) number
- Primary subnet on the shared link
- K-values (metric weights)
- Authentication mode and key
- Named mode vs. classic mode (when mixing)
Step 4: Check for Network Statement Issues
If an interface isn't running EIGRP, no adjacency will form over it.
R1(config-router)# network 10.1.1.0 0.0.0.255
Ensure the network statement and wildcard mask correctly include the interface IP. Also verify the interface isn't configured as passive-interface, which suppresses hellos.
Step 5: Inspect Authentication Settings
Misconfigured authentication silently drops hellos and prevents adjacency.
R1# show key chain
Both routers must use identical key chains, key IDs, key strings, and authentication mode (MD5 or SHA in named mode).
Step 6: Debug EIGRP Hellos and Events
When configs look correct but the neighbor still won't come up:
R1# debug ip eigrp notifications
R1# debug eigrp neighbors
Warning: Always disable debugs with undebug all in production to avoid CPU spikes.
Step 7: Troubleshoot Stuck-in-Active (SIA) Routes
A stuck-in-active route occurs when a router queries neighbors for an alternate path and doesn't receive a reply within the SIA timer (default 180 seconds).
R1# show ip eigrp events
Fixes for SIA issues:
- Use EIGRP stub routers on spoke sites to limit query scope.
- Apply manual route summarization at distribution points.
- Filter unnecessary routes with distribute-lists.
- Upgrade IOS for improved SIA handling (SIA-Query/SIA-Reply).
Step 8: Troubleshoot Missing EIGRP Routes
If the adjacency is up but routes are missing, inspect the EIGRP topology table.
R1# show ip eigrp topology all-links
R1# show ip route eigrp
Common reasons routes are missing:
- Route not advertised by the neighbor
- Distribute-lists or offset-lists filtering the prefix
- Auto-summary causing classful summarization issues
- Administrative distance favoring another protocol
- Metric mismatch preventing successor selection
Step 9: Check Auto-Summary and Discontiguous Networks
EIGRP classic mode historically had auto-summary enabled. In discontiguous networks, this can cause routing black holes.
Modern IOS versions disable auto-summary by default, but always confirm during troubleshooting.
Step 10: Verify Redistribution and Metric Settings
Redistributing routes into EIGRP without a seed metric causes them to be ignored.
Always specify bandwidth, delay, reliability, load, and MTU when redistributing external routes into EIGRP.
Step 11: Clear EIGRP Safely
After changing configurations, force EIGRP to reconverge:
R1# clear ip route *
Use with caution—these commands temporarily disrupt routing.
Common EIGRP Errors and Quick Fixes
| Symptom | Likely Cause | Fix |
|---|---|---|
| No neighbor formed | AS mismatch or network statement missing | Align AS and add network statement |
| Adjacency flapping | Duplex issue or high CPU | Check interface counters and load |
| Stuck-in-Active (SIA) | Excessive query scope | Use stubs and summarization |
| Missing routes | Auto-summary or filter | Disable auto-summary, review filters |
| K-value mismatch | Non-default metric weights | Match K-values on both routers |
Best Practices for Stable EIGRP Networks
- Use EIGRP named mode for modern deployments—it's easier to manage.
- Configure stub routers on branch sites to minimize query propagation.
- Summarize routes at distribution layers to improve convergence.
- Enable MD5 or SHA authentication on all adjacencies.
- Use passive-interface default and explicitly enable EIGRP-facing interfaces.
- Monitor with show ip eigrp events and syslog for early warning of issues.
Final Thoughts
Mastering EIGRP troubleshooting on Cisco routers requires a disciplined, layered approach—verify connectivity, confirm adjacency, align parameters, inspect the topology table, and validate route installation. By following this step-by-step playbook, you can resolve 95% of EIGRP issues quickly and confidently, whether in the lab or in production.
💡 Pro Tip: For any EIGRP outage, start with show ip eigrp neighbors, show ip eigrp topology, and show ip protocols. These three commands uncover the majority of EIGRP problems in seconds.
Keywords: EIGRP troubleshooting Cisco, Cisco EIGRP commands, EIGRP neighbor not forming, EIGRP stuck in active, EIGRP SIA fix, CCNP EIGRP guide, EIGRP named mode.
