Network Management: an introduction

(1)

introduction

Network Management: an introduction

Daniel Ranc

Network & Services Management Group

Leader

(2)

Course overview

• Introduction

• TMN Architecture

• TMN Information

(3)

introduction 3

Course overview

• Introduction

• TMN Architecture

• TMN Information

• Management protocols

(4)

Introduction to Network

Management

• What is the subject?

• The models

• The standards

• The definitions

• Why manage networks?

• PDH example

• TMN Management

• pointers

(5)

introduction 5

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 of

services and workflows

order management,

workflow execution

order execution

(6)

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 of

(7)

introduction 7

Network Management models

• Needed to simplify a complex universe

• models are orthogonal e.g. adopt different

perspectives

• concepts related to ODP viewpoints:

– functional model

• description of activity classes – informational model

• specification of managed information – architectural model

• definition of management building blocs – communication model

(8)

A world of standards

• The main ones:

– ISO – ITU-T – ETSI – TINA – TMF – OMG

• Our perspective: the Operator ’s =

Telecommunication Management Network

(TMN)

(9)

introduction 9

First definitions

• Definition proposal 2: to configure, maintain

and exploit networks from the distance

• Functionally, 5 areas:

– F = Fault – C = Configuration – A = Accounting – P = Performance – S = Security

(10)

Why manage networks?

• Networks Business Model

– Deliver bandwidth • on time

• contracted quality

– lost paquets, availability – SLA

– For the new services • low jitter

(11)

introduction 11

Main properties

• Involves Distribution

• Involves Complexity

• Is Costly

– up to 30% of total network cost

• Is not optimal

(12)

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)

(13)

introduction 13

PDH example

• Transmitted values are:

– in one block

– semantically at the level of machine registers – analogy to assembler programming

(14)

PDH example

– opérations performed locally (craft terminal) or from the distance

– management software is equipment-specific

(15)

introduction 15

TMN management

• Yet another definition:

– architectural, technical and functional paradigm

characterized by consistency and large functional scope, – realizing network management from an Open Systems

point of view.

(16)

TMN management

a rc h it e c tu re

pr

ot

oc

ol

s

F C

A

P

S

(17)

introduction 17

TMN management

• Active organizations: ITU-T (ex CCITT), ETSI, EURESCOM, NMF, OMG, …

• attempt to circumvent the limitations of proprietary technologies

• management of complex flexible equipment • FCAPS complete

• deployed today

• market: WAN, high bandwidth backbones

• technologies: SDH, ATM, mobiles, submarine cables, WDM

(18)

Network Management Rationale

• High Information Technology cost

• Mandatory

• Complex

• Multiple technologies & protocols

• Main question:

(19)

introduction 19

Some pointers

• Books:

– our book :-)

– Network Management, Stallings – the ICM book:

www.ee.ucl.ac.uk/~dgriffin/papers/book/icmbook.html

• Web resources

– all vendors (HP, Sun, IBM, Cisco, Alcatel...) – other links:

• webbin ’CMIP: www.misa.zurich.ibm.com/webbin • Festor ’s links: www.loria.fr/~festor/NM-index.html • TINA: www.tinac.org

• ETSI: www.etsi.fr/tmn • OMG: www.omg.org • TMF: www.nmf.org

(20)

(21)

introduction 21

Course overview

• Introduction

• TMN Architecture

• TMN Information

• Management protocols

(22)

– Network-TMN relationship – TMN functions – architectural requirements – functional architecture – reference points – management information – agents, managers, the frame – shared management knowledge – management layers

(23)

introduction 23

• TMN independant of managed network

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

Operations System Operations System Operations System

Data Communication Network (DCN)

Workstation

Telecommunication Network

Exchange Transmission_System Exchange Transmission

System Exchange

TMN

(24)

• 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

(25)

introduction 25

• The activity to manage network failures

– alarm notification – manager action – repair

(26)

• The activity to configure and maintain network

equipments

• Two kinds of life cycle

– long term • VPN – short term

• VPN,,,,,,

(27)

introduction 27

• The activity to manage and calculate the

users ’s account

• traditional telcom specialiity

• Emerging « flat rate » paradigm

(28)

• 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

Performance Management

(29)

introduction 29

• Defining

– access control – functional control

• Network Access Domain (NAD) • Function Access Domain (FAD)

• Never implemented

– why?

(30)

– Distributed software, heterogeneous implementations – network = distributed heterogeneous resources

– cooperative structure of distributed functions – technology lifecycle

– reliability, security

– client or 3rd party access – hihgly competitive market – inter TMN cooperation

– time to market constraints

Architectural requirements for

TMN

(31)

introduction 31

Cisco 6000

Enterasys 3000

Perf.

Fault

_InTel

Motorola

Distribution

(32)

OSF

WSF

MF

TMN

• Operations Systems Function • Workstation Function

• Mediation Function

• Network Element Function • Q Adaptor Function

(33)

introduction 33

• 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

(34)

• 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

(35)

introduction 35

• 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

TMN reference points

(36)

NEF MF OSF WSF QAF x m q q q f g

TMN reference points

(37)

introduction 37

• Two points of view:

– management information specifications = information models (static)

• abstract view of managed resources • relies on functional blocs

– information exchange (dynamic) • OSI stacks

(38)

• 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 of Managed Objects)

(39)

introduction 39

• Management processes are either:

– managers – agents

manager

requests

notifications

Management system _{Managed system}

agent

Managed objects

(40)

TMN

managed objects

managed information base

Management system Q3 interface agent Conceptual view including managed resources

The frame

(41)

introduction 41 MIB A M resource M A CMIP CMIP CMIS info model B

system A _{system B} _{info model C} system C

sees sees

(42)

• Between agents and managers to support:

• specs. of protocols, functionalities, supported MOCs, existing instances, naming relations

MIB A M system A _{system B}

Shared management

knowledge

(43)

introduction 43

TMN

Operations Systems

Data Communication Network

Mediation Device

work-station

Data Communication Network

Q adapter Network Element Q adapter Network Element X/F/Q3 F X Q3/F Qx Qx Qx Q3 Q3

Physical architecture of the

TMN

(44)

OS

OS MF Business Management Layer

Service Management Layer

Network Management Layer

Element Management Layer

Q3

QX

Physical architecture of the

TMN

(45)

introduction 45

• 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

(46)

• 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

Conclusions

(47)

introduction 47

(48)

Course overview

• Introduction

• TMN Architecture

• TMN Information

(49)

introduction 49

Network Management information

Daniel Ranc

(50)

Network Management

information

• Object oriented concepts: reminder

• information model

• the GDMO language

• ASN.1 syntaxes

(51)

introduction 51

Object oriented concepts:

reminder

class

instance

class

class allomorphism inheritance

instanciation encapsulation attributes methods interface behaviour

(52)

Object oriented concepts:

reminder

• Inheritance flavours

Generic car

4 wheels

Sports car, big

Truck, big payload

(53)

introduction 53

Object oriented concepts:

reminder

• Inheritance flavours

Generic car

4 wheels

Car with automatic

gearbox

Truck, big payload

(54)

Notion of information model/1

• Management information circulating between

manager and agents

• composed of Managed 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 MOs

(55)

introduction 55

Notion of information model/2

• 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 • constants

(56)

Notion of information model/3

• Inheritance

– in GDMO, inheritance by extension

– all properties of the superclass unchanged – multiple inheritance ok

top

system discriminator logRecord

(57)

introduction 57

Notion of information model/4

• Naming, containment

– a MO instance may contain other Mos – useful to model real containment

• rack/card

• directory/files/records

– defined by the name binding template

• Naming tree

– set of all naming relationships of the MIB

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

(58)

Notion of information model/5

root system log alarmRecord eventForwardingDiscriminator

(59)

introduction 59

Notion of information model/6

• 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 Name • based 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)

(60)

Notion of information model/7

• Three trees:

– inheritance – containment – registration

(61)

introduction 61

Notion of information model/8

system

log

alarmRecord

eventForwardingDiscriminator (systemId = «BDC»)

(logId = «SMK») (EFDId = «a»)

(alarmRecordId = «5»)

FDN of this alarmRecord:

(62)

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

(63)

introduction 63

GDMO /2

• Managed Object Class:

<class name> MANAGED OBJECT CLASS DERIVED FROM <class name> ;

CHARACTERIZED BY <package name> ; BEHAVIOUR DEFINED AS ... ;

ATTRIBUTES <attribute name> {GET|SET|REPLACE}; ;;;

(64)

GDMO /3

a real MOC

subNetwork MANAGED OBJECT CLASS

DERIVED FROM top; CHARACTERIZED BY createDeleteNotificationPackage, attributeValueChangeNotificationPackage PACKAGE; BEHAVIOUR DEFINED AS ... ATTRIBUTES signalType GET; subNetworkId GET; containedSubnetWorkList GET; ACTIONS addToSubNetworkConnections; deleteFromSubNetworkConnections;

(65)

introduction 65

GDMO/4 - PACKAGE template

• Syntaxic container

serviceStatePackage PACKAGE ATTRIBUTES administrativeState GET-REPLACE, availabilityStatus GET-REPLACE, controlStatus GET-REPLACE, operationalState GET, usageState GET;

(66)

GDMO/5 - NAME BINDING

template

<name-binding name> NAME BINDING

SUBORDINATE OBJECT CLASS <class name>

NAMED BY SUPERIOR OBJECT CLASS <class name> WITH ATTRIBUTE <attribute name>

REGISTERED AS <object id>;

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

(67)

introduction 67

GDMO/6 - ATTRIBUTE template

<attribute name> ATTRIBUTE

WITH ATTRIBUTE SYNTAX <syntax reference>; [MATCHES FOR { EQUALITY|ORDERING

|SUBSTRINGS|SET-COMPARISON|SET-INTERSECTION } [BEHAVIOUR ...;]

[PARAMETERS ...;] REGISTERED AS <object id>; 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»;;

(68)

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...

(69)

introduction 69

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] }

(70)

Software engineering of TMN

classes C++ classes C++ librairies framework programmer classes C++ objects objects objetcs LINK specs GDMO specs ASN.1 compiler GDMO compiler ASN.1 compiler C++ compiler C++ compiler C++ agent

(71)

introduction 71

(72)

Course overview

• Introduction

• TMN Architecture

• TMN Information

(73)

introduction 73

Daniel Ranc

Network & Services Management Group

Leader

[email protected]

(74)

Protocols in NM

• CMIS/P

ITU-T

• SNMP

IETF

(75)

introduction 75

Protocols in NM

• CMIS/P

ITU-T

• SNMP

IETF

(76)

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

(77)

introduction 77

CMIS/P properties

• General invocation:

(78)

CMIS/P properties

• General invocation:

<primitive> (fdn, oid, type, scope, filter);

get

set

create

delete

action

(79)

introduction 79

CMIS/P properties

• General invocation:

<primitive> (fdn, oid, type, scope, filter);

get

set

create

delete

action

Full

distinguished

name

(80)

CMIS/P properties

• General invocation:

<primitive> (fdn, oid, type, scope, filter);

get

set

create

delete

action

Full

Object

Identifier

(81)

introduction 81

CMIS/P properties

• General invocation:

<primitive> (fdn, oid, type, scope, filter);

get

set

create

delete

action

Full

distinguished

name

Object

Identifier

best effort/

transactional

(82)

CMIS/P properties

• General invocation:

<primitive> (fdn, oid, type, scope, filter);

get

set

create

delete

action

Full

Object

Identifier

best effort/

Depth

in MIB tree

(83)

introduction 83

CMIS/P properties

• General invocation:

<primitive> (fdn, oid, type, scope, filter);

get

set

create

delete

action

Full

distinguished

name

Object

Identifier

best effort/

transactional

Depth

in MIB tree

Conditions

on object

(84)

CMIP scope

• Depth of request execution

Scope = 2

Starting point

(85)

introduction 85

CMIP scope

• Depth of request execution

Scope = 2

Starting point

(86)

CMIP filter

• Conditions on any object property

Starting point

filter =

« AdministrativeState = none »,

scope = any

(87)

introduction 87

CMIP filter

• Conditions on any object property

Starting point

filter =

« AdministrativeState = none »,

scope = any

(88)

CMIP evaluation

• Advantages

– many results possible in one request – transactional on 1 request basis