Activity 7.5.2: RIPv2 Challenge Configuration Lab

In this packet tracer activity, its similar to the previous one.  There are three routers, four switches, and five host. My first task was to subnet the address space. By doing this, I started off by looking over the network requirements that is included with the activity directions. Afterwards, I assigned the subnetwork addresses to the topology diagram. I assigned the subnet 192.168.40.0 network to the HQ LAN1. My task was then to Determine the interface addresses. First I must assign the appropriate addresses to the device interfaces. After that, I began to cable the network. I was ready to perform basic router configuration to the devices which was BRANCH, HQ, and ISP routers. I configured the router hostname, Disabled the DNS lookup, Configured an EXEC mode password, configured a banner, configured a password of console connections, and configured a password for telnet. I then configured and activated serial and fast ethernet addresses., per each router. I then configured the ethernet interface of PC1, PC2, PC3, PC4, and PC5, along with their IP addresses. I then verified the connectivity to next-hop device. Afterwards, I configured RIPv2 routing on the branch router. HQ router, then static routing on the ISP router. Finally, I verified the configurations.

Packet Tracer Exploration: RIPv2 Basic Configuration Lab 7.5.1.2

This Packet tracer's network topology consists of three routers, four switches, and for hosts. First I cabled the network according to the chart and existing devices. For each router, I loaded the required scripts. I then examined the current status of the network by issuing the "show ip interface brief' command. I checked the connectivity between R2 and the hosts on the R1 and R3 lans. Afterwards, I checked the connectivity between the PCs by sending out several ping commands from one host to another. I then configured RIPv2 on each router. by issuing the command "router rip"then "version 2" right after that. I then verified that RIPv2 is running on the routers by using show ip protocol and show run. I then examined the automatic summarization of routes with the debug ip rip. Then, i disabled automatic summarization by using "router rip" command and "no auto-summary" right afterwards. I did that for each router. I examined the routing table again, and also checked the connectivity between the PC's again. After that, My completion rate from the Packet tracer activity was 100%. I learned how to cable a network according to the topology diagram, how to load scripts, examine routing updates with debug ip rip, disable automatic summarization, examine routing tables, verifying network connectivity, and how to document RIPv2 configuration

Packet Tracer Exploration: Routing Table Corruption 7.4.3.2

This network topology consists of 5 routers. One router at the very top named R2, which is connected to a serial leading to another router named R1. R2 also connects to another router (R3) via crossover cable. R3 and R1 are also connected by a crossover cable. R1 is connected to another router named ISP. There is one other router named R4 that is not connected to anything. First I turned up the interfaces by issuing the no shutdown command in each interface. I examined the routing table on R1. Afterwards, I configured router rip for each router. with the network 172.16.0.0. I then began to configure static routing from the ISP router using the commands:

ip route 172.16.1.0 255.255.255.255.0 s0/0/0
ip route 172.16.2.0 255.255.255.255.0 s0/0/0
ip route 172.16.3.0 255.255.255.255.0 s0/0/0
ip route 172.16.5.0 255.255.255.255.0 s0/0/0

I then connected the Fa0/0 interface on R4 directly to the fa1/0 interface of R3.
Afterwards, I checked the routing table on R4, and everything looked fine and up and running.

Packet Tracer Exploration: Configure RIPv2 7.2.4.2

This packet tracer exploration activity also had the same network topology as the previous chapter 7. First I was required to upgrade the network to RIPv2. I examined the operation of RIPv2 from the CLI tab by issuing "Show ip protocols". I noticed the version of the RIP updates being sent and received. I then issued the "show ip route" command. There were missing routes on R1 and R3 plus the multiple paths to 172.30.0.0/16 on R2. I was ready to configure the routers for RIPv2 In each router i issued router rip, then I entered the command "version 2". Then I used the command "clear ip route" in order to force the routers to rebuild their routing tables so they can converge. I proceeded to examine the operation of RIPv2 with automatic summarization by using the command debug ip rip. I then disabled the automatic summarization by using the command no-auto summary. Finally, I examined RIPv2 updates in simulation mode, so i can examine the PDU information at layer 3, 4, and 7 to observe the exchange process.

Packet Tracer Exploration: Verify Non-Convergence Using Commands 7.1.5.2

In this packet tracer consists of the same network topology setup as the previous network. I did not have to do any configuring, however, we needed to perform several tasks in order to ensure the reliability of the network. First I verified and tested the connectivity. I verified the link status by issuing the command show ip interface brief. Afterwards, I used ping commands from router 2. I used the command "Ping 172.30.1.1, and it was partially successful. Then I pinged 172.30.100.1, and it was also partially successful. Once I was finished with that, I went over to router 1 and accessed the CLI tab. I then pinged devices from there also. I issued the "Ping 10.1.0.1" and "Ping 172.30.100.1" however, Ping 172.30.100.1 was a failed ping, which meant that the connection to that device was not good. I also issued ping commands from router 3 also. I then examined the routing table on each router by accessing their CLI tab and using the "Show IP route" It turns out that there is no connection to the network 172.30.100.0/24. I was able to examine the updates sent and received on router 2 by issuing the "debug ip rip" command. By doing this, I was able to simulate and trace the pings. I entered simulation mode so I can monitor and trace the destination of packets in order to find out where the problem was. By examining the inbound and outbound PDU details in order for me to understand the content of the RIP updates.

Packet Tracer Exploration: Configuring Discontiguous Routes 7.1.2.3

In this packet tracer exploration activity, I am presented with a network topology that consists of three routers. R1, R2, and R3. There are two switches connected to R1 which are named R1 LAN0 and R1 LAN1. One switch is connected to R2 called R2 LAN. One switch is also connected to R3 which is named R3 LAN. It asked me to make basic RIP configurations, which it involved the "router rip" command. Then I put in all the networks necessary by using the "Network [ip address]" command. Afterwards, i issued the commands "passive-interface [interface]" command so that it can suppress sending updates out those interfaces. I then saved by issuing the copy run start command. I repeated this process throughout the rest of the routers in order to finish the rest of the packet tracer activity. I reviewed on how to do basic configuration for RIP throughout the network

LAB2_JeromeCardenas_CCNA

A network topology was presented on the white board, which we were required to build in packet tracer. This is the fully functional topology on packet tracer

We were then required to configure a password for each mode, in each router, in order to keep them secure, and safe from being breached.

We also needed to set up a banner, which also serves as protection for router.

This is the show run command for each router.

ACME ROUTER:

This is the show run for Warner B

It is clear that the banners are set up and passwords that i've configured are encrypted for each router.

In order to make this network in packet tracer, we were also required to insert the correct modules in each router, in order to make the network functional, and cheap as possible.

The following pictures are the physical tab of each router.

WARNER B:

ACME:

In each router, there is only one WIC-2T, because other modules were not necessary. In the open slots, I put covers, to help prevent the router from potentially getting damaged or slowed down due to dust particles.