Abstract: At a provider edge (PE) router of PE routers of an Ethernet virtual private network (EVPN) configured to implement a border gateway protocol (BGP): receiving, from a multicast receiver, a multicast join for multicast traffic originated from a multicast source; identifying a next hop PE router for the multicast source; generating an EVPN route to the PE router, the EVPN route including an EVPN instance-route target that identifies the EVPN, and a specifically targeted route target that identifies the next hop PE router and that is configured to override the EVPN instance-route target to cause only the next hop PE router, and not any other of the PE routers, to import the EVPN route, when the EVPN route is advertised across the EVPN to the PE routers; and advertising the EVPN route across the EVPN to the PE routers.

Abstract: A method is performed at a provider edge node configured to communicate with remote provider edge nodes over an Ethernet virtual private network. The method includes receiving, from the remote provider edge nodes, route advertisements for a common subnet hosted on the remote provider edge nodes. The route advertisements include distinct remote route distinguishers, a common IP prefix for the common subnet, and remote paths for the common subnet. The method further includes determining whether there are at least a predetermined number of the remote paths preferred over a local path for the common subnet hosted on the provider edge node based on the remote route distinguishers and a local route distinguisher for the local path. The method includes, when there are at least the predetermined number of the remote paths preferred over the local path, suppressing sending of a route advertisement for the local path for the common subnet.

Abstract: In one embodiment, a method includes receiving, by a first router, data from a network component. The method also includes determining, by the first router, a first link bandwidth capacity between the first router and a host device and determining, by the first router, a first score for the first router based on the first link bandwidth capacity. The method also includes determining, by the first router, a second link bandwidth capacity between a second router and the host device and determining, by the first router, a second score for the second router based on the second link bandwidth capacity. The method further includes comparing, by the first router, at least the first score and the second score to determine a highest score and assigning, by the first router, an edge router associated with the highest score to communicate the data to the host device.

Abstract: A method comprises, at a first router configured to perform Bit Index Explicit Replication (BIER) for forwarding of multicast packets in a network, storing configuration information that indicates that the first router belongs to multiple subdomains of a BIER domain, and is able to forward the multicast packets for a virtual private network on the multiple subdomains. The method further comprises, during an auto-discovery procedure, generating an auto-discovery message to include an auto-discovery route and route attributes that indicate the multiple subdomains, and sending the auto-discovery message to a second router of the virtual private network the network.

Abstract: A method comprises, at a first router configured to perform Bit Index Explicit Replication (BIER) for forwarding of multicast packets in a network, storing configuration information that indicates that the first router belongs to multiple subdomains of a BIER domain, and is able to forward the multicast packets for a virtual private network on the multiple subdomains. The method further comprises, during an auto-discovery procedure, generating an auto-discovery message to include an auto-discovery route and route attributes that indicate the multiple subdomains, and sending the auto-discovery message to a second router of the virtual private network the network.

Abstract: In some embodiments, a first provider edge (PE) router is coupled to a first customer edge (CE) router; a second CE router; and a second PE router. The second PE router is coupled to the first CE router and the second CE router. The first PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the second PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router. The second PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the first PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router.

Abstract: In some embodiments, a first provider edge (PE) router is coupled to a first customer edge (CE) router; a second CE router; and a second PE router. The second PE router is coupled to the first CE router and the second CE router. The first PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the second PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router. The second PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the first PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router.

Abstract: Techniques and mechanisms for a control plane approach for dense topologies that focusses on discovering shared ECMP groups in the control plane independent of per-prefix learning and then learning prefixes via these shared ECMP groups instead of learning prefixes via one next-hop at a time. In dense topologies, this approach helps minimize BGP path scale, corresponding signaling and enables control plane scaling that is an order of magnitude higher than a traditional eBGP control plane. During link and node topology changes, the described control plane approach enables control plane signaling that is prefix independent and an order of magnitude lower. A control plane approach to path-list sharing and prefix independent signaling on link and node topology changes enables prefix independent convergence (PIC) in scenarios that would not be possible otherwise with traditional FIB driven path-list sharing and PIC.

Abstract: In one embodiment, a method includes receiving, by a first router, data from a network component. The method also includes determining, by the first router, a first link bandwidth capacity between the first router and a host device and determining, by the first router, a first score for the first router based on the first link bandwidth capacity, The method also includes determining, by the first router, a second link bandwidth capacity between a second router and the host device and determining, by the first router, a second score for the second router based on the second link bandwidth capacity. The method further includes comparing, by the first router, at least the first score and the second score to determine a highest score and assigning, by the first router, an edge router associated with the highest score to communicate the data to the host device.

Abstract: Techniques and mechanisms for a control plane approach for dense topologies that focusses on discovering shared ECMP groups in the control plane independent of per-prefix learning and then learning prefixes via these shared ECMP groups instead of learning prefixes via one next-hop at a time. In dense topologies, this approach helps minimize BGP path scale, corresponding signaling and enables control plane scaling that is an order of magnitude higher than a traditional eBGP control plane. During link and node topology changes, the described control plane approach enables control plane signaling that is prefix independent and an order of magnitude lower. A control plane approach to path-list sharing and prefix independent signaling on link and node topology changes enables prefix independent convergence (PIC) in scenarios that would not be possible otherwise with traditional FIB driven path-list sharing and PIC.

Abstract: A method is performed by a network controller. The method includes receiving information that defines a topology of a network having Ethernet Segments configured with virtual local area networks (VLANs) and including provider edges that are multi-homed to customer edges. The method further comprises, based on the topology, determining for the VLANs particular provider edges among the provider edges that are to operate as designated forwarders of traffic for the VLANs, such that the VLANs are load balanced across the particular provider edges. The method also includes programming the particular provider edges as the designated forwarders of traffic for the VLANs.

Abstract: A method is performed at a provider edge node configured to communicate with remote provider edge nodes over an Ethernet virtual private network. The method includes receiving, from the remote provider edge nodes, route advertisements for a common subnet hosted on the remote provider edge nodes. The route advertisements include distinct remote route distinguishers, a common IP prefix for the common subnet, and remote paths for the common subnet. The method further includes determining whether there are at least a predetermined number of the remote paths preferred over a local path for the common subnet hosted on the provider edge node based on the remote route distinguishers and a local route distinguisher for the local path. The method includes, when there are at least the predetermined number of the remote paths preferred over the local path, suppressing sending of a route advertisement for the local path for the common subnet.

Abstract: Techniques and mechanisms for a control plane approach for dense topologies that focusses on discovering shared ECMP groups in the control plane independent of per-prefix learning and then learning prefixes via these shared ECMP groups instead of learning prefixes via one next-hop at a time. In dense topologies, this approach helps minimize BGP path scale, corresponding signaling and enables control plane scaling that is an order of magnitude higher than a traditional eBGP control plane. During link and node topology changes, the described control plane approach enables control plane signaling that is prefix independent and an order of magnitude lower. A control plane approach to path-list sharing and prefix independent signaling on link and node topology changes enables prefix independent convergence (PIC) in scenarios that would not be possible otherwise with traditional FIB driven path-list sharing and PIC.

Abstract: In some embodiments, a first provider edge (PE) router is coupled to a first customer edge (CE) router; a second CE router; and a second PE router. The second PE router is coupled to the first CE router and the second CE router. The first PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the second PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router. The second PE router is configured with a primary label comprising a primary next hop of the first CE router and a backup next hop of the first PE router and a secondary label comprising a primary next hop of the first CE router and a backup next hop of the second CE router.

Abstract: In one embodiment, a method includes receiving, by a first router, data from a network component. The method also includes determining, by the first router, a first link bandwidth capacity between the first router and a host device and determining, by the first router, a first score for the first router based on the first link bandwidth capacity. The method also includes determining, by the first router, a second link bandwidth capacity between a second router and the host device and determining, by the first router, a second score for the second router based on the second link bandwidth capacity. The method further includes comparing, by the first router, at least the first score and the second score to determine a highest score and assigning, by the first router, an edge router associated with the highest score to communicate the data to the host device.

Abstract: A method comprises, at a first router configured to perform Bit Index Explicit Replication (BIER) for forwarding of multicast packets in a network, storing configuration information that indicates that the first router belongs to multiple subdomains of a BIER domain, and is able to forward the multicast packets for a virtual private network on the multiple subdomains. The method further comprises, during an auto-discovery procedure, generating an auto-discovery message to include an auto-discovery route and route attributes that indicate the multiple subdomains, and sending the auto-discovery message to a second router of the virtual private network the network.

Abstract: A method is performed by a network controller. The method includes receiving information that defines a topology of a network having Ethernet Segments configured with virtual local area networks (VLANs) and including provider edges that are multi-homed to customer edges. The method further comprises, based on the topology, determining for the VLANs particular provider edges among the provider edges that are to operate as designated forwarders of traffic for the VLANs, such that the VLANs are load balanced across the particular provider edges. The method also includes programming the particular provider edges as the designated forwarders of traffic for the VLANs.

Abstract: A method comprises, at a first router configured to perform Bit Index Explicit Replication (BIER) for forwarding of multicast packets in a network, storing configuration information that indicates that the first router belongs to multiple subdomains of a BIER domain, and is able to forward the multicast packets for a virtual private network on the multiple subdomains. The method further comprises, during an auto-discovery procedure, generating an auto-discovery message to include an auto-discovery route and route attributes that indicate the multiple subdomains, and sending the auto-discovery message to a second router of the virtual private network the network.

Abstract: In one embodiment, a method includes receiving, by a first router, data from a network component. The method also includes determining, by the first router, a first link bandwidth capacity between the first router and a host device and determining, by the first router, a first score for the first router based on the first link bandwidth capacity. The method also includes determining, by the first router, a second link bandwidth capacity between a second router and the host device and determining, by the first router, a second score for the second router based on the second link bandwidth capacity. The method further includes comparing, by the first router, at least the first score and the second score to determine a highest score and assigning, by the first router, an edge router associated with the highest score to communicate the data to the host device.

Abstract: In general, techniques are described for configuring a provider edge (PE) network device of an Ethernet virtual private network (EVPN) to use a common traffic engineering label (e.g., MPLS label) for different EVPN route types associated with the same EVPN. In some examples, the techniques include sending a first layer three (L3) control plane message that indicates a label-switched network protocol label that corresponds to a first EVPN route type, wherein the first L3 control plane message indicates that a first PE network device is reachable in the L2 segment. The techniques may include performing L2 address learning to determine at least one L2 address associated with the layer two segment of the EVPN. The techniques may include sending a second L3 control plane message that indicates the same label included in the first L3 control plane message corresponds to a second EVPN route type.