Packet Tracer 4.7.1.3 Packet Tracer skills integration challenge

For this packet tracer it was very demanding. i had to apply a good amount of skills that i got from the CCNA 1. the first thing that needed to be done was to make an addressing scheme. i had to scan through old notes in order to do this but after that it wasn't that difficult. After i came up with an addressing scheme i started with adding a custom made device named 2621XM Router which is where most of the configuring would take place. i started with some basic configurations using enable password cisco and enable secret class for the encryption and password. From there i went into R1 and i used the first four serial interfaces that would correspond with the interfaces of the custom router as instructed. From there i would move on to doing some more configurations that include adding the addresses i was able to come up with from the 4 subnets. Basically after the addresses i would then set the clock rate for the all the four serial interfaces accompanied with the no shutdown command. After that i moved on to configuring the branches. Similar steps R1 like the clock rate being set to 64000, but that is the only similarity. All four of the LANs made use the same fast ethernet interfaces corresponding of course to one branch since all of them would have different ip addresses. As a result, the next necessary step after that was to do some simple physical connections in the logical works pace which was straightforward. The final part was to finally add the static routes and default routes in order to finally make the topology complete. After that the final part was to test the connectivity using the ping command in order to test connectivity, which was successful.

Packet Tracer 4.5.1.2 Routing Loops

In this lab i was able to troubleshoot a routing loop. it wasn't that difficult of an assignment because the only problem was that the interfaces were configured wrong. All that needed to be done was use no ip route 0.0.0.0 0.0.0.0 s0/1 because that was meant for router Branch 2. then i would use  ip route 0.0.0.0 0.0.0.0 s0/0 to branch 1. D=First i would have to enable an used the config command in order to do there configurations. As a result, i redid the ping that was asked of before and the ping was successful. the reason why was because it was there was no longer a loop on the packets since a proper configuration was added to the routing table.

Lab 3.2.5.2 Convergence

In this packet tracer lab i was able to to add a new LAN that included a switch and PC. From there i had to configure addresses and routes in order to learn more about the debugging output and network converging. the first thing that i did was to analyze the routing table for all of the routers in order to see which of them were associated with the RIP protocol. From there i added the new LAN that included a 2960 switch and host to Router 3. From there i used the certain commands in order to configure the routers with the proper addresses and subnet mask. From there i went to the desktop of the new PC in order to do more ip configurations and add a default route. After that i used the  show ip route command in order to check if the routes i configured were added to the routing table. Although it was configured the route had not been added because the no shutdown command was not used in order to turn the route on.  From there all that was left to do was use the debug ip rip for router R2 and R3 in order for the networks to be added to the routing table. from there i turn off the debugging ip rip with the command no debug ip rip because there are risks associated with the use of the debug command that include it using a lot of memory and other things. From there i was able to get 100% completion.

Lab 3.2.2.2 Characteristics of IGP and EGP routing protcols

In this packet tracer i was able to learn a little about a autonomous system and some new commands. to start off i did the show ip protocol in order to look up the protocols being used for the router selected. this information on gateways, routing for the network and interfaces. their are some similarities with the show ip route in where they show me the routing table and the type of connections and which interface they are connected to. i started with configuring R1 in the autonomous system with ip route 0.0.0.0 0.0.0.0. s0/0/0. this would be classified as the default route that would use the exit interface. that same thing would go for router R2 and R3. From there i would check the routing table for all the routers in order to see if the default routes were added successfully. since the ping from PC1 to ISP failed because of the host being un reachable i would also have to make a static route.  from there i would configure a static route for all of the internal networks apart of AS1. From there i would then ping once again to see if connectivity would be successful. it turning out successful meant that the static routes and default routes were all configured correctly.

Lab 2.2.3.3 configure ethernet interfaces for IP on Hosts and Routers

In this lab i was able to do multiple configurations on a bunch of devices that include PCs, ethernet interfaces etc. for starters i configured the addresses on all three PCSs including the subnet mask, and the default gateway. form there i used the show ip interface brief in order to check the status of the fast ethernet interfaces. form there i moved on to checking the connectivity of the hosts and routers by using the show show arp in order to map the IP address to am MAC address on the router. from there i was able to used the ping and completely 100%.

Lab 2.1.2.3 build the chapter topology

in this lab i was able to build a topology from scratch which was good practice on how to do everything. as a result, i was able to understand what to connect to what in terms of the copper cable an ethernet. however i was told to connect ports that were told to me by the steps. so i didn't really have to use the ports they gave me, but to understand what they were trying to tell me. i was also able to configure the routers through the table they gave me in order for the network to successfully work and turn on the ports status. i was able to learn what specific wiring that had to be used in order for the 1841  routers to work correctly. most of the ports that i used were pretty easy to figure out once you got the first one up and running since they all followed a logical pattern.

Packet Tracer 1.4.2.2 Determining the best using routing tables.

In this lab it had started with already 100% complete. All that it gave were some questions from me to answer. from those question i was given all the answers just by exploring the network that included looking for the routing protocol, best metric, and the best path which would be FastEthernet0/0 since it was the only one configured, henceforth the best path. i feel that i really didn't learn that much from this lab since must of the things i already have done in the previous labs. i probably would have learned more from actually troubleshooting the network problems and finding answers my own way. Since this network was bigger then the others i previously had to work on having to troubleshoot it would have been a lot more worth it then just answering questions.

Packet Tracer 1.3.5.2 Routing Table Principles

in this packet tracer i was able to learn about the routing table and more things about it. i start with a ping from the desktop of PC3 which results in it being in it being unsuccessful. so i troubleshoot this problem further by going into the CLI to configure an address. once i configure i try the ping again only for it to fail because of the request timing out. so i know had to look for another way of fixing the routing issue in R3. so what i did was by viewing the ping from PC1 to PC3 in simulation mode i could see the problem from a different perspective. so i filter the traffic so that only the ICMP packets is shown. i then add a simple PDU and click on PC1. this will recognize PC1 as the source of traffic, and then press PC3 as the destination host. this completely trouble shoots the problem that was associated with the ping and traveling of the packet.

Lab 1.3.4.2 Dynamic Routing

in this lab it focused on static rouing. the difference between Static and Dynamic is that in static routing you would have to entering the addresses manually in the routing table through the CLI. In Dynamic routing is a change that happens automatically in the network topology as if it adapts. in this lab i went to the CLI in order to configure the the router by using a new command router RIP. after i configure RIP in router R2, R3, R4 i would then analyze the routing table on each of the routers. as i press R1 to show ip route i notice that router shows directly connected routes along with static and dynamic routes. from there i would move to ping from R3 to PC1 only for it to be successful. all in all i then configure a static route in R2 since a static route doesn't adapt to changes in the network like a dynamic route. fom ther i ping once again but instead with R3 to PC1 and reach 100% completion.

Packet Tracer 1.3.3 Static Routing

In this packet tracer lab what i was able to learn about static routing. First i was told to enter the CLI  for R3 and configure terminal in order to add the static route. i enabled the router and added the command ip route 192.168.1.0 255.255.255.0 192.168.3.1. with this i was able to see the addresses with the show ip route  command. AFter that i would then have to ping R1 to reach R#. For task 2 i would enter a static route on R1 in order to reach R3. to do this i would move on to configuring R1 with similar commands as R3. Although the only difference would obviously be the command ip route 192.168.3.0 255.255.255.0 FastEthernet 0/1. From there i would similarly repeat a similar process on the remaining router to reach R1's LAN. After doing another ping but for R3 to PC1 the ping is successful. After that i reached 100% completion. i was able to learn about static routes and their importance to the network.

Packet Tracer 1.3.2.2 Directly Connected Networks

In this lab i was able to constantly add more from what i done before and improve my troubleshooting skills. in this lab i had to configure to routers R1 and R2. in this lab it shows the importance of having a routing table. without one packets wouldn't know where to go and as result, the packets will never arrive. i had to configure the ports Fa 0/0 and S0/0/0. since i had all the commands needed to do this task it was practically a breeze in entering it in the CLI. From there i was able to get green lights for all of the devices and resulting in completing this lab. After that all i did was use ping to see if the connectivity was functioning properly.

Packet Tracer 1.2.2 Configuring and Verifying R1

From this lab i had to out into action previous commands in order for me to complete the lab. To start if off i had to configure R1 using the CLI instead of the config tab. This was a bit more difficult since everything had to be done manually instead of just entering IP addresses and everything else is done automatically. i started of  with having to enter passwords in order to start configuration on the Serial0/0/0 and Fa0/0 ports. After successfully entering the corresponding addresses with the routing table given to me i was able to get the green light for the switch and router. However for the other side i had to to config the serial port in order for a complete connection to be done. The command that i had to use for the enabling for the secret passwords i used the vty command for this set up. After that i had a complete lab with new skills and tactics for more difficult configurations.

Packet Tracer 1.2.1.2 Connecting and Identifying Devices

In this packet tracer lab some of the things required where to configure the devices in the logical workspace  that included two PCs, 2 Routers and one switch. The first thing that i had to do was connect the corresponding ports of all the devices in the workspace. After that i gave all the devices new names which required little effort. the trickier part was using the "place note" feature to assign the network numbers for the devices. After that all that was left to do was put in the correct addresses for all the devices according to the routing table given. As a result, i was able to apply skills that i learned from previous labs and make everything run much more quickly and successfully.