Packet tracer lab

EIGRP Concepts, Configuration, and

Troubleshooting

Dr. C. BouSaba

EIGRP

• “Enhanced” Interior Gateway Routing Protocol and based on IGRP. • Developed to allow easy transition from IGRP to EIGRP. (“Like IGRP+”) • Cisco proprietary, released in 1994 • EIGRP is an advanced distanceadvanced distance--vectorvector RP relying on features commonly

associated with link-state protocols. (also called hybrid routing protocolhybrid routing protocol).

• Note: The Hybrid term sometimes misleads people into thinking EIGRP has the topology benefits of a link state routing protocol. It does not. EIGRP is a distance vector routing protocol and suffers from all of the disadvantages of any other distance vector routing protocol, i.e. routing loops.

• Note: “Often described as a hybrid routing protocol offering the best of distance-vector and link-state algorithms.” - I would say “features of distance-vector and link-state” not necessarily “the best.”

IGRP and EIGRP: A migration path

Automatic redistribution between IGRP and EIGRP as long as “AS” numbers are the same.

Outside routes (redistributed) are tagged as

external routes.

No differentiation between internal and

external routes.

Maximum Hop Count = 224Maximum Hop Count = 255

bandwidth = (10,000,000/bandwidth kbps) * 256

delay = (delay/10) * 256

32 bit metric for bandwidth and delay

bandwidth = (10,000,000/bandwidth kbps)

delay = delay/10

24 bit metric for bandwidth and delay

Classless Routing Protocol

• VLSM, CIDR

Classful Routing Protocol

EIGRPIGRP

Metric Calculations

• EIGRP Delay = IGRP Delay x 256 = (Delay / 10) x 256 • EIGRP Bandwidth = IGRP Bandwidth x 256 = (107 / Bandwidth) x 256 • EIGRP Metric = IGRP metric x 256

• EIGRP Metric = 256*([K1*Bw + K2*Bw/(256-Load) + K3*Delay]*[K5/(Reliability + K4)]).

• The default values for weights are: • K1 - 1 k1 for bandwidth (Kbps) • K2 - 0 k2 for load • K3 - 1 k3 for delay • K4 - 0 k4 and k5 for Reliability • K5 - 0

• if K5 = 0 � [K5/(Reliability + K4)] = 0 – The default EIGRP metric = 256*(Bw + Delay)

• Router(config-router)# metric weights tos k1 k2 k3 k4 k5

Displaying Interface Values

shows reliability as a fraction of 255, for example (higher is better):

rely 190/255 (or 74% reliability)

rely 234/255 (or 92% reliability)

rely 255/255 (or 100% reliability)

Router> show interface s0/0

Serial0/0 is up, line protocol is up

Hardware is QUICC Serial

Description: Out to VERIO

Internet address is 207.21.113.186/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

rely 255/255, load 246/255

Encapsulation PPP, loopback not set

Keepalive set (10 sec)

<output omitted>

Bandwidth Delay

Reliability Load

shows load as a fraction of 255, for

example (lower is better):

load 10/255 (or 3% loaded link)

load 40/255 (or 16% loaded link)

load 255/255 (or 100% loaded link)

Routing Table MetricRouting Table Metric

• Default: Slowest of bandwidth plus the sum of the delays of all outgoing interfaces from “this router” to the destination network.

Media

Bandwidth

K= kilobits

BWEIGRP

10,000,000/Bandwidth

*256

Delay

DLYEIGRP Delay/10

*256

100M ATM 100,000K 25,600 100 µµµµS 2,560

Fast Ethernet 100,000K 25,600 100 µµµµS 2,560

FDDI 100,000K 25,600 100 µµµµS 2,560

HSSI 45,045K 56,832 20,000 µµµµS 512,000

16M Token Ring 16,000K 160,000 630 µµµµS 16,128

Ethernet 10,000K 256,000 1,000 µµµµS 25,600

T1 (Serial

Default) 1,544K 1,657,856 20,000 µµµµS 512,000

512K 512K 4,999,936 20,000 µµµµS 512,000

DS0 64K 40,000,000 20,000 µµµµS 512,000

56K 56K 45,714,176 20,000 µµµµS 512,000

BWEIGRP and DLYEIGRP display values as sent in EIGRP updates and used in calculating the EIGRP metric.

EIGRP Metrics Values displayed in show interface

commands and sent in routing updates.

Calculated values (cumulative) displayed in routing table (show ip route).

The Routing Table: Metrics Calculation

How does SanJose2 calculate the cost for this route?

Displaying Interface Values

Westasman> show interface fa0/0

Ethernet0 is up, line protocol is up

Hardware is Lance, address is 0010.7b3a.cf84 (bia 0010.7b3a.cf84)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

rely 255/255, load 1/255

<output omitted>

SanJose2> show interface s0/0

Serial0/0 is up, line protocol is up

Hardware is QUICC Serial

Description: Out to Westasman

Internet address is 192.168.64.5/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

rely 255/255, load 246/255

<output omitted>

S0/0 192.168.64.2/30

S0/0 192.168.64.1/30

S0/1 192.168.64.6/30

S0/0 192.168.64.5/30

Fa0/0 192.168.72.1/24

Fa0/0 192.168.1.1/24

Fa0/0 192.168.1.2/24

EIGRP AS 100

Bandwidth = (10,000,000/bandwidth kbps) * 256

Westasman

SanJose1 SanJose2

Bandwidth = 1,657,856

Bandwidth = 25,600

Delay = 512,000

Delay = 2,560

Determining the costs

FastEthernet

= (10,000,000/100,000) * 256

= 25,600

T1

= (10,000,000/1544) * 256

= 1,657,856

S0/0 192.168.64.2/30

S0/0 192.168.64.1/30

S0/1 192.168.64.6/30

S0/0 192.168.64.5/30

Fa0/0 192.168.72.1/24

Fa0/0 192.168.1.1/24

Fa0/0 192.168.1.2/24

EIGRP AS 100

Delay = (delay/10) * 256

Westasman

SanJose1 SanJose2

Bandwidth = 1,657,856

Bandwidth = 25,600

Delay = 512,000

Delay = 2,560

Determining the costs

FastEthernet

= (100/10) * 256

= 2,560

T1

= (20,000/10) * 256

= 512,000

S0/0 192.168.64.2/30

S0/0 192.168.64.1/30

S0/1 192.168.64.6/30

S0/0 192.168.64.5/30

Fa0/0 192.168.72.1/24

Fa0/0 192.168.1.1/24

Fa0/0 192.168.1.2/24

EIGRP AS 100

What is the cost (metric) for 192.168.72.0/24 from SanJose2?

Westasman

SanJose1 SanJose2

Bandwidth = 1,657,856

Bandwidth = 25,600

Slowest!

Delay = 512,000

Delay = 2,560

1,657,856

512,000 2,560

-------------- 2,172,416

Cost: Slowest bandwidth

+ sum of delays

The cost!

Determining the costs

bandwidth = (10,000,000/bandwidth kbps) * 256

delay = (delay/10) * 256

The Routing Table

Administrative Distance / Metric

SanJose2#show ip route

D 192.168.72.0/24 [90/2172416] via 192.168.64.6, 00:28:26, Serial0

EIGRP and IGRP compatibility

• Automatic redistribution occurs when the same AS number is used for EIGRP and IGRP.

• EIGRP scales the IGRP metric by a factor of 256. • IGRP reduces the metric by a factor of 256.

EIGRP and IGRP compatibility

• 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.

10,476 = 6,476(BW)+2,000(DLY)+2,000(DLY)

IGRP Metrics! (Does not multiply by 256.

External

External

Features of EIGRP

• Classless Routing Protocol (VLSM, CIDR)

• Faster convergence times and improved scalability

• Multiprotocol support: TCP/IP, IPX/SPX, Appletalk

– There is no IPX/SPX or Appletalk in CCNA or CCNP

• Rapid Convergence and Better handling of routing loops – (DUAL) (coming) • Efficient Use of Bandwidth

– Partial, bounded updates: Incremental updates only to routers that need them.

– Minimal bandwidth consumption: Uses Hello packets and EIGRP packets by

default use no more that 50% of link’s bandwidth EIGRP packets.

• PDM (Protocol Dependent Module)

– Keeps EIGRP is modular

– Different PDMs can be added to EIGRP as new routed protocols are enhanced

or developed: IPv4, IPv6, IPX, and AppleTalk

• Unequal-cost load balancing same as IGRP (unlike OSPF)

EIGRP Terminology

• Neighbor table – Each EIGRP router maintains a neighbor table that lists adjacent routers. This table is comparable to the adjacency database used by OSPF. There is a neighbor table for each protocol that EIGRP supports.

• Topology table – Every EIGRP router maintains a topology table for each configured network protocol. This table includes route entries for all destinations that the router has learned. All learned routes to a destination are maintained in the topology table.

• Routing table – EIGRP chooses the best routes to a destination from the topology table and places these routes in the routing table. Each EIGRP router maintains a routing table for each network protocol.

• Successor – A successor is a route selected as the primary route to use to reach a destination. Successors are the entries kept in the routing table. Multiple successors for a destination can be retained in the routing table.

• Feasible successor – A feasible successor is a backup route. These routes are selected at the same time the successors are identified, but are kept in the topology table. Multiple feasible successors for a destination can be retained in the topology table.

• Each EIGRP router maintains a neighbor table that lists adjacent routers. • This table is comparable to the adjacency database used by OSPF. • There is a neighbor table for each protocol that EIGRP supports • Whenever a new neighbor is discovered, the address of that neighbor and

the interface used to reach it are recorded in a new neighbor table entry.

RouterC#show ip eigrp neighbors

IP-EIGRP neighbors for process 44

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 192.168.0.1 Se0 11 00:03:09 1138 5000 0 6

1 192.168.1.2 Et0 12 00:34:46 4 200 0 4

Neighbor Table

RouterC#show ip eigrp neighbors

IP-EIGRP neighbors for process 44

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 192.168.0.1 Se0 11 00:03:09 1138 5000 0 6

1 192.168.1.2 Et0 12 00:34:46 4 200 0 4

• Neighbor address The network-layer address of the neighbor router(s). • Queue count The number of packets waiting in queue to be sent. If this value is

constantly higher than zero, then there may be a congestion problem at the router. A

zero means that there are no EIGRP packets in the queue.

Neighbor Table

• 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)

• Hold Time The interval to wait without receiving anything from a neighbor before considering the link unavailable.

• Originally, the expected packet was a hello packet, but in current Cisco IOS software releases, any EIGRP packets received after the first hello will reset the timer.

• Note that an EIGRP router can maintain multiple neighbor tables, one for each L3 protocol running (for example, IP, AppleTalk).

• A router must run a unique EIGRP process for each routed protocol.

RTX#show ip eigrp neighbors

IP-EIGRP neighbors for process 1

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

1 10.2.0.2 Se1 12 00:27:39 333 1998 0 10

0 10.1.0.1 Se0 14 01:17:14 40 240 0 27

RTX#show ipx eigrp neighbors

IPX EIGRP Neighbors for process 22

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

1 2000.0000.0c76.080c Se1 14 00:04:21 28 200 0 22

0 1000.0000.0c38.6fa2 Se0 14 00:04:24 28 200 0 22

RTX#show appletalk eigrp neighbors

AT/EIGRP Neighbors for process 1, router id 2

H Address Interface Hold Uptime SRTT RTO Q Seq

(sec) (ms) Cnt Num

0 1000.123 Se0 11 00:15:01 8 200 0 7

1 2000.28 Se1 14 00:41:11 11 200 0 9

Neighbor Table

• Topology table – Each EIGRP router maintains a topology

table for each configured net. protocol.

– This table includes route entries for all

destinations that the router has learned.

– All learned routes to a destination are

maintained in the topology table.

• EIGRP uses its topology table to store all the info. it needs to calculate a set of distances and

vectors to all reachable destinations.

Topology Table

SanJose2#show ip eigrp topology all-links

P 192.168.72.0/24, 1 successors, FD is 2172416, serno 93

via 192.168.64.6 (2172416/28160), Serial0

via 192.168.1.1 (2174976/2172416), FastEthernet0

P 192.168.64.0/30, 1 successors, FD is 2172416, serno 91

via 192.168.1.1 (2172416/2169856), FastEthernet0

via 192.168.64.6 (2681856/2169856), Serial0

P 192.168.64.4/30, 1 successors, FD is 2169856, serno 72

via Connected, Serial0

P 192.168.1.0/24, 1 successors, FD is 28160, serno 1

via Connected, FastEthernet0

• 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

Topology Table – Extra Information

RTX#sh ip eigrp top 204.100.50.0

IP-EIGRP topology entry for 204.100.50.0/24

State is Passive, Query origin flag is 1, 1 Successor(s), FD is 2297856

Routing Descriptor Blocks:

10.1.0.1 (Serial0), from 10.1.0.1, Send flag is 0x0

Composite metric is (2297856/128256), Route is External

Vector metric:

Minimum bandwidth is 1544 Kbit

Total delay is 25000 microseconds

Reliability is 255/255

Load is 1/255

Minimum MTU is 1500

Hop count is 1

External data:

Originating router is 192.168.1.1

AS number of route is 0

External protocol is Connected, external metric is 0

Administrator tag is 0 (0x00000000)

FD/RD

Topology Table

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.

Alex Zinin, Cisco IP Routing

Topology Table

• EIGRP chooses the best routes (that is, successor) 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. • 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

IP Routing Table

SanJose2#show ip route

D 192.168.72.0/24 [90/2172416]

via 192.168.64.6, 00:28:26, Serial0

Routing Table

Showing the cost in the Routing Table

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

RTX#show ipx route

11 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.

No default route known.

C 1000 (HDLC), Se0

E 3000 [2681856/0] via 2000.0000.0c76.080c, age 00:10:49, 1u, Se1

E 4000 [276864000/2] via 2000.0000.0c76.080c, age 00:10:41, 1u, Se1

RTX#show appletalk route

Codes: R - RTMP derived, E - EIGRP derived, C - connected, A - AURP

S - static P - proxy

6 routes in internet

The first zone listed for each entry is its default (primary) zone.

E Net 100-101 [1/G] via 1000.123, 1400 sec, Serial0, zone san fran

E Net 300-301 [1/G] via 2000.28, 3016 sec, Serial1, zone san jose

Routing Tables

• EIGRP routers keep route and topology information readily available in RAM so that they can react quickly to changes.

• Like OSPF, EIGRP keeps this information in several tables, or databases.

– 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!

EIGRP Terminology and Operations

• Successor – Current Route

– A successor is a route selected as the primary route to use to reach a destination.

– Successors are the entries kept in the routing table.

• Feasible Successor - A backup route

– A feasible successor is a backup route.

– These routes are selected at the same time the successors are identified, but they are kept in the topology table.

– Multiple feasible successors for a destination can be retained in the topology table.

Let’s see how this works!

EIGRP Terminology and Operations

Successors and Feasible Successors

Successors and Feasible Successors

Successors and Feasible Successors

Feasible distance (FD) is the minimum distance (metric) along a path to a

destination network.

Reported distance (RD) is the distance (metric) towards a destination as advertised

by an upstream neighbor. Reported distance is the distance reported in the

queries, the replies and the updates.

A neighbor meets the feasible condition(FC) if the reported distance by the

neighbor is smaller than or equal to the current feasible distance (FD) of this

router. "If a neighbors metric is less than mine, then I know the neighbor doesn't

have a loop going through me."

A feasible successor is a neighbor whose reported distance (RD) is less than the current feasible distance (FD). Feasible successor is one who meets the feasible

condition (FC).

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.

Successors and Feasible Successors

Successors and Feasible Successors

172.30.1.0

172.30.1.0

Successors and Feasible Successors

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

Current Successor = 31 RD of RTY= 21

Feasible Successor, FC: RD30 < FD31

FD to 172.30.1.0 is 31 via Router Y

172.30.1.0

RTZ is NOT Feasible

Successor, FC: RD220 not< FD31

Successors and Feasible Successors

Current Successor = 31 RD of RTY= 21

Feasible Successor, FC: RD30 < FD31

FD to 172.30.1.0 is 31 via Router Y

172.30.1.0

• RTY is successor with a computed cost of 31. • “31” is the Feasible Distance (FD). • RTX is a feasible successor because its RD is less than or equal to the FD.

- RTX’s RD (30) is less than the FD (31).

RTZ is NOT Feasible

Successor, FC: RD220 not< FD31

Example of a Loop, What if…

Cost=9

Cost=40Cost=40

RTZ has a Reported Distance to

RTA of 220. Since its Reported Distance is greater than RTA’s own Feasibile Distance of 31, RTA can’t trust that the route RTZ takes is somehow back

through itself.

RTZ FD = 220

RTZ to RTA is 189

RTA to

172.30.1.0 is 31

172.30.1.0

Feasible Successor exists:

• If current successor route fails, feasible successor becomes the current successor, i.e. the current route.

• Routing of packets continue with little delay.

No Feasible Successor exists:

• This may be because the Reported Distance is greater than the Feasible Distance.

• Before this route can be installed, it must be placed in the active state and recomputed. (later)

• Routing of packets continue but with more of a delay.

What if the successor fails?

Successors and Feasible Successors

Current Successor = 40 RD of RTX= 30

New Successor

FD to 172.30.1.0 is 40 via Router X

172.30.1.0

RTZ is NOT Feasible

Successor, FC: RD220 not< FD31

X

• Since RTX is the feasible successor, and becomes the successor. • RTX is immediately installed from the topology table into the routing table (no recomputation

of DUAL).

• RTA’s new FD via RTX is 40. • RTZ is not a feasible successor, because it’s RD (220) is still greater than the new FD (40)

for 172.30.1.0/24.

Successors and Feasible Successors

Current Successor = 40 RD of RTX= 30

FD to 172.30.1.0 is 40 via Router X

172.30.1.0

RTZ is NOT Feasible

Successor, FC: RD220 not< FD40

X

• 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!

X

?

Successors and Feasible Successors

Current Successor = 230 RD of RTZ= 220

FD to 172.30.1.0 is 230 via Router Z

172.30.1.0

RTZ is NOT Feasible

Successor, FC: RD220 not< FD40

X

• After a a series of EIGRP Queries and Replies (coming), and a recomputation of DUAL, RTZ becomes the successor.

• There is nothing better to prohibit it from being the successor.

X

Topology table

• Each EIGRP router maintains a topology table for each configured network protocol.

• This table includes route entries for all destinations that the router has learned. All learned routes to a destination are maintained in the topology table.

show ip eigrp topology

• (Feasible Distance/Reported Distance) • 1 successor (route) if FDs are different

– smaller FD metric, that route is the the only successor

– larger FD metric, those routes are possible feasible successor

• 2 or more successors (routes) if FDs are the same – Load balancing happens automatically

One last reminder….

Understanding the Topology Table (not in the curriculum)

SanJose2#show ip eigrp top all

P 192.168.72.0/24, 1 successors, FD is 2172416, serno 93

via 192.168.64.6 (2172416/28160), Serial0

via 192.168.1.1 (2174976/2172416), FastEthernet0

P 192.168.64.0/30, 1 successors, FD is 2172416, serno 91

via 192.168.1.1 (2172416/2169856), FastEthernet0

via 192.168.64.6 (2681856/2169856), Serial0

SanJose2#show ip eigrp top all

P 192.168.72.0/24, 1 successors, FD is 2172416, serno 93

via 192.168.64.6 (2172416/28160), Serial0

via 192.168.1.1 (2174976/2172416), FastEthernet0

P 192.168.64.0/30, 1 successors, FD is 2172416, serno 91

via 192.168.1.1 (2172416/2169856), FastEthernet0

via 192.168.64.6 (2681856/2169856), Serial0

P 192.168.64.4/30, 1 successors, FD is 2169856, serno 72

via Connected, Serial0

P 192.168.1.0/24, 1 successors, FD is 28160, serno 1

via Connected, FastEthernet0

Understanding the Topology Table

SanJose2#show ip eigrp top all-links

IP-EIGRP Topology Table for AS(100)/ID(192.168.64.5)

Codes: P - Passive, A - Active, U - Update, Q - Query, R

- Reply,r - Reply status

P 192.168.72.0/24, 1 successors, FD is 2172416, serno 22

via 192.168.64.6 (2172416/28160), Serial0

via 192.168.1.1 (2174976/2172416), FastEthernet0

successor

feasible successor

Feasible distance

Feasible distance if this router was the successor. Includes the 2,560

delay cost of additional Fast Ethernet link.

Understanding the Topology Table

Feasible Distance/Reported Distance

SanJose2#show ip eigrp top all-links

IP-EIGRP Topology Table for AS(100)/ID(192.168.64.5)

Codes: P - Passive, A - Active, U - Update, Q - Query, R

- Reply,r - Reply status

P 192.168.72.0/24, 1 successors, FD is 2172416, serno 22

via 192.168.64.6 (2172416/28160), Serial0

via 192.168.1.1 (2174976/2172416), FastEthernet0

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!

Feasible distance

Reported Distance

successor

feasible successor

Question: What if there is only one entry in the Topology Table?

Answer: There is only a successor and no feasible successors.

• There are either no other neighbors with a route to this network or the reported distance of that neighbor is greater than the current feasible distance. (You will see this in the lab.)

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.

Questions

Example of a Loop, What if…

Cost=9

Cost=40Cost=40

RTZ has a Reported Distance to

RTA of 220. Since its Reported Distance is greater than RTA’s own Feasibile Distance of 31, RTA can’t trust that the route RTZ takes is somehow back

through itself.

RTZ FD = 220

RTZ to RTA is 189

RTA to

172.30.1.0 is 31

172.30.1.0

The five EIGRP packet types are:

EIGRP Packet Types

EIGRP Hello Packet

• Used to discover, verify, and rediscover neighbor routers. • EIGRP routers send hellos at a fixed (and configurable) interval, called

the hello interval.

• The default hello interval depends on the bandwidth of the interface. • Hello interval 5 seconds, hold time 15 seconds for T1 and faster • Hello interval 60 seconds, hold time 180 seconds for slower than T1 • On IP networks, EIGRP hello packets are multicast, 224.0.0.10 • If a neighbor is not heard from for the duration of the hold time (three

times hello interval), EIGRP considers that neighbor down, and DUAL must step in to reevaluate the routing table.

–By default, the hold time is three times the hello interval, but an administrator can configure both timers as desired.

• Unlike OSPF routers, EIGRP routers do not need to have the same hello intervals and hold down intervals.

Acknowledgement Packet

• Acknowledgement packets, which are “data-less” hello packets, are used to ensure reliable communication.

• Unlike multicast hellos, acknowledgement packets are unicast. • Acknowledgements can be made by piggybacking on other kinds of

EIGRP packets, such as reply packets.

Update Packet

• Update packets are used when a router discovers a new neighbor. –An EIGRP sends unicast update packets to that new neighbor so that it can add to its topology table.

–More than one update packet may be needed to convey all of the topology information to the newly discovered neighbor.

• EIGRP updates are only sent when: -A network is added or removed from the topology database

-The successor for a given network changes

-The locally used metric is updated.

• The EIGRP router sends a multicast update packet to all neighbors alerting them to the change.

• EIGRP routers exchange routing information the same way as other distance vector routing protocols, but do not send periodic updates.

Query and Reply Packets

• EIGRP routers use query packets whenever it needs specific information from one, or all, of its neighbors.

– A reply packet is used to respond to a query.

• If an EIGRP router loses its successor and cannot find a feasible successor for a route, DUAL places the route in the active state.

– The router multicasts a query to all neighbors, searching for a successor to the destination network.

– Neighbors must send replies that either provide information on successors, or indicate that no successor information is available.

• Queries can be multicast or unicast, while replies are always unicast.

• A router views its feasible successors as neighbors that are downstream, or closer, to the destination than it is.

• If something goes wrong with the successor, DUAL can quickly identify a feasible successor from the topology table, and install a new route to the

destination.

• If no feasible successors to the destination exist, DUAL places the route in the active state.

• 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.

• Recomputation happens if a route becomes unavailable and DUAL can’t find any feasible successors.

• Another route may exist, it is just that their Reported Distance was greater than your Feasible Distance.

Query and Reply Packets

XX

QueriesQueries

RepliesReplies

RtrF

RtrC

RtrE

RtrD

RtrB

RtrA

RtrG

• If there were no Feasible Successors, the router must ask neighbors for help in hope of finding a new, loop-free path to the destination.

• Neighbor routers are compelled to reply to this query. – If a neighbor has a route, it will reply with information about the successor(s).

– If not, the neighbor notifies the sender that it doesn’t have a route to the destination either.

Looking for new route

Query and Reply Packets

If a feasible successor does not exist:

• 1. The router flags the route as active. • 2. The router looks for an alternate path by sending out a query packet to all neighbors to

learn if they have a path to the given destination.

– The query packets are multicast out every interface except the one which the dead link

was learned, adhering to the split horizon rule.

• 3. If a neighbor does have a path that does not involve the querying router, or no path at all to the destination, it unicasts a reply with this information.

– If a neighbor that receives the query is using the querying router as its feasible

successor, then it multicasts its own query packet to its neighbor, which creates a

“ripple effect” through the network until a new path is found or a major network

boundary is met.

• 4. When the query router receives replies, it reacts based on the answer in the reply: – If the reply included a successor or feasible successor, the information is put into its

topology table, and the querying router waits until all replies are received. It then

recalculates the topology table, and adds the successr(s) to the routing table. The route

returns to a passive state in the topolgy table and routing can continue.

– If none of the replies includes a successor or feasible successor, the querying router

removes the active route from its topology table and routing tables.

• If a neighbor router to which a query is sent does not reply within the active time of 180 seconds, EIGRP tears down the neighbor relationship with the offending router and puts routes learned from that router into an active state.

Return Route or Forward Query

Query and Reply Packets

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.

Routes via RTY and RTX Fail!

172.30.1.0X

? RTZ was previously NOT a Feasible Successor, FC: RD220

not< FD31 or FD40, but now there is no

Sucessor

X

QueriesQueries

RepliesReplies

In this scenario…

Cost=100

Cost=99Cost=89

RTZ has a Reported Distance to

RTA of 220. Since its Reported Distance is greater than RTA’s own Feasibile Distance of 31, RTA can’t trust that the route RTZ takes is somehow back

through itself.

QueriesQueries

RepliesReplies

?

X

X All Replies are saying they do not have a route

Example from the curriculum…

1 2

3 4

Example from the curriculum…

5 6

7

No feasible successor in the topology table. EIGRP domain still finds another route.

SanJose2#debug eigrp fsm

EIGRP FSM Events/Actions debugging is on

SanJose2(config)#inter s 0

SanJose2(config-if)#shut

03:11:44: DUAL: Destination 192.168.72.0/24

03:11:44: DUAL: Find FS for dest 192.168.72.0/24. FD is 2172416, RD is

2172416

03:11:44: DUAL: 192.168.64.6 metric 4294967295/4294967295 not

found Dmin is 4294967295

03:11:44: DUAL: Dest 192.168.72.0/24 entering active state.

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

Example of debug eigrp fsm

XX

RepliesReplies

Router A

Router B

Router C

Router

D

QueriesQueries

XX

XX

XX

XX

� 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.

Stuck in Active (SIA)

• Typically, SIAs results when a router cannot answer a query because:

– the router is too busy to answer the query (generally high cpu utilization)

– the router cannot allocate the memory to process the

query or build the reply packet

– the circuit between the two routers is not good (packet

loss)

– unidirectional links (a link on which traffic can only flow

in one direction due to a failure)

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.

Troubleshooting (SIA) - FYI

Configuring EIGRP

Configuring EIGRP for IP networks

Router(config)#router eigrp autonomous-system-number

• This value must match all routers within the internetwork.

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.

Summarizing EIGRP Routes: no auto-summary

• EIGRP automatically summarizes routes at the classful boundary, the boundary where the network address ends

as defined by class-based addressing.

Summarizing EIGRP Routes: no auto-summary

• In the presence of discontiguous subnetworks, automatic summarization must be disabled for routing to work properly.

• To turn off auto-summarization, use the following command: Router(config-router)#no auto-summary

Summarizing EIGRP Routes: Interface Summarization

Router(config-if)#ip summary-address eigrp autonomous-system-number

ip-address mask administrative-distance

RTC(config)#router eigrp 2446

RTC(config-router)#no auto-summary

RTC(config-router)#exit

RTC(config)#interface serial0/0

RTC(config-if)#ip summary-address eigrp 2446 2.1.0.0 255.255.0.0

Summarizing EIGRP Routes: Interface Summarization

RTC(config)#interface serial0/0

RTC(config-if)#ip summary-address eigrp 2446 2.1.0.0 255.255.0.0

RTC’s Routing Table:

D 2.1.0.0/16 is a summary, 00:00:22, Null0

• 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

EIGRP show commands

EIGRP debug commands

Few last items not in the curriculum…

Optional Interface Command:

RTA(config-router)# variance number

IGRP and EIGRP also support unequal cost path load balancing, which is known as variance.

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, where n is the number specified by the variance command.

Note: If a path isn't a feasible successor, then it isn't used in load balancing.

EIGRP variance command

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

EIGRP variance command

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.

router eigrp 1

network x.x.x.x

variance 2

EIGRP variance command

Two unequal-cost paths:

• E-B-A with a metric of 30 <<<-- Also below 2*20

• E-C-A with a metric of 20 <<<-- Minimum Metric

• E-D-A with a metric of 45

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.

EIGRP variance command

router eigrp 1

network x.x.x.x

variance 2

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.

traffic-share {balanced | min}

no traffic share {balanced | min}

balanced

• Distributes traffic proportionately to the ratios of the metrics. min

• Uses routes that have minimum costs

• For more information: http://www.cisco.com/en/US/tech/tk365/tk207/technologies_tech_note0 9186a008009437d.shtml

Redistribution b/t EIGRP & IGRP

Same AS numbers

Router Two router eigrp 2000 network 172.16.1.0 ! router igrp 2000 network 10.0.0.0

(automatic redistribution)

Different AS numbers

Router Two router eigrp 2000

redistribute igrp 1000

network 172.16.1.0

!

router igrp 1000

redistribute eigrp 2000

network 10.0.0.0

So what is the difference? We’ll see later when discussing Redistribution.

There are three ways to inject a default route into EIGRP:

• Redistribute a static route

• IP default-network

• Summarize to 0.0.0.0/0

EIGRP and Default Routes (Review)

Redistribute a static route

• Use the first method when you want to draw all traffic to unknown destinations to a default route at the core of the network.

• This method is effective for advertising connections to the Internet, but will redistribute all static routes into EIGRP.

• For example:

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>

EIGRP and Default Routes (Review)

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

EIGRP and Default Routes (Review)

Extra: Summarize to 0.0.0.0/0

• Summarizing to a default route is effective only when you want to provide remote sites with a default route.

• Since summaries are configured per interface, you don't need to worry about using distribute-lists or other mechanisms to prevent the default route from being propagated toward the core

of your network.

router eigrp 100

network 10.0.0.0

!

interface serial 0

ip address 10.1.1.1

ip summary-address eigrp 100 0.0.0.0 0.0.0.0

EIGRP and Default Routes (Review)

Easy to implementDifficult to implement

Scalable, but no hierarchical designScalable; administratively defined

“areas” provide manageable hierarchy

Proprietary; Cisco routers onlyOpen standard; multivendor support

Automatic route-summarization and user-

defined route summaries

Administrator can define route

summarization

Supports CIDR and VLSM, rapid

convergence, partial updates, neighbor

discovery

Supports CIDR and VLSM, rapid

convergence, partial updates, neighbor

discovery

EIGRPOSPF

Equal-cost load balancing Unequal-cost load balancing

OSPF versus EIGRP

EIGRP and IGRP Metric Review

Metrics used by EIGRP in making routing decisions are (lower the metric the better):

1- bandwidth, 2- delay, 3- load, and 4- reliability

By default, EIGRP uses only:

1- Bandwidth is a the carrying capacity

2- Delay is the end-to-end travel time.

Metric Calculation

Analogies: Think of

bandwidth as the width of the pipe

delay as the length of the pipe.

If bandwidth and delay are the default, when are load and reliability used?

Only when configured by the network administrator to do so!

EIGRP also tracks (but does not use in its metric calculation):

• MTU (Maximum Transmission Unit) • Hop Count

Use show interface command to view the metrics used on a specific interface that is routing EIGRP.

• These are the raw values.

Router> show interfaces s1/0

Serial1/0 is up, line protocol is up

Hardware is QUICC Serial

Description: Out to VERIO

Internet address is 207.21.113.186/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

rely 255/255, load 246/255

Encapsulation PPP, loopback not set

Keepalive set (10 sec)

<output omitted>

bandwidth delay

reliability load

Metric Calculation

Bandwidth

• Expressed in kilobits (show interface) • This is a static number and used for metric calculations only. • Does not necessarily reflect the actual bandwidth of the link. • It is an information parameter only. • You cannot adjust the actual bandwidth on an interface with this command. • Use the show interface command to display the raw value

The default values:

• Default bandwidth of a Cisco interface depends on the type of interface.

• Default bandwidth of a Cisco serial interface is 1544 kilobits or 1,544,000 bps (T1), whether that interface is attached to a T1 line (1.544 Mbps) or a 56K line.

• IGRP/EIGRP metric uses the slowest bandwidth of all of the outbound interfaces to the destination network.

Metric Calculation

Changing the bandwidth informational parameter:

The bandwidth can be changed using:

Router(config-if)# bandwidth kilobits

To restore the default value:

Router(config-if)# no bandwidth

Metric Calculation

Delay

• Like bandwidth, delay it is a static number. • Expressed in microseconds, millionths of a second • (Uses the Greek letter mu with an S, µS, NOT “ms” which is millisecond or

thousandths of a second)

• Use the show interface command to display the raw value • It is an information parameter only.

The default values:

• The default delay value of a Cisco interface depends upon the type of interface.

• Default delay of a Cisco serial interface is 20,000 µseconds, that of a T1 line.

• IGRP/EIGRP metric uses the sum of all of the delays of all of the outbound interfaces to the destination network.

Metric Calculation

Changing the delay informational parameter:

The delay can be changed using:

Router(config-if)# delay tens-of- µS

(microseconds)

Example of changing the delay on a serial interface to 30,000 microseconds:

Router(config-if)# delay 3000

To restore the 20,000 microsecond default value:

Router(config-if)# no delay

Metric Calculation

IGRP

• bandwidth = (10,000,000/bandwidth) • delay = delay/10

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

Metric Calculation

Media

Bandwidth

K= kilobits

BWEIGRP

10,000,000/Bandwidth

*256

Delay

DLYEIGRP Delay/10

*256

100M ATM 100,000K 25,600 100 µµµµS 2,560

Fast Ethernet 100,000K 25,600 100 µµµµS 2,560

FDDI 100,000K 25,600 100 µµµµS 2,560

HSSI 45,045K 56,832 20,000 µµµµS 512,000

16M Token Ring 16,000K 160,000 630 µµµµS 16,128

Ethernet 10,000K 256,000 1,000 µµµµS 25,600

T1 (Serial

Default) 1,544K 1,657,856 20,000 µµµµS 512,000

512K 512K 4,999,936 20,000 µµµµS 512,000

DS0 64K 40,000,000 20,000 µµµµS 512,000

56K 56K 45,714,176 20,000 µµµµS 512,000

BWEIGRP and DLYEIGRP display values as sent in EIGRP updates and used in calculating the EIGRP metric.

EIGRP Metrics Values displayed in show interface

commands and sent in routing updates.

Calculated values (cumulative) displayed in routing table (show ip route).

Media

Bandwidth

K= kilobits

BWIGRP

10,000,000/Bandwidth

Delay

DLYIGRP Delay/10

100M ATM 100,000K 100 100 µµµµS 10

Fast Ethernet 100,000K 100 100 µµµµS 10

FDDI 100,000 100 100 µµµµS 10

HSSI 45,045K 222 20,000 µµµµS 2,000

16M Token Ring 16,000K 625 630 µµµµS 63

Ethernet 10,000K 1,000 1,000 µµµµS 100

T1 (Serial Default) 1,544K 6,476 20,000 µµµµS 2,000

512K 512K 19,531 20,000 µµµµS 2,000

DS0 64K 156,250 20,000 µµµµS 2,000

56K 56K 178,571 20,000 µµµµS 2,000

BWIGRP and DLYIGRP display values as sent in IGRP updates and used in calculating the IGRP metric.

IGRP Metrics Values displayed in show interface

commands and sent in routing updates.

Calculated values (cumulative) displayed in routing table (show ip route). EIGRP values are 256 times greater.

Router> show interfaces s1/0

Serial1/0 is up, line protocol is up

Hardware is QUICC Serial

Description: Out to VERIO

Internet address is 207.21.113.186/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

rely 255/255, load 246/255

Encapsulation PPP, loopback not set

Keepalive set (10 sec)

<output omitted>

bandwidth delay

reliability load

Metric Calculation

Media

Bandwidth

K= kilobits

BWIGRP

10,000,000/Bandwidth

Delay

DLYIGRP Delay/10

100M ATM 100,000K 100 100 µµµµS 10

Fast Ethernet 100,000K 100 100 µµµµS 10

FDDI 100,000 100 100 µµµµS 10

HSSI 45,045K 222 20,000 µµµµS 2,000

16M Token Ring 16,000K 625 630 µµµµS 63

Ethernet 10,000K 1,000 1,000 µµµµS 100

T1 (Serial Default) 1,544K 6,476 20,000 µµµµS 2,000

512K 512K 19,531 20,000 µµµµS 2,000

DS0 64K 156,250 20,000 µµµµS 2,000

56K 56K 178,571 20,000 µµµµS 2,000

BWIGRP and DLYIGRP display values as sent in IGRP updates and used in calculating the IGRP metric.

Media

Bandwidth

K= kilobits

BWEIGRP

10,000,000/Bandwidth

*256

Delay

DLYEIGRP Delay/10

*256

100M ATM 100,000K 25,600 100 µµµµS 2,560

Fast Ethernet 100,000K 25,600 100 µµµµS 2,560

FDDI 100,000K 25,600 100 µµµµS 2,560

HSSI 45,045K 56,832 20,000 µµµµS 512,000

16M Token Ring 16,000K 160,000 630 µµµµS 16,128

Ethernet 10,000K 256,000 1,000 µµµµS 25,600

T1 (Serial

Default)

1,544K 1,657,856 20,000 µµµµS 512,000

512K 512K 4,999,936 20,000 µµµµS 512,000

DS0 64K 40,000,000 20,000 µµµµS 512,000

56K 56K 45,714,176 20,000 µµµµS 512,000

BWEIGRP and DLYEIGRP display values as sent in EIGRP updates and used in calculating the EIGRP metric.

Viva la

difference!

IGRP

EIGRP

Calculated values (cumulative) displayed in routing table (show ip route).

EIGRP values are 256 times greater.

The metrics used by EIGRP in making routing decisions are (lower the metric the better):

• bandwidth • delay • load • reliability

By default, EIGRP uses only:

• Bandwidth • Delay

Reliability and Load

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

Expressed as an 8 bit number

• 255 is a 100% reliable link • 1 is a minimally reliable link

Higher the better!

Reliability and Load

shows reliability as a fraction of 255, for example:

rely 190/255 (or 74% reliability)

rely 234/255 (or 92% reliability)

rely 255/255 (or 100% reliability)

Router> show interfaces s1/0

Serial1/0 is up, line protocol is up

Hardware is QUICC Serial

Description: Out to VERIO

Internet address is 207.21.113.186/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

rely 255/255, load 246/255

Encapsulation PPP, loopback not set

Keepalive set (10 sec)

<output omitted>

bandwidth delay

reliability load

Reliability and Load

Load

• Load is measure dynamically • Uses channel occupancy for measurement • Reflects the total outgoing load 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

Expressed as an 8 bit number

• 255 is a 100% loaded link • 1 is a minimally loaded link

Lower the better!

Note: Even though load and reliability are dynamically changing values, EIGRP will not recalculate the route metric when these parameters change.

Reliability and 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)

Router> show interfaces s1/0

Serial1/0 is up, line protocol is up

Hardware is QUICC Serial

Description: Out to VERIO

Internet address is 207.21.113.186/30

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,

rely 255/255, load 246/255

Encapsulation PPP, loopback not set

Keepalive set (10 sec)

<output omitted>

bandwidth delay

reliability load

Reliability and Load

IGRP/EIGRP metric =

[k1* BWIGRP(minimum) +

(k2* BWIGRP(minimum))/(256-LOAD) +

k3* DLYIGRP(sum) ] *

[k5/RELIABILITY + k4)]

• k2 metric effects LOAD • k4 and k5 effects RELIABILITY • Multiply Reliability only if > 0

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

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”

The command to adjust the k values is:

Router(config-router)# metric weights tos k1 k2 k3 k4 k5

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.

Reliability and Load

EIGRP-BouSaba.pdf