WO2015052854A1 - Système de gestion de trafic et procédé de gestion de trafic - Google Patents

Système de gestion de trafic et procédé de gestion de trafic Download PDF

Info

Publication number
WO2015052854A1
WO2015052854A1 PCT/JP2014/002247 JP2014002247W WO2015052854A1 WO 2015052854 A1 WO2015052854 A1 WO 2015052854A1 JP 2014002247 W JP2014002247 W JP 2014002247W WO 2015052854 A1 WO2015052854 A1 WO 2015052854A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
information
switch
interface controller
network interface
Prior art date
Application number
PCT/JP2014/002247
Other languages
English (en)
Japanese (ja)
Inventor
聡 辻
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to JP2015541415A priority Critical patent/JPWO2015052854A1/ja
Publication of WO2015052854A1 publication Critical patent/WO2015052854A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/65—Re-configuration of fast packet switches

Definitions

  • the present invention relates to a traffic management system and a traffic management method, and more particularly to a traffic management system and a traffic management method capable of managing traffic between computer systems sharing the same network interface controller.
  • the I / O device is SR-IOV (Single Root-I / O Virtualization).
  • the chip set supports IOMMU (I / O Memory Management Unit), it is possible to share the same I / O device from one or more virtual machines.
  • I / O devices can be shared from one or more physically different computer systems.
  • FIG. 10 is a block diagram showing an overview of a network interface controller corresponding to SR-IOV or MR-IOV.
  • a network interface controller 1 compatible with SR-IOV or MR-IOV internally includes a packet switch 10 for communication between computer systems sharing the network interface controller 1. And a forwarding table 12 used by the packet switch 10 to determine the output destination of the packet.
  • a forwarding table 12 used by the packet switch 10 to determine the output destination of the packet.
  • information indicating a destination such as a MAC (Media Access Control) address included in the packet header and an output destination interface (computer system interface 14 or external network port 16) are registered as a set.
  • the packet switch 10 and the forwarding table 12 are often limited to simple functions in order to reduce the chip size and cost of the network interface controller 1. For this reason, for example, only switching using only the MAC address and VLAN ID is possible, and examples of not holding traffic statistical information are seen.
  • a PCI-Express interface 18 As an interface for the computer system, a PCI-Express interface 18, one or more computer system interfaces 14, and the like so that the network interface controller 1 can be shared from one or more computer systems. Is provided.
  • the PCI-Express interface 18 includes a function for handling transmission / reception of signals compliant with the PCI-Express standard with a CPU (Central Processing Unit), and a register and interface for setting the network interface controller 1. .
  • the computer system interface 14 is called a physical function (PF) or a virtual function (VF) in the SR-IOV or MR-IOV specifications.
  • the PCI-Express interface 18 analyzes a signal conforming to the PCI-Express standard sent from the CPU, determines which computer system interface 14 is the data to be transferred, and determines the computer system interface determined as the transfer destination The signal is transferred to 14.
  • the network interface controller 1 includes one or more external network ports 16 for connecting to an external network.
  • FIG. 11 is a system configuration diagram showing a state where one or more computer systems 4 share the network interface controller 1. As shown in FIG. 11, the network interface controller 1 is shared by one or more computer systems 4 (computer system 4a, computer system 4b,...) Via an I / O switch 3.
  • the computer system 4 includes a CPU 40, a memory 42, and an I / O interface 44.
  • An example of the I / O interface 44 is a PCI-Express interface, for example.
  • some functions of the I / O interface 44 may be built in the CPU 40.
  • various peripheral devices such as a hard disk and an optical drive are connected to the computer system 4 via the I / O interface 44 or the like.
  • the I / O switch 3 has a function of switching a signal conforming to PCI-Express.
  • data is transferred as a packet. That is, a header indicating a destination and CRC (Cyclic Redundant Check) data for error check are added to the data, and the data is switched and transferred by the I / O switch 3.
  • CRC Cyclic Redundant Check
  • a packet that flows through a computer network such as Ethernet (registered trademark) is referred to as a network packet
  • a packet that flows through a PCI-Express bus is referred to as a PCIe packet.
  • the PCIe packet is transferred.
  • the network packet is as follows by the operation of each part of the network interface controller 1 shown in FIG. Forwarded to
  • the PCIe packet is sent from the computer system 4 a to the computer system interface 14 assigned to the computer system 4 a provided in the network interface controller 1 via the I / O interface 44 and the I / O switch 3. Send.
  • a network packet is stored in the payload portion of the PCIe packet.
  • the computer system 4a divides the network packet, divides it into payloads of one or more PCIe packets, stores them, and transmits them.
  • the network interface controller 1 that has received the PCIe packet from the computer system 4 a takes out the network packet from the PCIe packet by the PCI-Express interface 18.
  • the network interface controller 1 assembles the network packet.
  • the packet switch 10 refers to the forwarding table 12 using the header information of the network packet and searches for the computer system interface 14 that is the transfer destination of the network packet.
  • the packet switch 10 outputs the network packet to the computer system interface 14 which is the transfer destination of the network packet obtained by the search result of the forwarding table 12.
  • the output network packet is stored as a payload in the PCIe packet by the PCI-Express interface 18 and transferred to the destination computer system 4b.
  • the network interface controller 1 since the network interface controller 1 operates like a network switch, it must be managed as a network switch.
  • network interface controller 1 Is defined to forward all network packets from the computer system 4 to an external network. Therefore, in the case of communication between the computer systems 4 sharing the network interface controller 1, a network switch that is directly connected to the external network port 16 of the network interface controller 1 and that exists in the external network inputs the network packet. Is output to the same port as the input port, the network packet is returned to the network interface controller 1 that has output the network packet. Processing necessary for switching of the network switch is performed in the adjacent switch, thereby realizing switching between the computer systems 4.
  • VEPA Virtual Ethernet Port Aggregator
  • Non-Patent Document 1 since all traffic is transferred to the network switch of the external network, from the viewpoint of network management, only the network switch is managed as in the past. Good.
  • the first problem in the prior art is that communication between computer systems 4 sharing the network interface controller 1 cannot be managed in the case of the techniques shown in FIGS.
  • the second problem in the prior art is that, in the case of the techniques described in Non-Patent Document 1 and Non-Patent Document 2, the link between the network interface controller 1 and the network switch of the external network becomes a bottleneck. Is a point.
  • the third problem in the prior art is that, in the case of the techniques shown in FIGS. 10 and 11, the management point is greatly increased if the network interface controller 1 is managed in the same manner as the conventional network switch. That is the point.
  • the number of network interface controllers 1 is equal to the number of computer systems 4 at the maximum, so that depending on the environment such as a large-scale data center, the number of computer systems 4 becomes enormous and the number of network switches This is because the number is several tens of times.
  • the present invention has the first problem described above, that is, the problem that communication between computer systems 4 sharing the network interface controller 1 cannot be managed, and the second problem, that is, all network packets are A traffic management system capable of effectively solving the problem that communication performance is deteriorated by using an external network and the third problem, that is, the problem that the management point of the network is greatly increased; Its purpose is to provide a traffic management method.
  • the traffic management system and the traffic management method according to the present invention mainly adopt the following characteristic configuration.
  • a traffic management system includes at least one network interface controller that transmits and receives information to and from one or more computer systems, and is connected to the network interface controller and transmits information to and from an external network.
  • a traffic management system that includes at least one or more network switches that transmit and receive and a logical switch configuration system that constitutes a logical switch, and manages information to be transmitted and received, each network interface controller including the network interface controller For traffic between one or more computer systems that share the network, the transfer process is completed within the network interface controller, and the statistical information of the traffic is displayed.
  • the logical switch configuration system includes a mechanism for acquiring configuration information and statistical information from each network interface controller and each network switch and configuring the logical switch configuration system as one logical switch. It is characterized by that.
  • a traffic management method includes one or more network interface controllers that transmit and receive information to and from one or more computer systems, and the network interface controller that is connected to the network interface controller and transmits information to and from external networks.
  • the logical switch configuration system has a mechanism for acquiring configuration information and statistical information from each network interface controller and each network switch and configuring the logical switch as one logical switch. It is characterized by that.
  • the traffic between one or more computer systems sharing the network interface controller and the traffic flowing through the network switch to which the network interface controller is connected can be reduced without degrading the communication performance.
  • Centralized management is possible without increasing management points.
  • the reason is that the configuration information and statistical information are obtained from the network interface controller and the network switch, and a mechanism for configuring the logical interface as one logical switch is provided, and between one or more computer systems sharing the network interface controller. This is because the traffic can be completed in the network interface controller.
  • FIG. 1 It is a system configuration figure showing an example of composition of a traffic management system concerning an embodiment of the present invention. It is a block block diagram which shows an example of an internal structure of the network interface controller shown to the traffic management system of FIG. It is a block block diagram which shows an example of an internal structure of the network switch shown to the traffic management system of FIG. It is a block block diagram which shows an example of an internal structure of the logical switch management part of the logical switch management system shown in the traffic management system of FIG. It is a sequence diagram which shows an example of the flow of a process for the logical switch management system shown in FIG. 1 to comprise a logical switch.
  • FIG. 1 It is a system configuration figure showing an example of composition of a traffic management system concerning an embodiment of the present invention. It is a block block diagram which shows an example of an internal structure of the network interface controller shown to the traffic management system of FIG. It is a block block diagram which shows an example of an internal structure of the network switch shown to the traffic management system of FIG. It is a block
  • FIG. 3 is a flowchart showing an example of processing for adding an entry to a loopback table or updating an entry registered in the loopback table when the network interface controller shown in FIG. 2 receives a network packet.
  • structure figure which shows an example of a structure of the traffic management system at the time of implementing using an open flow.
  • It is a block block diagram which shows an example of an internal structure of the network interface controller corresponding to an open flow shown to the traffic management system of FIG.
  • FIG. 2 is a system configuration diagram illustrating a state in which one or more computer systems share a network interface controller.
  • the traffic management method according to the present invention may be implemented as a traffic management program that can be executed by a computer, or the traffic management program may be recorded on a computer-readable recording medium. Needless to say.
  • the traffic management system of the present invention provides a mechanism for acquiring configuration information and statistical information from a network interface controller and a network switch and configuring it as a single logical switch, and sharing one or more network interface controllers.
  • the main feature is that the transfer process can be completed within the network interface controller.
  • the traffic flowing through the network switch to which the network interface controller is connected can be increased without degrading the communication performance and the management point. Rather, it is made possible to centrally manage.
  • the present invention comprises a table (loopback table) for holding traffic identification information and statistical information between one or more computer systems sharing a network interface controller in the network interface controller
  • a logical switch management system having a mechanism configured as a logical switch includes configuration information acquisition means (a network interface controller management unit interface and a network switch management unit interface) for acquiring configuration information from a network interface controller and a network switch, Connection information management means (connection information) for managing connection information indicating how the network interface controller and the network switch are connected.
  • Logical switch configuration means for determining the number of ports of the logical switch and the number of entries in the forwarding table from the identification unit, the statistical information, the configuration information, and the connection information, and configuring the logical switch
  • the main features include at least a logical switch port management unit and a logical switch forwarding table management unit) and traffic information acquisition means (logical switch management interface) for acquiring traffic information from the configured logical switch. It is said.
  • FIG. 1 is a system configuration diagram showing a configuration example of a traffic management system according to an embodiment of the present invention.
  • the traffic management system 8 shown in FIG. 1 includes a logical switch management system 6, one or more network interface controllers 5, and one or more network switches 7.
  • the logical switch management system 6 includes at least a logical switch management unit 60, a network switch management unit 62, and a network interface controller management unit 64.
  • FIG. 2 is a block diagram showing an example of the internal configuration of the network interface controller 5 shown in the traffic management system 8 of FIG.
  • the network interface controller 5 shown as an example in FIG. 2 is configured by newly adding a loopback table 13 and a management interface 17 to the conventional network interface controller 1 shown in FIG.
  • the same components as those of the conventional network interface controller 1 shown in FIG. 10 are denoted by the same reference numerals, and detailed description thereof is omitted here.
  • the loopback table 13 includes traffic identification information, an identifier of the destination computer system interface 14, and traffic for traffic between computer systems sharing the same network interface controller 5 (computer system 4 shown in FIG. 11). Is a table for managing the statistical information.
  • the traffic identification information is, for example, physical information of the network interface controller 5 such as the identifier of the computer system interface 14 of the transmission source, MAC address, VLAN ID, IP address, L4 (Layer 4: Transport) Layer) is composed of a set of information included in the header of a network packet, such as a protocol type and an L4 port number.
  • L4 Layer 4: Transport
  • the traffic statistical information includes at least the number of passing packets of each flow, the number of passing bytes, and the time when the entry of the flow was last referred.
  • the management interface 17 is an interface for connecting to the logical switch management system 6.
  • the management interface 17 may be an interface that is physically independent of the external network port 16, an interface that is physically integrated with the external network port 16, or a PCI-Express. An interface via the interface 18 may be used.
  • FIG. 3 is a block configuration diagram showing an example of the internal configuration of the network switch 7 shown in the traffic management system 8 of FIG.
  • the network switch 7 illustrated in FIG. 3 includes at least a packet switch 70, a forwarding table 72, one or more network ports 74, a packet switch management unit 76, and a management interface 78.
  • Each network port 74 is an interface for connecting to the network interface controller 5 and other network switches 7 and is used for transmitting and receiving network packets.
  • the packet switch 70 is a module for determining a network port 74 as an output destination by referring to the forwarding table 72 based on the information of the network packet received from any one of the network ports 74, and transmitting the network packet. is there.
  • the packet switch 70 may perform not only the process of determining and sending out the output destination network port 74 but also the process of dropping the network packet, the process of rewriting the header information of the network packet, and the like. good.
  • the forwarding table 72 includes flow identification information, a destination network port 74 identifier, and flow statistics for traffic flowing through the packet switch 70. It is a table for managing information.
  • the packet switch management unit 76 is a module for managing the packet switch 70. Specifically, processing such as entry reading and writing to the forwarding table 72 and setting to the network port 74 can be mentioned.
  • the packet switch management unit 76 is realized in the form of an application that runs on a general-purpose CPU and a general-purpose OS.
  • the management interface 78 is an interface for connecting to the logical switch management system 6.
  • the management interface 78 may be realized as a management port provided in a general network switch, or may be realized as an interface physically integrated with any one of the network ports 74.
  • the logical switch management system 6 shown in FIG. 1 includes at least the logical switch management unit 60, the network switch management unit 62, and the network interface controller management unit 64, as described above.
  • the logical switch management system 6 has a function of logically managing the network interface controller 5 and the network switch 7 as one switch.
  • the network interface controller management unit 64 of the logical switch management system 6 sends the specification information (configuration information) and traffic transfer status (statistical information) of each network interface controller 5 via the management interface 17 of each network interface controller 5. Read and hold inside. Further, the network switch management unit 62 reads the specification information (configuration information) and traffic transfer status (statistical information) of each network switch 7 via the management interface 78 of each network switch 7 and holds them internally. To do.
  • each of the network interface controller management unit 64 and the network switch management unit 62 internally includes information on the specification information and traffic transfer status of each network interface controller 5, and the specification information and traffic of each network switch 7. And a storage area for storing information on the transfer status of each.
  • a logical switch is configured using information acquired and held by the network switch management unit 62 and the network interface controller management unit 64.
  • the specification information of each network interface controller 5 acquired and held by the network interface controller management unit 64 includes at least the total number of computer system interfaces 14, the total number of entries in the loopback table 13, and the number of external network ports 16. Including the total number.
  • the total number of entries in the forwarding table 12, functions provided in the computer system interface 14, functions provided in the packet switch 10, and the like are assumed as examples of specification information of each network interface controller 5. .
  • the traffic transfer status of each network interface controller 5 acquired and held by the network interface controller management unit 64 includes at least the number of used entries in the loopback table 13 of each network interface controller 5 and the used entries. And registered information. In addition to such information, for example, the number of entries used in the forwarding table 12 and information registered in the entries used in the forwarding table 12 are assumed as the traffic transfer status of each network interface controller 5.
  • the specification information of each network switch 7 acquired and held by the network switch management unit 62 includes at least the total number of entries in the forwarding table 72 of each network switch 7 and the total number of network ports 74.
  • functions provided in the network port 74, functions provided in the packet switch 70, and the like are assumed as examples of the specification information of each network switch 7.
  • the traffic transfer status of each network switch 7 acquired and held by the network switch management unit 62 is registered in at least the number of entries used in the forwarding table 72 of each network switch 7 and the entries used in the forwarding table 72. Information.
  • the information registered in the forwarding table 72 includes at least flow identification information, the number of passing packets for each flow, the number of passing bytes, and the time when the entry of the flow was last referred.
  • FIG. 4 is a block configuration diagram showing an example of an internal configuration of the logical switch management unit 60 of the logical switch management system 6 shown in the traffic management system 8 of FIG. 4 includes a network switch management unit interface 600, a network interface controller management unit interface 610, a logical switch forwarding table management unit 620, a logical switch port management unit 630, and connection information management. 640 and a logical switch management interface 660 at least.
  • the network switch management unit interface 600 is an interface for transmitting and receiving information to and from the network switch management unit 62 in the logical switch management system 6 shown in FIG.
  • the network interface controller management unit interface 610 is an interface for transmitting and receiving information to and from the network interface controller management unit 64 in the logical switch management system 6 shown in FIG.
  • the logical switch forwarding table management unit 620 includes the information of the loopback table 13 of the network interface controller 5 of FIG. 2 acquired by the network interface controller management unit 64 and the forwarding of the network switch 7 of FIG. 3 acquired by the network switch management unit 62. This is a module that logically manages the information in the table 72 as one table. As a result, the logical switch forwarding table management unit 620 holds statistical information of flows that flow through the network interface controller 5 and the network switch 7.
  • the logical switch port management unit 630 includes information on the computer system interface 14 of the network interface controller 5 acquired by the network interface controller management unit 64 of FIG. 1 and the network of the network switch 7 acquired by the network switch management unit 62 of FIG. This is a module that manages the information of the port 74 as a port included in the logical switch.
  • the connection information management unit 640 manages connection information between the network interface controller 5 and the network switch 7.
  • the connection information is information indicating which external network port 16 of which network interface controller 5 is connected to which network port 74 of which network switch 7.
  • the connection information may be statically stored in advance, or for example, connection information may be dynamically acquired by flowing a network packet for link connection confirmation. In the latter case, for example, it is assumed to use LLDP (Link Layer Discovery Protocol).
  • the logical switch management interface 660 is an interface for reading logical switch information.
  • the configuration of the logical switch such as the number of ports of the logical switch and the size of the forwarding table of the logical switch, and the statistical information of the flow flowing through the logical switch can be acquired.
  • the logical switch port manager 630 determines which computer system interface 14 of which network interface controller 5 corresponds to which network port 74 of which network switch 7 the logical switch port corresponds to. Associate. The result of the association is held by the logical switch port management unit 630 as mapping information.
  • the logical switch port management unit 630 has acquired the function of the computer system interface 14 and the function of the network port 74 in the network switch management unit 62 and the network interface controller management unit 64.
  • information indicating what function is provided for each logical port can be added to the mapping information.
  • FIG. 5 is a sequence diagram illustrating an example of a process flow for the logical switch management system 6 illustrated in FIG. 1 to configure a logical switch. Information transmission / reception between the network interface controller 5 and the network switch 7 is performed. In addition, an example of a processing flow in the logical switch management system 6 is shown. Note that the processing of the logical switch management system 6 shown in FIG. 5 is periodically performed at an arbitrary timing.
  • the logical switch management system 6 acquires information on the computer system interface 14 and the loopback table 13 from the network interface controller 5 through the network interface controller management unit 64 (steps). S100).
  • Examples of information related to the computer system interface 14 include the number of computer system interfaces 14 and the functions of each computer system interface 14.
  • Examples of information relating to the loopback table 13 include the number of entries in the loopback table 13.
  • the logical switch management system 6 acquires information regarding the network port 74 and the forwarding table 72 from the network switch 7 through the network switch management unit 62 (step S110).
  • Examples of information related to the network port 74 include the number of network ports 74, functions provided in each network port 74, and the like.
  • Examples of information related to the forwarding table 72 include the number of entries in the forwarding table 72.
  • step S110 can be executed first, or step S100 and step S110 can be executed simultaneously.
  • the logical switch management system 6 obtains the number of logical switch ports from the information regarding the number of computer system interfaces 14 acquired from the network interface controller 5 and the number of network ports 74 acquired from the network switch 7 ( Step S120).
  • the logical switch management system 6 uses the information on the number of entries in the loopback table 13 acquired from the network interface controller 5 and the information on the number of entries in the forwarding table 72 acquired from the network switch 7 to enter the entry in the forwarding table of the logical switch.
  • the number is obtained (step S130).
  • step S130 can be executed first, or step S120 and step S130 can be executed simultaneously.
  • the logical switch management system 6 configures a logical switch based on the calculated number of ports of the logical switch and the number of entries in the forwarding table of the logical switch.
  • FIG. 6 shows a process for adding an entry to the loopback table 13 or a process for updating an entry registered in the loopback table 13 when the network interface controller 5 shown in FIG. 2 receives a network packet. It is a flowchart which shows an example.
  • step S200 when the network interface controller 5 receives a network packet from either the computer system interface 14 or the external network port 16, the network interface controller 5 refers to the forwarding table 12 (step S200).
  • the network interface controller 5 determines whether both the input / output ports of the received network packet are the computer system interface 14 using the result of referring to the forwarding table 12 in step S200 (step S200). S210).
  • whether the input / output port of each network packet is the computer system interface 14 is determined, for example, by the network interface controller 5, which port is the computer system interface 14, or the network interface controller 5. It is conceivable to hold information indicating whether or not there is, and compare this information with the result of referring to the forwarding table 12. Alternatively, it can also be realized by including in each entry of the forwarding table 12 a flag indicating that both of the input / output ports are the computer system interface 14.
  • the network interface controller 5 uses the information of the header of the network packet to loop back. It is determined whether or not an entry exists in the table 13 (step S220).
  • the network interface controller 5 updates the statistical information of the entry in the loopback table 13 (Step S230).
  • the network interface controller 5 additionally registers the identifier of the flow to which the received network packet belongs in the loopback table 13 as a new entry. (Step S240).
  • step S210 if any one of the input / output ports of the network packet is not the computer system interface 14 (No in step S210), the network interface controller 5 does not perform any operation on the loopback table 13.
  • the flow statistics are periodically obtained from the loopback table 13 of the network interface controller 5 and the forwarding table 72 of the network switch 7 at predetermined intervals.
  • the information is acquired and the information in the forwarding table of the logical switch is updated.
  • the traffic management system 8 As described above in detail, the traffic management system 8 according to the present embodiment provides the following effects.
  • each network interface controller 5 of the traffic management system 8 includes a loopback table 13, can hold statistical information regarding traffic between computer systems 4 sharing the network interface controller 5, and the network interface controller 5.
  • the transfer process can be completed within the network interface controller 5.
  • the logical switch management system 6 performs logical processing based on information on the loopback table 13 and the computer system interface 14 of the network interface controller 5 and information on the forwarding table 72 and network port 74 of the network switch 7. By configuring the switch, the network interface controller 5 and the network switch 7 can be managed as one logical switch.
  • the traffic between the one or more computer systems 4 sharing the network interface controller 5 and the traffic flowing through the network switch 7 to which the network interface controller 5 is connected can be reduced without degrading the communication performance.
  • Centralized management is possible without increasing management points.
  • OpenFlow is one of the technologies for constructing a software-defined network (SDN: Software-Defined Network) on a physical network.
  • SDN Software-Defined Network
  • FIG. 7 is a system configuration diagram showing an example of the configuration of the traffic management system 80 when implemented using OpenFlow.
  • OpenFlow please refer to “OpenFlow Specification Version 1.3.1 (Wire Protocol 0x04) September 6, 2012”, ⁇ https: //www.opennetworking. org / images / stories / downloads / specification / openflow-spec-v1.3.1.pdf>, and so on, are not described in detail here.
  • the traffic management system 80 shown in FIG. 7 includes an OpenFlow controller 110, one or more OpenFlow switches 100, and one or more OpenFlow compatible network interface controllers 120.
  • the OpenFlow controller 110 controls the switches (OpenFlow switch 100 and OpenFlow compatible network interface controller 120) corresponding to the OpenFlow specification by using an API (Application Programming Interface) based on the OpenFlow specification.
  • API Application Programming Interface
  • the OpenFlow controller 110 includes an OpenFlow interface 140.
  • OpenFlow there is no specific provision regarding how to control the network in advance. Instead, the user can use the OpenFlow interface 140 to select an arbitrary network control application for controlling the network. It can be freely implemented.
  • a logical switch management unit 60 As a network control application, a logical switch management unit 60, a network interface controller management unit 64, which have the same functions as those in the logical switch management system 6 of FIG.
  • the network switch management unit 62 is mounted in a form arbitrarily defined by the user using the OpenFlow interface 140. However, at that time, the network interface controller management unit 64 and the network switch management unit 62 use an API provided by the OpenFlow interface 140.
  • OpenFlow a control communication connection called a secure channel is established between the OpenFlow controller 110 and a switch corresponding to the OpenFlow specification.
  • the OpenFlow controller 110 includes a secure channel control unit 130 for this purpose.
  • OpenFlow controller 110 when OpenFlow controller 110 and a switch that supports OpenFlow are connected through a secure channel, information about what function the switch that supports OpenFlow has is provided. Exchange with 110. The information includes information about the number of ports of the switch corresponding to the open flow and the number of entries in the flow table provided for performing flow management in the switch corresponding to the open flow. As a result, the OpenFlow controller 110 can configure a logical switch.
  • the OpenFlow controller 110 can read the information in the flow table of the switch corresponding to the OpenFlow at an arbitrary timing, the information about how many flow entries are consumed and the statistical information of each flow Can also be acquired reliably.
  • FIG. 8 is a block configuration diagram showing an example of the internal configuration of the network interface controller 120 for OpenFlow shown in the traffic management system 80 of FIG.
  • the open flow compatible network interface controller 120 shown in FIG. 8 is different from the network interface controller 5 shown in FIG. 2 in that a control CPU 19 and a flow table 20 are added, and a forwarding table 12 and a loopback table. 13 are excluded, but the other parts are composed of the same elements as those of the network interface controller 5 of FIG.
  • the same components as those of the network interface controller 5 of FIG. 2 are denoted by the same reference numerals as those of the network interface controller 5 of FIG. 2, and detailed description thereof is omitted here.
  • the flow table 20 is a table for flow management in OpenFlow.
  • the flow entry of the flow table 20 includes an input port number to the packet switch 10, a key defined by information (an identifier of the network packet) included in a network packet header such as a MAC address and an IP address, and the key And an action for a packet belonging to a packet group matching the above.
  • the key can also use a wild card, and is defined as “a flow with an L4 port number of 80 (port number meaning HTTP (Hyper Text Transfer Protocol)) regardless of the MAC address or IP address”.
  • the action can specify not only the output destination port of the network packet but also the rewriting of the header of the network packet, the packet drop, and the like. Note that the packet switch 10 operates based on the actions held in the flow table 20 in this embodiment.
  • the control CPU 19 processes the OpenFlow protocol, controls the packet switch 10 and the flow table 20, and executes an OpenFlow agent for managing a secure channel with the OpenFlow controller 110.
  • the OpenFlow agent exchanges messages with the OpenFlow controller 110 based on the OpenFlow specifications, and reads information from the flow table 20 based on the messages.
  • the traffic between the computer systems 4 sharing the OpenFlow compatible network interface controller 120 can be detected as follows.
  • the OpenFlow controller 110 and the OpenFlow compatible network interface controller 120 exchange information regarding the functions provided in the OpenFlow compatible network interface controller 120, which of the ports included in the OpenFlow compatible network interface controller 120 is The function is extended so that information including information indicating whether the interface is for the computer system 14 is exchanged. Extensions like this are possible in the form of vendor extensions in OpenFlow. Thereby, the OpenFlow controller 110 can acquire information about which port of the OpenFlow compatible network interface controller 120 is the computer system interface 14.
  • the OpenFlow controller 110 acquires information on entries registered in the flow table 20 of the OpenFlow compatible network interface controller 120, and the input port included in the key and the output destination port included in the action are , It is determined whether or not both are the computer system interface 14. When both are the computer system interface 14, the flow can be recognized as traffic between the computer systems 4 sharing the open flow compatible network interface controller 120.
  • FIG. 9 is a block configuration diagram showing an example of the internal configuration of the OpenFlow switch 100 shown in the traffic management system 80 of FIG. 9 is different from the network switch 7 of FIG. 3 in that a flow table 73 and a control CPU 77 are added, and a forwarding table 72 and a packet switch management unit 76 are excluded.
  • the other parts are the same as those of the network switch 7 in FIG.
  • the same components as those of the network switch 7 of FIG. 3 are denoted by the same reference numerals as those of the network switch 7 of FIG. 3, and detailed description thereof is omitted here.
  • flow table 73 and the control CPU 77 have exactly the same functions as the flow table 20 and the control CPU 19 of the open flow compatible network interface controller 120, respectively. The detailed explanation is omitted.
  • a logical switch configured so that the network interface controller and the network switch are collectively managed to manage traffic. It can be suitably applied to the application.
  • Network Interface Controller 3 I / O Switch 4 Computer System 4a Computer System 4b Computer System 5 Network Interface Controller 6 Logical Switch Management System 7 Network Switch 8 Traffic Management System 10 Packet Switch 12 Forwarding Table 13 Loopback Table 14 Computer System Interface 16 External network port 17 Management interface 18 PCI-Express interface 19 Control CPU 20 Flow table 40 CPU 42 Memory 44 I / O Interface 60 Logical Switch Manager 62 Network Switch Manager 64 Network Interface Controller Manager 70 Packet Switch 72 Forwarding Table 73 Flow Table 74 Network Port 76 Packet Switch Manager 77 Control CPU 78 Management Interface 80 Traffic Management System 100 OpenFlow Switch 110 OpenFlow Controller 120 OpenFlow Compatible Network Interface Controller 130 Secure Channel Controller 140 OpenFlow Interface 600 Network Switch Manager Interface 610 Network Interface Controller Manager Interface 620 Logical Switch Forwarding Table Management Section 630 Logical switch port management section 640 Connection information management section 650 Mapping information management section 660 Logical switch management interface

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un système de gestion de trafic qui comprend : un ou plusieurs contrôleurs d'interface réseau (5) pour envoyer des informations à et recevoir des informations à partir d'un ou plusieurs systèmes informatiques ; un ou plusieurs commutateurs de réseau (7) qui envoient des informations à et reçoivent des informations à partir d'un réseau externe ; et un système de gestion de commutateur logique (6) qui regroupe et gère le trafic. Le contrôleur (5) est pourvu d'un mécanisme qui effectue en interne un traitement de transfert relatif au trafic d'un ou plusieurs systèmes informatiques partagés. Le système de gestion de commutateur logique (6) est muni d'un mécanisme qui acquiert des informations de configuration et des informations statistiques à partir du contrôleur (5) et du commutateur de réseau (7) et configure le résultat sous la forme d'un commutateur logique. En conséquence, il est possible de fournir un système de gestion de trafic qui permet de regrouper et de gérer le trafic qui s'écoule entre un contrôleur d'interface de réseau et un commutateur de réseau qui est connecté à celui-ci.
PCT/JP2014/002247 2013-10-07 2014-04-22 Système de gestion de trafic et procédé de gestion de trafic WO2015052854A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2015541415A JPWO2015052854A1 (ja) 2013-10-07 2014-04-22 トラフィック管理システムおよびトラフィック管理方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2013209858 2013-10-07
JP2013-209858 2013-10-07

Publications (1)

Publication Number Publication Date
WO2015052854A1 true WO2015052854A1 (fr) 2015-04-16

Family

ID=52812696

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/002247 WO2015052854A1 (fr) 2013-10-07 2014-04-22 Système de gestion de trafic et procédé de gestion de trafic

Country Status (2)

Country Link
JP (1) JPWO2015052854A1 (fr)
WO (1) WO2015052854A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017164219A1 (fr) * 2016-03-24 2017-09-28 日本電気株式会社 Dispositif de gestion d'informations statistiques, système de communication, procédé et programme de gestion d'informations statistiques

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009139170A1 (fr) * 2008-05-16 2009-11-19 パナソニック株式会社 Détecteur de paquets d'attaque, procédé de détection de paquets d'attaque, récepteur d'image, dispositif de stockage de contenu et dispositif de communication ip
JP2009296158A (ja) * 2008-06-03 2009-12-17 Alaxala Networks Corp 通信データ統計装置および通信データ統計方法
US20110032944A1 (en) * 2009-08-06 2011-02-10 Uri Elzur Method and System for Switching in a Virtualized Platform
US20110103389A1 (en) * 2009-11-03 2011-05-05 Blade Network Technologies, Inc. Method and apparatus for switching traffic between virtual machines
WO2012114398A1 (fr) * 2011-02-24 2012-08-30 Nec Corporation Système de réseau, système de commande et procédé de commande de flux

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009139170A1 (fr) * 2008-05-16 2009-11-19 パナソニック株式会社 Détecteur de paquets d'attaque, procédé de détection de paquets d'attaque, récepteur d'image, dispositif de stockage de contenu et dispositif de communication ip
JP2009296158A (ja) * 2008-06-03 2009-12-17 Alaxala Networks Corp 通信データ統計装置および通信データ統計方法
US20110032944A1 (en) * 2009-08-06 2011-02-10 Uri Elzur Method and System for Switching in a Virtualized Platform
US20110103389A1 (en) * 2009-11-03 2011-05-05 Blade Network Technologies, Inc. Method and apparatus for switching traffic between virtual machines
WO2012114398A1 (fr) * 2011-02-24 2012-08-30 Nec Corporation Système de réseau, système de commande et procédé de commande de flux

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017164219A1 (fr) * 2016-03-24 2017-09-28 日本電気株式会社 Dispositif de gestion d'informations statistiques, système de communication, procédé et programme de gestion d'informations statistiques

Also Published As

Publication number Publication date
JPWO2015052854A1 (ja) 2017-03-09

Similar Documents

Publication Publication Date Title
US9311120B2 (en) Method and system for virtual machine networking
JP5360607B2 (ja) Ｐｃｉエクスプレススイッチ、ｐｃｉエクスプレスシステム、及びネットワーク制御方法
US8750106B2 (en) Interface control system and interface control method
US8571408B2 (en) Hardware accelerated data frame forwarding
US7082138B2 (en) Internal communication protocol for data switching equipment
US20130117469A1 (en) Register access in distributed virtual bridge environment
TW201933837A (zh) 虛擬網路隧道內流量資料擷取方法與系統
US8493850B2 (en) Communication apparatus and frame transmission method
US20190266116A1 (en) Network controller - sideband interface port controller
US10050906B2 (en) Virtual node having separate control and data planes
US8989194B1 (en) Systems and methods for improving network redundancy and for facile initialization in a centrally-controlled network
US20160134559A1 (en) Network controller-sideband interface port controller
US9385951B2 (en) Apparatus and method for controlling packet transfer based on registered destination information
WO2014064976A1 (fr) Dispositif de réseau, procédé de commande et programme
KR101934908B1 (ko) Sdn 기반의 통합 라우팅에 의한 피씨 전원 제어 방법
US9755892B2 (en) Integrated device managment over Ethernet network
CN104471538B (zh) 一种数据流处理方法、设备和系统
WO2014126094A1 (fr) Système et procédé de communication, dispositif de gestion, et procédé et programme de contrôle de dispositif de gestion
WO2015052854A1 (fr) Système de gestion de trafic et procédé de gestion de trafic
US11533277B2 (en) Method and system for virtual channel remapping
US20050125523A1 (en) Methodology for remote HBA management using message encapsulation
KR20180040963A (ko) Sdn 기반의 통합 라우팅 방법 및 멀티 테넌트 지원 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14851670

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2015541415

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14851670

Country of ref document: EP

Kind code of ref document: A1