CN108632125B

CN108632125B - Multicast table item management method, device, equipment and machine readable storage medium

Info

Publication number: CN108632125B
Application number: CN201810367015.XA
Authority: CN
Inventors: 陈建
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2018-04-23
Filing date: 2018-04-23
Publication date: 2020-12-29
Anticipated expiration: 2038-04-23
Also published as: CN108632125A

Abstract

The application provides a multicast table item management method, a multicast table item management device, multicast table item management equipment and a machine-readable storage medium, wherein the method comprises the following steps: receiving a first route notification message sent by a second PE device, wherein the first route notification message comprises address information of a multicast group to which a CE device belongs, a first multicast protocol version identifier and a first priority; if a multicast list item corresponding to the address information of the multicast group exists and the first multicast protocol version identification is different from the second multicast protocol version identification in the multicast list item, comparing the first priority with the second priority in the multicast list item; and if the first priority is superior to the second priority, replacing the second multicast protocol version identification and the second priority in the multicast list item by using the first multicast protocol version identification and the first priority. By the technical scheme, the multicast protocol version identification can be prevented from being wrong, so that the multicast list item is correct, the multicast protocol version identification of the multicast list item is correctly updated, and the user experience is improved.

Description

Multicast table item management method, device, equipment and machine readable storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a multicast table entry management method, apparatus, device, and machine-readable storage medium.

Background

An EVPN (Ethernet Virtual Private Network) is a two-layer VPN (Virtual Private Network) technology, where a control plane uses MP-BGP (Multi Protocol-Border Gateway Protocol) to announce routing information, and a data plane uses VXLAN (Virtual Extensible Local Area Network) encapsulation to forward a packet. VXLAN is a two-layer VPN technology based on an IP network and adopting a "MAC (Media Access Control) in UDP (User Datagram Protocol)" encapsulation form, and VXLAN may provide two-layer interconnection for distributed sites and may provide service isolation for different tenants based on an existing service provider or an existing enterprise IP network.

In EVPN, in order to improve reliability, a multi-homing access networking may also be adopted, that is, a CE (Customer Edge) device accesses a plurality of PE (Provider Edge) devices, and it is assumed that a PE device 1 and a PE device 2 are accessed. Based on this, if the CE device may send different multicast join messages to the PE device 1 and the PE device 2 at different time intervals, the multicast entries generated by the PE device 1 and the PE device 2 may be inconsistent, which may cause a forwarding error to occur when the PE device 1 and the PE device 2 forward data belonging to the CE device.

Disclosure of Invention

The application provides a multicast table item management method, a multicast table item management device and a machine-readable storage medium, which are used for enabling multicast table items generated by a plurality of PE devices connected with the same CE device to be consistent and solving the problem of forwarding errors of the PE devices due to inconsistency of the multicast table items.

In one aspect, the present application provides a multicast entry management method, which is applied to a first PE device in a multi-homing networking, where the multi-homing networking further includes a second PE device and a CE device, and the CE device accesses the first PE device and the second PE device in a multi-homing manner, where the method includes:

receiving a first route notification message sent by the second PE device, where the first route notification message includes multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs, a first multicast protocol version identifier used when the CE device accesses the multicast group, and a first priority corresponding to the first multicast protocol version identifier;

if a multicast list item corresponding to the address information of the multicast group exists and the first multicast protocol version identification is different from the second multicast protocol version identification in the multicast list item, comparing the first priority with a second priority corresponding to the second multicast protocol version identification in the multicast list item;

and if the first priority is superior to the second priority, replacing the second multicast protocol version identification and the second priority in the multicast list item by using the first multicast protocol version identification and the first priority.

In another aspect, the present application provides a multicast table entry management apparatus, which is applied to a first PE device in a multi-homing networking, where the multi-homing networking further includes a second PE device and a CE device, and the CE device accesses the first PE device and the second PE device in a multi-homing manner, where the apparatus includes:

a receiving module, configured to receive a first route advertisement message sent by the second PE device, where the first route advertisement message includes multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs, a first multicast protocol version identifier used when the CE device accesses the multicast group, and a first priority corresponding to the first multicast protocol version identifier;

a comparing module, configured to compare a first priority with a second priority corresponding to a second multicast protocol version identifier in the multicast entry if a multicast entry corresponding to the address information of the multicast group exists and the first multicast protocol version identifier is different from the second multicast protocol version identifier in the multicast entry;

and the processing module is used for replacing the second multicast protocol version identifier and the second priority in the multicast list item by using the first multicast protocol version identifier and the first priority if the first priority is superior to the second priority.

In yet another aspect, the present application provides a PE device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute machine-executable instructions to perform the method steps described above.

In yet another aspect, the present application provides a machine-readable storage medium having stored thereon machine-executable instructions that, when invoked and executed by a processor, cause the processor to perform the method steps described above.

Based on the above technical solution, in this embodiment of the application, after receiving a route notification message sent by a second PE device, a first PE device may obtain address information of a multicast group, a first multicast protocol version identifier, and a first priority from the route notification message; if a multicast list item corresponding to the address information of the multicast group exists and the first multicast protocol version identification is different from the second multicast protocol version identification in the multicast list item, comparing the first priority with the second priority in the multicast list item; if the first priority is superior to the second priority, replacing the second multicast protocol version identification in the multicast list item by using the first multicast protocol version identification; if the first priority is not better than the second priority, the second multicast protocol version identification in the multicast list item is reserved. Therefore, the multicast protocol version identification in the multicast list item can be determined based on the priority, the error of the multicast protocol version identification is avoided, the multicast list item is correct, the multicast protocol version identification of the multicast list item is correctly updated, the user experience is improved, and the forwarding error when the data belonging to the CE equipment is forwarded is avoided.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.

FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;

fig. 2A and fig. 2B are flowcharts illustrating a multicast entry management method according to an embodiment of the present application;

fig. 3 is a block diagram of a multicast table entry management apparatus according to an embodiment of the present application;

fig. 4 is a hardware structure diagram of a PE device according to an embodiment of the present application.

Detailed Description

The terminology used in the embodiments of the present application 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 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 is meant to encompass 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 in the embodiments of the present application to describe various information, the 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. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".

The embodiment of the application provides a multicast table item management method, which can be applied to EVPN adopting multi-homing access networking. In EVPN, to improve reliability, a multi-homed access service may be provided for CE devices by at least two PE devices. Referring to fig. 1, a schematic view of an application scenario of the embodiment of the present application is shown, taking an example that two PE devices provide a multi-homing access service for a CE device, in an actual application, more PE devices may also provide a multi-homing access service for a CE device, which is not limited to this.

The PE device 121 and the PE device 122 are configured to provide a multi-home access service for the CE device 111, and a link between the PE device 121 and the CE device 111 and a link between the PE device 122 and the CE device 111 are referred to as ES (Ethernet Segment), where the ES is represented by ESI (Ethernet Segment Identifier). The link between the PE device 121 and the CE device 111 and the link between the PE device 122 and the CE device 111 correspond to the same ESI, for example, the ESI of the link between the PE device 121 and the CE device 111 is 1, and the ESI of the link between the PE device 122 and the CE device 111 is 1.

Referring to fig. 1, it can be understood that VXLAN mechanism is run in PE device 121 and PE device 122. For example, the PE devices establish a VXLAN tunnel between themselves, associate the VXLAN tunnel with a local VXLAN, identify the VXLAN to which the received message (sent by the CE device) belongs, so as to learn the source MAC address in the message to the VSI corresponding to the VXLAN, forward the message in the VSI, learn the MAC address of the CE device, forward the message according to the learned MAC address table entry, and so on.

In this embodiment of the present application, on a PE device, a three-layer interface or an ethernet Service Instance (Service Instance) managed by a VSI (Virtual Switch Instance) is referred to as an AC (access Circuit) or an AC port. The PE device associates the local AC with the VSI. After the PE equipment receives the data message sent by the CE equipment, the VSI associated with the PE equipment is searched, and a VXLAN is established in the VSI, wherein the established VXLAN is the VXLAN to which the data message belongs. Meanwhile, it can be understood that the AC receiving the data packet is also an output interface for subsequently forwarding the data packet to the CE device.

In the embodiment of the present application, the link between the PE device 121 and the CE device 111 through the AC1211 and the link between the PE device 122 and the CE device 111 through the AC1221 have the same ESI. It is understood that the VXLAN mechanism operating between PE devices is an existing VXLAN mechanism and will not be repeated here. The PE device and the CE device access a service for multiple affiliations, that is, in the networking environment provided in the embodiment of the present invention, the same CE device is connected to different PE devices through multiple links.

In the application scenario, the multicast entry management method in this embodiment may include the following steps:

step 211, the CE device 111 sends a multicast join message to the PE device 121, where the multicast join message may carry address information of a multicast group and a multicast protocol version identifier used when the CE device 111 accesses the multicast group. The address information of the multicast group includes a source address (source) and a group address (group), for example, the source address is 225.0.0.1, and the group address is 192.168.0.1. If the CE device 111 currently accesses the multicast group using version 1 of the IGMP protocol (hereinafter, abbreviated as V1), the multicast protocol version is identified as V1.

The CE device 111 may select a PE device from the PE devices 121 and 122, for example, randomly select a PE device or select a PE device by using a hash algorithm, which is not limited to this selection manner, and assuming that the PE device 121 is selected, the CE device 111 sends a multicast join packet to the selected PE device 121.

In step 212, after receiving the multicast join packet, the PE device 121 parses the address information and the multicast protocol version identifier of the multicast group from the multicast join packet. Because there is no multicast entry corresponding to the address information of the multicast group, a multicast entry is generated, where the multicast entry includes the address information of the multicast group (the address information may be a KEY value of the current multicast entry), the multicast protocol version identifier, and an initial priority (e.g., priority 1). The output interface of the multicast entry is an interface, such as AC1211, that receives the multicast join message.

Referring to table 1, an example of the multicast table entry is shown, and the content of the multicast table entry is not limited.

TABLE 1

Address information of multicast group	Multicast protocol version identification	Priority level	Outlet interface
				A source address 225.0.0.1; group address 192.168.0.1	V1	1	AC1211

In step 213, PE device 121 sends a route advertisement message (e.g., a BGP route advertisement message, etc.) to PE device 122. The route advertisement message may carry address information (e.g., source address 225.0.0.1 and group address 192.168.0.1), multicast protocol version identification (e.g., V1), and priority (e.g., priority 1) of the multicast group in the multicast entry. In addition, the route advertisement message may also carry ESI 1 corresponding to AC 1211.

In step 214, after receiving the route advertisement message, the PE device 122 obtains address information, multicast protocol version identifier, priority, and ESI (for example, ESI 1) of the multicast group from the route advertisement message; since there is no multicast entry corresponding to the address information of the multicast group, the PE device 122 generates a multicast entry, which may include the address information of the multicast group, the multicast protocol version identifier, and the priority. In addition, the output interface of the multicast table entry is the AC corresponding to the ESI.

Referring to table 2, an example of the multicast table entry is shown, and the content of the multicast table entry is not limited.

TABLE 2

Address information of multicast group	Multicast protocol version identification	Priority level	Outlet interface
				A source address 225.0.0.1; group address 192.168.0.1	V1	1	AC1221

In an example, after receiving the route advertisement message, if the route advertisement message carries ESI, and the ESI is the same as ESI 1 configured by the PE device 122 for the CE device 111, the PE device 122 generates the multicast entry shown in table 2, where an outgoing interface of the multicast entry is AC1221 corresponding to ESI 1.

In addition, if the route notification message does not carry ESI, or the ESI carried by the route notification message is different from the ESI 1 configured by the PE device 122 for the CE device 111, when the multicast entry is generated, the outgoing interface is a VXLAN tunnel between the PE device 122 and the PE device 121, instead of AC1221, and other contents of the multicast entry are similar to those in table 2, which is not described herein again, and in the subsequent process, the description is given by taking table 2 as an example.

Step 215, after modifying the currently used multicast protocol version identifier to version 2, the CE device 111 sends a multicast join message to the PE device 122, where the multicast join message may carry address information of a multicast group and a multicast protocol version identifier, and the address information of the multicast group includes a source address and a group address, for example, the source address is 225.0.0.1, and the group address is 192.168.0.1. If the CE device 111 currently accesses the multicast group using version 2 of the IGMP protocol (hereinafter, abbreviated as V2), the multicast protocol version is identified as V2.

The CE device 111 may select a PE device from the PE devices 121 and 122, for example, randomly select a PE device or select a PE device by using a hash algorithm, and the selection manner is not limited, and assuming that the PE device 122 is selected, the CE device 111 sends a multicast join packet to the selected PE device 122.

In step 216, after receiving the multicast join packet, the PE device 122 parses the address information and the multicast protocol version identifier of the multicast group from the multicast join packet. Because there is a multicast entry (as shown in table 2) corresponding to the address information of the multicast group, and the multicast protocol version identifier (e.g., V2) carried in the multicast join packet is different from the multicast protocol version identifier (e.g., V1) in the multicast entry, the PE device 122 may replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier carried in the multicast join packet, and adjust the priority in the multicast entry, and the adjusted priority is greater than the priority before adjustment, for example, priority 1 in the multicast entry may be adjusted to priority 2.

For example, the PE device 122 may modify the multicast entry shown in table 2 to the multicast entry shown in table 3, although table 3 is only an example of the multicast entry, and the content of the multicast entry is not limited.

TABLE 3

Address information of multicast group	Multicast protocol version identification	Priority level	Outlet interface
				A source address 225.0.0.1; group address 192.168.0.1	V2	2	AC1221

In an example, after receiving the multicast join message, if the multicast protocol version identifier carried in the multicast join message is the same as the multicast protocol version identifier in the multicast entry, the PE device 122 may not update the multicast entry, and end the process.

In step 217, PE device 122 sends a route advertisement message (e.g., BGP route advertisement message, etc.) to PE device 121. The route advertisement message may carry address information (e.g., source address 225.0.0.1 and group address 192.168.0.1), multicast protocol version identification (e.g., V2), and priority (e.g., priority 2) of the multicast group in the multicast entry. In addition, the route advertisement message may also carry ESI 1 corresponding to AC 1221.

In step 218, after receiving the route advertisement message, the PE device 121 acquires the address information, the multicast protocol version identifier, the priority, and the ESI (for example, ESI 1) of the multicast group from the route advertisement message. Since there is a multicast entry (as shown in table 1) corresponding to the address information of the multicast group, and the multicast protocol version identifier (e.g., V2) carried by the route advertisement message is different from the multicast protocol version identifier (e.g., V1) in the multicast entry, the priority (e.g., priority 2) carried by the route advertisement message may be compared with the priority (e.g., priority 1) in the multicast entry.

After receiving the route notification message, if the multicast protocol version identifier carried in the route notification message is the same as the multicast protocol version identifier in the multicast entry, the PE device 121 may not update the multicast entry, and end the process.

In an example, after receiving the route advertisement message, if the PE device 121 carries ESI in the route advertisement message and the ESI is the same as ESI 1 configured by the PE device 121 for the CE device 111, the PE device 121 may compare the priority carried in the route advertisement message with the priority in the multicast entry.

In addition, if the route advertisement message does not carry ESI, or the ESI carried by the route advertisement message is different from the ESI 1 configured by the PE device 121 for the CE device 111, the PE device 121 may generate a multicast entry, and when the multicast entry is generated, an outgoing interface is a VXLAN tunnel between the PE device 121 and the PE device 122, instead of the AC1211, and other contents of the multicast entry are similar to those in table 1, which is not described herein again.

In step 219, if the priority carried by the route notification message is higher than the priority in the multicast entry, the PE device 121 may replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier carried by the route notification message, and replace the priority in the multicast entry with the priority carried by the route notification message. If the priority in the multicast entry is higher than the priority carried in the route notification message, the PE device 121 may reserve the multicast protocol version identifier and the priority in the multicast entry, and end the process.

If the priority carried by the route notification message is equal to the priority in the multicast entry, the PE device 121 may determine to replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier carried by the route notification message according to the IP address of the PE device 121 and the IP address of the PE device 122, and replace the priority in the multicast entry with the priority carried by the route notification message; or determining to reserve the multicast protocol version identification and the priority in the multicast table entry. For example, the PE device 121 may further compare the IP address of the PE device 121 with the IP address of the PE device 122, and if the IP address of the PE device 122 is smaller than the IP address of the PE device 121, the multicast protocol version identifier in the multicast entry may be replaced by the multicast protocol version identifier carried in the route notification message, and the priority in the multicast entry may be replaced by the priority carried in the route notification message. If the IP address of the PE device 121 is smaller than the IP address of the PE device 122, the multicast protocol version identification and priority in the multicast entry may be retained.

In step 219, because the priority (e.g., priority 2) carried by the route notification message is higher than the priority (e.g., priority 1) in the multicast entry, the PE device 121 may replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier carried by the route notification message, and replace the priority in the multicast entry with the priority carried by the route notification message. For example, the multicast entry shown in table 1 is modified to the multicast entry shown in table 4, and table 4 is only an example of the multicast entry, which is not limited to this.

TABLE 4

Address information of multicast group	Multicast protocol version identification	Priority level	Outlet interface
				A source address 225.0.0.1; group address 192.168.0.1	V2	2	AC1211

In a conventional manner, the route notification message does not carry a priority, and the multicast entry does not include a priority, so that after receiving the route notification message, if the multicast protocol version identifier carried in the route notification message is V2 and the multicast protocol version identifier in the multicast entry is V1, the PE device 121 reserves V1 in the multicast entry, or replaces V1 with V2 carried in the route notification message, and the PE device 121 does not have an accurate processing manner, which may cause an error in the multicast protocol version identifier of the multicast entry.

Different from the foregoing manner, in the embodiment of the present application, the route notification message carries a priority, and the multicast table entry includes a priority, so that if the priority carried by the route notification message is better than the priority in the multicast table entry, V2 carried by the route notification message may be used to replace V1, and if the priority in the multicast table entry is better than the priority carried by the route notification message, V1 in the multicast table entry may be retained. Therefore, the multicast protocol version identification in the multicast list item can be determined based on the priority, and the multicast protocol version identification in the multiple PE devices is prevented from being wrong, so that the multicast list item contents in the multiple PE devices are consistent.

In step 219, the route advertisement message may further include ESI 1, where ESI 1 is used to instruct the CE device 111 to access multiple links when accessing different PE devices; if the priority carried by the route advertisement message is better than the priority in the multicast entry, the PE device 121 may further send an inquiry request carrying address information of the multicast group to the CE device 111 connected to the multiple links represented by the ESI 1, where the inquiry request is used to request a multicast protocol version identifier corresponding to the address information of the multicast group.

After receiving the query request, the CE device 111 may locally obtain a multicast protocol version identifier (e.g., V2) corresponding to the address information of the multicast group, and return a query response carrying the multicast protocol version identifier to the PE device 121.

Further, if the PE device 121 receives an inquiry response returned by the CE device 111 in response to the inquiry request, and the multicast protocol version identifier carried in the inquiry response is the multicast protocol version identifier carried in the route notification message (i.e., V2), the PE device 121 may replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier carried in the route notification message, and replace the priority in the multicast entry with the priority carried in the route notification message.

In addition, if the multicast protocol version identifier carried in the query response is the multicast protocol version identifier in the multicast entry (i.e., V1), the PE device 121 may reserve the multicast protocol version identifier and the priority in the multicast entry.

In one example, where the PE device 121 sends a query request to the CE device 111, the effect may include:

in case one, if an attacker attacks the PE device 121, and sends a route advertisement message carrying a high priority to the PE device 121, and sends a query request to the CE device 111, it is possible to avoid modifying the multicast protocol version identifier in the multicast entry into the multicast protocol version identifier of the attacker, avoid making mistakes in the multicast protocol version identifier, and improve security.

In case two, after the CE device 111 sends the multicast join message carrying V1 to the PE device 122, the multicast protocol version identifier is modified to V2, and the multicast join message carrying V2 is sent to the PE device 121. Thus, the multicast protocol version id in the multicast entry of PE device 121 is V2, and the multicast protocol version id in the route advertisement message sent by PE device 122 to PE device 121 is V1. Assuming that the priority in the route advertisement message is higher than the priority in the multicast entry, the PE device 121 sends the query request to the CE device 111, so as to avoid modifying V2 in the multicast entry into the wrong V1, avoid making a multicast protocol version identification error, and improve the accuracy.

In the above embodiment, since the conventional route advertisement message does not include the priority, the conventional route advertisement message may be modified so that the route advertisement message may include the extended community attribute, that is, in the above route advertisement message, the priority may be carried by the extended community attribute.

The route advertisement message may include, but is not limited to: EVPN Route of 7 types (e.g. IGMP Join sync Route, i.e. the Join synchronization Route of Internet group management protocol), where the Route of 7 types is used to synchronize the address information of multicast group, the version identification of multicast protocol, etc. On this basis, an Extended Community attribute (e.g. IGMP Mobility Extended Community, i.e. IGMP migratable Extended Community attribute) may be added to the class 7 routes, and the priority is carried through the Extended Community attribute. For example, the extended community attribute includes a type field (type) for indicating that the type of the extended community attribute is a priority field and a Sequence Number field (Sequence Number) whose value represents a priority value, the priority being higher the priority value is.

In the above embodiment, when the CE device 112 transmits multicast data to the CE device 111, the PE device 123 receives the multicast data, and transmits the multicast data to the PE device 122 through the VXLAN tunnel a, or transmits the multicast data to the PE device 121 through the VXLAN tunnel B, which is not limited in this regard. After receiving the multicast data, the PE device 121 queries the multicast table entry shown in table 4 through the address information of the multicast group carried by the multicast data, obtains an output interface AC1211, and sends the multicast data to the CE device 111 through the AC 1211; or after receiving the multicast data, the PE device 122 queries the multicast entry shown in table 3 through the address information of the multicast group carried by the multicast data, obtains an output interface AC1221, and sends the multicast data to the CE device 111 through the AC 1221. The multicast data is successfully transmitted to CE device 111.

Based on the same application concept as the method described above, an embodiment of the present application further provides a multicast table management method, where the method may be applied to a first PE device in a multi-homing networking, where the multi-homing networking further includes a second PE device and a CE device, and the CE device is multi-homed to access the first PE device and the second PE device. Referring to fig. 1, the first PE device is a PE device 121, and the second PE device is a PE device 122, or the first PE device is the PE device 122, and the second PE device is the PE device 121. Referring to fig. 2A, a flowchart of the multicast entry management method is shown, where the method may include the following steps:

step 311, receiving a first route advertisement message sent by a second PE device, where the first route advertisement message includes multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs, a first multicast protocol version identifier used when the CE device accesses the multicast group, and a first priority corresponding to the first multicast protocol version identifier.

Step 312, if there is a multicast entry corresponding to the address information of the multicast group and the first multicast protocol version identifier is different from the second multicast protocol version identifier in the multicast entry, comparing the first priority with a second priority corresponding to the second multicast protocol version identifier in the multicast entry.

Step 313, if the first priority is better than the second priority, the second multicast protocol version id and the second priority in the multicast entry are replaced by the first multicast protocol version id and the first priority.

The first route advertisement message may further include ESI, where the ESI is used to indicate multiple links when the CE device accesses different PE devices; based on this, replacing the second multicast protocol version identification and the second priority in the multicast entry with the first multicast protocol version identification and the first priority may include, but is not limited to: and sending an inquiry request carrying the address information of the multicast group to CE equipment connected with the plurality of links represented by the ESI, wherein the inquiry request is used for requesting a multicast protocol version identifier corresponding to the address information of the multicast group. Further, receiving a query response returned by the CE device for the query request, and if the multicast protocol version identifier carried in the query response is the first multicast protocol version identifier, replacing the second multicast protocol version identifier and the second priority in the multicast entry with the first multicast protocol version identifier and the first priority.

For convenience of differentiation, the route advertisement message sent by the second PE device to the first PE device may be referred to as a first route advertisement message, the multicast protocol version identifier in the first route advertisement message may be referred to as a first multicast protocol version identifier, and the priority in the first route advertisement message may be referred to as a first priority. In addition, the multicast protocol version identification in the multicast entry may be referred to as a second multicast protocol version identification, and the priority in the multicast entry may be referred to as a second priority.

Taking the first PE device as the PE device 121 and the second PE device as the PE device 122, the implementation flow of steps 311 to 313 may refer to steps 218 to 219, which is not described in detail again.

For example, after receiving the first route notification message, the PE device 121 acquires the address information of the multicast group, the first multicast protocol version identifier, and the first priority from the first route notification message, and because there is a multicast entry corresponding to the address information of the multicast group, and the first multicast protocol version identifier is different from the second multicast protocol version identifier in the multicast entry, the first priority is superior to the second priority in the multicast entry, the PE device 121 replaces the second multicast protocol version identifier in the multicast entry with the first multicast protocol version identifier, and replaces the second priority in the multicast entry with the first priority.

In an example, after receiving a first route notification message sent by a second PE device, a first PE device may generate a multicast entry if there is no multicast entry corresponding to the address information of the multicast group; the multicast list item comprises address information of the multicast group, a first multicast protocol version identification and a first priority.

Taking the first PE device as the PE device 122 and the second PE device as the PE device 121, the above process may refer to step 214, which is not described again. For example, after receiving the first route notification message, the PE device 122 acquires the address information of the multicast group, the first multicast protocol version identifier, and the first priority from the first route notification message, and generates the multicast entry shown in table 2 because there is no multicast entry corresponding to the address information of the multicast group.

The processing flow shown in fig. 2A is a processing flow in which the first PE device receives the route advertisement message, and when the first PE device receives the multicast join packet sent by the CE device, the processing flow may also be as shown in fig. 2B, where the method may be applied to the first PE device, and the method may include the following steps:

step 321, receiving a multicast join message sent by the CE device, where the multicast join message includes multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs, and a multicast protocol version identifier used when the CE device accesses the multicast group.

Step 322, determine whether there is a multicast entry corresponding to the address information of the multicast group.

If so, step 323 may be performed; if not, step 324 may be performed.

Step 323, if the multicast protocol version identification carried by the multicast join message is different from the multicast protocol version identification in the multicast entry, replacing the multicast protocol version identification in the multicast entry with the multicast protocol version identification carried by the multicast join message, and adjusting the priority corresponding to the multicast protocol version identification in the multicast entry; wherein the adjusted priority is greater than the priority before adjustment; if the multicast protocol version identifier carried by the multicast join message is the same as the multicast protocol version identifier in the multicast entry, the multicast entry may not be updated, and the process is ended. After step 323, step 325 is performed.

In step 324, a multicast entry is generated, where the multicast entry may include address information of the multicast group, a multicast protocol version identifier, and an initial priority, which are carried in the multicast join packet. Step 325 is performed after step 324.

Step 325, sending a second route notification message to the second PE device, where the second route notification message carries the address information of the multicast group, the multicast protocol version identifier in the multicast entry, and the priority in the multicast entry.

Taking the first PE device as the PE device 121 and the second PE device as the PE device 122, the implementation flow of step 321 to step 325 can refer to step 212 to step 213, which is not described in detail again.

For example, after receiving the multicast join message sent by the CE device 111, the PE device 121 parses the address information and the multicast protocol version identifier of the multicast group from the multicast join message, and may generate the multicast entry shown in table 1 and send the route notification message to the PE device 122 because there is no multicast entry corresponding to the address information of the multicast group.

Taking the first PE device as the PE device 122 and the second PE device as the PE device 121 as an example, the implementation flows of step 321 to step 325 may refer to step 216 to step 217, which are not described in detail again.

For example, after receiving the multicast join packet sent by the CE device 111, the PE device 122 may analyze the address information and the multicast protocol version identifier of the multicast group from the multicast join packet, and because there is a multicast entry corresponding to the address information of the multicast group, the PE device 122 may replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier carried in the multicast join packet, adjust the priority in the multicast entry, and send a route notification message to the PE device 121.

Based on the same application concept as the method described above, an embodiment of the present application further provides a multicast table entry management apparatus, which is applied to a first PE device in a multi-homing networking, where the multi-homing networking further includes a second PE device and a CE device, and the CE device accesses the first PE device and the second PE device in a multi-homing manner, as shown in fig. 3, which is a structure diagram of the apparatus, and the apparatus includes:

a receiving module 31, configured to receive a first route advertisement message sent by the second PE device, where the first route advertisement message includes multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs, a first multicast protocol version identifier used when the CE device accesses the multicast group, and a first priority corresponding to the first multicast protocol version identifier;

a comparing module 32, configured to compare a first priority with a second priority corresponding to a second multicast protocol version identifier in the multicast entry if a multicast entry corresponding to the address information of the multicast group exists and the first multicast protocol version identifier is different from the second multicast protocol version identifier in the multicast entry;

a processing module 33, configured to replace the second multicast protocol version identifier and the second priority in the multicast entry with the first multicast protocol version identifier and the first priority if the first priority is higher than the second priority.

In one example, the multicast entry management apparatus may further include (not shown in the figure): a generating module, configured to generate a multicast entry if there is no multicast entry corresponding to the address information of the multicast group;

wherein the multicast entry includes address information of the multicast group, the first multicast protocol version identifier, and the first priority.

In one example, the first route advertisement message further includes an ethernet segment identity ESI, where the ESI is used to indicate a plurality of links when the CE device accesses different PE devices;

the processing module 33 is specifically configured to:

sending a query request carrying address information of the multicast group to CE equipment connected with a plurality of links represented by the ESI, wherein the query request is used for requesting a multicast protocol version identifier corresponding to the address information of the multicast group;

receiving a query response returned by the CE equipment for the query request;

and if the multicast protocol version identification carried by the query response is the first multicast protocol version identification, replacing the second multicast protocol version identification and the second priority by using the first multicast protocol version identification and the first priority.

The receiving module 31 is further configured to receive a multicast join packet sent by the CE device, where the multicast join packet includes the multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs and a multicast protocol version identifier used when the CE device accesses the multicast group;

the processing module 33 is further configured to, if a multicast entry corresponding to the address information of the multicast group exists and the multicast protocol version identifier is different from the multicast protocol version identifier in the multicast entry, replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier included in the multicast join packet, and adjust a priority level corresponding to the multicast protocol version identifier in the multicast entry; wherein the adjusted priority is greater than the priority before adjustment;

the generating module is further configured to generate a multicast entry if there is no multicast entry corresponding to the address information of the multicast group, where the multicast entry includes the address information of the multicast group, a multicast protocol version identifier included in the multicast join packet, and an initial priority.

In one example, the multicast entry management apparatus may further include (not shown in the figure): a sending module, configured to send a second route advertisement message to the second PE device, where the second route advertisement message includes address information of the multicast group, a multicast protocol version identifier in the multicast entry, and a priority in the multicast entry.

The route advertisement message further comprises an extended community attribute for carrying the priority.

Based on the technical scheme, in the embodiment of the application, the multicast protocol version identification in the multicast list item can be determined based on the priority, so that the multicast list item is correct, the multicast protocol version identification of the multicast list item is correctly updated, the user experience is improved, and the forwarding error when the data belonging to the CE equipment is forwarded is avoided.

For the PE device (such as the first PE device described above) provided in the embodiment of the present application, from a hardware level, a schematic diagram of a hardware architecture can be seen in fig. 4. The method comprises the following steps: a machine-readable storage medium and a processor, wherein: the machine-readable storage medium stores machine-executable instructions executable by the processor; the processor is configured to execute machine-executable instructions to implement the multicast entry management operations disclosed in the above examples.

A machine-readable storage medium is provided by embodiments of the present application that stores machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the multicast entry management operations disclosed in the above examples.

Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A multicast table item management method is applied to a first PE device in a multi-homing network, the multi-homing network further comprises a second PE device and a CE device, the CE device accesses the first PE device and the second PE device in a multi-homing manner, and the method comprises the following steps:

2. The method of claim 1,

after receiving the first route advertisement message sent by the second PE device, the method further includes:

if the multicast list item corresponding to the address information of the multicast group does not exist, generating a multicast list item;

3. The method of claim 1, wherein said first route advertisement message further comprises an ethernet segment identity ESI, said ESI indicating a plurality of links when said CE device accesses different PE devices;

the replacing the second multicast protocol version identifier and the second priority in the multicast entry with the first multicast protocol version identifier and the first priority includes: sending a query request carrying address information of the multicast group to CE equipment connected with a plurality of links represented by the ESI, wherein the query request is used for requesting a multicast protocol version identifier corresponding to the address information of the multicast group;

receiving a query response returned by the CE equipment for the query request;

4. The method of claim 1, further comprising:

receiving a multicast adding message sent by the CE device, wherein the multicast adding message comprises the multicast information, and the multicast information comprises address information of a multicast group to which the CE device belongs and a multicast protocol version identifier used when the CE device accesses the multicast group;

if a multicast list item corresponding to the address information of the multicast group exists and the multicast protocol version identification is different from the multicast protocol version identification in the multicast list item, replacing the multicast protocol version identification in the multicast list item with the multicast protocol version identification included in the multicast adding message and adjusting the priority corresponding to the multicast protocol version identification in the multicast list item; wherein the adjusted priority is greater than the priority before adjustment;

if the multicast list item corresponding to the address information of the multicast group does not exist, generating a multicast list item, wherein the multicast list item comprises the address information of the multicast group, a multicast protocol version identifier and an initial priority, and the multicast protocol version identifier and the initial priority are included in the multicast adding message.

5. The method of claim 4, further comprising:

and sending a second route notification message to the second PE device, wherein the second route notification message comprises address information of the multicast group, a multicast protocol version identifier in the multicast table item and a priority in the multicast table item.

6. The method according to any of claims 1-5, wherein said route advertisement message further comprises an extended community attribute, said extended community attribute being used to carry said priority.

7. The multicast table item management device is applied to a first PE device in a multi-homing networking, wherein the multi-homing networking further includes a second PE device and a CE device, the CE device has a multi-homing access to the first PE device and the second PE device, and the device includes:

8. The apparatus of claim 7, further comprising: a generating module, configured to generate a multicast entry if there is no multicast entry corresponding to the address information of the multicast group;

9. The apparatus according to claim 7, wherein the first route advertisement message further includes an ethernet segment identity ESI indicating a plurality of links when the CE device accesses different PE devices;

the processing module is specifically configured to: sending a query request carrying address information of the multicast group to CE equipment connected with a plurality of links represented by the ESI, wherein the query request is used for requesting a multicast protocol version identifier corresponding to the address information of the multicast group;

receiving a query response returned by the CE equipment for the query request;

10. The apparatus of claim 8,

the receiving module is further configured to receive a multicast join message sent by the CE device, where the multicast join message includes the multicast information, and the multicast information includes address information of a multicast group to which the CE device belongs and a multicast protocol version identifier used when the CE device accesses the multicast group;

the processing module is further configured to, if a multicast entry corresponding to the address information of the multicast group exists and the multicast protocol version identifier is different from the multicast protocol version identifier in the multicast entry, replace the multicast protocol version identifier in the multicast entry with the multicast protocol version identifier included in the multicast join packet, and adjust a priority level corresponding to the multicast protocol version identifier in the multicast entry; wherein the adjusted priority is greater than the priority before adjustment;

11. The apparatus of claim 10, further comprising:

a sending module, configured to send a second route advertisement message to the second PE device, where the second route advertisement message includes address information of the multicast group, a multicast protocol version identifier in the multicast entry, and a priority in the multicast entry.

12. The apparatus according to any of claims 7-11, wherein the route advertisement message further comprises an extended community attribute, the extended community attribute being used to carry the priority.

13. A PE device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute machine executable instructions to perform the method steps of any of claims 1-6.

14. A machine-readable storage medium having stored thereon machine-executable instructions which, when invoked and executed by a processor, cause the processor to perform the method steps of any of claims 1-6.