Hands-On Lab: Configuring Basic EIGRP Routing

This hands-on lab configures EIGRP between three routers using the network command, verifies neighbor relationships form, and confirms routes are exchanged, establishing the foundational EIGRP configuration workflow.

EIGRP Basic ConfigurationEIGRP Neighbor FormationEIGRP Route Verification

~3 دقیقه مطالعه · آخرین به‌روزرسانی ۳۱ شهریور ۱۴۰۵

Lab Objective

Configure EIGRP with a common autonomous system number on three routers, verify neighbor adjacencies form, and confirm each router learns routes to networks it is not directly connected to.

Lab Purpose

Basic EIGRP configuration establishes the foundational workflow that every more advanced EIGRP topic builds upon — matching AS numbers between routers is the single most critical requirement, since a mismatch silently prevents any neighbor relationship from forming at all.

Lab Topology

R1 ---- Serial0/0/0 ---- R2 ---- Serial0/0/1 ---- R3

R1: 10.10.10.1/30, LAN 192.168.10.0/24
R2: 10.10.10.2/30 and 10.20.20.1/30
R3: 10.20.20.2/30, LAN 192.168.30.0/24

EIGRP AS 100 to be used throughout

Task 1: Configure Basic Addressing

Configure all interfaces shown, including each router's LAN.

Task 2: Enable EIGRP on All Three Routers

Enable EIGRP AS 100 on all three routers, advertising the appropriate networks.

Task 3: Verify Neighbor Formation

Confirm EIGRP neighbor relationships form between R1-R2 and R2-R3.

Task 4: Verify Routes Are Learned

Confirm R1 has learned about R3's LAN via EIGRP, despite no direct connection.

Task 5: Verify End-to-End Connectivity

Confirm R1's LAN can reach R3's LAN.

Solution and Verification

R1(config)# interface serial0/0/0
R1(config-if)# ip address 10.10.10.1 255.255.255.252
R1(config-if)# no shutdown
R1(config-if)# exit
R1(config)# interface gigabitethernet0/0
R1(config-if)# ip address 192.168.10.1 255.255.255.0
R1(config-if)# no shutdown

R2(config)# interface serial0/0/0
R2(config-if)# ip address 10.10.10.2 255.255.255.252
R2(config-if)# clock rate 64000
R2(config-if)# no shutdown
R2(config-if)# exit
R2(config)# interface serial0/0/1
R2(config-if)# ip address 10.20.20.1 255.255.255.252
R2(config-if)# clock rate 64000
R2(config-if)# no shutdown

R3(config)# interface serial0/0/1
R3(config-if)# ip address 10.20.20.2 255.255.255.252
R3(config-if)# no shutdown
R3(config-if)# exit
R3(config)# interface gigabitethernet0/0
R3(config-if)# ip address 192.168.30.1 255.255.255.0
R3(config-if)# no shutdown

R1(config)# router eigrp 100
R1(config-router)# network 10.10.10.0 0.0.0.3
R1(config-router)# network 192.168.10.0
R1(config-router)# no auto-summary

R2(config)# router eigrp 100
R2(config-router)# network 10.10.10.0 0.0.0.3
R2(config-router)# network 10.20.20.0 0.0.0.3
R2(config-router)# no auto-summary

R3(config)# router eigrp 100
R3(config-router)# network 10.20.20.0 0.0.0.3
R3(config-router)# network 192.168.30.0
R3(config-router)# no auto-summary

R1# show ip eigrp neighbors

H   Address         Interface   Hold Uptime
0   10.10.10.2      Se0/0/0      13  00:02:14

R1# show ip route eigrp

D    10.20.20.0/30 [90/2681856] via 10.10.10.2, Serial0/0/0
D    192.168.30.0/24 [90/2707456] via 10.10.10.2, Serial0/0/0

R1# ping 192.168.30.1

!!!!!
Success rate is 100 percent (5/5)

Key Takeaway

The AS number in router eigrp 100 must match exactly between every router expected to form a neighbor relationship — unlike OSPF's process ID which is only locally significant, this value is exchanged and checked during EIGRP neighbor formation, making a typo here a common and easy-to-miss cause of neighbors that simply never appear.

نوشته و پژوهش‌شده توسط دکتر شاهین صیامی

مقالات مرتبط

Hands-On Lab: Final Comprehensive CCNP Troubleshooting Challenge (BGP, DMVPN, and QoS Integration)

This hands-on lab presents a complex multi-layer failure across an integrated BGP-over-DMVPN topology combined with QoS marking, requiring systematic diagnosis of a route reflector misconfiguration, an NHRP registration failure, and an incorrectly applied QoS policy simultaneously affecting the same network.

ادامه

Hands-On Lab: Configuring BGP over DMVPN

This hands-on lab runs iBGP as the routing protocol across the same DMVPN hub-and-spoke topology used in the two previous labs, configuring the hub as a route reflector so spokes learn each other's routes without a full iBGP mesh, combining two previously separate concepts into one integrated design.

ادامه

Hands-On Lab: Configuring OSPF over DMVPN

This hands-on lab runs OSPF as the dynamic routing protocol across the same DMVPN hub-and-spoke topology, configuring the tunnel interface as an OSPF point-to-multipoint network type to correctly handle the hub-and-spoke adjacency pattern without requiring the broadcast network type's DR/BDR election.

ادامه

Hands-On Lab: Configuring EIGRP over DMVPN

This hands-on lab runs EIGRP as the dynamic routing protocol across the DMVPN hub-and-spoke topology built in earlier labs, verifying neighbor relationships form correctly across the multipoint tunnel and routes propagate without requiring per-spoke static configuration on the hub.

ادامه

Hands-On Lab: Configuring HSRP MD5 Authentication

This hands-on lab configures MD5 authentication on an HSRP group, verifying two routers with matching authentication strings form a normal active/standby relationship while a router with a mismatched string is excluded from the group entirely.

ادامه

Hands-On Lab: Configuring Cisco Umbrella-Style DNS Security via DNS Forwarding Redirection

This hands-on lab configures a router to redirect all client DNS queries toward a security-focused DNS resolver using DNS forwarding interception, approximating cloud-delivered DNS security enforcement without requiring per-client configuration changes.

ادامه