CCNA: Semester 2 RIP: Network Discovery

Objective
In this lab, you will configure RIP routing between all three routers. This will allow your routers to route packets so that all routers and all hosts will be able to reach (ping) each other. This is the first RIP lab we have had, so we will discuss many of these items in more detail later. For now we will focus on the RIP update messages being exchanged between the routers. Instructor note: This lab is under the assumption that students are not yet familiar with configuring RIP. This lab is designed for discussing information about network discovery from the chapter on Routing Theory and Concepts.

Scenario
There are five separate classful networks. After configuring RIP, we want to view the RIP update messages being sent and received by each router. Questions: What are the different classful networks? Are there any subnets? If so, what are they?

Setup
Use the 8 Steps to Success to help you configure the routers. Be sure your cabling is correct, as this causes more troubleshooting issues than anything else. If the routers have a startup-config already on them, erase it and reboot the routers. Configure the routers to include hostnames and the proper interface commands including IP addresses, subnet masks, etc. Each router should be able to ping the interface of the adjacent (neighboring) router and the host on its LAN (Ethernet) interface. Test and troubleshoot as necessary.

Basic Configurations Does not include clock rate, no shutdown and some other necessary commands. Note: Even though the networks are in numerical order, obviously this does not need to be the case. We only did this to make it easier to remember where the networks originated from. SanJose2 hostname SanJose2 interface ethernet 0 ip add 192.168.1.1 255.255.255.0 interface serial 0 ip add 192.168.2.1 255.255.255.0 SanJose1 hostname SanJose1 interface ethernet 0 ip add 192.168.3.1 255.255.255.0 interface serial 0 ip add 192.168.2.2 255.255.255.0 interface serial 1 ip add 192.168.4.2 255.255.255.0 Baypointe hostname Baypointe interface ethernet 0 ip add 192.168.5.1 255.255.255.0 interface serial 0 ip add 192.168.4.1 255.255.255.0

Step 1 Starting debug ip rip

BEFORE we configure RIP, we want to turn on the debugging of RIP messages. This is not a normally something you would do on a production network unless you are troubleshooting the network. However, the whole purpose of this lab is to view the RIP updates messages sent and received by each router, so we will use the debug command to accomplish this task. Use the following command on each router to keep the debug out from interfering with you command-line input: Router(config)# line console 0 Router(config-line)# logging synchronous On each router, start the process debug ip rip, which will allow us to view RIP update messages being sent and received. You must be in privileged mode to run debug. SanJose1# debug ip rip RIP protocol debugging is on SanJose2# debug ip rip RIP protocol debugging is on Baypointe# debug ip rip RIP protocol debugging is on

Step 2 Starting RIP

We will examine RIP much more closely later (chapter on Routing Protocols), but for now all you need to know is how to start RIP. (There really isnt much more to it than that!) Now we can start RIP on each router. From global configuration you will enter the command: Router(config)#router rip Once you are in the Router RIP configuration sub-mode, all you need to do is enter the classful network address for each directly connected network, using the network command. Router(config-router)#network directly-connected-classful-network-address For the best viewing results, I would suggest doing these commands in this order. Here are the commands for each router: SanJose2#configure terminal Enter configuration commands, one per line. SanJose2(config)#router rip SanJose2(config-router)#network 192.168.1.0 SanJose2(config-router)#network 192.168.2.0 End with CNTL/Z.

Baypointe#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Baypointe(config)#router rip Baypointe(config-router)#network 192.168.4.0 Baypointe(config-router)#network 192.168.5.0 SanJose1#configure terminal Enter configuration commands, one per line. SanJose1(config)#router rip SanJose1(config-router)#network 192.168.2.0 SanJose1(config-router)#network 192.168.3.0 SanJose1(config-router)#network 192.168.4.0 You will immediately begin to see: SanJose2 01:03:27: RIP: sending v1 update to 01:03:27: network 192.168.2.0, 01:03:27: RIP: sending v1 update to 01:03:27: network 192.168.1.0, Baypointe 01:02:37: RIP: sending v1 update to 01:02:37: network 192.168.4.0, 01:02:37: RIP: sending v1 update to 01:02:37: network 192.168.5.0, 255.255.255.255 via Ethernet0 (192.168.1.1) metric 1 255.255.255.255 via Serial0 (192.168.2.1) metric 1 255.255.255.255 via Ethernet0 (192.168.5.1) metric 1 255.255.255.255 via Serial0 (192.168.4.1) metric 1 End with CNTL/Z.

SanJose1 01:07:14: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.3.1) 01:07:14: network 192.168.4.0, metric 1 01:07:14: network 192.168.2.0, metric 1 01:07:14: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.2.2) 01:07:14: network 192.168.4.0, metric 1 01:07:14: network 192.168.3.0, metric 1 01:07:14: RIP: sending v1 update to 255.255.255.255 via Serial1 (192.168.4.1) 01:07:14: network 192.168.2.0, metric 1 01:07:14: network 192.168.3.0, metric 1

Step 3 Understanding the debug ip rip output

Because we have RIP protocol debugging on (debug ip rip) we will begin to see network discovery, as each router: SENDING RIP MESSAGES Each router will begin to send RIP update message out each interface belonging to one of the network statements. SanJose2(config)#router rip SanJose2(config-router)#network 192.168.1.0 SanJose2(config-router)#network 192.168.2.0 For example, SanJose2 to will send out RIP update messages on Ethernet 0 because that interface has an IP address that belong to the network 192.168.1.0, and on Serial 0 because that interface has an IP address that belongs to the network 192.168.2.0. Just because a router has a directly connected network does not mean it will automatically include that network in its routing updates to neighboring routers. The network command also tells the RIP to include these networks in its updates to adjacent neighbors. 255.255.255.255 via Ethernet0 (192.168.1.1) metric 1 255.255.255.255 via Serial0 (192.168.2.1) metric 1

SanJose2 01:03:27: RIP: sending v1 update to 01:03:27: network 192.168.2.0, 01:03:27: RIP: sending v1 update to 01:03:27: network 192.168.1.0,

LISTENING FOR RIP MESSAGES Routers will also listen for RIP messages on each interface belonging to one of the network statements. For example, SanJose2 to will listen for RIP update messages on Ethernet 0 because that interface has an IP address that belong to the network 192.168.1.0, and also listen for RIP update messages on Serial 0 because that interface has an IP address that belongs to the network 192.168.2.0. As RIP messages are received router, will add those networks in the messages to their routing tables: o If the RIP message contains a network not currently in the routing table. o If the RIP message contains a network with a better metric (fewer hops) than an entry currently in the routing table. SanJose2 01:10:56: RIP: received v1 update from 192.168.2.2 on Serial0 01:10:56: 192.168.4.0 in 1 hops 01:10:56: 192.168.3.0 in 1 hops

NOTE: We will discuss this lab in class, so be sure to review the outputs carefully.

Step 4 Viewing the debug ip rip output

Remember that SanJose1 will learn routes to networks from SanJose2. It will then send that information to Baypointe, telling Baypointe that it is the next hop to get to those networks, and incrementing the metric (hop count) by one. After convergence, each router will continue to send its RIP update messages out the appropriate interfaces every 30 seconds. Lets look at the debug messages and the routing table for each router: SanJose2 01:30:45: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.1.1) 01:30:45: network 192.168.4.0, metric 2 01:30:45: network 192.168.5.0, metric 3 01:30:45: network 192.168.2.0, metric 1 01:30:45: network 192.168.3.0, metric 2 01:30:45: RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.2.1) 01:30:45: network 192.168.1.0, metric 1 SanJose2# 01:30:50: RIP: received v1 update from 192.168.2.2 on Serial0 01:30:50: 192.168.4.0 in 1 hops 01:30:50: 192.168.5.0 in 2 hops 01:30:50: 192.168.3.0 in 1 hops SanJose2# SanJose2#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, * - candidate default U - per-user static route, o - ODR Gateway of last resort is not set R 192.168.4.0/24 R 192.168.5.0/24 C 192.168.1.0/24 C 192.168.2.0/24 R 192.168.3.0/24 SanJose2# [120/1] via [120/2] via is directly is directly [120/1] via 192.168.2.2, 00:00:10, Serial0 192.168.2.2, 00:00:10, Serial0 connected, Ethernet0 connected, Serial0 192.168.2.2, 00:00:10, Serial0

SanJose1 01:33:05: 01:33:05: SanJose1# 01:33:07: 01:33:07: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: 01:33:08: SanJose1# RIP: received v1 update from 192.168.4.1 on Serial1 192.168.5.0 in 1 hops RIP: received v1 update from 192.168.2.1 on Serial0 192.168.1.0 in 1 hops RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.3.1) network 192.168.4.0, metric 1 network 192.168.5.0, metric 2 network 192.168.1.0, metric 2 network 192.168.2.0, metric 1 RIP: sending v1 update to 255.255.255.255 via Serial0 (192.168.2.2) network 192.168.4.0, metric 1 network 192.168.5.0, metric 2 network 192.168.3.0, metric 1 RIP: sending v1 update to 255.255.255.255 via Serial1 (192.168.4.2) network 192.168.1.0, metric 2 network 192.168.2.0, metric 1 network 192.168.3.0, metric 1

SanJose1#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, * - candidate default U - per-user static route, o - ODR Gateway of last resort is not set C 192.168.4.0/24 R 192.168.5.0/24 R 192.168.1.0/24 C 192.168.2.0/24 C 192.168.3.0/24 SanJose1# is directly [120/1] via [120/1] via is directly is directly connected, Serial1 192.168.4.1, 00:00:12, Serial1 192.168.2.1, 00:00:10, Serial0 connected, Serial0 connected, Ethernet0

Baypointe 01:34:53: RIP: 01:34:53: 01:34:53: 01:34:53: 01:34:53: 01:34:53: RIP: 01:34:53: Baypointe# 01:34:56: RIP: 01:34:56: 01:34:56: 01:34:56: Baypointe# sending network network network network sending network v1 update to 192.168.4.0, 192.168.1.0, 192.168.2.0, 192.168.3.0, v1 update to 192.168.5.0, 255.255.255.255 via Ethernet0 (192.168.5.1) metric 1 metric 3 metric 2 metric 2 255.255.255.255 via Serial0 (192.168.4.1) metric 1

received v1 192.168.1.0 192.168.2.0 192.168.3.0

update from 192.168.4.2 on Serial0 in 2 hops in 1 hops in 1 hops

Baypointe#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, * - candidate default U - per-user static route, o - ODR Gateway of last resort is not set C 192.168.4.0/24 C 192.168.5.0/24 R 192.168.1.0/24 R 192.168.2.0/24 R 192.168.3.0/24 Baypointe# is directly is directly [120/2] via [120/1] via [120/1] via connected, Serial0 connected, Ethernet0 192.168.4.2, 00:00:23, Serial0 192.168.4.2, 00:00:23, Serial0 192.168.4.2, 00:00:23, Serial0

NOTE: At this point all routers should be able to ping all networks. We will discuss RIP much more in the chapter on Routing Protocols (RIP).

Step 5 Turning-off debug

Dont forget to turn-off debug when you are done collecting the output. Router# undebug all or Baypointe# undebug ip rip

Step 6 Reflections
In class we will discuss some of the following issues with network discovery and RIP update messages: Split horizon Split horizon with poison reverse (This is Ciscos implementation, however this information is not displayed with debug ip rip.) RIP update messages and the routing tables. Do the routers need to send RIP messages out its stub Ethernet interfaces?

Once again, congratulations! Your understanding of this information will help you go a long way in understanding other aspects of networking and routing.
7