Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
5 - EIGRP
IGRP EIGRP
Automatic redistribution between IGRP and EIGRP as long as “AS” numbers are the same.
– k1 for bandwidth
– k2 for load
– k3 for delay
– k4 and k5 for Reliability
EIGRP
Router(config-router)# metric
bandwidth is in kbps weights tos k1 k2 k3 k4 k5
Rick Graziani graziani@cabrillo.edu
Displaying Interface Values
shows reliability as a fraction of 255, for shows load as a fraction of 255, for
example (higher is better): example (lower is better):
rely 190/255 (or 74% reliability) load 10/255 (or 3% loaded link)
rely 234/255 (or 92% reliability) load 40/255 (or 16% loaded link)
rely 255/255 (or 100% reliability) load 255/255 (or 100% loaded link)
BWEIGRP and DLYEIGRP display values as sent in EIGRP updates and used in
calculating the EIGRP metric. Calculated values (cumulative) displayed in
routing table (show ip route).
Rick Graziani graziani@cabrillo.edu 8
SanJose2#show ip route
D 192.168.72.0/24 [90/2172416]
via 192.168.64.6, 00:28:26, Serial0
= 25,600 Bandwidth =
Westasman
25,600
S0/0 192.168.64.2/30 S0/1 192.168.64.6/30
T1
= (10,000,000/1544) * 256 Delay =
= 1,657,856 512,000
Fa0/0 192.168.1.1/24
EIGRP
AS 100
Rick Graziani graziani@cabrillo.edu
Determining the costs
Delay = (delay/10) * 256
Delay =
FastEthernet 2,560
= (100/10) * 256 Fa0/0 192.168.72.1/24
= 2,560 Bandwidth =
Westasman
25,600
S0/0 192.168.64.2/30 S0/1 192.168.64.6/30
T1
= (20,000/10) * 256 Delay =
= 512,000 512,000
Fa0/0 192.168.1.1/24
EIGRP
AS 100
Rick Graziani graziani@cabrillo.edu
Determining the costs
What is the cost (metric) for 192.168.72.0/24 from SanJose2?
Delay =
Cost: Slowest bandwidth
2,560
+ sum of delays Fa0/0 192.168.72.1/24
1,657,856 Bandwidth =
512,000 Westasman
25,600
2,560 S0/0 192.168.64.2/30 S0/1 192.168.64.6/30
--------------
2,172,416
The cost! Delay =
512,000
External
External
10,476 = 6,476(BW)+2,000(DLY)+2,000(DLY)
IGRP Metrics! (Does not multiply by 256.
• EIGRP will tag routes learned from IGRP, or any outside source, as
external because they did not originate from EIGRP routers.
• IGRP cannot differentiate between internal and external routes.
Rick Graziani graziani@cabrillo.edu 18
Features of EIGRP
• Smooth Round Trip Timer (SRTT) The average time it takes to send
and receive packets from a neighbor.
• This timer is used to determine the retransmit interval (RTO)
• Not only does the topology table track information regarding route states, but it
can also record special information for external routes, including the
administrator tag.
• EIGRP classifies routes as either internal or external.
• EIGRP uses a process called route tagging to add special tags to each route.
• These tags identify a route as internal or external, and may include other
information as well.
All external routes are included in the topology table, and are tagged with the
following information:
• The identification number (router ID) of the EIGRP router that redistributed the
route into the EIGRP network
– The EIGRP router ID is normally selected in the same manner as Open
Shortest Path First (OSPF)
– Can also use: eigrp router-id <router-id>
• The AS number of the destination
• The protocol used in that external network
• The cost or metric received from that external protocol
• The configurable administrator tag
Rick Graziani graziani@cabrillo.edu 26
Topology Table – Explained Soon!
Question: Since EIGRP has a topology table, does this make it a link-
state routing protocol?
Answer:
• No, the information in the topology table is not in the form of LSAs
describing the complete network topology.
• The EIGRP topology table contains information about paths through
the router’s adjacent neighbors.
• Also, EIGRP does not perform shortest-path calculation by calculating
the shortest-path tree, but instead uses the DUAL algorithm.
• EIGRP chooses the best (that is, successor) routes to a destination from the
topology table and places these routes in the routing table.
• Each EIGRP router maintains a topology table for each network protocol.
• EIGRP displays both internal EIGRP routes and external EIGRP routes.
RouterB#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default U - per-user static route
Gateway of last resort is not set
C 10.1.1.0 is directly connected, Serial0
D 172.16.0.0 [90/2681856] via 10.1.1.0, Serial0
D EX 192.168.1.0 [170/2681856] via 10.1.1.1, 00:00:04, Serial0
• The routing table contains the routes installed by DUAL as the best loop-free
paths to a given destination.
• EIGRP will maintain up to four routes per destination.
• These routes can be of equal, or unequal cost (if using the variance
command). (later)
RouterB#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default U - per-user static route
Gateway of last resort is not set
C 10.1.1.0 is directly connected, Serial0
D 172.16.0.0 [90/2681856] via 10.1.1.0, Serial0
D EX 192.168.1.0 [170/2681856] via 10.1.1.1, 00:00:04, Serial0
Routing Table
SanJose2#show ip route
D 192.168.72.0/24 [90/2172416]
via 192.168.64.6, 00:28:26, Serial0
Rick Graziani graziani@cabrillo.edu 32
Routing Tables
RTX#show ip route
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
D 192.168.5.0/24 [90/3219456] via 10.2.0.2, 00:12:19, Serial1
D 192.168.1.0/24 [90/2195456] via 10.1.0.1, 00:12:19, Serial0
C 192.168.2.0/24 is directly connected, Ethernet0
D 192.168.3.0/24 [90/2195456] via 10.2.0.2, 00:12:19, Serial1
What is FSM?
• An FSM is an abstract machine, not a mechanical device with
moving parts.
• FSMs define a set of possible states something can go through,
what events causes those states, and what events result from
those states.
• Designers use FSMs to describe how a device, computer
program, or routing algorithm will react to a set of input events.
HUNGRY
NO FOOD (START)
FOR 5
HOURS FOOD IS
INEDIBLE
GET FOOD
EAT ENOUGH
FOOD
• EIGRP is modular
• Different PDMs can be added to EIGRP as new routed protocols are
enhanced or developed:
– IPv4, IPv6, IPX, and AppleTalk
Each PDM is responsible for all functions related to its specific routed
protocol.
• The IP-EIGRP module is responsible for the following:
– Sending and receiving EIGRP packets that bear IP data
– Notifying DUAL of new IP routing information that is received
– Maintaining the results of DUAL’s routing decisions in the IP
routing table
– Redistributing routing information that was learned by other IP-
capable routing protocols
– Neighbor table
– Topology table
– Routing table
– Successor
– Feasible Successor
• We will first have an overview of all of the terminology and then see
how it works and what it all means!
Your route (metric) to the network (RD to me) must be LESS than my current route
(my total metric) to that same network. If your route (metric) to the network (RD to
me) is LESS than my current route (my total metric), I will include you as a
FEASIBLE SUCCESSOR.
If your route (metric) to the network (RD to me) is MORE than my current route (my
total metric), I will NOT include you as a FEASIBLE SUCCESSOR.
Rick Graziani graziani@cabrillo.edu 49
Successors and Feasible Successors
172.30.1.0
172.30.1.0
172.30.1.0
FD to 172.30.1.0 is
31 via Router Y
Current Successor = 31
RTZ is NOT Feasible
RD of RTY= 21 Successor, FC:
RD220 not< FD31
Advertised or
Destination Feasible Dist. Reported. Dist. Neighbor
172.30.1.0 40 30 X In Topology Table
172.30.1.0 31 21 Y In Routing Table
172.30.1.0 230 220 Z Not in Topology Table
Rick Graziani graziani@cabrillo.edu 51
Successors and Feasible Successors
Feasible Successor, FC: RD30 < FD31
172.30.1.0
FD to 172.30.1.0 is
31 via Router Y
Current Successor = 31
RTZ is NOT Feasible
RD of RTY= 21 Successor, FC:
RD220 not< FD31
172.30.1.0
FD to 172.30.1.0 is
X
40 via Router X
X 172.30.1.0
FD to 172.30.1.0 is
X
40 via Router X
?
RTZ is NOT Feasible
Current Successor = 40
RD of RTX= 30 Successor, FC:
RD220 not< FD40
• RTZ is not a feasible successor.
• It’s RD (220) is greater than the previous FD (40) for 172.30.1.0/24.
• Before this route can be installed, the route to net 24 must be placed in the
active state and recomputed.
• Coming soon!
Rick Graziani graziani@cabrillo.edu 56
Successors and Feasible Successors
X 172.30.1.0
FD to 172.30.1.0 is
X
230 via Router Z
Reported Distance
Reported Distance: This is the distance (cost) reported by the neighboring router, ie.
Westasman and SanJose1.
• Westasman’s Reported Distance is 28,160 = 25,600 (BW) + 2,560 (DLY)
• SanJose1’s Reported Distance is 2,172,416 = 1,657,856 (BW) + 512,000 (DLY) +
2,560 (DLY)
Feasible Successor: Since SJ1’s Reported Distance 2172416 is less than or
equal to the Feasible Distance 2172416, it is included as a Feasible
Successor!
Rick Graziani graziani@cabrillo.edu 62
Questions
Question: Why does EIGRP use DUAL? I.e. Why doesn’t EIGRP install
routes with an RD greater than its current FD?
Answer: EIGRP is a distance vector routing protocol. It only knows about
distances/routes from what its’ neighbors tell it. The only way EIGRP can
trust that another router’s route is not back through itself, is to make sure
the other router’s distance is equal to or less than its own distance to that
network.
http://www.rware.demon.co.uk/eigrp.htm
Rick Graziani graziani@cabrillo.edu 70
Version - there has only been one version
Opcode - this is the EIGRP packet type:
1 - Update
3 - Query
EIGRP Packet Format (FYI)
4 - Reply http://www.rware.demon.co.uk/eigrp.htm
5 - Hello
6 - IPX SAP
Checksum - this is calculated for the whole EIGRP portion of the IP datagram
Flags - The LSB (0x00000001) is the Init bit meaning that the route in this packet is the first in a new neighbor relationship. The
next bit (0x00000002) is the Conditional Receive bit used in Cisco's Reliable Multicasting algorithm.
Sequence - the 32-bit sequence number used by RTP.
ACK - the 32-bit sequence last heard from the neighbor. A Hello packet with a non-zero value is an ACK.
AS Number - the Autonomous System number of the EIGRP domain.
Type/Length/Value (TLV) - There are a number of TLVs, all of them begin with a 16 bit Type field and a 16 bit Length field. There
then follows a number of fields that vary depending on the type as given below.
General TLVs
0x0001 - General EIGRP parameters (applies to any EIGRP packet regardless of protocol)
0x0003 - Sequence (used by Cisco's Reliable Multicast)
0x0004 - EIGRP software version, the original version being 0 and the current version being 1 (used by Cisco's Reliable
Multicast)
0x0005 - Next Multicast Sequence (used by Cisco's Reliable Multicast)
IP TLVs
0x0102 - IP internal routes
0x0103 - IP external routes
AppleTalk TLVs
0x0202 - AppleTalk internal routes
0x0203 - AppleTalk external routes
0x0204 - AppleTalk cable setup
IPX TLVs
0x0302 - IPX internal routes
0x0303 - IPX external routes
Rick Graziani graziani@cabrillo.edu 71
Query and Reply Packets
• Entries in the topology table can be in one of two states: active or passive.
• A passive route is one that is stable and available for use.
• An active route is a route in the process of being recomputed by DUAL.
RtrB
Queries
Replies
RtrE
RtrA
X
RtrF
RtrC
RtrG
X 172.30.1.0
Queries
Replies
?
RTZ was previously
NOT a Feasible
Successor, FC: RD220
not< FD31 or FD40, but
now there is no
Sucessor
RTZ replies that it still has a route to 172.30.1.0, while RTX and RTY reply
that they do not.
Current Successor is now RTZ, with a FD of 230 and a RD of RTZ= 220.
Rick Graziani graziani@cabrillo.edu 76
In this scenario…
X
Queries
Replies
All
X
Replies
are
saying
they do
?
not have
a route
RTZ has a Reported Distance to
RTA of 220. Since its Reported
Distance is greater than RTA’s
Cost=89 Cost=99
own Feasibile Distance of 31,
RTA can’t trust that the route
Cost=100 RTZ takes is somehow back
through itself.
Rick Graziani graziani@cabrillo.edu 77
Example from the curriculum…
1 2
3 4
5 6
Feasible successor is in the topology table. Backup route takes over right away.
Westasman#debug eigrp fsm
02:21:42: DUAL: Find FS for dest 192.168.64.4/30. FD is 2169856, RD is
2169856
02:21:42: DUAL: 0.0.0.0 metric 2169856/0
02:21:42: DUAL: 192.168.64.1 metric 4294967295/4294967295
found Dmin is 216985
Queries
Replies
B
X
Router
A X
X
X
In some cases, it can take too long for the query to be answered.
When this happens, the router that issued the query gives up and resets its
neighbor relationship with the router that didn’t answer.
The most basic situation where this occurs is when it simply takes too long
for a query to reach the other end of the network and a reply to travel back.
Rick Graziani graziani@cabrillo.edu 81
Stuck in Active (SIA)
Troubleshooting Steps:
Step 1: find the routes which are consistently being reported as stuck in
active.
– If you are logging console messages, a quick perusal of the log will
indicate which routes are being marked as stuck in active most
often.
Step 2: find out which routers are consistently failing to answer queries (not
always easy).
– Use the show ip eigrp topology active command.
• Any neighbors which have the r beside them are neighbors that
the router is waiting on replies from
• the active timer is how long the route has been active.
• pay particular attention to routes that have replies outstanding
and have been active for 2 to 3 minute
Step 3: find the reason why that router is not receiving or answering queries
– One you have found the router that is consistently not answering
queries, look for problems on the link to this neighbor, memory or
CPU utilization problems with this neighbor, etc.
• Depending on the cause, you may have to restrict the “query range” of
EIGRP routers.
– You may have to redesign parts of the network
• Although not recommended, you can also increase the amount of time
the router will wait after sending a query out before declaring the route
stuck in active.
• This can be changed using the command:
timers active-time time in minutes
Router(config-router)#network network-number
• The network command configures only connected networks.
Router(config-router)#eigrp log-neighbor-changes
• This command enables the logging of neighbor adjacency changes to
monitor the stability of the routing system and to help detect problems.
Router(config-if)#bandwidth kilobits
• When configuring serial links using EIGRP it is important to configure
the bandwidth setting on the interface. If the bandwidth setting is not
changed for these interfaces EIGRP assumes the default bandwidth
on the link instead of the true bandwidth.
Rick Graziani graziani@cabrillo.edu 88
EIGRP and the bandwidth command
If care is not taken in the configuration of the WAN, EIGRP can swamp the network.
The following three rules should be adhered to when configuring EIGRP over an
NBMA cloud such as Frame Relay:
1. EIGRP traffic should not exceed the CIR capacity of the virtual circuit (VC).
2. The aggregated traffic EIGRP has over all the VCs should not exceed the
access line speed of the interface.
3. The bandwidth allocated to EIGRP on each VC must be the same in both
directions.
Rick Graziani graziani@cabrillo.edu 89
EIGRP and the bandwidth command
If care is not taken in the configuration of the WAN, EIGRP can swamp the network.
2. Use subinterfaces.
• The bandwidth command may be configured on each subinterface, which allows
different speeds on each VC. (For routing metric purposes only!)
• In this case, subinterfaces are configured for the links with the differing CIRs.
• The links that have the same configured CIR are presented as a single subinterface with
a bandwidth reflecting the aggregate CIR of all the circuits. Three of the VCs have the
same CIR, 256 Kbps. All three VCs are grouped together as a multipoint subinterface,
serial 0/0.1.
• The single remaining VC, which has a lower CIR, 56 Kbps, can be assigned a point-to-
point subinterface, serial0/0.2.
Rick Graziani graziani@cabrillo.edu 91
The bandwidth-percent command
RTC(config)#interface serial0/0
RTC(config-if)#ip summary-address eigrp 2446 2.1.0.0 255.255.0.0
RTC(config)#interface serial0/0
RTC(config-if)#ip summary-address eigrp 2446 2.1.0.0 255.255.0.0
• Notice that the summary route is sourced from Null0, and not an actual interface.
• That is because this route is used for advertisement purposes and does not represent a
path that RTC can take to reach that network.
• On RTC, this route has an administrative distance of 5.
• RTD is oblivious to the summarization but accepts the route. It assigns the route the
administrative distance of a "normal" EIGRP route, which is 90, by default
Let's look at an example, there are three ways to get to Network X, from
Router E: (Note: metrics incorrectly not including outgoing interface to
Net X.)
E-B-A with a metric of 30
E-C-A with a metric of 20 <<<-- Minimum Metric
E-D-A with a metric of 45
Rick Graziani graziani@cabrillo.edu 101
EIGRP variance command
router eigrp 1
network x.x.x.x
variance 2
variance 2
• This increases the minimum metric to 40 (2 * 20 = 40).
• EIGRP includes all the routes that have a metric less than or equal
to 40, and are feasible successors.
• In the above configuration, EIGRP now uses two paths to get to
Network X, E-C-A and E-B-A, because both paths have a metric
under 40.
Rick Graziani graziani@cabrillo.edu 102
EIGRP variance command
router eigrp 1
network x.x.x.x
variance 2
EIGRP doesn't use path E-D-A because it has a metric of 45, and it's not a feasible
successor. Can have up to 6 unequal cost paths.
Rick Graziani graziani@cabrillo.edu 103
EIGRP Traffic Share
• To control how traffic is distributed among routes when there are
multiple routes for the same destination network that have different
costs, use the traffic-share router configuration command.
• To disable this function, use the no form of the command.
balanced
• Distributes traffic proportionately to the ratios of the metrics.
min
• Uses routes that have minimum costs
Gateway Router
ip route 0.0.0.0 0.0.0.0 x.x.x.x (next hop)
!
router eigrp 100
redistribute static
<text omitted>
Ip default-network
• Propagates a default route to other routers, but needs to have a
route or default route out once the packets arrive.
Gateway Router
router igrp 24
<text omitted>
network 207.21.20.0
ip route 0.0.0.0 0.0.0.0 207.21.20.1
ip default-network 207.21.20.0
Supports CIDR and VLSM, rapid Supports CIDR and VLSM, rapid
convergence, partial updates, neighbor convergence, partial updates, neighbor
discovery discovery
Administrator can define route Automatic route-summarization and user-
summarization defined route summaries
Analogies:
Think of bandwidth as the width of the pipe
and
delay as the length of the pipe.
Use show interface command to view the metrics used on a specific interface
that is routing EIGRP.
• These are the raw values.
reliability load
• IGRP/EIGRP metric uses the sum of all of the delays of all of the outbound
interfaces to the destination network.
Rick Graziani graziani@cabrillo.edu 117
Metric Calculation
EIGRP
• bandwidth = (10,000,000/bandwidth) * 256
• delay = (delay/10) * 256
Note: The reference-bandwidth
For both IGRP and EIGRP: 107, (10,000,000/bandwidth kbps), whereas
with OSPF it was 108 (100,000,000/bandwidth)
The difference:
• IGRP metric is 24 bits long
• EIGRP metric is 32 bits long
• EIGRP metric is 256 times greater for the same route
• EIGRP allows for finer comparison of potential routes
BWEIGRP and DLYEIGRP display values as sent in EIGRP updates and used in
calculating the EIGRP metric. Calculated values (cumulative) displayed in
routing table (show ip route).
Rick Graziani graziani@cabrillo.edu 120
IGRP Metrics
Values displayed in show interface
commands and sent in routing updates.
BWIGRP and DLYIGRP display values as sent in IGRP updates and used in calculating
the IGRP metric. Calculated values (cumulative) displayed in routing table
(show ip route). EIGRP values are 256 times greater.
Rick Graziani graziani@cabrillo.edu 121
Metric Calculation
reliability load
The metrics used by EIGRP in making routing decisions are (lower the
metric the better):
• bandwidth
• delay
• load
• reliability
Reliability
• Reliability is measure dynamically
• Uses error rate for measurement
• Reflects the total outgoing error rates of the interfaces along the
route
• Calculated on a five minute weighted average, so not to allow
sudden peaks and valleys to make a significant impact
reliability load
Note: Even though load and reliability are dynamically changing values,
EIGRP will not recalculate the route metric when these parameters
change.
reliability load
shows load as a fraction of 255, for example:
load 10/255 (or 3% loaded link)
load 40/255 (or 16% loaded link)
load 255/255 (or 100% loaded link)
Default:
k1=k3=1 and k2=k4=k5=0
• You may change the k values to change what you want to give more or less weight to.
– k1 for bandwidth
– k2 for load
– k3 for delay
– k4 and k5 for Reliability
• Higher the k value, the more that part of the metric is used to calculate the overall IGRP
metric
Rick Graziani graziani@cabrillo.edu 129
Reliability and Load
Turning the knobs:
We can use the other metrics of Reliability and Load by adjusting their k values
to something greater than “0”
Notes:
• tos is always set to 0; at one time it was Cisco’s intent to use it, but it was
never implemented
• EIGRP neighbors must agree on K values to establish an adjacency and to
avoid routing loops.
Caution!
• Know what the impact will be before changing the defaults.
• It can give you unexpected results if you do not know what you are doing!
• If you modify the weights, you should configure all routers so they are all using
the same weight values.