Coggle requires JavaScript to display documents.
Used to tell if hardware is overheating The smelling of burning insulation or components is very distinct and bad Taste in smell go hand-n-hand, if you can smell it, you can taste it, and sometimes you can taste acridness of something burning
You can touch to see if components are hot You can tell if a fan has failed if there is no vibration
Seeing things and going "that's not quite right"Used to see the condition and function via LEDs and Error Beeps Cables which are not connected Cable connected to the wrong port Loose cable connections Damaged cables and connectors Use of the wrong type of cable
Cables which are not connected Cable connected to the wrong port Loose cable connections Damaged cables and connectors Use of the wrong type of cable
Can be used to detect major issues electrical problems, proper operation of cooling fans and disk drives Devices have distinct sounds and any change can indicate a problem
T568A or T568B
Be able to tell the difference between when you need a Straight-through cable from a Crossover cable
the central nervous system of wired networks and one of the most common issues when experiencing inactivity.
Starts as the Physical Layer and the Physical components and moves up the OSI model A good approach to use when the issue is a physical one Most networking problems reside at the lower levels, so implementing the bottom-up approach is often effective
starts with end-user applications and moves down the OSI model End-user app of an end system are tested before looking at more specific networking pieces. This approach for simpler problems, or when you think the problem is software related Disadvantages requires checking every network application until issue is found each conclusion and possibility must be documented good luck finding out where to start
requires checking every network application until issue is found each conclusion and possibility must be documented good luck finding out where to start
The network admin selects a layer and tests in both directions from that layer. starts by collecting user experience of the issue, document symptoms and with that info, make an informed guess of where to look first When a layer is verified as functioning properly, it can be assumed that the layers below it are functioning
one of the most basic troubleshooting techniques Approach discover the traffic path all the way from source to destination. Scope reduce to just the links and devices that are in the forwarding path. Objective eliminate the links and devices that are irrelevant to the troubleshooting task at hand
discover the traffic path all the way from source to destination.
reduce to just the links and devices that are in the forwarding path.
eliminate the links and devices that are irrelevant to the troubleshooting task at hand
AKA Swap-the-ComponentYou Physically swap the problematic device with a known, working one (Know Good Spare) can be ideal method for quick problem resolution. If the problem lies within multiple devices, it may not be possible to correctly isolate the problem
can be ideal method for quick problem resolution. If the problem lies within multiple devices, it may not be possible to correctly isolate the problem
AKA Spot-The-DifferenceAttempts to resolve the problem by changing the nonoperational elements to be consistent with the working onesCompare Configurations Software versions Hardware other device properties, links or processes Weakness Method might lead to a working solution, without clearly revealing the actual issue
AKA Shoot-from-the-hip approachyou're guessing, you're going off a hunch
IP address Subnet mask Default Gateway
MAC address IP addresses of Default Gateways DNS server DHCP server and lease info
release current DHCP config
requests for new config info from the DHCP server