WO2020200200A1 - 路由方法及路由设备 - Google Patents

路由方法及路由设备 Download PDF

Info

Publication number
WO2020200200A1
WO2020200200A1 PCT/CN2020/082437 CN2020082437W WO2020200200A1 WO 2020200200 A1 WO2020200200 A1 WO 2020200200A1 CN 2020082437 W CN2020082437 W CN 2020082437W WO 2020200200 A1 WO2020200200 A1 WO 2020200200A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing
evpn
message
mac
interface
Prior art date
Application number
PCT/CN2020/082437
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 WO2020200200A1 publication Critical patent/WO2020200200A1/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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/34—Source routing
    • 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/66—Layer 2 routing, e.g. in Ethernet based MAN's

Definitions

  • the present disclosure relates to (but not limited to) the field of communication technology.
  • Layer 2 Virtual Private Network Layer 2 Virtual Private Network
  • Layer 3 Virtual Private Network Layer 3 Virtual Private Network, L3VPN
  • IRB Called Integrated Routing and Bridge
  • the forwarding process is very long, which is a great burden for the implementation of the forwarding plane, especially when the forwarding plane is implemented using ASIC chips, it is necessary to implement this set of forwarding procedures with high performance, which puts pressure on the cost of the forwarding plane. Big.
  • the embodiments of the present disclosure provide a routing method and routing equipment.
  • the routing method provided by the embodiment of the present disclosure includes: a first provider edge (Provider Edge, PE) device receives a first routing message sent by a second PE device, and the Layer 2 label attribute of the first routing message (Layer 2) 2
  • the Label Atribute, L2LA) carries the value of the Layer 3 Label Entity (L3LE), and the L2LA is used to carry the Layer 2 label entity in the Ethernet Virtual Private Network (EVPN) routing ( Layer 2 Label Entity, L2LE) value routing attribute;
  • the L2LE is the EVPN local label corresponding to the media access control virtual routing and forwarding (Media Access Control Virtual Routing Forwading, MAC-VRF) instance, and the L3LE is the network protocol virtual
  • IP-VRF Internet Protocol Virtual Routing Forwading
  • the routing method provided by the embodiment of the present disclosure includes: the second PE device sends a first routing message to the first PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is in the EVPN routing
  • the routing attribute used to carry the value of L2LE is the L2LE is the EVPN local label corresponding to the MAC-VRF instance, and the L3LE is the EVPN local label corresponding to the IP-VRF instance
  • the first routing message is used for the first
  • a PE device adds the L3LE represented by the L2LA in the first routing packet to the EVPN data packet forwarded to the second PE device.
  • the routing device includes: a receiving unit, configured to receive a first routing message sent by a second PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is in the EVPN
  • the routing attribute used to carry the value of L2LE in the routing is the L2LE is the EVPN local label corresponding to the MAC-VRF instance, and the L3LE is the EVPN local label corresponding to the IP-VRF instance;
  • the generating unit is configured to be based on the first
  • the routing message generates a first EVPN routing entry, and the value of the EVPN instance (EVPN Instance, EVI) label of the first EVPN routing entry is the value of the L2LA in the first routing message.
  • EVI EVI
  • the routing device includes: a sending unit, configured to send a first routing message to a first PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is the EVPN routing
  • the routing attribute used to carry the value of L2LE in the L2LE is the L2LE is the EVPN local label corresponding to the MAC-VRF instance, and the L3LE is the EVPN local label corresponding to the IP-VRF instance; the first routing message is used for the
  • the first PE device adds the L3LE represented by the L2LA in the first routing packet to the EVPN data packet forwarded to the second PE device.
  • the routing device includes a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method described above.
  • the computer-readable storage medium provided by the embodiments of the present disclosure is used to store a computer program, and the computer program enables a computer to execute the above-mentioned routing method.
  • Figure 1 is a networking diagram of application example 6 of the present disclosure in the hierarchical EVPN network
  • FIG. 2 is a schematic flowchart of a routing method provided by an embodiment of the present disclosure
  • Figure 3 is a networking diagram of application examples 1-3 of the present disclosure.
  • Figure 4 is a networking diagram of application examples 4, 5 and 6 of the present disclosure.
  • FIG. 5 is a diagram of the data message encapsulation format of application example 2 of the present disclosure.
  • Fig. 6 is a data message encapsulation format diagram of application example 3 of the present disclosure.
  • FIG. 7 is a data packet encapsulation format diagram of application examples 4, 5 and 6 of the present disclosure.
  • Fig. 8 is a format diagram of MAC mapping addresses of application examples 4, 5 and 6 of the present disclosure.
  • Fig. 9 is a format diagram of GEPL mapping address of application example 6 of the present disclosure.
  • FIG. 10 is a format diagram of GEPL of Application Example 6 of the present disclosure.
  • FIG. 11 is a format diagram of data packet encapsulation of application example 8 of the present disclosure.
  • Figure 12 is a networking diagram before optimization of application example 9 of the present disclosure.
  • Figure 13 is a networking diagram optimized through application example 9 of the present disclosure.
  • FIG. 14 is a structural diagram of a routing device provided by an embodiment of the present disclosure.
  • FIG. 15 is a schematic flowchart of a routing method provided by an embodiment of the present disclosure.
  • FIG. 16 is a structural diagram of another routing device provided by an embodiment of the present disclosure.
  • Fig. 17 is a structural diagram of another routing device provided by an embodiment of the present disclosure.
  • EVPN technology can provide Layer 2 EVPN (Layer 2 EVPN, L2EVPN) services and Layer 3 EVPN (Layer 3 EVPN, L3EVPN) services.
  • the L2EVPN service is forwarded based on the Media Access Control (MAC) address
  • the L3EVPN service is forwarded based on the Internet Protocol (IP) address.
  • the EVPN service binds access circuit (AC) interfaces and forwards data packets through virtual routing and forwarding (Virtual Routing Forwading, VRF) instances on each of its PE nodes.
  • AC access circuit
  • the VRF instance of L2EVPN is referred to as a MAC-VRF instance
  • the VRF instance of L3EVPN is referred to as an IP-VRF instance
  • the MAC-VRF instance and IP-VRF instance are collectively referred to as an EVPN instance (EVPN Instance, EVI).
  • L2EVPN or L3EVPN there are the following three encapsulation formats: Multi-Protocol Label Switching (MPLS) encapsulation, Virtual Extended LAN (VXLAN) encapsulation, and IPv6 data planning segment routing (Segment Routing) with IPv6 dataplan, SRv6) encapsulation.
  • MPLS Multi-Protocol Label Switching
  • VXLAN Virtual Extended LAN
  • IPv6 data planning segment routing with IPv6 dataplan
  • SRv6 encapsulation IPv6 data planning segment routing
  • an MPLS label is used to identify EVI
  • VNI VXLAN Network Identifier
  • SID Segment ID
  • EVI tags The above three entities that identify EVI are collectively called EVI tags, the EVI tags that identify MAC-VRF are called Layer 2 EVI (L2EVI) tags, and the EVI tags that identify IP-VRF are called Layer 3 EVI (Layer 3 EVI, L3EVI) label.
  • L2EVI Layer 2 EVI
  • IP-VRF Layer 3 EVI
  • the node where the EVI is located is called the PE node of the EVPN service.
  • the node where the EVI is located in the EVPN encapsulated by VXLAN is called the VTEP or NVE node of the EVPN service.
  • the VTEP/NVE/PE nodes are collectively referred to as PE nodes in this disclosure.
  • EVPN can combine L2EVPN and L3EVPN to form an EVPN IRB service.
  • the method is to bind the same interface to both a MAC-VRF instance and an IP-VRF instance.
  • the interface is called the MAC-VRF.
  • the IRB interface of the instance also referred to as the MAC-VRF instance and the IP-VRF instance, are connected through the IRB interface.
  • the following forwarding process is required: firstly, check the MAC table in MAC-VRF instance 1 to get IRB interface 1; secondly, query in the IP-VRF instance 1 bound to IRB interface 1 IP routing table and get IRB interface 2; again, check the ARP table encapsulation ether header based on IRB interface 2; finally, check the MAC table in the MAC-VRF instance corresponding to IRB interface 2 for forwarding.
  • This set of forwarding procedures is very long and has a great burden on the forwarding plane implementation. Especially when the forwarding plane is implemented using ASIC chips, it is necessary to implement this set of forwarding procedures with high performance, which puts great pressure on the cost of the forwarding plane.
  • IRB can realize the communication of the same subnet to be forwarded in L2EVPN.
  • the communication across subnets needs to be forwarded in L2EVPN according to the L2EVI label, and then forwarded in L3EVPN, which makes the forwarding process too long and low performance.
  • the following technical solutions of the embodiments of the present disclosure are proposed.
  • the embodiments of the present disclosure involve the following concepts: RT-1 routing, RT-2 routing, RT-3 routing, RT-5 routing, Layer 2 Label Entity (L2LE), Layer 3 Label Entity (Layer 3 Label) Entity, L3LE), Layer 2 Label Atribute (L2LA), Layer 3 Label Atribute (L3LA), RT-5G route, RT-5L route, End Point (EP), Endpoint Label (End Point Label, EPL), Downstream-assigned EPL (DAEPL), Global End Point Label (Global EPL, GEPL), Access Circuit (AC), Export Route Target (export Route Target, eRT), broadcast domain identifier (Broadcast Domain Identifier, BDI), virtual routing and forwarding edge identifier (VRF Edge Identifier, VE-ID).
  • RT-1 route is EVPN route type (Route-Type) 1, which is the first type of EVPN route.
  • RT-2, RT-3, and RT-5 are the second, third, and fifth types of EVPN routes.
  • the L2LE of an IRB interface that is, the forwarding label corresponding to the Broadcast Domain (BD) instance to which the IRB interface belongs, is a VNI (called L2VNI) in VXLAN EVPN, and an MPLS label in MPLS EVPN.
  • SRv6 EVPN is an SRv6 SID.
  • the L3LE of an IRB interface that is, the forwarding label corresponding to the IP-VRF instance bound to the IRB interface, is a VNI (called L3VNI) in VXLAN EVPN, an MPLS label in MPLS EVPN, and an MPLS label in SRv6 EVPN One SRv6 SID.
  • L2LA is the route attribute that carries the value of L2LE in the RT-1, RT-2, and RT-3 routes.
  • VXLAN EVPN or MPLS EVPN it is the label field of the EVPN route (in RT-2 route, it is the MPLS Label1 field)
  • SRv6 EVPN it is the SRv6 VPN SID TLV of the EVPN route (its SID-Type field value is 2).
  • L3LA is the route attribute that carries the value of L3LE in RT-2 and RT-5 routes.
  • VXLAN EVPN or MPLS EVPN it is the label field of the EVPN route (in RT-2 route, it is the MPLS Label2 field).
  • SRv6 EVPN Where is the SRv6 VPN SID TLV of the EVPN route (its SID-Type field value is 1).
  • the RT-5G route is an RT-5 route whose GW-IP field is not 0 and does not carry L3LE
  • the RT-5L route is an RT-5 route whose GW-IP is 0 and carries L3LE.
  • the PE node receiving an RT-5G route from the remote end will cause the corresponding routing entry to be added to the routing table of the IP-VRF instance.
  • the GW-IP field of the RT-5G routing message is the GW of the corresponding routing entry. -IP field.
  • the GW-IP field of some routing entries in the IP-VRF instance is not generated by the RT-5G routing message, but has the same effect, and is also called the GW-IP field at this time.
  • EP can be an IRB or AC.
  • EPL is an EVI label that can identify an EP at the same time.
  • DAEPL is an EPL assigned by a downstream node to an upstream node.
  • GEPL is an EPL that can identify the EP on all PE nodes of the EVPN service where the EP is located.
  • the access-side interface in the MAC-VRF instance and the access-side interface in the IP-VRF instance are collectively referred to as AC.
  • the eRT in the Border Gateway Protocol (BGP) routing message is used for the receiver of the routing message to decide whether to import it into a certain IP-VRF instance or MAC-VRF instance.
  • Border Gateway Protocol BGP
  • BDI is an identifier of a BD instance that satisfies the following conditions: if a BD instance BD1 is bridged to an IP-VRF instance VRF1, this VRF1 can respectively communicate with an IP-VRF instance on several remote PE nodes.
  • IP-VRF instances (Including the VRF1) contains a total of several BD instances, all BD instances belonging to the same broadcast domain have the same BDI, and any two BD instances belonging to different broadcast domains have different BDIs.
  • VE-ID is the identifier of an IP-VRF instance that satisfies the following conditions: If an IP-VRF instance VRF1 can communicate with an IP-VRF instance on several remote PE nodes, then these IP-VRF instances (including The VE-IDs of the VRF1 instance) are different from each other.
  • FIG. 2 is a schematic flowchart of a routing method provided by an embodiment of the disclosure. As shown in FIG. 2, the routing method includes step 201 and step 202.
  • the first PE device receives the first routing message sent by the second PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is used to carry the L2LE in the EVPN routing Value routing attribute; the L2LE is the EVPN local label corresponding to the MAC-VRF instance, and the L3LE is the EVPN local label corresponding to the IP-VRF instance.
  • the first routing message refers to a routing protocol message, usually a BGP routing message. It should be noted that when there is a Route Reflector (RR) node that changes the next hop between the second PE device and the first PE device, the L2LA in the first routing message received by the first PE device The value of may be a modified value of RR. At this time, RR acts as a proxy node of the second PE device, and the existence of RR does not affect the processing flow on the first PE device.
  • RR Route Reflector
  • the second PE device side is configured with a first MAC-VRF instance and a first IP-VRF instance, and the first MAC-VRF instance and the first IP-VRF instance pass through the An interface connection, the first MAC-VRF instance is connected to the first AC; the L3LE carried in the first routing message is the L3LE of the first IP-VRF instance.
  • the first PE device adds the L3LE represented by the L2LA in the first routing packet to the EVPN data packet forwarded to the second PE device.
  • step 201 and step 202 above are directed to the behavior of the control plane.
  • the behavior of the above control plane determines the behavior of the subsequent forwarding plane.
  • the implementation of the behavior of the control plane in the embodiments of the present disclosure can be implemented automatically without modifying the forwarding instruction. The act of obtaining a new forwarding surface. It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to VXLAN EVPN, or MPLS EVPN, or SRv6 EVPN.
  • the L2LE and the L3LE are VNIs; or in MPLS EVPN, the L2LE and the L3LE are MPLS labels; or in SRv6 EVPN, the L2LE and the L3LE are SRv6 SIDs .
  • the following describes different implementation manners of the first EVPN route entry and how to implement the behavior of the forwarding plane based on the first EVPN route entry.
  • the first routing message also carries the MAC of the first interface, the first interface is an IRB interface, and the first PE device generates a first EVPN routing entry based on the first routing message,
  • the value of the EVI label of the first EVPN route entry is the value of the L2LA in the first route message, and the first EVPN route entry is a MAC entry.
  • the behavior of the forwarding plane includes: (1) The first PE device receives the first Ethernet packet, and determines that the receiving end of the first Ethernet packet is the destination based on the first EVPN routing entry. The second PE device, and a first target packet to be sent to the second PE device is generated based on the first Ethernet packet, the first target packet carrying the EVI tag; the first Ethernet The message carries the first IP message, the first EVPN routing entry is a MAC entry, and the MAC entry represents the MAC of the first interface; (2) the first PE device reports the first target The message is sent to the second PE device, and the first target message uses the EVI tag to determine the IP-VRF instance to which the EVI tag belongs on the second PE device, and in the IP-VRF instance Query the IP routing table to forward the first target packet.
  • the first target packet when the L3LE is an SRv6 SID (see application example 2) or an MPLS label (see application example 3), the first target packet includes the Ethernet header of the first Ethernet packet.
  • the first target packet when the L3LE is an SRv6 SID or an MPLS label, the first target packet does not include the Ethernet header of the first Ethernet packet, and the first The Ethernet header information of the Ethernet message is carried in the outer IP area of the first target message.
  • the outer IP area includes a source IP area and/or a destination IP area.
  • the first routing message also carries at least one of the IP and MAC of the first interface, and the first interface is an IRB interface.
  • the first PE device generates a first IP routing entry and a second IP routing entry based on the first routing message, and the IP key in the first IP routing entry is all the values in the first routing message.
  • the IP of the first interface, GW-IP is an IP address containing the MAC address of the first interface in the first routing message and a first specified value; the IP key value of the second IP routing entry For the GW-IP of the first IP routing entry, its own GW-IP is empty, the next hop of the public network is the next hop of the first routing message, and the EVI label is in the first routing message The value of L2LA.
  • the first forwarding plane behavior includes: (1) the first PE device receives a second IP packet, and obtains the EVI label based on the second IP routing entry; (2) The first PE device adds an Ethernet header and the EVI tag to the outer layer of the second IP packet to obtain a second target packet; (3) the first PE device sends the second target packet To the second PE device, the second target packet is forwarded on the second PE device based on the EVI signature.
  • the second target message may be an MPLS message, or an SRv6 message, or a VXLAN message.
  • the second IP routing entry is obtained based on the first IP routing entry.
  • the first PE device side is configured with a second MAC-VRF instance and a second IP-VRF instance, and the second MAC-VRF instance and the second IP-VRF instance pass through The second interface is connected; further, the first PE device adds the MAC address of the second interface and the IP address of the second specified value as a first host route entry to the second IP-VRF instance, so The second interface is an IRB interface.
  • the second designated value is the same as the aforementioned first designated value.
  • the second forwarding plane behavior includes: (1) The first PE device receives a second Ethernet packet, and the destination MAC of the second Ethernet packet is the MAC of the second interface; The second Ethernet packet carries a third IP packet; (2) The first PE device is in the first PE device according to the destination MAC containing the second Ethernet packet and the IP address of the second specified value. 2.
  • the second PE device (3) The first PE device obtains the EVI label based on the second IP routing entry, and adds an Ethernet header and the EVI label to the outer layer of the third IP packet , Obtain a third target packet; (4) The first PE device sends the third target packet to the second PE device, and the third target packet is based on the second PE device The EVI signature is forwarded.
  • the first PE device adds a second subnet route entry to the second IP-VRF instance (see application example 5), and the second subnet route entry is a host part and the first IP-VRF instance.
  • the host routing entry part of the route where the MAC of the second interface is located is the same, that is, the first host routing entry can hit the second subnet routing entry.
  • the first PE device queries the IP routing table in the second IP-VRF instance according to the destination MAC of the second Ethernet packet and the IP address of the second specified value, and according to the first The second subnet routing entry determines that the second Ethernet packet is broadcast in the BD instance to which the second Ethernet packet belongs.
  • the second MAC-VRF instance is optional, but the second IP-VRF instance is necessary for both forwarding plane behaviors.
  • the key value in the first routing message contains GEPL, the L2LA of the first routing message is the DAEPL corresponding to the first AC or the first interface, and the next hop is the first 2.
  • the IP address of the PE device the GEPL is a label that uniquely identifies the first AC or the first interface in the EVPN service where the first IP-VRF instance is located.
  • the first PE device generates a third IP routing entry based on the first routing message, the IP key value in the third IP routing entry is an IP address containing the GEPL and a third specified value, and the EVI label is In the DAEPL, the next hop is the next hop of the first routing message, and the GW-IP is empty.
  • the first routing message may also carry the third designated value, and the GEPL and the third designated value may be different parts of the same field, or may be different fields.
  • the GEPL is a label that uniquely identifies the first AC or the first interface in the EVPN service where the first IP-VRF instance is located, which means that the GEPL is A label that uniquely identifies the first AC or the first interface among all nodes of the EVPN service where the first IP-VRF instance is located.
  • the first PE device receives a fourth target packet sent by the second PE device, where the fourth target packet is received by the second PE device pair through the first AC or the first interface Is obtained by encapsulating the received first packet, the fourth target packet carries the GEPL corresponding to the first AC; the first PE device generates a fourth IP routing entry based on the fourth target packet, The IP key in the fourth IP routing entry is the source IP of the first packet, GW-IP is the IP address containing the GEPL in the first packet and the third specified value, and the label is empty. The first PE device generates a fifth IP routing entry based on the fourth target packet, and the IP key value in the fifth IP routing entry contains the source MAC address of the first packet and the third The IP address of the specified value, GW-IP is the IP key value of the third IP routing entry, and the label is empty.
  • the first message may be an Ethernet message, or an IP message, or an ARP message.
  • the GEPL is carried between the EVPN label and the inner Ethernet header in the data message.
  • the value of the GEPL or the IP address obtained by mapping the GEPL is carried in the IP option in the data message.
  • the behavior of the first forwarding plane includes: (1) The first PE device receives a third Ethernet packet, and the destination MAC of the third Ethernet packet is contained in the IP key value of the fifth IP routing entry MAC; (2) The first PE device determines the third IP routing entry according to the GW-IP of the fifth IP routing entry, and forwards the third Ethernet packet according to the third IP routing entry.
  • the second forwarding plane behavior includes: (1) the first PE device receives a fourth IP packet, and the destination IP of the fourth IP packet is the IP key value of the fourth IP routing entry; (2) ) The first PE device determines the third IP routing entry according to the GW-IP of the fourth IP routing entry, and forwards the fourth IP packet according to the third IP routing entry.
  • the technical solutions of the embodiments of the present disclosure implement unified look-up tables with mixed layer 2 and layer 3 VPNs, overcome the problems of long IRB function forwarding process and low performance existing in the existing VPN technology, and realize IRB under the condition of controllable hardware cost.
  • the two goals of function and avoiding MAC address overload are achieved simultaneously, which improves the utilization efficiency of the routing table entry resources of the VPN core node, and avoids the consumption of the routing table entry resources of the VPN core node by each host.
  • Routing refers to routing messages, usually BGP routing messages, and routing entries refer to forwarding entries in the IP routing table or MAC address table of the forwarding plane.
  • the GW-IP concept in routing in the following application example has the same meaning as the GW-IP concept in RT-5 routing.
  • the GW-IP concept of the routing entry corresponds to the RT-5 routing in the routing entry corresponding to the RT-5 routing.
  • the fields corresponding to GW-IP have the same meaning.
  • FIG. 3 The networking diagrams of Application Example 1 to Application Example 3 in the following application examples are shown in Figure 3.
  • P1 and P2 represent two operator nodes (Provider, P), and PE1 and PE2 represent two operator edges (Provider Edge, PE) equipment, CE1 and CE2 represent two Customer Edge (CE) equipment,
  • VRF1 is an IP-VRF instance of the same EVPN service on different nodes
  • BD1 and BD2 are used to distinguish different subnets of the EVPN service A corresponding MAC-VRF instance on the same node
  • the MAC-VRF instance is also a BD instance.
  • the 3 has a corresponding BD instance on different PE devices of the EVPN service, that is, there is a BD1 on each of PE1 and PE2.
  • the PE device is called a PE node in an MPLS network, and is also called a VTEP node or NVE node in a VXLAN network.
  • the BD instance and the IP-VRF instance are connected by an IRB interface (shown by the dotted line in the figure).
  • the AC of the BD instance may be a sub-interface on the physical interface (as shown by the thin solid lines marked AC1, AC2, AC3, or AC4 in the figure).
  • P1 and P2 nodes are nodes in the underlay network, which are P devices in MPLS networks, and IP forwarding devices in VXLAN or SRv6 networks.
  • CE1 has two Layer 3 interfaces IF1 and IF4, which are connected to AC1 and AC4, respectively
  • CE2 has two Layer 3 interfaces IF2 and IF3, which are connected to AC2 and AC3, respectively.
  • the IP addresses of IF1, IF2, IF3, and IF4 are respectively H1, H2, H3, and H4, and the MAC addresses are respectively M1, M2, M3, and M4.
  • the IRB interface connecting the BD1 instance and the VRF1 instance on PE2 is marked as IRB1
  • the IRB interface connecting the BD1 instance and the VRF1 instance on PE1 is marked as IRB2
  • the MAC addresses of IRB1 and IRB2 are marked as Mb1 and Mb2, respectively .
  • AC1 and AC2 are both interfaces in the broadcast domain of BD1
  • AC3 is the interface in the broadcast domain of BD2
  • AC4 is the Layer 3 interface in the VRF1 instance.
  • Figure 4 adds PE3 and CE3 on the basis of Figure 3.
  • Figure 4 shows the BD3 instance on PE3 and the one on PE1.
  • the BD3 instances belong to the same broadcast domain, and AC5 is connected to the Layer 3 interface IF5 on CE3.
  • AC5 is the interface in the BD3 instance.
  • the BD3 instance and the VRF1 instance are connected through the IRB3 interface.
  • Figure 4 is used in application example 6 as its networking diagram on the non-hierarchical EVPN network architecture.
  • Figure 1 shows the networking diagram of application example 6 in the following application examples under the hierarchical EVPN network architecture.
  • Step (1) PE2 advertises the RT-2 route (ie, type 2 EVPN route) packet (denoted as X1) corresponding to the IRB interface (denoted as IRB1 interface) corresponding to its local BD instance BD1 to PE1.
  • the value of L2LA in X1 is not the value of L2LE (that is, the L2VNI corresponding to the BD1 instance) but the value of L3LE (that is, the L3VNI corresponding to the IP-VRF instance).
  • Step (2) PE1 receives the routing message X1 and adds it to the local BD1 instance to form a MAC entry in the BD1 instance (its MAC address is Mb1).
  • the L3VNI is recorded in the Mb1 entry.
  • Step (3) PE1 receives the Ethernet packet EP1 from the local AC1, its source MAC is M1, its destination MAC is Mb1, its inner layer is IP packet is P1, for P1, its source IP is H1, and its destination IP It is H3, and the MAC address table is checked to determine the transmission to the remote PE2; the PE1 adds VXLAN encapsulation outside the EP1 to become a message USP1, where the source IP of the VXLAN encapsulation is N1 and the destination IP is N2; PE1 sends the USP1 message to PE2.
  • Step (4) PE2 receives the USP1 message, knows that it is going to perform VXLAN termination and its VNI is L3VNI, and transfers the IP message (ie P1) carried by the USP1 message to the IP corresponding to the L3VNI -Check the routing table and forward in the VRF instance, and finally forward it from AC3 to the IF3 interface of CE2 through the BD2 instance and its IRB interface.
  • IP message ie P1
  • Step (3) The following dependency exists on the control plane: the M1 and H1 are the MAC address and IP address of IF1, respectively, the Mb1 is the MAC address of the IRB1 interface connecting the BD1 instance and the VRF1 instance on PE2, and the H3 is The IP address of IF3, where N1 and N2 are IP addresses that identify PE1 and PE2, respectively.
  • the AC1 is bound to a broadcast domain (denoted as BD1), the MAC address table is the MAC address table corresponding to BD1, the N2 is recorded in the MAC address table entry corresponding to the Mb1, and the PE1 receives the The routing message X1 learns the correspondence between the Mb1 and the N2.
  • BD1 broadcast domain
  • the MAC address table is the MAC address table corresponding to BD1
  • the N2 is recorded in the MAC address table entry corresponding to the Mb1
  • the PE1 receives the The routing message X1 learns the correspondence between the Mb1 and the N2.
  • Step (4) The following dependency exists on the control plane: on the PE2 node, the L3VNI is bound to the IP-VRF (marked as VRF1 in Figure 1), and the L2VNI is bound to the MAC-VRF (in Figure 1 Marked as BD1).
  • the PE2 publishes the RT-2 route corresponding to the IRB interface to PE1, it carries L3VNI instead of L2VNI, and the L3VNI is the L3VNI bound to the IP-VRF instance bound to the IRB interface.
  • step (3) is to check the MAC address table for forwarding
  • step (4) is to check the IP routing table for forwarding.
  • the two are completely different forwarding processes. In some cases, if the sending end It is to check the MAC address table for forwarding, and at the receiving end, it must be forwarded at least through the destination MAC. In addition, if the sending end is to check the IP routing table for forwarding, the receiving end still needs to check the IP routing table for forwarding.
  • PE1 when PE1 receives an Ethernet packet with an inner IP packet of P7 from AC4 in the local VRF1 instance (for example, a data packet communicating from IF4 to IRB1), and checks the IP-VRF route through the EVPN symmetric forwarding process and forwards P7 to PE2
  • the forwarding of P7 in PE2 and the forwarding of P1 in PE2 are both based on L3VNI to check the same IP routing table.
  • L3VNI to check IP Routing table, one takes the IRB process according to L2VNI.
  • the present disclosure unifies the table look-up process in the two cases, and thus can delete the forwarding instructions that follow the IRB process according to the L2VNI. Therefore, the instruction resource consumption of the forwarding plane can be reduced, especially when the forwarding plane is implemented by an ASIC chip, the advantages are obvious.
  • this example uses the communication from IF1 to IF3 as an example to illustrate the technical solutions of the present disclosure, in this example, communication from IF1 to IF2 can also exist at the same time, and these communications still rely on The EVPN process defined in some situations, this example is only a partial modification of the EVPN process in some situations, and it still needs to be implemented on the basis of the EVPN process in some situations.
  • PE2 can also advertise the MAC entries it learned on AC1 to PE1 in the form of RT-2 routes.
  • PE1 will import the X1 routes and these routes into the BD1 instance to form MAC entries. , You can take the same action.
  • Application example 1 takes VXLAN EVPN as an example.
  • the L2EVPN encapsulation of VXLAN EVPN has the same format as the L3EVPN encapsulation. Therefore, only the control plane needs to be extended to achieve the purpose of reducing the forwarding plane.
  • L2EVPN encapsulation and L3EVPN encapsulation have different formats. The same purpose cannot be achieved by extending the control plane. Therefore, the encapsulation format used by SRv6/MPLS EVPN in L2EVPN and L3EVPN must be unified first. To achieve the above purpose. This unification actually removes the encapsulation format defined by SRv6/MPLS EVPN specifically for L3EVPN.
  • L3EVPN forwarding a data message format compatible with L2EVPN is also adopted.
  • the following uses SRv6 EVPN as an example to explain how to perform the above transformation.
  • Application example 2 includes the following process (taking the communication from the IF1 interface to the IF3 interface as an example) steps (1) to (4).
  • Step (1) PE2 publishes the RT-2 routing packet (denoted as X1) corresponding to the IRB1 interface to PE1.
  • the value of L2LA in X1 is not the value of L2LE (that is, the SRv6 SID corresponding to the BD1 instance) but the value of L3LE (that is, the SRv6 SID corresponding to the IP-VRF instance).
  • Step (2) PE1 receives the routing message X1 and adds it to the local BD1 instance to form a MAC entry in the BD1 instance (its MAC address is Mb1).
  • the Mb1 entry records the SRv6 SID corresponding to the IP-VRF instance on PE2.
  • Step (3) PE1 receives Ethernet packet EP2 from local AC1, its source MAC is M1, its destination MAC is Mb1, its inner layer is IP packet is P2, for P2, its source IP is H1, and its destination IP Is H3, and checks the MAC address table to determine the transmission to the remote PE2; the PE1 adds SRv6 encapsulation outside the EP2 to become the message USP2 (as shown on the right side of Figure 5), where the source of the SRv6 encapsulation The IP is N1, and the destination IP is N2; PE1 sends the USP2 message to PE2.
  • Step (4) PE2 receives an IP message (such as the USP2 message), checks the global routing table according to its destination IP (such as the N2) to obtain its SID type, and performs different forwarding according to different SID types.
  • the SID types include at least End.DT46E and End.DT2U.
  • the SID of End.DT46E is the newly defined SRv6 SID of this disclosure. Specifically, the SID of End.DT46E and End.DT46 have the same functions, in addition to the following additional functions: its inner IP
  • the Ethernet encapsulation corresponding to the payload is also used as part of the payload of End.DT46E.
  • the outer DIP is a SID of End.DT46E type (for example, for communication from IF1 to IF3), the inner Ethernet header is stripped first, and then the routing table is checked and forwarded in the corresponding IP-VRF instance according to the inner IP; If the outer DIP is an End.DT2U type SID (for example, for communication from IF1 to IF2), it will be forwarded by checking the MAC address table in the corresponding MAC-VRF instance according to the inner Ethernet header.
  • End.DT2U type SID for example, for communication from IF1 to IF2
  • Step (1) The following dependency exists on the control plane: the AC1 is bound to the broadcast domain BD1, the MAC address table is the MAC address table corresponding to BD1, and the N2 is recorded in the MAC address entry corresponding to the Mb1, so The PE1 learns the correspondence between the Mb1 and the N2 by receiving the routing message X1, and the N2 is carried in the source IP of the USP2.
  • Step (2) The following dependency exists on the control plane: On the PE2 node, the End.DT46E type SID is bound to the IP-VRF (denoted as VRF1), and the End.DT2U type SID is bound to the MAC-VRF.
  • VRF1 IP-VRF
  • the End.DT2U type SID is bound to the MAC-VRF.
  • the PE2 publishes the RT-2 route corresponding to the IRB interface to PE1, it carries the SID of End.DT46E instead of the SID of End.DT2U, and the SID of End.DT46E is the IP bound to the IRB interface -The SID of End.DT46E type bound to the VRF instance.
  • step (1) it is to check the MAC address table for forwarding
  • step (2) it is to check the IP routing table for forwarding.
  • the two are completely different forwarding processes, and in some cases, if The sending end is to look up the MAC address table for forwarding, and the receiving end still needs to forward at least through the destination MAC first. In addition, if the sending end is to check the IP routing table for forwarding, the receiving end still needs to check the IP routing table for forwarding.
  • the End.DT46E type of SID now adopts unified encapsulation and simultaneously completes the L3 EVPN forwarding scenario and the EVPN IRB forwarding scenario that were originally completed by the End.DT46 and End.DT2U SID types and two packet encapsulation formats. Therefore, The current End.DT2U type SID no longer needs to support the EVPN IRB forwarding process. Moreover, the current End.DT46E uses a unified forwarding process to complete the L3 EVPN forwarding division and the EVPN IRB forwarding division. Therefore, the instruction resource consumption of the forwarding plane can be reduced, especially when the forwarding plane is implemented by an ASIC chip. The advantages are obvious.
  • the forwarding on PE2 in some cases is through the process from MAC-VRF (ie BD1) to IP-VRF and then to MAC-VRF (ie BD2), but In this example, only the process from IP-VRF to MAC-VRF is passed, so the forwarding performance is also high.
  • Application example 2 uses SRv6 EVPN as an example to illustrate how to unify the encapsulation formats used in L2EVPN and L3EVPN.
  • the following uses MPLS EVPN as an example to illustrate how to perform the above transformation.
  • Application example 3 includes the following process (taking the communication from the IF1 interface to the IF3 interface as an example) steps (1) to (4).
  • Step (1) PE2 publishes the RT-2 routing packet (denoted as X1) corresponding to IRB1 to PE1.
  • the value of L2LA in X1 is not the value of L2LE (that is, the MPLS label corresponding to the BD1 instance) but the value of L3LE (that is, the MPLS label corresponding to the IP-VRF instance).
  • Step (2) PE1 receives the routing message X1 and adds it to the local BD1 instance to form a MAC entry in the BD1 instance (its MAC address is Mb1).
  • the Mb1 entry records the MPLS label corresponding to the IP-VRF instance.
  • Step (3) PE1 receives the Ethernet packet EP3 from the local AC1, its source MAC is M1, its destination MAC is Mb1, its inner layer is IP packet P3, and for the P3, its source IP is H1, and its destination The IP is H3, and the MAC address table is checked to decide to send it to the remote PE2; the PE1 adds EVPN encapsulation to the EP3 to become a message USP3 (as shown on the right side of FIG. 6). PE1 sends the USP3 message to PE2.
  • Step (4) PE2 receives the USP3 message, finds the corresponding IP-VRF according to its EVPN label, and transfers the P3 message from the USP3 message in the Ethernet message EP3 carried in the inner layer of the EVPN label The message is extracted, and the destination IP (ie, H3) of the P3 message is used to look up the routing table in the IP-VRF and forward the P3 message according to the routing table.
  • the destination IP ie, H3
  • the IP packet in the inner layer of the label does not carry Ethernet encapsulation, and Ethernet encapsulation needs to be included here because
  • the packets received by PE2 from PE1 through the L3EVI label here are not necessarily forwarded in the L3 EVPN (IP-VRF) process of PE1, but may also be forwarded in the L2 EVPN (MAC-VRF) process of PE1 (As shown in step 303), in order to handle these two situations at the same time (for example, the communication from IF1 to IRB1 and the communication from IF4 to IRB1), the Ethernet encapsulation corresponding to the inner IP packet needs to be reserved uniformly.
  • the bottom label of the USP3 message received by PE2 is an L3EVI label, but the inner layer of the L3EVI label is an Ethernet message.
  • Step (3) The following dependency exists on the control plane: the AC1 is bound to the broadcast domain BD1, the MAC address table is the MAC address table corresponding to BD1, and the EVPN encapsulation information is recorded in the MAC address table entry corresponding to Mb1, The PE1 obtains the EVPN encapsulation information by receiving the routing message X1 sent by the PE2.
  • Step (4) has the following dependency on the control plane: when the PE2 publishes the RT-2 route corresponding to the IRB interface to PE1, it carries the EVI label of the IP-VRF bound to the IRB interface instead of the IRB interface. EVI tag of the specified MAC-VRF (ie BD instance).
  • PE may go through a forwarding process of "(IP-VRF)-IRB-(MAC-VRF)" when forwarding IP data packets in the IP-VRF instance.
  • This application example shortens it to only the IP -VRF can complete the entire forwarding process through routing iteration.
  • application example 4 is based on application example 3, and is not limited to this.
  • Application example 4 may also be based on application example 1 or application example 2.
  • Application example 4 includes the following process (taking the communication from the IF4 interface to the IRB1 interface as an example) steps (1) to (4).
  • Step (1) PE2 publishes the RT-2 routing packet (denoted as X1) corresponding to the IRB1 interface to PE1.
  • the value of L2LA in X1 is not the value of L2LE (that is, the MPLS label corresponding to the BD1 instance) but the value of L3LE (that is, the MPLS label corresponding to the VRF1 instance) (denoted as Lx1).
  • Step (2) PE1 receives the routing message X1 and adds it to the local BD1 instance to form a MAC entry in the BD1 instance (its MAC address is Mb1).
  • the Mb1 entry records the MPLS label corresponding to the IP-VRF instance.
  • PE1 receives the routing entry X1 and adds it to the local VRF1 instance to form two detailed routing entries in the VRF1 instance, which are marked as RE4a and RE4b respectively, and the IP key value of the RE4a entry is the X1 IP (ie I1) in the key value of X1, GW-IP is the MAC mapping address corresponding to the MAC (ie Mb1) in the key value of X1; the IP key value of the RE4b entry is the MAC mapping address, GW-IP If it is empty, the next hop of the public network is the next hop of X1 (ie, N2), and the EVPN outgoing label is the label represented by L2LA in X1.
  • the IP key value of the RE4a entry is the X1 IP (ie I1) in the key value of X1
  • GW-IP is the MAC mapping address corresponding to the MAC (ie Mb1) in the key value of X1
  • the IP key value of the RE4b entry is the
  • Step (3) PE1 receives an IP packet that needs to be forwarded in the VRF1 instance (for example, an IP packet communicating from IF4 to IRB1).
  • the source IP is H4 and the destination IP is I1.
  • the PE1 only passes through the The RE4a and RE4b in the IP-VRF instance obtain the value of Lx1, and there is no need to obtain the value of Lx1 in the BD1 instance; the PE1 is added outside the IP packet
  • the Ethernet header and the label with the value Lx1 become the MPLS message USP4, and the MPLS message USP4 is sent to PE2 through the MPLS tunnel.
  • the format of the USP4 after the MPLS tunnel encapsulation is added is shown in FIG. 7, and the GEPL is vacant in this specific implementation.
  • Step (4) PE2 receives the USP4 message, finds the VRF1 instance according to its EVPN label, and finds the IRB1 interface from the destination IP (ie I1) of the IP message carried in the inner layer of the USP4 message.
  • Step (3) The following dependency exists on the control plane: PE1 receives the route X1 from PE2, the type of the route X1 is the RT-2 route, the IP in the key value of the route X1 is I1, and the key value is The MAC of Mb1 is Mb1, its BGP next hop is N2, the value of its MPLS Label1 field is Lx1, the MAC mapping address corresponding to Mb1 is IPm1, and the MAC mapping address is composed of the first designated prefix, BDI, and MAC address ( As shown in Figure 8), the first designated prefix is an 8-byte designated value, the lower 6 bytes are the Mb1 address, and the BDI is the BDI that identifies the BD instance to which the Mb1 address belongs.
  • the designated prefix is selected as a special value, which can ensure that the MAC mapping address does not conflict with the host IP address in the IP-VRF instance.
  • PE1 will receive the X1 from PE2 and map it to the following two RT-5 detailed routes Y1 and Y2 from PE2:
  • the Y1 is a detailed RT-5 route, and the IP in the key value is the I1 , Its GW IP is IPm1, and its label value is empty;
  • the Y2 is a detailed RT-5 route, the IP in its key value is IPm1, its EVPN label is the Lx1, its router’s MAC is Mb1, and its BGP
  • the next hop is N2, and its GW IP is 0.
  • the Y1 forms a routing entry RE4a in the routing table of the VRF1 instance, and the Y2 forms a routing entry RE4b in the routing table. Therefore, in some cases, the ARP on the IRB1 interface is queried to obtain the remote MAC and then The behavior of checking the MAC address table in BD1 described in IRB1 can be replaced by the iterative process of routing from RE4a to RE4b in the VRF1 instance. Since checking the IP routing table is inherently necessary for EVPN Layer 3 forwarding, there is actually no increase in the number of table lookups, but the original process of checking the ARP table and MAC address table is removed.
  • the RT-3 route corresponding to the BD can also be advertised in the IP-VRF instance bound to the IRB interface bound to the BD.
  • RD fills in the RD of the IP-VRF
  • the Ethernet Tag ID fills in BDI
  • eRT Fill in the eRT of the IP-VRF instance
  • fill in the label with the label allocated by this node for the BD which is called the BD label of the BD instance.
  • the BD label identifies both the IP-VRF instance and the BD instance.
  • the MAC entry in BD1 and the IP routing entry formed by the MAC mapping address in BD1 in VRF1 are of the same origin, so they are duplicate information.
  • Application example 5 combines the former on the basis of application example 4. It is further unified into the latter, thereby reducing duplicate information.
  • Application example 5 includes the following process (taking the communication from the IF1 interface to the IRB1 interface as an example) steps (1) to (5).
  • Step (1) PE2 publishes the RT-2 routing entry (denoted as X1) corresponding to the IRB1 interface to PE1.
  • the value of L2LA in X1 is not the value of L2LE (that is, the MPLS label corresponding to the BD1 instance) but the value of L3LE (that is, the MPLS label corresponding to the IP-VRF instance) (denoted as Lx2).
  • Step (2) PE1 receives the routing entry X1 and adds it to the local VRF1 instance to form two detailed routing entries in the VRF1 instance, which are respectively recorded as RE5a and RE5b.
  • the IP key value of the RE5a entry is The IP in the key of X1 (that is, the I1), GW-IP is the MAC mapping address corresponding to the MAC in the key of X1 (that is, the Mb1); the IP key of the RE5b entry is the The GW-IP and GW-IP of the RE5a entry are empty, the next hop of the public network is the next hop of the X1, and the EVPN outgoing label is the L2LA field in the X1.
  • Step (3) the MAC mapping address of the MAC address Mb2 of the local IRB2 interface of PE1 is IPm2, the IP-VRF instance to which IRB2 belongs is VRF1, and the PE1 adds the IPm2 as a 128-bit route to the VRF1 instance.
  • Step (4) PE1 receives an Ethernet message EDP5 from AC1 in the BD1 instance, and the PE1 uses the MAC mapping address corresponding to the destination MAC of the EDP5 to check the routing table of VRF1 (for the communication from the IF1 interface to the IRB1 interface)
  • the source MAC of the EDP5 is M1
  • its destination MAC is the Mb2
  • its inner IP packet is P8, and for P8, its source IP is H1
  • its destination IP is I1) Hit the IPm2 routing entry
  • IPm2 is an IRB mapping address
  • Step (5) PE2 receives the USP5 message, finds the corresponding IP-VRF (ie VRF1) according to its EVPN label, and extracts the P8 message from the Ethernet message carried by the USP5 message, The destination IP (ie I1) of the P8 message is used to determine the IRB interface (ie IRB1) to which it belongs, and the P8 message is processed on the IRB interface.
  • IP-VRF IP-VRF1
  • PE1 can also add the MAC entries learned from the local AC in BD1 to VRF1 in the form of MAC mapping addresses, and remove the MAC entries in BD1. It is worth noting that at this time, for the communication from IF1 to IF2, the process of checking the IP-VRF routing table according to the MAC mapping address of the destination MAC is also required.
  • the upper 64 bits of all MAC mapping addresses are the first specified value.
  • a 64-bit IPv6 route with the upper 64 bits as the first specified value can be generated in the IP-VRF instance. This route is called a BUM route.
  • BUM route When checking the IP routing table with the MAC mapping address and hits the BUM route, it means that the message should be broadcast in the BD instance to which the message belongs.
  • the BUM route two goals are achieved. The first is to check the IP routing table through the MAC mapping address and it will not hit the default route, which ensures that the default route is still only used for Layer 3 forwarding; the second is through the MAC mapping address It is impossible to check the IP routing table without hitting any routes, because BUM routes always meet the hit conditions.
  • this example achieves the effect of pruning duplicate information, and at the same time, it unifies the routing tables checked by Layer 2 forwarding and Layer 3 forwarding, making the BD1 instance degenerate into an instance without MAC entries (Further, those of ordinary skill in the art can also move the RT-3 routing to the VRF1 instance, so that the BD1 instance further degenerates into a conceptual entity without forwarding entries and no longer a MAC-VRF instance), which The function as a forwarding instance is replaced by the VRF1 instance.
  • this disclosure refers to the IP address mapped from the MAC address of the IRB interface as the IRB mapping address, which can be set by setting the next hop address of the IPv6 routing entry formed by the IRB mapping address of the local IRB interface to a special value. It is distinguished from other IPv6 routing entries, so as to adopt different forwarding behaviors from other IPv6 routing entries.
  • the host MAC address needs to be published to the remote PE node, which means that if there is an SPE node between PE1 and PE2, the MAC address information of all hosts should be stored on the SPE node to form a MAC address overload situation.
  • Application example 6 is based on application example 5. Overcome these difficulties and use MAC address learning on the data plane to solve the problem of MAC address overload.
  • Application example 6 includes the following process steps (1) to (8).
  • the MPLS-based L3 EVPN label allocated by PE2 to the IRB1 interface in the VRF1 instance is DAEPL5, and the GEPL corresponding to DAEPL5 is GEPL5, then PE2 advertises the GEPL route corresponding to IRB1 to PE1,
  • the GEPL route may be a detailed RT-2 route, the IP address in the key value of the RT-2 route is the GEPL mapping address corresponding to the GEPL5, and the MAC address in the key value is 0, and its route distinction
  • the symbol RD is the RD of the VRF1 instance, its L2LA attribute is the DAEPL5 label, and its next hop is the node IP address of PE2 (ie, N2).
  • Step (2) the BD1 instance on PE2 is bound to the AC2 interface, the MPLS-based L3 EVPN label assigned to the AC2 interface in the BD1 instance is DAEPL6, and the GEPL corresponding to the DAEPL6 is GEPL6, then PE2 publishes information to PE1
  • the GEPL route corresponding to AC1 where the GEPL route can be a detailed RT-2 route, the IP address in the key value of the RT-2 route is the GEPL mapping address corresponding to the GEPL6, and the key value is MAC
  • the address is 0, its RD is the RD of the VRF1 instance, its L2LA attribute is the DAEPL6 label, and its next hop is the node IP address of PE2 (ie, N2).
  • step (1) and step (2) are independent, and the following step (3) can be inherited after step (1) or after step (2).
  • Step (3) PE1 receives the GEPL route described in step (1) or step (2), and adds it to the local VRF1 instance to form routing entries RE6a and RE6b, RE6a and RE6b in the VRF1 instance, respectively
  • the IP key value of the entry is the IP in the key value of the corresponding GEPL route
  • GW-IP is empty
  • the next hop of the public network is the next hop of the corresponding GEPL route
  • the EVPN out label is the value of the L2LA attribute of the corresponding GEPL route.
  • Step (4) when PE2 receives the message EDP6 from the local AC2 or when PE2 sends the IP message IDP7 from the IRB1 interface in the VRF1 instance and encapsulates the IDP7 into an Ethernet message EDP7, PE2 is encapsulating the EDP6 or When the IDP7 is sent to PE1, it is first encapsulated as a message MEDP5.
  • the MEDP5 includes the GEPL corresponding to the AC2 or IRB1 (ie, the GEPL5 or GEPL6).
  • the EDP6 or IDP7 is The source MAC in the MEDP5 is denoted as Mx, the source IP is denoted as IPx, and the GEPL is denoted as GEPLx.
  • Step (5) when PE1 receives the MEDP5 from PE2 and finds that it carries GEPL, the PE1 is like receiving two RT-5G routes (denoted as G6a and G6b) in the following form: the key of the G6a
  • the IP in the value is the IPx
  • GW-IP is the GEPL mapping address of the GEPLx, and the label is empty
  • the IP in the G6b key value is the MAC mapping address of the Mx
  • GW-IP is the GEPLx
  • the GEPL mapping address, the label is empty.
  • Step (6) when PE1 receives the Ethernet message EDP8 from the local AC1, its destination MAC is the MAC (ie Mx) in the key value of G6b, and the PE1 determines the corresponding RE6a according to the GW-IP of the G6b Or RE6b, and encapsulate and forward the EDP8 message according to the RE6a or RE6b.
  • Step (7) When PE1 receives an IP message IDP8 on the AC4 interface, its destination IP is the IP (ie IPx) in the key value of G6a, and the PE1 determines the corresponding IP according to the GW-IP of G6a RE6a or RE6b, and encapsulate and forward the IDP8 message according to the RE6a or RE6b. Encapsulating the IDP8 message includes adding an Ethernet header to it.
  • Step (8) PE2 receives the EDP8 or IDP8 message, finds the corresponding IRB interface or AC interface according to its EVPN label, and then forwards it in the IP-VRF instance to which the IRB interface belongs, or forwards the message from the AC interface Get out.
  • the IRB1 interface can be found according to the DAEPL5 label (that is, the label in the RE6a), and the AC2 interface can be found according to the DAEPL6 label (that is, the label in the RE6b).
  • application example 6 and application example 4 have the same dependence on the control plane.
  • application example 6 does not use EVPN routing to advertise the host MAC address, but still uses EVPN routing similar to step (1) in application example 4 to advertise the L3LE corresponding to the IRB/AC interface.
  • application example 6 can obtain the following information from the IP routing entry (such as the G6b) obtained from the remote MAC address mapping: its GW-IP address is the global EP label mapping address corresponding to the MAC address (One possible format is shown in Figure 9), the BDI of the BD instance to which the MAC address belongs, and the MAC address of the IRB interface bound to the BD to which the MAC address belongs.
  • the EP label mapping address is an address mapped from GEPL, specifically, the EP label mapping address is an IP address mapped from GEPL and the second designated prefix.
  • the GEPL is a label formed by mapping the virtual routing forwarding edge identifier VE-ID and DAEPL, and its format is shown in FIG. 10.
  • the VE-ID is the unique identifier of the PE node where the IP-VRF instance is located on all nodes of the IP-VRF service
  • the DAEPL is the identification assigned by the PE node where the AC/IRB is located in the label space of each platform.
  • the AC is a message ingress interface when the MAC address corresponding to the MAC mapping address is learned as a local MAC entry.
  • the GEPL may also include a 4-byte version number.
  • the version number takes the eighth specified value.
  • VE-ID and DAEPL can also be compressed so that the sum of the two bit widths does not exceed 20 bits. At this time, DAEPL can only use a section of the tag pool of each platform.
  • each IP-VRF instance needs to be configured with a VE-ID in advance.
  • the method is that all IP-VRF instances in the same VPN (located in different PE nodes) must be configured with different VE-ID.
  • the ingress GEPL is only used for the data plane learning of MAC/ARP entries, not for forwarding current data packets, and it is in the inner layer of the egress EP label, so it may not be a standard MPLS label, for example, it can be a new control word.
  • the sum of the bit widths of the two fields of VE-ID and DAEPL does not exceed 20 bits, it can also be a layer of MPLS label.
  • VE-ID and DAEPL can be used as a layer of MPLS label respectively. At this time, the label corresponding to VE-ID can be outside, and the label of DAEPL is inside.
  • VE-ID and DAEPL are actually a kind of upstream distribution label for the egress node of the outer EP label.
  • the export EP label is their context label.
  • the label corresponding to VE-ID is a label in a new context label space. This label space corresponds to each VPN and can be called per VPN label. space.
  • GEPL itself does not necessarily require DAEPL as its component.
  • the construction of GEPL from DAEPL is a special method of this example and is not used to limit the format of GEPL. It can be used as long as it conforms to the GEPL concept defined in this disclosure.
  • EVPN technology can provide L2VPN services and L3VPN services.
  • L2VPN services since the MAC address routing entry of the L2VPN service (hereinafter referred to as the MAC entry) corresponds to the MAC address of the host, the MAC address is not available Convergence, therefore, the number of MAC entries is proportional to the number of hosts, which will cause the VPN core node MAC address routing overload.
  • SPE equipment refers to the equipment that is connected to the UPE and is located inside the network. It is called the upper layer PE (Superstratum PE) equipment or the carrier-side PE (Service Provider-end PE) equipment. The SPE equipment mainly completes the VPN routing. Management and release.
  • UPE equipment refers to equipment directly connected to users, called underlayer PE (Underlayer PE) equipment or user-end PE (User-end PE) equipment, UPE equipment mainly completes the user access function.
  • Figure 1 is an example of two SPE devices (SPE1 and SPE2) and two UPE devices (UPE1 and UPE2, respectively).
  • SPE1 and SPE2 SPE devices
  • UPE1 and UPE2 UPE devices
  • MAC entries of all hosts need to be stored on SPE1 and SPE2. When the number of hosts is too large, it will cause MAC entries are overloaded.
  • PBB EVPN does not need to publish the MAC address of the host to the VPN core node, but only needs to publish the B-MAC address corresponding to the ESI or PE device, thereby solving the problem of MAC entry overload.
  • PBB EVPN can only be used as a pure L2VPN alone, and cannot be used in IRB scenarios in combination with L3VPN.
  • the reason is that its protocol stack is too complicated, the forwarding process is too long, and the number of table lookups is too many, which cannot be implemented efficiently.
  • ASIC chips do not support it, and microcode implementation basically needs to sacrifice 1/2 or even 3/4 throughput.
  • IRB function and avoiding MAC address overload are difficult to achieve at the same time.
  • a technical solution corresponding to the embodiment of the present disclosure and the application example is proposed.
  • step (3) in application example 5 can also be superimposed with this example.
  • AC1 will receive an Ethernet report whose destination MAC is Mb2
  • the Ethernet message will be forwarded according to the method in step (4) in application example 5.
  • the GEPL labels corresponding to the corresponding Layer 2 ACs of the same ESI on different PE devices of the same L2EVI need to be consistent.
  • static configuration can be used.
  • the GEPL tag can also be used for ESI filtering (breaking the loop formed across PE devices in the same ES).
  • application example 7 is identical to application example 6.
  • application example 7 does not carry GEPL between the EVPN label and the inner Ethernet header, but directly carries the value of GEPL or the GEPL mapping address in the IP option. Except for the position of GEPL in the data packet encapsulation, the control plane and forwarding process of application example 7 are exactly the same as those of specific application example 6.
  • application example 8 is identical to application example 2.
  • application example 8 does not carry the inner Ethernet header. Instead, the original Ethernet header information is built in the lower 64 bits of the outer source IP and destination IP.
  • the present disclosure uses the outer source IP or the outer
  • the lower 64 bits of the layer destination IP are called ARG.ETH, and the position of the ARG.ETH is shown in FIG. 11.
  • the source MAC and Ethertype information can be built in the lower 64 bits of the outer source IP
  • the destination MAC and VLAN information can be built in the lower 64 bits of the outer source IP.
  • Application example 9 can be modified on the basis of any application example in application example 1, application example 2, and application example 3. When one of the application examples (denoted as basic application example) is selected as the basis, unless otherwise specified Otherwise, application example 9 is exactly the same as the basic application example.
  • DGW Data Center Gateway
  • the DGW node may be modified from PE1 in the basic application example.
  • application example 9 is on the DGW node in the data center centralized gateway network. As shown in Figure 13, application example 9 does not deploy BD instances (you need to first refer to application example 9 to degenerate BD instances into concepts The method of the sexual entity is modified), only the IRB interface is deployed as a centralized gateway interface, and the MAC address of the IRB interface is advertised to the VTEP node through the RT-2 route.
  • IP-VRF label As the Label1 field (VXLAN and MPLS encapsulation) of the RT-2 route or SRv6 SID that replaces the function of the Label1 field.
  • the label of the IP-VRF may be a VNI label, an MPLS label, and an SRv6 SID.
  • an embodiment of the present disclosure also provides a routing device.
  • the routing device includes a receiving unit 1401, a generating unit 1402, and a routing unit 1403.
  • the receiving unit 1401 is configured to receive a first routing message sent by a second PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is a routing attribute used to carry the value of L2LE in EVPN routing
  • the L2LE is the EVPN local label corresponding to the MAC-VRF instance
  • the L3LE is the EVPN local label corresponding to the IP-VRF instance.
  • the generating unit 1402 is configured to generate a first EVPN routing entry based on the first routing message, and the value of the EVI label of the first EVPN routing entry is the value of the L2LA in the first routing message.
  • the routing device further includes: a routing unit 1403, configured to receive a first Ethernet packet, and determine based on the first EVPN routing entry that the receiving end of the first Ethernet packet is the second PE device, And generating a first target packet to be sent to the second PE device based on the first Ethernet packet, the first target packet carrying the EVI tag; the first Ethernet packet carrying the first IP packet, the first EVPN routing entry is a MAC entry; the first target packet is sent to the second PE device, and the first target packet passes through the second PE device
  • the EVI tag determines the IP-VRF instance to which the EVI tag belongs, and queries the IP routing table in the IP-VRF instance to forward the first target message.
  • each unit in the routing device shown in FIG. 14 can be understood with reference to the relevant description of the foregoing routing method.
  • the function of each unit in the routing device shown in Fig. 14 can be realized by a program running on a processor, or by a specific logic circuit.
  • FIG. 15 is a schematic flowchart of a routing method provided by an embodiment of the disclosure. As shown in FIG. 15, the routing method includes step 1501.
  • the second PE device sends a first routing message to the first PE device.
  • the L2LA of the first routing message carries the value of L3LE, and the L2LA is used to carry the value of L2LE in the EVPN route. Routing attributes; the L2LE is the EVPN local label corresponding to the MAC-VRF instance, the L3LE is the EVPN local label corresponding to the IP-VRF instance; the first routing message is used by the first PE device to the The EVPN data message forwarded by the second PE device adds the L3LE indicated by the L2LA in the first routing message.
  • step 1501 above is directed to the behavior of the control plane, and the behavior of the above control plane determines the behavior of the subsequent forwarding plane.
  • the implementation of the behavior of the control plane in the embodiments of the present disclosure can automatically obtain a new one without modifying the forwarding instruction. The act of forwarding the face. It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to VXLAN EVPN, or MPLS EVPN, or SRv6 EVPN.
  • the L2LE and the L3LE are VNI; or, in MPLS EVPN, the L2LE and the L3LE are MPLS labels; or, in SRv6 EVPN, the L2LE and the L3LE are SRv6 SID.
  • the second PE device when the L3LE is an SRv6 SID or an MPLS label, receives a data packet carrying the L3LE sent by the first PE device, and the second PE device determines The data message includes an Ethernet header within the L3LE.
  • the data message refers to all target messages sent by the first PE device that include the L3LE.
  • the second PE device side is configured with a first MAC-VRF instance and a first IP-VRF instance, and the first MAC-VRF instance and the first IP-VRF instance pass through the An interface connection, the first MAC-VRF instance is connected to the first AC; the L3LE carried in the first routing message is the L3LE of the first IP-VRF instance.
  • the first routing message also carries at least one of the IP and MAC of the first interface, and the first interface is an IRB interface.
  • the key value in the first routing message includes GEPL, and the L2LA of the first routing message is the DAEPL corresponding to the first AC or the first interface, and One hop is the IP address of the second PE device; the GEPL is a value that uniquely identifies the first AC or the first interface in the EVPN service where the first IP-VRF instance is located.
  • the second PE device receives the first packet to be forwarded to the first PE device from the first AC or the first interface; the second PE device displays the first packet in the first packet
  • the outer layer adds the GEPL to obtain a fourth target packet, and sends the fourth target packet to the first PE device; for the second PE device, the first packet is received from the first interface
  • the first packet is sent to the first interface from the IP-VRF instance to which the first interface belongs.
  • an embodiment of the present disclosure also provides a routing device. As shown in FIG. 16, the routing device includes a sending unit 1601.
  • the sending unit 1601 is configured to send a first routing message to the first PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is a routing attribute used to carry the value of L2LE in EVPN routing
  • the L2LE is the EVPN local label corresponding to the MAC-VRF instance
  • the L3LE is the EVPN local label corresponding to the IP-VRF instance
  • the first routing message is used by the first PE device in the direction of the second
  • the EVPN data message forwarded by the PE device adds the L3LE indicated by the L2LA in the first routing message.
  • each unit in the routing device shown in FIG. 16 can be understood with reference to the related description of the foregoing routing method.
  • the function of each unit in the routing device shown in FIG. 16 can be realized by a program running on a processor, or can be realized by a specific logic circuit.
  • Fig. 17 is a structural diagram of another routing device provided by an embodiment of the present disclosure.
  • the routing device 1700 shown in FIG. 17 includes a processor 1710, and the processor 1710 can call and run a computer program from a memory to implement the method in the embodiment of the present disclosure.
  • the routing device 1700 may further include a memory 1720.
  • the processor 1710 may call and run a computer program from the memory 1720 to implement the method in the embodiment of the present disclosure.
  • the memory 1720 may be a separate device independent of the processor 1710, or may be integrated in the processor 1710.
  • the routing device 1700 may further include a transceiver 1730, and the processor 1710 may control the transceiver 1730 to communicate with other devices, specifically, it may send information or data to other devices, or Receive information or data sent by other devices.
  • the transceiver 1730 may include a transmitter and a receiver.
  • the transceiver 1730 may further include an antenna, and the number of antennas may be one or more.
  • the embodiments of the present disclosure also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present disclosure, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present disclosure.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present disclosure.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the computer program causes the computer to execute the various methods implemented by the mobile terminal/terminal device in the embodiments of the present disclosure. For the sake of brevity, the corresponding process will not be repeated here.
  • the embodiments of the present disclosure also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present disclosure, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present disclosure.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present disclosure.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present disclosure.
  • it is not here. Repeat it again.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present disclosure, and the computer program instructions cause the computer to execute the corresponding methods implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present disclosure.
  • the process will not be repeated here.
  • the embodiment of the present disclosure also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present disclosure.
  • the computer program is run on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present disclosure.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present disclosure.
  • the computer program runs on the computer, the computer executes each method in the embodiment of the present disclosure. For the sake of brevity, the corresponding process implemented by the device will not be repeated here.
  • the first PE device receives the first routing message sent by the second PE device, the L2LA of the first routing message carries the value of L3LE, and the L2LA is in the EVPN routing
  • the routing attribute used to carry the value of L2LE is the L2LE is the EVPN local label corresponding to the MAC-VRF instance, and the L3LE is the EVPN local label corresponding to the IP-VRF instance; the first PE device is based on the first route
  • the message generates a first EVPN routing entry, and the value of the EVI label of the first EVPN routing entry is the value of the L2LA in the first routing message.
  • the EVPN IRB message of the destination MAC sent from the remote MAC-VRF can be forwarded directly into the IP-VRF instance without being forwarded by the MAC-VRF instance for the MAC of the local IRB interface, thereby simplifying
  • the forwarding process of EVPN IRB services especially in the case of EVPN IRB forwarding that originally required two MAC-VRF instance forwarding, through the implementation of the technical solution of the present disclosure, only one MAC-VRF instance forwarding is required at most.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can A personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请公开了一种路由方法及路由设备，所述方法包括：第一PE设备接收第二PE设备发送的第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；其中，所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加由所述第一路由报文中的L2LA所表示的L3LE。

Description

路由方法及路由设备 技术领域
本公开涉及(但不限于)通讯技术领域。
背景技术
二层虚拟专用网(Layer 2 Virtual Private Network，L2VPN)和三层虚拟专用网(Layer 3 Virtual Private Network，L3VPN)作为广泛应用的虚拟专用网(Virtual Private Network，VPN)技术，常常是组合应用的，称为集成路由与桥(Integrated Routing and Bridge，IRB)。
在某些情况下，转发流程是很长的，对于转发面实现来说有很大负担，尤其在转发面采用ASIC芯片实现时，要高性能地实现这套转发流程，对于转发面的成本压力很大。
发明内容
本公开实施例提供了一种路由方法及路由设备。
本公开实施例提供的路由方法，包括：第一运营商边缘(Provider Edge，PE)设备接收第二PE设备发送的第一路由报文，所述第一路由报文的二层标签属性(Layer 2 Label Atribute，L2LA)中携带三层标签实体(Layer 3 Label Entity，L3LE)的值，所述L2LA是在以太虚拟专用网(Ethernet Virtual Private Network，EVPN)路由中用于携带二层标签实体(Layer 2 Label Entity，L2LE)的值的路由属性；所述L2LE是媒体接入控制虚拟路由转发(Media Access Control Virtual Routing Forwading，MAC-VRF)实例对应的EVPN本地标签，所述L3LE是网络协议虚拟路由转发(Internet Protocol Virtual Routing Forwading，IP-VRF)实例对应的EVPN本地标签；所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加由所述第一路由报文中的L2LA所表示的L3LE。
本公开实施例提供的路由方法，包括：第二PE设备向第一PE 设备发送第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；所述第一路由报文用于所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加所述第一路由报文中的L2LA所表示的L3LE。
本公开实施例提供的路由设备，包括：接收单元，用于接收第二PE设备发送的第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；生成单元，用于基于所述第一路由报文生成第一EVPN路由条目，所述第一EVPN路由条目的EVPN实例(EVPN Instance，EVI)标签的值为所述第一路由报文中的L2LA的值。
本公开实施例提供的路由设备，包括：发送单元，用于向第一PE设备发送第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；所述第一路由报文用于所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加所述第一路由报文中的L2LA所表示的L3LE。
本公开实施例提供的路由设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行上文所述的方法。
本公开实施例提供的计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行上述的路由方法。
附图说明
附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。在附图中：
图1是本公开应用示例6在EVPN网络层次化中的组网图；
图2是本公开实施例提供的路由方法的流程示意图；
图3是本公开应用示例1-3的组网图；
图4是本公开应用示例4、5和6的组网图；
图5是本公开应用示例2的数据报文封装格式图；
图6是本公开应用示例3的数据报文封装格式图；
图7是本公开应用示例4、5和6的数据报文封装格式图；
图8是本公开应用示例4、5和6的MAC映射地址的格式图；
图9是本公开应用示例6的GEPL映射地址的格式图；
图10是本公开应用示例6的GEPL的格式图；
图11是本公开应用示例8的数据报文封装的格式图；
图12是经过本公开应用示例9优化前的组网图；
图13是经过本公开应用示例9优化后的组网图；
图14是本公开实施例提供的一种路由设备的结构图；
图15是本公开实施例提供的路由方法的流程示意图；
图16是本公开实施例提供的另一种路由设备的结构图；以及
图17是本公开实施例提供的又一种路由设备的结构图。
具体实施方式
为了能够更加详尽地了解本公开实施例的特点与技术内容，下面结合附图对本公开实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本公开实施例。
EVPN技术可以提供二层EVPN(Layer 2 EVPN，L2EVPN)业务和三层EVPN(Layer 3 EVPN，L3EVPN)业务。L2EVPN业务基于媒体接入控制(Media Access Control，MAC)地址进行转发，L3EVPN业务基于网络协议(Internet Protocol，IP)地址转发。EVPN业务在其每个PE节点上通过虚拟路由转发(Virtual Routing Forwading，VRF)实例来绑定接入电路(Access Circuit，AC)接口和转发数据包。L2EVPN的VRF实例称为MAC-VRF实例，L3EVPN的VRF实例称为IP-VRF实例，MAC-VRF实例和IP-VRF实例统称为EVPN实例(EVPN Instance， EVI)。
无论L2EVPN还是L3EVPN，都有以下三种封装格式：多协议标签交换(Multi-Protocol Label Switching，MPLS)封装、虚拟扩展局域网(Virtual eXtended LAN，VXLAN)封装和使用IPv6数据计划分段路由(Segment Routing with IPv6 dataplan，SRv6)封装。在MPLS封装下采用MPLS标签来标识EVI，在VXLAN封装下采用VXLAN网络标识符(VXLAN Network Identifier，VNI)来标识EVI，在SRv6封装下采用SRv6段标识符(Segment ID，SID)来标识EVI。以上三种标识EVI的实体统称为EVI标签，标识MAC-VRF的EVI标签称为二层EVI(Layer 2 EVI，L2EVI)标签，标识IP-VRF的EVI标签称为三层EVI(Layer 3 EVI，L3EVI)标签。
在MPLS或SRv6封装的EVPN业务中，EVI所在的节点称为该EVPN业务的PE节点，类似地，VXLAN封装的EVPN中EVI所在的节点称为该EVPN业务的VTEP或NVE节点。为描述方便起见，本公开中将VTEP/NVE/PE节点统称为PE节点。
EVPN可以将L2EVPN和L3EVPN组合起来形成EVPN IRB业务，其方法是：将同一个接口既绑定一个MAC-VRF实例又绑定一个IP-VRF实例，此时，该接口称为所述MAC-VRF实例的IRB接口，也称为所述MAC-VRF实例和所述IP-VRF实例通过该IRB接口进行了连接。
在EVPN IRB业务中，某些情况下要经过如下转发流程：首先，在MAC-VRF实例1中查MAC表得到IRB接口1；其次，在IRB接口1所绑定的IP-VRF实例1中查询IP路由表并得到IRB接口2；再次，基于IRB接口2查ARP表封装以太头；最后，在IRB接口2对应MAC-VRF实例中查MAC表进行转发。这一套转发流程是很长的，对于转发面实现来说有很大负担，尤其在转发面采用ASIC芯片实现时，要高性能地实现这套转发流程，对于转发面的成本压力很大。
IRB可以实现同子网的通信在L2EVPN中转发，跨子网的通信在某些情况下需要先根据L2EVI标签在L2EVPN中转发，再在L3EVPN中转发，使得转发流程过长、性能较低。为了克服VPN技术中存在的转发流程过长、性能较低的问题，提出了本公开实施例的以下技术方 案。
为描述方便起见，以下对本公开实施例中涉及到的相关概念进行说明。本公开实施例涉及到如下概念：RT-1路由、RT-2路由、RT-3路由、RT-5路由、二层标签实体(Layer 2 Label Entity，L2LE)、三层标签实体(Layer 3 Label Entity，L3LE)、二层标签属性(Layer 2 Label Atribute，L2LA)、三层标签属性(Layer 3 Label Atribute，L3LA)、RT-5G路由、RT-5L路由、端点(End Point，EP)、端点标签(End Point Label，EPL)、下游分配端点标签(Downstream-assigned EPL，DAEPL)、全局端点标签(Global EPL，GEPL)、接入电路(Access Circuit，AC)、导出路由目标(export Route Target，eRT)、广播域标识符(Broadcast Domain Identifier，BDI)、虚拟路由转发边缘标识符(VRF Edge Identifier，VE-ID)。
RT-1路由，即EVPN路由类型(Route-Type)1，也就是第一类EVPN路由，同理，RT-2、RT-3、RT-5分别是第2、3、5类EVPN路由。
一个IRB接口的L2LE，即该IRB接口所属的广播域(Broadcast Domaing，BD)实例对应的转发标签，在VXLAN EVPN中是一个VNI(称为L2VNI)，在MPLS EVPN中是一个MPLS标签，在SRv6 EVPN中是一个SRv6 SID。
一个IRB接口的L3LE，即该IRB接口所绑定的IP-VRF实例对应的转发标签，在VXLAN EVPN中是一个VNI(称为L3VNI)，在MPLS EVPN中是一个MPLS标签，在SRv6 EVPN中是一个SRv6 SID。
L2LA是RT-1、RT-2、RT-3路由中承载L2LE的值的路由属性，在VXLAN EVPN或MPLS EVPN中是所述EVPN路由的标签字段(在RT-2路由中为MPLS Label1字段)，在SRv6 EVPN中是所述EVPN路由的SRv6 VPN SID TLV(其SID-Type字段值为2)。
L3LA是RT-2、RT-5路由中承载L3LE的值的路由属性，在VXLAN EVPN或MPLS EVPN中是所述EVPN路由的标签字段(在RT-2路由中为MPLS Label2字段)，在SRv6 EVPN中是所述EVPN路由的SRv6 VPN SID TLV(其SID-Type字段值为1)。
RT-5G路由是GW-IP字段不为0且不携带L3LE的RT-5路由， RT-5L路由是GW-IP为0且携带L3LE的RT-5路由。此外，PE节点从远端接收一条RT-5G路由会导致在IP-VRF实例的路由表中添加对应的路由条目，该RT-5G路由报文的GW-IP字段是其对应的路由条目的GW-IP字段。进一步地，IP-VRF实例中的有些路由条目的GW-IP字段并不是由RT-5G路由报文产生的，但与之具有相同的作用，此时也称为GW-IP字段。
EP可以是IRB或AC，EPL是可以同时标识某个EP的EVI标签，DAEPL是下游节点分配给上游节点的EPL，GEPL是在EP所在EVPN业务的所有PE节点上都能标识该EP的EPL。
本公开将MAC-VRF实例中的接入侧接口和IP-VRF实例中的接入侧接口统称为AC。
边界网关协议(Border Gateway Protocol，BGP)路由报文中的eRT用于在路由报文的接收方决定是否将其导入到某个IP-VRF实例或MAC-VRF实例。
BDI为BD实例的满足如下条件的标识符：若一个BD实例BD1桥接到IP-VRF实例VRF1，该VRF1可以分别与若干远端PE节点上的某个IP-VRF实例相通，这些IP-VRF实例(包括所述VRF1)中总共包含若干个BD实例，则属于同一广播域的所有BD实例具有相同的BDI，属于不同广播域的任意两个BD实例具有不同的BDI。
VE-ID为IP-VRF实例的满足如下条件的标识符：若某个IP-VRF实例VRF1可以分别与若干远端PE节点上的某个IP-VRF实例相通，则这些IP-VRF实例(包括所述VRF1实例)的VE-ID互不相同。
图2为本公开实施例提供的路由方法的流程示意图，如图2所示，所述路由方法包括步骤201和步骤202。
在步骤201中，第一PE设备接收第二PE设备发送的第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签。
所述第一路由报文是指路由协议报文，通常是BGP路由报文。 需要说明的是，当第二PE设备与第一PE设备之间存在更改下一跳的路由反射器(Route Reflector，RR)节点时，第一PE设备接收到的第一路由报文中的L2LA的值可能是经过RR修改后的值，此时，RR作为第二PE设备的代理节点，RR的存在不影响第一PE设备上的处理流程。
本公开实施例中，所述第二PE设备侧配置有第一MAC-VRF实例和第一IP-VRF实例，所述第一MAC-VRF实例和所述第一IP-VRF实例之间通过第一接口连接，所述第一MAC-VRF实例与第一AC连接；所述第一路由报文中携带的L3LE为所述第一IP-VRF实例的L3LE。
在步骤202中，所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加由所述第一路由报文中的L2LA所表示的L3LE。
上述步骤201和步骤202的方案是针对控制面的行为，上述控制面的行为决定了后续转发面的行为，通过本公开实施例的控制面的行为的实现可以在不修改转发指令的情况下自动获得新的转发面的行为。需要说明的是，本公开实施例的技术方案可以应用于VXLAN EVPN中，或MPLS EVPN中，或SRv6 EVPN中。进一步，在VXLAN EVPN中，所述L2LE和所述L3LE是VNI；或者在MPLS EVPN中，所述L2LE和所述L3LE是MPLS标签；或者在SRv6 EVPN中，所述L2LE和所述L3LE是SRv6 SID。
下面对第一EVPN路由条目的不同实现方式，以及基于该第一EVPN路由条目如何实现转发面的行为进行描述。
方式一：所述第一路由报文还携带所述第一接口的MAC，所述第一接口为IRB接口，所述第一PE设备基于所述第一路由报文生成第一EVPN路由条目，所述第一EVPN路由条目的EVI标签的值为所述第一路由报文中的L2LA的值，所述第一EVPN路由条目为MAC条目。
转发面的行为(参见应用示例1)包括：(1)所述第一PE设备接收第一以太报文，并基于所述第一EVPN路由条目确定所述第一以太报文的接收端为所述第二PE设备，以及基于所述第一以太报文生成待发送给所述第二PE设备的第一目标报文，所述第一目标报文携带所述EVI标签；所述第一以太报文承载了第一IP报文，所述第一 EVPN路由条目为MAC条目，所述MAC条目表示所述第一接口的MAC；(2)所述第一PE设备将所述第一目标报文发送给所述第二PE设备，所述第一目标报文在所述第二PE设备上通过所述EVI标签确定该EVI标签所属的IP-VRF实例，并在所述IP-VRF实例中查询IP路由表转发所述第一目标报文。
在一实施方式中，当所述L3LE为SRv6 SID(参见应用示例2)或MPLS标签(参见应用示例3)时，所述第一目标报文中包含所述第一以太报文的以太头。
在另一实施方式(参见应用示例8)中，当所述L3LE为SRv6 SID或MPLS标签时，所述第一目标报文中不包含所述第一以太报文的以太头，所述第一以太报文的以太头信息承载在所述第一目标报文的外层IP区域。这里，所述外层IP区域包括源IP区域和/或目的IP区域。
方式二：所述第一路由报文中还携带所述第一接口的IP和MAC之中的至少之一，所述第一接口为IRB接口。所述第一PE设备基于所述第一路由报文生成第一IP路由条目和第二IP路由条目，所述第一IP路由条目中的IP键值为所述第一路由报文中的所述第一接口的IP，GW-IP为包含所述第一路由报文中的所述第一接口的MAC地址和第一指定值的IP地址；所述第二IP路由条目的IP键值为所述第一IP路由条目的GW-IP，其自身的GW-IP为空，公网下一跳为所述第一路由报文的下一跳，EVI标签为所述第一路由报文中的L2LA的值。
第一种转发面的行为(参见应用示例4)包括：(1)所述第一PE设备接收第二IP报文，并基于所述第二IP路由条目获取所述EVI标签；(2)所述第一PE设备在所述第二IP报文的外层添加以太头和所述EVI标签，得到第二目标报文；(3)所述第一PE设备将所述第二目标报文发送给所述第二PE设备，所述第二目标报文在所述第二PE设备上基于所述EVI签进行转发。
需要说明的是，所述第二目标报文可以是MPLS报文，或者是SRv6报文，或者是VXLAN报文。所述第二IP路由条目基于所述第一IP路由条目获得。
在本公开实施例中，所述第一PE设备侧配置有第二MAC-VRF实例和第二IP-VRF实例，所述第二MAC-VRF实例和所述第二IP-VRF实例之间通过第二接口连接；进一步，所述第一PE设备将包含所述第二接口的MAC地址与第二指定值的IP地址作为第一主机路由条目添加到所述第二IP-VRF实例中，所述第二接口为IRB接口。相应地，有如下第二种转发面的行为。在一种实现方式中，所述第二指定值与前述的第一指定值相同。
第二种转发面的行为(参见应用示例5)包括：(1)所述第一PE设备接收第二以太报文，所述第二以太报文的目的MAC为所述第二接口的MAC；所述第二以太报文承载了第三IP报文；(2)所述第一PE设备根据包含所述第二以太报文的目的MAC与所述第二指定值的IP地址在所述第二IP-VRF实例中查询IP路由表，根据所述第一主机路由条目确定继续基于所述第三IP报文的目的IP查询IP路由表，以确定所述第三IP报文的接收端为所述第二PE设备；(3)所述第一PE设备基于所述第二IP路由条目获取所述EVI标签，并在所述第三IP报文的外层添加以太头和所述EVI标签，得到第三目标报文；(4)所述第一PE设备将所述第三目标报文发送给所述第二PE设备，所述第三目标报文在所述第二PE设备上基于所述EVI签进行转发。
进一步，所述第一PE设备将第二子网路由条目添加到所述第二IP-VRF实例中(参见应用示例5)，所述第二子网路由条目是一条主机部分与所述第一主机路由条目中所述第二接口的MAC所在的部分位置相同的路由，也就是说，所述第一主机路由条目能命中所述第二子网路由条目。基于此，所述第一PE设备根据包含所述第二以太报文的目的MAC与所述第二指定值的IP地址在所述第二IP-VRF实例中查询IP路由表，根据所述第二子网路由条目确定在所述第二以太报文所属的BD实例中广播所述第二以太报文。
需要说明的是，对于第一种转发面的行为，所述第二MAC-VRF实例是可选的，但所述第二IP-VRF实例对于两种转发面的行为都是必须的。
方式三：所述第一路由报文中的键值中包含GEPL，所述第一路由报文的L2LA为所述第一AC或所述第一接口对应的DAEPL，下一跳为所述第二PE设备的IP地址；所述GEPL为在所述第一IP-VRF实例所在的EVPN业务中唯一地标识所述第一AC或所述第一接口的标签。所述第一PE设备基于所述第一路由报文生成第三IP路由条目，所述第三IP路由条目中的IP键值为包含所述GEPL和第三指定值的IP地址，EVI标签为所述DAEPL，下一跳为所述第一路由报文的下一跳，GW-IP为空。
这里，在一实施例中，所述第一路由报文中还可以携带所述第三指定值，所述GEPL和第三指定值可以是同一字段的不同部分，也可以是不同字段。
需要说明的是，所述GEPL为在所述第一IP-VRF实例所在的EVPN业务中唯一地标识所述第一AC或所述第一接口的标签，是指：所述GEPL为在所述第一IP-VRF实例所在的EVPN业务的所有节点中唯一地标识所述第一AC或所述第一接口的标签。
进一步，第一PE设备接收所述第二PE设备发送的第四目标报文，所述第四目标报文是由所述第二PE设备对通过所述第一AC或所述第一接口接收到的第一报文进行封装处理得到的，所述第四目标报文携带所述第一AC对应的GEPL；所述第一PE设备基于所述第四目标报文生成第四IP路由条目，所述第四IP路由条目中IP键值为所述第一报文的源IP，GW-IP为包含所述第一报文中的GEPL和所述第三指定值的IP地址，标签为空；所述第一PE设备基于所述第四目标报文生成第五IP路由条目，所述第五IP路由条目中IP键值为包含所述第一报文的源MAC地址和所述第三指定值的IP地址，GW-IP为所述第三IP路由条目的IP键值，标签为空。
这里，所述第一报文可以是以太报文、或IP报文、或ARP报文。
在一实施方式(参见应用示例6)中，所述GEPL在数据报文中携带在EVPN标签和内层以太头之间。
在另一实施方式(参见应用示例7)中，所述GEPL的值或GEPL进行映射得到的IP地址在数据报文中携带在IP选项中。
第一种转发面的行为包括：(1)所述第一PE设备接收第三以太报文，所述第三以太报文的目的MAC为所述第五IP路由条目的IP键值中包含的MAC；(2)所述第一PE设备根据所述第五IP路由条目的GW-IP确定所述第三IP路由条目，并根据所述第三IP路由条目转发所述第三以太报文。
第二种转发面的行为包括：(1)所述第一PE设备接收第四IP报文，所述第四IP报文的目的IP为所述第四IP路由条目的IP键值；(2)所述第一PE设备根据所述第四IP路由条目的GW-IP确定所述第三IP路由条目，并根据所述第三IP路由条目转发所述第四IP报文。
本公开实施例的技术方案混合二三层VPN实现统一查表，克服了现有VPN技术中存在的IRB功能转发流程过长、性能较低的问题，实现了在硬件成本可控的情况下IRB功能与避免MAC地址过载两个目标同时达成，提升了VPN核心节点的路由表项资源的利用效率，避免了每个主机对于VPN核心节点的路由表项资源的消耗。
以下结合具体应用示例对本公开实施例的技术方案进行举例说明，需要说明的是，以下应用示例仅用于举例作用，并不限定本公开实施例的技术方案的范围。
为描述方便起见，以下应用示例中区分路由和路由条目两个概念，路由指路由报文，通常是BGP路由报文，路由条目指转发面的IP路由表或MAC地址表中的转发条目。以下应用示例中路由中的GW-IP概念与RT-5路由中的GW-IP概念具有相同的含义，路由条目的GW-IP概念与RT-5路由对应的路由条目中与RT-5路由的GW-IP对应的字段具有相同的含义。
以下应用示例中的应用示例1至应用示例3的组网图如图3所示，P1和P2代表两个运营商节点(Provider，P)，PE1和PE2代表两个运营商边缘(Provider Edge，PE)设备，CE1和CE2代表两个用户边缘(Customer Edge，CE)设备，VRF1是同一条EVPN业务在不同节点上的IP-VRF实例，BD1、BD2用于区分所述EVPN业务的不同子网在同一节点上对应的MAC-VRF实例，所述MAC-VRF实例同时也 是BD实例。图3所示的BD1在EVPN业务的不同PE设备上各有一个对应的BD实例，即PE1和PE2上各有一个BD1。所述PE设备在MPLS网络中称为PE节点，在VXLAN网络中也称为VTEP节点或NVE节点。在同一节点上，BD实例与IP-VRF实例之间以IRB接口(如图中虚线所示)相连接。所述BD实例的AC可以是物理接口上的一个子接口(如图中标注AC1、AC2、AC3或AC4的细实线所示)。P1和P2节点是下层(underlay)网络中的节点，在MPLS网络中就是P设备，在VXLAN或SRv6网络中就是IP转发设备。还有如下实体在图中没有画出：CE1上有两个三层接口IF1和IF4，分别与AC1和AC4连通，CE2上有两个三层接口IF2和IF3，分别与AC2和AC3连通，所述IF1、IF2、IF3、IF4的IP地址分别为H1、H2、H3、H4，MAC地址分别为M1、M2、M3、M4。为描述方便起见，将PE2上连接BD1实例和VRF1实例的IRB接口记为IRB1，将PE1上连接BD1实例和VRF1实例的IRB接口记为IRB2，将IRB1和IRB2的MAC地址分别记为Mb1和Mb2，将IRB1和IRB2的IP地址分别记为I1和I2，将标识PE1的可路由IP地址记为N1，将标识PE2的可路由IP地址记为N2。AC1和AC2均是BD1广播域中的接口，AC3是BD2广播域中的接口，AC4是VRF1实例中的三层接口。
以下应用示例中的应用示例4至应用示例6的组网图如图4所示，图4在图3的基础上增加了PE3和CE3，图4所示的PE3上的BD3实例与PE1上的BD3实例属于同一个广播域，AC5与CE3上的三层接口IF5连通。AC5是BD3实例中的接口，在PE1上BD3实例与VRF1实例通过IRB3接口相连。图4在应用示例6中作为其在非层次化EVPN网络架构上的组网图。
以下应用示例中的应用示例6在层次化EVPN网络架构下的组网图如图1所示。
应用示例1
在VXLAN EVPN中，L2 EVPN和L3 EVPN数据报文采用的封装格式都是一样的，都包括内层以太头。这种情况下，只需要在控制面进行扩展，就可以实现报文在PE1被二层转发到PE2并且在终结VXLAN封装后直接被三层转发。应用示例1包括如下流程(以从IF1接口到 IF3接口的通信为例进行说明)步骤(1)至步骤(4)。步骤(1)，PE2将其本地BD实例BD1对应的IRB接口(记为IRB1接口)对应的RT-2路由(即第2类EVPN路由)报文(记为X1)发布给PE1。所述X1中的L2LA的值不是填写L2LE(即BD1实例对应的L2VNI)的值而是填写L3LE(即IP-VRF实例对应的L3VNI)的值。
步骤(2)，PE1收到所述路由报文X1，将其加入到本地的BD1实例，形成所述BD1实例中的一条MAC条目(其MAC地址为Mb1)。所述Mb1条目中记录了所述L3VNI。
步骤(3)，PE1从本地AC1收到以太报文EP1，其源MAC为M1，其目的MAC为Mb1，其内层为IP报文为P1，对于P1，其源IP为H1，其目的IP为H3，并查MAC地址表来决定往远端PE2的发送；所述PE1在所述EP1外面添加VXLAN封装，成为报文USP1，其中所述VXLAN封装的源IP为N1，目的IP为N2；PE1将所述USP1报文发送给PE2。
步骤(4)，PE2收到所述USP1报文，得知其要进行VXLAN终结并且其VNI为L3VNI，将所述USP1报文所承载的IP报文(即P1)在所述L3VNI对应的IP-VRF实例中查路由表转发，最终经过BD2实例及其IRB接口从AC3转发到CE2的IF3接口。
步骤(3)对于控制面存在如下依赖关系：所述M1和H1分别是IF1的MAC地址和IP地址，所述Mb1是PE2上连接BD1实例和VRF1实例的IRB1接口的MAC地址，所述H3是IF3的IP地址，所述N1和N2分别是标识PE1和PE2的IP地址。
所述AC1绑定一个广播域(记为BD1)，所述MAC地址表为BD1对应的MAC地址表，所述N2记录在所述Mb1对应的MAC地址表项中，所述PE1通过接收所述路由报文X1获知所述Mb1与所述N2的对应关系。
步骤(4)对于控制面存在如下依赖关系：在PE2节点上，所述L3VNI绑定所述IP-VRF(图1中记为VRF1)，所述L2VNI绑定所述MAC-VRF(图1中记为BD1)。所述PE2在发布IRB接口对应的RT-2路由给PE1时，携带L3VNI而不是L2VNI，所述L3VNI就是该IRB接口所绑定的IP-VRF实例所绑定的L3VNI。
值得注意的是，步骤(3)中是查MAC地址表转发，而步骤(4)中则是查IP路由表转发，两者是完全不同的转发流程，而在一些情形下，如果在发送端是查MAC地址表转发，在接收端仍然要至少先通过目的MAC转发。此外，如果发送端是查IP路由表转发，到接收端仍然要先查IP路由表转发。
这样，当PE1从本地VRF1实例中的AC4收到一个内层IP包为P7的以太包(比如从IF4到IRB1通信的数据包)，并且查IP-VRF路由走EVPN对称转发流程转发P7到PE2上的同一个VRF1实例时，所述P7在PE2中的转发与所述P1在PE2中的转发都是根据L3VNI查同一张IP路由表，但是，在一些情形下，则是一个根据L3VNI查IP路由表，一个根据L2VNI走IRB流程。本公开统一了两种情况下的查表过程，因而可以删除根据L2VNI走IRB流程的转发指令，因此，可以减轻转发面的指令资源消耗，尤其在转发面采用ASIC芯片实现时，优势较为明显。
值得注意的是，虽然本示例是以从IF1到IF3的通信为例来说明本公开的技术方案的，但本示例中也是可以同时存在从IF1到IF2的通信的，这些通信依赖的仍然是在一些情形下定义的EVPN流程，本示例只是对于在一些情形下的EVPN流程进行了局部修改，仍然要在一些情形下的EVPN流程的基础上实施。
值得注意的是，PE2还可以将其在AC1上学到的MAC条目以RT-2路由的形式通告给PE1，PE1对于所述X1路由和这些路由，在将其导入到BD1实例中形成MAC条目时，可以采取相同的处理行为。
应用示例1是以VXLAN EVPN为例的，VXLAN EVPN的L2EVPN封装和L3EVPN封装具有相同的格式，因此，只需要扩展控制面就达到了减化转发面的目的。在SRv6 EVPN和MPLS EVPN中，L2EVPN封装和L3EVPN封装具有不同的格式，无法仅通过扩展控制面来实现同样的目的，因此，必须首先统一SRv6/MPLS EVPN在L2EVPN和L3EVPN中采用的封装格式，才能实现上述目的。这种统一，实际上就是去除SRv6/MPLS EVPN专门为L3EVPN定义的封装格式，在L3EVPN转发中，也采用与L2EVPN兼容的数据报文格式，下面以SRv6 EVPN为例，说 明如何进行上述改造。应用示例2包括如下流程(以从IF1接口到IF3接口的通信为例进行说明)步骤(1)至步骤(4)。
步骤(1)，PE2发布IRB1接口对应的RT-2路由报文(记为X1)给PE1。所述X1中的L2LA的值不是填写L2LE(即BD1实例对应的SRv6 SID)的值而是填写L3LE(即IP-VRF实例对应的SRv6 SID)的值。
步骤(2)，PE1收到所述路由报文X1，将其加入到本地的BD1实例，形成所述BD1实例中的一条MAC条目(其MAC地址为Mb1)。所述Mb1条目中记录了所述IP-VRF实例在PE2上对应的SRv6 SID。
步骤(3)，PE1从本地AC1收到以太报文EP2，其源MAC为M1，其目的MAC为Mb1，其内层为IP报文为P2，对于P2，其源IP为H1，其目的IP为H3，并查MAC地址表来决定往远端PE2的发送；所述PE1在所述EP2外面添加SRv6封装，成为报文USP2(如图5右侧所示)，其中所述SRv6封装的源IP为N1，目的IP为N2；PE1将所述USP2报文发送给PE2。
步骤(4)，PE2收到IP报文(比如所述USP2报文)，根据其目的IP(比如所述N2)查全局路由表得到其SID类型，并根据不同的SID类型进行不同的转发。所述SID类型至少包括End.DT46E、End.DT2U。所述End.DT46E的SID是本公开新定义的SRv6 SID，具体地，所述End.DT46E与End.DT46类型的SID具有相同的功能，除此之外还具有如下附加功能：其内层IP载荷对应的以太封装同样被作为End.DT46E的载荷的一部分。
若外层DIP是一个End.DT46E类型的SID(比如，对于从IF1到IF3的通信)，则先剥离其内层以太头再根据内层IP在对应的IP-VRF实例中查路由表转发；若外层DIP是一个End.DT2U类型的SID(比如，对于从IF1到IF2的通信)，则根据内层以太头在对应MAC-VRF实例中查MAC地址表转发。
步骤(1)对于控制面存在如下依赖关系：所述AC1绑定广播域BD1，所述MAC地址表为BD1对应的MAC地址表，所述N2记录在所述Mb1对应的MAC地址条目中，所述PE1通过接收所述路由报文X1获 知所述Mb1与所述N2的对应关系，所述N2承载在所述USP2的源IP中。
步骤(2)对于控制面存在如下依赖关系：在PE2节点上，所述End.DT46E类型的SID绑定所述IP-VRF(记为VRF1)，所述End.DT2U类型的SID绑定所述MAC-VRF。所述PE2在发布IRB接口对应的RT-2路由给PE1时，携带End.DT46E类型的SID而不是End.DT2U类型的SID，所述End.DT46E类型的SID就是该IRB接口所绑定的IP-VRF实例所绑定的End.DT46E类型的SID。
值得注意的是，在步骤(1)中是查MAC地址表转发，而在步骤(2)中则是查IP路由表转发，两者是完全不同的转发流程，而在一些情形下，如果在发送端是查MAC地址表转发，在接收端仍然要至少先通过目的MAC转发。此外，如果发送端是查IP路由表转发，到接收端仍然要先查IP路由表转发。
这样，现在End.DT46E类型的SID采用统一的封装同时完成了原来通过End.DT46和End.DT2U两种SID类型和两种报文封装格式才能完成的L3 EVPN转发情境和EVPN IRB转发情境，因而现在的End.DT2U类型的SID不再需要支持EVPN IRB转发流程。而且，现在的End.DT46E是通过统一的转发流程来完成所述L3 EVPN转发分工和所述EVPN IRB转发分工，因此，可以减轻转发面的指令资源消耗，尤其在转发面采用ASIC芯片实现时，优势较为明显。
值得注意的是，对于从IF1到IF3的通信，在PE2上的转发在在一些情形下是经过从MAC-VRF(即BD1)到IP-VRF再到MAC-VRF(即BD2)的过程，但在本示例中，只经过从IP-VRF到MAC-VRF的过程，因此转发性能也较高。
应用示例2是以SRv6 EVPN为例说明如何统一L2EVPN和L3EVPN中采用的封装格式，下面以MPLS EVPN为例，说明如何进行上述改造。应用示例3包括如下流程(以从IF1接口到IF3接口的通信为例)步骤(1)至步骤(4)。
步骤(1)，PE2发布IRB1对应的RT-2路由报文(记为X1)给PE1。所述X1中的L2LA的值不是填写L2LE(即BD1实例对应的MPLS 标签)的值而是填写L3LE(即IP-VRF实例对应的MPLS标签)的值。
步骤(2)，PE1收到所述路由报文X1，将其加入到本地的BD1实例，形成所述BD1实例中的一条MAC条目(其MAC地址为Mb1)。所述Mb1条目中记录了所述IP-VRF实例对应的MPLS标签。
步骤(3)，PE1从本地AC1收到以太报文EP3，其源MAC为M1，其目的MAC为Mb1，其内层为IP报文P3，对于所述P3，其源IP为H1，其目的IP为H3，并查MAC地址表决定往远端PE2发送；所述PE1给所述EP3添加EVPN封装，成为报文USP3(如图6右侧所示)。PE1将所述USP3报文发送给PE2。
步骤(4)，PE2收到所述USP3报文，根据其EVPN标签找到对应的IP-VRF，从所述USP3报文在所述EVPN标签内层承载的以太报文EP3中将所述P3报文提取出来，并以所述P3报文的目的IP(即H3)在该IP-VRF中查路由表根据路由表转发所述P3报文。
值得注意的是，在一些情形下，如果一个MPLS EVPN标签绑定的是一个IP-VRF实例，则该标签内层的IP报文是不带以太封装的，本处则需要包括以太封装，因为本处PE2从PE1通过L3EVI标签收到的报文，不一定是在PE1的L3 EVPN(IP-VRF)流程中转发过来的，也有可能是在PE1的L2 EVPN(MAC-VRF)流程中转发过来的(如步骤303所示)，为了同时处理这两种情况(比如从IF1到IRB1通信和从IF4到IRB1通信两种情况)，需要统一保留内层IP报文对应的以太封装。在步骤304中，PE2收到的USP3报文的栈底标签为L3EVI标签，但L3EVI标签内层却是一个以太报文。
步骤(3)对于控制面存在如下依赖关系：所述AC1绑定广播域BD1，所述MAC地址表为BD1对应的MAC地址表，所述EVPN封装信息记录在Mb1对应的MAC地址表项中，所述PE1通过接收PE2发来的所述路由报文X1获得所述EVPN封装信息。
步骤(4)对于控制面存在如下依赖关系：所述PE2在发布IRB接口对应的RT-2路由给PE1时，携带该IRB接口所绑定的IP-VRF的EVI标签而不是该IRB接口所绑定的MAC-VRF(即BD实例)的EVI标签。
值得注意的是，虽然本公开以一个MAC-VRF中只有一个BD的情况为例，但在MAC-VRF中有多个BD的情况下也是适用的，此时，本领域的普通技术人员知道如何在本公开提供的具体实施方式和应用示例的基础上进行相应调整。
在一些情形下，PE在IP-VRF实例中转发IP数据报文时可能经过“(IP-VRF)-IRB-(MAC-VRF)”这样一个转发流程，本应用示例将其缩短为只在IP-VRF中通过路由迭代就可以完成整个转发过程。需要说明的是，应用示例4是以应用示例3为基础进行举例说明，不局限于此，应用示例4还可以以应用示例1或应用示例2为基础。应用示例4包括如下流程(以从IF4接口到IRB1接口的通信为例进行说明)步骤(1)至步骤(4)。
步骤(1)，PE2发布IRB1接口对应的RT-2路由报文(记为X1)给PE1。所述X1中的L2LA的值不是填写L2LE(即BD1实例对应的MPLS标签)的值而是填写L3LE(即VRF1实例对应的MPLS标签)的值(记为Lx1)。
步骤(2)，PE1收到所述路由报文X1，将其加入到本地的BD1实例，形成所述BD1实例中的一条MAC条目(其MAC地址为Mb1)。所述Mb1条目中记录了所述IP-VRF实例对应的MPLS标签。进一步，PE1收到所述路由条目X1，将其加入到本地的VRF1实例，形成所述VRF1实例中的两条明细路由条目，分别记为RE4a和RE4b，RE4a条目的IP键值为所述X1的键值中的IP(即I1)，GW-IP为所述X1的键值中的MAC(即Mb1)对应的MAC映射地址；RE4b条目的IP键值为所述MAC映射地址，GW-IP为空，公网下一跳为所述X1的下一跳(即N2)，EVPN出标签为所述X1中的L2LA表示的标签。
步骤(3)，PE1收到一个需要在VRF1实例中转发的IP报文(比如从IF4到IRB1通信的IP报文)，其源IP为H4，目的IP为I1，所述PE1只通过在所述IP-VRF实例中的所述RE4a和所述RE4b就得到了所述Lx1的值，而不需要在所述BD1实例中获取所述Lx1的值；所述PE1在所述IP报文外面添加以太头以及值为Lx1的标签，成为MPLS报文USP4，并通过MPLS隧道将所述MPLS报文USP4发送给PE2。 所述USP4在添加MPLS隧道封装后的格式如图7所示，GEPL在本具体实施方式中空缺。
步骤(4)，PE2收到所述USP4报文，根据其EVPN标签找到所述VRF1实例，从所述USP4报文内层承载的IP报文的目的IP(即I1)找到所述IRB1接口。
步骤(3)对于控制面存在如下依赖关系：PE1从PE2收到所述路由X1，所述路由X1的类型为RT-2路由，所述路由X1的键值中的IP为I1，键值中的MAC为Mb1，其BGP下一跳为N2，其MPLS Label1字段的值为Lx1，所述Mb1对应的MAC映射地址为IPm1，所述MAC映射地址由第一指定前缀、BDI和MAC地址组成(如图8所示)，所述第一指定前缀为8字节指定值，低6字节为所述Mb1地址，所述BDI为标识所述Mb1地址所属的BD实例的BDI，通过将第一指定前缀选取为特殊的值，可以保证MAC映射地址与所述IP-VRF实例中的主机IP地址不会相冲突。
于是，PE1将从PE2收到所述X1映射为从PE2收到如下两条RT-5明细路由Y1和Y2：所述Y1是一条明细RT-5路由，其键值中的IP为所述I1，其GW IP为IPm1，其标签值为空；所述Y2是一条明细RT-5路由，其键值中的IP为IPm1，其EVPN标签为所述Lx1，其路由器的MAC为Mb1，其BGP下一跳为N2，其GW IP为0。
经过映射过后，所述Y1在VRF1实例的路由表中形成路由条目RE4a，所述Y2在路由表中形成路由条目RE4b，于是，在一些情形下，在查询IRB1接口上的ARP得到远端MAC然后在IRB1所述的BD1中查MAC地址表的行为，就可以用在VRF1实例中从RE4a到RE4b的路由迭代的过程来取代。由于查IP路由表对于EVPN三层转发本来就是必须的，这里实际上没有增加查表次数，反而去掉了原来查ARP表和MAC地址表的流程。
值得注意的是，BD对应的RT-3路由也可以改为在该BD绑定的IRB接口所绑定的IP-VRF实例中发布，RD填IP-VRF的RD，Ethernet Tag ID填BDI，eRT填IP-VRF实例的eRT，标签填本节点为该BD分配的标签，称为该BD实例的BD标签，所述BD标签同时标识所述 IP-VRF实例和所述BD实例。
在应用示例4中，BD1中的MAC条目和VRF1中的由BD1中的MAC映射地址形成的IP路由条目是同源的，因而是重复的信息，应用示例5在应用示例4的基础上将前者进一步统一到后者中，从而减少了重复信息。应用示例5包括如下流程(以从IF1接口到IRB1接口的通信为例进行说明)步骤(1)至步骤(5)。
步骤(1)，PE2发布IRB1接口对应的RT-2路由条目(记为X1)给PE1。所述X1中的L2LA的值不是填写L2LE(即BD1实例对应的MPLS标签)的值而是填写L3LE(即IP-VRF实例对应的MPLS标签)的值(记为Lx2)。
步骤(2)，PE1收到所述路由条目X1，将其加入到本地的VRF1实例，形成所述VRF1实例中的两条明细路由条目，分别记为RE5a和RE5b，RE5a条目的IP键值为所述X1的键值中的IP(即所述I1)，GW-IP为所述X1的键值中的MAC(即所述Mb1)对应的MAC映射地址；RE5b条目的IP键值为所述RE5a条目的GW-IP，GW-IP为空，公网下一跳为所述X1的下一跳，EVPN出标签为所述X1中的L2LA字段。
步骤(3)，PE1本地IRB2接口的MAC地址Mb2的MAC映射地址为IPm2，IRB2所属的IP-VRF实例为VRF1，所述PE1将所述IPm2作为128位路由添加到所述VRF1实例中。
步骤(4)，PE1在BD1实例中的AC1收到一个以太报文EDP5，所述PE1以所述EDP5的目的MAC对应的MAC映射地址查VRF1的路由表(对于从IF1接口到IRB1接口的通信来说，所述EDP5的源MAC为M1，其目的MAC为所述Mb2，其内层IP报文为P8，对于P8，其源IP为H1，其目的IP为I1)命中所述IPm2路由条目，得知IPm2是IRB映射地址，于是以所述P8报文的目的IP(即所述I1)查VRF路由表，根据所述RE5a和RE5b路由按如下方法将报文转发给PE2：所述PE1只通过在所述IP-VRF实例中的所述RE5a和所述RE5b就得到了所述PE2在所述X1路由中发布的MPLS Label1字段的值Lx2；所述PE1在所述IP报文外面添加以太头以及值为Lx2的标签，成为MPLS报文USP5，并通过MPLS隧道将所述MPLS报文USP5发送给PE2。所 述USP5在添加MPLS隧道封装后的格式如图7所示，GEPL在本具体实施方式中空缺。
步骤(5)，PE2收到所述USP5报文，根据其EVPN标签找到对应的IP-VRF(即VRF1)，从所述USP5报文承载的以太报文中将所述P8报文提取出来，并以所述P8报文的目的IP(即I1)确定其所属的IRB接口(即IRB1)，并在该IRB接口上继续处理所述P8报文。
在上述步骤的基础上，PE1就可以将BD1中从本地AC学习到的MAC条目也以MAC映射地址的形式添加到VRF1中，同时去除BD1中的MAC条目。值得注意的是，这时，对于从IF1到IF2的通信来说，也要走按目的MAC的MAC映射地址查IP-VRF路由表的流程。
值得注意的是，所有MAC映射地址的高64位均为第一指定值，可以在IP-VRF实例生成一条高64位为第一指定值的64位IPv6路由，这条路由称为BUM路由，当以MAC映射地址查IP路由表命中BUM路由时，表示要在该报文所属BD实例中广播。通过添加BUM路由，达到了两个目的，第一是通过MAC映射地址查IP路由表不会命中缺省路由，这保证了缺省路由仍然只作用于三层转发；第二是通过MAC映射地址查IP路由表不可能不命中任何路由，因为BUM路由总是符合命中条件的。在一实施例中，BUM路由也可以每个BD实例各有一条，它们之间只有BDI字段的值不同。
值得注意的是，通过去除BD1中的MAC条目，本示例达到了剪除重复信息的效果，同时统一了二层转发和三层转发所查的路由表，使得BD1实例退化为一个没有MAC条目的实例(进一步地，本领域的普通技术人员，还可以把RT-3路由也移到VRF1实例，使得BD1实例进一步退化为一个没有转发条目的概念性实体，不再是一个MAC-VRF实例)，其作为转发实例的职能被VRF1实例所取代。
值得注意的是，本公开把由IRB接口的MAC地址映射成的IP地址称为IRB映射地址，可以通过将本地IRB接口的IRB映射地址形成的IPv6路由条目的下一跳地址设置为特殊值来与其它IPv6路由条目相互区分，从而采取与其它IPv6路由条目不同的转发行为。
在应用示例5中，主机MAC地址需要向远端PE节点发布，这意 味着如果PE1和PE2之间存在SPE节点，SPE节点上要存储所有主机的MAC地址信息，形成MAC地址过载的情况，为了避免这些情况发生，可以采取不通过路由发布主机MAC地址的办法，这意味着需要进行MAC地址学习，但是在MPLS封装上进行MAC地址学习存在一定困难，应用示例6在应用示例5的基础上，克服这些困难并采用在数据面进行MAC地址学习的方式来解决MAC地址过载的问题。应用示例6包括如下流程步骤(1)至步骤(8)。
步骤(1)，PE2在VRF1实例中为所述IRB1接口分配的MPLS-based方式的L3 EVPN标签为DAEPL5，所述DAEPL5对应的GEPL为GEPL5，则PE2对PE1发布所述IRB1对应的GEPL路由，其中所述GEPL路由可以是一条明细RT-2路由，所述RT-2路由的键值中的IP地址为所述GEPL5对应的GEPL映射地址，其键值中的MAC地址为0，其路由区分符RD为所述VRF1实例的RD，其L2LA属性为所述DAEPL5标签，其下一跳为PE2的节点IP地址(即N2)。
步骤(2)，PE2上BD1实例绑定AC2接口，BD1实例中为所述AC2接口分配的MPLS-based方式的L3 EVPN标签为DAEPL6，所述DAEPL6对应的GEPL为GEPL6，则PE2对PE1发布所述AC1对应的GEPL路由，其中所述GEPL路由可以是一条明细RT-2路由，所述RT-2路由的键值中的IP地址为所述GEPL6对应的GEPL映射地址，其键值中的MAC地址为0，其RD为所述VRF1实例的RD，其L2LA属性为所述DAEPL6标签，其下一跳为PE2的节点IP地址(即N2)。
需要说明的是，上述步骤(1)和步骤(2)是独立的，以下步骤(3)可以继承在步骤(1)之后或者继承在步骤(2)之后。
步骤(3)，PE1收到步骤(1)或步骤(2)中所述的GEPL路由，将其加入到本地的VRF1实例，分别形成所述VRF1实例中的路由条目RE6a和RE6b，RE6a和RE6b条目的IP键值均为相应GEPL路由的键值中的IP，GW-IP为空，公网下一跳为相应GEPL路由的下一跳，EVPN出标签为相应GEPL路由的L2LA属性的值。
步骤(4)，当PE2从本地AC2收到报文EDP6或者当PE2从VRF1实例中从IRB1接口发送IP报文IDP7并将所述IDP7封装为以太报文 EDP7时，PE2在将所述EDP6或所述IDP7发给PE1时，首先将其封装为报文MEDP5，所述MEDP5中包括所述AC2或IRB1对应的GEPL(即所述GEPL5或GEPL6)，为描述方便起见，所述EDP6或IDP7在所述MEDP5中的源MAC记为Mx，源IP记为IPx，所述GEPL记为GEPLx。
步骤(5)，当PE1从PE2收到所述MEDP5并发现其携带了GEPL时，所述PE1如同收到两条如下形式的RT-5G路由(记为G6a和G6b)：所述G6a的键值中的IP为所述IPx，GW-IP为所述GEPLx的GEPL映射地址，标签为空；所述G6b的键值中的IP为所述Mx的MAC映射地址，GW-IP为所述GEPLx的GEPL映射地址，标签为空。
步骤(6)，当PE1从本地AC1收到以太报文EDP8，其目的MAC为所述G6b的键值中的MAC(即Mx)，所述PE1根据所述G6b的GW-IP确定对应的RE6a或RE6b，并根据所述RE6a或RE6b封装和转发所述EDP8报文。
步骤(7)，当PE1在AC4接口上收到IP报文IDP8，其目的IP为所述G6a的键值中的IP(即IPx)，所述PE1根据所述G6a的GW-IP确定对应的RE6a或RE6b，并根据所述RE6a或RE6b封装和转发所述IDP8报文。封装所述IDP8报文包括为其添加以太头。
步骤(8)，PE2收到所述EDP8或IDP8报文，根据其EVPN标签找到对应的IRB接口或AC接口，然后在IRB接口所属的IP-VRF实例中转发，或者将报文从AC接口转发出去。根据所述DAEPL5标签(即所述RE6a中的标签)可以找到IRB1接口，根据所述DAEPL6标签(即所述RE6b中的标签)可以找到AC2接口。
除特殊说明之处以外，应用示例6与应用示例4对于控制面存在的依赖关系相同。
与应用示例4不同，应用示例6不采用EVPN路由发布主机MAC地址，但仍然采用与应用示例4中步骤(1)类似的EVPN路由发布IRB/AC接口对应的L3LE。
与应用示例4不同，应用示例6从由远端MAC地址映射得到的IP路由条目(比如所述G6b)中，能够获得如下信息：其GW-IP地址为该MAC地址对应的全局EP标签映射地址(其一种可能格式如图9 所示)，该MAC地址所属的BD实例的BDI，该MAC地址所属BD所绑定的IRB接口的MAC地址。
所述EP标签映射地址为由GEPL映射而成的地址，具体地，所述EP标签映射地址为由GEPL和第二指定前缀映射而成的IP地址。所述GEPL是由虚拟路由转发边缘标识符VE-ID与DAEPL映射而成的标签，其格式如图10所示。
所述VE-ID是IP-VRF实例所在PE节点在该IP-VRF业务的所有节点上唯一的标识符，所述DAEPL是由AC/IRB所在PE节点在每平台标签空间中分配的标识该AC/IRB的本地唯一标签。所述AC为将所述MAC映射地址对应的MAC地址作为本地MAC条目学到时的报文入接口。
除VE-ID和DAEPL之外，在一实施例中，GEPL中还可以包括4字节的版本号，本实施例中版本号取值为第八指定值。除Ver可选之外，VE-ID和DAEPL还可以压缩，以使两者位宽之和不超过20位，此时，DAEPL只能使用每平台标签池中的一段区间。
值得注意的是，为了将DAEPL映射为GEPL，需要给每个IP-VRF实例事先配置一个VE-ID，方法是，同一VPN中的所有(分别位于不同PE节点)IP-VRF实例必须配置不同的VE-ID。
值得注意的是，所述入口GEPL只用于MAC/ARP条目的数据面学习，不用于转发当前的数据报文，而且，它是在出口EP标签内层的，因此，它可以不是一个标准的MPLS标签，比如，它可以是一种新的控制字。当然，在VE-ID与DAEPL两个字段的位宽之和不超过20位的情况下，它也可以是一层MPLS标签。或者，也可以将VE-ID和DAEPL分别作为一层MPLS标签。此时，可以让VE-ID对应的标签在外，DAEPL的标签在内，此时，VE-ID和DAEPL对于其外层的出口EP标签的出口(Egress)节点来说其实就是一种上游分配标签，而所述出口EP标签就是它们的上下文标签，VE-ID对应的标签是在一种新的上下文标签空间中的标签，这种标签空间是与每个VPN对应的，可以称为每VPN标签空间。
值得注意的是，GEPL本身不一定要DAEPL作为它的组成部分，由DAEPL构建GEPL是本示例的一种特殊方法，不用于限定GEPL的格 式，只要符合本公开中定义的GEPL概念，均可以作为GEPL的具体格式。
值得注意的是，EVPN技术可以提供L2VPN业务和L3VPN业务，当其提供L2VPN业务时，由于L2VPN业务的MAC地址路由条目(以下简称为MAC条目)对应于主机的MAC地址，而MAC地址是不具备汇聚性的，因此，MAC条目的数量与主机数量成正比，这会造成VPN核心节点MAC地址路由过载。如图1所示，SPE设备是指接入UPE并位于网络内部的设备，称为上层PE(Superstratum PE)设备或运营商侧PE(Service Provider-end PE)设备，SPE设备主要完成VPN路由的管理和发布。UPE设备是指直接连接用户的设备，称为下层PE(Underlayer PE)设备或用户侧PE(User-end PE)设备，UPE设备主要完成用户接入功能。图1是以两个SPE设备(分别为SPE1和SPE2)和两个UPE设备(分别为UPE1和UPE2)为例，在SPE1和SPE2上需要存储所有主机的MAC条目，主机数量过多时，会导致MAC条目过载。PBB EVPN不需要对VPN核心节点发布主机的MAC地址，只需要发布与ESI或PE设备对应的B-MAC地址，从而解决了MAC条目过载的问题。但是，PBB EVPN只能单独作为纯L2VPN使用，而无法与L3VPN组合用于IRB场景，原因在于其协议栈过于复杂，转发流程过长，查表次数过多，无法高效率地实现，业界目前的ASIC芯片基本都不支持，微码实现也基本上需要以牺牲1/2甚至3/4的吞吐量的代价才能实现。也就是说，IRB功能和避免MAC地址过载，两者是难以同时实现的。为了克服VPN技术中存在的转发流程过长、性能较低的问题，提出了本公开实施例与本应用示例对应的技术方案。值得注意的是，该技术方案尤其对于在一些情形下从IF5到IF2的通信在PE1上的转发流程(其特点是经过从MAC-VRF到IP-VRF再到MAC-VRF)，实现了大幅度的简化，即使叠加避免MAC地址过载的功能(如本应用示例所示)，简化后的转发流程仍然可以只在VRF1实例中完成，因为BD1和BD2中的转发表项都已经合并到了VRF1实例中。
值得注意的是，应用示例5中的步骤(3)中的内容也可以与本示例相叠加，此时，对于从IF1到IF5的通信来说，从AC1将收到目 的MAC为Mb2的以太报文，该以太报文将按照应用示例5中的步骤(4)中的方法来转发。
值得注意的是，当二层AC具有ESI属性时，同一ESI在同一L2EVI的不同PE设备上的相互对应的二层AC对应的GEPL标签还需要保证一致性，本领域的普通技术人员应当知道如何保证这种一致性，比如，可以采用静态配置的方式。此时，所述GEPL标签还可以用于ESI过滤(破除同一ES内跨PE设备形成的环路)。
除特殊说明之处以外，应用示例7与应用示例6完全相同。
与应用示例6不同，应用示例7不在EVPN标签和内层以太头之间携带GEPL，而是直接在IP选项中携带GEPL的值或GEPL映射地址。除了GEPL在数据报文封装中所处的位置之外，应用示例7的控制面以及转发流程与具体应用示例6完全相同。
除特殊说明之处以外，应用示例8与应用示例2完全相同。
与应用示例2不同，应用示例8不携带内层以太头，取而代之的是，将原始以太头信息内置在外层源IP和目的IP的低64位，此时，本公开将外层源IP或外层目的IP的低64位称为ARG.ETH，所述ARG.ETH的位置如图11所示。比如，可以将源MAC和Ethertype信息内置在外层源IP的低64位，将目的MAC和VLAN信息内置在外层源IP的低64位。
除了存取SMAC/DMAC和VLAN、Ethertype信息并据以恢复出内层以太头之外，应用示例8的控制面以及转发流程与应用示例2完全相同。
应用示例9可以在应用示例1、应用示例2、应用示例3中任何一个应用示例的基础上进行修改得到，当选择其中一种应用示例(记为基础应用示例)作为基础时，除特殊说明之处以外，应用示例9与基础应用示例完全相同。
以图12所示数据中心集中式网关组网中的数据中心网关(DGW，Data Center Gateway)为例，三种基础应用示例的共同点是在DGW节点上都存在广播域BD实例(即MAC-VRF实例)。所述DGW节点可以由基础应用示例中的PE1修改得到。
与基础实施例不同，应用示例9在数据中心集中式网关组网中的DGW节点上，如图13所示，应用示例9不部署BD实例(需要首先参考应用示例9中使BD实例退化为概念性实体的方法进行改造)，只部署IRB接口作为集中式网关接口，该IRB接口的MAC地址通过RT-2路由发布给VTEP节点。
去掉BD实例后，在发布IRB接口的MAC的RT-2路由时，直接携带IP-VRF的标签作为RT-2路由的Label1字段(VXLAN和MPLS封装)或取代Label1字段功能的SRv6 SID。所述IP-VRF的标签可以是VNI标签、MPLS标签和SRv6 SID。
为实现上述路由方法，本公开实施例还提供了一种路由设备，如图14所示，所述路由设备包括接收单元1401、生成单元1402和路由单元1403。
接收单元1401用于接收第二PE设备发送的第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签。
生成单元1402用于基于所述第一路由报文生成第一EVPN路由条目，所述第一EVPN路由条目的EVI标签的值为所述第一路由报文中的L2LA的值。
进一步，所述路由设备还包括：路由单元1403，用于接收第一以太报文，并基于所述第一EVPN路由条目确定所述第一以太报文的接收端为所述第二PE设备，以及基于所述第一以太报文生成待发送给所述第二PE设备的第一目标报文，所述第一目标报文携带所述EVI标签；所述第一以太报文承载了第一IP报文，所述第一EVPN路由条目为MAC条目；将所述第一目标报文发送给所述第二PE设备，所述第一目标报文在所述第二PE设备上通过所述EVI标签确定该EVI标签所属的IP-VRF实例，并在所述IP-VRF实例中查询IP路由表转发所述第一目标报文。
本领域技术人员应当理解，图14所示的路由设备中的各单元的实现功能可参照前述路由方法的相关描述而理解。图14所示的路由 设备中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
图15为本公开实施例提供的路由方法的流程示意图，如图15所示，所述路由方法包括步骤1501。
在步骤1501，第二PE设备向第一PE设备发送第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；所述第一路由报文用于所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加所述第一路由报文中的L2LA所表示的L3LE。
上述步骤1501的方案是针对控制面的行为，上述控制面的行为决定了后续转发面的行为，通过本公开实施例的控制面的行为的实现可以在不修改转发指令的情况下自动获得新的转发面的行为。需要说明的是，本公开实施例的技术方案可以应用于VXLAN EVPN中，或MPLS EVPN中，或SRv6 EVPN中。进一步，在VXLAN EVPN中，所述L2LE和所述L3LE是VNI；或者，在MPLS EVPN中，所述L2LE和所述L3LE是MPLS标签；或者，在SRv6 EVPN中，所述L2LE和所述L3LE是SRv6 SID。
本公开实施例中，当所述L3LE为SRv6 SID或MPLS标签时，所述第二PE设备接收所述第一PE设备发送的携带所述L3LE的数据报文，所述第二PE设备确定所述数据报文在所述L3LE以内包含以太头。这里，所述数据报文指所述第一PE设备发来的包含该L3LE的所有目标报文。
本公开实施例中，所述第二PE设备侧配置有第一MAC-VRF实例和第一IP-VRF实例，所述第一MAC-VRF实例和所述第一IP-VRF实例之间通过第一接口连接，所述第一MAC-VRF实例与第一AC连接；所述第一路由报文中携带的L3LE为所述第一IP-VRF实例的L3LE。
进一步，在一实施方式中，所述第一路由报文中还携带所述第一接口的IP和MAC之中的至少之一，所述第一接口为IRB接口。
进一步，在另一实施方式中，所述第一路由报文中的键值中包 含GEPL，所述第一路由报文的L2LA为所述第一AC或所述第一接口对应的DAEPL，下一跳为所述第二PE设备的IP地址；所述GEPL为在所述第一IP-VRF实例所在的EVPN业务中唯一标识所述第一AC或所述第一接口的数值。
基于此，所述第二PE设备从所述第一AC或所述第一接口接收待转发给所述第一PE设备的第一报文；所述第二PE设备在所述第一报文外层添加所述GEPL，得到第四目标报文，将所述第四目标报文发送给所述第一PE设备；对于所述第二PE设备从所述第一接口接收所述第一报文的情况，所述第一报文是从所述第一接口所属的IP-VRF实例中发往所述第一接口。
需要说明的是，上述图15中的技术方案是从第二PE设备侧来描述的，第一PE设备侧的行为可以参照图2中的技术方案来理解，此处不再赘述。
为实现上述路由方法，本公开实施例还提供了一种路由设备，如图16所示，所述路由设备包括发送单元1601。
发送单元1601，用于向第一PE设备发送第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；所述第一路由报文用于所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加所述第一路由报文中的L2LA所表示的L3LE。
本领域技术人员应当理解，图16所示的路由设备中的各单元的实现功能可参照前述路由方法的相关描述而理解。图16所示的路由设备中的各单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
图17是本公开实施例提供的另一种路由设备的结构图。图17所示的路由设备1700包括处理器1710，处理器1710可以从存储器中调用并运行计算机程序，以实现本公开实施例中的方法。
在一实施例中，如图17所示，路由设备1700还可以包括存储器1720。处理器1710可以从存储器1720中调用并运行计算机程序， 以实现本公开实施例中的方法。
存储器1720可以是独立于处理器1710的一个单独的器件，也可以集成在处理器1710中。
在一实施例中，如图17所示，路由设备1700还可以包括收发器1730，处理器1710可以控制该收发器1730与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
收发器1730可以包括发射机和接收机。收发器1730还可以进一步包括天线，天线的数量可以为一个或多个。
本公开实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本公开实施例中的网络设备，并且该计算机程序使得计算机执行本公开实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
在一实施例中，该计算机可读存储介质可应用于本公开实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本公开实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本公开实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本公开实施例中的网络设备，并且该计算机程序指令使得计算机执行本公开实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
在一实施例中，该计算机程序产品可应用于本公开实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本公开实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本公开实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本公开实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本公开实施例的 各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
在一实施例中，该计算机程序可应用于本公开实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本公开实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
在本公开实施例的技术方案中，第一PE设备接收第二PE设备发送的第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性；所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；所述第一PE设备基于所述第一路由报文生成第一EVPN路由条目，所述第一EVPN路由条目的EVI标签的值为所述第一路由报文中的L2LA的值。如此，可以实现将远端MAC-VRF中发来的目的MAC为本端IRB接口的MAC的EVPN IRB报文在不经过MAC-VRF实例转发的情况下就直接进入IP-VRF实例转发，从而简化了EVPN IRB业务的转发流程，尤其是在原来需要经过两次MAC-VRF实例转发的EVPN IRB转发情况下，通过实施本公开的技术方案，最多只需要经过一次MAC-VRF实例转发。
同时，通过实施本公开的技术方案，可以删除从L2EVPN标签(包括MPLS标签、VNI和SID)进入MAC-VRF实例再进入IP-VRF实例这套转发指令序列，从而进一步减少了转发面的实现成本。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的几个实施例中，应该理解到，所揭露的系统、 装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应所述以权利要求的保护范围为准。

Claims (19)

  1. 一种路由方法，包括：
    第一运营商边缘PE设备接收第二PE设备发送的第一路由报文，所述第一路由报文的二层标签属性L2LA中携带三层标签实体L3LE的值，所述L2LA是在以太虚拟专用网EVPN路由中用于携带二层标签实体L2LE的值的路由属性，
    其中，所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签，所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加由所述第一路由报文中的L2LA所表示的L3LE。
  2. 根据权利要求1所述的方法，还包括：
    所述第一PE设备基于所述第一路由报文生成第一IP路由条目和第二IP路由条目，
    其中，所述第一IP路由条目中的IP键值为所述第一路由报文中的第一接口的IP，GW-IP为包含所述第一路由报文中的第一接口的MAC地址和第一指定值的IP地址；所述第二IP路由条目的IP键值为所述第一IP路由条目的GW-IP，其自身的GW-IP为空，公网下一跳为所述第一路由报文的下一跳，EVI标签为所述第一路由报文中的L2LA的值。
  3. 根据权利要求2所述的方法，其中，所述第一PE设备侧配置有第二MAC-VRF实例和第二IP-VRF实例，所述第二MAC-VRF实例和所述第二IP-VRF实例之间通过第二接口连接，所述方法还包括：
    所述第一PE设备将包含所述第二接口的MAC地址与第二指定值的IP地址作为第一主机路由条目添加到所述第二IP-VRF实例中，
    其中，所述第二接口为IRB接口。
  4. 根据权利要求3所述的方法，还包括：
    所述第一PE设备将第二子网路由条目添加到所述第二IP-VRF实例中，
    其中，所述第二子网路由条目是一条主机部分与所述第一主机路由条目中所述第二接口的MAC所在的部分位置相同的路由。
  5. 根据权利要求1所述的方法，其中，所述第一路由报文中的键值中包含全局端点标签GEPL，所述第一路由报文的L2LA为第一接入电路AC或第一接口对应的下游分配端点标签DAEPL，下一跳为所述第二PE设备的IP地址，所述GEPL为在第一IP-VRF实例所在的EVPN业务中唯一标识第一AC或第一接口的标签，
    并且其中，所述第一PE设备根据所述第一路由报文生成第三IP路由条目，所述第三IP路由条目中的IP键值为包含所述GEPL和第三指定值的IP地址，EVI标签为所述DAEPL，下一跳为所述第一路由报文的下一跳，GW-IP为空。
  6. 根据权利要求5所述的方法，还包括：
    第一PE设备接收所述第二PE设备发送的第四目标报文，所述第四目标报文是所述第二PE设备对通过所述第一AC或所述第一接口接收到的第一报文进行封装处理得到，所述第四目标报文携带所述第一AC对应的GEPL；
    所述第一PE设备基于所述第四目标报文生成第四IP路由条目，所述第四IP路由条目中IP键值为所述第一报文的源IP，GW-IP为包含所述第一报文中的GEPL和所述第三指定值的IP地址，标签为空；以及
    所述第一PE设备基于所述第四目标报文生成第五IP路由条目，所述第五IP路由条目中IP键值为包含所述第一报文的源MAC地址和所述第三指定值的IP地址，GW-IP为所述第三IP路由条目的IP键值，标签为空。
  7. 一种路由方法，包括：
    第二PE设备向第一PE设备发送第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性，
    其中，所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签，所述第一路由报文用于所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加所述第一路由报文中的L2LA所表示的L3LE。
  8. 根据权利要求7所述的方法，其中，
    在VXLAN EVPN中，所述L2LE和所述L3LE是VNI；或者
    在MPLS EVPN中，所述L2LE和所述L3LE是MPLS标签；或者
    在SRv6EVPN中，所述L2LE和所述L3LE是SRv6SID。
  9. 根据权利要求7所述的方法，其中，当所述L3LE为SRv6SID或MPLS标签时，所述第二PE设备接收所述第一PE设备发送的携带所述L3LE的数据报文，所述第二PE设备确定所述数据报文在所述L3LE以内包含以太头。
  10. 根据权利要求7至9中任一项所述的方法，其中，所述第二PE设备侧配置有第一MAC-VRF实例和第一IP-VRF实例，所述第一MAC-VRF实例和所述第一IP-VRF实例之间通过第一接口连接，所述第一MAC-VRF实例与第一AC连接，所述第一路由报文中携带的L3LE为所述第一IP-VRF实例的L3LE。
  11. 根据权利要求10所述的方法，其中，所述第一路由报文中还携带所述第一接口的IP和MAC之中的至少之一，所述第一接口为IRB接口。
  12. 根据权利要求10所述的方法，其中，所述第一路由报文中的键值中包含GEPL，所述第一路由报文的L2LA为所述第一AC或所 述第一接口对应的DAEPL，下一跳为所述第二PE设备的IP地址，所述GEPL为在所述第一IP-VRF实例所在的EVPN业务中唯一标识所述第一AC或所述第一接口的数值。
  13. 根据权利要求12所述的方法，还包括：
    所述第二PE设备从所述第一AC或所述第一接口接收待转发给所述第一PE设备的第一报文；以及
    所述第二PE设备在所述第一报文外层添加所述GEPL，得到第四目标报文，将所述第四目标报文发送给所述第一PE设备，
    其中，对于所述第二PE从所述第一接口接收所述第一报文的情况，所述第一报文是从所述第一接口所属的IP-VRF实例中发往所述第一接口。
  14. 一种路由设备，包括：
    接收单元，用于接收第二PE设备发送的第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性，所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签；以及
    生成单元，用于基于所述第一路由报文生成第一EVPN路由条目，所述第一EVPN路由条目的EVI标签的值为所述第一路由报文中的L2LA的值。
  15. 一种路由设备，包括：
    发送单元，用于向第一PE设备发送第一路由报文，所述第一路由报文的L2LA中携带L3LE的值，所述L2LA是在EVPN路由中用于携带L2LE的值的路由属性，所述L2LE是MAC-VRF实例对应的EVPN本地标签，所述L3LE是IP-VRF实例对应的EVPN本地标签，所述第一路由报文用于所述第一PE设备在向所述第二PE设备转发的EVPN数据报文中添加所述第一路由报文中的L2LA所表示的L3LE。
  16. 一种路由设备，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求1至6中任一项所述的路由方法。
  17. 一种路由设备，包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行如权利要求7至13中任一项所述的路由方法。
  18. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至6中任一项所述的路由方法。
  19. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求7至13中任一项所述的路由方法。
PCT/CN2020/082437 2019-04-04 2020-03-31 路由方法及路由设备 WO2020200200A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910272550.1 2019-04-04
CN201910272550.1A CN111786884B (zh) 2019-04-04 2019-04-04 一种路由方法及路由设备

Publications (1)

Publication Number Publication Date
WO2020200200A1 true WO2020200200A1 (zh) 2020-10-08

Family

ID=72664419

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/082437 WO2020200200A1 (zh) 2019-04-04 2020-03-31 路由方法及路由设备

Country Status (2)

Country Link
CN (1) CN111786884B (zh)
WO (1) WO2020200200A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113472665A (zh) * 2021-06-17 2021-10-01 新华三信息安全技术有限公司 Evpn下不同组网对接的实现方法及装置
CN113992565A (zh) * 2021-09-29 2022-01-28 新华三大数据技术有限公司 一种组播报文处理方法及装置
CN114827023A (zh) * 2021-01-28 2022-07-29 中国电信股份有限公司 端到端业务保障方法和系统
CN114827057A (zh) * 2021-01-11 2022-07-29 中国电信股份有限公司 通信方法以及通信系统
CN115190100A (zh) * 2022-07-04 2022-10-14 中国联合网络通信集团有限公司 数据转发方法、vtep网关、电子设备及可读存储介质
CN115334045A (zh) * 2022-08-12 2022-11-11 迈普通信技术股份有限公司 报文转发方法、装置、网关设备及存储介质
US20220417141A1 (en) * 2019-04-04 2022-12-29 Cisco Technology, Inc. Interoperability between symmetric and asymmetric evpn irb modes

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115695279A (zh) * 2021-07-31 2023-02-03 华为技术有限公司 一种基于第6版互联网协议的段路由SRv6的通信方法
CN115842764A (zh) * 2021-08-25 2023-03-24 中兴通讯股份有限公司 Rt-5g路由报文的发布方法、装置、存储介质和电子装置
CN117377020A (zh) * 2022-06-30 2024-01-09 中兴通讯股份有限公司 路由发布方法、电子设备和计算机可读存储介质
CN117478572A (zh) * 2022-07-21 2024-01-30 华为技术有限公司 通信方法及装置
CN117640486A (zh) * 2022-08-11 2024-03-01 中国电信股份有限公司 实现SRV6 policy网络H-VPN分层管理的方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103067279A (zh) * 2011-10-24 2013-04-24 中兴通讯股份有限公司 Vpn互联方法及系统
CN108199963A (zh) * 2017-12-27 2018-06-22 新华三技术有限公司 报文转发方法和装置
CN108574616A (zh) * 2017-03-14 2018-09-25 华为技术有限公司 一种处理路由的方法、设备及系统
US20180375763A1 (en) * 2017-06-27 2018-12-27 Cisco Technology, Inc. Ethernet Virtual Private Network (EVPN) using an Internet Protocol Version 6 Segment Routing (SRv6) Underlay Network and SRv6-enhanced Border Gateway Protocol (BGP) Signaling

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9992154B2 (en) * 2016-06-30 2018-06-05 Juniper Networks, Inc. Layer 3 convergence for EVPN link failure
US10142129B1 (en) * 2016-09-27 2018-11-27 Juniper Networks, Inc. Bum packet filtering in multi-homed EVPN overlay networks
US20180091445A1 (en) * 2016-09-29 2018-03-29 Juniper Networks, Inc. Evpn designated forwarder state propagation to customer edge devices using connectivity fault management
CN108696414A (zh) * 2017-04-05 2018-10-23 中兴通讯股份有限公司 多归接入方法、装置及多归属节点
CN108092890B (zh) * 2017-12-26 2020-01-07 新华三技术有限公司 路由建立方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103067279A (zh) * 2011-10-24 2013-04-24 中兴通讯股份有限公司 Vpn互联方法及系统
CN108574616A (zh) * 2017-03-14 2018-09-25 华为技术有限公司 一种处理路由的方法、设备及系统
US20180375763A1 (en) * 2017-06-27 2018-12-27 Cisco Technology, Inc. Ethernet Virtual Private Network (EVPN) using an Internet Protocol Version 6 Segment Routing (SRv6) Underlay Network and SRv6-enhanced Border Gateway Protocol (BGP) Signaling
CN108199963A (zh) * 2017-12-27 2018-06-22 新华三技术有限公司 报文转发方法和装置

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220417141A1 (en) * 2019-04-04 2022-12-29 Cisco Technology, Inc. Interoperability between symmetric and asymmetric evpn irb modes
US11716280B2 (en) * 2019-04-04 2023-08-01 Cisco Technology, Inc. Interoperability between symmetric and asymmetric EVPN IRB modes
CN114827057A (zh) * 2021-01-11 2022-07-29 中国电信股份有限公司 通信方法以及通信系统
CN114827057B (zh) * 2021-01-11 2024-04-16 中国电信股份有限公司 通信方法以及通信系统
CN114827023A (zh) * 2021-01-28 2022-07-29 中国电信股份有限公司 端到端业务保障方法和系统
CN114827023B (zh) * 2021-01-28 2023-06-02 中国电信股份有限公司 端到端业务保障方法和系统
CN113472665A (zh) * 2021-06-17 2021-10-01 新华三信息安全技术有限公司 Evpn下不同组网对接的实现方法及装置
CN113472665B (zh) * 2021-06-17 2022-11-18 新华三信息安全技术有限公司 Evpn下不同组网对接的实现方法及装置
CN113992565A (zh) * 2021-09-29 2022-01-28 新华三大数据技术有限公司 一种组播报文处理方法及装置
CN113992565B (zh) * 2021-09-29 2023-11-07 新华三大数据技术有限公司 一种组播报文处理方法及装置
CN115190100A (zh) * 2022-07-04 2022-10-14 中国联合网络通信集团有限公司 数据转发方法、vtep网关、电子设备及可读存储介质
CN115334045A (zh) * 2022-08-12 2022-11-11 迈普通信技术股份有限公司 报文转发方法、装置、网关设备及存储介质
CN115334045B (zh) * 2022-08-12 2023-12-19 迈普通信技术股份有限公司 报文转发方法、装置、网关设备及存储介质

Also Published As

Publication number Publication date
CN111786884B (zh) 2022-08-02
CN111786884A (zh) 2020-10-16

Similar Documents

Publication Publication Date Title
WO2020200200A1 (zh) 路由方法及路由设备
RU2735725C1 (ru) Способ и устройство обработки и отправки пакетов, узел pe и узел
US10361884B2 (en) Virtual private network forwarding and nexthop to transport mapping scheme
US11888651B2 (en) Virtual private network VPN service optimization method and device
EP3780545B1 (en) Flow specification protocol-based communications method, and device
US10484203B2 (en) Method for implementing communication between NVO3 network and MPLS network, and apparatus
WO2019105462A1 (zh) 报文的发送、处理方法及装置，pe节点，节点
CN107040463B (zh) 用于避免由于非对称mac获悉的流量泛洪的系统
US8665887B2 (en) Number automatic routing method, updating method, withdrawing method, router and device
US20110032843A1 (en) Setting up a virtual private network using virtual lan identifiers
WO2015165311A1 (zh) 传输数据报文的方法和供应商边缘设备
CN107070789B (zh) 主动-主动pbb-evpn冗余的流量黑洞避免和快速融合
CN110417655B (zh) 一种数据报文转发的方法及装置
WO2022184169A1 (zh) 报文转发方法、系统、存储介质及电子装置
US20230095253A1 (en) Fast reroute for ethernet virtual private networks - virtual extensible local area network
US20220200820A1 (en) Packet Sending Method and Apparatus
CN113904981B (zh) 一种路由信息处理方法、装置、电子设备和存储介质
EP4020903B1 (en) Method and apparatus for preventing traffic bypassing
US20230081052A1 (en) Method and apparatus for sending multicast packet
EP3487130B1 (en) Method, router and medium for avoiding traffic flooding due to asymmetric mac learning and achieving predictable convergence for pbb-evpn active-active redundancy
WO2021259271A1 (zh) 信息处理方法、节点及存储介质
WO2024032636A9 (zh) 实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备
WO2023077814A1 (zh) 一种路由发布的方法、装置及系统
Rabadan et al. Usage and Applicability of BGP MPLS-Based Ethernet VPN
Sajassi et al. Internet Engineering Task Force (IETF) J. Rabadan, Ed. Request for Comments: 8388 S. Palislamovic Category: Informational W. Henderickx

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: 20782024

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20782024

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18/03/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20782024

Country of ref document: EP

Kind code of ref document: A1