CIS 185 CCNP ROUTE

Chapter 2: Implementing EIGRP

1 of 3: Basic EIGRP
Rick Graziani
Cabrillo College
[email protected]

Spring 2015
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.

2
/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
!
interface Serial0/0/1
description R1-->R3
bandwidth 1544
ip address 10.1.103.1 255.255.255.248

4
Initial Config – R2

interface GigabitEthernet0/0
ip address 172.16.2.1 255.255.255.0
!
interface Serial0/0/0
description R2-->R1
bandwidth 64
ip address 10.1.102.2 255.255.255.248
!
interface Serial0/0/1
description R2-->R3
bandwidth 1024
ip address 10.1.203.2 255.255.255.248
clock rate 64000

5
Initial Config – R3

interface GigabitEthernet0/0
ip address 172.16.3.1 255.255.255.0
!
interface Serial0/0/0
description R3-->R1
bandwidth 1544
ip address 10.1.103.3 255.255.255.248
clock rate 64000
!
interface Serial0/0/1
description R3-->R2
bandwidth 1024
ip address 10.1.203.3 255.255.255.248

6
Configuring Basic EIGRP
R1(config)# router eigrp 1
R1(config-router)# network 172.16.0.0
R1(config-router)# network 10.0.0.0
R1(config-router)#

R2(config)# router eigrp 1

R2(config-router)# network 172.16.0.0
R2(config-router)# network 10.0.0.0
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)#
7
EIGRP Router ID
R1(config)# router eigrp 1
R1(config-router)# eigrp router-id 1.1.1.1

R2(config)# router eigrp 1

R2(config-router)# eigrp router-id 2.2.2.2

R3(config)# router eigrp 1

R3(config-router)# eigrp router-id 3.3.3.3
*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 8
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.

9
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. 10
EIGRP Neighbors Amount
Amount of
was
of time
was added
time since
added to
since this
to the
this neighbor
the neighbor
neighbor
neighbor table.
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
The local
local
Neighbor’s
Neighbor’s interface
interface Seconds
Seconds remaining
remaining
IPv4
IPv4 receiving
receiving before
before declaring
declaring
address
address EIGRP
EIGRP Hello
Hello neighbor
neighbor down.
down.
packets.
packets. Reset
Reset to
to hold
hold time
time
when
when Hello
Hello is
is
received.
received.

11
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#

12
EIGRP Interfaces
R2# show ip eigrp interfaces detail
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
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>

13
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>

14
IPv4 Routing Protocols
Routing Protocol is "eigrp 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
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
Routing Information Sources:
Gateway Distance Last Update
10.1.102.1 90 00:23:27 neighbors
10.1.203.3 90 00:23:28
Distance: internal 90 external 170
15
R2#
IPv4 Routing Protocols
Routing Protocol is "eigrp 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
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
METRIC2.2.2.2
Router-ID: = ( [K1 x Bandwidth + (K2 x Bandwidth) / (256-load) + K3 x Delay] x [K5 / (Reliability + K4] ) x 256
Topology : 0 (base)
METRIC = (3 [1
Active Timer: min x Bandwidth + (0 x Bandwidth) / (256-load) + 1 x Delay] x [0 / (Reliability + 0] ) x 256
Distance: internal
METRIC = (1 x90Bandwidth
external 170 + 1 x Delay) x 256
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
NOTE:
Automatic Summarization: disabled
Maximum path: 4 • The multiplication by 256 is a legacy feature to maintain
backwards compatibility with IGRP.
Routing for Networks:
10.0.0.0
172.16.0.0
Routing Information Sources:
Gateway Distance Last Update
10.1.102.1 90 00:23:27
10.1.203.3 90 00:23:28
Distance: internal 90 external 170
16
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.
 The EIGRP Wide Metric is beyond the scope of this book.
 For more information, see the Cisco.com document “EIGRP Wide Metrics,” at
http://www.cisco.com/c/en/us/td/docs/ios-
xml/ios/iproute_eigrp/configuration/15-mt/ire-15-mt-book/ire-wid-met.pdf. 17
Configuring Passive Interfaces X

R1(config)# router eigrp 1

R1(config-router)# passive-interface g0/0

R2(config)# router eigrp 1 X X

R2(config-router)# passive-interface g0/0

R3(config)# router eigrp 1

R3(config-router)# passive-interface g0/0

18
EIGRP Interfaces after Passive
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
R2#
R2# show ip protocols

<selected output>

Routing Protocol is "eigrp 1”

Passive Interface(s):
GigabitEthernet0/0

Routing for Networks:

10.0.0.0
172.16.0.0
19
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
*Feb 1 21:28:45.354: EIGRP: Sending HELLO on Se0/0/0 - paklen 20
*Feb 1 21:28:45.354: AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
*Feb 1 21:28:50.174: EIGRP: Sending HELLO on Se0/0/0 - paklen 20
*Feb 1 21:28:50.174: AS 1, Flags 0x0:(NULL), Seq 0/0 interfaceQ 0/0 iidbQ un/rely 0/0
*Feb 1 21:28:55.602: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.102.1 (Serial0/0/0) is down: holding time expired
R2#

 Shutdown on a serial link in a lab environment does not work because it brings down
20
both ends of the link
EIGRP Neighbors w/ Differing Timers 5/15
5/15
R2# show ip eigrp interfaces detail serial 0/0/0
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 68 10/390 390 0
Hello-interval is 5, Hold-time is 15
<>
----------------------------------------------------------------------------------------
R1# show ip eigrp interfaces detail serial 0/0/0
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 1290 10/390 6826 0
Hello-interval is 5, Hold-time is 15
<>
R1#show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.1.102.2 Se0/0/0 11 00:03:36 28 2340 0 26 21
<>
EIGRP Neighbors w/ Differing Timers 5/15
10/30
R1(config)# interface serial 0/0/0
R1(config-if)# ip hello-interval eigrp 1 10
R1(config-if)# ip hold-time eigrp 1 30
R1(config-if)# end
R1#
R1# show ip eigrp interfaces detail serial 0/0/0
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 1290 10/390 6826 0
Hello-interval is 10, Hold-time is 30
<>
R1# show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.1.102.2 Se0/0/0 12 00:25:47 1290 5000 0 54

22
Initial Route
Discovery
Observing EIGRP
R3# debug eigrp packet
R3# conf t
R3(config)# router eigrp 1
R3(config-router)# network 10.1.203.0 0.0.0.7
*Feb 1 22:06:45.678: EIGRP: Sending HELLO on Se0/0/1 - paklen 20
*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
*Feb 1 22:06:47.774: AS 1, Flags 0x0:(NULL), Seq 0/64 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 1/1
*Feb 1 22:06:47.778: EIGRP: Received ACK on Se0/0/1 - paklen 0 nbr 10.1.203.2
*Feb 1 22:06:47.778: AS 1, Flags 0x0:(NULL), Seq 0/64 interfaceQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/1

24
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# 25
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
172.16.0.0/16 is variably subnetted, 4 subnets, 2 masks
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# 26
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 27
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.
28
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)

29
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. 30
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
P 172.16.2.0/24, 1 successors, FD is 28160
via Connected, GigabitEthernet0/0
P 10.1.103.0/29, 1 successors, FD is 3523840
via 10.1.203.3 (3523840/2169856), Serial0/0/1
via 10.1.102.1 (41024000/2169856), Serial0/0/0
P 172.16.3.0/24, 1 successors, FD is 3014400
via 10.1.203.3 (3014400/28160), Serial0/0/1
via 10.1.102.1 (41026560/2172416), Serial0/0/0
P 10.1.203.0/29, 1 successors, FD is 3011840
via Connected, Serial0/0/1
P 172.16.1.0/24, 1 successors, FD is 3526400
via 10.1.203.3 (3526400/2172416), Serial0/0/1
via 10.1.102.1 (40514560/28160), Serial0/0/0
31
R2#
The Successor
R2# show ip eigrp topology

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

32
The Feasible Successor

R2#The
show reported
ip eigrp distance
topology - EIGRP neighbor’s FD to the same destination network.
 The metric that a router reports to a neighbor about its own cost to that network.
 Feasibility Condition:
P 172.16.3.0/24, 1 successors,The FC3014400
FD is is met when a neighbor’s reported distance (RD)
R1: Feasible
to a network is less than the local router’s FD to the same destination network.
via 10.1.203.3 (3014400/28160), Serial0/0/1 Successor
via 10.1.102.1 (41026560/2172416), Serial0/0/0
Outbound interface to
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. 33
Why is R1 a Feasible Successor?
R2# show ip eigrp topology

P 172.16.3.0/24, 1 successors, FD is 3014400

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.
34
Why is R1 a Feasible Successor?
R2# show ip eigrp topology

P 172.16.3.0/24, 1 successors, FD is 3014400

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

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 35
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)# interface serial 0/0/1
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
R2# show ip eigrp topology
<>
Successor from EIGRP Topology Table
P 172.16.3.0/24, 1 successors, FD is 3014400
via 10.1.102.1 (41026560/2172416), Serial0/0/0

R2# show ip route eigrp

<>
D 172.16.3.0/24 [90/41026560] via 10.1.102.1, 00:00:22, Serial0/0/0
R2# 36
Back to normal

Feasible
Successor Successor
R2(config)# interface serial 0/0/1
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
*Feb 2 00:03:03.346: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.203.3 (Serial0/0/1) is up: new adjacency

R2# show ip route eigrp

<>
D 172.16.3.0/24 [90/3014400] via 10.1.203.3, 00:00:09, Serial0/0/1
R2#

37
IPv4 Routing Table – EIGRP Routes

The EIGRP World from R1’s Distance Vector Perspective

R1# 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.203.0/29 [90/3523840] via 10.1.103.3, 00:07:11, Serial0/0/1
172.16.0.0/16 is variably subnetted, 4 subnets, 2 masks
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# 38
R1’s EIGRP Topology Table
R1# show ip eigrp topology
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

P 10.1.102.0/29, 1 successors, FD is 40512000

via Connected, Serial0/0/0
P 172.16.2.0/24, 1 successors, FD is 3526400
via 10.1.103.3 (3526400/3014400), Serial0/0/1
via 10.1.102.2 (40514560/28160), Serial0/0/0
P 10.1.103.0/29, 1 successors, FD is 2169856
via Connected, Serial0/0/1
P 172.16.3.0/24, 1 successors, FD is 2172416
via 10.1.103.3 (2172416/28160), Serial0/0/1
P 10.1.203.0/29, 1 successors, FD is 3523840
via 10.1.103.3 (3523840/3011840), Serial0/0/1
via 10.1.102.2 (41024000/3011840), Serial0/0/0
P 172.16.1.0/24, 1 successors, FD is 28160
via Connected, GigabitEthernet0/0

R1# 39
The Successor
R1# show ip eigrp topology

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

via 10.1.103.3 (2172416/28160), Serial0/0/1

Outbound interface to
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.
40
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.103.3 (2172416/28160), Serial0/0/1 R3: Successor
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
41
route.
DUAL: An Introduction R2 sends updates out all interfaces
Not shown

X
42
Observing EIGRP
Reply Query

R1# debug eigrp fsm Query

EIGRP Finite State Machine debugging is on
R1# conf t Reply
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)# interface serial 0/0/1
R1(config-if)# shutdown
X
*Feb 2 00:38:10.082: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.103.3 (Serial0/0/1) is down: 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

43
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
<>
P 172.16.3.0/24, 1 successors, FD is 41026560
via 10.1.102.2 (41026560/3014400), Serial0/0/0

R1#
R1# show ip route eigrp
<>

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

R1
44
Back to normal

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

R1(config-if)# no shutdown
45
R1(config-if)# end
*Feb 2 01:08:40.865: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 10.1.103.3 (Serial0/0/1) is up: new adjacency
R1#
R1# show ip eigrp topology
<>
P 172.16.3.0/24, 1 successors, FD is 2172416
R1# via 10.1.103.3 (2172416/28160), Serial0/0/1

R1# show ip route eigrp

<>
D 172.16.3.0/24 [90/2172416] via 10.1.103.3, 00:00:13, Serial0/0/1
R1#
45
CIS 185 CCNP ROUTE
Chapter 2: Implementing EIGRP
1 of 3: Basic EIGRP
Rick Graziani
Cabrillo College
[email protected]

Spring 2015