CN108183858B

CN108183858B - Route introducing method and device

Info

Publication number: CN108183858B
Application number: CN201711429737.5A
Authority: CN
Inventors: 陈建
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2017-12-26
Filing date: 2017-12-26
Publication date: 2020-12-29
Anticipated expiration: 2037-12-26
Also published as: CN108183858A

Abstract

The application provides a route introducing method and a device, the method is applied to local-end PE equipment in EVPN networking, and the method comprises the following steps: obtaining common RT and ESI of opposite-end PE equipment; when the common RT of the opposite-end PE device and the common RT of the local-end PE device have the same RT, generating an ES RT corresponding to ESI according to the ESI of the opposite-end PE device; and when the RT carried in the received EVPN route is matched with the generated ES RT, introducing the EVPN route into an MAC table entry and/or an IP table entry of local end PE equipment. By the method, the local PE equipment can directly introduce the EVPN route as long as the RT in the received EVPN route is determined to be the same as the locally generated ES RT, so that the time consumed by introducing the route is reduced, and the time consumed by introducing the route is not influenced by the RT number configured by the PE equipment any more.

Description

Route introducing method and device

Technical Field

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

Background

In EVPN (Ethernet Virtual Private Network), in order to improve the bandwidth utilization of links and enhance the Network reliability, a host (or a virtualized Virtual machine) of a user or a Private Network of the user is usually connected to multiple VTEPs in the EVPN Network through multiple links, which is called multi-homing access.

The common route reference method in EVPN is: after a PE (Provider Edge) device learns a local Route of a CE device from a CE (Customer Edge), an RD (Route distingguicher) and an RT (Route Target) are added to the Route, and then the Route is distributed to other PEs. The routes of different VPNs are distinguished in the public network by RD, and the routes between different CE devices are introduced and controlled by RT. When receiving a route issued by other PE equipment, the PE equipment compares the RT carried in the route with the RT configured locally, and the route is introduced only when the same RT value exists in the two.

Disclosure of Invention

The application provides a method and a device for rapidly introducing a route.

Specifically, the method is realized through the following technical scheme:

in a first aspect of the present application, a route introducing method is provided, which is applied to a local PE device in an EVPN networking, and the method includes:

obtaining common RT and ESI of opposite-end PE equipment;

when the common RT of the opposite-end PE device and the common RT of the local-end PE device have the same RT, generating an ES RT corresponding to ESI according to the ESI of the opposite-end PE device;

and when the RT carried in the received EVPN route is matched with the generated ES RT, introducing the EVPN route into an MAC table entry and/or an IP table entry of local end PE equipment.

In a second aspect of the present application, a route introducing apparatus is provided, which is applied to a local PE device in an EVPN networking, and the apparatus includes:

an obtaining unit, configured to obtain a common RT and an ESI of an opposite-end PE device;

an ES RT generating unit, configured to generate an ES RT corresponding to the ESI according to the ESI of the opposite-end PE device when the common RT of the opposite-end PE device and the common RT of the local-end PE device have the same RT;

and the route introducing unit is used for introducing the EVPN route into the MAC table entry and/or the IP table entry of the local PE equipment when the RT carried in the received EVPN route is matched with the generated ESRT.

According to the technical scheme, in the application, the local-end PE device generates a special RT according to the ESI of the opposite-end PE device, and the opposite-end PE device also generates the same special RT according to the ESI of the opposite-end PE device. Then, for the opposite-end PE device, the special RT may be carried in the issued EVPN route; for the local PE equipment, as long as the RT in the received EVPN route is determined to be the same as the locally generated special RT, the EVPN route can be directly introduced, so that the time consumed by introducing the route is reduced, and the time consumed by introducing the route is not influenced by the RT number configured by the PE equipment any more.

Drawings

FIG. 1 is a schematic diagram of an EVPN networking;

FIG. 2 is a flow chart of a method provided by an embodiment of the present application;

fig. 3 is a diagram of an interaction process between a local PE device and an opposite PE device according to an embodiment of the present application;

FIG. 4 is a block diagram of an apparatus according to an embodiment of the present disclosure;

fig. 5 is a hardware configuration diagram of the apparatus shown in fig. 4 according to an embodiment of the present application.

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 associated 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.

EVPN multihoming is a technology that supports CE connection to multiple PEs, and introduces the ES (Ethernet Segment) concept: when a station accesses to the EVPN network through a plurality of links, the links form an ES; each link is identified using the same ESI (Ethernet Segment Identifier) on the corresponding VTEP. For example, in the EVPN networking shown in fig. 1, CE1 is multihomed to PE1 and PE2, and the link connecting CE1 to PE1 and PE2 is uniquely identified by an ESI (e.g., es 1).

There are several types of EVPN routes, different types of EVPN routes can implement different functions, and there are eight types of EVPN routes defined at present. For example, a second type EVPN Route (hereinafter referred to as a second type Route, and similar abbreviations may also be used for other types of EVPN routes), that is, a MAC/IP Advertisement Route (MAC/IP Advertisement Route), may be used to synchronize MAC/IP table entries; three types of routes may be used to create tunnels; five types of routes may be used for synchronous IP network segment routing.

The introduction manner of a two-type route in the EVPN networking is described here by taking CE1, PE2, and PE3 in fig. 1 as examples: after learning the MAC (Medium Access Control) address of the CE1, the PE2 may issue a second type of route to the PE3, where the second type of route includes the MAC address of the CE1, the ESI of the CE1, and the RD, RT, and next hop of the PE 2. After receiving the two types of routes, PE3 compares the RTs in the two types of routes with the locally configured RTs, and introduces the two types of routes as long as the same RT exists in the two types of routes. Assuming that the RTs carried by the two types of routes are 1:1, 2:2, 3:3, and the locally configured RTs of PE3 are 3:3, 4:4, it can be determined through comparison that the two are the same RT 3:3, so PE3 can introduce the MAC address of CE1 carried by the two types of routes into the MAC entry of a VSI (Virtual Switch Interface) corresponding to RT 3: 3.

The disadvantage of this route introduction manner is that, for each received EVPN route, the PE device needs to compare each RT carried by the EVPN route with a locally configured RT to determine whether to introduce the EVPN route and into which forwarding instance the EVPN route is introduced; when there are more RTs configured on the PE device, introducing routes will take longer.

In the scheme, the local-end PE device generates a special RT according to ESI of the opposite-end PE device, and the opposite-end PE device also generates the same special RT based on the ESI of the opposite-end PE device. Then, for the opposite-end PE device, the special RT may be carried in the issued EVPN route; for the local PE equipment, as long as the RT in the received EVPN route is determined to be the same as the locally generated special RT, the EVPN route can be directly introduced, so that the time consumed by introducing the route is reduced, and the time consumed by introducing the route is not influenced by the RT number configured by the PE equipment any more. For the sake of distinction, hereinafter, a special RT generated based on ESI is referred to as an ES RT, a conventional RT is referred to as a normal RT, and the normal RT and the ES RT are collectively referred to as an RT.

The technical scheme of the application is described in the following with the accompanying drawings and various embodiments of the specification.

Referring to fig. 2, in one embodiment, any local PE device in the EVPN networking performs the following steps during operation:

step 201: the local terminal PE device obtains the common RT and ESI of the opposite terminal PE device.

Step 202: when the common RT of the opposite-end PE device and the common RT of the home-end PE device have the same RT, the home-end PE device generates an ES RT corresponding to ESI according to ESI of the opposite-end PE device.

Both ES RT and normal RT are 8 bytes, with the first 2 bytes defining the type of attribute and the last 6 bytes containing the value of the attribute. The attribute value of the ES RT is 0x0602, and the attribute value of the normal RT is 0x0002 or 0x 0102.

As an example, the ES RT may be generated by: the first 6 bytes are extracted from the ESI of 10 bytes, and spliced with the attribute value 0x0602 to obtain the ES RT.

For example, assuming an ESI of 0x12345678901234567890, 8 bytes of ES RT ═ 0x 0602123456789012 can be generated based on this ESI.

Step 203: when the RT carried in the received EVPN route is matched with the generated ES RT, the local end PE equipment introduces the EVPN route into a local MAC table entry and/or an IP table entry.

Thus, the flow shown in fig. 2 is completed.

As can be seen from the flow shown in fig. 2, compared with the above-described method for introducing a route by comparing the common RT carried in the EVPN route and the locally configured common RT, the route introducing method provided by the present application has the following advantages: 1) when the EVPN route is sent, only one ES RT is needed to be carried in the EVPN route, and a large number of common RTs are not needed to be carried, so that the number of bytes occupied by the EVPN route can be reduced, and the network bandwidth consumed by transmission of the EVPN route can be saved; 2) when determining whether to introduce the EVPN route, only the RT in the EVPN route needs to be compared with the ES RT which is locally generated, so that the time consumed by introducing the route can be reduced, and the time consumed by introducing the route does not increase with the increase of the number of the ordinary RTs configured by the PE equipment.

It should be noted that the route introduction method provided by the present application may be applied to the EVPN multihoming scenario shown in fig. 1; in an EVPN non-multihoming scenario, if a certain PE device is configured with an effective ESI, the route introduction method provided by the present application may also be used to enable an opposite-end PE device to quickly introduce an EVPN route issued by the PE device.

In order to make it clear and obvious for those skilled in the art, the following describes a specific implementation process of the method shown in fig. 2 through interaction between the local PE device and the opposite PE device in conjunction with fig. 3.

Step 301: the local PE equipment judges whether the equipment enables the routing introducing strategy based on the ES.

Here, it is determined whether the present apparatus enables an ES-based route introduction policy, that is, whether the present apparatus supports the capability of generating an ES RT according to ESI and performing route introduction and transmission according to the ES RT.

Step 302: and if the capability negotiation message is enabled, the local terminal PE equipment sends the capability negotiation message to the opposite terminal PE equipment.

In this embodiment, the capability negotiation message is used to indicate the PE device that sends the capability negotiation message to enable the route introduction policy based on the ES.

There are many implementations of the capability negotiation message, and two are briefly listed here:

the first method is as follows: by existing message types.

Take the implementation of capability negotiation messages over a class two route as an example. The local PE device can send a second type of route to the opposite PE device, wherein a new attribute is added in an extended Community attribute (Ext-Community) field of the second type of route, and the PE device represents that the local device enables an ES-based route introduction strategy through the new attribute; the RT in the second type of route may be filled with a preset RT value, where the preset RT value may be a globally applicable RT value agreed in advance for unconditionally introducing the capability negotiation message, and all the capability negotiation messages sent by the PE device to the outside carry the preset RT value; in the second type of routing, fields other than RT and the above capability attribute, such as RD, ESI, VLAN ID (i.e. ethernet Tag ID (ethernet Tag ID)), MAC Address Length (MAC Address Length), MAC Address, IP Address Length (IP Address Length), and IP Address, are all filled with invalid values (e.g. filled with 0).

Based on the first mode, after the opposite-end PE device receives and introduces a second-class route, if it is found that the new attribute in the extended community attribute field in the second-class route is a valid value and the other fields except the RT and the new attribute are invalid values, the received second-class route is regarded as a capability negotiation message, and it is determined that the PE device sending the capability negotiation message enables the route introduction policy based on the ES.

The second method comprises the following steps: by means of the new message type.

For example, a message type may be added, and for convenience of description, the added message type is referred to as a nine-type route. In one implementation, in order to make it possible for the capability negotiation messages and the ES introduction routes appearing later herein to multiplex the same message type, message formats that may define nine types of routes include RD, RT, ESI, and VLAN ID fields. When the capability negotiation message is realized through the nine types of routes in the format, the RT of the nine types of routes can be filled with a preset RT value, and the preset RT value can be a globally applicable RT value which is agreed in advance and is used for unconditionally introducing the capability negotiation message; and the RD, ESI and VLAN ID in the nine types of routes are filled into invalid values.

Step 303: after receiving the capability negotiation message sent by the local end PE device, the opposite end PE device judges whether to enable the routing introducing strategy based on the ES and whether to configure the ESI.

Step 304: and if the opposite-end PE device determines that the ES-based route is enabled by the opposite-end PE device to introduce the strategy and is configured with the ESI, sending the ESI configured by the opposite-end PE device and the common RT and VLAN ID associated with the ESI to the local-end PE device.

It should be noted that, if the VLAN is not configured on the peer PE device for ESI, the VLAN ID associated with ESI sent by the peer PE device to the local PE device is an invalid value.

For example, assuming that the interface rag0/1 of the PE2 connected to the CE1 in fig. 1 is a three-layer interface, the configuration on the PE2 is as follows:

the above configuration represents: the three-layer interface rag0/1 on PE2 is identified as ES1, the three-layer interface rag0/1 is associated with vsi1, vsi1 is associated with Vxlan1 and Tunnel12, RD corresponding to vsi1 is RD2, and RT corresponding to vsi1 is 1: 12: 23: 3.

Based on the above configuration, after receiving the capability negotiation message of PE3, PE2 confirms that the ES-based route introduction policy is locally enabled, and may send ES1 and the normal RT 1: 12: 23: 3 and RD2 associated with ES1 to PE3, because VLAN is not configured in tri-layer interface rag0/1 identified by ES1, PE2 responds to PE3 that VLAN ID associated with ES1 is an invalid value.

For another example, if the interface bag0/1 of the PE2 connected to the CE1 in fig. 1 is a two-layer interface, the configuration on the PE2 is as follows:

ES fast-import// enabling ES-based route introduction policy

The above configuration represents: the identifier of the two-layer interface bag0/1 on the PE2 is ES 2, and Vlan10 and Vlan20 are arranged under the two-layer interface bag0/1, wherein Vlan10 is associated with vsi 2, and Vlan20 is associated with vsi 3.

Based on the above configuration, after receiving the capability negotiation message of PE3, PE2 confirms that the ES-based route introduction policy is locally enabled, and may send ES 2 and ordinary RT 1: 12: 23: 3, Vlan10 and Vlan20, RD2:2, and RD 3:3 associated with ES 2 to PE 3.

For convenience of description, the present embodiment refers to the message in step 304 that is responsible for passing the ESI, the normal RT, and the VLAN ID of the PE device as an ES introduction route. ES introduction routing can also be implemented by existing message types or new message types.

If the routing is introduced by the ES through the existing two-type routing, the RD, the ordinary RT, the ESI and the VLAN ID configured on the PE device can be filled into the RD, the RT, the ESI and the VLAN ID fields of the two-type routing; meanwhile, the 4 fields of the MAC address length, the MAC address, the IP address length and the IP address in the second type of routing are filled into invalid values.

It is assumed that ES-introduced routing is implemented by newly defined message types (e.g., nine types of routing), whose message formats are described above, including RD, RT, ESI, and VLAN ID fields. When the ES introduction route is realized through the nine types of routes in the format, only the RD, the ordinary RT, the ESI and the VLAN ID configured on the PE device are needed to be filled into the corresponding fields of the nine types of routes.

It should be noted that, if a plurality of valid ESIs are configured on the peer PE device, the peer PE device may send a corresponding ES introduction route for each ESI. If the opposite PE device does not enable ES-based route introduction policy or does not configure valid ESI, no response is made.

Steps 301 to 304 describe a unidirectional capability negotiation process; similarly, the opposite-end PE device will also send a capability negotiation message to the home-end PE device, and the home-end PE device will also respond to the capability negotiation message and send the ESI, the normal RT, and the VLAN ID configured by itself to the opposite-end PE device through the ES introduction route. The following describes the ES RT generation procedure and the route introduction procedure based on the ES RT from the perspective of the home-end PE device.

Step 305: after receiving ESI of the opposite end PE device, and the common RT and VLAN ID associated with ESI, the local end PE device determines whether the common RT of the opposite end PE device and the common RT of the local end PE device have the same RT.

Step 306: if the same RT exists, the local-end PE device generates an ES RT corresponding to the ESI according to the ESI of the opposite-end PE device, searches the forwarding instance identifier corresponding to the same RT on the local-end PE device, and generates a route introduction table item.

The route introduction table entry generated here contains a matching item and a forwarding instance identifier corresponding to the matching item, where the matching item is ESI of the opposite-end PE device and VLAN ID associated with the ESI. The forwarding instance id herein includes a two-layer forwarding instance id (e.g., VSI id) and a three-layer forwarding instance id (e.g., VPN id).

As described above, the opposite-end PE device may send the ESI, the normal RT, and the VLAN ID configured by itself to the local-end PE device through the ES introduction route. An ES ingress route carries only one ESI, but can carry multiple VLAN IDs.

Assuming that ESI carried in a certain ES introduction route is ESI1, and VLAN ID carried includes VLAN ID1 and VLAN ID2, and a common RT carried by the ES introduction route and a local PE device have the same RT, and forwarding instances corresponding to the same RT are identified as vsi1 and vpn1, the generated route introduction entry may refer to table 1 or table 2.

TABLE 1

esi1+vlan id1	vsi1、vpn1
		esi1+vlan id2	vsi1、vpn1

TABLE 2

esi1+ vlan id1 or esi1+ vlan id2

vsi1、vpn1

Step 307: when the local PE equipment receives the EVPN route, whether an RT in the EVPN route is matched with an ES RT generated by the local PE equipment is judged, and if yes, the EVPN route is introduced into an MAC table entry and/or an IP table entry of the local PE equipment.

Otherwise, if no RT in the EVPN route is matched with the ES RT generated by the local PE equipment, the RT carried by the EVPN route can be matched with the ordinary RT of the local PE equipment; and if the RT carried by the EVPN route has the same RT with the common RT of the local end PE equipment, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the same RT.

In step 307, when it is determined that there is an RT in the EVPN route matching the existing ES RT of the local PE device, a route entry matching the ESI and the VLAN ID carried in the EVPN route may be searched.

From the foregoing, it can be seen that the ES RTs are generated from the first 6 bytes of ESI, which results in the possibility that the same ES RT may be generated from different ESIs. For example, two ESIs are 0x123456789012333333 and 0x123456789012444444, respectively, and the ES RTs generated according to the two ESIs are both 0x 0602123456789012. The non-uniqueness of the ES RT causes that in step 307, when it is determined that there is an RT in the EVPN route matching the ES RT generated by the PE device at the local end, a matching route entry cannot be found according to the ESI and VLAN ID carried by the EVPN route. For this case, the present application proposes the following solutions:

if finding out the route lead-in table item matched with ESI and VLAN ID carried by the EVPN route, leading the EVPN route into the MAC table item and/or IP table item corresponding to the forwarding instance identifier in the matched route lead-in table item;

and if the matched route introduction table entry is not found, matching the RT carried by the EVPN route with the common RT of the local end PE equipment, and introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the same RT if the RT carried by the EVPN route and the common RT of the local end PE equipment have the same RT. Optionally, subsequently, if the local PE device generates a new route introduction entry again, the EVPN route that can match the ES RT of the local PE device but cannot find the matching route introduction entry may be back-checked based on the newly generated route introduction entry to determine whether to introduce the EVPN route into the correct MAC entry and/or IP entry.

As an implementation manner, when the EVPN route is introduced into the MAC entry and/or the IP entry of the present device, the present embodiment may be divided into the following cases:

when the EVPN route is a second-class route and the IP address carried by the EVPN route is an invalid value, the EVPN route can be introduced into an MAC table entry of the equipment;

secondly, when the EVPN route is a second type route and the IP address carried by the EVPN route is an effective value, the EVPN route can be simultaneously introduced into the MAC table entry and the IP table entry of the equipment;

thirdly, when the EVPN route is five types of routes, the EVPN route can be introduced into the IP entry of the device.

In addition, considering that other types of EVPN routes may occur in the future, for other types of EVPN routes occurring in the future, if valid ESI is carried in the EVPN route, the route introduction method provided by the present application may also be considered.

The methods provided herein are described above. The following describes the apparatus provided in the present application:

referring to fig. 4, fig. 4 is a diagram illustrating the structure of the apparatus according to the present invention. The device is applied to local-end PE equipment in EVPN networking. As shown in fig. 4, the apparatus includes:

an obtaining unit 401, configured to obtain a normal RT and an ESI of an opposite-end PE device.

An ES RT generating unit 402, configured to generate an ESRT corresponding to the ESI according to the ESI of the opposite-end PE device when the common RT of the opposite-end PE device and the common RT of the local-end PE device have the same RT.

A route introducing unit 403, configured to introduce the EVPN route into a MAC entry and/or an IP entry of the local PE device when the RT carried in the received EVPN route matches the generated ES RT.

In one embodiment, the apparatus may further include a route entry generation unit; the obtaining unit 401 is further configured to obtain a VLAN ID associated with the ESI of the peer PE device. The route introducing table item generating unit is used for searching a forwarding instance identifier corresponding to the same RT on the local terminal PE equipment when the same RT exists between the common RT of the opposite terminal PE equipment and the common RT of the local terminal PE equipment; and generating a route introduction table item according to the obtained ESI of the opposite-end PE device, the VLAN ID associated with the ESI and the searched forwarding instance identifier, wherein the route introduction table item comprises a matching item and the forwarding instance identifier corresponding to the matching item, and the matching item is the ESI of the opposite-end PE device and the VLAN ID associated with the ESI.

In one embodiment, the route introducing unit 403 may be configured to search for a route introducing entry matching the ESI and the VLAN ID carried by the EVPN route; and if the EVPN route is found, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the forwarding instance identifier in the matched route introduction table entry.

In one embodiment, the route introducing unit 403 may be further configured to, if a route introducing entry matching the ESI and the VLAN ID carried in the EVPN route is not found, match the RT carried in the EVPN route with a common RT of the local PE device; and if the RT carried by the EVPN route has the same RT with the common RT of the local PE equipment, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the same RT.

In one embodiment, the obtaining unit 401 may be configured to determine whether the local PE device enables an ES-based route introduction policy; and if the capability negotiation message is enabled, sending a capability negotiation message to the opposite-end PE equipment, wherein the capability negotiation message is used for indicating the local-end PE equipment which sends the capability negotiation message to enable the ES-based route introduction strategy, so that the opposite-end PE equipment which receives the capability negotiation message sends the self-configured ESI and the common RT and VLAN ID which are associated with the ESI to the local-end PE equipment when determining that the local-end PE equipment enables the ES-based route introduction strategy and is configured with the ESI.

In one embodiment, the route introducing unit 403 may be configured to introduce the EVPN route into a MAC entry of a local PE device when the EVPN route is a type two route and an IP address carried by the EVPN route is an invalid value; when the EVPN route is a second-class route and the IP address carried by the EVPN route is an effective value, introducing the EVPN route into an MAC (media access control) table entry and an IP (Internet protocol) table entry of local PE (provider edge) equipment at the same time; and when the EVPN route is five types of routes, introducing the EVPN route into an IP table entry of local end PE equipment.

The implementation process of the functions and actions of each module 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.

It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation. The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The description of the apparatus shown in fig. 4 is thus completed.

Referring to fig. 5, the present application further provides a hardware architecture diagram of a PE device, where the PE device includes: a communication interface 501, a processor 502, a memory 503, and a bus 504; the communication interface 501, the processor 502 and the memory 503 are connected to communicate with each other via a bus 504.

The communication interface 501 is used for communicating with other PE devices. The processor 502 may be a Central Processing Unit (CPU), the memory 503 may be a non-volatile memory (non-volatile memory), and the memory 503 stores route importing logic instructions, and the processor 502 may execute the route importing logic instructions stored in the memory 503 to implement the functions of the local PE device in the flows shown in fig. 2 and fig. 3.

To this end, the description of the hardware configuration shown in fig. 5 is completed.

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 route introduction method is applied to home end service Provider Edge (PE) equipment in Ethernet Virtual Private Network (EVPN) networking, and comprises the following steps:

obtaining a common routing target RT and an Ethernet segment identifier ESI of opposite-end PE equipment;

when the RT carried in the received EVPN route is matched with the generated ES RT, introducing the EVPN route into an MAC table entry and/or an IP table entry of local end PE equipment; the RT carried by the EVPN route is a common RT or an ES RT;

wherein, the introducing the EVPN route into the MAC entry and/or the IP entry of the local PE device includes:

searching a route introduction table item matched with ESI and VLAN ID carried by the EVPN route;

and if the EVPN route is found, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the forwarding instance identifier in the matched route introduction table entry.

2. The method of claim 1, wherein prior to introducing the EVPN route into a MAC entry and/or an IP entry of a local PE device, the method further comprises:

obtaining VLAN ID associated with ESI of opposite terminal PE equipment;

when the common RT of the opposite-end PE equipment and the common RT of the local-end PE equipment have the same RT, searching a forwarding instance identifier corresponding to the same RT on the local-end PE equipment;

and generating a route introduction table item according to the obtained ESI of the opposite-end PE device, the VLAN ID associated with the ESI and the searched forwarding instance identifier, wherein the route introduction table item comprises a matching item and the forwarding instance identifier corresponding to the matching item, and the matching item is the ESI of the opposite-end PE device and the VLAN ID associated with the ESI.

3. The method of claim 1, wherein the method further comprises:

if no route introduction table item matched with ESI and VLAN ID carried by the EVPN route is found, matching RT carried by the EVPN route with common RT of local PE equipment;

and if the RT carried by the EVPN route has the same RT with the common RT of the local PE equipment, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the same RT.

4. The method as recited in claim 1, wherein obtaining the normal RT and ESI for the peer PE device comprises:

judging whether the local PE equipment enables an ES-based route introduction strategy or not;

and if the capability negotiation message is enabled, sending a capability negotiation message to the opposite-end PE equipment, wherein the capability negotiation message is used for indicating the local-end PE equipment which sends the capability negotiation message to enable the ES-based route introduction strategy, so that the opposite-end PE equipment which receives the capability negotiation message sends the self-configured ESI and the common RT and VLAN ID which are associated with the ESI to the local-end PE equipment when determining that the local-end PE equipment enables the ES-based route introduction strategy and is configured with the ESI.

5. The method of claim 1, wherein the introducing the EVPN route into the MAC entry and/or IP entry corresponding to the forwarding instance identification in the matching route introduction entry comprises:

when the EVPN route is a second-class route and an IP address carried by the EVPN route is an invalid value, introducing the EVPN route into an MAC table entry of local-end PE equipment;

when the EVPN route is a second-class route and the IP address carried by the EVPN route is an effective value, introducing the EVPN route into an MAC (media access control) table entry and an IP (Internet protocol) table entry of local PE (provider edge) equipment at the same time;

and when the EVPN route is five types of routes, introducing the EVPN route into an IP table entry of local end PE equipment.

6. A route introduction apparatus, applied to a home service provider edge PE device in an ethernet virtual private network EVPN networking, the apparatus comprising:

an obtaining unit, configured to obtain a common routing target RT and an ethernet segment identifier ESI of an opposite-end PE device;

a route introducing unit, configured to introduce the EVPN route into an MAC entry and/or an IP entry of the local PE device when an RT carried in the received EVPN route matches the generated ES RT; the RT carried by the EVPN route is a common RT or an ES RT;

the route introducing unit is used for searching a route introducing table entry matched with ESI and VLAN ID carried by the EVPN route; and if the EVPN route is found, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the forwarding instance identifier in the matched route introduction table entry.

7. The apparatus of claim 6, wherein the apparatus further comprises a route import table entry generation unit;

the obtaining unit is further configured to obtain a VLAN ID associated with the ESI of the opposite-end PE device;

the route introducing table item generating unit is used for searching a forwarding instance identifier corresponding to the same RT on the local terminal PE equipment when the same RT exists between the common RT of the opposite terminal PE equipment and the common RT of the local terminal PE equipment; and generating a route introduction table item according to the obtained ESI of the opposite-end PE device, the VLAN ID associated with the ESI and the searched forwarding instance identifier, wherein the route introduction table item comprises a matching item and the forwarding instance identifier corresponding to the matching item, and the matching item is the ESI of the opposite-end PE device and the VLAN ID associated with the ESI.

8. The apparatus of claim 6,

the route introducing unit is further configured to match the RT carried by the EVPN route with a normal RT of the local PE device if a route introducing entry matching the ESI and the VLAN ID carried by the EVPN route is not found; and if the RT carried by the EVPN route has the same RT with the common RT of the local PE equipment, introducing the EVPN route into the MAC table entry and/or the IP table entry corresponding to the same RT.

9. The apparatus of claim 6,

the acquiring unit is used for judging whether the local PE equipment enables an ES-based route introduction strategy; and if the capability negotiation message is enabled, sending a capability negotiation message to the opposite-end PE equipment, wherein the capability negotiation message is used for indicating the local-end PE equipment which sends the capability negotiation message to enable the ES-based route introduction strategy, so that the opposite-end PE equipment which receives the capability negotiation message sends the self-configured ESI and the common RT and VLAN ID which are associated with the ESI to the local-end PE equipment when determining that the local-end PE equipment enables the ES-based route introduction strategy and is configured with the ESI.

10. The apparatus of claim 6,

the route introducing unit is used for introducing the EVPN route into an MAC table entry of local PE equipment when the EVPN route is a second-class route and an IP address carried by the EVPN route is an invalid value; when the EVPN route is a second-class route and the IP address carried by the EVPN route is an effective value, introducing the EVPN route into an MAC (media access control) table entry and an IP (Internet protocol) table entry of local PE (provider edge) equipment at the same time; and when the EVPN route is five types of routes, introducing the EVPN route into an IP table entry of local end PE equipment.