Journal+Entry+-+May+16th+to+May+20th

ACHIEVEMENT CHART: TECHNOLOGICAL EDUCATION

 * || ===Knowledge===

Understanding
|| ===Thinking=== || ===Communication===

Journal
|| ===Application=== ||
 * ===50–59% (Level 1)=== ||  ||   ||   ||   ||
 * ===60–69% (Level 2)=== ||  ||   ||   ||   ||
 * ===70–79% (Level 3)=== || * || * ||  ||   ||
 * ===80–100% (Level 4=== ||  ||   || * || * ||

Knowledge and Understanding – Specific content acquired (software), and the comprehension of its meaning and significance (understanding)
__**Monday:**__ Today we watched a video about a guy talking about what was the previous 5000 days of computers were and what will be the future of computers in the next 5000 days which is also about 13 years. Then I finished my cable and then I worked on my binary counter and almost finished and tommorrow I will finish it.
 * Thinking – The use of critical and creative thinking skills and/or processes**
 * Application - of knowledge and skills (e.g., concepts, processes, use of equipment and technology)**
 * __Monday May 16th 2011:__**

=**__Tueday May 17th 2011:__**= -One of the first ways to gather information is to question the individual who reported the problem as well as any other affected users. Questions can include: end user experiences, observed symptoms, error messages and information about recent configuration changes to devices or applications. -There are several different structured troubleshooting techniques available, including: Top-down Bottom-up Divide-and-conquer -Top-down starts with the application layer and works down. It looks at the problem from the point of view of the user and the application. -Bottom-up starts with the physical layer and works up. The physical layer is concerned with hardware and wire connections. -Divide-and-Conquer typically begins troubleshooting at one of the middle layers and works up or down from there. For example, the troubleshooter may begin at the network layer, by verifying IP configuration information. -Trial and error relies on individual knowledge to determine the most probable cause of a problem. A troubleshooter makes an educated guess on the most likely solution based on past experience and knowledge of the network structure. Once the solution is implemented, if it does not work, the troubleshooter uses this information to help determine the next most likely cause. This process is repeated until the problem is isolated and solved. -With this technique the problem is assumed to be caused by a specific hardware component or a configuration file. The defective part or code is replaced by a known good device or file. While not necessarily locating the problem, this technique can save time and quickly restore network functionality. This relies on the availability of substitute parts, components, and backup configuration files which can be very expensive to maintain.
 * Relevant information I read On Chapter 9:**



-Vision is used to detect problems such as improperly connected or poorly constructed cables, including: cables which are not connected cables connected to the wrong port loose cable connections damaged cables and connectors Use of the wrong type of cable -Some of the available utilities include: ipconfig - Displays IP configuration information ping - Tests connections to other IP hosts tracert - Displays route taken to destination netstat - Displays network connections nslookup - Directly queries the name server for information on a destination domain - When a ping is sent to an IP address, a packet known as an echo request is sent across the network to the IP address specified. If the destination host receives the echo request, it responds with a packet known as an echo reply. If the source receives the echo reply, connectivity is verified. -If neither ping is successful, then network connectivity along the path to the destination is most likely the problem. If this occurs, it is common practice to ping the default gateway. If the ping to the default gateway is successful, the problem is not local. If the ping to the default gateway fails, the problem resides on the local network. -The Tracert utility provides connectivity information about the path a packet takes to reach the destination and about every router (hop) along the way. It also indicates how long a packet takes to get from the source to each hop and back (round trip time). Tracert can help identify where a packet may have been lost or delayed due to bottlenecks or slowdowns in the network. -The nslookup utility allows an end-user to look up information about a particular DNS name in the DNS server. -The easiest way to determine if the problem is with the wired or the wireless network is to: 1. Ping from a wireless client to the default gateway - this verifies if the wireless client is connecting as expected. 2. Ping from a wired client to the default gateway - this verifies if the wired client is connecting as expected. 3. Ping from the wireless client to a wired client - this verifies if the integrated router is functioning as expected. - If the wired client is unable to connect to the integrated router, one of the first things to check is the physical connectivity and cabling. - Two types of UTP cables are commonly encountered in networking: Straight-through cables and Cross-over cables. Using the wrong type of cable may prevent connectivity.

-The SSID is a case-sensitive, alpha-numeric string up to 32-characters. It must match on both the AP and client. If the SSID is broadcast and detected, this is not an issue. If the SSID is not broadcast, it must be manually entered onto the client. If the client is configured with the wrong SSID, it will not associate with the AP. Additionally, if another AP is present that is broadcasting the SSID, the client may automatically associate to it. - On most APs open authentication is configured by default, allowing all devices to connect. If a more secure form of authentication is configured, a key is necessary. Both the client and the AP must be configured with the same key. If the keys do not match, authentication will fail and the devices will not associate.

- Good troubleshooting documentation should include: Initial problem Steps taken to isolate the problem Results of all steps taken, both successful and unsuccessful Final determined cause of the problem Final problem resolution Preventative measures -The helpdesk will require information specific to the problem including: Symptoms encountered Who encountered the problem When the problem manifests Steps taken to identify the problem Results of steps taken -Record all information regarding the interaction with the helpdesk, such as: Time/date of call Name/ID of technician Problem reported Course of action taken Resolution/escalation Next steps (follow-up) -A helpdesk is a group of individuals with the knowledge and tools required to help diagnose and correct common problems. Today I reviewed the cisco chapter 9 and then I did my test.
 * __Wednesday May 18th 2011:__**

Today Mr. Brooks gave us the course chapter review and I did that half the class and then I did some scratch for then rest of the period.
 * __Thursday May 19th 2011:__**

I did my chapter 8 test ands then I barely finished my course practic exam.
 * __Friday May 20th 2011:__**