RIP VERSION 1 (RIPV1)
Objectives
RIP Background
RIP Characteristics and operation
Basic RIP configurations & Commands
Passive interfaces
RIP Automatic Summarization; advantages & disadvantages
Default Route & RIP1
Propagating the Default Route
RIP Version 1
RIPv1: Distance Vector,
Classful Routing Protocol
Background and Perspective
RIP evolved from the Xerox Network System (NS) in the late 1970’s.
Various vendors included their own, slightly different, version of the protocol in
their networking software.
In 1988, it was standardized under RFC 1058.
Why learn RIP?
Still in use today.
Help understand fundamental concepts and comparisons of protocols such as classful
(RIPv1) and classless (RIPv2).
RIP is not a protocol “on the way out.”
An IPv6 form of RIP called RIPng (next generation) is now available..
RIPv1 Characteristics and Message Format
NOTE:
The first version of RIP is often called RIPv1 to distinguish it from RIP version 2
(RIPv2).
Both versions share many of the same features.
When discussing features common to both versions, we will refer to RIP.
When discussing features unique to each version, we will use RIPv1 and RIPv2.
RIPv1 Characteristics and Message Format
RIP Characteristics:
Distance vector routing protocol.
Uses hop count as its only metric for path selection.
Advertised routes with hop counts greater than 15 are considered unreachable.
Routing Table Updates:
RIPv1: Broadcast every 30 seconds.
RIPv2: Multicast every 30 seconds.
RIPv1 Characteristics and Message Format
Encapsulated RIPv1 Message:
RIPv1 Characteristics and Message Format
Contains up to 25 routes for each IP
Address and Metric.
Extra space originally added to
support larger address space.
RIP Operation
On Start-up:
Each RIP-configured interface broadcasts a request message, asking any RIP
neighbours to send their complete routing table.
Each RIP neighbour responds with the information.
The requesting router evaluates each route:
If it’s a new route, it gets added to the routing table.
If it’s already in the routing table and has a better hop count (lower), the routing table is
updated.
If there are no changes, it is ignored.
The requesting router then sends a triggered update out all interfaces that contains its
routing table.
RIP Operation
1. R3 Start-up Request
2. R2, R1 Respond
3. R3, Triggered Update
IP Address Classes and Classful Routing
No Subnet
Mask
RIPv1 is a classful routing protocol.
RIPv1 does not send subnet mask information in the update.
The router determines the subnet mask.
Uses the subnet mask configured on a local interface.
OR applies the default, classful subnet mask.
Because of this limitation, RIPv1 networks cannot be discontiguous, nor can they
implement VLSM.
Administrative Distance (AD)
Administrative Distance (AD) is the trustworthiness (or preference) of the route
source.
RIP has a default administrative distance of 120.
When compared to other interior gateway protocols, RIP is the least-preferred routing
protocol.
RIP Version 1
Basic RIPv1 Configuration
RIPv1 Scenario A
Notice that this topology uses five Class C networks.
Remember, RIPv1 is a classful routing protocol and all networks MUST have the
same subnet mask.
We will see that the class of the network is used by RIPv1 to determine the
subnet mask.
Enabling RIP: router rip command
Global Configuration Mode
Issue command
Prompt changes
The router rip command:
Does not directly start the RIP process.
Provides access to configure routing protocol settings.
No routing updates are sent until you configure the networks that are
participating in RIP.
Enabling RIP: router rip command
Global Configuration Mode
Issue command
Prompt changes
• To remove the RIP routing process from a device:
no router rip
Stops the RIP process.
Erases all existing RIP configuration commands.
Specifying Networks
The network command:
Enter the classful network address for each directly connected network.
Functions:
Enables RIP on all interfaces that belong to a specific network. Associated interfaces will
now both send and receive RIP updates.
Advertises the specified network in RIP routing updates sent to other routers every 30
seconds.
Specifying Networks
ONLY directly connected classful
addresses!
RIP Version 1
Verification and Troubleshooting
show ip route command
C in the output indicates directly connected networks.
R in the output indicates RIP routes.
Because this command displays the entire routing table, it is normally the first
command used to check for convergence.
Routes might not immediately appear when you execute the command because
networks take some time to converge.
show ip route command
show ip route command
Identifies RIP as the source of the route.
Remote network address and subnet mask.
AD of 120 / Metric of 2 hops.
Address of the next-hop router.
Elapsed time since last update.
The local, exit interface
show ip protocols command
debug ip rip command
Passive Interfaces
No Router
Some routers can have interfaces that do not connect to another router.
There is no reason to send routing updates out that interface.
You can use the passive-interface command with RIP to configure an
interface to NOT send those updates.
Passive Interfaces
No Router
NO updates sent out interface fa0/0.
RIP Version 1
Automatic Summarization
Modified Topology
Scenario B
Modified Topology: Scenario B
172.30.0.0/16 192.168.4.0/24
192.168.5.0/24
Three classful networks: • 172.30.0.0/16 subnetted to:• 192.168.4.0/24
172.30.1.0/24 subnetted to:
172.30.0.0/16
172.30.2.0/24 192.168.4.8/30
192.168.4.0/24
172.30.3.0/24
192.168.5.0/24
Modified Topology: Scenario B
172.30.0.0/16 192.168.4.0/24
192.168.5.0/24
Fewer routes in a routing table means that the routing table process can more
quickly locate the route needed to forward the packet.
Summarizing several routes into a single route is known as route
summarization or route aggregation.
Modified Topology: Scenario B
Configuration Changes – R1
IOS automatically
corrects subnet
entries to a classful
network address.
The same thing will happen
when R2 and R3 are
changed.
Boundary Routers and Auto-Summarization
RIP is a classful routing protocol that automatically summarizes classful
networks across major network boundaries.
Boundary Routers and Auto-Summarization
R2 has interfaces in more than one major classful network.
This makes R2 a boundary router in RIP.
Boundary Routers and Auto-Summarization
Boundary routers summarize RIP subnets from one major network to the other.
Updates for the 172.30.1.0, 172.30.2.0, and 172.30.3.0 networks will
automatically be summarized into 172.30.0.0 when sent out R2’s Serial 0/0/1
interface.
Processing RIP Updates
Classful routing protocols such as RIPv1 do not include the subnet mask in the
routing update.
However, the routing table includes RIPv1 routes with both the network
address and the subnet mask.
So…..How does a router running RIPv1 determine what subnet mask it should
apply to a route when adding it to the routing table?
Rules for Processing RIP Updates
Routing Update and Interface Routing Update Subnet Mask
Same classful Major Network Use the Interface Subnet Mask
Different classful Major Network Use the Classful Subnet Mask
Rules for Processing RIP Updates
172.30.2.2/24
Routing Update and Interface Routing Update Subnet Mask
Same classful Major Network Use the Interface Subnet Mask
Different classful Major Network Use the Classful Subnet Mask
Sending RIP Updates
Using debug to view Automatic Summarization
Advantages of Auto-Summarization
Smaller routing
updates are sent
and received,
which uses less
bandwidth for
routing updates
between R2
and R3.
R3 has a single route for the 172.30.0.0/16 network, regardless of how many
subnets there are or how it is subnetted.
Using a single route results in a faster lookup process in the routing table for R3.
Disadvantages of Auto-Summarization
209.165.200.0/24 209.165.200.0/24
172.30.0.0/16 172.30.0.0/16
Discontiguous network, two or more subnets separated by at least one other
major network.
172.30.0.0/16 is a discontiguous network.
Discontiguous Networks Do Not Converge
RIPv1 configuration is correct, but it is unable to determine all the networks in
this discontiguous topology.
Discontiguous Networks Do Not Converge
172.30.0.0/16 172.30.0.0/16
Routers R1 and R3 will both advertise the 172.30.0.0/16 major network address
(a summary route) to R2.
Discontiguous Networks Do Not Converge
R1 does not have routes to the LANs attached to R3.
R3 does not have routes to the LANs attached to R1.
Discontiguous Networks Do Not Converge
Two equal cost paths to 172.30.0.0/16
172.30.0.0/16 172.30.0.0/16
Discontiguous Networks Do Not Converge
R2 will Load Balance
R1 and R3 will each receive half the traffic whether or not it is
destined for one of their LANs.
Discontiguous Networks Do Not Converge
Classful routing protocols do not support discontiguous networks
because the subnet mask is not included in the routing table update.
RIP Version 1
Default Route and RIPv1
Modified Topology
Scenario C
Default Routes
ISP
In today’s networks, customers do not necessarily have to exchange routing
updates with their ISP.
Customer routers have a default route that sends all traffic to the ISP router.
The ISP configures a static route pointing to the customer router for addresses
inside the customer’s network.
Default Routes
Default Route:
A special static route that is used to route packets with a destination IP address that
does not match any of the other routes in the routing table.
It tells the router…..
“If you don’t know where to forward
the frame, send it here.”
Uses a quad-zero definition for the route.
It matches all destination IP addresses
ip route 0.0.0.0 0.0.0.0
[next-hop-address/exit-interface]
RIPv1 Configuration R2 and R3
ISP
RIPv1 Configuration R2 and R3
Routing Tables
Propagating the Default Route
Routing Table
What about R1?
Knows the 172.30.0.0/24 subnets but nothing else.
How does it forward traffic destined for the internet?
It also needs a default route.
Could configure a static default route on every router but this is inefficient and does
not react to topology changes.
Propagating the Default Route
Instead, in R2, you can use the
default-information originate command.
This command specifies that R2 (already has a default route) is to originate
default information.
R2 is to include the static default route in RIP updates.
Propagating the Default Route
Summary
RIP Background
RIP Characteristics and operation
Basic RIP configurations & Commands
Passive interfaces
RIP Automatic Summarization; advantages & disadvantages
Default Route & RIP1
Propagating the Default Route
