2. Configuring RIPv2 is a pretty straightforward
process. Only three steps are required:
• 1. enabling RIP by using the router rip global
configuration command
• 2. instructing the router to use RIPv2 by typing
the version 2 command
• 3. telling RIP which networks to advertise by using one
or more network commands
• The first two commands are easy to comprehend, but
the last command requires a little bit more thought. With
the network command you specify which interfaces will
participate in the routing process.
• This command takes a classfull network as a parameter
and enables RIP on the corresponding interfaces.
3. Let's configure our sample network to use
RIP.
• Router R1 and R2 have directly connected subnets.
• We want to include these subnets in the RIP routing
process.
• To do that, we first need to enable RIP on both
routers and then advertise these subnets using the
network command.
4. • On router R1, in the global configuration mode, enter
the router rip command to enable RIP.
• In the RIP configuration mode, change the version of
the protocol to 2 by using the version 2 command.
• Next, use the network 10.0.0.0 command to include
the Fa0/1 interface on the router R1 in the routing
process.
• Remember, the network command takes a classfull
network number as a parameter, so in this case
every interface that has an IP address that begins
with 10 will be included in the RIP process (IP
addresses that begins with 10 are, by default, the
class A addresses and have the default subnet mask
of 255.0.0.0).
5. • For instance, if another interface on the router had
the IP address of 10.1.0.1 it would also be included
in the routing process with the network command.
• You also need to include the link between the two
routers in the RIP routing process.
• This is done by adding another network statement,
network 172.16.0.0.
6. So, the configuration on R1 should look like this:
The configuration on R2 looks similar, but with different
network number for the directly connected subnet:
7. You can verify that router R1 have a route to the R2's
directly connected subnet by typing the show ip
route command:
NOTE - the legend lists "R" for all RIP routes in the
routing table. Also note that the administrative
distance of 120 is shown, together with the metric of