NETWORK DESIGN

Chapter One
1. Applying Methodology to Network Design
1.1. Introduction
Computers and information networks are critical to the success of businesses, both large and small.
They connect people, support applications and services, and provide access to the resources that
keep the businesses running. To meet the daily requirements of businesses, networks themselves
are becoming quite complex.
Today, the Internet-based economy often demands around-the-clock customer service. This means that
business networks must be available nearly 100 percent of the time. They must be smart enough to
automatically protect against unexpected security incidents. These business networks must also be able to
adjust to changing traffic loads to maintain consistent application response times. It is no longer practical
to construct networks by connecting many standalone components without careful planning and design.

1.2. Types of Network design

1.2.1. Logical Network Design
Logical network design is a type of design which includes: - designing of network topology,
designing addressing and naming of network components especially central devices and end points,
selection of switching and routing protocols, developing network security strategies and finally
develop network management strategies.
1.2.2. Physical Network Design
Physical design outlines the pieces of the logical design network which are in a given network
architecture. Besides, it refers to the arrangement of computers and other physical components.
Physical network design involves the selection of LAN and WAN technologies for campus and
enterprise network designs as well as technologies for the remote-access and wide-area network
(WAN) components of an enterprise network design. During this network design process, choices
are made regarding cabling, physical and data link layer protocols, and internetworking devices
(such as switches, routers, and wireless access points). A logical design forms the foundation for
a physical design. In addition, business goals, technical requirements, network traffic
characteristics, and traffic flows influence a physical design.

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

1.3. Network Design Strategies

Analyzing requirements includes:

 Corporate Structure
What are the organizational units and how are they related to one another? How many users are
in each unit and where are they located? Much of this information is available in a simple
organizational chart.
 Desktop Configurations
From the networking standpoint, you need to identify the various hardware and software
configurations that currently exist: those you actually can and intend to connect to the network.
And the network adapters, software protocols, and network operating systems needed for the
connection.
 Enterprise applications and services
It is important to define the scope of applications and services. Are there enterprise applications,
such as a large personnel database, accessed by users in many departments? Are there departmental
applications limited to the users in a single department?
For example, you may want to place enterprise applications on the backbone and departmental
applications on smaller networks in individual departments.
 Workgroups
To manage network traffic and improve performance, have networking topology that enables
flexible workgroups. you need to discover the various workgroups, what unique applications their
users require, and how they access the software across departmental or even worldwide servers.
 Existing networks
Are they Ethernet-based, Token Rings, or something else? What type of cabling is in place? What
additional cabling will be required? What network protocols are being used? Look, too, beyond
LANs (local area networks) and identify the WANs. What types of WANs are in place, and what
other options are available?
 Data centers and facilities

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

The network infrastructure is essential to the data center. The important issues are where to locate
the facilities and how to build a WAN to support them. Are there sufficient conduits for cabling?
Is there adequate power and air conditioning? And what about the wiring closets? Are they secure?
Do they have sufficient power and ventilation?

Design for success

From the user’s perspective, the criteria for a successful network are
 functionality (Is the network useful and easy to use?),
 performance (Is it fast and responsive?), and
 reliability (Does it do what’s expected and when it’s needed?).
Key methods for the network architecture
Our network architecture depends on five methods, of which the most important is centralization.
The others are distribution, consolidation, duplication, and segregation. Some of these methods
may appear to be contradictory, but, in fact, they are complementary.
Standard issues
Once network standards are defined, it doesn’t mean you’re finished. New standards evolve as better
technologies emerge. You’ve got to be flexible and take advantage of those new technologies,
Survey technologies and trends
To develop a best network architecture, it is important to identify and understand the main
technologies, issues, and trends. Remaining well informed means solving problems, taking strategic
advantage of emerging technologies, and saving money.
Logical network topology
After analyzing user requirements, setting critical goals, and surveying the technologies, it’s time to
develop a logical topology for your distributed network architecture. The logical topology revolves
around a backbone, the central conduit between major network segments. (Subnets and
workgroups). What about the remote locations? Subnets can be connected to the backbone network
independently of location. This means you can connect the remote subnets in your remote offices
as well as the local subnets in the building complex to the backbone.

1.4. Network design Principles

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

 Functionality – The network must work. The network must allow users to meet their job
requirements. The network must provide user-to-user and user-to-application connectivity
with reasonable speed and reliability.
 Scalability – The network must be able to grow.
The initial design should grow without any major changes to the overall design.
• Adaptability – The network must be designed with a vision toward
• future technologies. – The network should include no element that would limit
implementation of new technologies as they become available.
• Manageability – The network should be designed to facilitate network monitoring and
management to ensure ongoing stability of operation.
1.5. Methodology to Network Design

PDIOO Lifecycle Approach to Network Design and Implementation. PDIOO stands for Plan,
Design, Implement, Operate, and Optimize. PDIOO is a Cisco methodology defines the continuous
life-cycle of services required for a network.

1.5.1 Prepare

It is anticipating the broad vision, requirements, and technologies needed to build and sustain a
competitive advantage. In the prepare phase, a company determines a business case and financial
rationale to support the adoption of new technology. By carefully anticipating future needs and
developing both a technology strategy and a high-level architecture to meet those needs, a business

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

is better equipped to contain costs during deployment and operations. So, business agility starts
with preparation

The next step is to ensure that before meeting with the client, whether internal or external some
basic business-related information has been collected
• Competition
• Market Conditions
• Future of the Industry
• Products Produced/Services Supplied
• Financial Condition
Once the basic information has been collected, meet with the customer to hear what they have to
say At that meeting, collect information on the project

Then to Identifying Customer Needs/Goals

 Analyzing Business Goals and Constraints
 Analyzing Technical Goals and Tradeoffs
 Characterizing the Existing Network
 Characterizing Network Traffic

1.5.2. Plan

For a network to scale properly a plan for addressing and naming must be developed IP addressing
should follow along with the number of discrete networks that will ultimately be needed Names
should reflect the type of device and location as this will help in troubleshooting At least at the
LAN level, there is no decision anymore: Ethernet is the only choice At this level switches are the
only choice for a new network There is no reason to use a hub anymore Networking computers
first and tracking the connections later can quickly become confusing and unmanageable as you
try to find which computer communicates with and shares resources with which other computers.
A network plan, therefore, is a formally created product that shows all the network’s components
and the planned connections between them. Such a plan is also used to manage the various types
of information. Your plan should show what types of information are stored where, and who is
allowed to use each type.

At the WAN level there are decisions to be made concerning routing protocols at least Routing
Protocols are used by routers to learn how to reach other networks
NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY
 NETWORK DESIGN

Which to use depends on

 Network size
 Equipment manufacturer
 Equipment age
The next step is to examine the security needs of the network Security must pay attention to
 Assets to protect
 Risks to these assets
 Establishing a clear and enforceable security policy
 User community training

Security is implemented through

 Authentication
 Authorization
 Auditing
 Encryption
 Connection Control
 Physical Protection
Management of the network is another consideration to build in Management requires
 timely information
 Performance
 Utilization
 Delay
 Downtime
 Throughput

Error rates

Successful technology deployment depends on an accurate assessment of a company’s current

network, security state, and overall readiness to support the proposed solution. In the plan phase,
a company ascertains whether it has adequate resources to manage a technology deployment
project to completion. To evaluate and improve network security, a company tests its network for
vulnerability to intruders and outside networks. The company then develops a detailed project plan

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

to identify resources, potential difficulties, individual responsibilities, and critical tasks necessary
to deliver the final project on time and on budge

Factors Involved in Network Planning

After you have completed your hardware plan, you are ready to begin network planning, from
the software perspective. As part of the planning process you must:
 Obtain a network number and, if applicable, register your network domain with the Inter
NIC. Devise an IP addressing scheme for your hosts, after you receive your IP network
number.
 Create a handwritten or typed list containing the IP addresses and host names of all
machines to comprise your network, which you can use as you build network databases.
 Determine which form of name service to use on your network: NIS, NIS+, DNS, or the
network databases in the local /etc directory.
 Establish administrative subdivisions, if appropriate for your network.
 Determine if your network is large enough to require routers, and, if appropriate, create a
network topology that supports them.
 Set up subnets, if appropriate for your network.

1.5.3. Design
Developing a detailed design is essential to reducing risk, delays, and the total cost of network
deployments. A design aligned with business goals and technical requirements can improve
network performance while supporting high availability, reliability, security, and scalability.
Day-to-day operations and network management processes need to be anticipated, and, when
necessary, custom applications are created to integrate new systems into existing infrastructure.
The design phase can also guide and accelerate successful implementation with a plan to stage,
configure, test, and validate network operations.
Logical Network Design

▪ Designing a Network Topology

▪ Designing Models for Addressing and Naming
▪ Selecting Switching and Routing Protocols
▪ Developing Network Security Strategies
▪ Developing Network Management Strategies

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

Physical Network Design

 Selecting Technologies and Devices for Campus Networks
 Selecting Technologies and Devices for Enterprise Networks
Designing a network is typically broken into three sections:
 Determine requirements
 Define the overall architecture
 Choose technology and specific devices
1.5.4. Implement
In the implement phase, a company works to integrate devices and new capabilities in accordance
with the design—without compromising network availability or performance. Install the network
and prepare to use the networkA network is essential to any successful organization, and it must
deliver vital services without disruption.
After identifying and resolving potential problems, the company attempts to speed return on
investment with an efficient migration and successful implementation—including installing,
configuring, integrating, testing, and commissioning all systems.

After network operation is validated, an organization can begin expanding and improving IT staff
skills to further increase productivity and reduce system downtime
1.5.5. Operate
Network operations represent a significant portion of IT budgets, so it’s important to be able to
reduce operating expenses while continually enhancing performance. Throughout the operate
phase, a company proactively monitors the health and vital signs of the network to improve service
quality; reduce disruptions; mitigate outages; and maintain high availability, reliability, and
security.
By providing an efficient framework and operational tools to respond to problems, a company can
avoid costly downtime and business interruption. Expert operations also allow an organization to
accommodate upgrades, moves, additions, and changes while effectively reducing operating costs.
Areas to look at in the test phase include
 Verify the design meets the business and technical goals
 Validate the design selections
 Identify bottlenecks
 Test redundant channels
NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY
 NETWORK DESIGN

 Assess the impact of total network failure

 Identify anything that might impede full deployment
If you are working on new network design and implementation you should also cheek the
following key points as new system.
Performance
Test the application with transaction volume that is within and at the top of the range expected
from the business requirements
Make sure that the resulting system behavior is within expectations or any formal service level
agreements
Stress
Expose the system to transaction volume substantially higher than what would normally be
expected and over a concentrated time period
Failure
Regression tests look to see what no longer works when the new stuff goes on line
Security

Ensure that people have the access level that is required and no more and that unauthorized people
cannot access the system

Requirements

Track each business requirement through the development process and make
sure that it is included in the final system

Usability

Determine that people can use the system easily and without frustration

Documentation

Check that hard-copy and online documentation are understandable and accurate

Training

Ensure that online or in-person training is effective and meets the training requirements Interface

Test your application interfaces with external databases or third-party companies

Disaster Recovery

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

See whether you can recover the system from a simulated disaster

Multiple Locations

Verify your system can function between multiple locations, if necessary

1.5.6. Optimize
A good business never stops looking for a competitive advantage. That is why continuous
improvement is a mainstay of the network lifecycle. In the optimize phase, a company is
continually looking for ways to achieve operational excellence through improved performance,
expanded services, and periodic reassessments of network value. Have business goals or technical
requirements changed? Is a new capability or enhanced performance recommended? As an
organization looks to optimize its network and prepares to adapt to changing needs, the lifecycle
begins anew—continually evolving the network and improving results.
Once the network is in place and running, it should be optimized Exactly how to do this will depend
on the hardware and protocols used.

Top down network design

In a flat network design, there is no hierarchy. Each network device has essentially the same job, and the
network is not divided into layers or modules. A flat network topology is easy to design and implement,
and it is easy to maintain, as long as the network is small in size. However, when the size of the network
grows, a flat network is undesirable. Lack of hierarchy makes troubleshooting difficult.
Designing a network presents several challenges, particularly when time is of the essence. Where
you begin the design process at the bottom of the OSI model with the physical layer, or at the top
with the application layer, is critical to your success. Let’s explore each approach (bottom-up vs.
top-down), including the pros and cons of each. Here, we examine these two approaches.
Bottom-up Approach:
This approach begins with the physical layer of the OSI model and works its way up. New, higher
bandwidth links might be purchased, as well as new routers, switches, firewalls, etc. Designing a
network with a bottom-up approach enables you to get your network set up much faster.
Top-down Approach:
With this approach, we are going to start with the requirements of the organization, the technology
that is needed, and then design it from the top-down. The application layer is the starting point,

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY

 NETWORK DESIGN

and the applications and services that are desperately needed are analyzed for their specific
requirements first.
Top-down Approach VS Bottom-up Approach
Top-Down Approach Bottom-up Approach
Advantage • Starts with the • Quick method
organizations • Leverages previous
• Provides big picture experience
to the designer and
customer
Disadvantage Time consuming • High probability of failure
• Might miss core components
of the organization

NETWORK DESIGN DEPARTMENT OF INFORMATUON TECHNOLOGY