Abstract: One technique includes receiving, in a first network, a multi-destination packet from a second network, and determining, based on the multi-destination packet, a first multi-destination tree in the first network for forwarding the multi-destination packet. In response to determining that the first multi-destination tree is not rooted on the network device, a second multi-destination tree in the first network is determined, and the multi-destination packet is transmitted using the second multi-destination tree. Another technique includes, upon detecting a first network device joining a network, sending a first indication to a second network device that the first network device is in a state for an amount of time. After the amount of time has elapsed, a second indication that the first network device has exited the state is sent to the second network device. A topology of the network is updated after the first network device has exited the state.

Abstract: One technique includes receiving, in a first network, a multi-destination packet from a second network, and determining, based on the multi-destination packet, a first multi-destination tree in the first network for forwarding the multi-destination packet. In response to determining that the first multi-destination tree is not rooted on the network device, a second multi-destination tree in the first network is determined, and the multi-destination packet is transmitted using the second multi-destination tree. Another technique includes, upon detecting a first network device joining a network, sending a first indication to a second network device that the first network device is in a state for an amount of time. After the amount of time has elapsed, a second indication that the first network device has exited the state is sent to the second network device. A topology of the network is updated after the first network device has exited the state.

Abstract: One technique includes receiving, in a first network, a multi-destination packet from a second network, and determining, based on the multi-destination packet, a first multi-destination tree in the first network for forwarding the multi-destination packet. In response to determining that the first multi-destination tree is not rooted on the network device, a second multi-destination tree in the first network is determined, and the multi-destination packet is transmitted using the second multi-destination tree. Another technique includes, upon detecting a first network device joining a network, sending a first indication to a second network device that the first network device is in a state for an amount of time. After the amount of time has elapsed, a second indication that the first network device has exited the state is sent to the second network device. A topology of the network is updated after the first network device has exited the state.

Abstract: One technique includes receiving, in a first network, a multi-destination packet from a second network, and determining, based on the multi-destination packet, a first multi-destination tree in the first network for forwarding the multi-destination packet. In response to determining that the first multi-destination tree is not rooted on the network device, a second multi-destination tree in the first network is determined, and the multi-destination packet is transmitted using the second multi-destination tree. Another technique includes, upon detecting a first network device joining a network, sending a first indication to a second network device that the first network device is in a state for an amount of time. After the amount of time has elapsed, a second indication that the first network device has exited the state is sent to the second network device. A topology of the network is updated after the first network device has exited the state.

Abstract: Embodiment provide recovering multicast data traffic during spine reload in software defined networks by identifying interfaces available between spine switches and a public network in a site; identifying Group Internet Protocol-outer (GIPo) addresses that handle multicast communications between endpoints associated together in a bridge domain, wherein the endpoints are connected via leaf switches in communication with the spine switches in a Clos topology; assigning each GIPo address to one virtual interface group (ViG) of a plurality of ViGs to generate GIPo-to-ViG mappings; distributing the GIPo-to-ViG mappings to the spine and leaf switches; assigning each ViG to one Interface as first ViG-to-Interface mappings; distributing the first ViG-to-Interface mappings to the spine and leaf switches and; when a number of available Interfaces changes, re-assigning each ViG to one currently-available Interface as second ViG-to-Interface mappings; and distributing the second ViG-to-Interface mappings to the spine swi

Abstract: Embodiment provide recovering multicast data traffic during spine reload in software defined networks by identifying interfaces available between spine switches and a public network in a site; identifying Group Internet Protocol-outer (GIPo) addresses that handle multicast communications between endpoints associated together in a bridge domain, wherein the endpoints are connected via leaf switches in communication with the spine switches in a Clos topology; assigning each GIPo address to one virtual interface group (ViG) of a plurality of ViGs to generate GIPo-to-ViG mappings; distributing the GIPo-to-ViG mappings to the spine and leaf switches; assigning each ViG to one Interface as first ViG-to-Interface mappings; distributing the first ViG-to-Interface mappings to the spine and leaf switches and; when a number of available Interfaces changes, re-assigning each ViG to one currently-available Interface as second ViG-to-Interface mappings; and distributing the second ViG-to-Interface mappings to the spine swi