Routing Information Protocol

V2 (RIPV2)
Chapter 7

ITE I Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 1
 Objectives

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 2
 Introduction
ƒ RIPV2:
ƒ Next-hop addresses included in the routing updates
ƒ Use of multicast addresses in sending updates
ƒ Authentication option available

ƒ Like RIPv1, RIPv2 is a distance vector routing protocol. Both

versions of RIP share the following features and limitations:
ƒ Use of holddown and other timers to help prevent routing loops.
ƒ Use of split horizon or split horizon with poison reverse to also help
prevent routing loops.
ƒ Use of triggered updates when there is a change in the topology
for faster convergence.
ƒ Maximum hop count limit of 15 hops, with the hop count of 16
signifying an unreachable network.
ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 3
Lab topology
Notice that R3 is using loopback interfaces (Lo0,
Lo1, and Lo2). A loopback interface is a software-
only interface that is used to emulate a physical
interface. Like other interfaces, it can be assigned
an IP address. Loopback interfaces are also used
by other routing protocols, such as OSPF, for
different purposes.

In a lab environment, loopback

interfaces are useful in creating
additional networks without having
to add more physical interfaces on
the router.
A loopback interface can be pinged
and the subnet can be advertised in
routing updates. Therefore,
loopback interfaces are ideal for
simulating multiple networks
attached to the same router.

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 4
 Static Routes and Null Interfaces
ƒ R2(config)#ip route 192.168.0.0 255.255.0.0 Null0
ƒ The address space represented by the static summary route
192.168.0.0/16 does not actually exist. In order to simulate this
static route, we use a null interface as the exit interface.
ƒ null interface is always up but does not forward or receive traffic.
Traffic sent to the null interface is discarded.
ƒ Using the null interface will allow R2 to advertise the static route in
RIP even though networks belonging to the summary
192.168.0.0/16 do not actually exist.

Test Connectivity using pings 7.1.2-2

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public
PT 7.1.2-3 5
 ƒ In RIPv1 message format, It does not include the subnet masks in
its routing updates. Therefore, RIPv1 cannot support discontiguous
networks, VLSM, or Classless Inter-Domain Routing (CIDR)
supernets.
ƒ RIPv1 on both the R1 and R3 routers will summarize their
172.30.0.0 subnets to the classful major network address of
172.30.0.0 when sending routing updates to R2.
ƒ From the perspective of R2, both updates have an equal cost of 1
hop to reach network 172.30.0.0/16. As you will see, R2 installs
both paths in the routing table.

Activity check 7.1.3-3

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 6
 RIPV1 :no VLSM support
ƒ R3 is sending the full 172.30.0.0 major classful network out Serial 0/0/1.
ƒ Why is RIPv1 on R3 not including the other subnets, 172.30.200.16/28 and 172.30.200.32/28, in
updates to R4? Those subnets do not have the same subnet mask as FastEthernet 0/0. This is why
all subnets must use the same subnet mask when a classful routing protocol is implemented in the
network.

RIP V1 :No CIDR 7.1.5-1

PT 7.1.5-2
ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 7
 Enable Rip V2 7.2.1-2
7.2.2

7.2.4-1
PT 7.2.4-2
ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 8
 One of the goals of Classless Inter-Domain Routing (CIDR) as stated by RFC 1519 is "to provide a
mechanism for the aggregation of routing information.“
On the R2 router, we configured a supernet - a static route to a single network that is used to represent
multiple networks or subnets.

RIP V2 & CIDR 7.3.2

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 9
 Verification & troubleshooting 7.4.1

ƒ It is always best to begin with the basics:

ƒ 1. Make sure all of the links (interfaces) are up and operational.
ƒ 2. Check the cabling.
ƒ 3. Check to make sure you have the correct IP address and subnet
mask on each interface.
ƒ 4. Remove any unnecessary configuration commands that are no
longer necessary or have been replaced by other commands.

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 10
 Common RIP v2 issues

ƒ Network Statements
ƒ Another source of problems might be incorrect or missing network
statements. Remember, the network statement does two things:
ƒ It enables the routing protocol to send and receive updates on any
local interfaces that belong to that network.
ƒ It includes that network in its routing updates to its neighboring
routers.
ƒ A missing or incorrect network statement will result in missed
routing updates and routing updates not being sent or received on
an interface.
ƒ Automatic Summarization
ƒ If there is a need or expectation for sending specific subnets and
not just summarized routes, make sure that automatic
summarization has been disabled.
ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 11
 Authentication

ƒ A security concern of any routing protocol is the possibility of

accepting invalid routing updates.
ƒ The source of these invalid routing updates could be an attacker
maliciously attempting to disrupt the network or trying to capture
packets by tricking the router into sending its updates to the wrong
destination.
ƒ Another source of invalid updates could be a misconfigured router.
ƒ Whatever the reason, it is good practice to authenticate routing
information transmitted between routers.
ƒ RIPv2, EIGRP, OSPF, IS-IS, and BGP can be configured to
authenticate routing information.
ƒ This practice ensures routers will only accept routing information
from other routers that have been configured with the same
password or authentication information.
Animation 7.4.3-1
ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public
PT 7.4.3-2 12
 Labs and Activities

ƒ Lab 7.5.1-1
ƒ PT 7.5.1-2
ƒ Lab 7.5.2-1
ƒ PT 7.5.2-2
ƒ Lab 7.5.3-1
ƒ PT 7.5.3-2

ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 13
ITE 1 Chapter 6 © 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 14