Abstract:
Embodiments for handling multidestination traffic in a network are described. It is determined that a destination of a packet, received at a network device, is a multihomed destination. In response to determining that the destination of the packet is a multihomed destination, a hash value is determined from a selection of header values of the packet using a hash function. The packet is forwarded to the destination using a shadow hash forwarding table based at least in part on determining, based on the hash value and a hash forwarding table, that the network device is a designated forwarder for the packet.
Abstract:
A network device receives multi-destination packets from a first node and forwards at least a first of the multi-destination packets to another network device using a first multi-destination tree with respect to the network device. The network device detects that a link associated with the first multi-destination tree satisfies one or more criteria and, in response to detecting that the link satisfies the one or more criteria, selects a second multi-destination tree with respect to the network device. The network device forwards at least a second of the multi-destination packets to the other network device using the second multi-destination tree.
Abstract:
A network device receives multi-destination packets from a first node and forwards at least a first of the multi-destination packets to another network device using a first multi-destination tree with respect to the network device. The network device detects that a link associated with the first multi-destination tree satisfies one or more criteria and, in response to detecting that the link satisfies the one or more criteria, selects a second multi-destination tree with respect to the network device. The network device forwards at least a second of the multi-destination packets to the other network device using the second multi-destination tree.
Abstract:
A method is provided one example embodiment and includes receiving a packet including a source /32 address and a destination /32 address. The source /32 address can indicate an Internet Protocol (IP) address of a source host that sent the packet. The destination /32 address can indicate an IP address of a destination host to which the packet is destined. The method may also include looking up the destination /32 address and the source /32 address in a Forwarding Information Base/adjacency (FIB)/(ADJ) table implemented in a hardware of a leaf switch in a network. Additionally, the method may include adding the source /32 address and corresponding adjacency information to the FIB/ADJ table if the destination /32 address is found in the FIB/ADJ table, and the source /32 address is not found in the FIB/ADJ table. The method may also include forwarding the packet to the destination host.
Abstract:
Embodiments for handling multidestination traffic in a network are described. The multidestination traffic includes packets that are in transit to a multihomed destination in the network. Upon determining the destination is multihomed, a network switch determines a hash value from a selection of header values in the network traffic and uses the hash value to determine if the network switch is a designated forwarder for the multihomed destination. The network switch handles the network traffic according to a designated forwarder status.
Abstract:
Embodiments for handling multidestination traffic in a network are described. The multidestination traffic includes packets that are in transit to a multihomed destination in the network. Upon determining the destination is multihomed, a network switch determines a hash value from a selection of header values in the network traffic and uses the hash value to determine if the network switch is a designated forwarder for the multihomed destination. The network switch handles the network traffic according a designated forwarder status.