KR101578622B1 - Method of failover for routing system - Google Patents

Abstract

A method for handling faults occurring in a routing system is disclosed. A method for handling a failure of a routing system includes the steps of: a router collecting information about at least one controller; Identifying an active client module among a plurality of client modules located on at least one controller based on information on the at least one controller; Determining a failure occurring in the routing system based on the information about the active client module identified by the router and processing the failure according to the object of the failure occurring in the routing system. Therefore, the redundant structure of the controller and the failure recovery procedure based on this structure are provided, so that the routing system can be stably controlled even in case of failure.

Description

[0001] METHOD OF FAILOVER FOR ROUTING SYSTEM [0002]

The present invention relates to software defined networking, and more particularly, to a method for handling faults occurring in a routing system.

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.

Specifically, the Open Networking Foundation (ONF) defines the OpenFlow protocol for communication between centralized controllers and L2 / L3 packet forwarding equipment.

In addition, OTWG (Optical Transport Working Group), which is a subordinate organization of ONF, has recently developed an OAM and a packet transmission network and an optical transport network in which a protection switching function is defined, It defines a standard interface for controlling the forwarding plane of equipment.

On the other hand, a routing system interface (Interface to Routing System) technology that supports control using an external controller for a routing system including legacy routing apparatuses in which the forwarding plane and the control plane are not separated is of great interest as the SDN technology for the routing system .

The interface to routing system technology is currently being standardized by the IETF, and frameworks and interfaces are being defined for communication between external controllers and existing or new router equipment.

The external controller that controls the routing system is a network device that plays an important role in delivering various control information related to router operation and status information of routers in real time.

However, there is a need for a specific countermeasure based on a logical / physical failure such as a controller and a control line connected to the controller, or a structure for storing transaction information on all operations performed between a client on a controller and an agent on a router It is not defined.

Therefore, introducing a controller that controls the routing system may cause serious problems in terms of stability in network operation.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method for handling a fault in a routing system.

According to an aspect of the present invention, there is provided a method of handling a fault in a routing system, the method comprising: collecting information on at least one controller; Identifying an active client module among a plurality of client modules located on at least one controller based on information on the at least one controller; Determining a failure occurring in the routing system based on the information about the active client module identified by the router and processing the failure according to the object of the failure occurring in the routing system.

Here, the routing system can configure a routing system interface by communicating with a plurality of client modules on at least one controller, the agent module located on the control plane of the router.

Wherein collecting information about the at least one controller includes broadcasting the client search request message by the router; And may receive a client search response message from at least one controller in response to the client search request message.

Here, the client search request message includes version information of a routing system interface for a router, RIB data model information for controlling information of a routing information base (RIB) on the router, system for controlling log information generated on a router log data model information, and policy data model information for setting a policy in the router.

Here, the client search response message includes version information of a routing system interface for each of a plurality of client modules, client ID information, secondary ID information for identifying a network application accommodated in each of a plurality of client modules, The number of allowed sessions for connection and the port information for session connection.

Wherein identifying the active client module may identify an active client module selected from a plurality of client modules at random or based on a predetermined policy.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may determine the failure occurring in the routing system through the Hello message exchange.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include a step of, when it is determined that the active client module and the standby client module included in the controller for controlling the router have failed, A session request message may be transmitted to the standby client module included in the controller for controlling the failure.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include the step of, when it is determined that a failure occurs in the controller for controlling the router, A failure can be handled by sending a request message.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include the step of transmitting the information on the failed interface and the cause of the failure to the active client to process the failure can do.

According to another aspect of the present invention, there is provided a method of handling a fault in a routing system, the method comprising: determining a fault occurring in the routing system; And processing the fault according to the object of the fault occurring in the routing system, wherein the routing system comprises an active client, a plurality of client modules, active and standby on the at least one controller, The module controls the router.

Here, the routing system can configure a routing system interface by communicating with a plurality of client modules on at least one controller, the agent module located on the control plane of the router.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include the steps of: detecting Client ID information for identifying an active client module that has been connected to the network; The failure can be handled using the session request message including the ID information and the information indicating the reconnection according to the failure.

Here, the method may include generating a client consistency table based on the session request message by the client module that receives the session request message and processes the failure, and manages the client consistency table.

Here, the step of determining a failure occurring in the routing system may be performed through a Hello message exchange.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include a step of, when it is determined that the active client module and the standby client module included in the controller for controlling the router have failed, A session request message may be transmitted to the standby client module included in the controller for controlling the failure.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include the step of, when it is determined that a failure occurs in the controller for controlling the router, A failure can be handled by sending a request message.

Here, the step of processing the failure according to the object of the failure occurring in the routing system may include the step of transmitting the information on the failed interface and the cause of the failure to the active client to process the failure can do.

The method for handling a failure of the routing system according to the present invention can provide a redundant structure of the controller and a failure recovery procedure based on the structure to stably control the routing system even in the event of a failure.

In addition, the method for handling a fault in the routing system according to the present invention can perform a consistent operation between the failed controller and the controller performing the recovery.

1 is an exemplary diagram illustrating a routing system controlled by a controller according to an embodiment of the present invention.
2 is an exemplary diagram illustrating a routing system including a duplicated network application according to an embodiment of the present invention.
3 is an exemplary diagram illustrating a routing system including a redundant controller according to an embodiment of the present invention.
4 is an exemplary diagram illustrating a routing system including a redundant controller according to another embodiment of the present invention.
5 is an exemplary diagram illustrating information collection for at least one controller in accordance with an embodiment of the present invention.
FIG. 6 is an exemplary diagram for explaining generation of a client list and selection of an active client module according to an embodiment of the present invention. FIG.
FIG. 7 is an exemplary diagram for explaining an error process when a physical link failure of a router occurs according to an embodiment of the present invention. FIG.
FIG. 8 is an exemplary diagram for explaining an error process when a failure occurs in an active client module according to an embodiment of the present invention. FIG.
9 is an exemplary diagram for explaining an error process when a controller fails in accordance with an embodiment of the present invention.
10 is an exemplary diagram for explaining generation and management of a client consistency table 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, a 'controller' referred to in the present invention refers to a functional entity that controls related components (eg, switches, routers, etc.) to control the flow of traffic. Shape, implementation position, and the like. For example, a controller may refer to a controller functional entity defined in ONF, IETF, ETSI, and / or ITU-T.

The term 'router' or 'network equipment' referred to in the present invention means a functional element for substantially forwarding, switching or routing traffic (or packet). It is defined in ONF, IETF, ETSI and / or ITU-T A router, a switch element, a router element, a forwarding element, and so on.

It should be noted that the embodiments of the present invention described below can be applied to IEEE, ITU-T, and the like that perform standardization on standard documents and / or transmission networks created in ONF, IETF, ETSI, ITU- T, and IETFs. That is, those of the embodiments of the present invention that are not specifically described in order to clearly illustrate the technical idea of the present invention can be supported by the standard documents prepared by the above standardization bodies. In addition, all terms used in the present invention can be described by the standard document.

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

1 is an exemplary diagram illustrating a routing system controlled by a controller 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 controller 100 controls a plurality of routers 210 and 220.

Specifically, the router A 210 and the router B 220 can be controlled by the controller 100 physically separated from each other.

First, the routers 210 and 220 may be divided into a control plane and a data plane according to functions.

The topology DBs 216 and 226, and the policy DBs 215 and 225, which are connected to the network, May reside on the control plane of the routers 210, 220.

In addition, the forwarding information base modules 217 and 227 may reside on the data planes of the routers 210 and 210. Accordingly, the information updated by the routing protocol may be transmitted to the forwarding information base modules 217 and 227 of the data plane via the routing information base modules 214 and 224.

Meanwhile, the controller 100 can accommodate various network applications 300 through the Northbound API provided by the controller 100. [

The Agent modules 211 and 221 existing on the control planes of the routers 210 and 220 and the Client module 101 of the controller 100 communicate with each other through a standardized routing system interface (I2RS) Can be performed.

The client module 101 converts the routing control information received from the network application 300 into a form capable of being parsed by the Agent modules 211 and 221 and transmits the converted routing control information to the Agent modules 211 and 221.

Agent modules 211 and 221 parses the received routing control information and transmits the topology DBs 216 and 226, the policy DBs 215 and 225 and the Routing Information Base (RIB) module 214, and 224, the signaling protocol modules 212 and 222, and the routing protocol modules 213 and 223.

The routers 210 and 220 may perform a monitoring function of transmitting various event information of routers set by the operator to the client module 101 through the Agent modules 211 and 221.

On the other hand, the controller 100 can have Client ID information that can represent itself. The client ID is a character string or an integer value representing the uniqueness of the controller 100 or the client module 101 and is used for authentication and control processes for operations performed between the routers 210 and 220 and the controller 100 .

For example, when the controller 100 having the client ID 1000 performs an operation for adding the routing information of the prefix 220.210.100.x / 24 to the router A 210, ID 1000 and the information related to the addition of the corresponding prefix, and transmits this information to the Agent module 211 of the router A 210.

The Agent module 211 of the router A 210 checks whether the currently received transaction information matches the Client ID information in connection with itself, and then performs the corresponding operation. Otherwise, the Agent module 211 of the router A 210 notifies the corresponding Client module 101 of the error information And so on.

2 is an exemplary diagram illustrating a routing system including a duplicated network application according to an embodiment of the present invention.

2, a secondary ID is defined for the network applications 300 and 300-1 accessing the client module 101 of the controller 100 and the network applications 300 and 300-1 are activated or standby active or standby) Network Application (300, 300-1).

When a failure occurs in an active network application 300 or a standby network application 300-1, it is necessary to define what procedure to perform failover.

FIG. 3 is an exemplary diagram illustrating a routing system including a redundant controller according to an embodiment of the present invention. FIG. 4 is a block diagram illustrating a routing system including a redundant controller according to another embodiment of the present invention. Fig.

3 and 4, the case where the controllers 110 and 120 include the duplicated client modules 111, 111-1, 121 and 121-1 will be described.

For example, controller A 110 may include active and standby client modules 111 and 111-1, and controller B 120 may include active and standby and client modules 121 and 121-1 that are duplicated in a standby state.

Also, considering that the controller itself may fail, the control itself can be physically duplicated like the controller A 110 and the controller B 120.

FIG. 3 illustrates a structure in which a network application 300 controlling routers 210 and 220 is physically separated from controllers 110 and 120. FIG. 4 illustrates a structure in which network applications 310 and 320 are connected to controllers 110 and 120 ). ≪ / RTI > The client modules 111, 111-1, 121 and 121-1 have Client IDs themselves and the network applications 300, 310 and 320 are client modules 111, 111-1, 121 and 121-1, And Secondary ID information for interworking with each other.

In FIG. 3, a database 400 for storing all information controlled through the controllers 110 and 120 may be separately configured.

The database 400 includes a Transaction DB 410 for storing transaction information of all operations controlled by the actual network applications 300, 310 and 320 and a Transaction DB 410 for collecting all the events and log information transmitted from the routers 210 and 220 And an I / F status DB 420. For example, FIG. 3 shows a transaction used to control an actual router with respect to the Transaction DB 410.

As shown in FIGS. 3 and 4, when a failure occurs in the routing system environment based on the redundant controllers 110 and 120 with the active client modules 111 and 121 and the standby client modules 111-1 and 121-1, In order to perform the automatic failure processing, when the Agent modules 211 and 221 of the routers 210 and 220 are initialized, a procedure for collecting information about the redundant controllers, an active Client module 111 and 121, A procedure for establishing and maintaining a session between the modules 211 and 221 is required.

5 is an exemplary diagram illustrating information collection for at least one controller in accordance with an embodiment of the present invention.

Referring to FIG. 5, a procedure for collecting duplicated controller information at the time of initialization of the Agent modules 211 and 221 will be described.

5, the Agent modules 211 and 221 include Client modules 111 and 111-1, 121-1 and 121-2 existing on the management network to which the active Client modules 111 and 121 and the Agent modules 211 and 221 are connected, 121, and 121-1. The client discovery request message may be broadcast to the client terminal 100 in order to discover the client discovery request message.

Here, the client search request message may include IPv4 or IPv6 addresses of the Agent modules 211 and 221 in the IP header, and may transmit various control information that the Agent modules 211 and 221 can perform.

For example, in practice, control over the routers 110 and 120 on the side of the controllers 110 and 120 may be performed based on a data model that shapes the various functions of the routers 110 and 120 , And transmits the information on the data models that the Agent modules 211 and 221 can perform in the client search request message.

The Agent module 211 of the router A 210 includes RIB data model information for controlling RIB information on the router together with general information such as version information of the routing system interface, The system log data model information for controlling the log information, and the policy data model information for various policy settings to be set in the router.

In addition, the client modules 111 and 112 receiving the client search request message from the Agent module 211 can generate the Agent List based on the information of the received Agent module.

The active client modules 111 and 112 include I2RS version information of the Client module, Client ID information, Secondary ID information of the Network Application connected to the Client, the number of allowed sessions for connection with the Agent module, (Client Discovery Response Message) including information, etc., to the Agent module 211. The Agent Discovery Response Message may be unicast to the Agent Module 211. [

FIG. 6 is an exemplary diagram for explaining generation of a client list and selection of an active client module according to an embodiment of the present invention. FIG.

6, the Agent module 211 receiving the Client Discovery Response message from the plurality of controllers 110 and 120 stores information on the received Client module and generates a client list (Client list) Lt; / RTI > Therefore, the Agent module 211 can determine the active client modules 111 and 121 and the standby client modules 111-1 and 121-1 using the client list.

For example, the selection for an active Client module may be performed randomly or may be determined according to a preset operator's policy.

6 shows an example in which the Agent module 211 of the router A 210 selects the Client module 111 having the Client ID 100 as the active Client module and the Client module 121-1 having the Client ID 101 as the standby Client module Show selected results.

The Agent module 211 may select an active Client module and then request a session connection with the Client module 111 based on the port information received from the Client module 111. [

After the session connection, the Hello message can be interchanged according to the set period until the session ends to check the state of the session between the Agent module 211 and the Client module 111.

For example, the Hello message is transmitted in a unidirectional manner, and each of the Agent module 211 and the Client module 111 can transmit a Hello message to a partner. When the operator does not transmit the Hello message for a predetermined period, .

FIG. 7 is an exemplary diagram for explaining an error process when a physical link failure of a router occurs according to an embodiment of the present invention. FIG.

The failure occurring in the routing system can be classified into the failures of the controllers 110 and 120 and the failures of the routers 210 and 220.

First, a case where a failure occurs in a physical link connected to the routers 210 and 220 will be described.

In this case, the routers 210 and 220, which have detected the failure, can transmit network failure event information including the failure interface information and the failure cause information to the active client module 111 in connection .

In addition, the routers 210 and 220 may perform a procedure of updating the routing table according to the recovery policy for the router, and may transmit the changed topology information to the active client module 111 during connection.

When a physical failure occurs in the routers 210 and 220, the active client module 111 connected to the Agent modules 211 and 221 of the routers 210 and 220 transmits a Hello message to the router 210 And 220 can be detected or an error can be detected by updating the routing table from the adjacent routers 210 and 220 of the failed routers 210 and 220.

FIG. 8 is an exemplary diagram for explaining an error process when a failure occurs in an active client module according to an embodiment of the present invention. FIG.

Referring to FIG. 8, the Agent module 211 can detect a failure of the active Client module 111 through a Hello message not received. In this case, the standby Client module 111-1 (Session Request Message) to the mobile station (MS) to attempt reconnection.

This is because the active client module 111 can be switched to the standby client module 111-1 in the controller A 110 that performs reconnection to the same controller A 110.

Here, in order to recover a session that has been disconnected from the existing active client module 111, the session request message includes an ID of a router making a session request, a Client ID and secondary ID information of the Cilent module 111 that was previously connected, And information indicating reconnection according to the information.

If the standby client module 111-1 of the controller 110 normally restores the failure, the standby client module 111-1 transmits a session response message to the Agent module 211 The session connection can be notified that the connection has been successfully performed.

The standby client module 111-1 changes its state to an active state and searches the Transaction DB 410 using the Client ID included in the reconnection message to determine whether the transaction state running) can be performed continuously.

FIG. 9 is an exemplary diagram for explaining an error process when a controller fails in accordance with an embodiment of the present invention. FIG. 10 is an exemplary diagram for explaining generation and management of a client consistency table according to an embodiment of the present invention. to be.

A case where a failure occurs in the entire active client module 111 and the standby client module 111-1 in the controller A 110 that is currently controlling the router A 210 will be described with reference to FIG.

When a failure occurs in the entire active client module 111 and the standby client module 111-1 in the controller A 110, the Agent module 211, which attempts to reconnect through a session request message, It is possible to detect that a failure has occurred in the entire Client modules 111 and 111-1 in the controller A (110).

The Agent module 211 may try to connect to another controller B 120 in a standby state from a client list configured in the past.

When the Agent module 211 tries to connect to the controller B 120, the Session Initiation message including the Client ID information and the Secondary ID information used in the active Client module 111 of the existing controller A 110 is used Connection can be attempted.

When the active client module 121 of the controller B 120 operates normally, reconnection can be successfully performed.

Therefore, according to the embodiment of the present invention, the routers 110 and 120 judge a failure occurring in the routing system in a state where the router is controlled by the active client module and process the failure according to the object of the failure occurring in the routing system .

Referring to FIG. 10, the active client module 121 of the controller B 120 receiving the session request message informs the Agent module 211 that the session connection has been successfully performed through the session request message have.

In addition, the active client module 121 generates a client consistency table indicating that the failed client ID and its own client ID information are correlated based on the client ID and the secondary ID information included in the session request message, Can be generated.

The client B consistency table can be maintained until the failure is recovered and the controller B 120 can determine that all the messages transmitted from the router A 210 that has attempted the session connection request from the controller A 110, So that the information stored before the failure and the information stored after the failure can be managed by the coherent controller. .

More specifically, FIG. 10 shows an example in which the controller B 120 generates and manages a client consistency table as a failure occurs in the controller A 110.

For example, the active client module 121 of the controller B 120 transmits a Route addition request transmitted from the Network Application 320, which is received in the Client modules 121 and 121-1 of the controller B 120, The transaction information can be added using the client ID 100 and the secondary 3000, which are information on the existing controller A 110.

Therefore, the active client module 121 of the controller B 120 can maintain and manage the consistent table information before and after the failure with respect to the event and the operation result transmitted from the Agent module 111. [

The method for handling a failure of a routing system according to an embodiment of the present invention can provide a redundant structure of a controller and a failure recovery procedure based on such a structure to stably control a routing system even in the event of a failure.

In addition, the method for handling a fault in the routing system according to the present invention can perform a consistent operation between the failed controller and the controller performing the recovery.

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

100: controller 110: controller A
120: Controller B
101, 111, 111-1, 121, 121-1: Client module
210: Router A 220: Router B
211, 221: Agent module
212, 222: Signaling protocol module
213, 223: Routing protocol module
214, 224: Routing information base module
215, 225: Policy DB
216, 226: Topology DB
217, 227: Forwarding information base module
300, 301, 310, 320: Network application
400: Database 410: Transaction DB
420: I / F status DB

Claims (18)

In fault handling for a routing system,
The router collecting information about at least one controller;
The router identifying an active client module among a plurality of client modules located on the at least one controller based on information about the at least one controller; And
The router determining a failure occurring in the routing system based on the information on the identified active client module and processing the failure according to the object of the failure occurring in the routing system,
The routing system comprises:
Wherein an active client module controls the router among a plurality of client modules that are duplicated active and standby on the at least one controller.
A method of handling a failure of a routing system. The method according to claim 1,
The routing system comprises:
Wherein the agent module located on the control plane of the router communicates with the plurality of client modules on the at least one controller to configure the routing system interface.
A method of handling a failure of a routing system. The method according to claim 1,
Wherein collecting information about the at least one controller comprises:
Broadcasting the client search request message by the router; And
And receiving a client search response message from the at least one controller in response to the client search request message.
A method of handling a failure of a routing system. The method of claim 3,
The client search request message includes:
(RIB) data model information for controlling information of a routing information base (RIB) on the router, system log data model information for controlling log information generated on the router, And policy data model information for policy setting.
A method of handling a failure of a routing system. The method of claim 3,
The client search response message includes:
A version number of the routing system interface for each of the plurality of client modules, Client ID information, Secondary ID information for identifying a network application accommodated in each of the plurality of client modules, a number of allowed sessions for connection with the agent module of the router And port information for connection to a session.
A method of handling a failure of a routing system. The method according to claim 1,
Wherein identifying the active client module comprises:
Characterized in that it identifies the active client module selected randomly or based on a predetermined policy among the plurality of client modules.
A method of handling a failure of a routing system. The method according to claim 1,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
Wherein the routing system is configured to determine a failure occurring in the routing system through a Hello message exchange.
A method of handling a failure of a routing system. The method according to claim 1,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
If it is determined that the active client module and the standby client module included in the controller for controlling the router have failed,
And a session request message is transmitted to the standby client module included in the controller for controlling the router to process the failure.
A method of handling a failure of a routing system. The method according to claim 1,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
If it is determined that a failure has occurred in the controller that controls the router,
Wherein the controller is configured to process a fault by transmitting a session request message to another controller using a client list based on information on the at least one controller.
A method of handling a failure of a routing system. The method according to claim 1,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
If it is determined that the physical link of the router has failed,
And transmits the information on the failed interface and information on the cause of the failure to the active client to process the failure.
A method of handling a failure of a routing system. In fault handling for a routing system,
Determining a failure occurring in the routing system by the router; And
Processing the fault according to the object of the fault occurring in the routing system,
The routing system comprises:
An active client module controls the router among a plurality of client modules that are duplicated active and standby on at least one controller,
The router includes:
And determining a failure occurring in the routing system based on the information on the active client module.
A method of handling a failure of a routing system. The method of claim 11,
The routing system comprises:
Wherein the agent module located on the control plane of the router communicates with the plurality of client modules on the at least one controller to configure the routing system interface.
A method of handling a failure of a routing system. The method of claim 11,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
A session request message including Client ID information for identifying the active client module that has been previously connected, Secondary ID information for identifying a network application accommodated in the active client module that has been previously connected, and information indicating reconnection according to the failure Lt; RTI ID = 0.0 > a < / RTI > fault,
A method of handling a failure of a routing system. 14. The method of claim 13,
Wherein the client module that receives the session request message and processes the failure generates and manages a client consistency table based on the session request message.
A method of handling a failure of a routing system. The method of claim 11,
Wherein the step of determining a failure occurring in the routing system comprises:
Lt; RTI ID = 0.0 > Hello message exchange. ≪ / RTI >
A method of handling a failure of a routing system. The method of claim 11,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
If it is determined that the active client module and the standby client module included in the controller for controlling the router have failed,
And a session request message is transmitted to the standby client module included in the controller for controlling the router to process the failure.
A method of handling a failure of a routing system. The method of claim 11,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
If it is determined that a failure has occurred in the controller that controls the router,
Wherein the controller is configured to process a fault by transmitting a session request message to another controller using a client list based on information on the at least one controller.
A method of handling a failure of a routing system. The method of claim 12,
Wherein the step of processing the failure according to the object of the failure occurring in the routing system comprises:
If it is determined that the physical link of the router has failed,
And transmits the information on the failed interface and information on the cause of the failure to the active client to process the failure.
A method of handling a failure of a routing system.

Images