0% found this document useful (0 votes)
35 views8 pagesCN Notes
5 docs
Uploaded by
vaibhavigirkarCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
35 views8 pagesCN Notes
5 docs
Uploaded by
vaibhavigirkarCopyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
/ 8
Bioraga Borvices
Newwork infrastru
Senvoosr
eee ence
[Adapive
icture virtualization
eras WANS [ono
oe | oe (Fee
a ee a
veaonn Fig 3.22 Cisco SONA Offerings
securly
9.2.1 Advantages of SONA:
‘The advantages of SONA are as follows :
1, Functionality
2, Performance
3. Availability ’
4, Efficiency
5, Security
6. Manageability
7. Scalability
Functionality :
It supports the requirements of organization.
Performance :
— The desired responsiveness, throughput and
utilization on a per application basis are provided
through the network infrastructure and services
Availability :
It provides the required reliable services anywhere,
.
an
Efficiency :
It offers the required network
infrastructure with reasonable operational costs and
suitable capital investment on a migration path to a
‘more intelligent network, through step-by-step
growth of network services.
services and
SONA provides security while protecting information
assets and infrastructure from inside and outside
threats.
Manageability :
Manageability offers control, performance monitoring
and fault detection in the network.
Scolability :
It supports growth and expansion of organizational
tasks, by dividing funetions and products into layers.
‘The network growth is easier due to this separation.
9.3 Network Design Methodology
The network design methodology is derived from the
Cisco Prepare, Plan, Design. Implement, Operate, and
Optimize (PPDIOO) methodology.
PPDIOO retlects a lifecycle of network.
9.3.1. Design as an Integral Part of the
PPDIOO Mothodology :
Fig, 9.3.1 illustrates the phases of PPDIOO and their
relation to the network design methodology.
wren (6-3026) Fig. 9.3.1 : PPDIOO Network Lifecycle
‘As shown in Fig. 9.3.2, the phases of PPDIOO lifecycle
are separate, yet closely related to each other.
Following are the three phases of PPDIOO:
1. Prepare phase
2. Plan phase
3. Design phase
Prepare phase :
_ The prepare phase involves establishment of the
business requirements, developing a network strategy
and proposing a high-level conceptual architecture,
identifying technologies which can support the
network architecture.
strategy is developed in order to assess the business
case for the propc.ed architecture, financial
justification for the network.
Plan phase :
The main function of plan phase is to identify the
network requirements.
It identifies the network requirements based on the
goals for the network, where the network will be
installed, required network services and so forth.
~ This phase involves assessing the sites for installing
the network or any existing networks.
~ A gap analysis is performed by the plan phase to
determine the existing system infrastructure, sites,
‘and operational environment can support the
proposed system.
UN (Sem, 5 /AL& ML /MU) °.
A plan phase manages the tasks, responsibilities,
critical milestones and needed 10
Implement the changes to the network
resources
The proposed project plan should align with th
scope, cost and resource parameters established in
the original business requirements
Ign pha
After planning of network requirements, the next
phase is design phase.
The specialists design the network according to
planned requirements.
The designer includes any additional data gathered
during network analysis and network audit, when
upgrading the existing network and data through
discussion with managers and network users.
The generated network design specification is a
complete detailed design that meets the current
business and technical requirements.
includes
reliability,
The complete network
specifications to
security, scalability and performance.
designed
support availability,
These are basic design specifications for the
implementation activity.
Implement phase :
Implementation and verification starts after
approving the network design.
The implementation of network and any additional
components is done according to the design
specifications.
The goal of implement phase is to integrate devices
without disrupting the existing network or creating
points of vulnerability.
Operate phase
Operation is the final test of the correctness of
design. This phase maintains the network health
through day-to-day operations,
The network health includes maintaining high
availability and reducing expenses.
The reactive fault detection and correction as well as
performance monitoring takes place in daily
Operations that provides initial data for the optimize
phase.
WF lettronteds BF cn (sem 5 a1 ML/MU)
3. Optimize phase
‘The optimize phase is based on the management of
proactive network
The goal of this phase isto identify and resolve issues
before the real problems arise and affect the
organization
When proactive management cannot predict and
mitigate the failures, there is need of reactive fault
detection and correction (ie. troubleshooting).
= The optimize phase can lead to network redesign
because of the following reasons
1. If too many network problems or errors arises.
2. If performance does not meet expected
requirements.
3, If new applications are identified to support
‘organizational and technical requirements.
9.3.2 Advantages of Lifecycle Approach to
Network Design :
= The network lifecycle approach provides following
advantages in the network design :
1. Lowering the total cost of network ownership.
2. Increasing network availabilty.
3. _ Improving business agility.
Accelerating access t6 applications and services.
Lowering the total cost of network ownership :
= The total cost of network ownership is lowered by:
1. Identifying and validating the requirements of
technology.
2. Planning for the changes i
resource requirements.
infrastructure and
3. Developing a strong network design according
to technical requirements and business goals.
4, Improving the network efficiency.
5. Accelerating successful implementation.
6. Lowering operating expenses by improving the
efficiency of operation processes and tools.
Increasing network availability :
~The network availability can be increased by:
1. Assessing the state of the network's security and
its capability to support the proposed design
Entorprise Network Desion
Generating a strong operational design lang
validating the operation of network
3, Specifying the accurate set of software ang
releases and keeping them
hardware
operational
4, Testing the proposed system before installation,
5, Monitoring the system and assessing availabilty
trends and alerts
6 Identifying security breaches and defining
remediation plans.
7. Improving the skills of stat
Improving business agility: abilt
= The business agility can be improved by:
1. Integrating technical requirements and business
goals into a detailed design and demonstrating
that the network is functioning as specified.
2. Establishing business requirements. and
technology strategies.
3. Expertly installing, configuring, and integrating
system components.
Continue to enhance performance.
Readying sites to support the system to be
implemented.
‘Accelerating access to applications and services :
— Applications and services can be accessed very fast
by
1. Assessing and improving —_ operational
preparedness to support present and planned
technologies and services.
2. Improving the reliability, availability and stability
of the network and the applications running on
it
3. Improving efficiency and effectiveness of
service-delivery by increasing availability,
resource capability and performance.
4, Managing and solving problems that affect the
system and keeping software applications
present.
9.3.3 Design Methodology :
Definition :
A design methodology is a documented, systematic
method of doing something,
HF lechtnoutedge
y Sovnove quictly -
7 cusSem SIAL MLM)
gn ~q methodology Is helpful when designing an Enrico owen oes
va nternetwork that needs creative production on This step makes decisions about networked
tight schedule. 2 | infrastructure, infrastructure se 1 applications.
sd sqantages of ign methodology: The dat Petia
= The data required for making these decisions 5
qhe advantages of 2 desl :
oe Ign methodology are as | “lected during the first wo steps
ee pater sure that no step Is minted while = To verity the correctness of the design, 2 pilot oF
y following the process. prototype network can be constructed.
; 2. It offers a framework for the design process = A pilot or prototype network identifies and corrects
deliverables. ‘any problems a a proof of concept before
4, It supports consistency in the creative process implementing the entire network.
ly providing network designers to set suitable |~ A cetaled design document is written in this step. It
deadlines and maintain customer ond manager includes information documented in the previous
satisfaction. steps.
:
; 4. It permits customers and managers to confirm | ~ THe design implementation process 5 executed after
that the designers have idea about how to meet. completion of the design
their requirements.
= This process includes the following steps
13.3.1 Steps in Top-down Design 4, Plan the implementation +
Methodology -
A —Inthis step, cost assessment and the implementation
he design methodology includes three basic steps : procedures are prepared in advance to speed uP and
1, Identify customer requirements. clarify the actual implementation.
2. Characterize the existing network and sites. _- This step Is performed during the design phase of
3, Design the network topology and solutions. PPDIOO.
sept: Identity customer requirements: 2. Implement and verify the design :
this step is typically completed during the PPDIOO | ~ In this step, the actual im lementation and
i
Prepare phase. verification of the design takes place, by building 2
In this step, key decision makers identify the initial network.
requirements of network. = This step is performed during the implement phase of
A high-level conceptual architecture is proposed the PPDIOO.
3, Monitor and optionally redesign :
based on these requirements.
acterize the existing network and sites :
sep 2: Chare
This step consists of site and network audit and
network analysis.
thoroughly checked for
the network audit.
raffic, congestion is
The existing network is
integrity and quality during
The network behavior such as t
analyzed during the network analy
rk topology and sol
rk is generated in
sis.
ftep 3: Design the netwo! lutions ¢
The detailed design of the networ
:
‘the network is continuously monitored and checked
{or errors during the operation step.
1A network redesign can be required in case of
frequent troubleshooting problems othenvise it is
impossible to manage,
roid network redesign if al previous
d accurately.
Itis possible to ave
steps have been complete’
‘This step is apart of the operate and optimize phe ~The designe fly to design 2 network sk
after establishing’ the organizational requirements
and documenting the existing network.
= The designing of a large or even medium-sized
network can be a complex project.
= The procedures have been developed to make the
design process easy by dividing it into smaller and
more manageable steps.
= Approcess is made smooth by identifying the separate
steps or tasks to reduce the potential risk.
= A top-down design approach enables the designer to
see the big picture” before getting to the details.
= Due to top-down design approach, the design goal
becomes clear and it starts the design from the
viewpoint of the required applications.
~ Network devices are selected after a detailed analysis
of requirements.
= In very complex networks, the structured design
1s are combined with the top-down approach.
pra
= A bottom-up or connect-the-dots approach is a
contrast to top-down design in which network
devices and technologies‘ are selected first.
‘A bottom-up approach always results in an improper
\
network for the required services.
Y Bottom-up approach is used when a very quick
response to the design request is required.
