EIGRP Routing Protocol Concepts
AI-Generated Content
EIGRP Routing Protocol Concepts
In modern enterprise networks, efficient and reliable routing is non-negotiable. While older protocols can be slow to adapt or prone to loops, the Enhanced Interior Gateway Routing Protocol (EIGRP) offers a powerful, Cisco-developed solution that blends the best of distance-vector and link-state behaviors. For your CCNA certification and real-world network engineering, mastering EIGRP is crucial because it forms the intelligent, fast-converging backbone of countless Cisco-centric networks, using a sophisticated algorithm to ensure speed without sacrificing stability.
EIGRP Fundamentals: The Advanced Distance-Vector Protocol
EIGRP is formally classified as an advanced distance-vector protocol, also called a hybrid routing protocol. This means it retains the simplicity of distance-vector protocols—where routers advertise their routing tables to directly connected neighbors—but incorporates key link-state characteristics. Unlike its predecessor IGRP, EIGRP sends incremental, bounded updates. It only sends routing information when a path changes, and only to routers that need that information, which drastically reduces network overhead. Furthermore, EIGRP uses Reliable Transport Protocol (RTP) to ensure delivery of these update packets, a feature absent in traditional distance-vector protocols like RIP.
A core differentiator is EIGRP’s ability to track multiple paths to a destination network. It doesn't simply choose the single best path and discard the rest. Instead, it uses the Diffusing Update Algorithm (DUAL) to maintain a topology table containing all learned routes. This table is separate from the routing table and is the key to EIGRP’s rapid convergence. From this topology table, DUAL selects the absolute best path to install into the routing table and can also identify backup paths that are immediately usable if the primary fails, eliminating the wait for new route calculations.
The DUAL Algorithm and Path Selection
The Diffusing Update Algorithm (DUAL) is the genius behind EIGRP’s loop-free and fast-converging operation. To understand DUAL, you must master three interrelated concepts: Feasible Distance, Reported Distance, and the Feasibility Condition.
The Feasible Distance (FD) is the total metric of the best path from your router to the destination network. It's your router's calculated cost. The Reported Distance (RD), also called the Advertised Distance, is the metric as reported by a neighboring router for its own path to that same destination. In essence, the RD is the neighbor's FD to the target.
DUAL uses these values to enforce a loop-prevention rule known as the Feasibility Condition: A path can be considered a viable backup only if the neighbor's RD for that path is less than your current FD. If this condition is true, the path is guaranteed to be loop-free. The best path, with the lowest FD, is called the Successor, and its route is installed in the routing table. Any backup path that meets the Feasibility Condition is called a Feasible Successor and is stored in the topology table. If a successor fails, a feasible successor can be promoted to the routing table instantly without triggering a full DUAL recomputation, which is the secret to EIGRP's fast convergence.
Metric Calculation: Bandwidth and Delay
EIGRP uses a composite metric to determine the best path. By default, it uses only bandwidth and delay of the links in the path. Reliability and load can be configured but are disabled by default. The composite metric formula is:
With the default K-values (K1=1, K3=1, K2=0, K4=0, K5=0), this complex formula simplifies dramatically to:
Here, is the slowest link (in kilobits per second) along the path, and is the sum of all interface delays (in tens of microseconds) along the path. You must calculate the bandwidth component using the slowest link. For example, a path with a 100 Mbps (100,000 Kbps) link and a 1.544 Mbps (1544 Kbps) T1 link uses 1544 for the . The delay is an interface attribute you can view with show interfaces. The result is a scalar value where a lower number is better. For the CCNA exam, you must be comfortable interpreting and comparing these calculated metrics.
Configuration and Verification for CCNA
Configuring basic EIGRP is straightforward, but verification commands reveal its inner workings. To enable EIGRP for Autonomous System (AS) 100 and advertise the 192.168.1.0/24 network connected to GigabitEthernet0/0, you would enter global configuration mode and use the following commands. Note the use of wildcard masks in the network statement.
Router(config)# router eigrp 100
Router(config-router)# network 192.168.1.0 0.0.0.255EIGRP will automatically advertise the network of any interface whose IP address falls within the range specified by the network command.
Verification is where your conceptual knowledge is tested. Key commands include:
-
show ip route eigrp: Displays EIGRP-learned routes in the routing table, indicating the successor path and its FD. -
show ip eigrp topology: This is critical. It shows the topology table, listing successors, feasible successors, the FD, and the RD for each path. A route with only a successor and no feasible successor will have the note "successor is the only path." -
show ip eigrp neighbors: Lists all adjacent EIGRP neighbors, their interface, and the hold timer. No neighbors mean no routing updates. -
show ip protocols: Summarizes the routing protocol configuration, including the AS number, K-values, and networks being advertised.
For the CCNA, expect scenario-based questions where you must interpret the output of these commands to determine why a route is missing, why a neighbor relationship failed, or which path DUAL will select as the successor.
Common Pitfalls
- Misunderstanding the Feasibility Condition: The most common conceptual error is confusing Feasible Distance and Reported Distance. Remember, for a path to be a feasible successor, the neighbor's Reported Distance must be less than your router's current Feasible Distance to the destination. If you compare the wrong values, you'll misinterpret the topology table and fail to identify available backup paths.
- Incorrect Wildcard Mask in Network Statements: EIGRP uses wildcard masks, not subnet masks, in its
networkcommands. A wildcard mask of0.0.0.255matches the first three octets exactly. Using a standard subnet mask like255.255.255.0is a syntax error and will prevent interfaces from being enabled for EIGRP. Always double-check this syntax in configuration questions.
- Autonomous System Mismatch: EIGRP neighbors must be configured with the same Autonomous System (AS) number to form an adjacency. A simple typo (e.g., AS 100 on one router and AS 101 on another) is a frequent cause of neighbor relationships failing to establish. Always verify with
show ip eigrp neighbors.
- Overlooking Bandwidth on Serial Interfaces: By default, Cisco serial interfaces have a bandwidth setting of 1.544 Mbps (T1). If this is not manually configured to match the actual contracted speed of a slower link (like a 512 Kbps connection), EIGRP will use the incorrect, overly optimistic bandwidth in its metric calculation. This can lead to suboptimal routing. The correct bandwidth should always be configured on WAN interfaces.
Summary
- EIGRP is an advanced distance-vector protocol that uses the DUAL algorithm for fast, loop-free convergence by maintaining a topology table of all learned routes.
- Path selection relies on the Feasible Distance (FD) and Reported Distance (RD). The best path is the Successor, and a valid backup is a Feasible Successor, which must meet the Feasibility Condition: RD < FD.
- The default composite metric is calculated using the lowest bandwidth and the total delay of the path, with the formula .
- Basic configuration involves enabling EIGRP with an AS number and using
networkstatements with wildcard masks. Mastery of verification commands likeshow ip eigrp topologyandshow ip eigrp neighborsis essential for the CCNA exam and real-world troubleshooting. - Avoid common mistakes like misapplying the Feasibility Condition, using subnet masks instead of wildcard masks, having AS mismatches, and neglecting to configure accurate bandwidth settings on serial interfaces.