globals v2.51 handouts

7/31/2019 Globals v2.51 Handouts

1/51

1

Network Management: an introduction

Daniel Ranc

LOR/Network & Services Management Group

[email protected]

18/01/2012 2

Course overview

Introduction

TMN Architecture

TMN Information

Management protocols


2/51

2

18/01/2012 3

Course overview

Introduction

TMN Architecture

TMN Information


18/01/2012 4

Introduction to Network Management

Some questions & answers

The models

The standards

The definitions

Why manage networks?

Simple PDH example

TMN Management example

pointers


3/51

3

18/01/2012 5


Network Management allows, at least, to monitor & configurethe network

To capture knowledge on network sanity and service efficiency

In order to insure QoS control

To make provision for network evolution

Maintenance & new systems deployment

As such, Network Management is in the value chain of theoperator

and included in a broader landscape of OSS/BSS

18/01/2012 6


Networks Business Model

Deliver bandwidth

on time

contracted quality

lost paquets, availability

SLA

For increasingly real-time oriented services

low jitter

High bandwidth

High stress


4/51

4

18/01/2012 7

What is managed?

Primarily the Network Resources:

Routers, switches, repeaters,

Links

Applications (software)

But also:

Technologies (Moore law)

Users (access rights, QoS profiles, )

Business aspects (RoI, OPEX, CAPEX)Legal aspects

(i.e. a network MUST be managed by a responsible person)

18/01/2012 8

What is Network Management all about?

A metaphor: the enterprise business layers

Strategical

Services

Tactical

Execution

Definition of enterprise

goals and business model

marketing, definition ofservices and workflows

order management,

workflow execution

order execution


5/51

5

18/01/2012 9

What is Network Management all about?

Using the metaphor:

Business Management Layer

Service Management Layer

Network Management Layer

Element Management Layer

As defined by

standards

Definition proposal 1: activity of deployment,

analysis, monitoring and control ofNetwork Resources

18/01/2012 10

Network Management models

Needed to simplify a complex universe

models are orthogonal e.g. adopt different perspectives

concepts related to ODP viewpoints:

functional modeldescription of activity classes

informational model

specification of managed information

architectural model

definition of management building blocs

communication model

specification of the communication infrastructure


6/51

6

18/01/2012 11

A world of standards

The main ones:

ISO

ITU-T

ETSI

TINA

TMF

OMG

Our perspective: the Operator s = TelecommunicationManagement Network (TMN)

Standards define a frameworkwith some prescriptive aspects

18/01/2012 12

First definitions

Definition proposal 2: to configure, maintain and exploitnetworks from the distance

Functionally, 5 areas:

F = Fault

C = Configuration

A = Accounting

P = Performance

S = Security


7/51

7

18/01/2012 13

Main properties /1

Involves Distribution

Involves Complexity

Is Costly

up to 30% of total network cost

Is not optimal

industrial products still in loom

18/01/2012 14

Main properties /2

A broad landscape of usages and technical approaches

Standard-based approaches:

Operator network management: the Telecommunications

Management Network (TMN)

LAN management: Simple Network Management Protocol (SNMP)

Enterprise management: Web based Enterprise Management

(WBEM)

Etc.

Proprietary approches

anything


8/51

8

18/01/2012 15

Simple PDH example

in this case management

requires only few operations, mainly provisioning

C, F and P

can live with proprietary protocols

that are mainly of tabular nature

(US: TL/1)

18/01/2012 16

Simple PDH example

Transmitted values are:

in one block

semantically at the level of machine registers

analogy to assembler programming


9/51

9

18/01/2012 17

Simple PDH example

operations performed locally (craft terminal) or from the distance

management software is equipment-specific

PDH

Craft terminalCentralized management

This obsolete proprietary approach is still what

many vendors offer today

18/01/2012 18

TMN management example

Yet another definition:

architectural, technical and functional paradigm characterized byconsistencyand large functional scope,

realizing network management from an Open Systems point ofview.

Gdel law...


10/51


11/51

11

18/01/2012 21

Network Management Rationale

High Information Technology cost

Mandatory

Complex

Multiple technologies & protocols

Main question:

How to keep things running?

18/01/2012 22

Some pointers

Books:

our book :-)

Network Management, Stallings

the ICM book: www.ee.ucl.ac.uk/~dgriffin/papers/book

Gestion des rseaux et des services, N. Simoni et S. Znaty, Interditions, 1997

Web resources

all vendors (HP, Sun, IBM, Cisco, Alcatel-Lucent........)

other links:

Carleton university:

http://www.sce.carleton.ca/netmanage/links.html

TMF: http://www.tmforum.org

ETSI: http://www.etsi.org/WebSite/Technologies/oss.aspx

OMG: www.omg.org


12/51

12

18/01/2012 23

Any questions?

18/01/2012 24

Course overview

Introduction

TMN Architecture

TMN Information



13/51

13

18/01/2012 25

Network-TMN relationship

TMN functions

architectural requirements

functional architecture

reference points

management information

agents, managers, the frame

shared management knowledge

management layers

plan

18/01/2012 26

TMN independant of managed network

it may use the managed network (e.g. SDH, ATM)

Operations

SystemOperations

System

Operations

System

Data Communication Network (DCN)Workstation

Telecommunication Network

ExchangeTransmission

SystemExchange

Transmission

SystemExchange

TMN

Network-TMN relationship


14/51

14

18/01/2012 27

Management environment

a generic model for a heterogeneous network

distributed by nature

uses OSI services

object orientation

large functional scope

X.700 standard defines the functional domains: Fault,Configuration, Accounting, Performance, Security

FCAPS

TMN functions

18/01/2012 28

The activity to manage network failures

alarm notification

manager action

repair

Fault management

alarm

repair

decision


15/51

15

18/01/2012 29

The activity to configure and maintain networkequipments

Two kinds of life cycle

long term

VPN

short term

VPN,,,,,,

Configuration management

18/01/2012 30

The activity to manage and calculate the users s account

Usage-based

Criteria: duration, distance, QoS, bandwidth,

traditional telcom specialitySee SS7 signalling

Emerging flat rate paradigm

Accounting Management


16/51

16

18/01/2012 31

The activity of summarizing the network s availability

Not for speed

Statistics on:

lost packets

lost seconds

lost milliseconds

lost microseconds

lost nanoseconds

lost picoseconds

lost seconds

Performance Management

18/01/2012 32

Defining

access control

functional control

Network Access Domain (NAD)

Function Access Domain (FAD)

Never implemented

why?

Security Management


17/51

17

18/01/2012 33

Distributed software, heterogeneous implementations

network = distributed heterogeneous resources

cooperative structure of distributed functions

technology lifecycle

reliability, security

client or 3rd party access

highly competitive market

inter TMN cooperation

time to market constraints

Architectural requirements for TMN

18/01/2012 34

Cisco 6000 Enterasys 3000

Perf.Fault InTelMotorola

Distribution


18/51

18

18/01/2012 35

OSF

WSF

MF

QAF NEF

TMN

Operations Systems Function

Workstation Function

Mediation Function Network Element Function

Q Adaptor Function

Functional architecture of TMN

18/01/2012 36

Operations systems function

realizes the FCAPS and TMN management

Workstation function

interprets management information for the user interface +user interface (out of TMN)

Network Element Function

managed entity - access to managed resources (out of TMN)

Mediation function, Q adaptator function

information shift or adaptation

Functional architecture of TMN


19/51

19

18/01/2012 37

Why Reference Points?

Unique means to define

information exchange

functional exchange

between components of Network Management

Reference Points Specifications are the basics for:

Open Systems

TMN reference points

18/01/2012 38

Define the interfaces between functional blocs

3 classes of RPs:

q bet. OSF, QAF, MF, NEF

qx:NEF-MF, QAF-MF, MF-MF

q3: NEF-OSF, QAF-OSF, MF-OSF, OSF-OSF

f bet. OSF-WSF

x: bet. OSFs of different TMNs

minor classes:

g: WSF-user, m: QAF-non TMN entities



20/51

20

18/01/2012 39

NEF MF OSF WSF

QAF

TMN

x

m

q

q q f g


18/01/2012 40

Two points of view:

management information specifications = informationmodels (static)

abstract view of managed resources

relies on functional blocs

information exchange (dynamic)

OSI stacks

Management information


21/51

21

18/01/2012 41

Object orientation

information models built from managed objects

Managed Object Classes (MOCs)

MOCs = conceptual views of resources

MOCs = true objects

attributes, inheritance, actions/operations, behaviour,

notifications (=messages)

specified in GDMO language (Guidelines for Definition ofManaged Objects)

Management information

18/01/2012 42

Management processes are either:

managers

agents

manager

requests

notifications

Management system Managed system

agent

Managed objects

Manager, agent roles


22/51

22

18/01/2012 43

TMN

Managed resources

managed objects

managed information base

Management system

Q3 interface

agent

Conceptualviewincludingmanagedresources

The frame

18/01/2012 44

MIB

A M

resource

M A

CMIP CMIP

CMIS

info model Bsystem A system B system Cinfo model C

sees sees

Cascading interaction


23/51

23

18/01/2012 45

Between agents and managers to support:

specs. of protocols, functionalities, supported MOCs, existing

instances, naming relations

MIB

AM

system A system B

Shared management knowledge

18/01/2012 46

TMNOperations Systems

Data Communication Network

Mediation Device

work-

station

Data Communication Network

Q

adapter

Network

ElementQ

adapter

Network

Element

X/F/Q3

FX

Q3/F

Qx

Qx Qx

Q3Q3

Physical architecture of the TMN


24/51

24

18/01/2012 47

OS

OS

OS

OS

MF

NE

Business Management Layer

Service Management Layer

Network Management Layer

Element Management Layer

Network Element Layer

Q3

Q3

Q3

QX

QX

Physical architecture of the TMN

18/01/2012 48

Simple Network Management Protocol

IETF standard

defines the protocol, the MIB, the Structure of Managed

Information

simplified TMN tables, not classes

ASN.1 types

primitives GET, SET, TRAP

LAN oriented but

de facto success

And SNMP ??


25/51

25

18/01/2012 49

The TMN architecture is:

open

in the sense of Open Systems

in the sense of incompleteness

complex

necessarily

eliminates the small players

some questions

transactions, security, SML, BML,

info model mapping, compilation vs. Interpretation

F, X interfaces

Conclusions

18/01/2012 50

Any questions?


26/51

26

18/01/2012 51

Course overview

Introduction

TMN Architecture

TMN Information


Network Management information

Daniel Ranc

[email protected]


27/51

27

18/01/2012 53

Network Management information

Object oriented concepts: reminder

information model

the GDMO language

ASN.1 syntaxes

18/01/2012 54


class

instance

class

classinheritanceallomorphism

instanciation

encapsulation

attributes

methods

interface

behaviour


28/51

28

18/01/2012 55


Inheritance flavours

Generic car

4 wheels

Sports car, big

engine

Truck, big payload

specialisation

18/01/2012 56


Inheritance flavours

Generic car4 wheels

Car with automatic

gearbox

Truck, big payload

extension


29/51

29

18/01/2012 57

Notion of information model/1

Management information circulating between manager andagents

composed ofManaged Objects:

abstracting managed resources

accessed by the manager: the real resource remains hidden

MOs are composed of packages

attributes, operations, notifications, behaviour

an info model is a set of MOsinfo models for EML, NML

18/01/2012 58


Encapsulation

hides and protects the inside of the object

access through messages

internal operations hidden

Attributes

have a value that may be structured

carried by an ASN.1 syntax

are accessed by operations on the object

The behaviour defines:

semantics of attributes, operations

operation pre- and postconditions


30/51

30

18/01/2012 59


Inheritance

in GDMO, inheritance by extension

all properties of the superclass unchanged

multiple inheritance ok

top

system discriminator logRecord

alarmRecord

eventForwardingDiscriminator

18/01/2012 60


Naming, containment

a MO instance may contain other Mos

useful to model real containment

rack/card

directory/files/records

defined by the name bindingtemplate

Naming tree

set of all naming relationships of the MIB

each instance has a name derived by its place in the tree

dynamicity: MO life cycle


31/51

31

18/01/2012 61


root

system

log

alarmRecord


18/01/2012 62


Structure of names

identification of MOCs: registration tree

object identifier (OID) - ASN.1

sequence of integers representing the trail from the root til the class

identification of instances: Distinguishedt Namebased on Attribute Value Assertions (AVAs)

exemple: (localValue = 34)

the AVA names the instance at its level of the tree, Relative

Distinguished Name (RDN)

the full chain of AVAs is the Full Distinguished Name (FDN)


32/51

32

18/01/2012 63


Three trees:

inheritance

containment

registration

18/01/2012 64


system

log

alarmRecord


(systemId = BDC)

(logId = SMK) (EFDId = a)

(alarmRecordId = 5)

FDN of this alarmRecord:

{ (systemId = BDC), (logId = SMK), (alarmRecordId = 5) }


33/51

33

18/01/2012 65

GDMO /1

specification langage for MOCs

Guidelines for the Definition of Managed Objects

general properties:

OO

ASN.1 macros (cf.)

base structures: templates

classes

attribute sets: packages

attributes

naming links

actions

18/01/2012 66

GDMO /2

Managed Object Class:

MANAGED OBJECT CLASS

DERIVED FROM ;

CHARACTERIZED BY ;BEHAVIOUR DEFINED AS ... ;

ATTRIBUTES {GET|SET|REPLACE};

;;;

REGISTERED AS ;


34/51


35/51

35

18/01/2012 69

GDMO/5 - NAME BINDING template

NAME BINDING

SUBORDINATE OBJECT CLASS

NAMED BY SUPERIOR OBJECT CLASS

WITH ATTRIBUTE

REGISTERED AS ;

subNetwork-network NAME BINDING

SUBORDINATE OBJECT CLASS subNetwork AND SUBCLASSES;

NAMED BY SUPERIOR OBJECT CLASS network AND SUBCLASSES;

WITH ATTRIBUTE subNetworkId;

REGISTERED AS { etsi NameBinding 23 };subNetwork-subNetwork NAME BINDING

SUBORDINATE OBJECT CLASS subNetwork AND SUBCLASSES;

NAMED BY SUPERIOR OBJECT CLASS subNetwork AND SUBCLASSES;

WITH ATTRIBUTE subNetworkId;

REGISTERED AS { etsi NameBinding 24 };

18/01/2012 70

GDMO/6 - ATTRIBUTE template

ATTRIBUTE

WITH ATTRIBUTE SYNTAX ;

[MATCHES FOR { EQUALITY|ORDERING

|SUBSTRINGS|SET-COMPARISON|SET-INTERSECTION }

[BEHAVIOUR ...;]

[PARAMETERS ...;]

REGISTERED AS ;

subNetworkId ATTRIBUTE

WITH ATTRIBUTE SYNTAX NA4ASN.1.NameType;

MATCHES FOR EQUALITY;

BEHAVIOUR

subNetworkIdBehaviour BEHAVIOUR

DEFINED AS

The subnetworkId is an attribute type whose

distinguished value can be used as an RDN when

naming an instance of the subNetwork object

class;;

REGISTERED AS { etsi attribute 45 };


36/51

36

18/01/2012 71

ASN.1/1

Abstract Syntax Notation One

the end of the communication chain

value transport by OSI stack

abstract syntax = independant of:

implementation langage

processor

each application has its coding/decoding to/from ASN.1 which is

common esperanto marshalling/unmarshalling

simple types : INTEGER, BOOLEAN, REAL, OCTET STRING...

construted types: SEQUENCE, SET, CHOICE...

18/01/2012 72

ASN.1/2

MulticastUnidirectional ::= SEQUENCE {

fromNWTPs SET OF ObjectInstance,

toNWTPs SET OF ObjectInstance

}

Directionality ::= CHOICE {

simpleUnidirectional[0],

simpleBidirectional [1],

multicastUnidirectional [2],

conferenceAll [3],

broadcast [4],

ptoMultipoint [5]

}


37/51

37

18/01/2012 73

Software engineering of TMN

classesC++

classesC++

librairiesframework

programmerclassesC++

objects

objects

objetcs

LINK

specs GDMO

specs ASN.1

compilerGDMO

compilerASN.1

compilerC++

compilerC++

compilerC++

agent+manager

18/01/2012 74

Any questions?


38/51

38

18/01/2012 75

Course overview

Introduction

TMN Architecture

TMN Information


Daniel Ranc

Network & Services Management Group Leader

[email protected]

Protocols in Network Management


39/51

39

18/01/2012 77

Protocols in NM

CMIS/P ITU-T

SNMP IETF

comparison

18/01/2012 78

Protocols in NM

CMIS/P ITU-T

SNMP IETF

comparison


40/51

40

18/01/2012 79

CMIS/P rationale

Common Management Information Services/Protocol

To solve the limitations of SNMP

Layer 7 specifications

Requires ROSE, ACSE services

Serves a Systems Management Application Entity (SMAE)

Transport of management information

defined by information models in GDMO

carried by ASN.1 structures

18/01/2012 80

CMIS/P properties

General invocation:

(fdn, oid, type, scope, filter);


41/51

41

18/01/2012 81

CMIS/P properties

General invocation:


getset

createdeleteaction

18/01/2012 82

CMIS/P properties

General invocation:


getsetcreatedeleteaction

Full

distinguished

name


42/51

42

18/01/2012 83

CMIS/P properties

General invocation:


getset

createdeleteaction

Full

distinguished

name

Object

Identifier

18/01/2012 84

CMIS/P properties

General invocation:



Full

distinguished

name

Object

Identifier

best effort/

transactional


43/51

43

18/01/2012 85

CMIS/P properties

General invocation:


getset

createdeleteaction

Full

distinguished

name

Object

Identifier

best effort/

transactional

Depth

in MIB tree

18/01/2012 86

CMIS/P properties

General invocation:



Full

distinguished

name

Object

Identifier

best effort/

transactional

Depth

in MIB tree

Conditions

on object


44/51

44

18/01/2012 87

CMIP scope

Depth of request execution

Scope = 2

Starting point

18/01/2012 88

CMIP scope

Depth of request execution

Scope = 2

Starting point


45/51

45

18/01/2012 89

CMIP filter

Conditions on any object property

Starting point

filter =

AdministrativeState = none ,

scope = any

18/01/2012 90

CMIP filter

Conditions on any object property

Starting point

filter =

AdministrativeState = none ,scope = any


46/51

46

18/01/2012 91

CMIP evaluation

Advantages

many results possible in one request

transactional on 1 request basis

full TMN GDMO support

uses OSI stack

Drawbacks

transactional on 1 request basis

complexity, important learning curveuses OSI stack

industrial tools heavy & cumbersome

18/01/2012 92

CMIP tool example: XMP/XOM

XMP/XOM : programming standards for CMIP by X/Openconsortium

XMP: Management Processing

XOM: Object Management

Implementation: HP OpenViewhighly cumbersome

learning curve

cost

Alternative: TMN++

C++ image of CMIP

TMF, few implementations


47/51

47

18/01/2012 93

CMIP tool example: XMP/XOM

Example ofset action

Process space XOM spaceManaged system

Set(toto,

oid,

Value = 2);

ASN.1

mapping

XMP handling

Managing system

18/01/2012 94

Protocols in NM

CMIS/P ITU-T

SNMP IETF

comparison


48/51

48

18/01/2012 95

SNMP rationale

Simple Network Management Protocol - IETF

To solve rapidly, with a transient solution by tinkering,management problems (1986), while ITU-T will provide theabsolute perfect solution

0 learning curve

Classical protocol scheme over UDP

Small but beautiful

18/01/2012 96

SNMP properties

General invocation:

(oid, value);

getset Object

Identifier

+ trap


49/51

49

18/01/2012 97

SNMP properties

Flat information model

no OO

no containment

no create, delete = static MIBs

not GDMO, but Simple Management Interface (SMI) language

static objects defined by OIDs of IETF specs

full use of ASN.1

Many IETF MIBsMIB II

RMON

. (RFCs)

18/01/2012 98

SNMP tool example: JMX

Sun s Java Management eXtensions specifications: JMX

Implementations by Sun, AdventNet, IBM/Taligent

Providing a ful OO view on SNMP

dynamic protocol adaptation

mibgen skeleton compiler

SNMP get : class.get(Oid) method


50/51

50

18/01/2012 99

Protocols in NM

CMIS/P ITU-T

SNMP IETF

comparison

18/01/2012 100

CMIP/SNMP comparison

CMIP SNMP

learning curve 0 +++

power +++ +

OO +++ 0access asynchronous synchronous

dynamicity +++ 0

penetration + +++

security ACSE/ROSE UDP

notifications +++ trap

understanding 0 +++


51/51

18/01/2012 101

Any questions?

globals v2.51 handouts

Documents