Telecommunications Infrastructures

and Operations

Unit 1 - Basic concepts

Network Management and Operations

Jesús Alcober, David Rincón

Dept. Enginyeria Telemàtica
September 2015
IOT – EETAC - UPC 1

Contents
• Network Management and Operations
• Why?
• Networks
• Heterogeneous networks, Real cases
• Services
• Evolution towards Virtualization
• SLA
• Management & monitoring protocols
• Models: TMN
• Role of Network Management in an organization
• Summary and Conclusions
IOT – EETAC - UPC 2
 Network Management
and Operations

Network Management and Operations

o Practical application of:

 Technology / Standards
 Processes
 Implementation Methods
 Operational Requirements

in the monitoring and management of

communications networks

IOT – EETAC - UPC 4

 Network Management

• In general, may refer to any of the

Operational Support Systems (OSS) or
functions in the ITU-T Telecommunications
Management Network (TMN) model

• More specifically, may refer to only the

Network Layer

IOT – EETAC - UPC 5

Why study this?

• Because Network Management Systems
(NMS) are critical
• Examples of some problems
o A videoconference crashes because terminals see
multicast traffic from external users
o A lack of hard disk capacity makes a video service
fail
o A misconfiguration of a VLAN in a switch produces
loss of connectivity
o A user is billed a wrong amount for his/her service

IOT – EETAC - UPC 6

 Our Mission
• Service, Service, Service
• No other phrase has the capability to remove
bureaucratic or financial barriers to solving a
problem than the phrase “service affecting”
• Our mission as network / service
managers is to maintain, activate and
manage service
• Service must be transparent

IOT – EETAC - UPC 7

Types of service?
• Networks
o Telephony (IP & POTS), Wireless telephony/data, connectivity to ISP,
LAN, MAN & WAN networks…
• Storage
o User data (Dropbox, Google, Cloud…)
o Data warehousing (DBs for business operations)
• Services - applications
o Business-related applications, Accounting/billing, Decision Support
Systems…
o Data centers with virtualized services, CDNs…
• Distributed services
o Smart cities, telemetering, smart electrical grid, mobility…

IOT – EETAC - UPC 8

 Information Management
• What kind of information do we manage?
o Wavelength assignments in optical networks, patch panel
mappings…
o Resource usage: link bandwidth, packet losses, delay…
o Routes / capacities / traffic engineering policies, VLANs,
VPNs…
o Mean Time Between Failures (MTBF) & Mean Time To Repair
(MTTR)
o Serial Numbers, Router configuration files…
o Service performance, billing, accounting…
o Alarms
…and the list goes on!

IOT – EETAC - UPC 9

Management Tools
• What kind of management tools do we use?
o Monitoring of
o Equipment
o Services
o Fault Management Systems (FMS)
o Trouble Ticketing
o Workflow
o Provisioning
o Documentation
o .....

IOT – EETAC - UPC 10

 Hey, what about money?
• A bunch of acronyms you’ll have to know and use…
• CAPEX
• Capital Expenses / expenditure
• Initial investment in infrastructure
• OPEX
• Operational Expenses
• Continuous expenditure
• Equipment amortization
• Spreading payments over multiple periods
• Data centers example: OPEX depreciated in 4 years, CAPEX in 15 y
• ROI
• Return on investment Gain  Cost
• Evaluates the efficiency of the investment
ROI 
Cost
IOT – EETAC - UPC 11

Hey, what about money? (2)

• Other terms you will hear
1) Long tail markets
What we used to call “niche”

2) Two-sided markets
Did you know that CDNs are a two-sided market?

3) Churn (actually, “churn rate”)

Migration of subscribers between operators.
What does a churn rate of 25% mean in 4 years?

Exercise: search, read and discuss

IOT – EETAC - UPC 12

 Hey, what about laws?
• Regulation and legislation MUST be taken in
consideration
• Spectrum usage, radiation emission…
• Infrastructure legal and physical constraints
• What can be and cannot be done with certain user data
• Personal Data Protection
• Data Conservation Laws for operators – Police & judges
• Quality of service (QoS) parameters that you must reach
independently of the contract
• Network neutrality Exercise: take a look
… at the CNMC-Telecos
webpage and blog
IOT – EETAC - UPC 13

Functional Groups
• What functional groups might be involved in
“Network Management”?
o Planning – design (aka “Engineering”)
o Construction – deployment
o RedIRIS example
o Service provisioning
o GÉANT example
o Operation - NOC (Network Operation Center)
o Deutsche Telekom example
o Accounting / billing
o Commercial: new services, sales…
o Who else?
Technical job profiles!
IOT – EETAC - UPC 14
 Deutsche Telekom NOC (Bamberg, Germany, 2005)
NOCs

Slide #10

IOT – EETAC - UPC 15

Networks
 Networks
• Legacy
o Class 5/4 switching (analogue telephony)
o SS7
o POTS/ISDN
o ATM
o Older LANs (token ring, token bus, collision-
based Ethernet)

IOT – EETAC - UPC 17

Networks
• Legacy
• Enterprise
o Advanced Ethernet (Giga / 10Giga / 40-100Giga)
o VLANs, QoS - prioritization
o IP
o VPNs, QoS - prioritization
o MPLS
o Wireless (WLAN, WiMax, 3G/4G)
o Application Servers / Databases
o Internet / Intranet

IOT – EETAC - UPC 18

 Networks
• Legacy
• Enterprise
• Transport
o SONET-SDH
o Carrier Ethernet / Metro Ethernet
o Lightwave, optical circuits, MPλS
o Microwave
o Personal /enterprise wireless (WLAN, WiMax, 3G/4G)
o Fiber plant
o Dark/lit fiber
o Traffic engineering!
IOT – EETAC - UPC 19

A Heterogeneous Network

Circuit / POTS

IP / ATM / MPLS
Metro Ethernet /SDN

SONET-SDH /
Carrier Ethernet / SDN

Servers,
DWDM / Wavelength (optical services… IaaS,
circuits) / Dark & lit fiber PaaS, SaaS

IOT – EETAC - UPC 20

 A Heterogeneous Scenario
o Network Heterogeneity
o GÉANT example
o What management protocols might be present?
o We’ll see and study a nice list
o How is end-to-end service provisioned?
o GÉANT optical circuits example
o Does a fiber cut affect all services?
o RedIris 10 example
o How is an IP service billed?
o Pricing (IOT-OE)
o How is QoS measured? What applications / parameters
might be monitored?
o SLA, Hibernia example
o Capacity needed? → ADX, PX
o Is security ensured? → SX

IOT – EETAC - UPC 21

Internet 2 (Abilene, 2010)

22
 Internet 2 (Abilene, 2012)

23

Example: GÉANT network

• European Research and Education Network
o Backbone for the National RENs
o RedIris in Spain, RENATER (France), Janet (UK)…
o 23 countries, but only 18 routers
o BGP peering with NRENs
o Political / technical / economical reasons
o Heterogeneous backbone
o Network: SDH/SONET + Ethernet + optical circuits
o Services: IP connectivity, permanent (CERN) and on-
demand optical services (lambdas)

Visit GÉANT website: services offered, network topology

IOT – EETAC - UPC 24
Concepts: dark fibre, lit fibre,
managed wavelength
GÉANT
GÉANT’s Layer 1/2 topology

27
 GÉANT monitoring tools
• Circuits information
• IP/MPLS, SDH, WDM
• Points of Presence (PoP) information
• Equipment, status…
• Reports
• Statistics: availability, usage…
• Weathermap
• Link loads
• Looking glass (router commands)

Demo of GÉANT Tools website

IOT – EETAC - UPC 29

RedIris 10 (up to 2010)

30
 RedIris 10 routing
• Routes to BCN
– MAD IR2 BCN – PLM BCN
– IR2 BCN – PMP ZAR BCN
– IR4 IR2 BCN – RIO ZAR BCN
– BAD SEV VAL BCN – STD BIL PMP ZAR BCN
– BCN – STG IR2 BCN
– BIL PMP ZAR BCN – SEV VAL BCN
– CRE SEV VAL BCN – TEN IR4 IR2 BCN
– LSP SEV VAL BCN – VAL BCN
– MUR VAL BCN – VDL IR4 IR2 BCN
– OVI STG IR2 BCN – ZAR BCN
Exercises: 1) Draw routes 2) can you infer Traffic Policies? 31

RedIris 10 Weathermap

32
 RedIris 10 Weathermap

33

RedIris Nova (2011)

Transmisión óptica hasta 80 canales x 10Gbps sobre una red propia de 14.000
km de fibra oscura iluminada con fotónica TROADM de última generación

Infraestructura de fibra
11.500 km de fibra óptica G.652-D de nuevo despliegue (2010) en la península
2.000 km de fibra óptica submarina G.655, de nuevo despliegue (2011) con las Islas Canarias.
Infraestructura de fibra contratada por mas de una década:
hasta el año 2032 para la fibra peninsular y
hasta el año 2042 para la fibra de Canarias
53 Puntos de Presencia o PdPs con capacidad para insertar/extraer portadoras ópticas
hasta 80 canales de 10Gbps en los PdPs penínsulares
hasta 128 canales para los PdPs en Canarias
121 Puntos de Alojamiento Intermedios o PAIs donde se amplifica la señal óptica.
89 enlaces de fibra (3 de los cuales son submarinos) formando 19 anillos de fibra.

Servicios sobre la red óptica: Red Híbrida para enrutar paquetes y conmutar circuitos:
Transmisión y conmutación de circuitos dedicados 10Gbps y redes Ethernet.
Servicio de conectividad global IPv4 e IPv6, con una red troncal mallada a 20Gbps.
34
Soporte de multicast nativo
RedIris Nova (2011)

35

RedIris Nova (2012)

36
 RedIris Nova (2011)
Red Troncal IP
RedIRIS pone a disposición de sus instituciones afiliadas una red troncal IP de alta
capacidad, con un backbone a 20Gbps, direccionamiento IPv4 e IPv6 y Multicast.
RedIRIS-NOVA transporta el acceso de las instituciones, a traves de canales
ópticos 10Gbps, a uno de los puntos de presencia IP de la red troncal. La
redundancia se configura a nivel IP (verde), con BGP y dos accesos diversificados
a dos puntos de presencia IP. O bien, el acceso IP se protege en la capa óptica,
manteniendo un acceso IP, pero con dos rutas ópticas diversificadas (rosa).

Conectividad Externa
Esta accesibilidad se obtiene a través de la conexión con la red pan-europea de
investigación GEANT, de la cual RedIRIS forma parte.
La conectividad externa de RedIRIS se completa a través de la interconexión con
proveedores comerciales o ISPs. A nivel nacional, con la conexión a los dos puntos
neutros de intercambio de tráfico comercial de Internet en España: ESPANIX (en
Madrid) y CATNIX (en Barcelona); y, a nivel internacional, por medio de contratos
con proveedores de tránsito de ámbito mundial.
37

RedIris Nova – IP / BGP

38
 RedIris Nova – weathermap (Feb’12)

39

RedIris Nova – weathermap (Sept’12)

40
Exercise: check weathermap and http://www.rediris-nova.es
 RedIRIS Nova Fiber’s Economy Model
“El Gobierno Español ostenta un derecho de uso
sobre la infraestructura óptica en modelo IRU, por
un periodo de 21 años para la infraestructura de
ámbito peninsular, y de 30 años para la
infraestructura que permite unir la Península con
Canarias.”

• What is an IRU model?

Exercise: read about
• Why is it used? IRUs and discuss

IOT – EETAC - UPC 41

Services
 Services
• Network access /connectivity
• Content delivery & sharing
• HTTP, IPTV, P2P… Youtube/Spotify… social
networking… collaborative work
• (networked) Applications
• Wireless apps → big market now!
• Wired too, but converging
• Data centers
• Virtualization of tasks, machines, and even networks!
• Cloud (Gmail, Amazon)… Software Defined Networks…

IOT – EETAC - UPC 43

Evolution of services…

Backbone Traffic Projections on USA

3
10

2
10
Traffic (Tb/s)

1
10

0
10 P2P

10
-1 Wireless Voice

-2
10
2010 2015 2020
Year

15
 … towards Virtualization
• Virtualization
– Technological maturity allows network devices (routers,
switches, storage and computing elements ...) to be virtualized.
The user requires a specific service and the provider offers the “tailored”
resources (i.e., what the user exactly needs), obtained as a composition of
elementary services.

Software, platform or infrastructure offered as

a service (SaaS, PaaS, IaaS)
• Google App ..
• Windows Azure,. Net Exercise: read about
• Cloud Computing, Amazon EC2, S3,.. Amazon EC2
• Software Defined Networking, OpenFlow
45

Virtualization, Cloud & SDN

Functionalities Functionalities Functionalities Functionalities

IP Communications IP Communications

OS OS OS + Distributed Control Plane

Specialized Specialized Specialized Specialized
hardware hardware hardware hardware
Applications

Network elements
Communications IP SDN
Operating
Processors
System

Hardware Applications Applications Applications

Monolithic
process
Communications Communications Communications
... Communications

storage OS OS OS OS
and
communication Hardware
architectures Hypervisor Hypervisor (for example, Vmware)

Hardware Hardware Hardware

Virtualization Cloud 46
 Cloud Computing
Cloud is a type of parallel distributed system that comprises a collection of virtualized
computers that are presented as a unique and dynamic computing and storage
resource based on an SLA between the service provider and the consumer on internet

Software as a Service SaaS

of QoS and SLA

Billing and price

Monitorization
• Google Apps
• Salesforce
• Web 2.0
• Programming APIs

Platform as a Service PaaS

SLA negotiation

Security
• Microsoft Azure
• Aneka
• Google AppEngine

Infrastructure as a Service IaaS

Admission control

Accountability
• Virtualization
• Eucaliptus
• OpenNebula, OpenNaaS
• Amazon S3, EC2
• VMware Data centers Grid Storage

47

Service Level
Agreement (SLA)
 Service Level Agreement (SLA)
• Agreement between customer and provider
• Parameters to be measured, assured levels, margins
• It also defines procedures, penalties/discounts
• Applied to both Networks and Services

• Service Level Objectives (SLOs)

• Some are related to service performance
• Availability, BW, delay, jitter, losses, MTTR…
• Some are related to operational support
• Time to report issues, ticket escalation procedures…

IOT – EETAC - UPC 49

Service Level Agreement (SLA)

• Network SLA
• QoS parameters
• BW, delay, jitter, losses
• Examples: ADSL quality report, EBU audiovisual SLA
• Availability:
• The “rule of the 5 nines”: 99.999% (high), but also
99.99% (medium) and 99% - 99.9% (low)
• MTBF, MTTR

Availability – XLAM examples

IOT – EETAC - UPC

Examples of Network SLAs 50
 Service Level Agreement (SLA)
• Service SLA
• It depends a lot on the actual service
• Example, a virtualized web server
• Service parameters
• Requests/second
• Bandwidth
• Availability:
• Critical in the case of services!!
• Backup recovery time
• Hot standby, cold standby, no standby

EBU document about SLAs for audiovisual services

IOT – EETAC - UPC

RedIris NOVA SLA – escalation 51

Management and
monitoring protocols
 Management Protocols (legacy)

• SNMP
• Q3
• TL1
• CORBA
• CMIP
• Proprietary

IOT – EETAC - UPC 53

Management Protocols (modern)

• Netconf
• Yang
• Openflow
• BGP
• ALTO

Context: SDN

IOT – EETAC - UPC 54

 Monitoring Protocols and Applications
• Traffic monitoring
• SNMP – link loads
• Traffic flows
• Netflow, Jflow, Sflow – see next slide
• Traffic matrices – Critical information for network planning, traffic
engineering and routing !!
• Route monitoring / Route Analytics
• Do you really control BGP / IGP decisions? Equal Cost multipath
• Weathermap
• Looking Glass
• Databases
• Usually multi-scale, Round Robin Database
• Popular applications: Cacti, RRDtool, pmacct

IOT – EETAC - UPC Exercise: GÉANT monitoring tools 55

Example of NetFlow records

ivan@debian:~/tfc$ nfdump -r nfcap.v05.2010-01-17.122522+0100

Date flow start Duration Proto Src IP Addr:Port Dst IP Addr:Port Packets Bytes Flows
2010-01-17 09:15:48.372 0.000 TCP 222.35.136.xxx:45034 -> 193.144.51.xxx:22 1 68 1
2010-01-17 09:15:15.094 0.000 TCP 222.35.136.xxx:34767 -> 193.144.51.xxx:22 1 56 1
2010-01-17 09:15:19.949 0.000 TCP 222.35.136.xxx:47396 -> 193.144.51.xxx:22 1 72 1
2010-01-17 09:15:24.389 0.000 TCP 222.35.136.xxx:58955 -> 193.144.50.xxx:22 1 52 1
2010-01-17 09:15:01.676 0.000 TCP 222.35.136.xxx:35393 -> 193.144.51.xxx:22 1 68 1
2010-01-17 09:15:06.645 0.000 TCP 222.35.136.xxx:39575 -> 193.144.51.xxx:22 1 104 1
2010-01-17 09:15:15.422 0.000 TCP 222.35.136.xxx:48114 -> 193.144.51.xxx:22 1 196 1
2010-01-17 09:15:40.862 0.000 TCP 222.35.136.xxx:37147 -> 193.144.51.xxx:22 1 72 1
2010-01-17 09:15:43.738 0.000 TCP 222.35.136.xxx:40600 -> 193.144.62.xxx:22 1 52 1
2010-01-17 09:15:14.707 0.000 TCP 222.35.136.xxx:35618 -> 193.144.51.xxx:22 1 104 1
2010-01-17 09:15:32.677 0.000 TCP 222.35.136.xxx:43662 -> 193.144.51.xxx:22 1 60 1
2010-01-17 09:15:31.801 0.000 TCP 222.35.136.xxx:50149 -> 193.144.62.xxx:22 1 136 1
2010-01-17 09:15:51.729 0.000 TCP 95.108.157.xxx:54060 -> 193.146.208.xx:80 1 52 1
2010-01-17 09:15:12.298 0.000 TCP 77.196.162.xxx:53687 -> 193.144.57.xxx:6000 1 1188 1
2010-01-17 09:15:22.033 0.446 TCP 194.169.201.xxx:80 -> 193.144.79.xxx:26505 8 12000 1
2010-01-17 09:15:38.694 0.000 TCP 81.184.8.xxx:51260 -> 193.146.43.xxx:38787 1 54 1
2010-01-17 09:15:06.122 40.614 TCP 85.56.18.xxx:26215 -> 193.146.38.xx:64613 4 4516 1
2010-01-17 09:15:22.033 0.000 TCP 85.56.18.xxx:26215 -> 193.146.38.xx:64613 1 465 1
2010-01-17 09:15:02.196 55.011 TCP 82.60.18.xxx:57563 -> 193.144.56.xxx:11629 16 652 1
2010-01-17 09:15:01.676 0.000 UDP 188.128.29.xxx:24370 -> 193.146.32.xx:53 1 73 1
2010-01-17 09:15:05.943 51.187 TCP 193.144.56.xxx:11629 -> 85.179.88.x:1951 7 10178 1
2010-01-17 09:15:17.911 39.219 TCP 193.144.56.xxx:11629 -> 85.179.88.x:1951 4 2899 1
 Traffic matrices
STTL

NYCM
CHIN
DNVR
WASH
SNVA IPLS
KSCY
ATLA
LOSA ATLA-M5

HSTN

Abilene topology (2004)

Example: Abilene traffic matrix

ATLA-M5
WASH
NYCM
DNVR
KSCY
HSTN
SNVA
LOSA

ATLA

CHIN
IPLS
STTL

80 Mbps
STTL
SNVA
DNVR 60 Mbps
LOSA
KSCY
HSTN
40 Mbps
IPLS
ATLA
CHIN
20 Mbps
NYCM
WASH
ATLA-M5 0 Mbps

Traffic matrix from Abilene (March 2nd 2004, 12:00-12:05)

 Functional models:
TMN

Functional Models for Network

Management
• Examples
o OSI / Internet
o TMN

• Purpose
o Break complex systems and concepts into
manageable modules with well-defined
interfaces
o Support re-use and interaction between
heterogeneous systems

IOT – EETAC - UPC 60

 Networks - OSI Model
• Application
• Presentation
• Session
• Transport
• Network
• Data Link
• Physical

IOT – EETAC - UPC 61

OSI Model benefits

• Well defined protocol interfaces enable us
to:
o Run multiple protocols (IP, IPX) over Ethernet
o Run multiple applications (P2P, IPtel, IPTV,
HTTP, FTP, Telnet) over IP
o Run IP over SDH/SONET
o ….and so on….
o The TMN model is designed to promote the
same kind of interworking in the management
domain

IOT – EETAC - UPC 62

 Networks - TMN Model
• Protocol model defined by ITU-T
for managing open systems in a
communications network

More Specific
More Generic
o Network Element / Equipment
o Element Management
o Network Management
o Service Management
o Business Management

ITU-T M.3010

IOT – EETAC - UPC 63

Networks - TMN Model

• Network Element / Equipment Layer
o Provides agent services, mapping the physical
aspects of the equipment into the TMN
framework
 Lowest level of the hierarchy
 Includes the network equipment + any craft/direct
interface to controlling the functions of the
equipment
 Historically, manual controls, ASCII text / terminal
interface
 Interfaces to support element management

IOT – EETAC - UPC 64

 Networks - TMN Model
• Element Management Layer
o Contains functions for the handling of individual
network elements
 Alarm management, handling of information,
backup, logging, and maintenance of hardware and
software.
 Control of multiple instances of network equipment,
often of the same type or class
 Many times a GUI interface as a front-end to a text-
based CLI (Command Line Interface) – SNMP too
 Interfaces to support Network Management

IOT – EETAC - UPC 65

Networks - TMN Model

• Network Management Layer
o Performs functions for distribution of network
resources
 configuration, control and supervision of the
network.
 May be homogeneous or heterogeneous
equipment/technology
 Comprises a view of multiple systems working
together
 Interfaces to support Service Level Management

IOT – EETAC - UPC 66

 Networks - TMN Model
• Service Management Layer
o Performs functions for the handling of services
in the network
 definition, administration and charging of services.
 Individual networks and components are now
abstracted to view services rather than networks or
equipment
 Interfaces with customers and contracts (Service
Level Agreements)
 Interfaces to support Business Layer Management

IOT – EETAC - UPC 67

Networks - TMN Model

• Business Management Layer
o Performs functions related to business aspects,
analyzes trends and quality issues, for example,
or to provide a basis for billing and other
financial reports.
 Provides a overall business perspective to the
networks and services being managed.
 For example, Return On Investment applications
and forecasts may operate at this layer. In other
words, “Is this network making money?”

IOT – EETAC - UPC 68

 Where to go for more info…
• www.itu.org
• www.ietf.org
• www.tmforum.org

IOT – EETAC - UPC 69

Models going forward….

• As we examine different systems, try to
evaluate them by which layer and function(s)
they cover in the TMN model.
• This will become our basis for identifying
implementation issues and limitations.
• Models are an abstraction of things in the
real world – where is this beneficial, where
does it become a problem?

IOT – EETAC - UPC 70

 Catch!
• The need to abstract heterogeneous
networks to a generic management system
Versus
• The need to manage specific capabilities of
equipment

IOT – EETAC - UPC 71

Role of Network
Management in an
organization
 Network Management
• Technology Pressures
• Organizational

TECH
Pressures
• Cost Pressures
• Regulatory Pressures COST ORG

REG
Slide #30

IOT – EETAC - UPC 73

Network Management
• Are Network Management/OSS functions
typically cost centers or profit centers?
• Why?
• Is it possible to have ROI on OSS?

IOT – EETAC - UPC 74

 Costs
• Hardware
• Software
• Personnel
• Training
• What else?

IOT – EETAC - UPC 75

Sample Costs
• NMS Servers $200K
• Routers $120K
• OSS Software $1,000K
• Personnel (24x7) $1,250K
• Training $50K
• Communications $150K

IOT – EETAC - UPC 76

 Return on Investment (ROI)
• What does effective Network Management
buy?
o SLA compliance
o Customer satisfaction
o Competitive edge
o What else?

IOT – EETAC - UPC 77

Return on Investment (ROI)

• Will saving 10% on a contract by meeting an
SLA pay for a network management
system?
• Will advanced services such as self-
provisioning, instant activation, etc. pull
through additional business?
• Will field forces be deployed more efficiently,
saving travel expenses?
Exercise: Document about the ROI
of network management
IOT – EETAC - UPC 78
 Costs of ineffective management
• Fines
• Lost customers
• Contract penalties
• Capacity waste
• What else?

IOT – EETAC - UPC 79

Is there a “Silver Bullet”?

• Definitely not

• However, by emphasizing
an “integrated approach”,
we can maximize the value
of our management
systems and processes.

IOT – EETAC - UPC 80

 An “Integrated Approach”
• An Integrated Model
o Tools
o Organizations
o Processes
o People

IOT – EETAC - UPC 81

Integrated Model - Tools

• Fault Management Systems - monitoring
• Provisioning Systems
• Accounting
• Customer Care
• Documentation
• Workflow

IOT – EETAC - UPC 82

 Integrated Model - Organizations
• Effective designation of roles and
responsibilities
• Established procedures and methods of
communication
• Accountability
• Cohesive action
• Common goals

IOT – EETAC - UPC 83

Integrated Model - Processes

• Clear, accessible procedures for:
o Emergencies
o Repair
o Forecasting
o Escalation
o Security
o Service Activation – provisioning

IOT – EETAC - UPC 84

 Integrated Model - People
• People make it all work (or not work)
o Training
o Motivation
o Scheduling
o Logistics (travel, expenses)
o Costs

IOT – EETAC - UPC 85

Network Management Blueprint

Personnel
Requirements

Training

Organization

Tools Processes

IOT – EETAC - UPC 86

 OSS vendors
• Telcordia • Ceon
• Cramer Systems • Sigma Systems
• Granite • Astracon
• Visionael • HarmonyCOM
• Metasolv • Syndesis
• NetCracker • CoManage
• Emperative • Agilent
• Eftia • Orchestream
• Circuit Vision • Many, many more….

IOT – EETAC - UPC 87

Summary and
Conclusions
 Summary
• Importance of Network Management and
Operations
• Networks: heterogeneity
• Services: virtualization is the trend
• SLAs: concept & parameters
• Management & Monitoring protocols
• TMN as a model for understanding
management protocols and architectures

IOT – EETAC - UPC 89

Conclusions

• Network Management and Operations

o Technical, Economical, Social and Political
constraints
o Complex!! But cheer up - it is a lot of fun, and
job opportunities!

o IOT: just an introduction to what you’ll find in

the “real world”
o Anyway, the “real world” in telecommunications
is changing and evolving – you’ll learn there!

IOT – EETAC - UPC 90