CN115643208A

CN115643208A - Communication method and device

Info

Publication number: CN115643208A
Application number: CN202211202311.7A
Authority: CN
Inventors: 谢岢洋
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2022-09-29
Filing date: 2022-09-29
Publication date: 2023-01-24

Abstract

The application provides a communication method and a device, wherein the method is applied to a first PE, the first PE is positioned in an EVPN network, the EVPN network also comprises a second PE, a CE is respectively connected with the first PE and the second PE through different links, the first PE and the second PE form a multi-attribution group, and the method comprises the following steps: when the second PE fails, obtaining ESI from an EAD per ES route sent by the second PE, wherein the ESI is an identifier of the same ES associated with the first PE and the second PE; acquiring a MAC-IP route which is sent by the second PE and comprises the ESI according to the ESI; acquiring a first MAC table entry correspondingly generated by the MAC-IP route according to the MAC-IP route; and converting the first MAC table entry into a second MAC table entry.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.

Background

In the existing virtual private local area network service (VPLS) network, RFC7432 proposes a scheme for fast convergence of unicast traffic, which can implement fast convergence of unicast traffic through revocation of EAD per ES routing.

As shown in fig. 1, fig. 1 is a schematic diagram of an existing VPLS network structure. In fig. 1, an Ethernet Virtual Private Network (EVPN) point-to-multipoint networking is formed between a Provider Edge (PE) 1, a PE2, and a PE3, and provides two-layer interworking between a Customer Edge (CE) 1 and a CE 2. The forwarding plane among PE1, PE2 and PE3 may be encapsulated by Virtual extended Local Area Network (VXLAN), multi-Protocol Label Switching (MPLS) or Segment Routing (SRv 6) based on IPv 6. CE1 is dual-homed to EVPN through Ethernet Segment (ES).

After the PE learns the Media Access Control Address (MAC) of the user side accessed to the local (for example, the MAC of the virtual machine accessed to the PE, the MAC of the Ethernet switch, the MAC of the virtual machine accessed to the PE through the Ethernet switch, etc.), the MAC-IP Route (also called MAC-IP Advertisement Route) passing through the EVPN synchronizes the MAC of the user side to other PEs which have established Border Gateway Protocol (BGP) neighbors. For example, PE2 learns MAC1 of CE1 from the AC connected to CE1 and synchronizes to PE1 and PE3. And after receiving the MAC-IP route issued by the PE2, the PE3 generates an MAC table entry of the MAC 1. If the ES mode of accessing the CE1 to the EVPN is a single active ES, the exit direction of the MAC table entry is a main path and a standby path pointing to the PE1 and the PE 2; if the ES mode of accessing the EVPN by CE1 is multi-active ES, the exit direction of the MAC table entry is an equivalent path pointing to PE1 and PE 2. Similarly, on PE1, the outgoing direction of the MAC table entry points to the AC connected to CE 1.

When a link between PE2 and CE1 fails, on PE3, if the ES mode is a multi-active ES, PE3 needs to update the outgoing direction of the MAC entry from the equivalent path pointing to PE1 and PE2 to a single path pointing to PE 2; if the ES mode is a single active ES, PE3 needs to update the outgoing direction of the MAC entry from the primary path pointing to PE1 and PE2 to the secondary path.

Because the number of the user-side MACs learned by the PE is huge, if waiting for other PEs to update all the synchronous MAC-IP routes, a large amount of traffic messages will be lost due to an outgoing direction error. RFC7432 therefore proposes a scheme for fast convergence of unicast traffic.

That is, when a PE associates with an ES, an EAD per ES route of EVPN needs to be issued, where the route includes an Ethernet Segment Identifier (hereinafter referred to as "Ethernet Segment Identifier") and an address of the PE issuing the route. Meanwhile, the MAC-IP route issued by the PE also includes the ESI and the user-side MAC of the ES indicated by the access ESI. For example, after PE3 receives the MAC-IP route issued by PE2 and the EAD per ES route issued by PE1 and PE2, the exit direction of the MAC entry is different according to the ES mode. When the link between PE2 and CE1 fails, the EAD per ES route issued by PE2 is withdrawn, and all traffic including MAC1 cannot be forwarded to PE2 any more. Therefore, the modification of the outgoing direction of the MAC table entry can be realized only by one route revocation.

However, the above unicast traffic fast convergence scheme exposes a problem for node failures. When PE2 is restarted, the BGP neighbors between PE2 and PE1, PE3 are all disconnected. All routes on PE1, PE3 that are equivalent to those issued by PE2 are unreachable (including EAD per ES routes and MAC-IP routes). Therefore, on PE3, the exit direction of the MAC entry is updated not only after the EAD per ES route withdrawal is processed; and meanwhile, after the MAC-IP route revocation is processed, deleting the corresponding MAC table entry.

Similarly, the MAC entry is also deleted in PE1, which results in the unicast traffic being changed to unknown unicast traffic in PE1 and PE3. And switching the flow to the PE1 until the CE1 senses the PE2 fault, replying the MAC to the user side by the PE1, then issuing the MAC to the PE3, and changing the flow into the known unicast flow.

In practical applications, in order to prevent excessive traffic of Broadcast, unknown Unicast, and Multicast (english: broadcast, unknown Unicast, multicast traffic, abbreviated as BUM) of a backbone network from causing excessive forwarding pressure of a network-side device, the rate of the BUM traffic is usually limited. Therefore, when a PE fails, a large amount of unicast traffic packet loss will occur. Therefore, a technology for reducing the packet loss of unicast traffic when a single node in a multi-homing group fails is urgently needed.

The existing draft-eat-bass-enhance-evpn-all-active-08 provides a delayed deletion scheme, and the problem can be solved. With reference to fig. 1, the main process is as follows:

PE1 and PE2 are both associated with the same ES, and issue EAD per EVI routes and EAD per ES routes to other PEs that have established BGP neighbors. PE2 learns MAC1 of CE1 and synchronizes to PE1 and PE3 through MAC-IP routing. After receiving the EAD per EVI route, the EAD per ES route and the MAC-IP route issued by the PE1 and the PE2, the PE3 determines that the ES mode of the CE1 accessing the EVPN is a multi-active ES, and the outgoing direction of the MAC table entry of the locally generated MAC1 is an equivalent path pointing to the PE1 and the PE 2.

After receiving the EAD per EVI route, the EAD per ES route and the MAC-IP route issued by the PE2, the PE1 locally generates the MAC table entry of the MAC1, and the outgoing direction of the MAC table entry points to the AC connected with the CE 1. At the same time, PE1 also issues MAC-IP routing for MAC 1.

After receiving the MAC-IP route issued by the PE1, the PE3 determines that the MAC-IP route is the same as the MAC-IP route issued by the PE2, and the PE3 preferably selects one MAC-IP route to take effect. Similarly, PE2 will also receive the MAC-IP route issued by PE 1. However, as for PE2, since the MAC-IP route issued by PE1 is the same as the MAC-IP route issued by itself, PE2 prefers to validate the MAC1 learned by itself without further processing the MAC-IP route issued by PE 1.

When PE2 fails, BGP neighbors between PE2 and PE1 and PE3 are all disconnected. PE1, PE3 will withdraw all routes issued by PE 2. When PE1 processes MAC-IP route revocation issued by PE2, if determining that the outgoing direction of the MAC table entry corresponding to the MAC-IP route points to an Access Circuit (AC) connected with CE1, PE1 does not delete the MAC table entry and revoke the MAC-IP route issued by PE1, but starts a timer (for example, 2 min). When the PE3 processes the MAC-IP route revocation issued by the PE2, if the same MAC-IP route is determined to be received from the PE1, the PE3 selects the MAC-IP route issued by the PE1 to continuously take effect, and does not delete the MAC table entry corresponding to the MAC-IP route.

After the CE1 senses the PE2 fault, the flow is switched to the PE1, and after the PE1 learns the MAC1 again, the timer is closed. After the timer is overtime, the PE1 deletes the MAC table entry which is not learned by the PE1, and cancels the corresponding MAC-IP route.

However, the delayed deletion scheme provided by draft-eastlake-less-enhance-evpn-all-active-08 also exposes the following problems: 1) When the number of the user-side MACs is large, PE1 cannot guarantee that all the user-side MACs are learned within a fixed time. After the timing time is exceeded, if all user side MAC entries are not learned, the PE1 still deletes the MAC entry of the user side MAC entries which are not learned, so that the unicast flow is changed into unknown unicast flow on the PE1 and the PE 3; 2) A failure scenario and an aging scenario cannot be distinguished. When the user-side MAC learned by PE2 is normally aged, PE2 revokes the issued MAC-IP route. At this time, PE1 still enters the flow of the delayed deletion scheme, resulting in the aged user-side MAC remaining in PE1 and PE3.

Disclosure of Invention

In view of this, the present application provides a communication method and apparatus, so as to solve the problem that, in a delayed deletion scheme provided in the existing draft, when the number of user-side MACs is large, a PE cannot guarantee that all user-side MACs are learned within a fixed time and that a user-side MAC to be aged remains in the PE.

In a first aspect, the present application provides a communication method, where the method is applied to a first PE, the first PE is in an EVPN networking, the EVPN networking further includes a second PE, a CE establishes connections with the first PE and the second PE through different links, respectively, and the first PE and the second PE form a multi-affiliation group, where the method includes:

when the second PE fails, obtaining ESI from an EAD per ES route sent by the second PE, wherein the ESI is an identifier of the same ES associated with the first PE and the second PE;

acquiring a MAC-IP route which is sent by the second PE and comprises the ESI according to the ESI;

acquiring a first MAC table entry correspondingly generated by the MAC-IP route according to the MAC-IP route;

and converting the first MAC table entry into a second MAC table entry.

In a second aspect, the present application provides a communication apparatus, where the apparatus is applied to a first PE, the first PE is in an EVPN networking, the EVPN networking further includes a second PE, a CE establishes connections with the first PE and the second PE through different links, respectively, and the first PE and the second PE form a multi-affiliation group, where the apparatus includes:

a first obtaining unit, configured to obtain an ESI from an EAD per ES route sent by the second PE when the second PE fails, where the ESI is an identifier of an identical ES associated with the first PE and the second PE;

a second obtaining unit, configured to obtain, according to the ESI, a MAC-IP route including the ESI sent by the second PE;

a third obtaining unit, configured to obtain, according to the MAC-IP route, a first MAC entry correspondingly generated by the MAC-IP route;

and the conversion unit is used for converting the first MAC table item into a second MAC table item.

In a third aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to perform the method provided by the first aspect of the present application.

Therefore, by applying the communication method and apparatus provided by the present application, when the second PE fails, the ESI is obtained from the EAD per ES route sent by the second PE, and the ESI is an identifier of the same ES associated with the first PE and the second PE; according to ESI, the first PE obtains a MAC-IP route which comprises ESI and is sent by the second PE; according to the MAC-IP route, the first PE acquires a first MAC table entry which is correspondingly generated by the MAC-IP route; the first PE converts the first MAC table entry into a second MAC table entry.

Therefore, the MAC table items synchronously learned are deleted without starting an additional timer. When the MAC table entry is aged normally, because the EAD per ES route is not cancelled, the PE2 and the PE3 receive the MAC-IP route cancellation, the MAC table entry can be deleted normally, and the condition that a useless MAC table occupies the MAC table resource for a long time is avoided. When EAD per ES route withdrawal is processed, the MAC-IP route of PE synchronization associated with the same ES is learned as a local MAC table item again. Even if the number of the MAC at the user side is huge and the PE learns that the MAC at the user side is slow, packet loss caused by deletion of the MAC table entry can not be caused. The problem that in a delayed deletion scheme provided by the existing draft, when the number of user side MAC is large, PE cannot guarantee that all user side MAC is learned within a timing time and user side MAC to be aged remains in PE is solved.

Drawings

Fig. 1 is a schematic diagram of a conventional VPLS network structure;

fig. 2 is a flowchart of a communication method according to an embodiment of the present application;

fig. 3 is a block diagram of a communication device according to an embodiment of the present application;

fig. 4 is a hardware structure of a network device according to an embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the exemplary embodiments below do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context.

A communication method provided in an embodiment of the present application is described in detail below. Referring to fig. 2, fig. 2 is a flowchart of a communication method according to an embodiment of the present disclosure. The method is applied to a first PE. The communication method provided by the embodiment of the application can comprise the following steps.

Step 210, when the second PE fails, obtaining ESI from an EAD per ES route sent by the second PE, where the ESI is an identifier of a same ES associated with the first PE and the second PE;

specifically, the first PE is in an EVPN network, and the EVPN network further includes a second PE and a third PE. The third PE may specifically be a far end PE. The CE establishes connection with the first PE through the first link, and the CE establishes connection with the second PE through the second link. The first PE and the second PE form a multi-homing group. The set of first and second links, referred to as ES, is identified by ESI.

After the networking is successful, the first PE and the second PE are both associated with the same ES, and an EAD per EVI route and an EAD per ES route are issued to other PEs with established BGP neighbors. When the flow reaches the second PE, the second PE learns the MAC of the user side and synchronizes to the first PE and the third PE through the MAC-IP routing of the EVPN.

It should be noted that the EAD per EVI Route and the EAD per ES Route may be collectively referred to as Ethernet Auto-discovery Route (hereinafter referred to as EAD Route), which is also a kind of Route of EVPN. This class of routes includes two classes of sub-routes, namely EAD per EVI (EVPN Instance) routes and EAD per ES routes. EAD per EVI routing is used to discover primary or equivalent paths in EVPN. EAD per ES routing is used for rapid convergence of MAC table entries in the event of failure in EVPN.

The MAC-IP route may be referred to as a MAC-IP distribution route, i.e., a class two route that is EVPN, and is used to advertise a MAC address and host routing information (i.e., ARP information and ND information).

And after receiving the EAD per EVI route, the EAD per ES route and the MAC-IP route issued by the first PE and the second PE, the third PE determines that the ES mode of the CE accessed to the EVPN is a multi-active ES, and locally generates an MAC table entry of the MAC of the user side. The outgoing direction of the MAC entry is an equal cost path pointing to the first PE and the second PE.

After receiving the EAD per EVI route, the EAD per ES route and the MAC-IP route issued by the second PE, the first PE locally generates the MAC table entry of the user side MAC. The outgoing direction of the MAC entry points to the AC connected to the CE. At the same time, the first PE also issues MAC-IP routing of the user side MAC. The MAC-IP route is the same as the MAC-IP route issued by the second PE.

And after receiving the MAC-IP route issued by the first PE, the third PE determines that the MAC-IP route is the same as the MAC-IP route issued by the second PE, and the third PE preferably selects one MAC-IP route to take effect. However, no matter the route issued by the first PE or the second PE is preferred to be valid, the egress direction of the MAC table generated by the third PE is the same.

The second PE will also receive the MAC-IP route issued by the first PE. However, for the second PE, since the MAC-IP route issued by the first PE is the same as the MAC-IP route issued by itself, the second PE prefers the user-side MAC learned by itself to take effect, and does not process the MAC-IP route issued by the first PE any more.

When the second PE fails, the first PE perceives that the BGP neighbors established with the second PE are disconnected. The first PE triggers itself to start the process of withdrawing all routes synchronized by the second PE.

In the second PE-synchronized route, the earliest processing is required because the EAD per ES route has a fast convergence function. The first PE obtains locally the EAD per ES route previously sent by the second PE and obtains the ESI from within the EAD per ES route. The ESI is an identification of the same ES associated with the first PE and the second PE.

Step 220, obtaining a MAC-IP route including the ESI sent by the second PE according to the ESI;

specifically, according to the description of step 210, after the first PE obtains the ESI, the MAC-IP route sent by the second PE including the ESI is obtained according to the ESI.

In the embodiment of the application, the MAC-IP route synchronized by the PE includes the user side MAC, ESI and the migration sequence number.

Step 230, obtaining a first MAC entry correspondingly generated by the MAC-IP route according to the MAC-IP route;

specifically, according to the description in step 220, after obtaining the MAC-IP route including the ESI, the first PE obtains the first MAC entry generated by using the MAC-IP route from the local MAC table.

Optionally, the first MAC entry includes a status field, and the status field stores a first value, where the first value is used to indicate that the first MAC entry is a MAC entry generated through the MAC-IP route. The first value may be embodied as a kind of index, e.g. EVPN.

Step 240, converting the first MAC entry into a second MAC entry.

Specifically, according to the description in step 230, after the first PE obtains the first MAC entry, the first PE updates the state field of the first MAC entry to obtain the second MAC entry.

Optionally, the specific process of the first PE converting the first MAC entry into the second MAC entry includes: the first PE updates a first value stored in the state field into a second value to obtain a second MAC table entry; the first PE starts the aging timing of the second MAC table item.

Optionally, the second MAC table entry includes a status field, and the status field stores a second value, where the second value is used to indicate that the second MAC table entry is a MAC table entry generated through traffic learning. The second value may be embodied as a label, e.g. dynamic.

Therefore, by applying the communication method provided by the present application, when the second PE fails, the ESI is obtained from the EAD per ES route sent by the second PE, and the ESI is an identifier of the same ES associated with the first PE and the second PE; according to ESI, the first PE obtains MAC-IP route including ESI sent by the second PE; according to the MAC-IP route, the first PE acquires a first MAC table entry which is correspondingly generated by the MAC-IP route; the first PE converts the first MAC table entry into a second MAC table entry.

Therefore, the MAC table entry synchronously learned is deleted without starting an additional timer. When the MAC table entry is aged normally, because the EAD per ES route is not cancelled, PE2 and PE3 receive the MAC-IP route cancellation, the MAC table entry can be deleted normally, and the condition that a useless MAC table occupies the MAC table resource for a long time is avoided. When EAD per ES route withdrawal is processed, the MAC-IP route of PE synchronization associated with the same ES is learned as a local MAC table item again. Even if the number of the MAC at the user side is huge and the PE learns that the MAC at the user side is slow, packet loss caused by deletion of the MAC table entry can not be caused. The problem that in a delayed deletion scheme provided by the existing draft, when the number of the user side MAC is large, the PE cannot guarantee that all the user side MAC is learned in a timing time and the user side MAC to be aged remains in the PE is solved.

Optionally, in this embodiment, the method further includes that the first PE withdraws other routes sent by the second PE except the MAC-IP route involved in the foregoing steps.

Specifically, the first PE obtains other routes sent by the second PE except the MAC-IP route including the ESI described above. Other routes include, but are not limited to, MAC-IP routes that do not include ESI, EAD per EVI routes, EAD per ES routes, and the like.

And the first PE deletes the third MAC table entries correspondingly generated by other routes.

It should be noted that the route withdrawal process of the third PE may refer to the processing manner of PE3 provided by the background art draft-eat-less-enhance-evpn-all-active-08, and will not be described again here.

Referring to the networking shown in fig. 1, an EVPN point-to-multipoint networking is formed between PE1, PE2, and PE3, so as to provide two-layer interworking between CE1 and CE 2. The forwarding plane between PE1, PE2 and PE3 may employ VXLAN encapsulation, MPLS encapsulation or SRv6 encapsulation. CE1 accesses EVPN through ES double attribution, the identification of the ES is ESI, CE2 accesses EVPN through single attribution.

PE1 and PE2 are both associated with the same ES, and issue EAD per EVI routes and EAD per ES routes to other PEs that have established BGP neighbors. PE2 learns MAC1 of CE1 and synchronizes to PE1 and PE3 through MAC-IP routing. After receiving the EAD per EVI route, the EAD per ES route and the MAC-IP route issued by PE1 and PE2, PE3 determines that the ES mode in which CE1 accesses the EVPN is a multi-active ES, and the exit direction of the locally generated MAC entry of MAC1 is an equivalent path pointing to PE1 and PE 2.

After receiving the MAC-IP route issued by the PE1, the PE3 determines that the MAC-IP route is the same as the MAC-IP route issued by the PE2, and the PE3 preferably selects one MAC-IP route to take effect. Similarly, PE2 will also receive the MAC-IP route issued by PE 1. However, for PE2, since the MAC-IP route issued by PE1 is the same as the MAC-IP route issued by itself, PE2 prefers that the MAC1 learned by itself is effective and does not process the MAC-IP route issued by PE 1.

When PE2 fails, BGP neighbors between PE2 and PE1 and PE3 are all disconnected. PE1, PE3 will withdraw all routes issued by PE 1. PE1 obtains locally the EAD per ES route that PE2 sent earlier and the ESI from within the EAD per ES route.

After PE1 obtains ESI, according to ESI, obtaining MAC-IP route including ESI sent by PE 2. From the local MAC table, PE1 obtains a first MAC table entry generated using the MAC-IP route that includes the ESI. The first MAC entry includes a status field that stores an EVPN for indicating that the first MAC entry is a MAC entry generated through MAC-IP routing.

After the PE1 acquires the first MAC entry, the PE1 updates EVPN stored in the state field to dynamic, which is used to indicate that the second MAC entry is a MAC entry generated through traffic learning. PE1 obtains a second MAC table item and starts aging timing of the second MAC table item.

Based on the same inventive concept, the embodiment of the application also provides a communication device corresponding to the communication method. Referring to fig. 3, fig. 3 is a communication apparatus provided in this embodiment, where the apparatus is applied to a first PE, the first PE is in an EVPN networking, the EVPN networking further includes a second PE, a CE establishes a connection with the first PE and the second PE through different links, respectively, and the first PE and the second PE form a multi-homing group, where the apparatus includes:

a first obtaining unit 310, configured to obtain an ESI from an EAD per ES route sent by the second PE when the second PE fails, where the ESI is an identifier of a same ES associated with the first PE and the second PE;

a second obtaining unit 320, configured to obtain, according to the ESI, a MAC-IP route that includes the ESI and is sent by the second PE;

a third obtaining unit 330, configured to obtain, according to the MAC-IP route, a first MAC entry correspondingly generated by the MAC-IP route;

a converting unit 340, configured to convert the first MAC table entry into a second MAC table entry.

Optionally, the first MAC entry includes a status field, where the status field stores a first value, and the first value is used to indicate that the first MAC entry is a MAC entry generated through MAC-IP routing;

the second MAC entry includes the status field, and the status field stores a second value, where the second value is used to indicate that the second MAC entry is a MAC entry generated through traffic learning.

Optionally, the converting unit 340 is specifically configured to update the first value stored in the status field to the second value, so as to obtain the second MAC entry;

and starting the aging timing of the second MAC table entry.

Optionally, the apparatus further comprises: a fourth obtaining unit (not shown in the figure) configured to obtain a route other than the MAC-IP route sent by the second PE;

and a deleting unit (not shown in the figure) configured to delete the third MAC entry correspondingly generated by the other route.

Therefore, with the communication device provided in the present application, when the second PE fails, the ESI is obtained from the EAD per ES route sent by the second PE, where the ESI is an identifier of the same ES associated with the first PE and the second PE; according to ESI, the first PE obtains MAC-IP route including ESI sent by the second PE; according to the MAC-IP route, the first PE obtains a first MAC table entry correspondingly generated by the MAC-IP route; the first PE converts the first MAC table item into a second MAC table item.

Therefore, the MAC table entry synchronously learned is deleted without starting an additional timer. When the MAC table entry is aged normally, because the EAD per ES route is not cancelled, PE2 and PE3 receive the MAC-IP route cancellation, the MAC table entry can be deleted normally, and the condition that a useless MAC table occupies the MAC table resource for a long time is avoided. When EAD per ES route revocation is processed, PE-synchronized MAC-IP routes associated with the same ES are relearned as native MAC entry. Even if the number of the MAC at the user side is huge and the PE learns that the MAC at the user side is slow, packet loss caused by deletion of the MAC table entry can not be caused. The problem that in a delayed deletion scheme provided by the existing draft, when the number of the user side MAC is large, the PE cannot guarantee that all the user side MAC is learned in a timing time and the user side MAC to be aged remains in the PE is solved.

Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 4, which includes a processor 410, a transceiver 420, and a machine-readable storage medium 430, where the machine-readable storage medium 430 stores machine-executable instructions capable of being executed by the processor 410, and the processor 410 is caused by the machine-executable instructions to perform the communication method provided by the embodiment of the present application. The path protection device shown in fig. 3 may be implemented by using a hardware structure of a network device as shown in fig. 4.

The computer-readable storage medium 430 may include a Random Access Memory (RAM) or a Non-volatile Memory (NVM), such as at least one disk Memory. Alternatively, the computer-readable storage medium 430 may also be at least one memory device located remotely from the processor 410.

The Processor 410 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In the embodiment of the present application, the processor 410 is caused by machine executable instructions by reading the machine executable instructions stored in the machine readable storage medium 430 to enable the processor 410 itself and the call transceiver 420 to perform the communication method described in the embodiment of the present application.

Additionally, embodiments of the present application provide a machine-readable storage medium 430, where the machine-readable storage medium 430 stores machine-executable instructions that, when invoked and executed by the processor 410, cause the processor 410 itself and the invoking transceiver 420 to perform the communication methods described in embodiments of the present application.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiment, since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 position, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

As for the embodiments of the communication apparatus and the machine-readable storage medium, since the contents of the related methods are substantially similar to those of the foregoing embodiments of the methods, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the embodiments of the methods.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A communication method is applied to a first PE, the first PE is in an EVPN networking, the EVPN networking further comprises a second PE, a CE establishes connection with the first PE and the second PE respectively through different links, the first PE and the second PE form a multi-attribution group, and the method comprises the following steps:

and converting the first MAC table item into a second MAC table item.

2. The method of claim 1, wherein the first MAC entry comprises a status field, and wherein the status field stores a first value indicating that the first MAC entry is a MAC entry generated via MAC-IP routing;

the second MAC table entry includes the status field, and the status field stores a second value, where the second value is used to indicate that the second MAC table entry is a MAC table entry generated through traffic learning.

3. The method according to claim 2, wherein said converting the first MAC entry into the second MAC entry specifically comprises:

updating the first value stored in the state field to the second value to obtain the second MAC table entry;

and starting the aging timing of the second MAC table entry.

4. The method of claim 1, further comprising:

acquiring other routes sent by the second PE except the MAC-IP route;

and deleting the third MAC table entries correspondingly generated by the other routes.

5. A communication apparatus, wherein the apparatus is applied to a first PE, the first PE is in an EVPN networking, the EVPN networking further includes a second PE, a CE establishes connections with the first PE and the second PE through different links, respectively, and the first PE and the second PE form a multi-homing group, the apparatus includes:

6. The apparatus of claim 5, wherein the first MAC table entry comprises a status field, and wherein the status field stores a first value indicating that the first MAC table entry is a MAC table entry generated via MAC-IP routing;

7. The apparatus according to claim 6, wherein the converting unit is specifically configured to update the first value stored in the status field to the second value, so as to obtain the second MAC entry;

and starting the aging timing of the second MAC table entry.

8. The apparatus of claim 5, further comprising:

a fourth obtaining unit, configured to obtain a route other than the MAC-IP route sent by the second PE;

and the deleting unit is used for deleting the third MAC table entries correspondingly generated by the other routes.