[go: up one dir, main page]

WO2021103744A1 - Procédé et système de communication de réseau hétérogène, et contrôleur - Google Patents

Procédé et système de communication de réseau hétérogène, et contrôleur Download PDF

Info

Publication number
WO2021103744A1
WO2021103744A1 PCT/CN2020/114910 CN2020114910W WO2021103744A1 WO 2021103744 A1 WO2021103744 A1 WO 2021103744A1 CN 2020114910 W CN2020114910 W CN 2020114910W WO 2021103744 A1 WO2021103744 A1 WO 2021103744A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
openflow
evpn
entry
controller
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/114910
Other languages
English (en)
Chinese (zh)
Inventor
许多
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2021103744A1 publication Critical patent/WO2021103744A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/54—Organization of routing tables
    • 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/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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
    • 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/64—Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the embodiment of the present invention relates to but not limited to the technical field of network communication, and specifically relates to but not limited to a heterogeneous network communication method, system and controller.
  • SDN Software-defined networking
  • DC Data Center
  • WAN Wide Area Network
  • VXLAN Virtual Extensible LAN
  • OpenFlow and EVPN are two major solutions in the SDN field: OpenFlow is a centralized control plane of the controller, which uses a software-defined flow table forwarding method, which is more suitable for software equipment; and EVPN It is a distributed control plane, which requires the use of the EVPN protocol of the network device to learn routing table entries to guide forwarding, and is generally applicable to hardware network devices.
  • VXLAN In OpenFlow, a statically configured VXLAN tunnel is generally used to forward through the flow table.
  • EVPN VXLAN is a dynamic tunnel.
  • the communication problem between the OpenFlow domain and the EVPN domain heterogeneous network needs to be solved, involving VXLAN Difficulties such as tunnel creation, table entry synchronization, and message forwarding.
  • the heterogeneous network communication method, system, and controller provided by the embodiments of the present invention at least to some extent solve the problem that the current OpenFlow domain devices and EVPN domain devices cannot be mixed.
  • an embodiment of the present invention provides a heterogeneous network communication method, including: a controller receives a first message reported by an EVPN domain device through an MP-BGP connection channel, and converts the first message into a first table Item, and synchronize to the OpenFlow domain device through the OpenFlow connection channel; and/or, the controller receives the second message reported by the OpenFlow domain device through the OpenFlow connection channel, and converts the second message into a second table item, And through the MP-BGP connection channel to synchronize to the EVPN domain equipment.
  • the embodiment of the present invention also provides a controller, including: a routing protocol processing unit, an EVPN entry synchronization unit, an OpenFlow entry synchronization unit, and an OpenFlow device management unit;
  • the routing protocol processing unit supports standard BGP EVPN protocol processing, using Establish BGP neighbors with devices in the EVPN domain and advertise EVPN routes to each other;
  • the EVPN table item synchronization unit synchronizes the EVPN domain table items learned by the routing protocol processing unit to the OpenFlow domain, and at the same time receives the table item information of the OpenFlow domain and transmits it to the routing Protocol processing unit;
  • the OpenFlow entry synchronization unit receives the entries of the EVPN domain, and at the same time synchronizes the entries of the OpenFlow domain to the EVPN domain;
  • the OpenFlow device management unit is used to create a VXLAN tunnel in the OpenFlow domain, and is used for the OpenFlow domain and EVPN The entries of the domain are calculated to generate a flow table and delivered to the OpenFlow device.
  • the embodiment of the present invention also provides a heterogeneous network communication system, including: a controller, an EVPN domain device, and an OpenFlow domain device; the controller receives the first message reported by the EVPN domain device through an MP-BGP connection channel, The first message is converted into a first entry, and synchronized to the OpenFlow domain device through the OpenFlow connection channel; the controller receives the second message reported by the OpenFlow domain device through the OpenFlow connection channel, and transfers the first message to the OpenFlow domain device. The second message is converted into a second entry, and synchronized to the EVPN domain device through the MP-BGP connection channel.
  • the embodiment of the present invention also provides a computer storage medium, the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the implementation of the present invention.
  • Figure 1 is a schematic diagram of a VXLAN tunnel in a heterogeneous network provided by the implementation of the present invention
  • FIG. 2 is a schematic diagram of table entry synchronization in a heterogeneous network communication method provided by an embodiment of the present invention
  • Fig. 3 is a schematic diagram of a heterogeneous network communication system provided by an embodiment of the present invention.
  • OpenFlow is the centralized control plane of the controller, and the software-defined flow table forwarding method is adopted, which is more suitable for software equipment; while EVPN is a distributed control.
  • the EVPN protocol of the network device itself needs to be used to learn routing table entries to guide forwarding, which is generally applicable to hardware network devices. Since OpenFlow generally uses statically configured VXLAN tunnels for message forwarding, and EVPN generally uses dynamically configured VXLAN tunnels for message forwarding, VXLAN tunnels cannot be used directly when OpenFlow and EVPN are combined.
  • a heterogeneous network communication method proposed in this embodiment converts the guarantee through the controller to realize the guaranteed forwarding of OpenFlow and EVPN.
  • the heterogeneous network communication method of this implementation includes: the controller receives the first message reported by the EVPN domain device through the MP-BGP connection channel, converts the first message into the first entry, and synchronizes to the OpenFlow domain through the OpenFlow connection channel Device; and/or, the controller receives the second message reported by the OpenFlow domain device through the OpenFlow connection channel, converts the second message into a second entry, and synchronizes to the EVPN domain device through the MP-BGP connection channel.
  • the functions of the controller include: (1) Receive the first message reported by the EVPN domain device through the MP-BGP connection channel, convert the first message into the first entry, and synchronize through the OpenFlow connection channel To the OpenFlow domain device; (2) Receive the second message reported by the OpenFlow domain device through the OpenFlow connection channel, convert the second message into a second entry, and synchronize to the EVPN domain device through the MP-BGP connection channel; and ( 3) Receive the first message reported by the EVPN domain device through the MP-BGP connection channel, convert the first message into the first entry, and synchronize to the OpenFlow domain device through the OpenFlow connection channel, and receive the OpenFlow domain device through the OpenFlow connection channel The reported second message is converted into a second table entry and synchronized to the EVPN domain device through the MP-BGP connection channel.
  • BGP-4 can only manage IPV4 routing information. For applications that use other network layer protocols (such as ipv6), it is subject to certain restrictions when spreading across autonomous systems.
  • the IETF has extended BGP-4 to form MP-BGP.
  • the MP-BGP standard is RFC4760 (Multiprotocol Extensions for BGP-4, a multi-protocol extension of BGP-4).
  • NLRI Network Layer Reachability Information
  • Next_Hop attribute Next_Hop attribute
  • Aggregator attribute this attribute contains the aggregation The IP address of the BGP Speaker of the route).
  • MP_REACH_NLRI Multiprotocol Reachable NLRI, multi-protocol reachable NLRI. Used to advertise reachable routes and next hop information.
  • MP_UNREACH_NLRI Multiprotocol Unreachable NLRI, multi-protocol unreachable NLRI. Used to withdraw unreachable routes.
  • the OpenFlow connection channel a network communication protocol, belongs to the data link layer and can control the forwarding plane of the network switch or router, thereby changing the network path taken by the network data packet.
  • the first message and the second entry include: any one of type 3 routing, type 2 routing, and type 5 routing;
  • the second message and the first entry include: Layer 2 network broadcast table, MAC Any one of table, ARP table and routing table; Type 3 routing corresponds to the Layer 2 network broadcast table, Type 2 routing corresponds to the MAC table and ARP table, and Type 5 routing corresponds to the routing table.
  • the host mounted under the EVPN domain device when the EVPN domain device is a hardware switch, the host mounted under the EVPN domain device includes either a bare metal server or a virtual machine isolated by vlan in the server; when the OpenFlow domain device is a vSwitch software virtual switch, OpenFlow The host mounted under the domain device is a virtual machine.
  • the MP-BGP connection channel is established as a dynamic VXLAN tunnel
  • the dynamic VXLAN tunnel is dynamically established by the EVPN domain device through learning BGP and EVPN.
  • the EVPN domain device and the OpenFlow domain device learn the first entry and/or the second entry to generate Layer 2 and Layer 3 forwarding entries.
  • the OpenFlow connection channel after the OpenFlow connection channel is established, it is a static VXLAN tunnel.
  • the static VXLAN tunnel is statically imported and configured by the controller to the OpenFlow domain device.
  • the static VXLAN tunnel uses the VTEPIPs of the devices at both ends as a unique identifier.
  • the VTEPIP identifies that the outbound interface between different devices is a static VXLAN tunnel, and the static VXLAN tunnel is in the same domain or cross-domain, and is used to implement same-domain or cross-domain packet forwarding.
  • an MP-BGP connection channel is established with an EVPN domain device through a controller
  • an OpenFlow connection channel is established with an OpenFlow domain device, so as to realize receiving the first message and the EVPN domain device.
  • the purpose of the second message of the OpenFlow domain device is to convert the first message into the first entry, the second message into the second entry, and the first entry is synchronized to the OpenFlow domain device, giving the second
  • the table entries are synchronized to EVPN domain devices, which realizes the message exchange between OpenFlow domain devices and EVPN domain devices, and solves the problem that the current OpenFlow domain devices and EVPN domain devices cannot be mixed.
  • This embodiment provides another embodiment of a heterogeneous network communication method, including:
  • the controller realizes the synchronization and learning of table entries between the OpenFlow domain and the EVPN domain, and creates a heterogeneous VXLAN tunnel through the controller.
  • the service traffic between the OpenFlow domain and the EVPN domain device completes packet forwarding through the heterogeneous VXLAN tunnel.
  • the VXLAN tunnel on the OpenFlow domain device is statically imported and configured by the controller, and is uniquely identified by the local VTEPIP and the opposite VTEPIP.
  • the opposite device can be an OpenFlow domain device or an EVPN domain device.
  • the dynamic VXLAN tunnel on the EVPN domain device is dynamically created through BGP EVPN type 3 routing learning, and the routing table entries can come from other EVPN domain devices or the EVPN component module of the controller.
  • the controller converts the type 3 route of the EVPN domain into a Layer 2 network broadcast entry of the OpenFlow domain, and synchronizes it to the OpenFlow domain, so that the OpenFlow domain adds the EVPN domain device to the Layer 2 network broadcast domain.
  • the controller also converts the broadcast entries of the OpenFlow domain into EVPN domain type 3 routes and synchronizes them to the EVPN domain, so that the EVPN domain can discover the devices in the OpenFlow domain, and add the OpenFlow domain devices to the Layer 2 network broadcast domain, and then generate the corresponding VXLAN dynamic tunnel.
  • the controller In addition to synchronizing the Layer 2 network broadcast table (type 3 routing) between the devices in the OpenFlow domain and the EVPN domain, the controller also synchronizes the MAC table, ARP table (type 2 routing) and routing table (type 5 routing), these four tables When items are synchronized between domains, conversion processing is required.
  • Layer 2 network broadcast table type 3 routing
  • ARP table type 2 routing
  • routing table type 5 routing
  • the devices in the OpenFlow domain and the EVPN domain learn these entries and generate normal Layer 2 and Layer 3 forwarding entries.
  • the outbound interface for forwarding between VTEPs is a VXLAN tunnel. This tunnel can be in the same domain or in the same domain. It is cross-domain, realizing the same-domain and cross-domain business traffic forwarding.
  • a heterogeneous network communication method provided by the embodiment of the present invention can solve the communication problem of OpenFlow and EVPN heterogeneous SDN networks, so that the same controller can simultaneously manage and control software OpenFlow devices and hardware EVPN devices, without changing the OpenFlow and EVPN protocols Under the premise of standards and networking methods, the advantages of these two SDN technologies are used to form a hybrid overlay to meet various service deployment scenarios.
  • Fig. 1 is a schematic diagram of a heterogeneous VXLAN tunnel in an embodiment of the present invention.
  • the user imports the VXLAN static tunnel of the OpenFlow domain on the controller management interface, and creates a tunnel port on the device.
  • the VXLAN static tunnel is uniquely identified by the local VTEPIP and the peer VTEPIP:
  • tunnelPort ⁇ local_vtepip,peer_vtepip ⁇
  • VXLAN static tunnel can be an OpenFlow domain device or an EVPN domain device.
  • the corresponding tunnel port must be created between the two devices in the OpenFlow domain, but if the opposite end is a device in the EVPN domain, only the VXLAN static tunnel port is created at the end of the OpenFlow domain.
  • the EVPN domain device is a dynamic VXLAN tunnel, which is dynamically created by learning EVPN's Type 3 routing (Layer 2 network broadcast table).
  • the entries can come from other EVPN domain devices or from the OpenFlow domain.
  • the controller sends the Layer 2 network forwarding flow table to the OpenFlow domain device, and also generates Type 3 routing synchronization to the EVPN domain device, so that the EVPN domain device can automatically generate the corresponding heterogeneous VXLAN tunnel .
  • the embodiment of the present invention provides a heterogeneous network communication method, so that the software OpenFlow device and the hardware EVPN device controlled by the same controller can perform Layer 2 and Layer 3 network communication.
  • FIG. 2 is a schematic diagram of table entry synchronization provided by an embodiment of the present invention.
  • the controller establishes an OpenFlow connection channel with the device in the OpenFlow domain, and receives the status message reported by the device, the host's ARP message and the first unknown unicast message through the OpenFlow channel, and calculates the Layer 2 and Layer 3 forwarding path , To generate a flow table to deliver the device.
  • the flow table includes the Layer 2 broadcast table, MAC table, ARP table and routing table.
  • the device in the OpenFlow domain is generally a vSwitch software virtual switch, and the host connected to it is generally a virtual machine.
  • the controller establishes an MP-BGP connection with the equipment in the EVPN domain, and the host routing table entries learned by the EVPN equipment are synchronized to the controller.
  • the controller obtains the forwarding path of the OpenFlow domain equipment through conversion processing and calculation, and generates the corresponding forwarding table entries.
  • the controller also synchronizes the routing information of the OpenFlow domain host to each EVPN device after conversion processing, and the EVPN device performs routing iteration to obtain forwarding entries.
  • the EVPN routing table entries mainly include type 2, type 3, and type 5 routes.
  • the equipment in the EVPN domain is generally a hardware switch, and the host connected to it can be a bare metal server or a virtual machine isolated by vlan in the server.
  • the forwarding path between devices in the same domain or across domains is the corresponding VXLAN tunnel.
  • the method for the controller provided in the embodiment of the present invention to synchronize the type 3 route of the EVPN domain to the OpenFlow domain
  • Step 101 When creating a Layer 2 network instance on the controller, it is identified by VNET_ID, and the RD (Route Distinguisher) of the instance is automatically generated according to the VNET_ID.
  • the Layer 2 network instance issues the routing protocol processing unit in the EVPN domain device and the controller, uses the VNET_ID to combine into a string as the name of the Layer 2 network VXLAN instance, and automatically generates the ID of a Layer 2 network VXLAN instance;
  • Step 102 When the controller receives the type 3 route advertised by the EVPN domain device through BGP EVPN, the type 3 route is shown in Table 1 below:
  • RD uniquely identifies a Layer 2 network
  • Originating Router's IPAddress is the VTEP IP address of the device.
  • Step 103 The controller finds the Layer 2 network instance of the EVPN domain according to the RD.
  • the name of the VXLAN instance corresponds to the Layer 2 network instance VNET_ID of the OpenFlow domain, and can be directly converted. Therefore, the controller replaces the VXLAN_ID with VNET_ID to generate Layer 2 network broadcast entries required by the OpenFlow domain:
  • the domain parameter is used to indicate whether the entry comes from the OpenFlow domain or the EVPN domain.
  • Step 104 The controller adds the above-mentioned Layer 2 network broadcast entry to the Layer 2 broadcast table of the OpenFlow domain, and queries the corresponding VXLAN tunnel port ID on each device according to the VTEP_IP in it, and adds it to the outgoing port list of the group table. Deliver the updated GROUP group table to each OpenFlow domain device.
  • the method for the controller to synchronize the Layer 2 network broadcast table of the OpenFlow domain to the EVPN domain includes the following steps:
  • Step 201 The controller adds the OpenFlow domain device to the Layer 2 network broadcast domain according to the arrangement of the cloud platform or user configuration, and generates the corresponding Layer 2 network broadcast entry VNET_BROADCAST_INFO, where VTEP_IP is the device IP;
  • Step 202 The controller finds the VXLAN instance ID of the corresponding RD and EVPN domains according to the VNET_ID, and injects the broadcast entry into the VXLAN instance of the routing protocol processing unit;
  • Step 203 The routing protocol processing unit of the controller uses the RD and VTEP_IP to construct a type 3 route, and advertises it to the equipment in the EVPN domain through the BGP EVPN protocol.
  • the method for the controller to synchronize the type 2 routing MAC table of the EVPN domain to the OpenFlow domain includes the following steps:
  • Step 301 The EVPN domain device host goes online, learns the host MAC table, and advertises BGP EVPN type 2 routes, and the routing processing unit of the controller receives the type 2 routes, as shown in Table 2 below:
  • RD uniquely identifies a Layer 2 network
  • L2VNI is used to identify a Layer 2 network when business traffic is forwarded.
  • Step 302 The controller finds the Layer 2 network instance VXLAN_ID of the EVPN domain and the Layer 2 network instance VNET_ID of the OpenFlow domain according to the RD, and generates the host MAC entry required by the OpenFlow domain:
  • vtep_ip is the IP of the EVPN device that publishes the entry, which is obtained by the controller according to the source tunnel of the type 2 routing.
  • port_id is the port number of the host MAC table entry learned, and can be filled with 0, because for OpenFlow domain devices, only the corresponding forwarding path information, that is, the VTEP IP of the destination device, is required, and the specific port on which the host goes online is not concerned;
  • Step 303 The controller adds the above host MAC entry to the OpenFlow domain, queries the corresponding VXLAN tunnel port ID on each device according to the VTEP_IP therein, generates a flow table and sends it to each OpenFlow domain device.
  • Embodiment 6 is a diagrammatic representation of Embodiment 6
  • Step 401 The host of the OpenFlow domain device goes online, the first packet is sent to the controller through the packet-in, and the controller generates the corresponding host MAC table entry HOST_MAC_INFO, where VTEP_IP is the IP of the online device of the host;
  • Step 402 The controller finds the VXLAN instance ID of the corresponding RD and EVPN domains according to the VNET_ID, and injects the host MAC entry into the VXLAN instance of the routing protocol processing unit;
  • Step 403 The routing protocol processing unit of the controller uses the RD and VTEP_IP to construct a type 2 route, and advertises it to devices in the EVPN domain through the BGP EVPN protocol.
  • the method for the controller provided in this embodiment to synchronize the Type 2 routing IP table of the EVPN domain to the OpenFlow domain includes the following steps:
  • Step 501 The EVPN domain device host goes online, learns the host ARP table, and publishes the BGP EVPN type 2 routing IP table, and the routing processing unit of the controller receives the type 2 route, as shown in Table 3 below:
  • RD uniquely identifies a Layer 2 network
  • L2VNI is used to identify a Layer 2 network when business traffic is forwarded
  • L3VNI is used to identify a Layer 3 network when business traffic is forwarded. If the EVPN domain is configured in symmetric forwarding mode, the L2VNI and L3VNI are carried at the same time; if configured in asymmetric forwarding mode, only L2VNI is carried.
  • Step 502 The controller finds the Layer 2 network instance VXLAN_ID of the EVPN domain and the Layer 2 network instance VNET_ID of the OpenFlow domain according to the RD. If L3VNI is empty, the host ARP entry required by the OpenFlow domain is generated:
  • vrf_id is the three-layer network instance ID, which can be determined by querying vnet_id; type identifies the type of ARP table, which is generally divided into static and dynamic. Here it comes from EVPN, and the value is evpn, which means that the OpenFlow domain cannot age the entry , It needs to be deleted by the EVPN domain.
  • port_id is the port number that learned the ARP table entry of the host, fill in 0 here.
  • vrf_id is the three-layer network instance ID, which is determined according to vnet_id query; ip and mask are distributed as the destination prefix and mask length of the route, where ip is the host IP address, and the mask length is 32 (IPv4) or 128 (IPv6); next_hop is the original next hop of the route, which is empty here; router_mac is the MAC address of the EVPN device, used for routing and forwarding packet encapsulation, and it is empty here.
  • Step 503 The controller adds the above-mentioned host ARP entry or host routing table entry to the OpenFlow domain, queries the corresponding VXLAN tunnel port ID on each device according to the VTEP_IP therein, generates a flow table and sends it to each OpenFlow domain device.
  • Embodiment 8 is a diagrammatic representation of Embodiment 8
  • Step 601 The host of the OpenFlow domain device goes online, and the first packet is sent to the controller through the packet-in, and the controller generates the corresponding host ARP dynamic entry ARP_INFO, where VTEP_IP is the IP of the online device of the host.
  • the controller can also generate static ARP entries based on the OpenFlow domain host created by the cloud platform or user trigger;
  • Step 602 The controller finds the VXLAN instance ID of the corresponding RD and EVPN domains according to the VNET_ID, and injects the host ARP entry into the VXLAN instance of the routing protocol processing unit;
  • Step 603 The routing protocol processing unit of the controller uses the RD and VTEP_IP to construct a type 2 routing IP table, and advertises it to devices in the EVPN domain through the BGP EVPN protocol.
  • the method for the controller provided in this implementation to synchronize the Type 5 routing table of the EVPN domain to the OpenFlow domain includes the following steps:
  • Step 701 When creating a three-layer network instance on the controller, use the VRF_ID identification, and the RD (Route Distinguisher) of the instance is automatically generated according to the VRF_ID.
  • the layer 3 network instance issues the routing protocol processing unit in the EVPN domain device and the controller, and uses the VRF_ID to combine into a character string as the name of the layer 3 network routing and forwarding instance;
  • Step 702 When the EVPN domain device configures a static route or learns a dynamic route, it generates a routing forwarding table entry and advertises BGP EVPN type 5 routes, and the routing processing unit of the controller receives the type 5 routes, as shown in Table 4 below :
  • RD uniquely identifies a three-layer network
  • IP Prefix and IP Prefix Len are the IP prefix and prefix length of the route respectively
  • GW IP Address is the IP address of the routing and forwarding gateway
  • L3VNI is the three-layer network identifier when business traffic is forwarded.
  • the GW IP Address is not empty, but the MPLS Label is empty; in the type 5 route V form, the GW IP Address is empty, and the MPLS Label fills in L3VNI, and the BGP EVPN message carries the Router’s MAC extended community attribute.
  • Step 703 The controller finds the layer 3 network routing and forwarding instance of the EVPN domain according to the RD, and obtains the layer 3 network instance VRF_ID of the OpenFlow domain through name conversion of the instance. Generate the routing table entry ROUTE_INFO (see above) required by the OpenFlow domain.
  • ip and mask are distributed as IP Prefix and IP Prefix Len in type 5 routing; for type 5 routing in G form, next_hop is taken as GW IP Address, vtep_ip and router_mac are empty; for type 5 routing in V form, router_mac is carried Router's MAC, vtep_ip is the IP of the EVPN device that publishes the entry.
  • Step 704 The controller adds the aforementioned routing table entry to the OpenFlow domain.
  • the corresponding VXLAN tunnel port ID on each device is queried according to the VTEP_IP of the host routing or ARP table, and the flow table is generated and sent to each OpenFlow domain device;
  • the corresponding VXLAN tunnel port ID on each device is directly queried according to the VTEP_IP, and the flow table is generated and issued.
  • the OpenFlow domain does not actively generate a routing table, there is no need to synchronize routes from the OpenFlow domain to the EVPN domain.
  • the L2VNI and L3VNI of the OpenFlow domain and the EVPN domain are uniformly orchestrated and issued by the controller, and correspond to the two-layer network instance VNET_ID or the three-layer network instance VRF_ID, so no special processing is required during table entry conversion. Items can be ignored during synchronization.
  • This embodiment provides a controller.
  • the SDN corresponds to the controller of this embodiment.
  • the controller includes a routing protocol processing unit and an EVPN table. Item synchronization unit, OpenFlow table item synchronization unit and OpenFlow device management unit;
  • the routing protocol processing unit supports standard BGP EVPN protocol processing, which is used to establish BGP neighbors with devices in the EVPN domain and advertise EVPN routes to each other;
  • the EVPN entry synchronization unit synchronizes the EVPN domain entries learned by the routing protocol processing unit to the OpenFlow domain, and at the same time receives the entry information of the OpenFlow domain and passes it to the routing protocol processing unit;
  • the OpenFlow entry synchronization unit receives the entries of the EVPN domain, and at the same time synchronizes the entries of the OpenFlow domain to the EVPN domain;
  • the OpenFlow device management unit is used to create a VXLAN tunnel in the OpenFlow domain, calculate and generate a flow table for the entries in the OpenFlow domain and the EVPN domain, and deliver the OpenFlow device.
  • This embodiment also provides a heterogeneous network communication system.
  • the heterogeneous network communication system can be seen in FIG. 3.
  • the heterogeneous network communication system includes: a controller, an EVPN domain device, and an OpenFlow domain device;
  • the controller receives the first message reported by the EVPN domain device through the MP-BGP connection channel, converts the first message into the first entry, and synchronizes to the OpenFlow domain device through the OpenFlow connection channel;
  • the controller receives the second message reported by the OpenFlow domain device through the OpenFlow connection channel, converts the second message into a second entry, and synchronizes to the EVPN domain device through the MP-BGP connection channel.
  • the controller as the basis of the heterogeneous network communication system, includes four core units: routing protocol processing unit, EVPN entry synchronization unit, OpenFlow entry synchronization unit and OpenFlow device management unit .
  • the routing protocol processing unit uses the standard BGP EVPN protocol to establish BGP neighbors with devices in the EVPN domain and advertise EVPN routes to each other.
  • the EVPN table entry synchronization unit is responsible for synchronizing the EVPN table entries learned by the routing protocol processing unit to the OpenFlow domain, and at the same time receiving the table entry information of the OpenFlow domain, converting it into EVPN routing information, injecting it into the routing protocol processing unit, and publishing it to the EVPN domain device.
  • the OpenFlow entry synchronization unit receives the entries of the EVPN domain and generates the centralized control plane entries of the controller for user operation and maintenance query and path calculation of the OpenFlow domain; at the same time, it passes the existing OpenFlow domain entries of the controller to the EVPN table. Item synchronization unit.
  • the OpenFlow device management unit in addition to the normal OpenFlow domain device state management, the processing of messages sent by the host, and the creation of a VXLAN static tunnel, it also needs to perform forwarding path calculations for the OpenFlow domain and EVPN domain hosts to generate the forwarding required by the OpenFlow device
  • the flow table is issued concurrently.
  • the communication method and system for VXLAN tunnel creation, table item synchronization, and message forwarding in a heterogeneous network communication system does not affect the original protocol standards and networking methods of the OpenFlow domain and EVPN domain, so that These two SDN technologies are seamlessly integrated to form a hybrid overlay solution, and deployment scenarios are more flexible and diverse.
  • This embodiment also provides a computer-readable storage medium, which is included in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Volatile or non-volatile, removable or non-removable media.
  • Computer-readable storage media include but are not limited to RAM (Random Access Memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, charged Erasable Programmable Read-Only Memory) ), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and that can be accessed by a computer.
  • This embodiment also provides a computer-readable storage medium.
  • the computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the present invention.
  • a heterogeneous network communication method, system, and controller include: the controller receives a first message reported by an EVPN domain device through an MP-BGP connection channel, and converts the first message into a first message. Table entry and synchronize to the OpenFlow domain device through the OpenFlow connection channel; and/or, the controller receives the second packet reported by the OpenFlow domain device through the OpenFlow connection channel, converts the second packet into a second table entry, and passes the MP -The BGP connection channel is synchronized to the EVPN domain device.
  • the controller establishes an MP-BGP connection channel with an EVPN domain device, and an OpenFlow connection channel with an OpenFlow domain device.
  • communication media usually contain computer-readable instructions, data structures, computer program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery medium. Therefore, the embodiments of the present invention are not limited to any specific combination of hardware and software.

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

L'invention concerne un procédé et un système de communication de réseau hétérogène, et un contrôleur. Le procédé comprend les étapes suivantes : un contrôleur reçoit un premier message rapporté par un dispositif de domaine EVPN au moyen d'un canal de connexion MP-BGP, convertit le premier message en une première entrée et synchronise la première entrée avec un dispositif de domaine OpenFlow au moyen d'un canal de connexion OpenFlow ; et/ou le contrôleur reçoit un second message rapporté par le dispositif de domaine OpenFlow au moyen du canal de connexion OpenFlow, convertit le second message en une seconde entrée et synchronise la seconde entrée avec le dispositif de domaine EVPN au moyen du canal de connexion MP-BGP.
PCT/CN2020/114910 2019-11-25 2020-09-11 Procédé et système de communication de réseau hétérogène, et contrôleur Ceased WO2021103744A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911168055.2A CN112838985B (zh) 2019-11-25 2019-11-25 一种异构网络通信方法、系统和控制器
CN201911168055.2 2019-11-25

Publications (1)

Publication Number Publication Date
WO2021103744A1 true WO2021103744A1 (fr) 2021-06-03

Family

ID=75922402

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/114910 Ceased WO2021103744A1 (fr) 2019-11-25 2020-09-11 Procédé et système de communication de réseau hétérogène, et contrôleur

Country Status (2)

Country Link
CN (1) CN112838985B (fr)
WO (1) WO2021103744A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114500171A (zh) * 2021-12-29 2022-05-13 曙光云计算集团有限公司 网络系统及报文传输方法
CN118869581A (zh) * 2024-09-27 2024-10-29 苏州元脑智能科技有限公司 一种网络通信系统、方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9467536B1 (en) * 2014-03-21 2016-10-11 Cisco Technology, Inc. Shim layer abstraction in multi-protocol SDN controller
CN107204907A (zh) * 2016-03-16 2017-09-26 中兴通讯股份有限公司 云数据中心互联方法及装置
CN108989232A (zh) * 2017-05-31 2018-12-11 中兴通讯股份有限公司 Sdn中的报文交互方法及装置
CN109327374A (zh) * 2017-07-31 2019-02-12 杭州达乎科技有限公司 实现三层vpn网络接入的系统及方法
CN109479027A (zh) * 2016-08-04 2019-03-15 思科技术公司 用于互连基于控制器的虚拟网络和基于协议的虚拟网络的技术
CN110391997A (zh) * 2019-07-26 2019-10-29 新华三技术有限公司合肥分公司 一种报文转发方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106549873A (zh) * 2016-12-09 2017-03-29 北京邮电大学 一种异构控制器之间的通信方法及系统
CN108574613B (zh) * 2017-03-07 2022-05-10 中兴通讯股份有限公司 Sdn数据中心的二层互通方法及装置
CN109729019B (zh) * 2018-12-28 2022-05-31 新华三技术有限公司 一种evpn组网中专线业务的限速方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9467536B1 (en) * 2014-03-21 2016-10-11 Cisco Technology, Inc. Shim layer abstraction in multi-protocol SDN controller
CN107204907A (zh) * 2016-03-16 2017-09-26 中兴通讯股份有限公司 云数据中心互联方法及装置
CN109479027A (zh) * 2016-08-04 2019-03-15 思科技术公司 用于互连基于控制器的虚拟网络和基于协议的虚拟网络的技术
CN108989232A (zh) * 2017-05-31 2018-12-11 中兴通讯股份有限公司 Sdn中的报文交互方法及装置
CN109327374A (zh) * 2017-07-31 2019-02-12 杭州达乎科技有限公司 实现三层vpn网络接入的系统及方法
CN110391997A (zh) * 2019-07-26 2019-10-29 新华三技术有限公司合肥分公司 一种报文转发方法及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114500171A (zh) * 2021-12-29 2022-05-13 曙光云计算集团有限公司 网络系统及报文传输方法
CN114500171B (zh) * 2021-12-29 2023-05-26 曙光云计算集团有限公司 网络系统及报文传输方法
CN118869581A (zh) * 2024-09-27 2024-10-29 苏州元脑智能科技有限公司 一种网络通信系统、方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
CN112838985A (zh) 2021-05-25
CN112838985B (zh) 2024-04-02

Similar Documents

Publication Publication Date Title
EP3836490B1 (fr) Procédé de mise en oeuvre inter-domaine de réseau privé virtuel, dispositif et noeud frontière
US10757008B2 (en) Flow specification protocol-based communications method, device, and system
US9998368B2 (en) Zone routing system
CN111510379B (zh) Evpn报文处理方法、设备及系统
CN111865796B (zh) 用于网络业务的路径计算单元中央控制器（pcecc）
CN111385207B (zh) 一种业务数据的转发方法、网络设备及网络系统
EP3896923A1 (fr) Procédé et appareil d'envoi de paquets bier
CN101960785B (zh) 在链路状态协议受控以太网网络上实现vpn
US20230155932A1 (en) Multicast traffic transmission method and apparatus, communication node, and storage medium
WO2021063232A1 (fr) Procédé, appareil et système d'établissement d'élément de table d'acheminement bier
US12040965B2 (en) Supporting multicast communications
EP2466807A1 (fr) Transfert IP dans un réseau Ethernet contrôlé par protocole de routage basé sur le statut de liaison
CN104518972A (zh) 用于链路状态路由协议的动态区域过滤
US20200274739A1 (en) Methods, Nodes and Computer Readable Media for Tunnel Establishment Per Slice
US20220200820A1 (en) Packet Sending Method and Apparatus
US11362954B2 (en) Tunneling inter-domain stateless internet protocol multicast packets
US12244509B2 (en) PIM proxy over EVPN fabric
WO2023045871A1 (fr) Procédé de traitement de paquets, dispositif de réseau et système
WO2013139270A1 (fr) Procédé, dispositif et système pour implémenter un réseau privé virtuel en couche 3
WO2020098611A1 (fr) Procédé et appareil pour acquérir des informations de routage
WO2023274083A1 (fr) Procédé et appareil de publication de route, procédé et appareil de réacheminement de paquets, dispositif, et support de stockage
WO2021103744A1 (fr) Procédé et système de communication de réseau hétérogène, et contrôleur
WO2024016869A1 (fr) Procédé et appareil de configuration de multidiffusion
US9525615B2 (en) Systems and methods for implementing multiple ISIS routing instances on a network element
US11516123B2 (en) Configuring logical network devices for label-switched networks

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

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

Country of ref document: EP

Kind code of ref document: A1