CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte79

A new version of IP (IPv6), with much larger addresses (128 bit)
Assigning a subset of a public IP network to each company,

instead of an entire public IP network, to reduce waste, using a
feature called classless interdomain routing (CIDR)
Network Address Translation (NAT), which allows the use of
private IP networks
These three solutions matter to real networks today. However, to

stay focused on the topic of subnet design, this chapter focuses on
the third option, and in particular, the private IP networks that can
be used by an enterprise when also using NAT. (Be aware that
Chapter 14, “Network Address Translation,” in the CCNA 200-301
Official Cert Guide, Volume 2, Second Edition, gives more detail
about the last two bullets in the list, while Part VII of this book
discusses the first bullet item (IPv6) in more depth.
Focusing on the third item in the bullet list, NAT allows multiple
companies to use the exact same private IP network, using the same
IP addresses as other companies while still connecting to the
Internet. For example, Figure 11-13 shows the same two companies
connecting to the Internet as in Figure 11-12, but now with both
using the same private Class A network 10.0.0.0.
Figure 11-13 Reusing the Same Private Network 10.0.0.0 with NAT
Both companies use the same classful IP network (10.0.0.0). Both

companies can implement their subnet design internal to their
respective enterprise internetworks, without discussing their plans.
The two companies can even use the exact same IP addresses inside
network 10.0.0.0. And amazingly, at the same time, both companies
can even communicate with each other through the Internet.
The technology called Network Address Translation makes it possible

for companies to reuse the same IP networks, as shown in Figure
11-13. NAT does this by translating the IP addresses inside the
packets as they go from the enterprise to the Internet, using a small
number of public IP addresses to support tens of thousands of
private IP addresses. That one bit of information is not enough to
understand how NAT works; however, to keep the focus on
subnetting, the book defers the discussion of how NAT works until
CCNA 200-301 Official Cert Guide, Volume 2, Second Edition. For
now, accept that most companies use NAT, and therefore, they can
use private IP networks for their internetworks.
Private IP Networks
When using NAT—and almost every organization that connects to

the Internet uses NAT—the company can simply pick one or more of
the private IP networks from the list of reserved private IP network
numbers. RFC 1918 defines the list of available private IP networks,
which is summarized in Table 11-2.
Table 11-2 RFC 1918 Private Address Space
Class of Number of
Private IP Networks
Networks Networks
A 10.0.0.0 1
B 172.16.0.0 through 16
172.31.0.0
C 192.168.0.0 through 256

192.168.255.0
Note
In each class I teach online, I survey students about

who uses network 10.0.0.0 in their company, with an
average response of 60–70 percent using private class
A network 10.0.0.0.
From the perspective of making IPv4 work for the entire world,
private IP networks have helped preserve and extend IPv4 and its
use in every enterprise and throughout the Internet. In particular,
private networks have improved IPv4’s implementation worldwide by
Avoiding using another organization’s public address

range for private networks: Some organizations have a part of
their networks that need zero Internet access. The hosts in that
part of their network need IP addresses. RFC 1918 suggests that
truly private networks—that is, networks with no need for
Internet connectivity—use addresses from the RFC 1918 list of
private networks.
Delaying IPv4 address exhaustion: To delay the day in which
all public IPv4 addresses were assigned to organizations as public
addresses, RFC 1918 calls for the use of NAT along with private
networks for the addresses internal to an organization.
Reducing Internet routers’ routing table size: Using private
networks also helps reduce the size of the IP routing tables in
Internet routers. For instance, routers in the Internet do not need
routes for the private IP networks used inside organizations (in
fact, ISPs filter those routes).
Choosing an IP Network During the Design Phase
Today, most organizations use private IP networks along with NAT,

which requires a small CIDR block of public addresses. Some
companies use a public address block, like a public Class A, B, or C
network, per the original plan that would allow each company to
have its own unique public network. Some smaller number of
companies might use a public CIDR block for all addresses—in effect
a subset of a Class A, B, or C network—and subnet that block.
For the purposes of this book, most examples use private IP network
numbers. For the design step to choose a network number, just
choose a private Class A, B, or C network from the list of RFC 1918
private networks. Regardless, the subnetting math works the same
whether you begin with a public or private IP network.
After the choice to use a private IP network has been made, just
pick one that has enough IP addresses. You can have a small
internetwork and still choose to use private Class A network
10.0.0.0. It might seem wasteful to choose a Class A network that
has over 16 million IP addresses, especially if you need only a few
hundred. However, there’s no penalty or problem with using a
private network that is too large for your current or future needs.
Choose the Mask
If design engineers followed the topics in this chapter so far, in

order, they would know the following:
The number of subnets required

The number of hosts/subnet required
That a choice was made to use only one mask for all subnets so
that all subnets are the same size (same number of hosts/subnet)
The classful IP network number that will be subnetted
This section completes the design process, at least the parts

described in this chapter, by discussing how to choose that one mask
to use for all subnets. First, this section examines default masks,
used when a network is not subnetted, as a point of comparison.
Next, the concept of borrowing host bits to create subnet bits is
explored. Finally, this section ends with an example of how to create
a subnet mask based on the analysis of the requirements.
Classful IP Networks Before Subnetting
Before an engineer subnets a classful network, the network is a

single group of addresses. In other words, the engineer has not yet
subdivided the network into many smaller subsets called subnets.
When thinking about an unsubnetted classful network, the addresses

in a network have only two parts: the network part and host
part. Comparing any two addresses in the classful network:
The addresses have the same value in the network part.

The addresses have different values in the host part.
The actual sizes of the network and host parts of the addresses in a
network can be easily predicted, as shown in Figure 11-14.
Figure 11-14 Format of Unsubnetted Class A, B, and C Networks
In Figure 11-14, N and H represent the number of network and host

bits, respectively. Class rules define the number of network octets
(1, 2, or 3) for Classes A, B, and C, respectively; the figure shows
these values as a number of bits. The number of host octets is 3, 2,
or 1, respectively.
Continuing the analysis of a classful network before subnetting, the

number of addresses in one classful IP network can be calculated
with the same 2H – 2 formula previously discussed. In particular, the
size of an unsubnetted Class A, B, or C network is as follows:
Class A: 224 – 2 = 16,777,214

Class B: 216 – 2 = 65,534
Class C: 28 – 2 = 254
Borrowing Host Bits to Create Subnet Bits
To subnet a network, the designer thinks about the network and

host parts, as shown in Figure 11-15, and then the engineer adds a
third part in the middle: the subnet part. However, the designer
cannot change the size of the network part or the size of the entire
address (32 bits). To create a subnet part of the address structure,
the engineer borrows bits from the host part. Figure 11-15 shows
the general idea.
Figure 11-15 Concept of Borrowing Host Bits
Figure 11-15 shows a rectangle that represents the subnet mask. N,

representing the number of network bits, remains locked at 8, 16, or
24, depending on the class. Conceptually, the designer moves a
(dashed) dividing line into the host field, with subnet bits (S)
between the network and host parts, and the remaining host bits (H)
on the right. The three parts must add up to 32 because IPv4
addresses consist of 32 bits.
Choosing Enough Subnet and Host Bits
The design process requires a choice of where to place the dashed

line shown in Figure 11-15. But what is the right choice? How many
subnet and host bits should the designer choose? The answers hinge
on the requirements gathered in the early stages of the planning
process:
Number of subnets required

Number of hosts/subnet
The bits in the subnet part create a way to uniquely number the
different subnets that the design engineer wants to create. With 1
subnet bit, you can number 21 or 2 subnets. With 2 bits, 22 or 4
subnets; with 3 bits, 23 or 8 subnets; and so on. The number of
subnet bits must be large enough to uniquely number all the
subnets, as determined during the planning process.
At the same time, the remaining number of host bits must also be
large enough to number the host IP addresses in the largest subnet.
Remember, in this chapter, we assume the use of a single mask for
all subnets. This single mask must support both the required number
of subnets and the required number of hosts in the largest subnet.
Figure 11-16 shows the concept.

CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte79

Uploaded by

Copyright:

Available Formats

CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte79

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCNA 200-301 Official Cert Guid - Wendell Odom - New - Parte79

Uploaded by

Copyright:

Available Formats

A new version of IP (IPv6), with much larger addresses (128 bit)

Assigning a subset of a public IP network to each company,

These three solutions matter to real networks today. However, to

Both companies use the same classful IP network (10.0.0.0). Both

The technology called Network Address Translation makes it possible

When using NAT—and almost every organization that connects to

Table 11-2 RFC 1918 Private Address Space

C 192.168.0.0 through 256

In each class I teach online, I survey students about

Avoiding using another organization’s public address

Choosing an IP Network During the Design Phase

Today, most organizations use private IP networks along with NAT,

Choose the Mask

If design engineers followed the topics in this chapter so far, in

The number of subnets required

This section completes the design process, at least the parts

Classful IP Networks Before Subnetting

Before an engineer subnets a classful network, the network is a

When thinking about an unsubnetted classful network, the addresses

The addresses have the same value in the network part.

Figure 11-14 Format of Unsubnetted Class A, B, and C Networks

In Figure 11-14, N and H represent the number of network and host

Continuing the analysis of a classful network before subnetting, the

Class A: 224 – 2 = 16,777,214

Borrowing Host Bits to Create Subnet Bits

To subnet a network, the designer thinks about the network and

Figure 11-15 shows a rectangle that represents the subnet mask. N,

The design process requires a choice of where to place the dashed

Number of subnets required

You might also like