Task 1:
For reference information on configuring hostnames, please refer to:
Lab 35 Configuration and Verification Task 1
Task 2:
For reference information on configuring DCE clocking, please refer to:
Lab 35 Configuration and Verification Task 2
Task 3:
R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#int s0/0
R1(config-if)#ip add 192.168.0.1 255.255.255.252
R1(config-if)#no shutdown
R1(config)#int loo 100
R1(config-if)#ip add 10.10.100.1 255.255.255.224
R1(config-if)#exit
R1(config)#int loo 101
R1(config-if)#ip add 10.10.101.1 255.255.255.192
R1(config-if)#end
R1#
R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R2(config)#int s0/0
R2(config-if)#ip address 192.168.0.2 255.255.255.252
R1(config-if)#no shutdown
R2(config-if)#end
R2#
R1#ping 192.168.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
R2#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Task 4:
R2#conf t
Enter configuration commands, one per line. End with CNTL/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 CNTL/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. These are:
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. |