CN108777663B

CN108777663B - Method and device for synchronizing routing information

Info

Publication number: CN108777663B
Application number: CN201810549937.2A
Authority: CN
Inventors: 黄李伟; 王伟
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2018-05-31
Filing date: 2018-05-31
Publication date: 2021-02-09
Anticipated expiration: 2038-05-31
Also published as: CN108777663A

Abstract

The method is applied to a target VTEP and comprises the steps of generating first EVPN routing information carrying a first local forwarding table item and migration identification information aiming at a Virtual Machine (VM) when the VM of the migrated virtual machine is sensed; the first local forwarding table entry is a forwarding table entry of which an output interface established by the target VTEP aiming at the VM is an AC interface of an access circuit connected with the VM; and sending the first EVPN routing information to other VTEPs, so that the other VTEPs directly update the stored forwarding table entry aiming at the VM according to the first local forwarding table entry after detecting the migration identification information. The method and the device for processing the virtual machine migration failure have the advantages that the number value of migration and the number values before and after the migration are not required to be recorded, and the problem of migration failure caused by the fact that other VTEPs need to compare the number values before and after the migration when the virtual machine migrates too frequently in the prior art is solved.

Description

Method and device for synchronizing routing information

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for synchronizing routing information.

Background

As shown in fig. 1, in the data center technology, after a first Virtual Machine (Virtual Machine, VM1) is online for the first time at a source eXtensible Virtual local area Network (VXLAN) Tunnel endpoint (VXLAN Tunnel End Point, VTEP) (i.e., VTEP1 in fig. 1), the source VTEP synchronizes forwarding entries learned in the source VTEP by VM1 to other VTEPs (i.e., VTEP2 in fig. 1) based on MP-BGP (backward compatibility) through an Ethernet Virtual Private Network (Ethernet Virtual Private Network, EVPN), so that a second VM (i.e., VM2 in fig. 1) suspended under other VTEPs can access VM1 based on the synchronized forwarding entries.

As shown in fig. 2, after VM1 migrates from VTEP1 to VTEP3, VTEP3 synchronizes EVPN routing information carrying the attribute value of the migration expansion community corresponding to VM1 to VTEP1 and VTEP 2; wherein, the migration extended group attribute value is number value, VM1 migrates 1 time each time, VTEP maintains number plus 1. After receiving the EVPN routing information, VTEP1 and VTEP2 compare the number value in the EVPN routing information with the number value maintained by themselves, and perform forwarding table item switching operation of VM1 migration when the number value in the EVPN routing information is greater than the maintained number value.

However, when a VM repeatedly migrates among multiple VTEPs, if network congestion occurs among the VTEPs, the number value of the migration may not be well synchronized and recorded, so that after the VM1 migrates, the number value issued by the target VTEP where the VM1 is currently located is smaller than the number value currently recorded by the source VTEP and the synchronized VTEP (for short, other VTEPs), and the migration function may fail.

Disclosure of Invention

In view of this, an object of the embodiment of the present application is to provide a method and an apparatus for synchronizing routing information, where after detecting migration identification information, other VTEPs directly update a stored forwarding table entry for a migration VM according to a first local forwarding table entry, so as to solve a problem of migration failure caused by the fact that other VTEPs need to compare number values before and after migration when a virtual machine migrates too frequently.

In a first aspect, an embodiment of the present application provides a method for synchronizing routing information, where the method is applied to a target extensible virtual local area network VXLAN tunnel endpoint VTEP, and the method includes:

when a migrated virtual machine VM is sensed, generating first Ethernet virtual private network EVPN routing information carrying a first local forwarding table item and migration identification information aiming at the VM; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by a target VTEP for the VM is an AC interface of an access circuit connected with the VM;

and sending first EVPN routing information to other VTEPs, so that the other VTEPs update the stored forwarding table entry aiming at the VM according to the first local forwarding table entry after detecting the migration identification information.

In a second aspect, an embodiment of the present application further provides a method for synchronizing routing information, where the method is applied to other scalable virtual local area network VXLAN tunnel endpoint VTEP, and the method includes:

receiving Ethernet virtual private network EVPN routing information which is sent by a target VTEP and carries a first local forwarding table item and migration identification information of a migrated virtual machine VM; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by the target VTEP for the accessed VM is an AC interface of an access circuit connected with the VM;

and after detecting migration identification information in the EVPN routing information, updating the stored forwarding table entry aiming at the VM according to the first local forwarding table entry.

In a third aspect, an embodiment of the present application provides a device for synchronizing routing information, including:

the generation module is used for generating first Ethernet virtual private network EVPN routing information carrying a first local forwarding table item and migration identification information aiming at the VM when the migrated virtual machine VM is sensed; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by a target VTEP for the VM is an AC interface of an access circuit connected with the VM;

and a first sending module, configured to send first EVPN routing information to other VTEPs, so that after the other VTEPs detect the migration identification information, the forwarding table entry for the VM that is stored is updated according to the first local forwarding table entry.

In a fourth aspect, an embodiment of the present application provides a device for synchronizing routing information, including:

the receiving module is used for receiving Ethernet virtual private network EVPN routing information which is sent by the target VTEP and carries the first local forwarding table item and the migration identification information of the migrated virtual machine VM; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by the target VTEP for the accessed VM is an AC interface of an access circuit connected with the VM;

and the updating module is used for updating the stored forwarding table entry aiming at the VM according to the first local forwarding table entry after detecting the migration identification information in the EVPN routing information.

According to the method and device for synchronizing the routing information, when the target VTEP senses the migrated virtual machine VM, EVPN routing information carrying a first local forwarding table entry and migration identification information for the VM is generated to other VTEPs, and after the other VTEPs receive the EVPN routing information, if the migration identification information is detected, the stored forwarding table entry for the VM is directly updated according to the first local forwarding table entry. In the embodiment of the application, in the process of VM migration, a number value corresponding to the migration does not need to be recorded, and the number values before and after the migration do not need to be compared, and other VTEPs can update the locally stored forwarding table entry for the migrating VM as long as the first EVPN routing information from the target VTEP is detected to have the migration identification information, so that the problem of migration failure caused by the fact that other VTEPs need to compare the number values before and after the migration when the virtual machine migrates too frequently in the prior art is solved.

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 illustrates an application scenario diagram of a data center architecture in the prior art provided by an embodiment of the present application.

Fig. 2 is a schematic diagram illustrating an application scenario of another prior art data center architecture provided in an embodiment of the present application.

Fig. 3 shows an application scenario diagram of a data center architecture provided in an embodiment of the present application.

Fig. 4 is a flowchart illustrating a method for synchronizing routing information according to an embodiment of the present application.

Fig. 5 is a flowchart illustrating another method for synchronizing routing information according to an embodiment of the present application.

Fig. 6 is a flowchart illustrating another method for synchronizing routing information according to an embodiment of the present application.

Fig. 7 is a flowchart illustrating another method for synchronizing routing information according to an embodiment of the present application.

Fig. 8 is a schematic structural diagram illustrating another routing information synchronization apparatus provided in an embodiment of the present application.

Fig. 9 is a schematic structural diagram illustrating another routing information synchronization apparatus provided in an embodiment of the present application.

Fig. 10 shows a schematic structural diagram of a computer device 40 provided in an embodiment of the present application.

Fig. 11 shows a schematic structural diagram of a computer device 50 provided in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.

Fig. 3 shows an overall architecture diagram of a data center provided in an embodiment of the present application. As shown in fig. 3, a source eXtensible Virtual local area network (VXLAN) Tunnel endpoint (VXLAN Tunnel End Point, VTEP) (i.e., VTEP1 in fig. 3, corresponding to an IP address of 1.1.1.1), a destination VTEP (i.e., VTEP3 in fig. 3, corresponding to an IP address of 3.3.3.3) and a synchronous VTEP (i.e., VTEP2 in fig. 3, corresponding to an IP address of 2.2.2.2) are included. Wherein, the source VTEP refers to a VTEP accessed by a virtual machine which is subjected to migration (in the embodiment of the present application, the VTEP is referred to as a migration), and the target VTEP refers to a VTEP accessed by a virtual machine which is subjected to migration after the migration; a synchronized VTEP refers to a designated VTEP in the data center other than the source VTEP and the target VTEP, and thus the designated VTEP may be all VTEPs other than the source VTEP and the target VTEP, or may be a part of VTEPs other than the source VTEP and the target VTEP. A first Virtual Machine (VM 1) first comes online in VTEP1, and VTEP1 locally learns the forwarding entries of online VMs 1 (here, learning the forwarding entries is to construct the forwarding entries of corresponding VMs 1 by looking up the routing table). In this embodiment of the application, the learned forwarding table entry includes address information and egress interface information of the VM1, where the address information is an Internet Protocol (IP) or/physical address (MAC) address (in this embodiment, the address information is an IP address for example) of an interconnection between networks of the VM1, and the egress interface information is an AC1 interface of the VM1 connected to the VTEP 1.

After learning the forwarding table entry of VM1, VTEP1 synchronously carries second EVPN routing information of the forwarding table entry to VTEP2 and VTEP3 (where the second EVPN routing information is different from first EVPN routing information synchronized by VTEP3 after VM1 later migrates to below VTEP 3), VTEP2 and VTEP3 establish VXLAN tunnel 1 to VTEP1 above VTEP2 and VXLAN tunnel 3 to VTEP1 above VTEP3 after receiving the second EVPN routing information, and generate a second synchronous forwarding table entry for VM 1; the second synchronous forwarding table entries generated by VTEP2 and VTEP3 are different and are a second other forwarding table entry and a second target synchronous forwarding table entry respectively, where address information in the second other forwarding table entry is an IP/MAC address of VM1, VXLAN tunnel 1 from the output interface VTEP2 to VTEP1, address information in the second target synchronous forwarding table entry is an IP/MAC address of VM1, and VXLAN tunnel 3 from the output interface VTEP3 to VTEP 1.

When VTEP1 fails, it can be migrated to VTEP2 or VTEP3 to ensure that VM1 can operate normally. When VTEP1 recovers, it can migrate from VTEP2 or VTEP3 back into VTEP 1. Thus, VM1 may migrate repeatedly between VTEP1, VTEP2 and VTEP 3. If VM1 migrates from below VTEP1 to below VTEP3, VTEP3 needs to synchronize the route information of the second Ethernet Virtual Private Network (EVPN) to VTEP1 and VTEP2, where the route information of the first EVPN carries the first local forwarding table entry and migration identification information for VM1 (i.e., migration VM). After detecting the migration identification information, VTEP1 and VTEP2 directly update the stored forwarding table entry for VM1 according to the first local forwarding table entry, which solves the problem of migration failure caused by the need of comparing number values before and after migration by other VTEPs when the virtual machine migrates too frequently. The following describes a method for synchronizing routing information provided in the embodiments of the present application through embodiments.

As shown in fig. 4, a method for synchronizing routing information provided in a first embodiment of the present application is applied to a target eXtensible Virtual local area network (VXLAN) Tunnel endpoint (VXLAN Tunnel End Point, VTEP), and the method includes:

s101, when a migrated virtual machine VM is sensed, generating first Ethernet virtual private network EVPN routing information carrying a first local forwarding table item and migration identification information aiming at the VM; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by the target VTEP for the VM is an AC interface of an access circuit connected with the VM.

In the embodiment of the application, after receiving the online request information sent by the VM, the target VTEP verifies whether the identity information of the VM carried in the online request information is correct, and if the identity information is verified, the VM is marked as an online state, and meanwhile, a first local forwarding table entry of the VM is locally learned. In addition, the target VTEP also detects whether a second target synchronous forwarding table entry of the VM exists locally when the verification of the identity information passes, if so, the VM is determined to be a migrated VM, and if not, the VM is determined to be a newly accessed VM.

And whether the online VM is the migration VM or not influences whether the generated first EVPN routing information carries migration identification information aiming at the VM or not. When the VM is a migration VM, the generated first EVPN routing information carries a first local forwarding table item and migration identification information aiming at the VM; and when the VM is a newly accessed VM, the generated first EVPN routing information only carries a first local forwarding table item aiming at the VM, and does not carry migration identification information. Here, the second target synchronous forwarding table entry is generated by the target VTEP based on the second EVPN routing information synchronized by the source VTEP accessed by the VM before migration.

As shown in fig. 3, taking the migration VM as VM1, the target VTEP as VTEP3, the source VTEP as VTEP1, and the synchronous VTEP as VTEP2 as examples, the address information in the first local forwarding table entry carried by the first EVPN routing information generated by VTEP3 (here, to distinguish the second EVPN routing information synchronized by VTEP1 before VM1 migrates to VTEP 3) is the IP/MAC address of VM1, and the outgoing interface is VTEP3 connected to the AC2 interface of VM 1.

In the embodiment of the application, the migration identification information carried in the first EVPN routing information is a migration extension group tag, and the migration extension group tag is carried in a reserved field of a message where the first EVPN routing information is located, where the reserved field is a type field and a sub-type field. As an optional implementation manner, the Type is defined as 0x07 in the embodiment of the present application, and the Sub-Type is 0x00, that is, the migration Type is represented; the MAC MOVE flag identifies that the EVPN routing information is a virtual machine migration route.

The migration identification information is used for indicating that when the VTEP1 and the VTEP2 in the data center detect the migration identification information, the forwarding table entries for the VMs, which are stored in the data center, are directly updated according to the first local forwarding table entry.

S102, sending first EVPN routing information to other VTEPs, so that the other VTEPs update the stored forwarding table entry aiming at the VM according to the first local forwarding table entry after detecting the migration identification information.

In the embodiment of the application, the VTEP3 synchronizes the first EVPN routing information carrying the first local forwarding entry and the migration identification information to the VTEP1 and the VTEP 2.

After receiving the first EVPN routing information, VTEP1 and VTEP2 directly update a forwarding table entry locally stored for the VM1 according to a first local forwarding table entry in the first EVPN routing information if migration identification information is detected. The migration identification information here is different from the number value in the prior art, after detecting the number value, VTEP1 and VTEP2 need to determine whether the number value is greater than the number value currently maintained by each, and only when the number value is greater than the number value currently maintained by each, the number value stored in each forwarding table entry for VM1 is updated, but in the present application, VTEP1 and VTEP2 can directly update the forwarding table entry stored in each forwarding table entry for VM1 according to the first local forwarding table entry as long as the migration identification information is detected, and determination of the number value is not needed, so that the problem of migration failure caused by comparison of the number values before and after migration by other VTEPs when a virtual machine migrates too frequently in the prior art is solved.

Here, the method for updating the stored forwarding table entry for the migration VM by the source VTEP and the synchronous VTEP according to the first local forwarding table entry is as follows:

and the source VTEP generates a first source synchronous forwarding table item aiming at the VM according to the address information in the first local forwarding table item and the pre-established tunnel information from the source VTEP to the target VTEP. And the synchronous VTEP generates a first other synchronous forwarding table entry aiming at the VM according to the address information in the first local forwarding table entry and the pre-established tunnel information from the synchronous VTEP to the target VTEP.

As shown in fig. 3, taking the migration VM as VM1, the target VTEP as VTEP3, the source VTEP as VTEP1, and the synchronous VTEP as VTEP2 as examples, here, the first synchronous forwarding entries corresponding to VTEP1 and VTEP2 are different and are the first source synchronous forwarding entry and the first other synchronous forwarding entries respectively. VTEP1 and VTEP2 establish VXLAN tunnel 2 to VTEP3 over VTEP2 and VXLAN tunnel 4 to VTEP3 over VTEP1 after receiving the first EVPN routing information. Correspondingly, in the first source synchronous forwarding table entry for VM1 generated by VTEP 1: the address information is the IP address/MAC address of VM1, and the egress interface information is VXLAN tunnel 4 from VTEP1 to VTEP 3. In the first other synchronous forwarding table entry for the VM1 generated by the VTEP2, the address information is the IP address/MAC address of the VM1, and the outgoing interface information is the VXLAN tunnel 2 from the VTEP2 to the VTEP 3.

In consideration of the situation of attack messages, online request information received by a target VTEP may be a forged message sent by a counterfeiter through forging an IP address/MAC address of a VM, and in practice, the VM is not migrated to the target VTEP but is still suspended in a source VTEP, and for such situation, the solution adopted by the method for synchronizing routing information provided in the embodiment of the present application is as follows:

the other VTEP comprises a source VTEP and a synchronous VTEP; after updating a forwarding table entry aiming at the VM, which is stored by a source VTEP on the basis of the received first EVPN routing information, the source VTEP sends feedback information to the target VTEP; the feedback information carries a detection result of whether the VM is locally accessed. As shown in fig. 5, correspondingly, after sending the first EVPN routing information to the source VTEP, the target VTEP further includes:

s201, if the accessed VM exists in the source VTEP is determined according to feedback information returned by the source VTEP, whether the VM is accessed locally is detected; wherein the feedback information carries a detection result of whether the VM is accessed in the source VTEP.

In the embodiment of the application, if the target VTEP receives the feedback information returned by the source VTEP, the detection result in the feedback information is extracted, and if the detection result is that the VM which is accessed exists in the source VTEP, the target VTEP detects whether the VM is locally accessed. The specific detection method is that the target VTEP sends a detection message to the VM based on the IP/MAC address of the VM, judges whether a response message returned by the VM is received, if the response message returned by the VM is received, the accessed VM is confirmed, and if the response message returned by the VM is not received, the non-accessed VM is confirmed (in this case, the received online request information is considered to be an attack message).

S202, if detecting that the VM is not accessed locally, deleting the first local forwarding table entry, and informing the other VTEPs to delete the first synchronous forwarding table entry aiming at the VM; wherein the first synchronous forwarding table entry is generated by the other VTEPs based on the EVPN routing information.

In the embodiment of the application, after the target VTEP sends the probe message to the VM, if the response reply message returned by the VM is not received, it is determined that the VM is not locally accessed, and the received online request information is regarded as an attack message. Correspondingly, the target VTEP deletes the first local forwarding table entry for the VM, and simultaneously, notifies the source VTEP and the synchronous VTEP to delete the first synchronous forwarding table entry for the migrated VM.

Here, the target VTEP notifies the source VTEP and the synchronous VTEP to delete the first synchronous forwarding table entry for the migration VM by sending second synchronous route deletion information for the migration VM to the source VTEP and the synchronous VTEP (the synchronous route deletion information is to be distinguished from the first synchronous route deletion information sent by the source VTEP). And if the source VTEP receives second route deletion information from the target VTEP, deleting the first source synchronous forwarding table item. And the synchronous VTEP generates a first synchronous forwarding table entry as a first other synchronous forwarding table entry based on the first EVPN routing information, and deletes the first other synchronous forwarding table entry if receiving second route deletion information from the target VTEP.

Further, in the method for synchronizing routing information provided in this embodiment of the present application, a second target synchronous forwarding entry for the VM is stored in the target VTEP (that is, the second target synchronous forwarding entry, address information in the second target synchronous forwarding entry is an IP/MAC address of the VM1, and an outgoing interface is VXLAN tunnel 3 from VTEP3 to VTEP1), where the second synchronous forwarding entry is generated by VTEP3 based on second EVPN routing information synchronized with VTEP1 accessing the VM 1; the method further comprises the following steps:

and when the VM is determined not to be accessed in the source VTEP according to the feedback information returned by the source VTEP, if first synchronous route deletion information aiming at the VM sent by the source VTEP is received, deleting the stored second target synchronous forwarding table entry aiming at the VM according to the first synchronous route deletion information.

In this embodiment of the present application, if it is detected that the VM1 corresponding to the address information in the first local forwarding table entry is not accessed locally, the VTEP1 sends first synchronous route deletion information to the VTEP3 and VTEP2, and notifies the VTEP3 and VTEP2 to delete the second target synchronous forwarding table entry and the second other forwarding table entry, which are stored for the VM 1.

Correspondingly, after receiving the feedback information carrying the detection result returned by the VTEP1, the VTEP3 extracts the detection result in the feedback information, and if the detection result is judged that there is no accessed immigration VM1 in the VTEP1, deletes the stored second target synchronous forwarding table entry of the immigration VM1 after receiving the first synchronous route deletion information.

As shown in fig. 6, a method for synchronizing routing information provided in a second embodiment of the present application is applied to other VTEPs, and the method includes:

s301, receiving Ethernet virtual private network EVPN routing information which is sent by a target VTEP and carries a first local forwarding table item and migration identification information of a migrated virtual machine VM; the first local forwarding table entry is a forwarding table entry that an outgoing interface established by the target VTEP for the accessed VM is an AC interface of an access circuit connected to the VM.

As shown in fig. 3, the migration VM is VM1, the target VTEP is VTEP3, the source VTEP is VTEP1, and the synchronous VTEP is VTEP 2. The address information in the first local forwarding table entry carried by the first EVPN routing information generated by the VTEP3 is an IP/MAC address of the immigration VM1, and the outgoing interface is an AC2 interface where the VTEP3 is connected to the immigration VM 1.

The migration identification information carried in the first EVPN routing information is a migration extension group tag, and the migration extension group tag is carried in a reserved field of the first EVPN routing information (i.e. a message), where the reserved field is a type field and a sub-type field. As an optional implementation manner, the Type is defined as 0x07 in the embodiment of the present application, and the Sub-Type is 0x00, that is, the migration Type is represented; the MAC MOVE flag identifies that the EVPN routing information is a virtual machine migration route.

The migration identification information is used for indicating that when the VTEP1 and VTEP2 in the data center detect the migration identification information, the forwarding table entries for the VMs 1, which are stored in the data center, are directly updated according to the first local forwarding table entry.

S302, after detecting migration identification information in the EVPN routing information, updating the stored forwarding table entry aiming at the VM according to the first local forwarding table entry.

Here, the method for updating the stored forwarding table entry for the VM by the source VTEP and the synchronous VTEP according to the first local forwarding table entry is as follows:

and the source VTEP generates a first source synchronous forwarding table item aiming at the VM according to the address information of the VM in the first local forwarding table item and the pre-established tunnel information from the source VTEP to the target VTEP. And the synchronous VTEP generates a first other synchronous forwarding table item aiming at the VM according to the address information of the VM in the first local forwarding table item and the pre-established tunnel information from the synchronous VTEP to the target VTEP.

As shown in fig. 3, the first synchronous forwarding entries corresponding to the source VTEP (VTEP1) and the synchronous VTEP (VTEP2) are different and are the first source synchronous forwarding entry and the first other synchronous forwarding entry, respectively. VTEP1 and VTEP2 establish VXLAN tunnel 2 to VTEP3 over VTEP2 and VXLAN tunnel 4 to VTEP3 over VTEP1 after receiving the first EVPN routing information. Correspondingly, in the first source synchronous forwarding table entry for VM1 generated by VTEP 1: the address information is the IP address/MAC address of VM1, and the egress interface information is VXLAN tunnel 4 from VTEP1 to VTEP 3. In the first other synchronous forwarding table entry for the VM1 generated by the VTEP2, the address information is the IP address/MAC address of the VM1, and the outgoing interface information is the VXLAN tunnel 2 from the VTEP2 to the VTEP 3.

Further, in the method for synchronizing routing information provided in the embodiment of the present application, the other VTEPs include a source VTEP, and after the source VTEP updates a stored forwarding entry for the VM according to the first local forwarding entry, the method further includes:

the source VTEP sends feedback information to the target VTEP; the feedback information carries a detection result of whether the source VTEP accesses the VM corresponding to the first local forwarding entry.

In the embodiment of the application, after updating the forwarding table entry for the VM1, which is stored by the VTEP1, based on the received first EVPN routing information, the VTEP1 sends feedback information to the target VTEP 3; the feedback information carries a detection result of whether the VM1 is locally accessed.

Further, in the method for synchronizing routing information provided in the embodiment of the present application, the other VTEPs further include a synchronized VTEP; after the source VTEP updates the stored forwarding table entry for the VM according to the first local forwarding table entry, the method further includes:

if the source VTEP detects that the VM is not accessed locally, deleting a stored second local forwarding table entry aiming at the VM, and sending second synchronous route deletion information aiming at the VM to the target VTEP and the synchronous VTEP so as to enable the target VTEP and the synchronous VTEP to delete a second target synchronous forwarding table entry and a second other synchronous forwarding table entry aiming at the VM, which are stored respectively; the second local forwarding table entry is a forwarding table entry of which an outgoing interface established when the source VTEP accesses the VM is an AC interface connected to the VM.

In the embodiment of the present application, as shown in fig. 3, after receiving the first EVPN routing information, the VTEP1 (i.e., the source VTEP) establishes the VXLAN tunnel 4 to the VTEP3 on the VTEP1, generates the first source synchronous forwarding table entry whose address information is the IP/MAC address of the VM1, and the egress interface VTEP1 sends the first source synchronous forwarding table entry to the VXLAN tunnel 4 of the VTEP 3.

Afterwards, if VTEP1 detects that VM1 is not accessed locally, the stored first source synchronous forwarding table entry is deleted, and at the same time, first synchronous route deletion information is sent to VTEP3 and VTEP2, which notifies VTEP3 and VTEP2 to delete the second target synchronous forwarding table entry and the second other forwarding table entry, which are stored for VM 1.

In the embodiment of the application, a second other forwarding table entry and a second target synchronous forwarding table entry are generated by VTEP2 and VTEP3 based on second EVPN routing information synchronized by VTEP1, where in the second other forwarding table entry, the address information is an IP/MAC address of a VM1, and an egress interface VTEP2 goes to a VXLAN tunnel 1 of VTEP 1; in the second target synchronous forwarding table entry, the address information is the IP/MAC address of the VM1, and the VXLAN tunnel 3 from the egress interface VTEP3 to VTEP 1.

Further, in the method for synchronizing routing information provided in this embodiment of the present application, after the source VTEP updates the stored forwarding entry for the VM according to the first local forwarding entry, the method further includes:

and after detecting that the source VTEP is locally accessed to the VM, if second synchronous route deleting information sent by the target VTEP is received, deleting the first source synchronous forwarding table entry.

In the embodiment of the present application, when the VTEP3 confirms that the VM1 is not locally accessed, the received online request information is regarded as an attack packet. Correspondingly, VTEP3 deletes the first EVPN routing information for VM1, and issues second synchronous routing deletion information to VTEP1 and VTEP2 to notify VTEP1 and VTEP2 to delete the first source synchronous forwarding table entry and the first other synchronous forwarding table entry for VM1, which are stored in the first source synchronous forwarding table entry and the first other synchronous forwarding table entry. Here, after receiving the second synchronous route deletion information, VTEP1 deletes the generated first source synchronous forwarding table entry.

Further, in the method for synchronizing routing information provided in this embodiment of the present application, after the synchronizing VTEP updates the stored forwarding entry for the VM according to the first local forwarding entry, the method further includes:

if the synchronous VTEP receives second synchronous route deleting information sent by the target VTEP, deleting the first other synchronous forwarding table items aiming at the VM according to the second synchronous route deleting information;

alternatively, the first and second electrodes may be,

if the synchronous VTEP receives first synchronous route deletion information sent by the source VTEP, deleting stored second other synchronous forwarding table items aiming at the VM according to the first synchronous route deletion information; and the second other synchronous forwarding table entry is generated by the synchronous VTEP based on second EVPN routing information synchronized by the source VTEP accessed to the VM.

As shown in fig. 3, when receiving the first synchronization route deletion information sent by the source VTEP, the VTEP2 (i.e., the synchronized VTEP) deletes the stored second other forwarding entry for the VM1, where the address information in the second other forwarding entry is the IP/MAC address of the VM1, and the VTEP2 is an VXLAN tunnel 1 from the egress interface VTEP2 to the VTEP 1.

Further, as shown in fig. 7, in the method for synchronizing routing information provided in this embodiment of the present application, after the synchronizing VTEP updates the stored forwarding entry for the VM according to the first local forwarding entry, the method further includes:

s401, after receiving a data message with a destination address of the VM, if detecting that a plurality of synchronous forwarding table entries aiming at the VM exist at the same time, determining priorities of the plurality of synchronous forwarding table entries according to the sequence of generation time of the synchronous forwarding table entries; wherein the higher the generation time, the higher the priority.

In this embodiment of the application, if the VTEP2 receives a data packet sent by the VM2 that is suspended below the VTEP2, the destination address of the data packet is extracted, and if it is determined that the destination address of the data packet is the VM1 that is originally suspended in the VTEP1 but is currently suspended in the VTEP3, the data packet needs to be forwarded according to the generated synchronous forwarding table entry for the VM 1.

Here, if two synchronous forwarding entries for the VM1, such as the first other synchronous forwarding entry and the second other synchronous forwarding entry, exist in the VTEP2 at the same time, the VTEP2 determines the priorities of the two synchronous forwarding entries according to the generation times of the two synchronous forwarding entries.

In this embodiment of the present application, the generation time of the first other synchronous forwarding table entry is later, so that the priority of the first other synchronous forwarding table entry is higher than the priority of the second other synchronous forwarding table entry.

S402, forwarding the data message based on the synchronous forwarding table entry with the highest priority.

In this embodiment of the application, after determining that the synchronous forwarding entry with the highest priority is the first other synchronous forwarding entry, the VTEP2 forwards the data packet based on the first other synchronous forwarding entry.

According to the method for synchronizing the routing information, when the target VTEP senses the migrated virtual machine VM, EVPN routing information carrying a first local forwarding table entry and migration identification information for the VM is generated to other VTEPs, and after the other VTEPs receive the EVPN routing information, if the migration identification information is detected, the stored forwarding table entry for the VM is directly updated according to the first local forwarding table entry. In the embodiment of the application, in the process of VM migration, a number value corresponding to the migration does not need to be recorded, and the number values before and after the migration do not need to be compared, and other VTEPs can update the locally stored forwarding table entry for the migrating VM as long as the first EVPN routing information from the target VTEP is detected to have the migration identification information, so that the problem of migration failure caused by the fact that other VTEPs need to compare the number values before and after the migration when the virtual machine migrates too frequently in the prior art is solved.

As shown in fig. 8, a routing information synchronization apparatus provided in a third embodiment of the present application is configured to execute a routing information synchronization method in the second embodiment of the present application, where the apparatus includes:

the generation module 11 is configured to generate, when the migrated virtual machine VM is sensed, first ethernet virtual private network EVPN routing information carrying a first local forwarding table entry and migration identification information for the VM; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by a target VTEP for the VM is an AC interface of an access circuit connected with the VM;

a first sending module 12, configured to send first EVPN routing information to other VTEPs, so that after the other VTEPs detect the migration identification information, the forwarding table entry for the VM that is stored is updated according to the first local forwarding table entry.

Further, in the synchronization apparatus for routing information provided in the embodiment of the present application, the other VTEPs include a source VTEP; the device further comprises:

the detection module is used for detecting whether the VM is accessed locally or not when the VM accessed in the source VTEP is determined to exist in the source VTEP according to feedback information returned by the source VTEP; wherein the feedback information carries a detection result of whether the source VTEP is accessed to the VM;

a first deleting module, configured to delete the first local forwarding entry when detecting that the VM is not locally accessed, and notify the other VTEPs to delete the first synchronous forwarding entry for the VM; wherein the first synchronous forwarding table entry is generated by the other VTEPs based on the EVPN routing information.

Further, in the synchronization apparatus for routing information provided in this embodiment of the present application, a second target synchronous forwarding entry for the VM is stored in the target VTEP, and the second target synchronous forwarding entry is generated based on second EVPN routing information synchronized by the source VTEP accessing the VM; the first deletion module is further configured to:

As shown in fig. 9, a routing information synchronization apparatus according to a fourth embodiment of the present application is configured to execute a routing information synchronization method according to a second embodiment of the present application, where the apparatus includes:

a receiving module 21, configured to receive ethernet virtual private network EVPN routing information that is sent by the target VTEP and carries the first local forwarding table entry and the migration identification information of the migrated virtual machine VM; the first local forwarding table entry is a forwarding table entry of which an outgoing interface established by the target VTEP for the accessed VM is an AC interface of an access circuit connected with the VM;

an updating module 22, configured to update a stored forwarding entry for the VM according to the first local forwarding entry after detecting migration identification information in the EVPN routing information.

Further, in the synchronization apparatus for routing information provided in the embodiment of the present application, the apparatus further includes:

a second sending module, configured to send feedback information to the target VTEP; the feedback information carries a detection result of whether the source VTEP accesses the VM corresponding to the first local forwarding entry.

a second deleting module, configured to delete a stored second local forwarding entry for the VM when detecting that the VM is not locally accessed, and send second synchronous route deletion information for the VM to the target VTEP and the synchronous VTEP, so that the target VTEP and the synchronous VTEP delete a second target synchronous forwarding entry and a second other synchronous forwarding entry for the VM, which are stored in the target VTEP and the synchronous VTEP respectively; the second local forwarding table entry is a forwarding table entry of which an outgoing interface established when the source VTEP accesses the VM is an AC interface connected to the VM.

Further, in the synchronization apparatus for routing information provided in this embodiment of the present application, the first local forwarding table entry includes address information of the VM, and the update module is specifically configured to:

generating a first source synchronous forwarding table item aiming at the VM according to the address information of the VM in the first local forwarding table item and pre-established tunnel information from the source VTEP to the target VTEP;

the second deleting module is further configured to delete the first source synchronous forwarding table entry if second synchronous route deleting information sent by the target VTEP is received after the local access to the VM is detected.

generating a first other synchronous forwarding table entry aiming at the VM according to the address information of the VM in the first local forwarding table entry and the pre-established tunnel information from the synchronous VTEP to the target VTEP;

the second deleting module is further configured to, when second synchronous route deleting information sent by the target VTEP is received, delete the first other synchronous forwarding table entry for the VM according to the second synchronous route deleting information;

alternatively, the first and second electrodes may be,

the second deleting module is further configured to delete a stored second other synchronous forwarding table entry for the VM according to the first synchronous route deleting information when receiving the first synchronous route deleting information sent by the source VTEP; and the second other synchronous forwarding table entry is generated by the synchronous VTEP based on second EVPN routing information synchronized by the source VTEP accessed to the VM.

Further, the synchronization apparatus for routing information provided in the embodiment of the present application further includes:

a determining module, configured to determine priorities of multiple synchronous forwarding entries according to a sequence of generation times of the synchronous forwarding entries if it is detected that multiple synchronous forwarding entries for the VM exist at the same time after receiving a data packet whose destination address is the VM; wherein the later the generation time, the higher the priority;

and the forwarding module is used for forwarding the data message based on the synchronous forwarding table entry with the highest priority.

According to the routing information synchronization device provided by the embodiment of the application, when the target VTEP senses the migrated virtual machine VM, EVPN routing information carrying a first local forwarding table entry and migration identification information for the VM is generated to other VTEPs, and after the other VTEPs receive the EVPN routing information, if the migration identification information is detected, the stored forwarding table entry for the VM is directly updated according to the first local forwarding table entry. In the embodiment of the application, in the process of VM migration, a number value corresponding to the migration does not need to be recorded, and the number values before and after the migration do not need to be compared, and other VTEPs can update the locally stored forwarding table entry for the migrating VM as long as the first EVPN routing information from the target VTEP is detected to have the migration identification information, so that the problem of migration failure caused by the fact that other VTEPs need to compare the number values before and after the migration when the virtual machine migrates too frequently in the prior art is solved.

Fig. 10 is a schematic structural diagram of a computer device 40 according to an embodiment of the present application, and as shown in fig. 10, the computer device is configured to execute a synchronization method of routing information in fig. 4, where the device includes a memory 401, a processor 402, and a computer program stored in the memory 401 and executable on the processor 402, where the processor 402 implements the steps of the synchronization method of routing information when executing the computer program.

Specifically, the memory 401 and the processor 402 can be general-purpose memory and processor, and are not limited to specific examples, and the processor 402 can execute the above-mentioned routing information synchronization method when executing the computer program stored in the memory 401.

Corresponding to the method for synchronizing routing information in fig. 4, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the method for synchronizing routing information.

Specifically, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, and when the computer program on the storage medium is executed, the synchronization method of the routing information can be executed.

Fig. 11 is a schematic structural diagram of a computer device 50 according to another embodiment of the present application, and as shown in fig. 11, the computer device is configured to execute a synchronization method of routing information in fig. 6, where the device includes a memory 501, a processor 402, and a computer program stored in the memory 501 and executable on the processor 502, where the processor 502 implements the steps of the synchronization method of routing information when executing the computer program.

Specifically, the memory 501 and the processor 502 can be general-purpose memory and processor, and are not limited to specific examples, and the processor 502 can execute the above-described routing information synchronization method when executing the computer program stored in the memory 501.

Corresponding to the method for synchronizing routing information in fig. 6, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the method for synchronizing routing information.

The routing information synchronization device provided by the embodiment of the present application may be specific hardware on the device, or software or firmware installed on the device, or the like. The device provided by the embodiment of the present application has the same implementation principle and technical effect as the foregoing method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the foregoing method embodiments where no part of the device embodiments is mentioned. It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the foregoing systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.

Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the present disclosure, which should be construed in light of the above teachings. Are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for synchronizing routing information is applied to a target extensible virtual local area network VXLAN Tunnel Endpoint (VTEP), and comprises the following steps:

sending first EVPN routing information to other VTEPs, so that the other VTEPs update the stored forwarding table entry aiming at the VM according to the first local forwarding table entry after detecting the migration identification information;

the other VTEP comprises a source VTEP; after sending the first EVPN routing information to the source VTEP, the target VTEP further includes:

if the accessed VM exists in the source VTEP is determined according to feedback information returned by the source VTEP, whether the VM is accessed locally is detected; wherein the feedback information carries a detection result of whether the source VTEP is accessed to the VM;

if detecting that the VM is not accessed locally, deleting the first local forwarding table entry, and informing other VTEPs to delete the first synchronous forwarding table entry aiming at the VM; wherein the first synchronous forwarding table entry is generated by the other VTEPs based on the EVPN routing information.

2. The method for synchronizing routing information according to claim 1, wherein a second target synchronous forwarding entry for the VM is stored in the target VTEP, and the second target synchronous forwarding entry is generated based on second EVPN routing information synchronized with the source VTEP accessing the VM; the method further comprises the following steps:

3. A method for synchronizing routing information is applied to other extensible virtual local area network VXLAN Tunnel End Points (VTEPs), and comprises the following steps:

after detecting migration identification information in the EVPN routing information, updating a stored forwarding table item aiming at the VM according to the first local forwarding table item;

the other VTEPs include a source VTEP, and after the source VTEP updates the stored forwarding table entry for the VM according to the first local forwarding table entry, the method further includes:

4. The method of synchronizing routing information according to claim 3, wherein the other VTEPs further comprise a synchronizing VTEP; after the source VTEP updates the stored forwarding table entry for the VM according to the first local forwarding table entry, the method further includes:

5. The method according to claim 4, wherein the first local forwarding entry includes address information of the VM, and the source VTEP updates the stored forwarding entry for the VM according to the first local forwarding entry, including:

the source VTEP generates a first source synchronous forwarding table item aiming at the VM according to the address information of the VM in the first local forwarding table item and pre-established tunnel information from the source VTEP to the target VTEP;

after the source VTEP updates the stored forwarding table entry for the VM according to the first local forwarding table entry, the method further includes:

6. The method according to claim 4, wherein the first local forwarding entry includes address information of the VM, and the synchronous VTEP updates the stored forwarding entry for the VM according to the first local forwarding entry, including:

the synchronous VTEP generates a first other synchronous forwarding table item aiming at the VM according to the address information of the VM in the first local forwarding table item and pre-established tunnel information from the synchronous VTEP to the target VTEP;

after the synchronous VTEP updates the stored forwarding table entry for the VM according to the first local forwarding table entry, the method further includes:

alternatively, the first and second electrodes may be,

7. The method according to claim 4, wherein after the synchronizing VTEP updates the stored forwarding entry for the VM according to the first local forwarding entry, the method further comprises:

after receiving a data message with a destination address of the VM, if detecting that a plurality of synchronous forwarding table entries aiming at the VM exist at the same time, determining the priority of the plurality of synchronous forwarding table entries according to the sequence of the generation time of the synchronous forwarding table entries; wherein the later the generation time, the higher the priority;

and forwarding the data message based on the synchronous forwarding table entry with the highest priority.

8. An apparatus for synchronizing routing information, comprising:

a first sending module, configured to send first EVPN routing information to other VTEPs, so that after the other VTEPs detect the migration identification information, the forwarding table entry for the VM that is stored is updated according to the first local forwarding table entry;

the other VTEP comprises a source VTEP; the device further comprises:

9. An apparatus for synchronizing routing information, comprising:

an updating module, configured to update a stored forwarding entry for the VM according to the first local forwarding entry after detecting migration identification information in the EVPN routing information;

other VTEPs include a source VTEP, the apparatus further comprising:

a second sending module, configured to send feedback information to the target VTEP; the feedback information carries a detection result of whether the active VTEP is accessed to the VM corresponding to the first local forwarding table entry.