daniel ranc network & services management group leader ...agirs/nm-global-v1.01.pdf ·...

introduction

Network Management: an introduction

Daniel RancNetwork & Services Management Group

[email protected]

introduction 2

Course overview

• Introduction• TMN Architecture• TMN Information• Management protocols

introduction 3

Course overview


introduction 4

Introduction to Network

Management

• What is the subject?• The models• The standards• The definitions• Why manage networks?• PDH example• TMN Management• pointers

introduction 5

What is Network Management

all about?

• A metaphor: the enterprise business layers

Strategical

Services

Tactical

Execution

Definition of enterprisegoals and business model

marketing, definition ofservices and workflows

order management,workflow execution

order execution

introduction 6

What is Network Management

all about?

• Using the metaphor:– Business Management Layer– Service Management Layer– Network Management Layer– Element Management Layer

As defined bystandards

Definition proposal 1: activity of deployment,analysis, monitoring and control ofNetwork Resources

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• specification of the communication infrastructure

introduction 8

A world of standards

• The main ones:– ISO– ITU-T– ETSI– TINA– TMF– OMG

• Our perspective: the Operator ’s =Telecommunication Management Network(TMN)

• Standards define a framework with some prescriptive aspects

introduction 9

First definitions

• Definition proposal 2: to configure, maintainand exploit networks from the distance

• Functionally, 5 areas:– F = Fault– C = Configuration– A = Accounting– P = Performance– S = Security

introduction 10

Why manage networks?

• Networks Business Model– Deliver bandwidth

• on time• contracted quality

– lost paquets, availability– SLA

– For the new services• low jitter• no world wide wait

introduction 11

Main properties

• Involves Distribution• Involves Complexity• Is Costly

– up to 30% of total network cost

• Is not optimal– industrial products still in loom

introduction 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)

introduction 13

PDH example

• Transmitted values are:– in one block– semantically at the level of machine registers– analogy to assembler programming

introduction 14

PDH example

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

– management software is equipment-specific

PDH

Craft terminalCentralized management

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.

…Gödel law...

introduction 16

TMN management

arch

itect

ure

functional

prot

ocol

s

F C A P S

introduction 17

TMN management

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

• attempt to circumvent the limitations of proprietarytechnologies

• management of complex flexible equipment• FCAPS complete• deployed today• market: WAN, high bandwidth backbones• technologies: SDH, ATM, mobiles, submarine cables,

WDM

introduction 18

Network Management Rationale

• High Information Technology cost• Mandatory• Complex• Multiple technologies & protocols• Main question:

How to keep things running ?

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

introduction 20

Any questions?

introduction 21

Course overview


introduction 22

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

plan

introduction 23

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

OperationsSystem

OperationsSystem

OperationsSystem

Data Communication Network (DCN)Workstation

Telecommunication Network

ExchangeTransmissionSystem

Exchange TransmissionSystem

Exchange

TMN

Network-TMN relationship

introduction 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

TMN functions

introduction 25

• The activity to manage network failures– alarm notification– manager action– repair

Fault management

introduction 26

• The activity to configure and maintain network equipments

• Two kinds of life cycle– long term

• VPN– short term

• VPN,,,,,,

Configuration management

introduction 27

• The activity to manage and calculate the users ’s account

• traditional telcom specialiity• Emerging « flat rate » paradigm

Accounting Management

introduction 28

• The activity of summarizing the network ’savailability

• Not for speed• Statistics on:

– lost packets– lost seconds– lost milliseconds– lost microseconds– lost nanoseconds– lost picoseconds– lost …seconds

Performance Management

introduction 29

• Defining – access control– functional control

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

• Never implemented– why?

Security Management

introduction 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

introduction 31

Cisco 6000 Enterasys 3000

Perf.Fault InTelMotorola

Distribution

introduction 32

OSF

WSF

MF

QAF NEF

TMN

• Operations Systems Function• Workstation Function• Mediation Function• Network Element Function• Q Adaptor Function

Functional architecture of TMN

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

Functional architecture of TMN

introduction 34

• Why Reference Points?– Unique means to define

• information exchange• functional exchange

– between components of Network Management

• Reference Points Specifications are the basicsfor:

Open Systems

TMN reference points

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


introduction 36

NEF MF OSF WSF

QAF

TMN

x

m

q

q q f g


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

Management information

introduction 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 Definitionof Managed Objects)

Management information

introduction 39

• Management processes are either:– managers– agents

manager

requests

notifications

Management system Managed system

agent

Managed objects

Manager, agent roles

introduction 40

TMN

Managed resources

managed objectsmanaged information base

Management system

Q3 interface

agent

Conceptualviewincludingmanagedresources

The frame

introduction 41

MIB

A M

resource

M A

CMIP CMIP

CMIS

info model Bsystem A system B system Cinfo model C

sees sees

Cascading interaction

introduction 42

• 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

introduction 43

TMNOperations Systems

Data Communication Network

Mediation Device

work-station

Data Communication Network

Qadapter

NetworkElement

Qadapter

NetworkElement

X/F/Q3

FX

Q3/F

Qx

Qx Qx

Q3Q3

Physical architecture of the

TMN

introduction 44

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

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

And SNMP ??

introduction 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– F, X interfaces

Conclusions

introduction 47

Any questions?

introduction 48

Course overview


introduction 49

Network Management information

Daniel [email protected]

introduction 50

Network Management

information

• Object oriented concepts: reminder• information model• the GDMO language• ASN.1 syntaxes

introduction 51

Object oriented concepts:

reminder

class

instance

class

classinheritanceallomorphism

instanciation

encapsulation

attributes

methods

interface

behaviour

introduction 52


reminder

• Inheritance flavours

Generic car4 wheels

Sports car, bigengine

Truck, big payload

specialisation

introduction 53


reminder

• Inheritance flavours

Generic car4 wheels

Car with automaticgearbox

Truck, big payload

extension

introduction 54

Notion of information model/1

• Management information circulating betweenmanager 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– info models for EML, NML

introduction 55


• 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

introduction 56


• Inheritance– in GDMO, inheritance by extension– all properties of the superclass unchanged– multiple inheritance ok

top

system discriminator logRecord

alarmRecord

eventForwardingDiscriminator

introduction 57


• 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– dynamicity: MO life cycle

introduction 58


root

system

log

alarmRecord


introduction 59


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

introduction 60


• Three trees:– inheritance– containment– registration

introduction 61


system

log

alarmRecord


(systemId = «BDC»)

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

(alarmRecordId = «5»)

FDN of this alarmRecord: { (systemId = «BDC»), (logId = «SMK»), (alarmRecordId = «5») }

introduction 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• naming links• actions

introduction 63

GDMO /2

• Managed Object Class:

<class name> MANAGED OBJECT CLASSDERIVED FROM <class name> ;CHARACTERIZED BY <package name> ;BEHAVIOUR DEFINED AS ... ;ATTRIBUTES <attribute name> {GET|SET|REPLACE};;;;

REGISTERED AS <object identifier>;

introduction 64

GDMO /3

a real MOC

subNetwork MANAGED OBJECT CLASSDERIVED FROM top;CHARACTERIZED BY

createDeleteNotificationPackage,attributeValueChangeNotificationPackage PACKAGE;

BEHAVIOUR DEFINED AS...ATTRIBUTES

signalType GET;subNetworkId GET;containedSubnetWorkList GET;

ACTIONSaddToSubNetworkConnections;deleteFromSubNetworkConnections;

;;;REGISTERED AS { etsi ObjectClass 6 };

introduction 65

GDMO/4 - PACKAGE template

• Syntaxic container

serviceStatePackage PACKAGEATTRIBUTES

administrativeState GET-REPLACE,availabilityStatus GET-REPLACE,controlStatus GET-REPLACE,operationalState GET,usageState GET;

REGISTERERED AS { etsi Package 45 };

introduction 66

GDMO/5 - NAME BINDING

template

<name-binding name> NAME BINDINGSUBORDINATE OBJECT CLASS <class name>NAMED BY SUPERIOR OBJECT CLASS <class name>WITH ATTRIBUTE <attribute name>

REGISTERED AS <object id>;

subNetwork-network NAME BINDINGSUBORDINATE OBJECT CLASS subNetwork AND SUBCLASSES;NAMED BY SUPERIOR OBJECT CLASS network AND SUBCLASSES;WITH ATTRIBUTE subNetworkId;

REGISTERED AS { etsi NameBinding 23 };

subNetwork-subNetwork NAME BINDINGSUBORDINATE OBJECT CLASS subNetwork AND SUBCLASSES;NAMED BY SUPERIOR OBJECT CLASS subNetwork AND SUBCLASSES;WITH ATTRIBUTE subNetworkId;

REGISTERED AS { etsi NameBinding 24 };

introduction 67

GDMO/6 - ATTRIBUTE template

<attribute name> ATTRIBUTEWITH ATTRIBUTE SYNTAX <syntax reference>;[MATCHES FOR { EQUALITY|ORDERING|SUBSTRINGS|SET-COMPARISON|SET-INTERSECTION }[BEHAVIOUR ...;][PARAMETERS ...;]

REGISTERED AS <object id>;

subNetworkId ATTRIBUTEWITH ATTRIBUTE SYNTAX NA4ASN.1.NameType;MATCHES FOR EQUALITY;BEHAVIOUR

subNetworkIdBehaviour BEHAVIOURDEFINED AS «The subnetworkId is an attribute type whose distinguished value can be used as an RDN whennaming an instance of the subNetwork object class»;;

REGISTERED AS { etsi attribute 45 };

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

– construted types: SEQUENCE, SET, CHOICE...

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]

}

introduction 70

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

introduction 71

Any questions?

introduction 72

Course overview


introduction 73

Daniel RancNetwork & Services Management Group

[email protected]

Protocols in Network Management

introduction 74

Protocols in NM

• CMIS/P ITU-T• SNMP IETF• comparison

introduction 75

Protocols in NM


introduction 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

introduction 77

CMIS/P properties

• General invocation:

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

introduction 78

CMIS/P properties



getsetcreatedeleteaction

introduction 79

CMIS/P properties




Fulldistinguishedname

introduction 80

CMIS/P properties





ObjectIdentifier

introduction 81

CMIS/P properties





ObjectIdentifier

best effort/transactional

introduction 82

CMIS/P properties





ObjectIdentifier


Depthin MIB tree

introduction 83

CMIS/P properties





ObjectIdentifier


Depthin MIB tree

Conditionson object

introduction 84

CMIP scope

• Depth of request execution

Scope = 2

Starting point

introduction 85

CMIP scope

• Depth of request execution

Scope = 2

Starting point

introduction 86

CMIP filter

• Conditions on any object property

Starting point

filter = « AdministrativeState = none »,scope = any

introduction 87

CMIP filter

• Conditions on any object property

Starting point

filter = « AdministrativeState = none »,scope = any

introduction 88

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 curve– uses OSI stack– industrial tools heavy & cumbersome

introduction 89

CMIP tool example: XMP/XOM

• XMP/XOM : programming standards for CMIP byX/Open consortium– XMP: Management Processing– XOM: Object Management

• Implementation: HP OpenView– highly cumbersome– learning curve– cost

• Alternative: TMN++– C++ image of CMIP– TMF, few implementations

introduction 90

CMIP tool example: XMP/XOM

• Example of set action

Process space XOM spaceManaged system

Set(toto,oid, Value = 2);

ASN.1mapping

XMP handling

Managing system

introduction 91

Protocols in NM


introduction 92

SNMP rationale

• Simple Network Management Protocol - IETF• To solve rapidly, with a transient solution by

tinkering , management problems (1986), whileITU-T will provide the absolute perfect solution

• 0 learning curve• Classical protocol scheme over UDP

Small but beautiful

introduction 93

SNMP properties


<primitive> (oid, value);

getset Object

Identifier

+ trap

introduction 94

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 MIBs– MIB II– RMON– …. (RFCs)

introduction 95

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

introduction 96

Protocols in NM


introduction 97

CMIP/SNMP comparison

CMIP SNMPlearning curve 0 +++power +++ +OO +++ 0access asynchronous synchronousdynamicity +++ 0penetration + +++security ACSE/ROSE UDPnotifications +++ trapunderstanding 0 +++

introduction 98

Any questions?

daniel ranc network & services management group leader ...agirs/nm-global-v1.01.pdf ·...

Documents