Lab_9_RIP_Routing_Rev_IR_-_Tagged

pdf

School

Texas A&M University *

*We aren’t endorsed by this school

Course

315

Subject

Computer Science

Date

Feb 20, 2024

Type

pdf

Pages

5

Uploaded by BaronWren4759

Report
ESET 315, Local Area and Metropolitan Network Lab Laboratory 9: Experiments Using RIP Routing and Load Balancing Objective Gain familiarity with the Routing Information Protocol (RIP) dynamic distance vector routing protocol, and understand how routers automatically re-route traffic. Additionally, experiment with load balancing. Note: Please submit the lab report in groups of 4 students. Task 1: Assign IP addresses Table 1 provides the subnet numbers to be used for the network shown in Figure 1. Note that a subnet mask of /30 (255.255.255.252) is used for all the subnets. Table 1: Assign Subnet Numbers Subnet Number Subnet Mask Subnet 1 60.60.60.0 255.255.255.252 or /30 Subnet 2 60.60.60.__ 255.255.255.252 or /30 Subnet 3 60.60.60.__ 255.255.255.252 or /30 Subnet 4 60.60.60.__ 255.255.255.252 or /30 Subnet 5 60.60.60.__ 255.255.255.252 or /30 Subnet 6 60.60.60.__ 255.255.255.252 or /30 TA checkpoint: Show the TA the IP addresses your assigned. Q1: Identify the subnets in Figure 1, and assign an IP address to all the elements within each subnet using Table 2 1
ESET 315, Local Area and Metropolitan Network Lab Figure 1 – Network for Task 1 through 3 Table 2: Figure 1 Network IP addresses Device Node/ interface IP address Subnet Number Subnet Mask Router#1 Int E0 Int E1 Int S0 Router#2 Int S0 Int S1 Router#3 Int E0 Int E1 Int S0 Router#4 G0/0/0 G0/0/1 Laptop A Comp. Eth. Port Laptop B Comp. Eth. Port Task 2: Build and Configure Network in Figure 1 2
ESET 315, Local Area and Metropolitan Network Lab Using the network, you build in Task 1, complete the following steps: Note: Use a clock rate of 56000 for the serial connection. Enable RIP for routing protocol. 1. Check if your network is working by pinging from Desktop A to Desktop B and vice versa (ping from Desktop B to Desktop A). 2. Perform a traceroute from Desktop A to Desktop B and observe the path being used. 3. Use the "show ip route" command to check the routing tables of each router (R1, R2, and R3). 4. Open the Command Prompt on Desktop A and Desktop B (Start->CMD), and type the "route print" command. Inspect the routing table and compare it with the router's routing tables. 5. Enable debugging by typing the "debug ip rip" command in each router's (R1 and R3) privileged EXEC mode prompt. Wait for at least 45 seconds and check whether there was any output from the debug command. (Remember that to turn off specific debug commands, you should type the 'no' option, as in 'no debug ip rip events' . On the other hand, to turn off all debug commands, type 'undebug all' .) Question 2: Provide the screenshots of “sh ip route” for router 3. Check that all subnets are listed in the routing table. Question 3: Provide the screenshots of “debug ip rip” for router 3. This is the RIP advertisement. Observe the information sent in this RIP advertisement and explain the results. TA checkpoint: Show Task 2 results before going to the next Task Task 3: Testing the re-route when a link fails Using the network, you designed in Task 1, simulate a link failure by disconnecting one of the links. For example, you can disconnect the UTP cable between Router 1 and Router 3. 3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
ESET 315, Local Area and Metropolitan Network Lab 1. Check whether your network is working or not (ping from Desktop A to Desktop B, ping from Desktop B to Desktop A). 2. Do a traceroute from Desktop A to Desktop B. Check which path is being used. 3. Use the command “show ip route” to see the routing tables of each router (R1, R2, and R3) 4. Enable debugging: In each Router (R1 and R3), type the command debug ip rip at the privileged EXEC mode prompt. Wait for at least 45 seconds. Was there any output from the debug command? Task 4 Requirements: Load Balancing Across Multiple Paths Using the network shown in Figure 2 you will configure load balancing across multiple paths and observe the process. 1. Build and configure the network in Figure 3. Figure 2: Network to Test for Load Balancing Table 3: Network IP addresses for Figure 2 Device Node/ interface IP address Subnet Number Subnet Mask Router#1 Int E0 Int S0 4
ESET 315, Local Area and Metropolitan Network Lab Int S1 Router#3 Int E0 Int S0 Int S1 Laptop A Comp. Eth. Port Laptop B Comp. Eth. Port 2. Check the basic routing configuration. 2.1 Test your configuration by pinging all interfaces from each host. 2.2 Enter show ip protocol on each router. 2.3 Enter the command show ip route on both routers. List how the route is connected (directly, RIP), the IP address and the network. 3. Verify per-packet load balancing. 3.1 Because there are two routes to the destination network, half the packets are sent along one path and half travel over the other. The path selection alternates with each packet. 3.2 Observe this process by using the “debug ip packet” command on Router1. 3.3 Send 30 ping packets across the network from PC 2 to PC 1. This can be done with the “ping 60.60.60.xx –n 30” command on the host. As the pings are responded to, the router generates IP packet information. Stop the debug by using the command undebug all on Router1. Question 4: Examine and record part of the debug ip packet output. Task 5: Clean Up 1. Turn off the routers. Unplug power to the switches and plug them back so as to reset them 2. Turn your laptop’s firewalls back ON 3. Restore the Windows network configuration settings on the desktops. 4. Place the cables back into the stand. 5. Please check that you can access the internet on all your desktops before leaving the lab. 6. Verify with the TA, before being dismissed and get signed out. 5