**2. Management network overview**

The purpose of network management is the assignment and control of proper network resources, both hardware and software, to address service performance needs and the network's objectives. With the ever-increasing size and complexity of underlying networks and services, it has become impossible to carry out these functions without the support of automated tools (Zuidweg, 2002). As the size of communication networks keeps on growing, with more subscribers, faster connections and competing and cooperating technologies and the divergence of computers, data communications and telecommunications, the management of the resulting networks gets more important and time-critical. Telecommunication and services are in the process of revolutionary yet evolutionary changes due to transformation of the regulatory environment that in turn has given rise to rapid improvements in the underlying application, networking, computing, and transmission technologies.

There are two dominant network management models, which have been used to administration and control the most of existing networks: TMN and SNMP. Both network management systems operate using client/server architecture. SNMP standards are defined in a series of documents, called request for comments or RFCs proposed by the Internet Engineering Task Force (IETF) and Telecommunications Management Network TMN is introduced by the ITU-T (the former CCITT). Of these two TMN is gaining popularity for large complex networks.

In private network environment, SNMP enjoys near-universal support. In the public environment, however, a more heterogeneous mix of de facto telecommunications industry standards has prevailed, with a move toward TMN support. Moreover TMN was the first who started, as part of its Open Systems Interconnection (OSI) program, the development of the architecture for network management. The OSI management environment consists of tools and services need to control and supervise the management networks.

#### **2.1 OSI network management model**

The OSI network management model is a starting point for understanding network management. There are three basic components comprising the elements of the management architecture to support a successful implementation of the OSI Network Management Model, figure 1:

Fig. 1. Overview of OSI Network Management Model.

standard called Extended GDMO or simply GDMO+, for the incorporation of the management expert rules. Next will examined the design and development of a prototype. From there, we present the concept the formulation of the system design proposal and also an outline of the various stages in the system development cycle. Next section summarizes the performance of the system and the results of the research. Finally we outline the conclusion and future works.

The purpose of network management is the assignment and control of proper network resources, both hardware and software, to address service performance needs and the network's objectives. With the ever-increasing size and complexity of underlying networks and services, it has become impossible to carry out these functions without the support of automated tools (Zuidweg, 2002). As the size of communication networks keeps on growing, with more subscribers, faster connections and competing and cooperating technologies and the divergence of computers, data communications and telecommunications, the management of the resulting networks gets more important and time-critical. Telecommunication and services are in the process of revolutionary yet evolutionary changes due to transformation of the regulatory environment that in turn has given rise to rapid improvements in the

There are two dominant network management models, which have been used to administration and control the most of existing networks: TMN and SNMP. Both network management systems operate using client/server architecture. SNMP standards are defined in a series of documents, called request for comments or RFCs proposed by the Internet Engineering Task Force (IETF) and Telecommunications Management Network TMN is introduced by the ITU-T (the former CCITT). Of these two TMN is gaining popularity for

In private network environment, SNMP enjoys near-universal support. In the public environment, however, a more heterogeneous mix of de facto telecommunications industry standards has prevailed, with a move toward TMN support. Moreover TMN was the first who started, as part of its Open Systems Interconnection (OSI) program, the development of the architecture for network management. The OSI management environment consists of

The OSI network management model is a starting point for understanding network management. There are three basic components comprising the elements of the management architecture to support a successful implementation of the OSI Network

underlying application, networking, computing, and transmission technologies.

tools and services need to control and supervise the management networks.

**2. Management network overview** 

large complex networks.

**2.1 OSI network management model** 

Fig. 1. Overview of OSI Network Management Model.

Management Model, figure 1:


According to the International Organization for Standardization (ISO), the OSI network management model defines a conceptual model for managing all communication entities within a network. This main concept is the managed object, which is an abstract view of a logical o physical resource to be managed in the network (Hebrawi, 1995). Managed objects provide the necessary operations for the administration, monitoring and control of the telecommunications network. These operations are realized through the use the Common Management Information Protocol (CMIP) (International Telecommunication Union [ITU-T], 1997). This is a network management protocol built on the OSI communication model. The related Common Management Information Services (CMIS) (International Organization for Standardization [ISO], 1998) defines services for accessing information about network objects or devices, controlling them, and receiving status reports from them. For a specific management system, the management process involved will take on one of two possible roles, Figure 2:


Fig. 2. OSI manager/agent architecture

These managed objects are defined according the ISO Guidelines for Definition of Managed Objects (GDMO). GDMO language uses the object orient programming and defines how network objects and their behaviour are to be specified, including the syntax and semantics.

Integration of Knowledge Management in the MIB for the Network Management 27

Fig. 3. Independence of Objects and Expert Management

Fig. 4. Independence of Objects and Expert Management

The elements that at the moment form the GDMO standard do not make a reference to the knowledge base of an expert system. Until now the managed objects are not able to use the knowledge that the base of knowledge provides which collects the management operations and control of a management domain. We observe the need to define new structures for those cases in which it is necessary to express the knowledge. To solve this problem we suggest a refinement of the package template. We propose to extend the Guidelines for Definition of Managed Objects with the following goals: facilitate the normalization and

These goals will allow to developers specify the storage location and the update method of intelligent managed and provide a way to specify complex managed. Thus the description of certain aspects of managed object knowledge, e.g. the definition of expert rules, can be supported. We proposed adding a new property in GDMO standard named "rule". This

integration of the knowledge base of expert system into resources specifications.

This standard has been standardized by ITU-T in ITU-T X.722 and is now widely used to specify interfaces between different components of the TMN architecture. GDMO properties values types are described using the abstract syntax notation one (ASN.1) (Morris, 2003). ASN.1 describes an abstract syntax for data types and values.

Nowadays there are different domains of application of the expert systems in topics related with the network management. OSI classifies the systems management activities into five functional areas. We can categorize the expert systems used in network management within these five groups. Some expert system examples are Max & Opti, ANSWER, Trouble Locator, and CRITTER in fault diagnosis area, ESS-ES, ECXpert, and APRI in accounting management area, ACE, XCON, SMCS, and EXSim in configuration management area, TASA, NETTRA, and Scout in performance management area, NIDES, P-BEST, and NIDX in security management area. In this context the expert system that we have built, would be included in the area of work of the fault management (Liao, 2005; Negnevitsky, 2002; Yaguo & Zhengjia, 2009).

After this brief introduction to management elements, we will approach our research in the integration of knowledge management of expert system into MIB in the OSI management model. We are studying the way to integrate the expert knowledge in the management Internet model. Internet management model doesn't use the Object Oriented Programming such as it is used by the OSI model. This is one of the reasons for the Internet model simplicity. The definitions contain objects, specified with ASN.1 macros. In internet model the resources specifications can only be groups of scalar variables and cells tables in spite of not being an Object Oriented Programming model. We can use the tables of the Internet model as classes of the OSI model, where the attributes are the table columns and every file contains an instance of the class. The same as in OSI every object has an OID associated identifier.
