NETWORK DESIGN LIFECYCLE

TYPES OF NETWORK DESIGN

 Hierarchical network design has emerged as a widely adopted industry best
practice for establishing reliable, scalable, and cost-effective networks. In the
early days, networks utilized a flat design, expanding in a single direction
through hubs and switches, which posed challenges in filtering undesirable traffic
and controlling broadcasts.
 As networks grew larger, response times suffered, necessitating a new network
design approach that led to the adoption of the hierarchical model. Although flat
network design still has its applications, it is mostly used for small networks or
cost-conscious designs aiming to minimize the use of routers or switches.
What Is Hierarchical Network?
Typical Hierarchical Network Design
 The hierarchical structure of the network usually consists of access, distribution,
and core layers. While a three-layer design is common, it is not mandatory.
 Access Layer: The access layer, also known as the network edge, encompasses
the end devices (such as end-users and local servers) that directly access the
network
 Its primary functions include:
◦
Facilitating the connection of diverse end devices to the LAN network.
◦ Ensuring network security by preventing unauthorized devices from accessing
the LAN through the enforcement of security policies such as port security,
DHCP snooping, and static MAC address configuration.
Typical Hierarchical Network Design


 Its
◦ primary functions include:
◦
◦
◦
◦
Typical Hierarchical Network Design
 Core Layer: The core layer is commonly referred to as the backbone of the network because
it serves as a high-speed transport infrastructure between the switches located in the
distribution layer. It acts as the central aggregation point for multiple networks within the
overall network infrastructure.
 Its primary functions include:
◦ Consisting of high-speed network devices: Prioritize fast packet switching.
◦ Interconnectivity between distribution layer devices: The core layer facilitates seamless
connectivity and communication between the various devices present in the Distribution
Layer.
◦ Offloading CPU-intensive tasks: The core layer plays a critical role in offloading CPU-
intensive tasks like security services (restrictive ACLs), Quality of Service (QoS)
classification, inspection, and other packet manipulations. By handling these tasks at the
core layer, it prevents performance degradation on other network devices.
◦ Reliability and fault tolerance: It is designed to provide high availability and fault tolerance
to ensure maximum network performance and minimize disruptions
Advantages of Hierarchical Network

 Enhanced Network Performance: The distribution and core layers, consisting

of high-performance switches, increase speeds and minimize network bandwidth
issues. With a well-designed network, data can travel at nearly wire speed
between devices, optimizing performance, reducing latency, and ensuring
efficient data transmission throughout the network.
 Advanced Security: When it comes to security, hierarchical networks offer
increased control and customization. Security policies can be applied at various
levels, such as individual users, specific departments, or the entire organization.
This flexibility allows network administrators to create tailored network traffic
plans that align with the specific requirements of the enterprise. By keeping
network details restricted from most users, intentional or unintentional network
issues become less of a concern.
Advantages of Hierarchical Network

 Improved Flexibility and Scalability:

Hierarchical networks offer increased flexibility compared to other network
architectures. They allow for seamless addition of segments and elements without
causing major disruptions to the existing network.
 Simplified Management
Hierarchical networks are easier to manage due to their consistent functionality
across network layers. For example, making changes to one access layer switch
can be confidently replicated across others with the same role. Deploying new
switches is simplified as configurations can be easily copied. Troubleshooting and
recovery processes are also streamlined, as issues can be isolated and resolved
more efficiently within specific layers. Overall, hierarchical networks simplify
management tasks and enhance operational
Approaches to network design
 There are two common approaches to analyze and design networks:
 The 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
 The 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
NETWORK DESIGN LIFE CYCLE
PPDIOO Lifecycle Approach to Network
Design and Implementation
 PPDIOO stands for Prepare, Plan, Design, Implement, Operate, and Optimize.
 PPDIOO is a Cisco methodology that defines the continuous life-cycle of services
required for a network.
 PPDIOO stands for Prepare, Plan, Design, Implement, Operate, and Optimize.
PPDIOO is a Cisco methodology that defines the continuous life-cycle of services
required for a network.
PPDIOO Phases

• The PPDIOO phases are as follows:

• Prepare: Involves establishing the organizational requirements, developing a
network strategy, and identifying technologies that can best support the
architecture. The prepare phase can establish a financial justification for network
strategy by assessing the business case for the proposed architecture.


Plan: Involves identifying initial network requirements based on goals, facilities,

user needs, and so on. The plan phase involves characterizing sites and assessing
any existing networks and performing a gap analysis to determine whether the
existing system infrastructure, sites, and the operational environment can
support the proposed system. A project plan is useful for helping manage the
tasks, responsibilities, critical milestones, and resources required to implement
changes to the network. The project plan should align with the scope, cost, and
resource parameters established in the original business requirements.
PPDIOO Phases

 Design: The initial requirements that were derived in the planning phase drive
the activities of the network design specialists. The network design specification
is a comprehensive detailed design that meets current business and technical
requirements, and incorporates specifications to support availability, reliability,
security, scalability, and performance. The design specification is the basis for
the implementation activities.
 Implement: The network is built or additional components are incorporated
according to the design specifications, with the goal of integrating devices
without disrupting the existing network or creating points of vulnerability.
PPDIOO Phases

 Operate: Operation is the final test of the appropriateness of the design. The
operational phase involves maintaining network health through day-to-day
operations, including maintaining high availability and reducing expenses. The
fault detection, correction, and performance monitoring that occur in daily
operations provide the initial data for the optimization phase.
 Optimize: Involves proactive management of the network. The goal of proactive
management is to identify and resolve issues before they affect the organization.
Reactive fault detection and correction (troubleshooting) is needed when
proactive management cannot predict and mitigate failures. In the PPDIOO
process, the optimization phase can prompt a network redesign if too many
network problems and errors arise, if performance does not meet expectations,
or if new applications are identified to support organizational and technical
requirements.
Plan, Build, Manage (PBM)

 Cisco’s second lifecycle model is PBM. This was created as a simplified way to
engage customers in their projects. The PPDIOO phases are still relevant, but
they map to three simple phases.
 This is easier for customer engagement. Different teams, companies, or
consultants, can handle different sections of the project. For example:
1. Consultant- Design the solution. This is the Plan section
2. Internal IT- Implements the solution. This is the build section
3. A managed services team operates the solution. This is the Manage section
Plan
 The plan section includes:
• Strategy and Analysis
• Assessment of the current network
• Design of the revised network
Build
 The build section includes:
• Deployment of the new network
• Migration to the new network
• Validation of the new network
Manage

 The manage section includes:

• Product Support
• Solution Support
• Optimization
• Operations Management
Mapping PBM to PPDIOO

 As shown below, Each section still maps to PPDIOO. The teams in each PBM
phase can refer to their relevant PPDIOO tasks.
DESIGN PHASES
 Design phase methodology involves the following:

[Link] Topology
[Link] security
[Link] performance
[Link] scalability
Design Topology
 Design topology, which is the physical and logical layout of the network devices,
links, and segments.
 You must consider which network devices are best for the network requirements
and budget, how they will be distributed and interconnected, and how they will
provide redundancy, fault tolerance, and load balancing. Furthermore, you need
to consider how the topology can support security, segmentation, and isolation,
as well as enable easy management, monitoring, and troubleshooting.
Additionally, you must design the network addressing scheme, such as IP
addresses, subnets, and VLANs, as well
 Additionally, you must design the network addressing scheme, such as IP
addresses, subnets, and VLANs, as well as the routing protocols like OSPF, EIGRP,
or BGP
Design Security
 Involves protecting resources, data, and users from unauthorized access,
modification, or disruption. This requires identifying potential threats and
vulnerabilities of the network and implementing appropriate security measures
such as firewalls, VPNs, encryption, authentication, authorization, and auditing.
 Additionally, you need to design security policies and procedures such as access
control lists, password policies, backup plans, and incident response plans. When
doing so, consider what security risks and challenges exist in the environment
and applications, what security standards and regulations apply to the network,
what security objectives and expectations the users have, what security best
practices are recommended for the design and implementation process, and how
to test and verify the security design.
Design Performance
 The design of the performance of the network, deals with quality of service and
user experience of the network applications and functions.
 To do this, you should define the performance metrics and benchmarks, such as
throughput, latency, jitter, packet loss, and availability.
 Additionally, you should design optimization and enhancement techniques like
bandwidth management, traffic shaping, compression, caching, and load
balancing. When considering these factors, ask yourself: what are the
performance requirements and expectations of the network users and
applications? How will the performance be measured and monitored? How will
external factors like congestion or interference affect it? How can it be improved
or maintained over time? And how will it align with the business goals of the
organization?
Design Scalability
 Scalability of the network, is its ability to grow and adapt to changing demands
and conditions. Anticipating future needs and trends, such as new users, devices,
applications, or locations, is essential. You should also consider scalability
strategies and solutions, such as modular design, hierarchical design,
virtualization, cloud computing, and automation
 Additionally, ask yourself questions such as: what are the current and projected
network growth rates and patterns? How will the network design accommodate
or support the network expansion or contraction? How will it ensure compatibility
and interoperability with new or existing technologies or systems? How can it
leverage or integrate with emerging or innovative technologies or solutions? And
how will it enable flexibility and agility for the network users and managers?
Document Design
 Document the design of the network, involves communication and presentation
of the design details and specifications. It is essential to create and maintain
network design documentation, such as diagrams, tables, charts, reports and
proposals, that accurately describe and illustrate the network design
components and features
 This documentation should be used for validation, verification, implementation,
operation, maintenance, and improvement.
 To ensure this documentation is effective, it should be written in clear, concise
language with standard symbols, formats, and conventions. Additionally,
appropriate tools and software should be used for creating and managing the
documentation.
 Feedback from different sources should be used to improve and update the
documentation. Best practices and guidelines should also be followed when
organizing and storing the network design documentation
What Should Network Documentation Include?

 Physical Layout
• Floor maps: Include detailed floor maps of your facilities, marking the
precise locations of network devices. This helps in locating devices
during maintenance or troubleshooting.
• Rack diagrams: If you have server rooms or data centers, detailed
diagrams of your racks, including what’s installed and where, are
invaluable.
• Cabling: Detail the types of cables used, their lengths, and where they
connect. Color coding or labeling can help quickly identify different
networks or functions.
What Should Network Documentation
Include?
• Inventory list: Create a comprehensive list of all devices, including make,
model, serial number, purchase date, warranty expiration, and other relevant
details.
• Firmware and software versions: Track your devices’ software or firmware
versions. Planning upgrades and ensuring compatibility can be facilitated
through this approach.
• Data Center Infrastructure Management (DCIM): DCIM tools provide a
comprehensive view of the physical infrastructure of your data center, including
power, cooling, and environmental factors. It’s essential to keep track of the
insights provided by your DCIM solution, such as power usage efficiency, rack
temperature, and airflow. Detailed documentation can assist in optimizing the
performance and extending the lifespan of your data center assets.
What Should Network Documentation
Include?
 Network Topology
• Hierarchical diagrams: It’s helpful to have different levels of network
diagrams. High-level diagrams give a broad overview, while more detailed
diagrams can dive into specific areas or functions.
• Redundancy details: Highlight areas where redundancy is in place, such as
dual routers or backup internet lines. This helps in understanding failover
mechanisms and ensuring uninterrupted service.
What Should Network Documentation
Include?
 Change Logs
• History of changes: Anytime you change the network, you should document it.
This includes the nature of the change, the date, the person responsible, and the
reason for the difference.
• Rollback plans: For significant changes, always have a plan to revert to the
previous state if something goes awry.
 Access Details
• Login credentials: While security is paramount, having a secure method to
store and retrieve device login details can be vital, especially in emergencies.
• Remote access details: Information on remotely accessing the network,
possibly through VPNs or other secure methods, can be crucial for off-site
troubleshooting or management.
What Should Network Documentation
Include?
 Security Measures
• Firewall rules: Document the rules on your firewalls, explaining the rationale
behind each. This helps in reviewing and updating security measures.
• Intrusion detection and prevention systems (IDPS): Detail the systems to
detect and prevent unauthorized access or attacks.
• Security protocols: Outline the security measures and protocols in place,
ensuring everyone is aware and can follow them.
What Should Network Documentation
Include?
 Backup and Recovery Procedures
• Backup schedules: Document when you take backups, where they’re stored,
and how to restore them.
• Disaster recovery plan: Outline the necessary steps to take in case of major
disasters, ensuring a structured approach to recovery.
EXAMPLES OF DESIGN
EXAMPLE 1
EXAMPLE 2
EXAMPLE 3
EXAMPLE 4
EXAMPLE 5
EXAMPLE 6
EXAMPLE 7
EXAMPLE 8
EXAMPLE 9
Benefits of a Lifecycle Approach

 The network lifecycle approach provides several key benefits aside from keeping
the design process organized. The main documented reasons for applying a
lifecycle approach to campus design are as follows:
• Lowering the total cost of network ownership
• Increasing network availability
• Improving business agility
• Speeding access to applications and services
Components of a lucrative network design

1. A clear map of the network

2. The structure and layout of the cabling necessary
3. The type, quantity, and location of different devices available on the network
4. The IP addressing structure
5. Details of the network security architecture and processes involved
Network Communication Models
The OSI Reference Model
• There are two basic types of models that we use to describe the functions that must occur for network
communications to be successful:

• Protocol model - It closely matches the structure of a particular protocol suite. A protocol suite
includes a set of related protocols that typically provide all the functionality required for people to
communicate with the data network. The TCP/IP model is a protocol model because it describes
the functions at each layer of protocols within the TCP/IP suite.

• Reference model – It describes the functions that must be completed at a particular layer but
needs to specify exactly how a function should be accomplished. This model does not intend to
provide sufficient detail to define precisely how each protocol should work at each layer. The
primary purpose of a reference model is to aid in a clearer understanding of the functions and
processes necessary for network communications.

• The OSI project at the ISO created the most widely known internetwork reference model.
• It is used for data network design, operation specifications, and troubleshooting.
• This model refers to the OSI model.
© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 46
Network Communication Models
The OSI Reference Model (Cont.)
OSI Model Description
Layer
7 - Application The application layer contains protocols used for process-to-process communications.
6 - Presentation The presentation layer provides a typical representation of the data transferred between application layer
services.
5 - Session The session layer provides services to the presentation layer to organize its dialogue and manage data
exchange.
4 - Transport The transport layer defines services to segment, transfer, and reassemble the data for individual
communications between the end devices.
3 - Network The network layer provides services to exchange individual data over the network between identified end
devices.
2 - Data Link The data link layer protocols describe methods for exchanging data frames between devices over shared
media.
1 - Physical The physical layer protocols describe the mechanical, electrical, functional, and procedural means to
activate, maintain, and de-activate physical connections for a bit transmission to and from a network
device.

© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 47
Network Communication Models

OSI Model and TCP/IP Model Comparison

• Because TCP/IP is the protocol suite used for internet communications, why do we need to learn
the OSI model as well?
• The TCP/IP model visualizes the interactions of the various protocols that make up the TCP/IP
protocol suite.
• It does not describe general functions that are necessary for all networking communications.
• It describes the networking functions specific to those protocols in the TCP/IP protocol suite.
• The protocols that make up the TCP/IP protocol suite describes in terms of the OSI reference
model.

• The functions that occur at the internet layer in the

TCP/IP model are contained in the network layer of
the OSI Model, as shown in the figure.
• The transport layer functionality is the same
between both models.

© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 48
Network Communication Models

OSI Model and TCP/IP Model Comparison (Cont.)

• The key similarities are in the transport and network layers; however, the two models differ in how
they relate to the layers above and below each layer:
• OSI Layer 3, the network layer, maps directly to the TCP/IP internet layer. This layer
describes protocols that address and route messages through the internetwork.

• OSI Layer 4, the transport layer, maps directly to the TCP/IP transport layer. This layer
describes general services and functions that deliver ordered and reliable data between
source and destination hosts.

• The TCP/IP application layer includes several protocols that provide specific functionality to
various end-user applications. Application software developers and vendors use the OSI
model Layers 5, 6, and 7 as references to produce applications that operate on networks.

• The TCP/IP and OSI models commonly refer to protocols at various layers because the OSI
model separates the data link layer from the physical layer, which commonly refers to these
lower layers.

© 2020 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 49
Network design report
 [Link]
Design a Network in Cisco Packet Tracer.

 Case Study and Requirements:

• Design a network in Cisco Packet Tracer to connect ACCOUNTS and DELIVERY
departments through the following:
• Each department should contain at least two PCs.
• An appropriate number of switches should be used in the network.
• Using the given network [Link], all interfaces should be configured with
correct IP addresses, subnet mask and gateways.
• All devices in the network should be connected using appropriate cables.
• Test communication between devices in both ACCOUNTS and DELIVERY
departments