Lab Objective:
The objective of this lab exercise is for you to learn and understand how RIPv2 updates are sent. Unlike RIPv1, RIPv2 sends updates using multicast.
Lab Purpose:
RIPv2 update debugging is a fundamental skill. By default, RIPv2 sends updates via multicast. You can use debugging commands to troubleshoot network and routing problems. As a Cisco engineer, as well as in the Cisco CCNA exam, you will be expected to know how to verify RIPv2 updates using debugging commands.
Certification Level:
This lab is suitable for CCNA certification exam preparation.
Lab Difficulty:
This lab has a difficulty rating of 6/10.
Readiness Assessment:
When you are ready for your certification exam, you should complete this lab in no more than 10 minutes.
Lab Topology:
Please use the following topology to complete this lab exercise:
Task 1:
This lab will use only two routers. Configure the hostnames on routers R1 and R2 as illustrated in the topology.
Task 2:
Configure a back-to-back Serial connection between R1 and R2. Configure the DCE interface Serial0/0 in R2 to provide clocking to R1 at a clock speed of 2 Mbps.
Task 3:
Configure IP addresses 192.168.0.1/30 and 192.168.0.2/30 on R1 and R2 Serial0/0 interfaces, respectively. Configure the Loopback interfaces on R1 with the IP addresses illustrated in the topology.
Task 4:
Enable RIPv2 for the Serial0/0 interface on R2 and the Serial 0/0 and Loopback interfaces on R1.
Task 5:
Enable debugging on R1 and R2 and verify that RIPv2 updates are being sent out of all RIPv2-enabled networks. Keep in mind that by default, RIP sends updates every 30 seconds, so you will typically see updates within that timeframe. Familiarize yourself with the output of the debugs. Be sure to disable debugging when done.
Configuration and Verification
Task 1:
For reference information on configuring hostnames, please refer to earlier labs.
Task 2:
For reference information on configuring DCE clocking, please refer to earlier labs.
Task 3:
For reference information on configuring IP addressing, please refer to earlier labs.
Task 4:
R2#conf t Enter configuration commands, one per line. End with CTRL/Z. R2(config)#router rip R2(config-router)#version 2 R2(config-router)#net 192.168.0.0 R2(config-router)#end R2# R1#conf t Enter configuration commands, one per line. End with CTRL/Z. R1(config)#router rip R1(config-router)#net 10.0.0.0 R1(config-router)#net 192.168.0.0 R1(config-router)#end R1#
Task 5:
R1#debug ip rip events RIP event debugging is on *Mar 1 02:13:44.358: RIP: sending v2 update to 224.0.0.9 via Loopback101 (10.10.101.1) *Mar 1 02:13:44.358: RIP: Update contains 2 routes *Mar 1 02:13:44.358: RIP: Update queued *Mar 1 02:13:44.358: RIP: Update sent via Loopback101 *Mar 1 02:13:44.362: RIP: ignored v2 packet from 10.10.101.1 (sourced from one of our addresses) *Mar 1 02:13:46.189: RIP: sending v2 update to 224.0.0.9 via Loopback100 (10.10.100.1) *Mar 1 02:13:46.189: RIP: Update contains 2 routes *Mar 1 02:13:46.189: RIP: Update queued *Mar 1 02:13:46.189: RIP: Update sent via Loopback100 *Mar 1 02:13:46.193: RIP: ignored v2 packet from 10.10.100.1 (sourced from one of our addresses) *Mar 1 02:13:46.962: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (192.168.0.1) *Mar 1 02:13:46.962: RIP: Update contains 2 routes *Mar 1 02:13:46.962: RIP: Update queued *Mar 1 02:13:46.962: RIP: Update sent via Serial0/0 R1#undebug all All possible debugging has been turned off R2#debug ip rip events RIP event debugging is on *Mar 1 02:15:49.395: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (192.168.0.2) - suppressing null update *Mar 1 02:15:56.186: RIP: received v2 update from 192.168.0.1 on Serial0/0 *Mar 1 02:15:56.186: RIP: Update contains 2 routes *Mar 1 02:16:15.790: RIP: sending v2 update to 224.0.0.9 via Serial0/0 (192.168.0.2) - suppressing null update *Mar 1 02:16:25.422: RIP: received v2 update from 192.168.0.1 on Serial0/0 *Mar 1 02:16:25.422: RIP: Update contains 2 routes R2#undebug ip rip events RIP event debugging is off
NOTE: There are two other options available when it comes to debugging RIP:
R1#debug ip rip ? database RIP database events events RIP protocol events trigger RIP trigger extension <cr>
Play around with these options and familiarize yourself with the information they print. Also, remember that debugging is very processor-intensive and can do more harm than good in a live network, so always make sure you disable debugging when you have captured the information you were looking for.