Administração e Gestão de Infra-Estruturas de IT IT Infrastructure Management and Administration

Mestrado
em Engenharia InformáDca e de Computadores

Master Degree (MSc) in InformaDon Systems and Computer Engineering
Administração e Gestão de Infra-estruturas de IT

IT Infrastructure Management and Administration
Design Process of IT Infrastructures
Requirements Analysis
Prof. Rui Santos Cruz

rui.s.cruz@tecnico.ulisboa.pt
TODAY Requirements Analysis 2
IT Infrastructure Network Planning
Design ObjecDve
Main Principles
Requirements gathering
Requirements analysis
3
Planning for the Future

Examining the various component technologies Some generally accepted
that make up the IT Infrastructure, the key task guidelines for expected
becomes combining them to make a funcDonal lifeDmes of various
soluDon. components of the 
IT Infrastructure are:
It is important to weight informaDon, desires and
constraints to design the most funcDonal, cost-‐
effecDve, efficient and future-‐proof  Component Useful Life
IT Infrastructure possible. Building/Pathways 50+ years
Cabling 20+ years
The best design pracDces should be used to Hardware 3 to 5 years
anDcipate and plan for some possible future uses
for the design.
4
Basic Building Block: Networking

One of the most criDcal Building
Blocks of the IT Infrastructure is the
Network.
A Network is a communicaDon

system that seamlessly and
efficiently connects voice, data,
video and other selected
applicaDons together.
5
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:
What stuff do we get for the IT network?
How do we connect it all?
How do we have to configure it to work right?
TradiDonally, this meant mostly capacity planning

– having enough bandwidth to keep data moving
May be effecDve… 

…but typically results in over engineering
ObjecDves Requirements Analysis 8
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:
Security, considering both internal and

external threats
Different types of connec;vity
Reliability and/or availability

The Main Phases of Network Design Requirements Analysis 9
Network Design Phases

Designing a network is typically broken into
three secDons…
Determine requirements
Define the overall architecture
Choose technology and specific devices
…by applying a systems methodology to

networking:
considering the Analysis, Architecture and

Design as Processes with Informa;on
Flows between them
Network analysis, architecture, and Design, Third EdiDon
The Main Phases of Network Design Requirements Analysis 10
Network Design Phases

Main Principles Requirements Analysis 11
Two Main Principles

For a network design to work well, we
need to balance between:
Hierarchy – how much network traffic

flows connect in Ders of the organisaDon
Diversity/Interconnec;vity – offsets
hierarchy by allowing connecDons
between levels of the design, to improve
performance between them
Two Main Principles

Levels of hierarchy and diversity.
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.
Diversity (a.k.a. redundancy or interconnecDvity) provides a mechanism to

achieve performance within a hierarchical structure
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.
Two Main Principles

Requirements Requirements Analysis 14
Requirements? Boring!
Yes, determining the requirements for a
network probably is not as much fun as
shopping for really expensive hardware
And that may be why many networks are

poorly designed – no one bothered to
think through their requirements!
Many people will jump to a specific

technology or hardware soluDon, without
fully considering other opDons – the
obvious soluDon may not be the best one
We need to develop the low level design and

the higher level architecture, and understand
the environment in which they operate
We also need to prove that the design we
have chosen is ‘just right’:
Is that €2 million network backbone really
enough to meet our needs?
How do we know €500,000 wouldn’t have
been good enough?
Requirements
Network analysis is important in that:
Helps us understand the complexity and nuances of each network and the
systems they support.
Provides data upon which various decisions are made
These data can and should be documented as part of an audit trail for the
architecture and design processes.
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.
Network requirements can be gathered and/or derived from customers,

applicaDons, services and devices
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
Part of this process is managing the
expectaDons from customers and
stakeholders
They may expect a much simpler or more

expensive soluDon than is really needed
Showing analysis of different design

opDons, technologies, or architectures
can help prove you have the best
soluDon
Requirements
We need to use a systems approach for
understanding the network
The system goes far beyond the network

hardware, sodware, etc.
Also includes understanding the internal users,

the services to customers, applicaDons or
services for the operaDon, and external
environments
How do these need to interact?
What does the he organisaDon  

expect from the network?
Requirements
Consider how devices communicate

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
What services are expected from the network?
Typical performance levels might include capacity,

delay Dme, reliability
Example: Providing 1.5 Mb/s peak capacity to a

remote user
Example: Guaranteeing a maximum round-‐trip delay

of 100 ms to servers in a server farm
Func;ons include security, accounDng, scheduling,

management
Example: Defining a security or privacy level for a

group of internal users (Financials, OperaDons) or for
a Customer organisaDon
Requirements
Service requirements can include
the QoS (quality of service)
guarantees (Intserv, Diffserv, etc.)
This connects to network

management monitoring of
network performance

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
The Analysis of the Requirements

Analysis Requirements Analysis 28
How do we describe requirements for a network?
Need a process to filter or classify requirements:
Network requirements  
(oden have high, medium, low prioriDes)
Future requirements  
(planned upgrades)
Rejected requirements  
(remember for future ref.)
Informa;onal requirements  
(ideas, not required)
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
What is ‘fast enough’ for download/

upload? System response (RTT)?
How good video streaming need to be?
Security/Privacy for Customer info?
What is my budget for CAPEX and OPEX?
CAPEX-‐ Capital Expenditures Network analysis, architecture, and Design, Third EdiDon
OPEX-‐ OperaDonal Expenditures

Application Requirements
What types of Apps/services are we using or
providing?
Mission-‐criDcal
Rate-‐criDcal
Real-‐Dme and/or interacDve
How sensiDve are apps to RMA? 

(Reliability, Maintainability, Availability)
What capacity is needed?
What delay Dme is acceptable?

What groups of apps are being used?
Telemetry/command and control -‐ remote devices
VisualizaDon and simulaDon
Distributed compuDng
Web development, access, and use
Bulk data transport – FTP
Teleservices – Legacy Voice, VOIP, teleconference
OperaDons, admin, maintenance, and provisioning:

OSS/BSS, DNS, SMTP, SNMP, AAA, etc.
Client-‐server – ERP, SCM, CRM

Where are the ApplicaDons located?
Are some only used in certain locaDons?

Device Requirements
What kinds of devices are on the network?
Generic compuDng devices include normal PCs, Macs,

laptops, handheld computers, workstaDons
Customer devices: Phones, Smartphones, Tablets,

Set-‐Top-‐Boxes, Computers, etc.
Core Networks Servers include all flavours of server: 

– file, print, App/ComputaDon, and backup
Specialised devices include extreme servers

(supercomputers, massively parallel servers), data
collecDon systems (POS terminals), industry-‐specific
devices, networked devices (cameras, tools),
stoplights, ATMs, etc.
Device Requirements
Specialised devices are oden

locaDon-‐specific!

Device Requirements
We want an understanding
of the device’s performance:
– its ability to process data
from the network
Device I/O rates
Delay Dme for performing

a given app funcDon

Device Requirements
Performance results from many factors
Storage performance, that is, flash, disk drive,  

or tape performance
Processor (CPU) performance
Memory (RAM) performance (access Dmes)
Bus performance (bus capacity and arbitraDon

efficiency)
OS performance (effecDveness of the protocol

stack and APIs)
Device driver performance

Device Requirements
The device locaDons are also
criDcal
Oden generic devices can

be grouped by their
quanDty
Servers and specialised

stuff are shown
individually

Network requirements (may sound
redundant…) are the requirements for
interac;ng with the exis;ng network(s)
and network management concerns!
Most networks have to integrate into an

exisDng network, and plan for the future
evoluDon of the network

Issues with network integra;on include
Scaling dependencies – how will the size

of the exisDng network affect the new
one?
Loca;on dependencies – interacDon

between old and new networks could
change the locaDon of key components
Performance constraints – exisDng

network could limit performance of the
new one
Network, system, and support service
dependencies: addressing, security, rouDng
protocols and network management can all
be affected by the exisDng network
Interoperability dependencies: changes in

technology or media at the interfaces
between networks need to be accounted for,
as well as QoS guarantees, if any
Network obsolescence: do protocols or

technologies become obsolete during
transiDon?
Network management and security issues
need to be addressed throughout
development
How will the network be monitored for

events?
Monitoring for network performance?  

— What is the hierarchy for management
data flow?
Network configura;on?
Troubleshoot support?
Security analysis can include
the severity (effect) of an
aYack, and its probability of
occurrence

Other Requirements
AddiDonal requirements can include:
Opera;onal suitability – how well can the

operaDons teams configure and monitor the system
or services?
Supportability – how well can the operaDons teams

maintain the system?
Confidence – what is the data loss rate when the

system is running at its required throughput? Are
customer Usage Records accurate?
Availability – What levels of Service are guaranteed

for Customers and from Partner Suppliers?
Other Requirements
Requirements can come from other outside
sources – customers, legal requirements,
Regulators, enterprise requirements,
financial, interconnecDons, etc.
Financial requirements can include not

only the iniDal system cost, but also
ongoing maintenance and upgrading costs
Enterprise requirements typically include

integraDon of the network with exisDng
standards for voice, data, or other protocols
Financial Requirements
Funding is oden bounded by an overall cost
limit, consisDng of both one-‐;me and
recurring components.
One-‐;me costs are based on the actual

planning and construcDon of the network
and consist of network architecture,
design, procurement, deployment,
integraDon, and tesDng, and all
hardware/sodware components, as well
as the iniDal installaDon or establishment
of any services from service providers.
Financial Requirements
Funding is oden bounded by an overall
cost limit, consisDng of both one-‐;me and
recurring components.
Recurring costs are for tasks and items

that are expected to occur or be
replaced/upgraded on a periodic basis.
This includes network OAM&P, costs
from service providers, and provisions for
modificaDons to the network.

Requirements Analysis 48
SUMMARY
The Main Principles when designing a
network
Systems approach on Requirements

gathering
ClassificaDon of Requirements for the

adequate Analysis
Any QuesDons? Requirements Analysis 49

Administração e Gestão de Infra-Estruturas de IT IT Infrastructure Management and Administration

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Administração e Gestão de Infra-Estruturas de IT IT Infrastructure Management and Administration

Hochgeladen von

Copyright:

Verfügbare Formate

Mestrado

em Engenharia InformáDca e de Computadores

Administração e Gestão de Infra-estruturas de IT

Prof. Rui Santos Cruz

IT Infrastructure Network Planning

Planning for the Future

Basic Building Block: Networking

A Network is a communicaDon

What stuﬀ do we get for the IT network?

How do we connect it all?

TradiDonally, this meant mostly capacity planning

May be eﬀecDve…

Security, considering both internal and

Diﬀerent types of connec;vity

Reliability and/or availability

Network Design Phases

Deﬁne the overall architecture

Choose technology and speciﬁc devices

…by applying a systems methodology to

considering the Analysis, Architecture and

Network Design Phases

Network analysis, architecture, and Design, Third EdiDon

Two Main Principles

Hierarchy – how much network traﬃc

Two Main Principles

Diversity (a.k.a. redundancy or interconnecDvity) provides a mechanism to

Two Main Principles

Network analysis, architecture, and Design, Third EdiDon

And that may be why many networks are

Many people will jump to a speciﬁc

We need to develop the low level design and

Provides data upon which various decisions are made

Network requirements can be gathered and/or derived from customers,

They may expect a much simpler or more

Showing analysis of diﬀerent design

The system goes far beyond the network

Also includes understanding the internal users,

How do these need to interact?

What does the he organisaDon

Consider how devices communicate

Typical performance levels might include capacity,

Example: Providing 1.5 Mb/s peak capacity to a

Example: Guaranteeing a maximum round-­‐trip delay

Func;ons include security, accounDng, scheduling,

Example: Deﬁning a security or privacy level for a

This connects to network

Network analysis, architecture, and Design, Third EdiDon

The Analysis of the Requirements

Need a process to ﬁlter or classify requirements:

Network analysis, architecture, and Design, Third EdiDon

What is ‘fast enough’ for download/

How good video streaming need to be?

Security/Privacy for Customer info?

What is my budget for CAPEX and OPEX?

OPEX-­‐ OperaDonal Expenditures

Real-­‐Dme and/or interacDve

How sensiDve are apps to RMA?

What capacity is needed?

What delay Dme is acceptable?

Telemetry/command and control -­‐ remote devices

VisualizaDon and simulaDon

Web development, access, and use

Bulk data transport – FTP

May be eﬀecDve… 

What does the he organisaDon  

Example: Guaranteeing a maximum round-‐trip delay

OPEX-‐ OperaDonal Expenditures

Real-‐Dme and/or interacDve

How sensiDve are apps to RMA? 

Telemetry/command and control -‐ remote devices

Client-‐server – ERP, SCM, CRM

Core Networks Servers include all ﬂavours of server: 

Storage performance, that is, ﬂash, disk drive,  

Monitoring for network performance?  

One-‐;me costs are based on the actual