Lab 11 RIP Lesson A

Objective 

• To configure RIP in a simple network.
• To check metrics and administrative distance and for RIP.

Topology

Basic Setting

IPs for computers and routers have been set up.

Requirements

• You need to configure routers to use RIP to learn routing tables.
• You should use Version 2 RIP.
• You should be able to check routes based on RIP. 
• Test connectivity
• Monitor exchange of routing info based on RIP.

Steps
On Route2
Router#confi t
Router(config)#router rip
Router(config-router)#network 172.16.0.0
Router(config-router)#version 2

On Router3
Router#confi t
Router(config)#router rip
Router(config-router)#network 172.16.0.0
Router(config-router)#version 2
Router(config-router)#

On Router0
Router#confi t
Router(config)#router rip
Router(config-router)#network 172.16.0.0
Router(config-router)#version 2
Router(config-router)#

On Router1
Router#confi t
Router(config)#router rip
Router(config-router)#network 172.16.0.0
Router(config-router)#version 2
Router(config-router)#

Check 
Routing table on Router2
Router#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
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
172.16.0.0/24 is subnetted, 6 subnets
C 172.16.0.0 is directly connected, FastEthernet0/0
R 172.16.1.0 [120/2] via 172.16.3.2, 00:00:10, Serial2/0
R 172.16.2.0 [120/2] via 172.16.3.2, 00:00:10, Serial2/0
C 172.16.3.0 is directly connected, Serial2/0
R 172.16.4.0 [120/1] via 172.16.3.2, 00:00:10, Serial2/0
R 172.16.5.0 [120/1] via 172.16.3.2, 00:00:10, Serial2/0
Router#

Ping from PC1 to PC0
PC>ping 172.16.1.2
Pinging 172.16.1.2 with 32 bytes of data:
Request timed out.
Reply from 172.16.1.2: bytes=32 time=23ms TTL=125
Reply from 172.16.1.2: bytes=32 time=19ms TTL=125
Reply from 172.16.1.2: bytes=32 time=27ms TTL=125
Ping statistics for 172.16.1.2:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 27ms, Average = 23ms
PC>

Ping from PC1 to PC2
PC>ping 172.16.2.2
Pinging 172.16.2.2 with 32 bytes of data:
Request timed out.
Reply from 172.16.2.2: bytes=32 time=20ms TTL=125
Reply from 172.16.2.2: bytes=32 time=25ms TTL=125
Reply from 172.16.2.2: bytes=32 time=23ms TTL=125
Ping statistics for 172.16.2.2:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 25ms, Average = 22ms
PC>

Mointor RIP information exchange on Router2
Router#debug ip rip
RIP protocol debugging is on
Router#RIP: received v2 update from 172.16.3.2 on Serial2/0
172.16.1.0/24 via 0.0.0.0 in 2 hops
172.16.2.0/24 via 0.0.0.0 in 2 hops
172.16.4.0/24 via 0.0.0.0 in 1 hops
172.16.5.0/24 via 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (172.16.0.1)
RIP: build update entries
172.16.1.0/24 via 0.0.0.0, metric 3, tag 0
172.16.2.0/24 via 0.0.0.0, metric 3, tag 0
172.16.3.0/24 via 0.0.0.0, metric 1, tag 0
172.16.4.0/24 via 0.0.0.0, metric 2, tag 0
172.16.5.0/24 via 0.0.0.0, metric 2, tag 0
RIP: sending v2 update to 224.0.0.9 via Serial2/0 (172.16.3.1)
RIP: build update entries
172.16.0.0/24 via 0.0.0.0, metric 1, tag 0

Turn off Debug on Router2
Router#undebug all
All possible debugging has been turned off