Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
IP Subnetting Step #2: The Key Design Trade-off: Partitioning Network Address Host Bits
(Page 3 of 3)
Class B Subnetting Design Example
In some cases, especially with larger
networks, we may have multiple choices. Consider a more interesting
example, the larger Class B network 22.214.171.124, where we have a total
of 15 subnets and the largest has 450 hosts. Examining the subnet summary
table for Class B suggests four acceptable options, as shown in Figure 75.
Figure 75: Example Class B Subnetting: A More Difficult Decision
This Class B network needs at least 15 subnets and must allow up to 450 host per subnet. Three subnet ID bits is too few, and 8 means only 254 hosts per subnet, which is insufficient, but there are four acceptable options, so we must choose wisely. J
In all four of these, the
number of subnets is equal to 15 or greater, and the number of hosts
per subnet is over 450. So, which option should we choose? Usually,
we want to pick something in the middle. If we use 4 bits for
the subnet ID, this gives us only a maximum of 16 subnets, which limits
growth in the number of subnets, since we already have 15. The same
applies to the choice of 7 bits for the subnet ID, since we already
have 450 hosts in one subnet now, and that limits us to 510. Thus, we
probably want either 5 or 6 bits here. If we expect more growth in the
number of hosts in the largest subnet, we'd choose 5 bits; if we expect
more growth in the number of subnets, we'd choose 6 bits. If unsure,
it's probably best to assume more growth in the number of hosts per
subnet, so here we would choose 5 bits.
The converse problem may also occur:
you may be in a position where there are no rows in the table that will
match. For example, if our Class C example has 35 hosts in the largest
subnet instead of 25, we are out of luck: there is no combination of
subnet ID and host ID size that works. The same is true in our Class
B example if we had 4,500 hosts in that big subnet instead of 450. In
this situation we must either divide the large subnet into a smaller
one, use more than one IP address block, or upgrade to a larger block.
Key Concept: If there is more than one combination of subnet ID and host ID sizes that will meet requirements, try to choose a middle-of-the-road option that best anticipates future growth requirements. If no combination meets the requirements, the requirements have to change!
|If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!|
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.