Study Committee 35

Secretary 1999 Colloquium

M Monti 13 October
1-9 rue Pierre Nicolau Krakow
F-93407 Saint-Ouen FRANCE POLAND

C35-99 B32

TMN VERSUS SNMP-BASED NETWORK MANAGEMENT SYSTEMS

by
J. Luque 1, F. Gonzalo 2, J. I. Escudero 1, A. Carrasco1
1
Universidad de Sevilla
2
Endesa Ingeniería de Telecomunicaciones (Enditel)

(Spain)

1. INTRODUCTION

The OSI (Open System Interconnection) model has been a successful framework for
protocol architecture in some environments. Academically oriented systems or high-end
communication networks had taken advantage of its wide goals and generous features. When
network management arose as a major problem, the natural “official” answer was to build the
Telecommunication Management Network (TMN), an architecture based on the existing OSI
model. TMN systems have the same aim of universality as OSI systems. Therefore, both of them
are complete but at the same time heavy, complex and expensive solutions. In addition, OSI and
TMN approaches have to be approved by international standardization bodies (ISO and ITU-T),
which implies time-consuming efforts -a drawback in today’s rapidly changing communications
world.

On the other hand, to cope with the OSI drawbacks, the TCP-IP and related protocols have
become a de facto standard for many applications. Most computer networks, both in academic or
industrial environments are based on TCP-IP. Internet is also a TCP-IP based network. This
model uses quite simple but useful protocols to communicate computers. It does not provide full
support for every possible feature but its lack of functionality is far overcome by its availability
and almost universal extent. According to this philosophy, in the Internet-like networks a much
easier and informal approach has been adopted. Its kernel is the SNMP (Simple Network
Management Protocol), which is widely supported and allows for the easy management of
multivendor networks.

* Dpt. Tecnología Electrónica. Facultad de Informática. Av. Reina Mercedes, s/n. 41018-Sevilla. Spain.
Fax: +34 95 4552764 e-mail: jluque@cica.es
 This paper will address and compare the main characteristics of TMN and SNMP based
systems. We will try to discuss the reasons for choosing either of the two systems, considering not
just technical performance but also taking into account economic and commercial considerations.

2. NETWORK MANAGEMENT MODELS

The problem of managing communication networks emerges in a double realm: managing

computer networks and managing telecommunication networks. In the field of computer networks,
a standardized solution has been developed by ISO (International Organization for
Standardization) in the context of the OSI model [1]. According to this solution, the network
management task is carried out mainly by the application layer entities and is highly coupled to the
OSI model structures. That is, the ISO network management model is very ambitious, having many
functionalities, but on the other hand, it can turn out to be excessively heavy and complex.

The complexity of the ISO network

management model, its difficulty to follow Network
technological progress and the lack of Management
commercial products, make it necessary to look
for an alternative for managing computer
networks: the Internet model [2]. In this model, Computer Telecommunication
the management tasks are carried out by means of Networks Networks
very simple structures and protocols, which
allows for a fast and easy implementation of the
appropriate management systems. This solution, ISO Internet ITU-T
considering its limited design aims, is not able to OSI TMN
solve the problem of managing heterogeneous
networks with the same powerful capabilities Figure 1
shown by the ISO network management model.
However, for many real-life computer networks,
its functionality is considered satisfactory.

Finally, in the much more specific area of telecommunication networks, the integrated
network management problem emerges as well. To cope with this situation, ITU-T approves the
TMN model [3] benefiting from most of the concepts and standards defined by the ISO model.
This results in a very powerful model, although it has the same heaviness and slowness of the ISO
model. In the next paragraphs, each model will be described.

3. OSI MODEL

The ISO network management model is based on three basic elements: the structure of
management information, the protocols and the functions. The structure of management information
[4] is based on an object-oriented model where every sort of device is modeled by means of an
object class including its associated attributes, notifications and actions. The objects are
organized according to a tree of hierarchical dependency while the object classes are arranged
following an inheritance tree. The set of managed objects makes up the MIB (Management
Information Base). A standard language, called GDMO (Guidelines for the Definition of Managed
Objects) [5] has also been defined, allowing a non-ambiguous definition of every object class
characteristic. The resulting information model has a great describing capacity and easily permits
to deal with every particular situation which can arise when managing actual networks.

To solve the problem of communicating

with the network elements, the ISO model General Framework
depicts a layered structure (OSI model) where 7498-4
the management functions can be found in every 10040
layer, but mainly in the application layer. In that
layer, a set of management service modules
(SMASE: Systems Management Application Information Protocols Functions
Service Elements) are grouped, and the Structure 9595 10164-x
communication tasks associated to all 10165-x 9596
management functions are carried out. Each one
of these modules is supported by the services Figure 2
provided by application layer conventional
protocols, such as FTAM, ACSE and ROSE and, mainly, by CMIP (Common Management
Information Protocol), the specific ISO network management protocol [6]. The CMIP can support
the complex MIB information structures defined by ISO, and allows for a network management in
a distributed platform environment.

The last basic element of

User User the ISO network management
model are the functions. There
are many management functions
SMAE Systems Management
AE SMASE which can be classified into five
Application Serv. Elem.
functional areas: configuration
Common Management management, fault management,
CMISE
Information Serv. Elem. performance management,
accounting management, and
LME Remote Operation security management. The
LE ASEs ROSE
Service Element
functions in the configuration area
Association Control deal with the problem of
ACSE
Service Element evaluating the current state of the
network, and of bringing it to a
Presentation ASE: Application
proper state where the system
Layer Service Element
management requirements can be
Figure 3 fulfilled. The fault functions face
the problem of processing the
network devices alarms, making a diagnosis of their probable cause, locating and, eventually,
repairing the faults. The performance functions measure the efficiency of the network devices and
the quality of service provided to the users, suggesting procedures to improve those performances.
In the accounting area, we can find those functions related to the administrative aspects of the
network, such as the devices and services usage metering, the cost allocation and the invoicing.
Finally, the functions in the area of security deal with the problems related to establishing and
maintaining a network security policy.

4. TMN MODEL