9 hours 49 minutes
damaged cable. Not much to say about this, is there?
I've seen Twisted Para treated so poorly run over by chairs and equipment desk, sitting on it with the edges of the desk lag. I've seen people bundle it up, almost crumpling up the cable
cables breakable. Of course it is. With our cable, we examine it and replace it as necessary. We try to keep it safe from damage We try when we wrap up our cables to do it in an orderly fashion.
We try to run our cables in a way that is free from any sort of damage along the way. And we have cable testers again that can help us determine if our cable is functioning properly,
pins bent or missing pins. When I see this picture, it takes me back a little bit.
This looks like one of the old serial connectors that we used to use, or at least it's comparable to it, and we still see the V G a connectors out there. But we don't see a lot of connectors with these pins the way we used to, because pins can be a nightmare.
Pins get pent so easily. I remember just as a common thing with monitors, because people would pull out the V G a cable very carelessly, then you go plug it in. All of a sudden, the screen was just bright pink or dark blue or any sort of an uncover, and that was because of a bent pin.
Then, of course, trying to strengthen the pen. The first thing that happens is the pen snaps off, and that's no better either.
Just being very careful with our pens examining them.
The best thing we can do is go slow when we're making the connection and go slowly when we're disconnecting it as well.
Because those pins have purposes.
By damaging a pin, you may render the device unusable.
Bottlenecks. There is always a bottleneck on the network.
There's always some point that doesn't perform as quickly as others in this case, what we're really talking about noticing a serious amount of latency on the network, what's causing it?
First of all, devices that tend to cause late and see there are a million things I could think of.
One thing to consider our devices and inspect traffic firewalls, proxy servers, their jobs to capture traffic, inspect it and re transmit it.
If I have a device that doesn't perform well, that's going to cause latency or delay on the network.
Proxy servers actually enters at the packet, pull it apart, reassemble and re transmit
often proxy service Do cause a bit of delay.
Routers, network interfaces. We're going through a single network interface, going out to another network or out to the Internet.
Other performance issues are the duplex communication, the type of cable you're using, the amount of data that you're sending. There are so many things that can impact performance and slow things down.
Lights, lights will help you figure out what the heck is going on. There is no rocket science here. When you see a green light, things are probably pretty good.
Usually it's a yellow or amber light that indicates that there are issues, maybe collisions or some sort of not complete failure. But some sort of issue on the line,
and then usually the other option is just a jack of light.
Always check for that light.
If you're trying to determine what's failed, look at the lights. Those are the signals
that rubs are issues with cable,
We said There can be all kinds of problems with cable. So very common problems or attenuation.
Every cable will suffer attenuation of her distance. So we've just got to know what our distances are.
I'm not going to read through each one of these, but think about cross talk with twisted pair cabling, electromagnetic interference, duplex mismatch. I'm trying to hit the ones that I think are most likely to be on the exam
mismatch of duplex that will definitely cause issues with incorrect type of cable. Just remember the pros and cons of each cable type that might lead one type of cable to be preferable to another in the network connectivity issues. Look at your switch.
Is the port bad? Is the port lit? Is the port yellow? Are your connectors pin up properly?
There's just so many things to check as part of the process.
All right, guys, you will not believe it, But this wraps up our course. This is the end of module seven. And of course, in general
module seven, we focus on troubleshooting. We have to take an orderly and methodical approach. Troubleshooting and comp Tia, give us the steps.
Then we looked at troubleshooting devices and tools that we look to troubleshoot hardware and tools to troubleshoot software, including certain utilities like paying and trace route, and I'd be conflict that are best used from the command line.
Then we wrap things up by taking look at cable because, after all, that's the pathway that data travels across.
If the cable's damage are properly configured, obviously our signal doesn't have to have a clean pathway to get from source to destination.
I hope Modules seven has been helpful to you.
It's definitely important to have troubleshooting skills as a network technician.
This is a good chapter to go back and review.