Network management
Chapter 3
Basic Foundations of NM:
Standards, Models, and Language
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
*
Network Management: Principles and Practice
© Mani Subramanian 2010
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
*
*
Notes
We have standards in, almost, everything
- Introduction
- Standards
- Standards organizations
- Protocol standards of transport layers
- Protocol standards of management (application) layer
- Management Models
- Language
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
3.1 Network management standards
A standard = a widely used model
organizations working on NMS
*
Table 3.1 Network Management Standards
Chapter 3 Basic Foundations: Standards, Models, and Language
*
| Standard | Salient Points |
| CMIP /OSI | International standard (ISO/OSI) Management of data communications network - LAN and WAN Deals with all 7 layers Most complete Object oriented Well structured and layered 7. Consumes large resource in implementation |
| SNMP / Internet | Industry standard (IETF) Originally intended for management of Internet components, currently adopted for WAN and telecommunication systems Easy to implement Most widely implemented |
| TMN | International standard (ITU-T) Management of telecommunications network Based on OSI network management framework Addresses both network and administrative aspects of management eTOM industry standard for business processes for implementing TMN using NGOSS framework |
| IEEE | IEEE standards adopted internationally Addresses LAN and MAN management Adopts OSI standards significantly Deals with first two layers of OSI model |
| Web-based Management | Web-Based Enterprise Management (WBEM) Java Management Extension (JMX) XML-Based Network Management CORBA-based Network Management |
Common mngt information protocol, common mgt information services
*
Notes
OSI NM Model
Network Management: Principles and Practice
© Mani Subramanian 2010
- Organization
- Network management components
- Functions of components
- Relationships
- Information
- Structure of management information (SMI)
- Syntax and semantics
- Management information (data) base (MIB)
- Organization of management information
- Object-oriented
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- The organizational model describes the components needed for the network management, their functions and their relationships
*
Notes
- Communication
- Transfer syntax with bidirectional messages
- Transfer structure (PDU)
- Functions
- Application functions
- Configure components
- Monitor components
- Measure performance
- Secure information
- Accounting
Chapter 3 Basic Foundations: Standards, Models, and Language
OSI NM Model (cont.)
*
Network Management: Principles and Practice
© Mani Subramanian 2010
Accounting management is concerned with tracking network utilization information, such that individual users, departments, or business units can be appropriately billed or charged for accounting purposes.
Usage accounting
=La comptabilité d'utilisation
*
Notes
SNMP Architecture and Model
Network Management: Principles and Practice
© Mani Subramanian 2010
- Organization
- Same as OSI model
- Information
- Same as OSI, but scalar
- Communication
- Messages less complex than OSI and
unidirectional - Transfer structure (PDU)
- Functions
- Application functions
- Fault management
- Configuration management, MONITORINg
- Accounting management
- Performance management
- Security management
Chapter 3 Basic Foundations: Standards, Models, and Language
*
SNMP Model consists in 4 sub-models:
*
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
TMN Architecture
- Addresses management of telecommunication
networks - Based on OSI model
- Superstructure on OSI network
- Addresses network, service, and business
management
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
Organizational Model
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- 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 to managers
- Managed object
- Essentially, network element (Hubs, bridges, routers, transmission facilities) that is managed
- Houses management agent
Notes
Managed Object
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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 Basic Foundations: Standards, Models, and Language
*
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
Two-Tier Model
- 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)
Chapter 3 Basic Foundations: Standards, Models, and Language
*
https://www.quora.com/What-are-active-and-passive-networks-and-explain-with-a-circuit-diagram
http://www.excitingip.com/9/an-overview-of-passive-components-in-a-local-area-network/
http://www.excitingip.com/26/an-overview-of-active-components-in-an-ip-network/
*
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
Three-Tier Model
- Middle layer plays the dual role
- Agent to the top-level manager
- Manager to the managed objects
- Example of middle level: Remote monitoring
agent (RMON)
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes: Network domains can be managed locally
Network Management: Principles and Practice
© Mani Subramanian 2010
Manager of Managers
- Agent NMS manages the domain
- MoM presents integrated view of domains
- Domain may be geographical, administrative, vendor-specific products, etc.
Chapter 3 Basic Foundations: Standards, Models, and Language
*
*
Notes: NMS organized in a peer to peer system
Network Management: Principles and Practice
© Mani Subramanian 2010
Peer NMSs
- Dual role of both NMSs
- Network management system acts as peers
- Dumbbell architecture discussed in Chapter 1
- Notice that the manager and agent functions are processes and not systems
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
- Information Model: Analogy
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- Model concerned with structure and storage of management information
- Consider the information model within a library
- a figure in a book uniquely identified by
- ISBN, Chapter, and Figure number in that hierarchical order
- ID: {ISBN, chapter, figure}
- The three elements above define the syntax
- Semantics is the meaning of the three entities according to Webster’s dictionary
In our context, the information comprises syntax and semantics about management information
Information Model= SMI + MIB
SMI: structure of MI (Management Information)
MIB: organization of MI (MI Base- tree like structure)
- Structure of Management Information (SMI)
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
SMI defines for a managed object
- Syntax
- Semantics
- Plus additional information such as status
System= hardware + software
Examples of N. management information :
sysDescr
Components of the description of a system themselves: name, description, contact, ID …
Example
- sysDescr: { system 1 }
Syntax: OCTET STRING
Definition: "A textual description of the entity. "
Access: read-only
Status: mandatory
System description on a router or on server has a syntax (strings) and semantics according to the human knowledge
==
Information to be exchanged between two entities, (manager and agent); this information needs to be in acertain language that both entities understand and which specifies both syntax and semantics ; like 2 human beings exchanging some ingormtion.
The information model specifies structure (SMI) and organization (of all the managed objects, the management information items dealt with in a certain frame)
*
Title: System Information: 172.16.46.2
Name or IP Address: 172.16.46.2
System Name:
System Description: 3Com LinkBuilder FMS, SW version:3.02
System Contact:
System Location:
System Object ID: iso.org.dod.internet.private.enterprises.43.1.8.5
System Up Time: (2475380437) 286 days, 12:03:24.37
Figure 4.2(a) System Information on 172.16.46.2 Hub
Notes
Management Information Base (MIB)
Network Management: Principles and Practice
© Mani Subramanian 2010
- Information base contains information about managed objects
- Defines relationship between managed objects by grouping of related objects (in a tree-like structure)
- It is NOT a physical database (Oracle, Sybase ..). It is a virtual database (a schema) that is compiled into management modules : manager module/software and agent module /software
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Title: System Information: 172.16.46.2
Name or IP Address: 172.16.46.2
System Name:
System Description: 3Com LinkBuilder FMS, SW version:3.02
System Contact:
System Location:
System Object ID: iso.org.dod.internet.private.enterprises.43.1.8.5
System Up Time: (2475380437) 286 days, 12:03:24.37
Figure 4.2(a) System Information on 172.16.46.2 Hub
Notes
Information Base View: An Analogy
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
MIB View and Access of an Object
Network Management: Principles and Practice
© Mani Subramanian 2010
- A managed object has many attributes – its information base
- There are several operations that can be performed on the objects
- A user (manager) can view and perform only certain operations on the object by invoking the management agent
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
Management Data Base / Information Base
- Distinction between MDB and MIB
- MDB physical database; e.g., Oracle, Sybase
- MIB virtual database; schema compiled into management software.
- 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.
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
Management Information Tree
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Each managed object occupies a node in the tree
Notes
Network Management: Principles and Practice
© Mani Subramanian 2010
OSI Management Information Tree
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
The managed objects are uniquely defined by a tree structuring e specified by the OSI model
- internet OBJECT IDENTIFIER ::=
{ISO(1) ORG(3) DOD(6) INTERNET(1)}
In the CMIP there s smthg similar to the MIB in SNMP
*
Notes
- Type
- Name
- Syntax
- Definition
- Status
- Access
- Instance
Object Type and Instance
- 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 Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
A type of management information
*
Notes
Managed Object: Internet Perspective
object ID unique ID
and descriptor (name for the object)
syntax 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 Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Access: read some information , applying/performing some action on it
*
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 Practice
© Mani Subramanian 2010
Managed Object:
OSI Perspective
Chapter 3 Basic Foundations: Standards, Models, and Language
*
*
Notes
Packet Counter Example
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
|
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
Internet vs. OSI Managed Object
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- 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: Enhancement in SNMPv2
Mgmt. Communication Model
Network Management: Principles and Practice
© Mani Subramanian 2010
Figure 3.11 presents the communication model.
The applications in the manager module initiate requests to the agent in the Internet model. It is part of the operations in the OSI model. The agent executes the request on the network element; i.e., managed object, and returns responses to the manager.
The traps/notifications are the unsolicited messages, such as alarms, generated by the agent.
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- how the information/management data is exchanged between agent and manager processes, as well as between manager processes.
Now how the information is exchanged between systems
*
Notes
Transfer Protocols
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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 (connection-oriented) and connectionless transport
protocol; SNMPv2 extended to c-o, but rarely used
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Three aspects need to be addressed in the communication of information between two entities:
- transport medium of message exchange (transport protocol),
- message format of communication (application protocol),
- and the actual message (commands and responses).
***
Three aspects need to be addressed in the communication of information between two enti-
ties: transport medium of message exchange (transport protocol), message format of communication
(application protocol), and the actual message (commands and responses).
****
*
Notes
3.6 Abstract Syntax Notation One: ASN.1
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- ASN.1 is more than a syntax; it’s a language
- Addresses both syntax and semantics
- Makes application layer protocols independent of lower layer protocols
- Can generate machine-readable code: Basic Encoding Rules (BER) is used in management modules
So far, we discussed the information model and the communication model, a communication language is needed to specify syntax and semantics of the communication: formats and semantics for data transfer
- 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
A language is used to describe both syntax and semantics of managed objects
===
In the previous sections, we discussed the information model and the communication model, a communication language is needed to specify syntax and semantics of the communication: formats and semantics for data transfer
ASN.1 is a formal language
*
Notes
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
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
Backus-Nauer Form (BNF)
- 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 Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Definition:
<name> ::= <definition> [To be read: Name of the entity ::=(defined as) 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
This way allows to define complex managed objects based on basic ones
- Name of the entity ::=(defined aas) definition
- Each line of the rules is called assignment or production
3. The formal syntaxic language and grammer of B an d n
*
Notes
Simple Arithmetic Expression
Network Management: Principles and Practice
© Mani Subramanian 2010
<SAE> ::= <number> | <SAE><op><number>
Example: 26 = 13 x 2
Constructs and primitives
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
Type and Value
Network Management: Principles and Practice
© Mani Subramanian 2010
- Assignments
- <BooleanType> ::= BOOLEAN
- <BooleanValue> ::= TRUE | FALSE
- ASN.1 module is a group of assignments
person-name Person-Name::=
{
first "John",
middle “T",
last "Smith"
}
Chapter 3 Basic Foundations: Standards, Models, and Language
*
person-name is an ASN module which allows here to fix values of the data type Person-Name through 3 assignments
Data type assignment vs value assignment
*
Notes
- CHOICE
- SET
- SEQUENCE
- OF
- NULL
Keyword Examples
- Keywords are in all UPPERCASE letters
- Alternatives : CHOICE
- List maker: SET, SEQUENCE
- Repetition: SET OF, SEQUENCE OF:
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Such keywords allow to define complex managed objects based on basic ones
- BookPages ::= SEQUENCE OF { BookPageNumber}
or
BookPages ::=
SEQUENCE OF
{
SEQUENCE
{ChapterNumber, Separator, PageNumber}
}
To define new type
*
Notes
Data Type: Example 1
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
Data Type: Example 1
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
Data Type: Example 1
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
Data Type: Example 1
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
Data Type: Example 1
Network Management: Principles and Practice
© Mani Subramanian 2010
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
Data Type: Example 2
Network Management: Principles and Practice
© Mani Subramanian 2010
- SEQUENCE OF SEQUENCE makes a table== “repeats rows”
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
ASN.1 Data Type Conventions
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
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
Data Type: Structure & Tag
Network Management: Principles and Practice
© Mani Subramanian 2010
- Structure defines how data type is built
- Tag uniquely identifies the data type
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
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
- BookPages ::= SEQUENCE OF { BookPageNumber}
or
BookPages ::=
SEQUENCE OF
{
SEQUENCE
{ChapterNumber, Separator, PageNumber}
}
Chapter 3 Basic Foundations: Standards, Models, and Language
*
Notes
Tag
Network Management: Principles and Practice
© Mani Subramanian 2010
Example:
BOOLEAN Universal 1
INTEGER Universal 2
research Application [1] (Figure 3.13)
product-based Context-specific under research [0]
Chapter 3 Basic Foundations: Standards, Models, and Language
*
- 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
Notes
Enumerated Integer
- ENUMERATED is a special case of INTEGER
- Example: RainbowColors(5) is orange
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
RainbowColors ::= ENUMERATED
{
violet (0)
indigo (1)
blue (2)
green (3)
yellow (4)
orange (5)
red (6)
}
ASN.1 Module Example
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
*
IpNetMediaEntry ::=SEQUENCE{
ipNetToMediaIfIndex INTEGER
ipNetToMediaPhysAddress PhysAddress
ipNetToMediaNetAddress IpAddress
ipNetToMediaType INTEGER}
*
Network Management: Principles and Practice
© Mani Subramanian 2010
Chapter 3 Basic Foundations: Standards, Models, and Language
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
Notes
Macro
- Macro is used to create new data types
Network Management: Principles and Practice
© Mani Subramanian 2010
Example:
Chapter 3 Basic Foundations: Standards, Models, and Language
*
<macroname> MACRO ::=
BEGIN
TYPE NOTATION ::= <syntaxOfNewType>
VALUE NOTATION ::= <syntaxOfNewValue>
<auxiliaryAssignments>
END
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
Functional Model
Network Management: Principles and Practice
© Mani Subramanian 2010
- Configuration management
- Set and change network configuration and component parameters
- 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
Chapter 3 Basic Foundations: Standards, Models, and Language
*
user-oriented applications
This functional model addresses user-oriented applications
*
Network
Management
Information
Model
Organization
Model
Functional
Model
Communication
Model
Figure 3.1 OSl Network Management Model
Network
Management
Information
Model
Organization
Model
Functional
Model
Communication
Model
Figure 3.1 OSl Network Management Model
Network
Management
Information
Model
Organization
Model
Functional
Model
Communication
Model
Manager
Managed objects
Unmanaged objects
Figure 3.2 Two-Tier Network Management Organization Model
Agent process
MDB
MDB Management Database
Agent / Manager
Managed objects
Agent process
Manager
Figure 3.3 Three-Tier Network Management Organization Model
MDB
MDB
MDB Management Database
MoM
Agent
Agent NMS
Manager
Managed objects
Managed objects
Figure 3.4 Network Management Organization Model with MoM
Agent process
MDB
MDB
MDB
MoM Manager of Managers
MDB Management Database
Agent
Manager
Agent NMS
Agent
Agent NMS
Manager
Manager NMS
Agent NMS
Agent NMS
Manager NMS
Figure 3.5 Dual Role of Management Process
Title: System Information: 172.16.46.2
Name or IP Address: 172.16.46.2
System Name:
System Description: 3Com LinkBuilder FMS, SW version:3.02
System Contact:
System Location:
System Object ID: iso.org.dod.internet.private.enterprises.43.1.8.5
System Up Time: (2475380437) 286 days, 12:03:24.37
Figure 4.2(a) System Information on 172.16.46.2 Hub
sysServices (7)
sysLocation (6)
sysDescr (1)
system
(mib-2 1)
sysObjectId
(2)
sysUpTime (3)
sysName (5)
sysContact (4)
Figure 4.27 System Group
Manager
Managed objects
MDB
MIB
Agent process
MDB Management Database
MIB Management Information Base
Figure 3.6 Network Configuration with Data and Information Base
Root
Level 1
Level 2
Level 3
Figure 3.7 Generic Representation of Management Information Tree
iso-itu
2
itu
0
iso
1
org
3
dod
6
internet
1
Figure 3.8
OSI Management Information Tree
iso-itu
2
iso
1
itu
0
org
3
dod
6
internet
1
private
4
enterprise
1
IBM
2
Object Type:
Object ID
and
Descriptor
circle
Access:
Access
privilege
Defintion
:
Semantics -
textual description
Status
:
Implementaion
requirements
Syntax
:
model of object
Figure 3.9(a) Internet Perspective
Behaviour
Object Class:
Circular
object
Object Class:
Elliptical
object
Attributes
:
circle, dimension
Operations:
Push
Attributes:
ellipse, dimension
Notifications
:
Notify changes in
a
ttribute values
Figure 3.9(b) OSI Perspective
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
Manager
Agent
Operations / Requests
Responses
Notifications / Traps
Applications
Network Elements /
Managed Objects
Figure 3.11 Management Message Communication Model
Manager
Applications
Manager
Communication
Module
Transport Layers
Agent
Applications
Agent
Communication
Module
Transport Layers
Physical Medium
Operations / Requests / Responses
Traps / Notifications
SNMP (Internet)
CMIP (OSI)
UDP / IP (Internet)
OSI Lower Layer Profiles (OSI)
Figure 3.12 Management Communication Transfer Protocols
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
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
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
Data Type
Other
Tagged
Structured
Simple
Number
Tag
Structure
Class
Universal
Application
Context-
specific
Private
Figure 3.15 ASN.1 Data Type: Structure and Tag
RainbowColors ::= ENUMERATED
{
violet
(0)
indigo
(1)
blue
(2)
green
(3)
yellow
(4)
orange
(5)
red
(6)
}
IpNetMediaEntry ::=SEQUENCE{
ipNetToMediaIfIndex INTEGER
ipNetToMediaPhysAddress PhysAddress
ipNetToMediaNetAddress IpAddress
ipNetToMediaType INTEGER}
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
<
macroname> MACRO ::=
BEGIN
TYPE
NOTATION ::= <
syntaxOfNewType>
VALUE NOTATION ::= <
syntaxOfNewValue>
<
auxiliaryAssignments>
END
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}
OSI
Functional Model
Fault
Management
Configuration
Management
Performance
Management
Security
Management
Accounting
Management