JP2016225783A - Virtual network system and virtual network routing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a virtual network system that allows an SDN system using the OpenFlow technology to be constructed even for a narrow band network.SOLUTION: The system comprises an OpenFlow controller 1 and one or more OpenFlow switches 5, 13, 19, and 25. The OpenFlow controller 1 holds routing information for all of the OpenFlow switches 5, 13, 19, and 25 and manages all of the respective flow tables of the OpenFlow switches created on the basis of the routing information to configure the respective flow tables of the OpenFlow switches 5, 13, 19, and 25. The OpenFlow switches 5, 13, 19, and 25 transmit and receive user data according to the respective flow tables configured by the OpenFlow controller 1.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a virtual network system and a virtual network path setting method, and more particularly to a virtual network system and a virtual network that make it possible to construct an SDN (Software Defined Network) system using an OpenFlow protocol even in a narrow band. The present invention relates to a network route setting method.

  In recent years, with rapid development of communication infrastructure, communication has been performed in various communication forms. For this reason, SDN (Software Defined Network) system that constructs a network by software has been actively researched and developed as a network virtualization technology that can flexibly change the network configuration and communication data transfer operation. Yes. As one of the technologies for realizing the SDN system, OpenFlow (standard specifications established by the Open Networking Foundation, an industry organization as described in “OpenFlow Switch Specification Version 1.0.0” of Non-Patent Document 1 OpenFlow) technology is attracting particular attention.

  In the OpenFlow technology, the network function is separated into an “OpenFlow controller” that controls network control and an “OpenFlow switch” that controls communication data transfer processing. (OpenFlow controller) manages the route of packets and frames that flow through the network, and "OpenFlow switch" is a packet based on the flow table set by "OpenFlow controller". And frame transfer processing.

  There are two types of SDN systems to which OpenFlow technology is applied: an “overlay tunnel type SDN system” and a “hop-by-hop type SDN system”. The “Overlay Tunnel SDN System” is a technology that realizes an OpenFlow network in an existing network environment that does not have an OpenFlow compatible switch, and interconnects with an existing network. Need to be considered. On the other hand, the “Hop by Hop” SDN system is a technology that realizes an OpenFlow network using OpenFlow compatible network equipment. By defining the flow table independently, a new network virtualization mechanism can be realized.

Open Networking Foundation, “OpenFlow Switch Specification Version 1.0.0”, December 31, 2009, http://archive.openflow.org/documents/openflow-spec-v1.0.0.pdf (searched on April 24, 2015)

  However, the SDN system to which the OpenFlow technology is applied has the following problems.

  The first problem is that, in a hop-by-hop SDN system, when the network control function and the data transfer function are separated and the network setting is performed dynamically, network control is performed. The data is to squeeze the bandwidth used by the user data. The reason is that the OpenFlow controller uses the network communication bandwidth to send and receive messages to detect the network topology, so the OpenFlow controller and the OpenFlow switch This is because a large band is used.

  The second problem is that, in an overlay tunnel type SDN system, when a packet is encapsulated by a tunnel method such as VXLAN (Virtual Extensible Local Area Network), the band used by user data is compressed in a narrow band. There is to do. The reason is that when a packet is encapsulated by a tunnel method such as VXLAN, the size of the packet used for user data also increases, and only the header portion of the tunnel protocol is wasted. It is.

(Object of the present invention)
The present invention has been made in view of such problems, and a virtual network that makes it possible to construct an SDN (Software Defined Network) system to which an OpenFlow technology is applied even in a narrow-band network. It is an object to provide a system and a virtual network path setting method.

  In order to solve the above-described problem, the virtual network system and the virtual network path setting method according to the present invention mainly adopt the following characteristic configuration.

  (1) A virtual network system according to the present invention is a virtual network system including an open flow controller to which an open flow (OpenFlow) technology is applied and one or more open flow switches. Holds route setting information for all the OpenFlow switches, and collectively manages the flow tables of each of the OpenFlow switches created based on the route setting information. On the other hand, each of the OpenFlow switches transmits / receives user data according to the flow table set by the OpenFlow controller.

  (2) A virtual network path setting method according to the present invention is a virtual network path setting method in a network system including an OpenFlow controller to which OpenFlow technology is applied and one or more OpenFlow switches. The OpenFlow controller holds route setting information related to all the OpenFlow switches and collectively manages the flow tables of the OpenFlow switches created based on the route setting information. The corresponding flow table is set for each of the OpenFlow switches, while each OpenFlow switch transmits and receives user data according to the flow table set by the OpenFlow controller. line It is characterized in.

  According to the virtual network system and the virtual network path setting method of the present invention, the following effects can be obtained.

  In other words, the present invention includes an OpenFlow controller to which OpenFlow technology is applied and one or more OpenFlow switches, and the OpenFlow controller is an open flow controller. Since the routing information about the switch is held, the data for network control does not impose the network bandwidth used by the user data, and thus the SDN system can be operated even on a narrow-band physical network. Can be built. Furthermore, since the OpenFlow controller can also have a function of acquiring the MAC addresses of all terminals on the network, even if the IP segment is a different destination, user data can be used as a tunnel protocol. There is no need to add an encapsulated header, and an SDN system can be constructed on a narrow-band physical network.

It is a system configuration figure showing an example of a virtual network system concerning the present invention. It is a schematic diagram explaining the connection state by the open flow channel in the virtual network system shown in FIG. It is a conceptual diagram explaining the connection structural example of the 1st virtual network and 2nd virtual network in the virtual network system shown in FIG.

  Preferred embodiments of a virtual network system and a virtual network path setting method according to the present invention will be described below with reference to the accompanying drawings. In addition, it is needless to say that the drawing reference numerals attached to the following drawings are added for convenience to the respective elements as an example for facilitating understanding, and are not intended to limit the present invention to the illustrated embodiments. Yes.

(Features of the present invention)
Prior to the description of the embodiments of the present invention, an outline of the features of the present invention will be described first. The present invention is a hop-by-hop type virtual network system in which an OpenFlow technology is applied and a network function is separated into an OpenFlow controller and an OpenFlow switch. In order to construct an SDN system, the main feature is that an OpenFlow controller holds all path setting information. Thus, the OpenFlow controller can grasp the network topology without sending a dedicated message for detecting the network topology through the network using the network bandwidth. Therefore, the SDN system can be constructed even on a narrow-band physical network without squeezing the band used by the user data.

  In addition, the present invention is an overlay tunnel type in a virtual network system in which an OpenFlow technology is applied and a network function is separated into an OpenFlow controller and an OpenFlow switch. In order to construct an SDN system, the OpenFlow controller has a function of acquiring the MAC (Media Access Control) addresses of all terminals on the network. Based on the acquired MAC addresses of the terminals, the user frame Rewriting the destination to a MAC address is also a main feature. Thus, even if the IP segment is a different destination, the header portion of the encapsulated tunnel protocol, which was necessary for tunneling in the prior art, is no longer necessary, and the increase in the header portion reduces the network communication bandwidth. This makes it possible to transfer user frames without doing so. That is, since the data for the tunnel protocol header does not compress the band used by the user data, the SDN system can be constructed even on a narrow band physical network.

  In other words, the present invention makes it possible to improve the characteristics and performance of the network, reduce the size and weight, reduce the bandwidth used by the network control message, and improve the transmission efficiency of user data. It is characterized by making it possible to construct an SDN (Software Defined Network) system using the OpenFlow protocol.

(Configuration example of embodiment)
Next, as a configuration example of the embodiment according to the present invention, an example of the configuration of the virtual network system according to the present invention will be specifically described with reference to FIG. FIG. 1 is a system configuration diagram showing an example of a virtual network system according to the present invention. The virtual network system shown in FIG. 1 constructs an SDN (Software Defined Network) system to which an OpenFlow protocol is applied, and an OpenFlow controller 1 that performs network control and a data transfer operation 1 Or a plurality of OpenFlow switches (four in the example of FIG. 1; OpenFlow switch 5, OpenFlow switch 13, OpenFlow switch 19, and OpenFlow switch 25). And at least a switch).

  An OpenFlow controller 1 and an OpenFlow switch 5 are connected by a LAN cable 3 via respective ports 2 and 4. The OpenFlow switch 5 and the OpenFlow switch 13 are connected to each other by a LAN cable 10 via the respective ports 8 and 12, and the OpenFlow switch 5 and the OpenFlow (OpenFlow) ) The switch 19 is connected by the LAN cable 11 through the respective ports 6 and 18, and the OpenFlow switch 5 and the OpenFlow switch 25 are respectively connected to the ports 7 and 24. Are connected by a LAN cable 9. That is, the switch constitutes a two-layer dual star physical network in which the OpenFlow switch 5 is a center switch and the OpenFlow switches 13, 19, and 25 are base switches.

  1 is in a state in which one or a plurality of terminals are connected, and each terminal (in the example of FIG. 1, terminal 17, terminal 23, terminal 29, terminal 37 and four terminals). ) Is connected to each base switch. That is, the terminal 17 and the OpenFlow switch 13 are connected by the LAN cable 15 via the respective ports 16 and 14. The terminal 23 and the OpenFlow switch 19 are connected by the LAN cable 21 via the respective ports 22 and 20, and the terminal 37 and the OpenFlow switch 19 are connected to the respective ports 36. And a port 34 via a LAN cable 35. Further, the terminal 29 and the OpenFlow switch 25 are connected by a LAN cable 27 via the respective ports 28 and 26.

  Here, the terminal 17 and the terminal 23 belong on a two-layer dual star physical network having the OpenFlow switch 5 as a center and the OpenFlow switches 13, 19, and 25 as a base. There is a first virtual network 38 and a second virtual network 39 to which the terminal 37 and the terminal 29 belong, and the SDN is obtained by dividing the physical network into two virtual networks of the first virtual network 38 and the second virtual network 39. (Software Defined Network) system is built.

  FIG. 2 is a schematic diagram for explaining a connection state by an open flow channel in the virtual network system shown in FIG. As illustrated in FIG. 2, the OpenFlow controller 1 and the OpenFlow controller 1 are arranged on a star-type physical network having the OpenFlow switch 5 as a center and the OpenFlow switches 13, 19, and 25 as bases. An OpenFlow channel 30 is connected to the OpenFlow switch 5. Further, the OpenFlow controller 1 and the OpenFlow switch 13 are connected by an OpenFlow channel 31, and the OpenFlow controller 1 and the OpenFlow switch 19 are connected. The OpenFlow channel 32 is connected, and the OpenFlow controller 1 and the OpenFlow switch 25 are connected by an OpenFlow channel 33.

  That is, as shown in the system configuration diagram shown in FIG. 1, the OpenFlow channel 30 in FIG. 2 is a channel physically connected via the port 2, the LAN cable 3, and the port 4. The OpenFlow channel 31 is a channel connected via the port 2, the LAN cable 3, and the port 4, and further connected via the port 8, the LAN cable 10, and the port 12. The OpenFlow channel 32 is the port 2, The channel is connected via the LAN cable 3 and the port 4 and further via the port 6, the LAN cable 11 and the port 18, and the OpenFlow channel 33 is connected via the port 2, the LAN cable 3 and the port 4, and The channel is connected through the port 7, the LAN cable 9, and the port 24.

  For example, the transfer path for transmitting / receiving user data between the terminal 17 and the terminal 23 of FIG. 1 belonging to the first virtual network 38 is determined by the path setting from the OpenFlow controller 1 and determined transfer. The route passes from the terminal 17 via the port 16, the LAN cable 15, and the port 14 via the OpenFlow switch 13, and further, via the port 12, the LAN cable 10, and the port 8, the OpenFlow switch 13. From the OpenFlow switch 5 via the OpenFlow switch 5 via the OpenFlow switch 5 from the OpenFlow switch 5 via the OpenFlow switch 5 via the port 6, the LAN cable 11, and the port 18. Open flow (OpenFlo via LAN cable 21 and port 22 w) A route from the switch 19 to the terminal 23.

  Further, the transfer path for transmitting / receiving user data between the terminal 37 and the terminal 29 in FIG. 1 belonging to the second virtual network 39 is determined by the path setting from the OpenFlow controller 1 and determined transfer. The route passes from the terminal 37 via the port 36, the LAN cable 35, and the port 34 to the OpenFlow switch 19, and further via the port 18, the LAN cable 11, and the port 6 to the OpenFlow switch 19. From the OpenFlow switch 5 via the OpenFlow switch 5 via the OpenFlow switch 5 from the OpenFlow switch 5 via the OpenFlow switch 5 via the port 7, the LAN cable 9 and the port 24. OpenFlow (OpenFlow) via LAN cable 27 and port 28 A path from the switch 25 to the terminal 29.

  FIG. 3 is a conceptual diagram illustrating a connection configuration example of the first virtual network 38 and the second virtual network 39 in the virtual network system shown in FIG. That is, FIG. 3 shows that, according to the setting control of the OpenFlow controller 1, the terminals in the first virtual network 38 and the terminals in the second virtual network 39 can transmit / receive user data to / from each other. It is restricted that user data cannot be transmitted / received between a terminal in the first virtual network 38 and a terminal in the second virtual network 39 (that is, between terminals across different virtual networks). Show. As shown in FIG. 3, the terminal 17 and the terminal 23 in the first virtual network 38 can transmit and receive user data to each other, and the terminal 37 and the terminal 29 in the second virtual network 39 mutually transmit user data. Can be sent and received. However, the connection between the first virtual network 38 and the second virtual network 39 is limited, and the terminals (terminal 17 and terminal 23) in the first virtual network 38 and the terminals (terminals) in the second virtual network 39 37 and the terminal 29) are restricted so that user data cannot be transmitted and received.

  Table 1 below is a correspondence table (base switch / terminal connection table) between the base switches (switch 13, switch 19 and switch 25 shown in FIG. 1) and terminals connected to the base switches. Identifier, that is, a dispatch ID (dispatch-id), a port of the base switch to which the terminal is connected, and an IP (Internet Protocol) address of the terminal connected to the base switch are set. Is held by the OpenFlow controller 1.

  For example, in item No. 1 of Table 1, the dispatch ID of the OpenFlow switch 13 is set as the dispatch ID (dispatch-id) of the base switch, and the port of the base switch to which the terminal is connected is shown in FIG. The port 14 of the OpenFlow switch 13 shown is set, and the IP address of the terminal 17 connected to the OpenFlow switch 13 shown in FIG. 1 is set as the IP address of the terminal connected to the base switch. Has been.

  The following table 2 is a correspondence table (center switch / base switch connection table) between each port of the center switch (switch 5 shown in FIG. 1) and the base switch connected to each port of the center switch. Correspondence between each port of the center switch and the identifier of the base switch connected to each port of the center switch, that is, a dispatch ID (dispatch-id) is set, and the correspondence table shows the OpenFlow controller 1. keeping.

  For example, in item No. 1 of Table 2, the port 8 of the OpenFlow switch 5 shown in FIG. 1 is set as the center switch port, and the dispatch IDs of the base switches connected to the respective ports of the center switch ( As the dispatch-id), the dispatch ID of the OpenFlow switch 13 shown in FIG. 1 is set. That is, the OpenFlow controller 1 detects the network topology in the network from the correspondence table (base switch / terminal connection table) in Table 1 and the correspondence table (center switch / base switch connection table) in Table 2. Therefore, the physical network topology in the virtual network system shown in FIG. 1 is grasped without sending a dedicated message for network control.

(Description of operation example of embodiment)
Next, an example of the operation of the virtual network system shown in FIGS. 1 to 3 will be described in detail as a configuration example of the embodiment according to the present invention.

  The OpenFlow controller 1 shown in FIG. 1 and each OpenFlow switch (ie, OpenFlow switch 5, OpenFlow switch 13, OpenFlow switch 19, OpenFlow switch 19, OpenFlow (OpenFlow) ) When the respective power sources of the switches 25) are turned on and activated, each OpenFlow switch (ie, OpenFlow switch 5, OpenFlow switch 13, OpenFlow switch 19, OpenFlow switch 19, Open) The flow (OpenFlow) switch 25) starts connection of an OpenFlow channel to the OpenFlow controller 1.

  Each OpenFlow switch (ie, OpenFlow switch 5, OpenFlow switch 13, OpenFlow switch 19, OpenFlow switch 25) and OpenFlow controller 1 When the connection of the OpenFlow channel as illustrated in FIG. 2 is established, the OpenFlow controller 1 sets each of the OpenFlow switches 5, 13, 19, 25 in the initial state. Create a flow table. That is, as shown in the correspondence tables of Tables 1 and 2, the route setting information regarding all the OpenFlow switches 5, 13, 19, and 25 constituting the virtual network system is used as information indicating the network topology. The open flow (OpenFlow) controller 1 that is held refers to the correspondence tables in Tables 1 and 2, and the flow table of each of the OpenFlow switches 5, 13, 19, 25 as an initial state. Create

  Thereafter, the OpenFlow controller 1 first sets each flow table corresponding to each site switch as an initial state for each site switch in the created flow table. That is, the flow table shown in the following Table 3 is set in the OpenFlow switch 13, and the flow table shown in Table 4 is set in the OpenFlow switch 19, and the OpenFlow switch 19 In 25, the flow table shown in Table 5 is set.

  In the flow table set for each site switch, the correspondence between the match condition (match) related to user data from the terminal and the action (action) when the match condition is satisfied is set for each order of the flow to be evaluated. ing. For example, in the case of a flow table set in the OpenFlow switch 13, as shown in Table 3, the order of the flow to be evaluated is the first match condition (match), and user data is received from the terminal. An ARP (Address Resolution Protocol) reply packet or ICMP (Internet Control Message Protocol) echo reply packet (ARP reply packet, ICMP echo) in which the port is 'port 14' and the received user data acquires the MAC address of the terminal. The reply packet is a packet conforming to the TCP / IP protocol standard), and the source address is the IP address of the terminal 17, and as an action when the match condition is satisfied, For OpenFlow controller 1 That for transmitting the user data as a Packet an In message is set. The order of the flow to be evaluated is any case other than the first as the second match condition (match), and the received user data is used as an action when the match condition is satisfied. Set to discard.

  Next, the OpenFlow controller 1 sets a flow table corresponding to the center switch as an initial state for the center switch. That is, the flow table shown in the following Table 6 is set in the open flow (OpenFlow) switch 5 of the center switch.

  For the flow table set for the center switch, as with the base switch, the correspondence between the match condition (match) for user data and the action (action) when the match condition is satisfied for each order of the flow to be evaluated Relationship is set. For example, in the case of a flow table set in the open flow (OpenFlow) switch 5, as shown in Table 6, the order of the flow to be evaluated is the first match condition (match) regardless of the case. The action (action) is set to discard the received user data.

  Thereafter, the OpenFlow controller 1 transmits a packet out message for causing the terminal to transmit an ICMP (Internet Control Message Protocol) echo request for confirming the connection of the terminal to each base switch. That is, the OpenFlow controller 1 transmits, as a Packet Out message, a transmission instruction from the port 14 of the ICMP echo request in which the terminal 17 is set as the target IP address to the OpenFlow switch 13. The OpenFlow switch 19 transmits an ICMP echo request transmission instruction from the port 20 with the terminal 23 set as the target IP address as a Packet Out message, and sets the terminal 37 as the target IP address. An ICMP echo request transmission instruction from the port 34 is transmitted as a packet out message, and the port of the ICMP echo request in which the target IP address is set in the terminal 29 to the OpenFlow switch 25 is set. A transmission instruction from 26 to transmit a Packet Out message.

  When the OpenFlow switch 13 transmits an ICMP echo request from the port 14 to the terminal 17 in accordance with the received Packet Out message, the terminal 17 that has received the ICMP echo request returns an ICMP echo reply as an echo. The OpenFlow switch 13 receives the ICMP echo reply from the terminal 17 at the port 14.

  The OpenFlow switch 13 that has received the ICMP echo reply from the terminal 17 transmits the ICMP echo reply as a Packet In message to the OpenFlow controller 1 according to the flow table shown in Table 3. The OpenFlow controller 1 acquires the MAC address of the terminal 17 from the Packet In message received from the OpenFlow switch 13, and the flow table of the OpenFlow switch 13 shown in Table 3 Is updated to the flow table shown in Table 7 below.

  That is, the flow table of the OpenFlow switch 13 shown in Table 7 changes the item number 2 of the flow table of Table 3 to item number 4, changes the evaluation order to the fourth, As route information for transmitting and receiving user data between terminals in the virtual network 38, item number 2 and item number 3 are updated to a newly added state. In item No. 2, the order of the flow to be evaluated is the second match condition (match), the reception port of the user data from the terminal is “port 14”, and the source IP address is the IP of the terminal 17 And the destination IP address is the IP address of the terminal 23 in the same first virtual network 38. As an action when the match condition is satisfied, the received user data The identification number of the first virtual network 38, for example, “10” is assigned to the virtual network identifier VLAN ID to be assigned, and the user data received from the terminal 17 is sent from the port 12 to the open flow (OpenFlow) switch 5 of the center switch. In response to this, the transmission is set.

  In item No. 3, the order of the flow to be evaluated is the third match condition (match), the user data reception port is 'port 12', and the virtual network identifier VLAN ID is the first virtual network. As the action when the match condition is satisfied, the identification number is “10” of 38 and the destination IP address is the IP address of the terminal 17 in the same first virtual network 38. The virtual network identifier VLAN ID is removed from the received user data, the destination of the user data is changed from the transmission destination IP address to the MAC address of the terminal 17, and the transmission is performed from the port 14 toward the terminal 17. Is set.

  Next, the OpenFlow switch 19 transmits an ICMP echo request from each of the port 20 and the port 34 to the terminal 23 and the terminal 37 according to the received Packet Out message, and the terminal that has received the ICMP echo request. 23, when the terminal 37 returns an ICMP echo reply as an echo, the OpenFlow switch 19 receives the ICMP echo reply from the terminal 23 and the terminal 37 at the port 20 and the port 34, respectively.

  The OpenFlow switch 19 that has received the ICMP echo reply from each of the terminal 23 and the terminal 37 opens the ICMP echo reply from each of the terminal 23 and the terminal 37 as a Packet In message according to the flow table shown in Table 4. It transmits to the flow (OpenFlow) controller 1. The OpenFlow controller 1 acquires the MAC address of the terminal 23 and the MAC address of the terminal 37 from the Packet In message received from the OpenFlow switch 19, and the OpenFlow (shown in Table 4) The flow table of the OpenFlow switch 19 is updated to the flow table of Table 8 shown below.

  That is, the flow table of the OpenFlow switch 19 shown in Table 8 changes the item number 3 of the flow table of Table 4 to item number 7, changes the evaluation order to the seventh, As route information for transmitting and receiving user data between terminals in the virtual network 38, item number 3 and item number 4 are newly inserted and user data between terminals in the second virtual network 39 is added. Item number 5 and item number 6 are updated to the newly inserted state as route information for transmission and reception. In item No. 3, the order of the flow to be evaluated is the third match condition (match), the reception port of the user data from the terminal is “port 20”, and the source IP address is the IP of the terminal 23 And the destination IP address is the IP address of the terminal 17 in the same first virtual network 38. As an action when the match condition is satisfied, the received user data The identification number of the first virtual network 38, for example, “10” is assigned to the virtual network identifier VLAN ID to be assigned, and the user data received from the terminal 23 is sent from the port 18 to the open flow (OpenFlow) switch 5 of the center switch. In response to this, the transmission is set.

  In item No. 4, the order of the flow to be evaluated is the fourth match condition (match), the user data reception port is “port 18”, and the virtual network identifier VLAN ID is the first virtual network. As the action when the match condition is satisfied, the identification number is “10” of 38 and the destination IP address is the IP address of the terminal 23 in the same first virtual network 38. The virtual network identifier VLAN ID is removed from the received user data, the destination of the user data is changed from the transmission destination IP address to the MAC address of the terminal 23, and the transmission is performed from the port 20 toward the terminal 23. Is set.

  Further, in item No. 5, as the fifth matching condition (match) of the flow to be evaluated, the reception port of user data from the terminal is “port 34”, and the transmission source IP address is the terminal 37. And the destination IP address is the IP address of the terminal 29 in the same second virtual network 39, and the received user as an action when the match condition is satisfied The virtual network identifier VLAN ID assigned to the data is assigned the identification number of the second virtual network 39, for example, “20”, and the user data received from the terminal 37 is sent from the port 18 to the OpenFlow switch of the center switch. 5 is set to transmit.

  Item No. 6 includes a sixth data matching condition (match) in which the flow to be evaluated has a user data reception port of “port 18” and a virtual network identifier VLAN ID of the second virtual network. As the action when the match condition is satisfied, the identification number is “20” of 39 and the destination IP address is the IP address of the terminal 37 in the same second virtual network 39. The virtual network identifier VLAN ID is removed from the received user data, the destination of the user data is changed from the transmission destination IP address to the MAC address of the terminal 37, and the transmission is performed from the port 34 toward the terminal 37. Is set.

  Next, the OpenFlow switch 25 transmits an ICMP echo request from the port 26 to the terminal 29 in accordance with the received Packet Out message, and the terminal 29 that has received the ICMP echo request receives an ICMP echo reply as an echo. , The OpenFlow switch 25 receives the ICMP echo reply from the terminal 29 at the port 26.

  The OpenFlow switch 25 that has received the ICMP echo reply from the terminal 29 sends the ICMP echo reply from the terminal 29 as a Packet In message to the OpenFlow controller 1 according to the flow table shown in Table 5. To send. The OpenFlow controller 1 acquires the MAC address of the terminal 29 from the Packet In message received from the OpenFlow switch 25, and the flow table of the OpenFlow switch 25 shown in Table 5 Is updated to the following flow table in Table 9.

  That is, the flow table of the OpenFlow switch 13 shown in Table 9 changes the item number 2 of the flow table of Table 5 to item number 4, changes the evaluation order to the fourth, As route information for transmitting and receiving user data between terminals in the virtual network 39, item number 2 and item number 3 are newly updated and inserted. In item No. 2, as the second match condition (match) in the order of the flow to be evaluated, the reception port of user data from the terminal is “port 26”, and the source IP address is the IP of the terminal 29 And the destination IP address is the IP address of the terminal 37 in the same second virtual network 39. As an action when the match condition is satisfied, the received user data The virtual network identifier VLAN ID to be assigned is assigned the identification number of the second virtual network 39, for example, “20”, and the user data received from the terminal 37 is sent from the port 24 to the open flow (OpenFlow) switch 5 of the center switch. In response to this, the transmission is set.

  In item No. 3, the flow order of the flow is the third match condition (match), the user data reception port is “port 24”, and the virtual network identifier VLAN ID is the second virtual network 39. And the destination IP address is the IP address of the terminal 29 in the same second virtual network 39, and the action when the match condition is satisfied is as follows: The virtual network identifier VLAN ID is removed from the received user data, the destination of the user data is changed from the transmission destination IP address to the MAC address of the terminal 29, and transmission is performed from the port 26 toward the terminal 29. Is set.

  Finally, the OpenFlow controller 1 updates the flow table of Table 6 set in the OpenFlow switch 5 of the center switch, and opens the flow table shown in Table 10 below as OpenFlow (OpenFlow). ) Set to switch 5.

  In other words, the flow table of the OpenFlow switch 5 shown in Table 10 changes the item number 1 of the flow table of Table 6 to item number 5, changes the evaluation order to the fifth item, As route information for transmitting and receiving user data between terminals in the virtual network 38, item number 1 and item number 2 are newly inserted and user data between terminals in the second virtual network 39 is added. As route information for transmission / reception, item numbers 3 and 4 are updated to the newly added state. In item No. 1, the order of the flow to be evaluated is the first match condition (match), the user data reception port from the base switch (OpenFlow switch 13) is 'port 8', and The virtual network identifier VLAN ID is the identification number of the first virtual network 38, for example, '10', and the destination IP address is the IP address of the terminal 23 in the same first virtual network 38, As an action when the match condition is satisfied, it is set that user data received from the port 8 is transmitted from the port 6 to the OpenFlow switch 19 of the base switch.

  Further, in item number 2, the order of the flow to be evaluated is the second match condition (match), and the user data reception port from the base switch (OpenFlow switch 19) is “port 6”. And the virtual network identifier VLAN ID is the identification number of the first virtual network 38, for example '10', and the destination IP address is the IP address of the terminal 17 in the same first virtual network 38, As an action when the match condition is satisfied, it is set that user data received from the port 6 is transmitted from the port 8 to the OpenFlow switch 13 of the base switch.

  Furthermore, in item number 3, the order of the flow to be evaluated is the third match condition (match), and the user data reception port from the base switch (OpenFlow switch 19) is “port 6”. And the virtual network identifier VLAN ID is the identification number of the second virtual network 39, for example, “20”, and the destination IP address is the IP address of the terminal 29 in the same second virtual network 39. As an action when the match condition is satisfied, it is set that user data received from the port 6 is transmitted from the port 7 to the OpenFlow switch 25 of the base switch.

  In item No. 4, the order of the flow to be evaluated is the fourth match condition (match), and the user data reception port from the base switch (OpenFlow switch 25) is 'port 7', And the virtual network identifier VLAN ID is the identification number of the second virtual network 39, for example '20', and the destination IP address is the IP address of the terminal 37 in the same second virtual network 39, As an action when the match condition is satisfied, it is set that user data received from the port 7 is transmitted from the port 6 to the OpenFlow switch 19 of the base switch.

  When the operation of setting the flow table of Table 10 to the OpenFlow switch 5 is completed, in the virtual network system including the first virtual network 38 and the second virtual network 39, terminals belonging to the same virtual network are users. Transition to a state where data can be transmitted and received.

  For example, paying attention to the first virtual network 38, when the terminal 17 transmits a packet addressed to the terminal 23, the OpenFlow (OpenFlow) switch 13 transmits the packet to the match condition (No. 2 in the flow table of Table 7). match), a packet assigned the identification number “10” of the first virtual network 38 as the virtual network identifier VLAN ID is transmitted from the port 12 to the port 8 of the OpenFlow switch 5. In the OpenFlow switch 5 that has received the packet, since the match condition (match) of item number 1 in the flow table of Table 10 is true, the packet is transferred from the port 6 to the port of the OpenFlow switch 19. 18 is transmitted.

  In the OpenFlow switch 19 that has received the packet, since it matches the match condition (match) of item number 4 in the flow table of Table 8, the identification number of the first virtual network 38 of the virtual network identifier VLAN ID ' 10 ′ is removed, the destination is changed from the destination IP address to the MAC address of the terminal 23, and transmitted from the port 20 to the port 22 of the terminal 23. Thus, the terminal 23 can receive the packet transmitted by the terminal 17.

  For example, when the terminal 17 belonging to the first virtual network 38 transmits a packet addressed to the terminal 29 belonging to the second virtual network 39, the flow of Table 7 is performed in the OpenFlow switch 13. The packet is not applied to any of the match conditions (match) of item numbers 1 to 3 in the table, but is matched to the match condition (match) of item number 4, so that the packet is transmitted to the terminal 29. Without being destroyed.

  The configuration of the preferred embodiment of the present invention has been described above. However, it should be noted that such embodiments are merely examples of the present invention and do not limit the present invention in any way. Those skilled in the art will readily understand that various modifications and changes can be made according to a specific application without departing from the gist of the present invention.

1 OpenFlow controller 2 Port 3 attached to controller 1 LAN cable connecting controller 1 and switch 4 Port 5 attached to switch 5 OpenFlow switch 6 Included with OpenFlow switch 5 Port 7 attached to OpenFlow switch 5 Port 8 attached to OpenFlow switch 5 Port 9 attached to OpenFlow switch 5 LAN cable 10 for connecting OpenFlow switch 5 and OpenFlow switch 25 Open LAN cable 11 for connecting the OpenFlow switch 5 and the OpenFlow switch 13 LAN cable 12 for connecting the OpenFlow switch 5 and the OpenFlow switch 19 OpenFlow switch 13 Attached to Port 13 OpenFlow switch 14 Port 15 attached to OpenFlow switch 13 LAN cable 16 for connecting OpenFlow switch 13 and terminal 17 Port 17 attached to terminal 17 Terminal 18 Open flow ( Port 19 attached to OpenFlow switch 19 OpenFlow switch 20 Port 21 attached to OpenFlow switch 19 LAN cable 22 for connecting OpenFlow switch 19 and terminal 23 22 attached to terminal 23 Port 23 Terminal 24 Port 25 attached to OpenFlow switch 25 OpenFlow switch 26 Port 27 attached to OpenFlow switch 25 LAN for connecting OpenFlow switch 25 and terminal 29 K 28 Port 29 attached to terminal 29 Terminal 30 Open flow channel 31 between OpenFlow controller 1 and OpenFlow switch 5 OpenFlow controller 1 and OpenFlow switch 13 OpenFlow channel 32 between OpenFlow channel 1 between OpenFlow controller 1 and OpenFlow switch 19 OpenFlow channel 33 between OpenFlow controller 1 and OpenFlow switch 25 Flow channel 34 Port 35 attached to OpenFlow switch 19 LAN cable 36 connecting OpenFlow switch 19 and terminal 37 Port 37 attached to terminal 37 Terminal 38 First virtual network 39 Second virtual network Work

Claims (10)

  In a virtual network system composed of an OpenFlow controller to which OpenFlow technology is applied and one or a plurality of OpenFlow switches, the OpenFlow controller is route setting information related to all the OpenFlow switches. And managing the flow table of each of the OpenFlow switches created based on the route setting information collectively, and setting the corresponding flow table for each of the OpenFlow switches. On the other hand, each of the OpenFlow switches transmits / receives user data according to the flow table set by the OpenFlow controller.   The OpenFlow controller acquires MAC (Media Access Control) addresses of all terminals connected to the OpenFlow switches, updates the flow tables using the acquired MAC addresses, and The updated flow table is set for each of the corresponding OpenFlow switches, while each OpenFlow switch has user data in accordance with the flow table updated and set by the OpenFlow controller. 2. The virtual network system according to claim 1, wherein the user data is transmitted and received by changing the destination of the user to the MAC address of the terminal.   The OpenFlow controller transmits a MAC address acquisition request to each of the OpenFlow switches, and each of the OpenFlow switches receives a MAC address acquisition request from the OpenFlow controller based on the MAC address acquisition request. The virtual network system according to claim 2, wherein MAC addresses of all connected terminals are acquired and the acquired MAC addresses are notified to the requesting OpenFlow controller.   The OpenFlow controller transmits an ICMP (Internet Control Message Protocol) echo request packet conforming to the TCP / IP protocol standard as a Packet Out message as the MAC address acquisition request to be transmitted to each OpenFlow switch. Each OpenFlow switch transmits an ICMP echo request packet received as the Packet Out message to all the terminals connected to the OpenFlow switch. As a result, the ICMP echo including each MAC address is transmitted from each terminal. The reply packet is received, and the ICMP echo reply packet received from each terminal is returned to the OpenFlow controller as a Packet In message. Punfuro controller, virtual network system according to claim 3, characterized in that to obtain the MAC address of each terminal included in the respective ICMP echo reply packet has been returned from each of said open flow switch.   In a case where the OpenFlow switch is configured by a dual-tier physical network of two layers including a base switch connecting terminals and a center switch connecting the base switches, the path setting information related to the center switch Includes information that identifies an identifier for identifying each base switch and each port to which each base switch is connected with respect to each port of the center switch. The route setting information includes an identifier for identifying each base switch, and a port connected to the terminal and an IP (Internet Protocol) address of the terminal connected to the port for each port of the base switch. And information that identifies the Virtual network system according to any one of claims 1 to 4, characterized in.   In the flow table set in the base switch, when user data is received from a reception port to which a terminal is connected, a terminal and a destination IP address indicated by a source IP address included in the received user data are When the terminals shown are terminals belonging to the same virtual network, a virtual network identifier for identifying the virtual network is assigned to the received user data, and the transmission port to which the center switch is connected is assigned. 6. The virtual network system according to claim 5, wherein an operation to transfer is instructed.   The flow table set in the base switch deletes the virtual network identifier given to the received user data when the user data is received from the reception port to which the center switch is connected, and the user Changing the destination included in the data from the destination IP address to the MAC address of the terminal indicated by the destination IP address, and instructing the operation of transmitting the user data from the transmission port to which the terminal is connected The virtual network system according to claim 6.   In the flow table set in the center switch, when user data is received from a reception port to which any one of the base switches is connected, a destination IP address included as a destination in the received user data is displayed. Referring to the transmission port of the center switch, the base switch to which the terminal indicated by the transmission destination IP address is connected is instructed to transfer the user data to the transmission port to which the terminal is connected. The virtual network system according to claim 5, wherein the virtual network system is a virtual network system.   A virtual network path setting method in a network system comprising an OpenFlow controller to which OpenFlow technology is applied and one or more OpenFlow switches, wherein the OpenFlow controller Holds route setting information related to the flow switch, and manages the flow tables of each of the OpenFlow switches created based on the route setting information in a batch, and supports each of the OpenFlow switches. The virtual network path setting method according to claim 1, wherein each of the OpenFlow switches transmits and receives user data according to the flow table set by the OpenFlow controller.   The OpenFlow controller acquires MAC (Media Access Control) addresses of all terminals connected to the OpenFlow switches, updates the flow tables using the acquired MAC addresses, and The updated flow table is set for each of the corresponding OpenFlow switches, while each OpenFlow switch has user data in accordance with the flow table updated and set by the OpenFlow controller. The virtual network path setting method according to claim 9, wherein the user data is transmitted and received by changing the destination of the user to the MAC address of the terminal.

Images