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.
Tip You probably won't have enough room to write all this information on the map itself. Therefore, you should key information to a machine or cable name and record the actual details in a file on your computer. Or, if you prefer to do things your own way, that's fine — just make sure you know how to find what you've recorded. Whatever scheme you adopt, use it religiously. Also, make brief notes about how your scheme works, so that someone else can use your map if you're not available to explain it.
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.
Tip Applications such as Visio and HP OpenView can help you create network maps. Search your favorite Web browser's computer or networking section using the keywords network map to find other applications and companies that can help you with this process.
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.
Warning Whenever anything changes on your network, make updating the map and its associated database a priority.
Sitting down and checking your map is much less work than walking around and looking at the real objects that the map shows. If the map is current, you can keep on top of things from the comfort of your office. If it's out of date, you'd better start walking!
Chapter 6: Installing Network Interface Cards
Overview
Buckle up, because it's time to hook the network up to your prospective Windows Server 2003 in preparation for putting that sucker to work!
For most PCs, whether they run Windows Server 2003 or some other operating system, the network interface (or interfaces, if a machine has more than one network connection) comes in the form of network interface cards, known affectionately as NICs.
For the uninitiated, NIC is pronounced "nick"; just like what sometimes happens when you shave. NICs provide the essential link between the network medium and a computer that needs to access the network.
In this chapter, you find out about the basic types, functions, and capabilities of NICs, and how to choose the right type to use in your server. Along the way, you have a chance to pick up lots of tips and tricks about setting up these all-important components correctly the first time and every time.