WO2017113929A1 - Procédé et contrôleur de commande de grappe de dispositifs de transfert dans un réseautage défini par logiciel - Google Patents

Procédé et contrôleur de commande de grappe de dispositifs de transfert dans un réseautage défini par logiciel Download PDF

Info

Publication number
WO2017113929A1
WO2017113929A1 PCT/CN2016/101780 CN2016101780W WO2017113929A1 WO 2017113929 A1 WO2017113929 A1 WO 2017113929A1 CN 2016101780 W CN2016101780 W CN 2016101780W WO 2017113929 A1 WO2017113929 A1 WO 2017113929A1
Authority
WO
WIPO (PCT)
Prior art keywords
member device
port
flow table
forwarding
virtual
Prior art date
Application number
PCT/CN2016/101780
Other languages
English (en)
Chinese (zh)
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 中兴通讯股份有限公司
Publication of WO2017113929A1 publication Critical patent/WO2017113929A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering

Definitions

  • the present invention relates to a software defined network, and more particularly to a method and a corresponding controller for controlling a forwarding device cluster in a software defined network.
  • SDN Software Defined Networking
  • the control layer in SDN is extracted by the control functions in the original network devices such as switches and routers, and is implemented by independent control software.
  • the control functions in the original switches and routers are stripped from the infrastructure layer, and the control plane uniformly implements the forwarding management.
  • OpenFlow is a protocol running between the controller and the forwarding device in the SDN network. The controller writes forwarding entries such as flow tables and group tables to the switch through the OpenFlow protocol to complete control of the entire network.
  • the SDN network Similar to the traditional network, in the SDN network, in order to achieve load balancing and high reliability, it is also necessary to deploy multiple forwarding devices in a specific location of the network to form a cluster, which operates in active/standby mode or load sharing mode. To meet this requirement, you can deploy a device that uses the traditional cluster technology.
  • the forwarding device cluster implements load balancing forwarding or active/standby switchover when the fault occurs.
  • the SDN controller is presented as a single device.
  • the present invention provides the following technical solutions.
  • a method for controlling a cluster of forwarding devices in a software-defined network comprising:
  • the software-defined network SDN controller treats the forwarding device cluster as a single virtual forwarding device for path decision, wherein the forwarding device cluster includes multiple independently running member devices;
  • the SDN controller obtains the flow table of the member device according to the result of the path decision, and sends the flow table to the member device, and controls the outgoing traffic of the member device and the member device by using the flow table.
  • a controller in a software-defined network comprising: a cluster control device, the cluster control device comprising:
  • the path decision module is configured to perform the path decision by using the forwarding device cluster as a single virtual forwarding device, where the forwarding device cluster includes multiple independent running member devices;
  • the flow table generating module is configured to obtain a flow table of the member device according to the result of the path decision, and control, by using the flow table, the outward flow of traffic between the member devices and the member device;
  • the flow table sending module is configured to send the flow table of the member device to the member device.
  • the above schemes fully utilize the characteristics of the network-defined network to perform centralized control on the network devices.
  • the multiple forwarding devices that operate independently are used as a cluster to control the outbound traffic forwarding between the member devices of the cluster and the member devices. There is no need to run a proprietary protocol between the member devices, and the inter-communication between the member devices and the controller is not required.
  • Embodiment 1 is a flow chart of a control method according to Embodiment 1 of the present invention.
  • FIG. 2 is a block diagram of an SDN controller according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of an example of a forwarding device cluster of the present invention.
  • the embodiment of the present invention provides a method for controlling a forwarding device cluster in a software-defined network.
  • the SDN controller controls the independently-operated forwarding device through the OpenFlow protocol (or other flow control protocol) to form a forwarding device cluster.
  • the OpenFlow protocol or other flow control protocol
  • the method for controlling the forwarding device cluster in the software definition network in this embodiment is as shown in FIG. 1 and includes:
  • Step 110 The SDN controller considers the forwarding device cluster as a single virtual forwarding device to perform path decision, where the forwarding device cluster includes multiple independent running member devices.
  • the path decision includes: determining that the virtual forwarding device forwards the traffic (that is, forwards the packet) as a virtual port of the egress port, and the virtual port can be classified into two types: an unbundled port and/or Or a bundled port, where each unbundled port corresponds to a physical port on a member device; each bundle port corresponds to multiple external physical ports on one or more member devices.
  • Step 120 The SDN controller obtains a flow table of the member device according to the result of the path decision, and sends the flow table to the member device, and controls the outgoing traffic of the member device and the member device by using the flow table. .
  • outgoing traffic forwarding of member devices refers to traffic forwarding outside the forwarding device cluster.
  • the SDN controller controls the outgoing traffic forwarding between the member devices and the member device by using a flow table, including:
  • the first member device forwards the traffic directly from the device, and controls the second member device to forward the traffic from the device to the at least one first member device; wherein the first member device refers to A member device of the physical port corresponding to the virtual port, where the second member device refers to a member device that does not have a physical port corresponding to the virtual port.
  • the SDN controller obtains the flow table of the member device according to the result of the path decision, and may adopt the following manner: generating a unicast flow table of the virtual forwarding device according to the result of the path decision
  • the unicast flow table includes the virtual port as an egress port; and the unicast flow table is modified for each member device to obtain a flow table of the member device;
  • the modification includes: replacing the egress port with the physical port corresponding to the virtual port on the first member device;
  • the modifying includes: The physical port for the first bypass link is replaced by the second member device, and the first bypass link is the link of the second member device to the first member device.
  • the member device When the unicast traffic is forwarded, the member device includes a physical port as an egress port, and the traffic is forwarded from the physical port; and the delivered flow table includes multiple physical ports as egress ports. At time, one physical port may be selected to forward traffic from the plurality of physical ports. The specific selection may be performed according to one or more of the following (two or more, any combination) strategies: a load balancing strategy; a priority policy; and a random selection strategy. In the port list delivered by the controller to the member device, you can also set the weight for each port for the member device to select when the port is selected.
  • the SDN controller controls the outbound traffic forwarding between the member devices and the member device by using a flow table, including:
  • the first member device For each first member device, the first member device is controlled to directly forward the traffic from the first member device by using a flow table, and for the traffic from outside the cluster of the forwarding device, the first member device is also controlled.
  • the traffic is forwarded from the first member device to the other first member device that meets the following conditions: at least one of the virtual ports corresponding to the physical port is different from the virtual port corresponding to the physical port on the first member device;
  • the second member device is controlled by the flow table to forward traffic from the second member device to the first member device in the forwarding device cluster to switch traffic back to each of the virtual ports. Forward again;
  • the first member device refers to a member device that has a physical port corresponding to the virtual port
  • the second member device refers to a member device that does not have a physical port corresponding to the virtual port.
  • the first modification includes: replacing the flag indicating that the packet is from the inside of the cluster as a new matching entry, and replacing the egress port with the physical port corresponding to the virtual port on the member device;
  • the second modification includes Replacing the egress port with the physical port corresponding to the virtual port and the physical port set as the second bypass link on the member device, where the second bypass link is the first member device to the other first a link of the member device;
  • the third modification includes: replacing the egress port with the physical port set as the third bypass link on the second member device, and adding a command or an action to indicate that the packet is from the packet a flag inside the cluster;
  • the third bypass link is a link of the second member device to the first member device.
  • the third bypass link may include a link of the second member device to the first member device that satisfies the following condition 1 and condition 2, in addition to the link that receives the traffic, and selects in the following manner.
  • the virtual port corresponding to the physical port on the member device includes an unbundled port
  • the virtual port corresponding to the physical port on the member device includes a first bundle port, and the first bundle port refers to a bundle port corresponding to multiple physical ports on one member device;
  • the first member device is selected from the first member devices in which the virtual port corresponding to the physical port is the second bundle port and the corresponding second bundle port is the same, and the second bundle port is selected.
  • a bundle port corresponding to multiple physical ports on multiple member devices, the selection is performed according to one or more of the following strategies: a load balancing policy; a priority policy; and a random selection policy.
  • This embodiment is directed to the offline, fault, and new equipment that may occur in the forwarding device cluster.
  • the corresponding flow table control method is also proposed, as follows:
  • the SDN controller determines that a member device in the forwarding device cluster is offline, the offline member device and its port are deleted from the member device surviving the forwarding device cluster; each of the forwarding device clusters survives If the member device's flow table has an outbound port connected to the offline member device, the member device's flow table is deleted from the outbound port of the offline member device, and the updated flow table is resent to the member device.
  • the member device After the SDN controller determines that a member device in the forwarding device cluster is offline, the offline member device and its port are deleted from the member device surviving the forwarding device cluster; each of the forwarding device clusters survives If the member device's flow table has an outbound port connected to the offline member device, the member device's flow table is deleted from the outbound port of the offline member device, and the updated flow table is resent to the member device. The member device.
  • the SDN controller determines that the status of a virtual port as the egress port becomes inactive (ie, fails)
  • the physical port corresponding to the virtual port is deleted from the egress port of the corresponding flow table;
  • the updated flow table is re-delivered to the corresponding member device;
  • the member device corresponding to the flow table is connected to the entity of the first member device.
  • the port is added to the egress port of the flow table, and the updated flow table is re-delivered to the corresponding member device.
  • the SDN controller determines that a member device is connected to the physical port of the first member device or the link corresponding to the physical port is invalid, the physical port of the member device is updated as the physical port of the egress port.
  • the updated flow table is resent to the member device for connecting to the physical port of the other first member device.
  • the SDN controller After the SDN controller determines that the forwarding device cluster is in a split state (ie, the clusters become two or more parts that are not connected to each other), record an interconnection port between the inactive virtual port and the member device. And the link between the member devices that are invalidated, and the linkage port on the member device is disabled; and the path determination is performed on the virtual forwarding device, and the flow table of the member device is obtained according to the result of the path decision. And sent to the member device.
  • the flow table of the member device is obtained according to the result of the path decision, and is sent to the member device, and the member device has the virtual port.
  • the corresponding physical port (for example, if the newly added member device has a physical port added to the existing bundle port), the flow table of the original member device is updated and delivered to the corresponding member device according to the new topology of the forwarding device cluster. .
  • the embodiment also provides a controller in a software-defined network, including a cluster control device.
  • the cluster control device includes:
  • the path decision module 10 is configured to perform the path decision by using the forwarding device cluster as a single virtual forwarding device, where the forwarding device cluster includes multiple independent running member devices;
  • the flow table generating module 20 is configured to obtain a flow table of the member device according to the result of the path decision, and control, by using the flow table, the outward flow forwarding between the member devices and the member device;
  • the flow table issuing module 30 is configured to send the flow table of the member device to the member device.
  • the path decision module 10 performs a path decision, including: determining a virtual port that is an outbound port that forwards the traffic to the virtual forwarding device, where the virtual port includes an unbundled port and/or a bundle port, where: each unbundled A port corresponds to a physical port on a member device. Each bundle port corresponds to multiple external physical ports on one or more member devices.
  • the flow table generating module 20 controls the outbound traffic forwarding between the member devices and the member device by using the flow table, including: when the traffic forwarding is unicast traffic forwarding, the first member device is controlled by the flow table.
  • the traffic is directly forwarded from the device, and the second member device is configured to forward the traffic from the device to the at least one first member device.
  • the first member device refers to the physical port corresponding to the virtual port.
  • Member set refers to a member device that does not have a physical port corresponding to the virtual port.
  • the flow table generating module 20 obtains the flow table of the member device according to the result of the path decision, and includes: when the traffic is forwarded to the unicast traffic, the unicast flow table of the virtual forwarding device is generated according to the result of the path decision.
  • the unicast flow table includes the virtual port as an egress port; and the unicast flow table is modified for each member device to obtain a flow table of the member device;
  • the modification includes: replacing the egress port with a physical port corresponding to the virtual port on the first member device;
  • the modification includes: replacing the egress port with the physical port set as the first bypass link on the second member device, where the first bypass link is the link of the second member device to the first member device.
  • the flow table generating module 20 controls the outbound traffic forwarding between the member devices and the member device by using the flow table, including: when the traffic forwarding is broadcast or multicast traffic forwarding, for each first member device And controlling, by the flow table, the first member device to directly forward the traffic from the first member device, and controlling, by the first member device, the traffic from the first member device for the traffic from the outside of the forwarding device cluster Forwarding to the other first member device that meets the following conditions: at least one of the virtual ports corresponding to the physical port is different from the virtual port corresponding to the physical port on the first member device; and, for each second member device, the flow table is Controlling, by the second member device, the traffic from the second member device to the first member device in the forwarding device cluster, to forward the traffic back to each of the virtual ports, and then forward the traffic; wherein, the first A member device refers to a member device having a physical port corresponding to the virtual port, and the second member device refers to having no pair with the virtual port. Members device entity port.
  • the flow table generating module 20 obtains the flow table of the member device according to the result of the path decision, including: when the traffic forwarding is broadcast or multicast traffic forwarding, generating a broadcast of the virtual forwarding device according to the result of the path decision a multicast flow table, the broadcast or multicast flow table including the virtual port as an egress port; and for each of the first member devices, performing a first modification and a second modification on the broadcast or multicast flow table Obtaining a first flow table and a second flow table of the first member device respectively;
  • the first modification includes: replacing the flag indicating that the packet is from the inside of the cluster as a new matching entry, and replacing the egress port with the physical port corresponding to the virtual port on the member device; the second modification includes Replacing the egress port with the physical port corresponding to the virtual port and the physical port set as the second bypass link on the member device, where the second bypass link is the first member device to the other first The link of the member device.
  • the flow table generating module 20 obtains the flow table of the member device according to the result of the path decision, and includes: when the traffic forwarding is broadcast or multicast traffic forwarding, generating the virtual forwarding device according to the result of the path decision. a broadcast or multicast flow table, the broadcast or multicast flow table including the virtual port as an egress port; for each of the second member devices, performing a third modification on the broadcast or multicast flow table to obtain a flow table of the second member device;
  • the third modification includes: replacing the egress port with the physical port for the third bypass link on the second member device, and adding a command or an action to mark the packet with a flag indicating that the packet is from the inside of the cluster;
  • the third bypass link is a link of the second member device to the first member device.
  • the third bypass link includes a link of the second member device to the first member device that satisfies the following condition 1 and condition 2, in addition to the link that receives the traffic, and the first member selected in the following manner Device link:
  • the virtual port corresponding to the physical port on the member device includes an unbundled port
  • the virtual port corresponding to the physical port on the member device includes a first bundle port, and the first bundle port refers to a bundle port corresponding to multiple physical ports on one member device;
  • the first member device is selected from the first member devices in which the virtual port corresponding to the physical port is the second bundle port and the corresponding second bundle port is the same, and the second bundle port is selected.
  • the selection is performed according to one or more of the following strategies: a load balancing policy; a priority policy; and a random selection policy.
  • the cluster control device further includes one or more of the following modules:
  • the offline processing module is configured to: after determining that a member device in the forwarding device cluster is offline, deleting the offline member device and its port from the member device surviving the forwarding device cluster; and surviving the forwarding device cluster If the member device's flow table has an egress port connected to the offline member device, the egress port of the member device's flow table connected to the offline member device is deleted, and the updated flow table is re-updated. Issued to the member device;
  • the port failure processing module is configured to delete the physical port corresponding to the virtual port from the egress port of the corresponding flow table after determining that the status of the virtual port as the egress port becomes inactive; and For each flow table, the updated flow table is re-sent to the corresponding member device; for each flow table that has no outgoing port after the deletion, the member device corresponding to the flow table is connected to the first member device.
  • the physical port is added to the egress port of the flow table, and the updated flow table is re-delivered to the corresponding member device.
  • the communication fault processing module is configured to: after determining that the physical port of the member device is connected to the first member device or the link corresponding to the physical port is invalid, the flow table of the member device is used as the out port The physical port is updated to be connected to the physical port of the other first member device, and the updated flow table is resent to the member device;
  • the cluster split processing module is configured to: after determining that the forwarding device cluster is in a split state, the record is in An interconnection port between the inactive virtual port and the member device, and a link between the failed member devices, and disabling the linkage port on the member device; and restarting the virtual forwarding device Performing a path decision, and obtaining a flow table of the member device according to the result of the path decision and delivering the flow table to the member device;
  • the member joins the processing module, and the SDN controller determines that a member device joins the forwarding device cluster, obtains a flow table of the member device according to the result of the path decision, and sends the flow table to the member device, and has the member device
  • the flow table of the original member device is updated and sent to the corresponding member device according to the new topology of the forwarding device cluster.
  • This example involves the formation and configuration of a cluster.
  • the SDN controller controls multiple independent forwarding devices through the OpenFlow protocol to form a forwarding device cluster, which is presented as an integrated logical device.
  • the cluster consists of two OpenFlow forwarding devices, identified as DPID 1 and DPID 2.
  • the two forwarding devices have ports numbered 1, 2, 3, 4, 5, and 6, respectively.
  • the link between the member devices of the forwarding device cluster is, the link between port 3 of DPID 1 and port 3 of DPID 2, port 4 of DPID 1 and port 4 of DPID 2 in FIG. Not visible outside the cluster.
  • the link between the member devices can be configured by the administrator.
  • the SDN controller maintains the status of the internal link through link detection or path detection.
  • the virtual forwarding device presented by the forwarding device cluster exposes six ports (1, 2, 3, 4, 5, and 6 in Figure 1) and is divided into two categories:
  • Unbundled ports (1, 2, 3, 4) An unbundled port directly corresponds to a physical port on a member device that constitutes the cluster (that is, outside the cluster), such as port 1, 2, and DPID2 on DPID1. Port 1, 2. An unbundled port is interconnected with a neighbor device through an unbundled link. The port status directly corresponds to the state of the physical port.
  • Bundle port corresponds to one or more members of the cluster to forward multiple physical ports on the device. For example, port 5 on DPID 1 and port 5 on DPID 2 are bundled to form port 5, DPID. Port 6 on 1 and port 6 on DPID 2 are bundled to form port 6. When any of the physical port states is active, the bundled port status is active. When all port states are inactive, the bundled port status is inactive. . The bundled port is connected to the neighbor through the bundled link. The corresponding port of the neighboring device must also be bundled. It can be statically configured or negotiated through the aggregation protocol.
  • This example relates to the control of unicast traffic forwarding for a forwarding device cluster.
  • the SDN controller of this example delivers forwarding entries through the OpenFlow protocol to control and forward the device cluster.
  • Off unicast traffic forwarding including:
  • Step 1 The SDN controller regards the forwarding device cluster as a virtual forwarding device, and performs a path decision according to the network topology, and obtains a unicast flow table for controlling the virtual forwarding device to forward the unicast traffic.
  • Step 2 The SDN controller modifies the unicast flow table according to the physical port on the member device corresponding to the virtual port of the outbound port in the unicast flow table, and obtains the flow table of each member device and sends the flow table to each member device.
  • the following traffic forwarding control can be implemented through a flow table:
  • the device has a physical port corresponding to the virtual port (corresponding to the first member device in the above, the physical port on the device may correspond to the unbundled port, and may also correspond to If the physical port is one of the plurality of physical ports corresponding to the bundled port, the physical port is controlled by the flow table to control the member device to forward the traffic directly from the device. Go out.
  • the member device If the traffic needs to be sent back through the other member devices of the cluster, that is, if the device does not have a physical port corresponding to the virtual port (corresponding to the second member device in the above), the member device is controlled to flow back through the flow table. Forward to other member devices.
  • the member device can select one of the outbound port groups in the flow table as the actual forwarding port.
  • Example 1 The virtual outgoing port is 1, 5.
  • Both the DPID 1 and the DPID 2 can forward the traffic directly, and the following ports are selected as the egress port in the flow table delivered to the DPID 1 and the DPID 2: the egress port of the flow table delivered to the DPID 1 is 1, 5, and the DPID 2 The outgoing port of the delivered flow table is 5.
  • Example 2 The virtual outgoing port is 1, 2.
  • the DPID 1 can directly forward the traffic.
  • the port is determined by the method in the example 1.
  • the outgoing port of the forwarding table sent to DPID 1 is 1, 2.
  • the DPID 2 needs to forward the traffic to the DPID 1 and the port corresponding to the bypass link of the member device with the available egress port as the egress port.
  • the egress port of the flow table delivered to DPID 2 is 3 or 4.
  • This example relates to the control of forwarding device cluster broadcast or multicast traffic forwarding.
  • the SDN controller of this example delivers forwarding entries through the OpenFlow protocol to control traffic broadcast or multicast forwarding related to the forwarding device cluster, including:
  • Step 1 The SDN controller regards the forwarding device cluster as a virtual forwarding device, performs path decision according to the network topology, and obtains a broadcast or multicast flow table for controlling the virtual forwarding device to forward broadcast or multicast traffic; broadcast or multicast Packets need to be forwarded from multiple ports on the virtual forwarding device.
  • Step 2 The SDN controller modifies the broadcast or multicast flow table according to the physical port on the member device corresponding to the virtual port of the outbound port in the broadcast or multicast flow table, and obtains the flow table of each member device and delivers the flow table to each member device. Member equipment.
  • the following traffic forwarding control can be implemented through a flow table:
  • the packets received from the cluster member devices are controlled by the flow table to forward the traffic directly from the device.
  • the packets received by the device other than the cluster are forwarded through the flow table to control the member device to forward traffic from the device.
  • the device also controls the member device to forward the device from the device to other first member devices. At least one of the virtual ports corresponding to the physical port on the first member device is different from the virtual port corresponding to the physical port on the device. That is, if another first member device has the same bundle port as the own device, it may not be forwarded to the other first member device.
  • the member device is controlled by the flow table to forward the traffic from the device to the first member device, so that the traffic is returned to each device.
  • the virtual port is forwarded again.
  • a member port of a bundled port is distributed among multiple forwarding devices, and multiple internal links are available between a pair of devices.
  • the controller needs to select which ports to join the outbound port list to prevent multiple packets from being sent back. Port output. See the detailed description above for how to specifically select the link when detouring.
  • a command or an action is added to the forwarding table that is sent to the second member device, and the flag indicating that the packet is from the cluster is added to the forwarded packet, for example, by adding a VLAN tag or a tunnel identifier. Mark the flag for subsequent device identification and determine subsequent forwarding actions.
  • a flow table is sent to the DPID 1 (also referred to as a forwarding entry).
  • a flow table adds a matching item for identifying the packet received from the DPID 2 on the basis of the original matching item, and the egress port is 1, and the other port is 1.
  • the outbound port of a flow table is 1, 5.
  • One forwarding entry is sent to and from the DPID 2, and the egress port is 5, 3. However, the packet sent from the DPID 1 is directly discarded, that is, the link that receives the packet is not used as the bypass link.
  • a flow table that restores traffic to normal forwarding including:
  • Step 1 The SDN controller detects that a member device in the forwarding device cluster is offline.
  • Step 2 The SDN controller maintains the state of the forwarding device cluster, and removes the offline device and related ports from the cluster;
  • Step 3 If the traffic received by other surviving member devices in the cluster is originally forwarded by the offline device, you need to select other available bypass paths. Therefore, the SDN controller updates the flow table of these devices, that is, the original outgoing port connected to the offline device should be deleted, and only the outgoing port to other retractable devices is reserved.
  • the SDN controller restores the normal forwarding of the traffic by updating the entries on the surviving device, including:
  • Step 1 The forwarding device reports, or the SDN controller detects that the status of a port on the cluster member is changed to inactive.
  • Step 2 The SDN controller deletes the port from the affected flow table, that is, updates the flow table:
  • the device If the member device of the port is removed from the egress port of the member device, the device does not have any member ports of the port. If the device needs to be bypassed by other devices, the device is added to the port of the device. Out port
  • the original forwarding path is forwarded through the port.
  • the bypass path is modified, and the port is removed from the outbound port of the flow table, and the outgoing port of the other switchable device is reserved.
  • the SDN controller restores the normal forwarding of the traffic by updating the entries on the surviving device, including:
  • Step 1 The forwarding device reports or the controller detects that a port connected to other members on the cluster member is changed to inactive, or the controller detects that the internal path of the cluster is invalid.
  • Step 2 For the member devices that need to be forwarded through the port or link, modify the egress port in the flow table and switch back from other links.
  • the SDN controller disables the port on the device by performing the port linkage policy, triggers the path recalculation and resumes normal forwarding, including:
  • Step one the SDN controller determines that the cluster is in a split state
  • the forwarding device reports or the controller detects the inter-cluster port connectivity.
  • the state changes to inactive, etc., and the SDN controller can determine whether the cluster is in a split state, that is, become multiple parts that are not connected to each other.
  • Step 2 The SDN controller disables the linkage port on the device according to the linkage policy; if the linkage port includes a port that should be closed after a port fails.
  • Step 3 The SDN controller recalculates the path according to the current cluster topology, and delivers the forwarding table, so that the traffic is forwarded through other member devices of the cluster and other member ports of the bundled port.
  • This example involves a method in which a member of the cluster is in a normal working state, a faulty member is restored, or a new member device is added, and the SDN controller joins the device to the cluster to enable traffic to be forwarded by the device, including:
  • Step 1 The cluster member device establishes a connection with the controller and completes initialization, and the SDN controller joins the device to the cluster to maintain the related state.
  • Step 2 The SDN controller generates a delivered entry for the newly added device, and updates the flow table of the other device according to the new cluster topology.
  • Step 3 The flow meter is sent, and the newly added device can be used normally.
  • serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic).
  • the disc, the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the controllers described in various embodiments of the present invention.
  • the modules such as the path decision module, the flow table generation module, and the flow table delivery module may include software loaded on a server or related device and/or combined or interacted with related hardware.
  • the path decision module may include a corresponding logic circuit.
  • the corresponding program in the server system may be each functional module in the same software system, or may belong to different software/operating systems.
  • the invention is applicable to the field of the software-defined network, and is used for inter-communication between the member devices without running a proprietary protocol, and the link maintenance of the member device and the controller does not need special processing, and is relatively simple.

Abstract

L'invention concerne un procédé et un contrôleur permettant de commander une grappe de dispositifs de transfert dans un réseautage défini par logiciel (SDN). Le contrôleur SDN effectue une sélection de chemin en considérant la grappe de dispositifs de transfert comme un dispositif de transfert virtuel unique, la grappe de dispositif de transfert comprenant une pluralité de dispositifs membres fonctionnant indépendamment; et le contrôleur SDN obtient une table de flux des dispositifs membres selon un résultat de sélection de chemin, envoyant la table de flux aux dispositifs membres de sorte à commander le transfert de trafic entre les dispositifs membres et le transfert de trafic sortant des dispositifs membres. Le réseautage défini par logiciel est caractérisé par une commande centralisée de dispositifs de réseau et la présente invention tire avantage de cette caractéristique pour commander le transfert de trafic entre les dispositifs membres et le transfert de trafic sortant des dispositifs membres par l'intermédiaire d'une table de flux. L'interopérabilité de différents fabricants peut être obtenue sans exiger que des protocoles privés soient exécutés parmi les dispositifs membres; en outre, le maintien d'une liaison des dispositifs membres et du contrôleur ne nécessite aucun traitement spécial et est simplifié.
PCT/CN2016/101780 2015-12-29 2016-10-11 Procédé et contrôleur de commande de grappe de dispositifs de transfert dans un réseautage défini par logiciel WO2017113929A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201511020591.X 2015-12-29
CN201511020591.XA CN106936609B (zh) 2015-12-29 2015-12-29 一种软件定义网络中控制转发设备集群的方法及控制器

Publications (1)

Publication Number Publication Date
WO2017113929A1 true WO2017113929A1 (fr) 2017-07-06

Family

ID=59224569

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101780 WO2017113929A1 (fr) 2015-12-29 2016-10-11 Procédé et contrôleur de commande de grappe de dispositifs de transfert dans un réseautage défini par logiciel

Country Status (2)

Country Link
CN (1) CN106936609B (fr)
WO (1) WO2017113929A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112272105A (zh) * 2020-09-16 2021-01-26 浪潮思科网络科技有限公司 一种sdn控制器集群成员的控制方法、系统及介质
CN112491744A (zh) * 2020-11-13 2021-03-12 浪潮思科网络科技有限公司 一种端口流量镜像方法、设备及介质
CN113746730A (zh) * 2021-08-25 2021-12-03 新华三大数据技术有限公司 一种路由信息处理方法及装置
CN114070889A (zh) * 2021-11-10 2022-02-18 北京百度网讯科技有限公司 配置方法、流量转发方法、设备、存储介质及程序产品

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109412943B (zh) * 2017-08-18 2022-04-05 中兴通讯股份有限公司 一种sdn控制器集群流量处理方法、装置、设备及存储介质
CN108011825B (zh) * 2017-11-10 2020-07-28 深圳市泰信通信息技术有限公司 一种基于软件定义网络的多网络设备互联现实方法及系统
CN108494700B (zh) * 2018-02-02 2022-11-01 百度在线网络技术（北京）有限公司 跨链路数据传输方法、装置、计算机设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931587A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 虚拟集群路由方法及系统
CN104426731A (zh) * 2013-08-23 2015-03-18 杭州华三通信技术有限公司 一种生成树计算的方法和装置
CN104426792A (zh) * 2013-09-05 2015-03-18 中兴通讯股份有限公司 调度器支持能力的查询、通知方法及装置
CN104767778A (zh) * 2014-01-07 2015-07-08 中兴通讯股份有限公司 任务处理方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581058B (zh) * 2012-07-31 2017-02-15 杭州华三通信技术有限公司 数据中心网络中的报文转发方法和装置
CN103973676B (zh) * 2014-04-21 2017-05-24 蓝盾信息安全技术股份有限公司 一种基于sdn的云计算安全保护系统及方法
CN103986651B (zh) * 2014-05-30 2018-03-06 新华三技术有限公司 一种软件定义网络控制器及其控制方法
CN104407911B (zh) * 2014-10-31 2018-03-20 新华三技术有限公司 虚拟机迁移方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931587A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 虚拟集群路由方法及系统
CN104426731A (zh) * 2013-08-23 2015-03-18 杭州华三通信技术有限公司 一种生成树计算的方法和装置
CN104426792A (zh) * 2013-09-05 2015-03-18 中兴通讯股份有限公司 调度器支持能力的查询、通知方法及装置
CN104767778A (zh) * 2014-01-07 2015-07-08 中兴通讯股份有限公司 任务处理方法及装置

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112272105A (zh) * 2020-09-16 2021-01-26 浪潮思科网络科技有限公司 一种sdn控制器集群成员的控制方法、系统及介质
CN112272105B (zh) * 2020-09-16 2023-04-18 浪潮思科网络科技有限公司 一种sdn控制器集群成员的控制方法、系统及介质
CN112491744A (zh) * 2020-11-13 2021-03-12 浪潮思科网络科技有限公司 一种端口流量镜像方法、设备及介质
CN113746730A (zh) * 2021-08-25 2021-12-03 新华三大数据技术有限公司 一种路由信息处理方法及装置
CN114070889A (zh) * 2021-11-10 2022-02-18 北京百度网讯科技有限公司 配置方法、流量转发方法、设备、存储介质及程序产品
CN114070889B (zh) * 2021-11-10 2023-11-14 北京百度网讯科技有限公司 配置方法、流量转发方法、设备、存储介质及程序产品

Also Published As

Publication number Publication date
CN106936609A (zh) 2017-07-07
CN106936609B (zh) 2020-10-16

Similar Documents

Publication Publication Date Title
WO2017113929A1 (fr) Procédé et contrôleur de commande de grappe de dispositifs de transfert dans un réseautage défini par logiciel
US9628375B2 (en) N-node link aggregation group (LAG) systems that can support various topologies
CN110166356B (zh) 发送报文的方法和网络设备
US9614727B2 (en) N-node systems and methods for link aggregation groups (LAG)
US8730963B1 (en) Methods, systems, and computer readable media for improved multi-switch link aggregation group (MLAG) convergence
US8619605B2 (en) Method and apparatus for maintaining port state tables in a forwarding plane of a network element
US8654630B2 (en) Techniques for link redundancy in layer 2 networks
CN101155109B (zh) 一种以太网交换系统及设备
US20150172098A1 (en) Link aggregation in software-defined networks
US20140301401A1 (en) Providing aggregation link groups in logical network device
JP5488979B2 (ja) コンピュータシステム、コントローラ、スイッチ、及び通信方法
EP3213441B1 (fr) Redondance pour chaînes d'extension de port
CN104639464A (zh) OpenFlow交换机上实现跨交换机链路聚合的系统及方法
US20140369184A1 (en) General User Network Interface (UNI) Multi-homing Techniques For Shortest Path Bridging (SPB) Networks
CN105162704A (zh) Overlay网络中组播复制的方法及装置
WO2021082812A1 (fr) Procédé d'envoi de message et premier dispositif de réseau
WO2020114017A1 (fr) Procédé et appareil d'échange de trafic de centre de données, dispositif et support d'informations
CN111901133B (zh) 一种组播切换方法、装置、网络设备和存储介质
JP6109954B2 (ja) 仮想シャーシシステムにおけるパススルーモードのためのシステムおよび方法
CN110011912A (zh) 机箱式交换设备上行链路切换方法及装置
WO2020156355A1 (fr) Système, dispositif et procédé de partage de charge, carte unique et support de stockage
WO2023065750A1 (fr) Procédé et appareil de synchronisation d'état, et dispositif
CN116614436A (zh) 一种流量转发方法、装置、系统及主备交换机
KR101260646B1 (ko) 데이터 전달 방법 및 이를 이용한 네트워크 시스템

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: 16880721

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16880721

Country of ref document: EP

Kind code of ref document: A1