Table of Contents
Module 2 - Design the Network Structure
Section 4 - Design a Network-Layer Addressing and Naming Model
Case Study: Jones, Jones, & Jones
1. Describe your IP addressing plans for implementation
of your proposed system design.
-
You should use the contiguous Class C addresses defined in RFC 1918 Section
3 (192.168.0.0 to 192.168.255.255) within the bounds of Jones, Jones, &
Jones. Of course, separate networks will be defined for the WAN connections.
To keep things simple, the third octet will be used as a network number.
For expansion, you might group these for LAN and WAN, for example:
-
192.168.1.x through 192.168.99.x for the WANs
-
192.168.100.x through 192.168.199.x for the U.S. LANs
-
192.168.200.x through 192.168.254.x for the international LANs
-
Plenty of addresses are available, which makes it easy to immediately recognize
networks. With this grouping we would then make the following assignments:
-
192.168.101.x for Office 1
-
192.168.102.x for Office 2
-
192.168.103.x for Office 3
-
192.168.201.x for the Europe Office
-
192.168.202.x for the MidEast Office
-
The last octet can be used to identify the network nodes on each network,
which will provide 254 nodes for each office. With this solution, the routers
and PC/server nodes will support a simple 255.255.255.0 subnet mask. This
is an attractive solution because it provides simplicity for an administrative
staff that is not experienced with routers. Use of a 255.255.255.0 mask
on the WANs could be seen as a waste, but there are so many addresses available
that it is not important.
-
The nodes should then be grouped by class for ease of identification. This
solution would involve something similar to the following:
-
192.168.x.1 through 192.168.x.59 for the communications equipment
-
192.168.x.60 through 192.168.x.99 for the servers (file, print, mail, and
so on). Consider that there are many printers in a law firm.
-
192.168.x.100 through 192.168.x.254 for the user nodes
-
The NetWare DHCP should be installed on the servers and used to dynamically
assign IP addresses to the user computers.
2. Propose a plan for naming servers, routers,
and end nodes. Describe both the names themselves and the
method that will be used
to configure the names.
-
It would probably be best to name the servers with their office location
names suffixed with the last octet of the server node address, such as
DENVER001, which will aid in troubleshooting. The user nodes should be
named with names that aid troubleshooting. For example, a prefix of "PC"
for desktop PCs and "NB" for notebook computers followed by a "hyphen"
and the user's first initial and last name, such as PC-BSMITH or NB-BSMITH.
3. The managing partner called. She wanted to
emphasize that unauthorized workstations should not be
allowed access to the
Internet. How will you plan for this request in your design?
-
Static IP addresses should be assigned to specific users at the DHCP server.
All but these addresses will then be filtered at the Internet router.
4. Update your topology diagram to reflect the
new addressing scheme.
Click on the Back button in your browser to review Section 4 of Module
2. If you are finished with that section, click
here to go on to Module 2, Section 5.
Copyright Cisco Systems, Inc. -- Version 2.0 7/98