Packet Tracer 7.4.3.2 Routing Table Corruption

In this packet tracer i was able to get a basic idea no how ISP make proper use of static routes in order to get proper communication with proper other devices and vice versa. I stated the lab with all interfaces off and an empty routing table . I quickly configured all the necessary interfaces, resulting in the directly connected routes being added into the routing table. From there i wen t and added the RIP protocol into all the routers with the network 172.16.0.0 command. All the routers would be inputed with the same address since it is from  from the same subnetted network. from there all that was left to do was just connect R3 to R4 with a copper cross over connection. With this everything would ping successfully.

Packet Tracer 7.2.4.2 Configure RIPv2

In this packet tracer i was able to finally apply RIPv2. It is as you may already know a enhanced version of RIP that carries the subnet masks in its routing updates for routers. However we still need to configure in order to stop it fro sending updates for discontiguous subnets. Since that is its default function i had to use the no auto-summary command in order to stop it from automatically summarizing routes. To start off the lab i first analyze the protocols being used for the router, and notice that RIP is being used. AS a result, i quickly change to RIPv2 for all three routers. After that i would then used the clear ip route *  in order for the router to reconstruct its routing table in order for it to properly implement RIPv2. As soon as that was done all that was left was to stop the current newly placed routing protocol from sending automatic updates to the improper places. A mentioned before i would just use the no auto-summary and    resulting in a properly functioning RIPv2.

PAcket Tracer 7.1.5.2 Verify Non-Convergence Using Commands

In this lab all that needed to be done was to analyze the topology. some of the pings were not successful because of packets being sent the wrong way. This was seen using the show ip route in the routing table of R2 as instructed. There were two equal cost paths for the network 172.30.0/16. As a result, they are sent the wrong way. Another reason why pings from R1 fail is because of a network address that wasn't in R1 which was 172.30.100.0/24. After that i entered simulation mode to seethe where the packets go through. Following that i then went into the Event List filters in order to change the setting in order to se only the RIP events associated with the topology. What i was able to examine is that updates going to router R3 fail because of the network address that wasn't added to the routing table of R1.

Packet Tracer 7.1.2.3 Configuring Discontiguous Routes

In this packet tracer i was able to configure discontiguous routers using RIPv1. it was pretty straight forward. I went into all three routers and used router rip in order for configuring. For router R1 one thing that needed to be done was to combine to networks into one statement in order to enter it into rip. From there i used the passive-interface command in order to stop any updates from going to the networks that didn't have any routers. The same steps were done for the other two routers. After that all the needed to be done was to save the configurations so that it wouldn't be deleted if the entire topology were to be shutdown. To make sure all of my addresses were added i used the show ip route to see the rip configurations added to the routing table.

Basic Router Config 4/4/12

In this picture you can see the basic topology if the network. Most of the configuring came from ACME and WarnerB. In  total you can see 6PCs, 3 switches, 1 server and 2 routers.

Here you can see the physical port view of the ACME router. There is one WIC-2T inserted in the first port. From there i out covers on everything else in order to not make the mistake in adding unnecessary modules. 

This is the physical port view of the WarnerB router in which much like the first there is only one module which is WIC-2T and the rest have covers on them. After that you would turn the ports on and thats it for the physical view.

this is the show run for the WArner B router and it shows the line vty 0 4 passwords and banner.

This the show run for ACME for banner and passwords

this is the encrypted passwords for the WArner B

THis for ACME encrypted password

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.