Study guide
13.1 IP Multicast Addressing, Group Management (IGMPv1/v2/v3) & IGMP Snooping
CCNP Enterprise ENCOR 350-401
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Enterprise Architecture & Hierarchical Design
1.1 Enterprise Network Design Models & Hierarchical Campus Architecture 1.2 On-Premises, Cloud & Hybrid Infrastructure Deployment Models 1.3 Hardware Switching Architecture & Packet Forwarding
2 Chapter 2: Enterprise Quality of Service (QoS)
2.1 QoS Components: Classification, Marking & Trust Boundaries 2.2 QoS Policy: Queuing, Shaping, Policing & Interpreting MQC Output
3 Chapter 3: Software-Defined WAN (Catalyst SD-WAN)
3.1 Cisco Catalyst SD-WAN Architecture & Orchestration 3.2 SD-WAN Policies, Traffic Engineering & Application-Aware Routing
4 Chapter 4: Software-Defined Access (Catalyst SD-Access)
4.1 Catalyst SD-Access Fabric Architecture & Plane Separation 4.2 Cisco TrustSec, Security Group Tags (SGT), SXP & MACsec
5 Chapter 5: Device & Data Path Virtualization
5.1 Server & Network Device Virtualization 5.2 VRF-Lite & Virtual Routing Multi-Tenancy 5.3 GRE & IPsec Tunnel Virtualization Mechanics
6 Chapter 6: Network Virtualization & Overlay Technologies
6.1 LISP Architecture & EID-to-RLOC Mapping Mechanics 6.2 VXLAN & EVPN Overlay Architecture
7 Chapter 7: Layer 2 Infrastructure & Switching
7.1 VLANs, 802.1Q Trunking & VTPv3 7.2 Spanning Tree Protocol Mechanics 7.3 Advanced STP Protection Mechanisms 7.4 EtherChannel Link Aggregation
8 Chapter 8: Layer 3 Routing Foundations & EIGRP
8.1 IP Routing Foundations & Administrative Distance 8.2 Enhanced Interior Gateway Routing Protocol (EIGRP)
9 Chapter 9: OSPFv2 & OSPFv3 Operations
9.1 OSPFv2 Architecture & Neighbor State Machine 9.2 OSPF LSA Types & Multi-Area Design 9.3 OSPFv3 for IPv4 and IPv6 Address Families
10 Chapter 10: Border Gateway Protocol (BGP)
10.1 BGP Architecture, Neighbor States & Peering 10.2 BGP Path Attributes & Best Path Selection Algorithm
11 Chapter 11: Policy-Based Routing & Route Redistribution
11.1 Policy-Based Routing (PBR) & Route Maps 11.2 Route Redistribution & Loop Prevention
12 Chapter 12: IP Services & High Availability
12.1 First Hop Redundancy Protocols (HSRP, VRRP & GLBP) 12.2 Network Time Protocol (NTPv4) & Precision Time Protocol (PTP) 12.3 Network Address Translation (NAT/PAT) & VRF-Aware NAT
13 Chapter 13: IP Multicast Operations
13.1 IP Multicast Addressing, Group Management (IGMPv1/v2/v3) & IGMP Snooping 13.2 Protocol Independent Multicast (PIM-SM, PIM-SSM & Bidir-PIM) 13.3 Rendezvous Point (RP) Distribution Mechanisms
14 Chapter 14: Network Assurance & Monitoring
14.1 Diagnostic Utilities, Conditional Debugging & Path MTU Discovery 14.2 Syslog Architecture, Logging Facilities & Severity Levels 14.3 SNMPv1/v2c/v3 Security & Flexible NetFlow (FNF) Architecture 14.4 Switched Port Analyzer (SPAN, RSPAN, ERSPAN) & IP SLA Object Tracking
15 Chapter 15: Catalyst Center Assurance & Controller Operations
15.1 Cisco Catalyst Center (DNA Center) Assurance & AI Network Analytics 15.2 Cisco Catalyst Center Device Onboarding & Software Image Management (SWIM)
16 Chapter 16: Enterprise Security & Access Control
16.1 Device Hardening, AAA Architecture & RADIUS/TACACS+ 16.2 Access Control Lists (ACLs) for Infrastructure Security 16.3 Control Plane Policing (CoPP) & Control Plane Protection (CPPr) 16.4 Layer 2 Infrastructure Security Features 16.5 IEEE 802.1X Port-Based Authentication & MAB
17 Chapter 17: Threat Defense & API Security
17.1 Enterprise VPN Technologies (DMVPN Phase 1/2/3 & FlexVPN) 17.2 Next-Generation Threat Defense & Secure Access Service Edge (SASE)
18 Chapter 18: Network Automation, Programmability & Data Modeling
18.1 Python Fundamentals for Network Engineers & Cisco Libraries 18.2 YANG Data Modeling Language (RFC 6020/7950) & Model Types 18.3 REST API Architecture, HTTP Verbs, Security & Cisco Controller APIs 18.4 Model-Driven Telemetry (MDT) & NETCONF/RESTCONF Operations
19 Chapter 19: Orchestration, EEM & AI Operations
19.1 Configuration Management & Infrastructure as Code (Ansible & Terraform) 19.2 Cisco Embedded Event Manager (EEM) & Intent-Based Networking
13.1 IP Multicast Addressing, Group Management (IGMPv1/v2/v3) & IGMP Snooping
Key Takeaways Explain This Topic AI
IPv4 Multicast utilizes Class D address space (224.0.0.0/4, range 224.0.0.0 to 239.255.255.255), segmented into Link-Local Reserved (224.0.0.0/24), Internetwork Control (224.0.1.0/24), Source-Specific Multicast (232.0.0.0/8), and Administratively Scoped Private Multicast (239.0.0.0/8).
Layer 2 Multicast MAC mapping maps the low-order 23 bits of the IPv4 multicast address into the IANA MAC prefix 01:00:5E:00:00:00 through 01:00:5E:7F:FF:FF; discarding 5 high-order bits results in an exact 32:1 IP-to-MAC address ambiguity ratio.
IGMPv1 (RFC 1112) provides basic Join/Query functions with a 3-minute timeout; IGMPv2 (RFC 2236) adds Leave Group messages (224.0.0.2), Group-Specific Queries, Max Response Time, and lowest-IP Querier election; IGMPv3 (RFC 3376) adds Source Filtering (INCLUDE/EXCLUDE) sent to 224.0.0.22 to support Source-Specific Multicast (SSM).
IGMP Snooping constrains Layer 2 flooding by parsing IGMP membership reports to dynamically populate the Multicast Forwarding Database (MFDB), forwarding multicast traffic strictly to receiver ports and mrouter uplink ports.
An IGMP Snooping Querier generates periodic General Queries on Layer 2 switches within isolated VLANs lacking a Layer 3 multicast router, maintaining switch MFDB table states and preventing report timeouts.
Last updated: August 2026
13.1 IP Multicast Addressing, Group Management (IGMPv1/v2/v3) & IGMP Snooping
Core Blueprint Focus: Cisco 350-401 ENCOR v1.2 topic 3.3.d (describe multicast protocols such as RPF check, PIM SM, IGMP v2/v3, SSM, bidir, and MSDP) requires candidates to configure and verify IP multicast operations, including IPv4 multicast addressing, Layer 2 MAC address mapping calculations, Internet Group Management Protocol (IGMP) versions 1, 2, and 3, IGMP Snooping, and IGMP Querier functionality.
In traditional IP networking, data transmission follows one of three fundamental communication paradigms:
Unicast (One-to-One): A single source transmits separate, individual streams to each destination host. Transmitting a 10 Mbps video stream to 1,000 users requires 10 Gbps of outbound bandwidth from the server and saturates upstream WAN links with duplicate packets.
Broadcast (One-to-All): A single source transmits a single packet to every host on the Layer 2/3 broadcast domain ( 255.255.255.255 ). Every host must interrupt its CPU to process the packet, creating massive processing overhead for uninterested receivers.
Multicast (One-to-Many / Many-to-Many): A single source transmits a single data stream addressed to a logical group address. Routers replicate packets only at network branching points where downstream receivers have explicitly requested the stream, maximizing bandwidth efficiency and offloading server compute. +-----------------------------------------------------------------------------------+
- | UNICAST VS. MULTICAST BANDWIDTH REPLICATION MODEL |
- +-----------------------------------------------------------------------------------+
- | |
- | UNICAST (1:1) - 3 Streams (3 x 10 Mbps = 30 Mbps on Server Link) |
- | [Source] ===== 30 Mbps =====> [Router 1] ===== 20 Mbps =====> [Router 2] |
- | | / \ |
- | 10 Mbps 10 Mbps 10 Mbps |
- | v v v |
- | [Host A] [Host B] [Host C] |
- | |
- | MULTICAST (1:N) - 1 Stream (10 Mbps everywhere until branching points) |
- | [Source] ===== 10 Mbps =====> [Router 1] ===== 10 Mbps =====> [Router 2] |
- | | / \ |
- | 10 Mbps 10 Mbps 10 Mbps |
- | v v v |
- | [Host A] [Host B] [Host C] |
- +-----------------------------------------------------------------------------------+
1. IPv4 Multicast Addressing Architecture (Class D)
IPv4 addresses are divided into classes based on the high-order bits of the first octet. Class D is exclusively reserved for IP multicast, designated by the prefix 224.0.0.0/4 .
In binary notation, every Class D multicast address begins with the fixed 4-bit prefix 1110 : Binary: 11100000.00000000.00000000.00000000 to 11101111.11111111.11111111.11111111 \text{Binary: } \mathbf{1110}0000.00000000.00000000.00000000 \text{ to } \mathbf{1110}1111.11111111.11111111.11111111 Binary: 1110 0000.00000000.00000000.00000000 to 1110 1111.11111111.11111111.11111111 Decimal: 224.0.0.0 to 239.255.255.255 \text{Decimal: } 224.0.0.0 \text{ to } 239.255.255.255 Decimal: 224.0.0.0 to 239.255.255.255
Because multicast addresses represent an arbitrary group of receivers rather than an individual network interface, multicast addresses are destination addresses only . A host or router never uses a Class D address as the source IP address in an IP header. +-----------------------------------------------------------------------------------+
- | CLASS D MULTICAST ADDRESS RANGES |
- +-----------------------------------------------------------------------------------+
- | |
- | 224.0.0.0 224.0.1.0 232.0.0.0 233.0.0.0 239.0.0.0 |
- | | | | | | |
- | v v v v v |
- | [Link-Local] [Internetwork] [SSM] [GLOP] [Administratively|
- | [Reserved ] [Control ] [Source-Specific] [AS-Based] [Scoped / Private|
- | 224.0.0.255 224.0.1.255 232.255.255.255 233.255.255.255 239.255.255.255 |
- +-----------------------------------------------------------------------------------+
- IANA Multicast Address Allocations
Address Range Block Name Routable? Purpose & Well-Known Assignments
224.0.0.0/24 ; ( 224.0.0.0 – 224.0.0.255 ) Link-Local Reserved NO (TTL=1 enforced) Reserved for local network control protocols on the local physical subnet. Routers must never forward these packets across a Layer 3 boundary.; • 224.0.0.1 : All Systems / All Hosts on subnet; • 224.0.0.2 : All Multicast Routers on subnet; • 224.0.0.5 : OSPF All Routers; • 224.0.0.6 : OSPF Designated Routers (DR/BDR); • 224.0.0.9 : RIPv2 Routers; • 224.0.0.10 : EIGRP Routers; • 224.0.0.13 : PIMv2 Routers; • 224.0.0.18 : VRRP Advertisements; • 224.0.0.22 : IGMPv3 Membership Reports; • 224.0.0.102 : HSRPv2 and GLBP
224.0.1.0/24 ; ( 224.0.1.0 – 224.0.1.255 ) Internetwork Control Block YES Global network control protocols routable across autonomous systems.; • 224.0.1.1 : Network Time Protocol (NTP); • 224.0.1.39 : Cisco Auto-RP Candidate-RP-Announce; • 224.0.1.40 : Cisco Auto-RP RP-Mapping-Discovery
224.0.2.0 – 224.1.255.255 AD-HOC Group 1 YES Globally routed applications and enterprise streaming services.
224.2.0.0/16 SDP / SAP Block YES Session Announcement Protocol (SAP) and Session Description Protocol (SDP) multimedia conference directory listings.
232.0.0.0/8 ; ( 232.0.0.0 – 232.255.255.255 ) Source-Specific Multicast (SSM) YES Standardized in RFC 4607 for PIM-SSM with IGMPv3. Bypasses shared Rendezvous Points (RP) entirely.
233.0.0.0/8 GLOP Addressing YES RFC 3180 allocation mapping 16-bit Autonomous System Numbers (ASN) into the middle two octets: 233.AS_high.AS_low.0/24 . (e.g., AS 65000 -> 0xFDE8 -> 253.232 -> 233.253.232.0/24 ).
234.0.0.0/8 Unicast-Prefix-Based YES RFC 6034 dynamic mapping of IPv4 unicast prefixes into multicast addresses.
239.0.0.0/8 ; ( 239.0.0.0 – 239.255.255.255 ) Administratively Scoped (Private) YES (Internal Only) RFC 2365 private enterprise multicast space (the multicast equivalent of RFC 1918 unicast space). Sub-ranges:; • 239.255.0.0/16 : Local Site-Scoped (e.g., 239.255.0.0/16 ); • 239.192.0.0/14 : Organization-Local Scope
2. Layer 2 Multicast MAC Address Mapping & The 32:1 Overlap Math
Ethernet network interface cards (NICs) filter traffic at Layer 2 based on destination MAC addresses to avoid interrupting the host CPU for unwanted frames. For IP multicast to operate over Ethernet, Layer 3 IPv4 multicast addresses must be dynamically mapped into Layer 2 Ethernet MAC addresses.
The IANA MAC Address Space
The Internet Assigned Numbers Authority (IANA) owns the Organizationally Unique Identifier (OUI) block 00:00:5E . IANA dedicated half of this block for IPv4 multicast by reserving the 24-bit prefix 01:00:5E with the 24th bit set to 0 .
This creates the available Ethernet multicast MAC range: 01 : 00 : 5 E : 00 : 00 : 00 to 01 : 00 : 5 E : 7 F : F F : F F \mathbf{01:00:5E:00:00:00} \text{ to } \mathbf{01:00:5E:7F:FF:FF} 01 : 00 : 5E : 00 : 00 : 00 to 01 : 00 : 5E : 7F : FF : FF +-----------------------------------------------------------------------------------+
- | LAYER 3 TO LAYER 2 MULTICAST MAC MAPPING |
- +-----------------------------------------------------------------------------------+
- | |
- | IPv4 Multicast Address (32 bits): |
- | +------+-------------------------+----------------------------------------------+ |
- | | 1110 | 5 DISCARDED BITS | 23 LOW-ORDER BITS (Mapped) | |
- | +------+-------------------------+----------------------------------------------+ |
- | 4 bits 5 bits 23 bits |
- | | |
- | v (Direct Bit Copy) |
- | Ethernet Multicast MAC Address (48 bits): | |
- | +----------------------------+---+----------------------------------------------+ |
- | | 00000001:00000000:01011110 | 0 | 23 LOW-ORDER BITS (Copied) | |
- | | (01:00:5E) | | | |
- | +----------------------------+---+----------------------------------------------+ |
- | 24 bits 1 bit 23 bits |
- +-----------------------------------------------------------------------------------+
- Step-by-Step Mapping Procedure
The first 25 bits of the MAC address are fixed as 01:00:5E with a leading 0-bit ( 01:00:5E:0x:xx:xx where the high-order bit of the 4th octet is 0 ).
This leaves exactly 23 bits of the Ethernet MAC address available for mapping.
An IPv4 Class D address contains 32 bits , of which the first 4 bits ( 1110 ) identify Class D, leaving 28 variable bits .
The router/host copies the low-order 23 bits of the IPv4 multicast address directly into the low-order 23 bits of the Ethernet MAC address.
The remaining 5 high-order bits ( 28 − 23 = 5 28 - 23 = 5 28 − 23 = 5 ) of the IP multicast address are discarded .
The 32:1 Overlap Ambiguity Ratio
Because 5 bits of IP address information are lost during the Layer 2 translation, exactly: 2 5 = 32 2^5 = 32 2 5 = 32
32 distinct IPv4 multicast group addresses map to the exact same Layer 2 MAC address. +-----------------------------------------------------------------------------------+
- | 32:1 MULTICAST MAC OVERLAP EXAMPLE |
- +-----------------------------------------------------------------------------------+
- | Group 1: 224.1.1.1 (1110 0000.0000 0001.0000 0001.0000 0001) -> 01:00:5E:01:01:01|
- | Group 2: 224.129.1.1 (1110 0000.1000 0001.0000 0001.0000 0001) -> 01:00:5E:01:01:01|
- | Group 3: 225.1.1.1 (1110 0001.0000 0001.0000 0001.0000 0001) -> 01:00:5E:01:01:01|
- | Group 4: 225.129.1.1 (1110 0001.1000 0001.0000 0001.0000 0001) -> 01:00:5E:01:01:01|
- | ... |
- | Group 32: 239.129.1.1 (1110 1111.1000 0001.0000 0001.0000 0001) -> 01:00:5E:01:01:01|
- +-----------------------------------------------------------------------------------+
Warning
Design Impact: If an enterprise runs two high-bandwidth video channels simultaneously on 224.1.1.1 and 239.1.1.1 in the same VLAN, both streams will be encapsulated into frames with destination MAC 01:00:5E:01:01:01 . Access switch hardware ASICs filtering by Layer 2 MAC address will deliver both streams to receivers of either group, forcing host CPUs to discard unwanted traffic at Layer 3.
3. Internet Group Management Protocol (IGMPv1 vs IGMPv2 vs IGMPv3)
Internet Group Management Protocol (IGMP) operates between end-user receiver hosts and their directly connected First-Hop / Last-Hop Multicast Router (LHR). IGMP allows hosts to dynamically signal group membership (join and leave requests) to local routers. +-----------------------------------------------------------------------------------+
- | IGMP OPERATIONAL SCOPE |
- +-----------------------------------------------------------------------------------+
- | |
- | [ Multicast Source ] |
- | | |
- | v (PIM Multicast Routing Backbone) |
- | +-----------------+ |
- | | Last-Hop Router | <======================+ |
- | +-----------------+ | |
- | | | IGMPv1 / IGMPv2 / IGMPv3 |
- | =========+========= Access VLAN Subnet =====| (Host-to-Router Signaling) |
- | | | |
- | +-----------------+ | |
- | | | | |
- | v v | |
- | +---------+ +---------+ | |
- | | Host 1 | | Host 2 | <=========+ |
- | | Receiver| | Receiver| |
- | +---------+ +---------+ |
- +-----------------------------------------------------------------------------------+
- IGMP Version Comparison
- Technical Parameter IGMP Version 1 (RFC 1112) IGMP Version 2 (RFC 2236) IGMP Version 3 (RFC 3376)
- IP Protocol Number IP Protocol 2 IP Protocol 2 IP Protocol 2
- General Query Destination 224.0.0.1 (All-Hosts) 224.0.0.1 (All-Hosts) 224.0.0.1 (All-Hosts)
- Query Interval 60 seconds 60 seconds (default) 60 seconds (default)
Max Response Time Field No (Fixed 10 seconds implicit) Yes (Units: 1/10th sec, default 10s) Yes (Units: 1/10th sec, exponential code)
Group Membership Report Sent to Group IP ( G G G ) Sent to Group IP ( G G G ) Sent to 224.0.0.22 (IGMPv3 Routers)
Report Suppression Yes (Random timer 0-10s) Yes (Random timer 0-10s) No (All hosts send reports to provide explicit source tracking)
Explicit Leave Mechanism No (Host goes silent; router waits 3 minutes) Yes (Leave Group message sent to 224.0.0.2 / All-Routers) Yes (Included in State-Change Report to 224.0.0.22 )
Group-Specific Query No Yes (Sent to Group IP after Leave) Yes (Group-and-Source-Specific Query)
Querier Election Relies on Multicast Routing Protocol (PIM DR) Native Election: Router with Lowest IP Address on subnet Native Election: Router with Lowest IP Address on subnet
Source Filtering (SSM) No ( *, G only) No ( *, G only) Yes ( INCLUDE and EXCLUDE modes for S, G )
Deep Dive: IGMPv2 Mechanics
IGMPv2 is the most widespread baseline multicast signaling protocol in enterprise networks.
General Query and Report:
The elected Querier periodically sends an IGMP General Query to 224.0.0.1 with a Max Response Time (default 10 seconds).
Hosts set a random response timer between 0 and Max Response Time for each group they belong to.
When the earliest timer expires on a host, that host transmits an IGMP Membership Report to the group address G G G .
Other hosts listening on the shared segment hear this report and suppress their own reports ( Report Suppression ), reducing control traffic.
Querier Election:
When multiple routers share a multi-access LAN segment, all routers initially transmit General Queries with their interface IP.
The router with the lowest numerical IPv4 address wins the election and becomes the designated IGMP Querier .
Non-querier routers reset an Other Querier Present Timer (default: 2 × Query Interval + 1 2 × Max Response Time = 125 s 2 \times \text{Query Interval} + \frac{1}{2} \times \text{Max Response Time} = 125\text{s} 2 × Query Interval + 2 1 × Max Response Time = 125 s ). If the active querier fails, the non-querier takes over.
Leave Group & Group-Specific Query:
When a host leaves a group, it transmits an IGMP Leave Group message (Type 0x17 ) to 224.0.0.2 (All Multicast Routers).
Upon receiving the Leave, the Querier immediately sends a Group-Specific Query destined to the specific group address G G G with a reduced Max Response Time ( Last Member Query Interval , default: 1 second).
The Querier repeats this query based on the Last Member Query Count (default: 2 times).
If no host sends a Membership Report within 2 × 1 s = 2 s 2 \times 1\text{s} = 2\text{s} 2 × 1 s = 2 s , the router prunes the group from the interface, reducing leave latency from 180 seconds (IGMPv1) to approximately 2 seconds. +-----------------------------------------------------------------------------------+
- | IGMPv2 LEAVE GROUP TIMELINE |
- +-----------------------------------------------------------------------------------+
- | |
- | Host A IGMP Querier (Router) Host B |
- | | | | |
- | |--- 1. IGMP Leave (Group 239.1.1.1)->| | |
- | | (Sent to 224.0.0.2) | | |
- | | |--- 2. Group-Specific Query ->| |
- | | | (Dest: 239.1.1.1, MRT=1s) | |
- | | | | |
- | | |<-- 3. Membership Report -----| |
- | | | (Host B still wants it) | |
- | | | | |
- | | | [Stream Continues to Subnet] | |
- +-----------------------------------------------------------------------------------+
- Deep Dive: IGMPv3 and Source Filtering (SSM)
IGMPv3 (RFC 3376) introduces Source Filtering , empowering client applications to request traffic from explicit sender unicast IP addresses. This is the client-side foundation for Source-Specific Multicast (PIM-SSM) .
Filter Modes:
INCLUDE <Source-List> : The host requests multicast packets sent to group G G G only if they originate from the specific source IPs in the list ( (S, G) state).
EXCLUDE <Source-List> : The host requests multicast packets sent to group G G G from all sources except the specific source IPs in the list. An empty exclude list ( EXCLUDE {} ) represents standard (*, G) any-source join.
Report Destination ( 224.0.0.22 ): All IGMPv3 reports are sent directly to the reserved multicast address 224.0.0.22 (IGMPv3-capable routers). Hosts do not listen to 224.0.0.22; therefore, report suppression is disabled in IGMPv3, allowing routers to maintain full per-host source visibility.
Loading diagram... IGMPv2 Join, Leave, and Querier Election Sequence
- 4. Layer 2 IGMP Snooping & IGMP Snooping Querier
- The Layer 2 Multicast Flooding Dilemma
By default, a standard Layer 2 Ethernet switch learns source MAC addresses to populate its CAM (MAC address) table. Because multicast MAC addresses ( 01:00:5E:xx:xx:xx ) are strictly destination addresses and never appear as source MACs , the switch never learns them.
Consequently, without optimization, a Layer 2 switch treats all multicast frames as Unknown Multicast / Broadcast frames and floods them out every single port in the VLAN , saturating client access links and degrading Wi-Fi access points. +-----------------------------------------------------------------------------------+
- | WITHOUT IGMP SNOOPING VS. WITH IGMP SNOOPING |
- +-----------------------------------------------------------------------------------+
- | |
- | WITHOUT IGMP SNOOPING: Multicast flooded to ALL ports in VLAN |
- | [Router / Source] === Multicast Stream ===> [ Access Switch ] |
- | / | \ |
- | (Flood) (Flood) (Flood) |
- | v v v |
- | [Host 1] [Host 2] [Host 3] |
- | (Wants) (Unwanted)(Unwanted) |
- | |
- | WITH IGMP SNOOPING: Switch snoops IGMP and forwards ONLY to interested ports |
- | [Router / Source] === Multicast Stream ===> [ Access Switch ] |
- | / | \ |
- | (Forward) (Blocked) (Blocked) |
- | v v v |
- | [Host 1] [Host 2] [Host 3] |
- | (Wants) (Clean) (Clean) |
- +-----------------------------------------------------------------------------------+
- How IGMP Snooping Operates
When IGMP Snooping is enabled globally and on the VLAN (enabled by default on Cisco Catalyst switches):
The switch ASIC intercepts and inspects Layer 3 IGMP control packets exchanged between hosts and routers.
Router Port (mrouter port) Detection: The switch identifies ports connected to Layer 3 multicast routers by listening for IGMP General Queries, PIM Hellos, or Cisco Group Management Protocol (CGMP) packets. These ports are added to the multicast router port list for the VLAN.
Host Port Tracking: When a host on Port Gi1/0/1 transmits an IGMP Membership Report for group 239.1.1.1 , the switch parses the report and creates an entry in its Layer 2 Multicast Forwarding Database (MFDB) binding MAC 01:00:5E:01:01:01 to port Gi1/0/1.
Data Forwarding: When incoming multicast data frames arrive on the switch, hardware ASICs look up the destination MAC in the MFDB and forward frames only to ports with registered receivers and to upstream mrouter ports.
Fast-Leave / Immediate-Leave ( ip igmp snooping vlan <id> immediate-leave ): In topologies where only a single host is connected per physical switch port, enabling immediate leave allows the switch to immediately prune the port upon receiving an IGMP Leave without waiting for Group-Specific Queries.
The IGMP Snooping Querier
IGMP Snooping relies entirely on periodic IGMP General Queries to refresh its MFDB table timers. If a VLAN is completely isolated at Layer 2 (e.g., an isolated storage, video surveillance, or backup VLAN with no Layer 3 default gateway router running PIM/IGMP):
Hosts send initial IGMP Membership Reports upon boot, establishing initial multicast flows.
Because no router exists to send periodic General Queries, host report suppression timers never trigger, and hosts remain silent.
The switch's IGMP snooping group membership timer (default: 300 seconds) expires.
The switch purges the group entries from the MFDB, causing multicast traffic to either be dropped or flooded as unknown broadcast.
Solution: IGMP Snooping Querier ( ip igmp snooping querier ) Configuring the switch as an IGMP Snooping Querier allows the Layer 2 switch to generate periodic IGMPv2 General Queries (using a configured source IP or 0.0.0.0 ) to keep the IGMP snooping table active without requiring a Layer 3 multicast routing license or physical router.
5. Cisco IOS-XE Configuration & Verification CLI
1. Enabling Multicast Routing and IGMP Snooping ! Globally enable multicast routing on Layer 3 switches / routers
ip multicast-routing
- ! Global IGMP Snooping configuration (enabled by default on Catalyst switches)
- ip igmp snooping
- ip igmp snooping vlan 10
- ! Enable Immediate-Leave on point-to-point host access ports
- ip igmp snooping vlan 10 immediate-leave
- ! Configure IGMP Snooping Querier for Layer 2 only VLAN
- ip igmp snooping querier
- ip igmp snooping querier version 2
- ip igmp snooping querier address 192.168.10.254
- 2. Interface IGMP Tuning & Static Joins interface GigabitEthernet0/0/1.10
- encapsulation dot1Q 10
- ip address 192.168.10.1 255.255.255.0
- ip pim sparse-mode
- ! Configure IGMP Version 3 on interface (defaults to v2)
- ip igmp version 3
- ! Tune IGMP query interval and max response time
- ip igmp query-interval 30
- ip igmp query-max-response-time 5
- ! Join group statically on router for testing (punts to CPU)
- ip igmp join-group 239.1.1.1
- ! Statically forward group out interface without CPU punt
- ip igmp static-group 239.2.2.2
Note
Exam Distinction ( join-group vs static-group ): ip igmp join-group causes the router's local Route Processor to join the group, process multicast packets in software, and respond to ICMP pings. ip igmp static-group programs hardware ASICs to forward packets out the interface without sending copies to the local CPU.
3. Verification Commands & Diagnostics Switch# show ip igmp snooping
Global IGMP Snooping configuration:
- ------------------------------------------
- IGMP snooping : Enabled
- IGMPv3 snooping : Enabled
- Report suppression : Enabled
- TCN solicit query : Disabled
- Applied subnet-based entries : Disabled
Vlan 10:
- -------
- IGMP snooping : Enabled
- IGMPv2 immediate leave : Enabled
- Explicit host tracking : Enabled
- Multicast router learning mode : pim-dvmrp
- IGMP snooping querier : Enabled
- IGMP snooping querier address : 192.168.10.254
- IGMP snooping querier state : Acting Querier
- Switch# show ip igmp snooping groups vlan 10
- Vlan Group Type Version Port List
- ----------------------------------------------------------------------
- 10 239.1.1.1 dynamic v2 Gi1/0/1, Gi1/0/2
- 10 239.10.10.100 dynamic v3 Gi1/0/3
- Router# show ip igmp interface GigabitEthernet0/0/1.10
- GigabitEthernet0/0/1.10 is up, line protocol is up
- Internet address is 192.168.10.1/24
- IGMP is enabled on interface
- Current IGMP host version is 3
- Current IGMP router version is 3
- IGMP query interval is 30 seconds
- IGMP querier timeout is 60 seconds
- IGMP max query response time is 5 seconds
- Last member query count is 2
- Last member query response interval is 1000 ms
- Inbound IGMP access group is not set
- IGMP activity: 5 joins, 2 leaves
- Multicast routing is enabled on interface
- Multicast TTL threshold is 0
- Multicast designated router (DR) is 192.168.10.1 (this system)
- IGMP querying router is 192.168.10.1 (this system)
Multicast groups joined by this system (number of users):
239.1.1.1(1)
- Router# show ip igmp groups
- IGMP Connected Group Membership
- Group Address Interface Uptime Expires Last Reporter Group Accounted
- 239.1.1.1 Gi0/0/1.10 00:14:22 00:00:25 192.168.10.50
- 239.10.10.100 Gi0/0/1.10 00:05:10 00:00:28 192.168.10.55
- 224.0.1.40 Gi0/0/1.10 01:02:11 00:00:21 192.168.10.1