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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Topology Maps<br />

An updated <strong>network</strong> <strong>to</strong>pology map is essential. This map should depict (at least) <strong>the</strong><br />

cabling plant and <strong>the</strong> bridges, switches, hubs, routers, and so forth on <strong>the</strong> <strong>network</strong>.<br />

The map should indicate <strong>the</strong> physical locations of <strong>the</strong> equipment, <strong>network</strong> segments,<br />

and device and interface addressing information. In most cases, it is easier <strong>to</strong><br />

develop maps that depict specific elements. For instance, one map might document<br />

physical device interconnections, ano<strong>the</strong>r might describe <strong>the</strong> <strong>network</strong> logically from<br />

a pro<strong>to</strong>col addressing perspective. One map might depict <strong>the</strong> equipment racks by<br />

device and location in <strong>the</strong> computer or cable distribution room. The idea is <strong>to</strong> map<br />

out <strong>the</strong> <strong>network</strong> in such a way that anyone can find anything by looking at <strong>the</strong><br />

correct map. Mapping is a common feature of many management systems, and<br />

some are better at it than o<strong>the</strong>rs. These systems also support au<strong>to</strong>matic device<br />

discovery and can relay status information. Though <strong>the</strong>y are helpful <strong>to</strong> display and<br />

manage <strong>the</strong> <strong>network</strong>, <strong>the</strong>y are not suitable for constructing all <strong>the</strong> maps necessary<br />

for a solid documentation set.<br />

Device Information<br />

Each <strong>network</strong> component should have a device information sheet. This can be an<br />

Access or Oracle database, a set of index cards, even a set of Web pages. The idea<br />

is <strong>to</strong> construct a uniform fact sheet about each device on <strong>the</strong> <strong>network</strong> from<br />

end-station <strong>to</strong> routers. You should develop a universal identity scheme for all <strong>the</strong><br />

<strong>network</strong>ed devices. This can be a hostname, internal audit, or lease serial number;<br />

you can even use <strong>the</strong> device's MAC address. The ID needs <strong>to</strong> be unique <strong>to</strong> <strong>the</strong> device<br />

and that one that will ideally never be duplicated or become obsolete (such as an<br />

employee or department name). This tag is what you can use <strong>to</strong> sort through <strong>the</strong><br />

information. Then, for each device, you want <strong>to</strong> record some subset of <strong>the</strong> following<br />

information:<br />

• Universal ID<br />

• Hostname/system name<br />

• Installation location<br />

• Network address(es) and supported pro<strong>to</strong>cols<br />

• MAC address(es)<br />

• Telco circuit ID(s) (if appropriate)<br />

• Manufacture and model<br />

• Vendor information and contact numbers<br />

• Service contract number<br />

• Local technical contact<br />

• Data port assignments (what end-devices are connected <strong>to</strong> its ports)<br />

• Software version<br />

• Dependent or adjacent devices

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

Saved successfully!

Ooh no, something went wrong!