KR20030072103A - system and method for providing fault information - Google Patents

Abstract

In the method for providing failure information according to the present invention, in the method for providing failure information generated in the exchange system, the failure occurrence information transmitted from the exchange system is diagnosed and divided into predetermined time intervals according to the occurrence of the failure information. Storing the fault information, updating the fault statistics information at regular intervals, backing up the updated fault statistics information every time period by time period, and generating fault history information, and requesting updated fault statistics information or By performing the step of providing the information of the relevant time zone in the fault history information, it is possible to identify the current failure situation of the system in real time by managing the real time and cumulative statistical data on the failure of the exchange system, Various GUI (Graphic User Interface) such as graph Through this, you can manage the system efficiently.

Description

Fault information providing system and method thereof

The present invention relates to a disability information providing system and a method thereof, and in particular, reinforces statistical portions that were weak in management tools such as maintenance administration PC (MAP) / remote maintenance administration PC (RMAP) for Inforex System. The present invention relates to a failure information providing system and method for efficient management of diagnostic data so that a system administrator can identify and cope with a system failure situation more conveniently.

The Infolex system has a highly reliable structure by adopting distributed control, distributed database structure, and redundant parts of the system. In addition, it is possible to expand up to 15,360 lines in the form of shelves and nodes based on its breakthrough technology, and it accommodates large memory, ensuring flexibility in function expansion, and various data communication networks such as voice, data, and video according to ISDN commercialization It is a future-oriented comprehensive information and communication system with access function.

1 is a schematic block diagram of a system for performing fault handling in a conventional InfoRex system. As illustrated, when a failure occurs in the system, a diagnostic task 1, which is diagnosing the system, detects it and sends a message indicating that the failure has occurred (IO Process Module (hereinafter referred to as IPM)). 2) to send. The IPM is a card that handles input / output. The message received from the task 1 is stored in the hard disk 3 as data related to the failure, and the inquiry of the failure history is performed through a system management program such as the MAP 4.

As such, the conventional Infolex system provides a failure history of the system failure, but cannot provide statistical data because there is no efficient statistical data processing module for the diagnostic data. That is, there is no intermediate module that allows the user to extract and view the desired information by using the failure message.

Therefore, the system administrator of the actual site (site) has a problem that it is difficult to efficiently manage the system failure because the system administrator does not obtain the information that can properly cope with the failure situation of the system.

SUMMARY OF THE INVENTION The present invention has been made to solve such a conventional problem, and provides a failure information providing system and method for efficiently classifying a failure diagnosis message of a system and storing it in a database so that a failure history can be viewed at each time zone. There is this.

1 is a schematic block diagram of a conventional fault information providing system.

Figure 2 is a block diagram of a failure management server equipped with a failure information providing system according to the present invention.

3 is an internal configuration block diagram and message flow diagram of the diagnostic manager module shown in FIG.

* Description of the symbols for the main parts of the drawings *

1: Diagnostic task 2: IPM (IO Process Module)

3: hard disk drive (HDD) 4: MAP

10: IAP11: Diagnostic Task

20: I / O Server 21: IPM

30: failure management server 31: data collection module

32: diagnostic manager module 32a: initialization processing module

32b: message processing unit 32c: DB management processing unit

33: DB33a: Log DB

33b: SUM DB34: Workspace (WA)

34a: Current workspace (CURR_WA) 34b: Cumulative workspace (SUM_WA)

35: dynamic library module 36: data reporter module

40: web browser 41: user screen

In the apparatus for processing a failure generated in the exchange system according to the present invention for achieving the above object, the first storage module for accumulating and storing the failure history information divided by a certain time period according to the failure occurrence information transmitted from the exchange system And a second storage module for storing fault statistics information divided by a certain time period according to the fault occurrence information transmitted from the exchange system for a predetermined time period, and diagnosing fault occurrence information transmitted from the exchange system for each time in the first storage module. A diagnostic manager module that accumulates and stores the statistical information stored in the second storage module as fault history information in the first storage module at regular intervals, and a dynamic library for calling real-time statistical information stored in the second storage module. Module, externally requested query time and statistics from outside If there is a request for data, the dynamic reporter module reads the statistical information of the corresponding time zone stored in the second storage module and the fault history information stored for each time slot in the first storage module, and provides the data reporter module to the user of the web environment. It is composed.

In addition, the fault information providing method according to the present invention, in the method for providing fault information generated in the exchange system, by diagnosing fault occurrence information transmitted from the exchange system and divided by a certain time period according to the fault occurrence information fault statistics information Temporarily storing the information, updating the failure statistics information at regular intervals, backing up the updated failure statistics information every time period by time period to generate failure history information, and, upon request, updated failure statistics. Providing the information of the corresponding time zone among the information or the fault history information.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

2 is a block diagram of a failure management server equipped with a failure information providing system according to the present invention. Referring to FIG. 2, the relationship between the IAP and the I / O server and other modules in the failure management server (Admin Server).

The failure management server 30 is connected to an IAP 10 that implements a diagnostic task 11 for diagnosing a failure, an I / O server 20, and a user web browser environment 40.

IAP 10 stands for Exchange System as an abbreviation for Integrated Access Platform. The diagnostic task 11 is provided to diagnose whether or not a failure has occurred in the switchboard, and to indicate that a failure has occurred. At this time, a message indicating the occurrence of a failure uses an AFS message type. AFS message refers to Alarm Fault Status message.

When the I / O server 20 receives a message indicating that a failure has occurred in the network from the diagnostic task 11 of the IAP 10, the I / O server 20 transmits the failure to the failure management server 30 for failure processing. In the I / O server 20, an IPM 21, which is a card in charge of input and output, is mounted.

The failure management server 30 receives a failure data from the data collection module 31 for collecting failure data through the IPM 21 of the I / O server 20 and the data collection module 31 and performs failure processing. The diagnostic manager module 32, a DB 33 for storing various types of failure data under the control of the diagnostic manager module 32, and a working area for storing real-time statistical information on the generated failures. 34), the dynamic library module 35 for delivering fault data stored in the work area to the outside according to an external monitoring request, and the fault data stored in the work area 34 through the dynamic library module 35 to the outside. It consists of a data reporter module 36 for reporting.

The data collection module 31 receives the fault data transmitted through the I / O server 20 and transmits the fault data to the diagnosis manager module 32.

The diagnostic manager module 32 may be composed of an initializer 32a, a message handler 32b, and a DB handler 32c.

FIG. 3 is a block diagram of the diagnostic manager module shown in FIG. 2 and a schematic function of each block. Referring to Figure 3, let's look at the function of each building block.

The initialization module 32a is a routine for performing the following initialization operations for the internal module driving and environment of the diagnostic manager module 32. Initialize the socket interface for the interface between the data collection modules 31, initialize the DB, initialize the SQL server I / F (interface), initialize the WA (CURR_WA and SUM_WA), between the internal modules of the diagnostic manager module Initializes the message queue for the interface, requests the shape information message of the shape information of the system, for example, the state of the node / self / card / port of the system and performs the processing accordingly.

The message processing module 32b is a routine module for buffering a fault message received from the IAP system 10 into an internal queue, reading and analyzing the message. That is, the POD message and the configuration information message having the fault message information are received from the data collection module. Here, the POD message indicates a message that occurs periodically as a periodic message.

At this time, the POD message received from the data collection module 31 has an AFS message form. The record format of the AFS message may be different from that of the log record processed by the DB management processing module 32c. Therefore, it is necessary to extract only the necessary items from the DB management processing module 32c among the log records received from the data collection module 31. To this end, the message processing module 32b buffers the received message in an internal queue, reads the message, analyzes the content of the message, and delivers the message to the DB management processing module 32c.

The DB management processing module 32c is a routine that actually processes the failure message analyzed by the message processing module 32b. Accordingly, the error counter is changed and the contents of the diagnosis DB are changed.

The DB 33 is composed of a log DB 33a which stores a history of failures and a SUM DB 33b which stores failure history information classified at 15 minute intervals.

The log DB 33a is a DB used for inquiring a detailed failure history for each time zone. The log DB 33a is configured to store a log record after sorting the failure message (AFS message) received from the system.

On the other hand, the SUM DB 33b is a DB used to count the number of failure occurrences, the number of failure restorations, and the number of remaining failures for each unit of time, and stores the contents of the SUM_WA 34a every 15 minutes. In the SUM DB 33b, only the Node, Self, and Status DB are stored.

WA 34 means an area within a work area where data used by a database management system (DBMS) is stored. A user work area includes a storage area for all data items of a subschema called by an application. have.

WA 34 may be composed of a SUM_WA 34a and a CURR_WA 34b. SUM_WA 34a and CURR_WA 34b may add a "Failure Recovery Time" field to distinguish recent failure recovery history during monitoring.

SUM_WA 34a is a WA that is temporarily maintained in main memory to make SUM DB 33b for 15 minutes. Stored in the DB 33b. In real-time monitoring, it is used to show cumulative statistics within the time period.

CURR_WA 34b displays the current fault status for each card and port and is used for monitoring the current status. This WA is a 15 minute cycle and is not stored in the database.

The dynamic library module 35 is a working area 34 managed by the diagnosis manager module 32. The working library 34 is an area implemented with shared memory. The dynamic library module 35 displays a diagnostic data to a user or to an administrator. 36) As it is written in ASP, it provides COM DLL to access diagnostic WA from ASP module. Here, COM DLL stands for Component Object Model Dynamic Link Library and represents a dynamic link library for a data access method for providing a data interface between different modules.

When there is a request from the outside, the data reporter module 36 reads various data by accessing the WA 33 through a COM DLL (DLL dynamic link library) to show the diagnostic data to the user or the administrator. This module displays to the user and can be written in ASP so that users can access the web through the Internet.

Let's look at the operation of the fault information providing system configured as described above.

When the diagnostic manager module 32 is driven, the initialization processing module 32a requests the configuration information message (Config Message) from the data collection module 31 and performs a response process, thereby performing configuration information of the system (node, self). Request, receive, and update the WA 34 with respect to the shape information.

If a failure occurs in the IAP system 10, the diagnostic task 11 of the IAP sends a diagnostic message related to the failure in a message format called an AFS message, and the message processing module 32a transmits data to the configuration information (config) or the like. It classifies into log items and calls each processing module (initialization module or DB management module) for each message type to change the value of each fault counter.

On the other hand, because the failure situation of the system can persist over a 15 minute boundary, the failure list for this is queued. In other words, the current system failure is managed by 15 minutes (WA and SUM DB management by 15 minutes), so the WA is cleared after 15 minutes. Therefore, after 15 minutes of time, there is no information on the current disability. Therefore, if the fault persists at the time of saving WA every 15 minutes, the status value of 'continuous' is stored in the linked list quqe.

In case of an alarm occurrence message, it is stored in the order of occurrence time in the alarm list (AlarmQlist), which is a linked list, and the corresponding AFS code is analyzed to update the values of related SUM_WA and CURR_WA.

In the case of a fault occurrence message, it is stored in the order of occurrence time in the fault list (FaultQlist), which is a link list, and the corresponding AFS code is analyzed to update the values of related SUM_WA and CURR_WA.

On the other hand, in the case of an Alarm Clear message, the corresponding alarm is removed from the linked list Alarm List (AlarmQlist) and the AFS code is analyzed to update the values of related SUM_WA and CURR_WA.

In the case of a Fault Recovery message among the Status messages, the fault is removed from the FaultQlist, the AFS code is analyzed, and the values of the associated SUM_WA 34a and CURR_WA 34b are updated. For other status messages, the AFS code is analyzed to update the values of SUM_WA 34a and CURR_WA 34b.

By generating a timer every 15 minutes, the contents of the SUM WA 34a are stored in the SUM DB 33b every 15 minutes, and the contents of the SUM_WA 34a are reset. In addition, the alarms and faults remaining in the alarm list AlarmQlist and the fault list FaultQlist are stored again in the log DB 33a. At this time, the state of alarm and fault is stored as a type of "Alarm Continue / Fault Continue". It manages the history of the fault when the alarm and fault are not cleared within the corresponding 15 minute time interval and continues for the next 15 minutes, making log history simpler regardless of the time the alarm first occurred. To search.

When the first AFS message is received after the diagnosis manager module 32 is started, or after writing the SUM_WA 34a to the SUM DB 33b every 15 minutes, the time of the first AFS message received in the corresponding 15 minute time zone. After comparing the time stamp values, register a (15-α) minute timer and generate a timeout message every 15 minutes. This is to record the SUM_WA 34a in the SUM DB 33b every 15 minutes.

According to the present invention, the real-time and cumulative statistical data on the failure of the IAP system can be managed to grasp the current failure situation of the system in real time, and various failures (Graphic User Interface (GUI) such as numerical values, graphs, etc. This can be managed through the system, so that the system can be managed efficiently.

In addition, in the case of a continuous failure, the occurrence time can be immediately known, so that in case of a major system failure (system restart), a failure system administrator can manage the failure history more conveniently.

Claims (10)

In the system for providing fault information generated in the exchange system, A first storage module for accumulating and storing fault history information divided by predetermined time zones according to fault occurrence information transmitted from the exchange system; A second storage module configured to store fault statistics information, which are divided by a predetermined time zone, for a predetermined time according to fault occurrence information transmitted from the exchange system; Diagnosis of failure occurrence information transmitted from the exchange system is accumulated and stored in the first storage module for each time, and statistical information stored in the second storage module is accumulated and stored as failure history information in the first storage module at regular intervals. A diagnostic manager module, A dynamic library module for calling real time statistical information stored in the second storage module; When there is a request for inquiry of a desired time zone and a request for statistical data, a web environment is read through statistical information of a corresponding time zone stored in the second storage module and corresponding fault history information stored for each time zone in the first storage module through the dynamic library module. Fault information providing system comprising a data reporter module for providing a user of. The method of claim 1, wherein the first storage module, A first DB that sequentially accumulates failure occurrence information transmitted from the exchange system and stores a failure history; Disability information providing system comprising a second DB for storing the failure history by dividing the failure occurrence information delivered from the exchange system by a predetermined time period. The method of claim 2, wherein the first storage module, And a queue for storing the remaining faults as a fault list after a predetermined time, and restoring the faults in the first DB until the corresponding fault is recovered at a predetermined time interval. The method of claim 1, wherein the second storage module, A first operating area for temporarily storing fault statistics information in a corresponding time period during real time monitoring; And a second operating area temporarily maintained in the main memory for a predetermined period to form a predetermined period of failure history information, and then backed up and stored in the first storage module. The method of claim 1, wherein the diagnostic manager module, Initialize the message queue for the interface between the socket interface for receiving fault information from the exchange system, the internal DB, the second storage module, the internal module of the diagnostic manager module, and request system configuration information from the exchange system. Module, A message processing module for interpreting system shape information transmitted from the exchange system and a failure occurrence message transmitted from the exchange system according to a request of the initialization module; According to the failure occurrence information interpreted by the message processing module, fault history information is generated for each predetermined time, stored in the first storage module, updated failure statistics information of the second storage module for each predetermined time, and And a DB management processing module for backing up and updating the updated hourly statistical information of the second storage module to the first storage module. The method of claim 1, wherein the failure statistics information, Disability information providing system comprising at least one of the number of failures, the number of failure recovery, the remaining number of failures per unit time zone. The method of claim 1, wherein the failure statistics information, The total failure is divided into above card level and below port level, and the partial failure where the port level failure occurs is stored in a table that can determine whether to display the failure status according to the level so that the failure status of the upper level is not displayed. Disability Information System. In the method for providing fault information generated in the exchange system, Diagnosing fault occurrence information transmitted from the exchange system and temporarily storing the fault occurrence information as fault statistics information according to the fault occurrence time; Updating the fault statistics information at regular intervals; Generating fault history information by backing up the updated fault statistics information for each time period; If there is a request, providing the information of the corresponding time zone in the updated failure statistics information or failure history information. The method of claim 8, wherein the providing of the information of the corresponding time zone is provided through a web environment. The method of claim 9, wherein the web environment supports a graphical user interface of a numerical value or a graph.