CN113114553B

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

Info

Publication number: CN113114553B
Application number: CN202110439612.0A
Authority: CN
Inventors: 谢岢洋
Original assignee: New H3C Security Technologies Co Ltd
Current assignee: New H3C Security Technologies Co Ltd
Priority date: 2021-04-23
Filing date: 2021-04-23
Publication date: 2022-04-01
Anticipated expiration: 2041-04-23
Also published as: CN113114553A

Abstract

The application provides a method and a device for realizing different networking docking under an EVPN, 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, and the method comprises the following steps: receiving a first service message sent by the second PE, wherein the first service message comprises a first destination address and a first destination MAC address, and the first destination address comprises a function field; when the SID type of the first destination address is a first SID type and the function field indicates the VSI, searching a unicast forwarding table in the VSI according to the first destination MAC address; and if the unicast forwarding table does not have the unicast forwarding table item matched with the first destination MAC address, broadcasting the first service message at 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

The SRv6-TE strategy is a Segment Routing Traffic Engineering strategy (SR-TE Policy) based on IPv6 Segment Routing (SR), which provides a flexible forwarding path selection method and can meet different forwarding requirements of users. When a plurality of paths exist between a source node and a destination node in the SR network, the SRv6-TE strategy is reasonably utilized to select a forwarding path, which not only facilitates the management and planning of the network by an administrator, but also can effectively reduce the forwarding pressure of network equipment.

An EVPN VPLS group Network is formed by configuring a Virtual Private LAN Service (VPLS) under an Ethernet Virtual Private Network (EVPN for short). 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. EVPN VPLS over SRv6 means that EVPN VPLS service is carried through an IPv6 SR tunnel, user two-layer data is transparently transmitted through an IPv6 network, and a user network passes through an IPv6 network to establish point-to-multipoint connection.

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. The EVPN VPWS over SRv6 refers to the fact that an EVPN VPWS service is borne through an IPv6 SR tunnel, user two-layer data are transmitted transparently through an IPv6 network, and the fact that a user network passes through an IPv6 network to establish point-to-point connection is achieved.

The existing VPWS 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 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.

In the process of interfacing the EVPN VPWS networking to the EVPN VPLS networking, as shown in fig. 1, fig. 1 is a schematic diagram of interfacing the EVPN VPWS networking to the EVPN VPLS networking. In fig. 1, EVPN VPWS over SRv6 services are configured in both a1 and a 2; EVPN VPLS over SRv6 services are configured in the B1, the B2, the C1 and the C2, and after configuration is completed, flow intercommunication among the host 1, the host 2 and the host 3 is achieved.

Wherein, A1 and A2 are each a multi-homing member, B1 and B2 are each a multi-homing member, and C1 and C2 are each a multi-homing member. In the foregoing multi-networking docking, the redundant backup mode of all the multi-homing members is the multi-active mode.

Aiming at a multi-active mode of a multi-homing member in an EVPN VPLS networking, broadcast traffic is discarded at an Access Circuit (AC) port which has the role of a Backup Designated Forwarder (BDF). For example, in the multi-active mode, the host 3 accesses C1 and C2 through the aggregation port, the broadcast traffic load is shared to C1 and C2, and C1 and C2 need to broadcast on all Srv6 tunnels respectively. Broadcast traffic arrives at B1 and B2. If the AC ports of B1 and B2 both forward broadcast traffic, host 2 will receive duplicate broadcast traffic. Thus, broadcast traffic needs to be dropped at the AC port, which is BDF in role.

For multi-active mode of multi-homed members in EVPN VPWS networking, traffic cannot be dropped at an AC portal with a BDF role. For EVPN VPWS networking, traffic does not distinguish between broadcast or unicast. For example, in the multi-active mode, the host 1 accesses a1 and a2 through the aggregation port, and the traffic load is shared to a1 and a 2. In A1, the SRv6 tunnel from A1 to B1 and the SRv6 tunnel from A1 to B2 are equivalent tunnels, and the traffic can be load-shared to B-1 and B-2 through the equivalent tunnels. If the AC ports with BDF roles in B1 and B2 drop traffic at this time, half of the traffic will be dropped, increasing the traffic risk.

Therefore, in the multi-network docking, for a multi-active mode of a multi-homing member, an EVPN VPLS networking and an EVPN VPWS networking, the traffic processing operation at the AC with the BDF role is contradictory, and the same AC port cannot simultaneously meet the forwarding requirement of the multi-network docking.

Disclosure of Invention

In view of this, the present application provides a method and an apparatus for implementing different network interfacing under EVPN, so as to solve the problem that the same AC port in the existing multi-network interfacing cannot simultaneously meet the forwarding requirement of the multi-network interfacing.

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, and a VSI is configured in the first PE, and the method includes:

receiving a first service message sent by the second PE, wherein the first service message comprises a first destination address and a first destination MAC address, and the first destination address comprises a function field;

when the SID type of the first destination address is a first SID type and the function field indicates the VSI, searching a unicast forwarding table in the VSI according to the first destination MAC address;

and if the unicast forwarding table does not have the unicast forwarding table item matched with the first destination MAC address, broadcasting the first service message at 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, and a VSI is configured in the first PE, and the apparatus includes:

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

a searching unit, configured to search, when a SID type of the first destination address is a first SID type and the functional field indicates the VSI, a unicast forwarding table in the VSI according to the first destination MAC address;

a sending unit, configured to broadcast the first service packet at all AC ports in the VSI if a unicast forwarding table entry matching the first destination MAC address does not exist in the unicast forwarding table.

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 implementing different networking docking under EVPN provided by the present application, the first PE receives the first service packet sent by the second PE, where the first service packet includes the first destination address and the first destination MAC address, and the first destination address includes the function field. And when the SID type of the first destination address is the first SID type and the function field indicates the VSI, the first PE searches the unicast forwarding table in the VSI according to the first destination MAC address. And if the unicast forwarding table does not have the unicast forwarding table item matched with the first destination MAC address, the first PE broadcasts the first service message at all AC ports in the VSI.

Thus, a first PE in the EVPN VPLS network can be connected with a second PE in the EVPN VPWS network, and when receiving a non-unicast service message sent by the second PE, the non-unicast service message can be broadcasted through all AC ports in the VSI. The problem of the same AC mouth can't satisfy the forwarding demand that multiunit network docked simultaneously in the current multiunit network butt joint is solved. The forwarding requirements of the EVPN VPLS networking and the EVPN VPWS networking can be met by the first PE at the same time.

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 structural diagram of an implementation apparatus for different networking docking under EVPN provided in the 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 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, where the first service packet includes a first destination address and a first destination MAC address, and the first destination address includes a function field.

Specifically, a VPLS service is configured in a first service Provider network Edge (PE for short), and a VPWS service is configured in a second PE. A tunnel has been established SRv6 between the first PE and the second PE. Through the SRv6 tunnel, the first PE receives a first service packet sent by the second PE, where the first service packet includes a first destination address and a first destination Media Access Control (MAC) address.

The first destination address is specifically in the form of a Segment Identifier (SID). The SID is represented in the form of an IPv6 address, but does not correspond to an interface address on any device. The first destination address includes a locator (locator) field and a function (function) field. The positioning field is used for identifying the routing capability and guiding the message to be forwarded at the designated node. The location field is unique within the SR domain. The function field is used to identify a network function of the device, such as forwarding a message, performing a specific service, and the like. And after receiving the message, the designated node in the SR domain executes related operations according to the functional field.

Further, a process of generating a destination address of at least one SID type is included before this step.

A Virtual Switch Instance (VSI) is configured in the first PE, and the VSI is a Virtual Instance that provides a layer two switching service for a VPLS Instance in the PE. The VSI may be considered as a virtual switch in the PE that has all the functions of a traditional ethernet switch, including source MAC address learning, MAC address aging, flooding, etc. And forwarding the two-layer data message in the VPLS instance is realized through the VSI.

Within the VSI, a first PE generates a first destination address including a first SID type, the first SID type being an end.dx2 type. The first destination address includes a function field that points to the VSI. Wherein, the SID of END.DX2 type identifies the SID of the two-layer cross-connect and is used for identifying an endpoint. And the forwarding action corresponding to the SID of the END.DX2 type is to remove the IPv6 message header and the extension header thereof and forward the rest messages to the outgoing interface corresponding to the SID. Dx2 type SID is used for EVPN VPWS networking scenarios.

In the embodiment of the present application, since the first PE is configured with the VPLS service, it can be understood that the first PE also generates destination addresses of other SID types, for example, SID of end.d.d 2m type and SID of end.d 2u type. The process of generating the end.dt2m type SID and the end.dt2u type SID by the first PE is the same as the process of generating the end.dt2m type SID and the end.dt2u type SID by the PE in the existing EVPN VPLS network, and will not be described again here.

Wherein, SID of END.DT2M type represents SID of two-layer cross-connect and broadcast flooding for identifying an endpoint. And the forwarding action corresponding to SID of the END.DT2M type is to remove the IPv6 message header and the extension header thereof and broadcast and flood the rest messages in the broadcast domain. And the SID of the DT2M type is used for the BUM flow scene of the EVPN VPLS networking.

A SID of dt2u type represents a SID of a two-layer cross-connect and unicast MAC table lookup function for identifying an endpoint. And the forwarding action corresponding to the SID of the END.DT2U type is to remove the IPv6 message header and the expansion header thereof, look up the MAC table through the destination MAC address included in the residual message, and forward the residual message to the corresponding outgoing interface according to the MAC table item. SID of DT2U type is used for unicast traffic scene of EVPN VPLS networking.

In an embodiment of the present application, the first PE may also establish a connection with a third PE. And configuring VPLS service in the third PE. That is, the first PE and the third PE are both located in the EVPN VPLS networking, the second PE is located in the EVPN VPWS networking, and the first PE serves as a device for interfacing the EVPN VPLS networking and the EVPN VPWS networking.

It should be noted that, in this embodiment of the present application, each PE of the first PE, the second PE, and the third PE may be a multi-homing member, that is, the first PE includes two PEs, the two PEs form a pair-homing member group, each PE is connected to the host, and meanwhile, each PE is fully connected to each PE included in the second PE and the third PE. The second PE comprises two PEs, the two PEs form a pair of attribution member groups, each PE is connected with the host, and meanwhile, each PE is fully connected with each PE included by the first PE. The third PE comprises two PEs, the two PEs form a pair of attribution member groups, each PE is connected with the host, and meanwhile, each PE is fully connected with each PE included by the first PE.

It is understood that, in the embodiment of the present application, each of the first PE, the second PE, and the third PE may also be a non-multihomed member, or some PEs may be multihomed members, and some PEs may be non-multihomed members. Each PE may perform the corresponding steps as described in the embodiments of the present application.

Furthermore, after the first PE generates the destination address of at least one SID type, the first PE generates different EVPN routes according to different EVPN networks to which each SID type is applicable.

The first PE generates a first Ethernet Auto-discovery Route (also called AD Route), which is a kind of EVPN Route. The first Ethernet auto-discovery route includes a first destination address of the first SID type and a first Ethernet tag identification (Ethernet tag ID). Wherein the first ethernet tag identifies a first local service identification (service ID) of the storage configuration.

It will be appreciated that the first ethernet auto-discovery route includes a number of other fields, such as: RD, RT, encapsulation type, etc., and other fields are configured according to the current networking form and the existing EVPN protocol, and will not be repeated here. The first ethernet auto-discovery route includes two subclass routes, one for AD EVI and one for AD ES. The aforementioned first ethernet auto-discovery route is specifically an AD EVI route.

The first PE transmits the first ethernet auto-discovery route within the EVPN, i.e., within the EVPN VPLS networking and the EVPN VPWS networking. The second PE and the third PE can both receive the first Ethernet auto-discovery route. And the third PE is used as a device for configuring the VPLS, and acquires the first destination address and the first Ethernet label identification from the first Ethernet automatic discovery route after receiving the first Ethernet automatic discovery route. The third PE determines that the SID type of the first destination address cannot be processed by itself and the content stored in the first ethernet tag identifier cannot be processed by itself, and then the third PE does not generate the host route and the forwarding table entry according to the first ethernet auto discovery route. The third PE stores the first ethernet auto-discovery route.

And after receiving the first Ethernet automatic discovery route, the second PE acquires a first destination address and a first Ethernet label identifier from the first Ethernet automatic discovery route. The second PE identifies the SID type of the first destination address as a first SID type and the first Ethernet label mark as a first local service mark. The second PE acquires the configured first remote service identification. The second PE compares the first local service identification with the first remote service identification to see if they are consistent. If so, the second PE establishes SRv6 a tunnel with the first PE according to the first destination address of the first SID type.

It can be understood that the second PE further establishes a binding relationship between the AC port accessing the local host and the SRv6 tunnel, so that, after subsequently receiving the service packet sent by the host through the AC port, the service packet is sent to the first PE through the corresponding SRv6 tunnel according to the binding relationship.

It should be noted that, if the first PE and the second PE are both the multihomed member group, each PE in the first PE sends the first ethernet auto-discovery route in the EVPN, and establishes SRv6 tunnels with each PE in the second PE in the foregoing manner.

Further, the second PE also generates an ethernet auto-discovery route, which may be specifically the second ethernet auto-discovery route. The second ethernet auto-discovery route includes a second destination address of the first SID type and a second ethernet tag identification. Wherein the second Ethernet tag identity stores a second local service identity configured by the second PE.

It is understood that the second ethernet auto-discovery route includes a plurality of other fields that are identical to the plurality of other fields included in the first ethernet auto-discovery route, but are configured according to the current networking form and the existing EVPN protocol specification, and will not be repeated here.

The second PE sends a second ethernet auto-discovery route within the EVPN. The first PE and the third PE can both receive the second Ethernet auto-discovery route. And the third PE is used as a device for configuring the VPLS, and acquires a second destination address and a second Ethernet label identification from the received second Ethernet automatic discovery route. The third PE determines that the SID type of the second destination address cannot be processed by itself and the content stored in the second ethernet tag identifier cannot be processed by itself, so that the third PE does not generate the host route and the forwarding table entry according to the second ethernet auto-discovery route. The third PE stores the second ethernet auto-discovery route.

And after receiving the second Ethernet automatic discovery route, the first PE acquires a second destination address and a second Ethernet label identifier from the second Ethernet automatic discovery route. The first PE identifies the SID type of the second destination address as the first SID type, and the second Ethernet label identification is the second local service identification configured by the second PE. The first PE acquires the configured second remote service identification. The first PE compares whether the second local service identification is consistent with the second remote service identification. If so, the first PE establishes SRv6 a tunnel with the second PE according to the second destination address of the first SID type.

It can be understood that, the first PE further establishes a binding relationship between the AC port accessing the local host and the SRv6 tunnel, so that, after subsequently receiving the service packet sent by the host through the AC port, the service packet is sent to the second PE through the corresponding SRv6 tunnel according to the binding relationship.

Further, since the first PE configures VPLS service, according to the existing EVPN protocol, the first PE also generates an Ethernet auto discovery Route, a MAC/IP Advertisement Route (MAC/IP Advertisement Route), and an Inclusive Multicast Ethernet label Route (also called IMET Route).

For example, the MAC/IP issue route generated by the first PE includes a destination address of the second SID type, which is end.dt2u type. The IMET route generated by the first PE includes a destination address of a third SID type, the third SID type being an END.DT2M type.

Of course, in this embodiment of the present application, the first PE further generates an Ethernet auto-discovery route, which includes a destination address of the second SID type and an Ethernet tag identification (Ethernet tag ID). Wherein the Ethernet tag identification stores the VLAN ID of the AC port in the first PE.

The first PE sends the Ethernet automatic discovery route, the MAC/IP release route and the IMET route in the EVPN. The EVPN routes may be received by both the second PE and the third PE. It can be understood that the second PE and the third PE may process the received corresponding EVPN routes according to the service configured by the second PE and the third PE according to the specification of the existing EVPN protocol, and generate the host route and the forwarding table entry. And the EVPN route which can not be processed by the routing table is stored locally.

In a similar way, the second PE and the third PE generate and transmit corresponding EVPN routes within the EVPN according to the self-configured service, so that the PE receiving the EVPN route processes the received corresponding EVPN route according to the self-configured service, and generates a host route and a forwarding table entry. And the EVPN route which can not be processed by the routing table is stored locally.

The first PE, the second PE, and the third PE generate and transmit corresponding EVPN routes within an EVPN according to a service configured by the first PE, the second PE, and the third PE, which are all the prior art, and are not repeated here.

As shown in fig. 1, fig. 1 is a schematic diagram of EVPN VPWS networking interfacing EVPN VPLS networking. In fig. 1, EVPN VPWS over SRv6 services are configured in both a1 and a 2; EVPN VPLS over SRv6 services are configured in the B1, the B2, the C1 and the C2, and after configuration is completed, flow intercommunication among the host 1, the host 2 and the host 3 is achieved.

Wherein, A1 and A2 are each a multi-homing member, B1 and B2 are each a multi-homing member, and C1 and C2 are each a multi-homing member. In the foregoing multi-networking docking, the redundant backup mode of all the multi-homing members is the multi-active mode. The B1, B2 devices may be the first PE, a1, a2 devices may be the second PE, C1, C2 devices in the foregoing embodiments may be the third PE in the foregoing embodiments.

The following description will be given by taking B1 as an example. VSI 1 is configured in B1, and within VSI 1, B1 generates a first destination address including a first SID type, which is an end.dx2 type. The first destination address includes a function field that points to the VSI 1.

B1 generates different EVPN routes according to different EVPN networks to which each SID type is applicable after B1 generates a first destination address of the first SID type.

B1 generates a first ethernet auto-discovery route, a type of EVPN route. The first ethernet auto-discovery route includes a first destination address of a first SID type and a first ethernet tag identification. Wherein the first Ethernet tag identifies a first local service identity of the storage configuration.

B1 sends the first ethernet auto-discovery route within EVPN, i.e., within EVPN VPLS networking and EVPN VPWS networking. A1, a2, C1, C2 may all receive the first ethernet auto discovery route. C1 and C2 (taking C1 as an example) are devices that configure VPLS service, and obtain the first destination address and the first ethernet tag identifier from the first ethernet auto-discovery route after receiving the first ethernet auto-discovery route. C1 determines that the SID type of the first destination address cannot be processed by itself and the content stored in the first ethernet tag identifier cannot be processed by itself, then C1 will not generate the host route and the forwarding table entry according to the first ethernet auto-discovery route. C1 stores the first ethernet auto-discovery route.

After receiving the first ethernet auto-discovery route, a1 and a2 (taking a1 as an example) obtain a first destination address and a first ethernet tag identifier. A1 identifies the SID type of the first destination address as the first SID type and the first ethernet tag as the first local service identifier. A1 obtains the configured first remote service identity. A1 compares whether the first local service identity is consistent with the first remote service identity. If so, A1 establishes SRv6 a tunnel with B1 based on the first destination address of the first SID type.

It can be understood that the a1 also establishes a binding relationship between the AC port accessing the local host and the SRv6 tunnel, so that, after subsequently receiving the service packet sent by the host through the AC port, the service packet is sent to the B1 through the corresponding SRv6 tunnel according to the binding relationship.

Similarly, a2 and B1 establish SRv6 tunnels, and a1, a2 and B2 also establish SRv6 tunnels. The tunnel SRv6 established by the A1 and the B1 and B2 forms an equivalent path. Subsequently, when a1 sends the traffic packet of host 1, the traffic packet may be sent to B1 and B2 through two tunnels SRv 6.

Through the established SRv6 tunnel, B1 receives the first traffic packet sent by a1, where the first traffic packet includes a first destination address and a first destination MAC address.

Further, a1 also generates an ethernet auto-discovery route, which may be specifically the second ethernet auto-discovery route. The second ethernet auto-discovery route includes a second destination address of the first SID type and a second ethernet tag identification. Wherein the second ethernet tag identification stores a second local service identification of the a1 configuration.

A1 sends a second ethernet auto discovery route within EVPN. Both B1, C1 may receive the second ethernet auto discovery route. C1, as a device for configuring VPLS service, obtains the second destination address and the second ethernet tag identifier from the second ethernet auto-discovery route after receiving the second ethernet auto-discovery route. C1 determines that the SID type of the second destination address cannot be processed by itself and the content stored in the second ethernet tag identifier cannot be processed by itself, then C1 will not generate the host route and the forwarding table entry according to the second ethernet auto-discovery route. C1 stores the second ethernet auto discovery route.

B1 obtains the second destination address and the second ethernet tag identification from the second ethernet auto-discovery route after receiving the second ethernet auto-discovery route. The B1 identifies the SID type of the second destination address as the first SID type, and the second Ethernet label identifier as the second local service identifier configured by A1. B1 obtains the configured second remote service identity. B1 compares whether the second local service identity is consistent with the second remote service identity. If so, B1 establishes SRv6 tunnel with A1 based on the second destination address of the first SID type.

It can be understood that the B1 also establishes a binding relationship between the AC port accessing the local host and the SRv6 tunnel, so that, after subsequently receiving the service packet sent by the host through the AC port, the service packet is sent to the a1 through the corresponding SRv6 tunnel according to the binding relationship.

Further, since B1 is configured with VPLS traffic, the first PE also generates ethernet auto-discovery routes, MAC/IP distribution routes, and IMET routes in accordance with the existing EVPN protocol.

For example, the MAC/IP distribution route generated by B1 includes a destination address of the second SID type, which is end.dt2u type. The IMET route generated by B1 includes a destination address of a third SID type, which is end.d 2m type.

Of course, in the embodiment of the present application, B1 also generates an ethernet auto-discovery route including the destination address of the second SID type and the ethernet tag identification. Where the ethernet tag identifies the VLAN ID of the AC port in storage B1.

B1 sends the ethernet auto-discovery route, MAC/IP issue route, and IMET route described above within EVPN. Both a1 and C1 may receive the EVPN route. It is understood that a1 and C1 can process the received corresponding EVPN route according to the service configured by themselves and generate the host route and forwarding table entry according to the specification of the existing EVPN protocol. And the EVPN route which can not be processed by the routing table is stored locally.

Similarly, the a1 and the C1 generate and transmit corresponding EVPN routes in the EVPN according to the self-configured services, so that the PE receiving the EVPN routes processes the received corresponding EVPN routes according to the self-configured services, and generates the host route and the forwarding table entry. And the EVPN route which can not be processed by the routing table is stored locally.

The above-mentioned a1, B1, C1 generate and transmit the corresponding EVPN route within the EVPN according to the self-configured traffic, which are all the prior art, and will not be repeated here.

Step 220, when the SID type of the first destination address is a first SID type and the functional field indicates the VSI, searching a unicast forwarding table in the VSI according to the first destination MAC address.

Specifically, according to the description of step 220, after receiving the first service packet, the first PE obtains the first destination address and the first destination MAC address.

The first PE identifies the SID type and the function field of the first destination address, and if the SID type of the first destination address is the first SID type and the function field indicates the VSI of the first PE, the first PE searches the unicast forwarding table in the VSI according to the first destination MAC address.

It will be appreciated that the unicast forwarding table may be embodied as a MAC forwarding table, stored within the VSI. The MAC forwarding table includes a destination MAC address and an egress interface, which is an AC port of the first PE.

According to the foregoing example, after receiving the first service packet, B1 obtains the first destination address and the first destination MAC address therefrom. B1 identifies the SID type and function field of the first destination address, if the SID type of the first destination address is the first SID type and the function field indicates VSI 1, B1 searches the unicast forwarding table in VSI according to the first destination MAC address.

Step 230, if there is no unicast forwarding table entry matching the first destination MAC address in the unicast forwarding table, broadcasting the first service packet at all AC ports in the VSI.

Specifically, according to the description in step 230, if the unicast forwarding table has a unicast forwarding table entry matching the first destination MAC address, the first PE determines that the first service packet is a BUM traffic. The first PE broadcasts a first service message at all AC ports in the VSI.

And if the unicast forwarding table item matched with the first destination MAC address exists in the unicast forwarding table, the first PE determines that the first service message is unicast flow. The first PE acquires an output interface from the unicast forwarding table entry. And through the output interface, the first PE forwards the first service message to a host machine accessed to the output interface.

It should be noted that, according to the characteristics of the EVPN VPWS networking, when the second PE sends the service packet to the first PE, the second PE does not distinguish whether the service packet is BUM traffic or unicast traffic. After receiving the service message sent by the second PE, the first PE realizes unicast forwarding or broadcast flooding of the service message in the EVPN VPWS network on the premise of not considering the role of the AC port of the first PE according to the unicast forwarding table configured in the VSI.

Meanwhile, the first PE still processes the service message in the EVPN VPLS network according to the existing EVPN protocol. The same AC port can meet the forwarding requirement of the multi-group network docking at the same time.

According to the foregoing example, if there is a unicast forwarding table entry matching the first destination MAC address in the unicast forwarding table, B1 determines that the first service packet is broadcast & unknown unicast & multicast (BUM) traffic. B1 broadcasts the first traffic message at all AC ports within VSI 1.

If a unicast forwarding table entry matching the first destination MAC address exists in the unicast forwarding table, B1 determines that the first service packet is unicast traffic. B1 obtains the outgoing interface, i.e. the corresponding AC port, from the unicast forwarding table entry. Through the AC port, B1 forwards the first traffic packet to the host accessing the AC port.

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. 3, fig. 3 is a structural diagram of an implementation apparatus for different networking docking under EVPN according to an embodiment of the present application. The apparatus is applied to a first PE in an EVPN VPLS (virtual private network service) mesh network, the first PE is butted with a second PE in the EVPN VPWS mesh network, and VSI (virtual local area network) is configured in the first PE, and the apparatus comprises:

a receiving unit 310, configured to receive a first service packet sent by the second PE, where the first service packet includes a first destination address and a first destination MAC address, and the first destination address includes a function field;

a searching unit 320, configured to search, when the SID type of the first destination address is a first SID type and the function field indicates the VSI, a unicast forwarding table in the VSI according to the first destination MAC address;

a sending unit 330, configured to broadcast the first service packet at all AC ports in the VSI if a unicast forwarding table entry matching the first destination MAC address does not exist in the unicast forwarding table.

Optionally, the apparatus further comprises: an obtaining unit (not shown in the figure), configured to obtain an egress interface from a unicast forwarding table entry if the unicast forwarding table entry exists, where the unicast forwarding table entry is matched with the first destination MAC address;

the sending unit 330 is further configured to forward the first service packet to a host accessing the egress interface through the egress interface.

Optionally, the apparatus further comprises: a generating unit (not shown in the figure), configured to generate, within the VSI, a first destination address including the first SID type, where the first SID type is an end.dx2 type.

Optionally, the sending unit 330 is further configured to send, within the EVPN, a first ethernet auto discovery route, where the first ethernet auto discovery route includes a first destination address of the first SID type and a first ethernet tag identifier, and the first ethernet tag identifier stores a configured first local service identifier, so that after the second PE receives the PE of the first ethernet auto discovery route, whether the first local service identifier is consistent with a configured first remote service identifier is compared, and if so, an SRv6 tunnel is established with the first PE according to the first destination address of the first SID type.

Optionally, the receiving unit 310 is further configured to receive a second ethernet auto discovery route sent by the second PE, where the second ethernet auto discovery route includes a second destination address of the first SID type and a second ethernet tag identifier, and the second ethernet tag identifier stores a second local service identifier configured by the second PE;

the device further comprises: a comparing unit (not shown in the figure) for comparing whether the second local service identifier is consistent with the configured second remote service identifier;

and a establishing unit (not shown in the figure), configured to establish SRv6 a tunnel with the second PE according to the second destination address of the first SID type if the two are consistent.

Therefore, by applying the device for implementing different networking docking under EVPN provided by the present application, the first PE receives the first service packet sent by the second PE, where the first service packet includes the first destination address and the first destination MAC address, and the first destination address includes the function field. And when the SID type of the first destination address is the first SID type and the function field indicates the VSI, the first PE searches the unicast forwarding table in the VSI according to the first destination MAC address. And if the unicast forwarding table does not have the unicast forwarding table item matched with the first destination MAC address, the first PE broadcasts the first service message at all AC ports in the VSI.

Based on the same inventive concept, the present application further provides a network device, as shown in fig. 4, including 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 implementation method for different networking interfacing under EVPN provided by the present application. The device for implementing different networking interfaces under EVPN shown in fig. 3 can be implemented by using a hardware structure of a network device 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, so as to enable the processor 410 itself and the transceiver 420 to execute the implementation method of different networking interfacing under EVPN described in the foregoing embodiment of the present application.

In addition, the present application provides a machine-readable storage medium 430, where the machine-readable storage medium 430 stores machine executable instructions, and when the machine executable instructions are called and executed by the processor 410, the machine executable instructions cause the processor 410 itself and the calling transceiver 420 to execute the implementation method of different networking interfacing under EVPN described in the foregoing 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 is docked with a second PE in the EVPN VPWS networking, and VSI is configured in the first PE, and the method comprises the following steps:

2. The method of claim 1, further comprising:

if a unicast forwarding table entry matched with the first destination MAC address exists in the unicast forwarding table, acquiring an output interface from the unicast forwarding table entry;

and forwarding the first service message to a host accessed to the output interface through the output interface.

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

within the VSI, a first destination address is generated that includes the first SID type, the first SID type being an END.DX2 type.

4. The method according to claim 3, wherein before receiving the first service packet sent by the second PE, the method further comprises:

and sending a first Ethernet automatic discovery route in the EVPN, wherein the first Ethernet automatic discovery route comprises a first destination address of the first SID type and a first Ethernet label, and the first Ethernet label stores a configured first local service label, so that after the second PE receives the first Ethernet automatic discovery route, whether the first local service label is consistent with a configured first remote service label is compared, and if so, an SRv6 tunnel is established with the first PE according to the first destination address of the first SID type.

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

receiving a second ethernet auto discovery route sent by the second PE, where the second ethernet auto discovery route includes a second destination address of the first SID type and a second ethernet tag identifier, and the second ethernet tag identifier stores a second local service identifier configured by the second PE;

comparing whether the second local service identification is consistent with a configured second remote service identification;

if so, a tunnel is established SRv6 with the second PE according to the second destination address of the first SID type.

6. 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 the EVPN VPWS networking, and a VSI is configured in the first PE, and the apparatus includes:

7. The apparatus of claim 6, further comprising:

an obtaining unit, configured to obtain an output interface from a unicast forwarding table entry if the unicast forwarding table entry matching the first destination MAC address exists in the unicast forwarding table;

the sending unit is further configured to forward the first service packet to a host accessing the egress interface through the egress interface.

8. The apparatus of claim 6, further comprising:

a generating unit, configured to generate, within the VSI, a first destination address including the first SID type, where the first SID type is an end.dx2 type.

9. The apparatus according to claim 8, wherein the sending unit is further configured to send, within the EVPN, a first ethernet auto discovery route, where the first ethernet auto discovery route includes a first destination address of the first SID type and a first ethernet tag identifier, and the first ethernet tag identifier stores a configured first local service identifier, so that after the second PE receives the first ethernet auto discovery route, the second PE compares whether the first local service identifier is consistent with a configured first remote service identifier, and if so, establishes SRv6 a tunnel with the first PE according to the first destination address of the first SID type.

10. The apparatus according to claim 6, wherein the receiving unit is further configured to receive a second ethernet auto discovery route sent by the second PE, where the second ethernet auto discovery route includes a second destination address of the first SID type and a second ethernet tag identifier, and the second ethernet tag identifier stores a second local service identifier configured by the second PE;

the device further comprises: the comparison unit is used for comparing whether the second local service identifier is consistent with the configured second remote service identifier or not;

and if the two destination addresses are consistent, establishing SRv6 a tunnel with the second PE according to the second destination address of the first SID type.