Abstract: A network device may receive, from a timing source of a network, timing information. The network device may identify a client device to which the timing information is to be provided, wherein the network device provides an interface between the client device and the network. The network device may select a virtual network address to associate with a timing agent of the network device, wherein the virtual network address is within an address range that is reachable by the client device. The network device may provide to the client device, and via a network layer communication, a timing control packet comprising the timing information, wherein the timing control packet identifies the virtual network address as a source network address of the timing control packet, and wherein the timing information is to be used by the client device to update a clock of the client device.

Abstract: A first provider edge device may receive device information from a second provider edge device included in an Ethernet virtual private network (EVPN). The device information may identify a media access control (MAC) address and may indicate that the device is connected to the second provider edge device. The first provider edge device may receive data transmitted by the device and may determine, based on information included in the data, that the device has moved from the second provider edge device to the first provider edge device. The first provider edge device may generate a data packet including mobility information indicating that the device has moved to the first provider edge device. The first provider edge device may transmit, via a data plane of the EVPN, the data packet to the second provider edge device to permit the second provider edge device to update routing information for the device.

Abstract: A network device may receive, from a timing source of a network, timing information. The network device may identify a client device to which the timing information is to be provided, wherein the network device provides an interface between the client device and the network. The network device may select a virtual network address to associate with a timing agent of the network device, wherein the virtual network address is within an address range that is reachable by the client device. The network device may provide to the client device, and via a network layer communication, a timing control packet comprising the timing information, wherein the timing control packet identifies the virtual network address as a source network address of the timing control packet, and wherein the timing information is to be used by the client device to update a clock of the client device.

Abstract: A network device may receive, from a timing source of a network, timing information. The network device may identify a client device to which the timing information is to be provided, wherein the network device provides an interface between the client device and the network. The network device may select a virtual network address to associate with a timing agent of the network device, wherein the virtual network address is within an address range that is reachable by the client device. The network device may provide to the client device, and via a network layer communication, a timing control packet comprising the timing information, wherein the timing control packet identifies the virtual network address as a source network address of the timing control packet, and wherein the timing information is to be used by the client device to update a clock of the client device.

Abstract: Techniques are described for managing a split-brain scenario in a multihomed environment by exchanging isolation information between a leaf device and two or more spine devices to which the leaf device is multihomed via a link aggregation group (LAG). The techniques include selecting one of the spine devices as a primary spine device and determining, based on the isolation information, whether the spine devices are isolated from each other. In the split-brain scenario in which all of the spine devices are isolated from each other, the primary spine device is configured to maintain the LAG with the leaf device while the other spine devices mark the LAG with the leaf device as down. In this way, in the split-brain scenario, the leaf device may continue to send traffic to other leaf devices in the leaf layer using the LAG to the primary spine device.

Abstract: A device may receive, from a provider edge device, a packet to be provided to one or more other provider edge devices. Some of the one or more other provider edge devices may be multi-homed with a same customer edge device as the provider edge device. The device may configure a source IP address of the packet based on a capability of an assisted replicator device after receiving the packet. The capability may relate to whether the assisted replicator device is capable of retaining the source IP address of the packet as received from the provider edge device. The device may provide the packet to at least some provider edge devices, of the one or more other provider edge devices, after configuring the source IP address of the packet.

Abstract: A first provider edge device may receive device information from a second provider edge device included in an Ethernet virtual private network (EVPN). The device information may identify a media access control (MAC) address and may indicate that the device is connected to the second provider edge device. The first provider edge device may receive data transmitted by the device and may determine, based on information included in the data, that the device has moved from the second provider edge device to the first provider edge device. The first provider edge device may generate a data packet including mobility information indicating that the device has moved to the first provider edge device. The first provider edge device may transmit, via a data plane of the EVPN, the data packet to the second provider edge device to permit the second provider edge device to update routing information for the device.

Abstract: A device may receive, from a provider edge device, a packet to be provided to one or more other provider edge devices. Some of the one or more other provider edge devices may be multi-homed with a same customer edge device as the provider edge device. The device may configure a source IP address of the packet based on a capability of an assisted replicator device after receiving the packet. The capability may relate to whether the assisted replicator device is capable of retaining the source IP address of the packet as received from the provider edge device. The device may provide the packet to at least some provider edge devices, of the one or more other provider edge devices, after configuring the source IP address of the packet.