KR19980026888A - Remote fault management method using Simple Network Management Protocol (SNMP) in asynchronous transmission (ATM) device - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

A failure management method in remote area using simple network management protocol in asynchronous transmission device.

2. The technical problem to be solved by the invention

It is intended to reduce the load on the failure management block and to simultaneously control a large number of identical devices from remote locations.

3. Summary of Solution to Invention

It detects the failure of CANS system and provides the necessary information to the operator according to the level of the failure, and if necessary, executes the prescribed operation without the operator's instruction, and also provides the failure information to the network manager. Run In addition, even when the failure is recovered, it provides the information to the operator according to the information of the corresponding failure recovery and also executes the functions to provide the corresponding recovery information to the network administrator. And the remote network manager collects the fault information of CANS and processes it statistically and also executes the necessary functions according to the fault information generated. The database used here uses basic information management (MIB).

4. Important uses of the invention

Used for fault management in asynchronous transmission device.

Description

Remote fault management method using Simple Network Management Protocol (SNMP) in asynchronous transmission (ATM) device

The present invention, when a failure occurs in the devices using the asynchronous transfer mode (Asynchronous Transfer Mode: ATM) method to deliver to the remote network manager using a simple network management protocol (SNMP), and the information transmitted from the remote site and The present invention relates to a remote fault management method of managing these faults using predefined information.

The technical field to which the present invention belongs belongs to a maintenance function for performing fault management of any device. At this time, the failure management function detects when a failure occurs, provides the necessary information to the operator according to the level of the corresponding failure, executes the prescribed operation without the operator's instruction if necessary, and also applies the failure information to the remote network administrator. Say the function to provide. Also, when the failure is recovered, the above functions are executed according to the information of the corresponding failure recovery.

Here, network management refers to remote control of several arbitrary devices. For this function, data transfer protocol is required between the remote device and the actual device, and one of the international standards for this is SNMP.

In the centralized B-NT system (hereinafter referred to as CANS) in which the present invention is used, the failure management function using the simple network management protocol (SNMP) has not been used until now. The present invention relates to how to detect failure information by using the SNMP function and a method of managing it remotely.

In general, the fault management method detects a fault in the hardware of the failing device and transfers it to a block for processing it in software. In this block, necessary fault handling is performed by an operation command with an operator. The failure management scheme generates a large number of failure messages at the same time as the hardware modules in the device increase, and in this case, failure handling may be delayed or the operation of the failure management block may be inoperable. In addition, when a failure occurs in each device, even if the existing general method is a minor failure, the operator of the device has to deal with it at the place where the device is installed.

Accordingly, it is an object of the present invention to provide a remote failure management method that can reduce the load of the failure management block and simultaneously control a large number of identical devices at a remote location.

In other words, the present invention provides a method for executing a failure management function in a CANS ATM device implementing a network management function using SNMP, and a remote failure management method capable of processing them remotely.

1 is a structural diagram of a CANS system, which is a centralized B-NT system,

2 is a software structure diagram of a centralized B-NT system;

3 is a conceptual diagram of remote failure management of the present invention;

4 is a flowchart illustrating overall failure management in a CANS system;

5 is a flowchart illustrating overall failure management in a remote system;

6 is a flowchart of analyzing fault information in a CANS system;

7 is a flowchart of troubleshooting in a CANS system;

8 is a flowchart for updating a related MIB in a CANS system and a remote system;

9 is a flowchart for reporting an operator and remote location information in a CANS system;

10 is a flowchart for analyzing fault information in a remote system;

11 is a flowchart of failure handling in a remote system;

12 is a flowchart of fault information collection and statistics in a remote system.

* Description of the main symbols in the drawing

ACPB: ATM Layer Control Processing Block

ATM: Asynchronous Transfer Mode

ATMB: ATM Layer Block

CANS: Centralized Access Node System (Centralized B-NT System, or Centralized Access Node System)

CANS-MIB: CANS Management Information Base

MDPB: Mux / Demux Processing Block

MIB: Management Information Base

MMIB: Man Machine Interface Block

PDU: Protocol Data Unit

PSIB: Physical Layer Sb Interface Block

PTIB: Physical Layer Tb Interface Block

SAGB: SNMP AGent Block

SCPB: System Control Processing Block

SIGB: Signaling Block

IPCB: InterProcess Control Block

NMS: Network Management System

SMFB: System Management Function Block

SNMP: Simple Network Management Protocol

OAM: Operation And Maintenance

To this end, the present invention is carried out by the following processing.

First, it detects when a CANS system has a failure and provides the operator with the necessary information according to the level of the failure, and if necessary, executes the prescribed operation without the operator's instructions, and also provides the network manager with the failure information. Execute the function. In addition, even when the failure is recovered, it provides the information to the operator according to the information of the corresponding failure recovery and also executes the functions to provide the corresponding recovery information to the network administrator.

Secondly, the remote network manager collects CANS fault information and performs statistical processing on it, and also executes necessary functions according to the fault information generated. The database used here uses basic information management (MIB).

Below. With reference to the accompanying drawings will be described an embodiment of the present invention;

The present invention operates on SCPB of FIG. 1 and is implemented on the SAGB block of FIG. 3 is a conceptual diagram of remote failure management of the present invention.

In FIG. 1, the user's data is input through a PSIB (one of 3, 4, 5, 6), passes through an ATMB 7 block which is responsible for ATM layer processing, and MDPB (8) which multiplexes / demultiplexes these data. ) Will pass through the block. User data past the MDPB (8) block is finally transmitted over the PTIB (9) block to the network side. On the contrary, user data from the network side is input to the PTIB (9) block and transmitted through the corresponding PSIB (3, 4, 5, 6) through the MDPB (8) and ATMB (7) blocks. In order to transmit data of these users, the ACPB (2) block directly controls the PSIB (3, 4, 5, 6), ATMB (7), MDPB (8), and PTIB (9) hardware. It is also responsible for the OAM function. In the SCPB (1) block, the communication function with the operator operating the CANS 10, the signaling function of the CANS, the network management function of the CANS, etc. are comprehensively executed, and the functional block thereof is shown in FIG.

The MMIB 14 block of FIG. 2 performs a communication function with an operator operating a CANS system through a console terminal, and the data generated by the operator's instructions are sent to the SMFB 13, SIGB 12, and SAGB. (15) It is responsible for transmitting to blocks and interpreting data from each block and reporting it to the operator. The SMFB (13) block interprets the data sent from the MMIB (14) by the operator's instructions and executes the indicated command. The hardware-related information is transmitted to the ACPB (2) block through the IPCB (11) block. In addition, the system allocates resources to the SIGB 12 and SAGB 15 blocks while exchanging messages, and performs initialization such as initializing when the system is first started. The SIGB 12 block interprets and executes the signal related data presented through the IPCB 11 block, and communicates the related information with the SMFB 13, MMIB 14, and SAGB 15 blocks.

The SAGB 15 block is a block in which the present invention is implemented, and is responsible for interpreting network management instructions displayed through Ethernet and transmitting CANS-MIB information or designating a new value according to the indicated instruction. do. It collects and organizes CANS-MIB related information through MMIB (14), SMFB (13), and SIGB (12) blocks, and collects and organizes the information displayed through IPCB (11). It also collects and analyzes fault-related information and executes the task. If necessary, CANS-MIB information is transmitted to the SMFB 13, SIGB 12, and MMIB 14 blocks.

3 is a conceptual diagram of remote failure management in which the present invention is implemented.

That is, the SAGB block on the CANS side performs the function of reporting the information to the remote place while analyzing and processing the fault information, and the remote network management system analyzes the received fault information and performs the fault processing and statistics processing if necessary. Perform a function such as updating the MIB.

4 is a flowchart illustrating overall failure management in a CANS system according to the present invention.

When the hardware failure information 101 and the software failure information 102 are received, it is determined whether the processing is possible inside the CANS system (103). The basis for judgment is specified by the operator and remote manager in advance, taking into account the frequency of failure or the processor power of the CANS system.

If internal processing is possible, the fault information is analyzed (104), and the fault is processed (105). The MIB is then updated (106), reported to the operator and the remote administrator (107), and terminated. If the internal processing is not possible, immediately update the relevant MIB (106), report the information to the operator and the remote administrator (107), and then terminate. The processing procedure of the failure information analysis 104 function is shown in FIG. 6, the failure processing 105 function is shown in FIG. 7, the relevant MIB update 106 function is shown in FIG. 8, and the operator and remote location information reporting function 107 is shown in FIG. 9. The flow chart is shown in.

When there is SNMP indication information related to the failure processing (108), the information is analyzed (109), the process is processed (110), the corresponding MIB is updated (111), and ends.

6 is a flowchart of failure information analysis in a CANS system.

First, check whether a failure has occurred (301), and if a failure occurs, analyze the failure contents (302). This is to identify the type of system handicapped, board handicapped, port handicapped, connection handicapped, software handicapped, etc. Thereafter, these disabilities are determined as a pre-determined disability 303, and in the case of the prescribed disability, a disability grade of urgent / major / normal is determined (304). If it is confirmed as recovery information rather than a failure (301), a message is sent to the SMFB block (305), the associated MIB is updated (306), a message is configured for the operator report (307), and reported to the operator ( 308). If the failure is not a defined fault, that is, the analysis is not possible, a suitable message is constructed (307) and reported to the operator (308).

7 is a flowchart of troubleshooting in a CANS system.

It is determined whether the isolation of the portion where the failure has occurred is necessary (401). If quarantine is necessary, quarantine the affected part (402), generate an alarm signal (403), and send a message to the SMFB (404). If no isolation is required, a message is sent to the SMFB (404).

8 is a flow diagram of an associated MIB update in a CANS system and a remote system.

After retrieving the MIB for each type of failure (501), the failure information is compared (502). If these data are different from each other, the corresponding MIB is updated (503). However, if their data values are the same, a message for reporting is constructed (504) and then output to the operator or administrator (505).

9 is an operator and remote information reporting flowchart in the CANS system.

First, the alarm type is classified (601), a corresponding message is configured (602), and output to the operator (603). Thereafter, it is determined whether it is a type to be reported to a remote location (604), and if it is a matter to be reported, an SNMP message is configured (605) and transmitted (606).

5 is a flowchart of overall failure management in a remote system.

First, when an SNMP message is received (201), it executes SNMP protocol processing (202). Since this is a standardized protocol for transmitting and receiving management information between systems, there is no separate flow chart, and the standardized procedure is followed. After analyzing the failure information (203), it is determined whether the processor can be generated in the network management system (204), if possible to generate a processor (205), and after performing the corresponding failure processing (206) In operation 208, the failure information is performed. However, when it is determined that the processor cannot be generated (204), it is reported to the administrator (207) and the post processing of failure information is performed (208). The limit of the processor is designated by the administrator in advance, and this is determined by considering the processor capability of the system.

In the failure information post-processing, failure information is first collected and statistically processed (209), and the associated MIB is updated (210).

10 is a flowchart of the failure information analysis 203 function, a flowchart of the failure processing 206 function is shown in FIG. 11, a flowchart of the failure information collection and statistics 209 function is shown in FIG. 12, and a MIB update 210 function is shown. The flowchart is shown in FIG.

10 is a flowchart of failure information analysis in a remote system.

First, it is determined whether or not the failure occurs or recovery (701), and in the case of a disabled person the analysis of the failure (702). Here, we extract which kind of failures occurred in which systems and at what locations. The disability level is then determined (703). However, if it is determined as recovery information (701), the relevant MIB is updated (704), a message for reporting is constructed (705), and reported to the administrator (706).

11 is a flowchart of failure handling in a remote system.

After retrieving the relevant MIB information for each of the failure contents (801), it is determined whether the failure needs to be indicated to the system (802). If necessary, an SNMP message is constructed (803) and transmitted (804).

12 is a flow chart of fault information collection and statistics in a remote system.

After determining whether short-term information collection has been selected (901), if information collection is desired, the relevant system number is retrieved (902), and information on the type of failure and location (903) is stored. It is then determined whether to run long term statistics (904). If short-term information collection is selected as unnecessary (901), it is immediately determined whether to execute long-term statistics (904). If the long-term statistical function is to be executed (901), the relevant system number is retrieved (905), and the statistical data for that time is retrieved (906), and the data is updated (907).

The present invention described above is capable of various substitutions, modifications, and changes within the scope without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains, and thus is limited to the above-described embodiments and drawings. It is not.

In the conventional case, the centralized B-NT system had a failure management function in itself, but there was no remote failure management function. The present invention proposes a problem management method using SNMP to perform a problem management function at a remote location.

In the CANS ATM device in which the present invention is implemented, there is a MIB. In this case, MIBs necessary for fault management are set in advance, and when a failure occurs in the system, the contents of the corresponding MIB are transmitted to the remote network manager. According to the instruction, necessary actions are performed.

According to the present invention, in the CANS system, when a failure occurs, it is first determined whether it is executable in itself, and only when the self execution is possible, and if it is impossible to execute in itself, such as a case of message congestion, it is immediately reported to the remote administrator. And the load of the failure management block can be reduced by not immediately executing the error handling.

It is also possible to simultaneously control a large number of identical devices at a remote location.

Claims (9)

In a failure management method applied to a centralized B-NT system (hereinafter referred to as a CANS system) for remote failure management using a simple network management protocol (SNMP), when hardware failure information and software failure information are received, a failure occurs. A first step of determining whether processing within the CANS system is possible in consideration of factors including frequency and processor capability of the CANS system; The second step of analyzing the fault information, processing the fault, updating the related MIB, and reporting the information to the operator and remote manager if internal processing is possible; if the internal processing is not possible, update the related MIB immediately. And a third step of reporting the information to the remote manager. The method of claim 1, wherein the procedure for analyzing failure information in the second step confirms whether a failure has occurred, and if the failure occurs, the failure information is a system disabled board, a disabled board, a disabled port, a connected disabled software, a disabled person, etc. Analyzing the contents of the disability by identifying the type and location of the disability; Determining whether these disabilities are pre-defined disabilities, and determining disability grades of urgent / major / moderate if the disabilities are prescribed; sending a message to the system management function block (SMFB) if it is identified as recovery information rather than a disability. Failure management method in a CANS system characterized in that it comprises a process. 2. The method of claim 1, wherein the failure processing procedure in the second step comprises: determining whether the isolation of the portion where the failure has occurred is necessary; if an isolation is required, an isolation signal is generated and an alarm signal is generated. And transmitting a message to a system management function block (SMFB), and if the isolation is not necessary, transmitting a message to a system management function block (SMFB). The method according to claim 1, wherein the related MIB update processing procedure in the second and third steps comprises: searching for MIBs for each type of failure and then comparing failure information; if the data are different from each other, updating the corresponding MIB. If the data value is the same, and comprises a process for configuring a message for reporting, and outputting it to the operator or administrator, the failure management method in a CANS system, characterized in that the. The method of claim 1, wherein the operator and remote alarm report processing procedure in the second and third steps comprises: classifying alarm types, constructing a corresponding message, and outputting the message to the operator; In the case of a matter to be reported by determining the recognition, failure management method in a CANS system comprising the step of constructing a simple network management protocol (SNMP) message and transmitting to a remote location. A failure management method applied to a remote system for remote failure management using a simple network management protocol (SNMP), comprising: a first step of executing an SNMP protocol process when a simple network management protocol (SNMP) message is received; A second step of determining whether a processor can be generated in the network management system; generating a processor if it can be generated, executing a corresponding failure process, and performing post-processing of failure information; When it is determined that the processor can not be generated, the fourth step of reporting this to the administrator, and performing post-processing failure information; In the post-processing failure information, the failure information is first collected and statistically processed, and the relevant MIB is updated. And a fifth step of the failure management method in the remote system. The method of claim 6, wherein the process of analyzing fault information in the second step determines whether a fault has occurred or is repaired, and in the case of a fault, extracts what kind of fault has occurred at which location in which system. Analyzing; judging the level of disability; If it is determined as recovery information, updating the relevant MIB, constructing a message for reporting, and then reporting it to the administrator. The method of claim 6, wherein the fault handling procedure in the third step comprises: searching for relevant MIB information for each fault content, and then determining whether to indicate to the failing system; A method of managing a failure in a remote system, comprising: constructing a management protocol (SNMP) message and transmitting the same. The method of claim 6, wherein in the fifth step, the information collection and statistical processing procedure of the fault information is performed after determining whether short-term information collection has been selected. The process of storing; the process of determining whether to execute long-term statistics; if it is selected that short-term information collection is unnecessary, it is determined whether to execute the long-term statistics immediately. Retrieval of statistical data, and updating the data.