The complete CCNP/CCIE interview preparation toolkit: 15 quick-fire facts, 15 one-sentence concept answers, 20 scenario-based troubleshooting questions, and a 15-question interactive quiz with scoring and replay.
Common Causes:
Troubleshooting Steps:
show ip eigrp neighbors debug eigrp packets hello show ip interface | include access list show ip access-lists
Fix: Verify bidirectional hello reachability, remove blocking ACLs, and disable uRPF if it's dropping asymmetric traffic.
Root Cause: One router has custom metric weights (e.g., metric weights 0 1 1 1 1 1) while the other uses defaults.
Fix โ Align to Default on BOTH routers:
router eigrp 1234 metric weights 0 1 0 1 0 0 ! Verify show ip protocols | include K-values
Production Tip: Always apply K-value changes during a maintenance window โ clearing the EIGRP process causes routing disruptions.
Meaning: High Q-Count indicates pending unacknowledged packets โ the local router is waiting for ACKs that aren't arriving.
Possible Causes: Congested link, slow neighbor CPU, packet loss, or MTU/fragmentation issues.
Diagnostic Commands:
show ip eigrp neighbors detail show interface | include error|drop|CRC show processes cpu | include EIGRP
Fix: Reduce congestion, verify MTU consistency, check for duplex mismatches, and ensure the neighbor CPU isn't overloaded.
What Happens: The adjacency never forms. Static unicast and dynamic multicast are incompatible โ neither side sends Hellos the other can receive.
Verification:
show ip eigrp neighbors ! Shows empty peer list ! Syslog: Neighbor down: Static and dynamic configurations incompatible
Fix: Make both sides consistent โ either both static OR both dynamic.
Symptoms:
Neighbor down: holding time expiredWhy: The router with 3s Hello sends faster, but the other side's hold timer is still 15s. If even one Hello is delayed by more than 15s, the neighbor is declared dead.
Fix: Align timers on both sides. Recommended ratio: Hold = 3 ร Hello.
Impact: Routes from the duplicated RID are silently discarded. Partial reachability failures occur with no obvious correlation to a single event.
Syslog:
%DUAL-4-DUP_RID: Duplicate router ID 1.1.1.1 detected from 10.1.12.2
Fix:
router eigrp 1234 eigrp router-id 10.1.1.99 clear ip eigrp 1234 neighbors *
Checklist:
Root Cause: No feasible successor exists, so the route enters Active state and EIGRP sends queries. If neighbors don't respond within 3 minutes (default active-timer), SIA occurs.
Fix Options:
router eigrp 1234 eigrp stub connected summary
Issue: EIGRP has no MTU-checking mechanism like OSPF, so adjacency will still form. But Null Updates larger than 1400 bytes may be dropped, causing intermittent adjacency flaps.
Fix: Align MTUs on both sides:
interface GigabitEthernet0/0 ip mtu 1400
Note: Unlike OSPF, EIGRP doesn't get stuck in EXSTART; it just silently drops large packets.
passive-interface default globally, but you need to enable EIGRP only on one specific interface. How do you do it?
Configuration:
router eigrp 1234 passive-interface default no passive-interface GigabitEthernet0/0
Why This Works: passive-interface default stops Hellos on all interfaces, then no passive-interface selectively enables the one you want. This is the recommended security best practice.
Diagnostic Steps:
show key chain EIGRP-KEY show run interface GigabitEthernet0/0 | include authentication show ip eigrp neighbors
Common Causes:
Fix: Ensure key ID, key-string, and mode match exactly on both sides.
Result: Adjacency fails to form. The static side sends unicast Hellos to the peer, but the peer sends multicast Hellos that the static side ignores.
Syslog:
%DUAL-5-NBRCHANGE: Neighbor 10.1.12.2 is down: Static and dynamic neighbor configurations are incompatible
Fix: Configure the neighbor command on BOTH sides of the link.
Best Practice Configuration:
router eigrp 1234 passive-interface default no passive-interface GigabitEthernet0/0 network 10.1.12.0 0.0.0.255
Why This Works: The network statement activates EIGRP on matching interfaces, but passive-interface default keeps Hellos silenced everywhere else. Only the specified interface participates.
Possible Causes:
distribute-list, prefix-list, or route-map is blocking the routesDiagnostic:
show ip eigrp topology show ip protocols show ip route | include [prefix]
Recommended Sequence:
neighbor commands on BOTH routers โ do NOT remove dynamic config yetpassive-interface or multicast-specific settings if they were blockingshow ip eigrp neighbors to confirm stable adjacencyImportant: EIGRP does not allow static and dynamic on the same interface โ you must plan a brief window where both sides are cut over.
clear ip eigrp neighbors *. What happens to routes, and how fast do they reconverge?
Immediate Effect: All EIGRP neighborships are torn down. Routes learned from EIGRP are removed from the routing table.
Reconvergence: Typically within 10โ30 seconds โ Hellos re-exchange, Null Updates verify bidirectionality, and topology tables repopulate.
Production Tip: Never run this command casually on a production core router. Use during maintenance windows or apply clear ip eigrp neighbors [specific-ip] for single neighbors.
Step-by-Step Fix:
! On both routers: show ip protocols | include K-values ! Note current values router eigrp 1234 metric weights 0 1 0 1 0 0 ! Align to default ! Verify show ip eigrp neighbors
Warning: If K-values were custom because of a specific QoS or path-engineering design, do NOT blindly reset to default โ align them to the intended values.
Hidden Causes to Check:
show ip eigrp interfaces show ip eigrp interfaces detail | include passive show ip protocols | include AS
Recommended Approach:
show ip prefix-listdistribute-list ... in at the EIGRP process level (inbound filtering is safer than outbound โ no risk of breaking downstream routers)show ip eigrp topology that routes are filtered as expectedip prefix-list FILTER permit 10.1.0.0/16 ge 24 le 28 router eigrp 1234 distribute-list prefix FILTER in GigabitEthernet0/0
Most Likely Cause: The ACL is blocking EIGRP's protocol 88 traffic or the multicast address 224.0.0.10. Even well-intentioned security ACLs commonly forget EIGRP.
Fix: Add explicit permit statements at the TOP of the ACL:
ip access-list extended SECURITY_ACL permit eigrp any any permit ip 224.0.0.10 0.0.0.0 any ! ... rest of ACL
Verification:
show ip eigrp neighbors show ip access-lists SECURITY_ACL