Designating a primary multicast flow and a backup multicast flow for multicast traffic
A network device may receive a first redundant multicast flow indication from a first network device, and may receive a second redundant multicast flow indication from a second network device. The device may designate a primary multicast flow based on the first redundant multicast flow indication, and may designate a backup multicast flow based on the second redundant multicast flow indication. The device may accept the primary multicast flow and may discard the backup multicast flow.
1 . A method, comprising:
receiving, by a network device, a first redundant multicast flow indication from a first network device and a second redundant multicast flow indication from a second network device,
wherein the first redundant multicast flow indication includes a first virtual extensible local area network (VXLAN) network identifier (VNI) or a first source VXLAN tunnel endpoint (VTEP) identifier and the second redundant multicast flow indication includes a second VNI or a second source VTEP identifier, and
wherein one or more of the first redundant multicast flow indication and the second redundant multicast flow indication is a Type 10 selective-provider multicast service interface route identifier;
designating, by the network device, a primary multicast flow based on the first redundant multicast flow indication;
designating, by the network device, a backup multicast flow based on the second redundant multicast flow indication;
accepting, by the network device, the primary multicast flow; and
monitoring, by the network device, a rate of the primary multicast flow.
2 . The method of claim 1 , further comprising: receiving a report from a host device; and
identifying the first redundant multicast flow indication and the second redundant multicast flow indication based on receiving the report.
3 . The method of claim 1 , further comprising: continuing to accept the primary multicast flow based on the rate of the primary multicast flow satisfying a rate threshold.
4 . The method of claim 3 , further comprising: accepting the backup multicast flow based on the rate of the primary multicast flow failing to satisfy the rate threshold.
5 . The method of claim 4 , wherein accepting the backup multicast flow comprises:
accepting multicast traffic with an outer source address that matches an address of the second network device forwarding the backup multicast flow.
6 . The method of claim 1 , wherein accepting the primary multicast flow comprises:
accepting multicast traffic with an outer source address that matches an address of the first network device forwarding the primary multicast flow.
7 . The method of claim 1 , wherein the network device is a service leaf network device or a data center interconnect gateway.
8 . A network device, comprising:
one or more memories; and
one or more processors to:
receive a first redundant multicast flow indication from a first network device and a second redundant multicast flow indication from a second network device,
wherein the first redundant multicast flow indication includes a first virtual extensible local area network (VXLAN) network identifier (VNI) or a first source VXLAN tunnel endpoint (VTEP) identifier and the second redundant multicast flow indication includes a second VNI or a second source VTEP identifier, and
wherein one or more of the first redundant multicast flow indication and the second redundant multicast flow indication is a Type 10 selective-provider multicast service interface (S-PMSI) route identifier;
designate a primary multicast flow based on the first redundant multicast flow indication;
designate a backup multicast flow based on the second redundant multicast flow indication;
accept the primary multicast flow; and
monitor a rate of the primary multicast flow.
9 . The network device of claim 8 , wherein the first network device is connected to a source of the primary multicast flow via a first protocol independent multicast (PIM) gateway and the second network device is connected to the source of the backup multicast flow via a second PIM gateway.
10 . The network device of claim 8 , wherein the first network device and the second network device communicate with the network device via an Ethernet virtual private network.
11 . The network device of claim 8 , wherein the one or more processors, to receive the first redundant multicast flow indication from the first network device and the second redundant multicast flow indication from the second network device, are to:
receive the first redundant multicast flow indication from a first advertisement generated by the first network device; and
receive the second redundant multicast flow indication from a second advertisement generated by the second network device.
12 . The network device of claim 8 , wherein the one or more processors, are further to:
broadcast a Type 6 selective multicast Ethernet tag (SMET) route based on receiving an Internet group management protocol (IGMP) report; and
wherein the one or more processors, to receive the first redundant multicast flow indication from the first network device and the second redundant multicast flow indication from a second network device, are to:
identify the first redundant multicast flow indication and the second redundant multicast flow indication based on receiving the IGMP report.
13 . The network device of claim 8 , wherein the one or more processors are further to:
accept the backup multicast flow based on the rate of the primary multicast flow failing to satisfy a rate threshold.
14 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a network device, cause the network device to:
receive a first redundant multicast flow indication from a first network device and a second redundant multicast flow indication from a second network device,
wherein the first redundant multicast flow indication includes a first virtual extensible local area network (VXLAN) network identifier (VNI) or a first source VXLAN tunnel endpoint (VTEP) identifier and the second redundant multicast flow indication includes a second VNI or a second source VTEP identifier, and
wherein one or more of the first redundant multicast flow indication and the second redundant multicast flow indication is a Type 10 selective-provider multicast service interface route identifier;
designate a primary multicast flow based on the first redundant multicast flow indication;
designate a backup multicast flow based on the second redundant multicast flow indication;
accept the primary multicast flow; and
monitor a rate of the primary multicast flow.
15 . The non-transitory computer-readable medium of claim 14 , wherein the one or more instructions further cause the network device to:
receive a report from a host device; and
identify the first redundant multicast flow indication and the second redundant multicast flow indication based on receiving the report.
16 . The non-transitory computer-readable medium of claim 14 , wherein the one or more instructions further cause the network device to:
continue to accept the primary multicast flow based on the rate of the primary multicast flow satisfying a rate threshold.
17 . The non-transitory computer-readable medium of claim 16 , wherein the one or more instructions further cause the network device to:
accept the backup multicast flow based on the rate of the primary multicast flow failing to satisfy the rate threshold.
18 . The non-transitory computer-readable medium of claim 14 , wherein the network device is a service leaf network device or a data center interconnect gateway.
19 . The non-transitory computer-readable medium of claim 14 , wherein the one or more instructions, to accept the backup multicast flow, causes the network device to:
accept multicast traffic with an outer source address that matches an address of the second network device forwarding the backup multicast flow.
20 . The non-transitory computer-readable medium of claim 14 , wherein the one or more instructions, to accept the backup multicast flow, causes the network device to:
accept multicast traffic with an outer source address that matches an address of the first network device forwarding the primary multicast flow.