Ch.16/Mod.7 - Distance Vector Routing Protocols Part 2 of 2: Distance Vector Routing and Igrp IGRP Features
Ch.16/Mod.7 - Distance Vector Routing Protocols Part 2 of 2: Distance Vector Routing and Igrp IGRP Features
1
IGRP Metrics Administrative Distances
• The metrics that IGRP uses are: Cisco Default Administrative Distances
– Bandwidth – The lowest bandwidth value in the path
Route Source Administrative Distance
– Delay – The cumulative interface delay along the path Connected interface 0
– Reliability – The reliability on the link towards the destination as Static Route 1
determined by the exchange of keepalives EIGRP summary route 5
– Load – The load on a link towards the destination based on bits per External BGP 20
second EIGRP 90
– NO… MTU – The Maximum Transmission Unit value of the path. IGRP 100
MTU has never been used by IGRP or EIGRP as a routing OSPF 110
metric. IS-IS 115
• IGRP has an administrative distance of 100, more “trustworthy” than RIP 120
RIP at 120. EGP 140
• This means a Cisco router will prefer an IGRP learned route over a RIP External EIGRP 170
Internal BGP 200
learned route to the same network.
Unknown 255
• Interior
“Interior routes are routes between subnets of a network attached to a
router interface(Router Subinterfaces and VLANs:Inter-VLAN Routing).
If the network attached to a router is not subnetted, IGRP does not
advertise interior routes.”
• Clarification
• IGRP also advertises three types of routes:
– interior, system, and exterior.
• Interior routes are routes between subnets in the network attached to a
router interface.
• If the network attached to a router is not subnetted, IGRP does not
advertise interior routes.
2
IGRP Routes IGRP Routes
• System • Exterior
“System routes are routes to networks within an autonomous system. “Exterior routes are routes to networks outside the autonomous system
The Cisco IOS software derives system routes from directly connected that are considered when identifying a gateway of last resort. The Cisco
network interfaces and system route information provided by other IOS software chooses a gateway of last resort from the list of exterior
IGRP-speaking routers or access servers. System routes do not include routes that IGRP provides. The software uses the gateway (router) of
subnet information.” last resort if a better route is not found and the destination is not a
connected network. If the autonomous system has more than one
connection to an external network, different routers can choose different
exterior routers as the gateway of last resort.”
IGRP
IGRP Timers
Timers
Update timer
3
IGRP IGRP
Timers Timers
• The invalid timer specifies how long a router should wait in the absence • The holddown timer specifies the amount of time for which
of routing-update messages about a specific route before declaring that information about poorer routes are ignored.
route invalid (unreachable), but still in the routing table. • Zinin: “Holddown specifies the number of seconds that a route must
• The IGRP default for this variable is three times the update period or spend in holddown state after expiration of the Invalid Timer.”
270 seconds. • The IGRP default for this variable is three times the update timer
• Then placed in the holddown state. period plus 10 seconds = 280 seconds.
• “If I haven’t heard from you in 270 seconds, I am considering this route • The original route is still in the routing table but marked as
as unreachable, I will start the holddown timer, but I will keep it in the unreachable, until the flush timer expires.
routing table until the flush timer expires.”
IGRP IGRP
Timers Timers
Flush timer
• Finally, the flush timer indicates how much time should pass before a route is
flushed from the routing table.
• The IGRP default is seven times the routing update timer or 630 seconds.
• Zinin: “Flush specifies the number of seconds that a route must remain in the • All timers begin at the same time.
routing table in the garbage collection state after it exits the holddown state.”
– Update timer = 90 seconds
• Each time an update is received the invalid and flush timers are reset.
– Invalid timer = 270 seconds
• If the invalid timer expires before another update is heard, the route is marked
– Holddown timer = 280 seconds
as unreachable, but remains in the routing table.
– Flush timer = 630 seconds
• If the flush timer then expires before another update is heard, the route will be
deleted from the routing table. • Today, IGRP is showing its age, it lacks support for variable length
subnet masks (VLSM).
• Enhanced IGRP (EIGRP) supports VLSM.
4
Configuring IGRP Configuring IGRP
Router(config)#router rip
Router(config-router)#network 172.16.0.0
Router(config-router)#network 192.168.1.0
Router(config-router)#exit
Router(config)#router igrp 10
Router(config-router)#network 172.16.0.0
Router(config-router)#network 192.168.1.0
Router(config-router)#exit
Router(config)#no router rip
• Enable IGRP
• Suggestion: Remove RIP configuration from routers even
though the administrative distance will prefer RIP
5
Verifying IGRP Verifying IGRP
6
Troubleshooting IGRP Troubleshooting IGRP
Process Domain
Process Domain
Router
Router Router
IGRP 30 IGRP 40 AS 90
Routing Domain
AS 10
Routing Domain
7
Summary
reliability load
Routing Table Metric
• Default: Slowest of bandwidth plus the sum of the delays of
all outgoing interfaces from “this router” to the destination
network.
8
Metric Calculation Metric Calculation
Bandwidth
Changing the bandwidth informational parameter:
• 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. The bandwidth can be changed using:
• It is an information parameter only. Router(config-if)# bandwidth kilobits
• You cannot adjust the actual bandwidth on an interface with this command.
• Use the show interface command to display the raw value To restore the default value:
Router(config-if)# no bandwidth
The default values:
• Default bandwidth of a Cisco interface depends on the type of interface.
• IGRP metric uses the slowest bandwidth of all of the outbound interfaces to
the destination network.
• IGRP metric uses the sum of all of the delays of all of the outbound interfaces
to the destination network.
9
Metric Calculation IGRP Metrics
Values displayed in show interface
commands and sent in routing updates.
IGRP
• bandwidth = (10,000,000/bandwidth) 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
• delay = delay/10 FDDI
HSSI
100,000
45,045K
100
222
100 S
20,000 S
10
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.
10
From Casablanca to 172.20.40.0/24
IGRP metric
Calculating the IGRP Metric
= highest BWIGRP + total of the DLYIGRP
Using the
= 19,531 + (100 + 2,000 + 2,000 + 100) Raw Values:
= 19,531 + 4,200 Bandwidth and Delay
= 23,731
11
Calculating Delay Slowest Bandwidth + Sum of Delays
So how is Delay, DLY IGRP, calculated? IGRP metric = Bandwidth + Delay
• Delay is the total sum of delays on the outgoing interfaces, in 10-
microsecond units
• The sum of the delays on each of the outgoing interfaces between IGRP metric = 19,531 + 4,200
Casablanca and Yalta, from 172.20.1.0/24 through 172.20.40.0/24 is:
= 23,731
• 1,000 (Casablanca) + 20,000 (Teheran) + 20,000 (Quebec) + 1,000
(Yalta) = 42,000
IF we were using RIP, the RIP metric would be 3 hops.
We need this in 10-microsecond units:
= (1,000/10)+(20,000/10) + (20,000/10) + (1,000/10)
= 100 + 2,000 + 2,000 + 100
or
= (1,000 + 20,000 + 20,000 +1,000) / 10
12