PT 4.4.1 Packet Tracer: Routing Loops

In this packet tracer we will identify what routing loop does to the network and what functions to take when a routing loop occurs. Routing Loops occur when there is an invalid static route or route in the network, when there is an error in the network the packet is then being constantly messaged through the network until it is eventually terminated. You can verify this using show run and ip route to check what the error is. The error in the route was Serial route 0.0.0.0 0.0.0.0 serial 0/1 had to be configured into the network; as a result of this direct conflict i used config t to enter in the ip route 0.0.0.0 0.0.0.0 0/1. After completing that, i could ping thorugh the network perfectly.

PT 3.4.4.2 Packet tracer: Viewing Routing Table Information -show ip route

Basically in this packet tracer, we are suppose to learn how we use show ip route and what the routing table actually represents in the network. show ip route gives you 2 addresses that show the source and the destination ip; but there is also something that is highlighted in brackets that is also important. For example, have you ever seen this next to the source ip [1/0]? You have! The 2 numbers are the AD (Administrative Distance) and the hop count (Which is the 0). To change the routes from static or directly connected just put in show ip route static/connected.

PT 3.2.5.2 Packet Tracer: Convergence

My Objectives for this Packet Tracer is to...
______________________________________________________________________________________
-View the routing table on a converged network
-Add new LAN to topology
-View debugging output
-Watch the network convergent process
-Putting a new Network in an existing one

What was learned via RIP updates for Router 2? What i learned was that both router 2 and 3 were on the same subnets via 192.168.1.2 Serial 0/0/0

What network was learned via RIP updates for Router3? The network that was learned through Router2 and 3 was that they are in the same LAN network.

Next i add a switch (followed by a host) to router3 so i can have an extra subnet with another host. After that i use ip configuration to enter the new network information for PC2 (Which is the new host for the switch). What was new was i had to use router rip to add the new protocol into the connected network. Next i view the debugging output for the network in all of the networks. Finally, i turn off the debugging and i ping from PC2 to PC0 to see if my new whole network works.

PT 3.2.2.2 Packet Tracer- Characteristics of IGP & EGP Routing Protocol

In this Packet Tracer my objective is to...
-Investigate Autonomous System 1
-Investigate ISP Router (Internet Service Provider)
-Verify Connectivity among devices within AS1
-Verify Connectivity from PC1 to ISP Router
-Create default routes between AS1 routers and the ISP Router
-Create Static Routes on the ISP router to reach the network within AS1
-Verify connectivity from AS1 devices to ISP routers

First step to solving this packet tracer is to investigate AS1 which means autonomous system 1. An autonomous system is a group of routers under the control of an Administrator. The second step, is to investigate the ISP router which is the Internet Service Provider. Then finally Verify the connectivity to see if the newtwork works.

PT 2.2.3.3 Packet Tracer- Configure Ethernet IP on Hosts and Routers

Basically in this packet tracer i had to configure the ethernet ip's and ports so that way the hosts in the LAN network could be able to communicate. The first thing i did, was i entered the IP host gateway, subnet masks, and IP addresses; Simply put. Next i went into the terminal and ip configed it to the routers, the other configuration was from the PC's. After i was finished i checked my work. The whole point of this packet tracer was to enter in the configuration so that the hosts in the LAN network may communicate.

PT 1.5.2.2 Packet Tracer- Basic Router Configuration

In this Packet Tracer i had to cable the whole network, erase and reload the routers, and test to verify. First i obviously cabled the network first, i then configured the network to make a path. Last, i tested using show ip routes to verify my network works.

PT 1.5.1.2 Packet Tracer- Cabling a Network with Routers, Switches, and Hosts

In this packet tracer all i had to do is connect the cables using the correct cables. I will put a list of all the connections for each of the devices.

R1-S1 straight through cable using FastEthernet 0/0 to Fast Ethernet 0/1
Straight through cable through PC1 FastEthernet 0/2 to S1
Crossover cable from R2 to PC2 using FastEthernet 0/0
DCE from Serial 0/0/0 of R1 to DTE Serial 0/0/0 of R2

And the rest is from the router configuration which can be accesss to the IP table in the Packet Tracer.

PT 1.4.3.2 Packet Tracer- Equal Cost Load Balancing

For this lab i had to examine the network because it was already set up. There was no problem with the network when i examined the Equal load Balancing. I examined the network by using the command show ip routes and the simulator.

PT 1.4.2.2 Packet Tracer- Determine Best Path using Routing Tables

In this packet tracer everything was provided to me, all the routers already had an IP setup so i didn't need to configure it. The network was using Connected routes, Static Routes, and RIP routes which made the network work altogether. Basically it taught me which route was the quickest to reach the end and the host devices.

PT 1.3.5.2 Packet Tracer- Routing Table Principles

In this packet tracer you learn more about what the routing table is used for and how the routers use this as a principle. My first step was to figure out why PC1 cannot hop to PC3. I pinged PC1 to PC3 and configured the routing table for an easier path, 192.168.4.10. After that, i had to see is my routing configuration was a success by using the command show ip route. As a result, it gave me the path i correctly punched in and i pinged to PC3 (Which then worked).

PT 1.3.4.2 Packet Tracer- Dynamic Routing

So in this packet tracer i will be able to learn and describe how the routing table contains both dynamic routing and static routing. In this routing packet tracer, dynamic routing is basically an easier way for the network to gain a path automatically from other routers and to establish an easier routing path or the best path to take to the end user. In order to attain this procedure you must configure RIP within each of the routers and look at the ip statistics to see if it worked.

PT 1.3.3.2 Packet Tracer- Static Routing

In this Packet Tracer i will be able to how routing tables can use and obtain static routes and be able to explain the routing table when i hit show ip route. First step to this Packet tracer is to configure the table for R3 and add an ip route that is 192.168.3.0; this allows a connection for the subnet to R1. When i command show ip routes it gave me this static route 192.168.1.0/24 [1/0] via 192.168.3.1. When i pinged the router to the address 192.168.1.10 it was not successful because there was no route between R3 and R1. After examining the problem i added the route 192.168.3.0 to R1 so that way i can bridge a connection to R3; after completing what i was suppose to do when i hit show ip route i saw my route was successful. To test out the network i pinged the signal to the R1 subnet and the ping was successful; it had an 80% success rate while making a round trip. Therefore, what i have learned was that static routing in the table allows you to connect and configure the whole network for a complete connection.