KR20180005554A - Flow management system, controller and method for detecting fault - Google Patents

Abstract

A flow control system, controller and fault detection method are provided. The flow control system includes a collecting unit for collecting fault event messages generated in the network equipment, and a flow controller for analyzing the fault event message and detecting at least one flow in which the fault has occurred.

Description

[0001] FLOW MANAGEMENT SYSTEM, CONTROLLER AND METHOD FOR DETECTING FAULT [0002] FIELD OF THE INVENTION [0003]

The present invention relates to a flow control system, a controller, and a fault detection method.

Due to the development of communication and networks, network administrators often request network configuration, and customers want to transfer data using different connection resources in accordance with the characteristics of data, that is, real-time, importance and security.

Also, in a world that wants to connect with all things, the importance of dataflow becomes bigger.

In the Internet environment that we currently use, we set up a flow in units of user packets (data) and transmit the data.

However, in the 5G network, it plans to apply wireless, mobile, optical transmission and IoT (Internet of Things) based on SDN (Software Defined Network) / NFV (Network Function Virtualization).

SDN and NFV, which are virtual network environments, also need to create flows for communicating with each other and transmit data using them.

In this way, in order to efficiently and reliably transmit data in a virtual network environment, it is necessary to manage each flow in which data is transmitted.

In the future, the number of network devices will increase more and more, and there is a problem that the complexity is great when the failure is managed in the network equipment unit as in the present.

A problem to be solved by the present invention is to provide a flow control system, a controller, and a fault detection method for managing faults of network equipment in units of a flow.

According to one aspect of the present invention, a flow control system includes a collecting unit for collecting fault event messages generated in network equipment, and a flow control unit for analyzing the fault event message and detecting at least one flow that has failed .

The flow control unit,

And outputting a fault management screen showing at least one flow in which the fault has occurred among the plurality of flows.

The flow control unit,

When the fault occurred flow is clicked on the fault management screen,

In the fault detail screen,

And fault detail information generated in at least one network device connected to the clicked flow,

The fault detail information,

A failure grade, an alarm code, a network equipment name, a light message, an occurrence position, a failure type, and an alarm reception time acquired from the failure event message.

Further comprising a storage unit for storing flow configuration information mapped with device identification information and location information of each of at least one network equipment connected to the flow for each flow,

The flow control unit,

Wherein the controller is configured to detect the faulty network device and location information of the faulty network device by parsing the fault event message and to use at least one flow mapped to the faulted network equipment and location information using the flow configuration information, .

The flow control unit,

Flow generation information, flow change information, and flow deletion information from a controller that controls the network devices to generate and update the flow configuration information,

Wherein the flow generation information, the flow change information,

A flow identifier, and device identification information and location information of the network equipment connected to the flow.

The location information may include:

Wherein the information includes at least one of rack information, shelf information, slot information, port information, and channel information of a network equipment,

The flow control unit,

Extracting at least one of rack information, self information, slot information, port information, and channel information of a failed network device by parsing event information included in the failure event message, and transmitting at least one flow mapped to the extracted information Can be detected from the flow configuration information.

The event information is in the form of a serial number in which letters and numbers are combined,

The flow control unit,

Self information, slot information, port information, and channel information corresponding to the respective rack numbers according to the manufacturer of the network equipment or the rack type or the self type, Information of at least one of the information can be retrieved from the flow configuration information to detect a corresponding flow.

According to another aspect of the present invention, there is provided a controller for managing network devices, comprising: a flow controller for performing a flow creation, an alteration, and a deletion through an interface with the network devices; And a flow control unit operable to transmit the device identification information and the position information to the flow control system,

Wherein the device identification information and the location information of the network equipment,

And can be used to manage the failure of the network equipment in the flow control system on a flow-by-flow basis.

Wherein the flow controller-

It is possible to transmit the device identification information and the location information for all the network devices located at the end of one flow with respect to one flow.

Wherein the flow control unit comprises:

When a flow connection command is transmitted to at least one network equipment requiring flow connection, deletion and change and a response indicating whether a command is executed is normally received, a flow identifier and at least one network equipment To the flow control system through the flow controller interworking unit.

According to another aspect of the present invention, a fault detection method includes a flow control system connected to a controller for controlling network equipment, the method comprising: receiving a fault event message generated in the network equipment; And analyzing the fault event message to detect at least one flow that has failed.

After the detecting step,

Outputting a fault management screen displaying at least one flow in which the fault has occurred from among a plurality of flows and switching to a fault detail screen when clicking the fault occurred flow on the fault control screen,

In the fault detail screen,

The fault detail information including the fault occurrence time, the alarm grade, the alarm code, the network equipment name, the light message, the occurrence position, the fault type, and the alarm reception time acquired from the fault event message.

Before the receiving step,

Further comprising the step of generating flow configuration information to which device identification information and location information of each of at least one network equipment connected to the flow for each flow are mapped,

Wherein the detecting comprises:

The method comprising the steps of: detecting the failed network device and location information of the failed network device by parsing the failed event message; and analyzing at least one flow mapped to the failed network device and the location information using the flow configuration information, And determining that the flow has occurred.

The location information may include:

Wherein the information includes at least one of rack information, shelf information, slot information, port information, and channel information of a network equipment,

The step of detecting the location information of the failed network equipment comprises:

Identifying event information in the form of a serial number in which characters and numbers are combined from the failure event message; determining whether the manufacturer and the equipment type of the failed network device is a rack type or a self type; Port information and channel information among sequential numbers other than numbers or letters detected by the rack information or the self information, and sequentially detecting slot information, port information, and channel information, And a step of detecting.

Wherein the generating comprises:

Flow generation information, flow change information, and flow deletion information from a controller that controls the network devices to generate and update the flow configuration information,

The flow generation information, the flow change information, and the flow deletion information may include a flow identifier and device identification information and location information of the network equipment connected to the flow.

According to the embodiment of the present invention, it is possible to provide a failure monitoring function in a flow unit, which is a logical connection unit logically created for data transfer in a virtual network such as SDN / NFV, Recognition and coping.

In addition, since it is possible to monitor the processing performed only by the equipment failure by using the fault event occurring in the network equipment, it is possible to monitor the flow based on the flow, so that the fault can be identified by the service name or the specific name, .

FIG. 1 is a diagram illustrating a network configuration for managing faults on a flow-by-flow basis according to an embodiment of the present invention.
2 is a conceptual diagram of a software defined networking (SDN) system according to an embodiment of the present invention.
3 is a block diagram showing a configuration of a flow control system according to an embodiment of the present invention.
4 is a flowchart illustrating a fault detection method of a flow control system according to an embodiment of the present invention.
5 is an exemplary diagram of flow configuration information according to an embodiment of the present invention.
6 is a view for explaining elements constituting a location of a network equipment according to an embodiment of the present invention.
7 is a diagram illustrating a configuration of a failure event message according to an embodiment of the present invention.
8 is a diagram for explaining fault event parsing according to an embodiment of the present invention.
9 is an exemplary diagram mapping a fault event according to an embodiment of the present invention with flow configuration information.
10 is a flowchart illustrating a fault event parsing process according to an embodiment of the present invention.
11 is a view for explaining channel information mapping according to an embodiment of the present invention.
12 is a view illustrating an example of a fault management screen according to an embodiment of the present invention.
13 is a diagram illustrating an example of a fault detail view screen according to an embodiment of the present invention.
14 is a block diagram showing a configuration of a controller according to an embodiment of the present invention.
FIG. 15 is a flowchart showing a flow generating operation according to an embodiment of the present invention.
16 is a flowchart showing a flow erasing operation according to an embodiment of the present invention.
17 is a flowchart showing a flow changing operation according to an embodiment of the present invention.
18 is a hardware block diagram according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly explain the present invention, parts not related to the description are omitted, and like parts are denoted by similar reference numerals throughout the specification

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise.

Also, the terms " part, "" module," and " module ", etc. in the specification mean a unit for processing at least one function or operation and may be implemented by hardware or software or a combination of hardware and software have.

Now, a flow control system, a controller, and a fault detection method according to an embodiment of the present invention will be described with reference to the drawings.

FIG. 1 is a diagram illustrating a network configuration for managing faults on a flow-by-flow basis according to an embodiment of the present invention.

Referring to FIG. 1, the flow control system 100 is interlocked with the controller 200. And collects fault event messages generated in the network devices 300 by being connected to the network devices 300. Then, the collected fault event messages are parsed to manage faults on a flow-by-flow basis. That is, although the fault has conventionally been managed in units of network equipment, the flow control system 100 manages and provides the fault on a flow-by-flow basis.

The controller 200 manages the network devices 300, and centrally manages and controls the plurality of network devices 300.

The controller 200 may define the flow of packets occurring in the network devices 300 of the lower layer. That is, it is possible to calculate a path (data path) to be flowed by referring to a network topology or the like with respect to a flow allowed in the network policy, and then set an entry of a flow in the network devices 300 on the path.

The controller 200 can communicate with the network devices 300 using a specific protocol, for example, a software defined networking (SDN) protocol, an open flow protocol, or the like.

The controller 200 monitors the network devices 300 and dynamically sets a packet transmission path of the network devices 300 in the network according to communication conditions. The controller 200 registers the flow on the network equipment 300 by creating a flow table.

Here, the flow defines a predetermined process (action) to be performed on a packet conforming to a predetermined rule (rule). A flow may refer to a packet flow of a particular path according to a series of packets sharing a value of at least one header field from a single switch or a combination of multiple flow entries of multiple switches.

The controller 200 may include a physical device or a virtual device. Examples of the controller 200 include a calculator such as a PC, an appliance, a workstation, a mainframe, and a supercomputer, an expansion board mounted on a calculator, or a virtual machine (VM) have.

The network equipment 300 functions to process packets under the control of the controller 200. The network device 300 can process the received packet and relay the flow between the network devices 400. [

The network devices 300 perform packet transmission according to the flow table. The network devices 300 transmit the received packet according to the flow entry registered in its own flow table.

Examples of network equipment 300 may be a mobile communication base station, a base station controller, a gateway device, a switch in a wired network, a router, a physical switch, or a virtual switch built on a physical machine. An example of a switch is a layer 3 switch, a layer 4 switch, an L7 switch / application layer 7 switch or a multi-layer switch, a proxy, a gateway, , A firewall, a load balancing device, a band control device, a security monitoring and control device, a base station, an access point, a computer having a plurality of communication ports, and the like.

The network device 400 may be a personal computer (PC), a client terminal, a server, a workstation, a supercomputer, a mobile communication terminal, a smart phone, or a smart pad.

At this time, the controller 200 creates, deletes and changes the flow through the network devices 300 and the API (Application Program Interface).

Here, A, B, D, F, G correspond to the network equipment connected to the flow between the devices 1 and 2. There may be a plurality of flows through one network equipment.

At this time, when the flow control system 100 receives the fault event message generated in the network device A, the flow control system 100 manages faults for all the flows connected to the network device A.

The controller 200 instructs each network device 300 to generate a flow in consideration of QoS (Quality of Service) or the like in order to transmit specific data to the destination 400. [ This process allows the controller 200 to use an open flow protocol, according to one example. That is, it controls which port of the network device 300 and which port of the destination network device 300 is to be connected. During this process, the flow control system 100 interacts with the controller 200 to construct the flow configuration information as shown in FIG.

That is, the flow control system 100 transmits network device information, rack information, shelf information, slot information, port information, and the like, which are related information, to all the network devices 300, Information of the channel, and channel information, and constructs the end information of one flow.

The controller 200 processes connection establishment, deletion, and change for all flows, and transfers the processed information to the flow control system 100. [ Through this process, the flow control system 100 always has the latest information of all the flows.

Thereafter, the flow control system 100 collects all the fault events from the network equipment 300 and displays the flow abnormality based on the fault event.

2 is a conceptual diagram of a software defined networking (SDN) system in accordance with an embodiment of the present invention.

SDN technology separates the control plane and the data plane so that most of the intelligence is located in the control plane of the controller and network devices such as switches or routers are used to control the control plane in flow units, for example through standardized protocols such as open flow protocols It has a simple structure that processes packets according to the rules it provides.

Referring to FIG. 2, the controller 200 is divided into an application layer and a control layer. A set of APIs is provided between the control layer and the application layer.

The application layer can implement common network services using APIs and can manage all types of policies such as routing, access control, traffic engineering, QoS management, and power control to meet business objectives.

The control layer can provide new functionality based on the Global View across network resources.

It can implement the configuration function of the subnetwork using the standardized API, and has the function to control the traffic, and to grasp the state of all the resources including the network and the server.

The controller 200 transmits a command to the network device 300. The network device 300 performs processing such as transmitting, modifying, or discarding a packet to a destination according to a command.

FIG. 3 is a block diagram illustrating a configuration of a flow control system according to an embodiment of the present invention. FIG. 4 is a flowchart illustrating a fault detection method of a flow control system according to an embodiment of the present invention. 6 is a view for explaining elements constituting a location of a network equipment according to an embodiment of the present invention. FIG. 7 is a view illustrating a flow of a fault event message according to an embodiment of the present invention. FIG. 8 is a diagram for explaining failure event parsing according to an embodiment of the present invention, FIG. 9 is an example of mapping failure events according to an embodiment of the present invention to flow configuration information, and FIG. FIG. 11 is a view for explaining a channel information mapping according to an embodiment of the present invention. FIG. An exemplary view showing a screen according to the control failure patients embodiment, and Fig. 13 shows an example of fault detail view screen in the embodiment;

3, the flow control system 100 includes a storage unit 101, a failure collecting unit 103, a flow control unit 105, and an output unit 107. [

The storage unit 101 stores flow configuration information mapped with device identification information and location information of each of at least one network equipment connected to the flow for each flow.

The fault collecting unit 103 collects the events from all the network devices 300. The fault collecting unit 103 receives the fault event message generated in the network equipment.

The flow controller 105 analyzes the fault event message and detects at least one flow in which the fault has occurred. And outputs to the output unit 107 a failure control screen displaying at least one flow in which a failure occurs among the plurality of flows.

The flow controller 105 parses the failure event message to detect the location information of the failed network device and the failed network device.

The flow controller 105 uses the flow configuration information stored in the storage unit 101 to determine at least one flow mapped to the network equipment and the location information of the fault as a flow in which the fault occurred.

The flow control unit 105 receives the flow generation information, the flow change information, and the flow deletion information from the controller 200 and generates and updates the flow configuration information of the storage unit 101. [

Here, the flow generation information, the flow change information, and the flow deletion information include a flow identifier and device identification information and location information of the network equipment connected to the flow. At this time, the location information includes at least one of rack information, shelf information, slot information, port information, and channel information of the network equipment.

At this time, referring to FIG. 6, one network device may include a rack, a shelf, a slot, and a port.

The rack may consist of a steel or synthetic resin frame having a box-shaped void space. These racks have space for mounting and fixing devices, and for connecting devices and cables. The internal space of the rack is divided into slots. The slot has the concept of unit space for detachment of equipment. The shelf guides the external equipment to be inserted into the slot and maintains the fastened state.

Each of these racks, shelves, slots, and ports is mapped to a serial number value that is a combination of letters or numbers for each network device, and these serial numbers can be used as location information of the network equipment.

3, the flow controller 105 parses the event information included in the failure event message to extract at least one of the rack information, the self information, the slot information, the port information, and the channel information of the failed network device And detects at least one flow mapped with the extracted information from the flow configuration information.

Here, when a failure occurs in the network device 300, a failure event is generated. The information display method of the failure event differs for each device manufacturer. Based on this point, the flow controller 105 distinguishes the device name and the information indicating the occurrence location of the failure such as a rack, a sal, a slot, a port, and a channel from the failure event information generated in each network equipment 300.

As described above, the flow control unit 105 performs an operation for mapping a fault event for detecting a network fault occurrence location from a fault event on a flow-by-flow basis using the flow configuration information. With this operation, it is possible to calculate which flow is affected by the fault occurrence event.

Here, in order to facilitate mapping, only necessary information may be extracted from the flow configuration information beforehand, and a table for mapping may be separately created.

The output unit 107 is means for outputting a flow control screen transmitted from the flow control unit 105 through a monitor.

Here, the flow control screen can be implemented as shown in FIG. Referring to FIG. 12, the flow control screen displays only each flow name and indicates in real time whether or not there is a fault in this flow.

At this time, when the flow having the fault is clicked, the screen is switched to the flow fault detail view screen as shown in FIG.

The cause of the failure in the flow may be caused by a failure occurring in the plurality of network devices 300. The fault detail screen comprises fault detail information generated in at least one network equipment 300 connected to the clicked flow.

These fault detail information lists the fault occurrence time, the alarm class, the alarm code, the network equipment name, the awakening message, the occurrence location, the fault type and the alarm reception time obtained from the fault event message.

Referring to FIG. 4, the fault detection operation of the flow control system 100 is as follows.

The flow control unit 105 collects flow information from the controller 200 in accordance with flow creation, change, and deletion, and generates and updates flow configuration information (S101).

The fault collecting unit 103 receives the fault event message generated in at least one network equipment 300 (S103).

The flow controller 105 parses the fault event message to detect the location of the faulty network device (S105), and maps the fault event on a per flow basis based on the fault occurrence location (S107). That is, the fault event is separated into information indicating the location (S105), and the separated information is mapped with the flow configuration information to determine the flow connected to the network devices 300 having the fault.

The flow controller 105 outputs the occurrence of the fault on the control screen in flow units (S111).

Referring to FIG. 5, the flow configuration information maps each piece of equipment information, rack, shelf, slot, port, and channel information connected to the flow for each of the flows (A, B, ...). Here, the equipment information is equipment identification information of the network equipment, and may be in the form of a serial number.

A plurality of different network devices may be mapped in one flow. A plurality of flows may be mapped to one network device.

FIG. 7 shows an example of a failure event message P1 generated in the network device 300. FIG.

Among the failure event messages P1, '10 .83.240.136 'and' 60848 'indicate the equipment name. In the fault event message P1, '2016-06-28 00:06:18' indicates the time when the fault event message was received. Among the failure event messages P1, 'INTF2.A-P2-AU3-6-2-TU3-1' indicates an alarm occurrence position, that is, a failure occurrence position. Among the failure event messages P1, 'STM64U' indicates a card name. &Quot; MJ " in the failure event message P1 indicates an alarm level.

That is, the flow controller 105 can predefine the type, type, etc. of information included in the failure event message and can parse the information necessary for detecting the failure occurrence position from the failure event message.

8 (a) is a table simplified by device name and event information. FIG. 8B is a table showing failure events for each event number.

The device name in FIG. 8A is the information detected in the failure event message P1 of FIG. 7, and the mapping relationship between FIG. 8A and FIG. 8B is determined by the flow control unit 105 in advance .

Therefore, the device name obtained by parsing the failure event message as shown in FIG. 7 is finally identified as '93354433B' through the mapping relationship between FIG. 8 (a) and FIG. 8 (b). The event information of FIG. 8A is also obtained by parsing the failure event message as shown in FIG. 7, which is confirmed as occurrence position information as shown in FIG. 8B, and this confirmation process will be described later with reference to FIG. 10 . That is, it is possible to parse occurrence location information '01010302501' from 'INTF2.A-P2-AU3-6-2-TU3-1' indicating the event information.

The generated location information of the flow corresponding to '93354433B' as shown in FIG. 8 (b) and the generated location information of FIG. 8 (b) are mapped to a rack, a shelf, a slot and a port, as shown in FIG.

The flow control unit 105 confirms the flow corresponding to '93354433B' with A and B. Among them, the flow at which the generation position information finally corresponds can be determined, and it is confirmed as the flow A. That is, in the occurrence position information '01010302501', the first two numbers (01) represent racks, the next two numbers (01) represent selfs, the next two numbers (03) (02) denotes a port, and the last three-digit number (501) denotes a channel. As described above, the generated location information is mapped to a rack, a shelf, a slot, a port, and a channel, respectively, to detect a corresponding flow.

Referring to FIG. 10, there is shown a process of detecting occurrence location information (01010302501) from the event information (eg, INTF2.A-P2-AU3-6-2-TU3-1) described with reference to FIG. 7 and FIG. This operation is performed by the flow control unit 105.

The manufacturer of the network device that has generated the failure event determines whether the device is 'same-searched' and whether the device type is the self-type (S101). Here, the rack-type equipment is a rack-type equipment, and a rack type equipment is mainly used where a lot of equipment is required at one time. And the self-type is a self-unit installed. Of course, some network devices can be rack-mounted and self-contained, but some require self-installation.

If it is judged as a self-type, 0101 is assigned to the beginning of the position information (S203). That is, rack = 01 and self = 01 are assigned.

It is judged whether or not the next three digits of 'INTF' included in the fault event (INTF2.A-P2-AU3-6-2-TU3-1) exist (S205). If so, the next three digits, i.e., '2.A', are assigned with slot = 03 (S209). At this time, since the slot order is 1A, 1B, 2A, and 2B, 1A = 01, 1B = 02, 2A = 03, 2B = 04,

Next, it is determined (211) whether there is a number after P in the event information (INTF2.A-P2-AU3-6-2-TU3-1). If it is present, the number following P, that is, 2 indicates a port, is assigned with port = 02 (S213).

It is determined whether the remaining symbols and numbers are included in the event information (S215). At this time, if it is not included, error processing is performed (S207).

On the other hand, if it exists, the channel 501 is detected from the remaining symbols and numbers, that is, AU3-6-2 (S217). Then, in step S219, a failure occurrence position of 01010302501 is finally detected through steps S203, S209, S213, and S217,

If it is determined in step S203 that the apparatus is not 'UMI' or 'RACK type', the process proceeds to step S221. If it is judged that it is a rack type with Yumi, it is judged whether there is a first two digit of the failure event (S223).

At this time, if it does not exist, error processing is performed (S225).

On the other hand, if it exists, the first two digits are detected as rack information (S227).

It is determined whether there is a next two digit (S229). If it does not exist, error processing is performed (S225). If it exists, it is detected as self-information (S231).

It is determined whether there is a next two digit (S233). If it does not exist, error processing is performed (S225). If so, slot information is detected (S235).

It is determined whether there is a next two digit (S237). If it does not exist, error processing is performed (S225). If it exists, it is detected as port information (S239).

Then, it is judged whether all the data exist or not, and if there is no data, error processing is performed (S225). If it exists, it is detected with the channel information (S243).

Then, the fault occurrence position of '04020110001' is finally detected through S227, S231, S235, S239 and S243, for example.

The mapping of the channel information in step S217 is as shown in FIG.

The channel number can be calculated through the signal multiplexing rule.

When AU3-6-2 is included in the failure event, the AUG absolute number 6 in Fig. 11 corresponds to STN2. Then, AU3-6-2 is finally detected as 222 sequentially arranged with STN4 = 2, AUG number = 2, AUG absolute number = 6, and AU3 number = 2, finally STN4, AUG number and AU3 number. The detected 222 is the channel number.

AU3-9-1 is finally detected as STN4, AUG number, and AU3 number 311 through STN4 = 3, AUG number = 1, AUG absolute number = 9, and AU3 number = The channel number 311 thus detected becomes the channel number.

AU3-12-3 is finally detected as STN4, AUG number, and AU3 number 343 through STN4 = 3, AUG number = 4, AUG absolute number = 12 and AU3 number = The channel number 343 thus detected becomes the channel number.

FIG. 14 is a block diagram showing the configuration of a controller according to an embodiment of the present invention, FIG. 15 is a flowchart showing a flow generating operation according to an embodiment of the present invention, FIG. 16 is a flow- FIG. 17 is a flowchart showing a flow changing operation according to the embodiment of the present invention.

First, referring to FIG. 14, the controller 200 includes a flow control unit 201 and a flow controller interlocking unit 203.

The flow control unit 201 performs creation, modification, and deletion of a flow through the interface with the network devices 300.

The flow control unit 201 transmits a flow connection command to at least one network device 300 that requires flow connection, deletion and change, and waits for a response indicating whether or not to execute the command is normally received. When the normal response is received, the flow identifier and the device identification information and location information of each of the at least one network equipment that requires flow connection, deletion, and change are transmitted to the flow control system 100 through the flow control interworking unit 203 .

The flow control interlocking unit 203 transmits the information requested by the flow control unit 201 to the flow control system 100 as means for interlocking with the flow control system 100. [ That is, it transmits the device identification information and the location information of the network equipment 300 connected to the generated, changed and deleted flow to the flow control system 100.

At this time, device identification information and location information for all network devices located at the end E2E are transmitted to one flow.

Referring to FIG. 15, the flow control unit 201 constructs a flow entry by the number N of all equipments related to the flow connection in the flow table (S301).

The flow control unit 201 counts the number of equipment that has completed the flow generation operation, and determines whether the count meets the total number of equipment N (S303).

If not, the flow control unit 201 transmits a flow connection command to the network equipment connected to the flow to be generated (S305). Then, it waits for a command execution response (S307).

At this time, it is judged whether a response to the command is normally received (S309), and if it is normally received, the flow returns to the step before step S303.

On the other hand, if it is not normally received, all the execution tasks are canceled so far (S311).

When the flow connection command transmission operation is completed for all the devices in step S303, the flow controller interworking unit 203 transmits the device identification information and the position information of at least one network device 300 connected to the flow to the flow control system 100 (S313).

Referring to FIG. 16, the flow control unit 201 forms a flow entry by the number N of all equipment related to flow deletion in the flow table (S401).

The flow control unit 201 counts the number of equipment that has completed the flow deletion operation, and determines whether the count satisfies the total number of equipment N (S403).

If not, the flow control unit 201 transmits a flow delete command to the network equipment connected to the flow to be deleted (S405). Then, it waits for a command execution response (S407).

At this time, it is determined whether a response to the command is normally received (S409), and if the response is received normally, the flow returns to the step before step S403.

On the other hand, if it is not normally received, all the execution tasks are canceled up to now (S411).

When the flow deletion command transmission operation is completed for all the devices in step S303, the flow controller interworking unit 203 transmits device identification information and location information of at least one network device 300 connected to the flow to the flow control system 100 (S413).

Referring to FIG. 17, the flow control unit 201 constructs a flow entry by the number N of all equipment related to the flow change in the flow table (S501).

The flow control unit 201 counts the number of equipment that has completed the flow change operation, and determines whether the count meets the total number of equipment N (S503).

If not, the flow control unit 201 transmits a flow change command to the network equipment connected to the flow to be changed (S505). Then, it waits for a command execution response (S507).

At this time, it is determined whether a response to the command is normally received (S509), and if it is normally received, the flow returns to the step before step S503.

On the other hand, if it is not normally received, all the execution tasks are canceled so far (S511).

When the flow change command transmission operation is completed for all the devices in step S503, the flow controller interworking unit 203 transmits device identification information and location information of at least one network device 300 connected to the flow to the flow control system 100 (S513).

As described above, the flow control system 100 can manage new flow configuration information through steps S313, S413, and S513.

Fig. 18 is a hardware block diagram according to the embodiment of the present invention, which shows hardware blocks of a flow control system and a controller, respectively.

Referring to Figure 18, each of the flow control system 100 and the controller 200 includes hardware (including a memory device 501, a storage device 503, a processor 505 and at least one communication device 507, etc.) 500), and stores a program that is executed in combination with hardware at a specified location. The hardware has a configuration and performance capable of executing the present invention. The program includes instructions implementing the method of operation of the invention described with reference to FIGS. 1 through 17, and in combination with hardware such as processor 505 and memory device 501 implement the present invention.

The embodiments of the present invention described above are not implemented only by the apparatus and method, but may be implemented through a program for realizing the function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

Claims (15)

A collection unit for collecting failure event messages generated in the network devices, and
And a flow control unit for analyzing the fault event message and detecting at least one flow in which a fault has occurred,
Gt; The method of claim 1,
The flow control unit,
And outputs a fault management screen displaying at least one flow in which the fault has occurred among the plurality of flows. 3. The method of claim 2,
The flow control unit,
When the fault occurred flow is clicked on the fault management screen,
In the fault detail screen,
And fault detail information generated in at least one network device connected to the clicked flow,
The fault detail information,
An alarm code, a network equipment name, a light message, an occurrence position, a failure type, and an alarm reception time acquired from the failure event message. The method of claim 1,
Further comprising a storage unit for storing flow configuration information mapped with device identification information and location information of each of at least one network equipment connected to the flow for each flow,
The flow control unit,
Wherein the controller is configured to detect the faulty network device and location information of the faulty network device by parsing the fault event message and to use at least one flow mapped to the faulted network equipment and location information using the flow configuration information, The flow control system determining the flow control system. 5. The method of claim 4,
The flow control unit,
Flow generation information, flow change information, and flow deletion information from a controller that controls the network devices to generate and update the flow configuration information,
Wherein the flow generation information, the flow change information,
A flow identifier, and device identification information and location information of the network equipment connected to the flow. 5. The method of claim 4,
The location information may include:
Wherein the information includes at least one of rack information, shelf information, slot information, port information, and channel information of a network equipment,
The flow control unit,
Extracting at least one of rack information, self information, slot information, port information, and channel information of a failed network device by parsing event information included in the failure event message, and transmitting at least one flow mapped to the extracted information From the flow configuration information. The method of claim 6,
The event information is in the form of a serial number in which letters and numbers are combined,
The flow control unit,
Self information, slot information, port information, and channel information corresponding to the respective rack numbers according to the manufacturer of the network equipment or the rack type or the self type, Information of at least one of the pieces of information is retrieved from the flow configuration information to detect a corresponding flow. As a controller for managing network devices,
A flow controller for creating, changing, and deleting a flow through an interface with the network devices; and
And a flow control unit operable to transmit, to the flow control system, device identification information and location information of network equipment connected to the created, changed, and deleted flows,
Wherein the device identification information and the location information of the network equipment,
Wherein the controller is used to manage faults of the network equipment in the flow control system on a flow-by-flow basis. 9. The method of claim 8,
Wherein the flow controller-
A controller that transmits device identification information and location information for all network devices located at endpoints for a flow. 9. The method of claim 8,
Wherein the flow control unit comprises:
When a flow connection command is transmitted to at least one network equipment requiring flow connection, deletion and change and a response indicating whether a command is executed is normally received, a flow identifier and at least one network equipment And transmits the device identification information and the position information of the device to the flow control system through the flow control interworking unit. CLAIMS What is claimed is: 1. A method for detecting a failure in a network equipment, the flow control system being connected to a controller for controlling network equipment,
Receiving a failure event message generated in the network devices, and
Analyzing the fault event message to detect at least one flow that has failed;
≪ / RTI > 12. The method of claim 11,
After the detecting step,
Outputting a fault management screen showing at least one flow in which the fault has occurred among a plurality of flows, and
Further comprising the step of switching to a failure detail screen upon clicking on a faulted flow on the fault management screen,
In the fault detail screen,
And fault detail information including fault occurrence time, alarm class, alarm code, network equipment name, light message, occurrence position, fault type and alarm reception time obtained from the fault event message. 12. The method of claim 11,
Before the receiving step,
Further comprising the step of generating flow configuration information to which device identification information and location information of each of at least one network equipment connected to the flow for each flow are mapped,
Wherein the detecting comprises:
Detecting the faulty network device and the location information of the faulty network device by parsing the fault event message, and
Determining at least one flow mapped to the network equipment and the location information of the fault using the flow configuration information as a faulted flow
≪ / RTI > The method of claim 13,
The location information may include:
Wherein the information includes at least one of rack information, shelf information, slot information, port information, and channel information of a network equipment,
The step of detecting the location information of the failed network equipment comprises:
Confirming event information in the form of a serial number in which characters and numbers are combined from the fault event message;
Detecting at least one first digit or letter of the serial number as rack information or self information of the network equipment by discriminating whether the manufacturer and equipment type of the network equipment in which the failure has occurred is a rack type or a self type,
The slot information, the port information, and the channel information sequentially from among the remaining serial numbers excluding the numbers or characters detected by the rack information or the self information
≪ / RTI > The method of claim 13,
Wherein the generating comprises:
Flow generation information, flow change information, and flow deletion information from a controller that controls the network devices to generate and update the flow configuration information,
Wherein the flow generation information, the flow change information,
A flow identifier, and device identification information and location information of the network equipment connected to the flow.

Images