11.01.2013 Views

Workshop

Workshop

Workshop

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Previous Table of Contents Next<br />

Hour 2<br />

You Can’t Have Too Much Documentation, Money,<br />

or Love!<br />

Would you start out on a car trip in a strange country without a map? Of course you wouldn’t, but this is<br />

what people do every day when they fail to document their ever-expanding networks. When it comes<br />

time to troubleshoot, those who don’t have a map to go by will just shrug and shake their heads.<br />

Undocumented networks are mostly incomprehensible. You need some method of getting your bearings,<br />

and network documentation can be an compass in what can be a sea of confusion.<br />

Navigating a Bad Network Neighborhood<br />

There will be those who tell you that complete documentation is too much trouble, or that it takes too<br />

much time and doesn’t buy you all that much. This is utter hogwash. (Although many gray areas exist in<br />

network troubleshooting, this is one issue that is utterly black and white.) Folks without documented<br />

networks are the ones running around with their hair on fire while others with documented networks have<br />

fixed the problem, gone to lunch, done something productive, and gone home to spend time with their<br />

kids. This may sound rather judgmental, but there’s just too much evidence that suggests that you either<br />

document once and have a reference during times of trouble or you fail to document at all and end up<br />

having to figure out something multiple times during each crisis.<br />

Not only does insufficient documentation waste time when your network is having problems, but it also<br />

causes unnecessary fear and confusion during the crisis. You owe it to yourself to have as clear a<br />

situation as possible when you start to troubleshoot—believe me, there’s enough uncertainty and doubt<br />

when you’re trying to find your way out of a bad network neighborhood without adding to it due to a<br />

lack of a good map.<br />

Documentation Dividends<br />

Enough with the dire warnings and horror stories! Let’s set aside all the negatives due to a lack of<br />

documentation. On the positive side, you can see tangible benefits to having an acceptable level of<br />

documentation. Perhaps the one benefit you’ll appreciate most is that a documented network is a network<br />

from which you can walk away. You can take a vacation from a documented network without worrying<br />

about whether you’re going to be called if something goes wrong. Because you’re not the only person<br />

with access to information about how your network is set up, others can deal with it while you watch the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!