Route 2 Eigrp Implementingeigrp

CCNP ROUTE
Chapter 2: Implementing EIGRP

Basic EIGRP
Types of Routing Protocols
Exterior
Gateway
Interior Gateway Protocols Protocols
Distance Vector Link State Path Vector
Distance Vector Routing Link State Routing Path Vector
Protocols Protocols
IPv4 RIPv2 EIGRP OSPFv2 IS-IS BGP-4
RIPng EIGRP for OSPFv3 * IS-IS for BGP-4 for
IPv6 IPv6 IPv6 IPv6 or
MP-BGP
* OSPFv3 supports routing both IPv4 and IPv6.
3
EIGRP Capabilities and Attributes
 EIGRP formerly known as Cisco-proprietary distance-vector protocol with link-state
features.
 On May 2016 EIGRP Become Standard based on RFC-7868
 EIGRP features include:
• Fast convergence
• Partial updates
• Multiple network layer support
• Use of multicast and unicast communication
• Variable-length subnet masking (VLSM) support
• Seamless connectivity across all data link layer protocols and topologies
• By default, it performs automatic route summarization at major network
boundaries (can be disabled) but can also be configured to summarize on
interfaces.
EIGRP Terminology
 Neighbor table
 Topology table
 Routing table
 Advertised Distance (AD)
 Feasible Distance (FD)
 Successor
 Feasible successor (FS)
 Passive Versus Active Routes
EIGRP Tables
 Neighbor table
 Contains EIGRP neighbor addresses and the interface through
which they can be reached.
 Topology table
 Contains all destinations advertised by neighboring routers.
 Routing table
 Contains EIGRP successor routes.
AD versus FD
 Advertised Distance (AD)
 Advertised distance (AD), also referred to as the Reported
Distance, is the cost between the next-hop router and the
destination.
 Feasible Distance (FD)
 Feasible distance (FD) is the cost between the local router and the
next-hop router plus the next-hop router’s AD to the destination
network.
Successor and Feasible Successor
 Successor
 A successor is a neighboring router that has a least-cost path to a destination
(the lowest FD) that is guaranteed not to be part of a routing loop.
 Successor routes are offered to the routing table to be used for forwarding
packets.
 Multiple successors can exist if they have the same FD.
 Feasible successor (FS)
 A feasible successor is a neighbor that is closer to the destination, but it is not
the least-cost path.
 A feasible successor ensures a loop-free topology because it must have an AD
less than the FD of the current successor route.
 Feasible successors are selected at the same time as successors but are kept
in the topology table as backups to the successor routes.
 The topology table can maintain multiple feasible successors for a destination.
Passive versus Active Routes
 Passive Route
 A route is considered passive when the router is not performing
recomputation on that route.
 Passive is the operational, stable state.
 Active route
 A route is active when it is undergoing recomputation.
Key EIGRP Technologies
 Reliable Transport Protocol (RTP)
 Responsible for guaranteed, ordered delivery of EIGRP packets to all
neighbors.
 Neighbor discovery/recovery mechanism
 Enables EIGRP routers to dynamically learn when their neighbors become
unreachable or inoperative by periodically sending small hello packets.
 Protocol-dependent modules (PDMs)
 Responsible for network layer protocol-specific requirements such as IP, IPv6,
AppleTalk, and Novell NetWare.
 DUAL finite-state machine
 Diffusing Update Algorithm (DUAL) is the routing algorithm that tracks all
routes advertised by all neighbors and uses distance information, known as the
composite metric, to select efficient, loop-free paths to all destinations.
Reliable Transport Protocol
 EIGRP cannot use the services of UDP or TCP since IPX and
Appletalk do not use the TCP/IP protocol suite.
 Reliable Transport Protocol (RTP) is the Transport layer protocol
uniquely used by EIGRP for the delivery and reception of EIGRP
packets.
 RTP is similar to TCP but is a Cisco proprietary.
 RTP provides reliable or unreliable service as the situation warrants.
 Reliable packets (Update, Query, Reply) require explicit
acknowledgement while unreliable packets (Hello, ACK) do not.
Neighbor Discovery / Recovery
 EIGRP routers actively establish relationships with their neighbors.
 Adjacencies are established using small Hello packets which are sent
every 5 or 60 seconds.
 If a neighbor misses 3 consecutive Hello packets then the route is
considered invalid.
 Default = 15 seconds or 180 seconds.
Neighbor Discovery / Recovery
Protocol-Dependent Modules
 Various routed protocols are supported through its PDMs.
 Provides independence from routed protocols.
 PDMs are modular, scalable and adaptable.
 EIGRP can adapt to new or revised routed protocols.
 PDMs protect EIGRP from painstaking revision.
 Each PDM is responsible for all functions related to its specific routed
protocol.
Protocol-Dependent Modules
EIGRP maintains individual

tables for each routed
protocol.
/24
Topology
/24
/24
Initial Config – R1
interface GigabitEthernet0/0
ip address 172.16.1.1 255.255.255.0
!
interface Serial0/0/0
description R1-->R2
bandwidth 64
ip address 10.1.102.1 255.255.255.248
clock rate 64000
!
description R1-->R3
bandwidth 1544
ip address 10.1.103.1 255.255.255.248
17
ip address 172.16.2.1 255.255.255.0
!
description R2-->R1
bandwidth 64
ip address 10.1.102.2 255.255.255.248
!
description R2-->R3
bandwidth 1024
ip address 10.1.203.2 255.255.255.248
clock rate 64000
18
ip address 172.16.3.1 255.255.255.0
!
description R3-->R1
bandwidth 1544
ip address 10.1.103.3 255.255.255.248
clock rate 64000
!
description R3-->R2
bandwidth 1024
ip address 10.1.203.3 255.255.255.248
19
Configuring Basic EIGRP
R1(config)# router eigrp 1
R1(config-router)# network 172.16.0.0
R1(config-router)#

R2(config-router)#
/29 255.255.255.248
R3(config)# router eigrp 1 255.255.255.255

R3(config-router)# network 172.16.3.0 0.0.0.255 - 255.255.255.248
R3(config-router)# network 10.1.103.0 0.0.0.7 ------------------
R3(config-router)# network 10.1.203.0 0.0.0.7 0. 0. 0. 7
R3(config-router)#
20
EIGRP Router ID
R1(config-router)# eigrp router-id 1.1.1.1


*Feb 1 20:00:37.883: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor
10.1.103.1 (Serial0/0/0) is down: route configuration changed
*Feb 1 20:00:42.279: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor
10.1.103.1 (Serial0/0/0) is up: new adjacency 21
EIGRP Packets
 IP EIGRP relies on 5 types of packets to maintain its various tables and
establish complex relationships with neighbor routers.
Packet Type Description
Hello Used to discover other EIGRP routers in the network.
Acknowledgement Used to acknowledge the receipt of any EIGRP packet.
Update Convey routing information to known destinations.
Query Used to get specific information from a neighbor router.
Reply Used to respond to a query.

22
EIGRP Hello Packets
 Hello packets are used to discover & form adjacencies with neighbors.
 Multicasted to:
 IPv4: 224.0.0.10
 IPv6: FF02::A
 Hello packets are always sent unreliably.
 Therefore Hello packets do not require acknowledgment. 23
EIGRP Neighbors Amount of time since this neighbor
was added to the neighbor table.
R2# show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 10.1.203.3 Se0/0/1 10 00:03:15 28 168 0 19
0 10.1.102.1 Se0/0/0 12 00:13:22 23 2340 0 46
R2#
The local
Neighbor’s interface Seconds remaining
IPv4 receiving before declaring
address EIGRP Hello neighbor down.
packets. Reset to hold time
when Hello is
received.
24
EIGRP Interfaces
R2# show ip eigrp interfaces
EIGRP-IPv4 Interfaces for AS(1)
Xmit Queue PeerQ Mean Pacing Time Multicast Pending
Interface Peers Un/Reliable Un/Reliable SRTT Un/Reliable Flow Timer Routes
Se0/0/0 1 0/0 0/0 23 10/390 478 0
Se0/0/1 1 0/0 0/0 28 0/23 139 0
Gi0/0 0 0/0 0/0 0 0/0 0 0
R2#
25
EIGRP Interfaces
R2# show ip eigrp interfaces detail
Se0/0/0 1 0/0 0/0 23 10/390 478 0
Hello-interval is 5, Hold-time is 15
Split-horizon is enabled
Next xmit serial <none>
Packetized sent/expedited: 20/0
Hello's sent/expedited: 2186/4
Un/reliable mcasts: 0/0 Un/reliable ucasts: 23/23
Mcast exceptions: 0 CR packets: 0 ACKs suppressed: 0
Retransmissions sent: 0 Out-of-sequence rcvd: 1
Topology-ids on interface - 0
Authentication mode is not set
<rest of output omitted>
26
IPv4 Routing Protocols
R2# show ip protocols
*** IP Routing is NSF aware ***
Routing Protocol is "application"

Sending updates every 0 seconds
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Maximum path: 32
Routing for Networks:
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 4)
<continued next slide>
27
Routing Protocol is "eigrp 1"
IPv4 Routing Protocols EIGRP Process ID
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP-IPv4 Protocol for AS(1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 2.2.2.2 EIGRP Router ID
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170 Hopcount is not a metric
Maximum path: 4
Maximum hopcount 100 Variance – For unequal cost load
Maximum metric variance 1 balancing
Automatic Summarization: disabled Starting with 15.0 no auto-
Maximum path: 4
Routing for Networks: summary is the default
10.0.0.0
172.16.0.0
network statements
10.1.102.1 90 00:23:27 neighbors
10.1.203.3 90 00:23:28
Distance: internal 90 external 170
28
R2#
Routing Protocol is "eigrp 1"
IPv4 Routing Protocols
Default networks flagged in outgoing updates
EIGRP Composite
Default networks accepted from incoming updates
EIGRP-IPv4 Protocol for AS(1)
Metric Formula
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID:
METRIC 2.2.2.2
= ( [K1 x Bandwidth + (K2 x Bandwidth) / (256-load) + K3 x Delay] x [K5 / (Reliability + K4] ) x 256
Topology : 0 (base)
METRIC = ( Timer:
Active [1 x Bandwidth
3 min + (0 x Bandwidth) / (256-load) + 1 x Delay] x [0 / (Reliability + 0] ) x 256
METRIC = (1 path:
Maximum x Bandwidth
4 + 1 x Delay) x 256
Maximum hopcount 100
Maximum metric variance 1
NOTE:
Automatic Summarization: disabled
Maximum path:• 4The multiplication by 256 is a legacy feature to maintain
backwards compatibility with IGRP.
10.0.0.0
172.16.0.0
10.1.102.1 90 00:23:27
10.1.203.3 90 00:23:28
29
R2#
EIGRP Wide Metrics
 The EIGRP composite cost metric does not scale correctly for high-bandwidth
interfaces or Ethernet channels, resulting in incorrect or inconsistent routing
behavior.
 The lowest delay that can be configured for an interface is 10 microseconds.
 As a result, high-speed interfaces, such as 10 Gigabit Ethernet (GE) interfaces,
or high-speed interfaces channeled together (GE ether channel) will appear to
EIGRP as a single GE interface.
 To resolve this issue, the EIGRP Wide Metrics feature supports 64-bit metric
calculations
 The 64-bit metric calculations work only in EIGRP named mode configurations.
30
Configuring Passive Interfaces X

R1(config-router)# passive-interface
g0/0
R2(config)# router eigrp 1 X X

g0/0

g0/0
31
EIGRP Interfaces after Passive
R2# show ip eigrp interfaces
Se0/0/0 1 0/0 0/0 23 10/390 478 0
Se0/0/1 1 0/0 0/0 28 0/23 139 0
R2#
R2# show ip protocols
<selected output>
Routing Protocol is "eigrp 1”
Passive Interface(s):
GigabitEthernet0/0

10.0.0.0
172.16.0.0
R2# 32
Observing Hello Packets
R1(config)# interface serial 0/0/0
R1(config-if)# no ip address
R1(config-if)#
X
*Feb 1 21:34:02.926: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.102.2 (Serial0/0/0) is down:
interface down
R1(config-if)#
-------------------------------------------------------------------------------------------------
-
R2# debug eigrp packets hello
(HELLO)
EIGRP Packet debugging is on
R2#
*Feb 1 21:28:40.602: EIGRP: Received HELLO on Se0/0/0 - paklen 20 nbr 10.1.102.1
*Feb 1 21:28:41.062: EIGRP: Sending HELLO on Se0/0/0 - paklen 20
*Feb 1 21:28:41.062: AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
holding time expired
R2#
 Shutdown on a serial link in a lab environment does not work because it brings down
33
both ends of the link
EIGRP Neighbors w/ Differing Timers 5/15
5/15
R2# show ip eigrp interfaces detail serial 0/0/0
Se0/0/0 1 0/0 0/0 68 10/390 390 0
<>
----------------------------------------------------------------------------------------
Se0/0/0 1 0/0 0/0 1290 10/390 6826 0
<>
R1#show ip eigrp neighbors
(sec) (ms) Cnt Num
0 10.1.102.2 Se0/0/0 11 00:03:36 28 2340 0 26 34
<>
EIGRP Neighbors w/ Differing Timers 5/15

10/30
R1(config-if)# ip hello-interval eigrp 1 10
R1(config-if)# ip hold-time eigrp 1 30
R1(config-if)# end
R1#
Se0/0/0 1 0/0 0/0 1290 10/390 6826 0
<>
R1# show ip eigrp neighbors
(sec) (ms) Cnt Num
0 10.1.102.2 Se0/0/0 12 00:25:47 1290 5000 0 54
35
Initial
Route
Discovery
Observing EIGRP
R3# debug eigrp packet
R3# conf t
R3(config-router)# network 10.1.203.0 0.0.0.7
*Feb 1 22:06:45.698: EIGRP: Received HELLO on Se0/0/1 - paklen 30 nbr 10.1.203.2
*Feb 1 22:06:45.698: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.203.2 (Serial0/0/1) is up:
new adjacency
*Feb 1 22:06:45.698: *Feb 1 22:06:45.698: EIGRP: Enqueueing UPDATE on Se0/0/1 - paklen 0 nbr
10.1.203.2 tid 0 iidbQ un/rely 0/1 peerQ un/rely 0/0
*Feb 1 22:06:45.706: EIGRP: Sending UPDATE on Se0/0/1 - paklen 0 nbr 10.1.203.2 tid 0
*Feb 1 22:06:45.706: AS 1, Flags 0x1:(INIT), Seq 63/0 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ
un/rely 0/1
*Feb 1 22:06:47.770: EIGRP: Received UPDATE on Se0/0/1 - paklen 222 nbr 10.1.203.2
*Feb 1 22:06:47.770: AS 1, Flags 0x0:(NULL), Seq 64/63 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ
un/rely 0/1
*Feb 1 22:06:47.770: EIGRP: Enqueueing ACK on Se0/0/1 - paklen 0 nbr 10.1.203.2 tid 0
*Feb 1 22:06:47.770: Ack seq 64 iidbQ un/rely 0/0 peerQ un/rely 1/1
*Feb 1 22:06:47.774: EIGRP: Sending ACK on Se0/0/1 - paklen 0 nbr 10.1.203.2 tid 0
un/rely 1/1
*Feb 1 22:06:47.778: EIGRP: Received ACK on Se0/0/1 - paklen 0 nbr 10.1.203.2
un/rely 0/1 37
Observing EIGRP
R3# show ip eigrp traffic

EIGRP-IPv4 Traffic Statistics for AS(1)
Hellos sent/received: 8319/6103
Updates sent/received: 48/43
Queries sent/received: 5/9
Replies sent/received: 9/5
Acks sent/received: 51/57
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 145
PDM Process ID: 106
Socket Queue: 0/10000/2/0 (current/max/highest/drops)
Input Queue: 0/2000/2/0 (current/max/highest/drops)
R3# 38
IPv4 Routing Table – EIGRP Routes
The EIGRP World from R2’s Distance Vector Perspective
R2# show ip route eigrp

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
<output omitted>
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

D 10.1.103.0/29 [90/3523840] via 10.1.203.3, 00:58:05, Serial0/0/1
D 172.16.1.0/24 [90/3526400] via 10.1.203.3, 00:58:05, Serial0/0/1
D 172.16.3.0/24 [90/3014400] via 10.1.203.3, 00:58:05, Serial0/0/1
R2# 39
DUAL Concepts
 Diffusing Update Algorithm is the algorithm used by EIGRP.
 Determines:
 Best loop-free path
 Loop-free backup paths (which can be used immediately)
 DUAL also provides the following:
 Fast convergence
 Minimum bandwidth usage with bounded updates
 DUAL uses several terms that are discussed in more detail throughout this
section:
 Successor
 Feasible distance
 Feasible successor
 Reported distance or advertised distance
 Feasible condition or feasibility condition 40
I can get to 10.0.0.0/8 I can get to
10.0.0.0/8 with a 10.0.0.0/8 with a
metric of 300. metric of 100.
RX
R2 R3
I will choose R3 to
get to 10.0.0.0/8
RA R1 which means I
have a cost of 120.
Is R2 a valid back
RB up?
No, because it comes back through me
R1 (loop). It only knows this route
because of me.
41
I can get to 10.0.0.0/8 I can get to
10.0.0.0/8 with a 10.0.0.0/8 with a
metric of 300. metric of 100.
RX
RB
R2 R3
I will choose R3 to
get to 10.0.0.0/8
RA R1 which means I
have a cost of 120.
Is R2 a valid back
up?
Yes, because it has its own
path to 10.0.0.0/8. (no loop)
42
I can only use R2 as a
backup if it reports a
cost less than my total
cost through R3.
 EIGRP is a distance vector routing

protocol.
 Does not see any topology map.
 Can’t tell if there is a loop or not?
 To play it safe, EIGRP only accepts a
backup route if it meets the Feasibility
Condition (coming).
 R1 will only use R2 if R2’s metric to
10.0.0.0/8 is less than R1’s cost
through R3. 43
R2’s EIGRP Topology Table
R2# show ip eigrp topology
EIGRP-IPv4 Topology Table for AS(1)/ID(2.2.2.2)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 10.1.102.0/29, 1 successors, FD is 40512000

via Connected, Serial0/0/0
via Connected, GigabitEthernet0/0
via 10.1.203.3 (3523840/2169856), Serial0/0/1
via 10.1.102.1 (41024000/2169856), Serial0/0/0
via 10.1.203.3 (3014400/28160), Serial0/0/1
via 10.1.102.1 (41026560/2172416), Serial0/0/0
via 10.1.203.3 (3526400/2172416), Serial0/0/1
via 10.1.102.1 (40514560/28160), Serial0/0/0
44
R2#
The Successor
P 172.16.3.0/24, 1 successors, FD is 3014400 R3: Successor

via 10.1.203.3 (3014400/28160), Serial0/0/1
via 10.1.102.1 (41026560/2172416), Serial0/0/0
Outbound interface to
reach this network
Next hop Feasible distance
address of
the successor Successor’s (R3’s)
Reported Distance
Successor
45
The Feasible Successor

R2#The reported
show distance
ip eigrp - EIGRP neighbor’s FD to the same destination network.
topology
 The metric that a router reports to a neighbor about its own cost to that network.
 Feasibility Condition:
P 172.16.3.0/24, The FC is met when
1 successors, FD isa neighbor’s
3014400 reported distance (RD)
to a network is less than the(3014400/28160),
local router’s FD to the R1: Feasible
same destination network.
via 10.1.203.3 Serial0/0/1 Successor
via 10.1.102.1 (41026560/2172416), Serial0/0/0
reach this network
R2’s feasible R1’s (feasible
Next hop
distance if R1 successor)
address of
becomes the Reported
the Feasible
Successor. Distance to R2
Successor
This would the Feasible
metric in R2’s Successor
routing table via
R1. 46
Why is R1 a Feasible Successor?

via 10.1.203.3 (3014400/28160), Serial0/0/1 R3: Successor
via 10.1.102.1 (41026560/2172416), Serial0/0/0 R1: Feasible
Successor
Feasibility Condition:
R1’s Reported Distance is less than
R2’s Feasible Distance via R3, so
R1 is a Feasible Successor.
 A Feasible Successor is a neighbor who has a Feasible
loop-free backup path to the same network as the
successor by satisfying the feasibility condition.
Successor
 Can become new successor with no packets lost.
47
Why is R1 a Feasible Successor?

via 10.1.102.1 (41026560/2172416), Serial0/0/0 R1: Feasible
Successor
My current metric (feasible distance)

3,014,400. If current best path to 172.16.3.0
becomes unavailable you will become my
successor with a (feasible distance) of
41,026,560 (slower bw and additional delay)
My cost to 172.16.3.0 is 2,172,416. If this is Successor

less than your current metric (feasible
distance) then I am a feasible successor.
Feasible Successor 48
Using a Feasible Successor?
My new successor is R1 with a
metric (feasible distance) of X
41,026,560
I’m the new successor

R2(config-if)# shutdown
R2(config-if)# end
*Feb 1 23:51:54.218: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.203.3
(Serial0/0/1) is down: interface down R2 immediately uses Feasible
<> Successor from EIGRP Topology Table
via 10.1.102.1 (41026560/2172416), Serial0/0/0

<>
D 172.16.3.0/24 [90/41026560] via 10.1.102.1, 00:00:22, Serial0/0/0
R2#
49
Back to normal
Feasible
Successor Successor
R2(config-if)# no shutdown
R2(config-if)# end
*Feb 2 00:02:59.422: %LINK-3-UPDOWN: Interface Serial0/0/1, changed state to up
(Serial0/0/1) is up: new adjacency

<>
D 172.16.3.0/24 [90/3014400] via 10.1.203.3, 00:00:09, Serial0/0/1
R2#
50
IPv4 Routing Table – EIGRP Routes
The EIGRP World from R1’s Distance Vector Perspective

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
<output omitted>
Gateway of last resort is not set

D 10.1.203.0/29 [90/3523840] via 10.1.103.3, 00:07:11, Serial0/0/1
D 172.16.2.0/24 [90/3526400] via 10.1.103.3, 00:07:09, Serial0/0/1
D 172.16.3.0/24 [90/2172416] via 10.1.103.3, 00:07:09, Serial0/0/1
R1# 51
R1’s EIGRP Topology Table
EIGRP-IPv4 Topology Table for AS(1)/ID(1.1.1.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

via 10.1.103.3 (3526400/3014400), Serial0/0/1
via 10.1.102.2 (40514560/28160), Serial0/0/0
via 10.1.103.3 (2172416/28160), Serial0/0/1
via 10.1.103.3 (3523840/3011840), Serial0/0/1
via 10.1.102.2 (41024000/3011840), Serial0/0/0
via Connected, GigabitEthernet0/0
R1#
52
The Successor
P 172.16.3.0/24, 1 successors, FD is 2172416 R3: Successor

via 10.1.103.3 (2172416/28160), Serial0/0/1
reach this network
Next hop Feasible distance
address of
the successor Successor’s (R3’s)
Reported Distance
 NO feasible successor
 To be a feasible successor, R2 must satisfy the
Feasibility Condition.
53
Why is R2 is NOT a Feasible Successor?
R1# show ip eigrp topology all-links
P 172.16.3.0/24, 1 successors, FD is 2172416, serno 23

via 10.1.102.2 (41026560/3014400), Serial0/0/0 R2: NOT
Feasible
Successor
Feasibility Condition:
R2’s Reported Distance is NOT less
than R1’s Feasible Distance via R3,
so R2 is NOT a Feasible Successor.
 Does this mean R2 cannot be used if the current
best path fails?
 No, R2 can be used, but there will be a longer delay
before adding it to the routing table.
 DUAL will need to find (Query) R2 to see if it has a 54
DUAL: An Introduction R2 sends updates out all interfaces
Not shown
X
55
Observing EIGRP
Reply Query
R1# debug eigrp fsm
EIGRP Finite State Machine debugging is on
Query
R1# conf t Reply
Enter configuration commands, one per line. End with CNTL/Z.
R1(config-if)# shutdown
X
interface down
*Feb 2 00:38:10.086: DUAL: Destination 172.16.3.0/24 for tid 0
*Feb 2 00:38:10.086: EIGRP-IPv4(1): Find FS for dest 172.16.3.0/24. FD is 2172416, RD is 2172416
on tid 0
*Feb 2 00:38:10.086: DUAL: AS(1) Dest 172.16.3.0/24 entering active state for tid 0.
*Feb 2 00:38:10.086: EIGRP-IPv4(1): Set reply-status table. Count is 1.
*Feb 2 00:38:10.554: DUAL: AS(1) Removing dest 172.16.3.0/24, nexthop 10.1.103.3
*Feb 2 00:38:10.554: EIGRP-IPv4(1): rcvreply: 172.16.3.0/24 via 10.1.102.2 metric
41026560/3014400 for tid
*Feb 2 00:38:10.554: EIGRP-IPv4(1): Find FS for dest 172.16.3.0/24. FD is 72057594037927935, RD
is 72057594037927935 on tid 0found
*Feb 2 00:38:10.554: DUAL: AS(1) Removing dest 172.16.3.0/24, nexthop 10.1.103.3
*Feb 2 00:38:10.554: DUAL: AS(1) RT installed 172.16.3.0/24 via 10.1.102.2
*Feb 2 00:38:10.554: DUAL: AS(1) Send update about 172.16.3.0/24. Reason: metric chg on tid 0
56
New Route I’m the new successor
My new successor is R2 with a

metric (feasible distance) of
41,026,560. I don’t have a feasible
successor.
R1# show ip eigrp topology X
<>
via 10.1.102.2 (41026560/3014400), Serial0/0/0
R1#
<>
D 172.16.3.0/24 [90/41026560] via 10.1.102.2, 00:14:08, Serial0/0/0

R1
57
Back to normal

R1(config-if)# no shutdown
58
R1(config-if)# end
(Serial0/0/1) is up: new adjacency
R1#
<>
R1# via 10.1.103.3 (2172416/28160), Serial0/0/1

<>
D 172.16.3.0/24 [90/2172416] via 10.1.103.3, 00:00:13, Serial0/0/1
R1# 58
EIGRP Queries, Stub Routing,
Summarization
59
EIGRP Queries
Router
Queries B
Replies
Router
A
X
X
n When there is no feasible successor DUAL puts the route into Active
(topology table) and sends queries to neighbors looking for another path.
60
EIGRP
Queries and
Stuck in
Active
 Router loses a route and does not have an FS in its topology table, it looks for an alternative
path to the destination. - known as going active on a route
 If a neighbor does not have an alternative route, it queries each of its own neighbors for an
alternative path.
 The queries then propagate through the network, thus creating an expanding tree of queries.
61
Router
Stuck in Active (SIA) C Router D
Router
Queries
Replies
SIA Router
B
X
A
X
X
n When EIGRP returns a stuck in active (SIA) message, it means that it has
not received a reply to a query.
n Summarization can help prevent SIA. 62
EIGRP 101 EIGRP 102
Stuck-in-Active
 The most common reasons for SIA routes are as follows:

 The router is too busy to answer the query
 The link between the two routers is not good
 A failure causes traffic on a link to flow in only one direction.
 This is called a unidirectional link.
 Misconceptions
 Using multiple EIGRP domains (AS’s) to simulate OSPF areas (later)
will help limit the scope of the queries.
 This is not true, the boundary router will create a new EIGRP query
into the other EIGRP domain.
63
Queries
Optimizing EIGRP
 Reduce queries
 EIGRP Summarization
 EIGRP Stub Routing
 Reduce the affect of SIAs
 EIGRP Active Enhancement Process
64
Reduce Queries by using Summary Routes
S0/0/0
HQ(config)# interface serial 0/0/0

HQ(config-if)# ip summary-address eigrp 1 192.168.0.0 255.255.0.0
 HQ performs summarization for all remote networks.

 A summary route is announced to other routers, like router GW.
65
Reduce Queries by using Summary Routes
?
 Connectivity to the remote location fails

 HQ has no feasible successors to reach the lost network
 HQ sends a query to its neighbors including GW.
 GW receives a query for a network 192.168.12.0/24…
 Immediately responds with a reply message without further forwarding the query because it
has a summary route 192.168.0.0/16 from HQ, which also describes 192.168.12.0/24 prefix.
 Because this route was learned from router HQ, router GW will respond that it does not
have an alternative path for 192.168.12.0/24.
 The summary is still valid as long as there is one prefix covered by the summary. 66
Manual
Summarization
 EIGRP can be configured to summarize routes, whether or not automatic

summarization (auto-summary) is enabled. 67
Manual 192.168.1.0/24,
192.168.1.0/24, 192.168.2.0/24,
Summarization 192.168.2.0/24, 192.168.3.0/24
192.168.3.0/24
Only pertinent routes shown
R1# show ip route
D 192.168.1.0/24 [90/2172416] via 192.168.10.6, 02:07:38, S0/0/1
D 192.168.2.0/24 [90/2297856] via 192.168.10.6, 00:00:34, S0/0/1
D 192.168.3.0/24 [90/2297856] via 192.168.10.6, 00:00:18, S0/0/1
R2# show ip route

D 192.168.1.0/24 [90/3014400] via 192.168.10.10, 02:08:50, S0/0/1
D 192.168.2.0/24 [90/3139840] via 192.168.10.10, 00:01:46, S0/0/1
D 192.168.3.0/24 [90/3139840] via 192.168.10.10, 00:01:30, S0/0/1
 Instead of sending three separate networks, R3 can summarize the 192.168.1.0/24,
192.168.2.0/24, and 192.168.3.0/24 networks as a single route. 68
Determining the Summary EIGRP Route
1. Write out the networks that you want to summarize in binary.

2. Find the matching bits.
 Count the number of leftmost matching bits, which in this example is 22.
 This number becomes your subnet mask for the summarized route: /22
or 255.255.252.0.
3. To find the network address for summarization, copy the matching 22 bits
and add all 0 bits to the end to make 32 bits.
The result is the summary network address and mask for 192.168.0.0/22 69
Configure EIGRP
192.168.0.0/22
Manual
Summarization 192.168.0.0/22
Router(config-if)# ip summary-address eigrp as-number network-address

subnet-mask
R3(config-if)# ip summary-address eigrp 1 192.168.0.0 255.255.252.0
R3(config-if)# ip summary-address eigrp 1 192.168.0.0 255.255.252.0
R3# show ip route
Creates a Null0 summary route
<output omitted>
D 192.168.0.0/22 is a summary, 00:00:06, Null0
70
Verify EIGRP
Manual 192.168.0.0/22
Summarization 192.168.0.0/22
R1# show ip route

<output omitted>
D 192.168.0.0/22 [90/2172416] via 192.168.10.6, 00:01:11, Serial0/0/1
R2# show ip route
<output omitted>
D 192.168.0.0/22 [90/3014400] via 192.168.10.10, 00:00:23, Serial0/0/1
 Fewer number of total routes in routing table - Faster routing table lookup process.
 Summary routes also require less bandwidth and memory
 Single route can be sent rather than multiple individual routes.
 NOTE: The minimum metric of specified routes is used as the metric of the summary route. 71
Automatic Summarization at Classful Network Boundary
I’m an EIGRP for IPv4
router configured for
automatic summarization.
IPv4 Routing Table
172.16.1.0/24 172.17.0.0/30
172.16.2.0/24 R1 R2 172.16.0.0/16 via R1
172.16.3.0/24 Summary Update: 172.16.0.0/16
Classful Networks
Class A: 0.0.0.0 to 127.255.255.255 Default Mask: 255.0.0.0 or /8
Class B: 128.0.0.0 to 191.255.255.255 Default Mask: 255.255.0.0 or /16
Class C: 192.0.0.0 to 223.255.255.255 Default Mask: 255.255.255.0 or /24
 When enabled, EIGRP summarizes at classful boundaries.

 EIGRP groups subnets into their Class A, B, or C network address
and creates a single entry.
72
EIGRP for IPv4 automatic summarization
defaults
 Since IOS 15.0(1)M and 12.2(33),
automatic summarization is disabled. 172.16.1.0/24
R1(config-router)# no auto-summary 172.16.2.0/24
172.16.3.0/24
 Prior, automatic summarization was
enabled.
R1(config-router)# auto-summary

<Output omitted>

D 172.16.1.0/24 [90/2170112] via 192.168.10.5, 02:21:10, Serial0/0/0
D 172.16.2.0/24 [90/3012096] via 192.168.10.9, 02:21:10, Serial0/0/1
D 172.16.3.0/30 [90/41024000] via 192.168.10.9, 02:21:10, Serial0/0/1
[90/41024000] via 192.168.10.5, 02:21:10, Serial0/0/0
R3# 73
Default Static Route
Propagating a
Default Route
R2(config)# ip route 0.0.0.0 0.0.0.0 serial 0/1/0
R2(config-router)# redistribute static
74
Queries
Optimizing EIGRP
 Reduce queries
75
EIGRP Interfaces The summary route of 192.168.16.0/23 is
installed in HQ’s route table rather than the
directly connected 192.168.16.0/24 because
HQ# show ip route eigrp 192.168.16.0/24 is included in the summary.
D 192.168.0.0/24 [90/409600] via 172.16.1.2, 00:12:07, Ethernet0/0
D 192.168.16.0/23 [90/307200] via 172.16.1.2, 00:12:07, Ethernet0/0
D EX 192.168.18.0/24 [170/307200] via 172.16.1.2, 00:12:07, Ethernet0/0
BR1A announces to HQ:

 Summary route to 192.168.16.0/23 (192.168.16.0/24
and 192.168.17.0/24)
 It’s static route to 192.168.18.0/24 that it redistributes into
EIGRP and announces the prefix as an external EIGRP route to
HQ.
 BR1A also advertises its own directly connected networks
192.168.0.0/24 and 192.168.16.0/24
76
Stub Routers
EIGRP
Updates
X
Stub
Queries X
 Stub Routers learn routes from nonstub routers but…
 Stub routers do not forward EIGRP learned routes to other neighbors
 Nonstub routers do not send query messages to stub routers…. Stub
will send what it wants (if anything).
77
Stub Router Options
Options – One or more, except for receive-only EIGRP Updates
 connected – Sends connected routes covered by a network statement.
 Most widely practical stub option (default)
 summary - Sends summary routes, manually created or automatic. (default)
 static - Sends static routes redistributed with the redistribute static
command.
 redistributed – Sends all redistributed routes configured with the
redistribute command.
 receive-only - Restricts the stub router from sharing any of its routes with
any other EIGRP router.
 This option does not permit any other option to be used.
 This option is rarely used.
 Router has a single interface or using NAT (later) 78
Stub default: connected and summary
BR1A(config)# router eigrp 1
BR1A(config-router)# eigrp stub
*Oct 18 11:51:16.232: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.16.1.1
(Ethernet0/0) is down:
HQ# show ip route eigrp
D 192.168.0.0/24 [90/409600] via 172.16.1.2, 00:09:07, Ethernet0/0

D 192.168.16.0/23 [90/307200] via 172.16.1.2, 00:09:07, Ethernet0/0
Default: connected and summary

 When you configure or change the EIGRP stub options,
any neighboring session needs to be torn down and
reestablished.
79
Stub default: connected and summary
BR1A(config-router)# eigrp stub
HQ# show ip eigrp neighbors detail
(sec) (ms) Cnt Num
0 10.2.2.2 Se0/0/0 14 00:21:37 20 120 0 15
Version 16.0/2.0, Retrans: 0, Retries: 0, Prefixes: 3
Topology-ids from peer - 0
Stub Peer Advertising (CONNECTED SUMMARY ) Routes
Suppressing queries
Max Nbrs: 0, Current Nbrs: 0
HQ#
Default: connected and summary
80
Stub default: connected
BR1A(config-router)# eigrp stub connected
D 192.168.0.0/24 [90/409600] via 172.16.1.2, 00:14:52, Ethernet0/0

D 192.168.16.0/24 [90/307200] via 172.16.1.2, 00:14:52, Ethernet0/0
 connected – Sends connected routes covered by a network

statement.
 Most widely practical stub option (default)
 The summary route of 192.168.16.0/23 is installed in
HQ’s route table rather than the directly connected
192.168.16.0/24 because 192.168.16.0/24 is included in
the summary.
81
Stub default: receive-only
BR1A(config-router)# eigrp stub receive-only
<No routes learned from BR1A>
 receive-only - Restricts the stub router from sharing any of its

routes with any other EIGRP router.
 Useful in cases when all hosts behind router BR1A would be
translated using NAT with PAT.
 HQ has no need to be aware of networks behind router BR1A
because all outgoing traffic would be destined for BR1A’s
egress interface, where NAT would be performed.
82
Queries
Optimizing EIGRP
 Reduce queries
83
Active Process
Enhancement
feature
 Cisco IOS Software Release 12.1(5) and later, with the Active
Process Enhancement feature.
 This feature enables an EIGRP router to monitor the progression of
the search for a successor route and ensure that the neighbor is still
reachable.
84
BEFORE Active Process Enhancement feature.
X 10.1.1.0/24 gone; no FS
A Never heard from B
Query
X 3 min timer
So after 3 min reset adjacency along with all networks
B 10.1.1.0/24 gone; no FS
No entry so sends Query
Bad link; reply never makes it
No entry send Reply

C
10.1.1.0/24 gone;
Remove 10.1.1.0/24
85
AFTER Active Process Enhancement feature.
Thanks for letting me know, X 10.1.1.0/24 gone; no FS
I will not terminate our adjacency. A
After 1.5 min SIA Query Query The neighbor relationship
between Routers A and B
remains intact.
10.1.1.0/24 gone; no FS
SIA Reply: I’m ok but waiting on C B
No entry so sends Query
After 1.5 min SIA Query
(3 attempts until I terminal Bad link; reply never makes it
adjacency with C)
No entry send Reply

C
10.1.1.0/24 gone;
Remove 10.1.1.0/24
86
EIGRP Load Balancing
87
Variance command
Router(config)# router eigrp 1
Router(config-router)# variance multiplier
 Cisco IOS allows up to 32 equal-cost paths (IOS dependent), 4 by default.
 EIGRP does unequal cost load balancing, forwarding packets relative to the metric.
 The variance command:
 Instructs the router to include routes with a metric less than or equal to n times
the minimum metric route for that destination
 n is the number specified by the variance command (1 -128).
 Default = 1
 The maximum-paths number EIGRP is used to sent the number of load-balancing
paths (up to 32 paths).
 1 disables load balancing
 Note: If a path isn't a feasible successor, then it isn't used in load balancing.
 Note: Load balancing is only performed on traffic that passes through the router, not
88
traffic generated by the router.
Variance command
RD
FS
Succ
FS
 Successor: R3 with a FD of 20
 Feasible Successors: R2 and R5
 R2’s RD of 10 < R3’s FD of 20
 R5’s RD of 10 < R3’s FD of 20
 R4 is NOT a FS because it’s RD of 25 > R3’s FD of 20

89
Variance command
RD
FS
Succ x 2 = 40
FS R1(config)# router eigrp 110

R1(config-router)# variance 2
 Variance = 2
 R3’s FDv 2 x 20 (FD) = 40
 R2 is added as successor to R1’s routing table: R2’s FD of 30 < R3’s FDv of 40
 R5 is NOT added to R1’s routing table: R5’s FD of 50 > R3’s FDv of 40
 R5 would still be a Feasible Successor
 Note: R4 is not considered even if it’s FD was < or = R3’s FDv of 40 because it is not a FS
 The load in is balanced proportional to the bandwidth.
 FD of the route via router R2 is 30
 FD of the route via router R3 is 20
 Ratio of traffic between the two paths will be proportional to the metric. 90
EIGRP over MPLS
91
Layer 2 and Layer 3 MPLS VPN Solutions
 Layer 2 MPLS VPN provides a Layer 2 service across the backbone

 R1 and R2 are connected together on the same IP subnet.
 Layer 3 MPLS VPN provides a Layer 3 service across the backbone

 R1 and R2 are connected to ISP edge routers; on each side, a separate
IP subnet is used.
92
Layer 3 MPLS VPNs
L3
192.168.1.0/30 192.168.2.0/30
network network
 R1 and R2 are configured for EIGRP as if there

were a corporate core network between them.
 EIGRP parameters between R1 and R2 (such as
the AS number, authentication password, and so
on) are often governed/coordinated by the
service provider. 93
Layer 3 MPLS VPNs
 R1 establishes an EIGRP neighbor relationship with the PE1 (Provider

Edge) router,
 R2 establishes an EIGRP neighbor relationship with the PE2 router.
 Routers R1 and R2 do NOT establish an EIGRP neighbor relationship with
each other. 94
Layer 2 MPLS VPNs
192.168.1.100/27
network
 EIGRP needs to be enabled with the same AS number on both routers.

 network command includes the interface toward the PE router (PE1 and PE2)
over which the routers R1 and R2 will form their neighbor relationship.
 From the EIGRP perspective, the MPLS backbone and routers PE1 and PE2
95
are not visible.
Layer 2 MPLS VPNs
 A neighbor relationship is established directly between routers R1

and R2 over the MPLS backbone. 96
Thank You

Route 2 Eigrp Implementingeigrp

Uploaded by

Copyright:

Available Formats

Route 2 Eigrp Implementingeigrp

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Route 2 Eigrp Implementingeigrp

Uploaded by

Copyright:

Available Formats

CCNP ROUTE

Chapter 2: Implementing EIGRP

EIGRP maintains individual

R2(config)# router eigrp 1

R3(config)# router eigrp 1 255.255.255.255

R2(config)# router eigrp 1

R3(config)# router eigrp 1

Hello Used to discover other EIGRP routers in the network.

Acknowledgement Used to acknowledge the receipt of any EIGRP packet.

Update Convey routing information to known destinations.

Query Used to get specific information from a neighbor router.

Reply Used to respond to a query.

<rest of output omitted>

Routing Protocol is "application"

<continued next slide>

R1(config)# router eigrp 1

R2(config)# router eigrp 1 X X

R3(config)# router eigrp 1

Routing Protocol is "eigrp 1”

Routing for Networks:

R1(config)# interface serial 0/0/0

R3# show ip eigrp traffic

The EIGRP World from R2’s Distance Vector Perspective

R2# show ip route eigrp

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

 EIGRP is a distance vector routing

P 10.1.102.0/29, 1 successors, FD is 40512000

P 172.16.3.0/24, 1 successors, FD is 3014400 R3: Successor

P 172.16.3.0/24, 1 successors, FD is 3014400

P 172.16.3.0/24, 1 successors, FD is 3014400

My current metric (feasible distance)

My cost to 172.16.3.0 is 2,172,416. If this is Successor

I’m the new successor

R2# show ip route eigrp

R2# show ip route eigrp

The EIGRP World from R1’s Distance Vector Perspective

R1# show ip route eigrp

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 5 subnets, 2 masks

P 10.1.102.0/29, 1 successors, FD is 40512000

P 172.16.3.0/24, 1 successors, FD is 2172416 R3: Successor

P 172.16.3.0/24, 1 successors, FD is 2172416, serno 23

My new successor is R2 with a

D 172.16.3.0/24 [90/41026560] via 10.1.102.2, 00:14:08, Serial0/0/0

R1(config)# interface serial 0/0/1

R1# show ip route eigrp

 The most common reasons for SIA routes are as follows:

HQ(config)# interface serial 0/0/0

 HQ performs summarization for all remote networks.

 Connectivity to the remote location fails

 EIGRP can be configured to summarize routes, whether or not automatic

R2# show ip route

1. Write out the networks that you want to summarize in binary.

Router(config-if)# ip summary-address eigrp as-number network-address

R1# show ip route

 When enabled, EIGRP summarizes at classful boundaries.

R3# show ip route eigrp

172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks