Chapter 13 dealt with what to do when something on a network inevitably goes wrong.
Most systems eventually experience some kind of trouble, and when they do, it's imperative that the trouble be as short-lived as possible. When something does crop up, it's best to identify what the problems and symptoms are (often, this will be obvious) and then move on to a fix. The first step in this direction often takes the form of identifying the affected area, determining what changed to cause the problem in the first place, and then making adjustments of one sort or another (replacing cables, updating or rolling back updates, fixing faulty hardware, reconfiguring something, and so forth) until the problem is solved and then documenting it afterwards.
The chapter also covered various types of troubleshooting tools - various instruments and devices for checking the integrity of a network's cables, the quality of its power flow, and even the traffic emitted by its nodes were discussed. I now want a butt set, a multimeter, and a wireless network testing tool.
An interesting chapter, if for no other reason than I see this kind of stuff as where a lot of the real fun of working with computers comes in. Problem solving is good.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment