EIGRP is fast to converge, easy to configure and still common in Cisco-based enterprise networks. In this lab you will configure EIGRP on th...
EIGRP is fast to converge, easy to configure and still common in Cisco-based enterprise networks. In this lab you will configure EIGRP on three routers in Packet Tracer, then spend most of your time on verification: reading the neighbor table, understanding the topology table, and recognizing successors and feasible successors. I will also show how the same configuration looks in EIGRP named mode, which you will meet on newer IOS.
EIGRP in a nutshell
EIGRP (Enhanced Interior Gateway Routing Protocol) is an advanced distance-vector protocol originally developed by Cisco and later published as RFC 7868. The points you need for this lab:
- Routers form neighbor relationships by sending hellos to multicast 224.0.0.10, every 5 seconds on LAN links. The default hold time is 15 seconds.
- Neighbors must share the same autonomous system (AS) number, the same K-values, and a common subnet.
- The DUAL algorithm calculates loop-free paths. The best path is the successor. A backup that is guaranteed loop-free is a feasible successor.
- The default metric uses bandwidth (lowest along the path) and delay (sum along the path).
- Administrative distance: 90 for internal routes, 170 for external (redistributed) routes.
Lab topology
Three 2911 routers connected in a triangle, each with its own LAN. All links are GigabitEthernet.
| Device | Interface | IP address | Connected to |
|---|---|---|---|
| R1 | G0/0 | 10.1.12.1/30 | R2 G0/0 |
| R1 | G0/1 | 10.1.13.1/30 | R3 G0/0 |
| R1 | G0/2 | 192.168.1.1/24 | LAN 1 |
| R2 | G0/0 | 10.1.12.2/30 | R1 G0/0 |
| R2 | G0/1 | 10.1.23.1/30 | R3 G0/1 |
| R2 | G0/2 | 192.168.2.1/24 | LAN 2 |
| R3 | G0/0 | 10.1.13.2/30 | R1 G0/1 |
| R3 | G0/1 | 10.1.23.2/30 | R2 G0/1 |
| R3 | G0/2 | 192.168.3.1/24 | LAN 3 |
| PC1 / PC2 / PC3 | NIC | 192.168.1.10 / 192.168.2.10 / 192.168.3.10 | Gateway is the .1 of each LAN |
EIGRP AS number: 100. Router IDs: 1.1.1.1, 2.2.2.2 and 3.3.3.3.
Configure all interface IP addresses and no shutdown first, and confirm with show ip interface brief that each router can ping its directly connected neighbors.
Step 1: Configure EIGRP (classic mode)
R1(config)# router eigrp 100
R1(config-router)# eigrp router-id 1.1.1.1
R1(config-router)# network 10.1.12.0 0.0.0.3
R1(config-router)# network 10.1.13.0 0.0.0.3
R1(config-router)# network 192.168.1.0 0.0.0.255
R1(config-router)# passive-interface gigabitEthernet0/2
R1(config-router)# no auto-summary
router eigrp 100starts EIGRP with AS 100. The number must match on all routers that should be neighbors.eigrp router-idsets a stable ID. Without it, the router picks the highest loopback address, or else the highest active interface address.networkwith a wildcard mask enables EIGRP on every interface whose address falls inside that range, and advertises the connected subnet. You can also writenetwork 10.0.0.0without a wildcard, which matches every 10.x.x.x interface; precise wildcards make your intent clear.passive-interfacestops hellos on the LAN, so no one can form an EIGRP neighbor from a user port, but the LAN subnet is still advertised.no auto-summaryprevents summarization at classful boundaries. Recent IOS releases disable auto-summary by default, but older releases and Packet Tracer may not, so I always type it.
R2(config)# router eigrp 100
R2(config-router)# eigrp router-id 2.2.2.2
R2(config-router)# network 10.1.12.0 0.0.0.3
R2(config-router)# network 10.1.23.0 0.0.0.3
R2(config-router)# network 192.168.2.0 0.0.0.255
R2(config-router)# passive-interface gigabitEthernet0/2
R2(config-router)# no auto-summary
R3(config)# router eigrp 100
R3(config-router)# eigrp router-id 3.3.3.3
R3(config-router)# network 10.1.13.0 0.0.0.3
R3(config-router)# network 10.1.23.0 0.0.0.3
R3(config-router)# network 192.168.3.0 0.0.0.255
R3(config-router)# passive-interface gigabitEthernet0/2
R3(config-router)# no auto-summary
As soon as a neighbor is found, IOS logs a message like this on R1:
%DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 10.1.12.2 (GigabitEthernet0/0) is up: new adjacency
%DUAL-5-NBRCHANGE: IP-EIGRP 100: Neighbor 10.1.13.2 (GigabitEthernet0/1) is up: new adjacency
Step 2: Verify neighbors
R1# show ip eigrp neighbors
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.1.12.2 Gig0/0 13 00:04:12 40 1000 0 9
1 10.1.13.2 Gig0/1 12 00:03:55 40 1000 0 11
| Column | Meaning |
|---|---|
| H | Order in which neighbors were learned |
| Address / Interface | Neighbor's IP and the local interface it was heard on |
| Hold | Seconds left before the neighbor is declared down; it counts down from 15 and resets with each hello, so it should stay between about 10 and 15 |
| Uptime | How long the adjacency has been up; if it keeps resetting, the neighbor is flapping |
| SRTT / RTO | Smooth round-trip time and retransmission timeout for reliable packets |
| Q Cnt | Packets waiting to be sent; should be 0 |
| Seq Num | Last sequence number received from that neighbor |
Newer IOS releases print the header as "EIGRP-IPv4 Neighbors for AS(100)".
Step 3: Verify the routing table
R1# show ip route eigrp
10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
D 10.1.23.0/30 [90/3072] via 10.1.12.2, 00:04:05, GigabitEthernet0/0
[90/3072] via 10.1.13.2, 00:04:05, GigabitEthernet0/1
D 192.168.2.0/24 [90/3072] via 10.1.12.2, 00:04:05, GigabitEthernet0/0
D 192.168.3.0/24 [90/3072] via 10.1.13.2, 00:03:50, GigabitEthernet0/1
"D" means EIGRP (from DUAL). [90/3072] is administrative distance 90 and metric 3072. Notice 10.1.23.0/30 has two equal-cost paths, so EIGRP installs both and load-shares.
Where does 3072 come from?
With default K-values, the classic metric is:
metric = 256 x ( 10^7 / lowest bandwidth in kbps + total delay in tens of microseconds )
For 192.168.2.0/24 via R2, the path uses R1 G0/0 and R2 G0/2. Both are GigabitEthernet: bandwidth 1,000,000 kbps and delay 10 microseconds each.
- Bandwidth part: 10,000,000 / 1,000,000 = 10
- Delay part: (10 + 10) / 10 = 2
- Metric: 256 x (10 + 2) = 3072
For R2 itself, the LAN is directly connected, so its metric is 256 x (10 + 1) = 2816. Keep that number in mind for the topology table.
Step 4: Verify the topology table
R1# show ip eigrp topology
IP-EIGRP Topology Table for AS 100/ID(1.1.1.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - Reply status
P 10.1.12.0/30, 1 successors, FD is 2816
via Connected, GigabitEthernet0/0
P 10.1.13.0/30, 1 successors, FD is 2816
via Connected, GigabitEthernet0/1
P 10.1.23.0/30, 2 successors, FD is 3072
via 10.1.12.2 (3072/2816), GigabitEthernet0/0
via 10.1.13.2 (3072/2816), GigabitEthernet0/1
P 192.168.1.0/24, 1 successors, FD is 2816
via Connected, GigabitEthernet0/2
P 192.168.2.0/24, 1 successors, FD is 3072
via 10.1.12.2 (3072/2816), GigabitEthernet0/0
P 192.168.3.0/24, 1 successors, FD is 3072
via 10.1.13.2 (3072/2816), GigabitEthernet0/1
How to read an entry:
- P = passive, meaning the route is stable. A (active) means the router is querying neighbors for a replacement path; a route stuck in active is a problem.
- FD (feasible distance) is this router's best metric to the destination.
- (3072/2816) is (metric through this neighbor / reported distance). The reported distance (RD), also called advertised distance, is the neighbor's own metric to the destination.
Why is there no feasible successor for 192.168.2.0/24?
Look at the path through R3. R3 reaches 192.168.2.0/24 via R2 with a metric of 3072, so R3's reported distance is 3072. R1's total metric via R3 would be 256 x (10 + 3) = 3328.
The feasibility condition says a backup path qualifies as a feasible successor only if its reported distance is strictly less than the current feasible distance. Here RD 3072 is equal to FD 3072, not less, so the R3 path is not a feasible successor and does not appear in the default output. If the R1–R2 link fails, R1 must go active and query its neighbors before using R3.
To see every path, including ones that fail the feasibility condition:
R1# show ip eigrp topology all-links
...output trimmed...
P 192.168.2.0/24, 1 successors, FD is 3072, serno 8
via 10.1.12.2 (3072/2816), GigabitEthernet0/0
via 10.1.13.2 (3328/3072), GigabitEthernet0/1
If your Packet Tracer version does not accept all-links, try it on IOSv in GNS3. The serial number (serno) will differ on your router.
Step 5: Other useful verification
R1# show ip protocols
Routing Protocol is "eigrp 100"
...output trimmed...
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 100
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.1.12.0/30
10.1.13.0/30
192.168.1.0
Passive Interface(s):
GigabitEthernet0/2
Routing Information Sources:
Gateway Distance Last Update
10.1.12.2 90 00:04:01
10.1.13.2 90 00:03:47
Distance: internal 90 external 170
This one command confirms the AS number, the K-values, auto-summary status, which networks are enabled, which interfaces are passive, and the administrative distances. Exact layout varies by IOS version. Also try show ip eigrp interfaces, which lists the interfaces running EIGRP and the number of peers on each; a passive interface does not appear there.
Finally, test end to end: ping 192.168.3.10 from PC1, and run tracert 192.168.2.10 to confirm the path goes through 10.1.12.2.
Named mode vs classic mode
Everything above is classic mode, configured under router eigrp <AS>. Newer IOS releases (15.x and later, including IOSv) also support named mode, which groups all EIGRP settings, including per-interface ones, under one hierarchy. Packet Tracer does not support named mode, so practice it in GNS3 with IOSv. The same R1 configuration in named mode:
R1(config)# router eigrp LAB
R1(config-router)# address-family ipv4 unicast autonomous-system 100
R1(config-router-af)# eigrp router-id 1.1.1.1
R1(config-router-af)# network 10.1.12.0 0.0.0.3
R1(config-router-af)# network 10.1.13.0 0.0.0.3
R1(config-router-af)# network 192.168.1.0 0.0.0.255
R1(config-router-af)# af-interface gigabitEthernet0/2
R1(config-router-af-interface)# passive-interface
R1(config-router-af-interface)# exit-af-interface
R1(config-router-af)# exit-address-family
| Item | Classic mode | Named mode |
|---|---|---|
| Entry command | router eigrp 100 | router eigrp LAB + address-family ipv4 unicast autonomous-system 100 |
| Interface settings | Spread across interface config | Under af-interface |
| IPv4 and IPv6 | Separate processes | Separate address families in one process |
| Metrics | 32-bit classic metric | 64-bit wide metrics, better for 10G and faster links |
The name (LAB) is only locally significant; the AS number is what must match between neighbors. Classic and named routers can be neighbors as long as AS and K-values match.
Prefer video? Watch more hands-on labs on the Technical Hakim YouTube channel.
Common mistakes
- AS number mismatch.
router eigrp 100on R1 androuter eigrp 10on R2 never form a neighbor, and there is no error message. Compare withshow ip protocols. - Wrong wildcard mask. Typing a subnet mask (255.255.255.252) instead of a wildcard (0.0.0.3) in the network command enables EIGRP on the wrong interfaces, or none.
- Passive interface on a transit link. If you make G0/0 passive by mistake, the R1–R2 adjacency disappears. Only LAN-facing interfaces should be passive.
- K-value mismatch. If someone changed
metric weightson one router, neighbors fail with a log message mentioning a K-value mismatch. - Subnet mismatch. Neighbors on different subnets (for example a /30 on one side and a /29 on the other) do not form an adjacency; IOS reports "not on common subnet".
- Auto-summary with discontiguous networks. With auto-summary on, two routers may both advertise 10.0.0.0/8 and traffic goes to the wrong place. Use
no auto-summary. - Forgetting to advertise the LAN. Neighbors are up but remote PCs cannot reach your LAN. Check that the LAN subnet is in a network statement.
Summary
You configured EIGRP AS 100 on three routers, made LAN interfaces passive, and verified the result with show ip eigrp neighbors, show ip route eigrp, show ip eigrp topology and show ip protocols. You calculated the metric by hand, saw equal-cost load sharing, and learned why a backup path is only a feasible successor when its reported distance is lower than the feasible distance. Finally, you saw how the same setup looks in named mode.
Related tutorials
- RIP vs EIGRP vs OSPF: Routing Protocols Compared (with Lab)
- OSPF Single-Area Configuration: Full Lab with Verification
- Static Routes vs Default Routes: When to Use Each (with Lab)
- How to Install and Set Up GNS3 on Windows: Beginner's Guide
Sources
- RFC 7868 – Cisco's Enhanced Interior Gateway Routing Protocol (EIGRP): https://www.rfc-editor.org/rfc/rfc7868
- Cisco IP Routing: EIGRP Configuration Guide – EIGRP Named Mode
- Cisco IOS IP Routing: EIGRP Command Reference
No comments