EIGRP

Introduction
Overview of EIGRP
Enhanced IGRP is a Cisco-proprietary routing protocol released in 1992.
EIGRP was created as a classless version of IGRP.

EIGRP acts like a link-state routing protocol, but its still a distance vector
routing protocol.
In 2013, Cisco released a basic functionality of EIGRP as an open standard to
the IETF as an informational RFC.

Cisco will continue to maintain control of EIGRP.
Thanhnd CCIE#50479
EIGRP Packets
IP EIGRP relies on 5 types of packets to maintain its various tables
and establish complex relationships with neighbor routers.
Packet Type
Hello
Acknowledgement
Thanhnd CCIE#50479
Description
Used to discover other EIGRP routers in the network.
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.
Neighbor Discovery
The goal of any dynamic routing protocol is to:

Learn about remote networks
Reach convergence in the routing domain.
To establish and maintain EIGRP neighbor adjacencies, EIGRP
routers:
Use the Hello packet
Metric parameters must match (later)
AS number must match
Thanhnd CCIE#50479
Initial Route
Discovery
Thanhnd CCIE#50479
Hello Packets
Hello packets are sent on a regular interval.

Router assumes that as long as it is receiving Hello packets from a
neighbor, the neighbor and its routes remain viable.
The interval depends on the interfaces bandwidth.
Low Bandwidth = 60 seconds
Default interval on multipoint nonbroadcast multiaccess networks
(NBMA) such as X.25, Frame Relay, and ATM interfaces with access
links of T1 (1.544 Mbps) or slower.
High bandwidth = 5 seconds
Default interval on circuits with bandwidth greater than T1 such as
Ethernet LANs.
Thanhnd CCIE#50479
Hello Holdtime
Hold time - maximum time the router should wait to receive the next
hello before declaring that neighbor as unreachable.

Default hold time - 3 times the hello interval
If the hold time expires:
EIGRP declares the route as down
DUAL searches for a new path in the topology table or by sending out
queries.
More later.
Thanhnd CCIE#50479
EIGRP Packet Types

Update and
Acknowledgement
Packets
EIGRP
uses
triggered
updates
Update
Packets
Contains only the routing information needed (a change occurs)
Sent only to those routers that require it.
Uses reliable delivery.
Acknowledgment (ACK) Packets

Sent when reliable delivery is used (update, query, and reply packets).
Unreliable unicast.
Thanhnd CCIE#50479
EIGRP Packet
Types Query
and Reply
Packets
Why Query?
Another router
could be
attached to the
same
Used
byLAN.
DUAL when searching for networks and other tasks.
Queries and replies use reliable delivery.

DUAL is discussed in a later section.
Queries can use multicast or unicast, whereas Replies are always
sent as unicast.
Thanhnd CCIE#50479
Configure EIGRP
10
Topology
Thanhnd CCIE#50479
11
eigrp router-id Command

RID: 2.2.2.2
R2(config)# router eigrp 1
R2(config-router)# eigrp router-id 2.2.2.2
R2(config-router)#
RID: 1.1.1.1
RID: 3.3.3.3

R1(config-router)#
R3(config-router)#
Thanhnd CCIE#50479
12
12
network Command

R3(config-router)# network 192.168.1.0
R3(config-router)# network 192.168.10.4 0.0.0.3
*Feb 28 20:47:22.695: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor
192.168.10.5 (Serial0/0/0) is up: new adjacency
R3(config-router)#
R3(config-router)# network 192.168.10.8 0.0.0.3
*Feb 28 20:47:06.555: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor
192.168.10.9 (Serial0/0/1) is up: new adjacency
R3(config-router)#
13
Thanhnd CCIE#50479
13
Verify the R3 Routing

Table
R3# show ip route | begin Gateway

Gateway of last resort is not set
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
D
172.16.1.0/24 [90/2170112] via 192.168.10.5, 00:12:00, Serial0/0/0
D
172.16.2.0/24 [90/2170112] via 192.168.10.9, 00:16:49, Serial0/0/1
D
172.16.3.0/30 [90/2681856] via 192.168.10.9, 00:52:55, Serial0/0/1
[90/2681856] via 192.168.10.5, 00:52:55, Serial0/0/0
C
192.168.1.0/24 is directly connected, GigabitEthernet0/0
L
192.168.1.1/32 is directly connected, GigabitEthernet0/0
C
192.168.10.4/30 is directly connected, Serial0/0/0
L
C
L
R3#
14
Thanhnd CCIE#50479
14
CHECKING COMMANDS
15
IPv4 Routing Table EIGRP Routes

The EIGRP World from R2s Distance Vector Perspective
R2#showiprouteeigrp
Codes:Llocal,Cconnected,Sstatic,RRIP,Mmobile,BBGP
DEIGRP,EXEIGRPexternal,OOSPF,IAOSPFinterarea
<outputomitted>
Gatewayoflastresortisnotset
10.0.0.0/8isvariablysubnetted,5subnets,2masks
D10.1.103.0/29[90/3523840]via10.1.203.3,00:58:05,Serial0/0/1
172.16.0.0/16isvariablysubnetted,4subnets,2masks
D172.16.1.0/24[90/3526400]via10.1.203.3,00:58:05,Serial0/0/1
D172.16.3.0/24[90/3014400]via10.1.203.3,00:58:05,Serial0/0/1
R2#
Thanhnd CCIE#50479
16
16
EIGRP Neighbors
Amount
Amount of
of time
time since
since this
this neighbor
neighbor
was
was added
added to
to the
the neighbor
neighbor table.
table.
R2#showipeigrpneighbors
EIGRPIPv4NeighborsforAS(1)
HAddressInterfaceHoldUptimeSRTTRTOQSeq
(sec)(ms)CntNum
110.1.203.3Se0/0/11000:03:1528168019
010.1.102.1Se0/0/01200:13:22232340046
R2#
Neighbors
Neighbors
IPv4
IPv4
address
address
Thanhnd CCIE#50479
The
The local
local
interface
interface
receiving
receiving
EIGRP
EIGRP Hello
Hello
packets.
packets.
Seconds
Seconds remaining
remaining
before
before declaring
declaring
neighbor
neighbor down.
down.
Reset
Reset to
to hold
hold time
time
when
when Hello
Hello is
is
received.
received.
17
17
EIGRP Interfaces
R2#showipeigrpinterfaces
EIGRPIPv4InterfacesforAS(1)
XmitQueuePeerQMeanPacingTimeMulticastPending
InterfacePeersUn/ReliableUn/ReliableSRTTUn/ReliableFlowTimerRoutes
Se0/0/010/00/02310/3904780
Se0/0/110/00/0280/231390
Gi0/000/00/000/000
R2#
Thanhnd CCIE#50479
18
18
EIGRP Interfaces
R2#showipeigrpinterfacesdetail
Se0/0/010/00/02310/3904780
Hellointervalis5,Holdtimeis15
Splithorizonisenabled
Nextxmitserial<none>
Packetizedsent/expedited:20/0
Hello'ssent/expedited:2186/4
Un/reliablemcasts:0/0Un/reliableucasts:23/23
Mcastexceptions:0CRpackets:0ACKssuppressed:0
Retransmissionssent:0Outofsequencercvd:1
Topologyidsoninterface0
Authenticationmodeisnotset
<restofoutputomitted>
Thanhnd CCIE#50479
19
19
IPv4 Routing Protocols

R2#showipprotocols
***IPRoutingisNSFaware***
RoutingProtocolis"application"
Sendingupdatesevery0seconds
Invalidafter0seconds,holddown0,flushedafter0
Outgoingupdatefilterlistforallinterfacesisnotset
Incomingupdatefilterlistforallinterfacesisnotset
Maximumpath:32
RoutingforNetworks:
RoutingInformationSources:
GatewayDistanceLastUpdate
Distance:(defaultis4)
<continuednextslide>
Thanhnd CCIE#50479
20
20
EIGRP Process ID
IPv4 Routing Protocols
RoutingProtocolis"eigrp1"
Outgoingupdatefilterlistforallinterfacesisnotset
Incomingupdatefilterlistforallinterfacesisnotset
Defaultnetworksflaggedinoutgoingupdates
Defaultnetworksacceptedfromincomingupdates
EIGRPIPv4ProtocolforAS(1)
MetricweightK1=1,K2=0,K3=1,K4=0,K5=0
NSFawarerouteholdtimeris240
RouterID:2.2.2.2
Topology:0(base)
ActiveTimer:3min
Distance:internal90external170
Maximumpath:4
Maximumhopcount100
Maximummetricvariance1
EIGRP Router ID
Variance For unequal

cost load balancing
AutomaticSummarization:disabled
Maximumpath:4
RoutingforNetworks:
Starting with 15.0 no
network
10.0.0.0
172.16.0.0
statements auto-summary is the
RoutingInformationSources:
GatewayDistanceLastUpdate
default
10.1.102.19000:23:27
10.1.203.39000:23:28
Distance:internal90external170
neighbors
R2#
Thanhnd CCIE#50479
21
21
Observing EIGRP
R3#showipeigrptraffic
EIGRPIPv4TrafficStatisticsforAS(1)
Hellossent/received:8319/6103
Updatessent/received:48/43
Queriessent/received:5/9
Repliessent/received:9/5
Ackssent/received:51/57
SIAQueriessent/received:0/0
SIARepliessent/received:0/0
HelloProcessID:145
PDMProcessID:106
SocketQueue:0/10000/2/0(current/max/highest/drops)
InputQueue:0/2000/2/0(current/max/highest/drops)
R3#
Thanhnd CCIE#50479
22
22
Observing Hello Packets

R1(config)#interfaceserial0/0/0
R1(configif)#noipaddress
R1(configif)#
*Feb121:34:02.926:%DUAL5NBRCHANGE:EIGRPIPv41:Neighbor10.1.102.2(Serial0/0/0)isdown:
interfacedown
R1(configif)#
R2#debugeigrppacketshello
(HELLO)
EIGRPPacketdebuggingison
R2#
*Feb121:28:40.602:EIGRP:ReceivedHELLOonSe0/0/0paklen20nbr10.1.102.1
*Feb121:28:41.062:EIGRP:SendingHELLOonSe0/0/0paklen20
*Feb121:28:41.062:AS1,Flags0x0:(NULL),Seq0/0interfaceQ0/0iidbQun/rely0/0
*Feb121:28:55.602:%DUAL5NBRCHANGE:EIGRPIPv41:Neighbor10.1.102.1(Serial0/0/0)isdown:
holdingtimeexpired
R2#
Shutdown on a serial link in a lab environment does not work because it brings down both ends of
the link
Thanhnd CCIE#50479
23
23
Observing EIGRP Packets

R3#debugeigrppacket
R3#conft
R3(config)#routereigrp1
R3(configrouter)#network10.1.203.00.0.0.7
*Feb122:06:45.698:EIGRP:ReceivedHELLOonSe0/0/1paklen30nbr10.1.203.2
*Feb122:06:45.698:%DUAL5NBRCHANGE:EIGRPIPv41:Neighbor10.1.203.2(Serial0/0/1)isup:
newadjacency
*Feb122:06:45.698:*Feb122:06:45.698:EIGRP:EnqueueingUPDATEonSe0/0/1paklen0nbr
10.1.203.2tid0iidbQun/rely0/1peerQun/rely0/0
*Feb122:06:45.706:EIGRP:SendingUPDATEonSe0/0/1paklen0nbr10.1.203.2tid0
*Feb122:06:45.706:AS1,Flags0x1:(INIT),Seq63/0interfaceQ0/0iidbQun/rely0/0peerQ
un/rely0/1
*Feb122:06:47.770:EIGRP:ReceivedUPDATEonSe0/0/1paklen222nbr10.1.203.2
*Feb122:06:47.770:AS1,Flags0x0:(NULL),Seq64/63interfaceQ0/0iidbQun/rely0/0peerQ
un/rely0/1
*Feb122:06:47.770:EIGRP:EnqueueingACKonSe0/0/1paklen0nbr10.1.203.2tid0
*Feb122:06:47.770:Ackseq64iidbQun/rely0/0peerQun/rely1/1
*Feb122:06:47.774:EIGRP:SendingACKonSe0/0/1paklen0nbr10.1.203.2tid0
un/rely1/1
*Feb122:06:47.778:EIGRP:ReceivedACKonSe0/0/1paklen0nbr10.1.203.2
un/rely0/1
Thanhnd CCIE#50479
24
24
Passvie Interface
Hello/HoldTimers
IP bandwidth Percent
Default-Route
25
Configuring Passive Interfaces
R1(configrouter)#passiveinterfaceg0/0
Thanhnd CCIE#50479
26
26
EIGRP Interfaces after Passive

R2#showipeigrpinterfaces
Se0/0/010/00/02310/3904780
Se0/0/110/00/0280/231390
R2#
R2#showipprotocols
<selectedoutput>
RoutingProtocolis"eigrp1
PassiveInterface(s):
GigabitEthernet0/0
RoutingforNetworks:
10.0.0.0
172.16.0.0
R2#
Thanhnd CCIE#50479
27
27
EIGRP Neighbors w/ Differing Timers
5/15
5/15
R2#showipeigrpinterfacesdetailserial0/0/0
Se0/0/010/00/06810/3903900
<>
Se0/0/010/00/0129010/39068260
<>
(sec)(ms)CntNum
010.1.102.2Se0/0/01100:03:36282340026
<>
Thanhnd CCIE#50479
28
28
EIGRP Neighbors w/ Differing Timers

R1(config)#interfaceserial0/0/0
R1(configif)#iphellointervaleigrp110
R1(configif)#ipholdtimeeigrp130
R1(configif)#end
R1#
5/15
10/30
Se0/0/010/00/0129010/39068260
<>
(sec)(ms)CntNum
010.1.102.2Se0/0/01200:25:4712905000054
Thanhnd CCIE#50479
29
29
The bandwidth-percent command

ip bandwidth-percent eigrp as-number percent
interface serial 0/0/0
bandwidth 56
ip bandwidth-percent eigrp 209 75
The bandwidth-percent command configures the percentage of
bandwidth that may be used by EIGRP on an interface.
By default, EIGRP is set to use only up to 50% of the bandwidth of an
interface to exchange routing information.
In order to calculate its percentage, the bandwidth-percent command
relies on the value set by the bandwidth command.
Allows EIGRP to use up to 75 percent (42 kbps) of a 56-kbps serial link in
autonomous system 209.
Thanhnd CCIE#50479
30
30
Propagating a Default
Route
Re
di
st
rib
ut
e
st
at
ic
Default Static Route

Re
di
st
rib
ut
e
st
at
ic
Redistribute Static
R2(config)# ip route 0.0.0.0 0.0.0.0 serial 0/1/0
R2(config-router)# redistribute static
Summary Route
R2(config-if)#ip summary-address eigrp 100 0.0.0.0 0.0.0.0
Network 0.0.0.0
R2(config)#ip route 0.0.0.0 0.0.0.0 lo0
R2(config)#router eigrp 100
R2(config-router)#network 0.0.0.0
Default-Network
R2(config)#ip default-network 192.168.1.0
Thanhnd CCIE#50479
31
31
EIGRP Authentication
32
Simple and MD5 Authentication
Neighbor router authentication - Routers only participate in routing based on
predefined passwords.
Routers use two types of authentication:
Simple password authentication (also called plain text

authentication)
Supported by Integrated System-Integrated System (IS-IS), OSPF, and
Routing Information Protocol Version 2 (RIPv2)
MD5 authentication
Supported by OSPF, RIPv2, BGP, and EIGRP
Provides authentication but does not provide confidentiality.
The contents of the protocol packets are not encrypted.
By default, no authentication is used for EIGRP packets.
Thanhnd CCIE#50479
33
33
Planning for EIGRP Authentication

Configuring EIGRP MD5 authentication requires the following steps:
Step 1: Configure the authentication mode for EIGRP
Step 2: Configure the key chain
Step 3: Optionally configure the keys lifetime parameters
Step 4: Enable authentication to use the key(s) in the key chain
Thanhnd CCIE#50479
34
34
MD5 Configuration Example
EIGRP router configuration is not shown.
Thanhnd CCIE#50479
35
35
MD5 authentication is configured on the
serial 0/0/1 interface with:

ipauthenticationmodeeigrp100md5
The keychainR1chaincommand
enters configuration mode for the

R1chain key chain.
Two keys are defined in this key chain.

Key 1 has the string: firstkey
Key 2 has the string secondkey
Each key has an authentication string
and lifetime specified.

The administrator wants to change the
keys on all the routers in the network

each month to improve the security.
The administrator configures an overlap
of one week to change the keys on all

the routers
The validity of key 2 is configured 1
Thanhnd CCIE#50479
week before the expiration of key 1 to

allow the new key to 36
be applied to all the
routers in the network.
36
Send and Receive Keys

Sending: send-lifetime
Only one key is used for sending
EIGRP packets depending upon the

lifetime of that key.
The router will use the first key (by
key number) which has a valid

lifetime for sending EIGRP packets.
Receiving: accept-lifetime
When receiving an EIGRP packet
any valid key can be used as long as

its lifetime matches and the
keystring matches.
If there are multiple valid keys the
router will use the first key (by key

number) which has a valid lifetime for
accepting EIGRP packets.
Thanhnd CCIE#50479
37
37
Key 1 is set to firstkey.
Acceptable for receiving EIGRP packets
received from January 1, 2009 onward:

acceptlifetime04:00:00Jan1
2009infinite
However, sendlifetime04:00:00Jan
1200904:00:00Jan312009
specifies that this key is only valid for use
when sending packets until January 31, 2009
It is no longer valid for use in sending packets
after January 31st 2009.
Key 2 is set to secondkey

Acceptable for receiving EIGRP packets from
January 25, 2009 onward:

acceptlifetime04:00:00Jan25
2009infinite.
This key can also be used for sending EIGRP
packets from January 25, 2009 onward

sendlifetime04:00:00Jan25
2009infinite
Thanhnd CCIE#50479
38
38
The authenticating key ID (number) and the key string on

both the sending router and the receiving router must be
the same.
The key chain can be different
EIGRP router configuration is not shown.
Thanhnd CCIE#50479
39
39
The authenticating key and a key ID on

both the sending router and the
receiving router must be the same.
The router uses the first, by key number, valid key for sending packets.
R1 (sending):
Will use key 1 for sending, from January 1st to 31st, 2009,
Will use key 2 for sending as of 4:00 am on January 25th, 2009.
Thanhnd CCIE#50479
40
40
The authenticating key and a key ID on

both the sending router and the
receiving router must be the same.
R1 (receiving):
Will accept key 1 for received packets, from January 1st 2009,
Will also accept key 2 for received packets, from January 25th 2009.
All other MD5 packets will be dropped.
Thanhnd CCIE#50479
41
41
Verifying Authentication
Thanhnd CCIE#50479
42
42
Verifying Authentication
Key chain R1chain and both keys key 1 (with authentication string
firstkey) and key 2 (with authentication string secondkey) are

displayed.
Under each key, the lifetime of the key is also shown.
Thanhnd CCIE#50479
43
43
EIGRP Metric
44
EIGRP
Composite
Metric and
the K
Values
EIGRP uses the following values in its composite metric to calculate the
preferred path to a network:
Bandwidth: The lowest bandwidth between source and destination.

Delay: The cumulative interface delay along the path
Reliability: Worst reliability between source and destination, based on
keepalives.
Load: Worst load on a link between source and destination, based on the
packet rate and the configured bandwidth of the interface.
Note: Although MTU is included in the routing table updates, it is not a
routing metric used by EIGRP or IGRP.
Thanhnd CCIE#50479
45
45
The Composite Metric
By default:
K1 and K3 are set to 1,

K2, K4, and K5 are set to 0.
The result is that only the bandwidth and delay values are used in the
computation of the default composite metric.
Thanhnd CCIE#50479
46
46
Using the
bandwidth
Command
Configure the
bandwidth
commands for R1,
R2 and R3.
R1(config)# inter s 0/0/0
R1(config-if)# bandwidth 64
Modify the bandwidth on the appropriate serial interfaces.
Be sure to modify both ends of the link.
Thanhnd CCIE#50479
47
47
Example
Metric
Calculation
Using the default values for K1 and K3, you can simplify this
calculation to:
slowest bandwidth (or minimum bandwidth)
plus cumulative sum of all the delays
-----------------------------------------------48
EIGRP route metric
Thanhnd CCIE#50479
48
DUAL
Successor
Feasible Distance (FD)
Feasible Successor (FS)
Reported Distance (RD) or Advertised Distance (AD)
Feasible Condition or Feasibility Condition (FC)
49
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
Thanhnd CCIE#50479
50
50
Successor and Feasible Distance

R2# show ip route
<code output omitted>
D
IP address of the
successor
192.168.1.0/24 [90/3012096] via 192.168.10.10, 00:12:32, Serial0/0/1
R3 is my successor
for getting to
192.168.1.0/24
Successo
r
A successor is a neighboring router that is used for packet forwarding and
is the least-cost route to the destination network.
What router is the successor for R2 for this network?
R3
Thanhnd CCIE#50479
51
Successor and Feasible Distance

R2# show ip route
<code output omitted>
D
Feasible Distance
192.168.1.0/24 [90/3012096] via 192.168.10.10, 00:12:32, Serial0/0/1
R3 is my successor
for getting to
192.168.1.0/24
Successo
r
Feasible distance (FD) is the lowest calculated metric to reach the
destination network.
The metric for the route.
Thanhnd CCIE#50479
52
52
Is R1 a Feasible Successor?
Does R2 know if R1 has a loop-free backup path to
192.168.1.0/24?
Remember, EIGRP is a Distance Vector Routing protocol.
Thanhnd CCIE#50479
53
Feasible
Successor
A feasible successor (FS) is a neighbor who has a loop-free backup
path to the same network as the successor by satisfying the

feasibility condition.
Would R2 consider R1 to be a feasible successor to network
192.168.1.0/24?
To be a feasible successor, R1 must satisfy the feasibility condition
(FC).
Thanhnd CCIE#50479
54
54
Sending the Reported Distance

I will send R2
my feasible
RD
distance to
2,170,112
reach
R2
192.168.1.0/24
as a reported
distance.
R1
Feasible
FD
Successor?
2,170,112
R1# show ip route
<Output omitted>
D
R3
192.168.1.0/24
192.168.1.0/24 [90/2170112] via 192.168.10.6, 02:44:50, Serial0/0/1
The reported distance (advertised distance) - EIGRP neighbors FD to the

same destination network.
The metric that a router reports to a neighbor about its own cost to that
network.
Feasibility Condition: The FC is met when a neighbors reported distance
55 destination
(RD) to a network is less than the local routers FD to the same
network.
Thanhnd CCIE#50479
55
Examining an Entry in
the Topology Table
R2# show ip eigrp topology

<Output omitted>
P 192.168.1.0/24, 1 successors, FD is 3012096
via 192.168.10.10 (3012096/2816), Serial0/0/1
via 172.16.3.1 (41024256/2170112), Serial0/0/0
Destination network
Indicates passive or
active state
Thanhnd CCIE#50479
Feasible distance
Number of successors
56
56
The Successor
<Output omitted>
via 192.168.10.10 (3012096/2816), Serial0/0/1
via 172.16.3.1 (41024256/2170112), Serial0/0/0
Next hop
address of
the successor
Thanhnd CCIE#50479
Feasible distance
Successors (R3)
Reported Distance
Outbound interface to
reach this network
57
57
The Feasible Successor

R2#show ip eigrp topology
<Output omitted>
via 192.168.10.10 (3012096/2816), Serial0/0/1
via 172.16.3.1 (41024256/2170112), Serial0/0/0
Next hop
address of the
feasible
successor (R1)
Thanhnd CCIE#50479
Feasible distance if
the feasible
successor (R1) was
the successor
Outbound interface to
reach this network
Feasible Successors (R1)
58
Reported Distance
58
The Reported Distance

is less than the Feasible
Distances, so it is a
Feasible Successor.
R2#show ip eigrp topology

<Output omitted>
via 192.168.10.10 (3012096/2816), Serial0/0/1
via 172.16.3.1 (41024256/2170112), Serial0/0/0
Thanhnd CCIE#50479
59
59
Example: No Feasible Successor
Thanhnd CCIE#50479
60
60
Feasible
Successor?
Successor
R1#show ip route
<Output omitted>
D
192.168.1.0/24 [90/2170112] via 192.168.10.6, 01:23:13, Serial0/0/1
Feasible Distance
Thanhnd CCIE#50479
Next-hop router (R3) is the successor

61
61
You can view all possible links

whether they satisfy the
feasible condition or not by
adding the [all-links]
Feasible
option.
Successor?
Even those routes that are
not FSs.
RD = 3,012.096
Does R2 meet the Feasibility
Condition?
FD = 2,170,112
Is R2s RD less than R1s
FD?
No! So does not meet
Feasibility Condition.
R1# show ip eigrp topology all-links
Successor
P 192.168.1.0/24, 1 successors, FD is 2170112, serno 9

via 192.168.10.6 (2170112/2816), Serial0/0/1 Successor
via 172.16.3.2 (41024256/3012096), Serial0/0/0 Not a
feasible
successor
R1s Feasible Distance
Thanhnd CCIE#50479
R2s Reported Distance
62
62
Even though R2 looks like a

viable backup path to
192.168.1.0/24, R1 has no idea
that its path is not a potential
loop back through itself.
Does this mean R2 cannot be
used if the successor fails?
R2 can be used, but there
will be a longer delay before
adding it to the routing
table.
Before this can happen,
DUAL will need to do some
further processing, which is
explained in the next topic.
New
Successor
FD = 2,170,112
R1# show ip eigrp topology all-links

P 192.168.1.0/24, 1 successors, FD is 2170112, serno 9
via 192.168.10.6 (2170112/2816), Serial0/0/1 Successor
via 172.16.3.2 (41024256/3012096), Serial0/0/0 Not a
feasible
successor
R1s Feasible Distance
Thanhnd CCIE#50479
R2s Reported Distance
63
63
DUAL Finite State Machine
The centerpiece of EIGRP is DUAL (EIGRP route-calculation engine).
DUAL Finite State Machine (FSM)

This FSM contains all the logic used to calculate and compare routes in an
EIGRP network.
Thanhnd CCIE#50479
64
64
DUAL FSM
FSMs defines:
The set of possible states that something can go through

What events cause those states
What events result from those states
Beyond the scope of this course.
Thanhnd CCIE#50479
65
65
FSM Example
HUNGRY
(START)
NO FOOD
FOR 5
HOURS
FOOD IS
IN EDIBLE
GET FOOD
EAT MORE
FOOD
FULL
EATIN G
NOT ENOUGH
FOOD
EAT ENOUGH
FOOD
Thanhnd CCIE#50479
66
66
When there is No Feasible Successor DUAL needed
Successor
No Feasible Successor
Thanhnd CCIE#50479
67
67
Successor
via 192.168.10.6 (2170112/2816), Serial0/0/1
Successor (R3)
Thanhnd CCIE#50479
No feasible successor
68
68
No Feasible Successor so DUAL is

initiated
192.168.1.0/24 network put into the
active state and shows that EIGRP
queries are sent to other neighbors.
R2 replies with a path to this network
This becomes the new successor
Installed into the routing table.
New
Successor
R1#debug eigrp fsm

EIGRP Finite State Machine debugging is on
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#interface s 0/0/1
R1(config-if)#shutdown
<Output omitted>
EIGRP-IPv4(1): Find FS for dest 192.168.1.0/24. FD is 2170112, RD is 2170112
DUAL: AS(1) Dest 192.168.1.0/24 entering active state for tid 0.
EIGRP-IPv4(1): dest(192.168.1.0/24) active
EIGRP-IPv4(1): rcvreply: 192.168.1.0/24 via 172.16.3.2 metric 41024256/3012096
EIGRP-IPv4(1): reply count is 1
EIGRP-IPv4(1): Find FS for dest 192.168.1.0/24. FD is 72057594037927935, RD is
72057594037927935
DUAL: AS(1) Removing dest 192.168.1.0/24, nexthop 192.168.10.6
DUAL: AS(1) RT installed 192.168.1.0/24 via 172.16.3.2
<Output omitted>
R1(config-if)#end
69
Thanhnd CCIE#50479
R1#undebug
all
69
Successor
X
via 172.16.3.2 (41024256/3012096), Serial0/0/0
Successor (R2)
Thanhnd CCIE#50479
70
70
If the link comes back

up and R3 is again the
successor..
R2 doesnt become the
feasible successor
because it doesnt
meet the feasibility
condition.
Even though it was
once the successor.
EIGRP is distance
vector!
Successor
via 192.168.10.6 (2170112/2816), Serial0/0/1
Successor (R3)
Thanhnd CCIE#50479
71
71
EIGRP Load Balancing
72
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 traffic generated by the
router.
Thanhnd CCIE#50479
73
Variance command
RD
FS
Succ
FS
Successor: R3 with a FD of 20
Feasible Successors: R2 and R5
R2s RD of 10 < R3s FD of 20
R5s RD of 10 < R3s FD of 20
R4 is NOT a FS because its RD of 25 > R3s FD of 20
Thanhnd CCIE#50479
74
74
Variance command
RD
FS
Succ
FS
Variance = 2
x 2 = 40
R1(config-router)# variance 2
R3s FDv 2 x 20 (FD) = 40

R2 is added as successor to R1s routing table: R2s FD of 30 < R3s FDv of 40
R5 is NOT added to R1s routing table: R5s FD of 50 > R3s FD v of 40
R5 would still be a Feasible Successor

Note: R4 is not considered even if its FD was < or = R3s FD v 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.
Thanhnd CCIE#50479
75
75
EIGRP Optimization
76
EIGRP Summarization
77
Manual Summarization
EIGRP can be configured to summarize routes, whether or not automatic
summarization (auto-summary) is enabled.
Thanhnd CCIE#50479
78
78
Manual Summarization
Only pertinent routes shown
192.168.1.0/24,
192.168.2.0/24,
192.168.3.0/24
192.168.1.0/24,
192.168.2.0/24,
192.168.3.0/24
R1#
D
D
D
show ip route
192.168.1.0/24 [90/2172416] via 192.168.10.6, 02:07:38, S0/0/1
192.168.2.0/24 [90/2297856] via 192.168.10.6, 00:00:34, S0/0/1
192.168.3.0/24 [90/2297856] via 192.168.10.6, 00:00:18, S0/0/1
R2#
D
D
D
show ip route
192.168.1.0/24 [90/3014400] via 192.168.10.10, 02:08:50, S0/0/1
192.168.2.0/24 [90/3139840] via 192.168.10.10, 00:01:46, S0/0/1
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.
Thanhnd CCIE#50479
79
79
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
Thanhnd CCIE#50479
80
80
Configure EIGRP
Manual
Summarization
192.168.0.0/22
192.168.0.0/22
Router(config-if)# ip summary-address eigrp as-number network-address

subnet-mask
R3(config)# interface serial 0/0/0
R3(config-if)# ip summary-address eigrp 1 192.168.0.0 255.255.252.0
R3(config)# interface serial 0/0/1
R3(config-if)# ip summary-address eigrp 1 192.168.0.0 255.255.252.0
R3# show ip route
Creates a Null0 summary
<output omitted>
route
D 192.168.0.0/22 is a summary, 00:00:06, Null0
Thanhnd CCIE#50479
81
81
Verify EIGRP
Manual
Summarization
192.168.0.0/22
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.
Thanhnd CCIE#50479
82
82
Automatic Summarization at Classful Network Boundary

Im an EIGRP for IPv4
router configured for
automatic summarization.
172.16.1.0/24
172.16.2.0/24
172.16.3.0/24
IPv4 Routing Table

172.17.0.0/30
R1
Summary Update: 172.16.0.0/16
R2
172.16.0.0/16 via R1
Classful Networks
Class A: 0.0.0.0 to 127.255.255.255
Class B: 128.0.0.0 to 191.255.255.255
Class C: 192.0.0.0 to 223.255.255.255
Default Mask: 255.0.0.0 or /8

Default Mask: 255.255.0.0 or /16
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.
83
Thanhnd CCIE#50479
83
Since IOS 15.0(1)M and 12.2(33), automatic
summarization is disabled.
R1(config-router)# no auto-summary
172.16.1.0/24
172.16.2.0/24
172.16.3.0/24
44
//22
..00 44
..11 00//22 44
1166 22.. //22
22.. 66.. ..00
1177 22..11 66..33
1177 22..11
1177
EIGRP for IPv4 automatic summarization

defaults
Prior, automatic summarization was enabled.

R1(config-router)# auto-summary
R3# show ip route eigrp

<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#
Thanhnd CCIE#50479
84
84
EIGRP Stub
85
Stub Routers
Introduced with IOS 12.0

Stub router
Only has one neighbor
Only needs a default route
Commonly used in a hub and spoke network topology.
Helps with convergence
Thanhnd CCIE#50479
86
Stub Routers
Queries
X
Im a Stub
Only the remote router is configured as a stub.

Only specified routes are propagated from the remote (stub) router.
Any neighbor will not query the stub router for any routes.
Stub router will send a special peer information packet to all
neighboring routers to report its status as a stub router.

Thanhnd CCIE#50479
87
87
Stub default: connected and summary

BR1A(config)#routereigrp1
BR1A(configrouter)#eigrpstub
HQ#showipeigrpneighborsdetail
(sec)(ms)CntNum
010.2.2.2Se0/0/01400:21:3720120015
Version16.0/2.0,Retrans:0,Retries:0,Prefixes:3
Topologyidsfrompeer0
StubPeerAdvertising(CONNECTEDSUMMARY)Routes
Suppressingqueries
MaxNbrs:0,CurrentNbrs:0
HQ#
Default: connected and summary
Thanhnd CCIE#50479
88
88
Stub Routers
Queries
X
Im a Stub
receive-only Stub does not send any route.
No other keyword can be specified,

Use this option if there is a single interface on the router.
connected (default) Stub sends connected routes if the EIGRP network
command is used (10.1.1.0/24).

Otherwise you will need to use the redistribute connected command under the
EIGRP process (later).
static Stub sends static routes in its routing table.
Redistributing static routes with the redistribute static command is still

necessary (later).
summary (default) Stub will send summary routes.
Configured with the ip summary-address eigrp command or automatically at a

major network border router with the auto-summary command enabled.
redistribute - Stub will send redistributed routes.
89
Redistributing routes with the redistribute command is still necessary.
Thanhnd CCIE#50479
89
eigrpstubconnected
Router B will advertise only
10.1.2.0/24 to Router A.
Notice that although 10.1.3.0/24 is
eigrpstubconnected
Thanhnd CCIE#50479
also a connected network.

It is not advertised to Router A
because there is not a network

10.1.3.0 0.0.0.255 command, and
connected routes are not redistributed.
90
90
eigrpstubsummary
10.1.2.0/23, the summary route that is

configured on the router, to Router A.
eigrpstubsummary
Thanhnd CCIE#50479
91
91
eigrpstubstatic
eigrpstubstatic
Thanhnd CCIE#50479
10.1.4.0/24, the static route that is

configured on the router, to Router A.
(Note that the redistribute static
command is configured on Router B.)
92
92
eigrpstubreceiveonly
Router B will not advertise anything to
Router A.
eigrpstubreceiveonly
Thanhnd CCIE#50479
93
93
eigrpstubredistributed
10.1.4.0/24, the redistributed static

route, to Router A.
eigrpstubredistributed
Thanhnd CCIE#50479
94
94
EIGRP Query and SIA
95
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.

This is 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.

When a router answers a query, it stops the spread of the query
through that branch of the network .
Thanhnd CCIE#50479
96
Stuck in Active (SIA)

Router
B
Queries
Replies
SIA
Router
C
Router D
Router
A
When EIGRP returns a stuck in active (SIA) message, it means that it

has not received a reply to a query.
Summarization can help prevent SIA.
Thanhnd CCIE#50479
97
97
Stuck-in-Active
EIGRP 101
EIGRP 102
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 (ASs) to simulate OSPF areas (later) will
help limit the scope of the queries.
Thanhnd CCIE#50479
This is not true, the boundary router will create a new EIGRP query into the
other EIGRP domain.
98
98
Preventing SIA
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.
Thanhnd CCIE#50479
99
99
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.
Thanhnd CCIE#50479
100
100
BEFORE Active Process Enhancement feature.
10.1.1.0/24 gone; no FS
Never heard from B
Query
So after 3 min reset adjacency along with all networks
3 min timer
10.1.1.0/24 gone; no FS
No entry so sends Query
Bad link; reply never makes it
No entry send Reply

10.1.1.0/24 gone;
Remove 10.1.1.0/24
101
Thanhnd CCIE#50479
101
AFTER Active Process Enhancement feature.

Thanks for letting me know,
I will not terminate our adjacency. A
After 1.5 min SIA Query
SIA Reply: Im ok but waiting on

B
C
After 1.5 min SIA Query
(3 attempts until I terminal
adjacency with C)
C
Thanhnd CCIE#50479
10.1.1.0/24 gone; no FS
Query
The neighbor relationship

between Routers A and B
remains intact.
10.1.1.0/24 gone; no FS
No entry so sends Query
Bad link; reply never makes it
No entry send Reply

10.1.1.0/24 gone;
Remove 10.1.1.0/24
102
102

EIGRP

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

EIGRP

Caricato da

Copyright:

Formati disponibili

Introduction

Enhanced IGRP is a Cisco-proprietary routing protocol released in 1992.

EIGRP was created as a classless version of IGRP.

the IETF as an informational RFC.

Convey routing information to known destinations.

Used to get specific information from a neighbor router.

Used to respond to a query.

The goal of any dynamic routing protocol is to:

Metric parameters must match (later)

AS number must match

Hello packets are sent on a regular interval.

hello before declaring that neighbor as unreachable.

EIGRP Packet Types

Acknowledgment (ACK) Packets

Queries and replies use reliable delivery.

eigrp router-id Command

R1(config)# router eigrp 1

R3(config)# router eigrp 1

Verify the R3 Routing

R3# show ip route | begin Gateway

IPv4 Routing Table EIGRP Routes

IPv4 Routing Protocols

IPv4 Routing Protocols

Variance For unequal

Observing Hello Packets

Observing EIGRP Packets

Configuring Passive Interfaces

EIGRP Interfaces after Passive

EIGRP Neighbors w/ Differing Timers

EIGRP Neighbors w/ Differing Timers

The bandwidth-percent command

bandwidth that may be used by EIGRP on an interface.

By default, EIGRP is set to use only up to 50% of the bandwidth of an

interface to exchange routing information.

In order to calculate its percentage, the bandwidth-percent command

relies on the value set by the bandwidth command.

Allows EIGRP to use up to 75 percent (42 kbps) of a 56-kbps serial link in

autonomous system 209.

Default Static Route

Simple and MD5 Authentication

Neighbor router authentication - Routers only participate in routing based on

Simple password authentication (also called plain text

Planning for EIGRP Authentication

MD5 Configuration Example

EIGRP router configuration is not shown.

MD5 authentication is configured on the

MD5 Configuration Example

serial 0/0/1 interface with:

enters configuration mode for the

Two keys are defined in this key chain.

and lifetime specified.

keys on all the routers in the network

of one week to change the keys on all

week before the expiration of key 1 to

Send and Receive Keys

MD5 Configuration Example

EIGRP packets depending upon the

key number) which has a valid

any valid key can be used as long as

router will use the first key (by key

Key 1 is set to firstkey.

MD5 Configuration Example

Acceptable for receiving EIGRP packets