KR101783097B1 - Method for recording/reading operation log information in router network based on software defined networking and apparatus thereof - Google Patents

Abstract

Disclosed is a method for recording and viewing operation log information in an SDN-based router network and an apparatus for performing the method. A method of recording operation log information in a router network includes: detecting a log event occurring as an operation is performed in a network device; And recording log information corresponding to the detected log event according to the log service component set in the network device. Accordingly, by defining various parameters in the log information recorded in the SDN-based routing system structure, the controller can provide a function of more effectively tracking the failure situation of the router.

Description

TECHNICAL FIELD The present invention relates to a method and apparatus for recording / viewing operation log information in an SDN-based router network.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to software defined networking (SDN), and more particularly, to a method and apparatus for recording and viewing operation log information in an SDN-based router network.

Software that can define and control the network centrally as if it is software programming by dividing communication system independently into forwarding plane and control plane for flexible operation and cost reduction of communication network. Research is underway on software defined networking (SDN) technology.

The Open Networking Foundation (ONF) defines the OpenFlow protocol for communication between centralized controllers and packet forwarding devices. Specifically, ONF defines the OpenFlow protocol to allow packet forwarding routing through centralized controller equipment to equipment with only L2 / L3 packet forwarding plane.

Recently, the Optical Transport Working Group (OTWG), a subordinate organization of the ONF, has also developed an OAM (Operation, Administration and Management) and packet transmission network and an optical transport network And defines a standard interface for controlling the forwarding plane of the transport network equipment through a separate control plane.

On the other hand, the Interface to Routing System (I2RS), which supports control using an external controller, is very interested in the routing system including the existing legacy routing equipment which does not separate the forwarding plane and the control plane from the SDN technology for the routing system have.

I2RS technology is currently being standardized by the IETF, and frameworks and interfaces are being defined to enable communication between external controllers and existing or new router equipment.

In the SDN-based routing system, the controller can issue various operation execution commands to the router, and the router can transmit information to the controller in real time as a result of performing the corresponding operation. In addition, the router can transmit to the controller whenever the result information of an operation performed within the router is generated.

However, when the amount of operation execution commands transmitted from the controller is increased, or when an operation execution command is transmitted from the plurality of controllers to the router at the same time, there is a loss of operation information due to a race condition of operation and a performance deterioration thereof Thereby causing problems such as malfunction or interruption in services running inside the router.

In addition, the SDN-based routing system permits control of routers such as the existing CLI (Command Line Interface) and SNMP (Simple Network Management Protocol). Therefore, when an operator performs an operation through connection of a CLI and an SNMP-based router rather than a structure of a controller based on the SDN, the operation affects an operation set based on the SDN-based controller, Or a problem such as interruption may occur.

This problem is not a problem occurring in the structure of the SDN based routing system, but it is a problem that can be occurred in operation. The operator should be able to analyze the cause of the problem and solve the problem.

However, the SDN-based routing system technology defined so far does not consider a technique for tracking the cause of the problem during such operation.

In order to solve the above problems, an object of the present invention is to provide a method of recording operation log information in an SDN-based router network.

It is another object of the present invention to provide a method for browsing operation log information in an SDN-based router network.

It is another object of the present invention to provide a method for processing operation log information in an SDN-based router network.

According to another aspect of the present invention, there is provided a method of recording operation log information in a router network, the method comprising: receiving a log event generated when an operation is performed in a network device, Detecting; And recording log information corresponding to the detected log event according to the log service component set in the network device.

Here, the log service component set in the network device may include service name and version information of the log service component, a controller list using the log service component, and information about sub-parameters set for each controller belonging to the controller list.

Here, the subparameter includes at least one of a controller's identification information, a log file name, a log file size, a log file number, a log level indicating a storage criterion of log information, a policy when a log file storage space is insufficient, And information on the presence / absence of notification to the controller to which it belongs.

Here, the log information corresponding to the detected log event may include log identification information, a log event occurrence time, a log event occurrence entity identification information, and operation information.

Here, the operation information may include at least one of operation name information, operation parameter information, operation group code information, and operation result code information.

Here, the log information corresponding to the detected log event may further include at least one of network application identification information and log related service name information.

According to another aspect of the present invention, there is provided a method for browsing operation log information in a router network, the method comprising: Generating a log browse message including the log browse message; Transmitting a log browsing message to a network device for browsing log information corresponding to the information to be browsed; And receiving log information corresponding to the browsing object information from the network device.

Here, the browsing object information can be specified by the log event generating entity or log related service name information.

Here, the browsing object information may be specified by one of log identification information, log event occurrence time, and operation information.

Here, the network device records log information according to a log service component set by the controller, and the log service component includes a service name and version information of the log service component, a controller list using the log service component, And may include information on sub-parameters that are individually set.

According to another aspect of the present invention, there is provided a method of processing operation log information in a router network, the method comprising: Setting a component; Detecting a log event that occurs as a network device performs an operation on a network device; And the network device processing the log information corresponding to the detected log event according to the log service component.

Here, the log service component may include service name and version information of the log service component, a controller list using the log service component, and information about sub-parameters set for each controller belonging to the controller list.

Herein, the step of processing log information corresponding to the detected log event may record log information including log identification information, log event occurrence time, identification information of a log event occurrence entity, and operation information.

Here, the operation information may include at least one of operation name information, operation parameter information, operation group code information, and operation result code information.

Here, the step of processing log information corresponding to the detected log event may record log information further including at least one of network application identification information and log related service name information.

Here, the processing of the log information corresponding to the detected log event may transmit log information corresponding to the log event detected according to the log service component to the controller.

The method of recording and browsing the operation log information in the SDN-based router network according to the present invention defines various parameters in the log information recorded in the SDN-based routing system structure so that the controller can more effectively It is possible to provide a function of tracking.

In addition, the log service can be defined as a component type, and the log configuration can be separately recorded in a multi-controller environment through parameter configuration for a multi-controller environment, thereby diversifying the log policy for each controller.

1 is a block diagram illustrating a structure of an SDN-based routing system according to an embodiment of the present invention.
2 is a conceptual diagram illustrating a log service component set in a network device according to an embodiment of the present invention.
3 is an exemplary diagram illustrating a log service component set in a network device according to an embodiment of the present invention.
4 is a conceptual diagram illustrating a structure of log information stored in a log database of a network device according to an embodiment of the present invention.
5 is an exemplary diagram illustrating log information stored in a log database of a network device according to an embodiment of the present invention.
6 is a flowchart for explaining a method of browsing operation log information through a controller according to an embodiment of the present invention.
7 is a flowchart for explaining a method of browsing operation log information through a controller according to another embodiment of the present invention.
8 is a flowchart for explaining a method of browsing operation log information through a controller according to another embodiment of the present invention.
9 is a flowchart for explaining operation group-based log information processing according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terms first, second, A, B, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

Hereinafter, the controller referred to in the present invention refers to an integrated SDN controller, which is a functional entity that controls related components (e.g., switches, routers, etc.) .

Further, the controller is not limited by the physical implementation form or the location of the implementation. For example, the controller means a controller functional entity defined by ONF (OpenFlow), IETF (Internet Engineering Task Force), ETSI (International Telecommunication Standards Institute) and / or ITU-T (International Telecommunication Union Telecommunication) can do.

The network device referred to in the present invention may refer to a functional element that substantially forwards, switches, or routes traffic (or packets), such as a 'switch' or a 'router. Thus, in the present invention, the network device may be referred to as a switch or a router.

For example, a network device means a switch, a router, a switching element, a routing element, and a forwarding element defined in ONF, IETF, ETSI and / or ITU-T .

Hereinafter, parameters and / or message types defined in an operation procedure for recording / browsing operation log information in an SDN-based router network according to an embodiment of the present invention are not limited to the specific messages described below.

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

1 is a block diagram illustrating a structure of an SDN-based routing system according to an embodiment of the present invention.

Referring to FIG. 1, a routing system according to an embodiment of the present invention may be configured such that a plurality of controllers 110 and 120 control a plurality of routers 210 and 210, The agents 211 and 221 existing on the control plane and the clients 111 and 121 of the controllers 110 and 120 communicate with each other through an interface to routing system (I2RS), which is a standardized routing system interface .

The controllers 110 and 120 may have clients 111 and 121 as service modules for controlling the routers 210 and 220. However, in the present invention, the clients 111 and 121 may have the same concept as the controllers 110 and 120.

The routers 210 and 220 may be divided into a control plane and a data plane according to functions. The routers 210 and 220 have modular agents 211 and 221 for receiving and performing operations transmitted from the controllers 110 and 120, respectively. Here, the Agents 211 and 221 may exist on the control planes of the routers 210 and 220. In addition, the forwarding information base modules 217 and 227 may reside on the data planes of the routers 210 and 210.

The agents 211 and 221 of the routers 210 and 220 are service functional blocks for controlling recording and viewing of log information and include a log service block 213 and 223 and a database 215 , 225). Although the Log service blocks 213 and 223 and the databases 215 and 225 are shown as being included in the Agents 211 and 221 but may be a module or medium separate from the Agents 211 and 221, , 220).

The log service blocks 213 and 223 allow operations to be performed internally in the routers 210 and 220 and log information on the operation execution results transmitted to the clients 111 and 121 of the controllers 110 and 120 through the DB 215 , And 225, respectively. The log service blocks 213 and 223 may transmit log information to the controllers 110 and 120 at the request of the clients 111 and 121. [

More specifically, it is necessary to define a component model in which routers 210 and 220 support a function of recording or browsing log information generated according to an operation.

In the present invention, a component model supporting a function of recording or browsing log information can be set or defined as a log service component. In other words, the log service component may refer to a concept equivalent to the component model.

Accordingly, it is necessary to set the log service component in the Log service blocks 213 and 223 of the routers 210 and 220, and various parameters for specifying (modeling) the log service component will be described later with reference to FIG.

2 is a conceptual diagram illustrating a log service component set in a network device according to an embodiment of the present invention.

Referring to FIG. 2, a log service component set in a network device according to an embodiment of the present invention may be defined by various parameters. That is, the log service component shown in FIG. 2 may be defined by various parameters, and may have a concept of a policy that defines processing for log information.

The meanings of the parameters and the notation format of Fig. 2 are shown in Table 1. In detail, Table 1 shows parameter information of the log service component.

parameter Notation type Parameter Item Description Service Name String (string) Service name information of log service component Component Version Integer (integer value) Log service component version information Client List Array (array) Client list using log service component Client ID String (string) About Client ID Log File Name String (string) Log file name Log File Size Integer (integer value) Log file size Log File Number Integer (integer value) Number of log files Log Level Integer (integer value) Log level information
Level "1" - critical error (system error information)
Level "2" - operational error & warning
Level "3" - debugging (debugging information) Log File Saturation Policy Integer ( Integer value ) Policy when the log file storage space is insufficient
Policy "1" - rewrite (overwrite existing file)
Policy " 2 " - transmit log file
           (Pass all log information to Client)
Policy "3" - stop & notification
           (Stop log generation and notify Client) Publish-Subscriber Support Boolean Whether or not the client using the log service component is notified when a log event occurs

The parameters of the log service component will be described with reference to Table 1 below.

The Service Name and Component Version information means the service name and version information of the log service component, and the Client List can refer to a controller list or a client list using the log service component.

In addition, subparameters set for each controller belonging to the controller list can be defined. The subparameters include a log file name, a log file size, a log file number, and a log level indicating a storage criterion of log information (client ID information), a log file name Log Level), a log file storage policy (Log File Saturation Policy), and information on the presence or absence of a notification (Publish-Subscriber Support) in a controller belonging to the controller list when a log event occurs.

For example, in the case of a log level among the subparameters, three levels can be set. (Log Level: 3), which stores all the log information generated, and operational warning & error log level (Log Level: 2), which stores the log only when warning and error information occur when the operation is performed. There can be a critical error log level (Log Level: 1) that stores the log only when a system problem occurs.

On the other hand, a large integer value of the log level operates with a log level of an integer value smaller than itself. For example, when the Log Level is set to 2, the log information including the critical error log information having the Log Level of 1 can be stored.

The Log File Saturation Policy parameter refers to a policy used when the log file space is insufficient to store log information. Depending on the setting value, the oldest log file of the existing file is overwritten with the log information, or the oldest log file After deleting the contents, log information can be saved. In addition, it is also possible to store log information continuously after delivering log information to a client, or to notify a client of insufficient log storage space without storing log information.

The Publish-Subscriber Support parameter is a function that notifies the client using the log service whenever a log event occurs, and can notify that a log event has occurred based on the Client ID information of the Client List.

If you refer to the parameters of the log service component, it is possible to configure the processing of the log information file for each client. However, when processing the log information file in common, it is possible that a plurality of clients share one log file have. For example, when a plurality of clients are set for load distribution of operations by a controller, log information needs to be stored through one log file.

Meanwhile, the log service component shown in FIG. 2 can be configured as a common component that can be commonly used by a plurality of controllers and a sub-component that is a controller-specific component that can be used adaptively to each controller. In this case, parameters commonly used in the log information file between the controllers, such as Service name, Component version, and Client list, may be defined in the common component.

In addition, parameter information common to all controllers connected to the same router, as well as parameter information common to only some controllers, may be configured as common components. For example, between controllers with a Log File Saturation Policy of 3 (stop & notification), the common parameters may be defined as common components between some subset controllers.

Only the Log File Saturation Policy has been exemplarily described, but it goes without saying that various modifications are possible. Such a common component may be generated by a router that has received a policy from a plurality of controllers, and a plurality of controllers connected to the same router may cause the router to generate a common component based on the agreement.

On the other hand, a controller-specific component can be defined by various parameters such as a client ID, which are set adaptively for each controller or client. Thus, the log service component can be configured to provide a log service by combining or mapping common components and component by controller.

3 is an exemplary diagram illustrating a log service component set in a network device according to an embodiment of the present invention.

Figure 3 shows an embodiment using the log service component defined in Figure 2 and Table 1; Referring to FIG. 3, the controller A 110 and the controller B 120 show the details of the parameter setting of the log service component with respect to the router A 210.

Assuming that the controller A 110 is matched with the client 1 of the log service component, it is known that five log files of 512k size are set to log level 2. Publish-subscriber support is true, You can tell that you need to notify the client every time. In addition, if there is insufficient space in the five log files, you can see that the existing log files use a policy to overwrite them.

Next, when it is assumed that the controller B 120 is matched with the client 2 of the log service component, it is found that two log files of the size of 256 k are set to the log level 3, and since the publish-subscriber support is false, Is set and the client is not notified. In addition, if the space of two log files is insufficient, it is not notified to the client without recording.

Therefore, by referring to the definition of the log service component as described above, it is possible to record log information for each controller in a multi-controller environment by setting parameters for each controller for setting the log service component, Lt; / RTI > It is also possible to dynamically set log policies as needed.

Meanwhile, when a log event is generated through the log service component of FIG. 2, the structure of log information actually stored in the database will be described with reference to FIG. 4 and Table 2.

4 is a conceptual diagram illustrating a structure of log information stored in a log database of a network device according to an embodiment of the present invention.

4, the log information stored in the log database of the network device according to an exemplary embodiment of the present invention includes log identification information (Log ID), a log event occurrence time (Timestamp), an Origin ID Operation information, network application ID, and log-related service name (Service Name). Here, the operation information may include operation name information, operation parameter information, operation group code information, and operation result code information.

Table 2 shows parameter information of the log information.

parameter Notation type Parameter Item Description Log ID String (string) Log ID information Timestamp String (string) Log event occurrence time Origin ID String (string) ID information of the log event generation subject Network Application ID String (string) network application  ID information Service Name String (string) Log-related services Name  Information Operation Information Operation Information Operation Name String (string) operation Name  Information Operation Parameters Integer ( Integer value ) Operation parameter information Operation Group Code Integer ( Integer value ) Operation group code information Operation Result Code Integer ( Integer value ) Operation result code information

The parameter information of the log information will be described with reference to Table 2 below.

The Log ID parameter indicates the ID information of the log. If a log event occurs, the router can set it to its own unique value.

The Timestamp parameter indicates the time at which the log event occurred, and time zone information, date information, and time information up to ms units may be displayed based on the time information set by the router system.

Origin ID information is the ID information of the log event generating entity. When the log is generated by the operation performed from the client, the corresponding Client ID information is set. If the log is generated by the self-performed operation in the router, Value is set.

The Network Application ID parameter refers to the ID information of the Network Application that exists in the upper part of the Client in the case of operation transmitted from the Client. If log information is generated from the operation performed in the router itself, the Network Application ID information may not be set have.

Service Name Parameter information indicates the name of the service component that generated the log event in the Agent.

Operation Information indicates information about various operations defined by the corresponding service component.

The sub-parameter information of the Operation Information includes an Operation Name indicating an operation name, Operation Parameters indicating an operation parameter value, an Operation Group Code indicating a grouped operation code, and an Operation Result Code indicating a result value of the operation. Here, the operation result code information may mean the operation result value of the service model.

More specifically, the Operation Group Code information allows the log information to be browsed based on a representative code grouped in the client as a parameter item required when an operation transmitted from an actual client is transferred as a grouped operation rather than as a single operation .

Also, as described with reference to FIG. 2, since a plurality of clients can commonly set processing for a log information file and share one log file, the Operation Group Code is a group operation indicating a grouped operation from a plurality of clients It is a matter of course that it can be given by code.

5 is an exemplary diagram illustrating log information stored in a log database of a network device according to an embodiment of the present invention.

FIG. 5 shows an embodiment of the log information storage described in FIG. 4 and Table 2. FIG.

5, a controller (ID information - KT.Controller.OperatorA) 110 has a Network Application (ID information - KT.Controller) for controlling a router network, Protocol has been requested to perform operation for setting Hello Timer Interval and Hold Time information. The controller 110 may interwork with the network appilcation 300 through a northbound interface.

The Agent 211 of the router A 210 processes the two OSPF related commands transmitted from the controller 110 through the database 215 based on the log service component and then transmits the OSPF related commands to the log Information can be stored.

Log ID information is automatically generated from the Agent 211 of the router A 210 and the time information of the log event is automatically stored in the timestamp item based on the time information of the router.

The Origin ID information is stored as KT.Controller.OperatorA, which is the Client ID address of the controller A 110, and the Network Application ID information of the controller A 110 is additionally stored.

The service name information stores the service model name of the OSPF model, which is a service model for OSPF routing protocol, and the operation information stores information about Hello Interval and parameter information about Hold Time for each log.

In addition, the operation group code information is stored as OSPF_Timer_Control information indicating that two separate operations are associated with the OSPF timer related control. The group information is generated and transmitted from the controller A 110 requesting the operation, It can be automatically classified based on the operation system of the OSPF service model and generated.

If you refer to the log information, you can see from the controller that the Hello Interval operation is set to 30 seconds, and return code 0 tells you that the operation was performed correctly.

On the other hand, the hold time is set to 90 seconds, but the result is 10, indicating that the return code is not a valid value. Accordingly, the client that has performed the operation request can know in real time that the operation for the OSPF timer control has not been successfully performed, through the operation result code transmitted from the agent 211. In addition, it is possible to perform more accurate cause analysis based on the log information recording, and when an operation failure occurs in a service interruption or an arbitrary service due to a cause other than the request of the client, operation group code information, service model information, By viewing the log information based on the Origin ID information and the like, it is possible to easily analyze the cause of the trouble from the viewpoint of the operator.

Therefore, according to the method for recording log information by the network device according to the embodiment of the present invention, the network device can detect a log event that occurs according to the operation performed in the network device, The log information corresponding to the detected log event can be recorded.

FIG. 6 is a flowchart illustrating a method for browsing operation log information through a controller according to an embodiment of the present invention. FIG. 7 illustrates a method for browsing operation log information through a controller according to another embodiment of the present invention And FIG. 8 is a flowchart for explaining a method of browsing operation log information through a controller according to another embodiment of the present invention.

Referring to FIG. 6, an example in which a controller reads log information about an operation requested from a controller based on an Origin ID is shown.

First, the client inside the controller can access the Agent and input the ID information of the controller itself to the Origin ID of the log information structure to request the log information transfer (S610).

The agent of the router can request the log information from the database based on the Client ID information inputted to the Log service block in the Origin ID (S620, S630). The agent of the router can receive the log file data corresponding to the Client ID information input to the Origin ID from the date base through the Log service block (S640, S650). Accordingly, the agent of the router can forward the log file data received from the Log service block to the client of the controller (S660).

If the database is managed for each client rather than sharing the database for multiple clients, the Agent can transmit the log information file managed by the client to the corresponding client as it is.

Referring to FIG. 7, an example of browsing log information about operations performed in a router controlled by a controller based on Origin ID is shown.

As in the embodiment of FIG. 6, the client inside the controller can request the log information from the Agent by inputting the Agent ID in the Origin ID information (S710).

The agent of the router can request the log information from the database based on the Agent ID information input in the Origin ID to the Log service block (S720, S730). The agent of the router can receive the log file data corresponding to the Agent ID information input to the Origin ID from the date base through the Log service block (S740, S750). Accordingly, the agent of the router can forward the log file data received from the Log service block to the client of the controller (S760).

Referring to FIG. 8, an example of browsing log information of an operation performed based on a service name is shown.

The agent of the router can request log information from the database based on the OSPF inputted in the service name to the log service block (S820, S830). The agent of the router can receive the log file data corresponding to the OSPF inputted in the service name from the data base through the log service block (S840, S850). Accordingly, the agent of the router can forward the log file data received from the Log service block to the client of the controller (S860).

There are various service components in the SDN-based routing system, and there is a service component that is a source of log generation because a logging event is generated according to an operation performed according to a service component.

That is, the client can request the agent to specify specific service component information when browsing the log information, and the agent can respond only to the log information generated by the execution of the corresponding service component.

Therefore, according to the method for the controller according to the embodiment of the present invention to browse the log information, the controller can generate the log browse message including the browse target information specifying the log information to be browsed, The log browsing message can be transmitted to the network device for browsing the corresponding log information, and the log information corresponding to the browsing object information can be received from the network device.

Here, the browsing object information can be specified by identification information of a log event generating entity, log related service name information, log identification information, log event occurrence time, operation information, and the like.

9 is a flowchart for explaining operation group-based log information processing according to an embodiment of the present invention.

9 shows an example in which an operation is performed based on a specific operation group in an SDN-based routing system.

Operations applied to the routing system can be performed based on a plurality of operations rather than a single operation, and the controller of the SDN-based routing system can transmit the plurality of operations to the router.

Accordingly, a plurality of operations are delivered to the router in the form of a grouped message, and the log information can also be stored through an operation group code that can represent these operations.

Referring to FIG. 9, a plurality of operations can be transmitted from a client to an agent, and log information can be generated based on a group code grouped according to an operation result.

For example, the client requests the router to set the OSPF timer, and can set the hello timer and the holdoff timer to be set at that time as a group code "Add OSPF Timer", which is a grouping, and request the router's agent (S910) . Here, the group code can be assigned to a code representing a plurality of operation actions when requesting from the client to the agent, and the client can manage the group code information for the requested operation group. Accordingly, the controller can request the agent to browse the log information based on the group code information corresponding to the log information in the future, and only the necessary log information can be received from the agent.

The Agent may request the OSPF service component to set the requested OSPF timer (S920). The OSPF service component sets a timer according to the request of the agent and responds the result to the agent (S930, S940). Accordingly, the Agent can reply the result of the OSPF timer setting to the client (S950).

In step S960, the agent can request the log service block based on the result of the OSPF timer setting in step S960, and the log service block can store the generated log information in the database in step S970. Therefore, the agent can receive the response of the storage result of the log information through the log service block.

Thus, according to a method of processing log information in a software-defined networking environment, the controller can configure a log service component on the network device, and the network device can detect a log event that occurs as an operation is performed on the network device, The network device can process the log information corresponding to the log event detected according to the log service component.

More specifically, the network device may record log information including log identification information, log event occurrence time, log event occurrence entity identification information, operation information, network application identification information, and log related service name information.

Also, the network device may transmit log information corresponding to the detected log event to the controller according to the log service component.

The method of recording and viewing the operation log information in the SDN-based router network according to the embodiment of the present invention defines various parameters in the log information recorded in the SDN-based routing system structure, It is possible to provide a function of tracking more effectively.

In addition, the log service can be defined as a component type, and the log configuration can be separately recorded in a multi-controller environment through parameter configuration for a multi-controller environment, thereby diversifying the log policy for each controller.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the present invention as defined by the following claims It can be understood that

110: Controller A 120: Controller B
111, 121: Client
210: Router A 220: Router B
211, 221: Agent 213, 223: Log service block
215, 225: Database (DB)
217, 227: Forwarding information base module
300: Network Application

Claims (16)

A method for a network device to record log information,
Detecting a log event occurring as an operation is performed in the network device; And
And recording log information corresponding to the detected log event according to a log service component set in the network device,
Wherein the log service component set in the network device includes a service name and version information of the log service component, a controller list using the log service component, and information about sub-parameters set for each of at least two controllers belonging to the controller list,
The subparameter includes at least one of a controller identification information, a log file name, a log file size, a log file number, a log level indicating a storage criterion of log information, a policy when a log file storage space is insufficient, And information on the presence or absence of the notification.
A method for recording operation log information in a router network. delete delete The method according to claim 1,
The log information corresponding to the detected log event is,
A log event occurrence time, a log event occurrence subject identification information, and operation information,
A method for recording operation log information in a router network. The method of claim 4,
The operation information includes:
Wherein the operation information includes at least one of operation name information, operation parameter information, operation group code information,
A method for recording operation log information in a router network. The method of claim 4,
The log information corresponding to the detected log event is,
Further comprising at least one of network application identification information and log related service name information.
A method for recording operation log information in a router network. In a method for the controller to view log information,
Generating a log browse message including browse target information specifying log information to be browsed;
Transmitting the log viewing message to a network device for browsing log information corresponding to the information to be browsed; And
And receiving log information corresponding to the browsing object information from the network device,
Wherein the network device records log information according to a log service component set by a controller, the log service component including a service name and version information of the log service component, a controller list using the log service component, Information about sub-parameters set for each of two or more controllers,
The subparameter includes at least one of a controller identification information, a log file name, a log file size, a log file number, a log level indicating a storage criterion of log information, a policy when a log file storage space is insufficient, And information on the presence or absence of the notification.
A method for browsing operation log information in a router network. The method of claim 7,
The reading target information includes:
And the log-related service name information, which is specified by the log-
A method for browsing operation log information in a router network. The method of claim 7,
The reading target information includes:
Which is specified by one of log identification information, log event occurrence time, and operation information,
A method for browsing operation log information in a router network. delete A method for processing log information in a software defined networking environment,
Setting a log service component in which a network device is controlled from a controller;
Detecting a log event occurring as the network device performs an operation in the network device; And
The network device processing log information corresponding to the detected log event according to the log service component,
Wherein the log service component includes information on a service name and version information of the log service component, a controller list using the log service component, and information on sub-parameters set for each of at least two controllers belonging to the controller list,
The subparameter includes at least one of a controller identification information, a log file name, a log file size, a log file number, a log level indicating a storage criterion of log information, a policy when a log file storage space is insufficient, And information on the presence or absence of the notification.
A method for processing operation log information in a router network. delete The method of claim 11,
Wherein the processing of the log information corresponding to the detected log event comprises:
Log information including the log identification information, the log event occurrence time, the log event occurrence subject identification information, and the operation information,
A method for processing operation log information in a router network. 14. The method of claim 13,
The operation information includes:
Wherein the operation information includes at least one of operation name information, operation parameter information, operation group code information,
A method for processing operation log information in a router network. 14. The method of claim 13,
Wherein the processing of the log information corresponding to the detected log event comprises:
The network application identification information, and the log related service name information.
A method for processing operation log information in a router network. The method of claim 11,
Wherein the processing of the log information corresponding to the detected log event comprises:
And transmits log information corresponding to the detected log event to the controller according to the log service component.
A method for processing operation log information in a router network.

Images