Layer 2 multicast is about how switches forward multicast frames based on MAC addresses, and how flooding is limited with IGMP snooping.

Facts / key topics

Why does it exist?

Multicast is one-to-many. The switch does not understand IP multicast – only MAC. Without control, multicast floods to all ports: unnecessary load on hosts, wasted bandwidth, “broadcast-like” behaviour. Typical scenarios: IPTV, video streams, financial feeds, routing protocols (OSPF, EIGRP use multicast).

How is it solved?

Step by step

  1. Multicast frame arrives: Ethernet frame with a multicast MAC; the switch doesn’t know the group yet → flooding
  2. IGMP snooping (if enabled): the switch sniffs IGMP joins/leaves and builds an L2 multicast table (MAC → ports)
  3. Normal operation: multicast frames are forwarded only to member ports
  4. Leave/timeout: host sends IGMP Leave → port removed from the group (CCNP: querier failover, robustness)

Key terminology

Term Explanation
Multicast MAC MAC representing a multicast group
Flooding Frame sent out all ports in the VLAN
IGMP snooping Switch “listens” to IGMP to control forwarding
Querier Device that sends IGMP queries
Multicast group Logical group of receivers

Elements

Element Description CCNA CCNP
Multicast flooding Default switch behaviour
MAC mapping IP → multicast MAC
IGMP snooping Intelligent forwarding
IGMP querier L2 querier on the switch
Fast leave Fast port removal

Dependencies & special considerations

Configuration (Cisco IOS / IOS-XE)

! Basic (CCNA)
ip igmp snooping
! Advanced (CCNP)
ip igmp snooping vlan 10
ip igmp snooping querier
! Verification
show ip igmp snooping
show ip igmp snooping groups

Troubleshooting

show mac address-table multicast
show ip igmp snooping groups

Design & best practices

Exam tips ⚠️

Quick summary