The Physical Network

After you've decided on the network protocols and the services you need to offer on the network, identified potential bottlenecks, and evaluated the security problems associated with your network needs, you can then design the physical aspects of the network.

The preceding chapter discussed different physical network topologies. There are tools you can use, such as Visio, to draw a physical network diagram. Tools such as these are expensive but make a much better presentation to management than hand-drawn network layouts. Whichever tool you decide to use to create the actual network drawings, just be sure that the drawings are clear and concise . Looking back at your network application requirements, bandwidth requirements, and the like, you can then start designing the physical network, deciding where to place important servers and redundant devices.

Planning Resources

Finally, keep in mind that technology changes rapidly in the computer and networking fields. Although hubs might have been sufficient a few years ago, today these are now legacy devices that have been replaced by switches that operate much faster and cost about the same as a hub used to cost. Although Bill Gates might have thought (way back when) that no one would ever need more than 640KB of memory, that prediction proved false almost as soon as it left his mouth. As we all know, change is the only constant thing in this universe. With technology, this is especially the case today.

If you are about to set yourself on a course of designing a network, become familiar with all the latest technologies, and don't depend solely on past experience. The best way to keep up with new technologies is to read about them. You can use books, such as this one, and resources on the World Wide Web, and you can also talk to knowledgeable consultants who are experts in their field.

Finally, Appendix C, "Internet Resources for Network Administrators," can point you to some interesting books and Web sites that contain helpful information. You'll find links in the appendix to sites that specialize in security, network protocols, and so on. You'll also find sites that maintain copies of Internet Request for Comments (RFC) documents, which spell out standards that are used on the Internet.

Chapter 4. Upgrading Strategies and Project Management

SOME OF THE MAIN TOPICS IN THIS CHAPTER ARE

Where Do You Start?

Determining When an Upgrade Is Necessary ”The Evaluation Process

What Resources Are Needed for the Upgrade?

Planning an Upgrade

Testing the Plan

Deployment

User Training

Closing the Book ”Documenting What Has Changed and Why

Other Considerations for Upgrading

This chapter discusses some things you should consider when deciding whether an upgrade is needed for the network, and some of the steps necessary to accomplish the task. It is not a simple task to undertake a major network upgrade. It is not a simple task to undertake an upgrade of even a single departmental network, depending on the applications, servers, network bandwidth required, and other factors. Any sort of upgrade contemplated in this book should be done so in an orderly fashion, and the appropriate documentation (before and after) needs to be created. Documentation does not mean that you have an absolute set of directions that must be followed. Instead, it is a set of documents you can create before the upgrade, and then modify as circumstances reveal new problems or opportunities that may arise during the upgrading process.