KR20040028400A - Fault management system of metro ethernet network and method thereof - Google Patents

Abstract

PURPOSE: A device and a method for processing a failure of a Metro-Ethernet network are provided to efficiently process the failure through a central server by transmitting the failure information to the central server while frequently monitoring the Metro-Ethernet network through a gateway system. CONSTITUTION: The gateway systems(3,4,5) for managing local networks dividing each network are placed to each region. The gateway systems and an operator(1) are connected through a Metro-Ethernet network management system(2). The gateway system collects information for each network and alarm information such as failure information, and transmits the alarm information to the Metro-Ethernet network management system. The Metro-Ethernet network management system processes/manages the failure using the alarm information and informs the operator of the failure. The Metro-Ethernet network management system includes a network management database(20) and the central server(21). The central server includes a failure manager(22), a configuration manager(23), a performance manager(24), a GUI(Graphic User Interface) device(25), an additional device(26), and a linking device(27).

Description

Fault management system of metro Ethernet network and method thereof

The present invention relates to a failure handling apparatus and a method of a macro Ethernet network, and has a macro Ethernet network management system between an operator and a gateway system, and performs a fast and accurate failure management, the Ethernet Ethernet network capable of efficient network management The present invention relates to an apparatus and a method for treating disorders.

At present, the domestic Internet environment is based on the wireless LAN environment and the macro Ethernet method due to the rapid spread of asymmetric digital subscriber lines (hereinafter referred to as ADSL) and the expansion of the base of personal computer (PC) game rooms. The way access networks are organized is on the rise.

Accordingly, in order to provide a stable service through smooth operation management of the access network, network operators need a network management system that manages each network element constituting a new access network.

However, when a problem occurs such as a failure in a large network having hundreds of thousands of network elements, it is necessary to accurately identify where the failure occurs and to deal with the failure quickly. It only functions as much as storing it in a database, processing it, and outputting it. Therefore, it is difficult to manage a stable and efficient network.

In addition, conventionally requires the expansion of a large capacity server for monitoring the status of all the devices and ports constituting the large-scale Internet network and collecting performance data, but the expansion of large capacity server is economical and labor loss is difficult to be realistically implemented.

In order to solve this problem, a unit gateway management area is divided by using a conventionally distributed gateway system, data is collected for devices existing in the divided management area, raw data is generated, and various central management servers are used. Notify via communication means. The central management server collects the received data, processes it, stores it in a database, and makes it available to other related systems such as a billing system.

However, when transmitting data to a central server in such a gateway system that is located locally, there is a problem that it is difficult to efficiently process a large amount of data in a short period of time to transmit a small amount containing the correct information.

An object of the present invention for solving the above problems, by monitoring the Ethernet network in a macro through the gateway system from time to time to detect the occurrence of the failure, by transmitting the failure information to the central server, through the central server to efficiently handle the failure There is.

1 is an overall system diagram for the failure of the macro Ethernet network according to the present invention.

Figure 2 is a block diagram of a macro Ethernet network management system of FIG.

3 is a block diagram of the failure management apparatus of FIG.

4 is a configuration diagram of a gateway system of FIG. 3.

5 is a diagram illustrating a format structure for transmission between a central server and a gateway system according to the present invention;

6 is a flowchart illustrating a failure processing of a macro network according to the present invention.

The present invention for achieving the above object is an operator for managing the Ethernet Ethernet network, a plurality of gateway systems for collecting information of a plurality of local networks, testing the local network, and transmits the test results, and the plurality of Located between the two gateway systems and the operator, characterized in that it comprises a network management system for analyzing the test results and information collected from the plurality of gateways and processing the fault display to the operator.

The above and other objects and features and advantages of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings.

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

1 is a complete system diagram for failure handling of a macro ethernet network according to the present invention, a failure handling system of a macro ethernet network manages local networks which first divide each network in order to manage failure of a macro ethernet network. The gateway system (3, 4, 5) is located locally, and each of the gateway system (3, 4, 5) and the operator 1 is provided with a macro Ethernet network management system (2) to connect .

The gateway system (3, 4, 5) collects alarm information such as information about each network and fault information from each local network, transmits the alarm information to the macro Ethernet network management system (2), and the macro Ethernet The network management system 2 uses the alarm information transmitted from the gateway systems 3, 4, and 5 to perform fault processing and fault management, and notify the operator 1.

Referring to FIG. 2 to describe the macro Ethernet network management system 2 in more detail, the macro Ethernet network management system 2 includes a network management database 20 and a central server 21.

The network management database 20 receives and stores the fault information collected by the gateway systems 3, 4, and 5 from each local network through the central server 21, and interlocks with the central server 21 to provide a central server. Provide the necessary information in (21).

The central server 21 includes a failure management device 22, a configuration management device 23, a performance management device 24, a GUI function device 25, an additional function device 26, an interworking function device 27, By using the fault information received from the gateway system (3, 4, 5), the fault handling and management.

The failure management device 22 collects information of each local network from each gateway system 3, 4, 5, and performs device ping (packet internet groper) test, port ping test, and simple network management. A simple network management protocol (hereinafter referred to as SNMP) detects a fault through a polling test, collects an SNMP trap, handles the fault, and stores the result in the network management database 20. , The alarm information stored from the network management database 20 is fetched.

Here, ping is a basic Internet program that checks whether a specific Internet address exists and can accept the request. It is used to check whether the host that the user is trying to access is actually running. In addition, ping can determine how fast a running host responds. It can also find the IP address of a site that only knows the domain name.

In addition, polling is a transmission control method that continuously checks the status of other programs or devices in a program or device in communication. Generally, polling indicates whether a corresponding program or device is connected or wants to transmit data. Check it.

SNMP, on the other hand, is a protocol for monitoring and integrating network management and operation of network devices. Trap is a special condition placed in a running program for testing. For example, error traps test and restore error conditions. To provide a routine, a debugging trap is to wait for the execution of a particular instruction, stop the program, and analyze the system state at that moment.

The configuration management apparatus 23 registers information such as location information and subscriber information of the network apparatus in the network management database 20 by using the alarm information collected through the failure management apparatus 22 described above. The information related to the facility is used to generate and modify reports on the network facility.

The performance management device 24 collects the performance information of the network device collected through the above-described failure management device 22 and registered in the network management database 20 and ports and links included in the network device. After the process analysis, a report on the network device and port, etc. is generated and notified to the operator or stored in the network management database 20.

The GUI function device 25 provides a graphical interface on the screen of the operator 1 remotely located in the information, reports and information of the network facilities, devices, etc. processed from the configuration management device 23 and the performance management device 24 described above. By displaying through, the operator 1 can confirm the information.

The additional function device 26 is responsible for additional functions such as operator management and system management of the central server 21, and the interworking function device 27 is interlocked with other external systems 28 such as billing related systems, Send and receive information such as billing of the network facilities.

3 will be described in more detail with respect to the above-described failure management apparatus 22. The failure management apparatus 22 includes a communication processor 220, a config manager 221, a management target distributor 222, a buffer 223, and a failure information processor 224.

The communication processor 220 transmits / receives alarm information and SNMP trap information collected from each local area network in connection with each gateway system 3, 4, and 5, and performs a ping test and an SNMP polling test from the management target distributor 222. If there is a request, the test request is transmitted to the gateway system 3, 4, 5, and the test result is received and delivered to the above-described management target distributor 222.

In addition, when the designated gateway system 3, 4, 5 cannot communicate while transmitting and receiving alarm information with the gateway system 3, 4, 5, the config manager 221 is notified of the fact that it is down, and in advance, The designated backup gateway system 225 temporarily transmits alarm information such as a device list and a port list to the network information.

As described above, the config manager 221 designates a data transmission structure between the communication processor 220 and the local gateway systems 3, 4 and 5, and determines whether the gateway system 3, 4, 5 is operating normally. It monitors, designates the backup gateway system 225, manages the number of buffers 223 and the size of each buffer 223, the cycle T of the management target distributor 222, and the filtering IP list.

The management target distributor 222 is configured within the period T in which the network device registered in the network management database 20 and the port information and node information included in the network device are previously specified from the configuration management device 23 described above. Search once. By using the retrieved node information, a device list and a port list are generated, and filtering out inappropriate IP information based on the IP information, and then the filtered information is transmitted to the interworking function device 27, and the other system 28 is connected. Is sent. At this time, IP is assigned to all devices, and IP is also assigned to each port.

Meanwhile, the generated device list and the port list are stored in a memory (not shown) that the management target distributor 222 has built-in, and when there is no change in the period T of the management distribution distributor 222, the memory ( Node information, device list, and port list existing on the network (not shown), and if there is a change, extracts a list, generates a new device list and a port list, and transmits it to the communication processor 220. If there is no change, the communication processor 220 notifies "no change".

The buffer 223 is a memory array of the central server 21 system, and the size and number of memory arrays are designated by the config manager 221 and according to the size of the central server 21 system and network elements to be managed. Is determined.

The failure information processor 224 monitors the above-described buffer 223, extracts information stored in the buffer, and uses the extracted information to determine whether the information relates to a device or a port. After that, in the case of a device, the information is compared with the information about the device stored in the network management database 20, and if there is a change, the change in the device table (not shown) of the network management database 20. Save it.

On the other hand, if the target of the information is a port, it is determined whether or not the device including the corresponding port is broken. If the device is disabled, the information on the port is discarded. The information of the corresponding ports stored in the management database 20 is compared, and if there is a change, the change is stored in a port table (not shown) of the network management database 20. This is because when a device fails, all ports belonging to the device are in a failed state, but just because a device is in a failed state does not mean that all ports are in a normal state of failing back.

The failure of the node and the number of failures of the node having a failure is stored, and the corresponding information is displayed on the operator screen through the GUI function device (25).

On the other hand, if the type of failure is different from the type of the ping test, SNMP polling, SNMP trap used by the error handling device 22 proposed in the present invention, only the failure type is added to the failure details of the device and port list, and the rest Discard the contents.

FIG. 4 is a configuration diagram of the gateway system of FIG. 3, which includes a failure collector 40, a communication processor 46, and a filter 45.

Fault collector 40 discloses a device ping tester 41, a port ping tester 42, an SNMP polling tester 43, and an SNMP trap collector 44.

The device ping tester 41 performs a ping test on all devices existing in the local network once in a period T transmitted from the central server 21 through the communication processor 46, and filters the test results into the filter 45. To send. At this time, the period (T) is preferably set so that the device ping tester 41 can fully test all the devices of the local network.

The port ping tester 42 performs a ping test on all ports included in all devices in the local network once in a period T transmitted from the central server 21 through the communication processor 46. Because of the large number, a thread is created to run multiple tests simultaneously. At this time, the number of threads is transmitted from the central server 21 through the communication processor 46. Here, the period T is preferably set so that the device port ping tester 42 can fully test all devices in the local network.

The SNMP polling tester 43 performs an SNMP poll for all devices in the local network once in a period T transmitted from the central server 21 through the communication processor 46, thereby performing a device from the SNMP agent of each device. It reads ifOperStatus item with up-down information about all ports belonging to and determines whether each port is in normal state. At this time, if SNMP polling fails, it is determined to be a device failure, and the result is transmitted to the filter 45.

The SNMP trap collector 44 is a daemon process that receives an SNMP trap message notified by each device, and transmits all received trap messages to the filter 45.

The filter 45 continuously stores the results of performing the ping test and the SNMP polling test requested from the management target distributor 222, and compares the new ping test result with the stored ping test result. If there is no change in the result value, it is discarded. If there is a change in the result value, the result value including the test period is transmitted to the central server 21 through the communication processor 46.

In addition, the filter 45, when the management target distributor 222 requests to collect the SNMP trap, if all the various traps delivered by the device to pass to the central server 21, the load on the central server 21 is increased, Remove all traps except the port's up / down traps. And, depending on the device, if multiple traps occur for one device failure, the filter 45 causes only one trap to be sent to the central server 21.

The communication processor 46 receives the target and management distributor period T for collecting the fault information in the region from the central server 21, and transmits the filtered information to the central server 21 through the filter 45. It handles the communication with the central server 21.

At this time, the communication processor 46 transfers the filtered information to the communication processor 220 of the central server 21 in a predetermined format to the socket, the socket is to communicate with the channel, once the port used once knows each other It should be able to communicate in a predetermined format by predetermine which values come in sequence like the program's struct syntax.

Referring to FIG. 5 to describe the format proposed by the present invention.

As shown in FIG. 5, the format includes IP address information, state information, object type, event type, time information, gateway IP address information (destIpAddress), gateway index information (gwIndex), and the like. It includes.

FIG. 6 is a flowchart illustrating a failure handling of a macro network according to the present invention, in which a failure of an apparatus and a port of a local network occurs and the operator 1 recognizes the failure.

The gateway system 3, 4, 5 periodically performs ping test and SNMP polling test on each local network, so that the ping tester 41, 42 detects a failure during the test, or the SNMP polling tester 43 is a port. The up / down state of the ifOperSttus item is read and trap information is collected from the SNMP trap collector 44 (S60).

The collected information is filtered using the filter 45 of the gateway systems 3, 4, and 5 to determine whether there is a state transition of the corresponding information (S61). And discards the trap information (S69), and if there is a state transition, transmits the corresponding test result and the trap information to the communication processor 220 of the central server 21 (S62).

The test result and the trap information thus transmitted are stored in the buffer 223 (S63), and the target of the test result and the trap information is identified as a device or a port through the fault information processor 224 (S64). If it is a device, it is determined whether there is a state transition by comparing with the corresponding device information registered in the network management database 20 (S65).

If there is no state transition in the above-described step (S65), the corresponding information is discarded (S66). If there is a state transition, the test result and trap information are stored in the network management database 20 and then terminated.

On the other hand, if the target is a port in the above-described step (S64), it is determined whether the test result and trap information is failure information or failure recovery information (S68), in the case of failure information, whether the device to which the port belongs is disabled. By determining whether (S69), if the device of the corresponding device is disabled, the corresponding information is discarded (S66).

On the other hand, if the device does not belong to the corresponding port list by comparing the previously stored port list and the corresponding test results and trap information, to determine whether there is a state transition of the test results and trap information (S70), if there is no state transition Discarding the information (S66), if there is a state transition, it is stored in the network management database 20 (S71), and ends.

If the test result and the trap information in the above-mentioned step (S68) is the failure recovery information, it is determined whether there is a state transition of the failure recovery information (S72), and if there is no state transition (S73), if there is a state transition It ends after storing in the network management database 20 (S74).

As such, when the alarm information transmitted from the gateway systems 3, 4, and 5 is stored in the buffer 223, the fault information processor 224, which frequently monitors the buffer 223, extracts the alarm information stored in the buffer 223. Then, it is determined whether the corresponding alarm information relates to the device or the port.

Thereafter, if the corresponding alarm information is information about a device, it is stored in the network management database 20. If the corresponding alarm information is information about a port, it is determined whether a device to which the corresponding port belongs is a failure, and a device to which the corresponding port belongs to has failed. Otherwise, if discarded, and stores the information of the device to which the port belongs in the network management database (20).

Therefore, the fault management is flexibly managed according to the network size through the gateway system (3, 4, 5) which collects the fault information from the central server 21 and the access network devices existing in each region and communicates the management information with the server system. Do it.

As described above, the fault handling apparatus and method of the macro Ethernet network according to the present invention, fast and accurate fault detection through the device ping tester, port ping tester, simple network management protocol polling tester, simple network management protocol trap collector By dealing with faults, it is effective to provide the best service to customers through stable network management.

In addition, a preferred embodiment of the present invention is for the purpose of illustration, those skilled in the art will be able to various modifications, changes, substitutions and additions through the spirit and scope of the appended claims, such modifications and changes are the following claims It should be seen as belonging to a range.

Claims (6)

Operator to manage the Ethernet network in a macro; A plurality of gateway systems collecting information on a plurality of local networks, testing the local networks, and transmitting the test results; Located between the plurality of gateway systems and the operator, a failure management apparatus of a macro Ethernet network including a network management system for analyzing and testing the test results and information collected from the plurality of gateways and display them to the operator . According to claim 1, The network management system, A network management database for storing network information, alarm information, device and port information, and failure handling details; And Compared with the information received from the gateway system and the information of the network management database, if there is any changed information in the network management database, the failure processing apparatus of the macro Ethernet network characterized in that it comprises a central server for handling the failure . The method of claim 2, wherein the central server, A failure management device receiving failure information of the local network from the gateway system and handling and managing the failure; A configuration management device that stores the location information and the subscriber information of the device in the network management database and generates a report on the device, if the object having a failure is a device using the failure information; A performance management apparatus using the failure information to store information on the port in the network management database and to generate a report regarding the port if a failure target is a port; A graphical interface device displaying information stored in the network management database to the operator through the configuration management device and the performance management device; An additional function device for operator management and system management; And Failure handling apparatus of the macro Ethernet network characterized in that it comprises an interlocking function device interoperating with an external system. According to claim 3, The failure management device, A communication processor for transmitting a test request message to the gateway system and receiving the failure information and a test result; A management target distributor for retrieving device and port information stored in the network management database once in a predetermined period and generating a device list and a port list using the retrieved information; A configuration manager for designating a data transmission structure between the communication processor and the gateway system and monitoring whether the gateway system is in normal operation; A size and number designated by the config manager, and a buffer configured to temporarily store the test result and the failure information; And By using the fault information, it is determined whether the corresponding fault is a handicap for a device or a handicap for a port. If the device is a fault, the fault processing is performed using information related to the device. Failure handling apparatus of the macro Ethernet network characterized in that it comprises a failure information processor for processing. The method of claim 1, wherein the gateway system, A device ping tester for pinging the device; A pot ping tester that pings the pot; A simple network management protocol polling tester configured to perform a simple network management protocol polling test on the local network; And a simple network management protocol trap collector for collecting a simple network management protocol trap for the local network. A fault detection step of detecting a failure of a network element using a ping test, a simple network management protocol polling test, and a simple network management protocol trap collection; A transmission step of transmitting the detected failure information to a central server and storing in the buffer; A determination step of determining whether a target of the failure information transmitted from the buffer is a device or a port; A device step of comparing the previously stored device information with the device information of the alarm information, discarding if there is no change, and storing the changed information newly if there is a change in the determination step; If the target is a port in the determination step, if the device to which the port belongs has a failure, discard the device. A port step of newly storing the changed information if there is a change; When the alarm information about the port in the port step is the failure recovery information, the previously stored failure recovery information and the failure recovery information of the alarm information is compared and discarded if there is no change, and if there is a change, the changed information is newly stored. How to deal with the failure of the macro Ethernet network including the storage step.