You are on page 1of 6

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 Ingeniera 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 todays 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. Tecnologa Electrnica. Facultad de Informtica. 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
The ITU-T management model, formally called TMN (Telecommunication Management
Network), is highly based on the OSI model which leads to a structure relying on three basic
elements (structure of management information, protocols and functions). Additionally, the TMN
model takes advantage of and adopts many ISO management standards. Using this ISO kernel, the
TMN model expands in two directions: on the one hand it widens the concepts and functions in
order to fit the telecommunication networks features; and, on the other side, it establishes a set of
specific standards for each particular technology. So, for instance, there are specific standards to
manage technologies such as SDH, ISDN, ATM, etc.

ISO ITU-T
General Framework General
7498-4 Framework
10040 M.30xx

Information Functions Protocols


Information Protocols Functions
Structure M.32xx Q.8xx
Structure 9595 10164-x M.31xx M.3300
10165-x 9596 M.3400

Technology
dependent
management

Figure 4

The TMN management information follows the patterns set in the ISO model but they are
expanded to offer a catalogue of object classes adapted to the specific modeling needs found in
the telecommunication network elements [7]. Particularly relevant in this structure of management
information are those object classes related to the topological specification of the network. On the
other hand, the standardized
protocols, specified as a part of the Security
Q.3 interface [8], use the layered ISO Performance
structure where the CMIP plays the Configuration
main role as the management Accounting
protocol. Fault

The functions in the TMN Bussines Management


model follow, in some way, the
organization in five basic functional Service Management
areas defined in the ISO model. But,
on the other hand, each one of these
functions is structured in four layers: Network Management
element management, network
management, service management Element Management
and business management. So, for
instance, the configuration functions Figure 5
of a PABX (Private Automatic
Branch eXchange) can be considered from four different levels: a) determining states and
parameters as a single device (element management); b) considered as part of a network which
has to be configured as a whole (network management); c) as a device which is able to provide
different kinds of services to the users (service management); and d) as an element of business
where economic, working and technical aspects (business management) have to be considered.

5. INTERNET MODEL

The Internet model for managing


communication networks is based on a very simple General Framework
set of protocols and structures of information. The RFC 1052
RFC 1155
structure of information follows the object-
oriented model but introducing many
simplifications with regard to the TMN model. Information Structure Protocols
This situation makes the modeling of complex RFC 1213 RFC 1157
MIB-II SNMP
devices, networks and services more difficult but,
on the other hand, it makes the management
Figure 6
applications considerably easier. While an Internet
MIB can always be described according to the
TMN model, the opposite is not true. Many features modeling objects in TMN have no translation
to the Internet management model.

On the other hand, the network management protocol follows the layered structure of
Internet (more limited than the OSI model of TMN) using the SNMP (Simple Network
Management Protocol) as the management protocol, usually on top of a stack of TCP/IP protocols.
The SNMP protocol, designed with the aim of simplicity, is able to manage many features of many
devices, but it has severe limitations for managing complex objects or a structure of objects.

The limitations of the Internet model are, at the same time, an advantage and a drawback.
On the one hand it is clear that it limits the capabilities of managing the network. But, on the other
hand, its simple design permits an easy development of agents and managers, functions and
management platforms. This situation has led to a fast commercial expansion. There are many
devices supporting the SNMP management protocol, while only the high-end systems support the
CMIP standard. Additionally, many vendors provide management platforms based on SNMP, with
similar functions and performances and at very attractive prices. The greater simplicity of the
Internet model, its greater market share, and the greater number of competitors make a situation of
lower prices possible.

On the other hand, TMN management platforms support many functionalities and can
describe and manage almost every particular aspect of a telecommunications network. However,
the number of communication devices which are able to interface in a Q.3 way is even lower. For
this reason, the prices of TMN management systems are remarkably higher than their SNMP
equivalents, where a 10 to 1 price ratio, or higher, is not uncommon.

6. CONCLUSIONS

In this paper three different models for network management and its main features have
been shown. From our point of view, in small networks with limited management functions,
SNMP-based management systems are the best solution considering the balance between price
and performance. Nevertheless, in middle and large size networks, and when these networks
require a wide range of management functions, using SNMP-based systems can be a hindrance for
the present and a risk for the future. In every particular case we must consider the convenience of
relying on a TMN-based management system, which can guarantee a full functionality and a
proper system scalability.

ACKNOWLEDGEMENTS

The work described in this paper has been co-funded by the Comisin Interministerial de Ciencia
y Tecnologa (CICYT) and the European Commission in the framework of the Fondo Europeo de
Desarrollo Regional (FEDER) through a project bearing reference number 1FD97-0595.

REFERENCES

[1] International Organization for Standardization. ISO 7498-4. Management Framework.


ISO, 1989.
[2] William Stalling: SNMP and SNMPv2: The Infrastructure for Network Management.
IEEE Communications Magazine, March, 1998.
[3] International Telecommunication Union- Telecommunication Sector. ITU-T Rec. M.3010.
Principles for a Telecommunication Management Network. ITU-T, 1996.
[4] International Organization for Standardization. ISO 10165-2. Structure of management
Information. Definition of management information. ISO, 1992.
[5] International Organization for Standardization. ISO 10165-4. Structure of management
Information. Guidelines for the definition of managed objects. ISO, 1992.
[6] International Organization for Standardization. ISO 9596-1. Common Management
Information Protocol (CMIP): Specification. ISO, 1991.
[7] International Telecommunication Union- Telecommunication Sector. ITU-T Rec. M.3100.
Generic Managed Object Class Library. ITU-T, 1995.
[8] International Telecommunication Union- Telecommunication Sector. ITU-T Rec. Q.812.
Upper layer protocol profiles for the Q.3 interface. ITU-T, 1993.

You might also like