| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
IP Subnetting Step #1: Requirements Analysis (Page 1 of 2) When you are building or upgrading a network as a whole, the first step isn't buying hardware, or figuring out protocols, or even design. It's requirements analysis, the process of determining what it is the network needs to do. Without this foundation, you risk implementing a network that may perfectly match your designbut not meet the needs of your organization. The exact same rule applies to subnetting as well. Before we look at the gory details of host addresses and subnet masks, we must decide how to subnet the network. To do that, we must understand the requirements of the network. Analyzing the requirements of the network for subnetting isn't difficult, because there are only a few issues that we need to consider. Since requirements analysis is usually done by asking questions, here's a list of the most important questions in analyzing subnetting requirements:
The first question is important because everything in subnetting is based around dividing up a Class A, Class B or Class C network, so we need to know which we are dealing with. If we are in the process of designing a network from scratch and don't have a Class A, B or C block yet, then we will determine which we need based on the approximate size of the organization. After that, we need to determine two key numbers: how many physical subnets we have, and the maximum number of hosts per subnet.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||