JP2013545321A - Communication system, control device, node, processing rule setting method and program - Google Patents

Abstract

In a communication system that realizes communication by transferring a packet by a node arranged in a network, each node is allowed to set and maintain a consistent processing rule.
A communication system includes a plurality of nodes including a packet processing unit that processes a received packet in accordance with a processing rule that associates a process to be applied to a packet with a matching rule for specifying a packet to which the process is applied; In response to a processing rule setting request from an arbitrary node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for nodes on the packet transfer route, and the processing rules are mutually connected. And a controller for recording in association with each other. The control device inquires a node on the packet transfer path about the setting status of the processing rule, and when an abnormality is detected in the processing rule set in at least one node, the control device relates to the setting in the other node. Perform rollback operation of processing rules.
[Selection] Figure 1

Description

(Description of related applications)
The present invention is based on the priority claim of Japanese Patent Application No. 2010-232792 (filed on Oct. 15, 2010), the entire description of which is incorporated herein by reference. Shall.
The present invention relates to a communication system, a control device, a node, a processing rule setting method, and a program, and in particular, a communication system, a node, a control device, a communication method, and a communication method for realizing communication by transferring a packet by a node arranged in a network. Regarding the program.

  As shown in Non-Patent Documents 1 and 2, in recent years, a technique called OpenFlow has been proposed. OpenFlow captures communication as an end-to-end flow and performs path control, failure recovery, load balancing, and optimization on a per-flow basis. The OpenFlow switch that functions as a forwarding node includes a secure channel for communication with the OpenFlow controller, and operates according to a flow table that is appropriately added or rewritten from the OpenFlow controller. In the flow table, for each flow, a set of a collation rule (matching rule) that collates with the packet header, an action (Actions) that defines the processing content, and flow statistical information (Stats) is defined (see FIG. 38). ).

  FIG. 38 illustrates action names and action contents defined in Non-Patent Document 2. OUTPUT is an action for outputting a packet to a designated port (interface). SET_VLAN_VID to SET_TP_DST are actions for modifying the field of the packet header.

  For example, when the OpenFlow switch receives the first packet (first packet), the OpenFlow switch searches the flow table for an entry having a matching rule (FlowKey) that matches the header information of the received packet. When an entry that matches the received packet is found as a result of the search, the OpenFlow switch performs the processing content described in the action field of the entry on the received packet. On the other hand, if no entry matching the received packet is found as a result of the search, the OpenFlow switch forwards the received packet to the OpenFlow controller via the secure channel, and the source / destination of the received packet. To request the determination of the route of the packet based on the above, receive the flow entry that realizes this, and update the flow table.

  Non-Patent Document 3 is a specification of a protocol (ForCES) that separates a transfer element and a control element. 4.3.1.2.2 of the same literature. In the Transaction Protocol section, it is described that two-phase commitment control is used for transaction management of a transfer element or a plurality of messages between transfer elements.

Nick McKeown and seven others, "OpenFlow: Enabling Innovation in Campus Networks", [online], [searched September 21, 2010], Internet <URL: https://www.openflowswitch.org//documents/openflow- wp-latest.pdf> "OpenFlow Switch Specification" Version 1.0.0. (Wire Protocol 0x01) [searched on September 21, 2010], Internet <URL: https://www.openflowswitch.org/documents/openflow-spec-v1.0.0. pdf> "RFC5810-Forwarding and Control Element Separation (ForCES) Protocol Specification", [searched on September 21, 2010], Internet <URL: https://www.faqs.org/rfcs/rfc5810.html>

  The OpenFlow controller (hereinafter referred to as “control device” including the OpenFlow controllers in Non-Patent Documents 2 and 3) that receives the request for determining the route of the received packet forwards the received packet and subsequent packets belonging to the same flow. In order to achieve this, all the open flow switches on the transfer path (hereinafter referred to as “nodes” including the open flow switches of Non-Patent Documents 2 and 3) have a consistent flow entry (hereinafter, Non-Patent Document 2, 3), including the flow entry stored in the flow table of the open flow switch 3). In addition, if appropriate processing rules cannot be set for some nodes on the transfer path, not only packet discard but also a situation where the packet is transferred in a loop shape may occur. It is necessary to detect and deal with it immediately.

  Furthermore, after setting the processing rule, it is conceivable that a part of the processing rule is lost due to a node failure or the like, and in this case, the consistency of the flow entry may be impaired.

  However, the specification of OpenFlow in Non-Patent Document 2 is that even if there is a node for which the appropriate processing rule is not set, the processing rule is reset to the control device when the node receives a subsequent packet. It is configured to restore consistency by requesting, and there is no mechanism for quickly detecting a lack of consistency in processing rules and taking countermeasures.

  The present invention has been made in view of the circumstances described above, and the object of the present invention is to provide a communication system, a control device, a node, and a processing rule that can set and maintain a consistent processing rule in a node. To provide a setting method and a program.

  According to the first aspect of the present invention, there are provided a plurality of packet processing units that process a received packet according to a processing rule that associates a process applied to a packet with a matching rule for specifying a packet to which the process is applied. In response to a processing rule setting request from a node and an arbitrary node, a packet transfer route is calculated, and a processing rule for realizing the packet transfer route is set for a node on the packet transfer route. A control device that records the rules in association with each other, wherein the control device inquires a node on the packet transfer path about the setting status of the processing rules, and the processing rules set in at least one node are abnormal. When a system is detected, a communication system is provided that performs a rollback operation of related processing rules set in other nodes. That.

  According to the second aspect of the present invention, there are provided a plurality of packet processing units that process a received packet according to a processing rule that associates a process applied to a packet with a matching rule for specifying a packet to which the process is applied. In response to a processing rule setting request from an arbitrary node connected to a node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for a node on the packet transfer route, The processing rules are recorded in association with each other, and further, the nodes on the packet transfer path are inquired about the setting status of the processing rules, and when an abnormality is detected in the processing rules set in at least one node, etc. There is provided a control device that performs a rollback operation of related processing rules set in the node.

  According to a third aspect of the present invention, there is provided a packet processing unit that processes a received packet according to a processing rule that associates a process applied to a packet with a matching rule for specifying a packet to which the process is applied. In response to an inquiry from any one of Items 8 to 14, the flow identifier assigned to the processing rule and the transaction identifier assigned in common to the processing rule associated with the processing rule are returned. A node is provided.

  According to a fourth aspect of the present invention, there are provided a plurality of packet processing units that process a received packet according to a processing rule that associates a process to be applied to a packet with a matching rule for specifying a packet to which the process is applied. In response to a processing rule setting request from the node, the node and the connected control device calculate a packet forwarding route, and a processing rule for realizing the packet forwarding route is provided to the node on the packet forwarding route. A step of recording the processing rules in association with each other and inquiring a node on the packet transfer path about the setting status of the processing rules, and an abnormality is detected in the processing rules set in at least one node. If there is a step, perform a rollback operation of related processing rules set in other nodes, and The law is provided. The method is tied to specific machines: nodes and control devices that control these nodes.

  According to a fifth aspect of the present invention, there is provided a program that is executed by a computer that constitutes the control device or node described above. This program can be recorded on a computer-readable storage medium. That is, the present invention can be embodied as a computer program product.

  According to the present invention, it is possible to set and maintain a consistent processing rule in a node.

It is a figure for demonstrating the outline | summary of this invention. It is a figure showing the structure of the 1st Embodiment of this invention. It is a block diagram showing the structure of the node of the 1st Embodiment of this invention. It is a figure for demonstrating the relationship between the flow table of the note of 1st Embodiment of this invention, and an event buffer. It is a figure for demonstrating the flow table of the node of the 1st Embodiment of this invention. It is a block diagram showing the structure of the processing rule setting apparatus of the 1st Embodiment of this invention. It is a figure for demonstrating the flow setting log of the processing rule setting apparatus of the 1st Embodiment of this invention. It is a block diagram showing the structure of the route control apparatus of the 1st Embodiment of this invention. It is a figure for demonstrating the transaction log of the path control apparatus of the 1st Embodiment of this invention. It is a figure for demonstrating the operation example of the 1st Embodiment of this invention. FIG. 11 is a continuation diagram of FIG. 10. FIG. 12 is a continuation diagram of FIG. 11. FIG. 13 is a continuation diagram of FIG. 12. It is a figure showing the structure of the 2nd Embodiment of this invention. It is a block diagram showing the structure of the node of the 2nd Embodiment of this invention. It is a figure for demonstrating the operation example of the 2nd Embodiment of this invention. FIG. 14 is a continuation diagram of FIG. 13. It is a sequence diagram showing operation | movement (normal update) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (node update abnormality) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (processing rule setting apparatus abnormality after completion | finish of transaction) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (The update abnormality of a node and the processing rule setting apparatus abnormality after completion | finish of a transaction) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (the processing rule setting apparatus abnormality before the commit response reception) of the 3rd Embodiment of this invention. FIG. 10 is a sequence diagram illustrating operations of the third embodiment of the present invention (node update abnormality and processing rule setting apparatus abnormality before commit response reception). It is a sequence diagram showing operation (processing rule setting device abnormality before node update abnormality and rollback completion notification reception) of the third exemplary embodiment of the present invention. It is a sequence diagram showing the operation | movement (the processing rule setting apparatus abnormality before commit request transmission) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (the node update abnormality and the processing rule setting apparatus abnormality before transmission of a rollback instruction | indication) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (processing rule setting apparatus abnormality before receiving a processing rule setting response) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (the node update abnormality and the processing rule setting apparatus abnormality before receiving a processing rule setting response) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (processing rule setting apparatus abnormality before reception of a processing rule setting result) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (The node update abnormality and the processing rule setting apparatus abnormality before receiving a processing rule setting result) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (processing rule setting apparatus abnormality before processing rule setting) of the 3rd Embodiment of this invention. It is a sequence diagram showing operation (node update abnormality and processing rule setting device abnormality before setting processing rule) of the third exemplary embodiment of the present invention. It is a sequence diagram showing the operation | movement (processing rule setting apparatus abnormality before reception of a processing rule recording completion notification) of the 3rd Embodiment of this invention. It is a sequence diagram showing operation (processing rule setting apparatus abnormality before node update abnormality and processing rule record completion notification reception) of the third exemplary embodiment of the present invention. It is a sequence diagram showing the operation | movement (processing rule setting apparatus abnormality before a processing rule recording request | requirement) of the 3rd Embodiment of this invention. It is a sequence diagram showing the operation | movement (the node update abnormality and the processing rule setting apparatus abnormality before a processing rule recording request | requirement) of the 3rd Embodiment of this invention. It is a sequence diagram showing operation | movement (normal update) of the 4th Embodiment of this invention. It is a figure showing the structure of the flow entry of a nonpatent literature 2.

  First, the outline of the present invention will be described. As shown in FIG. 1, the present invention includes a plurality of packet processing units that process a received packet in accordance with a processing rule that associates a process applied to a packet with a matching rule for specifying a packet to which the process is applied. In response to a processing rule setting request from the node 10 and an arbitrary node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for a node on the packet transfer route, This can be realized by the control device 20 that records processing rules in association with each other (see processing rule setting log 21). The control device inquires the node on the packet transfer path about the setting status of the processing rule (see the set processing rule 11), and when an abnormality is detected in the processing rule set in at least one node, Performs a rollback operation of related processing rules set in other nodes. Note that the reference numerals of the drawings attached to this summary are attached to the respective elements for convenience as an example for facilitating understanding, and are not intended to limit the present invention to the illustrated embodiment.

  For example, assume that the control device 20 calculates a packet transfer path that passes through the two nodes # 1 and # 2 in FIG. 1 as the communication path between the host (A) and the host (B) in FIG. In this case, the control device 20 outputs a packet received from the host (A) to the node # 1 from the port to which the node # 2 is connected, and sends a packet received from the node # 1 to the node # 2. The processing rule to be output from the port to which B) is connected is set (FlowMod (Add)). Further, the control device 20 records a setting history (log) of each set processing rule.

  After setting the processing rule, the control device 20 inquires the node # 1 and node # 2 about the setting status of the processing rule. As the inquiry method, a Barrier message (Request / Reply) or a statistical information request message (Stats Request / Reply) defined in Non-Patent Document 2 can be used.

  As a result of the inquiry, when an abnormality is recognized in the processing rule set in one node (for example, node # 2 in FIG. 1), the control device 20 refers to the processing rule setting log 21 and sets other nodes. A rollback operation of the set processing rule is performed (Roll Back). Specifically, in the control device 20, a processing rule that belongs to the same flow (that is, the transaction ID described later) is the same as the processing rule that has failed in the setting in the node # 2 in FIG. An operation for deleting or updating (returning to the original) the processing rule of the node # 1 is performed.

  For example, when a packet transmitted from the host (A) is transferred to the node # 2 via the node # 1, a processing rule having a matching rule that matches the packet is not set in the node # 2. In this case, a processing rule setting request is made to the control device 20, but if the node # 2 has a matching rule that belongs to another flow but matches the corresponding packet, the processing according to the processing rule is performed. For example, transfer to another node (not shown) and header rewriting are performed.

  According to the present invention, since the rollback operation using the setting history is performed as described above, it is possible to prevent unintended packet processing as described above from being performed.

  In the example of FIG. 1, the control device 20 records the setting history. However, the control device 20 may record the setting history in another journal server or a backup control device. In the following embodiment, an example will be described in which the functions of the control device 20 are distributed and clustered, and each cluster has a redundant configuration in order to increase the availability of the entire communication system.

[First Embodiment]
Next, a first embodiment of the present invention will be described in detail with reference to the drawings. FIG. 2 is a diagram showing the configuration of the first exemplary embodiment of the present invention. Referring to FIG. 2, a plurality of nodes 10, processing rule setting devices 20 a to 20 d that belong to the first cluster or the second cluster and constitute the active system and the standby system, the path control device 30, and the system management device 40, respectively. Is shown. In addition, the element (code | symbol 20) enclosed with the dashed-dotted line in FIG. 2 is equivalent to 20 A of control apparatuses mentioned above.

  The first cluster processing rule setting devices 20 a and 20 b (second cluster processing rule setting devices 20 c and 20 d) are devices that set processing rules for the subordinate nodes 10. In the example of FIG. 2, the first cluster processing rule setting device 20a operates in the active state, and the first cluster processing rule setting device 20b is in the standby state. Similarly, in the second cluster, the second cluster processing rule setting device 20c operates in the active state, and the second cluster processing rule setting device 20d is in the standby state.

  The route control device 30 is transferred from the processing rule setting devices (in this case, the first cluster processing rule setting device 20a and the second cluster processing rule setting device 20c) in the active state among the processing rule setting devices 20a to 20d. Based on the processing rule creation request, a packet transfer path is calculated and a corresponding processing rule is created. The processing rule setting device in each active state is instructed to set the created processing rule. In addition, the routing control device 30 inquires to the processing rule setting device in each active state described above whether the processing rule has been set correctly, records the result in the transaction log held in the own device, and If so, perform a rollback operation.

  The system management device 40 is a device that confirms the operating state of the processing rule setting devices 20a to 20d and performs switching operation between the active system and the standby system based on the result.

  Subsequently, each device constituting the above-described communication system will be described in detail with reference to the drawings.

[node]
FIG. 3 is a block diagram showing the configuration of the node according to the first exemplary embodiment of the present invention. Referring to FIG. 3, a configuration including a flow table setting unit 12, an event buffer 13, a journal transmission unit 14, a flow table 15, a packet processing unit 16, a packet transmission unit 17, and a packet reception unit 18. It is shown.

  The flow table setting unit 12 sets (adds) a processing rule in the flow table 15 or changes (rewrites) or deletes a processing rule registered in the flow table in accordance with instructions from the processing rule setting devices 20a to 20d.

  As shown in FIG. 4, the event buffer 13 is a buffer that stores a pointer indicating the position in the flow table of the entry that has been changed by the flow table setting unit 12 in a FIFO (First In First Out) system. In the example of FIG. 4, a pointer indicating a position in the flow table is stored. However, for example, a configuration in which the contents of the flow entry itself are buffered can be employed.

  In response to an inquiry regarding the processing rule setting status from the processing rule setting devices 20a to 20d, the journal transmission unit 14 reads the processing rule at the position indicated by the event buffer 13 and includes the flow ID and transaction ID of the processing rule. Send journal data. When the inquiry from the processing rule setting devices 20a to 20d uses a Barrier message (Barrier Request), the Barrier message (Barrier Reply) of Non-Patent Document 2 can be used as a response. Here, the Barrier message is a message for responding to the processing contents executed before the node receives the Barrier message (Barrier Request). In addition, it may be confirmed whether or not the entry is correctly set in each node by using Stats Request / Reply for inquiring statistical information (Stats) regarding the processing rule.

  As shown in FIG. 5, the flow table 15 includes a matching rule (Rule), processing contents (Actions) performed on a packet conforming to the matching rule, statistical information (Stats), and a processing rule within the node. Between the processing rule setting devices 20a to 20d with respect to a processing rule belonging to the same flow and a flow ID (Flow ID; corresponding to “flow cookie” in Non-Patent Document 2). This is a table in which a transaction ID (Transaction ID, corresponding to “xid” in Non-Patent Document 2), which is an identifier set to be unique, is one entry. In this configuration, a flow ID and a transaction ID are added to the flow entry held in the OpenFlow switch of Non-Patent Document 2 shown in FIG. As described above, by returning the flow entry including the flow ID and the transaction ID, the processing rule setting devices 20a to 20d share the transaction ID with each other whether or not the processing rule set by itself is set correctly. It can be determined whether or not a series of processing rules are set correctly.

  The packet processing unit 16 searches the flow table 15 for a processing rule having a matching rule that matches the packet received by the packet receiving unit 18, and executes the processing content (Actions) described in the processing rule. If no matching rule matching the packet received by the packet receiver 18 is found in the flow table 15, the packet (unknown packet) is transmitted to the processing rule setting devices 20a to 20d, and the processing rule is set. Ask.

  When the processing content (Actions) described in the processing rule is packet transfer (Output), the packet transmission unit 17 outputs the packet from the port specified by the processing content (Actions) to the next hop. To do.

  Note that the node 10 as described above can be realized by a configuration in which the event buffer 13 and the journal transmission unit 14 are added based on the OpenFlow switch of Non-Patent Document 2.

[Processing rule setting device]
FIG. 6 is a block diagram showing the configuration of the processing rule setting device 20a. Referring to FIG. 6, a configuration including a request acceptance unit 22, a cluster management unit 23, a processing rule setting unit 24, a journal confirmation unit 25, a journal acquisition unit 26, and a processing rule setting log storage unit 27. It is shown. Since the processing rule setting devices 20b to 20d have the same configuration, the description thereof is omitted.

  The request acceptance unit 22 receives various requests from the path control device 30 and the system management device 40 and transfers them to other processing units according to the request contents.

  The cluster management unit 23 performs communication for state synchronization with the processing rule setting devices belonging to the same cluster. Specifically, when the processing rule setting device 20a is operating in the active system, the processing rule that is requested to be set by the processing rule setting unit 24 to the node 10 is changed to a standby processing rule setting device (for example, a processing rule). A process of transmitting to the setting device 20b) and recording (backup) is performed. When the processing rule setting device 20a is operating in the standby system, the processing rule received from the active processing rule setting device (for example, the processing rule setting device 20b) is recorded in the processing rule setting log storage unit 27. Process.

  The processing rule setting unit 24 transfers the processing rule setting request and the rollback instruction received from the route control device 30 to the corresponding node 10 and registers the contents in the processing rule setting log storage unit 27.

  The journal acquisition unit 26 inquires the node 10 about the setting status of the processing rule, and acquires journal data including the flow ID and transaction ID included in the processing rule at the position indicated by the pointer of the event buffer 13 of the node 10.

  The journal confirmation unit 25 compares the journal data including the flow ID and transaction ID acquired by the journal acquisition unit 26 with the processing rule setting history stored in the processing rule setting log storage unit 27, and sets the processing rule. It is confirmed whether or not the processing rule set by the unit 24 is correctly set in the node 10. Further, the journal confirmation unit 25 transmits the confirmation result to the path control device 30.

  When the processing rule setting device 20a is operating in the active system, the processing rules set by the processing rule setting unit 24 are sequentially registered in the processing rule setting log storage unit 27. Further, when the processing rule setting device 20a is operating in the standby system, the processing rule received from the other processing rule setting device 20b received via the cluster management unit 23 is registered. That is, the contents of each processing rule setting log storage unit 27 of the active processing rule setting device 20a and the standby processing rule setting device 20b are in a synchronized state and registered in the flow table 15 of each node. Maintained in a consolidated state.

  FIG. 7 is an example of a processing rule setting log recorded in the processing rule setting log storage unit 27. In the example of FIG. 7, a processing rule setting target node (node ID), a flow ID, a processing rule, and a status flag (Status) indicating whether rollback has been performed are held.

[Route control device]
FIG. 8 is a block diagram showing the configuration of the route control device 30. Referring to FIG. 8, a configuration including a main processing unit 31, a processing rule setting unit 32, a transaction confirmation unit 33, and a transaction log storage unit 34 is shown.

  The main processing unit 31 refers to the network topology, calculates a packet transfer route for transferring a packet received from the processing rule setting request, and creates a processing rule to be set in a node on the packet transfer route.

  The processing rule setting unit 32 requests the processing rule setting device corresponding to the node on the packet transfer path to set the processing rule created by the main processing unit 31.

  The transaction confirmation unit 33 updates the transaction log from each processing rule setting device based on the confirmation result of whether or not the processing rule set by each processing rule setting device is correctly set in the node 10. As a result of the update, when a setting abnormality of a processing rule having a certain transaction ID is confirmed, the transaction confirmation unit 33 manages the node in which the processing rule having the transaction ID is set via the main processing unit 31. Instructs the processing rule setting device to roll back.

  The processing rule setting devices 20a to 20d and the path control device 30 (processing means) shown in FIGS. 6 and 8 perform the above-described processes by using the hardware of the computers constituting these devices. It can also be realized by a computer program to be executed. The configuration shown in FIGS. 6 and 8 is an example of the distribution of both functions. The processing rule setting devices 20a to 20d and the routing control device 30 (processing means) are integrated, or one processing means is replaced with the other. It is also possible to comprise.

  FIG. 9 shows a configuration example of the transaction log. In the example of FIG. 9, the transaction ID and the status (Status) of the transaction ID are recorded. In the transaction ID state (Status) field, for example, at the stage where the setting of the processing rule is requested, the status information “send request” is set according to the processing rule setting result received from each node (success. / Fail) is written.

  Next, the operation of this embodiment will be described in detail with reference to the drawings. 10 to 13 are diagrams for explaining an operation example of the first embodiment of the present invention. In the following description, a packet from one host to another host is input to the route control device 30, the route control device 30 calculates an appropriate packet transfer route, and a processing rule for realizing this packet transfer route has been created. Explain that it is.

  First, referring to FIG. 10, the route control device 30 requests the processing rule setting devices 20a and 20c operating in the active state to set processing rules ((1) in FIG. 10).

  In response to the processing rule setting request, the processing rule setting devices 20a and 20c operating in the active state request processing rule recording from the processing rule setting devices 20b and 20d, respectively, that stand by in the standby system ((( 2)).

  When processing rule recording completion notifications are received from the processing rule setting devices 20b and 20d waiting in the standby system ((3) in FIG. 10), the processing rule setting devices 20a and 20c send processing rules to the designated nodes 10 respectively. Is set ((4) in FIG. 10). Here, it is assumed that a new processing rule is additionally registered in the flow table 15 of the node 10.

  In response to the processing rule setting status inquiry from the processing rule setting devices 20a and 20c, the node 10 that has received the setting of the processing rule responds with a flow ID and a transaction ID as the processing rule setting status (see FIG. 10 (5)).

  Here, it is assumed that a failure has occurred in the processing rule setting device 20a and the system management device 40 has detected this. In this case, a normal flow ID and a transaction ID are returned from the processing rule setting device 20c, but no response is made from the processing rule setting device 20a ((7) and (7 'in FIG. 11).

  Since there is no response from the processing rule setting device 20a (time-out established), the path control device 30 determines that setting of a series of processing rules having the corresponding transaction ID has failed, and the processing rule setting device 20c A transaction ID is designated to instruct a rollback ((8) in FIG. 11).

  Upon receipt of the rollback instruction for the processing rule, the processing rule setting device 20c requests the processing rule setting device 20d waiting in the standby system to record the rollback content ((9) in FIG. 11).

  When the rollback content recording completion notification is received from the processing rule setting device 20d that stands by in the standby system ((10) in FIG. 11), the processing rule setting device 20c sends the specified transaction ID to the node 10 that has been set. A rollback is instructed ((11) in FIG. 11). Here, processing for deleting a processing rule having a corresponding transaction ID is performed from the flow table 15 of the node 10. When the processing rule is rewritten in (4) of FIG. 10, the processing rule setting device 20c refers to the processing rule setting log and performs processing for writing back the processing rule having the corresponding transaction ID. Let it run.

  In response to the inquiry about the rollback processing status from the processing rule setting device 20c, the node 10 that has received the rollback instruction responds with a flow ID and a transaction ID as a rollback completion notification ((( 12)).

  When the processing rule setting device 20c confirms that the rollback has been performed correctly in the rollback completion notification, the processing rule setting device 20c transmits a rollback completion notification to the path control device 30 ((13) in FIG. 11). .

  At this point, the processing rule whose consistency is not guaranteed on the second cluster side is deleted.

  Thereafter, when the system management device 40 activates the processing rule setting device 20b instead of the processing rule setting device 20a ((14) in FIG. 12), the processing rule setting device 20b responds to the inquiry about the setting status of the processing rule. The node 10 which has not responded is requested to transmit journal data including the flow ID and the transaction ID ((15) in FIG. 12).

  When the node 10 that has received the journal data transmission request responds with journal data including the flow ID and the transaction ID as the setting status of the flow table ((16) in FIG. 12), the processing rule setting device 20b The processing rule setting log 27 recorded in (2) is collated. Here, since the processing rule is correctly set in (4) of FIG. 10, the processing rule setting device 20b requests the route control device 30 to confirm whether or not to roll back from the viewpoint of the entire transaction ( (17) of FIG.

  The routing control device 30 that has received the confirmation request for whether or not to roll back refers to the transaction log 34 and confirms whether or not to roll back from the viewpoint of the entire transaction. Here, as described in (8) and (11) of FIG. 11, since the rollback has already been instructed to the processing rule setting device 20c, the path control device 30 instructs the processing rule setting device 20b. A rollback is instructed ((18) in FIG. 13).

  Receiving the rollback instruction, the processing rule setting device 20b instructs the designated node 10 to rollback ((19) in FIG. 13). Here, the process of deleting the processing rule registered in (4) of FIG. 10 is performed from the flow table 15 of the node 10.

  In response to the rollback processing status inquiry from the processing rule setting device 20b, the node 10 that has received the rollback instruction responds with a flow ID and a transaction ID as a rollback completion notification ((( 20)).

  When the processing rule setting device 20b confirms that the rollback has been performed correctly in the rollback completion notification, the processing rule setting device 20b transmits a rollback completion notification to the path control device 30 ((21) in FIG. 13). .

  At the stage where the above series of processing is completed, the processing rule setting device 20b notifies the activation completion to the system management device 40 ((22) in FIG. 13).

  At the above stage, the processing rule whose consistency is not guaranteed on the first cluster side is also deleted. The route control device 30 can set the intended processing rule for the intended node by making a processing rule setting request to the processing rule setting devices 20b and 20c again as necessary.

  The configuration of the present embodiment not only ensures the consistency of the setting of the processing rules, but also the control device is functionally distributed between the processing rule setting device and the route control device, and individual processing rule settings are made. The device is clustered and made redundant. For this reason, the load of each processing rule setting device is distributed. Furthermore, even if a failure occurs in a certain processing rule setting device, the service can be continued by switching to the standby system, so that high availability is realized.

[Second Embodiment]
In the first embodiment described above, the rollback is described with reference to the processing rule setting log 27 on the processing rule setting device side. However, by providing the node 10 with the processing rule setting log, the node side A configuration for performing rollback can also be realized.

  Hereinafter, a second embodiment of the present invention in which rollback is performed on the node side will be described. Further, in the following description, description of matters common to the first embodiment will be omitted, and description will be made focusing on the differences.

  FIG. 14 is a diagram showing the configuration of the second exemplary embodiment of the present invention. The difference from the first embodiment is that processing rule setting apparatuses belonging to different clusters are connected to each other, and processing rule setting logs can be acquired respectively. In addition, the element (code | symbol 20B) enclosed with the dashed-dotted line in FIG. 14 is equivalent to the control apparatus 20A mentioned above.

  FIG. 15 is a block diagram showing a configuration of a node according to the second exemplary embodiment of the present invention. The difference from the node 10 of the first embodiment shown in FIG. 3 is that the processing rule before rewriting is buffered together with the pointer in the event buffer 13A, not the pointer of the flow table.

  Next, the operation of this embodiment will be described in detail with reference to the drawings. 16 to 17 are diagrams for explaining an operation example of the second embodiment of the present invention. In response to the processing rule setting request, there is no processing rule setting response from the processing rule setting device 20a of the first cluster, and the operation until the system management device 40 activates the processing rule setting device 20b is the same as in the first embodiment. Since it is the same, description is abbreviate | omitted.

  The processing rule setting device 20b activated in (14) of FIG. 16 requests the transmission of journal data to the node 10A that has not responded to the processing rule setting status inquiry ((15) of FIG. 16). ).

  When the node 10A that receives the journal data transmission request responds with journal data including the flow ID and the transaction ID ((16) in FIG. 16), the processing rule setting device 20b records in (2) in FIG. It collates with the processing rule setting log 27 that has been used. Here, since the processing rule is correctly set in (4) of FIG. 10, the processing rule setting device 20b transmits the processing rule setting log 27 of the processing rule setting device 20c to the processing rule setting device 20c of the second cluster. The transmission is requested ((17A) in FIG. 16).

  When the processing rule setting log 27 is received from the processing rule setting device 20c ((18A) in FIG. 17), the processing rule setting device 20b receives the processing rule setting log 27 of the processing rule setting device 20c and (16) in FIG. The received journal data of the node 10A is collated.

  Here, as described in (8) and (11) of FIG. 11, since the rollback has already been instructed to the processing rule setting device 20c, from the processing rule setting log 27 of the processing rule setting device 20c. Also, the journal data of the node 10A received in (16) of FIG. 16 is in a more advanced state. Therefore, the processing rule setting device 20b instructs the node 10A to roll back by specifying the transaction ID ((19A) in FIG. 17).

  The node 10A performs rollback using the processing rule setting log, and responds with a flow ID and a transaction ID as a rollback completion notification in response to the inquiry of the rollback processing status from the processing rule setting device 20b. (20A in FIG. 17).

  When the processing rule setting device 20b confirms that the rollback is correctly performed in the rollback completion notification, the processing rule setting device 20b transmits an activation completion notification to the system management device 40 ((21A) in FIG. 17). .

  At this stage, also in the present embodiment, the deletion of the processing rule whose consistency is not guaranteed on the first cluster side is completed. The route control device 30 can set the intended processing rule for the intended node by making a processing rule setting request to the processing rule setting devices 20b and 20c again as necessary.

  As described above, by providing the processing rule setting log in the implementation node 10A, it is possible to perform rollback of appropriate contents even in a configuration in which the setting contents of past processing rules are held on the node side. It is.

[Third Embodiment]
Next, a third embodiment in which a commit request / commit response is performed between the route control device 30 and the processing rule setting devices 20a to 20d will be described. Since the third embodiment of the present invention can be realized with the same configuration as the first and second embodiments, the operation will be described in detail below with reference to the sequence diagrams of FIGS. To do.

(1. Successful completion)
First, with reference to FIG. 18, a series of flows when processing rules are normally set in the nodes 10 of the first cluster and the second cluster will be described.

  When an unknown packet is transferred from the node 10 (step S000 in FIG. 18), the path control device 30 calculates the transfer path of the packet and creates a processing rule for realizing the packet transfer path. The path control device 30 requests the processing rule setting devices 20a and 20c operating as the active system (ACT) to set the created processing rule (step S001 in FIG. 18).

  Receiving the processing rule setting request, the processing rule setting devices 20a and 20c request the standby processing (SBY) processing rule setting devices 20b and 20d to record the processing rule (step S002 in FIG. 18).

  When processing rule recording completion notifications are received from the processing rule setting devices 20b and 20d (step S003 in FIG. 18), the processing rule setting devices 20a and 20c respectively send processing rules to the nodes designated by the path control device 30. Is set (step S004 in FIG. 18).

  Each of the processing rule setting devices 20a and 20c inquires of the node instructed by the path control device 30 about the setting status of the processing rule, and receives the result (step S005 in FIG. 18).

  Next, the processing rule setting devices 20a and 20c transmit the processing rule setting status to the route control device 30 (step S006 in FIG. 18). Here, since the processing rule is normally set in each node, the path control device 30 requests the processing rule setting devices 20a and 20c to commit (step S007 in FIG. 18).

  When the commit OK is received from the processing rule setting devices 20a and 20c, the path control device 30 ends the transaction on the assumption that a series of processing rules have been correctly set.

(2. Rollback operation due to node failure)
Next, with reference to FIG. 19, a rollback operation in the case where there is an abnormality in the processing rule setting status from the node 10 will be described. The operations from Steps S000 to S006 in FIG. 19 are the same as the operations from Steps S000 to S006 in FIG.

  In the example of FIG. 19, in step S105, the processing rule setting status returned from the node 10 of the second cluster does not match the processing rule setting status grasped on the processing rule setting device 20c side. (Hereinafter, each case including FIG. 19 represents such a case as a processing rule setting status (NG)).

  The processing rule setting device 20c that has received the processing rule setting status transmits the flow ID and the transaction ID received from the node 10 of the second cluster as the processing rule setting status to the route control device 30 (FIG. 19). S106).

  The path control device 30 receives the correct flow ID and transaction ID from the processing rule setting device 20a (S005 in FIG. 19), but receives the wrong flow ID, transaction ID and reception from the processing rule setting device 20c. For this reason (S106 in FIG. 19), it is determined that the setting of a series of processing rules having the corresponding transaction ID has failed, and the rollback is instructed to the processing rule setting devices 20a and 20c by specifying the transaction ID ( S107 in FIG. 109).

  Thereafter, as in the case of setting the processing rule, after the recording / completion to the standby processing rule setting devices 20b and 20d (S108 and S109 in FIG. 19), a rollback instruction is given to each node 10. (S110 in FIG. 19). Finally, at the stage of receiving the notification of completion of the rookeback from the processing rule setting devices 20a and 20c, the path control device 30 ends the transaction on the assumption that a series of processing rules have been correctly rolled back.

  As described above, in this embodiment, even when there is a processing rule setting failure in the node 10, the rollback processing can be correctly performed based on the contents sent from the processing rule setting device 20a of another cluster. It becomes possible.

(3-1. Switching of processing rule setting device after completion of transaction)
Next, referring to FIG. 20, the system management device 40 causes the standby system processing rule to become abnormal, such as when an abnormality occurs in the processing rule setting device 20a after a series of processing is normally completed as shown in FIG. A subsequent operation when the setting device is activated will be described. The operations from Steps S000 to S008 in FIG. 20 are the same as the operations from Steps S000 to S008 in FIG.

  After that, when the system management device 40 activates the processing rule setting device 20b that has been waiting in the standby system (S201 in FIG. 20), the processing rule setting device 20b gives the flow ID and transaction ID to the node 10. The transmission of the included journal data is requested (202 in FIG. 20).

  When the journal data is received from the node 10 (S203 in FIG. 20), the processing rule setting device 20b collates with the processing rule setting history stored in the processing rule setting log storage unit 27 in its own device, and the collation result is obtained. It transmits to the route control apparatus 30 (S204 of FIG. 20).

  The path control device 30 refers to the transaction log 34 and confirms that the transaction confirmed based on the collation result is normally completed, and then sends an affirmative response (verification with the transaction log to the processing rule setting device 20b). ) (S205 in FIG. 20).

  The processing rule setting device 20b that has received the affirmative response (verification with transaction log OK) notifies the system management device 40 that the activation has been completed (S206 in FIG. 20).

(3-2. Switching of processing rule setting device after completion of rollback due to node error)
Next, a subsequent operation when the system management device 40 activates the standby processing rule setting device after completion of the rollback due to an abnormality in the processing rule setting status from the node 10 will be described. The operations from steps S000 to S112 in FIG. 21 are the same as the operations from steps S000 to S112 in FIG.

  The subsequent operations are the same as those in steps S201 to S205 in FIG. 20, but the rollback is completed in the processing rule setting device 20c as a result of referring to the transaction log 34. The rule setting device 20b is also instructed to roll back (S207 in FIG. 21).

  When the rollback completion notification is received from the processing rule setting device 20b (S208 in FIG. 21), the path control device 30 notifies the system management device 40 that the activation has been completed (S206 in FIG. 20). ).

  As described above, the activated processing rule setting device checks whether the processing rule set in the node is synchronized with the processing rule known by the own device, and further collates with the transaction log. Therefore, even if the processing rule setting device is switched by the system management device 40, the consistency of the processing rules set in each node is not impaired.

(4. Abnormality of processing rule setting device before processing rule setting completion or rollback completion)
Next, the operation when a failure occurs in the active processing rule setting device in the process of processing rule setting request to commit OK (rollback completion) will be described for each failure occurrence timing.

  FIG. 22 is a sequence diagram showing an operation when a commit OK is not transmitted from one processing rule setting device 20a in response to a commit request after normal setting of a processing rule. In this case, as in the case described with reference to FIG. 11 in the first embodiment, the path control device 30 instructs the processing rule setting device 20c to which the commit OK has been sent to perform rollback. Become. The specific operation is the same as steps S108 to S111 in FIG. Thereafter, as described with reference to FIG. 20, switching of the processing rule setting device and acquisition / collation of journal data are performed by the system management device 40. Here, since the rollback has already been instructed to the processing rule setting device 20c, the path control device 30 also instructs the activated processing rule setting device 20b to perform rollback.

  FIG. 23 is a sequence showing an operation when a processing rule setting status from the node 10 is abnormal and a rollback completion notification is not transmitted from one processing rule setting device 20a after performing a rollback operation. FIG. In this case, as in FIG. 22, switching of the processing rule setting device by the system management device 40 and acquisition / collation of journal data are performed, but the rollback processing at the node 10 has been completed normally, so it is activated as it is. Completed.

  In FIG. 24, the processing rule setting status from the node 10 is abnormal, and after performing the rollback operation, one processing rule setting device 20a fails before receiving the rollback completion notification from the node 10. It is a sequence diagram showing the operation in the case of. In this case, as in FIG. 22, switching of the processing rule setting device by the system management device 40 and acquisition / collation of journal data are performed, but the rollback processing at the node 10 has been completed normally, so it is activated as it is. Completed.

  FIG. 25 is a sequence diagram showing an operation when a commit OK is not transmitted from one processing rule setting device 20a in response to a commit request after normal setting of a processing rule, as in FIG. 22 (FIG. 22). The difference is that the processing rule setting device of the first cluster has failed before the commit request is received.) The overall operation is the same as that shown in FIG.

  FIG. 26 is a sequence diagram illustrating an operation in the case where there is an abnormality in the processing rule setting status from the node 10 and one of the processing rule setting devices 20a has failed before issuing a rollback instruction. In this case, as in FIG. 22 and FIG. 25, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40, but rollback has already been instructed to the processing rule setting device 20c. Therefore, the path control device 30 instructs the activated processing rule setting device 20b to roll back.

  FIG. 27 is a sequence diagram showing the operation when the processing rule is successfully set but the processing rule setting success notification is not transmitted from one processing rule setting device 20a. The overall operation is the same as that shown in FIGS.

  In FIG. 28, there is an abnormality in the processing rule setting status from the node 10, and a response (processing rule setting status (NG)) is received from one processing rule setting device 20c. It is a sequence diagram showing the operation when there is no response from the device 20a. In this case, as in FIG. 26, switching of the processing rule setting device and acquisition / collation of journal data are performed by the system management device 40, but since the rollback has already been instructed to the processing rule setting device 20c, the route The control device 30 instructs the activated processing rule setting device 20b to roll back.

  FIG. 29 is a sequence diagram showing an operation when the processing rule is normally set but one processing rule setting device 20a cannot receive the processing rule setting status. Also in this case, the overall operation is the same as in FIG.

  FIG. 30 shows that there is an abnormality in the processing rule setting status from the node 10, and a response (processing rule setting status (NG)) is received from one processing rule setting device 20c. FIG. 10 is a sequence diagram showing an operation when the device 20a cannot receive the processing rule setting status and does not receive any response. In this case, as in FIG. 28, switching of the processing rule setting device and acquisition / collation of journal data are performed by the system management device 40, but since the rollback has already been instructed to the processing rule setting device 20c, the route The control device 30 instructs the activated processing rule setting device 20b to roll back.

  In FIG. 31, a response (processing rule setting status (OK)) indicating that the processing rule has been normally set is received from one processing rule setting device 20c, but the other processing rule setting device 20a sets the processing rule. FIG. 10 is a sequence diagram showing an operation when a failure has occurred before and there is no response. In this case, the path control device 30 instructs the processing rule setting device 20c to roll back, as in FIG. In addition, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40. As a result, it is found that the processing rule setting status of the node of the first cluster has already been rolled back. Therefore, the activation completion notification is transmitted as it is.

  In FIG. 32, there is an abnormality in the setting status of the processing rule from the node 10, and a response (processing rule setting status (NG)) is received from one processing rule setting device 20c. The apparatus 20a is a sequence diagram showing an operation when a failure occurs before setting a processing rule and there is no response. In this case, as in FIG. 31, the processing rule setting device 20c is instructed to roll back. In addition, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40. As a result, it is found that the processing rule setting status of the node of the first cluster has already been rolled back. Therefore, the activation completion notification is transmitted as it is.

  In FIG. 33, a response (processing rule setting status (OK)) indicating that the processing rule has been normally set is received from one processing rule setting device 20c, but the other processing rule setting device 20a records the processing rule. FIG. 10 is a sequence diagram illustrating an operation when a failure occurs before reception of a completion notification and there is no response. In this case, the path control device 30 instructs the processing rule setting device 20c to roll back, as in FIG. In addition, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40. As a result, it is found that the processing rule setting status of the node of the first cluster has already been rolled back. Therefore, the activation completion notification is transmitted as it is.

  In FIG. 34, there is an abnormality in the setting status of the processing rule from the node 10, and a response (processing rule setting status (NG)) is received from one processing rule setting device 20c. The apparatus 20a is a sequence diagram showing an operation when a failure occurs before receiving a processing rule recording completion notice and no response is received. In this case, as in FIG. 33, the processing rule setting device 20c is instructed to roll back. In addition, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40. As a result, it is found that the processing rule setting status of the node of the first cluster has already been rolled back. Therefore, the activation completion notification is transmitted as it is.

  In FIG. 35, a response (processing rule setting status (OK)) indicating that the processing rule has been normally set is received from one processing rule setting device 20c, but the other processing rule setting device 20a records the processing rule. FIG. 10 is a sequence diagram showing an operation when a failure has occurred before and there is no response. In this case, the path control device 30 instructs the processing rule setting device 20c to roll back, as in FIG. In addition, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40. As a result, it is found that the processing rule setting status of the node of the first cluster has already been rolled back. Therefore, the activation completion notification is transmitted as it is.

  In FIG. 36, there is an abnormality in the processing rule setting status from the node 10, and a response (processing rule setting status (NG)) is received from one processing rule setting device 20c. The apparatus 20a is a sequence diagram showing an operation in the case where a failure occurs before the processing rule is recorded and there is no response. In this case, as in FIG. 33, the processing rule setting device 20c is instructed to roll back. In addition, switching of the processing rule setting device and journal data acquisition / collation are performed by the system management device 40. As a result, it is found that the processing rule setting status of the node of the first cluster has already been rolled back. Therefore, the activation completion notification is transmitted as it is.

  As is clear from the above description, even if the processing rule setting device fails at any timing, it switches to the standby processing rule setting device and collates with the journal data of the node to determine whether rollback is necessary. It is possible to maintain the consistency of the setting status of processing rules.

  The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments, and further modifications, replacements, and replacements may be made without departing from the basic technical idea of the present invention. Adjustments can be made. For example, in the third embodiment described above, the processing rule setting device operating in the active system has been described as performing the commit. However, as illustrated in FIG. 37, the processing rule waiting in the standby system is performed. The setting device may also commit to the target (fourth embodiment).

Further, in each of the above-described embodiments, a description has been given of a configuration in which one routing control device and two processing rule setting devices are arranged in two clusters, respectively, but this configuration is a simple example of the embodiment of the present invention. This is for explanation. It goes without saying that the number of path control devices and processing rule setting devices can be changed as appropriate in accordance with required specifications required for a communication system to which the present invention is applied.
Each disclosure of the above non-patent document is incorporated herein by reference. Within the scope of the entire disclosure (including claims) of the present invention, the embodiments and examples can be changed and adjusted based on the basic technical concept. Further, various combinations or selections of various disclosed elements are possible within the scope of the claims of the present invention (claims).

Finally, a preferred form of the invention is summarized.
[First embodiment]
(Refer to the communication system according to the first viewpoint)
[Second form]
In the communication system of the first form,
The control device determines whether or not a flow identifier assigned to the processing rule set for the node and a transaction identifier assigned in common to the processing rules associated with each other are included in a response from the node. A communication system for discriminating whether or not individual processing rules are set and whether or not the processing rules associated with each other are set.
[Third embodiment]
In the communication system of the first or second form,
The control device is made redundant;
A communication system that backs up the set processing rule to a control device that stands by as a standby system among the control devices.
[Fourth form]
In the communication system of the third form,
The control device waiting as the standby system continues setting the processing rule to the node based on the setting status of the backup processing rule and the processing rule received from the node when switching to the active state. Or a communication system that performs a rollback operation.
[Fifth embodiment]
In the communication system according to any one of the first to fourth aspects,
The control device calculates a packet transfer route according to a processing rule setting request from an arbitrary node, and creates a processing rule for realizing the packet transfer route; and
A communication system configured to include a plurality of processing rule setting devices that set the processing rules for nodes belonging to a cluster to which the own device belongs among nodes on the packet transfer path.
[Sixth embodiment]
In the communication system of the fifth form,
The node holds a transaction identifier assigned in common to a processing rule associated with the processing rule and a processing rule before update in association with each other,
When an abnormality is detected in a processing rule set in at least one node, the processing rule setting device receives a set processing rule from a processing rule setting device belonging to another cluster and is included in the processing rule A communication system that performs a rollback operation based on a transaction identifier.
[Seventh form]
In the communication system of the fifth or sixth form,
If the routing control device succeeds in setting the processing rules associated with each other, the routing control device requests the processing rule setting devices to commit, and if the commit responses from the processing rule setting devices are not complete, A communication system that performs a back operation.
[Eighth form]
(Refer to the control device according to the second viewpoint)
[Ninth Embodiment]
In the control device of the eighth aspect,
Depending on whether or not the flow identifier assigned to the processing rule set in the node and the transaction identifier assigned in common to the processing rules associated with each other are included in the response from the node, individual processing rules And a control device for determining whether or not the processing rules associated with each other are set.
[Tenth embodiment]
In the control device of the eighth or ninth form,
A control device that is connected to a control device that is on standby as a standby system and causes the control device that is on standby as the standby system to back up the set processing rule.
[Eleventh form]
In the control device of the tenth aspect,
When the control device waiting as the standby system switches to the active state, the setting of the processing rule to the node is continued based on the backup processing rule and the setting state of the processing rule received from the node. A control device that performs a rollback operation.
[Twelfth embodiment]
In the control device according to any one of the eighth to eleventh aspects,
In response to a processing rule setting request from an arbitrary node, a route control device that calculates a packet transfer route and creates a processing rule that realizes the packet transfer route;
A control device configured to include a plurality of processing rule setting devices that set the processing rules for nodes belonging to a cluster to which the device belongs, among nodes on the packet transfer path.
[13th form]
In the control device of the twelfth aspect,
The node holds a transaction identifier assigned in common to a processing rule associated with the processing rule and a processing rule before update in association with each other,
When an abnormality is detected in the processing rule set in at least one node, the processing rule setting device belonging to another cluster receives the set processing rule, and based on the transaction identifier included in the processing rule, A control device that instructs the node to roll back.
[14th form]
In the control device of the twelfth or thirteenth aspect,
When the setting of the processing rules associated with each other is successful, the control device which requests the commit to each processing rule setting device and performs a rollback operation when the commit response from each processing rule setting device is not complete .
[15th form]
(Refer to the node from the third viewpoint)
[Sixteenth embodiment]
In the node of the fifteenth form,
Furthermore, the transaction identifier assigned in common to the processing rule associated with the processing rule and the processing rule before the update are stored in association with each other,
A node that performs a rollback operation based on the transaction identifier.
[17th form]
(Refer to the processing rule setting method from the fourth viewpoint.)
[18th form]
(Refer to the control device program from the fifth viewpoint)
[19th form]
(Refer to the above node program from the fifth viewpoint)

10 node 11 set processing rule 12 flow table setting unit 13, 13A event buffer 14 journal transmission unit 15 flow table 16 packet processing unit 17 packet transmission unit 18 packet receiving unit 20, 20A, 20B control device 20a first cluster processing rule setting Device 20b First cluster processing rule setting device 20c Second cluster processing rule setting device 20d Second cluster processing rule setting device 21 Processing rule setting log 22 Request acceptance unit 23 Cluster management unit 24 Processing rule setting unit 25 Journal confirmation unit 26 Journal acquisition Unit 27 Processing rule setting log storage unit 30 Path control device 31 Main processing unit 32 Processing rule setting unit 33 Transaction confirmation unit 34 Transaction log storage unit 40 System management device

Claims (19)

A plurality of nodes including a packet processing unit that processes a received packet in accordance with a processing rule that associates a process to be applied to a packet with a matching rule for identifying a packet to which the process is applied;
In response to a processing rule setting request from an arbitrary node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for nodes on the packet transfer route, and the processing rules are mutually connected. A controller for recording in association with each other,
The control device inquires a node on the packet transfer path about the setting status of the processing rule, and when an abnormality is detected in the processing rule set in at least one node, the control device relates to the setting in the other node. Roll back processing rules,
A communication system characterized by the above.   The control device determines whether or not a flow identifier assigned to the processing rule set for the node and a transaction identifier assigned in common to the processing rules associated with each other are included in a response from the node. The communication system according to claim 1, wherein it is determined whether or not individual processing rules are set and whether or not the processing rules associated with each other are set. The control device is made redundant;
The communication system according to claim 1 or 2, wherein the set processing rule is backed up by a control device waiting as a standby system among the control devices.   The control device waiting as the standby system continues setting the processing rule to the node based on the setting status of the backup processing rule and the processing rule received from the node when switching to the active state. Or the communication system of Claim 3 which performs rollback operation | movement. The control device calculates a packet transfer route according to a processing rule setting request from an arbitrary node, and creates a processing rule for realizing the packet transfer route; and
5. The apparatus according to claim 1, further comprising: a plurality of processing rule setting devices configured to set the processing rule for a node belonging to a cluster to which the own device belongs among nodes on the packet transfer path. Communication system. The node holds a transaction identifier assigned in common to a processing rule associated with the processing rule and a processing rule before update in association with each other,
When an abnormality is detected in a processing rule set in at least one node, the processing rule setting device receives a set processing rule from a processing rule setting device belonging to another cluster and is included in the processing rule 6. The communication system according to claim 5, wherein the node is instructed to roll back based on a transaction identifier.   If the routing control device succeeds in setting the processing rules associated with each other, the routing control device requests the processing rule setting devices to commit, and if the commit responses from the processing rule setting devices are not complete, The communication system according to claim 5 or 6, wherein a back operation is performed. A plurality of nodes including a packet processing unit that processes a received packet in accordance with a processing rule that associates a process to be applied to a packet with a matching rule for specifying a packet to which the process is applied, and
In response to a processing rule setting request from an arbitrary node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for nodes on the packet transfer route, and the processing rules are mutually connected. Record in association,
Further, the node of the packet transfer path is inquired about the setting status of the processing rule, and when an abnormality is detected in the processing rule set in at least one node, the role of the related processing rule set in the other node Doing back operation,
A control device characterized by.   Depending on whether or not the flow identifier assigned to the processing rule set in the node and the transaction identifier assigned in common to the processing rules associated with each other are included in the response from the node, individual processing rules The control device according to claim 8, wherein it is determined whether or not a processing rule associated with each other is set.   The control device according to claim 8 or 9, wherein the control device is connected to a control device waiting as a standby system and causes the control device waiting as the standby system to back up the set processing rule.   When the control device waiting as the standby system switches to the active state, the setting of the processing rule to the node is continued based on the backup processing rule and the setting state of the processing rule received from the node. The control device according to claim 10, which performs a rollback operation. In response to a processing rule setting request from an arbitrary node, a route control device that calculates a packet transfer route and creates a processing rule that realizes the packet transfer route;
12. A plurality of processing rule setting devices configured to set the processing rule for nodes belonging to a cluster to which the device belongs, among nodes on the packet transfer path. One control device. The node holds a transaction identifier assigned in common to a processing rule associated with the processing rule and a processing rule before update in association with each other,
When an abnormality is detected in the processing rule set in at least one node, the processing rule setting device belonging to another cluster receives the set processing rule, and based on the transaction identifier included in the processing rule, 13. The control device according to claim 12, which instructs a node to roll back.   A request for commit is made to each processing rule setting device when the setting of the processing rules associated with each other is successful, and a rollback operation is performed when a commit response from each processing rule setting device is not available. 12 or 13 control devices. A packet processing unit that processes a received packet in accordance with a processing rule that associates a process to be applied to a packet with a matching rule for identifying a packet to which the process is applied;
In response to an inquiry from the control device according to any one of claims 8 to 14, a flow identifier assigned to the processing rule, and a transaction identifier assigned in common to the processing rule associated with the processing rule, The responding node. Furthermore, the transaction identifier assigned in common to the processing rule associated with the processing rule and the processing rule before the update are stored in association with each other,
The node of claim 15, which performs a rollback operation based on a transaction identifier. A plurality of nodes including a packet processing unit that processes a received packet in accordance with a processing rule that associates a process to be applied to a packet and a matching rule for specifying a packet to which the process is applied; and a connected control device,
In response to a processing rule setting request from the node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for nodes on the packet transfer route, and the processing rules are mutually connected. Associating and recording,
Inquires the node on the packet transfer path about the setting status of the processing rule, and when an abnormality is detected in the processing rule set in at least one node, rollback operation of the related processing rule set in the other node Performing a step,
A processing rule setting method characterized by the above. A plurality of nodes including a packet processing unit that processes a received packet according to a processing rule that associates a process applied to a packet with a matching rule for identifying a packet to which the process is applied, and a connected control device A program to be executed by a computer,
In response to a processing rule setting request from the node, a packet transfer route is calculated, a processing rule for realizing the packet transfer route is set for nodes on the packet transfer route, and the processing rules are mutually connected. A process of recording in association,
Inquires the node on the packet transfer path about the setting status of the processing rule, and when an abnormality is detected in the processing rule set in at least one node, rollback operation of the related processing rule set in the other node Processing to perform
A program for causing the computer to execute. A program to be executed by a computer constituting a node including a packet processing unit that processes a received packet in accordance with a processing rule that associates a process to be applied to a packet and a matching rule for specifying a packet to which the process is applied,
In response to an inquiry from the control device according to any one of claims 8 to 14, a flow identifier assigned to the processing rule, and a transaction identifier assigned in common to the processing rule associated with the processing rule, A program that executes a process that responds.

Images