WO2021103744A1

WO2021103744A1 - Heterogeneous network communication method and system, and controller

Info

Publication number: WO2021103744A1
Application number: PCT/CN2020/114910
Authority: WO
Inventors: 许多
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-11-25
Filing date: 2020-09-11
Publication date: 2021-06-03
Also published as: CN112838985B; CN112838985A

Abstract

A heterogeneous network communication method and system, and a controller. The method comprises: a controller receives a first message reported by an EVPN domain device by means of an MP-BGP connection channel, converts the first message into a first entry, and synchronizes the first entry to an OpenFlow domain device by means of an OpenFlow connection channel; and/or, the controller receives a second message reported by the OpenFlow domain device by means of the OpenFlow connection channel, converts the second message into a second entry, and synchronizes the second entry to the EVPN domain device by means of the MP-BGP connection channel.

Description

Heterogeneous network communication method, system and controller

Cross-references to related applications

This application is filed based on a Chinese patent application with an application number of 201911168055.2 and an application date of November 25, 2019, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated into this application by reference.

Technical field

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.

Background technique

Software-defined networking (SDN, Software-defined networking) is an innovative network architecture that separates control logic and data forwarding. When SDN technology is applied in the data center (DC, Data Center), wide area network (WAN, Wide Area Network) and other fields, the VXLAN (Virtual Extensible LAN) tunnel technology is basically adopted to improve the scalability and deployment flexibility of the Layer 2 network. It can also simplify the network hierarchy of overlay services.

OpenFlow and EVPN (Ethernet Virtual Private Network, Ethernet Virtual Private Network) 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. These two technologies have their own advantages and disadvantages, and they are quite different in principle. However, in many deployment scenarios, in order to take advantage of the respective advantages of these two technologies, it is necessary to combine the two technologies to form a hybrid overlay solution.

In OpenFlow, a statically configured VXLAN tunnel is generally used to forward through the flow table. In EVPN, VXLAN is a dynamic tunnel. In the OpenFlow+EVPN hybrid overlay solution, 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.

Summary of the invention

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.

In view of this, 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. Provides the steps of a heterogeneous network communication method.

Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects will become apparent from the description in the specification of the present invention.

Description of the drawings

Figure 1 is a schematic diagram of a VXLAN tunnel in a heterogeneous network provided by the implementation of the present invention;

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.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present invention clearer, the following further describes the embodiments of the present invention in detail through specific implementations in conjunction with the accompanying drawings. It should be understood that the specific embodiments described here are only used to explain the present invention, but not used to limit the present invention.

Example one:

In the application field of SDN, the main solutions are OpenFlow and EVPN. In these two solutions, 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. On the other hand, 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. In order to achieve OpenFlow and In the mixed use of EVPN, 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.

In this embodiment, 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.

Traditional 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. In order to provide support for multiple network layer protocols, 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). In the packets used by BGP-4, three pieces of information related to IPv4 are carried in the Update packet. These three pieces of information are: NLRI (Network Layer Reachability Information) field, Next_Hop attribute, and Aggregator attribute (this attribute contains the aggregation The IP address of the BGP Speaker of the route). In order to support multiple network layer protocols, BGP-4 needs to reflect network layer protocol information to NLRI and Next_Hop. Two new path attributes are introduced in MP-BGP: 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.

In this embodiment, 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.

In this embodiment, 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.

In this embodiment, the MP-BGP connection channel is established as a dynamic VXLAN tunnel, and the dynamic VXLAN tunnel is dynamically established by the EVPN domain device through learning BGP and EVPN.

In this embodiment, 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.

In this embodiment, 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.

In this embodiment, 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.

In the method for heterogeneous network communication provided by the embodiment of the present invention, an MP-BGP connection channel is established with an EVPN domain device through a controller, and 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.

Embodiment two:

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.

Further, 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.

Further, 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.

Further, 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.

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.

Furthermore, 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.

Embodiment three:

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}

The opposite end of a 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. When the OpenFlow domain device joins the Layer 2 network, 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.

Figure 2 is a schematic diagram of table entry synchronization provided by an embodiment of the present invention. As shown in Figure 2, 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 device that delivers the OpenFlow domain. On the other hand, 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.

Regardless of whether it is an OpenFlow domain or an EVPN domain, the forwarding path between devices in the same domain or across domains is the corresponding VXLAN tunnel.

Embodiment four:

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,

Including the following steps:

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:

Table 1 RD route identifier of type 3 route

Among them, RD uniquely identifies a Layer 2 network, and 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:

Among them: 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.

Embodiment five:

The method for the controller to synchronize the Layer 2 network broadcast table of the OpenFlow domain to the EVPN domain provided by the embodiment of the present invention 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.

In the third embodiment, 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:

Table 2 RD route identifier of type 2 route

Among them: 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:

Among them, 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:

The method for the controller provided in this embodiment to synchronize the MAC table of the OpenFlow domain host to the EVPN domain includes the following steps:

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.

Embodiment Seven:

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:

Table 3 RD route identifier of type 2 route

Among them: RD uniquely identifies a Layer 2 network; L2VNI is used to identify a Layer 2 network when business traffic is forwarded, and 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:

Among them: 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.

If L3VNI is not empty, then generate host routing table entries required by the OpenFlow domain:

Among them: 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:

The method for the controller provided in this embodiment to synchronize the ARP table of the OpenFlow domain host to the EVPN domain includes the following steps:

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.

Example 9:

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 :

Table 4 RD route identifier of type 5 route

RD

ESI ID

Eth Tag ID

IP Prefix Len

IP Prefix

GW IP Address

MPLS Label

1:200

0

0～32 or 0～128

IP prefix

IP address

L3VNI

Among them: 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. In the type 5 route G form, 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.

Among them: 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. For the type 5 routing G form, further routing iterations to the host routing or ARP table are required, 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; For the type 5 routing V form, 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.

Since 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. In addition, 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.

Embodiment ten:

This embodiment provides a controller. For a schematic diagram of the controller, refer to FIG. 3. In FIG. 3, the SDN corresponds to the controller of this embodiment. In 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.

In the heterogeneous network communication system of Fig. 3, 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.

In summary, the communication method and system for VXLAN tunnel creation, table item synchronization, and message forwarding in a heterogeneous network communication system provided by the present invention 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. The embodiment and the steps of implementing the heterogeneous network communication method provided in the first to ninth embodiments.

According to an embodiment of 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. This achieves the purpose of receiving the first message from the EVPN domain device and the second message from the OpenFlow domain device, and at the same time, the first The message is converted to the first table entry, the second message is converted to the second table entry, the first table entry is synchronized to the OpenFlow domain device, and the second table entry is synchronized to the EVPN domain device, which realizes the OpenFlow domain device and EVPN The message exchange of domain devices solves the problem that the current OpenFlow domain devices and EVPN domain devices cannot be mixed.

It can be seen that those skilled in the art should understand that all or some of the steps, functional modules/units in the system, and devices in the methods disclosed above can be implemented as software (which can be implemented by computer program code executable by a computing device). ), firmware, hardware and their appropriate combination. In the hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components. The components are executed cooperatively. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .

In addition, as is well known to those of ordinary skill in the art, 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.

The above content is a further detailed description of the embodiments of the present invention in combination with specific implementations, and it cannot be considered that the specific implementation of the embodiments of the present invention is limited to these descriptions. For those of ordinary skill in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the embodiments of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

A heterogeneous network communication method, including:

The controller receives the first message reported by the EVPN domain device through the MP-BGP connection channel, converts the first message into a first entry, and synchronizes 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, converts the second message into a second entry, and synchronizes to the EVPN domain device through the MP-BGP connection channel.
The heterogeneous network communication method according to claim 1, wherein the first message and the second table entry comprise: any one of type 3 routing, type 2 routing, and type 5 routing;

The second message and the first entry include: any one of a layer 2 network broadcast table, a MAC table, an ARP table, and a routing table;

The type 3 route corresponds to the layer 2 network broadcast table, the type 2 route corresponds to the MAC table and the ARP table, and the type 5 route corresponds to the routing table.
The heterogeneous network communication method according to claim 1, wherein when the EVPN domain device is a hardware switch, the host mounted under the EVPN domain device includes any one of a bare metal server and a virtual machine isolated by vlan in the server. Species

When the OpenFlow domain device is a vSwitch software virtual switch, the host mounted under the OpenFlow domain device is a virtual machine.
The heterogeneous network communication method according to any one of claims 1 to 3, wherein the MP-BGP connection channel is established as a dynamic VXLAN tunnel, and the dynamic VXLAN tunnel is used by the EVPN domain device to learn BGP EVPN dynamics set up.
The heterogeneous network communication method according to claim 4, wherein the EVPN domain device and the OpenFlow domain device learn the first table entry and/or the second table entry to generate layer 2 and layer 3 forwarding tables item.
The heterogeneous network communication method according to any one of claims 1-3, wherein the OpenFlow connection channel is a static VXLAN tunnel after being established, and the static VXLAN tunnel is statically imported and configured by the controller to the OpenFlow domain device The static VXLAN tunnel uses the VTEP IP of the devices at both ends as a unique identifier.
The heterogeneous network communication method according to claim 6, wherein the outbound interface of the VTEP IP identification 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 realize the same Domain or cross-domain packet forwarding.
A controller including:

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 is used to synchronize the EVPN domain entries learned by the routing protocol processing unit to the OpenFlow domain, and at the same time receive the entry information of the OpenFlow domain and pass it to the routing protocol processing unit;

The OpenFlow entry synchronization unit is used to receive the entries of the EVPN domain, and at the same time synchronize 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.
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 the MP-BGP connection channel, converts the first message into a 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.
A computer-readable storage medium that stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the method according to any one of claims 1 to 7 The steps of a heterogeneous network communication method.