EVPN E-tree across domains
An EVPN network device may advertise an EVPN IMET (type-3) route in a corresponding message to one or more peer EVPN network devices. The EVPN IMET route advertisement message may include an E-tree extended community indicating a leaf or root designation of a locally attached site at the advertising EVPN network device. The inclusion of the E-tree extended community in the EVPN IMET route advertisement message may provide desired traffic handling for implementing an EVPN E-tree service such as handling of BUM traffic.
1. A method of operating a gateway to provide Ethernet Virtual Private Network (EVPN) Ethernet-tree (E-tree) service for a domain containing root and leaf hosts, the method comprising:
maintaining, by the gateway, a first floodlist identifying a first set of one or more Virtual Tunnel Endpoints (VTEPs) in the domain, wherein the root hosts are attached to the first set of one or more VTEPs;
maintaining, by the gateway, a second floodlist identifying a second set of one or more VTEPs in the domain, wherein the leaf hosts are attached to the second set of one or more VTEPs;
defining, by the gateway, a first Virtual Tunnel Endpoint (VTEP) address of the gateway for encapsulating traffic from the root hosts and a second VTEP address of the gateway for encapsulating traffic from the leaf hosts;
sending, by the gateway, a first route advertisement message with the first VTEP address toward one or more EVPN peer network devices, the first route advertisement message containing an indication of a root designation, wherein the root designation causes the one or more EVPN peer network devices to forward received VTEP-address-encapsulated traffic with the first VTEP address to one or more remote leaf hosts;
sending, by the gateway, a second route advertisement message with the second VTEP address toward the one or more EVPN peer network devices, the second route advertisement message containing an indication of a leaf designation, wherein the leaf designation causes the one or more EVPN peer network devices not to forward received VTEP-address-encapsulated traffic with the second VTEP address to the one or more remote leaf hosts;
receiving, by the gateway, local broadcast, unknown unicast, or multicast (BUM) traffic; and
forwarding, by the gateway, the local BUM traffic by encapsulating the local BUM traffic with at least one of the first VTEP address of the gateway or the second VTEP address of the gateway based on a comparison of a source VTEP of the local BUM traffic to at least one of the first set of one or more VTEPs identified in the first floodlist or the second set of one or more VTEPs identified the second floodlist.
2. The method defined in claim 1 , wherein forwarding the local BUM traffic by encapsulating the local BUM traffic with at least one of the first VTEP address of the gateway or the second VTEP address of the gateway comprises forwarding BUM traffic from a given root host of the root hosts by encapsulating the BUM traffic from the given root host using the first VTEP address of the gateway.
3. The method defined in claim 2 wherein the comparison comprises a comparison of a source VTEP of the BUM traffic from the given root host to at least one of the first set of one or more VTEPs identified in the first floodlist or the second set of one or more VTEPs identified in the second floodlist to determine that the source VTEP of the BUM traffic from the given root host has a root designation.
4. The method defined in claim 1 , wherein forwarding the local BUM traffic by encapsulating the local BUM traffic with at least one of the first VTEP address of the gateway or the second VTEP address of the gateway comprises forwarding BUM traffic from a given leaf host of the leaf hosts by encapsulating the BUM traffic from the given leaf host using the second VTEP address of the gateway.
5. The method defined in claim 4 wherein the comparison comprises a comparison of a source VTEP of the BUM traffic from the given leaf host to at least one of the first set of one or more VTEPs identified in the first floodlist or the second set of one or more VTEPs identified in the second floodlist to determine that the source VTEP of the BUM traffic from the given leaf host has a leaf designation.
6. The method defined in claim 1 , wherein
the first route advertisement message is a first EVPN Inclusive Multicast Ethernet Tag (IMET) route advertisement message.
7. The method defined in claim 6 , wherein
the second route advertisement message is a second EVPN IMET route advertisement message.
8. The method defined in claim 7 , wherein at least one of the first set of one or more VTEPs or the second set of one or more VTEPs is implemented on a VTEP device, the method further comprising:
sending the first EVPN IMET route advertisement message and the second EVPN IMET route advertisement message toward the VTEP device to maintain a third floodlist on the VTEP device identifying one or both of the first VTEP address of the gateway and the second VTEP address of the gateway.
9. The method defined in claim 8 , wherein the VTEP device is attached to a root host and wherein the third floodlist comprises the first VTEP address of the gateway and the second VTEP address of the gateway.
10. The method defined in claim 8 , wherein the VTEP device is attached to a leaf host and wherein the third floodlist comprises the first VTEP address of the gateway and not the second VTEP address of the gateway.
11. An Ethernet Virtual Private Network (EVPN) network device configured to provide Ethernet-tree (E-tree) service comprising:
memory circuitry configured to store first and second Virtual Tunnel Endpoint (VTEP) addresses for providing the E-tree service, wherein the first VTEP address and the second VTEP address are each an address of the EVPN network device;
control plane processing circuitry configured to
send a first route advertisement message with the first VTEP address of the EVPN network device toward one or more EVPN peer network devices, the first route advertisement message containing an indication of a root designation, wherein the root designation causes the one or more EVPN peer network devices to forward received VTEP-address-encapsulated traffic with the first VTEP address to one or more remote leaf hosts, and
send a second route advertisement message with the second VTEP address of the EVPN network device toward the one or more EVPN peer network devices, the second route advertisement message containing an indication of a leaf designation, wherein the leaf designation causes the one or more EVPN peer network devices not to forward received VTEP-address-encapsulated traffic with the second VTEP address to the one or more remote leaf hosts; and
one or more packet processors configured to
receive first local traffic,
determine that the first local traffic is from a root-designated source,
output the first local traffic with an encapsulation containing the first VTEP address of the EVPN network device,
receive second local traffic,
determine that the second local traffic is from a leaf-designated source, and
output the second local traffic with an encapsulation containing the second VTEP address of the EVPN network device.
12. The EVPN network device defined in claim 11 , wherein the memory circuitry is configured to store a first floodlist identifying one or more local root VTEPs and a second floodlist identifying one or more local leaf VTEPs.
13. The EVPN network device defined in claim 12 , wherein the second floodlist further identifies the one or more local root VTEPs.
14. The EVPN network device defined in claim 12 , wherein the one or more packet processors are configured to process the received first local traffic and the received second local traffic by accessing the first floodlist and the second floodlist.
15. The EVPN network device defined in claim 12 , wherein the one or more local root VTEPs and the one or more local leaf VTEPs are implemented at one or more VTEP devices and wherein the control plane processing circuitry is configured to send the first route advertisement message and the second route advertisement message toward the one or more VTEP devices and cause the one or more VTEP devices to maintain one or more additional floodlists each identifying one or both of the first VTEP address of the EVPN network device and the second VTEP address of the EVPN network device.
16. An Ethernet Virtual Private Network (EVPN) network device configured to provide Ethernet-tree (E-tree) service comprising:
memory circuitry configured to store first and second Virtual Tunnel Endpoint (VTEP) addresses of the EVPN network device;
control plane processing circuitry configured to send, toward an EVPN peer network device, first and second EVPN route advertisement messages respectively containing the first and second VTEP addresses of the EVPN network device, the first and second EVPN route advertisement messages respectively containing an indication of a root designation and an indication of a leaf designation, wherein the first EVPN route advertisement message causes the EVPN peer network device to forward received VTEP-address-encapsulated traffic with the first VTEP address to at least a remote leaf host and wherein the second EVPN route advertisement message causes the EVPN peer network device not to forward received VTEP-address-encapsulated traffic with the second VTEP address to the remote leaf host; and
one or more packet processors configured to
receive local traffic,
determine whether the local traffic is from a root-designated source or a leaf-designated source,
output the local traffic with an encapsulation containing the first VTEP address of the EVPN network device in response to determining that the local traffic is from the root-designated source, and
output the local traffic with an encapsulation containing the second VTEP address of the EVPN network device in response to determining that the local traffic is from the leaf-designated source.
17. The EVPN network device defined in claim 16 , wherein the first VTEP address of the EVPN network device is a root-designated VTEP address of the EVPN network device.
18. The EVPN network device defined in claim 17 , wherein the local traffic comprises root-sourced broadcast, unknown unicast, or multicast (BUM) traffic and wherein the one or more packet processors are configured to output the root-sourced BUM traffic with the encapsulation containing the first VTEP address of the EVPN network device.
19. The EVPN network device defined in claim 16 , wherein the second VTEP address of the EVPN network device is a leaf-designated VTEP address of the EVPN network device, wherein the local traffic comprises leaf-sourced broadcast, unknown unicast, or multicast (BUM) traffic and wherein the one or more packet processors are configured to output the leaf-sourced BUM traffic with the encapsulation containing the second VTEP address of the EVPN network device.