WO2020114017A1 - 数据中心流量互通方法、装置、设备及存储介质 - Google Patents

数据中心流量互通方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2020114017A1
WO2020114017A1 PCT/CN2019/103115 CN2019103115W WO2020114017A1 WO 2020114017 A1 WO2020114017 A1 WO 2020114017A1 CN 2019103115 W CN2019103115 W CN 2019103115W WO 2020114017 A1 WO2020114017 A1 WO 2020114017A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
physical
data center
port
logical
Prior art date
Application number
PCT/CN2019/103115
Other languages
English (en)
French (fr)
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 RU2021116294A priority Critical patent/RU2761186C1/ru
Priority to EP19894333.4A priority patent/EP3866393A4/en
Priority to JP2021526365A priority patent/JP7190569B2/ja
Publication of WO2020114017A1 publication Critical patent/WO2020114017A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • 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
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/12—Discovery or management of network topologies
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • the present application relates to the field of communications, and in particular, to a data center flow interworking method, device, equipment, and storage medium.
  • IDC Internet Data Center
  • VMs Virtual Machines
  • ICP Internet Content Provider, network content service provider
  • OTT Over The Top
  • service providers provide content and services through the network
  • more and more users Traffic is to access the content and services provided by ICP/OTT
  • the data center is the main platform for the content and services provided by ICP/OTT.
  • IT Information Technology
  • Data center traffic is divided into north-south traffic and east-west traffic.
  • the north-south direction is based on user access to data center content.
  • East-west traffic mainly refers to synchronization, backup, and CDN (Content Delivery Network) content push traffic within or across data centers.
  • CDN Content Delivery Network
  • the traffic between data centers is mainly carried on the Internet. Redundant protection of data center network traffic is a basic requirement for network reliability.
  • the physical stacking mode of the gateway is generally used to support redundant protection of egress traffic in the data center.
  • stacking mode the upstream and downstream of the physical device of the gateway does not sense the actual state switching of the gateway. There is a problem that two devices must be upgraded at the same time when the version is upgraded, and the network interruption time is longer.
  • the traditional data center network does not have a centralized control point, which results in the inability to manage the data center network traffic globally and schedule the network traffic in a unified manner, resulting in a problem of high operation and maintenance complexity.
  • Embodiments of the present application provide a data center traffic interworking method, device, equipment, and storage medium, to solve at least some problems in the prior art.
  • a data center traffic interworking method is provided with an SDN controller.
  • the method includes: configuring at least two gateway physical devices connected to the SDN controller as one logical device, wherein the gateway physical device
  • the physical port is a logical port of the logical device; based on an optimal network path and an association relationship to implement traffic communication between the data center and an external network, wherein the optimal network path is the physical port from the logical port to the gateway physical device
  • the association relationship is the relationship between the physical port of the gateway physical device and the external network.
  • the configuring at least two physical devices of the gateway connected to the SDN controller as one logical device includes: configuring the VTEP Group attribute on the SDN controller to MC-LAG; Based on the VTEP Group attribute, at least two physical devices of the gateway connected to the SDN controller are configured as a logical device.
  • configuring the at least two gateway physical devices accessing the SDN controller as one logical device includes: virtualizing the physical port of the gateway physical device as the logical device Logical port.
  • the virtualizing the physical port of the gateway physical device as the logical port of the logical device includes: configuring MC-LAG link information of the gateway physical device.
  • the configuring the MC-LAG link information of the physical device of the gateway includes: virtualizing at least two cross-rack stacking ports of the MC-LAG link into one logical port .
  • the virtualizing the physical port of the gateway physical device as the logical port of the logical device further includes: configuring peer link information of the gateway physical device.
  • the method before the step of implementing the flow communication between the data center and the external network based on the optimal network path and the association relationship, the method further includes: acquiring the logical port to the physical port of the gateway physical device The optimal network path.
  • the obtaining the optimal network path from the logical port to the physical port of the gateway physical device includes: obtaining routing information of the gateway physical device; based on the routing Information to calculate the optimal network path.
  • the method before the step of implementing the flow communication between the data center and the external network based on the optimal network path and the association relationship, the method further includes: configuring the physical port of the gateway physical device to associate with the external network relationship.
  • the association relationship between the physical port configuring the gateway physical device and the external network includes: configuring VDC or DCI service configuration information; orchestrating according to the VDC or DCI service configuration information The information of the SDN domain and the traditional domain of the gateway physical device, so as to obtain the association relationship between the physical port of the gateway physical device and the external network.
  • a network device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, when the computer program is executed by the processor.
  • a computer-readable storage medium has stored thereon a computer program, which when executed by a processor implements the steps of the method of any one of the first aspects.
  • FIG. 1 is a schematic block diagram of interaction of various modules of the SDN controller orchestrating data center network equipment according to Embodiment 1 of the present application to implement redundant protection of gateway egress traffic;
  • FIG. 3 is a flowchart of virtualizing a physical port of the physical device of the gateway into a logical port of the logical device according to Embodiment 1 of the present application;
  • FIG. 4 is a flowchart of obtaining an optimal network path for forwarding the traffic received by the logical port to the physical port of the physical device of the gateway according to Embodiment 1 of the present application;
  • FIG. 5 is a flowchart of configuring an association relationship between a physical port of the gateway physical device and an external network according to Embodiment 1 of the present application;
  • FIG. 6 is a block diagram of a networking of a data center traffic intercommunication device according to Embodiment 2 of this application;
  • FIG. 7 is a schematic block diagram of a data center traffic intercommunication device according to Embodiment 2 of the present application.
  • FIG. 8 is a functional block diagram of a logical device configuration module according to Embodiment 2 of the present application.
  • FIG. 9 is a functional block diagram of a logical interface configuration module according to Embodiment 2 of this application.
  • FIG. 10 is a schematic block diagram of a path calculation module according to Embodiment 2 of this application.
  • FIG. 11 is a schematic block diagram of the association relationship configuration module according to Embodiment 2 of the present application.
  • FIG. 12 is a schematic diagram of the failure of the gateway main device in the scenario of north-south traffic of the data center outlet according to Embodiment 3 of the present application;
  • FIG. 13 is a schematic diagram of Peer-Link failure under the scenario of north-south traffic of a data center outlet according to Embodiment 4 of the present application;
  • FIG. 14 is a schematic diagram of MC-LAG port failure under cross-data center east-west traffic scenarios according to Embodiment 5 of the present application.
  • SDN Software Defined Network, Software Defined Network
  • VXLAN VirtualExtensible LAN
  • its general framework is to implement applications without large-scale modification of the basic network
  • the load on the network can be separated from other network services, mainly based on the basic network technology based on IP)
  • Network virtualization architecture has become a mature solution supported and adopted by most manufacturers.
  • the embodiment of the present application proposes a controller management orchestration gateway physical device based on the SDN architecture.
  • the gateway physical device adopts MC-LAG (Multi-chassis Link Aggregation Group) mode to achieve redundant data center egress traffic I protected the model. It can solve the problems of long interruption of version upgrade network in stack mode deployment and the inability to manage the global operation and maintenance of the data center network.
  • MC-LAG Multi-chassis Link Aggregation Group
  • Stacking and MC-LAG have their own advantages and disadvantages. In general, for network design/maintenance staff, stacking is better at management and maintenance, and MC-LAG is better at reliability and low upgrade risk.
  • the centralized management of the controller in the embodiment of the present application reduces the complexity of operation and maintenance to a certain extent, and the use of MC-LAG can greatly improve the reliability of the network.
  • Table 1 Comparative analysis table of MC-LAG mode and stack mode.
  • the embodiment of the present application fully utilizes the advantages of MC-LAG technology with high reliability and low upgrade risk, and at the same time, the centralized management of the gateway by the controller compensates for the complexity of the MC-LAG technology configuration and maintenance to a certain extent.
  • the embodiment of the present application configures the gateway physical device as a logical device by setting an SDN controller, and virtualizes the physical port of the gateway physical device as a logical port of the logical device.
  • the logical device configured under the control of the SDN controller
  • the traffic is managed globally, so that the network traffic is uniformly scheduled to achieve the effect of reducing the complexity of operation and maintenance.
  • the MC-LAG mode is adopted to arrange the gateway logistics equipment, which can achieve the effect of short network interruption time when the gateway physical equipment fails or link failure or version upgrade, improve network reliability; solve the version of the gateway physical equipment in the stacking mode deployment scenario The problem of long network interruption during upgrade.
  • An embodiment of the present application provides a data center traffic interworking method.
  • An SDN controller is provided. As shown in FIG. 1, the SDN controller includes: a service configuration module 101: used to configure service-related information; and a device access management module 102 : Used to manage the information of the physical equipment of the gateway connected to the SDN controller; route management module 103: used to manage the routing information of the data center; link management module 105: used to collect the device topology of the data center and sense the link information And calculate the path of the link according to the routing information of the routing management module 103 to obtain the optimal network path; the packet sending and receiving processing module 104: used to process the received protocol messages; the device driver module 106: used to The information of the device access management module 102, the service configuration module 101 and the link management module 105 arranges the gateway physical devices.
  • the service-related information includes: VDC or DCI service configuration information.
  • the routing information of the data center includes: static routing, dynamic routing learned by the routing protocol, and direct connection routing information related to the interface.
  • a data center traffic interworking method includes: Step S201: Configure at least two gateway physical devices connected to an SDN controller as one logical device; wherein, the physical ports of the gateway physical devices are all Describe the logical port of the logical device; in specific application scenarios, configure the VTEP Group attribute on the SDN controller as MC-LAG; specifically configure the VTEP Group information on the SDN controller, and the VTEP Group attribute as MC-LAG, so that the two The physical device of the gateway presents a logical device on the network topology layer.
  • the device access management module 102 will save the information of the physical device of the accessed gateway.
  • the information of the physical device of the gateway is indexed by the Deviceid information. In this application scenario, two devices are used.
  • the physical device of the gateway is taken as an example, but it is not limited to two.
  • the physical port of the gateway physical device is the logical port of the logical device.
  • the physical port of the gateway physical device is virtualized as the logical port of the logical device.
  • Step S205 Based on the optimal network path and the association relationship, flow communication between the data center and the external network is realized.
  • the optimal network path is the optimal path from the logical port to the physical port of the gateway physical device
  • the association relationship is the relationship between the physical port of the gateway physical device and the external network.
  • the optimal network path and the association relationship may be set before the step of achieving the flow communication between the data center and the external network based on the optimal network path and the association relationship, or may be already set parameter.
  • the link management module 105 of the SDN controller will update the relevant information of the link after sensing the fault information of the gateway, and obtain the latest forwarding path through path calculation, thereby obtaining the new logical device
  • the interruption time is short.
  • the data center traffic interworking method can realize the redundant protection of north-south and DCI east-west traffic under the SDN data center network.
  • the equipment fails or the link fails it can be successfully switched to the backup equipment or link, and the network interruption time is short.
  • step S201 configuring at least two gateway physical devices connected to the SDN controller as one logical device, and further includes step S202: virtualizing the physical port of the gateway physical device into the logic The logical port of the device.
  • the virtualizing the physical port of the gateway physical device to the logical port of the logical device includes the following steps: Step S301: Configuring the MC-LAG link of the gateway physical device information.
  • the SDN controller configures the MC-LAG link of the gateway physical device, specifically: virtualizing the two cross-rack stacking ports of the MC-LAG link into a logical port.
  • the SDN controller virtualizes the two cross-rack stack ports of the MC-LAG link into one logical port.
  • the virtualized physical port is a logical port of the logical device, and further includes: Step S302: configuring peer link information of the physical device of the gateway.
  • the SDN controller configures the MC-LAG link and Peer-Link (peer-link) information of the gateway physical device, and the two cross-rack stacking ports of the MC-LAG are virtualized into a logic Port, after virtualizing the two cross-rack stacking ports into a logical port, during data transmission, the data of the logical port is only transmitted through one MC-LAG port, and the other MC-LAG port is in a standby state, that is In the data transmission, although the two physical MC-LAG ports are virtualized as one logical port, and there are virtual logical ports for data interaction with the outside, but specific to the gateway physical device, only one physical MC-LAG needs to be configured Data exchange is performed on the port, and another spare MC-LAG port does not need to be configured, and the port that is not configured with MC-LAG also occupies a global number on the logical device.
  • Peer-Link can be displayed on the management plane and can be configured accordingly.
  • step S205 before the step of implementing the flow communication between the data center and the external network based on the optimal network path and the association relationship further includes, step S203: acquiring the logical port to the gateway physical device The optimal network path of the physical port; that is, logical device reception is to receive traffic through the logical port, but the traffic received by the logical device needs to be transmitted to the physical port of the gateway physical device, but the logical port corresponds to the port of multiple gateway physical devices, so it needs to be calculated The optimal path from the logical port to the physical port of the physical device of the gateway.
  • obtaining the optimal network path from the logical port to the physical port of the gateway physical device includes: step S401: obtaining routing information of the gateway physical device; step S402: Calculate the optimal network path based on the routing information.
  • the SDN controller receives ARP learning, MAC learning, topology and entry information through the logical port, and sends and receives packet processing module 104, routing management module 103, and link management module 105 according to the actual report of the logical port interface.
  • the information and link port information of the device update the routing information of the physical device of the gateway, calculate the optimal network path, and then deliver the Openflow flow table to the SDN domain of the NVE computing node and the physical device of the gateway through the device driver module to guide the forwarding of internal network traffic in the data center.
  • step S205 before the step of implementing the flow communication between the data center and the external network based on the optimal network path and the association relationship further includes, step S204: configuring the physical port of the gateway physical device and the external network Relationship
  • configuring the association relationship between the physical port of the gateway physical device and the external network includes: Step S501: Configured VDC or DCI service configuration information; Step S502: According to the The VDC or DCI service configuration information arranges the information of the SDN domain and the traditional domain of the gateway physical device, so as to obtain the association relationship between the physical port of the gateway physical device and the external network.
  • SDN controller configures the association relationship between the gateway physical device and the external network, and uses the logical device as the logical router (Vrouter), and configure the configuration information of the logical router to the physical device entity of the gateway, so as to configure the port group information of the physical device of the gateway and the external network or external device;
  • the DCI service is configured according to the demand after creating the VDC service on the cloud platform of.
  • the port group type for the north-south traffic configuration is South-North
  • the port group type for the DCI east-west traffic configuration is East-West
  • the service configuration module 101 Based on the configured VDC or DCI service configuration information, the service configuration module 101, combined with the device information of the device access management module 102 and the related information of the link management module 105, notifies the device driver module to arrange the SDN domain and traditional domain of the gateway physical device according to the device situation Related information.
  • the SDN domain is mainly for forwarding information of the Openflow flow table to ensure that traffic in the data center domain can be directed to the physical device of the gateway.
  • the traditional domain is mainly for routing configuration information for interworking with external devices and MC-LAG related information for redundant protection of the physical device of the gateway. Controller
  • the traditional domain of the gateway physical device can be configured through devices such as Netconf, Restful, or Restconf that support the southbound configuration protocol (the protocol type is not limited).
  • This embodiment describes multiple scenarios for redundant protection of data center outlet traffic.
  • the main scenarios include the north-south traffic from the data center to the external network and the east-west traffic interconnection scenario across the data center.
  • the north-south traffic is mainly Layer 3 traffic
  • East-west traffic across data centers includes Layer 2 and 3 traffic.
  • the switching of the gateway physical device and the switching of the gateway physical device link, the network traffic interruption time is short, and the ordinary upgrade is in seconds.
  • the SDN controller is the core component for managing the data center network.
  • the modules included in the SDN controller and the interaction diagram of each module are shown in FIG. 1.
  • the SDN controller includes a service configuration module 101, a device access management module 102, and a route management module 103.
  • the service configuration module 101 is used to configure service-related information, mainly including configuration information related to the VDC network and the DCI service.
  • the device access management module 102 is used to manage the related information of the accessed physical gateway device, and is used when the SDN controller arranges the physical gateway device.
  • the route management module 103 is used to manage related routing information of the data center network, including configured static routes, dynamic routes learned by the routing protocol, and direct connection routes related to the interface.
  • the link management module 105 is used to collect device topology of the data center network and sense link information, perform path calculation on the link according to the routing information of the route management module 103, and obtain optimal link information of the data center network.
  • the sending and receiving packet processing module 104 is used to process protocol packets taken over by controllers such as ARP and Openflow.
  • the device driver module is used to arrange specific gateway physical devices according to the gateway physical device access information of the device access management module 102, the service-related information of the service configuration module 101, and the link information of the link management module 105.
  • the data center traffic intercommunication device further includes: a data center gateway, which is used to provide a gateway service for accessing the data center.
  • the data center traffic communication device further includes: a network virtual terminal and a host, the host is connected to the network virtual terminal, and the network virtual terminal is connected to the SDN controller.
  • the data center traffic intercommunication device includes an SDN controller (SDN Controller, SDN controller), which is used to organize and manage the network of the SDN data center, and releases the core technology of Openflow (SDN control forwarding separation) )
  • SDN controller SDN Controller, SDN controller
  • Openflow SDN control forwarding separation
  • VTEP Vxlan Tunnel EndPoint, Vxlan Tunnel Endpoint
  • NVE Network Virtualization EndPoint
  • SDN data center An Openflow switch or a TOR switch.
  • the host under the Openflow software switch inside the data center is a virtual machine VM
  • the host under the TOR (Top of Rack) switch is a bare metal server.
  • DCGW Data Center Gateway
  • SDN data center gateway provides gateway services for users to access services in the SDN data center.
  • the north-south traffic and the east-west traffic in the DC domain to the outside of the domain are respectively exported to the external network through the DCGW And the peer DC.
  • the upper cloud platform and cloud orchestrator deployed in the cloud data center mainly notify the SDN controller of network orchestration information for network management, and do not directly participate in the coordination with the physical equipment of the underlying gateway, which is not shown in Figure 2.
  • a data center traffic intercommunication device is provided with an SDN controller.
  • the device includes: a logical device configuration module 701: configured to configure at least two gateway physical devices connected to the SDN controller as a logic Device; logical interface configuration module 702: used to virtualize the physical port of the gateway physical device as the logical port of the logical device; path calculation module 703: used to obtain the logical port to the physical port of the gateway physical device Optimal network path; association relationship configuration module 704: used to configure the association relationship between the physical port of the gateway physical device and the external network; interworking module 705: used to implement the data center based on the optimal network path and association relationship Interflow of traffic from external networks.
  • the logical device configuration module 701 includes: MC-LAG configuration module 801: used to configure the VTEP Group attribute on the SDN controller to MC- LAG; device configuration module 802: used to configure the physical device of the gateway connected to the SDN controller as a logical device based on the VTEP Group attribute.
  • the logical interface configuration module 702 includes: an MC-LAG link information configuration module 901: an MC-LAG link for configuring a gateway physical device information.
  • the MC-LAG link information configuration module is specifically used to virtualize two cross-rack stacking ports of the MC-LAG link into one logical port.
  • the logical interface configuration module 702 further includes: a peer link information configuration module 902: configured to configure peer link information of a physical device of the gateway.
  • the path calculation module 703 includes: a routing information acquisition module 1001: used to acquire routing information of the gateway physical device; a calculation module 1002: used Calculate the optimal network path based on the routing information.
  • the association configuration module 704 includes: a service configuration information module 1101: VDC or DCI service configuration information for configuration; an orchestration module 1102: In order to arrange the information of the SDN domain and the traditional domain of the gateway physical device according to the VDC or DCI service configuration information, the association relationship between the physical port of the gateway physical device and the external network is obtained.
  • a service configuration information module 1101 VDC or DCI service configuration information for configuration
  • an orchestration module 1102 In order to arrange the information of the SDN domain and the traditional domain of the gateway physical device according to the VDC or DCI service configuration information, the association relationship between the physical port of the gateway physical device and the external network is obtained.
  • the main gateway device fails.
  • the main steps are as follows: In the first step, the SDN controller accesses the gateway physical device, and the SDN controller is configured with VTEP Group information, VTEP Group attribute is MC-LAG, two gateway physical devices present a logical device on the network topology layer. In the second step, the SDN controller configures the MC-LAG link and Peer-Link information of the physical device of the gateway.
  • the two cross-rack stacking ports of the MC-LAG are virtualized into one logical port, and the ports without the MC-LAG are configured. It also occupies a global number on the logical device.
  • the Peer-Link can be displayed on the management plane and can be configured accordingly.
  • the third step is to create a virtual router on the Openstack cloud platform, associate the external network configuration, configure the association relationship between the gateway physical device and the external network on the SDN controller, and configure the port group type of the gateway physical device to connect to South-North.
  • the ARP learning, MAC learning, topology and table entries of the SDN controller are all operated through the logical ports of the logical device.
  • the traffic in the domain of the SDN data center can reach the external network through the physical device of the gateway, and the north-south traffic between the domain and the outside can be interconnected.
  • the device with MC-LAG status as the standby device will be upgraded as the main device, and the Eth-Trunk (Ethernet Link Aggregation Group) link status on the device side is still Up, and the traffic forwarding status remains unchanged. Continue to forward traffic.
  • the SDN controller accesses the gateway physical device, and the SDN controller is configured with VTEP Group information , VTEP Group attribute is MC-LAG, two gateway physical devices present a logical device on the network topology layer.
  • the SDN controller configures the MC-LAG link and Peer-Link information of the physical device of the gateway.
  • the two cross-rack stacking ports of the MC-LAG are virtualized into one logical port, and the ports without the MC-LAG are configured. It also occupies a global number on the logical device.
  • Peer-Link can be displayed on the management plane and can be configured accordingly.
  • the third step is to create a virtual router on the Openstack cloud platform, associate the external network configuration, configure the association relationship between the gateway physical device and the external network on the SDN controller, and configure the external port group type of the gateway physical device as South-North.
  • Step 4 ARP learning, MAC learning, topology and table entries of the SDN controller are all operated through the logical port of the logical device.
  • the traffic in the domain of the SDN data center can reach the external network through the physical device of the gateway, and the north-south traffic between the domain and the outside can be interconnected.
  • the sixth step is the failure of the peer-link.
  • the MC-LAG active/standby state determines the link state of the Eth-Trunk.
  • the status of the Eth-Trunk link on the device with the MC-LAG state as the main state is still Up.
  • the device-side Eth-Trunk link in the MC-LAG state becomes Down, and the dual-homing scenario becomes the single-homing scenario.
  • the MC-LAG interface on the standby device is in the ERROR DOWN state. Once the peer-link failure recovers, the physical interface in the ERROR DOWN state will automatically return to the Up state.
  • the MC-LAG port is faulty.
  • the correlation steps are as follows: In the first step, the SDN controller is connected to the gateway physical device, and the VTEP Group information and VTEP Group attribute are configured on the SDN controller For MC-LAG, the two gateway physical devices present a logical device on the network topology layer. In the second step, the SDN controller configures the MC-LAG link and Peer-Link information of the physical device of the gateway.
  • the two cross-rack stacking ports of the MC-LAG are virtualized into one logical port, and the ports without the MC-LAG are configured. It also occupies a global number on the logical device.
  • the third step is to create a virtual router on the Openstack cloud platform, create a DCI instance on the cloud orchestrator (create an L2/L3DCI instance according to the application scenario), and configure the port group type of the gateway physical device and external device on the SDN controller as East- West.
  • ARP learning, MAC learning, topology and table entries of the SDN controller are all operated through the logical ports of the logical device.
  • the traffic in the SDN data center domain can reach the peer data center through the physical device of the gateway, so as to realize the east-west traffic communication across the data center.
  • the MC-LAG active/standby state will not change, traffic is switched to another link for forwarding, and the failed Eth-Trunk link state becomes Down.
  • the failed Eth-Trunk link no longer forwards traffic, and the VXLAN dual-homing scenario becomes a single-homing scenario.
  • the SDN controller senses the state change of the MC-LAG port and updates the related entries of Mac and Arp according to the latest state to guide the device forwarding.
  • Embodiments 3 to 5 are mainly for the implementation steps of device failure, link failure, and port failure. These three failures will appear in the scenario of north-south traffic of data center exit and cross-data center east-west traffic interworking. , Not all enumerated here, mainly explain the cooperative process of the controller and the physical device of the gateway under three fault conditions.
  • the centralized management of the gateway physical equipment by the SDN controller is realized.
  • the MC-LAG mode is adopted by orchestrating the gateway physical equipment, which can reach the network when the gateway physical equipment fails or the link fails or the version is upgraded.
  • the effect of short interruption time improves network reliability; the implementation of this technology solves the problem of long network interruption time for version upgrade in the scenario of gateway physical device stacking mode deployment.
  • An embodiment of the present application provides a network device, which can be understood as a physical device, including a processor and a memory storing executable instructions of the processor, and when the instructions are executed by the processor, any one of implementation one is performed The steps of the method.
  • the processor can be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU), a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or a One or more integrated circuits configured to implement the embodiments of the present application.
  • the memory is used to store the executable instructions of the processor; the memory is used to store the program code and transmit the program code to the processor.
  • the memory may include volatile memory (Volatile Memory), such as random access memory (Random Access Memory, RAM); may also include non-volatile memory (Non-Volatile Memory), such as read-only memory (Read-Only Memory, ROM), flash memory (Flash), hard disk (HDD), or solid-state drive (SSD); it can also include a combination of the above types of memory.
  • volatile memory such as random access memory (Random Access Memory, RAM
  • Non-Volatile Memory such as read-only memory (Read-Only Memory, ROM), flash memory (Flash), hard disk (HDD), or solid-state drive (SSD); it can also include a combination of the above types of memory.
  • An embodiment of the present application provides a computer-readable storage medium that stores a computer program on the computer-readable storage medium, and when the computer program is executed by a processor, implements the steps of the method described in any one of the embodiments .
  • the computer-readable storage medium includes, but is not limited to: ROM, RAM, magnetic disk or optical disk.

Landscapes

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

Abstract

本申请公开了一种数据中心流量互通方法、装置、设备及存储介质。其中，数据中心流量互通方法，其特征在于，设置SDN控制器，所述方法，包括：将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备(S201)，其中，所述网关物理设备的物理端口为所述逻辑设备的逻辑端口；基于最优网络路径和关联关系实现数据中心和外部网络的流量互通(S205)，其中，所述最优网络路径为所述逻辑端口到所述网关物理设备的物理端口的最优路径，所述关联关系为网关物理设备的物理端口和外部网络的关系。通过设置SDN控制器，在SDN控制器的控制下配置的逻辑设备对数据中心的流量进行全局管理，从而对网络流量进行统一调度，达到降低运维复杂度的效果。

Description

数据中心流量互通方法、装置、设备及存储介质
交叉引用
本申请引用于2018年12月04日递交的名称为“数据中心流量互通方法、装置、设备及存储介质”的第201811473922.9号中国专利申请，其通过引用被全部并入本申请。
技术领域
本申请涉及通信领域，尤其涉及一种数据中心流量互通方法、装置、设备及存储介质。
背景技术
伴随着云计算和移动互联网应用的发展，复杂的交互式应用在新型的IDC(Internet Data Center，互联网数据中心)中出现，特别是海量的数据访问和进程调用，使得单个IDC已经无法满足互联网应用的需要，必须将不同IDC整合为一个统一的资源池才能满足应用的需要。同时，作为连接IDC的承载网络必须支持由此产生的各种上层应用，如DC(Data Center，数据中心)间的虚拟化，VM(Virtual Machine，虚拟机)的实时迁移，跨DC的租户隔离等。
随着ICP(Internet Content Provider，网络内容服务商)和OTT(Over The Top，是指通过互联网向用户提供各种应用服务)服务商通过网络提供内容与服务的高速发展，越来越多的用户流量是访问ICP/OTT提供的内容与服务，而数据中心是ICP/OTT提供内容与服务 的主要平台，同时，随着云数据中心的成熟与发展，越来越多的企业选择将IT(Information Technology，信息技术)系统放入数据中心。因此，数据中心正在成为未来网络流量汇集点。
数据中心流量分为南北向流量和东西向流量。南北向以用户访问数据中心内容为主，东西向流量主要指数据中心内或跨数据中心同步、备份以及CDN(Content Delivery Network，内容分发网络)推送流量等。其中数据中心之间流量主要采用互联网承载。对数据中心网络流量的冗余保护是网络可靠性的基本要求。
在一些情形下，一般采用网关物理设备堆叠模式来支持数据中心出口流量的冗余保护。堆叠模式下，网关物理设备的上下行不感知网关的实际状态切换，存在版本升级时必须将两台设备同时升级，网络中断时间较长的问题。而且传统数据中心网络没有集中控制点，导致不能全局管理数据中心网络流量，并对网络流量进行统一调度，从而存在运维复杂度较高的问题。
发明内容
本申请实施例提供一种数据中心流量互通方法、装置、设备及存储介质，用以至少解决现有技术中存在的部分问题。
第一方面，一种数据中心流量互通方法，设置SDN控制器，所述方法，包括：将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，其中，所述网关物理设备的物理端口为所述逻辑设备的逻辑端口；基于最优网络路径和关联关系实现数据中心和外部网络的流量互通，其中，所述最优网络路径为所述逻辑端口到所述网关物理设备的物理端口的最优路径，所述关联关系为网关物理设备的物理端口和外部网络的关系。
作为本申请实施例的一种具体实现方式，所述将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，包括：将SDN控制器上的VTEP Group属性配置为MC-LAG；基于所述VTEP Group属性将接入SDN控制器的至少两个网关物理设备配置为一台逻辑设备。
作为本申请实施例的一种具体实现方式，所述将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，包括：将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口。
作为本申请实施例的一种具体实现方式，所述将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口，包括：配置网关物理设备的MC-LAG链路信息。
作为本申请实施例的一种具体实现方式，所述配置网关物理设备的MC-LAG链路信息，包括：将所述MC-LAG链路的至少两个跨机架堆叠端口虚拟成一个逻辑端口。
作为本申请实施例的一种具体实现方式，所述将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口，还包括：配置网关物理设备的对等链路信息。
作为本申请实施例的一种具体实现方式，基于最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤之前，还包括：获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径。
作为本申请实施例的一种具体实现方式，所述获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径，包括：获取所述网关物理设备的路由信息；基于所述路由信息计算所述最优网络路径。
作为本申请实施例的一种具体实现方式，基于最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤之前，还包括：配置所述网关物理设备的物理端口和外部网络的关联关系。
作为本申请实施例的一种具体实现方式，所述配置所述网关物理设备的物理端口和外部网络的关联关系，包括：配置VDC或DCI业务配置信息；根据所述VDC或DCI业务配置信息编排网关物理设备的SDN域和传统域的信息，从而得到所述网关物理设备的物理端口和外部网络的关联关系。
第二方面，一种网络设备，所述网络设备包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现第一方面中任一所述的方法的步骤。
第三方面，一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现第一方面中任一所述的方法的步骤。
上述说明仅是本申请技术方案的概述，为了能够更清楚了解本申请的技术手段，而可依照说明书的内容予以实施，并且为了让本申请的上述和其他目的、特征和优点能够更明显易懂，以下特举本申请的具体实施方式。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本申请的限制。而且在整个附图中，用相同的参考符号表示相同的部件。
图1为本申请实施例一所述的SDN控制器编排数据中心网络设 备实现网关出口流量冗余保护的各模块交互示意框图；
图2为本申请实施例一所述的数据中心流量互通方法的流程图；
图3为本申请实施例一所述的将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口的流程图；
图4为本申请实施例一所述的获取所述逻辑端口接收的流量转发给所述网关物理设备的物理端口的最优网络路径的流程图；
图5为本申请实施例一所述的配置所述网关物理设备的物理端口和外部网络的关联关系的流程图；
图6为本申请实施例二所述的数据中心流量互通装置的组网框图；
图7为本申请实施例二所述的数据中心流量互通装置的原理框图；
图8为本申请实施例二所述的逻辑设备配置模块的原理框图；
图9为本申请实施例二所述的逻辑接口配置模块的原理框图；
图10为本申请实施例二所述的路径计算模块的原理框图；
图11为本申请实施例二所述的关联关系配置模块的原理框图；
图12为本申请实施例三所述的数据中心出口南北向流量场景下网关主设备故障的示意图；
图13为本申请实施例四所述的数据中心出口南北向流量场景下Peer-Link故障的示意图；
图14为本申请实施例五所述的跨数据中心东西向流量场景下MC-LAG端口故障的示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附 图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
SDN(Software Defined Network，软件定义网络)自诞生以来就以其控制和转发分离、软件和硬件解耦及业务对网络的可编程等特性，赢得了业界的一致关注。利用SDN的技术优势服务于以云化数据中心互联为主要需求的新一代智能型承载网络，将是未来网络演进的一个新契机。
根据大部分数据中心内部情况，通过在现有网络上叠加一个软件定义的逻辑网络，让原有网络尽量不做改造，而是通过定义其上的逻辑网络实现业务逻辑，从而解决原有数据中心的网络问题，极大的节省传统用户投资。因此，以VXLAN(Virtual Extensible LAN，可扩展虚拟局域网)为代表的Overlay(指一种网络架构上叠加的虚拟化技术模式，其大体框架是对基础网络不进行大规模修改的条件下，实现应用在网络上的承载，并能与其它网络业务分离，以基于IP的基础网络技术为主)网络虚拟化架构已经成为目前多数厂商支持和采用的成熟方案。
本申请实施例提出了一种基于SDN架构下控制器管理编排网关物理设备，网关物理设备采用MC-LAG(Multi-chassis Link Aggregation Group，多机框链路聚合组)模式实现数据中心出口流量冗余保护的模型。可以解决堆叠模式部署存在的版本升级网络中断时间长以及不能对数据中心网络全局运维管理的问题。
堆叠和MC-LAG各有优缺点，总的来说，对于网络设计/维护人员，堆叠胜在管理维护简单，MC-LAG胜在可靠性和低升级风险。本 申请实施例中控制器集中管理一定程度上降低了运维的复杂性，而且采用MC-LAG可以大大提高网络的可靠性。
MC-LAG模式和堆叠模式的对比分析表格如表1所示。
Figure PCTCN2019103115-appb-000001
表1：MC-LAG模式和堆叠模式的对比分析表。
本申请实施例充分发挥了MC-LAG技术高可靠性和低升级风险的优势，同时通过控制器对网关的集中管理一定程度上弥补了MC-LAG技术配置维护复杂的缺陷。
本申请实施例通过设置SDN控制器，将网关物理设备配置为逻辑设备，并将网关物理设备的物理端口虚拟为逻辑设备的逻辑端口，在SDN控制器的控制下配置的逻辑设备对数据中心的流量进行全局管理，从而对网络流量进行统一调度，达到降低运维复杂度的效果。 同时通过编排网关物流设备采用MC-LAG模式，可以达到网关物理设备故障或链路故障或版本升级时网络中断时间短的效果，提高网络可靠性；解决了网关物理设备在堆叠模式部署场景下版本升级网络中断时间长的问题。
实施例一
本申请实施例提供一种数据中心流量互通方法，设置SDN控制器，所述SDN控制器，如图1所示，包括：业务配置模块101：用于配置业务相关信息；设备接入管理模块102：用于管理接入SDN控制器的网关物理设备的信息；路由管理模块103：用于管理数据中心的路由信息；链路管理模块105：用于收集数据中心的设备拓扑，以及感知链路信息，并根据所述路由管理模块103的路由信息对链路进行路径计算，得到最优网络路径；收发包处理模块104：用于处理接收的协议报文；设备驱动模块106：用于根据所述设备接入管理模块102、业务配置模块101及链路管理模块105的信息对网关物理设备进行编排。
在一示例性实施例中，业务相关信息，包括：VDC或DCI业务配置信息。在一示例性实施例中，数据中心的路由信息，包括：静态路由、路由协议学习到的动态路由以及接口相关的直连路由信息。
如图2所示，一种数据中心流量互通方法，包括：步骤S201：将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备；其中，所述网关物理设备的物理端口为所述逻辑设备的逻辑端口；在具体的应用场景中，将SDN控制器上的VTEP Group属性配置为MC-LAG；具体为SDN控制器上配置VTEP Group信息，VTEP Group属性为MC-LAG，使两台网关物理设备在网络拓扑层上呈现一台逻辑设 备，设备接入管理模块102将保存接入的网关物理设备信息，网关物理设备信息以Deviceid信息为索引，在本应用场景中虽然以两台网关物理设备为例，但并不仅仅限定为两台。
网关物理设备的物理端口为所述逻辑设备的逻辑端口，在一示例性实施例中，如下面步骤202中，将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口。
步骤S205：基于所述最优网络路径和关联关系实现数据中心和外部网络的流量互通。其中，所述最优网络路径为所述逻辑端口到所述网关物理设备的物理端口的最优路径，所述关联关系为网关物理设备的物理端口和外部网络的关系。在一示例性实施例中，最优网络路径和关联关系可以在基于所述最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤前进行设置，也可以是采用已经设置好的参数。
在网关物理设备故障或链路故障时，SDN控制器的链路管理模块105感知网关故障信息后会更新链路的相关信息，并通过路径计算得到最新的转发路径，从而得到新的逻辑设备内流量转发的最优网络路径，并通过设备驱动模块更新网关物理设备SDN域的流表信息和传统域的路由信息，最终实现网关出口南北向流量和东西向流量在网关故障或链路故障的情况下中断时间短。
通过数据中心流量互通方法可以实现在SDN数据中心组网下南北向和DCI东西向流量的冗余保护，在设备故障或链路故障时可以成功切换到备用设备或链路，网络中断时间短。
在一个具体的实施方式中，步骤S201：将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，还包括，步骤S202：将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口。
在一示例性实施例中，如图3所示，所述将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口，包括：步骤S301：配置网关物理设备的MC-LAG链路信息。
在一示例性实施例中，SDN控制器配置网关物理设备的MC-LAG链路，具体为：将所述MC-LAG链路的两个跨机架堆叠端口虚拟成一个逻辑端口。
具体为SDN控制器将MC-LAG链路的两个跨机架堆叠端口虚拟成一个逻辑端口。
在一示例性实施例中，所述将的物理端口虚拟为所述逻辑设备的逻辑端口，还包括：步骤S302：配置网关物理设备的对等链路信息。
在一个具体的应用场景中：SDN控制器配置网关物理设备的MC-LAG链路和Peer-Link(对等链路)信息，配置为MC-LAG的两个跨机架堆叠端口虚拟成一个逻辑端口，将两个跨机架堆叠端口虚拟成一个逻辑端口后，在数据传输时，逻辑端口的数据只通过一个MC-LAG的端口进行数据传输，另外一个MC-LAG的端口为备用状态，即在数据传输中虽然将两个物理的MC-LAG的端口虚拟为一个逻辑端口，有虚拟的逻辑端口与外部进行数据交互，但具体到网关物理设备上，只需要配置一个物理的MC-LAG的端口进行数据交互，另外一个备用的MC-LAG的端口不用配置，而对于未配置MC-LAG的端口，也在逻辑设备上占用一个全局编号。Peer-Link可以在管理面显示并可以进行相应配置，配置的网关物理设备的MC-LAG信息将保存在设备接入管理模块102对应设备信息表中。
在一个具体的实施方式中，步骤S205基于所述最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤之前还包括， 步骤S203：获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径；即逻辑设备接收是通过逻辑端口接收流量，但逻辑设备接收的流量需要传输给网关物理设备的物理端口，但逻辑端口对应多个网关物理设备的端口，因此需要计算逻辑端口到网关物理设备的物理端口的最优路径。
在一示例性实施例中，获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径，如图4所示，包括：步骤S401：获取所述网关物理设备的路由信息；步骤S402：基于所述路由信息计算所述最优网络路径。
在一个具体的应用场景中：SDN控制器通过逻辑端口接收ARP学习、MAC learning、拓扑和表项信息，收发包处理模块104、路由管理模块103、链路管理模块105根据逻辑端口接口的实际报文和设备链路端口信息更新网关物理设备路由信息，计算最优网络路径，再通过设备驱动模块下发Openflow流表到NVE计算节点和网关物理设备的SDN域，指导数据中心内部网络流量转发。
在一个具体的实施方式中，步骤S205基于所述最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤之前还包括，步骤S204：配置所述网关物理设备的物理端口和外部网络的关联关系；
在一示例性实施例中，配置所述网关物理设备的物理端口和外部网络的关联关系，如图5所示，包括：步骤S501：配置的VDC或DCI业务配置信息；步骤S502：根据所述VDC或DCI业务配置信息编排网关物理设备的SDN域和传统域的信息，从而得到所述网关物理设备的物理端口和外部网络的关联关系。
在一个具体的应用场景中：在云平台上配置数据中心Network、 Port、Subnet、Vrouter、外部网络等VDC业务信息，SDN控制器配置网关物理设备和外部网络的关联关系，将逻辑设备作为逻辑路由器(Vrouter)，并将逻辑路由器的配置信息配置到网关物理设备实体上，从而配置网关物理设备和外部网络或者外部设备连接的端口组信息；DCI业务是在云平台上创建VDC业务后根据需求配置的。南北向流量配置端口组类型为South-North，DCI东西向流量配置端口组类型为East-West，端口组中的端口关联生成的网关对应的逻辑端口信息。业务配置模块101根据配置的VDC或DCI业务配置信息，结合设备接入管理模块102的设备信息以及链路管理模块105的相关信息，通知设备驱动模块根据设备情况编排网关物理设备SDN域和传统域的相关信息。SDN域主要是Openflow流表转发信息，保证数据中心域内流量能导到网关物理设备，传统域主要是和外部设备互通的路由配置信息以及网关物理设备冗余保护的MC-LAG相关信息，控制器可以通过Netconf或Restful或Restconf等设备支持南向配置协议(不限定协议类型)来配置网关物理设备传统域。
本实施例描述了进行数据中心出口流量冗余保护的多种场景，主要场景包括数据中心出口到外部网络的南北向流量和跨数据中心的东西向流量互通场景，南北向流量主要是三层流量，跨数据中心的东西向流量包括二三层流量。在以上两大场景下进行网关物理设备的切换及网关物理设备链路的切换，网络流量中断时间短，普通升级秒级。
实施例二
SDN控制器是管理数据中心网络的核心组件，SDN控制器包含的模块以及各模块的交互图如图1所示，SDN控制器，包括业务配置 模块101、设备接入管理模块102、路由管理模块103、链路管理模块105、收发包处理模块104、设备驱动模块。
业务配置模块101，用于配置业务相关的信息，主要包括VDC网络和DCI业务相关的配置信息。
设备接入管理模块102，用于管理接入的网关物理设备的相关信息，在SDN控制器对网关物理设备进行编排时使用。
路由管理模块103，用于管理数据中心网络的相关路由信息，包括配置的静态路由、路由协议学习到的动态路由以及接口相关的直连路由等路由信息。
链路管理模块105，用于收集数据中心网络的设备拓扑，以及感知链路信息，根据路由管理模块103的路由信息对链路进行路径计算，得到数据中心网络的最佳链路信息。
收发包处理模块104，用于处理ARP、Openflow等控制器接管的协议报文。
设备驱动模块，用于根据设备接入管理模块102的网关物理设备接入信息以及业务配置模块101的业务相关的信息、链路管理模块105的链路信息对具体网关物理设备进行编排。
在一示例性实施例中，数据中心流量互通装置还包括：数据中心网关，所述数据中心网关：用于为访问数据中心提供网关服务。
在一示例性实施例中，数据中心流量互通装置还包括：网络虚拟终端和主机，所述主机与所述网络虚拟终端连接，所述网络虚拟终端与所述SDN控制器连接。
如图6所示，数据中心流量互通装置，包含SDN控制器(SDN Controller，SDN控制器)，用于对SDN数据中心的网络进行编排和管理，通过下发Openflow(SDN控制转发分离的核心技术)流表到VTEP (Vxlan Tunnel EndPoint，Vxlan隧道终端)设备实现数据中心内部二三层流量的转发，同时编排网关物理设备实现域内和域外网络的互通，以及流量的冗余保护。
NVE(Network Virtualization EndPoint，网络虚拟终端)，为SDN数据中心内部的VTEP设备，可以是Openflow交换机，也可以是TOR交换机。
HOST，在数据中心内部Openflow软件交换机下挂的主机是虚机VM，在TOR(Top Of Rack，架顶式交换机)交换机下的主机是裸金属服务器。
DCGW(Data Center Gateway，数据中心网关)，是SDN数据中心网关物理设备，为用户访问SDN数据中心内业务提供网关服务，DC域内到域外的南北向流量和东西向流量分别通过DCGW出口到外部网络和对端DC。
云数据中心部署的上层云平台和云编排器主要是把网络编排信息通知SDN控制器进行网络管理，并不直接参与和底层网关物理设备的协同，在图2中没有标示。
如图7所示，一种数据中心流量互通装置，设置SDN控制器，所述装置，包括：逻辑设备配置模块701：用于将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备；逻辑接口配置模块702：用于将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口；路径计算模块703：用于获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径；关联关系配置模块704：用于配置所述网关物理设备的物理端口和外部网络的关联关系；互通模块705：用于基于所述最优网络路径和关联关系实现数据中心和外部网络的流量互通。
作为本申请实施例的一种具体实现方式，如图8所示，所述逻辑设备配置模块701，包括：MC-LAG配置模块801：用于将SDN控制器上的VTEP Group属性配置为MC-LAG；设备配置模块802：用于基于所述VTEP Group属性将接入SDN控制器的网关物理设备配置为一台逻辑设备。
作为本申请实施例的一种具体实现方式，如图9所示，所述逻辑接口配置模块702，包括：MC-LAG链路信息配置模块901：用于配置网关物理设备的MC-LAG链路信息。
作为本申请实施例的一种具体实现方式，所述MC-LAG链路信息配置模块，具体：用于将所述MC-LAG链路的两个跨机架堆叠端口虚拟成一个逻辑端口。
作为本申请实施例的一种具体实现方式，所述逻辑接口配置模块702，还包括：对等链路信息配置模块902：用于配置网关物理设备的对等链路信息。
作为本申请实施例的一种具体实现方式，如图10所示，所述路径计算模块703，包括：路由信息获取模块1001：用于获取所述网关物理设备的路由信息；计算模块1002：用于基于所述路由信息计算所述最优网络路径。
作为本申请实施例的一种具体实现方式，如图11所示，所述关联关系配置模块704，包括：业务配置信息模块1101：用于配置的VDC或DCI业务配置信息；编排模块1102：用于根据所述VDC或DCI业务配置信息编排网关物理设备的SDN域和传统域的信息，从而得到所述网关物理设备的物理端口和外部网络的关联关系。
实施例三
如图12所示，在数据中心出口到外部网络的南北向流量互通 场景下，网关主设备故障，实现主要步骤如下：第一步，SDN控制器接入网关物理设备，SDN控制器上配置VTEP Group信息，VTEP Group属性为MC-LAG，两台网关物理设备在网络拓扑层上呈现一台逻辑设备。第二步，SDN控制器配置网关物理设备的MC-LAG链路和Peer-Link信息，配置为MC-LAG的两个跨机架堆叠端口虚拟成一个逻辑端口，未配置MC-LAG的端口，也在逻辑设备上占用一个全局编号。Peer-Link可以在管理面显示并可以进行相应配置。第三步，在Openstack云平台上创建虚拟路由器，关联外部网络配置，SDN控制器上配置网关物理设备和外部网络的关联关系，并配置网关物理设备对外连接的端口组类型为South-North。第四步，SDN控制器的ARP学习、MAC learning、拓扑和表项均通过逻辑设备的逻辑端口进行操作。第五步，SDN数据中心域内流量可以通过网关物理设备到达外部网络，实现域内到域外的南北向流量互通。第六步，网关主设备故障时，MC-LAG状态为备的设备将升级为主，其设备侧Eth-Trunk(以太网链路聚合组)链路状态仍为Up，流量转发状态不变，继续转发流量。MC-LAG状态为主的设备侧Eth-Trunk链路状态变为Down，双归场景变为单归场景。通过上面的几个步骤，可以实现网关主设备故障的情况下，数据中心出口南北向流量中断时间秒级。
实施例四
如图13所示，数据中心出口到外部网络的南北向流量互通场景下，Peer-link故障，关联步骤如下：第一步，SDN控制器接入网关物理设备，SDN控制器上配置VTEP Group信息，VTEP Group属性为MC-LAG，两台网关物理设备在网络拓扑层上呈现一台逻辑设备。第二步，SDN控制器配置网关物理设备的MC-LAG链路和Peer-Link信息，配置为MC-LAG的两个跨机架堆叠端口虚拟成一个逻辑端口，未配置 MC-LAG的端口，也在逻辑设备上占用一个全局编号。Peer-Link可以在管理面显示并可以进行相应配置。第三步，在Openstack云平台上创建虚拟路由器，关联外部网络配置，SDN控制器上配置网关物理设备和外部网络的关联关系，并配置网关物理设备对外的端口组类型为South-North。第四步：SDN控制器的ARP学习、MAC learning、拓扑和表项均通过逻辑设备的逻辑端口进行操作。第五步，SDN数据中心域内流量可以通过网关物理设备到达外部网络，实现域内到域外的南北向流量互通。第六步，Peer-link故障，当peer-link故障时，MC-LAG主备状态决定了Eth-Trunk的链路状态。MC-LAG状态为主的设备侧Eth-Trunk链路状态仍为Up。MC-LAG状态为备的设备侧Eth-Trunk链路状态变为Down，双归场景变为单归场景。peer-link故障但心跳状态正常会导致状态为备的设备上MC-LAG接口处于ERROR DOWN状态。一旦peer-link故障恢复，处于ERROR DOWN状态的物理接口将自动恢复为Up状态。通过上面的几个步骤，可以实现在Peer-link故障的情况下，数据中心出口南北向流量中断时间秒级。
实施例五
如图14所示，在跨数据中心流量互通场景下，MC-LAG端口故障，关联步骤如下：第一步，SDN控制器接入网关物理设备，SDN控制器上配置VTEP Group信息，VTEP Group属性为MC-LAG，两台网关物理设备在网络拓扑层上呈现一台逻辑设备。第二步，SDN控制器配置网关物理设备的MC-LAG链路和Peer-Link信息，配置为MC-LAG的两个跨机架堆叠端口虚拟成一个逻辑端口，未配置MC-LAG的端口，也在逻辑设备上占用一个全局编号。Peer-Link可以在管理面看到并进行相应配置。第三步，在Openstack云平台上创建虚拟路由器，在云编排器上创建DCI实例(根据应用场景创建L2/L3DCI实例)，SDN控 制器上配置网关物理设备和外部设备的端口组类型为East-West。第四步，SDN控制器的ARP学习、MAC learning、拓扑和表项均通过逻辑设备的逻辑端口进行操作。第五步，SDN数据中心域内流量可以通过网关物理设备到达对端数据中心，实现跨数据中心的东西向流量互通。第六步，MC-LAG端口故障时，MC-LAG主备状态不会变化，流量切换到另一条链路上进行转发，发生故障的Eth-Trunk链路状态变为Down。通过MC-LAG机制，发生故障的Eth-Trunk链路不再转发流量，VXLAN双归场景变为单归场景。SDN控制器感知MC-LAG端口状态变更，根据最新状态更新Mac、Arp相关表项指导设备转发。通过上面的几个步骤，可以实现跨数据中心东西向流量互通场景下MC-LAG端口故障后流量中断时间秒级。
实施例三至实施例五的描述主要是针对设备故障、链路故障、端口故障的实施步骤进行说明，这三种故障在数据中心出口南北向流量场景和跨数据中心东西向流量互通场景都会出现，在这里没有全部枚举，主要说明三种故障情况下控制器和网关物理设备的协同流程。
采用本申请实施例的方法和装置，实现了SDN控制器对网关物理设备的集中管理，同时通过编排网关物理设备采用MC-LAG模式，可以达到网关物理设备故障或链路故障或版本升级时网络中断时间短的效果，提高网络可靠性；通过本技术的实施解决了网关物理设备堆叠模式部署场景下版本升级网络中断时间长的问题。
实施例六
本申请实施例，提供一种网络设备，可以作为实体装置来理解，包括处理器以及存储有所述处理器可执行指令的存储器，当所述指令被处理器执行时，执行实施一中任一所述的方法的步骤。
上述方法步骤的具体实施例过程可参见第一实施例和第二实 施例，本实施例在此不再重复赘述。
处理器可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)，还可以是数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路。其中，存储器用于存储所述处理器的可执行指令；存储器，用于存储程序代码，并将该程序代码传输给处理器。存储器可以包括易失性存储器(Volatile Memory)，例如随机存取存储器(Random Access Memory，RAM)；也可以包括非易失性存储器(Non-Volatile Memory)，例如只读存储器(Read-Only Memory，ROM)、快闪存储器(Flash Memory)、硬盘(Hard Disk Drive，HDD)或固态硬盘(Solid-State Drive，SSD)；还可以包括上述种类的存储器的组合。
实施例七
本申请实施例，提供一种提供计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现实施例一中任一所述的方法的步骤。
上述方法步骤的具体实施例过程可参见第一实施例和第二实施例，本实施例在此不再重复赘述。其中，计算机可读存储介质包括但不限于为：ROM、RAM、磁盘或光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要 素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，这些均属于本申请的保护之内。

Claims (12)

  1. 一种数据中心流量互通方法，其特征在于，设置SDN控制器，所述方法，包括：
    将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，其中，所述网关物理设备的物理端口为所述逻辑设备的逻辑端口；
    基于最优网络路径和关联关系实现数据中心和外部网络的流量互通，其中，所述最优网络路径为所述逻辑端口到所述网关物理设备的物理端口的最优路径，所述关联关系为网关物理设备的物理端口和外部网络的关系。
  2. 如权利要求1所述的数据中心流量互通方法，其特征在于，所述将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，包括：
    将SDN控制器上的VTEP Group属性配置为MC-LAG；
    基于所述VTEP Group属性将接入SDN控制器的至少两个网关物理设备配置为一台逻辑设备。
  3. 如权利要求2所述的数据中心流量互通方法，其特征在于，所述将接入SDN控制器的至少两个网关物理设备配置为一个逻辑设备，包括：
    将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口。
  4. 如权利要求3所述的数据中心流量互通方法，其特征在于，所述将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口，包括：
    配置网关物理设备的MC-LAG链路信息。
  5. 如权利要求4所述的数据中心流量互通方法，其特征在于， 所述配置网关物理设备的MC-LAG链路信息，包括：
    将所述MC-LAG链路的至少两个跨机架堆叠端口虚拟成一个逻辑端口。
  6. 如权利要求3所述的数据中心流量互通方法，其特征在于，所述将所述网关物理设备的物理端口虚拟为所述逻辑设备的逻辑端口，还包括：
    配置网关物理设备的对等链路信息。
  7. 如权利要求1所述的数据中心流量互通方法，其特征在于，基于最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤之前，还包括：
    获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径。
  8. 如权利要求7所述的数据中心流量互通方法，其特征在于，所述获取所述逻辑端口到所述网关物理设备的物理端口的最优网络路径，包括：
    获取所述网关物理设备的路由信息；
    基于所述路由信息计算所述最优网络路径。
  9. 如权利要求1所述的数据中心流量互通方法，其特征在于，基于最优网络路径和关联关系实现数据中心和外部网络的流量互通的步骤之前，还包括：
    配置所述网关物理设备的物理端口和外部网络的关联关系。
  10. 如权利要求9所述的数据中心流量互通方法，其特征在于，所述配置所述网关物理设备的物理端口和外部网络的关联关系，包括：
    配置VDC或DCI业务配置信息；
    根据所述VDC或DCI业务配置信息编排网关物理设备的SDN域 和传统域的信息，从而得到所述网关物理设备的物理端口和外部网络的关联关系。
  11. 一种网络设备，其特征在于，所述网络设备包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至10中任一项所述的方法的步骤。
  12. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至10中任一项所述的方法的步骤。
PCT/CN2019/103115 2018-12-04 2019-08-28 数据中心流量互通方法、装置、设备及存储介质 WO2020114017A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
RU2021116294A RU2761186C1 (ru) 2018-12-04 2019-08-28 Способ и устройство для обмена трафиком центра обработки данных, устройство и носитель данных
EP19894333.4A EP3866393A4 (en) 2018-12-04 2019-08-28 METHOD AND APPARATUS FOR EXCHANGE OF DATA CENTER TRAFFIC, DEVICE AND INFORMATION MEDIA
JP2021526365A JP7190569B2 (ja) 2018-12-04 2019-08-28 データセンターのトラフィック共有方法、装置、デバイスおよび記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811473922.9A CN111277423B (zh) 2018-12-04 2018-12-04 数据中心流量互通方法、装置、设备及存储介质
CN201811473922.9 2018-12-04

Publications (1)

Publication Number Publication Date
WO2020114017A1 true WO2020114017A1 (zh) 2020-06-11

Family

ID=70973812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/103115 WO2020114017A1 (zh) 2018-12-04 2019-08-28 数据中心流量互通方法、装置、设备及存储介质

Country Status (5)

Country Link
EP (1) EP3866393A4 (zh)
JP (1) JP7190569B2 (zh)
CN (1) CN111277423B (zh)
RU (1) RU2761186C1 (zh)
WO (1) WO2020114017A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112615749A (zh) * 2020-12-28 2021-04-06 广州西麦科技股份有限公司 一种基于VXLAN和OpenFlow的流量调度系统和方法
CN114301838A (zh) * 2021-12-31 2022-04-08 锐捷网络股份有限公司 一种流表优化、报文转发的方法、网络、设备及存储介质
CN114513437A (zh) * 2022-01-20 2022-05-17 杭州朗和科技有限公司 一种网络测试方法、装置、介质及计算设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112929290B (zh) * 2021-02-02 2023-02-24 湖南快乐阳光互动娱乐传媒有限公司 一种限流方法、装置、系统、存储介质和设备、以及网关
CN113364691B (zh) * 2021-05-31 2022-11-29 广州趣丸网络科技有限公司 一种数据交互系统、方法、设备和存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150195178A1 (en) * 2014-01-09 2015-07-09 Ciena Corporation Method for resource optimized network virtualization overlay transport in virtualized data center environments
US20160277291A1 (en) * 2015-03-20 2016-09-22 Telefonaktiebolaget L M Ericsson (Publ) Shortest path bridge with mpls labels
US20160323179A1 (en) * 2015-04-29 2016-11-03 Telefonaktiebolaget L M Ericsson (Publ) Bng subscribers inter-chassis redundancy using mc-lag
WO2017144957A1 (en) * 2016-02-26 2017-08-31 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic re-route in a redundant system of a packet network
CN107431656A (zh) * 2015-03-20 2017-12-01 日本电气株式会社 控制设备、通信系统、控制方法及程序
US20180287965A1 (en) * 2017-03-29 2018-10-04 Fungible, Inc. Non-blocking any-to-any data center network with packet spraying over multiple alternate data paths
WO2018198114A1 (en) * 2017-04-25 2018-11-01 Drivenets Ltd. A virtual provider edge cluster for use in an sdn architecture

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140146664A1 (en) 2012-11-26 2014-05-29 Level 3 Communications, Llc Apparatus, system and method for packet switching
US9369408B1 (en) * 2014-01-31 2016-06-14 Google Inc. High performance and resilience in wide area networking
JP6191703B2 (ja) * 2014-02-05 2017-09-06 日本電気株式会社 通信制御システム、通信制御方法および通信制御プログラム
US9992102B2 (en) * 2015-08-28 2018-06-05 Ciena Corporation Methods and systems to select active and standby ports in link aggregation groups
JP2017050708A (ja) 2015-09-02 2017-03-09 日本電気株式会社 通信システム、制御装置、スイッチ、通信方法及びプログラム
CN107306193B (zh) * 2016-04-18 2020-11-27 中兴通讯股份有限公司 基于sdn网络的交换机端口信息感知方法、装置和终端设备
RU2643469C2 (ru) * 2016-05-31 2018-02-01 Би4Эн Груп Лимитед Способ передачи фреймов ethernet через программно-конфигурируемые сети (sdn)
CN106302076B (zh) * 2016-07-22 2020-03-06 浪潮(北京)电子信息产业有限公司 建立vxlan隧道的方法、系统及sdn控制器
US10193750B2 (en) 2016-09-07 2019-01-29 Cisco Technology, Inc. Managing virtual port channel switch peers from software-defined network controller
US10091097B2 (en) * 2016-10-27 2018-10-02 Nanning Fugui Precision Industrial Co., Ltd. Transmission path optimization method and software-defined networking controller using the method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150195178A1 (en) * 2014-01-09 2015-07-09 Ciena Corporation Method for resource optimized network virtualization overlay transport in virtualized data center environments
US20160277291A1 (en) * 2015-03-20 2016-09-22 Telefonaktiebolaget L M Ericsson (Publ) Shortest path bridge with mpls labels
CN107431656A (zh) * 2015-03-20 2017-12-01 日本电气株式会社 控制设备、通信系统、控制方法及程序
US20160323179A1 (en) * 2015-04-29 2016-11-03 Telefonaktiebolaget L M Ericsson (Publ) Bng subscribers inter-chassis redundancy using mc-lag
WO2017144957A1 (en) * 2016-02-26 2017-08-31 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic re-route in a redundant system of a packet network
US20180287965A1 (en) * 2017-03-29 2018-10-04 Fungible, Inc. Non-blocking any-to-any data center network with packet spraying over multiple alternate data paths
WO2018198114A1 (en) * 2017-04-25 2018-11-01 Drivenets Ltd. A virtual provider edge cluster for use in an sdn architecture

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3866393A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112615749A (zh) * 2020-12-28 2021-04-06 广州西麦科技股份有限公司 一种基于VXLAN和OpenFlow的流量调度系统和方法
CN112615749B (zh) * 2020-12-28 2023-04-18 广州西麦科技股份有限公司 一种基于VXLAN和OpenFlow的流量调度系统和方法
CN114301838A (zh) * 2021-12-31 2022-04-08 锐捷网络股份有限公司 一种流表优化、报文转发的方法、网络、设备及存储介质
CN114513437A (zh) * 2022-01-20 2022-05-17 杭州朗和科技有限公司 一种网络测试方法、装置、介质及计算设备
CN114513437B (zh) * 2022-01-20 2023-05-16 杭州朗和科技有限公司 一种网络测试方法、装置、介质及计算设备

Also Published As

Publication number Publication date
CN111277423A (zh) 2020-06-12
RU2761186C1 (ru) 2021-12-06
EP3866393A1 (en) 2021-08-18
EP3866393A4 (en) 2022-07-06
JP7190569B2 (ja) 2022-12-15
CN111277423B (zh) 2022-05-20
JP2022507436A (ja) 2022-01-18

Similar Documents

Publication Publication Date Title
CN110166356B (zh) 发送报文的方法和网络设备
WO2020114017A1 (zh) 数据中心流量互通方法、装置、设备及存储介质
US11323307B2 (en) Method and system of a dynamic high-availability mode based on current wide area network connectivity
US10200278B2 (en) Network management system control service for VXLAN on an MLAG domain
CN106375214B (zh) 一种基于sdn的层次化路由路径确定方法及装置
US9288555B2 (en) Data center network architecture
US20080215910A1 (en) High-Availability Networking with Intelligent Failover
EP2774329B1 (en) Data center network architecture
US9008080B1 (en) Systems and methods for controlling switches to monitor network traffic
EP3316555B1 (en) Mac address synchronization method, device and system
CN109714238A (zh) 一种用于实现虚拟机间通信的方法及设备
US11582102B2 (en) Systems and methods for integrating network switch management with computing resource management
CN105656645A (zh) 堆叠系统的故障处理的决策方法和装置
US10484333B2 (en) Methods and systems for providing limited data connectivity
WO2017113929A1 (zh) 一种软件定义网络中控制转发设备集群的方法及控制器
GB2485026A (en) Routed Split Multi-Link Trunking (RSMLT) resiliency for Wireless Local Area Network (WLAN) split-plane environments
CN115987778B (zh) 一种基于Kubernetes集群的容器通信方法
WO2024159954A1 (zh) 一种上行出口识别方法、装置及设备、介质和产品
CN113364678A (zh) 数据传输系统、方法、装置、电子设备和计算机可读介质
WO2020181733A1 (zh) 一种基于vpc的多数据中心互通方法及相关设备
CN113890823B (zh) 一种用于层次拓扑的交换机自动配置方法及介质
CN110830598B (zh) Bgp会话建立、发送接口地址和别名的方法及网络设备
CN113709018A (zh) 基于Vxlan接入虚拟化网络的方法和系统
CN116248581B (zh) 一种基于sdn的云场景网关集群主备切换方法及系统
CN111385182B (zh) 流量的传输方法及装置，系统

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021526365

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019894333

Country of ref document: EP

Effective date: 20210514

NENP Non-entry into the national phase

Ref country code: DE