7.2.2.4 Comparing RIP and EIGRP Path Selection FORM
7.2.2.4 Comparing RIP and EIGRP Path Selection FORM
Objectives
Part 1: Predict the Path
Part 2: Trace the Route
Part 3: Reflection Questions
Scenario
PCA and PCB need to communicate. The path that the data takes between these end devices can travel
through R1, R2, and R3, or it can travel through R4 and R5. The process by which routers select the best
path depends on the routing protocol. We will examine the behavior of two distance vector routing protocols,
Enhanced Interior Gateway Routing Protocol (EIGRP) and Routing Information Protocol version 2 (RIPv2).
Hop Count
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 2
4 Mb/s
What is the minimum bandwidth on the path? __________________
Wait a minute and show the routing table again. Which protocol codes are listed in the table and what
C = Connected, R = RIP
protocols do they represent? ____________________________________
1.2 Kbps
What is the minimum bandwidth on the path? __________________
89
e. What is the first number between the brackets in each RIP entry? __________________
If a packet could be dropped if it travels more hops than its TTL value allows.
_______________________________________________________________________________________
More bandwidth.
3. Which do you prefer for your own Internet access, lower hops or more bandwidth? _____________________
4. Is one routing protocol suitable for all applications? Why?
I believe that there is some variance to what is required for anyones needs, as almost always each
_______________________________________________________________________________________
person has their own needs that one protocol may be unable to cater to. In a general sense, I think
_______________________________________________________________________________________
one protocol may suit the needs to an extent, but others may be needed for a user's "100%" usage.
_______________________________________________________________________________________
2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 2