**5. Fault management application using GDMO+ specifications**

In order to evaluate the fault management capabilities of the integrate management solution proposed we have simulated an application that monitors an environment to collect fault event data (Baker et al., 2008). As said before we have considered a private network. We suppose this network as being heterogeneous and hierarchical. The intelligent sensor nodes only disseminate data when the network is being monitored and an error occurs in a resource (Premchand et al., 2008), figure 7.

The use of integrate knowledge in agents can help the system administrator in using the maximum capabilities of the intelligent network management platform without having to use other specification language to customize the application (Akinyokun & Imianvan, 2006).

Our system has the following components: an inference engine, a knowledge base, and a user interface, figure 8.

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


Detection mechanisms are implemented real-time in our prototype and have been embedded with the network elements, network protocols and devices. System operations, uses a supervision system called CSS (Communication Supervisory System) (Lei et al., 2009). This system can monitor, in real time, the network's main parameters, making use of the information supplied by a Supervisory Control and Data Acquisition (SCADA), formed by a Control Center (placed on the main CSE building), and Remote Terminal Units (RTUs) installed into different stations. The use of a SCADA system is due to the management limitations of network communication equipment. Fault identification involves testing the hypothetical faulty components. Repair is achieved by taking intelligent corrective actions. The CSS allows the operator to acquire information, alarms or digital and analogical parameters of measure, registered on each RTU (Doukas et al, 2007). Starting from the supplied information, the operator is able to undertake actions through the CSS in order to solve the failures that could appear or to send a technician to repair the stations equipment. The management system in normal operation generates different notifications and alarms. An alarm is an event generated asynchronously whenever the value of some quality indicator crosses a predefined threshold (either positively or negatively) (Maggiora et al., 2000). Those alarms are caused when an incident occurs. These events are accompanied by

> (31/01 1100.200 stat1 7\_TX\_C2 stat2 Alarm) 1 (31/01 1103.106 stat1 7\_TX\_C2 stat2 Alarm\_Disappears) 2 (31/01 1122.168 stat1 CTR190/7\_RX stat2 Alarm) 3 (31/01 1134.169 Mux3 EXT\_FONIA MAD Alarm\_Disappears) 4 (31/01 1134.122 stat4 CCA34C\_C1C2 stat3 LOCAL\_CHANEL\_2) 5 (01/02 1034.135 Transc\_1 SPU1\_BER\_1 BER Alarm) 6 (01/02 1034.146 Transc\_1 SPU1\_BER\_1 BER Alarm\_Disappears) 7

system can be extended by adding new higher level rules and facts.

Web browser such as Explorer o Mozilla (Hui et al., 2005).

parameters that show different aspects of the events (León et al., 1999).

**6. Control centre** 

...

...

standard and extensible platform with proven performance and quality. The experience with our prototype is that ART Enterprise is a useful tool for developing expert systems. - The knowledge base: The core of the system, this is a collection of facts and if-then production rules that represent stored knowledge about the problem domain (Power & Bahri, 2005). The knowledge base of our system is a collection of expert rules and facts expressed in the ARTScript programming language ART\*Enterprise. The knowledge base contains both static and dynamic information and knowledge about different network resources and common failures. The resultant expert system has about 600 rules and it has been employed Workstation to program the expert system. This initial knowledge has been acquired from the experts in the management domain. The knowledge base of our

Fig. 7. Power Company Network

Fig. 8. Architecture System


