Interworking method and device for VXLAN EVPN symmetrical networking

Abstract

This application relates to an interconnection method and apparatus for VXLAN EVPN symmetrical networking. The method includes: configuring a Common Layer 3 Virtual Network Identifier (VNI) on the VXLAN interface of a VTEP device; after receiving target traffic, the local VTEP device performs a route lookup on the destination address corresponding to the target traffic; when the destination address matches a gateway-directed route but no corresponding address resolution information is obtained, a probe route is generated; the probe route is sent to the peer VTEP device; an EVPN Type II route is received from the peer VTEP device; and the target traffic is forwarded according to the EVPN Type II route to achieve interconnection in VXLAN EVPN symmetrical networking. The interconnection method and apparatus for VXLAN EVPN symmetrical networking disclosed in this application can solve the interconnection obstacles caused by missing address resolution information in unidirectional traffic scenarios, and achieve rapid establishment and reliable interconnection of bidirectional traffic.

Description

Technical Field

[0001] This application relates to the field of computer information processing, and more specifically, to an interconnection method and apparatus for VXLAN EVPN symmetric networking. Background Technology

[0002] VXLAN (Virtual eXtensible Local Area Network) and EVPN (Ethernet Virtual Private Network) technologies are widely used in data center networks due to their excellent Layer 2 scalability and the separation of the control plane and forwarding plane, and are especially suitable for virtual machine migration scenarios.

[0003] In a VXLAN EVPN symmetric network that supports virtual machine migration, it is usually necessary to configure the same VXLAN gateway IP address and the same MAC address on multiple access devices or VXLAN Tunnel Endpoint (VTEP) devices so that business continuity can be maintained before and after virtual machine migration without modifying the network configuration.

[0004] Since different VTEP devices need to be configured with the same gateway address, existing technologies typically use a Layer 2 isolation method for networking. A common implementation is to assign the gateway to a Virtual Router Forwarding Instance (VRF), deploy the VXLAN tunnel on the VTEP device in a public VRF, and deploy the gateway access in a private VRF, while enabling the distributed gateway function on the VTEP device.

[0005] In this type of symmetrical network topology, even if the local VTEP device and the remote VTEP device are connected to hosts on the same network segment, the local VTEP device cannot directly learn the ARP (Address Resolution Protocol) or ND (Neighbor Discovery) information of the hosts connected to the remote VTEP device. Therefore, existing technologies typically enable ARP proxy or ND proxy functions on the gateway side, forcing relevant traffic to be forwarded through Layer 3. The implementation logic in the IPv6 scenario is similar to that in the IPv4 scenario.

[0006] The information disclosed in the background section is only intended to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0007] In view of this, this application provides an interconnection method and apparatus for VXLAN EVPN symmetric networking, which can solve the interconnection obstacles caused by the lack of address resolution information in unidirectional traffic scenarios and realize the rapid establishment and reliable interconnection of bidirectional traffic.

[0008] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0009] According to one aspect of this application, an interoperability method for VXLAN EVPN symmetrical networking is proposed. The method includes: configuring a common Layer 3 Virtual Network Identifier (VNI) on the VXLAN interface of a VTEP device; after receiving target traffic, the local VTEP device performs a route lookup on the destination address corresponding to the target traffic; when the destination address matches a gateway-directed route but no corresponding address resolution information is obtained, a probe route is generated; the probe route is sent to the peer VTEP device; an EVPN Class II route is received from the peer VTEP device; and the target traffic is forwarded according to the EVPN Class II route to achieve interoperability under VXLAN EVPN symmetrical networking.

[0010] In one exemplary embodiment of this application, when the destination address matches a gateway-directed route but no corresponding address resolution information is obtained, a probe route is generated, including: when the destination address matches a gateway-directed route and the corresponding ARP entry or ND entry is in an incomplete state, performing ARP probe or ND probe on the destination address; and when the probe fails and the VXLAN interface is configured with the common Layer 3 VNI, generating the probe route based on the destination address.

[0011] In one exemplary embodiment of this application, the method further includes: performing deduplication processing on probe routes that have the same common Layer 3 VNI, the same Layer 2 VNI, and the same address information.

[0012] In one exemplary embodiment of this application, sending the probe route to the peer VTEP device includes: sending the probe route to the peer VTEP device via Border Gateway Protocol (BGP).

[0013] In one exemplary embodiment of this application, after sending the probe route to the peer VTEP device, the method further includes: the peer VTEP device determining the target VXLAN interface based on the common Layer 3 VNI and address information carried by the probe route; and performing ARP probe or ND probe on the target VXLAN interface.

[0014] In one exemplary embodiment of this application, the peer VTEP device determines the target VXLAN interface based on the common Layer 3 VNI and address information carried by the probe route, including: after passing the BGP filtering policy, searching for a VXLAN interface with the same common Layer 3 VNI carried by the probe route in the VRFs that meet the filtering conditions; determining whether the target address carried by the probe route matches the network segment to which the VXLAN interface belongs; and if the match is successful, determining the VXLAN interface as the target VXLAN interface.

[0015] In one exemplary embodiment of this application, the method further includes: generating an EVPN Class II route after the peer VTEP device detects the corresponding ARP entry or ND entry.

[0016] In one exemplary embodiment of this application, after receiving the EVPN Type II route sent by the peer VTEP device, the method further includes: stopping ARP probing or ND probing based on the destination address; updating the corresponding ARP entry or ND entry to the NONE state; and, when a preset condition is met, canceling the corresponding probe route and sending route cancellation information to the peer VTEP device via BGP.

[0017] In one exemplary embodiment of this application, forwarding the target traffic according to the EVPN Type II route includes: establishing a detailed route to the remote access host according to the EVPN Type II route; and forwarding the target traffic based on the detailed route.

[0018] According to one aspect of this application, an interconnection device for VXLAN EVPN symmetrical networking is proposed. This device can be used in VTEP devices in VXLAN EVPN symmetrical networking. The device includes: a configuration module for configuring a common Layer 3 Virtual Network Identifier (VNI) on the VXLAN interface of the VTEP device; a query module for performing a route query on the destination address corresponding to the target traffic after the local VTEP device receives the target traffic; an information module for generating a probe route when the destination address matches a gateway direct-connected route but no corresponding address resolution information is obtained; a sending module for sending the probe route to the peer VTEP device; a receiving module for receiving the EVPN Class II route sent by the peer VTEP device; and a forwarding module for forwarding the target traffic according to the EVPN Class II route to achieve interconnection in VXLAN EVPN symmetrical networking.

[0019] According to one aspect of this application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs; and, when the one or more programs are executed by the one or more processors, causing the one or more processors to implement the method as described above.

[0020] According to one aspect of this application, a computer-readable medium is provided having a computer program stored thereon that, when executed by a processor, implements the method described above.

[0021] According to the interconnection method and apparatus for VXLAN EVPN symmetrical networking of this application, a common Layer 3 Virtual Network Identifier (VNI) is configured on the VXLAN interface of the VTEP device; after the local VTEP device receives target traffic, it performs a route query on the destination address corresponding to the target traffic; when the destination address matches the gateway direct-connected route but no corresponding address resolution information is obtained, a probe route is generated; the probe route is sent to the peer VTEP device; the local VTEP device receives the EVPN Class II route sent by the peer VTEP device; and the target traffic is forwarded according to the EVPN Class II route. This achieves interconnection under VXLAN EVPN symmetrical networking, which can solve the interconnection obstacles caused by the lack of address resolution information in unidirectional traffic scenarios and realize the rapid establishment and reliable interconnection of bidirectional traffic.

[0022] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this application. Attached Figure Description

[0023] The above and other objects, features, and advantages of this application will become more apparent from the detailed description of exemplary embodiments with reference to the accompanying drawings. The drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0024] Figure 1 This is a schematic diagram of the interconnection method for VXLAN EVPN symmetrical networking in existing technologies.

[0025] Figure 2 This is a flowchart illustrating an interconnection method for VXLAN EVPN symmetric networking according to an exemplary embodiment.

[0026] Figure 3 This is a flowchart illustrating an interconnection method for VXLAN EVPN symmetric networking according to another exemplary embodiment.

[0027] Figure 4 This is a flowchart illustrating an interconnection method for VXLAN EVPN symmetric networking according to another exemplary embodiment.

[0028] Figure 5 This is a block diagram illustrating an interconnection device for VXLAN EVPN symmetrical networking according to an exemplary embodiment.

[0029] Figure 6 This is a block diagram illustrating an electronic device according to an exemplary embodiment.

[0030] Figure 7 This is a block diagram illustrating a computer-readable medium according to an exemplary embodiment. Detailed Implementation

[0031] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this application will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0032] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0033] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0034] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0035] It should be understood that although the terms first, second, third, etc., may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of this application. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

[0036] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of exemplary embodiments, and the modules or processes in the drawings are not necessarily essential for implementing this application, and therefore cannot be used to limit the scope of protection of this application.

[0037] The technical abbreviations used in this application are explained as follows: Traffic: refers to the set of data packets forwarded in a network.

[0038] BGP: Border Gateway Protocol, is used for exchanging routing information between different networks.

[0039] VXLAN: Virtual eXtensible Local Area Network, is a tunneling encapsulation technology used to build large-scale Layer 2 networks.

[0040] ARP: Address Resolution Protocol, is used to resolve IP addresses to MAC addresses. It dynamically maintains the mapping relationship between IP addresses and MAC addresses through broadcast requests and unicast responses.

[0041] ND: Neighbor Discovery, a protocol used for address resolution and neighbor discovery in IPv6 networks.

[0042] VTEP: VXLAN Tunnel Endpoint, used for the encapsulation and decapsulation of VXLAN packets.

[0043] EVPN: Ethernet Virtual Private Network, is an MP-BGP address family used to carry and exchange VXLAN-related routing information.

[0044] MP-BGP: Multiprotocol Border Gateway Protocol, used to support the exchange of routing information among multiple address families.

[0045] Address family: An encapsulation and interaction format defined in MP-BGP to support the exchange of one or more routing information.

[0046] VRF: Virtual Routing and Forwarding, is used to implement multiple independent routing and forwarding tables within the same device.

[0047] Tunnel: A data transmission channel constructed using a specific encapsulation format. Messages transmitted in a tunnel must conform to the corresponding encapsulation format.

[0048] Inner message: After adding the VXLAN encapsulation header, the original message inside the VXLAN encapsulation has the same content as the message without VXLAN encapsulation.

[0049] Outer message: A UDP encapsulated message with the VXLAN tunnel peer as the destination IP address after adding a VXLAN encapsulation header.

[0050] Symmetrical networking: An EVPN networking method that supports virtual machine migration. In this networking method, traffic is forwarded at Layer 3 and the forwarding paths of the two communicating parties are symmetrical.

[0051] EVPN Category 2 Routing: Category 2 routing in EVPN, namely MAC / IP routing, is used to publish the MAC address and IP address information of hosts. It is usually used to synchronize ARP or ND information between VTEP devices.

[0052] like Figure 1 As shown, after investigation, the applicant found that in the implementation of existing ARP proxy or ND proxy, it is usually necessary to first determine whether a corresponding reachable route exists on the local VTEP device. If a reachable route exists, ARP proxy or ND proxy is performed; if no reachable route exists, no proxy operation is performed.

[0053] When a VTEP device learns an ARP or ND entry, it encapsulates the corresponding entry into an EVPN Type II route and advertises it to neighboring devices via Border Gateway Protocol (BGP). Upon receiving the EVPN Type II route, the peer device determines whether to process the route by checking if the route-target extended community attribute carried by the route matches the route-target configured in its local VRF. If a match is successful, a corresponding host route is generated to guide subsequent traffic forwarding; otherwise, the corresponding route is not used. Because ARP or ND proxies use Layer 3 forwarding when enabled, incoming traffic on the local device needs to rely on the corresponding route for forwarding.

[0054] However, in the existing VXLAN EVPN distributed virtual machine migration network, when both VTEP devices only publish EVPN Category 2 routes, if the destination address of the target traffic received by the local end belongs to the local VXLAN interface network segment, but the corresponding virtual machine is actually connected to the remote VTEP device, the local VTEP device can only hit the local directly connected route when querying routes, and cannot know which remote VTEP device the corresponding virtual machine is actually located on.

[0055] Meanwhile, because ARP proxy or ND proxy and distributed gateway functions are enabled, ARP request packets or ND request packets will not be sent to the remote VTEP device through the VXLAN tunnel, thus preventing the remote VTEP device from detecting probe requests for the corresponding address. Therefore, before the local end has learned the corresponding ARP or ND entries for the remote host, target traffic cannot communicate normally. Existing technologies typically rely on the VTEP device actively learning ARP / ND information, or on the access host actively sending gratuitous ARP packets to trigger the corresponding EVPN Category 2 route advertisement.

[0056] However, in scenarios with only unidirectional traffic, the remote VTEP device may never learn the corresponding ARP or ND entries, thus failing to advertise the corresponding EVPN Category 2 routes to the local device. In this case, even if the remote virtual machine remains online, the local VTEP device, unaware of the remote host's existence, cannot forward the corresponding traffic normally, leading to communication failures in VXLAN EVPN symmetric networking.

[0057] To address the technical bottlenecks in existing technologies, this application proposes an interoperability method for VXLAN EVPN symmetrical networking. The content of this application will be described in detail below with the aid of specific embodiments.

[0058] Figure 2 This is a flowchart illustrating an interoperability method for a VXLAN EVPN symmetric network according to an exemplary embodiment. The interoperability method 20 for a VXLAN EVPN symmetric network includes at least steps S202 to S212.

[0059] like Figure 2 As shown, in S202, a common Layer 3 Virtual Network Identifier (VNI) is configured on the VXLAN interface of the VTEP device.

[0060] In one embodiment, the public Layer 3 VNI is used to identify the VXLAN interface with probe functionality enabled and for subsequent probe route filtering and matching. One public Layer 3 VNI can be configured under each VXLAN interface, and different VXLAN interfaces are allowed to be configured with the same public Layer 3 VNI. Furthermore, the public Layer 3 VNI does not overlap with Layer 2 VNIs, nor with private Layer 3 VNIs in the VRF.

[0061] In one embodiment, the corresponding VXLAN interfaces on the local VTEP device and the remote VTEP device can be configured with the same common Layer 3 VNI, enabling both parties to identify corresponding probe functions based on the common Layer 3 VNI. The common Layer 3 VNI can be configured on the VXLAN interface with the distributed gateway function enabled.

[0062] In S204, after the local VTEP device receives the target traffic, it performs a route lookup for the destination address corresponding to the target traffic.

[0063] In this embodiment, the target traffic can be data traffic sent by the access host. After receiving the target traffic, the local VTEP device can query its local routing table based on the destination address.

[0064] In one embodiment, when the destination address belongs to the network segment of the local VXLAN interface, the corresponding gateway direct route can be matched. Since ARP proxy or ND proxy functions are enabled in VXLAN EVPN symmetrical networking, the target traffic is processed using a Layer 3 forwarding method after access.

[0065] In S206, when the destination address matches a directly connected route to the gateway but no corresponding address resolution information is obtained, a probe route is generated. For example, if the destination address matches a directly connected route to the gateway and the corresponding ARP or ND entry is in an incomplete state, an ARP probe or ND probe is performed on the destination address; if the probe fails and the VXLAN interface is configured with the common Layer 3 VNI, the probe route is generated based on the destination address.

[0066] In this embodiment, for example, when the destination address matches a gateway direct route and the corresponding ARP or ND entry is in an incomplete state, an ARP probe or ND probe can be performed on the destination address.

[0067] Furthermore, if no corresponding ARP or ND entry is obtained after a preset detection period, and the VXLAN interface is configured with the common Layer 3 VNI, the probe route is generated based on the destination address.

[0068] In one embodiment, the ARP probe may employ a broadcast ARP request method, and the ND probe may employ a neighbor request message method. The preset probe period and probe interval can be determined according to the device configuration.

[0069] In one embodiment, the probe route is a function class route derived from an EVPN Type II route extension. The probe route may carry a common Layer 3 VNI, a Layer 2 VNI, and the address to be probed, to trigger a remote VTEP device to perform address probing.

[0070] Furthermore, the probe route can adopt the following field format: MAC address length field is 0, MAC address field is all 0s, Ethernet Tag ID field is 0, ESI field is 0; Layer 2 VNI field is the Layer 2 VNI bound to the corresponding VXLAN interface; Layer 3 VNI field is the public Layer 3 VNI; in ARP scenario, IP address length field is 32; in ND scenario, IP address length field is 128.

[0071] In one embodiment, the method further includes: performing deduplication processing on probe routes that have the same common Layer 3 VNI, the same Layer 2 VNI, and the same address information.

[0072] Specifically, probe routes corresponding to the same common Layer 3 VNI, the same Layer 2 VNI, and the same destination address are not generated repeatedly, in order to reduce the number of duplicate probe routes in the control plane and reduce the occupation of network device resources.

[0073] In S208, the probe route is sent to the peer VTEP device. For example, the probe route can be sent to the peer VTEP device via Border Gateway Protocol (BGP). In this embodiment, the probe route can be propagated via the EVPN address family. Further, the probe route may carry a route-target extended community attribute, which can be the route-target configured in the Layer 2 domain to which the corresponding Layer 2 VNI belongs.

[0074] In one embodiment, after the probe route is generated by the local VTEP device, it can first be added to the local BGP routing table, and then advertised to the remote VTEP device through BGP neighbor relationships. The process of advertising the probe route can be applied to route reflectors and existing BGP filtering control policies.

[0075] In one embodiment, after sending the probe route to the peer VTEP device, the method further includes: the peer VTEP device determining the target VXLAN interface based on the common Layer 3 VNI and address information carried by the probe route; and performing ARP probe or ND probe on the target VXLAN interface.

[0076] More specifically, the peer VTEP device determines the target VXLAN interface based on the common Layer 3 VNI and address information carried by the probe route, including: after passing the BGP filtering policy, searching for a VXLAN interface with the same common Layer 3 VNI as the probe route in the VRFs that meet the filtering conditions; determining whether the target address carried by the probe route matches the network segment to which the VXLAN interface belongs; and if the match is successful, determining the VXLAN interface as the target VXLAN interface.

[0077] In one embodiment, when multiple VXLAN interfaces meet the above matching conditions, ARP probing or ND probing can be performed simultaneously on multiple VXLAN interfaces.

[0078] Furthermore, if the peer VTEP device does not detect the corresponding ARP or ND entry within the preset detection period, and the corresponding detection route still exists, a backoff algorithm can be used to increase the subsequent detection interval to reduce the network resource consumption caused by frequent detection.

[0079] In one embodiment, the method further includes generating an EVPN Class II route after the peer VTEP device detects the corresponding ARP or ND entry.

[0080] Specifically, after learning the corresponding ARP or ND entry, the peer VTEP device can convert the corresponding entry into an EVPN Type II route and send it to the local VTEP device via BGP. The EVPN Type II route can be used to generate host routes for the corresponding destination address.

[0081] The aforementioned Type 2 EVPN routes are referred to as probe Type 2 routes. After route generation, they are first added to the local VTEP BGP table. The route target extended community attribute carries the route target configured in the Layer 2 domain where the VNI bound to the VXLAN interface resides. The process of learning ARP / ND and converting it to a Type 2 EVPN route under this VXLAN interface is the same. Subsequent route advertising by the local VTEP BGP and route filtering and reception by the remote VTEP BGP are the same as for ordinary Type 2 EVPN routes, and reflectors and other BGP filtering control policies are also applicable. The difference is that after receiving a probe Type 2 route, the remote BGP does not use it to generate host routes. After filtering, it searches for all VXLAN interfaces with the same Layer 3 VNI configuration as the probe Type 2 route in the VRFs that meet the filtering conditions. If found, it checks whether the address carried in the Type 2 route and the address range of this VXLAN interface are in the same network segment. If they are in the same network segment, ARP / ND probing is performed on this VXLAN interface using the address carried in the route. The probing interval and period depend on the remote VTEP configuration. If the remote VTEP has multiple VXLAN interfaces that meet the above conditions, the above probing actions will be performed simultaneously on all interfaces. If the remote VTEP does not detect an ARP / ND entry for the corresponding address after the address probing cycle ends, but the Type 2 EVPN probe route in BGP still exists, a backoff algorithm is used to extend the probing interval. Probing stops after the Type 2 EVPN probe route in BGP is withdrawn. If the remote VTEP detects an ARP / ND entry for the corresponding address, the remote VTEP will no longer pay attention to the corresponding Type 2 EVPN probe route. Type 2 EVPN probe routes received by the remote VTEP follow BGP neighbor changes. If the remote VTEP does not support Type 2 EVPN probe routes, it will discard the route because the MAC address length carried by the route is invalid.

[0082] In S210, the local VTEP device receives the EVPN Type II route sent by the peer VTEP device. In this embodiment, after receiving the EVPN Type II route, the local VTEP device can generate a detailed route corresponding to the destination address based on the EVPN Type II route, so that subsequent traffic no longer hits the gateway directly connected route, but instead hits the host route pointing to the remote VTEP device.

[0083] In one embodiment, after receiving the EVPN Type II route sent by the peer VTEP device, the method further includes: stopping ARP probing or ND probing based on the destination address; updating the corresponding ARP entry or ND entry to the NONE state; and, when a preset condition is met, canceling the corresponding probe route and sending route cancellation information to the peer VTEP device via BGP.

[0084] Specifically, the preset conditions may include: the corresponding ARP entry or ND entry entering the NONE state for a preset duration, or the corresponding ARP entry or ND entry being reclaimed.

[0085] In S212, the target traffic is forwarded according to the EVPN Type II route to achieve interconnection under VXLAN EVPN symmetrical networking. For example, a detailed route to the remote access host can be established based on the EVPN Type II route; the target traffic is forwarded based on the detailed route.

[0086] In this embodiment, after the local VTEP device hits the corresponding detailed route, it can encapsulate the target traffic into a VXLAN packet and send it to the corresponding remote VTEP device through a VXLAN tunnel. The remote VTEP device then performs VXLAN decapsulation and forwards the packet to the corresponding access host, thereby achieving traffic interconnection under the VXLAN EVPN symmetrical networking.

[0087] After the local VTEP receives a Type 2 EVPN route from the remote VTEP, local traffic will no longer be forwarded to the directly connected route, but will instead be forwarded to the detailed route to the remote VTEP. Therefore, no traffic will trigger a probe to the corresponding IP address. The local ARP / ND entry will be updated to the NONE state. After a certain period of time T1 after the ARP / ND entry is updated to the NONE state, T1 is configurable, or the ARP / ND entry is recycled, the local VTEP will notify the local BGP that the Type 2 probe EVPN route to the corresponding address has been withdrawn. Subsequently, the local VTEP's BGP will advertise the route withdrawal to the remote VTEP.

[0088] According to the interoperability method for VXLAN EVPN symmetrical networking of this application, a common Layer 3 Virtual Network Identifier (VNI) is configured on the VXLAN interface of the VTEP device; after the local VTEP device receives target traffic, it performs a route lookup on the destination address corresponding to the target traffic; when the destination address matches the gateway's directly connected route but no corresponding address resolution information is obtained, a probe route is generated; the probe route is sent to the peer VTEP device; the local VTEP device receives the EVPN Class II route sent by the peer VTEP device; and the target traffic is forwarded according to the EVPN Class II route. This method achieves interoperability under VXLAN EVPN symmetrical networking, which can solve the interoperability barrier caused by the lack of address resolution information in unidirectional traffic scenarios and realize the rapid establishment and reliable interoperability of bidirectional traffic.

[0089] It should be clearly understood that this application describes how specific examples are formed and used, but the principles of this application are not limited to any details of these examples. Rather, based on the teachings of the disclosure of this application, these principles can be applied to many other embodiments.

[0090] Figure 3 This is a flowchart illustrating an interconnection method for VXLAN EVPN symmetric networking according to another exemplary embodiment. Figure 3 The process shown in step 30 is... Figure 2 A detailed description of the process shown.

[0091] like Figure 3 As shown, in S302, a message is received. Specifically, the local VTEP device receives the target message sent by the access host and obtains the destination address information corresponding to the target message.

[0092] In S304, no route was found. The local VTEP device queried its local routing table based on the destination address, but no corresponding route entry was found.

[0093] In S306, packet loss occurs. If no corresponding route is found, the local VTEP device discards the target packet.

[0094] In S308, a non-directly connected route was found.

[0095] In S310, forwarding is performed according to the route. The local VTEP device forwards the target packet based on the next-hop information corresponding to the non-directly connected route.

[0096] In S312, a directly connected route was found. The local VTEP device found that the destination address matched the gateway directly connected route corresponding to the VXLAN interface.

[0097] In S314, an ARP / ND probe is triggered. When the corresponding ARP or ND entry does not exist or is in an incomplete state, the local VTEP device performs an ARP or ND probe on the destination address.

[0098] In S316, ARP / ND detection was successful. The end VTEP device learned the corresponding ARP or ND entry.

[0099] In S318, normal forwarding occurs. The local VTEP device forwards the target packet normally based on the learned ARP or ND entries.

[0100] In S320, if ARP / ND probes fail, a new probe is triggered. If no corresponding ARP or ND entry is learned after a preset probe period, ARP or ND probes are triggered again based on the continuously received target traffic.

[0101] In S322, the VXLAN interface is configured with a common Layer 3 VNI. The local VTEP device detects that the current VXLAN interface is configured with a common Layer 3 VNI and enables the route detection function.

[0102] In S324, a Type II EVPN route is generated. The local VTEP device generates a Type II EVPN probe route based on the destination address to trigger remote probes.

[0103] In S326, the route is sent to the BGP neighbor. The local VTEP device sends the EVPN Type II probe route to the BGP neighbor device via the BGP EVPN address family.

[0104] In S328, the VXLAN interface is not configured with a common Layer 3 VNI. The local VTEP device detects that the current VXLAN interface does not have the common Layer 3 VNI function enabled.

[0105] In S330, the probing continues. Specifically, the local VTEP device continues to perform ARP or ND probing until it learns the corresponding ARP or ND entry, or until a preset termination condition is met.

[0106] Figure 4 This is a flowchart illustrating an interconnection method for VXLAN EVPN symmetric networking according to another exemplary embodiment. Figure 4 The process shown in step 40 is... Figure 2 A detailed description of the process shown.

[0107] like Figure 4 As shown, in S402, a probe Type II EVPN route is received. The peer VTEP device receives the probe Type II EVPN route sent by the local VTEP device through the BGP EVPN address family.

[0108] In S404, the VXLAN interface configured with the same public VNI under the VRF is searched. After passing the BGP filtering policy, the peer VTEP device searches for the VXLAN interface with the same public Layer 3 VNI carried by the probed Type II EVPN route in the VRF that meets the filtering conditions.

[0109] In S406, no interface was found, or the interface's configured network segment is different from the received route's network segment. No VXLAN interface matching the common Layer 3 VNI was found, or the network segment to which the VXLAN interface belongs is not the same network segment as the destination address carried by the probed Type 2 EVPN route.

[0110] In S408, no processing is performed. The peer VTEP device does not perform ARP or ND probe processing on the probed Type II EVPN routes.

[0111] In S410, the interface is located, and the interface's configured network segment is the same as the received route's network segment. A VXLAN interface matching the common Layer 3 VNI is found, and the network segment to which the VXLAN interface belongs is the same as the target address carried by the probed Type 2 EVPN route.

[0112] In S412, the interface probe receives the routed IP. The peer VTEP device performs ARP probe or ND probe on the target IP address carried by the probed Type II EVPN route under the VXLAN interface.

[0113] In S414, it was detected that the peer VTEP device has learned the ARP entry or ND entry corresponding to the target address.

[0114] In S416, Type II EVPN routes are generated and advertised. The peer VTEP device generates the corresponding Type II EVPN routes based on the learned ARP or ND entries and advertises them to the local VTEP device via BGP.

[0115] In S418, no route was detected, and the BGP route still exists. After a preset probe period, no corresponding ARP or ND entry was learned, and the corresponding Type II EVPN route still exists in the BGP routing table.

[0116] In S420, backoff detection is implemented. Specifically, the peer VTEP device uses a backoff algorithm to increase the detection interval of subsequent ARP or ND probes, and continues to perform the corresponding detection operation.

[0117] Those skilled in the art will understand that all or part of the steps of the above embodiments are implemented as a computer program executed by a CPU. When the computer program is executed by the CPU, it performs the functions defined by the method provided in this application. The program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk, or an optical disk.

[0118] Furthermore, it should be noted that the above figures are merely illustrative representations of the processes included in the method according to exemplary embodiments of this application, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0119] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0120] Figure 5This is a block diagram illustrating an interconnection device for VXLAN EVPN symmetrical networking according to an exemplary embodiment. Figure 5 As shown, the interconnection device 50 for VXLANEVPN symmetric networking includes: a configuration module 502, a query module 504, an information module 506, a sending module 508, a receiving module 510, and a forwarding module 512.

[0121] Configuration module 502 is used to configure a common Layer 3 Virtual Network Identifier (VNI) on the VXLAN interface of the VTEP device; The query module 504 is used to perform a route query on the destination address corresponding to the target traffic after the local VTEP device receives the target traffic; Information module 506 is used to generate a probe route when the destination address matches a gateway-directly connected route but no corresponding address resolution information is obtained; The sending module 508 is used to send the probe route to the peer VTEP device; The receiving module 510 is used to receive the EVPN Category 2 route sent by the peer VTEP device; The forwarding module 512 is used to forward the target traffic according to the EVPN Category II route to achieve interconnection under the VXLAN EVPN symmetrical networking.

[0122] According to the interconnection device for VXLAN EVPN symmetrical networking of this application, a common Layer 3 Virtual Network Identifier (VNI) is configured on the VXLAN interface of the VTEP device; after the local VTEP device receives target traffic, it performs a route query on the destination address corresponding to the target traffic; when the destination address matches the gateway direct route but no corresponding address resolution information is obtained, a probe route is generated; the probe route is sent to the peer VTEP device; the device receives the EVPN Class II route sent by the peer VTEP device; and forwards the target traffic according to the EVPN Class II route. This achieves interconnection under VXLAN EVPN symmetrical networking, which can solve the interconnection obstacles caused by the lack of address resolution information in unidirectional traffic scenarios and realize the rapid establishment and reliable interconnection of bidirectional traffic.

[0123] Figure 6 This is a block diagram illustrating an electronic device according to an exemplary embodiment.

[0124] The following reference Figure 6 To describe an electronic device 600 according to this embodiment of the present application. Figure 6 The electronic device 600 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0125] like Figure 6As shown, the electronic device 600 is presented in the form of a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different system components (including storage unit 620 and processing unit 610), a display unit 640, etc.

[0126] The storage unit stores program code that can be executed by the processing unit 610, causing the processing unit 610 to perform the steps described in this specification according to various exemplary embodiments of this application. For example, the processing unit 610 can perform actions such as... Figure 2 , Figure 3 , Figure 4 The steps are shown in the figure.

[0127] The storage unit 620 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 6201 and / or a cache storage unit 6202, and may further include a read-only memory unit (ROM) 6203.

[0128] The storage unit 620 may also include a program / utility 6204 having a set (at least one) program module 6205, such program module 6205 including but not limited to: an operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0129] Bus 630 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0130] Electronic device 600 can also communicate with one or more external devices 600' (e.g., keyboard, pointing device, Bluetooth device, etc.), enabling users to communicate with devices that interact with electronic device 600, and / or any device that allows electronic device 600 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 650. Furthermore, electronic device 600 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 660. Network adapter 660 can communicate with other modules of electronic device 600 via bus 630. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0131] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software, or by combining software with necessary hardware. Therefore, as... Figure 7 As shown, the technical solution according to the embodiments of this application can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, mobile hard drive, etc.) or on a network, and includes several instructions to cause a computing device (such as a personal computer, server, or network device, etc.) to execute the above-described method according to the embodiments of this application.

[0132] The software product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0133] The computer-readable storage medium may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The readable storage medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0134] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0135] The aforementioned computer-readable medium carries one or more programs. When these programs are executed by one of the devices, the computer-readable medium performs the following functions: configuring a common Layer 3 Virtual Network Identifier (VNI) on the VXLAN interface of the VTEP device; after receiving target traffic, the local VTEP device performs a route lookup for the destination address corresponding to the target traffic; when the destination address matches a gateway-directed route but no corresponding address resolution information is obtained, a probe route is generated; the probe route is sent to the peer VTEP device; the local VTEP device receives an EVPN Type II route sent by the peer VTEP device; and the target traffic is forwarded according to the EVPN Type II route to achieve interconnection under a VXLAN EVPN symmetrical network topology.

[0136] Those skilled in the art will understand that the above modules can be distributed in the device as described in the embodiments, or they can be modified accordingly and placed in one or more devices that are unique to this embodiment. The modules in the above embodiments can be combined into one module, or they can be further divided into multiple sub-modules.

[0137] Through the description of the above embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this application.

[0138] Exemplary embodiments of this application have been specifically shown and described above. It should be understood that this application is not limited to the detailed structures, arrangements, or implementation methods described herein; rather, this application is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. An interconnection method for VXLAN EVPN symmetrical networking, which can be used for VTEP devices in VXLAN EVPN symmetrical networking, characterized in that, include: Configure a common Layer 3 Virtual Network Identity (VNI) on the VXLAN interface of the VTEP device; After receiving the target traffic, the local VTEP device performs a route lookup on the destination address corresponding to the target traffic; When the destination address matches a directly connected route to the gateway but no corresponding address resolution information is obtained, a probe route is generated; Send the probe route to the peer VTEP device; Receive EVPN Category 2 routes sent by the peer VTEP device; The target traffic is forwarded according to the EVPN Category 2 route to achieve interconnection under VXLAN EVPN symmetrical networking.

2. The method as described in claim 1, characterized in that, When the destination address matches a directly connected route to the gateway but no corresponding address resolution information is obtained, a probe route is generated, including: When the destination address matches a gateway-directed route and the corresponding ARP or ND entry is in an incomplete state, perform an ARP probe or ND probe on the destination address. If the probe fails and the VXLAN interface is configured with the common Layer 3 VNI, the probe route is generated based on the destination address.

3. The method as described in claim 2, characterized in that, Also includes: Deduplication is performed on probe routes that have the same common Layer 3 VNI, the same Layer 2 VNI, and the same address information.

4. The method as described in claim 1, characterized in that, Sending the probe route to the peer VTEP device includes: The probe route is sent to the peer VTEP device via the Border Gateway Protocol (BGP).

5. The method as described in claim 1, characterized in that, After sending the probe route to the peer VTEP device, the method further includes: The peer VTEP device determines the target VXLAN interface based on the common Layer 3 VNI and address information carried by the probe route; Perform ARP or ND probes on the target VXLAN interface.

6. The method as described in claim 5, characterized in that, The peer VTEP device determines the target VXLAN interface based on the common Layer 3 VNI and address information carried in the probe route, including: After passing the BGP filtering policy, search for the VXLAN interface that is the same as the public Layer 3 VNI carried by the probe route in the VRFs that meet the filtering conditions. Determine whether the target address carried by the probe route matches the network segment to which the VXLAN interface belongs; Upon successful matching, the VXLAN interface is identified as the target VXLAN interface.

7. The method as described in claim 5, characterized in that, Also includes: After the peer VTEP device detects the corresponding ARP or ND entry, it generates an EVPN Class II route.

8. The method as described in claim 1, characterized in that, After receiving the EVPN Category 2 route sent by the peer VTEP device, the system further includes: Stop ARP or ND probing based on the destination address; Update the corresponding ARP or ND entry to the NONE state; When the preset conditions are met, the corresponding probe route is cancelled, and a route cancellation message is sent to the peer VTEP device via BGP.

9. The method as described in claim 1, characterized in that, According to the EVPN Category 2 route, the target traffic is forwarded, including: A detailed route to the remote access host is established based on the EVPN Category 2 route; The target traffic is forwarded based on the detailed routing.

10. An interconnection device for VXLAN EVPN symmetrical networking, which can be used in VTEP devices in VXLAN EVPN symmetrical networking, characterized in that, include: The configuration module is used to configure the common Layer 3 Virtual Network Identity (VNI) on the VXLAN interface of the VTEP device; The query module is used to perform a route query on the destination address corresponding to the target traffic after the local VTEP device receives the target traffic; The information module is used to generate a probe route when the destination address matches a gateway-directly connected route but no corresponding address resolution information is obtained; The sending module is used to send the probe route to the peer VTEP device; The receiving module is used to receive EVPN Category 2 routes sent by the peer VTEP device; The forwarding module is used to forward the target traffic according to the EVPN Category II route to achieve interconnection under VXLAN EVPN symmetrical networking.

Images