Multicast traffic distribution in a multi-pod network environment
An example method for to multicast traffic distribution in a multi-pod network environment is provided and includes provisioning a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network, calculating a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pod, indexing with the hash into the block of multicast group addresses designated for inter-pod BUM traffic to derive a global multicast group identical for the broadcast domain across the plurality of pods, and associating a local multicast group at the translator with the derived global multicast group.
1. A method executed by a hardware translator in a multi-pod network environment, the hardware translator including a processor configured to execute instructions in the multi-pod network environment, the method comprising:
provisioning, at the processor, a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network;
calculating, at the processor, a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pods;
indexing, at the processor, with the hash into the block of multicast group addresses designated for interpod BUM traffic to derive a global multicast group identical for the BD across the plurality of pods; and
associating, at the processor, a local multicast group at the translator with the BD.
2. The method of claim 1 , wherein a Layer 2 encapsulation over a Layer 3 network is used within each pod, and the Layer 2 encapsulation over the Layer 3 network is not used between pods.
3. The method of claim 1 , wherein the BD is associated with the global multicast group between the plurality of pods and a separate local multicast group within each pod in the plurality of pods.
4. The method of claim 1 , wherein computing the hash comprises calculating the hash over a BD parameter common to the plurality of pods.
5. The method of claim 4 , wherein the BD parameter comprises a BD name.
6. The method of claim 4 , wherein the BD parameter comprises a BD membership map including a list of the plurality of pods over which the BD extends.
7. The method of claim 6 , wherein the BD membership map comprises a set of combinations of site identifier and pod identifier of each one of the plurality of pods.
8. The method of claim 1 , wherein each pod comprises a fabric including a plurality of spine switches interconnected to leaf switches, wherein the leaf switches are connected to endpoints that generate or terminate packets in the network.
9. The method of claim 1 , further comprising:
receiving a packet with an overlay header indicating a BD and an underlay header indicating the global multicast group;
determining the local multicast group corresponding to the BD indicated in the overlay header;
rewriting the underlay header of the packet to replace the global multicast group with the local multicast group; and
distributing the packet among locally interested endpoints.
10. The method of claim 1 , further comprising:
receiving a packet with an underlay header indicating the local multicast group and an overlay header indicating the BD;
determining the hash corresponding to the BD;
indexing with the hash into the global multicast group;
rewriting the underlay header to replace the local multicast group with the global multicast group; and
distributing the packet among interested pods.
11. Non-transitory tangible media that includes instructions for execution, which when executed by a processor of a translator in a multi-pod network environment, is operable to perform operations comprising:
provisioning, at the processor, a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network;
calculating, at the processor, a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pods;
indexing, at the processor, with the hash into the block of multicast group addresses designated for interpod BUM traffic to derive a global multicast group identical for the broadcast domain across the plurality of pods; and
associating, at the processor, a local multicast group at the translator with the BD.
12. The media of claim 11 , wherein a Layer 2 encapsulation over a Layer 3 network is used within each pod, and the Layer 2 encapsulation over the Layer 3 network is not used between pods.
13. The media of claim 11 , wherein computing the hash comprises calculating the hash over a BD parameter common to the plurality of pods.
14. The media of claim 11 , wherein the operations further comprise:
receiving a packet with an overlay header indicating a BD and an underlay header indicating the global multicast group;
determining the local multicast group corresponding to the BD indicated in the overlay header;
rewriting the underlay header of the packet to replace the global multicast group with the local multicast group; and
distributing the packet among locally interested endpoints.
15. The media of claim 11 , wherein the operations further comprise:
receiving a packet with an underlay header indicating the local multicast group and an overlay header indicating the BD;
determining the hash corresponding to the BD;
indexing with the hash into the global multicast group;
rewriting the underlay header to replace the local multicast group with the global multicast group; and
distributing the packet among interested pods.
16. An apparatus in a multi-pod network environment, comprising:
a memory element for storing data; and
a processor, wherein the processor executes instructions associated with the data, wherein the processor and the memory element cooperate, such that the apparatus is configured for:
provisioning a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network;
calculating a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pods;
indexing with the hash into the block of multicast group addresses designated for inter-pod BUM traffic to derive a global multicast group identical for the broadcast domain across the plurality of pods; and
associating a local multicast group at the translator with the BD.
17. The apparatus of claim 16 , wherein a Layer 2 encapsulation over a Layer 3 network is used within each pod, and the Layer 2 encapsulation over the Layer 3 network is not used between pods.
18. The apparatus of claim 16 , wherein computing the hash comprises calculating the hash over a BD parameter common to the plurality of pods.
19. The apparatus of claim 16 , further configured for:
receiving a packet with an overlay header indicating a BD and an underlay header indicating the global multicast group;
determining the local multicast group corresponding to the BD indicated in the overlay header;
rewriting the underlay header of the packet to replace the global multicast group with the local multicast group; and
distributing the packet among locally interested endpoints.
20. The apparatus of claim 16 , further configured for:
receiving a packet with an underlay header indicating the local multicast group and an overlay header indicating the BD;
determining the hash corresponding to the BD;
indexing with the hash into the global multicast group;
rewriting the underlay header to replace the local multicast group with the global multicast group; and
distributing the packet among interested pods.