Chapter 3Basic Foundations:

Standards, Models, and Language

Chapter 3

1

Introduction

• Standards• Standards organizations• Protocol standards of transport layers• Protocol standards of management(application) layer

• Management Models• Language

Chapter 3

2

T a b l e 3 . 1 N e t w o r k M a n a g e m e n t S t a n d a r d s

S t a n d a r d S a l i e n t P o i n t s

O S I / C M I P I n t e r n a t i o n a l s t a n d a r d ( I S O / O S I ) M a n a g e m e n t o f d a t a c o m m u n i c a t i o n s n e t w o r k - L A N a n d

W A N D e a l s w i t h a l l 7 l a y e r s M o s t c o m p l e t e O b je c t o r i e n t e d W e l l s t r u c t u r e d a n d l a y e r e d C o n s u m e s l a r g e r e s o u r c e i n i m p l e m e n t a t i o n

S N M P /I n t e r n e t

I n d u s t r y s t a n d a r d ( I E T F ) O r ig in a l l y i n t e n d e d f o r m a n a g e m e n t o f I n t e r n e t c o m p o n e n t s ,

c u r r e n t l y a d o p te d f o r W A N a n d t e l e c o m m u n i c a t i o n s y s t e m s E a s y t o i m p l e m e n t M o s t w i d e l y i m p l e m e n t e d

T M N I n t e r n a t i o n a l s t a n d a r d ( I T U - T ) M a n a g e m e n t o f t e l e c o m m u n i c a t i o n s n e t w o r k B a s e d o n O S I n e t w o r k m a n a g e m e n t f r a m e w o r k A d d r e s s e s b o t h n e t w o r k a n d a d m i n i s t r a t i v e a s p e c t s o f

m a n a g e m e n t

I E E E I E E E s t a n d a r d s a d o p t e d i n t e r n a t i o n a l l y A d d r e s s e s L A N a n d M A N m a n a g e m e n t A d o p t s O S I s t a n d a r d s s i g n i f i c a n t l y D e a l s w i t h f i r s t t w o l a y e r s o f O S I R M

W e b - b a s e dM a n a g e m e n t

W e b - B a s e d E n t e r p r i s e M a n a g e m e n t ( W B E M ) J a v a M a n a g e m e n t A p p l i c a t i o n P r o g r a m I n t e r f a c e ( J M A P I )

Chapter 3

3

OSI Architecture and Model

NetworkMangement

InformationModel

OrganizationModel

FunctionalModel

CommunicationModel

Figure 3.1 OSl Network Management Model

Chapter 3

4

SNMP Architecture and Model

NetworkMangement

InformationModel

OrganizationModel

FunctionalModel

CommunicationModel

Figure 3.1 OSl Network Management Model

Chapter 3

5

TMN Architecture• Addresses management of telecommunicationnetworks

• Based on OSI model

• Superstructure on OSI network

• Addresses network, service, and business management

Chapter 3

6

Organizational Model• Manager

• Sends requests to agents• Monitors alarms• Houses applications• Provides user interface

• Agent• Gathers information from objects• Configures parameters of objects• Responds to managers’ requests• Generates alarms and sends them tomangers

• Managed object• Network element that is managed• Houses management agent• All objects are not managed / manageable

Chapter 3

7

Manager

Managed objects

Unmanaged objects

Figure 3.2 Two-Tier Network Mangement Organization Model

Agent process

MDB

MDB Management Database

Two-Tier ModelChapter 3

8

Agent / Manager

Managed objects

Agent process

Manager

Figure 3.3 Three-Tier Network Mangement Organization Model

MDB

MDB

MDB Management Database

Three-Tier Model

Chapter 3

9

MoM

AgentAgent NMS

Manager

Managed objectsManaged objects

Figure 3.4 Network Mangement Organization Model with MoM

Agent process

MDB

MDB MDB

MoM Manager of ManagersMDB Management Database

AgentManager

Agent NMS

AgentAgent NMS

Manager

Manager of ManagersChapter 3

10

Manager NMS

Agent NMS

Agent NMS

Manager NMS

Figure 3.5 Dual Role of Management Process

Peer NMSsChapter 3

11

Information Model: Analogy• Figure in a book uniquely identified by

• ISBN, Chapter, and Figure number in thathierarchical order

• ID: {ISBN, chapter, figure}

• The three elements above define the syntax

• Semantics is the meaning of the threeentities according to Webster’s dictionary

• The information comprises syntax and semanticsabout an object

Chapter 3

12

Structure of Management Information (SMI)

• SMI defines for a managed object• Syntax• Semantics• plus additional information such as status

• ExamplesysDescr: { system 1 }

Syntax: OCTET STRINGDefinition: "A textual description of the entity. "Access: read-onlyStatus: mandatory

Chapter 3

13

Management Information Base (MIB)

• Information base contains information about objects

• Organized by grouping of related objects

• Defines relationship between objects

• It is NOT a physical database. It is a virtualdatabase that is compiled into management module

Chapter 3

14

Information Base View: An Analogy

• Fulton County library system has many branches

• Each branch has a set of books

• The books in each branch is a different set

• The information base of the county has the view (catalog) of all books

• The information base of each branch has the catalog of books that belong to that branch.That is, each branch has its view (catalog) ofthe information base

• Let us apply this to MIB view

Chapter 3

15

MIB View and Access of an Object

• A managed object has many attributes - itsinformation base

• There are several operations that can beperformed on the objects

• A user (manager) can view and perform onlycertain operations on the object by invokingthe management agent

• The view of the object attributes that the agentperceives is the MIB view

• The operation that a user can perform is the MIB access

Chapter 3

16

Management Data Base / Information Base

Manager

Managed objects

MDB MIB

Agent process

MDB Management DatabaseMIB Management Information Base

Figure 3.6 Network Configuration with Data and Information Base

Chapter 3

17

Managed Object• Managed objects can be

• Network elements (hardware, system)• hubs, bridges, routers, transmission facilities

• Software (non-physical)• programs, algorithms

• Administrative information• contact person, name of group of objects (IP group)

Chapter 3

18

Root

Level 1

Level 2

Level 3

Figure 3.7 Generic Representation of Management Information Tree

Management Information Tree

Chapter 3

19

iso-itu2

itu0

iso1

org3

dod6

internet1

Figure 3.8 OSI Management Information Tree

OSI Management Information TreeChapter 3

20

• Type

• Name

• Syntax

• Definition

• Status

• Access

• Instance

Object Type and Instance

Chapter 3

21

Managed Object:Internet Perspective

Object Type:Object ID and

Descriptorcircle

Access:Access

privilege

Defintion:Semantics -

textual description

Status:Implementaionrequirements

Syntax :model of object

Figure 3.9(a) Internet Perspective

Chapter 3

22

Behaviour

Object Class:Circularobject

Ob

ject

Cla

ss:

Ellip

tica

l

ob

ject

Attributes:circle, dimension

Operations:Push

Attributes:ellipse, dimension

Notifications:Notify changes inattribute values

Figure 3.9(b) OSI Perspective

Managed Object:OSI Perspective

Chapter 3

23

C h a r a c t e r is t ic s E x a m p le O b je c t t y p e P k tC o u n te r

S y n ta x C o u n te r

A c c e s s R e a d - o n ly

S ta tu s M a n d a to r y

D e s c r ip t io n C o u n ts n u m b e r o f p a c k e ts

F ig u r e 3 .1 0 ( a ) In t e r n e t P e r s p e c t iv e

C h a r a c t e r is t ic s E x a m p le O b je c t c la s s P a c k e t C o u n te r

A t t r ib u te s S in g le - v a lu e d

O p e r a t io n s g e t , s e t

B e h a v io r R e t r ie v e s o r r e s e ts v a lu e s

N o t i f ic a t io n s G e n e r a te s n o t i f ic a t io n s o n n e w v a lu e

F ig u r e 3 .1 0 ( b ) O S I P e r s p e c t iv e

F ig u r e 3 .1 0 P a c k e t C o u n t e r A s E x a m p le o f M a n a g e d O b je c t

Packet Counter ExampleChapter 3

24

Internet Vs OSI Managed Object• Scalar object in Internet Vs Object-orientedapproach in OSI

• OSI characteristics of operations, behaviour, andnotification are part of communication model inInternet: get/set and response/alarm

• Internet syntax is absorbed as part of OSI attributes

• Internet access is part of OSI security model

• Internet status is part of OSI conformance application

• OSI permits creation and deletion of objects;Internet does not: Enhancement in SNMPv2

Chapter 3

25

Mgmt. Communication Model

Manager Agent

Operations /Requests

Responses

Notifications /TrapsApplications Network Elements /

Managed Objects

Figure 3.11 Management Message Communication Model

Chapter 3

26

Transfer Protocols

ManagerApplications

ManagerCommunication

Module

Transport Layers

AgentApplications

AgentCommunication

Module

Transport Layers

Physical Medium

Operations / Requests / ResponsesTraps / Notifications

SNMP (Internet)CMIP (OSI)

UDP / IP (Internet) OSI Lower Layer Profiles (OSI)

Figure 3.12 Management Communication Transfer Protocols

Chapter 3

27

Abstract Syntax Notation One• ASN.1 is more than a syntax; it’s a language

• Addresses both syntax and semantics

• Two type of syntax• Abstract syntax: set of rules that specifydata type and structure for information storage

• Transfer syntax: set of rules for communicating information between systems

• Makes application layer protocols independent of lower layer protocols

• Can generate machine-readable code: BasicEncoding Rules (BER) is used in managementmodules

Chapter 3

28

Backus-Nauer Form (BNF)Definition:<name> ::= <definition>Rules:<digit> ::= 0|1|2|3|4|5|6|7|8|9<number> ::= <number> | <digit> <number><op> ::= +|-|x|/<SAE> ::= <number>|<SAE>|<SAE><op><SAE>Example:• 9 is primitive 9• 19 is construct of 1 and 9• 619 is construct of 6 and 19

Chapter 3

29

Simple Arithmetic Expression

<SAE> ::= <number> | <SAE><op><number>

Example: 26 = 13 x 2

Constructs and primitives

Chapter 3

30

Type and Value

• Assignments• <BooleanType> ::= BOOLEAN• <BooleanValue> ::= TRUE | FALSE

• ASN.1 module is a group of assignmentsperson-name Person-Name::=

{first "John",middle "I",last "Smith"}

Chapter 3

31

Data Type: Example 1P ersonne lR ecord ::= S E T

{ N am e, title G raph icS tring , d iv is ion C H O IC E m arke ting [0 ] S E Q U E N C E

{S ecto r, C oun try},

research [1 ] C H O IC E{product-based [0 ] N U LL, bas ic [1 ] N U LL},

p roduction [2 ] S E Q U E N C E{P roduct-line , C oun try } }

e tc .F igure 3 .13 AS N .1 D ata Type D efin ition E xam ple 1

Chapter 3

32

Data Type: Example 2

T r a d e - m e s s a g e : := S E Q U E N C E{ in v o ic e - n o IN T E G E R n a m e G r a p h ic S t r in g , d e ta i ls S E Q U E N C E O F

S E Q U E N C E{ p a r t - n o IN T E G E R q u a n t i t y IN T E G E R } ,

c h a r g e R E A L , a u th e n t ic a to r S e c u r i t y - T y p e }

S e c u r i t y - T y p e : := S E T{ …

…… }

F ig u r e 3 .1 4 A S N .1 D a t a T y p e D e f in i t io n E x a m p le 2

Chapter 3

33

ASN.1 Symbols

Symbol Meaning

::= Defined as

| or, alternative, options of a list

- Signed number

-- Following the symbol are comments

{} Start and end of a list

[] Start and end of a tag

() Start and end of subtype

.. Range

Chapter 3

34

• CHOICE

• SET

• SEQUENCE

• OF

• NULL

Keyword Examples

Chapter 3

35

ASN.1 Data Type Conventions

Data Types Convention Example

Object name Initial lowercase letter sysDescr, etherStatsPkts

Application data type Initial uppercase letter Counter, IpAddress

Module Initial uppercase letter PersonnelRecord

Macro, MIB module All uppercase letters RMON-MIB

Keywords All uppercase letters INTEGER, BEGIN

Chapter 3

36

Data Type: Structure & TagData Type

OtherTaggedStructuredSimple

Number

Tag

Structure

Class

Universal Application Context-specific Private

Figure 3.15 ASN.1 Data Type Structure and Tag

Chapter 3

37

Structure • Simple• PageNumber ::= INTEGER• ChapterNumber ::= INTEGER

• Structure / Construct• BookPageNumber ::=

SEQUENCE{ChapterNumber, Separator, PageNumber

Example: {1-1, 2-3, 3-39}• Tagged

• Derived from another type; given a new ID• In Fig. 3-14, INTEGER is either universal orapplication specific

• Other types: • CHOICE, ANY

• BookPages ::= SEQUENCE OF { BookPageNumber}or

BookPages ::= SEQUENCE OF{SEQUENCE

{ChapterNumber, Separator, PageNumber}}

Chapter 3

38

Tag

• Tag uniquely identifies a data type• Comprises class and tag number• Class:

• Universal - always true• Application - only in the application used• Context-specific - specific context in application• Private - used extensively by commercial vendors

Chapter 3

39

Enumerated Integer

RainbowColors ::= ENUMERATED

{

violet (0)

indigo (1)

blue (2)

green (3)

yellow (4)

orange (5)

red (6)

}

Chapter 3

40

ASN.1 Module Example

IpNetMediaEntry ::=SEQUENCE{

ipNetToMediaIfIndex INTEGER

ipNetToMediaPhysAddress PhysAddress

ipNetToMediaNetAddress IpAddress

ipNetToMediaType INTEGER}

Chapter 3

41

N a m e : J o h n P S m i t hT i t l e : D i r e c t o rE m p l o y e e N u m b e r 5 1D a t e o f H i r e : 1 7 S e p t e m b e r 1 9 7 1N a m e o f S p o u s e ; M a r y T S m i t hN u m b e r o f C h i l d r e n 2C h i l d I n f o r m a t i o n

N a m e R a l p h T S m i t hD a t e o f B i r t h 1 1 N o v e m b e r 1 9 5 7

C h i l d I n f o r m a t i o nN a m e S u s a n B J o n e sD a t e o f B i r t h 1 7 J u l y 1 9 5 9

( a ) I n f o r m a l d e s c r i p t i o n o f p e r s o n n e l r e c o r d- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -P e r s o n n e l R e c o r d : : = [ A P P L I C A T I O N 0 ] I M P L I C I T S E T {

N a m e ,t i t l e [ 0 ] V i s i b l e S t r i n g ,n u m b e r E m p l o y e e N u m b e r ,d a t e O f H i r e [ 1 ] D a t e ,n a m e O f S p o u s e [ 2 ] N a m e ,c h i l d r e n [ 3 ] I M P L I C I T S E Q U E N C E O F C h i l d I n f o r m a t i o n D E F A U L T { } }

C h i l d I n f o r m a t i o n : : = S E T {N a m e ,d a t e O f B i r t h [ 0 ] D a t e }

N a m e : : = [ A P P L I C A T I O N 1 ] I M P L I C I T S E Q U E N C E {g i v e n N a m e V i s i b l e S t r i n g ,i n i t i a l V i s i b l e S t r i n g ,f a m i l y N a m e V i s i b l e S t r i n g }

E m p l o y e e N u m b e r : : = [ A P P L I C A T I O N 2 ] I M P L I C I T I N T E G E R

D a t e : : = [ A P P L I C A T I O N 3 ] I M P L I C I T V i s i b l e S t r i n g - - Y Y Y Y M M D D ( b ) A S N . 1 d e s c r i p t i o n o f t h e r e c o r d s t r u c t u r e

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -{ { g i v e n N a m e “ J o h n ” , i n i t i a l “ T ” , f a m i l y N a m e “ S m i t h ” } ,

t i t l e “ D i r e c t o r ”n u m b e r “ 5 1 ”d a t e O f H i r e “ 1 9 7 1 0 9 1 7 ”n a m e O f S p o u s e { g i v e n N a m e “ M a r y ” , i n i t i a l “ T ” , f a m i l y N a m e “ S m i t h ” } ,c h i l d r e n{ { { g i v e n N a m e “ R a l p h ” , i n i t i a l “ T ” , f a m i l y N a m e “ S m i t h ” } , d a t e O f B i r t h “ 1 9 5 7 1 1 1 1 ” } , { { g i v e n N a m e “ S u s a n ” , i n i t i a l “ B ” , f a m i l y N a m e “ J o n e s ” } d a t e O f B i r t h “ 1 9 5 9 0 7 1 7 ” } } }

( c ) A S N . 1 d e s c r i p t i o n o f a r e c o r d v a l u e

42

Object Name

iso-itu2

iso1

itu0

org3

dod6

internet1

private4

enterprise1

IBM2

Chapter 3

43

TLV Encoding

Type Length Value

Class(7-8th bits)

P/C(6th bit)

Tag Number(1-5th bits)

Class 8th bit 7th bitUniversal 0 0Application 0 1Context-specific 1 0Private 1 1

Chapter 3

44

Macro< m a c r o n a m e > M A C R O : : =B E G I N

T Y P E N O T A T I O N : : = < s y n t a x O f N e w T y p e >V A L U E N O T A T I O N : : = < s y n t a x O f N e w V a l u e >< a u x i l i a r y A s s i g n m e n t s >

E N D

C S 8 8 0 3 O B J E C T - I D E N T I T YS T A T U S c u r r e n t

D E S C R I P T I O N " A g r a d u a t e - l e v e l n e t w o r km a n a g e m e n t c o u r s e o f f e r e d e v e r y f a l l b yC o l l e g e o f C o m p u t i n g i n G e o r g i a I n s t i t u t e o fT e c h n o l o g y . "

: : = { c s c l a s s e s 5 0 }

Example:

Chapter 3

45

Functional Model

OSIFunctional Model

FaultManagement

ConfigurationManagement

PerformanceManagement

SecurityManagement

AccountingManagement

Chapter 3

46