You can be the best network troubleshooter in the world, but without documentation, you’re out to sea in a leaking boat. Documentation can mean the difference between ten minutes of downtime compared to two hours or so; therefore, a little work up front can really pay off in the long run.
Each type of documentation is important in its own way—for example, labels on cables, maps of the network cable runs, and functional diagrams of server placement are all valuable assets. Also, keeping a logbook can keep history from repeating itself. In other words, it gives you a point of reference when the network goes down.
In Hour 4, you’ll learn how many network problems are the result of human-initiated change—and what to do about it.