**3. Management knowledge definition**

After describing a number of important aspects which have to be considered when designing a language for behaviour descriptions, this section focuses on the syntax and semantics of the language GDMO which is discussed in this paper. Practical experience with GDMO shows that, from an intelligent point of view, the quality of GDMO specifications is not satisfactory. The managed object specifications are incomplete to define the management knowledge of a specific resource. As consequence a new element is necessary.

To solve the current problem to undertake an intelligent integrated management we offer an original contribution to include expert rules in the specifications of the network features. To answer these questions, it will be necessary to make changes on the template of the GDMO standard. To formalize the main proposal of the paper, we analyze necessary requirements area to undertake the related aspects with the knowledge integration in the managed objects. We present an extension of the standard GDMO, to accommodate the intelligent management requirements, figure 3.

GDMO is organized into templates, which are standard formats used in the definition of a particular aspect of the object. A complete object definition is a combination of interrelated templates. There are nine of these templates: class of managed objects, package, attribute, group of attributes, action, notification, parameter, connection of name and behaviour (Morris, 2003), figure 4.

Fig. 3. Independence of Objects and Expert Management

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).

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

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

After describing a number of important aspects which have to be considered when designing a language for behaviour descriptions, this section focuses on the syntax and semantics of the language GDMO which is discussed in this paper. Practical experience with GDMO shows that, from an intelligent point of view, the quality of GDMO specifications is not satisfactory. The managed object specifications are incomplete to define the management knowledge of a specific resource. As consequence a new element

To solve the current problem to undertake an intelligent integrated management we offer an original contribution to include expert rules in the specifications of the network features. To answer these questions, it will be necessary to make changes on the template of the GDMO standard. To formalize the main proposal of the paper, we analyze necessary requirements area to undertake the related aspects with the knowledge integration in the managed objects. We present an extension of the standard GDMO, to accommodate the intelligent

GDMO is organized into templates, which are standard formats used in the definition of a particular aspect of the object. A complete object definition is a combination of interrelated templates. There are nine of these templates: class of managed objects, package, attribute, group of attributes, action, notification, parameter, connection of name and behaviour

ASN.1 describes an abstract syntax for data types and values.

& Zhengjia, 2009).

identifier.

is necessary.

**3. Management knowledge definition** 

management requirements, figure 3.

(Morris, 2003), figure 4.

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 integration of the knowledge base of expert system into resources specifications.

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 Knowledge Management in the MIB for the Network Management 29

DERIVED FROM clause specifies the superclass or superclasses from which this managed object is derived (inherited). This plays a very important role, when determining the relations of inheritance which makes it possible to reutilize specific characteristics in other classes of managed objects. In addition, a great advantage is the reusability of the object classes and therefore of the expert rules which are defined. By using this clause, any attribute, operation, notification, and behaviour exposed by managed objects, as well as inheritance and containment relationships among managed objects and managed object

Packages included in the object class definition are identified by the CHARACTERIZED BY and CONDITIONAL PACKAGES clauses. The CHARACTERIZED BY clause identifies the package or packages that are always present when the managed object is included in the system. The CONDITIONAL PACKAGES clause is used to identify those packages that may or may not be included each time the managed object of this class is instantiated. Finally, the REGISTERED AS clause identifies the location of the managed object class on the OSI

The PACKAGE template is used to specify the characteristics that represent a consistent set of specifications about a network resource. One purpose of the package is to provide a set of re-useable definitions that can be used in several managed object class specifications. All the properties that we define in the package will be included later in the Managed Object Class Template, where the package is incorporated. A same package can be referenced by more than one class of managed objects. For each managed objects class, the following

4. Notifications: are the types of unsolicited information a managed object can send to a

The current template package in GDMO standard is adapted and we add a new feature. In addition to the properties indicated above, we suggest the incorporation of a new property called RULES and its associated template called "RULE", which contains all the

1. Attributes: are the types of data supported by the class (managed object).

specifications of the knowledge base for the expert system, figure 6.

2. Operations: are the actions supported by the class.

3. The behaviour of the managed object.

classes, can be defined, figure 5.

Fig. 5. Inheritance between classes

registration tree (Stallings, 2000).

**4.1 Package template** 

information is defined:

manager.

attribute will define all the aspect about the management knowledge in a specific managed object class. The set of managed object classes and instances under the control of an agent is knows as it's a MIB, an abstraction of network resources properties and states for the purpose or management. The MIB, which is specified using the Structure Management Information (SMI) defines the actual objects to be managed (Clemm, 2006).

Two relationships are essential for the inclusion of knowledge in the component definition of the network: Managed Object Class and Package. GDMO includes the basic template MANAGED OBJECT CLASS, which is always implemented and GDMO also defines an optional template named PACKAGE, which defines a combination of properties for later inclusion in a managed object class template.
