Source-initiated distribution of spine node identifiers of preferred spine nodes for use in multicast path selection
A router node may be configured for communication of multicast traffic in a network fabric which may include a plurality of spine nodes interconnected to a plurality of leaf nodes. The router node may be configured as one of the leaf nodes and serve as a first hop router for multicast traffic. At the router node, a message for flooding the network fabric may be sent based on an indication of communication of multicast traffic for a multicast group from a source device. The message may include at least one spine node identifier of at least one preferred spine node joined to the multicast group at the router node. The message may be for indicating, to at least one of the leaf nodes, to prioritize joining to the multicast group at the at least one preferred spine node according to at least one spine node identifier.
1. A method comprising:
at a router node configured for communication of multicast traffic in a network fabric comprising a plurality of spine nodes interconnected to a plurality of leaf nodes, and further configured as one of the leaf nodes,
sending a message for flooding the network fabric to communicate the message to other leaf nodes in the network fabric based on identifying an indication of communication of multicast traffic for a multicast group from a source device, the message including at least one spine node identifier of at least one excluded spine node to exclude from joining to the multicast group for the communication of the multicast traffic; and
forwarding the multicast traffic for the multicast group to one of the plurality of spine nodes other than the at least one excluded spine node indicated by the at least one spine node identifier.
2. The method of claim 1 , wherein the message is for indicating, to at least one of the other leaf nodes, to prohibit joining to the multicast group at the at least one excluded spine node according to the at least one spine node identifier.
3. The method of claim 1 , wherein the at least one spine node identifier of the at least one excluded spine node comprises a plurality of spine node identifiers of a plurality of excluded spine nodes to exclude from joining to the multicast group for the communication of the multicast traffic.
4. The method of claim 1 , wherein the message further includes at least one of a source address of the source device and a multicast group address of the multicast group for the multicast traffic.
5. The method of claim 1 , wherein the message further includes at least one preferred spine node identifier of at least one preferred spine node that is selected for joining to the multicast group for the communication of the multicast traffic.
6. The method of claim 1 , wherein a Protocol Independent Multicast (PIM) Flooding Mechanism (PFM) is used in the sending of the message for flooding the network fabric.
7. The method of claim 1 , wherein the at least one spine node identifier is included in the message as a type-length-value (TLV).
8. The method of claim 1 , wherein the router node is operative to serve as a first hop router for the multicast traffic of the multicast group.
9. The method of claim 1 , wherein the router node is part of an Internet Protocol (IP) network media data fabric which has the plurality of spine nodes interconnected to the plurality of leaf nodes as a plurality of spine switches interconnected to a plurality of leaf switches.
10. A router node comprising:
one or more processors;
a plurality of interfaces configured to connect in a network fabric comprising a plurality of spine nodes interconnected to a plurality of leaf nodes, wherein the router node is configured as one of the leaf nodes;
the one or more processors being configured to:
send, via an interface, a message for flooding the network fabric to communicate the message to other leaf nodes in the network fabric based on an indication of communication of multicast traffic for a multicast group from a source device, the message including at least one spine node identifier of at least one excluded spine node to exclude from joining to the multicast group for the communication of the multicast traffic; and
forward the multicast traffic for the multicast group to one of the plurality of spine nodes other than the at least one excluded spine node indicated by the at least one spine node identifier.
11. The router node of claim 10 , which is operative to serve as a first hop router for the communication of the multicast traffic, and wherein the message is for indicating, to at least one of the other leaf nodes, to prohibit joining to the multicast group at the at least one excluded spine node indicated by the at least one spine node identifier.
12. The router node of claim 10 , wherein the at least one spine node identifier of the at least one excluded spine node comprises a plurality of spine node identifiers of a plurality of excluded spine nodes to exclude from joining to the multicast group for the communication of the multicast traffic.
13. The router node of claim 10 , wherein the message further includes at least one preferred spine node identifier of at least one preferred spine node that is selected for joining to the multicast group for the communication of the multicast traffic.
14. The router node of claim 10 , which is part of an Internet Protocol (IP) network media data fabric which has the plurality of spine nodes interconnected to the plurality of leaf nodes as a plurality of spine switches interconnected to a plurality of leaf switches.
15. A method comprising:
at a router node configured for communication of multicast traffic in a network fabric comprising a plurality of spine nodes interconnected to a plurality of leaf nodes, and further configured as one of the leaf nodes,
receiving a message which is flooded in the network fabric by an originating leaf node which is operative to forward multicast traffic for a multicast group from a source device, the message including at least one spine node identifier of at least one excluded spine node;
receiving, from a receiver device, a request to join to the multicast group for the communication of the multicast traffic; and
joining to the multicast group at one of the plurality of spine nodes other than the at least one excluded spine node indicated by the at least one spine node identifier for the communication of the multicast traffic to the receiver device.
16. The method of claim 15 , further comprising:
prohibiting joining to the multicast group at the at least one excluded spine node according to the at least one spine node identifier.
17. The method of claim 15 , wherein the message further includes at least one preferred spine node identifier of at least one preferred spine node that is selected for joining to the multicast group for the communication of the multicast traffic, and the method further comprises:
prioritizing joining to the multicast group at the at least one preferred spine node according to the at least one preferred spine node identifier for the communication of the multicast traffic.
18. The method of claim 15 , wherein the message which is flooded in the network fabric is flooded in accordance with a Protocol Independent Multicast (PIM) Flooding Mechanism (PFM).
19. The method of claim 15 , wherein the router node serves as a last hop router for the multicast traffic of the multicast group.
20. The method of claim 15 , wherein the router node is part of an Internet Protocol (IP) network media data fabric which as the plurality of spine nodes interconnected to the plurality of leaf nodes as a plurality of spine switches interconnected to a plurality of leaf switches.