VXLAN Mastery · Lesson 02B · Deep dive

Underlay multicast: send once, the network copies

The second way to carry BUM traffic: map each VNI to a multicast group, let VTEPs join, and have the underlay replicate. This page shows how the tree is built, how one packet branches, what the outer headers look like, and how it compares with ingress replication.

📘 Builds on Lesson 2⏱ ~40 minutes🖱 Two animated walkthroughs🧠 Quiz and checklist
Progress is saved in this browser
1Starter⏱ 4 min

Underlay multicast: the network makes the copies

With underlay multicast, the source leaf sends one VXLAN packet whose outer destination is a multicast group address. The underlay routers (spines) already know which leaves are interested in that group, so they replicate the packet at the branching points of a tree.

📻 Plain-English analogy

A radio station transmits once. Everyone tuned to that channel hears it. The station does not call each listener. Leaves “tune in” to a group (a channel) by joining it. The spine is the transmitter tower that repeats the signal to everyone tuned in.

🧩 In VXLAN terms

Each VNI is mapped to a group such as 239.1.1.100. Every VTEP that has the VNI joins that group. A BUM frame becomes one packet to 239.1.1.100 and the tree delivers it to all members.

The shape of the traffic

1 packet leaves the source, the spine copies it
Leaf 1sends 1 packet Spinecopies where tree branches Leaf 2 (joined)Leaf 3 (joined)Leaf 4 (joined)Leaf 5 (not joined)
Key contrast with Lesson 2A: in ingress replication the source leaf sends N − 1 packets. Here it sends 1. The price is that the underlay must run multicast routing (usually PIM).
2Starter⏱ 6 min

Mapping VNIs to multicast groups

In this example each VNI is configured with an administratively scoped multicast group in 239.0.0.0/8; other address choices depend on network design and reserved-address rules. For each shared VNI, its group mapping must be consistent across participating VTEPs. You can give each VNI its own group, or let several VNIs share a group.

Try the mapping

See who receives the BUM frame

VNI membership: 10100 = Leaf 1, 2, 3 · 20200 = Leaf 1, 3 · 30300 = Leaf 3, 4 · 40400 = Leaf 2, 4

One group per VNI

More selective delivery: only VTEPs joined to that group should receive its VXLAN BUM traffic when multicast forwarding state and filtering are correct. Costs more multicast state (one mroute entry per group) on the spines.

Shared groups

Saves spine state, but a leaf that joined the group for another VNI still receives the packet. It receives unnecessary multicast traffic and discards packets for unsupported VNIs (potentially in hardware). This can consume unnecessary bandwidth; the receiving device may discard the packet in hardware, so CPU cost depends on the implementation.

3Intermediate⏱ 8 min

Before any frame moves: joining the group

Multicast delivery requires suitable forwarding state. A VTEP can signal group membership using IGMP toward an upstream multicast router; a PIM-capable leaf/router may instead send PIM joins. This specific walkthrough assumes the leaf VTEPs run PIM-SM and the spine is the Rendezvous Point (RP). Press Next step to see that particular design.

Build the multicast tree for VNI 10100

PIM control message (this example); IGMP possible at VTEP edgeMulticast VXLAN packet
Multicast underlay (PIM sparse mode) Spine = RPPIM rendezvous point Leaf 1VTEP 10.0.0.1Leaf 2VTEP 10.0.0.2Leaf 3VTEP 10.0.0.3Leaf 4VTEP 10.0.0.4Host A00:AA…:01Host B00:BB…:02Host C00:CC…:03Host D00:DD…:04

Packets in this step

In this PIM-SM ASM example, the join propagates hop-by-hop toward the RP: each router that receives a PIM join adds the incoming interface to the group’s outgoing interface list (OIL). After a successful reverse-path-forwarding (RPF) check, eligible OIL interfaces receive copies; the packet is not sent back out its incoming interface.
4Intermediate⏱ 8 min

Packet-by-packet: the same ARP broadcast, with multicast

The tree from chapter 3 is already built. Host A ARPs for Host B. Compare with Lesson 2A: how many packets leave Leaf 1 now?

Follow one broadcast through the multicast tree

Ethernet frame on a host linkVXLAN multicast (outer dst = group)VXLAN unicast
Multicast underlay (PIM sparse mode) Spine = RPreplicates by mroute Leaf 1VTEP 10.0.0.1Leaf 2VTEP 10.0.0.2Leaf 3VTEP 10.0.0.3Leaf 4VTEP 10.0.0.4Host A00:AA…:01Host B00:BB…:02Host C00:CC…:03Host D00:DD…:04

Packets in this step

Spot the pattern: Leaf 1’s uplink carries the broadcast once. The spine does the fan-out. The more VTEPs, the bigger the saving at the source.
5Intermediate⏱ 6 min

Inside the multicast packet

Compared with unicast VXLAN, the key changes are the outer multicast destination IP and corresponding next-hop/link-layer destination information; routing behavior is multicast rather than unicast. The outer destination IP is the group, and the outer destination MAC is the multicast MAC derived from it.

FieldValue for VNI 10100, group 239.1.1.100
Outer Ethernet dst (derived from the group)01:00:5E:01:01:64
Outer Ethernet src (Leaf 1)0C:01:01:01:01:01
Outer IP src (source VTEP)10.0.0.1
Outer IP dst (group)239.1.1.100
UDP src → dst52814 → 4789
VNI10100
Inner Ethernet dst → srcFF:FF:FF:FF:FF:FF ← 00:AA:AA:AA:AA:01
PayloadARP request

Group IP → multicast MAC calculator

Type any group in 224.0.0.0–239.255.255.255
The rule: multicast MAC = 01:00:5E + the low 23 bits of the group IP. The top bit of the second IP octet is dropped, so 32 different groups share one MAC. For example, “239.1.1.100” and “238.129.1.100” map to the same multicast Ethernet MAC because the top four IP bits and one additional bit are not represented.
6Mastery⏱ 6 min

PIM designs and the comparison with ingress replication

PIM sparse mode (ASM)

In PIM-SM Any-Source Multicast (ASM), receivers establish shared-tree state toward an RP; first-hop routers can register new sources. This lab models ASM, not the only possible multicast design.

Anycast RP

Multiple RPs can provide RP redundancy with anycast addressing, but the exact failover and load distribution depend on topology and routing. Source-registration synchronization mechanisms (such as MSDP or PIM anycast-RP procedures) depend on the anycast-RP design.

Bidirectional PIM

Bidirectional PIM uses a shared bidirectional tree and avoids the same per-source forwarding state used by traditional shortest-path-tree switching. It can suit many-source multicast designs, but requires appropriate platform support.

Replication calculator

Change the numbers
Source uplink packets/s, ingress replication
Source uplink packets/s, multicast
Illustrative shared-tree (*,G) entries for groups
Ingress replicationUnderlay multicast
Packets leaving the source per BUM frameN − 11
Who replicatesSource leafSpines (and any router on the tree)
Underlay requirementUnicast routing onlyMulticast forwarding and membership signaling (for example PIM-SM ASM and IGMP)
Extra stateFlood list per VNI on leavesMulticast forwarding state on participating routers; (*,G) and/or (S,G) by design
OperationsSimpleMore to design and troubleshoot
Best fitSmall to medium fabrics, WAN or multi-vendorLarge flat VNIs with heavy BUM, if multicast is already trusted
7Mastery⏱ 6 min

Configuration and troubleshooting

Two parts: the VTEP maps a VNI to a group, and the underlay runs PIM so the group has a tree.

    Illustrative only: these show the key lines, not a full configuration. Multicast-underlay support and syntax vary by vendor and software version (some platforms favour ingress replication), so check your vendor’s documentation.

    What’s wrong? Pick a symptom

    Troubleshooting helper
    Click a symptom to see the most likely cause.
    ✓Check yourself⏱ 5 min

    Test what you learned

    Eight questions, each with an explanation.

    Mastery checklist

    Tick each one when you can explain it in your own words.

    Cheat sheet

    • Source sends 1 packet to the group address
    • Each VNI maps to a group; same mapping everywhere
    • Leaf VTEPs can signal membership using IGMP or PIM, depending on design; PIM routers build multicast forwarding state
    • Outer dst MAC = 01:00:5E + low 23 bits of the group
    • After RPF succeeds, a multicast router copies to eligible OIL interfaces, excluding incoming
    • Shared groups cause wasted deliveries

    Next

    Next up is Lesson 03: the EVPN control plane (MP-BGP, route distinguishers, route targets and route types), which can also remove most flooding in the first place.