Chapter 3
Basic Foundations: Standards, Models, and Language
Chapter 3
Basic Foundations:
Standards, Models, and Language
Network Management: Principles and Practices
© Mani Subramanian 2011
1
Chapter 3
Basic Foundations: Standards, Models, and Language
Objectives
• Standards, Models, and Language needed for
network management
• Network Models
• OSI
• Internet
• TMN
• IEEE 802
• Web-based
• Management communication protocols
• SNMP
• CMIP
• XML
• CORBA
• ASN.1 language
• Syntax
• Macro
• Basic encoding rule
• Management application functions
Network Management: Principles and Practices
© Mani Subramanian 2011
2
Chapter 3
Basic Foundations: Standards, Models, and Language
Introduction
• Standards
• Standards organizations
• Protocol standards of transport layers
• Protocol standards of management
(application) layer
• Management Models
• Language
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
3
Chapter 3
Basic Foundations: Standards, Models, and Language
Table 3.1 Network Management Standards
Standard
OSI / CMIP
(Common
Management
Information
Protocol)
Internet /
SNMP
(Simple
Network
Management
Protocol)
TMN
(Telecom
Management
Network)
Salient Points
1. International standard (ISO/OSI)
2. Management of data communications network - LAN and WAN
3. Deals with all 7 layers
4. Most complete
5. Object oriented – classes, inheritance
6. Well structured and layered
7. Consumes large resource in implementation – complex
1. Industry standard (IETF)
2. Originally intended for management of Internet components,
currently adopted for WAN and telecommunication systems
3. Easy to implement – uses scalar objects
4. Most widely implemented
1. International standard (ITU-T)
2. Management of telecommunications network – service providers
3. Based on OSI network management framework
4. Addresses both network and administrative aspects of
management – Service and Business Management
5. eTOM industry standard for business processes for implementing
TMN using NGOSS framework
IEEE
1. IEEE standards adopted internationally
2. Addresses LAN and MAN management
3. Adopts OSI standards significantly
4. Deals with first two layers of OSI RM – Physical and Data Link
Emerging
Technologies
1. Web-Based Enterprise Management (WBEM)
2. Java Management Extension (JMX)
3. XML-Based Network Management
4.CORBA-based Network Management
Network Management: Principles and Practices
© Mani Subramanian 2011
4
Chapter 3
Basic Foundations: Standards, Models, and Language
OSI Architecture and Model
Network
Management
Organization
Model
Information
Model
Communication
Model
Functional
Model
Figure 3.1 OSl Network Management Model
Notes
• Organization
• Network management components
• Functions of components
• Relationships
• Information
• Structure of management information (SMI)
• Syntax and semantics
• Management information base (MIB)
• Organization of management information
• Object-oriented
Network Management: Principles and Practices
© Mani Subramanian 2011
5
Chapter 3
Basic Foundations: Standards, Models, and Language
OSI Architecture and Model (cont.)
Network
Management
Organization
Model
Information
Model
Communication
Model
Functional
Model
Figure 3.1 OSl Network Management Model
Notes
• Communication
• Transfer syntax with bidirectional messages
• M-SET, M-GET
• Transfer structure (PDU)
• Functional – User oriented requirements of NM
• Application functions (Covered in chapter 11)
• Configure components (CM)
• Monitor components (FM)
• Measure performance (PM)
• Secure information (SM)
• Usage accounting (AM)
Network Management: Principles and Practices
© Mani Subramanian 2011
6
Chapter 3
Basic Foundations: Standards, Models, and Language
SNMP Architecture and Model
(Not defined explicitly)
Network
Management
Organization
Model
Information
Model
Communication
Model
Functional
Model
Notes
• Organization
• Same as OSI model
• Information
• Same as OSI, but scalar
• Communication
• Messages less complex than OSI and unidirectional
(request, response)
• Transfer structure (PDU)
• Functions
• Application functions (less defined than OSI)
• Fault management
• Configuration management
• Account management – not addressed
• Performance management
• Security management – community-based
Network Management: Principles and Practices
© Mani Subramanian 2011
7
Chapter 3
Basic Foundations: Standards, Models, and Language
TMN Architecture
• Addresses management of telecommunication
networks
• Based on OSI model
• Superstructure on OSI network
• Addresses network, service, and business
management
• See chapter 10 for more details
Business Management
q3
Service Management
q3
Network Management
q3
Element Management
q3
Managed Network Element
Figure 10.11 TMN Service Architecture
Network Management: Principles and Practices
© Mani Subramanian 2011
8
Chapter 3
Basic Foundations: Standards, Models, and Language
Example (NMF)
TMN Logical
Layered Architecture
Business
Management
q3
Ref. Point
Service
Management
q3
Ref. Point
Network
Management
q3
Ref. Point
Element
Management
Physical Realization of
TMN Architecture
Customer
Service
Management
Q3
Service
Details
Service Mgmt
Tarif/Charging
Service Mgmt
Provisioning
Service
Configuration
Net Mgmt
Routing Admin
Equipment
Configuration
Net Element
Cust Admin
Q3
Performance and
Billing Data
Service Mgmt
Other
Serviceimpacting
Events
Net Mgmt
Traffic Admin
Q3
Net Mgmt
Restoration
Equipment
Alarms
Net Element
Switch Mgmt
Net Element
Trans Eqpt
Mgmt
Figure 10.14 TMN Realization Example (NMF)
Network Management: Principles and Practices
© Mani Subramanian 2011
9
Chapter 3
Basic Foundations: Standards, Models, and Language
Organizational Model
• Manager
• Manages the managed elements
• Sends requests to agents, retrieves
management information & stores it in MDB
• Monitors alarms – unsolicited traps/notifications
from agents
• Houses applications, e.g., CM, FM, etc.
• Provides user interface, e.g., HPOpenview
• Agent
• Gathers information from objects – get
• Configures parameters of objects – set
• Responds to managers’ requests – response
• Generates alarms and sends them to
managers (unsolicited) – trap
• Managed object
• Network element that is managed, e.g., hubs,
bridges, etc.
• Houses management agent – process running
• All objects are either not managed or
manageable (more expensive)
Network Management: Principles and Practices
© Mani Subramanian 2011
10
Chapter 3
Basic Foundations: Standards, Models, and Language
Two-Tier Model
MDB
Manager
Managed objects
Unmanaged objects
MDB Management Database
Agent process
Figure 3.2 Two-Tier Network Management Organization Model
Notes
• Agent built into network element
Example: Managed hub, managed router
• An agent can manage multiple elements
Example: Switched hub, ATM switch
• MDB is a physical database
• Unmanaged objects are network elements
that are not managed - both physical (unmanaged
hub) and logical (passive elements)
Network Management: Principles and Practices
© Mani Subramanian 2011
11
Chapter 3
Basic Foundations: Standards, Models, and Language
Three-Tier Model
MDB
Manager
MDB
Agent / Manager
Managed objects
MDB Management Database
Agent process
Figure 3.3 Three-Tier Network Management Organization Model
Notes
• Middle layer plays the dual role
• Agent to the top-level manager
• Manager to the managed objects - e.g., collects data
• Example of middle level: Remote monitoring
agent (RMON)
• Examples:
• Statistical measurement on a network
• Local site passes information to a remote site
Network Management: Principles and Practices
© Mani Subramanian 2011
12
Chapter 3
Basic Foundations: Standards, Models, and Language
Manager of Managers
MoM
MDB
Agent
Agent NMS
Manager
Agent
Agent NMS
MDB
Manager
MDB
Managed objects
Managed objects
Agent NMS
MoM Manager of Managers
MDB Management Database
Agent
Manager
Agent process
Figure 3.4 Network Management Organization Model with MoM
Notes
• Agent NMS manages the domain
• MoM presents integrated view of domains
• Domain may be geographical (cities), administrative
(departments), vendor-specific products (Cisco), etc.
Network Management: Principles and Practices
© Mani Subramanian 2011
13
Chapter 3
Basic Foundations: Standards, Models, and Language
Peer NMSs
Agent NMS
Manager NMS
Manager NMS
Agent NMS
Figure 3.5 Dual Role of Management Process
Notes
• NMSs configured in a peer-to-peer relationship
• Network management system acts as peers
• Dual role of both NMSs
• Example: Two network service providers exchange
Management information
• Dumbbell architecture discussed in Chapter 1 (see
next slide)
• Notice that the manager and agent functions are
processes and not systems
Network Management: Principles and Practices
© Mani Subramanian 2011
14
Chapter 3
Basic Foundations: Standards, Models, and Language
Interoperability
NMS
Vendor A
Messages
Services & Protocols
NMS
Vendor B
Network
Agent
Network
Agent
Network
Agent
Network
Agent
Network
Objects
Network
Objects
Network
Objects
Network
Objects
Figure 1.26 Network Management Interoperability
Application
Services
Objects
Vendor A
Objects
Management
Protocol
Vendor B
Objects
Objects
Transport
Protocols
(b) Services and Protocols
Figure 1.24 Network Management Dumbbell Architecture
Notes
• Message exchange between NMSs managing
different domains
Network Management: Principles and Practices
© Mani Subramanian 2011
15
Chapter 3
Basic Foundations: Standards, Models, and Language
Information Model: Analogy
• Information model – Structure & storage of information
• Figure in a book uniquely identified by
• ISBN, Chapter, and Figure number in that
hierarchical order
• ID: {ISBN, chapter, figure} – Hierarchy of designation
• The three elements above define the syntax – format
• Semantics is the meaning of the three entities
according to Webster’s dictionary
• The information comprises syntax and semantics
about an object
Notes
• Management information model =
objects representation (SMI) +
management information of objects (MIB)
• SMI defines the syntax & semantics of management
information stored in the MIB
• Information model specifies the information base to
describe managed objects and their relationships
(i.e., MIB)
Network Management: Principles and Practices
© Mani Subramanian 2011
16
Chapter 3
Basic Foundations: Standards, Models, and Language
Structure of Management Information
(SMI)
• SMI defines for a managed object
• Syntax
• Semantics – i.e., definition
• Plus additional information such as status
• Example
sysDescr:
{ system 1 }
Syntax:
OCTET STRING
Definition: "A textual description of the entity. "
Access:
read-only
Status:
mandatory
Notes
• Uses ASN.1: Abstract Syntax Notation One
• See RFC 1155:
• Section 4. Managed objects
• Section 4.3. Macros
Network Management: Principles and Practices
© Mani Subramanian 2011
17
Chapter 3
Basic Foundations: Standards, Models, and Language
Management Information Base (MIB)
• Used by manager & agents to store & exchange
management information
• Information base contains information about objects
• Organized by grouping of related objects (e.g., IP
group)
• Defines relationship between objects (e.g., object
system is a parent of object sysDescr)
• It is NOT a physical database. It is a virtual
database that is compiled into management module
Notes
• The agent MIB is used for accessing local information
requested by the manager, and sending a response back
• The manager MIB is used for accessing information
on all network components the manager manages.
• See RFC 1213
Network Management: Principles and Practices
© Mani Subramanian 2011
18
Chapter 3
Basic Foundations: Standards, Models, and Language
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) of
the information base
• Let us apply this to MIB view
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
19
Chapter 3
Basic Foundations: Standards, Models, and Language
MIB View and Access of an Object
• A managed object has many attributes - its
information base (e.g., IPAddress, # of ports)
• There are several operations that can be
performed on the objects (get, set)
• A user (manager) can view and perform only
certain operations on the object by invoking
the management agent – privileges depends on
the user and the managed object
• The view of the object attributes that the agent
perceives is the MIB view
• The operation that a user can perform is the
MIB access
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
20
Chapter 3
Basic Foundations: Standards, Models, and Language
Management Data Base / Information Base
Manager
MDB
MIB
MDB Management Database
MIB Management Information Base
Agent process
Managed objects
Figure 3.6 Network Configuration with Data and Information Base
Notes
• Distinction between MDB and MIB
• MDB physical database; e.g., Oracle, Sybase
• MIB virtual database; schema compiled into
management software (for processes to
exchange information).
• An NMS can automatically discover a managed
object, such as a hub, when added to the network
• The NMS can identify the new object as hub only
after the MIB schema of the hub is compiled into
NMS software.
Network Management: Principles and Practices
© Mani Subramanian 2011
21
Chapter 3
Basic Foundations: Standards, Models, and Language
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)
Notes
• In fact, any type of info that can be included in the
MIB can be managed.
Network Management: Principles and Practices
© Mani Subramanian 2011
22
Chapter 3
Basic Foundations: Standards, Models, and Language
Management Information Tree
Root
Level 1
Level 2
Level 3
Figure 3.7 Generic Representation of Management Information Tree
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
23
Chapter 3
Basic Foundations: Standards, Models, and Language
OSI Management Information Tree
itu
0
iso
1
iso-itu
2
org
3
dod
6
internet
1
Figure 3.8 OSI Management Information Tree
Notes
• iso
International Standards Organization
itu
International Telecommunications Union
dod Department of Defense
• Designation:
• iso
1
• org
1.3
• dod
1.3.6
• internet 1.3.6.1 – all internet managed
objects will start with this
Network Management: Principles and Practices
© Mani Subramanian 2011
24
Chapter 3
Basic Foundations: Standards, Models, and Language
Object Type and Instance
• Type
• Name
• Syntax
• Definition
• Status
• Access
• Instance
Notes
• Example of a circle
• “circle” is syntax
• Semantics is definition from dictionary
“A plane figure bounded by a single curved
line, every point of which is of equal distance
from the center of the figure.”
• Analogy of nursery school
Network Management: Principles and Practices
© Mani Subramanian 2011
25
Chapter 3
Basic Foundations: Standards, Models, and Language
Managed Object:
Internet Perspective
Access:
Access
privilege
Object Type:
Object ID and
Descriptor
circle
Status:
Implementaion
requirements
Syntax :
model of object
Defintion:
Semantics textual description
Figure 3.9(a) Internet Perspective
Notes
 object ID
unique ID
and descriptor
 syntax
and name for the object
used to model the object
 access
access privilege to a managed object
 status
implementation requirements
 definition
textual description of the semantics
of object type
Network Management: Principles and Practices
© Mani Subramanian 2011
26
Chapter 3
Basic Foundations: Standards, Models, and Language
Managed Object:
OSI Perspective
Object Class:
Circular
object
Behaviour
Object Class:
Elliptical
object
Notifications:
Notify changes in
attribute values
Operations:
Push
Attributes:
circle, dimension
Attributes:
ellipse, dimension
Figure 3.9(b) OSI Perspective
Notes
 object class
managed object
 attributes
attributes visible at its boundary
 operations
operations which may be applied to it
 behaviour
behavior exhibited by it in response to operation
 notifications
notifications emitted by the object
Network Management: Principles and Practices
© Mani Subramanian 2011
27
Chapter 3
Basic Foundations: Standards, Models, and Language
Packet Counter Example
Characteristics
Example
Object type
PktCounter
Syntax
Counter
Access
Read-only
Status
Mandatory
Description
Counts number of packets
Figure 3.10(a) Internet Perspective
Characteristics
Example
Object class
Packet Counter
Attributes
Single-valued
Operations
get, set
Behavior
Retrieves or resets values
Notifications
Generates notifications on new
value
Figure 3.10 (b) OSI Perspective
Figure 3.10 Packet Counter As Example of Managed Object
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
28
Chapter 3
Basic Foundations: Standards, Models, and Language
Internet vs. OSI Managed Object
• Scalar object in Internet vs. Object-oriented
approach in OSI
• OSI characteristics of operations, behavior, and
notification are part of communication model in
Internet: 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. However, enhancement in SNMPv2
include:
• Defining new data types
• Adding or deleting conceptual rows in tables
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
29
Chapter 3
Basic Foundations: Standards, Models, and Language
Mgmt. Communication Model
Operations / Requests
Manager
Applications
Responses
Agent
Notifications / Traps
Network Elements /
Managed Objects
Figure 3.11 Management Message Communication Model
Notes
• In Internet requests/responses, in OSI operations
• In Internet traps and notifications (SNMPv2), in
OSI notifications
Network Management: Principles and Practices
© Mani Subramanian 2011
30
Chapter 3
Basic Foundations: Standards, Models, and Language
Transfer Protocols
Manager
Applications
Operations / Requests / Responses
Traps / Notifications
Agent
Applications
Manager
Communication
Module
SNMP (Internet)
CMIP (OSI)
Agent
Communication
Module
Transport Layers
UDP / IP (Internet)
OSI Lower Layer Profiles (OSI)
Transport Layers
Physical Medium
Figure 3.12 Management Communication Transfer Protocols
Notes
• Internet is based on SNMP; OSI is based on CMIP
• OSI uses CMISE (Common Management Information
Service Element) application with CMIP
• OSI specifies both c-o and connectionless transport
protocol; SNMPv2 extended to c-o, but rarely used
Network Management: Principles and Practices
© Mani Subramanian 2011
31
Chapter 3
Basic Foundations: Standards, Models, and Language
Abstract Syntax Notation One
• ASN.1 is more than a syntax; it’s a formal language
• Addresses both syntax and semantics
• Two types of syntax
• Abstract syntax: set of rules that specify
data 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: Basic
Encoding Rules (BER) is used in management
modules
Notes
• ASN.1 developed jointly by ITU-T and ISO
• Abstract syntax → Information model
• Transfer syntax → Communication model
Network Management: Principles and Practices
© Mani Subramanian 2011
32
Chapter 3
Basic Foundations: Standards, Models, and Language
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
Notes
• BNF is used for ASN.1 constructs
• Constructs developed from primitives
• The above example illustrates how numbers
are constructed from the primitive <digit>
• Simple Arithmetic Expression entity (<SAE>) is
constructed from the primitives <digit> and
<op>
Network Management: Principles and Practices
© Mani Subramanian 2011
33
Chapter 3
Basic Foundations: Standards, Models, and Language
Simple Arithmetic Expression
<SAE> ::= <number> | <SAE><op><number>
Example: 26 = 13 x 2
Constructs and primitives
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
34
Chapter 3
Basic Foundations: Standards, Models, and Language
Type and Value
• Assignments
• <BooleanType> ::= BOOLEAN
• <BooleanValue> ::= TRUE | FALSE
• ASN.1 module is a group of assignments
person-name Person-Name::=
{
first
"John",
middle “T",
last
"Smith"
}
Notes
• Two basic parameters associated with
an entity (e.g., BOOLEAN)
• Data type
• Value (assigned to this data type)
• Keywords: entities with all capital letters
(e.g., TRUE)
Network Management: Principles and Practices
© Mani Subramanian 2011
35
Chapter 3
Basic Foundations: Standards, Models, and Language
Data Type: Example 1
PersonnelRecord ::= SET
{
Name,
title
GraphicString,
division CHOICE
marketing
[0] SEQUENCE
{Sector,
Country},
research
[1] CHOICE
{product-based [0] NULL,
basic
[1] NULL},
production
[2] SEQUENCE
{Product-line,
Country }
}
etc.
Figure 3.13 ASN.1 Data Type Definition: Example 1
Notes
• Module name starts with capital letters
• Data types:
• Primitives: NULL, GraphicString
• Constructs
• Alternatives : CHOICE
• List maker: SET, SEQUENCE
• Repetition: SET OF, SEQUENCE OF:
• Difference between SET and SEQUENCE
Network Management: Principles and Practices
© Mani Subramanian 2011
36
Chapter 3
Basic Foundations: Standards, Models, and Language
Data Type: Example 2
Trade-message ::= SEQUENCE
{invoice-no
INTEGER
name
GraphicString,
details
SEQUENCE OF
SEQUENCE
{part-no
INTEGER
quantity
INTEGER},
charge
REAL,
authenticator
Security-Type}
Security-Type ::= SET
{
…
…
… }
Figure 3.14 ASN.1 Data Type Definition: Example 2
Notes
• SET
– No order required
– Order not important
– Data types should all be distinct
• SEQUENCE
– The order in the list is maintained
• SEQUENCE OF SEQUENCE makes tables of rows
Network Management: Principles and Practices
© Mani Subramanian 2011
37
Chapter 3
Basic Foundations: Standards, Models, and Language
Modules
Formal Definition:
<module name> DEFINITIONS ::= BEGIN
<name> ::= <definition>
<name> ::= <definition>
END
Example:
RFC1213 DEFINITIONS ::= BEGIN
…
…
END
Notes
• A module is a group of assignments.
• Modules can be imported into and exported
from other modules.
Network Management: Principles and Practices
© Mani Subramanian 2011
38
Chapter 3
Basic Foundations: Standards, Models, and Language
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
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
39
Chapter 3
Basic Foundations: Standards, Models, and Language
Keyword Examples
• CHOICE
• SET
• SEQUENCE
• OF
• NULL
Notes
• Keywords are in all UPPERCASE letters
Network Management: Principles and Practices
© Mani Subramanian 2011
40
Chapter 3
Basic Foundations: Standards, Models, and Language
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
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
41
Chapter 3
Basic Foundations: Standards, Models, and Language
Data Type: Structure & Tag
Data Type
Tag
Structure
Number
Simple
Structured
Tagged
Other
Universal
Class
Application
Contextspecific
Private
Figure 3.15 ASN.1 Data Type: Structure and Tag
Notes
• A Data Type is defined based on a structure and a tag
• Structure defines how data type is built
• Tag uniquely identifies the data type
Network Management: Principles and Practices
© Mani Subramanian 2011
42
Chapter 3
Basic Foundations: Standards, Models, and Language
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 or
application specific
• Other types:
• CHOICE, ANY
Notes
• BookPages ::= SEQUENCE OF { BookPageNumber}
or
BookPages ::=
SEQUENCE OF
{
SEQUENCE
{ChapterNumber, Separator, PageNumber}
}
Network Management: Principles and Practices
© Mani Subramanian 2011
43
Chapter 3
Basic Foundations: Standards, Models, and Language
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
vendorsvendors
• Example (RFC 1155):
• IpAddress ::= [APPLICATION 0] IMPLICIT OCTET
STRING (SIZE (4))
• Counter ::= [APPLICATION 1] IMPLICIT INTEGER
(0..4294967295)
Notes
Example:
BOOLEAN
Universal 1
INTEGER
Universal 2
research
Application [1] (Figure 3.13)
product-based Context-specific under research [0]
Network Management: Principles and Practices
© Mani Subramanian 2011
44
Chapter 3
Basic Foundations: Standards, Models, and Language
Enumerated Integer
RainbowColors ::= ENUMERATED
{
}
violet
(0)
indigo
(1)
blue
(2)
green
(3)
yellow
(4)
orange
(5)
red
(6)
Example From the SNMP MIB (RFC
1157):
ErrorStatus ::=
INTEGER {
noError (0),
tooBig (1),
noSuchName (2),
badValues (3),
readOnly(4),
genErr (5)
}
Notes
• ENUMERATED is a special case of INTEGER
• Does not have INTEGER semantics → Arithmetic
operations should not be performed on enumerated
values.
• Example: RainbowColors (5) is orange
Network Management: Principles and Practices
© Mani Subramanian 2011
45
Chapter 3
Basic Foundations: Standards, Models, and Language
Subtype Data Type
• A subtype data type is derived from a
parent type.
Example:
PageNumber ::= INTEGER (0..255)
→ Limits the maximum page number to 255
Example (RFC 1213):
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS …
…
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
46
Chapter 3
Basic Foundations: Standards, Models, and Language
ASN.1 Module Example
• An entry of the address translation table in
SNMP IP MIB (RFC 1213) is the following:
IpNetMediaEntry ::=SEQUENCE{
ipNetToMediaIfIndex
INTEGER
ipNetToMediaPhysAddress
PhysAddress
ipNetToMediaNetAddress
IpAddress
ipNetToMediaType
INTEGER}
Notes
Network Management: Principles and Practices
© Mani Subramanian 2011
47
Chapter 3
Basic Foundations: Standards, Models, and Language
ASN.1 Example from ISO 8824
Name:
John T Smith
Title:
Director
Employee Number 51
Date of Hire:
17 September 1971
Name of Spouse; Mary T Smith
Number of Children 2
Child Information
Name
Ralph T Smith
Date of Birth 11 November 1957
Child Information
Name
Susan B Jones
Date of Birth 17 July 1959
(a) Informal description of personnel record
--------------------------------------------------------------------------------------------------------PersonnelRecord ::= [APPLICATION 0] IMPLICIT SET {
Name,
title [0] VisibleString,
number EmployeeNumber,
dateOfHire [1] Date,
nameOfSpouse [2] Name,
children [3] IMPLICIT SEQUENCE OF ChildInformation DEFAULT { } }
ChildInformation ::= SET {
Name,
dateOfBirth [0] Date }
Name ::= [APPLICATION 1] IMPLICIT SEQUENCE {
givenName VisibleString,
initial VisibleString,
familyName VisibleString }
EmployeeNumber ::= [APPLICATION 2] IMPLICIT INTEGER
Date ::= [APPLICATION 3] IMPLICIT VisibleString -- YYYYMMDD
(b) ASN.1 description of the record structure
--------------------------------------------------------------------------------------------------------{
{givenName “John”, initial “T”, familyName “Smith”},
title
“Director”
number
51
dateOfHire
“19710917”
nameOfSpouse
{givenName “Mary”, initial “T”, familyName “Smith”},
children
{{
{givenName “Ralph”, initial “T”, familyName “Smith”},
dateOfBirth
“19571111”},
{
{givenName “Susan”, initial “B”, familyName “Jones”}
dateOfBirth
“19590717”}}}
(c) ASN.1 description of a record value
Network Management: Principles and Practices
© Mani Subramanian 2011
48
Chapter 3
Basic Foundations: Standards, Models, and Language
Object Name
itu
0
iso
1
iso-itu
2
org
3
dod
6
internet
1
private
4
enterprise
1
IBM
2
Notes
• Example from RFC 1155:
internet OBJECT IDENTIFIER ::= {iso(1) org(3) dod(6) 1}
Network Management: Principles and Practices
© Mani Subramanian 2011
49
Chapter 3
Basic Foundations: Standards, Models, and Language
TLV Encoding
Type
Length
Class
(7-8th bits)
P/C
(6th bit)
Class
Universal
Application
Context-specific
Private
Value
Tag Number
(1-5th bits)
8th bit
0
0
1
1
7th bit
0
1
0
1
P/C bit:
0: primitive
1: construct
Notes
• ASN.1 syntax containing management info is encoded
using the BER (Basic Encoding Rules) → defined for
the transfer syntax.
• ASCII text data is converted to bit-oriented data.
• TLV: Type, Length, and Value are components
of the structure.
• Length: of the Value field in number of octets.
• Value: is encoded based on the data type.
Network Management: Principles and Practices
© Mani Subramanian 2011
50
Chapter 3
Basic Foundations: Standards, Models, and Language
TLV Encoding- INTEGER
Type
Class
(7-8th bits)
Class
Universal
Application
Context-specific
Private
Length
P/C
(6th bit)
th
Value
Tag Number
(1-5th bits)
th
8 bit 7 bit
0
0
0
1
1
0
1
1
P/C bit:
0: primitive
1: construct
• INTEGER: Universal 2
• Type: 00000010 [Class (00), P/C (0), Tag (00010)]
• Length:
• If Value length ≤ 127 → Use 1 octet (with b8 = 0)
• If Value length > 127 → Use >1 octet (with b8 = 1)
 First octet indicates number of octets
that follow to specify the Value length.
 Example: 128 → 10000001 10000000
• Value:
• If Value > 0 (always MSB = 0 → add more octets if needed)
 Example: 255 → 00000000 11111111
• If Value < 0 → twos-complement
 Takes the absolute value and inverts all 1s to 0s
and all 0s to 1s, then adds 1.
 Example: -5 → 11111011
• Example: TLV for 255
→ 00000010 00000010 00000000 11111111
Network Management: Principles and Practices
© Mani Subramanian 2011
51
Chapter 3
Basic Foundations: Standards, Models, and Language
TLV Encoding- OCTET STRING
Type
Class
(7-8th bits)
Class
Universal
Application
Context-specific
Private
Length
P/C
(6th bit)
th
Value
Tag Number
(1-5th bits)
th
8 bit 7 bit
0
0
0
1
1
0
1
1
P/C bit:
0: primitive
1: construct
Notes
• OCTET STRING: Universal 4
• Type: 00000100 [Class (00), P/C (0), Tag (00100)]
• Length: Number of octets in Value.
• Value: Binary representation of string.
• Example: TLV for ‘0C1B’ →
00000100 00000010 00001100 00011011
Network Management: Principles and Practices
© Mani Subramanian 2011
52
Chapter 3
Basic Foundations: Standards, Models, and Language
Macro
<macroname> MACRO ::=
BEGIN
TYPE NOTATION ::= <syntaxOfNewType>
VALUE NOTATION ::= <syntaxOfNewValue>
<auxiliaryAssignments>
END
Macro from RFC 2578 (SMIv2):
OBJECT-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::= value (VALUE OBJECT IDENTIFIER)
Status ::= "current" | "deprecated" | "obsolete“
ReferPart ::= "REFERENCE" Text | empty
Text ::= value(IA5String)
END
Example:
CS8803 OBJECT-IDENTITY
STATUS
current
DESCRIPTION "A graduate-level network
management course offered every fall by
College of Computing in Georgia Institute of
Technology."
::= {csclasses 50}
Notes
• Macro is used to create new data types
• TYPE NOTATION → defines the syntax of new types
• VALUE NOTATION → defines the syntax of new values
Network Management: Principles and Practices
© Mani Subramanian 2011
53
Chapter 3
Basic Foundations: Standards, Models, and Language
Functional Model
OSI
Functional Model
Configuration
Management
Fault
Management
Performance
Management
Security
Management
Accounting
Management
Notes
• Configuration management
• Set and change network configuration and
component parameters
• Network provisioning
• Inventory management
• Network topology
• Set up alarm thresholds
• Fault management
• Detection and isolation of failures in network
• Trouble ticket administration
• Performance management
• Monitor performance of network
• Security management
• Authentication
• Authorization
• Encryption
• Accounting management
• Functional accounting of network usage
Network Management: Principles and Practices
© Mani Subramanian 2011
54