Packet Tracer Lab 7.6.1

The Packet Tracer Activity integrates all the knowledge and skills you acquired in previous chapters of the routing curriculum. Skills related to the discussion of RIPv2 are also included. In this activity, you build a network from the ground up. Starting with an addressing space and network requirements, you must implement a network design that satisfies the specifications, then implement an effective RIPv2 routing configuration with integrated default routing. Detailed instructions are provided within the activity. Design and document the addressing scheme according to the procedure, this includes configuring static routes and setting default routes, as well as verifying and troubleshooting all those configurations afterwards.

Packet Tracer Lab 7.5.3

In this packet tracer activity, you begin by loading configuration scripts on each of the routers. These scripts contain errors that will prevent end-to-end communication across the network. After loading the corrupted scripts, troubleshoot each router to determine the configuration errors, and then use the appropriate commands to correct the configurations. When you have corrected all of the configuration errors, all of the hosts on the network should be able to communicate with each other. Once all the connections are verified then you should configure the proper subnet mask as well as ip addresses for all the devices on the network. In addition clock rates must be adjusted as well as making sure that the port status for all device is on.

Packet Tracer Lab 7.5.2

This Packet Tracer Activity is a mirror image of the previous one, just with more complex configurations and a larger emphasis on CLI. In this lab activity, you are given a network address that must be subnetted using VLSM to complete the addressing of the network. A combination of RIP version 2 and static routing will be required so that hosts on networks that are not directly connected will be able to communicate with each other and the Internet. All in all this packet tracer activity requires you to use RIPv2 commands such as ip interface brief, in order to properly configure a network supported by VLSM. For obvious reasons you must use the information provided to you in the procedure although you must also create your own ip addresses and subnet masks in accordance to the rest of the network and the RIPv2 protocol.

Packet Tracer 7.5.1

In the following packet tracer activity we review the basic configurations and functions of RIPv2. Including discontigous networks and using VLSM to subnet it. Since we are configuring a classless routing protocol then commands such as show ip route, debug ip rip, as well as show ip interface brief. It is also encouraged to set the timers, all in all RIPv2 configurations are similar to RIPv1. Although it is classless, basically the strengths of the RIP protocol are enhanced but the flaws remain evident. That means that you will have to work around the 15 and 16 hop count to infinity. Verification as well as troubleshooting should be simple at this point, so pinging should come naturally. The rest of this lab is configuring the network ip's and subnet mask according to the procedure.

Packet Tracer Lab 7.4.3

Routing table corruption is a severe issue that can influence your network, this packet tracer activity will expose and troubleshoot such corruption. To avoid such problems it must be made sure that each router has a default route to the desired destination. It is also advised to take other authentication precautions such as routers accepting routing information only from other routers with the same passwords. This will prevent malicious attacks from outside sources. You must implement a load balance between routers to make sure that the following procedures work without flaw. The rest revolves around tidying up all of the standard security issues such as passwords and secrets. You also must be aware of the timers that are initiated on your routers, most significantly the update timer. Commands that will prove to be of worth include the show cdp neighbor as well as show running config.

Packet Tracer Lab 7.2.4

In this packet tracer activity we venture into the RIPv2 field. Requirements include disabling automatic configurations as well as verifying configurations. RIPv2 is a classless routing protocol this means that it supports VLSM along with CIDR. In networks that use a VLSM addressing scheme, a classless routing protocol is essential to propagate all of the networks along with their correct subnet masks. As a result we will be using such a format for the network at hand. The debug ip rip command will be of assistance in this lab, in order to reverse the previous configurations of RIPv1. Many of the same commands that were used for verifying and troubleshooting RIPv1 can be used for RIPv2 as well. Such commands include show ip route, show ip interface brief, as well as show running config, and then skynet takes over.

Packet Tracer Lab 7.1.5

This Packet Tracer Activity is relevant to verifying non convergence through commands. As you should already know, updates are not sent across classful network boundaries with RIPv1. This Packet Tracer utilizes the ip route, ping, and debug ip rip commands. Two extensions are implemented in order to verify and enable RIPv1, the first is the subnet mask, allowing a 32 bit mask in the rip route entry. As a result, the receiving router no longer depends upon the subnet mask of the inbound interface or the classful mask when determining the subnet mask for a route. The latter allows a router to make better decisions regarding the next hop address. With help from these two extensions your a able to successfully verify the non convergence of the network, of course you still need to access the convergence through the CLI. The commands should never be neglected and are vital to the completion of this assignment.

Packet Tracer Lab 7.1.2

This Packet Tracer Activity revolved around configuring discontigous routes. It also integrate RIPv1 configuration skills. In addition we take into consideration RIPv1 limitations, in order to test the connectivity of the topology. This procedure includes verifying that both Protocol and Status fields are up this can be done through the show ip interface brief command. Since RIP does not support discontigous then we are required to implement auto summarization in the network. This is capable due to the fact that all updates have a cost of 1 hop to reach their neighbor and ultimately the entire network. As a result we are able to successfully configure this three router, four switch topology  through copper media cables. This is thanks to the 1 hop cost summarization that I previously elaborated on.

PacketTracer Activity 4/4/12

In this packet tracer activity we created a network with a server and a static ip addressing along with DHCP. We setup banners and configured the interfaces for all the routers, in addition we setup passwords, secret passwords, login passwords as well as telnet. The topology below shows a network one server, two routers, three switches and among them two are connected to three hosts. Straight through media is used except for the connection between two switches which is crossover as well as the utilization of serial dte for the connection between the two routers.

This is a preview of the network topology the IP addressing scheme is 192.168.1.0 and the subnet mask is 255.255.255.0.

These are the physical ports for the routers. As you see a WIC 2T port is used for one serial port of the Router for both routers.

This is a preview of the banner for the Routers, as you see it prompts you to enter your password to enable further access. The banner serves as a message of the day and is open upon desired entry into the routers configuration. 

Packet Tracer Activity 3/26/12

 This Packet Tracer Activity examined our individual ability to configure a network. This network consists of three routers (2811) and four switches (2950-44) and 3 hosts for each switch. We must configure the physical of each interface as well as the CLI routing and serial interfaces.

This is a preview of the topology

The following is a picture of each of the ports for the three routers and the interface configuration

This lab was a challenge because it tested our individual routing skills as well as examined all the aspects of RIP that we have learned over the course of chapter 5.

Packet Tracer Lab 4.7.1.3

In this Packet Tracer activity, we must build a network from the ground up. Starting with an addressing space and network requirements, an exploration of how to implement a network design that satisfies the specifications is desirable. Afterwards we must also implement an effective static routing configuration. Once we presume we have configured the network, we must test the connectivity in order to wrap up the procedure. The WAN is already configured so all that is needed to be done is to assign subnets, on the other hand for the LAN we must divide the addressing scheme and subnets according to the topology as well as the requirements. Once the addressing scheme is documented we must next configure a basic static and default routing. A password and secret password must be configured as well. Lastly we must perform a ping to ensure that the connectivity is correct, in addition it is also recommended to perform an extended ping to ensure absolute end to end connectivity between each router in the network. Troubleshoot until pings are successful and use verifications commands to not only make sure configurations are correct but also that they are complete.

Packet Tracer lab 4.4.1.2

In this packet tracer lab we examine routing loops, and experience how a routing loop may occur and effect a network. The routing loops will misconfigure the static routes in the network as well as cause degraded network performance. Routing loops eat up bandwidth and also router resources, resulting in a slow or even unresponsive network. Mechanisms that can be used to eliminate routing loops are as follows; holddown timers, split horizon, and triggered updates. Using these loop avoidance mechanisms in addition to the static route command ip route, I was able to complete this packet tracer activity.

Packet Tracer Lab 3.6.1.3

The Packet Tracer Skills Integration Challenge Activity for this chapter is very similar to the activity you completed at the end of Chapter 2. The scenario is slightly different, allowing you to better practice your skills. In this activity, you build a network from the ground up. Starting with an addressing space and network requirements, you must implement a network design that satisfies the specifications. Then you must implement an effective static routing configuration. Of course in addition a strict concern is placed on subnetting, as a result basic device configuration and static routing must be utilized to complete the routing table. Using the split subnetting strategy previously mentioned I was able to successfully configure and document the IP addressing scheme, afterwards I used the exit interface argument to configure the static and default routes. Once I have introduced end to end connectivity among the network, a ping must be performed to ensure optimal performance as well as correct configurations.

Packet Tracer Lab 3.5.4.2

In this Packet Tracer Activity we explore subnetting for the third time in Chapter 3. Although we are also entitled to design an IP addressing scheme in this activity. I took a similar approach to this one, as I did the previous two. I once again utilized the subnetting split strategy in which I split subnet boxes to the point were it will result in sixty four subnets with four addresses each. This of course was done in proportion to the scenarios number of IP addresses as well as the IP addresses themselves. I found that once this strategy is done in accordance to the given IP addressing scheme the end result is precise although the procedure is rigorous and time consuming. In this case once I had examined the network requirements the strategy proved to be insufficient, although the network would still be functional if the strategy was implemented.

Packet Tracer Lab 3.5.3.2

This Packet Tracer Activity resembles the previous one to the extent were your actions are mirrored. We must also assemble a custom routing table and subnet. Unlike the previous one we must instead configure a network on a much larger scale. Another difference is the fact that the IP addresses have been provided for us, this intertwines with the large scale network. The tactic I used was to split each individual square of the Subnet box to the point where the last split will result in sixty four subnets with four addresses each. This of course was done in accordance to the IP addresses given.

Packet Tracer Labs 3.5.2.2

In this Packet Tracer Activity we must implement our addressing scheme in order to complete the subnetting scenario. We investigated how to add a network to a routing table by enabling the RIP. We must configure the entire routing table. Keep in mind that running more than one program on a router is rare. The show ip route command must be utilized once more in order to achieve 100% completion. As a result using information from the show ip route would be an advantageous reference. The subnetting would be less complex if you implement a strategy revolving around classfull or classless subnetting. In this scenario classfull would be more desirable due to the avoidance of superfluous information. To update the routing tables constantly would be a nuisance, since after all you are entitled to create the routing table in the first place.

Packet Tracer Labs 3.4.4.2

In this Packet Tracer Lab we venture into an examination of the show ip route command. In addition we see the details of routing table entries. The output of the show ip route command displays the directly connected networks with no information about the AD (Administrative Distance) value. The output is similar to the output for static routes that point to an exit interface. The only difference is the letter C (directly connected) at the beginning of the entry, which indicates that this is a directly connected network. This command will reveal the distance for the directly connected route or routes.

Packe Tracer Lab 3.2.5.2

In this packet tracer activity we examine the convergence. The network has already been configured with 2 routers, 2 switches and 2 hosts. A new LAN will be added and you will examine the convergence. The convergence is when all router's routing tables are in a state of consistency. Slower convergence refers to RIP and IGRP, on the other hand a fast convergence refers to EIGRP and OSPF, in tis activity a faster convergence is preferable.

Packet Tracer Labs 3.2.2

 In this Packet Tracer we venture into the territory of dynamic routing. The network has already been configured with autonomous systems. We configure a default route from AS2 to AS3 and then to AS1 in order to simulate the Exterior Gateway which would take place from both routers to the ISP. Then a reverse route must be configured from the ISP to AS2 and AS3, note that this new route must be a static route. Observing the routing table is also part of procedure in order to notice and examine the changes from the forward and reverse routes.

Packet Tracer Lab 2.2.3

In this packet tracer we explored how to configure ethernet interfaces for Ip on hosts on hosts and routers. In addition we examine the ARP process in simulation mode. To elaborate ARP or Address Resolution Protocol is used to map an ip address to a MAC address. We used the no ip route command in order to shutdown the router and its previous information to complete the task at hand.