Enhanced Interior Gateway Routing Protocol (EIGRP) is a sophisticated routing protocol developed by Cisco Systems. Diffusing Update Algorithm (DUAL) is the core algorithm used by EIGRP to ensure loop-free paths and rapid convergence. It allows EIGRP to find the best path (successor) and pre-calculate backup paths (feasible successors) to destinations. If the primary path fails, EIGRP can immediately switch to a feasible successor without recomputing the entire route, minimizing downtime. DUAL also supports Variable Length Subnet Masks (VLSMs).

EIGRP is considered an advanced distance-vector routing protocol, often referred to as a hybrid protocol because it incorporates features typically found in both distance-vector and link-state routing protocols.

Here are the key features of EIGRP:

• Hybrid nature and efficient updates: EIGRP combines the simplicity of distance-vector protocols (learning routes from neighbors) with the rapid convergence and loop-avoidance mechanisms typically associated with link-state protocols. Unlike traditional distance-vector protocols that send periodic full routing table updates, EIGRP sends partial and bounded updates. This means updates are sent only when a change occurs, and only the affected routes are sent to the routers that need the information, significantly reducing bandwidth consumption.

• Reliable Transport Protocol (RTP): EIGRP uses its own RTP to ensure the reliable and ordered delivery of EIGRP packets. It includes sequence and acknowledgment numbers for reliable communication.

• Multiple tables: EIGRP maintains three distinct tables to manage routing information:

  • Neighbor table: Stores information about directly connected EIGRP routers (neighbors) with whom adjacency has been formed. Neighbor relationships are established using Hello packets.

  • Topology table: Contains all learned routes to destinations within the autonomous system, including the best paths (successors) and backup paths (feasible successors).

  • Routing table: Contains the best path to each destination, selected from the topology table.

• Composite metric and support for multiple network layer protocols: EIGRP calculates its metric using a combination of factors: bandwidth, delay, reliability, and load. By default, only bandwidth and delay are used in the metric calculation, as load and reliability can be dynamic and cause frequent route recalculations. The metric formula incorporates "K values" which determine which factors are used and their impact. EIGRP supports routing for various network layer protocols, including IPv4, IPv6, IPX, and AppleTalk, through the use of Protocol Dependent Modules (PDMs).

• Load balancing and route summarization: EIGRP supports both equal-cost and unequal-cost load balancing. This allows traffic to be distributed across multiple paths to a destination, even if those paths have different costs, optimizing network resource utilization. EIGRP supports both manual and automatic route summarization, which helps reduce the size of routing tables and improves routing efficiency and scalability.

• Authentication: EIGRP can use authentication (e.g., MD5 or SHA-2) to secure routing updates between neighbors, enhancing network security.

• Stub routing: EIGRP supports stub routing, which is used to optimize routing in hub-and-spoke topologies. A stub router limits the amount of EIGRP traffic and queries it receives, improving network stability and reducing memory consumption.

• Classless routing: EIGRP is a classless routing protocol, meaning it supports Variable Length Subnet Masks (VLSM) and Classless Inter-Domain Routing (CIDR).

• Administrative Distance (AD) and Hop Count: EIGRP has a default administrative distance of 90 for internal routes and 170 for external routes, which influences route selection when multiple routing protocols are in use. While not directly used in metric calculation, EIGRP has a configurable maximum hop count (default 100, up to 255) that acts as a loop prevention mechanism.

EIGRP offers several advantages that make it suitable for large and complex networks:

• Interface-Based Configuration: Unlike EIGRP for IPv4, which uses the network command to include networks in the EIGRP process, EIGRP for IPv6 is configured directly on the interfaces where it needs to run. This means there is no "network" command in EIGRPv6. Instead, you enable EIGRPv6 on specific interfaces.

• No Global IPv6 Address Requirement: EIGRP for IPv6 can be configured on interfaces without requiring a global IPv6 address. It primarily uses IPv6 link-local addresses for neighbor discovery and communication.

• Router ID: An EIGRP for IPv6 instance requires an explicit or implicit router ID to function properly. This router ID is a 32-bit number, still represented in IPv4 dotted-decimal format (e.g., 1.1.1.1). If a router doesn't have an IPv4 address from which to derive a router ID, it must be manually configured.

• Multicast Address: EIGRP for IPv6 uses the IPv6 multicast address FF02::A for sending its messages (like Hello packets and updates), which is the IPv6 equivalent of the 224.0.0.10 multicast address used by EIGRP for IPv4.

• Source Addresses: EIGRP for IPv6 messages are sourced using the IPv6 link-local address of the exit interface, whereas EIGRP for IPv4 messages use the IPv4 address of the outbound interface.

• Differentiated Configuration: Although the underlying mechanisms like the Diffusing Update Algorithm (DUAL) and metric calculations are similar to EIGRP for IPv4, EIGRP for IPv6 is configured and managed separately.

Enhanced Interior Gateway Routing Protocol (EIGRP) for IPv6 is an adaptation of the original EIGRP designed to support IPv6 networks. While it retains many core functionalities and benefits of EIGRP for IPv4, it incorporates specific enhancements and operational differences to accommodate the IPv6 addressing scheme and its unique characteristics.

• Interface-Based Configuration: EIGRP for IPv6 is configured directly on the interfaces rather than using a global network command.

• Router ID: Requires an explicit or implicit 32-bit router ID, often in IPv4 dotted-decimal format, even in IPv6-only environments.

• Multicast Address: Uses the IPv6 multicast address FF02::A for sending messages, equivalent to 224.0.0.10 in IPv4.

• Source Addresses: EIGRP for IPv6 messages are sourced from the IPv6 link-local address of the exit interface.

• Similar DUAL and Metric Calculation: Both IPv4 and IPv6 versions use the same DUAL algorithm and composite metric calculation.

EIGRP Nonstop Forwarding (NSF) is a high-availability feature designed to minimize traffic disruption during planned or unplanned control plane outages on a router, such as a Route Processor (RP) switchover or restart. To achieve this, EIGRP NSF relies on two distinct roles or levels of support among the routers in the network: EIGRP NSF Capability and EIGRP NSF Awareness.

Routers that are EIGRP NSF Aware (also known as NSF-helpers) are the neighboring EIGRP routers that understand the NSF-specific signaling from an NSF-capable router. When an NSF-aware router detects that an NSF-capable neighbor is undergoing a restart, it does not immediately tear down the EIGRP adjacency, even though it stops receiving Hello packets.

Instead, the NSF-aware router continues to hold the routing information it received from the restarting (NSF-capable) router for a predefined "grace period." This prevents the routing

Cisco Confidential

adjacency from dropping and avoids a network-wide routing reconvergence, which would otherwise lead to traffic loss. During this grace period, the NSF-capable router rebuilds its routing tables and re-establishes full EIGRP adjacency with its NSF-aware neighbors. Once the restarting router has fully recovered and synchronized its routing information, normal EIGRP operations resume seamlessly.

In essence, EIGRP NSF Capability refers to the ability of a router to maintain forwarding during its own control plane disruption, while EIGRP NSF Awareness refers to the ability of its neighbors to assist in this process by maintaining the routing adjacency and not triggering a network-wide reconvergence. This cooperative mechanism ensures minimal downtime and continuous packet forwarding in the event of a control plane failure.

• Minimized Downtime: The primary benefit is the significant reduction in network unavailability and packet loss during control plane failures or planned maintenance.

  •

  Seamless Operation: Users experience uninterrupted service, as traffic continues to flow even when the routing intelligence is temporarily unavailable.

  •

  Improved Network Stability: By preventing routing adjacencies from dropping, NSF avoids widespread route recalculations across the network, contributing to overall stability.

EIGRP stub routing is a feature designed to improve network stability, reduce resource utilization (CPU, memory, bandwidth), and simplify network design, particularly in hub-and-spoke or branch office topologies. It is used to control the flow of EIGRP routing updates and queries within a network.

When a router is configured as an EIGRP stub, it signals to its EIGRP neighbors that it is a stub router. A stub router is typically a router at the edge of an EIGRP domain that does not have other EIGRP neighbors beyond itself in a particular direction. It is usually a spoke router in a hub-and-spoke topology, or a router connected to a single upstream router.

The primary reasons for implementing EIGRP stub routing are:

• Improved Network Stability: By limiting the propagation of EIGRP queries, stub routing helps to confine the scope of route recalculations during topology changes. This prevents "stuck-in-active" (SIA) issues and reduces the impact of network instability.

• Reduced Resource Utilization: Stub routers do not need to maintain a full EIGRP topology table of the entire network. This reduces their CPU and memory usage. Additionally, by controlling what updates are sent and received, it conserves bandwidth.

• Simplified Configuration: It simplifies the routing configuration on stub routers, as they only advertise a limited set of routes.

• Enhanced Security: By preventing transit traffic through a stub router, it can act as a security measure, ensuring that traffic only flows towards the hub.

EIGRPv6 Stub Routing is the implementation of the EIGRP stub routing feature specifically for IPv6 networks. The core principles and benefits remain the same as with EIGRP for IPv4 stub routing, but adapted for the IPv6 addressing and operational context.

EIGRPv6 Stub Routing is used to improve network stability, reduce resource utilization (CPU, memory, bandwidth), and simplify the configuration of stub routers in an IPv6 EIGRP domain. A stub router is typically an edge device in a hub-and-spoke or branch office topology. It's usually a router that has only one or a few paths out of its local network segment, and it's not intended to be a transit point for traffic between other EIGRP peers.

In the given figure Switch B is configured as an EIGRPv6 stub router. Switches A and C are connected to the wider WAN. In this setup:

• Switch B advertises its connected, static, redistribution, and summary routes to Switches A and C.

• Conversely, Switch B does not advertise any routes that it learns from Switch A (and vice-versa). This ensures that Switch B only injects its local routes into the EIGRP domain and does not act as a transit router for routes learned from other EIGRP neighbors.

• Enhanced Stability: Prevents EIGRPv6 queries from propagating into the stub network, mitigating "Stuck In Active" (SIA) conditions and localizing the impact of topology changes. This is crucial for maintaining network uptime.

• Reduced Resource Consumption: Less memory and CPU are required on the stub router because it doesn't need to process or store a full EIGRPv6 topology table. Less bandwidth is consumed on the links to the stub, as fewer updates and no queries are sent.

• Simplified Design and Management: Streamlines the routing design for edge networks and simplifies the configuration on the stub devices.

• Optimized for Hub-and-Spoke: Ideal for IPv6 hub-and-spoke deployments, where spoke routers typically only need a default route (or a few specific routes) to reach the rest of the network.