Introduction to Network Design and Implementation

A networking infrastructure involves a number of hardware components including wiring,

connectors, racks, network interface cards, client and server workstations, and communications
devices such as repeaters, bridges, shared and switched hubs, and routers. It also includes
software such as network card drivers, communications protocols, network operating systems
and network application tools.

Computer network design refers to the planning of the implementation of a computer network
infrastructure. Network design is generally performed by network designers, engineers, IT
administrators and other related staff. It is done before the implementation of a network
infrastructure.

The objective of network design is to satisfy data communication requirements while

minimizing expense. Requirement scope can vary widely from one network design project to
another based on geographic particularities and the nature of the data requiring transport.

There are a number of details your network infrastructure design should show, these include:
 A clear map of the network.
 The structure and layout of the cabling required.
 The quantity, type and location of all devices on the network.
 Your IP addressing structure.
 Details of your network security architecture and processes

Network Requirements
Most businesses actually have only a few requirements for their network:
The network should stay up all the time, even in the event of failed links, equipment failure,
and overloaded conditions.
- The network should reliably deliver applications and provide reasonable response times
from any host to any host.
- The network should be secure. It should protect the data that is transmitted over it and
data stored on the devices that connect to it.
- The network should be easy to modify to adapt to network growth and general business
changes.
- Because failures occasionally occur, troubleshooting should be easy. Finding and fixing a
problem should not be too time-consuming

Goals of Network Design

When examined carefully, these requirements translate into four fundamental network design
goals:
- Scalability: Scalable network designs can grow to include new user groups and remote
sites and can support new applications without impacting the level of service delivered
to existing users.

1
 - Availability: A network designed for availability is one that delivers consistent, reliable
performance, 24 hours a day, 7 days a week. In addition, the failure of a single link or
piece of equipment should not significantly impact network performance.
- Security: Security is a feature that must be designed into the network, not added on
after the net-work is complete. Planning the location of security devices, filters, and
firewall features is critical to safeguarding network resources.
- Manageability: No matter how good the initial network design is, the available network
staff must be able to manage and support the network. A network that is too complex
or difficult to maintain cannot function effectively and efficiently

Five Things to Be Considered in Designing a Network

Important things to consider include balancing security issues with the desire for easy access to
information; building redundancy into the network in anticipation of breakdowns; and
standardizing hardware and software to keep maintenance costs in check.
- Connectivity and Security
Network connectivity today means more than Ethernet cables and wireless access points.
People today are more connected while mobile than ever before and many of them want
access to company email and data while they are out of the office. Balancing those needs while
maintaining security is a challenge that needs to be addressed in the design phase of any
network.
This includes where data is stored, either in-house or offsite with cloud-based solutions, what
types of information should be accessible, who should be able to access it, and which types of
devices should be included. Firewalls and access servers need to be secure without slowing
down operations.
- Redundancy and Backing Up
Redundancy means having backup devices in place for any mission-critical components in the
network. Even small organizations should consider using two servers. Two identical servers, for
example, can be configured with fail-safes so that one will take over if the other fails or requires
maintenance. A good rule of thumb is to have redundant components and services in place for
any part of a network that cannot be down for more than an hour.
If an organization hosts it own Web servers, or cannot be without Internet connectivity, a
second connection should be in place. Having an extra switch, wireless router, and a spare
laptop onsite is a good practice for ensuring that downtime is kept to a minimum.
- Standardization of Hardware and Software
Standardization of the hardware and software used in a network is important for ensuring the
network runs smoothly. It also reduces costs associated with maintenance, updates and repairs.
Conducting a full audit of the current computer systems, software and peripherals will help to
determine which should be standardized.
A CEO or director may require special consideration, but if 90 percent of the employees use the
same notebooks, with the same word processing and email programs, a software or hardware
patch across the organization can be conducted much less expensively than if everyone used a
different computer model with different software installed on each.

2
 - Disaster Recovery Plan
A detailed disaster recovery plan should be a part of any network design. This includes, but is
not limited to, provisions for back-up power and what procedures should be followed if the
network or server crashes. It should also include when data is backed up, how it is backed up
and where copies of the data are stored. A comprehensive disaster recovery plan includes
office disasters, building disasters, and metropolitan-wide disasters.
In most cases, important data should be backed up daily. Many organizations do a full weekly
backup, with daily incremental backups that copy any files that have been modified since the
last weekly backup. Backup files should be stored in a secure location off-site in the event of a
building disaster, such as a fire.
- Future Growth of the Organization
While it is not always possible to anticipate how large an organization may be five years in the
future, some allowances for future growth must be built into the network design. For example,
Microsoft Small Business Server can be an excellent choice for many small organizations.
However, if your office already has sixty employees, Small Business Server could soon be a
wasted investment, as it has a limit of only 75 users
Network design should factor in at least 20 percent growth per year, including everything from
switch ports to data backup systems.
Traditional network design approach
The traditional network design approach follows a structured systems analysis and design
process similar to that used to build application systems.
• The network analyst met with users to determine the needs and applications.
• The analyst estimated data traffic on each part of the network.
• The analyst designed circuits needed to support this traffic and obtains cost
estimates.
• Finally, a year or two later, the network is implemented
Three forces are making the traditional design approach less appropriate for many of today’s
networks:
1. The underlying technology of computers, networking devices and the circuits
themselves if rapidly changing.
2. The growth in network traffic is immense.
3. The balance of costs has changed dramatically over the last 10 years.
Analysis and Design Principles
There are two common approaches to analyze and design networks:
Top-down approach:
The top-down design approach simplifies the design process by splitting the design tasks to
make it more focused on the design scope and performed in a more controlled manner, which
can ultimately help network designers to view network design solutions from a business-driven
approach.

3
Bottom-up approach:
In contrast, the bottom-up approach focuses on selecting network technologies and design
models first. This can impose a high potential for design failures, because the network will not
meet the business or applications’ requirements.

Here is a look at some important comparison points between these very different approaches:
TOP-DOWN BOTTOM-UP
Pros Starts with the need of the Quick
organization
Provides a ‘’big picture’’ to the Leverages previous Experience
customer and the designer
CONS Time consuming Might miss some organizational
requirements
High probability of failure

Choosing the design approach that best fits your needs will result in a stronger network.
Recognizing the pros and cons of each approach can help you build the case for the appropriate
choice, giving you the opportunity to build a network that will meet the needs of the project or
organization — and improve network performance.

Reading Assignment:
Explain the major phases of the top down network design approach.
Structured Design
 A focus isplacedon understandingdataflow,datatypes,and processes that access or change
the data.
 A focus is placed on understanding the location and needs of user communities that access or
change data and processes.
 Several techniques and models can be used to characterize the existingsystem,newuser
requirements,andastructurefor the future system.
 A logical model is developed before the physical model.
 The logical model represents the basic building blocks, divided by function, and the
structure of the system.
 The physical model represents devices and specific technologies and implementations.
Network Design and Implementation Cycle
Typical systems are developed and continue to exist over a period of time, often called a systems
development life cycle (SDLC).
SDLC is a standardized process that IT, systems, and software engineering industries use to
build and test network. It entails a step-by-step development process with the goal of creating
high-quality network that meets or exceeds customer expectations.
Here are a few benefits SDLC can bring:
 Offers better visibility of a project plan
 Mitigates project risks and errors

4
  Allows team members to track the progress of their project
 Ensures all requirements and objectives are achieved
Phase 1 – Analyze Requirements
 Analyze business goals and constraints
 Analyze technical goals and tradeoffs
 Characterize the existing network
 Characterize network traffic
Phase 2 – Logical Network Design
 Design a network topology
 Design models for addressing and naming
 Select switching and routing protocols
 Develop network security strategies
 Develop network management strategies
Phase 3 – Physical Network Design
 Select technologies and devices for campus networks
 Select technologies and devices for enterprise networks
Phase 4 –Testing, Optimizing, and Documenting the Network Design
 Test the network design
 Optimize the networkdesign
 Document the networkdesign
Phase 5 – Implementation and Test network
Phase 6 – Monitor and optimize network performance

Business Goals for designing a good network

 Increase revenue
 Reduce operating costs
 Improve communications
 Shorten product development cycle
 Expand into worldwidemarkets
 Build partnerships with other companies
 Offer better customer support or new customer services

5
RecentBusinessPriorities designing a good network
 Mobility
 Security
 Resiliency (fault tolerance)
 Business continuity after adisaster
 Network projects must be prioritized based on fiscal goals
 Networks must offer the low delay required for real-time applications such asVoIP
Business Constraints for designing a good network
• Budget
• Staffing
• Schedule
• Politics and policies
Network management and administration refers to the processes, tools and applications used
to administer, operate and maintain a network infrastructure.
Performance management and fault analysis are also included in network management.

The network management model that defines five functional areas of network management is
the FCAPS model. FCAPS stands for Fault Management, Configuration Management, Accounting
Management, Performance Management, and Security Management. Each functional area
focuses on specific aspects of managing and maintaining a computer network. Let's briefly
explore each area:
1. Fault Management:
o Fault management deals with the detection, isolation, and resolution of network
faults or issues.
o It involves monitoring the network infrastructure to identify faults, generating
alerts or notifications when issues occur, and initiating appropriate actions for
troubleshooting and resolving the faults.
o Fault management aims to minimize network downtime and ensure that
network services and resources are available and reliable.
2. Configuration Management:
o Configuration management involves managing and maintaining the configuration
of network devices, software, and settings.
o It includes tasks such as device inventory management, configuration backup
and restoration, software version control, and change management.
o Configuration management ensures that network devices are correctly and
consistently configured, which contributes to network stability and reduces the
risk of misconfigurations causing issues.
3. Accounting Management:
o Accounting management, also known as accounting and billing management,
focuses on tracking and managing the network resource usage and associated
costs.

6
 o It involves collecting data on network usage, such as bandwidth consumption
and resource utilization, and generating reports for billing, capacity planning,
and cost allocation.
o Accounting management helps organizations understand and control their
network expenses, allocate resources effectively, and optimize network
performance.
4. Performance Management:
o Performance management involves monitoring and optimizing network
performance to ensure efficient and reliable operation.
o It includes activities like monitoring network performance metrics, analyzing
performance data, identifying performance bottlenecks or degradation, and
taking appropriate actions to enhance network performance.
o Performance management helps optimize network resources, identify capacity
constraints, and ensure that the network meets performance objectives and
service level agreements.
5. Security Management:
o Security management focuses on protecting the network infrastructure, data,
and resources from unauthorized access, threats, and vulnerabilities.
o It involves tasks such as network access control, authentication and
authorization, vulnerability management, intrusion detection and prevention,
and security policy enforcement.
o Security management aims to ensure the confidentiality, integrity, and
availability of network resources, prevent security breaches, and respond
effectively to security incidents.
The FCAPS model provides a structured framework for organizing and implementing network
management activities. By addressing each functional area, organizations can effectively
monitor, configure, account for, optimize performance, and secure their network
infrastructure.