Packet Tracer Lab 7.4.3.2 Reflection

This lab is called routing table corruption. It was a lengthy lab, but it was not difficult to do because the directions were clear. The first thing I had to do in this lab was turn on all the interfaces on the routers starting with R1. Then I had to examine the routing table of R1. After that, I entered the routing protocol on each router using the commands: router rip, network 172.16.0.0, exit respectively. The next step was to configure the default route on a router and use the default-information originate command to propagate the default route to the other routers on the network. After that, I had to configure static routes on the ISP router for the 172.16.1.0, 172.16.2.0, 172.16.3.0 and 172.16.5.0. The final thing I had to do was cable the Fa0/0 interface on R4 to the Fa1/0 interface on R3. All in all, this lab was fairly simple and easy to complete. It taught me how to "corrupt" routes in networks.

Packet Tracer Lab 7.2.4.2 Reflection

This lab is about RIPv2. The main goal of the activity is to teach the user how to configure RIPv2 in the network. The first thing I had to do was examine the current operation of RIPv1 on each of the routers by using the show ip protocol and show ip route commands. Then I used router rip and then used version 2 to configure RIPv2 on each of the routers. Then to verify that it worked, I used debug ip rip. Since RIPv2 is a classless routing protocol, it cannot have summarized routes because it needs to also support VLSM. If the network administrator does not disable auto-summarization, the RIPv2 could make incorrect decisions. In order to avoid that, I had to disable auto-summary and to do that, I had to enter the router rip command and then the no auto-summary. After that, I had to verify everything was done correctly and I entered the show ip protocols and show ip route commands. The final step was to examine how RIPv2 works and for that, I had to enter the Simulation mode and capture packets.

Packet Tracer Lab 7.1.5.2 Reflection

This activity was centered around verifying the connectivity of the network. I didn't really have to do anything for this lab, but I felt it was important that I attempted to follow the directions so I could see exactly how a non-convergence command can be used in networking. The first thing I had to do in the lab was ping the FastEthernet ports of routers R1 and R3. After analyzing the results, I was instructed to ping other addresses on other routers from R1 and R3. After that, I had to enter the debug ip rip command in order to see how the RIP was working. Then, I entered Simulation Mode on Packet Tracer and used the ping 172.30.1.1 command from router 2 and clicked the Auto Capture/ Play button in order to see whether or not the ping worked. All in all, this lab wasn't made to present any sort of a challenge to the user, but to give the user a good sense of how these non-convergence commands work.

Packet Tracer Lab 7.1.2.3 Reflection

This lab was a refresher activity on what we learned in Chapter 5 about RIPv1 and its configuration. The lab opened with a pre-done topology which is the basic topology of the chapter. It consisted of three routers and four switches. The lab's instructions said to execute the basic configurations on each of the routers using the routing table that the instructions provide. The first thing I had to do for this lab was configure the RIP on R1using the instructions the lab gave me. At first, I messed up because I put the individual network addresses in, but after reading later I saw that the lab required me to enter the summarized network addresses. Then I repeated that process for the other two routers. I also had to set passive interfaces which were not connected to the routers. Overall, this lab was pretty simple and because the instructions told me how to do it, it was even easier.

Topology

Routing Table