Routing forwarding processing method and device, storage medium and electronic device
By deploying global RD offsets in routing devices to generate different VPN routes, the problem of multicast traffic isolation caused by the preferential advertising of routing reflection devices is solved, thus achieving isolation of remote multicast traffic and improving network security.
Patent Information
- Application Number
- CN202310520860.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-12
AI Technical Summary
In existing technologies, route reflection devices selectively advertise routes, which leads to the problem that remote ends cannot isolate multicast traffic.
By deploying a global first RD offset on the first device, generating a first destination RD, and using it to generate the first VPN route, the route reflection device can distinguish routes from different devices and reflect them all to the third device, thereby solving the multicast traffic isolation problem.
It achieves isolation of remote multicast traffic, improves network isolation and security, and reduces network resource consumption.
Smart Images

Figure CN118945106A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communications, and in particular, to a routing forwarding processing method, device, storage medium, and electronic device. Background Art
[0002] The forwarding filter rule of Ethernet Virtual Private Tree (E-TREE) is that leaves do not forward messages to each other. This is the basic rule followed by all E-TREE implementations. This forwarding filter rule is called "leaf filtering". Leaf filtering rules are not only applicable between two local attachment circuits (ACs), but also between a local AC and a remote AC. The current processing is that the ingress PE forms a leaf label table, and the Leaf-AC uses the leaf label to reach the forwarding plane to carry the leaf attributes to the remote end. Among them, MPLS labels are used in MPLSEVPN to achieve this purpose, and the args field of the segment routing identifier (Segment ID, SID) is used in SRv6 EVPN to achieve this purpose. The message carrying the leaf label indicates that it comes from a remote leaf site, so it cannot be forwarded to any local leaf site.
[0003] The Leaf label table is formed based on the Ethernet Auto-discovery per Ethernet Segment Route (RT-1per-ES) of EVPN based on each Ethernet segment announced by the remote end. Currently, the prefixes used by RT-1per-ES routes are the same, that is, the Ethernet Tag ID (ETI) is 4294967295 and the Ethernet Segment ID (ESI) is 0. Therefore, when there is a route reflector (RR) device in the network, BGP routes will be preferentially announced, resulting in only one RT-1per-ES route being successfully announced, and a complete Leaf label table cannot be generated, resulting in the inability to isolate multicast traffic at the remote end.
[0004] There is no solution to 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. Summary of the invention
[0005] The embodiments of the present application provide a routing forwarding processing method, device, storage medium and electronic device to at least solve the problem in the related art that the routing reflection device preferentially announces the routes, resulting in the inability to isolate multicast traffic at the remote end.
[0006] According to an embodiment of the present application, a routing forwarding processing method is provided, the method comprising:
[0007] The first device deploys a global first route distinguisher (Route-Dist inguisher, referred to as RD) offset;
[0008] The first device generates a first destination RD according to the first RD offset;
[0009] The first device generates a first virtual private network (Virtual Private Network, VPN for short) route according to the first destination RD;
[0010] 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.
[0011] According to another embodiment of the present application, a routing processing method is also provided, the method comprising:
[0012] 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;
[0013] 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 application, a routing forwarding processing device is also provided, which is applied to a first device, and the device includes:
[0015] A deployment module, used to deploy the global first RD offset;
[0016] A first generating module, configured to generate a first target RD according to a first RD offset;
[0017] A second generating module, configured to generate a first VPN route according to the first destination RD;
[0018] The notification module is used 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.
[0019] According to another embodiment of the present application, a routing processing device is also provided, which is applied to a routing reflection device, and the device includes:
[0020] 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;
[0021] 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.
[0022] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
[0023] According to another embodiment of the present application, 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 execute the steps in any one of the above method embodiments.
[0024] In an embodiment of the present application, a first device deploys a global first RD offset; the first device generates a first destination RD according to the first RD offset; the first device generates a first VPN route according to the first destination RD, and notifies the first VPN route to the RR device, so that the route reflection device reflects both the first VPN route and the second VPN route notified by the second device to the third device, wherein the second VPN route is different from the first VPN route, which can solve the problem in the related art that the route reflection device preferentially notifies the route, resulting in the inability to isolate multicast traffic at the remote end. The first device generates a first target RD by using the deployed first RD offset, and generates a first VPN route according to the first destination RD, so that the VPN routes generated by the first device and the second device are 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 isolation of multicast traffic. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1It is a hardware structure block diagram of a computer device of the routing forwarding processing method of an embodiment of the present application;
[0026] Figure 2 The process of the routing forwarding processing method according to the embodiment of the present application is as follows Figure 1 ;
[0027] Figure 3 The process of the routing forwarding processing method according to the embodiment of the present application is as follows Figure 2 ;
[0028] Figure 4 is a schematic diagram of multicast traffic isolation according to this embodiment;
[0029] Figure 5 The framework of the routing forwarding processing device according to the embodiment of the present application Figure 1 ;
[0030] Figure 6 The framework of the routing forwarding processing device according to the embodiment of the present application Figure 2 . DETAILED DESCRIPTION
[0031] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0033] The method embodiments provided in the embodiments of the present application can be executed in a computer device or a similar computing device. Taking running on a computer device as an example, Figure 1 is a hardware structure block diagram of a computer device of the routing forwarding processing method of an embodiment of the present application, such as Figure 1 As shown, the computer device may include one or more ( Figure 1 Only one is shown in the figure) a processor 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 for communication functions and an input and output device 108. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above-mentioned computer device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.
[0034] 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 forwarding processing method in the embodiment of the present application. The processor 102 executes various functional applications and routing forwarding processing by running the computer program stored in the memory 104, that is, implementing the above 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 arranged 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.
[0035] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.
[0036] In this embodiment, a routing forwarding processing method running on the above-mentioned computer device is provided. Figure 2 The process of the routing forwarding processing method according to the embodiment of the present application is as follows Figure 1 ,like Figure 2 As shown, the process includes the following steps:
[0037] Step S202, the first device deploys a global first RD offset;
[0038] 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, and 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, and the device identifier may specifically be an identifier such as a MAC address that can uniquely identify the device, and the second RD offset is generated according to the device identifier of the second device, that is, the first RD offsets generated by different PE devices are different.
[0039] Step S204, the first device generates a first destination RD according to the first RD offset;
[0040] In this embodiment, the above step S204 may specifically include: in the case where the VPN instance has deployed RD, the first device generates the first destination RD according to the deployed initial RD and the first RD offset, 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 is generated by the second device according to the initial RD and the second RD offset, the second RD offset is different from the first RD offset, and since the first RD offset is different from the second RD offset, even if the initial RD is the same, the generated first destination RD is different from the second destination RD; in the case where the VPN instance has not deployed RD, the first device generates the first destination RD according to the first RD offset, the second destination RD is generated by the second device according to the second RD offset, and since the first RD offset is different from the second RD offset, the generated first destination RD is different from the second destination RD.
[0041] Step S206, the first device generates a first VPN route according to the first destination RD;
[0042] In this embodiment, the above step S206 may specifically include: the first device generates a first VPN route according to the first destination RD, the ETI of the routing prefix, and the ESI of the routing prefix; 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; the second destination RD is generated by the second device according to the deployed global second RD offset; since the first destination RD is different from the second destination RD, the values of the first VPN route and the second VPN route generated based on the same ETI of the routing prefix and the ESI of the routing prefix are different, which facilitates the route reflection device to distinguish routes from different devices.
[0043] Step S208: The first device notifies 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 notified by the second device to the third device, where the second VPN route is different from the first VPN route.
[0044] 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 through the deployed first RD offset, and generates a first VPN route according to the first destination RD, so that the VPN routes generated by the first device and the second device are 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 isolation of multicast traffic.
[0045] In an optional embodiment, after the above-mentioned step S208, the method further includes: the first device receives, through the route reflection device, a multicast message forwarded by the third device according to the Leaf label table, 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.
[0046] According to another embodiment of the present application, a routing processing method is also provided. Figure 3 The process of the routing forwarding processing method according to the embodiment of the present application is as follows Figure 2 ,like Figure 3 As shown, the process includes the following steps:
[0047] Step S302: The route reflection device receives a first VPN route announced by the first device, where 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.
[0048] 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.
[0049] Through the above steps S302 to S304, the problem in the related art that the route reflection device preferentially 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 through the deployed first RD offset, and generates a first VPN route according to the first destination RD, so that the VPN routes generated by the first device and the second device are different. The route reflection device can distinguish the routes of different devices and forward them all, so that the remote end can achieve isolation of multicast traffic.
[0050] In one embodiment, a third device is used to generate a Leaf label table for multicast message forwarding according to the Leaf label field of the routes carried by the first VPN route and the second VPN route, the Leaf label table including a first entry and a second entry, the neighbor of the first entry is the address of the first device, 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.
[0051] In one embodiment, after the above-mentioned step S304, the method also includes: the routing 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.
[0052] The following takes the first device as PE1, the second device as PE2, the third device as PE3, and the route reflection device as RR device as an example to describe the embodiment of the present application in detail.
[0053] This embodiment can implement multicast traffic isolation. A global offset is configured or automatically generated on the device. The VPN instance can convert the VPNID or RD of the instance into a new RD according to the offset. Thus, RD differentiation is completed without increasing the deployment plan, solving the problem of multicast traffic isolation.
[0054] When RD is deployed in the VPN instance, Figure 4 is a schematic diagram of multicast traffic isolation according to this embodiment, such as Figure 4 As shown in the figure, the VPN instances of PE1 and PE2 deploy the same RD. When PE1 and PE2 have the same prefix routes and need to advertise them to PE3, the following steps are included:
[0055] Step 1: Deploy a global RD offset on PE1. There are two ways to deploy the RD offset. The first is manual deployment, which is to manually configure the offset on the device according to the planned offset (different devices). The second is automatic deployment, which is to turn on the RD offset automatic deployment switch to automatically generate the RD offset based on the unique identifier of the device (for example, the MAC address of the device).
[0056] Step 2: The VPN instance of PE1 turns on the switch, and the RD of the VPN is calculated according to the global RD offset according to certain rules (for example, it can be calculated by directly performing AND, OR, addition, XOR and other operations) to generate a new RD;
[0057] 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 RD being the new RD. At the same time, the RR device also receives the route announced by PE2, with the RD being the original RD. The BGP protocol identifies a route based on the RD and the route prefix. Therefore, 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 a complete table entry on PE3 to solve the isolation problem.
[0058] On PE1, you can manually deploy the global RD offset according to the plan, or enable the automatic generation switch to automatically generate the global RD offset based on the unique device identifier such as the MAC address.
[0059] The VPN instance of PE1 turns on the switch so that the RD value of the EVPN RT-1per-ES route advertised on PE1 is the new RD value to solve the traffic isolation problem described above. The specific operations are as follows:
[0060] Assuming that the generated RD offset is 100:0, the offset and the original RD value (100:1) can be directly added (the calculation scheme is not limited to this), and the new RD of the EVPN E-TREE instance of PE1 is 200:1; the RD of the advertised EVPN RT-1per-ES route is 200:1, the ETI of the route prefix is 4294967295, the ESI of the route prefix is 0, the next hop field of the route is the loopback port address 10.1.1.1 of PE1, and the Leaf Label field of the route is the locally assigned LeafLabel; the route will be advertised to the RR device;
[0061] At this point, the RR receives the EVPN RT-1per-ES routes advertised by PE1 and PE2. The ETI and ESI values of the tunnel route prefix are the same, but the RDs are different. BGP considers them to be different prefixes, and both routes are reflected to PE3.
[0062] PE3 receives the EVPN RT-1per-ES route reflected by the RR and generates a Leaf label table based on the nexthop field and LeafLabel field of the route. The Leaf label table generates two entries. The neighbor of entry 1 is PE1's address 10.1.1.1, and the label is PE1's Leaf Label1. The neighbor of entry 2 is PE2's address 10.1.1.2, and the label is PE2's Leaf Label2.
[0063] When the AC3 side of PE3 receives a multicast message, it queries the broadcast member table of VPLS to query the broadcast members (PE1 and PE2 are in the member table). Since the Leaf attribute is deployed on the AC3 side, it will continue to query the Leaf label table and match the member address in the broadcast member table with the neighbor address in the Leaf label table. The multicast message received by the AC3 port on PE3 will be sent to PE1 and PE2 with the Leaf label. At this time, PE1 and PE2 both receive the message with the Leaf label and find that the local AC1 and AC2 are also deployed with the Leaf attribute. Both will discard the message, thus solving the problem of multiple packets, improving the isolation and security of the network, and reducing the consumption of network resources.
[0064] When RD is not deployed in the VPN instance and PE1 in the network does not want to plan RD and automatically deploys RD, the following steps are included:
[0065] 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, for the format of automatically generated RD, this application can also control it through configuration.
[0066] Step 2: The VPN instance of PE1 turns on the switch, and the RD of the VPN is calculated according to the global RD offset and the VPNID of the VPN according to certain rules (for example, it can be calculated by directly performing AND, OR, addition, XOR and other operations), and generates the RD according to the RD format;
[0067] PE1 generates a VPN route based on the new RD and announces it to the RR device. The RR device receives the VPN route announced by PE1 and reflects the route to PE3, which forms a routing table entry on PE3. This solves the isolation problem and simplifies the configuration in the network.
[0068] The VPN instance on PE1 does not need to deploy an RD. Only the global RD offset and RD format are deployed. When the VPN instance on PE1 turns on the switch, the VPN instance can automatically generate a new RD, and the newly generated RD value of the EVPN RT-1per-ES route advertised on PE1 is used to solve the above-mentioned traffic isolation problem. The specific operations are as follows:
[0069] Assume that the generated offset is 300:0 and the RD format is XXX:XXX; the VPNID of the EVPN E-TREE instance of PE1 is 1; the offset and the original VPNID value are directly added (the calculation scheme is not limited to this time), and the generated RD value is 300:1; the RD of the advertised EVPN RT-1per-ES route is 300:1, the ETI of the route prefix is 4294967295, the ESI of the route prefix is 0, the nexthop field of the route is the loopback port address 10.1.1.1 of PE1, and the Leaf Label field of the route is the locally assigned Leaf Label; the route will be advertised to the RR device;
[0070] After the notification is sent to RR, the operations of RR and PE3 refer to the steps of the previous example method 1, and finally the message is discarded on PE1 and PE2, thereby solving the problem of multiple packets, improving the isolation and security of the network, and reducing the consumption of network resources.
[0071] This embodiment introduces a solution for automatically deploying RDs. On the basis of inheriting the original RD, an offset is introduced to convert the upper RD value of the instance into another RD value according to a certain rule, thereby completing the RD differentiation without increasing the deployment plan and solving the problem of multicast traffic isolation.
[0072] According to another embodiment of the present application, a routing forwarding processing device is also provided. Figure 5 The framework of the routing forwarding processing device according to the embodiment of the present application Figure 1 ,like Figure 5 As shown, applied to a first device, the apparatus includes:
[0073] A deployment module 52, configured to deploy a global first RD offset;
[0074] A first generating module 54, configured to generate a first target RD according to a first RD offset;
[0075] A second generating module 56, configured to generate a first VPN route according to the first destination RD;
[0076] 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 announced by the second device to a third device, wherein the second VPN route is different from the first VPN route.
[0077] In one embodiment, the first generating module 54 is further used to generate the first destination RD according to the deployed initial RD and the first RD offset when the VPN instance has deployed RD, 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 initial RD, or the second destination RD is generated by the second device according to the initial RD and the second RD offset, and the second RD offset is different from the first RD offset; and to generate the first destination RD according to the first RD offset when the VPN instance has not deployed RD, 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.
[0078] In one embodiment, the second generation module 56 is further used to generate 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.
[0079] In one embodiment, the device further comprises:
[0080] a first message receiving module, configured to receive, through the route reflection 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;
[0081] The discarding module is used to discard the multicast message when determining that the Leaf attribute is deployed locally.
[0082] 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.
[0083] According to another embodiment of the present application, a routing processing device is also provided. Figure 6 The framework of the routing forwarding processing device according to the embodiment of the present application Figure 2 ,like Figure 6 As shown, the device is applied to a route reflection device, and the device includes:
[0084] A receiving routing module 62 is configured to receive a first 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;
[0085] 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.
[0086] In one embodiment, 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, 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.
[0087] In one embodiment, the device further comprises:
[0088] 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;
[0089] The sending module is used 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 Leaf attribute is deployed locally.
[0090] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
[0091] 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.
[0092] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
[0093] 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.
[0094] 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 herein.
[0095] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that 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 executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.
[0096] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.
Claims
1. A routing forwarding processing method, characterized in that: The method comprises: 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, characterized in that: 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that: The method comprises: 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, characterized in that 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, characterized in that 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, characterized in that: The device comprises: A deployment module, used to deploy a global first routing 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 used 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, characterized in that: The device comprises: 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 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.
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
Cited By
Route forwarding processing method, apparatus, storage medium and electronic apparatus
EP4704399A1
