US-12621239-B2 - Route advertisement method, apparatus, and system
Abstract
A route advertisement method includes advertising, by a first network device, an Internet Protocol (IP) prefix route to a second network device, where the IP Prefix route includes a gateway (GW) IP address and a Multi-Protocol Label Switching (MPLS) label. The GW IP address is an IP address of a first interface of the first network device. The MPLS Label is a label of a first IP-virtual routing and forwarding (IP-VRF) instance of the first network device. The first network device advertises a media access control (MAC)/IP route to the second network device, where the MAC/IP route includes the IP address of the first interface and a MAC address of the first interface.
Inventors
- Yang Huang
Assignees
- HUAWEI TECHNOLOGIES CO., LTD.
Dates
- Publication Date
- 20260505
- Application Date
- 20240430
- Priority Date
- 20211104
Claims (17)
- 1 . A first network device comprising: a first interface, wherein the first interface is a first supplementary broadcast domain (SBD) integrated routing and bridging (IRB) interface belonging to an SBD; one or more processors; and a memory configured to store program instructions, which, when executed by the one or more processors, cause the first network device to: advertise an Ethernet virtual private network (EVPN) Internet Protocol (IP) prefix route to a second network device, wherein the EVPN IP prefix route comprises a gateway (GW) IP address and a Multiprotocol Label Switching (MPLS) label, wherein the GW IP address is an IP address of the first interface, and wherein the MPLS label is a label of a first IP-virtual routing and forwarding (VRF) instance of the first network device; and advertise an EVPN media access control (MAC)/IP route to the second network device, wherein the EVPN MAC/IP route comprises the IP address and a MAC address of the first interface, wherein the second network device comprises a second IP-VRF instance, and wherein a second interface of the second network device does not support SBD IRB.
- 2 . The first network device of claim 1 , wherein the program instructions, when executed by the one or more processors, further cause the first network device to advertise, using a route reflector, the EVPN IP prefix route and the EVPN MAC/IP route to the second network device.
- 3 . The first network device of claim 1 , wherein the first SBD IRB interface belongs to an SBD that is used to connect the first IP-VRF instance and the second IP-VRF instance of the second network device.
- 4 . The first network device of claim 1 , wherein the first network device is a network virtualization edge (NVE) device or a datacenter gateway (DGW) device.
- 5 . The first network device of claim 1 , wherein the second network device is a network virtualization edge (NVE) device or a datacenter gateway (DGW) device.
- 6 . A second network device comprising: one or more processors; a second interface that does not support supplementary broadcast domain (SBD) integrated routing and bridging (IRB); and a memory configured to store program instructions, which, when executed by the one or more processors, cause the second network device to: receive an Ethernet virtual private network (EVPN) Internet Protocol (IP) prefix route of a first network device, wherein the EVPN IP prefix route comprises a gateway (GW) IP address and a Multiprotocol Label Switching (MPLS) label, wherein the GW IP address is an IP address of a first interface of the first network device, and wherein the MPLS label is a label of a first IP-virtual routing and forwarding (VRF) instance of the first network device; receive an EVPN media access control (MAC)/IP route of the first network device, wherein the EVPN MAC/IP route comprises the IP address and a MAC address of the first interface; and generate, based on the EVPN IP prefix route, a routing entry corresponding to a second IP-VRF instance of the second network device, wherein the routing entry comprises the MPLS label.
- 7 . The second network device of claim 6 , wherein the program instructions, when executed by the one or more processors, further cause the second network device to receive, from a route reflector, the EVPN IP prefix route and the EVPN MAC/IP route of the first network device.
- 8 . The second network device of claim 6 , wherein the program instructions, when executed by the one or more processors, further cause the second network device to: generate, based on the EVPN IP prefix route, a routing entry corresponding to the second IP-VRF instance, wherein the routing entry comprises the GW IP address; and generate, an entry of an Address Resolution Protocol (ARP) table based on the EVPN MAC/IP route, wherein the entry comprises the IP address and the MAC address.
- 9 . The second network device of claim 6 , wherein the first network device is a network virtualization edge (NVE) device or a datacenter gateway (DGW) device.
- 10 . The second network device of claim 6 , wherein the second network device is a network virtualization edge (NVE) device or a datacenter gateway (DGW) device.
- 11 . A computer program product comprising computer-executable instructions stored on a non-transitory computer-readable storage medium, wherein the computer-executable instructions, when executed by one or more processors of a first network device, cause the first network device to: advertise an Ethernet virtual private network (EVPN) Internet Protocol (IP) prefix route to a second network device, wherein the EVPN IP prefix route comprises a gateway (GW) IP address and a Multiprotocol Label Switching (MPLS) label, wherein the GW IP address is an IP address of a first interface of the first network device, and wherein the MPLS label is a label of a first IP-virtual routing and forwarding (VRF) instance of the first network device; and advertise an EVPN media access control (MAC)/IP route to the second network device, wherein the EVPN MAC/IP route comprises the IP address and a MAC address of the first interface, and wherein the first interface is a first supplementary broadcast domain (SBD) integrated routing and bridging (IRB) interface belonging to an SBD, wherein the second network device comprises a second IP-VRF instance, and wherein a second interface of the second network device does not support SBD IRB.
- 12 . The computer program product of claim 11 , wherein the computer-executable instructions when executed by the one or more processors further cause the first network device to advertise, using a route reflector, the EVPN IP prefix route and the EVPN MAC/IP route to the second network device.
- 13 . The computer program product of claim 11 , wherein the first interface is used to connect the first IP-VRF instance and the second IP-VRF instance of the second network device.
- 14 . The computer program product of claim 11 , wherein the first network device is a network virtualization edge (NVE) device.
- 15 . The computer program product of claim 11 , wherein the second network device is a network virtualization edge (NVE) device.
- 16 . The computer program product of claim 11 , wherein the second network device is a datacenter gateway (DGW) device.
- 17 . The computer program product of claim 11 , wherein the first network device is a datacenter gateway (DGW) device.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of International Patent Application No. PCT/CN2022/099511 filed on Jun. 17, 2022, which claims priority to Chinese Patent Application No. 202111301919.0 filed on Nov. 4, 2021. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties. TECHNICAL FIELD The present disclosure relates to the field of communication technologies, and in particular, to a route advertisement method, an apparatus, and a system. BACKGROUND An Ethernet virtual private network (EVPN) is a control plane protocol based on a border gateway protocol (BGP). An Internet Protocol prefix advertisement (IP Prefix) route is defined in a standard draft Rabadan, et al. “IP Prefix Advertisement in EVPN draft-ietf-bess-evpn-prefix-advertisement-11” dated May 18, 2018, released by the Internet Engineering Task Force (IETF). Service interworking between subnets may be implemented by advertising the IP Prefix route. The draft also defines a plurality of use cases to describe an application scenario of the IP Prefix route. The draft defines a route advertisement rule for a plurality of single scenarios. For example, Internet Protocol (IP) reachability information of a subnet may be advertised by advertising the IP Prefix route in an interface-less IP—virtual routing and forwarding (VRF)-to-IP-VRF model (Interface-less Model) and an interface-ful IP-VRF-to-IP-VRF with supplementary broadcast domain (SBD) integrated routing and bridging (IRB) model (Interface-ful Model). In an actual network environment, the Interface-less Model and the Interface-ful Model may be deployed in a mixed manner. In this networking, when a network virtualization edge (NVE) device advertises a route based on the Interface-less Model, a datacenter gateway (DGW) device that supports the Interface-ful Model cannot generate a valid routing table based on the route. When the NVE device advertises a route based on the Interface-ful Model, a DGW device that supports the Interface-less Model cannot generate a valid routing table based on the route. As a result, service reliability cannot be ensured. SUMMARY In view of this, embodiments of the present disclosure provide a route advertisement method, an apparatus, and a system. A first network device advertises an EVPN IP Prefix route to a second network device, where the IP Prefix route includes a gateway (GW) IP address and a Multi-Protocol Label Switching (MPLS) label, the GW IP address is an IP address of a first interface of the first network device, and the MPLS label is a label of a first IP-VRF instance of the first network device. The first network device advertises an EVPN media access control (MAC)/IP route to the second network device, where the MAC/IP route includes the IP address of the first interface and a MAC address of the first interface. An IP Prefix route sent by the first network device in an Interface-less Model is the same as a route sent in an Interface-ful Model. This resolves a route advertisement problem in a scenario in which the Interface-less Model and the Interface-ful Model are mixed, so that service interworking can be implemented regardless of whether a route reflector (RR) device is deployed, service reliability in this scenario is ensured, and network planning and configuration is simplified. In addition, a maximum of one RR device is needed when the RR device is deployed. This reduces a quantity of RRs. A technical solution provided in embodiments of the present disclosure is as follows. According to a first aspect, the present disclosure provides a route advertisement method. The method includes: A first network device advertises an EVPN IP Prefix route to a second network device, where the IP Prefix route includes a gateway internet protocol GW IP address and a MPLS Label, the GW IP address is an IP address of a first interface of the first network device, and the MPLS Label is a label of a first IP-VRF instance of the first network device. The first network device advertises an EVPN MAC/IP route to the second network device, where the MAC/IP route includes the IP address of the first interface and a MAC address of the first interface. Based on the solution provided in this embodiment, in a route advertisement process in a scenario in which an Interface-less Model and an Interface-ful Model are mixed, the first network device advertises the IP Prefix route to the second network device, where the IP Prefix route includes the GW IP address and the multi-protocol label switching label MPLS Label, the GW IP address is the IP address of the first interface of the first network device, and the MPLS Label is the label of the first IP-VRF instance of the first network device. The first network device advertises the EVPN MAC/IP route to the second network device, where the MAC/IP route includes the IP address of the first interface and the MAC address of the first interface. This resol