Administração e Gestão de Infra-Estruturas de IT IT Infrastructure Management and Administration
Administração e Gestão de Infra-Estruturas de IT IT Infrastructure Management and Administration
Administração e Gestão de Infra-Estruturas de IT IT Infrastructure Management and Administration
Design ObjecDve
Main Principles
Requirements gathering
Requirements
analysis
3
Enterprise
Network
The
An
Enterprise
Network
can
be
Unique
simple
or
very
sophisDcated,
and
may
include
local
and
wide
area
Screen
networks
(LAN/WAN),
and
integrate
Mockup
different
types
of
systems,
such
as
Windows
and
Apple
computers
and
operaDng
systems
(OS),
Unix-‐like
systems
or
even
mainframes.
6
Data
Center
Network
The
A
Data
Center
Network
(DCN)
Unique
holds
a
pivotal
role
in
a
data
Screen
center,
and
needs
to
be
scalable
and
efficient
in
order
to
connect
Mockup
tens
or
even
hundreds
of
thousands
of
servers.
ObjecDves Requirements
Analysis 7
Design Objective
Our
IT
Infrastructure
design
must
answer
some
preYy
basic
quesDons:
How do we have to configure it to work right?
Design Objective
While
some
uses
of
the
network
(internal
users
or
customers)
will
need
a
lot
of
bandwidth
(e.g.,
mulDmedia
streaming),
we
may
also
need
to
address:
Determine requirements
Diversity/Interconnec;vity
–
offsets
hierarchy
by
allowing
connecDons
between
levels
of
the
design,
to
improve
performance
between
them
Main
Principles Requirements
Analysis 12
Hierarchy
is
the
degree
of
concentraDon
of
networks
or
traffic
flows
at
interconnecDon
points
within
the
network
Hierarchy is the number of Ders of interconnecDon points within the network.
Hierarchy
provides
structure
in
the
network,
diversity
balances
this
structure
by
interconnecDng
the
network
at
different
levels
in
the
design
to
provide
greater
performance
through
parts
of
the
network.
Main
Principles Requirements
Analysis 13
Requirements? Boring!
Yes,
determining
the
requirements
for
a
network
probably
is
not
as
much
fun
as
shopping
for
really
expensive
hardware
Requirements
Network
analysis
is
important
in
that:
Helps
us
understand
the
complexity
and
nuances
of
each
network
and
the
systems
they
support.
These
data
can
and
should
be
documented
as
part
of
an
audit
trail
for
the
architecture
and
design
processes.
Requirements Requirements
Analysis 17
Requirements
Such
data
(requirements,
metrics)
help
ensure
that
the
resulDng
architecture
and
design
are
defensible.
Network
requirements
are
requests
for
capabiliDes
in
the
network,
usually
in
terms
of
performance
and
funcDon,
which
are
necessary
for
the
success
of
that
network.
Requirements
Requirements,
in
conjuncDon
with
measurements
(on
the
exisDng
network)
are
used
to
derive
traffic
flows
(sets
of
network
traffic
that
have
some
common
aYributes,
such
as
source/desDnaDon
address,
informaDon
type,
rouDng,
or
other
end-‐to-‐end
informaDon)
Requirements Requirements
Analysis 19
Requirements
Part
of
this
process
is
managing
the
expectaDons
from
customers
and
stakeholders
Requirements
We
need
to
use
a
systems
approach
for
understanding
the
network
Requirements
Network
services,
are
defined
as
levels
of
performance
and
funcDon
in
the
network.
Two
perspecDves:
Services
offered
by
the
network
to
the
rest
of
the
system
(the
devices,
applicaDons,
and
users)
Sets
of
requirements
from
the
network
that
are
expected
by
the
users,
applicaDons,
or
devices
Requirements Requirements
Analysis 23
Requirements Requirements
Analysis 24
Requirements
What
services
are
expected
from
the
network?
Requirements
Service
requirements
can
include
the
QoS
(quality
of
service)
guarantees
(Intserv,
Diffserv,
etc.)
Requirements:
Capacity
refers
to
the
ability
to
transfer
data
100
%
of
Bandwidth
is
the
Throughput
is
the
Capacity
l
ea
theoreDcal
data
actual
capacity,
the
Id
Throughput
Actual
carrying
capacity
of
quanDty
of
error
a
circuit
in
some
free
data
part
of
the
network
transmiYed
per
unit
of
Dme
100
%
of
Capacity
Offered
Load
Requirements
Analysis 27
Requirements Analysis
How
do
we
describe
requirements
for
a
network?
Network
requirements
(oden
have
high,
medium,
low
prioriDes)
Future
requirements
(planned
upgrades)
Rejected
requirements
(remember
for
future
ref.)
Informa;onal
requirements
(ideas,
not
required)
Analysis Requirements
Analysis 29
Requirements Analysis
Requirements
can
come
from
many
aspects
of
the
network
system
User/Customer Requirements
Applica;on/Service Requirements
Device Requirements
Network Requirements
Other Requirements
User/Customer Requirements
User
requirements
are
oden
qualita;ve
and
very
high
level
CAPEX-‐ Capital Expenditures Network analysis, architecture, and Design, Third EdiDon
Application Requirements
What
types
of
Apps/services
are
we
using
or
providing?
Mission-‐criDcal
Rate-‐criDcal
Application Requirements
What
groups
of
apps
are
being
used?
Distributed compuDng
Application Requirements
Where
are
the
ApplicaDons
located?
Device Requirements
What
kinds
of
devices
are
on
the
network?
Device Requirements
Device Requirements
We
want
an
understanding
of
the
device’s
performance:
–
its
ability
to
process
data
from
the
network
Device Requirements
Performance
results
from
many
factors
Device Requirements
The
device
locaDons
are
also
criDcal
Network Requirements
Network
requirements
(may
sound
redundant…)
are
the
requirements
for
interac;ng
with
the
exis;ng
network(s)
and
network
management
concerns!
Network Requirements
Issues
with
network
integra;on
include
Network Requirements
Network,
system,
and
support
service
dependencies:
addressing,
security,
rouDng
protocols
and
network
management
can
all
be
affected
by
the
exisDng
network
Network Requirements
Network
management
and
security
issues
need
to
be
addressed
throughout
development
Network configura;on?
Troubleshoot
support?
Network
analysis,
architecture,
and
Design,
Third
EdiDon
Analysis Requirements
Analysis 43
Network Requirements
Security
analysis
can
include
the
severity
(effect)
of
an
aYack,
and
its
probability
of
occurrence
Other Requirements
AddiDonal
requirements
can
include:
Other Requirements
Requirements
can
come
from
other
outside
sources
–
customers,
legal
requirements,
Regulators,
enterprise
requirements,
financial,
interconnecDons,
etc.
Financial Requirements
Funding
is
oden
bounded
by
an
overall
cost
limit,
consisDng
of
both
one-‐;me
and
recurring
components.
Financial Requirements
Funding
is
oden
bounded
by
an
overall
cost
limit,
consisDng
of
both
one-‐;me
and
recurring
components.
SUMMARY
The
Main
Principles
when
designing
a
network