What Is Successor in Networking?

Think of a successor as your go-to person for a specific task. Imagine you need to get a package delivered across town. You have a list of couriers, each with a different delivery time. The successor is the courier that promises the fastest and most reliable service — the one you always hand the package to first. If that courier is unavailable, you have a backup courier (called a feasible successor) ready to step in without you having to call every courier again. In networking terms, a router maintains a routing table with all known destinations. For each destination, EIGRP picks one best path — the successor — and may have one or more backup paths ready. This ensures that if the primary router fails, traffic can be rerouted almost instantly. The successor is chosen based on something called the composite metric, which EIGRP calculates from bandwidth, delay, reliability, load, and MTU along the path. The successor path must also be loop-free, which is guaranteed by a condition called the feasibility condition. This is important because in a complex network, a router might receive information about a path that looks good but is actually a loop — EIGRP’s algorithm prevents that. The successor concept is central to EIGRP’s fast convergence, meaning the network recovers quickly from failures without losing data packets or causing slowdowns. For IT professionals, understanding successors helps in designing resilient networks that can handle outages without interruption.

In simpler terms, the successor is the router that gets your data first because it offers the shortest, safest path to the final destination. It’s like a highway’s express lane that gets you there fastest. If that lane is closed, EIGRP already has an alternative route ready, so traffic keeps flowing smoothly. This is why EIGRP is favored in many enterprise networks — it doesn’t waste time recalculating everything after a failure. The successor is always the best choice, but it’s not permanent; if network conditions change (like a link becomes slower), EIGRP recalculates and may pick a new successor. In exam questions, you will be asked to identify which route is the successor based on given metrics, or to determine whether a backup path qualifies as a feasible successor. Mastering this concept helps you understand how EIGRP keeps networks stable and efficient, which is a core skill for CCNA candidates.

In EIGRP (Enhanced Interior Gateway Routing Protocol), a successor is the next-hop router that satisfies the feasibility condition and has the lowest feasible distance (FD) for a given destination network. The successor is derived from the EIGRP Diffusing Update Algorithm (DUAL), which guarantees loop-free paths at every instant. The feasible distance (FD) is the metric of the best path known to the router for a specific destination, calculated using the EIGRP composite metric formula: Metric = [K1 * bandwidth + (K2 * bandwidth) / (256 - load) + K3 * delay] * (K5 / (reliability + K4)). By default, only K1 and K3 are used, simplifying to metric = bandwidth + delay. bandwidth is computed as (10^7 / minimum bandwidth along the path) * 256, and delay is the sum of all outgoing interface delays in tens of microseconds, multiplied by 256. The successor must have an advertised distance (AD) — the metric reported by the neighbor to the destination — that is strictly less than the local router’s FD. This is the feasibility condition (FC), which ensures the neighbor is closer to the destination and does not route back through the local router, thus preventing routing loops.

EIGRP maintains three tables: the neighbor table, the topology table, and the routing table. The topology table contains all routes learned from neighbors, each with a reported distance (AD) and the local feasible distance (FD). Routes that meet the feasibility condition are marked as feasible successors and are stored as backup routes. The route with the lowest FD is selected as the successor and placed into the routing table with the next-hop address of the successor router. If the successor becomes unreachable (due to link failure or neighbor loss), EIGRP immediately promotes the best feasible successor to the successor role, which is called a local computation. This happens without sending any queries, enabling sub-second convergence. If no feasible successor exists, the router enters active state and sends queries to all neighbors to find a new path, which is slower and requires careful design to avoid queries flooding.

In real IT implementation, EIGRP is deployed in Cisco networks for its fast convergence and low overhead. Network engineers configure EIGRP with a process ID and network statements on interfaces. The successor concept affects route summarization, load balancing (EIGRP supports unequal-cost load balancing via variance), and interaction with other protocols like OSPF. In CCNA exams, candidates must calculate metrics from given bandwidth and delay values to identify the successor, or analyze which path qualifies as a feasible successor. Understanding successor vs feasible successor is critical for troubleshooting EIGRP convergence issues and for designing networks that meet service-level agreements. EIGRP’s use of successor ensures that routing decisions are deterministic and based on solid mathematical foundations, making it a reliable choice for many organizations.

DUAL uses the successor as the primary path for all traffic. When a route changes, DUAL performs a diffusing computation only if needed. The successor might change after a topology change (e.g., a link speed change or a neighbor removal). The router recalculates the FD and selects a new successor from the topology table. This dynamic adjustment ensures the routing table always reflects the best possible path without administrative intervention. In summary, the successor is the backbone of EIGRP’s routing decision — it is the single best path that guarantees loop-free, efficient forwarding.

The concept of a successor is fundamental to EIGRP because it directly influences how quickly a network can recover from a failure. In enterprise networks, downtime costs money — every minute that a link is down can mean lost sales, reduced productivity, or even safety risks in critical systems. EIGRP’s successor mechanism ensures that there is always one best path (the successor) and that backup paths (feasible successors) are pre-computed and loop-free. This means that when a primary link fails, the router can switch to a backup within milliseconds, without having to recalculate routes from scratch or flood the network with query messages. For network administrators, this translates to high availability and predictable performance. Without the successor concept, routing protocols would need to run full SPF calculations (like OSPF) or send queries to all neighbors (like old EIGRP without DUAL), which can cause network instability and slower convergence.

Another reason the successor matters is that it helps manage network traffic efficiently. By always forwarding packets through the best path, the network uses its resources (bandwidth and router processing) optimally. EIGRP also supports unequal-cost load balancing, where you can configure a variance parameter to allow traffic to be distributed among multiple successors (if they meet certain conditions). This is useful when you have links of different speeds and want to use them all without overloading the fastest one. The successor concept also simplifies troubleshooting: if a route is not working, you can check the routing table to see which next-hop is the successor and whether a feasible successor is available. This gives you immediate insight into the network’s redundancy. Moreover, understanding successors is crucial for designing networks that meet service-level agreements (SLAs). If you have two links to an ISP, you can ensure that one is the successor and the other is a feasible successor, so that if the primary link fails, traffic fails over instantly without user impact.

In summary, the successor is not just an abstract concept; it is the practical tool that EIGRP uses to provide fast convergence, efficient routing, and network resilience. For anyone studying for CCNA, it is a core building block for understanding how dynamic routing works in real environments. When you configure EIGRP in a lab or at work, you are relying on this mechanism to keep your network running smoothly.

Exam questions about the successor typically fall into three main patterns: identification, computation, and troubleshooting.

Identification questions present you with a topology table or a routing table and ask you to point out the successor for a given destination network. For example, you might see output from ‘show ip eigrp topology 10.0.0.0/16’ showing multiple paths. One path has FD 409600, AD 281600. Another has FD 512000, AD 409600. A third has FD 281600? Wait, if FD is 281600, that is lower than 409600, so that would be the successor. But the trick is that you must check that the AD of the successor is less than the local FD (which it always is for the route installed as successor). The question might ask: ‘Which of the following is the successor for network 10.0.0.0/16?’ and you choose the entry with the lowest FD. Multiple-choice options might list the next-hop IP addresses along with their metrics. Another variation: ‘How many successors are there for 192.168.2.0/24?’ If the topology shows two routes with equal FD (same metric), they are both successors and EIGRP load balances across them (by default up to 4 equal-cost paths). So you must count the routes with the lowest FD.

Computation questions give you the bandwidth and delay of each link along a path. For example: ‘Router A has two paths to network 10.1.1.0/24. Path 1: Bandwidth 100000 Kbps, Delay 1000 microseconds. Path 2: Bandwidth 10000 Kbps, Delay 500 microseconds. Which path is the successor?’ You need to compute the metric using the formula: metric = (10^7/bandwidth in Kbps)*256 + (delay in tens of microseconds)*256. For Path 1: (10^7/100000)*256 = 100*256 = 25600. Delay 1000 microseconds = 100 tens of microseconds, so 100*256 = 25600. Total = 51200. For Path 2: (10^7/10000)*256 = 1000*256 = 256000. Delay 500 microseconds = 50 tens of microseconds, so 50*256 = 12800. Total = 268800. So Path 1 has the lower metric and is the successor. Sometimes they give you comparative values and ask you to select which neighbor would become the successor. These questions test your ability to apply the metric formula quickly.

Troubleshooting questions often present a scenario where the network is experiencing slow convergence after a link failure. The question might show the output of ‘show ip eigrp topology all-links’ and ask: ‘Why did EIGRP have to perform a query for network 10.0.0.0/8 after the failure of Router B?’ The answer would be that no feasible successor existed for that network because all alternative paths had an AD >= FD. Alternatively, you might see a show command output that lists active routes, and the question asks: ‘Which router is the successor for 10.0.0.0/8?’ You would need to look at the routing table entries and identify the one with the next-hop that has the lowest metric. Another common trap: the output shows a route that is listed as both successor and feasible successor? No, only one is the successor; others are feasible successors. But if a route meets the feasibility condition (AD < FD) but has a higher FD than the successor, it is a feasible successor, not a successor. Some questions deliberately confuse these terms. They might say ‘Which of the following is the feasible successor?’ and list the successor, expecting you to know the difference. So careful reading is required.

In practice, understanding the successor is essential for designing and troubleshooting EIGRP networks. When you configure EIGRP on a Cisco router, you will use commands like router eigrp [ASN], network [network] to enable the protocol. The router automatically discovers neighbors and builds the topology table. To see the successor for a specific network, you use show ip route eigrp or show ip eigrp topology. The output shows you the feasible distance (FD) and the next-hop router. For example, if you see 'D 10.0.0.0/16 [90/30720] via 192.168.1.1, 00:01:23, GigabitEthernet0/0', the successor is 192.168.1.1 with metric 30720. The 'D' indicates EIGRP, and the 90 is the administrative distance. The FD is 30720.

When testing redundancy, you might simulate a link failure by shutting down an interface. If a feasible successor exists, the routing table will update almost instantly, and you can verify with show ip route that the next-hop changed to the backup router. If there is no feasible successor, you will see the route go down temporarily as EIGRP sends queries and recalculates. This can be observed with debug eigrp or by timing the convergence.

Network professionals often need to influence which router becomes the successor. You can adjust the bandwidth or delay on interfaces to change the metric. For example, if you want to prefer a specific link, you can set a lower delay on that interface. Or to avoid a link, set a higher delay. This is called administrative metric manipulation. Another common practice is to use the 'variance' command to allow unequal-cost load balancing. For instance, if the successor's FD is 1000, and you set variance 2, any route whose FD is less than or equal to 2000 and that meets the feasibility condition can be used as a backup (load balancing). However, be careful: variance only applies to routes that are feasible successors, not just any route with a lower FD. The feasibility condition (AD < FD) must still hold.

What can go wrong? One common issue is that a feasible successor is not available because the AD of an alternative route is too high (equal to or greater than FD). This may happen if the alternative path includes a link that goes through the local router (forming a loop) or if the bandwidth/delay are very asymmetric. In such cases, convergence can be slow (active state). To fix this, you might redesign the network to ensure that backup paths have lower AD by adding faster links or adjusting routing so that the alternate neighbor has a better view of the destination. Another potential problem is that too many successors can cause routing instability if the metric fluctuates. EIGRP uses a holddown-like mechanism (but not exactly) to avoid flapping. Also, if you misconfigure the delay value (e.g., setting it too high), you might inadvertently make a slow path look better than a fast path, causing suboptimal routing.

In summary, mastering the successor concept in practice means you can control path selection, design for fast failover, and troubleshoot convergence issues. It's not just theory—it's a daily tool for network engineers.