11.01.2013 Views

Workshop

Workshop

Workshop

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

sun rise on your beach vacation without your pager or cellular phone going off. Because the work day is<br />

already occupied enough without having to drag somebody around to show him or her all of the nuances<br />

of the network, your network documentation does this for you, leaving you time to do other work. Table<br />

2.1 describes the four major types of network documentation.<br />

Type Purpose<br />

Table 2.1Types of documentation<br />

Logical/functional map This type of documentation gives an overview of how data flows in<br />

general. It leaves out individual workstations and wire runs and<br />

simply shows the important parts of the network (such as the<br />

servers, routers, and network segments).<br />

Physical/layout map This type of documentation shows very specific information about<br />

the network, including all wires, hubs, local switches, and<br />

workstations.<br />

Device and cable labeling This type of documentation consists of physical labels that identify<br />

the devices or cables they’re attached to in big, bold letters.<br />

Detail/description This type of documentation can consist of a logical write-up of an<br />

application or system, or an everyday log of what’s done to a<br />

device or system. It includes anything that’s not intuitive and not<br />

included in manufacturer’s documentation.<br />

Logical/Functional Maps<br />

Logical or functional maps are probably the type of documentation that you’ll refer to most often.<br />

They’re used as a sort of “org chart” of your network, and, appropriately, they indicate which device or<br />

server is responsible for what function, as well as which devices depend upon other devices in order to<br />

work. Details are not as important here; flow is what you’re looking for. You’ll want to be able to<br />

determine, without being confused by unnecessary details, why department A can’t talk to the server, but<br />

department B can.<br />

Not every PC or printer needs to be on this chart, but every device that somebody else relies on (such as<br />

your servers and routers) does. You’ll need to make a per-case decision as to whether to include hubs or<br />

switches on this type of chart, based on whether these act as a group or stand alone. In other words, on<br />

this type of chart, hubs and switches (being a “neighborhood”) are usually represented on their own, but<br />

there might be cases in which a switch connects two different “neighborhoods” that would be<br />

appropriately represented separately. See Figure 2.1 for an example of a simple logical network.

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

Saved successfully!

Ooh no, something went wrong!