Wednesday, May 9, 2012
Activity 7.5.2: RIPv2 Challenge Configuration Lab
In this packet tracer activity, its similar to the previous one. There are three routers, four switches, and five host. My first task was to subnet the address space. By doing this, I started off by looking over the network requirements that is included with the activity directions. Afterwards, I assigned the subnetwork addresses to the topology diagram. I assigned the subnet 192.168.40.0 network to the HQ LAN1. My task was then to Determine the interface addresses. First I must assign the appropriate addresses to the device interfaces. After that, I began to cable the network. I was ready to perform basic router configuration to the devices which was BRANCH, HQ, and ISP routers. I configured the router hostname, Disabled the DNS lookup, Configured an EXEC mode password, configured a banner, configured a password of console connections, and configured a password for telnet. I then configured and activated serial and fast ethernet addresses., per each router. I then configured the ethernet interface of PC1, PC2, PC3, PC4, and PC5, along with their IP addresses. I then verified the connectivity to next-hop device. Afterwards, I configured RIPv2 routing on the branch router. HQ router, then static routing on the ISP router. Finally, I verified the configurations.
Monday, May 7, 2012
Packet Tracer Exploration: RIPv2 Basic Configuration Lab 7.5.1.2
This Packet tracer's network topology consists of three routers, four switches, and for hosts. First I cabled the network according to the chart and existing devices. For each router, I loaded the required scripts. I then examined the current status of the network by issuing the "show ip interface brief' command. I checked the connectivity between R2 and the hosts on the R1 and R3 lans. Afterwards, I checked the connectivity between the PCs by sending out several ping commands from one host to another. I then configured RIPv2 on each router. by issuing the command "router rip"then "version 2" right after that. I then verified that RIPv2 is running on the routers by using show ip protocol and show run. I then examined the automatic summarization of routes with the debug ip rip. Then, i disabled automatic summarization by using "router rip" command and "no auto-summary" right afterwards. I did that for each router. I examined the routing table again, and also checked the connectivity between the PC's again. After that, My completion rate from the Packet tracer activity was 100%. I learned how to cable a network according to the topology diagram, how to load scripts, examine routing updates with debug ip rip, disable automatic summarization, examine routing tables, verifying network connectivity, and how to document RIPv2 configuration
Packet Tracer Exploration: Routing Table Corruption 7.4.3.2
This network topology consists of 5 routers. One router at the very top named R2, which is connected to a serial leading to another router named R1. R2 also connects to another router (R3) via crossover cable. R3 and R1 are also connected by a crossover cable. R1 is connected to another router named ISP. There is one other router named R4 that is not connected to anything. First I turned up the interfaces by issuing the no shutdown command in each interface. I examined the routing table on R1. Afterwards, I configured router rip for each router. with the network 172.16.0.0. I then began to configure static routing from the ISP router using the commands:
ip route 172.16.1.0 255.255.255.255.0 s0/0/0
ip route 172.16.2.0 255.255.255.255.0 s0/0/0
ip route 172.16.3.0 255.255.255.255.0 s0/0/0
ip route 172.16.5.0 255.255.255.255.0 s0/0/0
I then connected the Fa0/0 interface on R4 directly to the fa1/0 interface of R3.
Afterwards, I checked the routing table on R4, and everything looked fine and up and running.
ip route 172.16.1.0 255.255.255.255.0 s0/0/0
ip route 172.16.2.0 255.255.255.255.0 s0/0/0
ip route 172.16.3.0 255.255.255.255.0 s0/0/0
ip route 172.16.5.0 255.255.255.255.0 s0/0/0
I then connected the Fa0/0 interface on R4 directly to the fa1/0 interface of R3.
Afterwards, I checked the routing table on R4, and everything looked fine and up and running.
Packet Tracer Exploration: Configure RIPv2 7.2.4.2
This packet tracer exploration activity also had the same network topology as the previous chapter 7. First I was required to upgrade the network to RIPv2. I examined the operation of RIPv2 from the CLI tab by issuing "Show ip protocols". I noticed the version of the RIP updates being sent and received. I then issued the "show ip route" command. There were missing routes on R1 and R3 plus the multiple paths to 172.30.0.0/16 on R2. I was ready to configure the routers for RIPv2 In each router i issued router rip, then I entered the command "version 2". Then I used the command "clear ip route" in order to force the routers to rebuild their routing tables so they can converge. I proceeded to examine the operation of RIPv2 with automatic summarization by using the command debug ip rip. I then disabled the automatic summarization by using the command no-auto summary. Finally, I examined RIPv2 updates in simulation mode, so i can examine the PDU information at layer 3, 4, and 7 to observe the exchange process.
Friday, May 4, 2012
Packet Tracer Exploration: Verify Non-Convergence Using Commands 7.1.5.2
In this packet tracer consists of the same network topology setup as the previous network. I did not have to do any configuring, however, we needed to perform several tasks in order to ensure the reliability of the network. First I verified and tested the connectivity. I verified the link status by issuing the command show ip interface brief. Afterwards, I used ping commands from router 2. I used the command "Ping 172.30.1.1, and it was partially successful. Then I pinged 172.30.100.1, and it was also partially successful. Once I was finished with that, I went over to router 1 and accessed the CLI tab. I then pinged devices from there also. I issued the "Ping 10.1.0.1" and "Ping 172.30.100.1" however, Ping 172.30.100.1 was a failed ping, which meant that the connection to that device was not good. I also issued ping commands from router 3 also. I then examined the routing table on each router by accessing their CLI tab and using the "Show IP route" It turns out that there is no connection to the network 172.30.100.0/24. I was able to examine the updates sent and received on router 2 by issuing the "debug ip rip" command. By doing this, I was able to simulate and trace the pings. I entered simulation mode so I can monitor and trace the destination of packets in order to find out where the problem was. By examining the inbound and outbound PDU details in order for me to understand the content of the RIP updates.
Packet Tracer Exploration: Configuring Discontiguous Routes 7.1.2.3
In this packet tracer exploration activity, I am presented with a network topology that consists of three routers. R1, R2, and R3. There are two switches connected to R1 which are named R1 LAN0 and R1 LAN1. One switch is connected to R2 called R2 LAN. One switch is also connected to R3 which is named R3 LAN. It asked me to make basic RIP configurations, which it involved the "router rip" command. Then I put in all the networks necessary by using the "Network [ip address]" command. Afterwards, i issued the commands "passive-interface [interface]" command so that it can suppress sending updates out those interfaces. I then saved by issuing the copy run start command. I repeated this process throughout the rest of the routers in order to finish the rest of the packet tracer activity. I reviewed on how to do basic configuration for RIP throughout the network
Wednesday, April 4, 2012
LAB2_JeromeCardenas_CCNA
A network topology was presented on the white board, which we were required to build in packet tracer. This is the fully functional topology on packet tracer
We were then required to configure a password for each mode, in each router, in order to keep them secure, and safe from being breached.
We also needed to set up a banner, which also serves as protection for router.
This is the show run command for each router.
ACME ROUTER:
This is the show run for Warner B
It is clear that the banners are set up and passwords that i've configured are encrypted for each router.
In order to make this network in packet tracer, we were also required to insert the correct modules in each router, in order to make the network functional, and cheap as possible.
The following pictures are the physical tab of each router.
WARNER B:
ACME:
In each router, there is only one WIC-2T, because other modules were not necessary. In the open slots, I put covers, to help prevent the router from potentially getting damaged or slowed down due to dust particles.
Wednesday, March 28, 2012
LAB1 Jerome Cardenas CCNA2
In this lab, we were required to set up a topology in packet tracer, that was presented on the board. The topology consisted of three routers, four switches, and twelve hosts in total. We first needed to get all the devices that we needed. We were told to use 2811 routers and 2950 switches. The hosts I used were all desktops. Afterwards, I put in all the necessary modules in the routers in order to set it up as its supposed to. I used four WIC-2T in order to have plenty of serial ports. I also put one NM-ESW-161 which provides us with 16 switching ports in each router. Here is a screenshot of the fully functional network.
I also configured each router in order to have the correct path to send packets. For each interface, I used the CLI in order to configure the correct path of the packets. For example, for the branch router, I used the commands:
enable
config t
int s0/0/0
ip address 1.1.1.1 255.255.255.252
no shutdown
exit
This was used in order to configure the interface s0/0/0 which leads to s0/0/1.
Here is the screen shot for each router's port view.
As you can see, in the screen shots, I configured each interface that was connected to each router. I configured each fast ethernet and serial that connected to branch and remote. However for HQ, I just needed to configure Serial interfaces, because there was no other interface that was connected to it. For HQ, I also set the clock rate to 64000.
The following is the routing table for each router:
HQ#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Branch#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.1.0/24 is directly connected, FastEthernet0/0
C 192.168.2.0/24 is directly connected, FastEthernet0/1
remote#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.3.0/24 is directly connected, FastEthernet0/0
C 192.168.4.0/24 is directly connected, FastEthernet0/1
Thursday, March 22, 2012
Packet Tracer Exploration: Ch4 - Packet tracer Skills Integration Challenge
This activity focused on subnetting skills, basic device configuration, and static routing. In this lab I learned how to design and document an addressing scheme thats based on the requirements. I learned how to pick out appropriate equipment, then cabled the devices. I Configured the static and default routing. I then learned how to verify full connectivity between all devices in the topology. First I designed an addressing scheme. First I placed four 2621XM in the network topology. I then connected all of the routers to 2621XM. I then renamed each router and it's hostname: [B1; B2; B3; B4]. I then connected switches to each router. Each router has 4 switches. I configured each switch to the subnet. I then configured all the routers to R1. I then tested the end-to-end connectivity. I used the ping command to do this. Each router pinged all other router interfaces and the web server. I used extended pings to test LAN connectivity to the web server. I then used verification commands to make sure that my configurations are complete.
Packet Tracer Exploration: Routing Loops
First of all, in this lab, all the routers have already been configured. All I am left to do is to identify the conditions leading to a routing loop and the implications on the router performance. I first examined branch1's configuration using the show run command. Then I located the static route command which is ip route 0.0.0.0 0.0.0.0 serial 0/. I did the same thing to examine branch2's configuration except to locate the static route command, i used the command ip route 0.0.0.0 0.0.0 serial 0/0. I tried to verify the connectivity from PC2 to PC0 using the ping command. The ping command was not successful and the packets failed to reach the destination. I reconfigured the routes by first clearing the current static route configuration. I did this by using the no ip route command. on both branch1 and branch2. I then re-configured the routers so that they can properly connect to each other. I then verified their connectivity again by using the ping command from PC2 to PC0, and it turns out my configuration was successful.
Thursday, March 15, 2012
Packet Tracer Exploration: Ch3 - Packet Tracer Skills Integration Challenge
This packet tracer is an overview of the entire chapter and previous packet tracers that I had completed in the past. First I designed an addressing scheme, then documented it. I then needed to select equipment and cable devices that were necessary for the network. I then connected the network together. Afterwards, I was able to apply basic configuration to each device in the network. After that, then I configured static and default routing. Once that was done, I was able to test the connectivity of the devices to make sure that each device was configured properly. I used commands such as ping. Oi then examined the configuration to make sure my configurations are complete.
Packet Tracer Exploration: Subnetting Scenario 3
In this lab, i was given the network address 192.168.1.0/24 to subnet and provide the IP addressing for then network shown in the topology diagram. First I examined the Network Requirements. I then Designed an IP addressing scheme by subnetting the 192.168.1.0/24 network into the appropriate number of subnets. In this packet tracer activity, I was able to determine the number of subnets that are needed. I then determined the number of hosts needed, and learned how to design the number of hosts needed. I then learned how to conduct research to find a solution
Packet Tracer Exploration: Subnetting Scenario 2
First I examined the network requirements. I then Designed an IP addressing scheme by subnetting the 172.16.0.0 network into the appropriate number of subnets. I needed to allow for the maximum number of hosts which was required for the largest subnet. I assigned the subnets to the network from the topology diagram. I assigned IP addresses to the Network Devices. First I assigned am address to the HQ router, then an address to the west router. I then assigned addresses to the East router, then addresses to the Branch1 router. Then I assigned addresses to the Branch 2 router, then assigned addresses to the Branch 3 router. I then assigned addresses to the Branch 4 router. Then I assigned addresses to the host PCs/ In the final task, I tested the Network Design. by applying my addressing scheme to the packet tracer file. I then Checked to see that all devices connected networks can ping each other and they were successful. In this packet tracer activity, I learned how to determine the number of subnets needed. I then determined the number of hosts needed. I then designed an appropriate addressing cheme. I then learned how to assign addresses and subnet mask pairs to device interfaces and hosts. I then examined the use of the available network address space. I then determined how static routing could be applied to the network.
Packet Tracer Exploration Subnetting Scenario 1
First I examined the network requirements. I then designed the IP addressing scheme by first subnetting the 192.168.9.9 network into the appropriate number of subnets. I then Assigned the subnets to the network shown in the Topology Diagram. In the third task, I assigned the IP address to the Network Devices, by first assign addresses to the HQ router. I then Assigned addresses to the BRANCH1 router also to the BRANCH2 router. I then assigned addresses to the host PCs. Lastly, i tested the Network Design. In this Packet Tracer activity, i determined the number of subnets needed. I determined the number of hosts needed. I designed an appropriate addressing scheme. I also assigned addresses and subnet mask pairs to device interfaces and hosts. I then Examined the use of the available network address space. I lastly, learned how to determine how static routing could be applied to the network.
Packet Tracer Exploration: Viewing Routing Table Information
In this packet tracer activity, I used the show ip route command so i can see details of routing table entries. All i needed to do was show the contents of the routing tables, since all routers have been configured. I used a version of the show ip command so I can see the details of routing table entries. In this packet tracer activity, I was able to review how to read and identify various things in the routing tables.
Packet Tracer Exploration: Convergence
In this packet tracer, I viewed the routing table of a converged network. I added a new Local area network to the topology. I learned how to view the debugging output. I finally watched the process of the network converging. First, I viewed the routing table for Routing table for Router2 and router 3. I then Documented the networks i learned from RIP. I then added a new LAN to the network topology by first adding a new 2960 switch and host to Router3. I Cabled the Switch from Fa0/1 interface to Router3's Fa0/1 interface. I then cabled the host to the fa0/2 interface on the switch.I then configured the appropriate IP addresses from the 12.0.0.0/8 addressing scheme for this LAN. I then Enabled the Fa0/1 interface on Router 3. I then Determined if the network has converged. I then turned on debugging on both routers. Afterwards, I was required to advertise the newly added network. THen I turned debugging off on router 2. I checked to see if the network has converged. In this lab, i learned how network converging works and how to actually set it up like that
Wednesday, March 14, 2012
Packet Tracer Exploration: Characteristics of IGP and EGP Routing Protocols
In this activity, i configured the default route from AS2 and AS3 (two different companies to the ISP (AS1) to simulate the Exterior Gateway Routing that would take place from both companies to the ISP. I then configured a static route from the ISP to AS2 and AS3 to simulate the exterior gateway routing that would take place from the ISP to its 2 customers AS2 and AS3. I looked at the routing table before and after both static routes and default routes were added so that i can observe how the routing table has changed. I verified the connections of each routers by checking to see if ping tests works. they did, and this packet tracer was successful.
Friday, March 9, 2012
Packet Tracer Exploration: Configure Ethernet Interfaces for IP on Hosts and routers
I used the packet tracer to practice configuring interfaces. Follow the additional instructions provided in the activity to examine the ARP process in simulation mode. First I configured IP information on Ethernet interfaces in a network. I then Configured the IP information on the PCs. I then Configured the IP information on router Ethernet interfaces. I was required to verify proper operation. I also verified the status on the bus routers, then the connectivity between hosts and routers. I went into simulation mode and observed the ARP operation. In this packet tracer activity, I practiced configuring PC's and Router Ethernet Interfaces. I then verified everything I did to make sure they were correct.
Packet Tracer Exploration: Build the Chapter Topology
In this packet tracer, I added all the necessary devices and connect them with the correct cabling. In this packet tracer, I first placed the devices on the topology. I then configured them accordingly. I added all the modules to the routers. I then named the devices in order to keep track of them and so that everything can be organized in the network. I then connected the devices. I connected the routers to each other using serial DCE. I also connected the devices to each other using straight through cables. I also used straight through cables in order to connect the LANs properly. In this activity, I learned how to place devices, configure them, rename them, then cable them.
Friday, March 2, 2012
Packet Tracer Exploration: Challenge Router Configuration
In this packet tracer activity, I designed and applied an IP addressing scheme for the topology show in the Topology Diagram. I allocated one class C network that i needed to subnet in order to provide a logical addressing scheme for the network. I cabled the network all together appropriately. Once the network is cabled, I configured each device with its appropriate basic configuration commands. The routers were then ready for interface address configuration according to the IP addressing scheme. When the configuration is complete, I used IOS commands to verify that the network is working properly. In this activity, I learned to subnet an address with the space it gave me. I was able to assign appropriate addresses to interfaces and document. I reviewed how to cable the network and perform basic configuration tasks on a router. I learned to configure and activate serial and FastEthernet interfaces. I then tested and verified all my configurations.
Packet Tracer Exploration: Basic Router Configuration
In this packet tracer, we were doing some basic router configuration. First I cabled the network. I connected each cable to its appropriate device. I then erased and reloaded the routers by: First I established a terminal session to router R1. I entered privileged EXEC mode. In order to clear the configuration, I issued the erase startup-config command. Once the prompt returned, I issued the reload commands. I repeated these steps on router 2 to remove the startup configurations, that could still be there. After I did all of that, I was able to apply basic configuration for router 1. It included disabling the DNS lookup with the no ip domain-lookup command. I then configured the passwords for EXEC, console password, and the virtual terminal lines. I configured the FastEthernet0/0 interface with the IP: 192.168.1.1/24. I then also configured the serial interface for the router. I then did the same thing to router 2. After doing all that, I tested the connectivity between Router R1 and R2. by ping commands. In this activity, I reviewed how to cable a network according to the topology diagram. I learned how to erase the startup configuration and reload a router to the default state. I then learned how to perform basic configuration tasks on a router. I was able to configure and activate Ethernet interfaces. THen Tested and verified configurations.
Thursday, March 1, 2012
Packet Tracer Exploration: Cabling a Network with Routers, Switches, and Hosts
In this Packet Tracer lab, I reviewed the previously learned skills, including basic IOS command line interface operation and configuration commands. I also learned to save configuration files to a text files and to a TFTP server. Essentially, this is an overview of all the past labs combined, in order to help us prepare for the future labs. First I Cabled the Ethernet Links of the Network. I connected the R1 Router to the S1 Swith. I then connected PC1 to the S1 Switch. I then COnnected PC2 to the R2 Router. Afterwards, I cabled the Serial link between the R1 and R2 Routers. I established a console connection to the R1 Router. I then needed to Erase and Reload the Routers. I applied Basic configuration of router R1, most of them by using the CLI tab. I then applied Basic Configuration of Router R2. I configured the IP addressing on the Host PCs. I made the router show commands like show running-config, then show startup-config, then show interfaces, then show version. I Used ping command to test the connectivity between the R1 Router and PC1. I then used Traceroute command at the R1 privileged EXEC prompt so that i can see the path in which the packet will take from T1 router to Pc1. I then create a start.txt File. Then I loaded that file into the R1 router. In this lab, i reviewed the previous learned skills. I learned the basic IOS command line interface operation. I then Learned Basic router configuration. I also learned how to verify and test configurations, and the management of configuration files.
Packet Tracer Exploration: Equal Cost Load Balancing
In this packet tracer, all devices on the network and included and are already configured. I examined the equal cost load balancing. First I Viewed routing table information for R1. To do that , i accessed the CLI tab in order to see the routing table. I used the "show ip route". I saw an entry of the available routes from PC 1 to PC 2 by going through R1. I went into Simulation mode to examine the packets. I pressed auto capture/play button so I can see how the packets travel throughout this network, more specifically, through this routing table. With this, I was able to examine the equal cost load balancing.
Packet Tracer Exploration: Determine Best Path Using Routing Tables
In this Packet Tracer activity, I determined the best path using the routing tables. First I viewed the routing table information for R2. To that, I Accessed the CLI tab from R2. I typed in the command show ip route, so that i can view the routing table. I then proceeded to examine the routing table information for R2. With this routing table, I found out which was the best path in which the packets would be sent.
Packet Tracer Exploration: Routing Table Principles
In this packet tracer activity, I investigated a fully-converged network with connected, static, and dynamic routing. Packets are forwarded through the network on a hop-by-hop basis. I also learned that each router makes an independent forwarding decision based upon the router's knowledge of destination paths. I found out that a router makes decisions based on the information in the routing table. The fact that one router has a complete routing table does not mean other routers have the same information. Routing information about a path from one network to another does not provide routing information about the reverse or return path.
Packet Tracer Exploration: Dynamic Routing
In this Packet Tracer Activity, i learned how the IOS installs and removes dynamic routes. First I configured the RIP on R2. I then configured RIP on R3. I then Configured RIP on R4. I then needed to verify the static and dynamic routes. First i Verified the routing tables on each router. I then examined the routing table on R1. I then Pinged from R3 to PC1. I entered a static route on R2 to reach R1's LAN. I configured a static route on R2, then I examined the routing table on R2. I Pinged R3 to PC1. In this activity, i learned that networks can use both dynamic and static routes, by seeing how they work together, and how to configure them.
Packet Tracer Exploration: Static Routing
In this packet tracer, i learned how the IOS installs and removes static routes. First I configured the static route on R3 using the CLI tab. I typed in the passwords and commands in order to access the ip route. However, the routing table shows directly connected routes, but there are no static routes to remote networks in the routing table. I then configured the terminal. I then examined the routing table on R3. Afterwards, I pinged R3 to PC1 in the CLI tab using the command "ping 192.168.1.10" The ping was not successful because there was no route on R1 to reach R3. I put in a static route on R1 to reach R3. I Configured the static route using the CLI tab. I examined the routing table on R1 from the CLI. I then Pinged from Router 3 to PC1. This activity helped me learn about how static routing worked, and how we can use The routing table to our advantage in networking.
Wednesday, February 29, 2012
Packet Tracer Exploration: Directly Connected Routes
In this packet tracer, we were enabling the Interfaces on each router using the CLI tab, because the Config tab is locked. We then verified the connectivity using ping. I learned the function of the routing table. It is to know the path in which the packets will be sent. I also learned how a router manages directly connected routes in the router table.
Packet Tracer Exploration: Configure and Verify R1
First I configured the router R1 hostname to R1. I then Configure The IP address for interface Ethernet0/0. I then Configured the passwords. Afterwards, i Configured the login banner. Once I was done with all that, I saved the configuration to finally implement the new settings to the router. A lot of these configuration and setting changes were made using CLI. I learned to use the show commands in order to verify the configuration.
Packet Tracer Exploration: Connecting and Identifying Devices
In this Packet tracer, I first connected the appropriate cables to each device. I then renamed each device. Afterwards, I placed the network addresses between all connections. The purpose of this packet tracer lab was to practice connecting cables from one device to another. I also learned how to rename each device, to suit its needs. I then learned how to use the place note feature in order to better organize the network on the packet tracer.
Packet Tracer Exploration: Using Packet Tracer Device Labs
In this lab, first I added a router to the network. I then put a serial module on the router. I then put the appropriate cables to connect the router to the network. We then configured the router, so that it can connect with the switch 1, and the Router 3. We then used CLI is to configure the device settings in order to set the passwords. Essentially, We learned about the three tabs in the router. The Physical tab, the Config tab, and the CLI tab. I was doing basic activities that involved all these tabs.
Packet Tracer Exploration: Cabling Devices
In the Packet tracer Cabling Devices, I was to connect one device to another. I connected PC1 to Hub1. I connected Router 1 to Switch 1. I connected Switch 1 to Router 2. I connected Router 2 to Router 3. Then I connected Router 3 to PC 3. I were practicing to connect them, using the appropriate cables and ports. Once I connected all the devices appropriately with their ports, then I my completion for this lab is 100%.
Tuesday, February 28, 2012
Packet Tracer Exploration: Using Setup Mode
In this packet tracer, First we cleared any existing configuration from Router 2. We used commands in order to clear the existing configuration. I restarted the router to "initialize" the erase. I then configured the router using setup mode. I needed to configure the router from scratch by setting up the passwords, the interface, the IP address, and the default subnet mask. I examined the results of using the setup. Then everything was fine.
Packet Tracer Exploration: Corporate Network Simulation
In this packet tracer, we observed how packets travel in a network with a lot of traffic. In the network, there were several routers, hosts, and switches. We went to simulation mode, then observed as the packets traveled to each end device.
Friday, February 10, 2012
Routers and computers packet tracer labs
In the first lab, we monitored the complex network of routers in simulation mode. with this, we were able to monitor and observe the traffic traveling throughout the network. We were able to see how the packets travel even with all the traffic occurring at the same time. In the second lab, we were configuring routers and other end devices. First we physically connected all devices using the appropriate cabe types. We then named all the devices so our work can be more organized. We then learned about how to use the place note feature to add network addresses between all connections
Tuesday, January 17, 2012
Carlos Dominguez Essay
Carlos Dominguez is the senior vice president, office of the chairman, and CEO of Cisco. On Thursday, January 12, 2012, Carlos Dominguez hosted a web seminar addressing several forms of technology that involved networking. He included the future of networking, and how we can put it to our advantage. In order for us to do this, it is required for us networkers to contribute our own play into the situation.
According to Carlos Dominguez, everyone who is obligated to networking can make a change or impact in our future society and generation. Each one of us is required to focus on staying relevant, and try to succeed. In order to make positive changes, we are to take initiative on the challenges, problems, and goals that we encounter in our careers. By doing this, technology and the right culture can create successful companies by making advances in our technology.
He also pointed out several inspirational things that encourages us to be triumphant in our future or current careers. One of them is to follow your dream. What this means is to for you to stay dedicated to what you want to do in life, and never give up. Another is making a change in people. You can do this by inspiring others to do what they have always wanted to as a career. Last but not least, he tells you to do what you think is best. This is helpful, not only to make you successful in life, but it will give you a better chance to be better as a person.
This web seminar prepares me for the real work force because it was very inspirational and motivates me to develop or work on future technology. The fact that impacted me the most about this web seminar is how we are now in an era where technology evolves at a very rapid pace. I agree with Carlos Dominguez because technology has almost every possible capability. The future generation is responsible for enhancing the significant aspects of our evolution, which is the technologic era.
I may be able to follow the footsteps of Carlos Dominguez, if I train myself to. However, I would much rather prefer creating my own footsteps for others to follow, and for other people to be inspired by me. This seminar motivated me to prolong my education in all subjects, but most specifically programming and networking.
Friday, January 13, 2012
Chapter 8 Case Study
a. What is this kind of Interference?
This kind of Interference is a physical interference
b. Explain why it can slow down the traffic.
If loud, consistant, noise is constantly hauling at exposed, uncovered cables, sound waves may be able to disrupt or slow down signals traveling down from the cables. This is the reason why the traffic is slowed down.
c. Would the result of the tests be any different if the network cabling was running next to a just installed small alarm clock instead of an A/C unit? Why?
The results in this experiment, would be different. Alarm clocks stop at a certain point and is not as consistent or loud. Also, the cables must be exposed. In order to have similar results, the direct source of the alarm clock must be directly on the exposed wires.
This kind of Interference is a physical interference
b. Explain why it can slow down the traffic.
If loud, consistant, noise is constantly hauling at exposed, uncovered cables, sound waves may be able to disrupt or slow down signals traveling down from the cables. This is the reason why the traffic is slowed down.
c. Would the result of the tests be any different if the network cabling was running next to a just installed small alarm clock instead of an A/C unit? Why?
The results in this experiment, would be different. Alarm clocks stop at a certain point and is not as consistent or loud. Also, the cables must be exposed. In order to have similar results, the direct source of the alarm clock must be directly on the exposed wires.
Subscribe to:
Posts (Atom)










