WO2023016234A1 - Rt4路由报文r4的发布方法及装置、存储介质及电子装置 - Google Patents

Rt4路由报文r4的发布方法及装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2023016234A1
WO2023016234A1 PCT/CN2022/107562 CN2022107562W WO2023016234A1 WO 2023016234 A1 WO2023016234 A1 WO 2023016234A1 CN 2022107562 W CN2022107562 W CN 2022107562W WO 2023016234 A1 WO2023016234 A1 WO 2023016234A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing
route
routing message
message
evpn
Prior art date
Application number
PCT/CN2022/107562
Other languages
English (en)
French (fr)
Inventor
舒晔
王玉保
张征
陈然
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023016234A1 publication Critical patent/WO2023016234A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/30—Routing of multiclass traffic

Definitions

  • the present disclosure relates to the communication field, and in particular, relates to a method and device, a storage medium, and an electronic device for publishing an RT4 routing message R4.
  • routing protocols such as Open Shortest Path First, Open Shortest Path First, referred to as OSPF, intermediate system to intermediate system, Intermediate System-to-Intermediate System, referred to as OSPF
  • OSPF Open Shortest Path First
  • BGP Border Gateway Protocol
  • CE will inform the dual-homed PE1 and PE2 which side should be preferred to proceed to the specified IP address by setting the Metric and other weights in the routing message (such as 1.1.1.1) Forwarding.
  • Figure 1 is a schematic diagram of EVPN in the related technology.
  • the forwarding path selection is not controlled by the weight of the CE's EVPN private network routing, but only by the DF election on ESI1.
  • the DF election between PE1 and PE2 cannot be based on the priority of the CE user side.
  • PE1, PE2, and PE3 deploy EVPN Layer 3 VRF instances; PE1 and PE2 are configured with VRF routes to NH_Prefix2 on CE1, and bind NH_Prefix2 routes to ESI; PE1 and PE2 respectively generate RT1 routes and publish them to PE3, and PE3 forms corresponding For Layer 3 ESI forwarding, the next hops are PE1 and PE2.
  • the host H2 and the host H1 behind CE1 communicate with each other, and there are two incoming ports int1 (10.2) and int2 (20.2 ) is dual-homed to PE1 and PE2; the gateway of int1 is int1 (10.1) of PE1, and the gateway of int2 is int2 (20.1) of PE2; NH_Prefix2 of CE1 establishes an EBGP neighbor relationship with PE1, and CE1 advertises the service route prefix1 (50.0/24) To PE1, PE1 generates an RT5 routing packet R5 of prefix1 (50.0/24), and the next hop to this route is NH_Prefix2, and PE1 adds the ESI (ESI1) information bound to NH_Prefix2 to the RT5 routing packet R5 and advertises it to PE3 and PE2; PE3 receives the RT5 route (50.0/24) message, according to the ES information (ESI1) carried in
  • PE3 queries the route forwarding table and forwards it to the dual-homing PE; PE1, according to the EBGP route, has the next hop as NH_Prefix2, and forwards the query to CE1 through the outbound interface int1 of NH_Prefix2 to implement interworking with service routes.
  • the existing three-layer ESI technology can effectively solve the problem of CE three-layer dual-homing network-side protection, but the DF election between dual-homing PEs can only rely on the DF priorities configured on PE1 and PE2, and cannot be based on CE user-side weights. Decision DF election result.
  • Embodiments of the present disclosure provide a method and device for issuing RT4 routing message R4, a storage medium, and an electronic device, so as to at least solve the problem of how to implement CE participation in DF election for dual-homing PEs in a three-layer dual-homing scenario.
  • a method for publishing RT4 routing message R4 including: instructing the virtual routing forwarding table VRF to register with the Ethernet virtual private network EVPN, so that EVPN generates a next hop with the service route R3
  • the RT4 routing message R4 corresponding to the IP address, wherein the next-hop IP address of the service route is in the prefix NH_Prefix2, and the RT4 routing message R4 is filled according to the routing priority to NH_Prefix2, and the RT4 routing message R4 uses
  • the ESI1 is the ESI index bound to NH_Prefix2; the DF election is the DF election through the ESI1; publish the RT4 routing message R4 to EVPN , wherein the RT4 routing message R4 carries weight information W4, and the W4 is determined by the routing priority.
  • a computer-readable storage medium where a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the above-mentioned RT4 routing report when running.
  • an electronic device including a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the above-mentioned processor executes the above-mentioned RT4 through the computer program.
  • the route priority to NH_Prefix2 (the route priority can come from the weight information released by the CE side) is used to perform the routing between PE1 and PE2 for the ESI.
  • DF elects, and publishes the route priority mapping in the RT4 route of the ESI to EVPN; when PE2 receives the RT4 route, it maps weight information based on the route priority carried in the RT4 route , to perform DF election; adopting the above technical solution, in the CE dual-homing PE scenario with three-layer ESI, the problem that CE cannot participate in determining the result of DF election is solved, thereby solving the aliasing behavior of PE3 based on three-layer ESI that cannot follow CE The problem of choosing a preferred forwarding path for expectations.
  • FIG. 1 is a schematic diagram of EVPN in the related technology of the present disclosure
  • Fig. 2 is the block diagram of the hardware structure of the computer terminal of the publishing method of the RT4 routing message R4 of the embodiment of the present disclosure
  • FIG. 3 is a flow chart (1) of a publishing method of an RT4 routing message R4 according to an embodiment of the present disclosure
  • FIG. 4 is a flow chart (2) of a publishing method of an RT4 routing message R4 according to an embodiment of the present disclosure
  • Fig. 5 is a flow chart (3) of a publishing method of an RT4 routing message R4 according to an embodiment of the present disclosure
  • Fig. 6 is a structural block diagram of an apparatus for publishing an RT4 routing message R4 according to an embodiment of the present disclosure.
  • FIG. 2 is a block diagram of a hardware structure of a computer terminal according to a method for publishing an RT4 routing message R4 according to an embodiment of the present disclosure.
  • the computer terminal can include one or more (only one shown in Figure 2) processor 202 (the processor 202 can include but not limited to a microprocessor (Microprocessor Unit, MPU for short) or programmable logic device (Programmable logic device, referred to as PLD)) and a memory 204 for storing data, in an exemplary embodiment, the above-mentioned computer terminal may also include a transmission device 206 and an input and output device 208 for communication functions.
  • MPU Microprocessor Unit
  • PLD programmable logic device
  • the above-mentioned computer terminal may also include a transmission device 206 and an input and output device 208 for communication functions.
  • the structure shown in FIG. 2 is only for illustration, and it does not limit the structure of the above computer terminal.
  • the computer terminal may also include more or less components than those shown in FIG. 2 , or have a different configuration with functions equivalent to those shown in FIG. 2 or more functions than those shown in FIG. 2 .
  • the memory 204 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the publishing method of the RT4 routing message R4 in the embodiment of the present disclosure, the processor 202 runs the computer program stored in the memory 204 program, so as to execute various functional applications and data processing, that is, to realize the above-mentioned method.
  • the memory 204 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 204 may further include a memory that is remotely located relative to the processor 202, and these remote memories may be connected to a computer terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 206 is used to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by the communication provider of the computer terminal.
  • the transmission device 206 includes a network interface controller (NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 206 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 3 is a flow chart (1) of a method for publishing an RT4 routing message R4 according to an embodiment of the disclosure. The process includes the following steps:
  • Step S302 PE1 configures the priority of the route from NH1 (such as 10.2) of CE1 to prefix2 (that is, NH_Prefix2, such as 1.1.1.1/32) as P1 and binds it to ESI1, according to NH_Prefix2 (that is, prefix2, such as 1.1.1.1/ 32) to construct an RT4 routing packet R4, and publish the R4 route to EVPN, wherein the R4 route carries weight information W4, and the W4 is determined by the routing priority P1.
  • NH1 such as 10.2
  • prefix2 that is, prefix2, such as 1.1.1.1/32
  • NH_Prefix2 that is, prefix2, such as 1.1.1.1/ 32
  • the RT4 routing message may be a Type 4 routing (also known as Ethernet segment routing) message of the L2VPN/EVPN address family of multi-protocol BGP, similarly, the following
  • the RT1 routing message can be the first type of routing (also known as Ethernet automatic discovery routing) message of the address family, and the RT5 routing message R5 described below can be the fifth type of routing of the address family ( Also known as IP Prefix Advertisement Routing) packet.
  • NH_Prefix2 corresponds to ESI1.
  • Step S304 PE2 receives the RT4 routing message R4 from PE1, and determines whether the DF node of the ESI is PE2 or PE1 according to the W4b and W4 in the R4b route. If the W4 is lower than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE2 is the DF node of the ESI1. If the W4 is higher than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE1 is the DF node of the ESI1.
  • FIG. 4 is a flowchart (2) of a method for publishing an RT4 routing message R4 according to an embodiment of the present disclosure. The process includes the following steps:
  • Step S402 PE2 configures the priority of the route from NH2 (such as 20.2) of CE1 to prefix2 (ie NH_Prefix2, such as 1.1.1.1/32) as P2 and binds it to ESI1, and constructs the RT4 routing report according to the priority of the route to NH_Prefix2
  • NH2 such as 20.2
  • prefix2 ie NH_Prefix2, such as 1.1.1.1/32
  • ESI1 binds it to ESI1
  • the RT4 routing report according to the priority of the route to NH_Prefix2
  • the R4 route is advertised to the EVPN, wherein the R4b route carries weight information W4b, and the W4b is determined by the route priority P2.
  • Step S404 PE1 receives the RT4 routing message R4b from PE2, and determines whether the DF node of the ESI is PE2 or PE1 according to the W4b and W4 in the R4b routing. If the W4 is lower than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE2 is the DF node of the ESI1. If the W4 is higher than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE1 is the DF node of the ESI1.
  • the above technical solution solves the problem that the CE cannot decide the DF election in the CE dual-homing PE scenario of the three-layer ESI, and then enables the dual-homing PE to use the routing priority of the CE route to perform the DF election.
  • VRF1 EVPN EVI instance
  • VRF2 EVPN EVI instance
  • an EVPN EVI instance (VRF3) is configured for PE3, wherein VRF3 and VRF1/VRF2 are configured with the same ingress and egress RT attribute, and the RT5 route message R5 and RT1 route published by PE1 and PE2 can be imported.
  • the virtual routing and forwarding table VRF is registered in the Ethernet virtual private network EVPN, so that before EVPN generates the RT5 routing message R5 corresponding to the service route, it also includes: indicating that the PE1 and PE2 are dual-homed to CE1, PE1 and CE1 INT1 is directly connected, and int2 between PE2 and CE1 is directly connected; the outbound interface of the static route configured on PE1 to NH_Prefix2 of CE1 is INT1, and the route priority is P1; the outbound interface of the static route configured on PE2 to NH_Prefix2 of CE1 is INT2, the route priority is P2; and the static route bound to PE1 and PE2 to NH_Prefix2 belongs to the same ES as ESI1.
  • the virtual routing and forwarding table VRF is registered in the Ethernet virtual private network EVPN, so that before EVPN generates the RT5 routing message R5 corresponding to the service route, it also includes: indicating that PE1 and PE2 are respectively the Prefix1 (such as 50.0) Service routing generates an RT5 routing message R5, and publishes the RT5 routing message R5 to the EVPN, and PE3 receives the RT5 routing message R5 of PE1 and PE2; wherein, the RT5 routing message R5 is PE1 Or PE2 is issued by VRF1 and VRF2 respectively, and the RT5 route carries the identifier ESI1 of the ES1; PE3 forms an IP forwarding table entry according to the received RT5 routing message R5, wherein the IP forwarding table Item implements the Aliasing function through the ESI1.
  • the virtual routing and forwarding table VRF is registered in the Ethernet virtual private network EVPN, so that before EVPN generates the RT5 routing message R5 corresponding to the service route, it also includes: PE1 and PE2 generate RT1 routes for the ESI1 and EVPN instances, Wherein, the RT1 route carries ES information and VRF label forwarding information; and the RT1 route is advertised to the EVPN.
  • the RT1 route also carries weight information W1, where the weight information W1 is determined by the election result of the DF election.
  • RT5 routing message R5 includes the ESI1.
  • PE3 receives the RT1 route published by PE1 and PE2, and forms an ESI forwarding table entry whose next hops are PE1 and PE2 respectively.
  • PE2 and PE3 form aliasing Aliasing according to Prefix1 and ESI index information ESI1 in the RT5 routing message R5 and the RT1 routing and forwarding information.
  • this disclosure proposes a method for publishing RT4 routing message R4, which can decide DF election according to CE routing priority, including: indicating the virtual routing forwarding table VRF in the Ethernet
  • the virtual private network EVPN registration so that EVPN generates the RT5 routing message R5 corresponding to the service route R3, the next-hop IP address of the service route R3 is in NH_Prefix2, the route configured to NH_Prefix2 is bound to ESI1, and passed to
  • the routing priority of NH_Prefix2 is used to elect the DF between PE1 and PE2 for the ESI1, and publish the ESI index ESI1 bound to the NH_Prefix2 carried in the RT5 routing message R5 to EVPN; received by PE3
  • a routing table entry is generated according to the Prefix1 carried in the RT5 routing message R5, and a forwarding table whose egress is ESI is formed according to the ESI index in the
  • the ESI used as the egress is used as an Overlay Index in the RT5 routing message R5, and can be used to implement IP Aliasing.
  • Fig. 5 is a flow chart (3) of the publishing method of the RT4 routing message R4 according to the embodiment of the present disclosure. As shown in Figure 5, the method includes the following steps:
  • Step S502 instruct the virtual routing and forwarding table VRF to register with the Ethernet virtual private network EVPN, so that EVPN generates the RT4 routing message R4 corresponding to the next-hop IP address of the service route R3, wherein the next-hop IP address of the service route R3 Jump IP address in NH_Prefix2;
  • next-hop IP address is in NH_Prefix2
  • ESI bound to the NH_Prefix2 is the ESI of the RT4 routing message R4, so the RT4 routing message R4 and the next-hop IP address correspondence.
  • Step S504 filling the RT4 routing message R4 according to the routing priority to NH_Prefix2, the RT4 routing message R4 is used for DF election between PE1 and PE2, wherein the ESI1 is the ESI index bound to NH_Prefix2 ;
  • the DF election is a DF election performed through the ESI1.
  • Step S506 publishing the RT4 routing packet R4 to the EVPN, wherein the RT4 routing packet R4 carries weight information W4, and the W4 is determined by the routing priority.
  • the PE2 After publishing the RT4 routing message R4 to the EVPN, the PE2 receives the RT4 routing message R4, and determines that the DF node of the ESI is Whether PE2 is PE1 or a third-party node, where the third-party node is a node other than PE1 and PE2.
  • the PE2 issues an RT4 routing message R4b to the ESI1, wherein the RT4 routing message R4b carries weight information W4b; when the PE1 receives the RT4 routing message R4b, according to The W4b and the W4 in the RT4 routing message R4b determine whether the DF node of the ESI is PE2, PE1 or a third-party node, wherein the third-party node is other than the PE1 and PE2 node.
  • the PE2 is the DF node of the ESI1; if the W4 is higher than the W4b, then the PE1 is the DF node of the ESI1; if the The weight information issued by the third-party node for the ESI is the highest weight among the PE1, PE2 and the third-party node, and the third-party node is the DF node of the ESI1.
  • PE1 and PE2 have a route to NH_Prefix2, instruct PE1 and PE2 to dual-home to CE1, configure on PE1 the priority of the route to NH_Prefix2 through IP address NH1 on CE1 to be P1, and configure on PE2 Set the priority of the route to NH_Prefix2 through IP address NH2 on CE1 to P2, and configure the NH_Prefix2 routes of PE1 and PE2 to belong to the same ES.
  • the virtual routing and forwarding table VRF is registered in the Ethernet virtual private network EVPN, so that before EVPN generates the RT4 routing message R4 corresponding to the next-hop IP address of the service route R3, PE1 and PE2 are respectively indicated as the IP prefix Prefix1 generates an RT5 routing message R5, publishes the RT5 routing message R5 to the EVPN, and instructs PE3 to receive the RT5 routing message R5 issued by the PE1 and the PE2; wherein, the RT5 routing message R5 The message R5 is issued by PE1 or PE2 for the EVPN instance EVI respectively, and the RT5 routing message R5 carries the identifier ESI1 of the ES1; PE3 forms an IP forwarding table according to the received RT5 routing message R5 item, wherein the IP forwarding entry implements the Aliasing function through the ESI1.
  • the virtual routing and forwarding table VRF is registered in the Ethernet virtual private network EVPN, so that before the EVPN generates the RT5 route packet R5 corresponding to the service route, PE1 and PE2 generate the RT1 route for the ESI1 and EVPN VRF instances, wherein the The RT1 route carries ES information and VRF label forwarding information; and the RT1 route is advertised to the EVPN.
  • the RT1 route also carries weight information W1, wherein the weight information W1 is determined by the election result of the DF election.
  • a corresponding RT5 routing message R5 is issued according to the service route R3, wherein the RT5 routing message R5 includes the ESI1.
  • PE3 After publishing the RT1 route and the RT5 route packet R5 to EVPN, PE3 receives the RT1 route published by PE1 and PE2; PE3 according to the ESI1 and The forwarding information of the RT1 route forms aliasing.
  • the DF election between PE1 and PE2 is performed on the ESI1 according to the routing priority to NH_Prefix2, where NH_Prefix2 is the service route Prefix1 next-hop IP address.
  • the present disclosure provides a publishing method of RT4 routing message R4, and the specific steps include:
  • Step 1 Configure EVPN EVI layer-3 instance VRF on PE1, PE2, and PE3.
  • PE1 corresponds to VRF1
  • PE2 corresponds to VRF2
  • PE3 corresponds to VRF3;
  • the direct connection interface INT2 of CE2 is added to VRF2; the interface directly connected between PE3 and host H2 is added to VRF3;
  • VRF1, VRF2, and VRF3 have the same inbound and outbound RT attributes, and can import RT1 routing and RT5 routing packets R5;
  • Step 2 PE1 configures INT1 and CE1 to directly connect to the network segment IP (10.1), and PE2 configures INT2 and CE1 to directly connect to the network segment IP (20.1);
  • Step 3 Configure the ESI index on PE1 as ESI1(00.11.22.33.44.55.66.77.88.99); configure the outbound interface of the static route to NH_Prefix2 on PE1 as INT1, route priority as P1, and bind it to ES instance ESI1;
  • Step 4 Configure the ESI index on PE2 as ESI1 (00.11.22.33.44.55.66.77.88.99); configure the outbound interface of the static route to NH_Prefix2 on PE2 as INT2, route priority as P2, and bind it to ES instance ESI1;
  • Step 5 PE1 generates an RT4 routing packet R4 for the ES of this device, and carries the routing priority P1 of NH_Prefix2 as weight information W4 in the RT4 routing packet R4 and publishes it to EVPN;
  • Step 6 PE2 generates an RT4 routing message R4b for the ES of this device, and uses the routing priority P2 of NH_Prefix2 as weight information W4b to carry in the RT4 routing message R4b and publish it to EVPN;
  • Step 7 PE2 receives the RT4 routing message R4 of PE1, and determines whether the DF node of the ESI is PE2 or PE1 according to the W4b and W4 in the R4b route. If the W4 is lower than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE2 is the DF node of the ESI1. If the W4 is higher than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE1 is the DF node of the ESI1.
  • Step 8 PE1 receives the RT4 routing message R4b from PE2, and determines whether the DF node of the ESI is PE2 or PE1 according to the W4b and W4 in the R4b routing. If the W4 is lower than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE2 is the DF node of the ESI1. If the W4 is higher than the weight information W4b of the RT4 routing packet R4b constructed by the PE2 for the ESI1, then the PE1 is the DF node of the ESI1.
  • Step 9 PE1 generates RT1 routes for ES and EVPN instance VRF1 of this device, RT1 routes carry ES information and VRF1 label forwarding information, and carry DF election results as route priorities in RT1 routing packets, and publish them to EVPN;
  • the priority of DF is P3, and the priority of non-DF is P4;
  • Step 10 PE2 generates RT1 routes for ES and EVPN instance VRF2 of this device, RT1 routes carry ES information and VRF2 label forwarding information, and carry DF election results as route priorities in RT1 routing packets, and publish them to EVPN;
  • the priority of DF is P3, and the priority of non-DF is P4;
  • Step 11 PE3 receives the RT1 route released by PE1 and PE2, forms ESI protection forwarding according to the label information (including VRF1 label forwarding information or VRF2 label forwarding information) and ESID, and the next hop points to PE1/PE2 respectively; and routes according to RT1
  • the priority of the route carried in determines the master and backup, P3 is the master, and P4 is the backup;
  • Step 12 PE2 receives the RT1 route released by PE1, and forms the local protection and forwarding of ESI according to the label information and ESID, and the next hops are CE1 and PE1 respectively; For local protection and forwarding, the next hops are PE1 and PE2 respectively;
  • Step 13 NH_Prefix2 of CE1 and PE1 establish a private network EBGP neighbor of VRF1, and advertise CE1's service route Prefix1 (50.0/24) to PE1;
  • Step 14 PE1 receives the service route Prefix1 (50.0/24) from the EBGP neighbor, and adds it to the VRF1 routing table to which EBGP belongs to form a local routing forwarding table.
  • the outbound interface is INT1, and the next hop is NH_Prefix2.
  • the specified ESI will update the IP forwarding table export to ESI1;
  • Step 15 The VRF virtual routing forwarding table (virtual routing forwarding) is registered with EVPN, EVPN generates the corresponding RT5 routing packet R5 for service route Prefix1 (50.0/24), and the RT5 routing packet R5 carries the IP prefix (50.0/24) and vpn RT attributes, check that the next hop of the service route is NH_Prefix2, add the ESI index ESI1 bound to the NH_Prefix2 static route in the RT5 route message R5, and publish the RT5 route to EVPN;
  • Step 16 PE3 receives the RT5 routing message R5, determines that the outbound RT of the RT5 routing message R5 is the same as the inbound RT of the VRF, and then forms a VRF routing table, and according to the routing prefix Prefix1 and the routing prefix carried in the RT5 routing message R5 ES index ESI1 forms an IP forwarding table whose export is ESI1;
  • Step 17 The destination IP of the service message sent by the host H4 is the service route IP3 (50.1).
  • PE3 receives the service message from the VRF3 entrance and looks up the table from VRF3 to determine the IP forwarding table corresponding to the prefix Prefix1 (50.0/24) of VRF3.
  • the egress is ESI1, forwarding service packets from ESI1 to PE1 or PE2;
  • Step 18 PE1 or PE2 receives the service packet forwarded by PE3, forwards the next hop to NH_Prefix2 according to the ESI, and forwards the service packet to CE1;
  • Step 19 CE1 analyzes the destination IP (50.1/32) after receiving the message, and communicates with the host H1 (50.1);
  • VRF1, VRF2, and VRF3 in step 5 above belong to the same service VPN, and deploy the same ingress and egress RT attributes.
  • This embodiment provides a method for distributing RT4 routing packets R4, which can decide EVPN DF election through CE routing priority, configure EVPN EVI three-layer instance VRF (same ingress and egress RT attributes) on PE1, PE2, and PE3, and dual-homing CE1 To PE1 and PE2, configure the ESI index on PE1 and PE2 as ESI1(00.11.22.33.44.55.66.77.88.99), configure the outbound interface of the static route to NH_Prefix2 on PE1 as INT1, and the route priority as P1(100), And bind with ES instance ESI1, configure the outbound interface of the static route to NH_Prefix2 on PE2 as INT2, route priority as P2(200), and bind with ES instance ESI1; among them, P1(100) has a higher priority than P2( 200); the host H2 behind CE1 is (50.1/32), the host H1 of CE2 is (100.2), and the CE2 host H2 (100.2/32) behind PE3 needs
  • the method flow includes the following steps:
  • Step S101 Configure EVPN EVI layer-3 instance VRF on PE1, PE2, and PE3.
  • PE1 corresponds to VRF1
  • PE2 corresponds to VRF2
  • PE3 corresponds to VRF3;
  • the direct connection interface INT2 of CE2 is added to VRF2; the interface directly connected between PE3 and host H2 is added to VRF3;
  • VRF1, VRF2, and VRF3 have an inbound and outbound RT attribute of (100:100), which can import RT1 route and RT5 route message R5;
  • Step S102 PE1 configures INT1 and CE1 to directly connect to the network segment IP (10.1), and PE2 configures INT2 and CE1 to directly connect to the network segment IP (20.1);
  • Step S103 Configure the ESI index on PE1 as ESI1 (00.11.22.33.44.55.66.77.88.99); PE1 configures the outbound interface of the static route to NH_Prefix2 as INT1, the route priority as P1 (100), and binds it to the ES instance ESI1 Certainly;
  • Step S104 Configure the ESI index on PE2 as ESI1 (00.11.22.33.44.55.66.77.88.99); PE2 configures the outbound interface of the static route to NH_Prefix2 as INT2, the route priority as P2 (200), and binds it to the ES instance ESI1 Certainly;
  • Step S105 PE1 generates an RT4 routing message R4 for the ES of the device, and carries the routing priority P1 (100) of NH_Prefix2 (1.1.1.1) as weight information W4 in the RT4 routing message R4 and publishes it to EVPN;
  • Step S106 PE2 generates RT4 routing message R4b for the ES of the device, and carries the routing priority P2 (200) of NH_Prefix2 (1.1.1.1) as weight information W4b in the R4b routing and publishes it to EVPN;
  • Step S107 PE2 receives the RT4 routing message R4 of PE1, compares the W4b(200) and the W4(100) in the R4b route, and W4(100) has a higher priority than the PE2.
  • the weight information W4b (200) of the RT4 routing message R4b constructed by the ESI1, electing PE1 to be the DF of the ESI1, and PE2 to be non-DF;
  • Step S108 PE1 receives the RT4 routing message R4b from PE2, compares the W4b (200) and the W4 (100) in the R4b route, and the W4b (200) is lower than the PE1. According to the weight information W4 (100) of the RT4 routing message R4 constructed by the ESI1, PE1 is elected as the DF of the ESI1, and PE2 is elected as the non-DF.
  • Step S109 PE1 generates RT1 routes for ES and EVPN instance VRF1 of the device, RT1 routes carry ES information and VRF1 label forwarding information, query the local DF election result is DF, carry P3 in the RT1 routing message as the route priority, and Publish to EVPN; Among them, the priority of DF is P3, and the priority of non-DF is P4;
  • Step S110 PE2 generates RT1 routes for ES and EVPN instance VRF2 of the device, RT1 routes carry ES information and VRF2 label forwarding information, query the local DF election result is non-DF, and use P4 as the route priority in the RT1 route message Carry and publish to EVPN;
  • Step S111 PE3 receives the RT1 route released by PE1 and PE2, forms ESI protection forwarding according to the label information and ESID, and the next hop points to PE1/PE2 respectively; the priority of reading the RT1 route of PE3 is P3, and the priority of the RT route of PE4 The level is P4; the main ESI is PE1, and the backup is PE2;
  • Step S112 PE2 receives the RT1 route published by PE1, and forms the local protection and forwarding of ESI according to the label information and ESID, and the next hops are CE1 and PE1 respectively; PE1 receives the RT1 route published by PE2, and forms the ESI route according to the label information and ESID For local protection and forwarding, the next hops are CE1 and PE2 respectively.
  • Step S113 NH_Prefix2 (1.1.1.1) of CE1 and PE1 establish a private network EBGP neighbor of VRF1, and publish CE1's service route Prefix1 (50.0/24) to PE1;
  • Step S114 PE1 receives the service route Prefix1 (50.0/24) from the EBGP neighbor, and adds it to the VRF1 routing table to which EBGP belongs to form a local routing forwarding table.
  • the outbound interface is INT1, and the next hop is NH_Prefix2.
  • the specified ESI will update the IP forwarding table export to ESI1;
  • Step S115 The VRF virtual routing forwarding table (virtual routing forwarding) is registered with EVPN, and EVPN generates a corresponding RT5 routing message R5 for the service route (50.0/24), and the RT5 routing message R5 carries the IP prefix (50.0/24) and vpn RT attribute (100:100), check that the next hop of the service route is NH_Prefix2, carry the ESI index ESI1 bound to the NH_Prefix2 static route in the RT5 routing message R5, and publish the RT5 routing message R5 to EVPN ;
  • Step S116: PE3 receives the RT5 routing message R5, judges that the outgoing RT of the RT5 routing message R5 is the same as the incoming RT (100:100) of the VRF, and imports the route into the VRF3 small table to form the IP routing table of Prefix1, and according to The IP forwarding table egress of Prefix1 formed by the routing prefix Prefix1 and ES index ESI1 carried in the RT5 routing message R5 is ESI1; the next hops are PE1 and PE2 respectively; the primary is PE1, and the backup is PE2;
  • Step S117 The destination IP of the service message sent by H2 is H1 (50.1).
  • PE3 receives the message from the entrance of VRF3 and looks up the table from VRF3, and checks that the IP forwarding table exit of the corresponding prefix Prefix1 (50.0/24) of VRF3 is ESI1. Packets are forwarded from ESI1 to ESI1 primary PE1;
  • Step S118 PE1 receives the forwarded message from PE3, and forwards the message to CE1 according to the ESI forwarding next hop as NH_Prefix2;
  • Step S119 After receiving the message, CE1 analyzes the destination IP (50.1/32), and communicates with the host H1 (50.1).
  • the embodiment of the present disclosure provides a method for distributing RT4 routing message R4, which can decide DF election through CE routing priority. Except for special instructions, the implementation steps of this method are the same as those in Embodiment 1. Before executing this method, it is determined that the route configured by PE1 to the Prefix2 of CE1 is IGP, and the route priority is P1, and that the route configured by PE2 to the Prefix2 of CE1 is IGP, and the route priority is P2; wherein, the IGP routing protocol can be ISIS or OSPF.
  • the process flow of the method implemented in the present disclosure includes the following steps:
  • Step S201 Unless otherwise specified, this step is the same as step S101;
  • Step S202 Unless otherwise specified, this step is the same as step S102;
  • Step S203 Configure the ESI index on PE1 as ESI1 (00.11.22.33.44.55.66.77.88.99); PE1 configures the outbound interface of the OSPF route to NH_Prefix2 as INT1, the route priority as P1 (100), and binds it to the ES instance ESI1 Certainly;
  • Step S204 Configure the ESI index on PE2 as ESI1 (00.11.22.33.44.55.66.77.88.99); PE2 configures the OSPF outbound interface of NH_Prefix2 as INT2, the routing priority as P2 (200), and binds it to the ES instance ESI1 .
  • step S205 to step S219 are the same as step S105 to step S119 in the first embodiment above.
  • the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
  • the technical solution of the present disclosure can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the methods of various embodiments of the present disclosure.
  • an apparatus for publishing the RT4 routing message R4 is also provided, and the apparatus is used to realize the above-mentioned embodiments and preferred implementation manners, which have already been described and will not be described in detail.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • Fig. 6 is a structural block diagram of an apparatus for publishing an RT4 routing message R4 according to an embodiment of the present disclosure.
  • the publishing device of RT4 routing message R4 includes:
  • the instruction module 62 is configured to instruct the virtual routing and forwarding table VRF to register in the Ethernet virtual private network EVPN, so that EVPN generates an RT4 routing message R4 corresponding to the next-hop IP address of the service route R3, wherein the service route R3 The next hop IP address is in NH_Prefix2;
  • the election module 64 is configured to fill the RT4 routing message R4 according to the routing priority to NH_Prefix2, and the RT4 routing message R4 is used for DF election between PE1 and PE2, wherein ESI1 is the ESI bound to NH_Prefix2 Index; the DF election is the DF election carried out through the ESI1;
  • the publishing module 66 is configured to publish the RT4 routing packet R4 to the EVPN, wherein the RT4 routing packet R4 carries weight information W4, and the W4 is determined by the routing priority.
  • the device for publishing the RT4 routing message R4 also includes:
  • the first determining module is configured to, after publishing the RT4 routing message R4 to EVPN, the PE2 receives the RT4 routing message R4, and determines the ESI according to the W4 in the RT4 routing message R4 Whether the DF node is PE2, PE1, or a third-party node, where the third-party node is a node other than the PE1 and PE2.
  • the second determining module is configured such that the PE2 issues an RT4 routing message R4b to the ESI1, wherein the RT4 routing message R4b carries weight information W4b; when the PE1 receives the RT4 routing message R4b In this case, according to the W4b and the W4 in the RT4 routing message R4b, it is determined whether the DF node of the ESI is PE2, PE1 or a third-party node, wherein the third-party node is a node other than the PE1 and PE2 other nodes.
  • the weight comparison module is configured such that if the W4 is lower than the W4b, the PE2 is the DF node of the ESI1; if the W4 is higher than the W4b, the PE1 is the DF node of the ESI1; If the weight information issued by the third-party node for the ESI is the highest weight among the PE1, PE2 and the third-party node, then the third-party node is the DF node of the ESI1.
  • the forwarding module is configured as a virtual route forwarding table VRF registered in the Ethernet virtual private network EVPN, so that after EVPN generates the RT5 route message R5 corresponding to the next-hop IP address of the service route R3, PE3 receives the RT5 route In the case of the packet R5, a routing table entry is generated according to the IP prefix Prefix1 carried in the RT5 routing packet R5, and a forwarding table whose egress is ESI is formed according to the ESI1 carried in the RT5 routing packet R5.
  • Configure the home module set it to instruct PE1 and PE2 to dual-home to CE1 when PE1 and PE2 have a route to NH_Prefix2, and configure the priority of the route to NH_Prefix2 through IP address NH1 on CE1 to be P1 on PE1, On PE2, configure the priority of the route to NH_Prefix2 through CE1's IP address NH2 to be P2, and configure the NH_Prefix2 routes of PE1 and PE2 to belong to the same ES.
  • the first routing generation module is set to register the virtual routing forwarding table VRF in the Ethernet virtual private network EVPN, so that EVPN generates the RT5 routing message R5 corresponding to the service routing, and instructs PE1 and PE2 to generate RT5 routing for the IP prefix Prefix1 respectively message R5, and publish the RT5 routing message R5 to the EVPN, and instruct PE3 to receive the RT5 routing message R5 issued by the PE1 and the PE2; wherein, the RT5 routing message R5 is PE1 or PE2 are respectively published by the EVPN instance EVI, and the RT5 routing message R5 carries the ES1 identifier ESI1; PE3 forms an IP forwarding entry according to the received RT5 routing message R5, wherein, The IP forwarding entry implements the Aliasing function through the ESI1.
  • the second routing generation module is configured to register the virtual routing forwarding table VRF in the Ethernet virtual private network EVPN, so that before EVPN generates the RT5 routing message R5 corresponding to the service routing, PE1 and PE2 generate RT1 routing for the ESI1 and EVPNVRF instances , wherein, the RT1 route carries ES information and VRF label forwarding information; and the RT1 route is advertised to the EVPN.
  • the weight carrying module is configured such that the RT1 route also carries weight information W1, wherein the weight information W1 is determined by the election result of the DF election.
  • the message publishing module is configured to publish a corresponding RT5 routing message R5 according to the service route R3, wherein the RT5 routing message R5 carries the ESI1.
  • the aliasing module is configured to publish the RT1 route and the RT5 route message R5 to the EVPN, PE3 receives the RT1 route published by PE1 and PE2; The ESI1 and the forwarding information of the RT1 route form an aliasing Aliasing.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • Embodiments of the present disclosure also provide an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.
  • the above-mentioned processor may be configured to execute the following steps through a computer program:
  • the RT4 routing message R4 is used for DF election between PE1 and PE2, wherein the ESI1 is an ESI index bound to NH_Prefix2;
  • the DF election is the DF election performed by the ESI1;
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • each module or each step of the above-mentioned disclosure can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开提供了一种RT4路由报文R4的发布方法及装置、存储介质及电子装置，其中，上述方法包括：指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3对应的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由R3的下一跳IP地址在NH_Prefix2中；根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，所述ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举；将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。

Description

RT4路由报文R4的发布方法及装置、存储介质及电子装置
本公开要求于2021年8月11日提交中国专利局、申请号为202110921575.7、发明名称“RT4路由报文R4的发布方法及装置、存储介质及电子装置”的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
技术领域
本公开涉及通信领域，具体而言，涉及一种RT4路由报文R4的发布方法及装置、存储介质及电子装置。
背景技术
在CE双归PE场景中，在PE-CE之间会使用路由协议(如开放式最短路径优先，Open Shortest Path First，简称为OSPF、中间系统到中间系统，Intermediate System-to-Intermediate System，简称为ISIS、边界网关协议，Border Gateway Protocol，简称为BGP)中，CE会通过在路由报文中设置Metric等权重来告知被双归的PE1、PE2应该优先选择哪边进行到指定IP地址(比如1.1.1.1)的转发。
但在实际应用中，在PE1和PE2将这些权重信息通告给第三PE时，却遇到了问题，图1是相关技术中EVPN示意图，如图1所示，由于PE3上采用了基于ESI1的混叠行为，其转发路径选择并不受到CE的EVPN私网路由中的权重的控制，只受ESI1上的DF选举的控制，但是，PE1和PE2之间的DF选举无法按照CE用户侧优先级来决策，基本工作原理为：
PE1、PE2、PE3部署EVPN三层VRF实例；PE1和PE2上均配置到CE1上NH_Prefix2的VRF路由，并将NH_Prefix2路由绑定ESI；PE1和PE2分别产生RT1路由发布给PE3，PE3上形成对应的三层ESI转发，下一跳为PE1和PE2。
主机H2和CE1背后的主机H1(CE1背后的子网50.0/24中的某个主机H1的IP地址，比如50.1/32)互通，在CE1上存在两个入端口int1(10.2)，int2(20.2)双归到PE1和PE2；int1的网关为PE1的int1(10.1)，int2的网关为PE2的int2(20.1)；CE1的NH_Prefix2和PE1建立EBGP邻居，CE1发布业务路由prefix1(50.0/24)路由到PE1上，PE1产生prefix1(50.0/24)的RT5路由报文R5，到该路由下一跳为NH_Prefix2，PE1将该RT5路由报文R5添加NH_Prefix2绑定的ESI(ESI1)信息通过EVPN发布给PE3和PE2；PE3上收到该RT5路由(50.0/24)报文，根据路由报文携带的ES信息(ESI1)，产生到该路由的转发出口为ESI1对应的转发表，下一跳分别为PE1和PE2，到达每个下一跳的优先级由PE1/PE2发布的RT-1路由中的权重信息决定，所述权重信息又由所述ESI1的DF选举结果决定。
PE3上查询路由转发表转发到双归PE；PE1上根据EBGP路由下一跳为NH_Prefix2，通过查询到NH_Prefix2的路由出接口int1转发给CE1，实现和业务路由的互通。
现有三层ESI技术，能有效解决CE三层双归的网络侧保护的问题，但是双归PE之间的DF选举只能依赖PE1和PE2上配置的DF优先级，不能按照CE用户侧权重来决策DF选举结果。
针对相关技术，在三层双归场景下，CE如何参与双归PE的DF选举，目前尚未提出有效的解决方案。
因此，有必要对相关技术予以改良以克服相关技术中的所述缺陷。
发明内容
本公开实施例提供了一种RT4路由报文R4的发布方法及装置、存储介质及电子装置，以至少解决在三层双归场景下，如何实现CE参与双归PE的DF选举的问题。
根据本公开实施例的一方面，提供一种RT4路由报文R4的发布方法，包括：指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由的下一跳IP地址在前缀NH_Prefix2中，根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，所述ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举；将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
根据本公开实施例的另一方面，还提供了一种RT4路由报文R4的发布装置，包括：指示模块，设置为指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由R3的下一跳IP地址在NH_Prefix2中；选举模块，设置为根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，所述ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举；发布模块，设置为将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
根据本公开实施例的又一方面，还提供了一种计算机可读的存储介质，该计算机可读的存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述RT4路由报文R4的发布方法。
根据本公开实施例的又一方面，还提供了一种电子装置，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，上述处理器通过计算机程序执行上述RT4路由报文R4的发布方法。
通过本公开，在ESI是与IP前缀NH_Prefix2相绑定的ESI时，通过到NH_Prefix2的路由优先级(路由优先级可以来自CE侧发布的权重信息)来为所述ESI进行PE1和PE2之间的DF选举，并将所述路由优先级映射在该ESI的RT4路由中发布到EVPN；在PE2收到所述RT4路由的情况下，根据RT4路由里携带的所述路由优先级映射成的权重信息，进行DF选举；采用上述技术方案，解决了在三层ESI的CE双归PE场景中，CE无法参与决定DF选举结果的问题，从而解决了PE3基于三层ESI的混叠行为导致不能按照CE的期望选择优先转发路径的问题。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示例性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开相关技术中EVPN示意图；
图2是本公开实施例的RT4路由报文R4的发布方法的计算机终端的硬件结构框图；
图3是根据本公开实施例的RT4路由报文R4的发布方法的流程图(一)；
图4是根据本公开实施例的RT4路由报文R4的发布方法的流程图(二)；
图5是根据本公开实施例的RT4路由报文R4的发布方法的流程图(三)；
图6是根据本公开实施例的RT4路由报文R4的发布装置的结构框图。
具体实施方式
为了使本技术领域的人员更好地理解本公开方案，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分的实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本公开保护的范围。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本公开的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例中所提供的方法实施例可以在计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图2是本公开实施例的RT4路由报文R4的发布方法的计算机终端的硬件结构框图。如图2所示，计算机终端可以包括一个或多个(图2中仅示出一个)处理器202(处理器202可以包括但不限于微处理器(Microprocessor Unit，简称是MPU)或可编程逻辑器件(Programmable logic device，简称是PLD))和用于存储数据的存储器204，在一个示例性实施例中，上述计算机终端还可以包括用于通信功能的传输设备206以及输入输出设备208。本领域普通技术人员可以理解，图2所示的结构仅为示意，其并不对上述计算机终端的结构造成限定。例如，计算机终端还可包括比图2中所示更多或者更少的组件，或者具有与图2所示等同功能或比图2所示功能更多的不同的配置。
存储器204可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的RT4路由报文R4的发布方法对应的计算机程序，处理器202通过运行存储在存储器204内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器204可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器204可进一步包括相对于处理器202远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置206用于经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中，传输装置206包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置206可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种RT4路由报文R4的发布方法，图3是根据本公开实施例的RT4路由报文R4的发布方法的流程图(一)，该流程包括如下步骤：
步骤S302，PE1配置经过CE1的NH1(比如10.2)到prefix2(即NH_Prefix2，比如1.1.1.1/32)的路由优先级为P1并和ESI1绑定，根据到NH_Prefix2(即prefix2，比如1.1.1.1/32)的路由优先级来构造RT4路由报文R4，将所述R4路由发布到EVPN，其中所述R4路由携带权重信息W4，所述W4由所述路由优先级P1决定。
需要说明的是，在一种实施方式中，所述RT4路由报文可以是多协议BGP的L2VPN/EVPN地址族的第4类路由(也称为以太分段路由)报文，类似地，以下所述RT1路由报文可以是所述地址族的第1类路由(也称为以太网自动发现路由)报文，以下所述RT5路由报文R5可以是所述地址族的第5类路由(也称为IP前缀发布路由)报文。
其中，NH_Prefix2与ESI1对应。
步骤S304，PE2收到PE1的RT4路由报文R4，根据所述R4b路由中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1。若所述W4低于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE2为所述ESI1的DF节点。若所述W4高于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE1为所述ESI1的DF节点。
在本实施例中提供了一种RT4路由报文R4的发布方法，图4是根据本公开实施例的RT4路由报文R4的发布方法的流程图(二)，该流程包括如下步骤：
步骤S402，PE2配置经过CE1的NH2(比如20.2)到prefix2(即NH_Prefix2，比如1.1.1.1/32)的路由优先级为P2并和ESI1绑定，根据到NH_Prefix2的路由优先级来构建RT4路由报文R4b，将所述R4路由发布到EVPN，其中所述R4b路由携带权重信息W4b，所述W4b由所述路由优先级P2决定。
步骤S404，PE1收到PE2的RT4路由报文R4b，根据所述R4b路由中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1。若所述W4低于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE2为所述ESI1的DF节点。若所述W4高于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE1为所述ESI1的DF节点。
采用上述技术方案，解决了在三层ESI的CE双归PE场景中，CE无法决策DF选举的问题，进而可以使得双归PE用CE路由的路由优先级进行DF选举。
可选的，在执行上述步骤S302以前，还需要为PE1配置EVPN EVI实例(VRF1)，为PE2配置EVPN EVI实例(VRF2)，其中VRF1和VRF2的出入RT属性相同，可以互相导入RT5路由和RT1路由；
可选的，上述步骤S402中，为PE3配置EVPN EVI实例(VRF3)，其中VRF3和VRF1/VRF2配置出入RT属性相同，可以导入PE1和PE2发布的RT5路由报文R5和RT1路由。可选的，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由对应的RT5路由报文R5之前，还包括：指示所述PE1和PE2双归到CE1，PE1与CE1的INT1为直连，PE2与CE1的int2为直连；在PE1上配置到CE1的NH_Prefix2的静态路由出接口为INT1，路由优先级为P1；在PE2配置到CE1的NH_Prefix2的静态路由出接口为INT2，路由优先级为P2；并绑定PE1和PE2到NH_Prefix2的静态路由同属一个ES为ESI1。
可选的，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由对应的RT5路由报文R5之前，还包括：指示PE1、PE2分别为所述Prefix1(比如50.0)的业务路由产生RT5路由报文R5，并将所述RT5路由报文R5发布到所述EVPN，以及PE3接收PE1和PE2的所述RT5路由报文R5；其中，所述RT5路由报文R5是PE1或PE2分别为所述 VRF1和VRF2发布的，且所述RT5路由携带所述ES1的标识ESI1；PE3根据收到的所述RT5路由报文R5形成IP转发表项，其中，所述IP转发表项通过所述ESI1实现混叠Aliasing功能。
可选的，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由对应的RT5路由报文R5之前，还包括：PE1和PE2为所述ESI1和EVPN实例产生RT1路由，其中，所述RT1路由携带ES信息和VRF标签转发信息；将所述RT1路由发布到EVPN。
可选的，所述RT1路由还携带权重信息W1，其中，所述权重信息W1由所述DF选举的选举结果决定。
可选的，根据所述业务路由R3发布对应的RT5路由报文，其中，所述RT5路由报文R5中包括所述ESI1。
可选的，将所述RT1路由和所述RT5路由报文R5发布到EVPN之后，还包括：PE3收到PE1和PE2发布的所述RT1路由，形成ESI转发表项下一跳分别为PE1和PE2；PE3根据所述RT5路由报文R5里的Prefix1和ESI索引信息ESI1与所述RT1路由转发信息形成混叠Aliasing。
为了更好的理解，在一个完整的实施例中，本公开提出了一种RT4路由报文R4的发布方法，能够根据CE路由优先级决策DF选举，包括：指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3对应的RT5路由报文R5，所述业务路由R3的下一跳IP地址在NH_Prefix2中，配置到NH_Prefix2的路由和ESI1相绑定，通过到NH_Prefix2的路由优先级来对所述ESI1进行PE1和PE2之间的DF进行选举，并将该RT5路由报文R5中携带的与所述NH_Prefix2绑定的ESI索引ESI1发布到EVPN；在PE3收到所述RT5路由的情况下，根据RT5路由报文R5里携带的所述Prefix1产生路由表项，并根据RT5路由报文R5里的ESI索引形成出口为ESI的转发表。
需要说明的是，作为所述出口的ESI在所述RT5路由报文R5里是作为重叠索引Overlay Index的，可用于实现IP混叠IP Aliasing。
图5是根据本公开实施例的RT4路由报文R4的发布方法的流程图(三)。如图5所示，该方法包括以下步骤：
步骤S502，指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由R3的下一跳IP地址在NH_Prefix2中；
需要说明的是，所述下一跳IP地址在NH_Prefix2中，与所述NH_Prefix2绑定的ESI即为所述RT4路由报文R4的ESI，因此所述RT4路由报文R4与所述下一跳IP地址对应。
步骤S504，根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，所述ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举。
步骤S506，将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
进一步地，将所述RT4路由报文R4发布到EVPN之后，所述PE2接收所述RT4路由报文R4，并根据所述RT4路由报文R4中的所述W4确定所述ESI的DF节点是PE2还是PE1还是第 三方节点，其中，所述第三方节点为除所述PE1和PE2之外的其他节点。
进一步地，所述PE2对所述ESI1发布RT4路由报文R4b，其中，所述RT4路由报文R4b中携带权重信息W4b；在所述PE1接收到所述RT4路由报文R4b的情况下，根据所述RT4路由报文R4b中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1还是第三方节点，其中，所述第三方节点为除所述PE1和PE2之外的其他节点。
进一步地，若所述W4低于所述W4b，则所述PE2为所述ESI1的DF节点；若所述W4高于所述W4b，则所述PE1为所述ESI1的DF节点；若所述第三方节点为所述ESI发布的权重信息为所述PE1，PE2和第三方节点中的最高权重，则所述第三方节点为所述ESI1的DF节点。
进一步地，在PE1和PE2有到NH_Prefix2的路由的情况下，指示所述PE1和PE2双归到CE1，在PE1上配置通过CE1上的IP地址NH1到达NH_Prefix2的路由优先级为P1，在PE2上配置通过CE1上的IP地址NH2到达NH_Prefix2的路由优先级为P2，并配置PE1和PE2的NH_Prefix2路由归属同一ES。进一步地，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4之前，指示PE1、PE2分别为所述IP前缀Prefix1产生RT5路由报文R5，并将所述RT5路由报文R5发布到所述EVPN，以及指示PE3接收所述PE1和所述PE2发布的所述RT5路由报文R5；其中，所述RT5路由报文R5为PE1或PE2分别为所述EVPN实例EVI发布的，且所述RT5路由报文R5中携带所述ES1的标识ESI1；PE3根据收到的所述RT5路由报文R5形成IP转发表项，其中，所述IP转发表项通过所述ESI1实现混叠Aliasing功能。
进一步地，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由对应的RT5路由报文R5之前，PE1和PE2为所述ESI1和EVPN VRF实例产生RT1路由，其中，所述RT1路由携带ES信息和VRF标签转发信息；将所述RT1路由发布到EVPN。
进一步地，所述RT1路由还携带权重信息W1，其中，所述权重信息W1由所述DF选举的选举结果决定。
进一步地，根据所述业务路由R3发布对应的RT5路由报文R5，其中，所述RT5路由报文R5中包括所述ESI1。
进一步地，将所述RT1路由和所述RT5路由报文R5发布到EVPN之后，PE3收到PE1和PE2发布的所述RT1路由；PE3根据所述prefix1的IP转发表项中的所述ESI1与所述RT1路由的转发信息形成混叠Aliasing。
其中，为了更好的理解上述根据CE路由优先级决策DF选举，具体的，根据到NH_Prefix2的路由优先级来对所述ESI1进行PE1和PE2之间的DF进行选举，其中NH_Prefix2为到业务路由Prefix1的下一跳IP地址。
本公开提供一种RT4路由报文R4的发布方法，具体步骤包括：
步骤1：在PE1、PE2、PE3配置EVPN EVI三层实例VRF，PE1对应VRF1，PE2对应VRF2，PE3对应VRF3；PE1和PE2双归到CE1，PE1和CE1的直连接口INT1加入VRF1，PE2和CE2的直连接口INT2加入VRF2；PE3和主机H2直连的接口加入VRF3；
其中，VRF1，VRF2，VRF3的出入RT属性相同，可以互相导入RT1路由和RT5路由报文R5；
步骤2：PE1配置INT1和CE1直连同网段IP(10.1)，PE2配置INT2和CE1直连同网段IP(20.1)；
步骤3：在PE1上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)；PE1配置到NH_Prefix2的静态路由出接口为INT1，路由优先级为P1，并和ES实例ESI1绑定；
步骤4：在PE2上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)；PE2配置到NH_Prefix2的静态路由出接口为INT2，路由优先级为P2，并和ES实例ESI1绑定；
步骤5：PE1为本设备的ES产生RT4路由报文R4，并将NH_Prefix2的路由优先级P1作为权重信息W4在RT4路由报文R4中携带并发布到EVPN；
步骤6：PE2为本设备的ES产生RT4路由报文R4b，并将NH_Prefix2的路由优先级P2作为权重信息W4b在RT4路由报文R4b中携带并发布到EVPN；
步骤7：PE2收到PE1的RT4路由报文R4，根据所述R4b路由中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1。若所述W4低于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE2为所述ESI1的DF节点。若所述W4高于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE1为所述ESI1的DF节点。
步骤8：PE1收到PE2的RT4路由报文R4b，根据所述R4b路由中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1。若所述W4低于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE2为所述ESI1的DF节点。若所述W4高于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b，则所述PE1为所述ESI1的DF节点。
步骤9：PE1为本设备的ES和EVPN实例VRF1产生RT1路由，RT1路由携带ES信息和VRF1标签转发信息，以及将DF选举结果作为路由优先级在RT1路由报文中携带，并发布到EVPN；
其中，DF优先级为P3，non-DF优先级为P4；
步骤10：PE2为本设备的ES和EVPN实例VRF2产生RT1路由，RT1路由携带ES信息和VRF2标签转发信息，以及将DF选举结果作为路由优先级在RT1路由报文中携带，并发布到EVPN；
其中，DF优先级为P3，non-DF优先级为P4；
步骤11：PE3收到PE1和PE2发布的RT1路由，根据标签信息(包括VRF1标签转发信息或VRF2标签转发信息)和ESID形成ESI的保护转发，下一跳分别指向PE1/PE2；并根据RT1路由中携带的路由优先级决定主备，P3为主，P4为备；
步骤12：PE2收到PE1发布的RT1路由，根据标签信息和ESID形成ESI的本地保护转发，下一跳分别为CE1和PE1；PE1收到PE2发布的RT1路由，根据标签信息和ESID形成ESI的本地保护转发，下一跳分别为PE1和PE2；
步骤13：CE1的NH_Prefix2和PE1建立VRF1的私网EBGP邻居，发布CE1的业务路由Prefix1(50.0/24)到PE1上；
步骤14：PE1上从EBGP邻居收到业务路由Prefix1(50.0/24)，加入到EBGP所属的VRF1路由表，形成本地路由转发表，出接口为INT1，下一跳为NH_Prefix2；根据NH_Prefix2静态路由绑定的ESI将IP转发表出口更新为ESI1；
步骤15：VRF虚拟路由转发表(virtual routing forwarding)在EVPN注册，EVPN为业务路由Prefix1(50.0/24)产生对应的RT5路由报文R5，RT5路由报文R5里携带IP前缀(50.0/24)和vpn RT属性，检查该业务路由的下一跳为NH_Prefix2，在RT5路由报文R5中添加与NH_Prefix2静态路由绑定的ESI索引ESI1，并将该RT5路由发布到EVPN；
步骤16：PE3收到该RT5路由报文R5，确定RT5路由报文R5的出向RT和VRF的入向RT 相同，后形成VRF路由表，并根据RT5路由报文R5中携带的路由前缀Prefix1和ES索引ESI1形成出口为ESI1的IP转发表；
步骤17：主机H4发业务报文的目的IP为业务路由IP3(50.1)，PE3从VRF3入口收到该业务报文从VRF3查表，确定VRF3的对应前缀Prefix1(50.0/24)的IP转发表出口为ESI1，将业务报文从ESI1转发到PE1或PE2；
步骤18：PE1或PE2收到PE3转发的业务报文，根据ESI转发下一跳为NH_Prefix2将业务报文转发给CE1；
步骤19：CE1收到报文后进行目的IP(50.1/32)解析，和主机H1(50.1)互通；
需要说明的是，上述步骤5中的VRF1、VRF2、VRF3属于同一业务VPN，部署相同出入RT属性。
显然，上述所描述的实施例仅仅是本公开一部分的实施例，而不是全部的实施例。为了更好的理解上述转发表的查找方法，以下结合实施例对上述过程进行说明，但不用于限定本公开实施例的技术方案，具体地：
实施例1
本实施例提供一种RT4路由报文R4的发布方法，能够通过CE路由优先级决策EVPN DF选举，在PE1、PE2、PE3配置EVPN EVI三层实例VRF(相同出入RT属性)，将CE1双归到PE1和PE2，在PE1和PE2上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)，在PE1上配置到NH_Prefix2的静态路由出接口为INT1，路由优先级为P1(100)，并和ES实例ESI1绑定，在PE2上配置到NH_Prefix2的静态路由出接口为INT2，路由优先级为P2(200)，并和ES实例ESI1绑定；其中P1(100)优先级高于P2(200)；CE1背后的主机H2为(50.1/32)，CE2的主机H1为(100.2)，PE3背后CE2主机H2(100.2/32)要和CE1的业务路由H1(50.1/32)互通。
该方法流程包括如下步骤：
步骤S101：在PE1、PE2、PE3配置EVPN EVI三层实例VRF，PE1对应VRF1，PE2对应VRF2，PE3对应VRF3；PE1和PE2双归到CE1，PE1和CE1的直连接口INT1加入VRF1，PE2和CE2的直连接口INT2加入VRF2；PE3和主机H2直连的接口加入VRF3；
其中，VRF1，VRF2，VRF3的出入RT属性为(100：100)，可以互相导入RT1路由和RT5路由报文R5；
步骤S102：PE1配置INT1和CE1直连同网段IP(10.1)，PE2配置INT2和CE1直连同网段IP(20.1)；
步骤S103：在PE1上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)；PE1配置到NH_Prefix2的静态路由出接口为INT1，路由优先级为P1(100)，并和ES实例ESI1绑定；
步骤S104：在PE2上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)；PE2配置到NH_Prefix2的静态路由出接口为INT2，路由优先级为P2(200)，并和ES实例ESI1绑定；
步骤S105：PE1为本设备的ES产生RT4路由报文R4，并将NH_Prefix2(1.1.1.1)的路由优先级P1(100)作为权重信息W4在RT4路由报文R4中携带并发布到EVPN；
步骤S106：PE2为本设备的ES产生RT4路由报文R4b，并将NH_Prefix2(1.1.1.1)的 路由优先级P2(200)作为权重信息W4b在R4b路由中携带并发布到EVPN；
步骤S107：PE2收到PE1的RT4路由报文R4，根据所述R4b路由中的所述W4b(200)和所述W4(100)进行比较，W4(100)优先级高于所述PE2为所述ESI1构建的RT4路由报文R4b的权重信息W4b(200)，选举PE1为所述ESI1的DF，PE2为non-DF；
步骤S108：PE1收到PE2的RT4路由报文R4b，根据所述R4b路由中的所述W4b(200)和所述W4(100)进行比较，所述W4b(200)低于所述PE1为所述ESI1构建的RT4路由报文R4的权重信息W4(100)，选举PE1为所述ESI1的DF，选举PE2为non-DF。
步骤S109：PE1为本设备的ES和EVPN实例VRF1产生RT1路由，RT1路由携带ES信息和VRF1标签转发信息，查询本地DF选举结果为DF，在RT1路由报文中携带P3作为路由优先级，并发布到EVPN；其中，DF优先级为P3，non-DF优先级为P4；
步骤S110：PE2为本设备的ES和EVPN实例VRF2产生RT1路由，RT1路由携带ES信息和VRF2标签转发信息，查询本地DF选举结果为non-DF，将P4作为路由优先级在RT1路由报文中携带，并发布到EVPN；
步骤S111：PE3收到PE1和PE2发布的RT1路由，根据标签信息和ESID形成ESI的保护转发，下一跳分别指向PE1/PE2；读取PE3的RT1路由优先级为P3，PE4的RT路由优先级为P4；形成ESI主为PE1，备为PE2；
步骤S112：PE2收到PE1发布的RT1路由，根据标签信息和ESID形成ESI的本地保护转发，下一跳分别为CE1和PE1；PE1收到PE2发布的RT1路由，根据标签信息和ESID形成ESI的本地保护转发，下一跳分别为CE1和PE2。
步骤S113：CE1的NH_Prefix2(1.1.1.1)和PE1建立VRF1的私网EBGP邻居，发布CE1的业务路由Prefix1(50.0/24)到PE1上；
步骤S114：PE1上从EBGP邻居收到业务路由Prefix1(50.0/24)，加入到EBGP所属的VRF1路由表，形成本地路由转发表，出接口为INT1，下一跳为NH_Prefix2；根据NH_Prefix2静态路由绑定的ESI将IP转发表出口更新为ESI1；
步骤S115：VRF虚拟路由转发表(virtual routing forwarding)在EVPN注册，EVPN为业务路由(50.0/24)产生对应的RT5路由报文R5，RT5路由报文R5里携带IP前缀(50.0/24)和vpn RT属性(100：100)，检查该业务路由的下一跳为NH_Prefix2，在RT5路由报文R5中携带与NH_Prefix2静态路由绑定的ESI索引ESI1，并将该RT5路由报文R5发布到EVPN；
步骤S116：PE3收到该RT5路由报文R5，判断RT5路由报文R5的出向RT和VRF的入向RT(100：100)相同，路由导入VRF3小表，形成Prefix1的IP路由表，并根据RT5路由报文R5中携带的路由前缀Prefix1和ES索引ESI1形成Prefix1的IP转发表出口为ESI1；下一跳分别为PE1和PE2；主为PE1，备为PE2；
步骤S117：H2发业务报文目的IP为H1(50.1)，PE3从VRF3入口收到该报文从VRF3查表，查VRF3的对应前缀Prefix1(50.0/24)的IP转发表出口为ESI1，将报文从ESI1转发到ESI1主PE1；
步骤S118：PE1收到PE3的转发报文，根据ESI转发下一跳为NH_Prefix2将报文转发给CE1；
步骤S119：CE1收到报文后进行目的IP(50.1/32)解析，和主机H1(50.1)互通。
实施例2
本公开实施例提供一种RT4路由报文R4的发布方法，可以通过CE路由优先级决策DF选举，除特殊说明之处以外，该方法的实现步骤和实施例1相同。在执行该方法之前，确定PE1配置到CE1的Prefix2的路由为IGP，路由优先级为P1，以及确定PE2配置到CE1的Prefix2的路由为IGP，路由优先级为P2；其中，IGP路由协议可以是ISIS或OSPF。
本公开实施的方法的流程包括如下步骤：
步骤S201：除特殊说明之处以外，本步骤与步骤S101相同；
步骤S202：除特殊说明之处以外，本步骤与步骤S102相同；
步骤S203：在PE1上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)；PE1配置到NH_Prefix2的OSPF路由出接口为INT1，路由优先级为P1(100)，并和ES实例ESI1绑定；
步骤S204：在PE2上配置ESI索引为ESI1(00.11.22.33.44.55.66.77.88.99)；PE2配置到NH_Prefix2的OSPF出接口为INT2，路由优先级为P2(200)，并和ES实例ESI1绑定。
除特殊说明之处外，步骤S205-步骤S219与上述实施例1中的步骤S105-步骤S119相同。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例的方法。
在本实施例中还提供了RT4路由报文R4的发布装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的设备较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本公开实施例的RT4路由报文R4的发布装置的结构框图。如图6所示，RT4路由报文R4的发布装置包括：
指示模块62，设置为指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由R3的下一跳IP地址在NH_Prefix2中；
选举模块64，设置为根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举；
发布模块66，设置为将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
在其他实施例中，RT4路由报文R4的发布装置还包括：
第一确定模块，设置为将所述RT4路由报文R4发布到EVPN之后，所述PE2接收所述RT4路由报文R4，并根据所述RT4路由报文R4中的所述W4确定所述ESI的DF节点是PE2还是PE1还是第三方节点，其中，所述第三方节点为除所述PE1和PE2之外的其他节点。
第二确定模块，设置为所述PE2对所述ESI1发布RT4路由报文R4b，其中，所述RT4路 由报文R4b中携带权重信息W4b；在所述PE1接收到所述RT4路由报文R4b的情况下，根据所述RT4路由报文R4b中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1还是第三方节点，其中，所述第三方节点为除所述PE1和PE2之外的其他节点。
权重比较模块，设置为若所述W4低于所述W4b，则所述PE2为所述ESI1的DF节点；若所述W4高于所述W4b，则所述PE1为所述ESI1的DF节点；若所述第三方节点为所述ESI发布的权重信息为所述PE1，PE2和第三方节点中的最高权重，则所述第三方节点为所述ESI1的DF节点。
转发模块，设置为虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT5路由报文R5之后，在PE3收到所述RT5路由报文R5的情况下，根据RT5路由报文R5中携带的所述IP前缀Prefix1产生路由表项，并根据RT5路由报文R5中携带的ESI1形成出口为ESI的转发表。
配置归属模块，设置为在PE1和PE2有到NH_Prefix2的路由的情况下，指示所述PE1和PE2双归到CE1，在PE1上配置通过CE1上的IP地址NH1到达NH_Prefix2的路由优先级为P1，在PE2上配置通过CE1上的IP地址NH2到达NH_Prefix2的路由优先级为P2，并配置PE1和PE2的NH_Prefix2路由归属同一ES。
第一路由产生模块，设置为虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由对应的RT5路由报文R5，指示PE1、PE2分别为所述IP前缀Prefix1产生RT5路由报文R5，并将所述RT5路由报文R5发布到所述EVPN，以及指示PE3接收所述PE1和所述PE2发布的所述RT5路由报文R5；其中，所述RT5路由报文R5为PE1或PE2分别为所述EVPN实例EVI发布的，且所述RT5路由报文R5中携带所述ES1的标识ESI1；PE3根据收到的所述RT5路由报文R5形成IP转发表项，其中，所述IP转发表项通过所述ESI1实现混叠Aliasing功能。
第二路由产生模块，设置为虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由对应的RT5路由报文R5之前，PE1和PE2为所述ESI1和EVPNVRF实例产生RT1路由，其中，所述RT1路由携带ES信息和VRF标签转发信息；将所述RT1路由发布到EVPN。
权重携带模块，设置为所述RT1路由还携带权重信息W1，其中，所述权重信息W1由所述DF选举的选举结果决定。
报文发布模块，设置为根据所述业务路由R3发布对应的RT5路由报文R5，其中，所述RT5路由报文R5中携带所述ESI1。
混叠模块，设置为将所述RT1路由和所述RT5路由报文R5发布到EVPN之后，PE3收到PE1和PE2发布的所述RT1路由；PE3根据所述prefix1的IP转发表项中的所述ESI1与所述RT1路由的转发信息形成混叠Aliasing。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算 机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，所述业务路由R3的下一跳IP地址在NH_Prefix2中；
S2，根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，所述ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为所述ESI1进行的DF选举；
S3，将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (14)

  1. 一种RT4路由报文R4的发布方法，包括：
    指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由R3的下一跳IP地址在NH_Prefix2中；
    根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举；
    将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
  2. 根据权利要求1所述的RT4路由报文R4的发布方法，其中，将所述RT4路由报文R4发布到EVPN之后，所述方法还包括：
    所述PE2接收所述RT4路由报文R4，并根据所述RT4路由报文R4中的所述W4确定所述ESI的DF节点是PE2还是PE1还是第三方节点，其中，所述第三方节点为除所述PE1和PE2之外的其他节点。
  3. 根据权利要求1所述的RT4路由报文R4的发布方法，其中，所述方法还包括：
    所述PE2对所述ESI1发布RT4路由报文R4b，其中，所述RT4路由报文R4b中携带权重信息W4b；
    在所述PE1接收到所述RT4路由报文R4b的情况下，根据所述RT4路由报文R4b中的所述W4b和所述W4确定所述ESI的DF节点是PE2还是PE1还是第三方节点，其中，所述第三方节点为除所述PE1和PE2之外的其他节点。
  4. 根据权利要求3所述的RT4路由报文R4的发布方法，其中，所述方法还包括：
    若所述W4低于所述W4b，则所述PE2为所述ESI1的DF节点；
    若所述W4高于所述W4b，则所述PE1为所述ESI1的DF节点；
    若所述第三方节点为所述ESI发布的权重信息为所述PE1，PE2和第三方节点中的最高权重，则所述第三方节点为所述ESI1的DF节点。
  5. 根据权利要求1所述的RT4路由报文R4的发布方法，其中，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4之后，所述方法还包括：
    在PE3收到所述RT5路由报文R5的情况下，根据RT5路由报文R5中携带的所述IP前缀Prefix1产生路由表项，并根据RT5路由报文R5的ESI1形成出口为ESI的转发表。
  6. 根据权利要求1所述的RT4路由报文R4的发布方法，其中，在PE1和PE2有到 NH_Prefix2的路由的情况下，所述方法还包括：
    指示所述PE1和PE2双归到CE1，在PE1上配置通过CE1上的IP地址NH1到达NH_Prefix2的路由优先级为P1，在PE2上配置通过CE1上的IP地址NH2到达NH_Prefix2的路由优先级为P2，并配置PE1和PE2的NH_Prefix2路由归属同一ES。
  7. 根据权利要求1所述的RT4路由报文R4的发布方法，其中，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由R3对应的RT5路由报文R5，所述方法还包括：
    指示PE1、PE2分别为所述IP前缀Prefix1产生RT5路由报文R5，并将所述RT5路由报文R5发布到所述EVPN，以及指示PE3接收所述PE1和所述PE2发布的所述RT5路由；其中，所述RT5路由报文R5为PE1或PE2分别为所述EVPN实例EVI发布的，且所述RT5路由报文R5中携带所述ES1的标识ESI1；
    PE3根据收到的所述RT5路由报文R5形成IP转发表项，其中，所述IP转发表项通过所述ESI1实现混叠Aliasing功能。
  8. 根据权利要求7所述的RT4路由报文R4的发布方法，其中，虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生业务路由R3对应的RT5路由报文R5之前，所述方法还包括：
    PE1和PE2为所述ESI1和EVPN VRF实例产生RT1路由，其中，所述RT1路由携带ES信息和VRF标签转发信息；
    将所述RT1路由发布到EVPN。
  9. 根据权利要求8所述的RT4路由报文R4的发布方法，其中，所述方法还包括：
    所述RT1路由还携带权重信息W1，其中，所述权重信息W1由所述DF选举的选举结果决定。
  10. 根据权利要求8所述的RT4路由报文R4的发布方法，其中，所述方法还包括：
    根据所述业务路由R3发布对应的RT5路由报文R5，其中，所述RT5路由报文R5中携带所述ESI1。
  11. 根据权利要求8或10所述的RT4路由报文R4的发布方法，其中，将所述RT1路由和所述RT5路由报文R5发布到EVPN之后，所述方法还包括：
    PE3收到PE1和PE2发布的所述RT1路由；
    PE3根据所述prefix1的IP转发表项中的所述ESI1与所述RT1路由的转发信息形成混叠Aliasing。
  12. 一种RT4路由报文R4的发布装置，包括：
    指示模块，设置为指示虚拟路由转发表VRF在以太网虚拟专用网EVPN注册，以使EVPN产生与业务路由R3的下一跳IP地址对应的RT4路由报文R4，其中，所述业务路由R3的下 一跳IP地址在NH_Prefix2中；
    选举模块，设置为根据到NH_Prefix2的路由优先级来填充RT4路由报文R4，所述RT4路由报文R4用于进行PE1和PE2之间的DF选举，其中，所述ESI1为与NH_Prefix2绑定的ESI索引；所述DF选举为通过所述ESI1进行的DF选举；
    发布模块，设置为将所述RT4路由报文R4发布到EVPN，其中，所述RT4路由报文R4携带权重信息W4，所述W4由所述路由优先级决定。
  13. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至11任一项中所述的方法。
  14. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为通过所述计算机程序执行所述权利要求1至11任一项中所述的方法。
PCT/CN2022/107562 2021-08-11 2022-07-25 Rt4路由报文r4的发布方法及装置、存储介质及电子装置 WO2023016234A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110921575.7A CN115914100A (zh) 2021-08-11 2021-08-11 Rt4路由报文r4的发布方法及装置、存储介质及电子装置
CN202110921575.7 2021-08-11

Publications (1)

Publication Number Publication Date
WO2023016234A1 true WO2023016234A1 (zh) 2023-02-16

Family

ID=85199842

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/107562 WO2023016234A1 (zh) 2021-08-11 2022-07-25 Rt4路由报文r4的发布方法及装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN115914100A (zh)
WO (1) WO2023016234A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170099180A1 (en) * 2015-10-01 2017-04-06 Juniper Networks, Inc. Fast convergence of evpn networks for multi homing topologies
US20170141963A1 (en) * 2015-11-18 2017-05-18 Telefonaktiebolaget L M Ericsson (Publ) Designated forwarder (df) election and re-election on provider edge (pe) failure in all-active redundancy topology
CN110391987A (zh) * 2018-04-16 2019-10-29 上海诺基亚贝尔股份有限公司 从运营商边缘设备集合中选择指定转发器的方法、设备及计算机可读介质
CN110708230A (zh) * 2019-09-16 2020-01-17 中国联合网络通信集团有限公司 一种指定转发者选举方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170099180A1 (en) * 2015-10-01 2017-04-06 Juniper Networks, Inc. Fast convergence of evpn networks for multi homing topologies
US20170141963A1 (en) * 2015-11-18 2017-05-18 Telefonaktiebolaget L M Ericsson (Publ) Designated forwarder (df) election and re-election on provider edge (pe) failure in all-active redundancy topology
CN110391987A (zh) * 2018-04-16 2019-10-29 上海诺基亚贝尔股份有限公司 从运营商边缘设备集合中选择指定转发器的方法、设备及计算机可读介质
CN110708230A (zh) * 2019-09-16 2020-01-17 中国联合网络通信集团有限公司 一种指定转发者选举方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
S. MOHANTY K. PATEL A. SAJASSI CISCO SYSTEMS, INC. J. DRAKE JUNIPER NETWORKS, INC.: "A new Designated Forwarder Election for the EVPN; draft-mohanty-l2vpn-evpn-df-election-01.txt", A NEW DESIGNATED FORWARDER ELECTION FOR THE EVPN; DRAFT-MOHANTY-L2VPN-EVPN-DF-ELECTION-01.TXT, 7 March 2015 (2015-03-07), pages 1 - 11, XP015105222 *

Also Published As

Publication number Publication date
CN115914100A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
CN109075984B (zh) 计算的spring组播的多点到多点树
JP5550757B2 (ja) リンクステートプロトコルによるｉｐフォワードにより制御されたイーサーネット・ネットワーク
CN101401083B (zh) 在ospf配置的网络中散布bgp属性信息来防止路由环的技术
JP6250825B2 (ja) データネットワークに最大冗長木（ｍａｘｉｍａｌｌｙ ｒｅｄｕｎｄａｎｔ ｔｒｅｅ）をデプロイする方法およびシステム
CN101455030B (zh) 动态共享风险节点组（srng）成员发现
JP5237391B2 (ja) リンク状態プロトコル制御型イーサネット・ネットワーク上でのｖｐｎの実装
KR102036626B1 (ko) 다중 영역 네트워크에서의 개선된 최단 경로 브릿징
US8717934B2 (en) Multicast source move detection for layer-2 interconnect solutions
US9736054B2 (en) Multicast active source discovery and management for layer-2 interconnect solutions
US8537840B1 (en) Angular distance calculation for BGP best path selection
CN107040469A (zh) 网络设备及方法
EP3188422B1 (en) Traffic black holing avoidance and fast convergence for active-active pbb-evpn redundancy
US7969867B2 (en) Backup route generation in border gateway protocol
US8902794B2 (en) System and method for providing N-way link-state routing redundancy without peer links in a network environment
KR20100113540A (ko) 링크 상태 프로토콜 제어형 이더넷 네트워크를 이용한 ｍｐｌｓ ｐ 노드 교체
CN104378297A (zh) 一种报文转发方法及设备
CN115225568B (zh) 对以太网虚拟私有网络—虚拟可扩展局域网的快速重路由
CN106936714A (zh) 一种vpn的处理方法和pe设备以及系统
CN113726653B (zh) 报文处理方法及装置
CN114978975B (zh) 以太网虚拟私有网络中的bum业务的快速重路由
EP3461079B1 (en) Path establishment method and device, and network node
WO2020244304A1 (zh) 路由信息发送的方法、路由选路的方法和装置
WO2023016234A1 (zh) Rt4路由报文r4的发布方法及装置、存储介质及电子装置
WO2023284675A1 (zh) 转发表的查找方法及装置、存储介质及电子装置
Marques et al. Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22855217

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE