EIGRP Overview: Neighbors, DUAL and Fast Convergence
Learn how EIGRP discovers routers, chooses loop-free paths, keeps backup routes, and reacts when a link fails. Follow one small lab from configuration to troubleshooting.
EIGRP at a Glance
EIGRP is a dynamic interior routing protocol. It was created by Cisco and uses the Diffusing Update Algorithm (DUAL) to choose paths that are free from routing loops.
In This Lesson
- Read the three-router lab
- Understand the core behavior
- Form neighbor relationships
- Follow the three EIGRP tables
- Learn successors and feasible successors
- Understand metric and K-value basics
- Explain and validate one learned route
- Troubleshoot in layers
- Continue with one focused topic
- Complete the guided practice
- Review the frequently asked questions
1. Read the Three-Router Lab
All three routers use EIGRP autonomous system 100. R1 reaches R3 through R2. The loopbacks give us stable networks to advertise and test.
RID 1.1.1.1Loopback: 10.1.1.1/24RID 2.2.2.2Transit routerRID 3.3.3.3Loopback: 10.3.3.3/2410.3.3.0/24 through R2.D.2. Understand EIGRP's Core Behavior
EIGRP does not send its entire routing table at a fixed interval. After neighbors synchronize, it normally sends an update only when information changes.
- Partial updates: An update carries changed route information, not the complete table.
- Bounded delivery: Information is sent to the neighbors that need it, rather than flooded through every unrelated segment.
- DUAL: The algorithm tests alternate paths before using them, which protects the network from loops.
- Flexible path use: EIGRP supports equal-cost and controlled unequal-cost load balancing.
- Classless routing: Subnet masks travel with routes, so VLSM and CIDR are supported.
3. Form Neighbor Relationships
Two connected routers first discover each other and agree on key settings. They use Hello packets to start and maintain the relationship.
Send Hello
The enabled interface sends an EIGRP Hello.
Check settings
AS number, K-values, subnet, and authentication must be compatible.
Become neighbors
Each router adds the other to its neighbor table.
Exchange routes
They synchronize useful routes and calculate loop-free paths.
| Setting | Requirement | If wrong |
|---|---|---|
| Autonomous system | Must match in classic mode | No neighbor relationship |
| K-values | Must match | Hello is rejected |
| Primary IP subnet | Must be compatible on the link | No direct neighbor |
| Authentication | Method and key must match when enabled | Packets are rejected |
| Hello and hold timers | Do not have to match | Each router advertises the hold time it expects |
4. Follow the Three EIGRP Tables
Use the tables in this order when learning or troubleshooting. Each one answers a different question.
Neighbor table
Who can I exchange routes with? It stores directly connected EIGRP peers and transport health.
Topology table
What paths did I learn? It stores route candidates, metrics, and DUAL state.
Routing table
Which path forwards traffic? It receives the selected successor route.
Inspect each table
show ip eigrp neighbors
show ip eigrp topology
show ip route eigrpRead the result
Neighbor present → exchange is possible
Prefix in topology → EIGRP learned a path
D route installed → path won selection5. Learn Successors and Feasible Successors
DUAL compares route metrics and keeps the best loop-free result. Tie each word to one destination, such as R3's 10.3.3.0/24 loopback.
| Term | Plain meaning | Practical use |
|---|---|---|
| Successor | The best loop-free path | Installed in the routing table |
| Feasible successor | A proven loop-free backup path | Can replace the successor quickly |
| Feasible distance (FD) | The local router's best total metric | Used as the comparison point |
| Reported distance (RD) | The neighbor's advertised metric | Shows how far the neighbor says it is |
| Feasibility condition | Alternate RD is lower than the current successor FD | Proves the alternate cannot loop through this router |
6. Understand Metric and K-Value Basics
By default, EIGRP chooses a path using the lowest configured bandwidth along the path and the total configured delay. It does not measure current link utilization to create the default metric.
- Bandwidth: EIGRP uses the configured interface bandwidth. A wrong value can cause a surprising path choice.
- Delay: Every outbound interface delay along the path contributes to the total.
- K-values: Neighbors must use the same metric weights. Keep defaults unless the design has been carefully validated.
7. Use Equal-Cost and Unequal-Cost Paths
EIGRP installs equal-cost paths automatically up to the configured maximum. It can also use qualified unequal-cost paths with variance, but every installed alternate must still pass EIGRP's loop-free rules.
| Path choice | Requirement | Practical result |
|---|---|---|
| Equal-cost | Multiple successors have the same best metric | Traffic can use more than one installed next hop |
| Unequal-cost | Path is loop-free and its metric is within the variance multiplier | A slower qualified path can also be installed |
| Backup only | Path is a feasible successor but is outside the allowed variance | Kept in topology for fast recovery, not used for normal forwarding |
Example controls
router eigrp 100
maximum-paths 4
variance 2Verify installed paths
show ip eigrp topology all-links
show ip route 10.3.3.0
show ip cef 10.3.3.3 detail8. Control Queries in a Larger Network
Fast convergence depends on how far EIGRP must search. A small, well-defined query domain is easier to predict than a flat network where every router asks many downstream neighbors.
- Summarize at boundaries: A router that has no detailed route behind a summary can stop an unnecessary Query.
- Use EIGRP stub at the edge: A stub router tells upstream neighbors not to use it as a transit search path for routes it should not know.
- Keep the topology intentional: Remove accidental transit paths and document redistribution points.
- Protect link and CPU health: Reliable Query and Reply delivery still depends on stable interfaces and responsive routers.
| Tool | What it limits | Use case |
|---|---|---|
| Feasible successor | May avoid a Query completely | A safe backup is already known |
| Route summary | Hides component-route changes beyond the boundary | Stable campus or WAN blocks |
| EIGRP stub | Prevents unsuitable query paths through an edge router | Branches, spokes, and non-transit sites |
9. Read Internal and External EIGRP Routes
A route's source affects its route code and administrative distance. Read both values before deciding why one route won over another routing source.
| Route type | Route code | Default AD | How it entered EIGRP |
|---|---|---|---|
| Internal | D | 90 | Originated inside the same EIGRP autonomous system |
| External | D EX | 170 | Redistributed from another routing source |
Compare route sources
show ip route 10.3.3.0
show ip route eigrp
show ip eigrp topology 10.3.3.0/24Read the brackets
D 10.3.3.0/24 [90/3072]
│ └─ EIGRP metric
└──── Administrative distance10. Protect EIGRP Neighbor Relationships
Authentication helps a router reject EIGRP packets that do not carry the expected key. It does not encrypt route information, so protect the management and transport network as well.
- Match both ends: Authentication mode, key chain, active key, and time validity must be compatible.
- Keep secrets out of guides: Use placeholders in documentation and store real keys in an approved secret system.
- Plan rotation: Overlap valid keys when the platform supports it, then verify every neighbor after the change.
- Use current platform options: Classic deployments commonly use MD5; named mode may support stronger algorithms such as HMAC-SHA-256.
| Symptom | Likely check | Evidence |
|---|---|---|
| No neighbor after enabling security | Mode, key chain, key ID, and secret | Compare both interface configurations |
| Neighbor drops at a specific time | Key lifetime and clock synchronization | Check clock, logs, and active key window |
| Only one link fails | Interface-level attachment | Confirm the correct interface uses the intended policy |
11. Plan Summaries and Redistribution Boundaries
Summarization makes the routing view smaller and can contain route changes. Redistribution connects routing domains, but it also introduces external routes and possible feedback loops.
Choose a boundary
Summarize where several stable component networks meet a campus, WAN, or branch boundary.
Control what crosses
Use explicit prefixes and route policy. Do not redistribute every route by habit.
Prove reachability
Verify the summary, component routes, external metric, return path, and failure behavior.
| Design action | Benefit | Main risk |
|---|---|---|
| Manual summary | Smaller tables and reduced query scope | Blackholing when the summary exists without a reachable component |
| Redistribution | Exchanges routes with another protocol or source | Loops, missing seed metric, or unexpected external paths |
| Route tagging and filtering | Identifies and blocks routes returning to their source | Incorrect policy can remove required reachability |
12. Know the Packet Types
EIGRP uses its Reliable Transport Protocol to manage delivery. Some packets need an acknowledgement; regular Hello packets do not.
| Packet | Purpose | Delivery behavior |
|---|---|---|
| Hello | Find and maintain neighbors | Unreliable; sent periodically |
| Update | Send route information | Can use reliable delivery |
| Query | Ask neighbors for an alternate path | Reliable |
| Reply | Answer a route query | Reliable |
| Acknowledgement | Confirm a reliable packet arrived | Unicast Hello packet with no data |
show ip eigrp neighbors can point to packet loss, congestion, or a neighbor that is not acknowledging reliable packets.13. Configure a Basic IPv4 Lab
Configure interface addresses first. Then enable the same EIGRP AS on every router and select the local interfaces that should participate.
R1
router eigrp 100
eigrp router-id 1.1.1.1
network 10.0.0.0 0.255.255.255
passive-interface Loopback0
no auto-summaryR2
router eigrp 100
eigrp router-id 2.2.2.2
network 10.0.0.0 0.255.255.255
no auto-summaryR3
router eigrp 100
eigrp router-id 3.3.3.3
network 10.0.0.0 0.255.255.255
passive-interface Loopback0
no auto-summaryrouter eigrp 100: Starts classic EIGRP. Direct neighbors must use the same AS number.network: Selects matching local interfaces; it does not directly advertise an arbitrary remote network.passive-interface: Advertises the connected loopback but stops EIGRP packets on that interface.
14. Recognize Named Mode and IPv6
Classic mode is easy for a first lab. Named mode places IPv4 and IPv6 address families under one EIGRP process and gives engineers one structured location for topology, interface, and address-family settings.
Named mode structure
router eigrp CAMPUS
address-family ipv4 autonomous-system 100
eigrp router-id 1.1.1.1
network 10.0.0.0 0.255.255.255
af-interface Loopback0
passive-interface
exit-af-interface
exit-address-familyIPv6 orientation
IPv6 multicast: FF02::A
Neighbors use link-local addresses
Router ID remains a 32-bit value
Verify with platform-specific
"show ipv6 eigrp" commands- Same routing ideas: Neighbors, DUAL, successors, feasible successors, and topology states still matter.
- Different command structure: Exact syntax varies by software release, so confirm the platform guide before deploying it.
- Router ID: IPv6 EIGRP still needs a unique 32-bit router ID even though routes carry IPv6 prefixes.
7. Explain and Validate One Learned Route
Use one destination from start to finish: R3's 10.3.3.0/24 loopback. R1 must first recognize R2 as a neighbor, learn the prefix through R2, select it as the successor, and finally install it for forwarding.
Step 1: Neighbor
R1# show ip eigrp neighbors
H Address Interface Hold Uptime Q
0 10.0.12.2 Gi0/0 12 00:18:42 0Step 2: Topology
R1# show ip eigrp topology 10.3.3.0/24
State is Passive, Query origin flag is 1
1 Successor, FD is 3072
via 10.0.12.2 (3072/2048), Gi0/0Step 3: Routing
R1# show ip route eigrp
D 10.3.3.0/24 [90/3072]
via 10.0.12.2, GigabitEthernet0/010.0.12.2, and a sourced ping proves forward and return traffic.”| Field | Healthy meaning | Warning sign |
|---|---|---|
| Hold | Counts down and refreshes when Hellos arrive | Reaches zero repeatedly |
| Q count | Normally stays at zero | Remains above zero |
| Passive topology state | DUAL calculation is complete | Route remains Active for too long |
Route code D | Internal EIGRP route installed | Expected prefix missing |
Route code D EX | External route imported into EIGRP | Unexpected redistribution |
8. Troubleshoot in Layers
Do not clear the EIGRP process as your first step. Find the first failed layer, record the evidence, and change one setting at a time.
| Symptom | Check first | Useful commands |
|---|---|---|
| No neighbor | Interface, subnet, AS number, K-values, passive state, authentication, protocol 88 filtering | show ip eigrp interfacesshow ip protocols |
| Neighbor resets | Hold timer expiry, link loss, authentication, duplicate addresses | show ip eigrp neighbors detailshow logging |
| Neighbor up, route missing | Network selection, topology entry, filtering, summarization, better route source | show ip eigrp topologyshow ip route |
| Route stays Active | Query scope, unreachable neighbor, packet loss, overloaded router | show ip eigrp topology activeshow processes cpu |
| Unexpected path | Bandwidth, delay, K-values, variance, interface settings | show interfacesshow ip eigrp topology all-links |
- Confirm every required interface is
up/upwith correct primary addressing. - Confirm EIGRP is enabled on the interface and is not passive.
- Compare AS number, K-values, and authentication on both ends.
- Trace the prefix from topology table to routing table, then test the return path.
9. Continue with One Focused Topic
This overview stops after the core learning path. Choose one lesson below when you are ready to study an advanced behavior without mixing several concepts together.
Packet behavior
Learn Hello, Update, Query, Reply, and acknowledgement behavior as one complete exchange.
Open packet typesMetrics and path choice
Study bandwidth, delay, K-values, successors, and feasible successors with calculated examples.
Open metricsConfiguration
Build the three-router lab step by step, then verify the neighbor, topology, and routing tables.
Open configuration17. Change EIGRP Safely
A routing change can affect many prefixes at once. Use a small change plan that defines the expected control-plane result and the traffic test before touching the configuration.
Capture baseline
Save neighbors, topology entries, routes, traffic tests, CPU, and logs.
Change one item
Apply the smallest approved configuration change.
Verify layers
Check adjacency, topology state, route selection, and both traffic directions.
Keep rollback ready
Revert if the result differs from the written success criteria.
| Checkpoint | Success evidence | Rollback trigger |
|---|---|---|
| Neighbors | Expected peers remain stable and Q count returns to zero | Repeated resets or a missing required peer |
| Topology | Changed prefixes return to Passive with expected successors | Unexpected Active routes or lost feasible successors |
| Routing table | Expected internal or external paths and next hops appear | Route loss, wrong source, or unintended redistribution |
| Traffic | Forward and return tests pass from useful source addresses | Loss, loops, or an unexpected path through a policy boundary |
10. Guided Practice Lab
Complete one task at a time. Restore the healthy baseline before starting the next fault so the evidence remains clear.
Task 1: Build the Baseline
- Address the links and loopbacks shown in the topology.
- Enable EIGRP AS 100 on R1, R2, and R3.
- Make the loopbacks passive.
- Verify two neighbor pairs and both remote loopback routes.
Expected result: R1 reaches 10.3.3.3 and R3 reaches 10.1.1.1.
Task 2: Follow a Route
- Choose R3's loopback prefix.
- Find it in R1's topology table.
- Record FD, RD, successor, and next hop.
- Confirm the same next hop in the routing table.
Expected result: You can explain how a learned path becomes a forwarding route.
Task 3: Repair an AS Mismatch
- In the isolated lab, change R3 to AS 200.
- Confirm the R2–R3 interface remains up/up.
- Compare
show ip protocolson both routers. - Restore AS 100 and prove routes return.
Expected result: You identify the routing-process mismatch without changing the IP address.
11. Frequently Asked Questions
Is EIGRP a distance-vector or link-state protocol?
EIGRP is commonly described as an advanced distance-vector protocol. It learns routes from neighbors but also keeps a topology table and uses DUAL to prove loop-free paths.
What must match for EIGRP neighbors to form?
In classic mode, the AS number and K-values must match. The connected interfaces also need compatible primary IP addressing, and any configured authentication must agree.
Do EIGRP Hello and hold timers have to match?
No. Each router tells its neighbor how long to keep the relationship without another Hello. Different timer values can work, although a consistent design is easier to operate.
Why is a feasible successor useful?
It is a backup path that DUAL has already proved loop-free. If the successor fails, EIGRP can use that backup without first asking every neighbor for a new route.
What does Passive mean in the topology table?
Passive is healthy. It means DUAL has finished calculating the route. Active means EIGRP is currently asking neighbors for another path.
What is the difference between D and D EX?
D marks an internal EIGRP route. D EX marks a route that entered EIGRP through redistribution from another routing source.
Can EIGRP use unequal-cost paths?
Yes. The variance command can allow qualified unequal-cost paths. The paths must still satisfy EIGRP's loop-free rules, so test the design before using it in production.