Thursday, March 29, 2012

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.

Thursday, March 22, 2012

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.

Tuesday, March 20, 2012

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.

Thursday, March 15, 2012

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.

Wednesday, March 14, 2012

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.

Friday, March 9, 2012

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.

Packet Tracer Labs 2.1.3

In this Packet Tracer we build a topology that will act as a foundation for the rest of the chapter. We add the necessary devices and configurations. For example you must adjust the physical of the routers by plugging the corresponding physical into the correct area. We also determine the media that is appropriate for the scenario but other than that no real modifications were necessary.

Thursday, March 1, 2012

Packet Tracer Lab 1.6.1

This Packet Tracer activity integrates all the knowledge and skills you have acquired in the previous sections. In this activity, you cultivate a network from the ground up. Starting with an addressing space and network requirements, you must implement a network design that satisfies the specifications. The objectives are to design and document a routing scheme according to the lab requirements. This includes selecting the appropriate equipment and and cable devices. Apply a basic configuration to the devices and as a result verify full connectivity between all the devices. In order to complete this verification you must identify layer 2 as well as layer 3 addresses used to switch packets. To elaborate you must create a simple PDU ping packet. Afterwords enter simulation mode and use the add simple pdu button to create a ping from PC1 to PC3. Lastly change edit filters so that only IMCP is simulated. As a result B2 will switch the ping packet to PC3.

Packet Tracer Lab 1.5.3

In this lab we are urged to challenge the router configuration. In order to due this you must have adept subnetting as well as configuration skills. Given an address space and network requirements, you are expected to design and implement an addressing scheme in a two-router topology. A deep examination of the routing tables, port status, as well as physical portion of the routers is stressed through this activity. Due to its complexity I was not able to complete it to its full potential. However with several different configurations you are able to have a plurality of path determination.

Packet Tracer 1.5.2

This packet tracer revolves around basic router configuration. It reviews skills such as device cabling as well as establishing a console connection. In addition to these and perhaps most importantly you practice the command interface or CLI basics. Path determination and switching function details are also stressed, this review is intended to make you adept in all components of routing table protocol. The four steps of packet delivery are essential to the completion of this lab and will result in the possible use of IMCP. To elaborate if no route is determined then Network Layer Internet Protocol will report errors and provide information relevant to the IP Packet processing. On the other hand if the destination IP address of the packet belongs to a remote network, then the packet is forwarded to another router. Remote networks can only be reached by forwarding packets to another router.

Pakcet Tracer Lab 1.4.3

This packet tracer activity involves equal cost load balancing. We examine a routing table in this lab and use the principles of equal cost load balancing to adjust it accordingly. Cost refers to the hop count, metric, and bandwidth. This value is used to determine the most favorable path to a particular destination. On the other hand load balancing, is translated into the capability of a router to distribute traffic over its network ports that are the same distance from the destination address. To have a successful load balancing outline, you must depend on both reliable speed as well as information. By having a good load balance scheme, as a reaction will impact your use of network segments resulting in an increase in network efficiency and bandwidth.

Packet Tracer 1.4.2

In this packet tracer we explore and determine how to locate the best and most productive path using routing tables. In addition to this we also explore the metric function. Each path must first be evaluated to determine which will be the best for the particular router at hand. Then hop count as well as metric must be compared among the paths. Speed is technically not an accurate description of bandwidth because all bits travel at the same speed over the same physical medium. Bandwidth is more accurately defined as the number of bits that can be transmitted over a link per second. Dynamic routing protocols typically use their own rules and metrics to build and update routing tables.

Packet Tracer Lab 1.3.5

In this Packet Tracer we embark on the exploration of the routing table principles. We venture in order to investigate a fully converged network connected, with static and dynamic routing. Every router will make its decisions based on the information provided in its particular configuration, therefore the fact that one router has information in its routing table does not mean the others in the same network will have that same identical information automatically. Routing information about a path from one network to another does not provide routing information about the reverse, or return, path. Due to these principles the network can run on a function known as asymmetric routing. This term depicts a path from network 1 to network 2 differing from a path from network 2 to network 1. To elaborate the going and returning paths are each unique.

Packet Tracer 1.3.4

This packet tracer revolved around dynamic routing. To elaborate how the IOS installs and removes dynamic routes. Remote networks can also be added to the routing table by using a dynamic routing protocol. Dynamic routing protocols are used by routers to share information about the reachability and status of remote networks. Dynamic routing protocols perform several activities, including network discovery as well as updating and maintaining routing tables. Network discovery is the ability of a routing protocol to share information about the networks that it knows about with other routers that are also using the same routing protocol. Once this process is done, the dynamic routing protocol will update and maintain networks within the routing tables capabilities.