JP6307932B2 - Packet transfer route acquisition system and packet transfer route acquisition method - Google Patents

Description

  The present invention relates to a packet transfer route acquisition system and a packet transfer route acquisition method.

  In a C / D (Control plane / Data plane) separation type network control system such as OpenFlow, when a large-scale communication network is controlled, distributed management of the network is performed by a plurality of network controllers.

  Assume that a packet is transmitted from a transmission source server to a destination server in a large-scale network of the C / D separation type as described above. In this case, if the network controller that manages the switch to which the source server is connected is different from the network controller that manages the switch to which the destination server is connected, the packet is sent to which switch in the network. The route information indicating which port has been routed is managed in a state of being divided by a plurality of network controllers.

  Therefore, in order to acquire the route information of the packet from the transmission source server to the destination server, it is required to inquire the individual network controller that manages the route information and acquire the route information.

  In addition, the switch may rewrite the packet header part during packet transfer. In that case, it is required to acquire rewrite information of the packet together with the route information and inquire the next network controller about the route information based on the rewritten packet information. Since various procedures are required in this way, it takes a lot of time to acquire route information of packets transferred across different networks.

  In Patent Document 1, a network controller that manages a network in a cluster that realizes communication with another network via a router manages the route information of the network in the own cluster, and further stores the route information with the adjacent network controller. A method for managing path information between clusters by exchanging is described.

  Patent Document 2 describes a method for centrally controlling and managing a virtual network distributed and managed by a plurality of network controllers.

JP 2006-246126 A International Publication WO2013 / 118690

  When the method described in Patent Document 1 is used, the user can acquire route information indicating which router the packet has passed from the transmission source server to the destination server. However, in the intra-cluster network and the inter-cluster network, when a bridge or a layer 2 switch is used between routers, the user cannot obtain route information indicating which bridge the packet has passed through. The reason is that the method described in Patent Document 1 targets only a network constructed by routers.

  Further, the method described in Patent Document 2 does not include a method for acquiring route information of packets flowing through a centrally managed network.

  Accordingly, an object of the present invention is to provide a packet transfer route acquisition system and a packet transfer route acquisition method that can easily acquire a transfer route below a data link layer of a packet transferred via a plurality of networks.

A packet transfer route acquisition system according to the present invention manages a first network and stores first transfer route information which is information of a transfer route in a data link layer or lower of a packet in the first network. A second control which is a first control device including a communication unit and a second network which manages a second network connected to the first network, and which is information on a transfer path of a packet in the second network below the data link layer A second control device including a second management unit that stores path information; an integrated control device that manages the first control device and the second control device and includes a transfer path acquisition unit; the management unit, the second storing transfer path information, the first management unit via a packet after passing through the first network is a packet through the second network, via the packet first A transfer path information, stored in association with the second identification information is identification information of the second transfer path information via packet, transfer route acquisition unit, first through the packet from the first management section The transfer path information and the second identification information are acquired together, and the second transfer path information of the transit packet is acquired from the second management unit based on the acquired second identification information.

The packet transfer route acquisition method according to the present invention is a first control for managing a first network and storing first transfer route information, which is information on a transfer route in a data link layer and below of a packet in the first network. A second network that manages a device and a second network connected to the first network, and stores second transfer route information that is information on a transfer route in a data link layer or lower of a packet in the second network; A packet transfer route acquisition method executed in a packet transfer route acquisition system including an integrated control device that manages the first control device and the second control device, wherein the second control device includes: , the second transfer path information via packet is a packet through the second network after passing through the first network storage, the first controller A first transfer path information via a packet, in association with the second identification information is identification information of the second transfer path information via packet, the integrated control device from the first control device The first transfer path information of the routed packet and the second identification information are acquired together, and the integrated control device performs the second transfer of the routed packet from the second control device based on the acquired second identification information. It is characterized by acquiring route information.

  According to the present invention, it is possible to easily acquire a transfer path below a data link layer of a packet transferred via a plurality of networks.

It is a block diagram which shows the structural example of 1st Embodiment of the packet transfer path | route acquisition system by this invention. It is explanatory drawing which shows the packet reception switch, packet reception port, packet transmission switch, and packet transmission port under a network controller. 3 is a block diagram illustrating a configuration example of an integrated network controller 4. FIG. 3 is a block diagram illustrating a configuration example of a first network controller 5. FIG. 3 is a block diagram illustrating a configuration example of a second network controller 6. FIG. It is explanatory drawing which shows an example of data flow information. It is explanatory drawing which shows the example of the control packet which a control packet production | generation part produces | generates. It is explanatory drawing which shows the example of the conversion packet which a control packet receiving part produces | generates. It is explanatory drawing which shows the structural example of the virtual network which connects a transmission source server and a destination server so that communication is possible. It is a flowchart which shows operation | movement of a network controller when a packet newly flows into a network. It is explanatory drawing which shows the example of the control packet which a control packet production | generation part produces | generates, and the control packet which a control packet reception part produces | generates. It is a flowchart which shows operation | movement of the network controller with respect to the transmitted control packet. It is a flowchart which shows the operation | movement of the network controller with respect to the transmitted packet. It is explanatory drawing which shows the example of the control packet which a control packet production | generation part produces | generates, and the conversion packet which a control packet reception part produces | generates. It is a flowchart which shows operation | movement of the network controller with respect to the transmitted control packet. It is a flowchart which shows operation | movement of the integrated network controller when acquiring a transfer path | route. It is a block diagram which shows the outline | summary of the packet transfer path | route acquisition system by this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration example of a first embodiment of a packet transfer route acquisition system according to the present invention. The packet transfer route acquisition system 1 shown in FIG. 1 includes switches 111 to 124, a transmission source server 2, a destination server 3, an integrated network controller 4, a first network controller 5, and a second network controller 6. including.

  The packet transfer path acquisition system 1 employs a C / D separation type network control system such as OpenFlow, for example.

  The transmission source server 2 has a function of transmitting a packet. The destination server 3 has a function of receiving a packet transmitted by the transmission source server 2.

  The switches 111 to 114 have a function of processing or forwarding packets according to the contents set from the first network controller 5. In addition, the switches 121 to 124 have a function of processing or transferring a packet according to the contents set by the second network controller 6.

  Note that the switches 111 to 114 are switches under the first network controller 5. FIG. 2 is an explanatory diagram showing a packet reception switch, a packet reception port, a packet transmission switch, and a packet transmission port under the network controller.

  As shown in FIG. 2A, among the switches under the first network controller 5, the end switch that first receives a packet is called an Ingress switch. A port that receives a packet in the Ingress switch is referred to as an Ingress port.

  Also, as shown in FIG. 2A, among the switches under the first network controller 5, the switch at the end that processes the packet last transferred to the destination server 3 or a switch under a different network controller is Egress. Called a switch. Also, a port that transmits a packet in the Egress switch is called an Egress port.

  When the Ingress switch receives the packet, the Ingress switch processes the packet according to the packet processing information set by the network controller. However, if the processing for the received packet is not set by the network controller, the Ingress switch notifies the first network controller 5 of a new packet message including the received packet and related information.

  As described above, the Ingress switch, the Ingress port, the Egress switch, and the Egress port have been described using the switches under the first network controller 5. As shown in FIG. 2B, the switch under the second network controller 6 similarly refers to the end switch and the reception port that receive the packet first as an Ingress switch and an Ingress port, respectively. Further, the end switch and the transmission port to be processed last are referred to as an Egress switch and an Egress port, respectively.

  FIG. 3 is a block diagram illustrating a configuration example of the integrated network controller 4. As shown in FIG. 3, the integrated network controller 4 includes a network setting unit 41 and a transfer path display unit 42.

  The integrated network controller 4 has a function as a meta controller that manages a plurality of network controllers. In the present embodiment, the integrated network controller 4 manages the first network controller 5 and the second network controller 6.

  The network setting unit 41 has a function of notifying the first network controller 5 and the second network controller 6 under management of network settings. Each network controller controls a switch under each network controller based on the notified network setting.

  The transfer path display unit 42 has a function of inquiring of the subordinate first network controller 5 and the second network controller 6 and acquiring a data flow in order to display the packet transfer path.

  In order to acquire the data flow, the transfer path display unit 42 transmits the MAC (Media Access Control) of the transmission source server 2 to the first network controller 5 that manages the switch to which the transmission source server 2 is connected. ) Address, IP (Internet Protocol) address, and VLAN (Virtual Local Area Network) ID are requested to request a data flow. The transfer path display unit 42 acquires the data flow from the first network controller 5 and the data flow ID in the adjacent second network controller 6.

  Next, the transfer path display unit 42 requests a data flow from the second network controller 6 based on the acquired data flow ID in the second network controller 6. The transfer path display unit 42 acquires the data flow corresponding to the data flow ID from the second network controller 6. By combining a series of data flows acquired by the above processing, the transfer route display unit 42 obtains and displays the transfer route of the packet from the transmission source server 2.

  FIG. 4 is a block diagram illustrating a configuration example of the first network controller 5. FIG. 5 is a block diagram illustrating a configuration example of the second network controller 6. The first network controller 5 and the second network controller 6 have a function of controlling the switches under each network controller based on the network settings acquired from the integrated network controller 4.

  As shown in FIG. 4, the first network controller 5 includes a data flow storage unit 51, a boundary port storage unit 52, a control packet storage unit 53, a data flow management unit 54, a switch setting unit 55, a packet And a processing unit 56. As shown in FIG. 5, the second network controller 6 includes a data flow storage unit 61, a boundary port storage unit 62, a control packet storage unit 63, a data flow management unit 64, and a switch setting unit 65. And a packet processing unit 66.

  The data flow storage unit 51 stores information related to the data flow generated by the first network controller 5. The data flow is information indicating how the network controller processes a packet received in the new packet message. The data flow includes packet transfer route information, processing applied to the packet, conditions of the packet to be applied (match condition), and the like.

  An example of data flow information stored in the data flow storage unit 51 is shown in FIG. FIG. 6 is an explanatory diagram showing an example of data flow information.

  As shown in FIG. 6, the data flow information includes a data flow ID, a data flow, and a backward data flow ID.

  The data flow ID indicates the data flow that is the target of the corresponding data flow information. The data flow is a generated data flow corresponding to the data flow ID.

  The backward data flow ID is a data flow ID corresponding to a flow for flowing a packet when a packet according to the flow corresponding to the data flow ID further flows through a network under management of the backward network controller. The backward data flow ID is managed by the backward network controller. Depending on the network settings, there may be a plurality of backward flows for one flow. In that case, a plurality of backward data flow IDs are registered in the data flow information.

  The boundary port storage unit 52 has a function of storing information on boundary ports connected to switches under different network controllers among the ports of the switches under the first network controller 5. Information indicating which port is a boundary port is included in the network setting notified by the integrated network controller 4. In the configuration example of the system illustrated in FIG. 1, the Egress port of the switch 114 corresponds to a boundary port.

  The control packet storage unit 53 has a function of temporarily storing control packets transmitted and received between different network controllers. The control packet stored in the control packet storage unit 53 is a control packet transmitted from the forward network controller. A data flow ID related to the flow of the forward network controller is stored in the payload portion of the stored control packet.

  When the first network controller 5 receives a new packet message from the Ingress switch, the data flow management unit 54 has a function of generating a data flow including a transfer path of a packet included in the message, a processing content for the packet, and the like. . The data flow management unit 54 stores the generated data flow in the data flow storage unit 51 together with a data flow ID for identifying each data flow.

  When the first network controller 5 receives a new packet message from the Ingress switch, the switch setting unit 55 sets the packet processing information to the switch in the route according to the packet transfer route obtained by the data flow management unit 54. It has a function.

  In addition, when the first network controller 5 is activated, the switch setting unit 55 refers to the boundary port storage unit 52 to the switch 114 that manages the boundary port, “when a control packet is received. Then, the processing information “notify the first network controller 5 of the received packet information as a new packet message” is set.

  The packet processing unit 56 includes an output packet generation unit 561, a control packet generation unit 562, and a control packet reception unit 563. As illustrated in FIG. 5, the packet processing unit 66 includes an output packet generation unit 661, a control packet generation unit 662, and a control packet reception unit 663, similarly to the packet processing unit 56.

  When the first network controller 5 receives a new packet message from the Ingress switch, the output packet generation unit 561 applies the processing content to the packet obtained by the data flow management unit 54 to the packet included in the message. By applying the processing content, the output packet generator 561 generates an output packet and notifies the Egress switch.

  The control packet generation unit 562 has a function of generating and transmitting a control packet. The control packet generation unit 562 refers to the boundary port storage unit 52 when the first network controller 5 receives a new packet message from the Ingress switch.

  When the packet received in the new packet message is a packet transferred from a switch under the front network controller or a packet transferred to a switch under the back network controller, the control packet generator 562 Generate and send. That is, the neighboring network is notified that a new data flow has been generated by the first network controller 5.

  When the received packet is a packet transferred from the forward network controller, the control packet generation unit 562 generates a control packet. Then, the control packet generation unit 562 transmits the generated control packet from the Ingress port.

  FIG. 7 is an explanatory diagram illustrating an example of a control packet generated by the control packet generator. As shown in FIG. 7A, in the packet header portion of the control packet to be transmitted, the source MAC address is the destination MAC address of the received packet, and the source IP address is the destination IP address of the received packet. The destination L4 port number of the received packet is set as the source layer 4 (hereinafter referred to as L4) port number.

  Also, in the packet header part of the control packet, the source MAC address of the received packet is the destination MAC address, the source IP address of the received packet is the destination IP address, and the received packet is the destination L4 port number. A dedicated ether type (hereinafter referred to as a dedicated ether type) is set to the Ethernet (registered trademark) type number (hereinafter referred to as an ether type) as the transmission source L4 port number.

  In the field of the packet header part other than the above, the same value as the received packet is set. The ether type is managed by IANA (Internet Assigned Numbers Authority). However, in the present embodiment, a dedicated ether type that is not used in IANA is used. In this way, the control packet generation unit 562 generates a control packet by switching the transmission source and destination of the received packet.

  In this embodiment, the packet ether type is used as a means for identifying the control packet, but other fields in the packet header may be used.

  When setting a value in the payload portion of the control packet to be transmitted, the control packet generation unit 562 checks whether a control packet having the same packet header portion as the received packet is stored in the control packet storage unit 53.

  When the control packet is stored, the control packet generation unit 562 displays the data flow ID of the payload portion of the stored control packet and the data flow data generated by the data flow management unit 54 for the received packet. Two data flow IDs, the flow ID, are set in the payload portion. After transmitting the set control packet, the control packet generation unit 562 deletes the control packet stored in the control packet storage unit 53.

  When the control packet is not stored, the control packet generator 562 sets only the data flow ID of the data flow generated by the data flow manager 54 for the received packet in the payload portion.

  Further, when the received packet is a packet transferred to the rear network controller, the control packet generation unit 562 generates a control packet. Then, the control packet generation unit 562 transmits the generated control packet from the Egress port.

  As shown in FIG. 7B, the packet header part of the transmitted control packet is set to the same value as the value of the packet header part of the output packet except for the ether type. A dedicated ether type is set as the ether type. As a result, a control packet having the same value in the packet header portion except for the ether type and the value in the packet header portion of the output packet transferred to the switch under the subordinate network controller is generated.

  The control packet generation unit 562 sets the data flow ID of the data flow generated by the data flow management unit 54 for the received packet in the payload portion of the control packet to be transmitted. Furthermore, the control packet generator 562 also sets a response required flag in the control packet.

  The required response flag is information indicating that the control packet in which the required response flag is set is a control packet transmitted from the front network controller to the rear network controller. The network controller that has received the control packet in which the response required flag is set transmits a control packet for response.

  When the first network controller 5 receives a new packet message from the Ingress switch when the first network controller 5 receives a new packet message, the control packet receiving unit 563 has a function of performing control packet reception processing when the ether type of the packet included in the message is a dedicated ether type. Have.

  If the received control packet has a response required flag, it means that the received control packet is a control packet transmitted by the forward network controller. In this case, the control packet receiving unit 563 stores the received control packet in the control packet storage unit 53. After saving, the control packet receiving unit 563 checks whether or not the control packet is still stored in the control packet storage unit 53 after a predetermined time has elapsed. The predetermined time is, for example, 10 seconds.

  If the control packet is not already stored, a new data flow is generated during a predetermined time, and the control packet accompanying the data flow generation is already transmitted to the forward network controller. Thereafter, the control packet receiving unit 563 does not transmit the control packet.

  When the control packet is still stored, the control packet receiving unit 563 compares the match condition of each data flow stored in the data flow storage unit 51 with the packet header part of the received control packet. By comparing, the control packet receiving unit 563 confirms whether there is a data flow corresponding to the flow through which the received control packet flows among the data flows managed by the first network controller 5.

  If there is a matching data flow, the data flow generated by the forward network controller is connected to the existing data flow of the first network controller 5. The control packet receiving unit 563 transmits a control packet for response including information on the matched data flow to the forward network.

  As shown in FIG. 7A, in the packet header portion of the control packet for response, the destination MAC address of the received control packet is the source MAC address, and the destination IP of the received control packet is the source IP address. The address is set to the destination L4 port number of the received control packet as the source L4 port number.

  Also, in the packet header part of the response control packet, the destination MAC address is the source MAC address of the received control packet, and the destination IP address is the source IP address of the received control packet is the destination L4 port number. Is the source L4 port number of the received control packet, and the dedicated ether type is set as the ether type.

  In the field of the packet header part other than the above, the same value as the received control packet is set. Thus, the control packet receiving unit 563 generates a control packet by switching the transmission source and destination of the received control packet.

  The control packet receiving unit 563 sets the data flow ID of the forward network controller stored in the payload part of the received control packet and the data flow ID of the data flow matched by comparison in the payload part of the control packet for response. Set.

  When there is no matching data flow, when a data flow that matches the control packet is newly created, a control packet accompanying the data flow creation is transmitted to the forward network controller. Therefore, the control packet receiving unit 563 does not transmit a control packet.

  If the received control packet does not have a response required flag, it means that the received control packet is a control packet transmitted by the rear network controller. In this case, the control packet receiving unit 563 refers to the data flow ID included in the payload portion of the received control packet.

  When the data flow ID in the first network controller 5 and the data flow ID in the rear network controller are stored in the payload portion, it means that the received control packet is a response control packet. In this case, the control packet receiving unit 563 stores the backward data flow ID of the data flow information stored in the data flow storage unit 51 and corresponding to the data flow ID stored in the payload unit in the first network controller 5. As described above, the data flow ID in the rear network controller included in the payload portion is stored.

  If only the data flow ID in the backward network controller is stored in the payload part, it means that a new data flow is generated in the backward network controller. In this case, the control packet receiving unit 563 associates the data flow ID of the rear network controller with the existing data flow of the first network controller 5.

  FIG. 8 is an explanatory diagram illustrating an example of a converted packet generated by the control packet receiving unit. As illustrated in FIG. 8, the control packet receiving unit 563 refers to the packet header portion of the received control packet and generates a converted packet in which the transmission source and the destination are switched.

  Based on the packet header condition of the generated converted packet and the process applied to the packet for each data flow stored in the data flow storage unit 51, the control packet receiving unit 563 stores the packet in the payload part. The data flow in the first network controller 5 associated with the stored data flow ID of the rear network controller is obtained.

  The control packet receiving unit 563 stores the data flow ID in the rear network controller stored in the payload portion as the rear data flow ID of the data flow information corresponding to the obtained data flow ID.

  The data flow storage unit 61, the boundary port storage unit 62, the control packet storage unit 63, the data flow management unit 64, the switch setting unit 65, and the packet processing unit 66 included in the second network controller 6 shown in FIG. The same processing as the data flow storage unit 51, boundary port storage unit 52, control packet storage unit 53, data flow management unit 54, switch setting unit 55, and packet processing unit 56 is performed. The output packet generator 661, the control packet generator 662, and the control packet receiver 663 included in the packet processor 66 are the same as the output packet generator 561, the control packet generator 562, and the control packet receiver 563, respectively. Therefore, the description of each part included in the second network controller 6 is omitted.

  In the packet transfer route acquisition system 1 according to the present embodiment, the switches 111 to 124, the transmission source server 2, the destination server 3, the integrated network controller 4, the first network controller 5 and the second network controller 6 are, for example, This is realized by a CPU (Central Processing Unit) that executes processing according to a program. Further, the switches 111 to 124, the transmission source server 2, the destination server 3, the integrated network controller 4, the first network controller 5 and the second network controller 6 may be realized by hardware.

  The network setting unit 41, the transfer path display unit 42, the data flow management unit 54, the switch setting unit 55, the packet processing unit 56, the data flow management unit 64, the switch setting unit 65, and the packet processing unit 66 are, for example, program controlled. It implement | achieves by CPU which performs a process according to this.

  In addition, the data flow storage unit 51, the boundary port storage unit 52, the control packet storage unit 53, the data flow storage unit 61, the boundary port storage unit 62, and the control packet storage unit 63 are realized by, for example, a RAM (Random Access Memory). The

  Hereinafter, the operation of the packet transfer route acquisition system 1 of the present embodiment will be described. Here, in the network configuration shown in FIG. 1, from the transmission source server 2 whose MAC address is MAC1, IP address is IP1, and VLAN ID is VLAN1, destination whose MAC address is MAC2, IP address is IP2, and VLAN ID is VLAN2. A case where a packet is transferred to the server 3 will be described as an example.

  FIG. 9 is an explanatory diagram showing a configuration example of a virtual network that connects the transmission source server and the destination server so that they can communicate with each other. As shown in FIG. 9, it is assumed that a virtual bridge is set as the network setting of the first network controller 5 and a virtual router is set as the network setting of the second network controller 6.

  As shown in FIG. 9, the MAC address assigned to the port on the virtual bridge side of the virtual router is MAC1 ', and the MAC address assigned to the port on the destination server 3 side of the virtual router is MAC2'. The VLAN ID used in the link between the virtual bridge and the virtual router is assumed to be VLAN 1 '. Each of the virtual bridge and the virtual router shown in FIG. 9 converts the VLAN ID and the MAC address.

  When the first network controller 5 and the second network controller 6 are activated, the switch setting unit 55 and the switch setting unit 65 refer to the boundary port storage unit 52 and the boundary port storage unit 62, respectively. Then, the switch setting unit 55 and the switch setting unit 65 “notify the network controller of the received packet information as a new packet message when a control packet is received” to the switch managing the boundary port. Suppose you set the processing information.

  FIG. 10 is a flowchart showing the operation of the network controller when a new packet flows into the network.

  When the transmission source server 2 transmits a packet to the destination server 3 (step A1), the switch 111 which is an Ingress switch in the first network controller 5 receives the transmitted packet (step A2).

  The switch 111 that has received the packet checks whether or not packet processing information has already been set from the first network controller 5 (step A3).

  If packet processing information has already been set (YES in step A3), the switch 111 transfers the packet to the switch 114 that is an Egress switch based on the set processing (step A4). Next, the packet is transferred from the switch 114 to the switch 121 that is an Ingress switch under the second network controller 6 (step A11). After being transferred, the switch 114 ends the process.

  When the packet processing information is not set (NO in step A3), the switch 111 notifies the first network controller 5 of a new packet message (step A5).

  When the data flow management unit 54 receives a new packet message, the data flow management unit 54 generates a data flow including the transfer route of the packet included in the message, the processing content for the packet, and the like. The data flow management unit 54 stores the generated data flow in the data flow storage unit 51 together with the data flow ID for identifying each data flow (step A6).

  Next, the switch setting unit 55 sets packet processing information to the switches in the route based on the generated data flow (step A7). Next, the output packet generator 561 generates an output packet by applying the processing content to the packet included in the generated data flow to the packet included in the notified new packet message (step A8). .

  Next, the control packet generator 562 generates a control packet based on the received packet. FIG. 11 is an explanatory diagram illustrating an example of a control packet generated by the control packet generator and a control packet generated by the control packet receiver.

  Since the received packet is a packet transferred to the switch under the second network controller 6, the control packet generator 562 generates a control packet as shown in FIG. When generating the control packet, the control packet generation unit 562 sets the data flow ID of the generated data flow in the payload portion. After the generation, the control packet generation unit 562 transmits the control packet from the Egress port (step A9).

  Next, the output packet generator 561 notifies the Egress switch of the output packet generated in step A8 (step A10). Through the above operation, the packet transmitted from the transmission source server 2 to the destination server 3 is transferred from the Egress switch under the first network controller 5 to the switch 121 which is an Ingress switch under the second network controller 6. (Step A11). After the transfer, the output packet generator 561 ends the process.

  Next, processing for the control packet transmitted in step A9 when a new data flow is created by the first network controller 5 will be described. FIG. 12 is a flowchart showing the operation of the network controller with respect to the transmitted control packet.

  The control packet transferred from the Egress switch under the first network controller 5 is received by the switch 121 which is an Ingress switch under the second network controller 6 (step B1).

  The switch 121 notifies the second network controller 6 of a new packet message related to the received control packet based on the processing information set when the second network controller 6 is activated (step B2).

  Next, the control packet receiving unit 663 stores the received control packet in the control packet storage unit 63 (step B3). After a predetermined time has elapsed (step B4), the control packet receiving unit 663 checks whether or not the control packet is stored in the control packet storage unit 63 (step B5).

  When the control packet has not been stored (NO in step B5), the control packet receiving unit 663 does not perform processing on the control packet.

  When the control packet is still stored (YES in step B5), the control packet receiving unit 663 uses the match condition of each data flow stored in the data flow storage unit 61 and the packet header part of the received control packet. And compare. By comparing, the control packet receiving unit 663 confirms whether or not there is a data flow corresponding to the flow through which the received control packet flows among the data flows managed by the second network controller 6 ( Step B6).

  When there is a data flow (YES in step B6), the control packet receiving unit 663 creates a control packet for response as shown in FIG. When generating the control packet, the control packet receiving unit 663 includes the data flow ID in the first network controller 5 stored in the payload part of the received control packet in the payload part of the control packet for response, and the step Two data flow IDs corresponding to the data flow in the second network controller 6 extracted in B6 are set.

  The control packet receiving unit 663 transmits the created response control packet to the first network (step B7). After the transmission, the control packet receiving unit 663 ends the process.

  If there is no data flow (NO in step B6), the control packet receiving unit 663 ends the process without performing anything on the control packet.

  Next, processing for a packet transmitted from the transmission source server 2 to the destination server 3 and transferred to the switch 121 that is an Ingress switch under the second network controller 6 will be described. FIG. 13 is a flowchart showing the operation of the network controller for the transmitted packet.

  The switch 121, which is an Ingress switch in the second network controller 6, receives the transferred packet (step C1). The switch 121 checks whether or not packet processing information has already been set from the second network controller 6 (step C2).

  If packet processing information has already been set (YES in step C2), the switch 121 transfers the packet to the switch 124 that is an Egress switch based on the set processing information (step C3). Next, the switch 124 transfers the packet to the destination server 3 (step C13). After the packet is transferred, the switch 124 ends the process.

  If packet processing information is not set (NO in step C2), the switch 121 notifies the second network controller 6 of a new packet message (step C4).

  When the data flow management unit 64 receives a new packet message, the data flow management unit 64 generates a data flow including the transfer route of the packet included in the message and the processing content for the packet. The data flow management unit 64 stores the generated data flow in the data flow storage unit 61 together with the data flow ID for identifying each data flow (step C5).

  Next, the switch setting unit 65 sets the packet processing information to the switch in the route based on the generated data flow (step C6). Next, the output packet generation unit 661 generates an output packet by applying the processing content to the packet included in the generated data flow to the packet included in the notified new packet message (step C7). .

  Next, the control packet generator 662 checks whether or not a control packet having the same packet header part as the packet header part of the packet received in the new packet message is stored in the control packet storage part 63 (step C8).

  If the control packet is stored (YES in step C8), the control packet generation unit 662 performs data flow management for the data flow ID included in the payload portion of the stored control packet and the received packet. A control packet in which two data flow IDs corresponding to the data flow generated by the unit 64 are set in the payload portion is generated.

  After the generation, the control packet generator 662 transmits the control packet from the Ingress port (step C9). Further, the control packet generator 662 deletes the stored control packet (step C10).

  If the control packet is not stored (NO in step C8), the control packet generator 662 uses only the data flow ID corresponding to the data flow generated by the data flow manager 64 for the received packet in the payload portion. Generate the set control packet.

  FIG. 14 is an explanatory diagram illustrating an example of a control packet generated by the control packet generator and a converted packet generated by the control packet receiver. The control packet generator 662 generates a control packet as shown in FIG. After the generation, the control packet generator 662 transmits the control packet from the Ingress port (step C11).

  Next, the output packet generator 661 notifies the output switch generated in step C7 to the Egress switch (step C12). Through the above operation, the packet transmitted from the transmission source server 2 to the destination server 3 is transferred from the Egress switch under the second network controller 6 to the destination server 3 (step C13). After the packet is transferred, the output packet generator 661 ends the process.

  Next, processing for control packets transmitted from the second network toward the first network in Step B7, Step C9, and Step C11 will be described. FIG. 15 is a flowchart showing the operation of the network controller with respect to the transmitted control packet.

  The control packet transferred from the Ingress switch under the second network controller 6 is received by the switch 114 which is an Egress switch under the first network controller 5 (step D1).

  The switch 114 notifies the first network controller 5 of a new packet message relating to the received control packet based on the processing information set when the first network controller 5 is activated (step D2).

  Next, the control packet receiving unit 563 refers to the payload portion of the received control packet and determines whether or not two data flow IDs in the first network controller 5 and data flow ID in the rear network controller are stored. Confirm (step D3).

  When two data flow IDs are stored (step D3-2), the control packet receiving unit 563 is the first network controller 5 stored in the payload unit and stored in the data flow storage unit 51. As the backward data flow ID of the data flow information corresponding to the data flow ID, the data flow ID in the backward network controller saved in the payload portion is saved (step D4). After the saving, the control packet receiving unit 563 ends the process.

  When only one data flow ID is stored (1 in step D3), the control packet receiving unit 563 refers to the packet header part of the received control packet, and transmits the source as shown in FIG. Then, a converted packet in which the destination is exchanged is generated (step D5).

  Next, the control packet receiving unit 563 generates a payload based on the packet header portion of the generated converted packet and the process applied to the packet and the packet matching condition of each data flow stored in the data flow storage unit 51. The data flow in the first network controller 5 associated with the data flow ID of the rear network controller stored in the section is obtained (step D6).

  As the backward data flow ID of the obtained data flow, the control packet receiving unit 563 stores the data flow ID in the backward network controller stored in the payload portion (step D7). After the saving, the control packet receiving unit 563 ends the process.

  In this way, by transmitting and receiving control packets between network controllers, the packet transfer route acquisition system grasps the relationship between flows in advance.

  Next, the operation of the integrated network controller 4 for obtaining the transfer path will be described. FIG. 16 is a flowchart illustrating the operation of the integrated network controller when acquiring a transfer path.

  The transfer path display unit 42 of the integrated network controller 4 sends the MAC address (MAC1) and IP of the transmission source server 2 to the first network controller 5 that manages the switch 111 to which the transmission source server 2 is connected. An address (IP1) and a VLAN ID (VLAN1) are respectively designated and a data flow is requested. By designating these pieces of information, the transfer path display unit 42 acquires one or more data flows originating from the transmission source server 2 and data flow IDs in adjacent network controllers (step E1).

  Next, the transfer path display unit 42 confirms the number of acquired data flow IDs in the adjacent network controller (step E2). If the number of data flow IDs is 0 (0 in step E2), it means that all flows are terminated in the network managed by the network controller that acquired the data flow. When the data flow ID is not acquired, the transfer path display unit 42 ends the process.

  When the number of data flow IDs in the acquired adjacent network controller is 1 or more (1 or more in Step E2), the transfer path display unit 42 determines whether the first data flow ID is based on the processing content for the packet included in the acquired data flow. The MAC address (MAC1), the IP address (IP1), and the VLAN ID (VLAN1 ′) at the time when the packet passes through each switch under the network controller 5 is obtained (step E3). The transfer path display unit 42 specifies each obtained information and requests a data flow from the adjacent second network controller 6.

  The transfer path display unit 42 acquires the data flow corresponding to the data flow ID acquired in the first step E1 and the data flow ID in the adjacent network controller from the second network controller 6.

  Since the number of data flow IDs in the adjacent network controller acquired from the second network controller 6 is 0 (0 in step E2), the transfer path display unit 42 ends the data flow request to the adjacent network controller. .

  The transfer path display unit 42 can determine the transfer path of the packet from the transmission source server 2 to the destination server 3 by combining the acquired data flows.

  When the packet transfer route acquisition system of this embodiment is used, a packet transfer route in a large-scale network managed by a plurality of network controllers can be displayed without taking much time. The reason is that the packet transfer path acquisition system manages the backward data flow ID for each data flow in the data flow storage unit, and the transfer path display unit acquires the data flow from the first network controller. This is because the data flow ID in the network controller is also acquired, and the data flow is acquired based on the acquired data flow ID for the second network controller.

  In the packet transfer route acquisition system of the present embodiment, when the network controller receives a new packet message from the Ingress switch and generates a data flow including the packet transfer route and the processing content for the packet, A control packet including a data flow ID for identifying the generated data flow is transmitted. In addition, when a control packet is received from a forward network closer to the transmission source server, a packet flowing through the forward network flows according to which flow managed by the own network controller based on data included in the received packet. The data flow ID corresponding to the obtained flow and the data flow ID in the forward network controller included in the received control packet are included in the control packet and transmitted to the forward network. In this way, the relationship between flows is grasped in advance by transmitting and receiving control packets between network controllers, so even when a user receives an inquiry about transfer route information, the user can send information without taking time. Can present.

  Next, the outline of the present invention will be described. FIG. 17 is a block diagram showing an outline of a packet transfer route acquisition system according to the present invention. The packet transfer route acquisition system 10 according to the present invention manages a first network and stores first transfer route information which is information of a transfer route in a data link layer or lower of a packet in the first network. The first control device 50 (for example, the first network controller 5) including the management unit 57 (for example, the data flow storage unit 51) and the second network connected to the first network are managed. 2nd control apparatus 60 containing the 2nd management part 67 (for example, data flow memory | storage part 61) which memorize | stores the 2nd transfer path | route information which is the information of the transfer path | route below the data link layer of the packet in 2 networks. (For example, the second network controller 6), the first control device 50, and the second control device 60 are managed, and the transfer route acquisition unit 43 (for example, And the integrated control device 40 (for example, the integrated network controller 4) including the transfer path display unit 42), and the second management unit 67 performs the second processing for the packets that pass through the first network and the second network. The transfer path information is stored, and the first management unit 57 stores the first transfer path information for the packet in association with the second identification information that is the identification information of the second transfer path information, and transfers the transfer information. The route acquisition unit 43 acquires the first transfer route information and the second identification information from the first management unit 57 together, and based on the acquired second identification information, the route acquisition unit 43 receives the second transfer information from the second management unit 67. 2 transfer path information is acquired.

  With such a configuration, the packet transfer path acquisition system can easily acquire transfer paths below the data link layer of packets transferred via a plurality of networks.

  The second management unit 67 transmits a control packet including the second identification information to the first network, and the first management unit 57 acquires the second identification information acquired from the transmitted control packet. May be associated with the first transfer path information.

  With such a configuration, the packet transfer path acquisition system can grasp the relationship between data flows in advance by transmitting and receiving control packets between network controllers.

  In addition, when a packet passing through the first network and the second network passes through the first network for the first time, the first management unit 57 uses the first information that is identification information of the first transfer path information of the packet. When the control packet including the identification information is transmitted to the second network, and the control packet including the first identification information and the second identification information is transmitted to the first network, the control packet includes the first identification information. The second identification information may be associated with the corresponding first transfer path information.

  With such a configuration, the packet transfer path acquisition system can associate each data flow in a plurality of networks through which the packet passes even when the network controller creates a data flow of the packet.

  In addition, the first management unit 57 and the second management unit 67 may create a control packet to be transmitted based on information on packets passing through the first network and the second network.

  With such a configuration, the packet transfer path acquisition system can cause the network controller that has received the control packet to search for the data flow corresponding to the control packet in the same manner as when searching for the data flow applied to the packet.

  In addition, the first management unit 57 and the second management unit 67 may manage the network using a data flow.

  With such a configuration, the packet transfer path acquisition system can acquire the packet transfer path below the data link layer from the packet transfer path information included in the data flow.

  The present invention is suitably applied to the field of SDN (Software Defined Networking) including OpenFlow.

1, 10 Packet transfer route acquisition system 2 Source server 3 Destination server 4 Integrated network controller 5 First network controller 6 Second network controller 40 Integrated control device 41 Network setting unit 42 Transfer route display unit 43 Transfer route acquisition unit 50 First control device 51, 61 Data flow storage unit 52, 62 Boundary port storage unit 53, 63 Control packet storage unit 54, 64 Data flow management unit 55, 65 Switch setting unit 56, 66 Packet processing unit 57 First management Unit 60 second control device 67 second management unit 111-124 switch 561, 661 output packet generation unit 562, 662 control packet generation unit 563, 663 control packet reception unit

Claims (10)

A first control unit that includes a first management unit that manages a first network and stores first transfer path information that is information of a transfer path below a data link layer of a packet in the first network; ,
A second network which manages a second network connected to the first network and stores second transfer path information which is information of a transfer path below a data link layer of a packet in the second network; A second control device including a management unit;
An integrated control device that manages the first control device and the second control device and includes a transfer path acquisition unit;
The second management unit stores second transfer path information of a transit packet that is a packet that passes through the second network after passing through the first network;
The first management section, the first and the transfer route information, and the second transfer path information of the identification information and is in association with the second identification information storage of the via packets of the via packet,
The transfer path acquisition unit acquires the first transfer path information of the routed packet and the second identification information from the first management unit together, and based on the acquired second identification information, A packet transfer route acquisition system, wherein the second transfer route information of the routed packet is acquired from a second management unit. The second management unit transmits a control packet including the second identification information to the first network,
The packet transfer path acquisition system according to claim 1, wherein the first management unit associates the second identification information acquired from the transmitted control packet with the first transfer path information. First management unit, via if packet passes through the first first network, the first of said through packet transfer route information first identification information identifying information of the control packet second including send to the network, when said first identification information and the control packet including a second identification information is transmitted to the first network, the first transfer path information corresponding to the first identification information The packet transfer path acquisition system according to claim 2, wherein the second identification information is associated with the packet transfer path acquisition system. A first management unit and the second management unit, the packet transfer route acquisition system according to claim 2 or claim 3 creates a control packet to be transmitted based on information via packets. The packet transfer path acquisition system according to any one of claims 1 to 4, wherein the first management unit and the second management unit manage a network using a data flow. A first control device that manages a first network and stores first transfer path information that is information of a transfer path below a data link layer of a packet in the first network; and the first network; A second control device that manages a second network connected thereto and stores second transfer path information, which is information of a transfer path below a data link layer of a packet in the second network; A packet transfer route acquisition method executed in a packet transfer route acquisition system including an integrated control device that manages one control device and the second control device,
The second control device stores second transfer path information of a routed packet that is a packet that passes through the second network after passing through the first network;
Said first controller, a first and a transfer path information, and the second transfer path information of the identification information and is in association with the second identification information storage of the via packets of the via packet,
The integrated control device acquires the first transfer route information of the route packet and the second identification information together from the first control device,
The said integrated control apparatus acquires the 2nd transfer path information of the said transit packet from the said 2nd control apparatus based on the acquired said 2nd identification information. The packet transfer path | route acquisition method characterized by the above-mentioned. The second control device transmits a control packet including the second identification information to the first network,
The packet transfer route acquisition method according to claim 6, wherein the first control device associates the second identification information acquired from the transmitted control packet with the first transfer route information. The first control device, via if packet passes through the first first network, the first of said through packet transfer route information first identification information identifying information of the control packet second including To the network,
It said first controller, when said first identification information and the control packet including a second identification information is transmitted to the first network, the first corresponding to the first identification information The packet transfer route acquisition method according to claim 7, wherein the second identification information is associated with transfer route information. First controller and the second controller, a packet transfer route acquisition method according to claim 7 or claim 8 generates control packet to be transmitted based on information via packets. The packet transfer route acquisition method according to any one of claims 6 to 9, wherein the first control device and the second control device manage a network using a data flow.

Images