Basic RIP Configuration: Topology Diagram
Basic RIP Configuration: Topology Diagram
Basic RIP Configuration: Topology Diagram
Topology Diagram
Learning Objectives
Upon completion of this lab, you will be able to:
• Cable a network according to the Topology Diagram.
• Erase the startup configuration and reload a router to the default state.
• Perform basic configuration tasks on a router.
• Configure and activate interfaces.
• Configure RIP routing on all routers.
• Verify RIP routing using show and debug commands.
• Reconfigure the network to make it contiguous.
• Observe automatic summarization at boundary router.
• Gather information about RIP processing using the debug ip rip command.
• Configure a static default route.
• Propagate default routes to RIP neighbors.
• Document the RIP configuration.
Scenario A: Running RIPv1 on Classful Networks
Topology Diagram
Step 1: Cable a network that is similar to the one in the Topology Diagram.
You can use any current router in your lab as long as it has the required interfaces shown in the
topology.
Note: If you use 1700, 2500, or 2600 routers, the router outputs and interface descriptions will
appear different.
Step 4: Test the PC configuration by pinging the default gateway from the PC.
Step 3: Configure RIP on the R2 router using the router rip and network commands.
R2(config)#router rip
R2(config-router)#network 192.168.2.0
R2(config-router)#network 192.168.3.0
R2(config-router)#network 192.168.4.0
R2(config-router)#end
%SYS-5-CONFIG_I: Configured from console by console
R2#copy run start
When you are finished with the RIP configuration, return to privileged EXEC mode and save the
current configuration to NVRAM.
Step 4: Configure RIP on the R3 router using the router rip and network commands.
R3(config)#router rip
R3(config-router)#network 192.168.4.0
R3(config-router)#network 192.168.5.0
R3(config-router)#end
%SYS-5-CONFIG_I: Configured from console by console
R3# copy run start
When you are finished with the RIP configuration, return to privileged EXEC mode and save the
current configuration to NVRAM.
Step 1: Use the show ip route command to verify that each router has all of the
networks in the topology entered in the routing table.
Routes learned through RIP are coded with an R in the routing table. If the tables are not
converged as shown here, troubleshoot your configuration. Did you verify that the configured
interfaces are active? Did you configure RIP correctly? Return to Task 3 and Task 4 to review
the steps necessary to achieve convergence.
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.1.0/24 is directly connected, FastEthernet0/0
C 192.168.2.0/24 is directly connected, Serial0/0/0
R 192.168.3.0/24 [120/1] via 192.168.2.2, 00:00:04, Serial0/0/0
R 192.168.4.0/24 [120/1] via 192.168.2.2, 00:00:04, Serial0/0/0
R 192.168.5.0/24 [120/2] via 192.168.2.2, 00:00:04, Serial0/0/0
R1#
R2#show ip route
<Output omitted>
R 192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:22, Serial0/0/0
C 192.168.2.0/24 is directly connected, Serial0/0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
C 192.168.4.0/24 is directly connected, Serial0/0/1
R 192.168.5.0/24 [120/1] via 192.168.4.1, 00:00:23, Serial0/0/1
R2#
R3#show ip route
<Output omitted>
R 192.168.1.0/24 [120/2] via 192.168.4.2, 00:00:18, Serial0/0/1
R 192.168.2.0/24 [120/1] via 192.168.4.2, 00:00:18, Serial0/0/1
R 192.168.3.0/24 [120/1] via 192.168.4.2, 00:00:18, Serial0/0/1
C 192.168.4.0/24 is directly connected, Serial0/0/1
C 192.168.5.0/24 is directly connected, FastEthernet0/0
R3#
Step 2: Use the show ip protocols command to view information about the routing
processes.
The show ip protocols command can be used to view information about the routing
processes that are occurring on the router. This output can be used to verify most RIP
parameters to confirm that:
• RIP routing is configured
• The correct interfaces send and receive RIP updates
• The router advertises the correct networks
• RIP neighbors are sending updates
R1#show ip route
Step 3: Use the debug ip rip command to view the RIP messages being sent and
received.
Rip updates are sent every 30 seconds so you may have to wait for debug information to be
displayed.
R1#debug ip rip
R1#RIP: received v1 update from 192.168.2.2 on Serial0/0/0
192.168.3.0 in 1 hops
192.168.4.0 in 1 hops
192.168.5.0 in 2 hops
RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0
(192.168.1.1)
RIP: build update entries
network 192.168.2.0 metric 1
network 192.168.3.0 metric 2
network 192.168.4.0 metric 2
network 192.168.5.0 metric 3
RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (192.168.2.1)
RIP: build update entries
network 192.168.1.0 metric 1
The debug output shows that R1 receives an update from R2. Notice how this update includes
all the networks that R1 does not already have in its routing table. Because the FastEthernet0/0
interface belongs to the 192.168.1.0 network configured under RIP, R1 builds an update to send
out that interface. The update includes all networks known to R1 except the network of the
interface. Finally, R1 builds an update to send to R2. Because of split horizon, R1 only includes
the 192.168.1.0 network in the update.
Step 4: Discontinue the debug output with the undebug all command.
R1#undebug all
All possible debugging has been turned off