CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Verifying whether multicast is enabled on a Cisco switch requires checking two distinct layers of the network stack. A switch operating purely at Layer 2 handles multicast traffic very differently from a multilayer switch routing multicast streams between VLANs. Before running verification commands, you need to determine whether your switch is responsible for local Layer 2 traffic optimization (IGMP snooping) or inter-VLAN Layer 3 packet forwarding (IP multicast routing and PIM).

Layer 2 IGMP Snooping vs. Layer 3 IP Multicast Routing

On Cisco Catalyst switches, “multicast” refers to two separate mechanisms with opposite default states. Layer 2 IGMP snooping listens to host-to-router messages so the switch only forwards multicast frames to ports with interested receivers, rather than flooding the entire VLAN. Layer 3 IP multicast routing actively routes multicast packets across subnet boundaries using Protocol Independent Multicast (PIM).

Feature / CriterionLayer 2 IGMP SnoopingLayer 3 IP Multicast Routing
OSI LayerLayer 2 (Data Link)Layer 3 (Network)
Default Status (Catalyst IOS/IOS-XE)Enabled by default globally and on all VLANsDisabled by default globally and on all interfaces
Primary FunctionPrevents Layer 2 multicast broadcast flooding within a single VLAN by examining IGMP reportsRoutes multicast streams between different VLANs (SVIs) or routed physical ports
Core Protocols UsedIGMPv1/v2/v3 Snooping, IGMP Snooping QuerierPIM Sparse Mode (PIM-SM), PIM-SSM, PIM Dense Mode, IGMP, MSDP
Cisco Licensing (Catalyst 9000)Included in Network Essentials (Base)Requires Network Advantage (for full L3 multicast routing)
Primary Verification Commandshow ip igmp snoopingshow ip multicast and show ip pim interface

Understanding this distinction ensures you check the right subsystem: if your hosts and multicast server sit in the same VLAN, you only need to verify IGMP snooping; if they sit in different subnets, you must check both IGMP snooping and Layer 3 multicast routing.

How to Check if Layer 2 IGMP Snooping Is Enabled

Even though IGMP snooping is enabled out of the box on Cisco Catalyst switches, administrators occasionally disable it on specific VLANs during troubleshooting or misconfigure the IGMP querier needed to keep group memberships alive. Follow these sequential steps to verify Layer 2 multicast functionality.

Step 1: Verify Global and Per-VLAN IGMP Snooping Status

Run the show ip igmp snooping command in privileged EXEC mode to inspect both the global switch state and individual VLAN settings. You can also append vlan <vlan-id> to filter the output to a single broadcast domain.

Switch# show ip igmp snooping vlan 10
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping                : Enabled
IGMPv3 snooping (minimal)    : Enabled
Report suppression           : Enabled
TCN solicit query            : Disabled
TCN flood query count        : 2
Robustness variable          : 2
Last member query count      : 2
Last member query interval   : 1000

Vlan 10:
--------
IGMP snooping                       : Enabled
IGMPv2 immediate leave              : Disabled
Explicit host tracking              : Enabled
Multicast router learning mode      : pim-dvmrp
CGMP interoperability mode          : IGMP_ONLY

Confirm that both Global IGMP Snooping configuration and the specific Vlan <id> entry display Enabled. If global snooping is disabled, per-VLAN settings have no effect, and the switch floods all multicast traffic across every port in the VLAN like a broadcast.

Step 2: Check for an Active IGMP Querier

IGMP snooping relies on periodic IGMP General Queries sent by a multicast router to prompt hosts to report their group memberships. Without a querier, the switch’s snooping table times out after a few minutes and drops multicast streams. Check if an active querier exists on your VLANs:

Switch# show ip igmp snooping querier
Vlan      IP Address               IGMP Version   Port             
-------------------------------------------------------------
10        10.10.10.1               v2             Switch
20        10.10.20.254             v2             Gi1/0/1

If a VLAN is missing from this output or shows 0.0.0.0, no device is sending membership queries on that subnet.

Step 3: Inspect Learned Multicast Groups and Router Ports

Once snooping and a querier are confirmed, verify that the switch is actively learning multicast group joins from receivers and identifying the upstream multicast router port (mrouter):

Switch# show ip igmp snooping groups vlan 10
Vlan      Group                    Type        Version     Port List
-----------------------------------------------------------------------
10        239.1.1.100              igmp        v2          Gi1/0/12, Gi1/0/15

Switch# show ip igmp snooping mrouter vlan 10
Vlan    ports
----    -----
  10    Gi1/0/1(dynamic)

If receivers are actively requesting a stream, their access ports appear under Port List, and the uplink toward the router or SVI appears under mrouter.

CLI Commands to Verify Layer 3 IP Multicast Routing and PIM

When a Cisco Catalyst switch acts as the default gateway routing multicast traffic between VLANs, you must verify that global IP multicast routing is turned on and that PIM is active on each participating Layer 3 interface. Use the following IOS and IOS-XE CLI commands and compare your results against the expected outputs.

! 1. Verify global Layer 3 multicast routing status
Switch# show ip multicast
  Multicast Routing: enabled
  Multicast Multipath: disabled
  Multicast Route limit: No limit
  Multicast Fallback group mode: Sparse

! Alternative check against the running configuration:
Switch# show running-config | include ip multicast-routing
ip multicast-routing distributed


! 2. Verify which Layer 3 interfaces (SVIs or routed ports) have PIM enabled
Switch# show ip pim interface
Address          Interface                Ver/   Nbr    Query  DR     DR
                                          Mode   Count  Intvl  Prior
10.10.10.1       Vlan10                   v2/S   1      30     1      10.10.10.2
10.10.20.1       Vlan20                   v2/S   0      30     1      10.10.20.1
172.16.0.2       GigabitEthernet1/0/48    v2/S   1      30     1      172.16.0.1
! Note: "v2/S" indicates PIMv2 Sparse Mode is active on the interface.
! If this output is blank, PIM is not configured on any interface.


! 3. Check active PIM neighbor adjacencies with upstream/downstream routers
Switch# show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable,
      L - DR Load-balancing Capable
Neighbor          Interface                Uptime/Expires    Ver   DR
Address                                                            Prio/Mode
10.10.10.2        Vlan10                   02:14:09/00:01:28 v2    1 / DR S P G
172.16.0.1        GigabitEthernet1/0/48    05:41:22/00:01:41 v2    100/ DR S P G


! 4. Inspect the active Layer 3 Multicast Routing Table (mroute)
Switch# show ip mroute 239.1.1.100
(*, 239.1.1.100), 00:15:32/stopped, RP 10.255.255.1, flags: SJC
  Incoming interface: GigabitEthernet1/0/48, RPF nbr 172.16.0.1
  Outgoing interface list:
    Vlan10, Forward/Sparse, 00:15:32/00:02:41

(10.10.20.50, 239.1.1.100), 00:12:10/00:02:51, flags: FT
  Incoming interface: Vlan20, RPF nbr 0.0.0.0
  Outgoing interface list:
    Vlan10, Forward/Sparse, 00:12:10/00:02:41

If show ip multicast returns Multicast Routing: disabled or show ip pim interface returns no entries, the switch will drop all inter-VLAN multicast traffic at the Layer 3 boundary.

How to Enable IP Multicast Routing and PIM on a Cisco Switch

If your verification commands reveal that Layer 3 multicast routing is disabled, use the following configuration template to enable it. Note that Catalyst 3650/3850 and Catalyst 9000 series switches running Cisco IOS-XE use ip multicast-routing distributed, whereas classic IOS switches use ip multicast-routing.

configure terminal

! 1. Enable global IP multicast routing
! Use "ip multicast-routing distributed" on Catalyst IOS-XE platforms,
! or "ip multicast-routing" on classic Catalyst IOS platforms:
ip multicast-routing distributed

! 2. Configure the Rendezvous Point (RP) address for PIM Sparse Mode
! (All multicast routers in the domain must agree on the RP IP address)
ip pim rp-address <rp-loopback-ip>

! 3. Enable PIM Sparse Mode on every SVI and routed uplink that carries multicast
interface Vlan<source-vlan-id>
 ip address <ip-address> <subnet-mask>
 ip pim sparse-mode
 exit

interface Vlan<receiver-vlan-id>
 ip address <ip-address> <subnet-mask>
 ip pim sparse-mode
 exit

interface <routed-uplink-interface>
 no switchport
 ip address <ip-address> <subnet-mask>
 ip pim sparse-mode
 exit

! 4. Save the configuration
end
write memory

Enabling ip pim sparse-mode on an SVI automatically enables IGMP on that interface as well, allowing the switch to act as the IGMP querier for that VLAN.

How to Check Multicast and PIM Status on a Cisco Nexus Switch

Data center networks running Cisco Nexus switches use NX-OS, which employs a modular feature-based architecture rather than the monolithic command structure of Catalyst IOS-XE. On NX-OS, multicast protocols do not even appear in the configuration or verification CLI until their corresponding features are enabled. Use the commands below to check multicast status on a Cisco Nexus switch.

! 1. Check if the PIM, IGMP, and MSDP features are enabled in NX-OS
Nexus-Switch# show feature | include "pim|igmp|msdp"
igmp                  1          enabled
msdp                  1          disabled
pim                   1          enabled
pim6                  1          disabled


! 2. Verify Layer 2 IGMP snooping status (enabled by default in NX-OS)
Nexus-Switch# show ip igmp snooping
Global IGMP Snooping Information:
  IGMP Snooping enabled
  Optimised Multicast Flood (OMF) enabled
  IGMPv1/v2 Report Suppression enabled
  IGMPv3 Report Suppression disabled
  Link Local Groups Suppression enabled


! 3. Check Layer 3 interfaces configured for PIM in the current VRF
Nexus-Switch# show ip pim interface brief
PIM Interface Status for VRF "default"
Interface               IP Address       PIM DR Address   Neighbor  Border
                                                          Count     Interface
Vlan10                  10.10.10.1/24    10.10.10.1          0      no
Ethernet1/49            172.16.0.2/30    172.16.0.1          1      no


! 4. Verify active PIM neighbors and the NX-OS multicast routing table
Nexus-Switch# show ip pim neighbor
Nexus-Switch# show ip mroute

If show feature indicates that pim or igmp is disabled on a Nexus switch, enable them in global configuration mode using feature pim and feature igmp before configuring interfaces.

Troubleshooting Multicast Traffic Not Passing Through a Cisco Switch

Sometimes all verification checks confirm that IGMP snooping, global multicast routing, and PIM are enabled, yet receivers still fail to receive multicast streams. Follow this diagnostic guide to isolate the root cause.

1. Fix Missing IGMP Queriers in Layer 2-Only Environments

If multicast sources and receivers reside in the same isolated Layer 2 VLAN without a PIM-enabled router or SVI, IGMP snooping will stop forwarding traffic after 3 to 4 minutes because no device sends periodic IGMP Membership Queries.
* Diagnosis: Run show ip igmp snooping querier as covered above.
* Resolution: Enable the switch’s built-in Layer 2 IGMP snooping querier on that VLAN (make sure the switch has an SVI IP address or assign a dummy querier IP):
text
Switch(config)# ip igmp snooping vlan 10 querier
Switch(config)# ip igmp snooping vlan 10 querier address 10.10.10.254

2. Verify Rendezvous Point (RP) Mapping and Reachability

In PIM Sparse Mode, switches cannot build shared trees (*, G) or register sources (S, G) unless they know the IP address of the Rendezvous Point and can reach it via unicast routing.
* Diagnosis: Run show ip pim rp mapping to verify that an RP is configured or learned via Auto-RP/BSR, and test unicast connectivity with ping <rp-ip>.
* Resolution: Ensure every Layer 3 switch in the multicast path has a matching ip pim rp-address statement (or valid Auto-RP/BSR configuration) and a valid unicast route to the RP’s loopback interface.

3. Check for Reverse Path Forwarding (RPF) Failures

Layer 3 multicast switches drop incoming multicast packets if the interface they arrive on does not match the outgoing interface the switch uses to reach the source’s unicast IP address.
* Diagnosis: Run show ip rpf <multicast-source-ip>. Look at the RPF interface and RPF neighbor fields:
text
Switch# show ip rpf 10.10.20.50
RPF information for ? (10.10.20.50)
RPF interface: Vlan20
RPF neighbor: ? (0.0.0.0) - directly connected
RPF route/mask: 10.10.20.0/24
RPF type: unicast (connected)

* Resolution: If show ip rpf reports failed, no route exists or points to an interface where PIM is disabled, fix the underlying unicast routing asymmetry or add a static multicast route (ip mroute <source-ip> <mask> <next-hop>).

4. Inspect Packet TTL and Reserved Multicast Addresses

Two common application-level mistakes prevent Cisco switches from routing multicast packets across VLANs even when network configuration is flawless:
* TTL = 1: Many streaming applications default to a Time-to-Live (TTL) value of 1. When a Layer 3 switch routes the packet to another VLAN, it decrements the TTL to 0 and drops the packet. Increase the sender’s multicast TTL setting to at least 15 or 64.
* Link-Local Address Range (224.0.0.0/24): Addresses from 224.0.0.0 to 224.0.0.255 are reserved by IANA for link-local control protocols (such as OSPF and VRRP). Cisco switches never route packets in this range across Layer 3 boundaries, regardless of TTL. Use organization-local multicast addresses in the 239.0.0.0/8 block instead.

5. Monitor Active Hardware Forwarding Counters

To verify whether the switch is receiving multicast packets from the source and forwarding them out the OIL (Outgoing Interface List), check the packet counters:

Switch# show ip mroute count

Look at the (S, G) entry for your stream. If Other counts: RPF failed or Total/Other drops increments while Forwarded stays at zero, the switch is dropping the stream due to RPF mismatches or an empty outgoing interface list.

Official Cisco Multicast Configuration Guides and Command References

For platform-specific syntax variations, hardware forwarding scale limits, and release-specific caveats, consult the authoritative Cisco documentation corresponding to your switch hardware and software train:

  • Cisco Catalyst 9000 Series (IOS-XE): Refer to the IP Multicast Routing Configuration Guide, Cisco IOS XE [Release] (Catalyst 9200 / 9300 / 9400 / 9500 / 9600 Switches).
  • Licensing Note: Full Layer 3 PIM Sparse Mode (ip pim sparse-mode), PIM-SSM, and MSDP require the Network Advantage license package. Switches running Network Essentials only support Layer 2 IGMP snooping and basic PIM stub routing.
  • Hardware Verification: On Catalyst 9000 switches, use show platform software fed switch active ipmcast info to inspect ASIC-level multicast forwarding resources.
  • Cisco Catalyst 3650 / 3850 Series (IOS-XE): Refer to the IP Multicast Routing Configuration Guide, Cisco IOS XE Denali / Everest / Fuji / Gibraltar (Catalyst 3650 and 3850 Switches).
  • Cisco IOS Master Command Reference: Refer to the Cisco IOS IP Multicast Command Reference for complete syntax descriptions and output field definitions for all show ip igmp, show ip pim, and show ip mroute commands.
  • Cisco Nexus 9000 Series (NX-OS): Refer to the Cisco Nexus 9000 Series NX-OS Multicast Routing Configuration Guide for VXLAN EVPN multicast underlay/overlay verification, Anycast RP, and NX-OS specific CLI syntax.

Conclusion

Checking whether multicast is enabled on a Cisco switch comes down to verifying the right layer for your topology. For single-VLAN environments, run show ip igmp snooping and show ip igmp snooping querier to confirm that Layer 2 filtering and membership queries are active. For multi-VLAN environments, run show ip multicast and show ip pim interface (or show feature on Nexus NX-OS) to confirm that Layer 3 multicast routing and PIM are enabled across your SVIs and uplinks. Combining these verification checks with RPF and RP diagnostics ensures your multicast streams flow reliably from source to receiver.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.