Multicast: IGMP, PIM, and Architecture

April 15, 2026·3 min read·567 words

Multicast sends the same packet to a group of receivers without duplicating it. It is essential for video (IPTV, Zoom multicast, internal training), financial markets (market data), IoT, and ACM services such as NetBoot. The architecture is based on IGMP for end hosts and PIM for routing. Comprehensive 2026 guide.

IGMP (Internet Group Management Protocol)

Protocol between an end host and a router/switch
IGMPv2 (RFC 2236): the standard for 20 years
IGMPv3 (RFC 3376): adds Source-Specific Multicast (SSM)
Messages: Query (the router sends a request), Report (the host requests to join), Leave (the host leaves)
Query interval: 125s by default

IGMP Snooping (Switches)

The L2 switch monitors IGMP and forwards multicast traffic only to ports with receivers:

Without snooping: multicast is broadcast across the VLAN, causing saturation
With snooping: traffic is forwarded only to requesting ports
Required for every multicast deployment
Cisco/Juniper: enabled by default on Catalyst/EX platforms

PIM (Protocol Independent Multicast)

PIM Sparse Mode (PIM-SM)

Standard for enterprise deployments
Rendezvous Point (RP): central router for each group
Traffic flow: Source → RP → Receivers
Switchover to the SPT (Shortest Path Tree) after the first packet
RP placement: geographically central to minimize latency

PIM Dense Mode (PIM-DM)

Flood and prune: sends traffic everywhere and then prunes it
Inefficient at scale
Obsolete; do not use

Bidirectional PIM (PIM-BiDir)

Bidirectional: sources and receivers use the same tree
Simpler, but less flexible
Use case: peer-to-peer multicast for financial markets and trading

Source-Specific Multicast (SSM)

The receiver specifies the group source (S,G)
No RP is required
Simplifies operations and improves security by preventing unauthorized sources
IANA range: 232.0.0.0/8
Requires IGMPv3

Multicast Addresses

224.0.0.0-224.0.0.255: link-local (OSPF 224.0.0.5, HSRP 224.0.0.2)
224.0.1.0-238.255.255.255: globally scoped
232.0.0.0/8: SSM
239.0.0.0/8: administratively scoped (RFC 2365), for private enterprise use
L2 mapping: last 23 bits → 01:00:5E:xx:xx:xx

RP (Rendezvous Point) Selection

Static RP

Manual configuration: all routers point to the same RP IP address
Simple, but with no native redundancy
Add HSRP/VRRP to the RP for HA

Auto-RP (Cisco)

RP candidates advertise through 224.0.1.39
The Mapping Agent selects the RP and distributes the mapping through 224.0.1.40
Legacy Cisco-only solution

BSR (Bootstrap Router)

IETF standard
RP candidates send their information to the BSR
The BSR distributes the RP-to-group mapping table
Multi-vendor

Anycast RP

Multiple RPs share the same IP address
Unicast routing directs traffic to the nearest RP
MSDP (Multicast Source Discovery Protocol) synchronizes sources between RPs
HA and load distribution

Cisco PIM-SM Configuration

ip multicast-routing distributed
interface Vlan 10 ; ip pim sparse-mode
ip pim rp-address 10.0.0.1: static RP
ip pim bsr-candidate Loopback0: BSR candidate
ip pim rp-candidate Loopback0: RP candidate

Enterprise Use Cases

Internal IPTV: corporate video distributed to N rooms
Financial trading: market data (Bloomberg and Reuters multicast feeds)
IoT: broadcast discovery (mDNS/SSDP)
Gaming events: high-quality live streams
Training: large-scale internal webinars

Troubleshooting

show ip mroute: multicast routing table
show ip pim interface: PIM status on interfaces
show ip pim rp: current RP for each group
show ip igmp groups: IGMP groups joined on each port
show ip mroute 232.1.1.1: status for a specific group
mtrace: multicast traceroute

Common Pitfalls

IGMP snooping disabled: all multicast traffic is broadcast
RP unreachable: no traffic due to a failed RPF check
IGMP v2/v3 mismatch between the host and switch
PIM flooding in DM: disable it everywhere

Order from OPTINOC

PIM-SM/SSM multicast design and Cisco/Juniper configuration. Optimized IGMP snooping. Capacity planning for corporate IPTV and trading environments. Quote within 48 hours.