09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

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.

However, <strong>the</strong> most valuable <strong>to</strong>ol of all, on any <strong>network</strong>, is proper documentation.<br />

Without adequate documentation, your <strong>network</strong> will become an unmanageable<br />

beast before your eyes. Documentation helps you and o<strong>the</strong>rs visualize <strong>the</strong> role of<br />

each component in <strong>the</strong> <strong>network</strong> and provides a common reference point for<br />

configuration, technical contact, and service and warranty information.<br />

Documentation<br />

This point cannot be emphasized enough: Good documentation is very important.<br />

Without it, you are lost. One of <strong>the</strong> most common misconceptions about computer<br />

<strong>network</strong>s is that <strong>the</strong>y are <strong>to</strong>o complicated <strong>to</strong> manage. This is not <strong>the</strong> case. A <strong>network</strong><br />

that is well designed and properly documented is easily managed, and when<br />

problems do arise, <strong>the</strong>y are often easy <strong>to</strong> pinpoint and resolve.<br />

Now, <strong>the</strong> word "documentation" is often misunders<strong>to</strong>od and is, in some circles, a<br />

"dirty" word. So, let's start with what documentation is not. It is not notes scribbled<br />

on napkins and pizza boxes, or a notebook filled with sketches. Proper <strong>network</strong><br />

documentation is a set of documents that describes <strong>the</strong> following:<br />

• The <strong>to</strong>pology of your <strong>network</strong>, each of its hardware components, and <strong>the</strong><br />

pro<strong>to</strong>cols in use <strong>to</strong> transmit, transport, and manage data delivery.<br />

• The site's (or sites') cabling infrastructure and labeling scheme, kind of<br />

cabling used (copper and fiber), types of connec<strong>to</strong>rs, patch panels, average<br />

cable length between <strong>the</strong> end-stations and <strong>the</strong> interconnect panel, and any<br />

certification documentation.<br />

• The servers on <strong>the</strong> <strong>network</strong>, <strong>the</strong>ir operating system, <strong>the</strong> function <strong>the</strong>y<br />

perform, <strong>network</strong> address information, administra<strong>to</strong>r information, and so<br />

on.<br />

• A management document that describes <strong>the</strong> general operational policies<br />

regarding <strong>the</strong> <strong>network</strong>. This document would also describe <strong>the</strong> management<br />

system, documentation policy, format, and contact information. This<br />

document is usually associated with a company's computer and physical<br />

security policy and a disaster recovery plan.<br />

The actual format and method you follow <strong>to</strong> document your <strong>network</strong> is up <strong>to</strong> you.<br />

Your company might already have a standard and format <strong>the</strong>y use for this kind of<br />

information. The key is <strong>to</strong> make sure it is accurate, up <strong>to</strong> date, readable, and easily<br />

accessible.<br />

To get you started, here are some basic ideas about <strong>the</strong> kinds of information your<br />

documentation should contain.

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

Saved successfully!

Ooh no, something went wrong!