CN113992573B

CN113992573B - Method and device for forwarding BUM (building information management) flow, PE (provider edge) equipment and storage medium

Info

Publication number: CN113992573B
Application number: CN202111249285.9A
Authority: CN
Inventors: 葛健楠
Original assignee: New H3C Security Technologies Co Ltd
Current assignee: New H3C Security Technologies Co Ltd
Priority date: 2021-10-26
Filing date: 2021-10-26
Publication date: 2023-03-31
Anticipated expiration: 2041-10-26
Also published as: CN113992573A

Abstract

The application provides a method and a device for forwarding BUM flow, PE equipment and a storage medium. The method comprises the following steps: identifying the home relationship between the first CE equipment and each PE equipment based on an NLRI message, wherein the NLRI message comprises a first ESI field and a second ESI field, the first ESI field is used for carrying ESI configured by an equipment interface of the PE equipment, the second ESI field is used for carrying ESI configured by a first AC port of the PE equipment, receiving BUM flow sent by the first CE equipment, adding an ESI label to the BUM flow, and sending the BUM flow to the second CE equipment through a second AC port of the second PE equipment; by the method, the problem that BUM flow cannot be forwarded between the first CE device and the second CE device due to horizontal segmentation under the condition of dual homing is solved.

Description

Method and device for forwarding BUM (building information management) flow, PE (provider edge) equipment and storage medium

Technical Field

The present application relates to network technologies, and in particular, to a method and an apparatus for forwarding BUM traffic, a PE device, and a storage medium.

Background

In the field of network communication, when an EVPN (Ethernet VPN, ethernet virtual private network) multi-homing technology is used for networking, in order to prevent the forwarding of BUM (Broadcast, unknown-unicast, multicast traffic) traffic from forming a loop, an ESI label carried in the BUM traffic is checked, the ESI (Ethernet Segment Identifier) is the unique Identifier of an ES (Ethernet Segment), links corresponding to interfaces with the same ESI belong to the same ES, when the ESI label value is the same as the ESI value of a PE (Provider Edge, service Provider network Edge) device interface, the forwarding of BUM traffic through the interface of the PE device is stopped, and this means for preventing the looping of BUM traffic is called horizontal segmentation; however, when CE (Customer Edge) devices are connected in a multi-homed manner, multiple AC (access Circuit) links may exist in an interface of one PE device, and thus, BUM traffic of different AC links may generate the same ESI label, which results in a problem that BUM traffic sent by one CE device cannot be forwarded to another CE device.

Disclosure of Invention

A first aspect of the present application provides a method for forwarding BUM traffic, which is applied to a PE device, and the method includes:

identifying an attribution relationship between first CE equipment and the PE equipment based on an NLRI message, wherein the attribution relationship comprises dual attribution, and the dual attribution is that the first CE equipment belongs to the PE equipment and second PE equipment at the same time; the NLRI message includes a first ESI field and a second ESI field, where the first ESI field is used to carry ESI configured for an equipment interface of the PE equipment, and the second ESI field is used to carry ESI configured for a first AC port of the PE equipment;

receiving BUM flow sent by first CE equipment, and adding an ESI label to the BUM flow according to the attribution relationship between the first CE equipment and each PE equipment;

and determining the matched attribution relationship based on the ESI label, and sending the BUM flow to a second CE device through a second AC port of a second PE device under the condition that the first CE device and the second CE device are in the same dual-attribution relationship.

A second aspect of the present application provides a PE apparatus, including: an attribution relation determining module, configured to identify an attribution relation between a first CE device and each PE device based on an NLRI packet, where the attribution relation includes dual attribution, and the dual attribution is that the first CE device belongs to the PE device and a second PE device at the same time; the NLRI message includes a first ESI field and a second ESI field, where the first ESI field is used to carry ESI configured for an equipment interface of the PE equipment, and the second ESI field is used to carry ESI configured for a first AC port of the PE equipment;

the flow forwarding module is used for receiving the BUM flow sent by the first CE equipment and adding the ESI label to the BUM flow according to the attribution relationship between the first CE equipment and each PE equipment; and determining the matched attribution relationship based on the ESI label, and sending the BUM flow to a second CE device through a second AC port of a second PE device under the condition that the first CE device and the second CE device are in the same dual-attribution relationship.

A third aspect of the present application provides a PE device, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to perform the method of the first aspect.

A fourth aspect of the present application provides a computer storage medium storing a computer program which, when executed by a processor, implements the method of the first aspect described above.

Based on the above technical solution, in the embodiment of the present application, ESI is configured for the AC port, so that the BUM traffic carries ESI different from the device interface of the PE device, thereby solving the problem in the prior art that the BUM traffic cannot be forwarded under the multi-homing condition of the CE device due to horizontal segmentation, and because the range of the ESI value is limited, ESI is not set in the case of single homing of the CE device in the present application, thereby saving resources of ESI tags.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.

FIG. 1 is a diagram of a network architecture for one embodiment of the present description.

FIG. 2 is a flow diagram of a method in accordance with one embodiment of the present disclosure.

Fig. 3 is another network architecture diagram for one embodiment of the present description.

Fig. 4 is another network architecture diagram for one embodiment of the present description.

FIG. 5 is a block diagram of an apparatus of one embodiment of the present description.

FIG. 6 is a block diagram of an apparatus of one embodiment of the present description.

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 specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification 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 should 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 description. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context.

The following provides a detailed description of examples of the present specification.

As shown in fig. 1, fig. 1 is a network architecture diagram provided in an embodiment of the present application, and the involved network entities include a CE device 111, a CE device 112, a CE device 113, a PE device 121, a PE device 122, and a PE device 123.

PE device 121 and PE device 122 are route reachable. The PE devices form a service provider network backbone 120. The source IP of the PE device 121 has a value of 1.1.1.1, the source IP of the PE device 122 has a value of 2.2.2.2, and the source IP of the PE device 123 has a value of 3.3.3.3. And PW connection is established between the PE devices, and the PW connection is formed by a pair of unidirectional virtual connections in opposite directions. The PW connection is established on a public network tunnel, and the public network tunnel passes through an IP (Internet protocol) or MPLS (multi protocol Label Switching) backbone network; one public network tunnel may carry multiple PW connections, and in this embodiment, the public network tunnel may be an MPLS tunnel.

The CE device 111 is connected to the PE device 121 and the PE device 122 through an AC link, the CE device 112 is connected to the PE device 121 and the PE device 122 through an AC link, and the CE device 113 is connected to the PE device 123 through an AC link, so that the CE device 111 and the CE device 112 are dual-homed, and the CE device 113 is single-homed. Link 131 and link 132 of CE device 111 and PE device belong to the first AC; link 133 and link 134 of CE device 112 with PE devices belong to the second AC, and link 135 of CE device 113 belongs to the third AC. Under the condition of dual homing, one side of the main link is required to be selected as a main link, and the other side of the main link is required to be selected as a standby link; the backup link may receive data, send known unicast, multicast data packets, but not send BUM traffic.

The method for establishing the active/standby link is to select the smallest VLAN Tag allowed to pass through in the first AC to represent the AC, where in this example, the VLAN Tag representing the first AC is 11.PE device 121 and PE device 122 mutually send an M-ES routing (Multiple Ethernet Segment routing) packet, which carries RD (routing identifier), ESI, IP address of the originating router, and RT (routing Target attribute), and after

PE devices

121 and 122 receive the M-ES routing packet, obtain the source IP after judging that the ESI values are the same, and assign an index value to the PE device according to the sequence of the source IP addresses from small to large, where the numbering starts from 0. In this embodiment, the numbers corresponding to the source IP 1.1.1.1 are sequentially 0, the numbers corresponding to the source IP 2.2.2.1 are sequentially 1, so the index value of the PE device 121 is 0, and the index value of the PE device 122 is 1. And then selecting the main link according to the remainder M of dividing the VLAN Tag by N, wherein N represents the number of members in the redundant backup group, and M corresponds to the main link with the number of the AC. In this example, the remainder of the VLAN Tag value 11 divided by 2 in the first AC is 1, that is, the number of the primary link of the first AC link is 1, and is the same as the index value of the PE device 122, so that the link 132 between the CE device 111 and the PE device 122 in the first AC is taken as the primary link, and the link 131 is taken as the standby link. In the same way, link 134 in the second AC is the primary link and link 133 is the standby link.

Next, introducing the concept of horizontal segmentation, if the PE device 121 receives the BUM traffic sent by the CE device 111, the PE device 121 generates an ESI tag according to ESI of its device interface, adds the ESI tag to the BUM traffic, and forwards the BUM traffic to the PE device 122. The PE device 122 detects ESI of the device interface connected to the CE device 111, and finds that ESI of the device interface is the same as ESI carried by the ESI tag, then the PE device 122 will not send the BUM traffic to the CE device 111, thereby preventing the BUM traffic from looping.

Therefore, when the CE device 111 sends the BUM traffic to the PE device 121, because the link 133 is a standby link, the PE device 121 does not send the BUM traffic to the CE device 112 through the link 133, but forwards the BUM traffic to the PE device 122, and because of the existence of horizontal split, the PE device 122 checks that the ESI tag carried in the BUM is the same as the ESI value of its device interface, and therefore does not send the BUM traffic to the CE device 112.

Therefore, in order to solve the problem that the BUM traffic cannot be forwarded in the conventional manner, the present application discloses a method for forwarding BUM traffic, as shown in fig. 2:

step 202: and identifying the home relationship of the first CE equipment based on the NLRI message.

Identifying an attribution relationship between first CE equipment and each PE equipment based on an NLRI message, wherein the attribution relationship comprises dual attribution, and the dual attribution is that the first CE equipment belongs to the PE equipment and a second PE equipment at the same time; the NLRI packet includes a first ESI field and a second ESI field, where the first ESI field is used to carry ESI configured for an equipment interface of the PE equipment, and the second ESI field is used to carry ESI configured for a first AC port of the PE equipment.

Step 204: BUM traffic is received, and an ESI tag is added to the BUM traffic.

The ESI tag is used to characterize the affiliation of the first CE device.

Step 206: and sending the BUM flow to a second CE device through a second AC port of a second PE device.

As an example, in step 202, the NLRI packet may include:

one or more of an ES-AD routing (Ethernet Auto-Discovery Route) packet, an M-MAC/IP routing (MAC/IP Advertisement Route) packet, and an M-ES routing packet.

The step of determining the affiliation of the first CE device to the PE device comprises:

and if the first ESI field does not carry the ESI of the device interface of the PE device and the second ESI field does not carry the ESI of the first AC port, the CE device belongs to the PE device.

As shown in fig. 3, a network architecture diagram of a single homing state in one embodiment of the present application. The involved network entities include CE device 111, CE device 112, PE device 121, PE device 122, PE device 123.PE device 121 and PE device 122 are route reachable. The PE devices form a service provider network backbone 120.

The CE device 111 is connected to the PE device 121 through the link 131 of the first AC, that is, the CE device 111 belongs to the PE device 121; CE device 112 is connected to PE device 122 via link 134 of the second AC, i.e., CE device 112 is exclusively owned by PE device 122.

When CE device 111 sends BUM traffic to PE device 121, the device interface of PE device 121 and the AC port of link 131 of the first AC do not have configuration ESI, CE device 111 is single-homed. The Ethernet Segment Identifier1 field of the NLRI packet of the PE device 121 carries a value of 0, the Ethernet Segment Identifier2 field carries a value of 0, and the values are 0 according to the Ethernet Segment Identifier1 field and the Ethernet Segment Identifier2 field. The Ethernet Segment Identifier1 field and the Ethernet Segment Identifier2 field are set to 0 values for representing unconfigured ESI values, so that other modes, such as blank and special value modes, can be used for representing.

And when the single-homing is carried out, the ES-AD routing NLRI message and the M-ES routing NLRI message are not sent so as to save resources.

And if the first ESI field carries the ESI of the device interface of the PE device and/or the second ESI word carries the ESI of the first AC port, the CE device belongs to the PE device and the second PE device in a dual-attribute mode.

As shown in fig. 4, a network architecture diagram of a dual-homed state in one embodiment of the present application. The involved network entities include CE device 111, CE device 112, PE device 121, PE device 122, PE device 123.PE device 121 and PE device 122 are routable. The PE devices form a service provider network backbone 120.

CE device 111 is connected to PE device 121 through link 131 of the first AC, and CE device 111 is connected to PE device 122 through link 132 of the first AC, that is, CE device 111 belongs to both PE device 121 and PE device 122; CE device 112 is connected to PE device 121 via link 133 of the second AC, and CE device 112 is connected to PE device 122 via link 134 of the second AC, i.e. CE device 112 belongs to both PE device 121 and PE device 122.

When the CE device 111 sends the BUM traffic to the PE device 121, the device port of the PE device 121 and/or the AC port configuration ESI of the link 131 of the first AC, and the CE device 111 is dual-homed, the Ethernet Segment Identifier1 field of the NLRI packet of the PE device 121 carries the ESI of the device interface configuration of the PE device 121 and/or the Ethernet Segment Identifier2 field carries the ESI of the AC port configuration of the link 131 of the first AC, according to the ESI carried by the Ethernet Segment Identifier1 field and/or the Ethernet Segment Identifier2 field.

In step 204, a label of the BUM traffic sent by the PE to the second PE device is generated based on the attribution relationship of the NLRI message identifier.

The step of generating the label of the BUM flow sent by the PE to the second PE device comprises the following steps:

and if the attribution relationship of the CE equipment is single attribution, not generating the ESI label.

As shown in fig. 3, the PE device 121 receives the BUM traffic sent by the CE device 111, and does not add an ESI label to the BUM traffic.

If the attribution relationship of the CE equipment is dual-attribution and the second ESI field carries the ESI of the first AC port, generating an ESI label based on the ESI of the first AC port of the second ESI field;

and if the attribution relationship of the CE equipment is dual-attribution and the second ESI field does not carry the ESI of the first AC port, generating an ESI label based on the ESI of the equipment interface of the PE equipment in the first ESI field.

As shown in fig. 4, the PE device 121 receives the BUM traffic sent by the CE device 111, and if the second ESI field carries the ESI of the AC port of the link 131 of the first AC, generates an ESI tag based on the ESI of the AC port of the link 131 of the first AC; if the second ESI field does not carry ESI of the AC port of the link 131 of the first AC, generating an ESI tag based on ESI of the device interface of the PE device 121 of the first ESI field, and adding the ESI tag to the BUM traffic. Before adding the label, checking whether the ESI value of the equipment interface configuration is the same as the ESI value of the first AC link AC port configuration, and if so, returning failure.

The PE device and the second PE device are reachable through routing.

As shown in fig. 3, the PE device 121 and the PE device 122 are connected through a public network tunnel 141, the PE device 121 and the PE device 122 are reachable by routing, and the PE device 121 and the PE device 122 are in a same network segment.

As shown in fig. 4, the PE device 121 and the PE device 122 are connected through a public network tunnel 141, the PE device 121 and the PE device 122 are reachable by routing, and the PE device 121 and the PE device 122 are in a same network segment.

The public network tunnel 141 is a tunnel that traverses an IP or MPLS backbone, and in this embodiment, the public network tunnel may be an MPLS tunnel.

In step 206, the PE device establishes a PW connection with a second PE device, where the PW connection is a pair of unidirectional virtual connections in opposite directions; and sending the BUM flow to a second AC port of a second PE device through the PW connection.

As shown in fig. 3, PE device 121 establishes a PW connection with PE device 122. The PE device 121 sends the BUM traffic to the PE device 122 via the PW connection, and the PE device 122 checks that the BUM traffic does not carry an ESI tag, and thus sends the BUM traffic to the CE device 112 via the AC port of the link 134 of the second AC.

As shown in fig. 4, PE device 121 establishes a PW connection with PE device 122. The link 133 of the second AC of the PE device 121 is a backup link, so the PE device 121 sends the BUM traffic to the PE device 122 over the PW connection. PE device 122 checks that the BUM traffic ESI label is different from its ESI and therefore sends the BUM traffic to CE device 112 via the AC port of link 134 of the second AC.

The method is described below with reference to specific examples.

In the embodiment of the present application, the format of the NLRI packet of the ES-AD route is shown in the following table:

route distingguisher (RD, 8 bytes)
	Ethernet Segment Identifier1 (first ESI,10 bytes)
Ethernet Segment Identifier2 (second ESI,10 bytes)
	Ethernet Tag ID (Ethernet Tag ID,4 bytes)
MPLS Label (MPLS Label, 3 bytes)

The format of the NLRI message of the M-MAC/IP route is shown in the following table:

the format of the NLRI message of the M-ES route is shown in the following table:

and identifying the attribution relationship between the CE equipment and the PE equipment based on the NLRI message. The Ethernet Segment Identifier1 field of the NLRI message carries the ESI configured by the equipment interface of the PE equipment, and the Ethernet Segment Identifier2 field of the NLRI message carries the ESI configured by the AC interface.

As shown in fig. 1, the PE device 121 and the PE device 122 are connected through a public network tunnel 141, the PE device 121 and the PE device 122 are reachable by routing, and the PE device 121 and the PE device 122 are in a same network segment. The PE devices form a service provider network backbone 120. The CE device 111 is connected to the PE device 121 and the PE device 122 through an AC link, the CE device 112 is connected to the PE device 121 and the PE device 122 through an AC link, and the CE device 113 is connected to the PE device 123 through an AC link, so that the CE device 111 and the CE device 112 are dual-homed, and the CE device 113 is single-homed. Link 131 and link 132 of CE device 111 belong to a first AC; link 133 and link 134 of CE device 112 belong to a second AC; link 135 of CE device 113 belongs to the third AC.

When CE device 111 needs to send BUM traffic to CE device 112, the device port configuration of PE device 121 and the AC port configuration ESI of link 131 of the first AC, CE device 111 is dual-homed, ethernet Segment Identifier1 field of NLRI packet of PE device 121 carries ESI of device interface configuration of PE device 121, ethernet Segment Identifier2 field carries ESI of AC port configuration of link 131 of the first AC, according to ESI carried by Ethernet Segment Identifier2 field.

Checking whether the ESI of the device interface configuration is the same as the ESI of the first AC link AC port configuration, and if so, returning a failure. If not, when the PE device 121 receives the BUM traffic sent by the CE device, an ESI tag is generated according to ESI of the AC port of the link 131 of the first AC, and is added to the BUM traffic.

The PE device 121 and the PE device 122 are connected through a public network tunnel 141, the PE device 121 and the PE device 122 are reachable through a route, and the PE device 121 and the PE device 122 are in a same network segment. The public network tunnel 141 is a tunnel traversing an IP or MPLS backbone, and in the embodiment of the present application, the public network tunnel may be an MPLS tunnel.

PE device 121 establishes a PW connection with PE device 122. The PE device 121 sends the BUM traffic to the PE device 122 through the PW connection, and the PE device 122 checks that the ESI tag ESI of the BUM traffic is different from the ESI of its device interface, so that the BUM traffic is sent to the CE device 112 through the AC port of the link 134 of the second AC.

When CE device 112 needs to send BUM traffic to CE device 111, since CE device 112 belongs to both sides, ethernet Segment Identifier1 field of NLRI packet of PE device 122 carries ESI configured for device interface of PE device 122, and Ethernet Segment Identifier2 field carries 0 value.

Checking whether the ESI of the device interface configuration is the same as the ESI of the first AC link AC port configuration, and if so, returning a failure. If not, when the PE device 122 receives the BUM traffic sent by the CE device, it generates an ESI tag according to ESI of its device interface, and adds the ESI tag to the BUM traffic.

The PE device 122 sends the BUM traffic to the PE device 121 through the PW connection, and the PE device 121 checks that the ESI label ESI of the BUM traffic is different from the ESI of the AC port of the link 131 of the first AC, and thus sends the BUM traffic to the CE device 111 through the AC port of the link 131 of the first AC.

In another embodiment of the present application, the ESI value may also be configured at the AC port of the link 134 of the second AC. When the PE device 121 sends the BUM traffic to the PE device 122 via the PW connection, the PE device 122 checks that the ESI tag ESI of the BUM traffic is different from the ESI of the AC port of the link 134 of the second AC, and thus sends the BUM traffic to the CE device 112 via the AC port of the link 134 of the second AC; when the PE device 122 sends the BUM traffic to the PE device 121 via the PW connection, the PE device 121 checks that the ESI tag ESI of the BUM traffic is different from the ESI of the AC port of the link 131 of the first AC, and thus sends the BUM traffic to the CE device 111 via the AC port of the link 131 of the first AC.

When the CE device 113 needs to send the BUM traffic to the CE device 112, the device interface of the PE device 123 and the AC interface of the link 135 of the third AC do not configure the ESI, the CE device 113 is single-homed, the Ethernet Segment Identifier1 field of the NLRI packet of the PE device 123 carries a value 0, the Ethernet Segment Identifier2 field carries a value 0, and both the Ethernet Segment Identifier1 field and the Ethernet Segment Identifier2 field are values 0.

The PE device 123 does not send the ES-AD routing NLRI message and the M-ES routing NLRI message to save resources.

The PE device 123 does not generate an ESI tag when receiving the BUM traffic sent by the CE device.

The PE device 122 and the PE device 123 are connected through a public network tunnel 141, where the public network tunnel 141 is a tunnel that traverses an IP or MPLS backbone, and in this embodiment, the public network tunnel may be an MPLS tunnel.

PE device 122 establishes a PW connection with PE device 123.PE device 123 sends the BUM traffic to PE device 122 over the PW connection, PE device 122 checks that the BUM traffic does not have an ESI tag, and therefore sends the BUM traffic to CE device 112 over the AC port of link 134 of the second AC.

As shown in fig. 5, fig. 5 is a block diagram of an apparatus 500 for forwarding BUM traffic according to an embodiment of the present specification, the apparatus including:

an attribution relation determining module 510, configured to identify, based on the NLRI packet, an attribution relation between the first CE device and each PE device, where the attribution relation includes dual attribution, and the dual attribution is that the first CE device belongs to the PE device and the second PE device at the same time; the NLRI message includes a first ESI field and a second ESI field, where the first ESI field is used to carry ESI configured for an equipment interface of the PE equipment, and the second ESI field is used to carry ESI configured for a first AC port of the PE equipment;

a traffic forwarding module 520, configured to receive a BUM traffic sent by a first CE device, and add an ESI tag to the BUM traffic according to an attribution relationship between the first CE device and each PE device; and determining the matched attribution relationship based on the ESI label, and sending the BUM flow to a second CE device through a second AC port of a second PE device under the condition that the first CE device and the second CE device are in the same dual-attribution relationship.

The detailed details of the implementation process of the functions and actions of each module in the above device are given in the implementation process of the corresponding steps in the above method, and are not described again here.

The embodiments of forwarding BUM traffic in this specification can be applied to network devices, such as PE devices. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor in which the file processing is located. From a hardware aspect, as shown in fig. 6, the hardware structure diagram of the router device where the file processing apparatus is located in the embodiment of this specification is shown in fig. 6, except for the processor 610, the memory 630, the network interface 620, and the nonvolatile memory 640 shown in fig. 6, the PE device where the apparatus 631 is located in the embodiment may also include other hardware according to an actual function of the network device, which is not described 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 modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

Correspondingly, an embodiment of the present specification further provides a PE device, where the PE device includes a memory, a processor, and a computer program stored in the memory and running on the memory, and when the processor executes the program, the method for forwarding the BUM traffic in any of the above embodiments is implemented.

Accordingly, the embodiments of the present specification further provide a computer storage medium, on which a computer program is stored, and when the program is executed by a processor, the computer storage medium implements the method for forwarding BUM traffic in any of the above embodiments.

This application may take the form of a computer program product embodied on one or more storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having program code embodied therein. Computer-usable storage media include permanent and non-permanent, removable and non-removable media, and may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of the storage medium of the computer include, but are not limited to: phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technologies, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic tape storage or other magnetic storage devices, or any other non-transmission medium, may be used to store information that may be accessed by a computing device.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the specification disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present description is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. A method for forwarding broadcast, unknown unicast and multicast BUM traffic is applied to PE equipment, and is characterized in that the method comprises the following steps:

identifying an attribution relationship between first CE equipment and each PE equipment based on an NLRI message, wherein the attribution relationship comprises dual attribution, and the dual attribution is that the first CE equipment belongs to the PE equipment and a second PE equipment at the same time; the NLRI message includes a first ESI field and a second ESI field, where the first ESI field is used to carry ESI configured for an equipment interface of the PE equipment, and the second ESI field is used to carry ESI configured for a first AC port of the PE equipment;

2. The method of claim 1, wherein the NLRI packet includes any one of:

ES-AD routing messages, M-MAC/IP routing messages and M-ES routing messages.

3. The method of claim 1, wherein the step of determining the affiliation of the first CE device with the PE device comprises:

if the first ESI field does not carry ESI of an equipment interface of the PE equipment and the second ESI field does not carry ESI of the first AC port, the CE equipment is single-homed to the PE equipment;

and if the first ESI field carries the ESI of the device interface of the PE device and/or the second ESI word carries the ESI of the first AC port, the CE device belongs to the PE device and the second PE device.

4. The method according to claim 3, further comprising generating a label of the BUM traffic sent by the PE device to a second PE device based on the attribution of the NLRI packet identifier.

5. The method according to claim 4, wherein the step of generating a label of the BUM traffic sent by the PE device to the second PE device comprises:

if the attribution relationship of the CE equipment is single attribution, not generating an ESI label;

6. The method of claim 1, further comprising:

and the PE equipment and the second PE equipment can reach the routing.

7. The method of claim 6, further comprising:

the PE equipment and second PE equipment establish PW connection, and the PW connection is a pair of unidirectional virtual connections in opposite directions;

and sending the BUM flow to a second AC port of a second PE device through the PW connection.

8. An apparatus for forwarding broadcast, unknown unicast, multicast BUM traffic, the apparatus comprising:

an attribution relation determining module, configured to identify an attribution relation between a first CE device and each PE device based on an NLRI packet, where the attribution relation includes dual attribution, and the dual attribution is that the first CE device belongs to both the PE device and a second PE device; the NLRI message includes a first ESI field and a second ESI field, where the first ESI field is used to carry ESI configured for an equipment interface of the PE equipment, and the second ESI field is used to carry ESI configured for a first AC port of the PE equipment;

9. A PE device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to perform the method of any one of claims 1-7.

10. A storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method of any one of claims 1-7.