03 dimensions

7/30/2019 03 Dimensions

1/47

Spring 2013

Bahador Bakhshi

CE & IT Department, Amirkabir University of Technology

This presentation is based on the slides listed in references.


2/47

Outline

Introduction

LifecycleInteroperability

Layers

unc ons

Summar

2


3/47

Outline

Introduction


Layers

unc ons

Summar

3


4/47

Introduction

Management dimensionsa es eas er o e ne a sys emc approac o so vng a ne wor

management problem

: Network

4


5/47

Introduction (contd)

Important fact:

These dimensions are (almost) orthogonal

xampes

It does not matter witch technology is managed

The management protocols must be interoperable

The management functionalities are needed

5


6/47

Outline

Introduction


Layers

unc ons

Summar

6


7/47

Network Lifecycle

7


8/47

Network Lifecycle (contd)

Planning

orecas user servce nee s, equpmen seec on,topology planning,

Deployment

Equipment installation and turn-up, physical setup, wiring,

logical setup and initial configuration

What is normally associated with network management

Decommissioning

Opposite of deployment, early notification of users if

affected, graceful shutdown, cutover of traffic, 8


9/47

Network Management Lifecycle

While the network management mainly implies the

However, each step of network lifecycle needs its own, . .,

Network installation & documentation in Deployment

Decommissioning phase

,lifecycle in a operational network

e wor managemen

To manage the network lifecycle

Is evolved in the lifecycle as a part of network9


10/47

Outline

Introduction


Layers

unc ons

Summar

10


11/47

Management Interoperabilit

NM is a distributed application, hence

A central challenge: How are systems involved

in mana ement able to intero erate Managing systems with managed systems

La er 3 connectivit is not sufficient L7 rotocols

Management applications with each other

Requires agreed-upon rules for interactions Standard management interfaces and protocols

11


12/47

Management Interoperability (contd)

Aspects of management interoperability

12


13/47

Communication Viewpoint

NM at the most basic level, is implemented by messages

Connectivity (e.g. IP) is a prerequisite but not sufficient IP connectivity: manager and agent can hear each other

Does not mean they speak the same language, or understand each

Generally involves a management protocol

How is a management session established? What underlying transport do you use?

How do ou authenticate?

13


14/47

Communication Viewpoint (contd)

How do you identify the request you havepus, w a parame ers are requre

How do you recognize a response to a request

s a tme stamp requre plus, whats the format there are dozens of them

ow s e message enco e XML? UTF-8?

a wo messages w e same reques are rece ve Execute the same request twice, or ignore?

What happens if a response is not received after a certain

14


15/47

Function Viewpoint

Describes the services a manager can expect from an agent

as c servces

Retrieve a piece of information

Modif a confi uration

Initiate an action

Receive an event

Advanced services (examples) Transaction support: commit and roll back multiple operations as if they

were one

Event subscription: receive only events of interest

Search and filter

Communication protocol defines the message that are beingexchanged to perform the function Advanced functions are im lemented throu h multi le mana ement rimitives

15


16/47

Information Viewpoint

The context of network management

A common terminology between manager and agent

Without a common terminology, no management interoperability

Meta model: the modeling constructs at your disposal todefine the model by which the managed system is referred to

Object oriented: collection of objects Data oriented, table oriented: entries and columns of tables

omman oren e : comman s an comman parame ers

Model: the actual representation of a type of managed. . , ,

Standards specifies the meta model

Model of MOs of an agent is given by vendor16


17/47

The Role of Standards

Goal: align the way in which things are managed

Its all about interoperability

,

Different vendors, Different device types, Different OS

Less time, cost to integrate

What to standardize

Management messages, encoding of information Functions, parameters, return codes

Management information (typically, meta-models)

17


18/47

NM Standardization Bodies

Numerous standards bodies, sometimes competing

Industry consortia

TeleManagement Forum (TMF), DSL Forum, DesktopMana ement Taskforce DMTF

Professional organizations

Members are individuals of a profession

IEEE,

Government-sanctioned bodies

-

18


19/47

Outline

Introduction

Lifecycle

Interoperability

Layers

unc ons

Summar

19


20/47

TMN: as an example of layering

TMN (Telecommunication Management Network) It is much more then just a network management layering

Problem

e erogeneous managemen sys ems orheterogeneous technologies

Standardized management network with alignedmana ement s stems for hetero eneous networks

Currently as e commerc a re evance

Used as reference model

20


21/47

TMN Layers

21


22/47

TMN Layers: Network Element

It is a manageable network device

It means the management agent

It provides agent services, mapping the

TMN framework

Get management parameters

Set management parameters (configuration) Alarm generation

22


23/47

TMN Layers: Element Management

Vendor specific management functions

Hides these differentiations from the Network Management

Detection of equipment errors

Measuring the resources that are being used

- , , .

Logging of statistical data

23


24/47

TMN Layers: Network Management

To manage the functions related to the interaction between

Involves with keeping the network running as a whole (end-o-en

Examples of functions

Creation of the complete network view Creation of dedicated paths through the network to support the QoS

Modification of routing tables

Monitoring of link utilization

Optimizing network performance

Detection of faults

24


25/47

TMN Layers: Service Management

Is concerned with management of those aspects that may

These users may be end users (customers) but also other service

roviders

Managing the services that the network provides andensurin those services are runnin smoothl

Service Provisioning and SLA guarantee

Quality of Service management (delay, loss, etc.)

Accounting

Addition and removal of users

Address assignment

25


26/47

TMN Layers: Business Management

It is responsible for the management of the wholeen erprse

management

Examples of functions

Billing and invoicing

Help desk management Business forecasting

26


27/47

TMN Layers

27


28/47

Considerations

Different layers are often handled by differentorganza ons; exampe

Technical layering can influence how a business isstructured and define its business relationships

For example, a transport provider might provide physical lines

and transmission equipment Network service providers provide voice or data services,

The multiple-layer approach is sometimes criticized management solutions consisting of multiple systems each

working at a different layer cause an integration difficult, costly

28

O li


29/47

Outline

Introduction

Lifecycle

Interoperability

Layersunc ons

Summar

29

F ti l Vi i t


30/47

Functional Viewpoint

Categorization of different management tasksypca y s are s m ar c arac ers cs an requremen s

Often addressed by management applications

Examples of categorization

Starting point: Common functions/ purposes of management tools

OAM&P (popular in telco world)

Starting point: Common structure of organizations running a network

Other categorizations are possible E.g. Fu ment, Assurance, B ng Teemanagemen Forum

E.g. FCAPS + Change Management (former IBM)

30

FCAPS l f f ti


31/47

FCAPS: as an example of functions

First articulated in ITU-T TMN Reference Model

Popular in datacommworld

Configuration

Accounting

Security

31

F lt M t


32/47

Fault Management

Functions related to dealing with faults in network

Monitoring networks and services for faults

Reacting to faults when they occur Managing resolution of faults

Being proactive about preventing faults before they occur

Important fault management functions

Fault diagnosis

Proactive fault management

32

C fi ti M t


33/47

Configuration Management

Functions related to dealing with how network, services,

Physical configuration, e.g.

Equipment, line cards, physical connectivit Logical configuration, e.g.

Protocol settings, logical interfaces, address assignments,,

Important configuration management functions Inventory

Auditing, Discovery, Auto-discovery

Image management

Backup and restore

33

C fi ti M t P i i i


34/47

Configuration Management: Provisioning

Provisioning: The steps required to set up networkan sys em resources o prov e, mo y, or revo ea network service Resources:

Bandwidth, CPU, Memory, Port assignments, Addressassignments (IP addresses, phone numbers, ..),

Scope: Individual s stems e ui ment rovisionin

E.g. set up a firewall

Coordinated configuration changes across multiple systems

Often re uired to rovide an end-to-end service

34

Accounting Management


35/47

Accounting Management

Account for usage of communicationresources and services

by whom at what time

consumed

Often forgotten but arguably the most

No accounting management, no revenue

ven as a user nee o now w a you pay o

35

Performance Management


36/47

Performance Management

Performance management taskson orng per ormance an servce eve s

Detecting performance trends, degradations

Common support functions

Accuracy, calibration, sampling considerations as common issues

Collection of performance data

Often, large volumes of data

Sampling as a common technique to address scale concerns Visualization of large data sets

Charts, histograms, etc

36

Security Management


37/47

Security Management

Management of security mechanisms, e.g.

ACL management

Consistency between routers on a network

Size of ACLs

Intrusion detection systems

Learning of patterns

How to rotect a ainst hitherto unknownpatterns

ys em secur y, an -vrus, 37

Time Horizon


38/47

Time Horizon

Short-term managementn e sca e o mnu e, secon or even near rea - me au oma e

Network monitoring

Medium-term management

Service provisioning, Fault elimination, Performance reporting

- In the scale of weeks or even month, mainly performed by human with

software assist Enhance management workflows, future (capacity) planning and

strategies

38

Outline


39/47

Outline

Introduction

Lifecycle

Interoperability

Layersunc ons

Summar

39

Management Organization & Process


40/47

Management Organization & Process

The nontechnical dimension of network management,

How to organize management

smoothly and reliably

The function life c cle and mana ement dimensions

described earlier can provide guidance for organizingmanagement

Standard procedures must be established and followed

for the network to run smoothl A lack of documented standard operating procedures can cause

problems because of: Inconsistent configurations, Troubleshooting,

40

TOM & eTOM


41/47

TOM & eTOM

Telecommunication Operation Map

TOM distinguishes among three life cycle stages FAB (Fulfillment,

Assurance, Billing) Fulfillment ensure that a service order that was received is carried out

Turning up any required equipment

Performing configuration

Reserving resources

ssurance nc u es a ac v es ensurng a a servce runsmoothly after it has been fulfilled

Monitoring service for QoS purposes Diagnosing any faults and repairing

Billing making sure that services provided are accounted properlyan can e e o e use

41


42/47

Customer

Operations

Fulfillment Assurance BillingOperationsSupport &Readiness

Strategy, Infrastructure & Product

ProductLifecycleManagement

InfrastructureLifecycleManagement

Strategy &Commit

Customer Relationship ManagementMarketing & Offer Management

Service Management & OperationsService Development & Management

Su lier/Partner Relationshi Mana ement

(Application, Computing and Network)

Su l Chain Develo ment & Mana ement

(Application, Computing and Network)

nterprseManagement

Strategic &EnterprisePlanning

Financial & Asset Enterprise Quality

Stakeholder & ExternalRelations Management

Brand Management,Market Research &Advertising

Human Resources

Disaster Recovery,Security & FraudManagement

Research &Development,

42

,Planning & Architecture

Technology

Acquisition

Outline


43/47

Outline

Introduction

Lifecycle

Interoperability

Layersunc ons

Summar

43

Relation Between Models


44/47


44

Relation Between Functional Models


45/47

Relation Between Functional Models

45



46/47


--

46

References


47/47

References

Reading Assignment: Chapter 4 of Alexander Clemm, Network , ,

Alexander Clemm, Network Management, Santa Clara University,

http://www.engr.scu.edu/~aclemm Woraphon Lilakiatsakun, Network Management, Mahanakorn

University of Technology,p: www.ms .mu .ac. ms _me a _ ec ure

Thomas Cavaiani, Network Management, Biose State University,. . . . .

47

03 dimensions

Documents