Windows Server 2003 for Dummies

Earlier in this chapter, we introduce you to most of the basic principles involved in designing and building a network. By now, you have a pretty good idea about how networks work. As you spend more time around networks, however, you may realize that what they do isn't nearly as important as what you know about what they do.

Whether you wrestle with networks only occasionally or full-time , you may discover that there's nothing like a network map to help you find and keep track of things on your network.

It's not a map; it's the whole enchilada!

Calling the collection of data that describes your network a map doesn't do this concept justice . A network map is certainly more than a mere drawing that shows where network components live on your network but creating such a drawing is a great way to start building a network map. If you look at the following list of things that a network map should contain, you'll see why such a map is more than a mere depiction:

• A list of all computers on your network, with supporting documentation

• A list of all network equipment such as servers and hubs, plus any repeaters, routers, and so on with supporting documentation

• A list of all printers and other similar equipment on the network such as scanners and fax machines with supporting documentation

• Lines to indicate where cables run and where junctions, taps, and other media- related elements are located

Capturing data for your network map

Because a network map is so important and such a powerful tool, pause right here and start one immediately. Be prepared to spend some time and energy on this project, because most of the data that makes up a network map is scattered all over the place.

Building a detailed network map is a worthwhile investment. It will pay for itself many times over as you come to depend on it. At worst, you discover more about your network than you ever wanted to know (but not more than you'll ever need to know). At best, you get to know your network so well that it will seldom throw you a curve ball and you may even find some things to tweak and tune while building that map.

Start at the foundation Obtaining a set of your building's architectural drawings or engineering plans can help a great deal. If you can find any drawings or plans, take them to an architect's supply store and make copies that you can mark up and use as a base map. (Most plans are created using an old-fashioned, ammonia-based copying system called blueline . You can copy even large- sized plans for less than $25 per plan.)

If no such plans are available, you can sketch a room-by-room layout on rectangular grid paper (such as an engineering pad) to make it easy to draw to scale. Be sure to mark the location of machines, approximate locations for cable runs, and so on.

Anything on your network should be on the map

Anything that merits attention or costs money is worth recording on your map. You don't need to go into great detail about each and every connector or note the exact length of every cable. (Approximate lengths within a meter or so are useful, however.) Indicate every major cable run, every computer, and every piece of gear attached to the network.

Take stock of your network

The information you gather while producing a network map creates a detailed inventory of what's on your network and where everything is located. Unfortunately, you quickly find out that this is a lot of information.

To make keeping an inventory easy for yourself (and for anyone who follows in your footsteps), build a template or form that you can fill out for each item on the network. This approach forces you to collect consistent information and makes delegating information gathering to others easier. Include all of the following information for each computer on the network:

• The hardware configuration for each machine: This should include a list of all interfaces and their settings, information about installed RAM and drives , and the make and model of the keyboard, display, and so on. If you can find out who sold you the equipment, write that down, too.

  Keeping track of equipment is typically the accounting department's responsibility. Check with them for a copy of your company's capital assets or a depreciable items inventory (if available). This type of documentation normally includes serial numbers and other identification for hardware on the network. If no one in your company has gathered such information, collect it yourself. It's valuable .

• The software configuration for each machine: This should include listings of configuration files, operating system data (including version number, most recent Service Pack applied, and so on), as well as a list of programs and versions installed on the machine.

• The network configuration for each machine: This should include the make and model of each network interface card (NIC), plus a list of driver files with names , version numbers, dates, and sizes. You can capture such data to a file easily on Windows systems by choosing Start Programs Accessories System Tools System Information Hardware Resources; use this as the basis for this inventory. (On Windows XP and Windows Server 2003 systems, the menu selection begins with Start All Programs.)

In addition to information on each computer, your inventory should also include the following data:

• A list of other equipment, such as hubs, routers, and printers: Include the manufacturer, model, make, and serial number for each piece of equipment. If the equipment includes memory modules, disk drives, or plug-in interface cards, get information about them, too. If the equipment uses software or firmware, record the name, version, release date, and any other information you can garner about such items.

• A list of all the cable segments on the network: Give each segment a unique name or number, and associate your records with whatever type of identifier you use for those segments. Record the type and make of cable, its length, the locations of its ends, and any significant connections or intermediate locations that you may have to visit in the future.

• A list of all the vendors who've worked on your network or its machines: Include names and phone numbers of contacts at each operation. This can be a valuable resource for technical support and troubleshooting. Over time, add the names and phone numbers of tech support or other individuals at these organizations who prove to be knowledgeable and helpful.

Essentially, the information gathered while creating and maintaining a network map forms a database of everything anyone needs to know about your network. To improve access to and usability of this data, consider storing the text for your network map in an honest-to-gosh database engine. If this is too labor- intensive , a file-or paper-based approach works but takes more effort to maintain over time. Whichever method of recording data for your map you use, be sure to keep your inventory complete and up-to-date.

When the network changes, so does the map!

One thing that you can always be sure of when it comes to networks: They're always changing. Your map is only as good as the information it contains. And the map only remains useful if that information is an accurate reflection of the real network in your organization.