CS5440 Networks Management

OSI Networks Management Model

Part 2

Instructor: Mphatsi L.A.

Office: SCN202
Email: la.mphatsi@gmail.com
 In this lecture ...

• Information model
• Communication model
 Information model

• The Information Model is concerned with the structure and storage

of information. For example, same as how information is structured
and stored in a library and accessed by all.
• The book is uniquely identified by an International Standard Book
Number (ISBN). It is a ten-digit number identification that refers to a
specific edition of a specific book.
• For example: The ISBN 0-13-437708-7 uniquely identifies the
following book: “Understanding SNMP MIBs” by the authors - David
Perkins and Evan McGinnis.
• We can therefore refer to a specific figure in the book by identifying a
chapter number and a figure number. Thus, the hierarchy of
designation {ISBN, Chapter, Figure} uniquely identifies the object,
which is the figure in the specified book.
 Information model

• Therefore “ISBN,” “Chapter,” and “Figure” define the syntax of the three
pieces of information associated with the figure; and the definition of their
meaning in a dictionary would be the semantics associated with them.
• The representation of objects and information that are relevant to their
management forms the management information model, as briefly
discussed previously under management agent.
• The information on network components is passed between the agent an
management processes [i.e. the information model specifies the
information base to describe managed objects and the relationship
between managed objects], e.g. the MIB.
• The structure defining the syntax and semantics of management
information is specified by the Structure of Management Information
[SMI].
 Information model

• The MIB is used by both agent and management processes to store

and exchange (set and get) management information.
• The MIB associated with an agent is simply called an agent MIB and
the MIB associated with a manager is designated as the manager
MIB.
• The manager MIB (shadow MIB) consists of information on all the
network components that it manages; whereas the MIB associated
with an agent process needs to know only its local information.
• For example, a country may have many libraries. Each library has
an index of all the books in that location - its MIB view. However, the
central index at the county’s main library, which manages all other
libraries, has the index of all books in all the county’s libraries—
global manager MIB view.
 Information model

• SMI defines a managed object:

– Syntax
– Semantics
– 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
 Information model

• Summary on the MIB:

– Information base contains information about managed objects.
– Organized by grouping of related objects.
– Defines relationship between objects.
– It is NOT a physical database. It is a virtual database that is compiled into
management module.
• MIB View and Access of an Object:
– 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.
 Information model

• The Management Data Base / Information Base:

• The following is the 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
• RECAP: A Managed Object can be:
– Network elements (hardware system): hubs, bridges, routers, etc.
– Software (non-physical): programs, algorithms.
– Administrative information: contact person, the name of group of objects
(e.g. IP group).
 Communication model

• The Communication Model addresses how management data is

communicated between agent and manager processes, aswell as
between manager processes themselves.
• Three aspects need to be addressed: transport medium of exchange
(transport protocol), message format of communication (application
protocol), and the actual message (commands and responses).
• The exchanged messages are the commands / requests / operations
and responses / notifications; illustrate this by the example of buying a
car from an automobile salesperson.
Management communication transfer protocols
 Information model

• The OSI uses CMISE [Common Management Information Service

Element] application with CMIP.
• This model also specifies both connection-oriented and
connectionless transport protocol;
• The purpose of CMISE is to transfer network management
information from one system to another (APP Layer).
• The CMISE can simply be viewed as a user application that
provides interface to the CMIP.
• In summary, the CMIP defines services for accessing information
about network objects or devices, controlling them, and receiving
status reports from them.
 Management Functions: The OAM&P

• Although FCAPS is probably the best-known functional reference

model, there are still other ways of organizing the discussed
management functions.
• An alternative to the FCAPS functional model categorization of
management functions can also be the OAM&P: Operations,
Administration, Maintenance, and Provisioning (as discussed in
introduction slides).
• The OAM&P model is popular in large telecommunications service
providers, whose internal organization OAM&P often reflects much
better than FCAPS; which is more popular with Enterprises.
The OAM&P functional groupings
The OAM&P functional flowchart
 Assignment

• Read about the limitations of FCAPS.

• Be in the position to present your findings in our next meeting.
 References and Acknowledgements

[1] Alexander Clemm, Ph.D., Network Management Fundamentals,

Copyright 2007 Cisco Systems, Inc.

[2] Chabalala S.C., National University of Lesotho, Mathematics &

Computer Science, 2012

[3] Raouf Boutaba, School of Computer Science, University of Waterloo