CN113472665A

CN113472665A - Method and device for realizing butt joint of different networks under EVPN

Info

Publication number: CN113472665A
Application number: CN202110671630.1A
Authority: CN
Inventors: 罗怡
Original assignee: New H3C Security Technologies Co Ltd
Current assignee: New H3C Security Technologies Co Ltd
Priority date: 2021-06-17
Filing date: 2021-06-17
Publication date: 2021-10-01
Anticipated expiration: 2041-06-17
Also published as: CN113472665B

Abstract

The method is applied to a first PE in an EVPN VPLS (virtual private LAN service) network, and receives a first service message sent by a second PE through a first PW (pseudo wire); searching whether a first AC port configured with a specified forwarding function exists in the VSI; if the first AC port exists, sending a first service message through the first AC port; if the first AC port does not exist, searching whether an MAC address table item matched with the first destination MAC address exists in an MAC address table or not in the VSI according to the first destination MAC address; if an MAC address table item matched with the first target MAC address exists, acquiring a corresponding output interface from the MAC address table item, and sending a first service message through the output interface; and if the MAC address table item matched with the first target MAC address does not exist, sending the first service message through all AC ports in the VSI.

Description

Method and device for realizing butt joint of different networks under EVPN

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing different network interfacing under EVPN.

Background

An Ethernet Virtual Private Network (EVPN) is a two-layer Virtual Private Network (VPN) technology, in which a control plane uses BGP-4 Multi-Protocol Extensions for BGP-4, MP-BGP to advertise EVPN routing information, and a data plane uses Virtual extended Local Area Network (VXLAN) or Multi-Protocol Label Switching (MPLS) to forward service messages. When the physical sites of the tenants are scattered at different positions, the EVPN can provide two-layer interconnection for the same subnet of the same tenant based on the existing service provider or an Internet Protocol (IP) network. Private network routing information of the VPN can also be issued through EVPN routing information so as to realize MPLS L3VPN networking.

Virtual Private LAN Service (VPLS for short) is configured under the EVPN to form an EVPN VPLS networking. The control layer of the network adopts MP-BGP to announce EVPN routing information, and the data layer adopts MPLS-encapsulated two-layer VPN technology. In the EVPN VPLS group network, a service Provider network Edge (PE for short) forwards a service message by looking up a Media Access Control Address (MAC for short) Address table, thereby providing a point-to-multipoint two-layer service for a user.

In an EVPN VPLS (virtual Private LAN service) group network of a single attribution scene, establishing a Private line (PW for short) service between PEs through an MAC/IP (media access control) distribution Route and an Inclusive Multicast Ethernet Tag Route (IMET Route); in the EVPN VPLS network in the multi-homing scenario, a multi-homing scenario service is also established additionally through an Ethernet Auto-discovery Route (also called AD Route) and an Ethernet Segment Route (Ethernet Segment Route).

Virtual Private Wire Service (VPWS) is configured under the EVPN to form an EVPN VPWS networking. The control layer of the network adopts MP-BGP to announce EVPN routing information, and the data layer adopts MPLS-encapsulated two-layer VPN technology. Service messages of a user network are forwarded through an access Circuit (English: AC for short) and a PW under cross connection, and a MAC address table does not need to be searched, so that point-to-point two-layer service is provided for users.

The method comprises the following steps that a PW service is established through an AD EVI route in an EVPN VPWS network group in a single attribution scene; and in the EVPN VPWS network group in the multi-homing scene, PW service is established through AD routing and Ethernet routing.

The existing VPWS service realizes a point-to-point VPN technology, and has the advantages of simple technology, single application scene and more limitations. In some complex networking requirements, the VPLS service can better meet various application scenarios of users. However, in the process of upgrading the whole network, the service is also adjusted, and the risk degree is high. Therefore, the EVPN VPWS networking is connected to the EVPN VPLS networking in a butt-joint mode at present, partial network replacement is met, gradual upgrading is achieved, and services are in smooth transition.

As shown in fig. 1, fig. 1 is a schematic diagram of EVPN VPWS networking interfacing EVPN VPLS networking. In the process of accessing the EVPN VPWS networking to the EVPN VPLS networking, the PE1 configures VPWS, and the PE2 configures VPLS service. PE1 receives and issues AD routes matching VPWS traffic. By negotiating the AD route, a PW is established between PE1 and PE2, and the PW is utilized to implement the intercommunication of different networking traffic under EVPN.

The existing method for accessing the EVPN VPWS networking to the EVPN VPLS networking also has the following defects; 1) after PE2 generates a PW accessed to PE1, forwarding logic of VPLS service traffic at PE2 side will be converted into a VLL forwarding mode, that is, an AC port of PE2 receives VPLS service traffic, and forwards VPLS service traffic to PE1 through a PW bound to the AC port; PE2 receives VPWS traffic over the PW and forwards the VPWS traffic to CE2 through the AC port bound to the PW. Thus, PE2 loses the unicast forwarding property of the existing lookup MAC address table of VPLS service; 2) ESI information cannot be carried in an AD route interacted between the conventional PE1 and the PE2 and used for establishing a PW, so that a PE2 side cannot form multi-homing redundancy protection to a P1 side by utilizing EVPN ESI characteristics; 3) if the PW is configured to a virtual local area network (english: virtual Local Area Network, abbreviation: VLAN) identification (english: identifier, abbreviation: ID) is the same as the VLAN ID configured at the AC port of P1, resulting in two routes being the same and inflexible deployment.

Disclosure of Invention

In view of this, the present application provides a method and an apparatus for implementing different networking docking under EVPN, so as to solve various problems involved in the different networking docking process under the existing EVPN.

In a first aspect, the present application provides a method for implementing different networking docks under EVPN, where the method is applied to a first PE in an EVPN VPLS networking, where the first PE docks a second PE in an EVPN VPWS networking, a VSI is configured in the first PE, a VPLS service is configured in the VSI, and a first PW has been established between the first PE and the second PE, and the method includes:

receiving a first service message sent by the second PE through the first PW, wherein the first service message comprises a first destination MAC address;

searching whether a first AC port configured with a specified forwarding function exists in the VSI;

if the first AC port exists, the first service message is sent through the first AC port;

if the first AC port does not exist, searching whether an MAC address table item matched with the first destination MAC address exists in an MAC address table or not in the VSI according to the first destination MAC address;

if an MAC address table item matched with the first target MAC address exists, acquiring a corresponding output interface from the MAC address table item, and sending the first service message through the output interface;

and if the MAC address table item matched with the first target MAC address does not exist, sending the first service message through all AC ports in the VSI.

In a second aspect, the present application provides an apparatus for implementing different networking interfaces under EVPN, where the apparatus is applied to a first PE in an EVPN VPLS networking, the first PE interfaces with a second PE in an EVPN VPWS networking, a VSI is configured in the first PE, a VPLS service is configured in the VSI, and a first PW has been established between the first PE and the second PE, and the apparatus includes:

a receiving unit, configured to receive, through the first PW, a first service packet sent by the second PE, where the first service packet includes a first destination MAC address;

the search unit is used for searching whether a first AC port configured with a specified forwarding function exists in the VSI;

a sending unit, configured to send the first service packet through the first AC port if the first AC port exists;

the searching unit is further configured to, if the first AC port does not exist, search, according to the first destination MAC address, whether an MAC address table entry matching the first destination MAC address exists in an MAC address table in the VSI;

the sending unit is further configured to, if an MAC address table entry matching the first destination MAC address exists, obtain a corresponding egress interface from the MAC address table entry, and send the first service packet through the egress interface;

the sending unit is further configured to send the first service packet through all AC ports in the VSI if there is no MAC address table entry matching the first destination MAC address.

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 method and the device for realizing different networking docking under EVPN provided by the present application, through the first PW, the first PE receives the first service packet sent by the second PE, where the first service packet includes the first destination MAC address. Within the VSI, the first PE looks for the presence of a first AC port configured with a specified forwarding function. And if the first AC port exists, the first PE sends the first service message through the first AC port. If the first AC port does not exist, the first PE searches whether an MAC address table item matched with the first destination MAC address exists in the MAC address table or not in the VSI according to the first destination MAC address. And if the MAC address table item matched with the first target MAC address exists, the first PE acquires a corresponding output interface from the MAC address table item and sends the first service message through the output interface. And if the MAC address table item matched with the first target MAC address does not exist, the first PE sends a first service message through all AC ports in the VSI.

Therefore, the first PE in the EVPN VPLS network can be in butt joint with the second PE in the EVPN VPWS network, and various problems involved in the butt joint process of different networks under the existing EVPN are solved. On the basis of not influencing the original functions of each service, the butt joint of different networks under the EVPN is realized, and the access of each service is convenient; meanwhile, the EVPN ESI multi-homing characteristic can be utilized to form the redundancy protection of the butt joint service and the flexible networking deployment.

Drawings

FIG. 1 is a schematic diagram of EVPN VPWS networking docking EVPN VPLS networking;

fig. 2 is a flowchart of a method for implementing different network interfacing under EVPN according to the embodiment of the present application;

fig. 3 is a networking schematic diagram of different networking docking under EVPN according to an embodiment of the present application;

fig. 4 is a networking schematic diagram of different networking interfaces under EVPN according to another embodiment of the present application;

fig. 5 is a networking schematic diagram of different networking docking under EVPN according to another embodiment of the present application;

fig. 6 is a structural diagram of an implementation apparatus for different networking docking under EVPN provided in the embodiment of the present application;

fig. 7 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 following exemplary embodiments 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 … …" or "when … …" or "in response to a determination", depending on the context.

The following describes in detail a method for implementing different network interfacing under EVPN provided in the embodiment of the present application. Referring to fig. 2, fig. 2 is a flowchart of a method for implementing different networking docking under EVPN according to the embodiment of the present application. The method is applied to the first PE, and the implementation method for different networking docking under EVPN provided by the embodiment of the present application may include the following steps.

Step 210, receiving a first service packet sent by the second PE through the first PW, where the first service packet includes a first destination MAC address.

Specifically, a Virtual Switch Instance (VSI for short) is configured in the first PE, and a VPLS service is configured in the VSI; and configuring a cross-connection group (XCG for short) in the second PE, and configuring the VPWS service in the XCG. A first PW has been established between the first PE and the second PE. Through the first PW, the first PE receives a first service message sent by the second PE, and the first service message comprises a first destination MAC address.

Step 220, in the VSI, it is searched whether there is a first AC port configured with a specified forwarding function.

Specifically, according to the description of step 210, within the VSI, it is looked up whether there is a first AC port configured with a specified forwarding function. If there is a first AC port configured with the specified forwarding function, step 230 is performed. If there is no first AC port that specifies a forwarding function, step 240 is performed.

In the embodiment of the application, the designated forwarding function specifically refers to a Tree-leaf-Only function. This function is used by PEs that are configured with VPLS traffic. When the AC port in the VSI is configured with the function, the incoming flow of the AC port is not broadcasted and is only forwarded to the PW bound with the AC port; when receiving the incoming traffic through the PW established with the second PE, the broadcast processing is not performed in the VSI, and the incoming traffic is forwarded only to the AC port in which the function is configured in the VSI. The unicast traffic received by the first PE is forwarded without this restriction, and the unicast forwarding processing is still performed following the lookup of the MAC address table.

Step 230, if the first AC port exists, sending the first service packet through the first AC port.

Specifically, according to the description in step 220, if there is a first AC port configured with the designated forwarding function, the first PE forwards the first service packet through the first AC port. That is, the first service packet is forwarded to a user network Edge (CE for short) accessing the AC interface through the first AC interface.

Step 240, if the first AC port does not exist, according to the first destination MAC address, searching whether a MAC address table entry matching the first destination MAC address exists in a MAC address table in the VSI.

Specifically, according to the description of step 220, if there is no first AC port configured with the designated forwarding function, the first PE searches, according to the first destination MAC address, whether there is a MAC address table entry matching the first destination MAC address in the VSI in the MAC address table.

If there is a MAC address entry matching the first destination MAC address, step 250 is performed. If there is no MAC address entry matching the first destination MAC address, then step 260 is performed.

It is understood that the MAC address table includes information of a destination MAC address field, an egress interface field, and the like. And searching the MAC address table to obtain a corresponding output interface from the MAC address table, and forwarding the service message through the output interface. The egress interface specifically indicates the AC port.

Step 250, if an MAC address table entry matching the first destination MAC address exists, obtaining a corresponding egress interface from the MAC address table entry, and sending the first service packet through the egress interface.

Specifically, according to the description in step 240, if there is an MAC address table entry matching the first destination MAC address, the first PE obtains the corresponding egress interface from the MAC address table entry, and sends the first service packet through the egress interface. That is, the first service packet is forwarded to the CE accessing the AC interface through the AC interface indicated by the outgoing interface.

Step 260, if there is no MAC address table entry matching the first destination MAC address, sending the first service packet through all AC ports in the VSI.

Specifically, according to the description of step 240, if there is no MAC address table entry matching the first destination MAC address, the first PE sends the first service packet through all AC ports in the VSI.

Therefore, the first PE in the EVPN VPLS network can be in butt joint with the second PE in the EVPN VPWS network, and various problems involved in the butt joint process of different networks under the existing EVPN are solved. On the basis of not influencing the original functions of each service, the butt joint of different networks under the EVPN is realized, and the access of each service is convenient; meanwhile, the multi-homing characteristic of Ethernet Segment Identifier (ESI) can be used to form the redundancy protection of the butt-joint service and flexible network deployment.

Optionally, in this embodiment of the present application, a process in which the first PE receives a service packet sent by the CE and forwards the service packet is further included.

Specifically, through the second AC interface, the first PE receives a second service packet sent by the CE, where the second service packet includes a second destination MAC address.

And when the second AC port is configured with the appointed forwarding function, the first PE sends a second service message through a second PW bound with the second AC port. When the second AC port is not configured with the appointed forwarding function, according to the second destination MAC address, in the VSI, the first PE searches whether an MAC address table item matched with the second destination MAC address exists in the MAC address table.

If the MAC address table item matched with the second target MAC address exists, the first PE acquires the corresponding output interface from the MAC address table item and sends a second service message through the output interface

And if the MAC address table item matched with the second destination MAC address does not exist, the first PE sends a second service message through other AC ports except the second AC port in the VSI and all PWs in the VSI.

Optionally, in this embodiment of the present application, the first PE may also be in a multi-homing member group, the multi-homing member group further includes a third PE, and a bypass (bypass) PW is established between the first PE and the third PE.

It is understood that a VSI is also configured in the third PE, and the identity of the VSI is the same as the identity of the VSI configured in the first PE. The third PE configures VPLS traffic within the VSI.

In the foregoing step 250, after the first PE obtains the corresponding egress interface from the MAC address table entry, the following steps may be further included:

if the third AC port indicated by the outgoing interface fails, the first PE sends the first service packet to the third PE through the bypass PW, so that after the third PE locally finds a fourth AC port having the same ESI as the third AC port, the third PE sends the first service packet through the fourth AC port.

Optionally, in this embodiment of the present application, the second PE may also be in a multi-homing membership group, the multi-homing membership group further includes a fourth PE, and a third PW has been established between the first PE and the fourth PE.

It is understood that an XCG is also configured in the fourth PE, the identity of which is the same as the identity of the XCG configured in the second PE. The fourth PE configures VPWS services within XCG.

In the foregoing embodiment, after the first PE receives the second service packet sent by the CE, the method may further include the following steps:

and when the number of the second PWs is multiple, the first PE sends a second service message through the multiple PWs.

Optionally, before step 210, a step of receiving, by the first PE, an EVPN-like route sent by the second PE is further included.

Specifically, the second PE configures an EVPN Local identification (Local ID) of 100, a Remote identification (Remote ID) of 200, an access Tree (Insert-Tree) function, and a designated Tree identification (Tree ID) of 300 within the VPWS service.

The second PE generates a first AD EVI route including a first Ethernet tag identification (Ethernet tag ID), a first Tree identification (Tree ID), first trunk information (Tree trunk), and first branch information (Tree branch).

The second PE transmits a first AD EVI route within the EVPN. The first PE receives the first AD EVI route, and obtains a first Ethernet label identification, a first tree identification, first trunk information and first branch information from the first AD EVI route.

The first PE compares whether the first tree identification is the same as a second tree identification configured in the VSI of the first PE; if the first Ethernet tag identification is the same as the second Ethernet tag identification configured in the VSI, the first PE compares whether the first Ethernet tag identification is the same as the second Ethernet tag identification configured in the VSI.

If so, the first PE identifies a value of the first trunk information and a value of the first branch information. If the value of the first trunk information is 1 and the value of the first branch information is 0, the first PE determines that the first AD EVI route is sent by the second PE, that is, the first PE determines that the source of the first AD EVI route is a PE configured with the VPWS service. The first PE and the second PE establish a first PW.

Optionally, before step 210, a step of generating and transmitting an EVPN type route by the first PE is further included.

Specifically, the first PE configures, within the VPLS service, an EVPN local identity of 200, a remote identity of 100, and an access tree function, and specifies a tree identity of 300.

The first PE generates a second AD EVI route that includes a third ethernet tag identification, a third Tree identification, second trunk information, second branch information, and first leaf information (Tree leaf).

The first PE transmits a second AD EVI route within the EVPN. And the second PE receives the second AD EVI route and acquires a third Ethernet label identification, a third tree identification, second trunk information, second branch information and first leaf information.

The second PE compares whether the third tree identification is the same as a fourth tree identification configured in the XCG or not; if the first Ethernet tag identification is the same as the second Ethernet tag identification, the second PE compares whether the third Ethernet tag identification is the same as a fourth Ethernet tag identification configured in the XCG.

If so, the second PE identifies a value of the second trunk information and a value of the second branch information. If the value of the second trunk information is 0 and the value of the second branch information is 1, the second PE determines that the second AD EVI route is sent by the first PE, that is, the second PE determines that the source of the second AD EVI route is a PE configured with the VPLS service. The second PE identifies a value of the first leaf information; if the value is 0, the second PE determines that the first PE is not in the multihomed membership group (the first PE does not identify the configuration ESI for the third tree, the second PE does not need to form multiple equivalent PWs to the first PE in response to AD ES routing). The second PE establishes a first PW with the first PE.

The first PE configures an EVPN local identifier 200, a remote identifier 100 and an access tree function in the VPLS service, and the designated tree identifier 300. The first PE specifies an ESI value of 1.2.3.4.5 for the tree identification, and specifies the mode as multi-live mode.

The first PE generates a third AD EVI route, the third AD EVI including a fifth ethernet tag identification, a fifth tree identification, third trunk information, third tree branch information, second leaf information, and ESI. At the same time, the first PE also generates a first AD ES route that includes the ESI and an ESI Flag (ESI Flag).

The first PE transmits a third AD EVI route and a first AD ES route within the EVPN. And the second PE receives the third AD EVI route and acquires a fifth Ethernet label identifier, a fifth tree identifier, third trunk information, third branch information, second leaf information and ESI from the third AD EVI route.

The second PE compares whether the fifth tree identification is the same as a sixth tree identification configured in the XCG or not; if yes, the second PE compares the fifth Ethernet label identification with a sixth Ethernet label identification configured in the XCG of the second PE to determine whether the fifth Ethernet label identification is the same as the sixth Ethernet label identification configured in the XCG of the second PE.

If the first and second PEs are the same, the second PE identifies a value of the third trunk information and a value of the third branch information. If the value of the third trunk information is 0 and the value of the third branch information is 1, the second PE determines that the third AD EVI route is sent by the first PE, that is, the second PE determines that the source of the second AD EVI route is a PE configured with the VPLS service. The second PE identifies a value of the second leaf information; if the value is 1, the second PE determines that the first PE is in the multihomed membership group (the first PE identifies the configuration ESI for the fifth tree, the second PE needs to form multiple equivalent PWs to the first PE in response to AD ES routing).

Since the third AD EVI route includes ESI, the second PE, upon receiving the first AD ES route, obtains the ESI and the ESI flag therefrom. The second PE identifies the value of the ESI flag, and if the value is 0, the second PE determines that the first PE and the third PE form a multi-homing member group (it may be understood that the second PE also receives the EVPN class route sent by the third PE, and the ESI flag included in the EVPN class route are the same as those included in the EVPN class route sent by the first PE, and the second PE determines that the first PE and the third PE form the multi-homing member group according to the EVPN class routes sent by the first PE and the third PE). The second PE establishes a first PW and a fourth PW with the first PE and the third PE respectively, wherein the first PW and the fourth PW are equivalent PWs.

Optionally, before step 210, a step of receiving, by the first PE, an EVPN-like route sent by the third PE is further included.

Specifically, the third PE configures, within the VPLS service, an EVPN local identity of 200, a remote identity of 100, and an access tree function, and specifies a tree identity of 300.

The second PE generates a first AD EVI route including a first Ethernet tag identification (Ethernet tag ID), a first Tree identification (Tree ID), first trunk information (Tree trunk), and first branch information (Tree branch). The third PE specifies the ESI value for the tree identification as 1.2.3.4.5, and at the same time specifies the mode as multi-live mode.

The third PE generates a fourth AD EVI route, the fourth AD EVI including a seventh ethernet tag identification, a seventh tree identification, fourth trunk information, fourth branch information, third leaf information, and ESI. At the same time, the third PE also generates a second AD ES route that includes the ESI and the ESI flag.

The third PE transmits a fourth AD EVI route and a second AD ES route within the EVPN. And the first PE receives the fourth AD EVI route and acquires a seventh Ethernet label identifier, a seventh tree identifier, fourth trunk information, fourth branch information, third leaf information and ESI from the fourth AD EVI route.

The first PE compares whether the seventh tree identification is the same as the eighth tree identification configured in the VSI of the first PE; if the first PE is the same as the second PE, the first PE compares whether the seventh Ethernet tag identification is the same as the eighth Ethernet tag identification configured in the VSI of the first PE.

And if the first PE is different and is the same as a ninth Ethernet label identifier configured in the VSI of the first PE, identifying the value of the fourth trunk information and the value of the fourth branch information by the first PE. If the value of the first trunk information is 0 and the value of the fourth branch information is 1, the first PE determines that the fourth AD EVI route is sent by the third PE, that is, the first PE determines that the source of the fourth AD EVI route is a PE configured with VPLS service. The first PE identifies a value of the third leaf information; if the value is 1, the first PE determines that the third PE has configured ESI for the seventh tree identification.

Since the fourth AD EVI route includes ESI, the first PE, upon receiving the second AD ES route, obtains the ESI and the ESI flag therefrom. The first PE identifies the ESI and the value of the ESI flag. If the ESI is the same as the ESI bound by the seventh tree identity and the value of the ESI flag is 0, then the first PE determines that the third PE is a member within the same multi-homed group of members. The first PE and the third PE establish a bypass PW.

Specifically, the second PE configures an EVPN Local identification (Local ID) of 100, a remote end identification of 200, and an access Tree (Insert-Tree) function, designating a Tree identification (Tree ID) of 300, within the VPWS service. The second PE specifies the ESI value for the tree identification as 1.2.3.4.5, and at the same time specifies the mode as multi-live mode.

The second PE generates a fifth AD EVI route, the fifth AD EVI including a tenth ethernet tag identification, a ninth tree identification, fifth trunk information, fifth branch information, and ESI. At the same time, the second PE also generates a third AD ES route that includes the ESI and the ESI flag.

The second PE transmits a fifth AD EVI route within the EVPN. And the first PE receives the fifth AD EVI route and acquires a tenth Ethernet label identifier, a ninth tree identifier, fifth trunk information, fifth branch information and ESI from the fifth AD EVI route.

The first PE compares whether the ninth tree identification is the same as a tenth tree identification configured in the VSI of the first PE; if the first PE is the same as the second PE, the first PE compares whether the tenth Ethernet tag identification is the same as the eleventh Ethernet tag identification configured in the VSI of the first PE.

If so, the first PE identifies a value of the fifth trunk information and a value of the fifth branch information. If the value of the fifth trunk information is 1 and the value of the fifth branch information is 0, the first PE determines that the fifth AD EVI route is sent by the second PE, that is, the first PE determines that the source of the fifth AD EVI route is a PE configured with the VPWS service.

Since the fifth AD EVI route includes ESI, the first PE, upon receiving the third AD ES route, obtains ESI and ESI flag therefrom. The first PE identifies the ESI and the value of the ESI flag. If the ESI is the same as the ESI included in the sixth AD EVI route and the fourth AD ES route sent by the fourth PE and the value of the ESI flag is 0, the first PE determines that the second PE and the fourth PE form the multihomed member group (it may be understood that the first PE also receives the EVPN class route sent by the fourth PE, and the ESI flag included in the EVPN class route are the same as the ESI and the ESI included in the EVPN class route sent by the second PE, and the first PE determines that the second PE and the fourth PE form the multihomed member group according to the EVPN class routes sent by the second PE and the fourth PE). The first PE establishes a first PW and a fifth PW with the second PE and the fourth PE respectively, wherein the first PW and the fifth PW are equivalent PWs.

Optionally, in this embodiment of the present application, if the value of the ESI flag is 1, the first PE determines that the second PE and the fourth PE form the active-standby redundant backup group. The first PE establishes a first PW and a fifth PW with the second PE and the fourth PE respectively, wherein the first PW is a main PW, and the fifth PW is a standby PW.

In summary, in the embodiment of the present application, an Insert-Tree (Insert-Tree) function is newly added in the VPWS service/VPLS service. Under the function, tree identifications are specified, and VPWS services/VPLS services with the same tree identifications can be mutually accessed. Meanwhile, the expanding group attribute of the EVPN type route is expanded and carried in the EVPN type route. When an EVPN VPWS networking and EVPN VPLS networking butt-joint scene needs to be deployed, equipment at two ends realizes service butt-joint through exchanging specific information included by an expanded group attribute matching insertion tree function, and then a butt-joint PW is established.

Wherein the insert tree function includes the following parameters:

tree identification: identifying a tree, wherein the VPWS service and the VPLS service with the same tree identification can be mutually accessed, and the tree identification can be bound with ESI and is used for realizing EVPN multi-homing;

trunk information: the device is used for identifying whether the route source is issued by the equipment for configuring the VPWS service, occupies 1 bit, and sets 1 to indicate that the route source is issued by the equipment for configuring the VPWS service;

branch information: the router is used for identifying whether the router is issued by the equipment configured with the VPLS service and occupies 1 bit; setting 1 to indicate that a route source is issued by equipment configured with VPLS service;

leaf information: the method comprises the steps that equipment used for identifying and configuring VPLS service comprises an AC port and multi-homing characteristics, when tree identification binding ESI is carried, the parameter is carried, the setting is 1, and the fact that AD EVI routing and AD ES routing are required to be matched is indicated to establish multi-homing PW;

carrying out PW butt joint: PW established by the butt joint of different networks under the EVPN is realized;

specifying a forwarding function: the method comprises the steps that the method is configured at an AC port associated with VPLS service, when the AC port is configured with the function, incoming flow received by the AC port is not broadcasted and is only forwarded to a butt PW bound with the AC port; when the butt PW receives the incoming flow, the broadcasting processing is not carried out in the VPLS service, and only the forwarding is carried out to the AC port with the appointed forwarding function; MAC unicast forwarding is not limited by the limitation, and unicast forwarding is still carried out by following the MAC address table;

in the multi-homing scene of the EVPN VPLS networking, an AC port with a designated forwarding function is configured in VPLS service, and multi-homing roles (DF, BDF), ESI values, single-living modes and multi-living modes of the multi-homing roles are inherited to ESI bound by tree identification;

the multi-homing scene of the EVPN VPWS networking, an AC port configured in a VPWS service, and multi-homing roles (DF, BDF), ESI values, single-living modes and multi-living modes of the AC port are inherited to ESI bound by tree identification.

The following describes in detail a method for implementing different network interfacing under EVPN provided in the embodiment of the present application. Referring to fig. 3, fig. 3 is a networking schematic diagram of different networking docking under EVPN according to an embodiment of the present application.

In fig. 3, a device configures XCG and VPWS service within XCG. The VPWS service is configured with an EVPN Local ID of 100, a Remote ID of 200, an Insert-Tree function and a specified Tree ID of 300.

The device A generates and sends an AD EVI route in the EVPN, wherein the AD EVI route comprises that the Ethernet tag ID is 100 (namely the EVPN Local ID), the Tree ID is 300, the Tree trunk is set to be 1, the Tree branch is set to be 0, and the Tree leaf is set to be 0.

And configuring a VSI in the B equipment, and configuring VPLS service in the VSI. An EVPN Local ID is configured to be 200, a Remote ID is configured to be 100, an Insert-Tree function is configured in the VPLS service, and a Tree ID is designated to be 300. The AC2 port is configured with a designated forwarding function, the AC3 port and the AC4 port are not configured with a designated forwarding function.

The B device generates and sends an AD EVI route within the EVPN, where the AD EVI route includes that Ethernet tag ID is 200 (i.e., EVPN Local ID), Tree ID is 300, Tree trunk set 0, Tree branch set 1, and Tree leaf set 0.

It can be understood that the AD EVI route also carries other fields, and the other fields are configured according to the current actual networking according to the existing EVPN protocol, and are not limited herein.

And a route receiving process:

and the device B receives the AD EVI route sent by the device A. Due to the locally configured Insert-Tree functionality, the B-device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the B device matches whether the Ethernet tag ID (100) included in the AD EVI route is consistent with the locally configured Remote ID (100). And if the matching is consistent, the B device identifies the Tree trunk and the Tree branch included in the AD EVI route. If the Tree trunk is set to 1 and the Tree branch is set to 0, the B device determines that the AD EVI routing source is sent by the a device configured with the VPWS service, and the B device does not need to check the Tree leaf. And B equipment establishes a PW with the A equipment according to the AD EVI route, wherein the outgoing direction of the PW is the A equipment.

And the device A receives the AD EVI route sent by the device B. Due to the locally configured Insert-Tree functionality, the a device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the B device matches whether the Ethernet tag ID (200) included in the AD EVI route is consistent with the locally configured Remote ID (200). And if the matching is consistent, the A device identifies the Tree trunk and the Tree branch included in the AD EVI route. If the Tree trunk is set to 0 and the Tree branch is set to 1, the a device determines that the AD EVI route source is sent by the B device configured with the VPLS service. The a device identifies Tree leaf. If the Tree leaf is set to be 0, the A device determines that the ESI is not configured for the Tree ID by the VPLS in the B device, and the A device does not locally need to respond to the AD ES route to form a plurality of PWs reaching the B device. And the equipment A establishes a PW with the equipment B according to the AD EVI route, and the outgoing direction of the PW is the equipment B.

And (3) flow forwarding process:

the equipment orientation A is as follows:

the A device receives the service message through an AC1 port, and performs point-to-point forwarding according to the VPWS service logic. And the device A forwards the service message to a PW bound with an AC1 port, wherein the outgoing direction of the PW is the device B.

And B, the equipment receives the service message through the PW. B equipment searches whether an AC port configuration designated forwarding function exists in the local VPLS service. If yes, sending a service message to the AC port; if not, searching the MAC address table of the local VPLS service according to the destination MAC included in the service message. If the MAC address table entry is found, unicast forwarding is carried out according to an output interface included in the MAC address table entry; otherwise, broadcasting is carried out on all AC ports in the local VPLS service.

B, device direction:

the B device receives the service message through an AC2 port, and the AC2 is configured with a designated forwarding function. And the device B forwards the service message to the PW bound with the AC2 port.

The B equipment receives the service message through an AC3 port/AC 4 port, and the designated forwarding function is not configured on the AC3 port/AC 4 port. The process of forwarding the service message by the device B according to the existing EVPN VPLS networking is executed, and the repeated description is not repeated again.

And the device A receives the service message through the PW and forwards the service message to the AC port bound with the PW.

The following describes in detail a method for implementing different network interfacing under EVPN provided in the embodiment of the present application. Referring to fig. 4, fig. 4 is a networking schematic diagram of different networking interfaces under EVPN according to another embodiment of the present application.

In fig. 4, XCG is configured in a device and VPWS service is configured within XCG. The VPWS service is configured with an EVPN Local ID of 100, a Remote ID of 200, an Insert-Tree function and a specified Tree ID of 300.

And configuring the VSI in the B1 equipment, and configuring VPLS service in the VSI. An EVPN Local ID is configured to be 200, a Remote ID is configured to be 100, an Insert-Tree function is configured in the VPLS service, and a Tree ID is designated to be 300. The B1 device specifies ESI to be 1.2.3.4.5 for Tree ID, specifies mode to be multi-active mode, configures specified forwarding function for AC2 port, configures AC3 port, and configures no specified forwarding function for AC4 port.

The B1 device generates and sends an AD EVI route within the EVPN, where the AD EVI route includes Ethernet tag ID of 200 (i.e., EVPN Local ID), Tree ID of 300, Tree trunk set 0, Tree branch set 1, Tree leaf set 1, ESI of 1.2.3.4.5, EVPN L2 attribute Control flag (Control Flags) of 0x 2.

The B1 device generates and sends an AD ES route within the EVPN, including ESI of 1.2.3.4.5 with ESI Flag 0.

Similarly, the B2 device configures the VSI and configures the VPLS service within the VSI. An EVPN Local ID is configured to be 200, a Remote ID is configured to be 100, an Insert-Tree function is configured in the VPLS service, and a Tree ID is designated to be 300. The B1 device specifies ESI to be 1.2.3.4.5 for Tree ID, specifies mode to be multi-active mode, configures specified forwarding function for AC1 port, and configures no specified forwarding function for AC2 port and AC3 port.

The B2 device generates and sends an AD EVI route within the EVPN, where the AD EVI route includes Ethernet tag ID of 200 (i.e., EVPN Local ID), Tree ID of 300, Tree trunk set 0, Tree branch set 1, Tree leaf set 1, ESI of 1.2.3.4.5, EVPN L2 attribute Control Flags of 0x 2.

The B2 device generates and sends an AD ES route within the EVPN, including ESI of 1.2.3.4.5 with ESI Flag 0.

It can be understood that the AD EVI route and the AD ES route also carry other fields, and the other fields are configured according to the current actual networking according to the existing EVPN protocol, and are not limited herein.

And a route receiving process:

the route of EVPN transmitted by the device a identifying the device B1 will be described as an example. And the A device receives the AD EVI route and the AD ES route transmitted by the B1/B2 device. Due to the locally configured Insert-Tree functionality, the a device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the A device matches whether the Ethernet tag ID (200) included in the AD EVI route is consistent with the locally configured Remote ID (200). And if the matching is consistent, the A device identifies the Tree trunk and the Tree branch included in the AD EVI route. If the Tree trunk is set to 0 and the Tree branch is set to 1, the a device determines that the AD EVI route source is sent by the B1 device configured with the VPLS service. The a device identifies Tree leaf. If the Tree leaf is set to 1, the A device determines that the ESI is configured for the VPLS service in the B1 device as the Tree ID, and the A device continues to identify the ESI and the ESI mark included in the AD ES route. If the AD EVI route includes the same ESI as the AD ES route and the ESI Flag is a multi-alive Flag0, then the A device determines that B1/B2 forms a multi-homed membership group. And the device A establishes the PW according to the AD EVI route, the AD ES route and the B1/B2 device respectively, the outgoing directions of the two PWs are B1/B2 devices respectively, and the two PWs form equivalent PWs.

It is understood that the procedures of AD EVI routing and AD ES routing sent by the a device to the B2 device are the same as those of AD EVI routing and AD ES routing sent by the a device to the B1 device, and will not be repeated here.

The explanation will be given by taking an example in which the B1 device identifies an EVPN-like route transmitted by the a device. The B1 device receives the AD EVI route sent by the a device. Due to the locally configured Insert-Tree functionality, the B1 device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the B1 device matches whether the Ethernet tag ID (100) included in the AD EVI route is consistent with the locally configured Remote ID (100). If the matching is consistent, the B1 device identifies the Tree trunk and the Tree branch included in the AD EVI route. If the Tree trunk is set to 1 and the Tree branch is set to 0, the B1 device determines that the AD EVI routing source is sent by the a device configured with the VPWS service, and the B1 device does not need to check the Tree leaf. And the B1 equipment establishes a PW with the A equipment according to the AD EVI route, and the outgoing direction of the PW is the A equipment.

The explanation will be given taking an example in which the B1 device recognizes an EVPN-like route transmitted by the B2 device. The B1 device receives the AD EVI route and the AD ES route transmitted by the B2 device. Due to the locally configured Insert-Tree functionality, the B1 device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the B1 device matches whether the Ethernet tag ID (200) included in the AD EVI route is consistent with the locally configured Remote ID (100). If the matching is not consistent, but the Ethernet tag ID (200) included in the AD EVI route is consistent with the locally configured Ethernet tag ID (200), the B1 device identifies the Tree trunk and the Tree bridge included in the AD EVI route. If the Tree trunk is set to 0 and the Tree branch is set to 1, the B1 device determines that the AD EVI route source is sent by the B2 device configured with VPLS service. The B1 device identifies a Tree leaf. If the Tree leaf is set to be 1, the B1 device determines that the VPLS service in the B2 device is Tree ID configuration ESI, and meanwhile, because the ESI is consistent with ESI specified by the Tree ID of the B1 device, the B1 device determines that the B2 device belongs to the same multi-homing member group as the self-homing member group. The B1 device continues to identify the ESI included in the AD ES route and the ESI flag. If the ESI included in the AD EVI route is the same as the ESI included in the AD ES route, and the ESI mark is a multi-activity Flag0, the B1 device establishes a bypass PW with the B2 device according to the AD EVI route and the AD ES route, and the exit direction of the bypass PW is the B2 device. And the Bypass PW is used for bypassing the service message to the Bypass PW when the local AC port fails, and the service message is forwarded to the CE/far end by the other multi-homing member. The default state of the Bypass PW is a Block state, and when a local AC port fails, the Block state is switched to an Up state.

It can be understood that the procedure of the B2 device receiving the AD EVI route and the AD ES route sent by the a device and the B1 device is the same as the procedure of the AD EVI route and the AD ES route sent by the B1 device to the a device and the B2 device, and will not be repeated here.

Note that when the Tree ID is designated as single alive mode, the AD ES route includes an ESI Flag of single alive Flag 1. After the ESI mark of the device A is identified as a single active mark Flag1, PWs are respectively established with a device B1/B2, the outgoing directions of the two PWs are respectively a device B1/B2, and the two PWs form a main PW and a standby PW.

And (3) flow forwarding process:

the equipment orientation A is as follows:

the A device receives the service message through an AC1 port, and performs point-to-point forwarding according to the VPWS service logic. And the A equipment forwards the service message to an equivalent PW bound with an AC1 port, wherein the outgoing direction of the equivalent PW is B1/B2 equipment.

And the B1/B2 equipment receives the service message through the PW. The B1/B2 device looks up whether there is an AC port configuration specific forwarding function within the local VPLS traffic. If yes, sending a service message to the AC port; if not, searching the MAC address table of the local VPLS service according to the destination MAC included in the service message. If the MAC address table entry is found, unicast forwarding is carried out according to an output interface included in the MAC address table entry; otherwise, broadcasting is carried out on all AC ports in the local VPLS service.

B, device direction:

the B1/B2 equipment receives the service message through an AC2 port, and the AC1 configures a designated forwarding function. And the device B forwards the service message to the equivalent PW bound with the AC1 port.

The B1/B2 equipment receives service messages through an AC3 port/AC 4 port, and the AC3 port/AC 4 port is not configured with a designated forwarding function. The process of forwarding the service message by the device B1/B2 with reference to the existing EVPN VPLS network is executed, and the description is not repeated again.

And the device A receives the service message through the equivalent PW and forwards the service message to an AC1 port bound with the equivalent PW.

The following describes in detail a method for implementing different network interfacing under EVPN provided in the embodiment of the present application. Referring to fig. 5, fig. 5 is a schematic networking diagram of different networking interfaces under EVPN according to another embodiment of the present application.

In fig. 5, an a1 device configures XCG and configures VPWS service within XCG. The VPWS service is configured with an EVPN Local ID of 100, a Remote ID of 200, an Insert-Tree function and a specified Tree ID of 300. The A1 device specifies ESI 1.2.3.4.5 for Tree ID and mode multi-live mode.

The A1 device generates and sends an AD EVI route in the EVPN, wherein the AD EVI route comprises that Ethernet tag ID is 100 (namely EVPN Local ID), Tree ID is 300, Tree trunk is set to be 1, Tree branch is set to be 0, Tree leaf is set to be 0, ESI is 1.2.3.4.5, EVPN L2 attribute Control Flags is 0x 2.

The a1 device generates and sends an AD ES route within the EVPN, including an ESI of 1.2.3.4.5 with the ESI Flag being a multi-alive Flag 0.

Similarly, the A2 equipment configures XCG and configures VPWS service in XCG. The VPWS service is configured with an EVPN Local ID of 100, a Remote ID of 200, an Insert-Tree function and a specified Tree ID of 300. The A2 device specifies ESI 1.2.3.4.5 for Tree ID and mode multi-live mode.

The A2 device generates and sends an AD EVI route in the EVPN, wherein the AD EVI route comprises that Ethernet tag ID is 100 (namely EVPN Local ID), Tree ID is 300, Tree trunk is set to be 1, Tree branch is set to be 0, Tree leaf is set to be 0, ESI is 1.2.3.4.5, EVPN L2 attribute Control Flags is 0x 2.

The a2 device generates and sends an AD ES route within the EVPN, including an ESI of 1.2.3.4.5 with the ESI Flag being a multi-alive Flag 0.

And a route receiving process:

the explanation will be given by taking an example in which the B device identifies an EVPN-like route transmitted by the a1 device. And the device B receives the AD EVI route and the AD ES route transmitted by the device A1/A2. Due to the locally configured Insert-Tree functionality, the B-device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the B device matches whether the Ethernet tag ID (100) included in the AD EVI route is consistent with the locally configured Remote ID (100). And if the matching is consistent, the B device identifies the Tree trunk and the Tree branch included in the AD EVI route. If the Tree trunk is set to 1 and the Tree branch is set to 0, the B device determines that the AD EVI routing source is sent by the a1 device configured with the VPWS service, and the B device does not need to check the Tree leaf. Meanwhile, the AD EVI routing also comprises ESI, the B device determines that the VPWS service in the A1 device configures ESI for Tree ID, and the B device continuously identifies the ESI and ESI mark included in the AD ES routing. If the AD EVI route includes the same ESI as the AD ES route and the ESI Flag is a multi-alive Flag0, then the B-device determines that A1/A2 forms a multi-homed membership group. And B equipment respectively establishes the PW according to the AD EVI route, the AD ES route and the A1/A2 equipment, the outgoing directions of the two PWs are respectively A1/A2 equipment, and the two PWs form equivalent PW.

It is understood that the procedures of AD EVI routing and AD ES routing sent by the B device to the a2 device are the same as those of AD EVI routing and AD ES routing sent by the B device to the a1 device, and will not be repeated here.

The description will be made by taking an example in which the a1 device identifies an EVPN-like route transmitted by the B device. The a1 device receives the AD EVI route sent by the B device. Due to the locally configured Insert-Tree functionality, the a1 device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the A1 device matches whether the Ethernet tag ID (200) included in the AD EVI route is consistent with the locally configured Remote ID (200). If the match is consistent, the A1 device identifies the Tree trunk and the Tree branch included in the AD EVI route. If the Tree trunk is set to 0 and the Tree branch is set to 1, the a1 device determines that the AD EVI route source is sent by the B device configured with the VPLS service. The a1 device identifies Tree leaf. If the Tree leaf is set to 0, the a1 device determines that the ESI is not configured for the Tree ID by the VPLS service in the B device, and the a1 device does not locally need to respond to the AD ES route to form multiple PWs to the B device. And the A1 equipment establishes a PW with the B equipment according to the AD EVI route, and the outgoing direction of the PW is the B equipment.

The description will be made by taking as an example that the a1 device recognizes an EVPN-like route transmitted by the a2 device. The a1 device receives the AD EVI route and the AD ES route transmitted by the a2 device. Due to the locally configured Insert-Tree functionality, the a1 device matches the Tree ID (300) included in the AD EVI route with the locally configured Tree ID (300). If the matching is consistent, the A1 device matches whether the Ethernet tag ID (100) included in the AD EVI route is consistent with the locally configured Remote ID (200). If the matching is not consistent, but the Ethernet tag ID (100) included in the AD EVI route is consistent with the locally configured Ethernet tag ID (100), the A1 equipment identifies the Tree trunk and the Tree bridge included in the AD EVI route. If the Tree trunk is set to 1 and the Tree branch is set to 0, the a1 device determines that the AD EVI routing source is sent by the a2 device configured with VPWS service, and the a1 device does not need to check the Tree leaf. Meanwhile, the AD EVI routing also comprises ESI, the A1 device determines that the VPWS service in the A2 device configures ESI for Tree ID, and the A1 device continues to identify ESI and ESI marks included in the AD ES routing. If the AD EVI route includes the same ESI as the AD ES route and the ESI Flag is a multi-alive Flag0, then the A1 device determines that it forms a multi-homed membership group with the A2 device. The A1 equipment establishes bypass PW with the A1/A2 equipment according to the AD EVI route and the AD ES route, and the outgoing direction of the bypass PW is the A2 equipment. And the Bypass PW is used for bypassing the service message to the Bypass PW when the local AC port fails, and the service message is forwarded to the CE/far end by the other multi-homing member. The default state of the Bypass PW is a Block state, and when a local AC port fails, the Block state is switched to an Up state.

It is understood that the procedure of the a2 device receiving the AD EVI route and the AD ES route sent by the a1 device and the B device is the same as the procedure of the AD EVI route and the AD ES route sent by the a1 device to the B device and the a2 device, and will not be repeated here.

Note that when the Tree ID is designated as single alive mode, the AD ES route includes an ESI Flag of single alive Flag 1. After the ESI mark of the device B is identified as a single active mark Flag1, PWs are respectively established with the device A1/A2, the outgoing directions of the two PWs are respectively the device A1/A2, and the two PWs form a main PW and a standby PW.

And (3) flow forwarding process:

the equipment orientation A is as follows:

the A1/A2 equipment receives the service message through an AC1 port, and performs point-to-point forwarding according to the VPWS service logic. The A1/A2 equipment forwards the service message to an equivalent PW bound with an AC1 port, and the outgoing direction of the equivalent PW is B equipment.

B, device direction:

the B device receives the service message through an AC2 port, and the AC2 is configured with a designated forwarding function. And the device B forwards the service message to the equivalent PW bound with the AC2 port.

The A1/A2 equipment receives the service message through the equivalent PW and forwards the service message to the AC1 port bound with the equivalent PW.

Based on the same inventive concept, the embodiment of the application also provides a device for realizing different networking butt joint under the EVPN, which corresponds to the method for realizing different networking butt joint under the EVPN. Referring to fig. 6, fig. 6 is a structural diagram of an implementation apparatus for different networking docking under EVPN according to the embodiment of the present application. The apparatus is applied to a first PE in an EVPN VPLS mesh network, where the first PE interfaces with a second PE in the EVPN VPWS mesh network, a VSI is configured in the first PE, a VPLS service is configured in the VSI, and a first PW has been established between the first PE and the second PE, and the apparatus includes:

a receiving unit 610, configured to receive, through the first PW, a first service packet sent by the second PE, where the first service packet includes a first destination MAC address;

a searching unit 620, configured to search whether a first AC port configured with a specified forwarding function exists in the VSI;

a sending unit 630, configured to send the first service packet through the first AC port if the first AC port exists;

the searching unit 620 is further configured to, if the first AC port does not exist, search, according to the first destination MAC address, whether an MAC address table entry matching the first destination MAC address exists in the MAC address table in the VSI;

the sending unit 630 is further configured to, if an MAC address table entry matching the first destination MAC address exists, obtain a corresponding egress interface from the MAC address table entry, and send the first service packet through the egress interface;

the sending unit 630 is further configured to send the first service packet through all AC ports in the VSI if there is no MAC address table entry matching the first destination MAC address.

Optionally, the receiving unit 610 is further configured to receive, through a second AC port, a second service packet sent by the CE, where the second service packet includes a second destination MAC address;

the sending unit 630 is further configured to send the second service packet through a second PW bound to the second AC interface when the second AC interface has configured the specified forwarding function;

the searching unit 620 is further configured to, when the designated forwarding function is not configured at the second AC port, according to the second destination MAC address, search, in the VSI, whether an MAC address table entry matching the second destination MAC address exists in an MAC address table;

the sending unit 630 is further configured to, if an MAC address table entry matching the second destination MAC address exists, obtain a corresponding egress interface from the MAC address table entry, and send the second service packet through the egress interface;

the sending unit 630 is further configured to send the second service packet through other AC ports in the VSI except the second AC port and all PWs in the VSI if the MAC address table entry matching the second destination MAC address does not exist.

Optionally, the first PE is in a multi-homing member group, the multi-homing member group further includes a third PE, and a bypass PW has been established between the first PE and the third PE;

the sending unit 630 is further configured to send the first service packet to the third PE through the bypass PW if a third AC port indicated by the egress interface fails, so that the third PE sends the first service packet through a fourth AC port after locally finding the fourth AC port having the same ESI as the third AC port.

Optionally, the second PE is in a multi-homing membership group, the multi-homing membership group further comprises a fourth PE, and a third PW has been established between the first PE and the fourth PE;

the sending unit 630 is further configured to send the second service packet through the multiple PWs when the number of the second PW is multiple.

Optionally, the receiving unit 610 is further configured to receive a first AD EVI route sent by the second PE, where the first AD EVI route includes a first ethernet tag identifier, a first tree identifier, first trunk information, and first branch information;

the device further comprises: a comparing unit (not shown in the figure) for comparing whether the first tree identifier is the same as a second tree identifier configured in the VSI;

the comparing unit (not shown in the figure) is further configured to, if the first ethernet tag identifier and the second ethernet tag identifier configured in the VSI are the same, compare whether the first ethernet tag identifier and the second ethernet tag identifier are the same;

an identifying unit (not shown in the figure) for identifying the value of the first trunk information and the value of the first branch information if the same;

a establishing unit (not shown in the figure), configured to determine that the first AD EVI route is sent by the second PE and establish the first PW with the second PE if the value of the first trunk information is 1 and the value of the first branch information is 0.

Optionally, an XCG is configured in the second PE, and a VPWS service is configured in the XCG;

the sending unit 630 is further configured to send, in the EVPN, a second AD EVI route, where the second AD EVI route includes a third ethernet tag identifier, a third tree identifier, second trunk information, second branch information, and first leaf information, so that after the second PE receives the second AD EVI route, whether the third tree identifier is the same as a fourth tree identifier configured in the XCG is compared; if yes, comparing whether the third Ethernet tag identification is the same as a fourth Ethernet tag identification configured in the XCG; if the trunk information and the branch information are the same, identifying a value of the second trunk information and a value of the second branch information; if the value of the second trunk information is 0 and the value of the second branch information is 1, determining that the second AD EVI route is sent by the first PE, and identifying the value of the first leaf information; and if the value is 0, establishing the first PW with the first PE.

the sending unit 630 is further configured to send, in the EVPN, a third AD EVI route and a first AD ES route, where the third AD EVI route includes a fifth ethernet tag identifier, a fifth tree identifier, third trunk information, third tree branch information, second leaf information, and ESI, and the first AD ES route includes the ESI and an ESI flag, so that after the second PE receives the third AD EVI route and the first AD ES route, whether the fifth tree identifier is the same as a sixth tree identifier configured in the XCG is compared; if yes, comparing whether the fifth Ethernet label identification is the same as a sixth Ethernet label identification configured in the XCG; if the tree trunk information and the tree branch information are the same, identifying the value of the third tree trunk information and the value of the third tree branch information; if the value of the third trunk information is 0 and the value of the third branch information is 1, determining that the third AD EVI route is sent by the first PE, and identifying the value of the second leaf information; if the value is 1, identifying the value of the ESI mark, if the value is 0, determining that the first PE and the third PE form a multi-homing membership group, and respectively establishing the first PW and the fourth PW with the first PE and the third PE, wherein the first PW and the fourth PW are equivalent PWs.

Optionally, the receiving unit 610 is further configured to receive a fourth AD EVI route and a second AD ES route sent by the third PE, where the fourth AD EVI route includes a seventh ethernet tag identifier, a seventh tree identifier, fourth trunk information, fourth branch information, third leaf information, and ESI, and the second AD ES route includes the ESI and the ESI flag;

the comparing unit (not shown in the figure) is further configured to compare whether the seventh tree identifier is the same as an eighth tree identifier configured in the VSI;

the comparing unit (not shown in the figure) is further configured to, if the seventh ethernet tag identifier is the same as the eighth ethernet tag identifier configured in the VSI, compare whether the seventh ethernet tag identifier is the same as the eighth ethernet tag identifier configured in the VSI;

the identification unit (not shown in the figure) is further configured to identify a value of the fourth trunk information and a value of the fourth branch information if the trunk information is not the same as a ninth ethernet tag identifier configured in the VSI;

the identifying unit (not shown in the figure) is further configured to identify the value of the third leaf information if the value of the first trunk information is 0 and the value of the fourth branch information is 1;

the identifying unit (not shown in the figure) is also used for identifying the ESI and the value of the ESI mark if the value is 1;

the establishing unit (not shown in the figure) is further configured to establish the bypass PW with the third PE if the ESI is the same as the ESI bound by the seventh tree identifier and the value of the ESI flag is 0.

Optionally, the receiving unit 610 is further configured to receive a fifth AD EVI route and a third AD ES route sent by the second PE, where the fifth AD EVI route includes a tenth ethernet tag identifier, a ninth tree identifier, fifth trunk information, fifth branch information, and ESI, and the third AD ES route includes the ESI and the ESI flag;

the comparing unit (not shown in the figure) is further configured to compare whether the ninth tree identifier is the same as a tenth tree identifier configured in the VSI;

the comparing unit (not shown in the figure) is further configured to, if the tenth ethernet tag identifier is the same as the eleventh ethernet tag identifier configured in the VSI, compare whether the tenth ethernet tag identifier is the same as the eleventh ethernet tag identifier configured in the VSI;

the identifying unit (not shown in the figure) is further configured to identify a value of the fifth trunk information and a value of the fifth branch information if the same;

the identifying unit (not shown in the figure) is further configured to identify the ESI and the value of the ESI flag if the value of the fifth trunk information is 1 and the value of the fifth branch information is 0;

the establishing unit (not shown in the figure) is further configured to establish the first PW and the fifth PW with the second PE and the fourth PE, respectively, if the ESI is the same as the ESI included in the sixth AD EVI route and the fourth AD ES route sent by the fourth PE and the ESI flag value is 0, where the first PW and the fifth PW are equivalent PWs.

Optionally, the establishing unit (not shown in the figure) is further configured to, if the value of the ESI flag is 1, respectively establish the first PW and the fifth PW with the second PE and the fourth PE, where the first PW is a main PW and the fifth PW is a standby PW.

Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 7, including a processor 710, a transceiver 720, and a machine-readable storage medium 730, where the machine-readable storage medium 730 stores machine-executable instructions capable of being executed by the processor 710, and the processor 710 is caused by the machine-executable instructions to perform the implementation method for different networking interfaces under EVPN provided by the embodiment of the present application. The device for implementing different networking interfaces under EVPN shown in fig. 6 can be implemented by using a hardware structure of a network device shown in fig. 7.

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

The Processor 710 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; 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 710 reads the machine executable instructions stored in the machine readable storage medium 730, and the machine executable instructions cause the processor 710 itself to be able to implement and invoke the transceiver 720 to perform the implementation method of different networking interfaces under EVPN described in the embodiment of the present application.

In addition, embodiments of the present application provide a machine-readable storage medium 730, where the machine-readable storage medium 730 stores machine executable instructions, and when invoked and executed by the processor 710, the machine executable instructions cause the processor 710 itself and the invoking transceiver 720 to perform the implementation method of different networking interfacing under EVPN described in the 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 embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments 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 place, or may be distributed on a plurality of 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.

For the implementation device and the machine-readable storage medium embodiment of different networking interfacing under EVPN, the content of the related method is basically similar to that of the foregoing method embodiment, so the description is relatively simple, and the relevant points can be referred to the partial description of the method embodiment.

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 method for realizing different networking docking under EVPN is characterized in that the method is applied to a first PE in an EVPN VPLS networking, the first PE docks a second PE in the EVPN VPWS networking, a VSI is configured in the first PE, a VPLS service is configured in the VSI, and a first PW is established between the first PE and the second PE, and the method comprises the following steps:

2. The method of claim 1, further comprising:

receiving a second service message sent by the CE through a second AC port, wherein the second service message comprises a second destination MAC address;

when the second AC port is configured with the appointed forwarding function, sending the second service message through a second PW bound with the second AC port;

when the second AC port is not configured with the appointed forwarding function, according to the second destination MAC address, whether an MAC address table item matched with the second destination MAC address exists in an MAC address table or not is searched in the VSI;

if an MAC address table item matched with the second target MAC address exists, acquiring a corresponding output interface from the MAC address table item, and sending the second service message through the output interface;

and if the MAC address table item matched with the second destination MAC address does not exist, sending the second service message through other AC ports except the second AC port in the VSI and all PWs in the VSI.

3. The method of claim 1 or 2, wherein the first PE is in a multi-homed group of members, the multi-homed group of members further comprising a third PE, a bypass PW having been established between the first PE and the third PE;

after obtaining the corresponding egress interface from the MAC address table entry, the method further includes:

and if the third AC port indicated by the outgoing interface fails, sending the first service packet to the third PE through the bypass PW, so that the third PE sends the first service packet through a fourth AC port after locally finding the fourth AC port having the same ESI as the third AC port.

4. The method of claim 1 or 2, wherein the second PE is in a multihomed membership group, wherein the multihomed membership group further comprises a fourth PE, and wherein a third PW has been established between the first PE and the fourth PE;

after receiving the second service packet sent by the CE, the method further includes:

and when the number of the second PW is multiple, sending the second service message through the multiple PWs.

5. The method according to claim 1, wherein before the receiving, via the first PW, the first service packet sent by the second PE, the method further comprises:

receiving a first AD EVI route sent by the second PE, wherein the first AD EVI route comprises a first Ethernet label identification, a first tree identification, first trunk information and first branch information;

comparing whether the first tree identification is the same as a second tree identification configured in the VSI;

if so, comparing whether the first Ethernet label identification is the same as a second Ethernet label identification configured in the VSI;

if the trunk information and the branch information are the same, identifying the value of the first trunk information and the value of the first branch information;

and if the value of the first trunk information is 1 and the value of the first branch information is 0, determining that the first AD EVI route is sent by the second PE, and establishing the first PW with the second PE.

6. The method of claim 1, wherein the second PE is configured with XCG, and wherein VPWS service is configured in the XCG;

before the receiving, by the first PW, the first service packet sent by the second PE, the method further includes:

sending a second AD EVI route in the EVPN, wherein the second AD EVI route comprises a third Ethernet label identification, a third tree identification, second trunk information, second branch information and first leaf information, so that after the second PE receives the second AD EVI route, whether the third tree identification is the same as a fourth tree identification configured in the XCG is compared; if yes, comparing whether the third Ethernet tag identification is the same as a fourth Ethernet tag identification configured in the XCG; if the trunk information and the branch information are the same, identifying a value of the second trunk information and a value of the second branch information; if the value of the second trunk information is 0 and the value of the second branch information is 1, determining that the second AD EVI route is sent by the first PE, and identifying the value of the first leaf information; and if the value is 0, establishing the first PW with the first PE.

7. The method of claim 3, wherein the second PE configures XCG therein, and wherein VPWS service is configured in the XCG;

sending a third AD EVI route and a first AD ES route in the EVPN, wherein the third AD EVI route comprises a fifth Ethernet label identification, a fifth tree identification, third trunk information, third branch information, second leaf information and ESI, and the first AD ES route comprises the ESI and the ESI mark, so that after the second PE receives the third AD EVI route and the first AD ES route, whether the fifth tree identification is the same as a sixth tree identification configured in the XCG is compared; if yes, comparing whether the fifth Ethernet label identification is the same as a sixth Ethernet label identification configured in the XCG; if the tree trunk information and the tree branch information are the same, identifying the value of the third tree trunk information and the value of the third tree branch information; if the value of the third trunk information is 0 and the value of the third branch information is 1, determining that the third AD EVI route is sent by the first PE, and identifying the value of the second leaf information; if the value is 1, identifying the value of the ESI mark, if the value is 0, determining that the first PE and the third PE form a multi-homing membership group, and respectively establishing the first PW and the fourth PW with the first PE and the third PE, wherein the first PW and the fourth PW are equivalent PWs.

8. The method according to claim 7, wherein before the receiving, via the first PW, the first service packet sent by the second PE, the method further comprises:

receiving a fourth AD EVI route and a second AD ES route sent by the third PE, wherein the fourth AD EVI route comprises a seventh Ethernet label identifier, a seventh tree identifier, fourth trunk information, fourth branch information, third leaf information and ESI, and the second AD ES route comprises the ESI and the ESI mark;

comparing whether the seventh tree identification is the same as an eighth tree identification configured in the VSI;

if yes, comparing whether the seventh Ethernet label identification is the same as an eighth Ethernet label identification configured in the VSI;

if the trunk information is different from the VSI and the trunk information is the same as a ninth Ethernet label identifier configured in the VSI, identifying a value of the fourth trunk information and a value of the fourth branch information;

identifying a value of the third leaf information if the value of the first trunk information is 0 and the value of the fourth branch information is 1;

if the value is 1, identifying the ESI and the value of the ESI flag;

and if the ESI is the same as the ESI bound by the seventh tree identifier and the value of the ESI flag is 0, establishing the bypass PW with the third PE.

9. The method according to claim 4, wherein before the receiving, via the first PW, the first traffic packet sent by the second PE, the method further comprises:

receiving a fifth AD EVI route and a third AD ES route sent by the second PE, wherein the fifth AD EVI route comprises a tenth Ethernet label identifier, a ninth tree identifier, fifth trunk information, fifth branch information and ESI, and the third AD ES route comprises the ESI and the ESI mark;

comparing whether the ninth tree identification is the same as a tenth tree identification configured in the VSI;

if yes, comparing whether the tenth Ethernet label identification is the same as an eleventh Ethernet label identification configured in the VSI;

if the tree trunk information is the same as the tree trunk information, identifying a value of the fifth tree trunk information and a value of the fifth branch information;

identifying the ESI and the value of the ESI flag if the value of the fifth trunk information is 1 and the value of the fifth branch information is 0;

if the ESI is the same as the ESI included in a sixth AD EVI route and a fourth AD ES route sent by a fourth PE, and the value of the ESI flag is 0, the first PW and the fifth PW are respectively established with the second PE and the fourth PE, and the first PW and the fifth PW are equivalent PWs.

10. The method of claim 9, further comprising:

if the ESI flag value is 1, establishing the first PW and the fifth PW with the second PE and the fourth PE respectively, wherein the first PW is a main PW, and the fifth PW is a standby PW.

11. An apparatus for implementing different networking interfaces under EVPN is applied to a first PE in an EVPN VPLS networking, where the first PE interfaces with a second PE in an EVPN VPWS networking, a VSI is configured in the first PE, a VPLS service is configured in the VSI, and a first PW has been established between the first PE and the second PE, and the apparatus includes: