Route forwarding processing method, apparatus, storage medium and electronic apparatus
By introducing global RD offsets and target RD generation in routing forwarding processing, the multicast traffic isolation problem caused by routing reflection devices to optimize routing announcements is solved, and effective isolation of multicast traffic and optimization of network resources are achieved.
Patent Information
- Application Number
- PCT/CN2023/143618
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-09
- Filing Date
- 2023-12-29
- Publication Date
- 2024-11-14
AI Technical Summary
The problem that the route reflecting device allows the remote to be unable to isolate multicast traffic in the remote area.
By deploying a global first routing distinguisher (RD) offset, different purpose RDs are generated and used to generate virtual private network (VPN) routes different from other devices, ensuring that the routing reflective device can distinguish and forward uniformly Routing from different devices enables isolation of multicast traffic.
It effectively solves the multicast traffic isolation problem caused by routing reflection devices to optimize routing announcements, improves network isolation and security, and reduces network resource consumption.
Smart Images

Figure CN2023143618_14112024_PF_FP_ABST
Abstract
Description
Routing forwarding processing method, device, storage medium and electronic device
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This disclosure is based on Chinese patent application CN2023105208607 filed on May 9, 2023, entitled “A routing forwarding processing method, device, storage medium and electronic device”, and claims the priority of the patent application, and all the contents disclosed therein are incorporated into this disclosure by reference. Technical Field
[0003] The embodiments of the present disclosure relate to the field of communications, and in particular, to a routing and forwarding processing method, device, storage medium, and electronic device. Background Art
[0004] The forwarding filtering rule of the Ethernet Virtual Private Tree (E-TREE) is that leaf nodes do not forward packets to each other. This is a basic rule followed by all E-TREE implementations and is called "leaf filtering." Leaf filtering applies not only between two local attachment circuits (ACs), but also between a local AC and a remote AC. Currently, the ingress PE forms a leaf label table, and the Leaf-AC uses the leaf label to reach the forwarding plane and carry the leaf attributes to the remote end. MPLS EVPN uses MPLS labels to achieve this, while SRv6 EVPN uses the args field of the segment routing identifier (SID). A packet carrying a leaf label indicates that it comes from a remote leaf site and, therefore, cannot be forwarded to any local leaf site.
[0005] The leaf label table is generated based on the remotely advertised EVPN Ethernet Auto-Discovery per Ethernet Segment Route (RT-1 per-ES). Currently, all RT-1 per-ES routes use the same prefix: the Ethernet Tag ID (ETI) is 4294967295 and the Ethernet Segment ID (ESI) is 0. Therefore, when a route reflector (RR) is present in the network, BGP routes are preferentially advertised. As a result, only one RT-1 per-ES route is successfully advertised, preventing the generation of a complete leaf label table and making it impossible to isolate multicast traffic at the remote end.
[0006] A solution has not yet been proposed to the problem in related technologies that a route reflector selectively announces routes, resulting in the inability of remote ends to isolate multicast traffic.
[0007] Summary of the Invention
[0008] The embodiments of the present disclosure provide a routing forwarding processing method, apparatus, storage medium, and electronic device to at least solve the problem in the related art that a routing reflection device selectively announces routes, resulting in the inability of remote end to isolate multicast traffic.
[0009] According to an embodiment of the present disclosure, a routing forwarding processing method is provided, the method comprising:
[0010] A first route distinguisher (RD) offset globally deployed by the first device;
[0011] The first device generates a first destination RD according to the first RD offset;
[0012] The first device generates a first virtual private network (VPN) route according to the first destination RD;
[0013] The first device advertises a first VPN route to a route reflection device, so that the route reflection device reflects both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
[0014] According to another embodiment of the present disclosure, a routing processing method is further provided, the method comprising:
[0015] The route reflection device receives a first virtual private network VPN route advertised by the first device, wherein the first VPN route is generated by the first device according to the first destination RD, and the first destination RD is generated by the first device according to a deployed global first RD offset;
[0016] The route reflection device reflects both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
[0017] According to another embodiment of the present disclosure, a routing and forwarding processing apparatus is provided, which is applied to a first device and includes:
[0018] Deployment module, set to deploy the first RD offset globally;
[0019] A first generating module, configured to generate a first destination RD according to the first RD offset;
[0020] A second generating module is configured to generate a first VPN route according to the first destination RD;
[0021] The notification module is configured to notify the first VPN route to a route reflection device, so that the route reflection device reflects both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
[0022] According to another embodiment of the present disclosure, a routing processing apparatus is provided, which is applied to a route reflection device. The apparatus includes:
[0023] a receiving routing module, configured to receive a first virtual private network VPN route announced by a first device, wherein the first VPN route is generated by the first device according to a first destination RD, and the first destination RD is generated by the first device according to a deployed global first RD offset;
[0024] The transmitting module is configured to reflect both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
[0025] According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.
[0026] According to another embodiment of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] FIG1 is a hardware structure block diagram of a computer device of a routing and forwarding processing method according to an embodiment of the present disclosure;
[0028] FIG2 is a flowchart of a routing and forwarding processing method according to an embodiment of the present disclosure;
[0029] FIG3 is a second flowchart of the routing and forwarding processing method according to an embodiment of the present disclosure;
[0030] FIG4 is a schematic diagram of multicast traffic isolation according to this embodiment;
[0031] FIG5 is a block diagram 1 of a routing and forwarding processing device according to an embodiment of the present disclosure;
[0032] FIG6 is a second block diagram of the routing and forwarding processing device according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0033] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with embodiments.
[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0035] The method embodiments provided in the embodiments of the present disclosure can be executed in a computer device or a similar computing device. Taking operation on a computer device as an example, FIG1 is a hardware structure block diagram of a computer device of the routing forwarding processing method of the embodiment of the present disclosure. As shown in FIG1 , the computer device may include one or more (only one is shown in FIG1 ) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device) and a memory 104 for storing data, wherein the above-mentioned computer device may also include a transmission device 106 and an input and output device 108 for communication functions. It can be understood by those skilled in the art that the structure shown in FIG1 is only for illustration and does not limit the structure of the above-mentioned computer device. For example, the computer device may also include more or fewer components than those shown in FIG1 , or have a configuration different from that shown in FIG1 .
[0036] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the routing and forwarding processing method in the embodiment of the present disclosure. The processor 102 executes various functional applications and routing and forwarding processing by running the computer program stored in the memory 104, that is, implementing the above-mentioned method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories can be connected to the computer device via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0037] The transmission device 106 is used to receive or send data via a network. A specific example of the aforementioned network may include a wireless network provided by a communications provider of a computer device. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.
[0038] In this embodiment, a routing forwarding processing method running on the above-mentioned computer device is provided. FIG2 is a flowchart of the routing forwarding processing method according to an embodiment of the present disclosure. As shown in FIG2 , the flow includes the following steps:
[0039] Step S202: The first device deploys a global first RD offset;
[0040] In this embodiment, the above-mentioned step S202 may specifically include: the first device deploys the first RD offset according to the received touch instruction, that is, the user manually deploys the first RD offset. The second RD offset in this embodiment may also be manually deployed; or the first device generates the first RD offset according to the device identifier of the first device. The device identifier may specifically be an identifier such as a MAC address that can uniquely identify the device. The second RD offset is generated according to the device identifier of the second device, that is, the first RD offset generated by different PE devices is different.
[0041] Step S204: The first device generates a first destination RD according to the first RD offset;
[0042] In this embodiment, step S204 may specifically include: if the VPN instance has an RD deployed, the first device generating a first destination RD based on the deployed initial RD and a first RD offset; the second VPN route is generated by the second device based on the second destination RD; the second destination RD is generated by the second device based on the initial RD, or is generated by the second device based on the initial RD and a second RD offset, the second RD offset being different from the first RD offset; since the first RD offset and the second RD offset are different, even if the initial RDs are the same, the generated first destination RD and the second destination RD are different; if the VPN instance has no RD deployed, the first device generating the first destination RD based on the first RD offset; the second destination RD is generated by the second device based on the second RD offset; since the first RD offset and the second RD offset are different, the generated first destination RD and the second destination RD are different.
[0043] Step S206: The first device generates a first VPN route according to the first destination RD;
[0044] In this embodiment, the above-mentioned step S206 may specifically include: the first device generates a first VPN route according to the first destination RD, the ETI of the route prefix, and the ESI of the route prefix; the second VPN route is generated by the second device according to the second destination RD, the ETI of the route prefix, and the ESI of the route prefix; the second destination RD is generated by the second device according to a deployed global second RD offset; because the first destination RD and the second destination RD are different, the values of the first VPN route and the second VPN route generated based on the same ETI of the route prefix and the ESI of the route prefix are different, which facilitates the route reflection device to distinguish routes from different devices.
[0045] In step S208, the first device advertises the first VPN route to the route reflection device, so that the route reflection device reflects both the first VPN route and the second VPN route advertised by the second device to the third device, where the second VPN route is different from the first VPN route.
[0046] Through the above steps S202 to S208, the problem that the route reflection device selectively announces the routes, resulting in the remote end being unable to isolate multicast traffic, can be solved. The first device generates a first target RD by using the deployed first RD offset, and generates a first VPN route based on the first target RD. This makes the VPN routes generated by the first device and the second device different, so that the route reflection device can distinguish the routes of different devices and transmit them all, so that the remote end can achieve multicast traffic isolation.
[0047] In an optional embodiment, after the above-mentioned step S208, the method further includes: the first device receives a multicast message forwarded by the third device according to the Leaf label table through the route reflection device, and the multicast message carries a Leaf label. The Leaf label table is generated by the third device according to the Leaf label field of the route carried in the first VPN route and the second VPN route. The Leaf label table includes a first entry and a second entry. The neighbor of the first entry is the address of the first device, and the label is the Leaf label of the first device. The neighbor of the second entry is the address of the second device, and the label is the Leaf label of the second device. When determining that the Leaf attribute is locally deployed, the first device discards the above-mentioned multicast message.
[0048] According to another embodiment of the present disclosure, a routing processing method is further provided. FIG3 is a second flowchart of the routing forwarding processing method according to an embodiment of the present disclosure. As shown in FIG3 , the process includes the following steps:
[0049] Step S302: The route reflector receives a first VPN route advertised by a first device, where the first VPN route is generated by the first device according to a first destination RD, which is generated by the first device according to a deployed global first RD offset.
[0050] In step S304, the route reflection device reflects both the first VPN route and the second VPN route advertised by the second device to the third device, where the second VPN route is different from the first VPN route.
[0051] Through the above steps S302 to S304, the problem in the related art that the route reflection device selectively announces the routes, resulting in the remote end being unable to isolate multicast traffic, can be solved. The first device generates a first target RD by using the deployed first RD offset, and generates a first VPN route based on the first target RD. This makes the VPN routes generated by the first device and the second device different. The route reflection device can distinguish the routes of different devices and forward them all, so that the remote end can achieve multicast traffic isolation.
[0052] In one embodiment, a third device is used to generate a Leaf label table for multicast message forwarding based on the Leaf label field of the routes carried by the first VPN route and the second VPN route. The Leaf label table includes a first entry and a second entry. The neighbor of the first entry is the address of the first device and the label is the Leaf label of the first device. The neighbor of the second entry is the address of the second device and the label is the Leaf label of the second device.
[0053] In one embodiment, after the above-mentioned step S304, the method further includes: the route reflection device receives the multicast message forwarded by the third device according to the above-mentioned Leaf label table, and the multicast message carries the Leaf label; sends the multicast message to the first device and the second device, so that the first device and the second device discard the multicast message when determining the locally deployed Leaf attribute.
[0054] The following describes the embodiments of the present disclosure in detail by taking the first device as PE1, the second device as PE2, the third device as PE3, and the route reflection device as an RR device as an example.
[0055] This embodiment can implement multicast traffic isolation. A global offset is configured or automatically generated on the device. VPN instances can use this offset to convert the instance's VPN ID or RD to a new RD. This allows RD differentiation without increasing deployment planning, solving the problem of multicast traffic isolation.
[0056] FIG4 is a schematic diagram of multicast traffic isolation according to this embodiment when an RD is deployed in a VPN instance. As shown in FIG4 , the VPN instances of PE1 and PE2 deploy the same RD. When PE1 and PE2 have the same prefix route and both need to advertise it to PE3, the following steps are included:
[0057] Step 1: Deploy a global RD offset on PE1. There are two ways to deploy the RD offset: manual deployment, which involves manually configuring the offset on the device based on the planned offset (this setting is different for each device). Automatic deployment, which involves enabling automatic RD offset deployment, automatically generates the RD offset based on the device's unique identifier (for example, the device's MAC address).
[0058] Step 2: The VPN instance on PE1 turns on the switch. The VPN's RD is calculated based on the global RD offset according to certain rules (for example, by performing direct AND, OR, addition, or XOR operations) to generate a new RD.
[0059] PE1 generates a VPN route based on the new RD and announces it to the RR device. The RR device receives the route announced by PE1 with the new RD. At the same time, the RR device also receives the route announced by PE2 with the original RD. The BGP protocol uses the RD and route prefix to identify a route. Therefore, if the two routes have the same prefix but different RDs, the RR device considers them to be two different routes and reflects them to PE3, thereby generating complete table entries on PE3 and resolving the isolation issue.
[0060] On PE1, you can manually configure the global RD offset according to the plan, or enable automatic generation to automatically generate the global RD offset based on the device's unique identifier, such as the MAC address.
[0061] The VPN instance on PE1 switches on so that the RD value of the EVPN RT-1 per-ES route advertised on PE1 is the new RD value. This resolves the aforementioned traffic isolation issue. The specific operations are as follows:
[0062] Assuming the generated RD offset is 100:0, the offset can be directly added to the original RD value (100:1) (the calculation scheme is not limited to this). The new RD of PE1's EVPN E-TREE instance is 200:1. The advertised EVPN RT-1 per-ES route has an RD of 200:1, an ETI of the route prefix of 4294967295, an ESI of the route prefix of 0, the next hop field of the route is PE1's loopback interface address 10.1.1.1, and the Leaf Label field of the route is the locally assigned Leaf Label. This route is then advertised to the RR device.
[0063] At this point, the RR receives the EVPN RT-1 per-ES routes advertised by PE1 and PE2. The tunnel route prefix has the same ETI and ESI values, but different RDs. BGP considers them to be different prefixes, and reflects both routes to PE3.
[0064] PE3 receives the EVPN RT-1 per-ES route reflected by the RR and generates a leaf label table based on the nexthop and leaf label fields of the route. The leaf label table contains two entries: Entry 1's neighbor is PE1's address 10.1.1.1, and its label is PE1's leaf label 1; Entry 2's neighbor is PE2's address 10.1.1.2, and its label is PE2's leaf label 2.
[0065] When PE3's AC3 side receives a multicast packet, it queries the VPLS broadcast member table for broadcast members (PE1 and PE2 are included in the member table). Because the Leaf attribute is deployed on AC3, it further queries the Leaf label table and matches the member address in the broadcast member table with the neighbor address in the Leaf label table. The multicast packet received by PE3's AC3 interface is sent to both PE1 and PE2 with the Leaf label. At this point, both PE1 and PE2 receive the packet with the Leaf label and discover that their local AC1 and AC2 also have the Leaf attribute deployed. Therefore, both PE1 and PE2 discard the packet. This resolves the multi-packet problem, improves network isolation and security, and reduces network resource consumption.
[0066] If RD is not deployed in the VPN instance and PE1 in the network does not want to plan an RD and automatically deploys an RD, the following steps are required:
[0067] Step 1: Deploy the global RD offset and RD format on PE1. The RD offset deployment method is the same as above. At the same time, the format of the automatically generated RD can also be controlled through configuration.
[0068] Step 2: The VPN instance on PE1 turns on the switch. The VPN's RD is calculated based on the global RD offset and the VPN ID according to certain rules (for example, by performing direct AND, OR, addition, or XOR operations) and the RD format.
[0069] PE1 generates a VPN route based on the new RD and advertises it to the RR. After receiving the VPN route advertised by PE1, the RR reflects the route to PE3, where a routing entry is created. This solves the isolation issue and simplifies network configuration.
[0070] On PE1, the VPN instance does not need to deploy an RD. Instead, it deploys a global RD offset and RD format. When the VPN instance on PE1 is switched on, the VPN instance automatically generates a new RD. This RD value is used in the EVPN RT-1 per-ES routes advertised on PE1 to resolve the aforementioned traffic isolation issue. The specific steps are as follows:
[0071] Assume the generated offset is 300:0 and the RD format is XXX:XXX. The VPN ID of PE1's EVPN E-TREE instance is 1. The offset is directly added to the original VPN ID value (the calculation scheme is not limited to this). The RD value is 300:1. The advertised EVPN RT-1 per-ES route has an RD of 300:1, an ETI of 4294967295, an ESI of 0, the nexthop field of the route is PE1's loopback interface address 10.1.1.1, and the leaf label field of the route is the locally assigned leaf label. This route is then advertised to the RR device.
[0072] After the notification is sent to RR, RR and PE3 perform the same operations as in Method 1 in the previous example. This ultimately results in PE1 and PE2 discarding the packet, thus resolving the multi-packet problem, improving network isolation and security, and reducing network resource consumption.
[0073] This embodiment introduces an automatic RD deployment solution. While inheriting the original RD, an offset is introduced to convert the upper RD value of the instance to another RD value according to certain rules. This completes RD differentiation without increasing deployment planning and solves the problem of multicast traffic isolation.
[0074] According to another embodiment of the present disclosure, a routing and forwarding processing apparatus is further provided. FIG5 is a block diagram of a routing and forwarding processing apparatus according to an embodiment of the present disclosure. As shown in FIG5 , the apparatus is applied to a first device, and the apparatus includes:
[0075] A deployment module 52 is configured to deploy a global first RD offset;
[0076] A first generating module 54 is configured to generate a first destination RD according to the first RD offset;
[0077] A second generating module 56 is configured to generate a first VPN route according to the first destination RD;
[0078] The notification module 58 is configured to notify the first VPN route to the route reflection device, so that the route reflection device reflects both the first VPN route and the second VPN route advertised by the second device to the third device, wherein the second VPN route is different from the first VPN route.
[0079] In one embodiment, the first generating module 54 is further configured to, when an RD has been deployed in the VPN instance, generate the first destination RD based on the deployed initial RD and the first RD offset, wherein the second VPN route is generated by the second device based on the second destination RD, and the second destination RD is generated by the second device based on the initial RD, or the second destination RD is generated by the second device based on the initial RD and a second RD offset, and the second RD offset is different from the first RD offset; and, when no RD is deployed in the VPN instance, generate the first destination RD based on the first RD offset, wherein the second VPN route is generated by the second device based on the second destination RD, and the second destination RD is generated by the second device based on the second RD offset.
[0080] In one embodiment, the second generation module 56 is further configured to generate the first VPN route based on the first destination RD, the Ethernet tag identifier ETI of the routing prefix, and the Ethernet segment identifier ESI of the routing prefix, wherein the second VPN route is generated by the second device based on the second destination RD, the ETI of the routing prefix, and the ESI of the routing prefix, and the second destination RD is generated by the second device based on a deployed global second RD offset.
[0081] In one embodiment, the apparatus further comprises:
[0082] a first message receiving module, configured to receive, through the route reflector device, a multicast message forwarded by a third device according to a leaf label table, wherein the multicast message carries a leaf label, wherein the leaf label table is generated by the third device according to the leaf label field of the routes carried in the first VPN route and the second VPN route, wherein the leaf label table includes a first entry and a second entry, wherein a neighbor of the first entry is an address of the first device and a label is a leaf label of the first device, and a neighbor of the second entry is an address of the second device and a label is a leaf label of the second device;
[0083] The discarding module is configured to discard the multicast message when determining that the local deployment Leaf attribute is determined.
[0084] In one embodiment, the deployment module 52 is further configured to deploy the first RD offset according to the received touch instruction; or generate the first RD offset according to a device identifier.
[0085] According to another embodiment of the present disclosure, a routing processing device is further provided. FIG6 is a block diagram of a routing forwarding processing device according to an embodiment of the present disclosure. As shown in FIG6 , the device is applied to a route reflection device. The device includes:
[0086] a receiving routing module 62, configured to receive a first VPN route advertised by a first device, wherein the first VPN route is generated by the first device according to a first destination RD, and the first destination RD is generated by the first device according to a deployed global first RD offset;
[0087] The transmitting module 64 is configured to reflect both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
[0088] In one embodiment, the third device is used to generate a leaf label table for multicast message forwarding based on the leaf label field of the routes carried by the first VPN route and the second VPN route, wherein the leaf label table includes a first entry and a second entry, the neighbor of the first entry is the address of the first device, and the label is the leaf label of the first device, and the neighbor of the second entry is the address of the second device, and the label is the leaf label of the second device.
[0089] In one embodiment, the apparatus further comprises:
[0090] a second message receiving module, configured to receive a multicast message forwarded by the third device according to the Leaf label table, wherein the multicast message carries a Leaf label;
[0091] The sending module is configured to send the multicast message to the first device and the second device, so that the first device and the second device discard the multicast message when determining that the local deployment Leaf attribute is determined.
[0092] An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.
[0093] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
[0094] An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0095] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.
[0096] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.
[0097] Obviously, those skilled in the art should understand that the modules or steps of the present disclosure described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any particular combination of hardware and software.
[0098] The foregoing description is merely a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art will readily appreciate that various modifications and variations of the present disclosure are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present disclosure shall be included within the scope of protection of the present disclosure.
Claims
1. A routing forwarding processing method, the method comprising: The first device deploys a global first route distinguisher RD offset; The first device generates a first destination RD according to the first RD offset; The first device generates a first virtual private network VPN route according to the first destination RD; The first device advertises a first VPN route to a route reflection device, so that the route reflection device reflects both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
2. The method according to claim 1, wherein: The first device generating a first destination RD according to the first RD offset includes: In the case where the VPN instance has deployed an RD, the first device generates the first destination RD according to the deployed initial RD and the first RD offset, wherein the second VPN route is generated by the second device according to the second destination RD, the second destination RD is generated by the second device according to the initial RD, or the second destination RD is generated by the second device according to the initial RD and a second RD offset, and the second RD offset is different from the first RD offset; When the VPN instance does not deploy RD, the first device generates the first destination RD according to the first RD offset, wherein the second VPN route is generated by the second device according to the second destination RD, and the second destination RD is generated by the second device according to the second RD offset.
3. The method according to claim 1, wherein: The first device generating a first virtual private network VPN route according to the first destination RD includes: The first device generates the first VPN route according to the first destination RD, the Ethernet tag identifier ETI of the routing prefix, and the Ethernet segment identifier ESI of the routing prefix, wherein the second VPN route is generated by the second device according to the second destination RD, the ETI of the routing prefix, and the ESI of the routing prefix, and the second destination RD is generated by the second device according to the deployed global second RD offset.
4. The method according to claim 1, wherein: After the first device notifies the first VPN route to the route reflection device, the method further includes: The first device receives, through the route reflection device, a multicast message forwarded by the third device according to a Leaf label table, wherein the multicast message carries a Leaf label, wherein the Leaf label table is generated by the third device according to the Leaf label field of the routes carried in the first VPN route and the second VPN route, wherein the Leaf label table includes a first entry and a second entry, wherein a neighbor of the first entry is an address of the first device, and a label is a Leaf label of the first device, and a neighbor of the second entry is an address of the second device, and a label is a Leaf label of the second device; When determining that the Leaf attribute is deployed locally, the first device discards the multicast message.
5. The method according to any one of claims 1 to 4, wherein: The first device deploys a global first routing distinguisher RD offset including: The first device deploys the first RD offset according to the received touch control instruction; or The first device generates the first RD offset according to a device identifier.
6. A routing processing method, the method comprising: The route reflection device receives a first virtual private network VPN route announced by the first device, wherein the first VPN route is generated by the first device according to a first destination RD, and the first destination RD is generated by the first device according to a deployed global first RD offset; The route reflection device reflects both the first VPN route and a second VPN route advertised by the second device to a third device, wherein the second VPN route is different from the first VPN route.
7. The method according to claim 6, wherein: The third device is used to generate a Leaf label table for multicast message forwarding according to the Leaf label field of the route carried by the first VPN route and the second VPN route, wherein the Leaf label table includes a first entry and a second entry, a neighbor of the first entry is an address of the first device, and a label is a Leaf label of the first device, and a neighbor of the second entry is an address of the second device, and a label is a Leaf label of the second device.
8. The method according to claim 7, wherein: After the route reflection device reflects both the first VPN route and the second VPN route advertised by the second device to the third device, the method further includes: The route reflection device receives the multicast message forwarded by the third device according to the Leaf label table, wherein the multicast message carries the Leaf label; The route reflection device sends the multicast message to the first device and the second device, so that the first device and the second device discard the multicast message when determining that the Leaf attribute is deployed locally.
9. A routing forwarding processing device, applied to a first device, the device comprising: Deployment module, set to deploy the global first route distinguisher RD offset; A first generating module, configured to generate a first target RD according to a first RD offset; A second generating module, configured to generate a first virtual private network VPN route according to the first destination RD; The notification module is configured to notify the first VPN route to the route reflection device, so that the route reflection device reflects both the first VPN route and the second VPN route announced by the second device to a third device, wherein the second VPN route is different from the first VPN route.
10. A routing processing device, applied to a routing reflection device, the device comprising: A receiving routing module, configured to receive a first virtual private network VPN route announced by a first device, wherein the first VPN route is generated by the first device according to a first destination RD, and the first destination RD is generated by the first device according to a deployed global first RD offset; The transmitting module is configured to reflect both the first VPN route and the second VPN route announced by the second device to a third device, wherein the second VPN route is different from the first VPN route.
11. A computer-readable storage medium, wherein a computer program is stored in the storage medium, wherein: The computer program is configured to execute the method of any one of claims 1 to 5, 6 to 8 when executed.
12. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 5 and 6 to 8.
Citation Information
Patent Citations
Method and device for realizing user access multi-homing network and network equipment
CN101616093A
Method and device for building primary pseudowire and spare pseudowire
CN102143060A
Routing method and routing device
WO2020200200A1
Allocation method and apparatus for virtual private network service identifier, and message processing method and apparatus
WO2023050981A1
Forwarding table lookup method and apparatus, and storage medium and electronic apparatus
WO2023284675A1
