Distance Vector Routing
Protocols
Routing Protocols and Concepts – Chapter 4
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
ITE PC v4.0
Chapter 1
1
Objectives
Identif
y
the characteristics of distance vector routin
g
p
rotocols.
ygp
Describe the network discovery process of distance vector
routing protocols using Routing Information Protocol (RIP).
Describe the processes to maintain accurate routing tables used
by distance vector routing protocols.
Id tif th diti l di t ti l d l i th
Id
en
tif
y
th
e con
diti
ons
l
protocols
are
in
use
today
ITE PC v4.0
Chapter 1
2
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Distance Vector Routing Protocols
Dynamic routing protocols help the network administrator overcome the time-
consuming and exacting process of configuring and maintaining
static routes
consuming
and
exacting
process
of
configuring
roa
d
cas
t
or mu
lti
cas
t
every
30
secon
d
s,
b
y
d
e
f
au
lt
.
Interior Gateway Routing Protocol (IGRP)
–proprietary protocol developed by Cisco.
–
Bandwidth, delay, load and reliability are used to create a composite metric.
Bandwidth,
delay,
load
()
–Cisco proprietary distance vector routing protocol.
–It can perform unequal cost load balancing.
–It uses Diffusing Update Algorithm (DUAL) to calculate the shortest path.
–
There are no periodic updates as with RIP and IGRP Routing updates are sent only
ITE PC v4.0
Chapter 1
3
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
–
There
are
no
periodic
updates
as
with
RIP
and
IGRP
Distance
to
final
destination
The distance or how far it is to the destination network
Vector or direction
traffic should be directed
Vector
,
or
direction
,
traffic
should
be
directed
The direction or interface in which packets should be forwarded
For example, in the figure,
R1 knows that the distance
to reach network
Periodic u
p
dates
p
•Periodic Updates sent at regular intervals (30 seconds for
RIP). Even if the topology has not changed in several days,
Neighbors
The router is only aware of the network addresses of its
own interfaces and the remote network addresses it can
reach through its neighbors.
It has no broader knowledge of the network topology
Broadcast updates
Broadcast Updates are sent to 255.255.255.255.
Some distance vector routing protocols use multicast
addresses instead of broadcast addresses
addresses
instead
of
broadcast
addresses
.
Entire routing table is included with routing update
Entire Routing Table Updates are sent, with some
e
x
cept
to
be
discussed
later,
periodically
to
all
neighbors.
Neighbors receiving these updates must process the entire
update to find pertinent information and discard the rest.
Some distance vector routing protocols like EIGRP do not
ITE PC v4.0
Chapter 1
5
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Some
distance
vector
m
i
s use
d
t
o ca
l
cu
l
a
t
e
th
e
b
es
t
pa
th
s an
d
th
en sen
d
that information to the neighbors.
–
Different routin
Time to convergence
Time to convergence defines how quickly the routers in the network topology share
routing information and reach a state of consistent knowledge.
The faster the convergence, the more preferable the protocol.
Scalability
Scalability defines how large a network can become based on the routing protocol that is
deployed
deployed
.
The larger the network is, the more scalable the routing protocol needs to be.
Resource usage
Resource usa
g
e includes the re
q
uirements of a routin
g
p
rotocol such as memor
y
s
p
ace
,
gq gp yp,
CPU utilization, and link bandwidth utilization.
Higher resource requirements necessitate more powerful hardware to support the routing
protocol operation
Protocols
ITE PC v4.0
Chapter 1
8
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Network Discovery
Router initial start up
(Cold Starts)
Cold Starts
Router
initial
start
up
(Cold
Starts)
When a router cold starts or powers up, it knows nothing about the
network topology. It does not even know that there are devices on
the other end of its links. The only information that a router has is
from its own saved configuration file stored in NVRAM.
Initial network discovery
-
Initial
E
xc
h
ange
If
a
routing
protocol
is
configured
then
•Routers will exchange routing information
•Initially, these updates only include information
about their directly connected networks.
Routing updates received from other routers
–Router checks update for new information
•If there is new information:
–Metric is updated
–New information is stored in routing table
After this first round of update exchanges, each
tk btth td t kfthi
rou
t
er
k
0
.
0
and
that
R3
does
not
yet
know
about
10.1.0.0?
–Full knowledge and a converged network will not take
place until there is another exchange of routing
information
ITE PC v4.0
Chapter 1
10
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
information
.
t
their own directly connected networks and
about the connected networks of their
immediate neighbors
immediate
neighbors
.
–Continuing the journey toward convergence,
the routers exchange the next round of periodic
updates Each router again checks the updates
updates
.
Each
router
again
checks
the
updates
for new information.
Routing updates received from other routers
–Router checks update for new information
•If there is new information:
For example R2 would not send
–
For
example
,
R2
would
not
send
an update out Serial 0/0/0
containin
g
the network 10.1.0.0
g
because R2 learned about that
network through Serial 0/0/0.
ITE PC v4.0
Chapter 1
12
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Network Discovery
Network
Discovery
Exchange of Routing Information
Network Discovery and convergence
The amount of time it takes for a network to converge is
The
amount
of
time
it
takes
for
a
network
to
converge
is
directly proportional to the size of that network.
Convergence must be reached before a network is considered
completely operable
3
learn about the new routes
advertised by B2-R4.
1
Routing Table Maintenance
Periodic Updates
: RIPv1 & RIPv2
Periodic
Updates
:
RIPv1
&
RIPv2
–These are time intervals in which a router sends out its entire routing
table.
•RIPv1: updates are sent every 30 seconds as a broadcast
(255.255.255.255) whether or not there has been a topology
change
change
•RIPv2: updates are sent every 30 seconds as a multicast
(224.0.0.9) whether or not there has been a topology change
ITE PC v4.0
and
to
maintain
up
-
to-date routing information in the routing table.
Failure of a link
–
Failure
of
a
link
–Introduction of a new link
–
Failure of a route
r
–Change of link parameters
ITE PC v4.0
Chapter 1
16
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Rti TblMit
R
ou
route
is
marked
as
invalid by setting the metric to 16.
•The route is retained in the routing table until
the flush timer expires.
–
Holddown time
r
•This timer stabilizes routing information and
helps prevent routing loops during periods
when the topology is converging on new
information.
B d f lt th h ldd ti i t f 180
•
B
y
d
e
f
au
lt
,
th
than
the
invalid timer.
•When the flush timer expires, the route is
removed from the routing table.
ITE PC v4.0
Chapter 1
17
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Routing Table Maintenance
EIGRP
EIGRP
–Unlike other distance vector routing protocols,
EIGRP does not send periodic updates.
–
Instead
,
EIGRP sends bounded u
p
dates about a
,p
route when a path changes or the metric for that
route changes.
EIGRP routing updates are
–Partial updates
•Updates sent only when there is a change in
routers
that
need
the
information are updated
–Non periodic
•
Updates are not sent out on a regular basis.
ITE PC v4.0
Chapter 1
18
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Updates
are
not
sent
out
on
a
updates
that notify their neighbors of the change.
Conditions in which triggered updates are sent
Conditions
in
which
triggered
updates
are
sent
–Interface changes state
–Route becomes unreachable
–Route is placed in routing table
ITE PC v4.0
Chapter 1
19
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Routing Table Maintenance
Routing
Table
appropriate router immediately.
However, there are two problems with
triggered updates:
triggered
updates:
–Packets containing the update message can
be dropped or corrupted by some link in the
network
network
.
–The triggered updates do not happen
instantaneously. It is possible that a router that
has not
y
et received the tri
gg
ered u
p
date will
yggp
issue a regular update at just the wrong time,
causing the bad route to be reinserted in a
neighbor that had already received the
triggered update
ITE PC v4.0
Chapter 1
20
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
oint
,
serial interfaces.
p,
•interface serial 0
• ip rip triggered
/>ITE PC v4.0
Chapter 1
21
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Routing Table Maintenance
Routing
Table
Maintenance
Random Jitter
Synchronized updates
Synchronized
updates
A condition where multiple routers on multi access LAN
segments transmit routing updates at the same time.
Pbl
ith h i d d t
P
ro
bl
ems w
Solution to problems with
synchronized updates
- Used of random variable
called RIP_JITTER
•A good reference is : Routing TCP/IP (Jeff
Doyle) page 193-196.
•
Update timers : timer for periodic update
ITE PC v4.0
Chapter 1
22
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Update
timers
:
timer
for
periodic
update
(default 30s) - RIP_JITTER (random to
prevent colision - 15% of the update timers)
Routing Table Maintenance
Routing
update
timer
at each reset to help avoid routing table synchronization. The
RIP updates from Cisco routers vary from 25.5 to 30 seconds, as
h i th d lt ti f th d t
s
h
own
i
n
th
e
d
e
lt
a
ti
mes o
f
th
ese up
d
a
t
es.
Routing TCP/IP,
Volume I (CCIE
A
condition
in
which
a
packet is continuously
transmitted within a
ift
ser
i
es o
f
rou
t
ers
without ever reaching
its destination.
its
destination.
ITE PC v4.0
Chapter 1
24
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public
Network convergence is degraded
Network
convergence
is
degraded
-Routing updates may be lost or not processed in a timely
manner
ITE PC v4.0
Chapter 1
25
© 2007 Cisco Systems, Inc. All rights reserved. Cisco Public