Wednesday, February 29, 2012

PT 1.3.2.2 Packet Tracer- Directly Conncted Routes

In this packet tracer i will be able to describe the function of the routing table and how the router manages directly connected routes in the routing table. My first step is by enabling the Fast Ethernet interface in R1 by using CLI and using the command interface Fastethernet 0/0 and no shutdown. After i did all of that i check the ip routes for a second time and it gave me the response 192.168.1.0/24 is directly connected, Fastethernet 0/0. After seeing the ip route i did the same thing for R2 except the ip this one is routing towards is 192.168.3.0/24 is directly connected, Fastethernet 0/0. The reason why i only had 1 route in the table for each router was because there was only 1 path for the network to hop towards, there was only 1 cable connecting towards a router so therefore it can only take 1 route. The other IP addresses can ping towards each other because i allowed the interface to go or hop towards the next router so it may then choose a path to go to the other PC.

PT 1.2.2.4 Packet Tracer- Configure and Verify R1

In this packet tracer, all of the devices were connected properly and i just had to configure R1 which was the host router. After i configure the router i needed to check the statistics to see if what i have configure has been implemented into the router. I needed to also put in the IP addresses into the router that was given to me on the table, however in this packet tracer i learned a new command code, which was log in banner so that unauthorized access is prohibited. When i was finished i saved it to the NVRAM which sends a copy of the messages to the other devices.

PT 1.2.1.2 Packet Tracer- Connecting and identifying Devices

In this lab my assignment was to connect all of the devices and identifying which cables and ports i am suppose to connect them to. This was simply easy, then i had to change all of the device names to something that can be easily recognizable. Finally i had to set the clock rate to the one given to us and plug in all f the IP Addresses in the chart.

PT 1.1.5.4 Packet Tracer- Using Packet Tracer Device Tabs

This is the outline of today's Packet Tracer
Place and connect the router.
• Place the router in the topology.
• Add a module.
• Connect the router to the neighboring devices.
• Perform the basic configuration.
• Change the router names.
• Configure interfaces.
• Complete the configuration.
• Add passwords.
• Verify the configuration.

This was my first time making a fully stable network from scrap. All i am given in this situation was routers and switches and end devices. I had to know what cables i needed to connect to different ports, i needed to give them ip addresses, i needed to configure the router, and i need to put names for each device. First thing i did in this Packet Tracer was i connected each device together and added a router and enabling it. Then i managed my configuration by setting up new passwords and testing out my network statistics. Then i tested the network to see if it works by using Check Results and simulation; the Test was success.

PT 1.1.5.3 Packet Tracer- Cabling Devices

This was probably the most simple packet tracer of them all. It mostly deals with the physical layer of the OSI model because all you have to do it connect all of the devices to both routers. I first connected the PC to the hub, then to the router, from the router to the switch; then the switch to the other 2 routers and end devices.

PT 1.1.4.3= Packet Tracer Using Setup Mode

Basically, my assignment was to configure my router and setting up passwords for it. I also learned some new codes while configuring the routers such as enable, enable secret, erase startup-config, show running-config, and check results. All of these codes will help benefit me to configure future routers to give myself access to the router with security. Although the passwords for the routers were quite simple, in the real job i would have to make them more complex and difficult because hackers can easily trace down or decode the passwords information if the password is too small or doesn't use a variety of different symbols.

PT# 1.1.1.5= Packet Tracer: Corporate Simulation

In This Packet Tracer All connections seemed to be working correctly. The packets were being sent fluently through the network without a problem. All the routers, servers, connections, switches, sub-nets.etc. What i first did to diagnose the network was doing the packet simulation. The Host computer was sending out a frame that tested the whole network which presented in a fully functional LAN