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.

LAB1 Jerome Cardenas CCNA2

In this lab, we were required to set up a topology in packet tracer, that was presented on the board. The topology consisted of three routers, four switches, and twelve hosts in total. We first needed to get all the devices that we needed. We were told to use 2811 routers and 2950 switches. The hosts I used were all desktops. Afterwards, I put in all the necessary modules in the routers in order to set it up as its supposed to. I used four WIC-2T in order to have plenty of serial ports. I also put one NM-ESW-161 which provides us with 16 switching ports in each router. Here is a screenshot of the fully functional network.

I also configured each router in order to have the correct path to send packets. For each interface, I used the CLI in order to configure the correct path of the packets. For example, for the branch  router, I used the commands:

enable

config t

int s0/0/0

ip address 1.1.1.1 255.255.255.252

no shutdown

exit

This was used in order to configure the interface s0/0/0 which leads to s0/0/1. 

Here is the screen shot for each router's port view.

As you can see, in the screen shots, I configured each interface that was connected to each router. I configured each fast ethernet and serial that connected to branch and remote. However for HQ, I just needed to configure Serial interfaces, because there was no other interface that was connected to it. For HQ, I also set the clock rate to 64000.

The following is the routing table for each router:

HQ#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

Branch#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

C    192.168.1.0/24 is directly connected, FastEthernet0/0

C    192.168.2.0/24 is directly connected, FastEthernet0/1

remote#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

C    192.168.3.0/24 is directly connected, FastEthernet0/0

C    192.168.4.0/24 is directly connected, FastEthernet0/1

Packet Tracer Exploration: Ch4 - Packet tracer Skills Integration Challenge

This activity focused on subnetting skills, basic device configuration, and static routing. In this lab I learned how to design and document an addressing scheme thats based on the requirements. I learned how to pick out appropriate equipment, then cabled the devices. I Configured the static and default routing. I then learned how to verify full connectivity between all devices in the topology. First I designed an addressing scheme. First I placed four 2621XM in the network topology. I then connected all of the routers to 2621XM. I then renamed each router and it's hostname: [B1; B2; B3; B4]. I then connected switches to each router. Each router has 4 switches. I configured each switch to the subnet. I then configured all the routers to R1. I then tested the end-to-end connectivity. I used the ping command to do this. Each router pinged all other router interfaces and the web server. I used extended pings to test LAN connectivity to the web server. I then used verification commands to make sure that my configurations are complete.

Packet Tracer Exploration: Routing Loops

First of all, in this lab, all the routers have already been configured. All I am left to do is to identify the conditions leading to a routing loop and the implications on the router performance. I first examined branch1's configuration using the show run command. Then I located the static route command which is ip route 0.0.0.0 0.0.0.0 serial 0/. I did the same thing to examine branch2's configuration except to locate the static route command, i used the command ip route 0.0.0.0 0.0.0 serial 0/0. I tried to verify the connectivity from PC2 to PC0 using the ping command. The ping command was not successful and the packets failed to reach the destination. I reconfigured the routes by first clearing the current static route configuration. I did this by using the no ip route command. on both branch1 and branch2. I then re-configured the routers so that they can properly connect to each other. I then verified their connectivity again by using the ping command from PC2 to PC0, and it turns out my configuration was successful.

Packet Tracer Exploration: Ch3 - Packet Tracer Skills Integration Challenge

This packet tracer is an overview of the entire chapter and previous packet tracers that I had completed in the past.  First I designed an addressing scheme, then documented it. I then needed to select equipment and cable devices that were necessary for the network. I then connected the network together. Afterwards, I was able to apply basic configuration to each device in the network.  After that, then I configured static and default routing. Once that was done, I was able to test the connectivity of the devices to make sure that each device was configured properly. I used commands such as ping.  Oi then examined the configuration to make sure my configurations are complete.

Packet Tracer Exploration: Subnetting Scenario 3

In this lab, i was given the network address 192.168.1.0/24 to subnet and provide the IP addressing for then network shown in the topology diagram. First I examined the Network Requirements. I then Designed an IP addressing scheme by subnetting the 192.168.1.0/24 network into the appropriate number of subnets. In this packet tracer activity, I was able to determine the number of subnets that are needed. I then determined the number of hosts needed, and learned how to design the number of hosts needed. I then learned how to conduct research to find a solution

Packet Tracer Exploration: Subnetting Scenario 2

First I examined the network requirements. I then Designed an IP addressing scheme by subnetting the 172.16.0.0 network into the appropriate number of subnets. I needed to allow for the maximum number of hosts which was required for the largest subnet. I assigned the subnets to the network from the topology diagram. I assigned IP addresses to the Network Devices. First I assigned am address to the HQ router, then an address to the west router. I then assigned addresses to the East router, then addresses to the Branch1 router. Then I assigned addresses to the Branch 2 router, then assigned addresses to the Branch 3 router. I then assigned addresses to the Branch 4 router. Then I assigned addresses to the host PCs/ In the final task, I tested the Network Design. by applying my addressing scheme to the packet tracer file. I then Checked to see that all devices connected networks can ping each other and they were successful. In this packet tracer activity, I learned how to determine the number of subnets needed. I then determined the number of hosts needed. I then designed an appropriate addressing cheme. I then learned how to assign addresses and subnet mask pairs to device interfaces and hosts. I then examined the use of the available network address space. I then determined how static routing could be applied to the network.

Packet Tracer Exploration Subnetting Scenario 1

First I examined the network requirements. I then designed the IP addressing scheme by first subnetting the 192.168.9.9 network into the appropriate number of subnets. I then Assigned the subnets to the network shown in the Topology Diagram. In the third task, I assigned the IP address to the Network Devices, by first assign addresses to the HQ router. I then Assigned addresses to the BRANCH1 router also to the BRANCH2 router. I then assigned addresses to the host PCs. Lastly, i tested the Network Design. In this Packet Tracer activity, i determined the number of subnets needed. I determined the number of hosts needed. I designed an appropriate addressing scheme. I also assigned addresses and subnet mask pairs to device interfaces and hosts. I then Examined the use of the available network address space. I lastly, learned how to determine how static routing could be applied to the network.

Packet Tracer Exploration: Viewing Routing Table Information

In this packet tracer activity, I used the show ip route command so i can see details of routing table entries. All i needed to do was show the contents of the routing tables, since all routers have been configured. I used a version of the show ip command so I can see the details of routing table entries. In this packet tracer activity, I was able to review how to read and identify various things in the routing tables.

Packet Tracer Exploration: Convergence

In this packet tracer, I viewed the routing table of a converged network. I added a new Local area network to the topology. I learned how to view the debugging output. I finally watched the process of the network converging. First, I viewed the routing table for Routing table for Router2 and router 3. I then Documented the networks i learned from RIP. I then added a new LAN to the network topology by first adding a new 2960 switch and host to Router3. I Cabled the Switch from Fa0/1 interface to Router3's Fa0/1 interface. I then cabled the host to the fa0/2 interface on the switch.I then configured the appropriate IP addresses from the 12.0.0.0/8 addressing scheme for this LAN. I then Enabled the Fa0/1 interface on Router 3. I then Determined if the network has converged. I then turned on debugging on both routers. Afterwards, I was required to advertise the newly added network. THen I turned debugging off on router 2. I checked to see if the network has converged. In this lab, i learned how network converging works and how to actually set it up like that

Packet Tracer Exploration: Characteristics of IGP and EGP Routing Protocols

In this activity, i configured the default route from AS2 and AS3 (two different companies to the ISP (AS1) to simulate the Exterior Gateway Routing that would take place from both companies to the ISP. I then configured a static route from the ISP to AS2 and AS3 to simulate the exterior gateway routing that would take place from the ISP to its 2 customers AS2 and AS3. I looked at the routing table before and after both static routes and default routes were added so that i can observe how the routing table has changed. I verified the connections of each routers by checking to see if ping tests works. they did, and this packet tracer was successful.

Packet Tracer Exploration: Configure Ethernet Interfaces for IP on Hosts and routers

I used the packet tracer to practice configuring interfaces. Follow the additional instructions provided in the activity to examine the ARP process in simulation mode. First I configured IP information on Ethernet interfaces in a network. I then Configured the IP information on the PCs. I then Configured the IP information on router Ethernet interfaces. I was required to verify proper operation. I also verified the status on the bus routers, then the connectivity between hosts and routers. I went into simulation mode and observed the ARP operation. In this packet tracer activity, I practiced configuring PC's and Router Ethernet Interfaces. I then verified everything I did to make sure they were correct.

Packet Tracer Exploration: Build the Chapter Topology

In this packet tracer, I added all the necessary devices and connect them with the correct cabling. In this packet tracer, I first placed the devices on the topology. I then configured them accordingly. I added all the modules to the routers. I then named the devices in order to keep track of them and so that everything can be organized in the network. I then connected the devices. I connected the routers to each other using serial DCE. I also connected the devices to each other using straight through cables. I also used straight through cables in order to connect the LANs properly. In this activity, I learned how to place devices, configure them, rename them, then cable them.

Packet Tracer Exploration: Challenge Router Configuration

In this packet tracer activity, I designed and applied an IP addressing scheme for the topology show in the Topology Diagram. I allocated one class C network that i needed to subnet in order to provide a logical addressing scheme for the network. I cabled the network all together appropriately. Once the network is cabled, I configured each device with its appropriate basic configuration commands. The routers were then ready for interface address configuration according to the IP addressing scheme. When the configuration is complete, I used IOS commands to verify that the network is working properly. In this activity, I learned to subnet an address with the space it gave me. I was able to assign appropriate addresses to interfaces and document. I reviewed how to cable the network and perform basic configuration tasks on a router. I learned to configure and activate serial and FastEthernet interfaces. I then tested and verified all my configurations.