Catalyst 5000 Family Software Configuration Guide (6.3 and 6.4) - Configuring Multicast Services [Cisco Catalyst 5000 Series Switches]

Table Of Contents

Configuring Multicast Services

Understanding How Multicasting Works

Multicasting and Multicast Services Overview

Understanding How CGMP Works

CGMP Overview

Joining a Multicast Group

Constraining Multicast Traffic

Leaving a Multicast Group

CGMP Leave Processing

Interaction Between CGMP Leave Processing and HSRP

Understanding How IGMP Snooping Works

IGMP Snooping Overview

Joining a Multicast Group

Constraining Multicast Traffic

Leaving a Multicast Group

IGMP Fast-Leave Processing

Understanding How RGMP Works

Understanding How GMRP Works

Configuring CGMP

CGMP Hardware and Software Requirements

Default CGMP Configuration

Enabling CGMP

Enabling CGMP Leave Processing

Displaying Multicast Router Information

Displaying Multicast Group Information

Checking CGMP Statistics

Disabling CGMP Fast-Leave Processing

Disabling CGMP

Configuring IGMP Snooping

IGMP Snooping Hardware and Software Requirements

Default IGMP Snooping Configuration

Enabling IGMP

Enabling IGMP Fast-Leave Processing

Displaying Multicast Router Information

Displaying Multicast Group Information

Displaying IGMP Statistics

Disabling IGMP Fast-Leave Processing

Disabling IGMP

Configuring RGMP

Default RGMP Configuration

Enabling and Disabling RGMP

Displaying RGMP Group Information

Displaying and Clearing RGMP VLAN Statistics

Displaying RGMP-Capable Router Ports

Displaying Multicast Protocol Status

Clearing RGMP Statistics

RGMP-Related CLI Commands

Configuring GMRP

GMRP Hardware and Software Requirements

Default GMRP Configuration

Enabling GMRP Globally

Enabling GMRP on Individual Switch Ports

Disabling GMRP on Individual Switch Ports

Enabling GMRP Forward-All Option

Disabling GMRP Forward-All Option

Configuring GMRP Registration

Setting Normal Registration Mode

Setting Fixed Registration Mode

Setting Forbidden Registration Mode

Setting the GARP Timers

Displaying GMRP Statistics

Clearing GMRP Statistics

Disabling GMRP on the Switch

Configuring Multicast Router Ports and Group Entries

Specifying Multicast Router Ports

Configuring Multicast Groups

Clearing Multicast Router Ports

Clearing Multicast Group Entries

Configuring Multicast Services

This chapter describes how to configure multicast services, including Cisco Group Management Protocol (CGMP), Internet Group Management Protocol (IGMP) snooping, Router Group Management Protocol (RGMP), and GARP Multicast Registration Protocol (GMRP) on the Catalyst enterprise LAN switches.

Note For complete syntax and usage information for the commands used in this chapter, refer to the Catalyst 5000 Family Command Reference.

This chapter consists of these sections:

•Understanding How Multicasting Works

•Configuring CGMP

•Configuring IGMP Snooping

•Configuring RGMP

•Configuring GMRP

•Configuring Multicast Router Ports and Group Entries

Understanding How Multicasting Works

These sections describe how multicasting works on the Catalyst enterprise LAN switches:

•Multicasting and Multicast Services Overview

•Understanding How CGMP Works

•Understanding How IGMP Snooping Works

•Understanding How RGMP Works

•Understanding How GMRP Works

Multicasting and Multicast Services Overview

CGMP, IGMP snooping, and GMRP manage multicast traffic in switches by allowing directed switching of IP multicast traffic. GMRP is protocol independent and can manage both IP multicast traffic and any Layer 2 multicast traffic.

Switches can use CGMP, IGMP snooping, or GMRP to dynamically configure switch ports so that IP multicast traffic is forwarded only to those ports associated with IP multicast hosts.

Note For more information on IP multicast and IGMP, refer to RFC 1112. GMRP is described in IEEE 802.1p. RFC 2236 describes Internet Group Management Protocol, Version 2.

CGMP and IGMP software components run on both the Cisco router and the switch. A CGMP-capable IP multicast router sees all IGMP packets and can inform the switch when specific hosts join or leave IP multicast groups.

You can statically configure multicast groups using the set cam static command. Multicast groups learned through IGMP snooping and CGMP are dynamic. If you specify group membership for a multicast group address, your static setting supersedes any automatic manipulation by IGMP snooping, CGMP, or GMRP. Multicast group membership lists can consist of both user-defined and IGMP snooping-, CGMP-, or GMRP-learned settings.

Understanding How CGMP Works

These sections describe CGMP:

•CGMP Overview

•Joining a Multicast Group

•Constraining Multicast Traffic

•Leaving a Multicast Group

•CGMP Leave Processing

•Interaction Between CGMP Leave Processing and HSRP

CGMP Overview

When the CGMP-capable router receives an IGMP control packet, it creates a CGMP packet that contains the request type (either join or leave), the multicast group address, and the Media Access Control (MAC) address of the host that sent the IGMP control packet. The router sends the packet to a well-known MAC address, 01-00-0c-dd-dd-dd, to which all CGMP-capable switches listen. When a CGMP-capable switch receives the packet, the supervisor engine interprets the packet and modifies the forwarding table automatically.

Note If a spanning tree (VLAN) topology changes, the CGMP-learned multicast groups on the VLAN are purged and the CGMP-capable router generates new multicast group information. We recommend that you enable the spanning tree PortFast feature on ports to which hosts are directly connected if you are using CGMP. For information on configuring spanning-tree PortFast, see Chapter 9, "Configuring Spanning Tree PortFast, UplinkFast, and BackboneFast."

If a CGMP-learned port link is disabled for any reason, that port is removed from any multicast group memberships.

Note You cannot enable CGMP on a switch if IGMP snooping or GMRP is already enabled on that switch.

Joining a Multicast Group

When a host wants to join an IP multicast group, it sends an unsolicited IGMP join message specifying the IP multicast group it wants to join. The IGMP join also contains the Group Destination Address (GDA), the Unicast Source Address (USA), the Multicast Destination IP, and the Unicast Source IP. The router receives the IGMP join and adds the interface to the outgoing interface list (OIL) for the group. The router then builds a CGMP join using the USA of the host and the GDA contained in the join from the host and multicasts the join to the well-known CGMP multicast address to which Catalyst family switches with CGMP enabled listen.

Upon receipt of the CGMP join, each switch performs a CAM table lookup to determine if it contains the MAC address of the host asking to join the multicast group. If a switch finds the MAC address of the host in its CAM table, the switch creates a multicast forwarding entry for that GDA and adds the multicast router port and the port returned by the lookup. The host associated with that port receives multicast traffic for that multicast group. As the router sends group queries, the hosts respond with join messages, and a CGMP join is generated each time a join is received, keeping the multicast entries in the switch updated.

Constraining Multicast Traffic

When a host begins sending multicast traffic, this traffic hits the multicast forwarding entry for that GDA and the switch forwards the traffic only to those ports associated with that entry.

Leaving a Multicast Group

The CGMP-capable router sends periodic multicast group queries. If a host wants to remain in a multicast group, it responds to the query from the router. In this case, the router generates a CGMP join for that host. If a host does not want to remain in the multicast group, it does not respond to the router query. In IGMP version 1, this is the only way hosts can leave a multicast group. After a number of queries, if the router receives no join messages from any host in a multicast group, the router sends a CGMP leave to the switch and requests that the switch remove the multicast group from its forwarding tables.

In IGMP version 2, a host can also send an IGMP leave message for the group it wants to leave. When the CGMP-capable router receives the IGMP leave message from the host, it sends an IGMP group-specific query. Any hosts still in the group receive this query and send an IGMP join if they wish to receive traffic for this group. As long as there are hosts interested in the group, the router does not generate a CGMP leave message for that GDA and all switch ports remain joined to the multicast forwarding entry for that group.

Note The router does not remove a multicast group from the forwarding tables of the switch until all the hosts in the group ask to leave the group (IGMP version 2), or no hosts respond to the router's IGMP queries (IGMP version 1). Once the last host leaves the group, the multicast router generates a CGMP leave for the GDA. When the switch receives the CGMP leave, the multicast forwarding entry for that GDA is removed from the forwarding table.

CGMP Leave Processing

When the switch is operating in CGMP mode, you should enable CGMP leave processing to ensure minimal leave latency. CGMP leave processing allows the switch to detect IGMP version 2 leave messages sent to the all-routers multicast address (224.0.0.2) by hosts. When the supervisor engine detects a leave message, it sends a MAC-based general query and starts a query-response timer. If this timer expires before a CGMP join is received for the group specified in the leave message, the port is pruned from the multicast forwarding entry for the multicast group specified in the original leave message. CGMP leave processing ensures optimal bandwidth management for all hosts on a switched network and is required when multicast receivers frequently change membership among multiple high-bandwidth groups (an example is video-on-demand channel surfing).

Interaction Between CGMP Leave Processing and HSRP

In a network topology where there are both multicast routers and also non-multicast router running HSRP, enabling CGMP leave processing on a switch can cause the following problems:

•HSRP communication between routers breaks

Because HSRP and multicast protocols both use the 224.0.0.2 Layer 3 address, HSRP hellos are captured and flooded on multicast router ports only when CGMP leave processing is enabled. As a result, non-multicast routers running HSRP will not see HSRP hello messages from other routers and HSRP communication will break down.

In Figure 16-1, if Router A and Router B are running HSRP but only Router A is learned as a multicast router, Router B will never see the HSRP hellos from Router A.

To prevent HSRP communication from breaking when CGMP leave processing is enabled, configure a static router port on the non-multicast routers using the set multicast router command.

Figure 16-1 Interaction between HSRP and CGMP Leave Processing

•Downstream switches flood traffic destined to the HSRP MAC address

When HSRP is running on the routers and CGMP leave processing is enabled, links to downstream switches are not learned as multicast router ports. This situation causes the HSRP MAC entries in the CAM tables of downstream switches to age out, and host traffic destined to the HSRP MAC is flooded on all ports in the VLAN.

In Figure 16-1, when HSRP routers respond (with the HSRP gateway address and MAC) to ARPs from hosts connected to Switch B, Switch B gets a CAM entry for the HSRP MAC. After 300 seconds, this entry ages out (unless another host connected to Switch B sends out an ARP) because the HSRP hellos are intercepted by Switch A and flooded only on the multicast router ports (the link to Switch B is not learned as a multicast router port). Once the entry is gone, all traffic with a Destination MAC identical to the HSRP MAC is flooded in the VLAN.

If links to downstream switches are not learned as multicast router ports, the HSRP hellos are not forwarded on those links and the CAM table entries for the HSRP MAC address are not refreshed. To prevent this situation from happening, configure a static multicast router port on the connection to the downstream switches using the set multicast router mod/port command. In Figure 16-1, this would mean that to allow Switch B to receive HSRP hellos, you must configure port 2/3 on Switch A as a static multicast router port.

Understanding How IGMP Snooping Works

These sections describe IGMP snooping:

•IGMP Snooping Overview

•Joining a Multicast Group

•Constraining Multicast Traffic

•Leaving a Multicast Group

•IGMP Fast-Leave Processing

IGMP Snooping Overview

IGMP snooping manages multicast traffic at Layer 2 on the Catalyst 5000 family switches by allowing directed switching of IP multicast traffic.

Switches can use IGMP snooping to configure Layer 2 interfaces dynamically so that IP multicast traffic is forwarded only to those interfaces associated with IP multicast devices.

Note For more information on IP multicast and IGMP, refer to RFC 1112 and RFC 2236.

Catalyst 5000 series switches can distinguish IGMP control traffic from multicast data traffic. When IGMP is enabled on the switch, IGMP control traffic is redirected to the CPU for further processing. This process is performed in hardware by specialized ASICs, which allow the switch to snoop IGMP control traffic with no peformance penalty.

The route processor sends out periodic general queries to all VLANs, and as multicast receivers respond to the router's queries, the switch intercepts them. Only the first IGMP join, per VLAN, per IP multicast group is forwarded to the router. Subsequent join messages for the same VLAN and group are suppressed. The switch processor creates one entry per VLAN in the Layer 2 forwarding table for each MAC group from which it receives an IGMP join request. All hosts interested in this multicast traffic send join requests and are added to the port list of this forwarding table entry.

If an IGMP snooping-learned port link is disabled for any reason, that port is removed from any multicast group memberships.

Note You cannot enable IGMP snooping on a switch if GMRP is already enabled on the switch.

Joining a Multicast Group

When a host wants to join an IP multicast group, it sends an IGMP join message specifying the IP multicast group it wants to join, for example group 224.1.2.3. The switch hardware recognizes that the packet is an IGMP report and redirects it to the switch CPU. The switch installs a new group entry for 01-00-5e-01-02-03 and adds the host port and the router port to that entry. The switch then relays the join from the host on all multicast router ports. The designated multicast router for the segment adds the outgoing interface (OIF) to the outgoing interface list (OIL) for the group and begins forwarding multicast traffic for 224.1.2.3 to this segment.

When a second host wants to join group 244.1.2.3, it sends out an IGMP report for this group. The switch hardware recognizes that this is an IGMP control packet and redirects it to the switch CPU. Since the switch already has a group entry for 01-00-5e-01-02-03, it just adds the second host port to the entry. Because this is not the first host joining the group, the switch suppresses the report (it is not sent to the router).

Constraining Multicast Traffic

When a host sends multicast traffic to a group, the switch hardware does not recognize the stream as IGMP control packets and the packets are not redirected to the switch CPU. Instead the multicast traffic hits the MAC group entry and the switch constrains the traffic to only those ports that have been added to that group entry.

The router sends IGMP general queries every 60 seconds by default. The switch floods these queries on all ports in the VLAN, and hosts that are interested in a multicast group respond with an IGMP join for each group in which they are interested.

The switch intercepts these IGMP joins, and only the first join per VLAN and per IP multicast group is forwarded on the multicast router ports. Subsequent reports for the same VLAN and group are suppressed (they are not sent to the router).

Note If your network has CGMP switches, join and leave suppression does not occur. In a network that has both IGMP and CGMP switches, all join and leave messages are forwarded to the multicast routers so that CGMP join and leave messages can be generated by the router.

Leaving a Multicast Group

The designated multicast router for a segment continues forwarding the multicast traffic to that VLAN as long as at least one host in the VLAN wishes to receive multicast traffic. When hosts want to leave a multicast group, they can either ignore the periodic general queries sent by the multicast router (IGMP version 1 host behavior), or they can send an IGMP leave (IGMP version 2 host behavior). When the switch receives a leave message, it sends out a MAC-based general query on the port on which it received the leave message to determine if any devices connected to this port are interested in traffic for the specific multicast group. If this port is the last port in the VLAN, the switch sends a MAC-based general query to all ports in the VLAN. MAC-based general queries are addressed to the Layer 2 Group Destination Address (GDA) MAC address for which the IGMP leave message was received. At Layer 3, the MAC-based general queries are addressed to 244.0.0.1 (all hosts), and in the IGMP header, the group address field is set to 0.0.0.0.

If no IGMP report is received for any of the IP multicast groups that map to the MAC multicast group address, the port is removed from the multicast forwarding entry. If the port is not the last non-multicast-router port in the entry, the switch suppresses the IGMP leave (it is not sent to the router). If the port is the last non-multicast-router port in the entry, the IGMP leave is forwarded to the multicast router ports and the MAC group forwarding entry is removed.

When the router receives the IGMP leave, it sends several IGMP group-specific queries. If no join messages are received in response to the queries, and there are no downstream routers connected through that interface, the router removes the interface from the OIL for that IP multicast group entry in the multicast routing table.

IGMP Fast-Leave Processing

IGMP snooping fast-leave processing allows the switch processor to remove an interface from the port list of a forwarding-table entry without first sending out a MAC-based general query on the port. When an IGMP leave is received on a port, the port is immediately removed from the multicast forwarding entry (or the entire entry is removed).

Note Do not use the fast-leave processing feature if more than one host is connected to each port. If you enable fast-leave when more than one host is connected to a port, some hosts might be dropped inadvertently. Fast leave is supported only with IGMP version 2 hosts.

Understanding How RGMP Works

RGMP packets are sent with the IP header's protocol type field set to 2 (IGMP) to the reserved "All Switches" IP address 224.0.0.25 (MAC address 01-00-5e-00-00-19). RGMP-capable switches listen for and process RGMP packets received on this address.

Without RGMP, all multicast routers receive all multicast data traffic entering the switch. With RGMP, a multicast router can request not to receive multicast traffic if that router has no downstream receivers for the multicast traffic. Catalyst enterprise LAN switches support RGMP, which enables a switch to reduce network congestion by forwarding multicast data traffic to only those routers that are configured to receive it.

Note To use RGMP, you muse enable IGMP snooping on the switch and Protocol independent multicast (PIM) on all routers and switches in your network. Only PIM sparse mode is currently supported.

All routers on the network must be RGMP-capable. RGMP-capable routers send periodic RGMP hello messages on all RGMP-configured interfaces. The RGMP hello message tells the switch not to send multicast data to the router unless an RGMP join has also been sent to the switch from that router. When an RGMP join is sent, the router is able to receive multicast data. To learn how to set a router to receive RGMP data, see the "RGMP-Related CLI Commands" section.

To stop receiving multicast data on a given interface for a given group, an RGMP-capable router sends an RGMP leave message on that interface. When RGMP is disabled on the router, an RGMP bye message is sent on all RGMP-configured interfaces.

Table 16-1 provides a summary of the RGMP packet types.

Table 16-1 RGMP Message Types

Description

Action

Hello

When the RGMP feature is enabled on the router, no multicast data traffic is sent to the router by the switch unless an RGMP join is specifically sent for a group.

Bye

When RGMP feature is disabled on the router, all multicast data traffic will be sent to the router by the switch.

Join

Multicast data traffic for a multicast MAC address from the L3 group address G are sent to the router. These packets will have group G in the Group Address field of the RGMP packet.

Leave

Multicast data traffic for the group G will not be sent to the router. These packets will have group G in the group address field of the RGMP packet.

Understanding How GMRP Works

GARP Multicast Registration Protocol (GMRP) is a Generic Attribute Registration Protocol (GARP) application that provides a constrained multicast flooding facility similar to IGMP snooping and CGMP. GMRP and GARP are industry-standard protocols defined by the IEEE. For detailed protocol operational information, refer to IEEE 802.1p.

GMRP can register and deregister multicast group addresses at the MAC layer throughout the Layer 2-connected network. GMRP is Layer 3-protocol independent, which allows it to support the multicast traffic of any Layer 3 protocol (such as IP, IPX, and so forth).

GMRP software components run on both the switch and on the host (Cisco is not a source for GMRP host software). On the host, in an IP multicast environment, you must use IGMP with GMRP. The host GMRP software generates Layer 2 GMRP versions of the host's Layer 3 IGMP control packets. The switch receives both the Layer 2 GMRP and the Layer 3 IGMP traffic from the host. The switch forwards the Layer 3 IGMP control packets to the router and uses the received GMRP traffic to constrain multicasts at Layer 2 in the host's VLAN.

When a host wants to join an IP multicast group, it sends an IGMP join, which creates a corresponding GMRP join.

When the switch receives the GMRP join, it adds the port through which the join was received to the appropriate multicast group. The switch propagates the GMRP join to all other hosts in the VLAN, one of which is typically the multicast source. When the source is multicasting to the group, the switch forwards the multicast only to the ports from which it received join messages for the group.

The switch sends periodic GMRP queries. If a host wants to remain in a multicast group, it responds to the query. In this case, the switch does nothing. If a host does not want to remain in the multicast group, it can either send a leave message or not respond to the periodic queries from the switch. If the switch receives a leave message or receives no response from the host for the duration of the leaveall timer, the switch removes the host from the multicast group.

Note To use GMRP in a routed environment, enable the GMRP forward-all option on all ports where routers are attached.

Configuring CGMP

These sections describe how to configure CGMP:

•CGMP Hardware and Software Requirements

•Default CGMP Configuration

•Enabling CGMP

•Enabling CGMP Leave Processing

•Displaying Multicast Router Information

•Displaying Multicast Group Information

•Checking CGMP Statistics

•Disabling CGMP Fast-Leave Processing

•Disabling CGMP

CGMP Hardware and Software Requirements

CGMP requires these hardware and software versions:

•Supervisor engine software release 2.2 or later

•Router running CGMP

Default CGMP Configuration

Table 16-2 shows the default CGMP configuration.

Table 16-2 CGMP Default Configuration

Feature

Default Value

CGMP enable state

Disabled

Multicast routers

None configured

Enabling CGMP

Note You cannot enable CGMP if IGMP snooping or GMRP is enabled.

To enable CGMP, perform this task in privileged mode:

Task

Command

Step 1

Enable CGMP on the switch.

set cgmp enable

Step 2

Verify that CGMP is enabled.

show cgmp statistics [vlan_num]

This example shows how to enable CGMP and verify the configuration:
Console> (enable) set cgmp enable
CGMP support for IP multicast enabled.
Console> (enable) show cgmp statistics 1
CGMP enabled
CGMP statistics for vlan 1:
valid rx pkts received           211915
invalid rx pkts received         0
valid cgmp joins received        211729
valid cgmp leaves received       186
valid igmp leaves received       0
valid igmp queries received      3122
igmp gs queries transmitted      0
igmp leaves transmitted          0
failures to add GDA to EARL      0
topology notifications received  80
number of CGMP packets dropped   2032227
Console> (enable)
Enabling CGMP Leave Processing

To enable CGMP leave processing, perform this task in privileged mode:

Task

Command

Step 1

Enable CGMP leave processing on the switch.

set cgmp leave enable

Step 2

Verify that CGMP leave processing is enabled.

show cgmp leave

This example shows how to enable CGMP leave processing and verify the configuration:
Console> (enable) set cgmp leave enable
CGMP leave processing enabled.
Console> (enable)
Console> (enable) show cgmp leave
CGMP:       enabled
CGMP leave: enabled
Console> (enable)
Displaying Multicast Router Information

When you enable CGMP, the switch automatically learns to which ports a multicast router is connected.

To display the dynamically learned multicast router information, perform one of these tasks in privileged mode:

Task

Command

Display information on dynamically learned and manually configured multicast router ports.

show multicast router [mod/port] [vlan_id]

Display information only on those multicast router ports learned dynamically using CGMP.

show multicast router cgmp [mod/port] [vlan_id]

This example shows how to display information on all multicast router ports (the asterisk [*] next to the multicast router on port 3/1 indicates that the entry was configured manually):
Console> (enable) show multicast router
CGMP enabled
IGMP disabled
Port       Vlan
---------  ----------------
 2/1       99
 2/2       255
 3/1    *  1
 7/9       2,99
Total Number of Entries = 4
'*' - Configured
Console> (enable)
This example shows how to display only those multicast router ports that were learned dynamically through CGMP:
Console> (enable) show multicast router cgmp
CGMP enabled
IGMP disabled
Port       Vlan
---------  ----------------
 2/1       99
 2/2       255
 7/9       2,99
Total Number of Entries = 3
'*' - Configured
Console> (enable)
Displaying Multicast Group Information

To display information about multicast groups, perform one of these tasks in privileged mode:

Task

Command

Display information about multicast groups.

show multicast group [mac_addr] [vlan_id]

Display only information about multicast groups learned dynamically through CGMP.

show multicast group cgmp [mac_addr] [vlan_id]

Display the total number of multicast addresses (groups) in each VLAN.

show multicast group count [vlan_id]

Display the total number of multicast addresses (groups) in each VLAN that were learned dynamically through CGMP.

show multicast group count cgmp [vlan_id]

This example shows how to display information about all multicast groups on the switch:
Console> (enable) show multicast group
CGMP enabled
IGMP disabled
VLAN  Dest MAC/Route Des  Destination Ports or VCs / [Protocol Type]
----  ------------------  ----------------------------------------------------
1     01-00-11-22-33-44*  2/6-12
1     01-11-22-33-44-55*  2/6-12
1     01-22-33-44-55-66*  2/6-12
1     01-33-44-55-66-77*  2/6-12
Total Number of Entries = 4
Console> (enable)
Checking CGMP Statistics

To check CGMP statistics on the switch, perform this task:

Task

Command

Display CGMP statistics.

show cgmp statistics [vlan_id]

This example shows how to display CGMP statistics:
Console> (enable) show cgmp statistics
CGMP enabled
CGMP statistics for vlan 1:
valid rx pkts received           211915
invalid rx pkts received         0
valid cgmp joins received        211729
valid cgmp leaves received       186
valid igmp leaves received       0
valid igmp queries received      3122
igmp gs queries transmitted      0
igmp leaves transmitted          0
failures to add GDA to EARL      0
topology notifications received  80
number of CGMP packets dropped   2032227
Console> (enable)
Disabling CGMP Fast-Leave Processing

To disable CGMP fast-leave processing, perform this task in privileged mode:

Task

Command

Disable CGMP fast-leave processing on the switch.

set cgmp leave disable

This example shows how to disable CGMP fast-leave processing on the switch:
Console> (enable) set cgmp leave disable
CGMP leave processing disabled.
Console> (enable)
Disabling CGMP

To disable CGMP on the switch, perform this task in privileged mode:

Task

Command

Disable CGMP on the switch.

set cgmp disable

This example shows how to disable CGMP:
Console> (enable) set cgmp disable
CGMP support for IP multicast disabled.
Console> (enable)
Configuring IGMP Snooping

Internet Group Management Protocol (IGMP) snooping allows switches to examine IGMP packets and make forwarding decisions based on their content.

These sections describe how to configure IGMP snooping:

•IGMP Snooping Hardware and Software Requirements

•Default IGMP Snooping Configuration

•Enabling IGMP

•Enabling IGMP Fast-Leave Processing

•Displaying Multicast Router Information

•Displaying Multicast Group Information

•Displaying IGMP Statistics

•Disabling IGMP Fast-Leave Processing

•Disabling IGMP

IGMP Snooping Hardware and Software Requirements

IGMP snooping requires these hardware and software versions:

•Supervisor Engine II G or III G, or Supervisor Engine III with a NFFC or NFFC II

•Supervisor engine software release 4.1 or later. Certain hardware requires a later version of software (for example, the NFFC II requires software release 4.3 or later)

•Router running IGMP

Default IGMP Snooping Configuration

Table 16-3 shows the default IGMP snooping configuration.

Table 16-3 IGMP Snooping Default Configuration

Feature

Default Value

IGMP snooping

Disabled

Multicast routers

None configured

Enabling IGMP

Note You cannot enable IGMP snooping if CGMP or GMRP is enabled.

To enable IGMP snooping, perform this task in privileged mode:

Task

Command

Step 1

Enable IGMP snooping on the switch.

set igmp enable

Step 2

Verify that IGMP snooping is enabled.

show igmp statistics [vlan_num]

This example shows how to enable IGMP snooping and verify the configuration:
Console> (enable) set igmp enable
IGMP Snooping is enabled.
CGMP is disabled.
Console> (enable) show igmp statistics
IGMP enabled
IGMP fastleave disabled
IGMP statistics for vlan 1:
Total valid pkts rcvd:           18951
Total invalid pkts recvd         0
General Queries recvd            377
Group Specific Queries recvd     0
MAC-Based General Queries recvd  0
Leaves recvd                     14
Reports recvd                    16741
Other Pkts recvd                 0
Queries  Xmitted                 0
GS Queries Xmitted               16
Reports Xmitted                  0
Leaves Xmitted                   0
Failures to add GDA to EARL      0
Topology Notifications rcvd      10
Console> (enable) 
Enabling IGMP Fast-Leave Processing

To enable IGMP fast-leave processing, perform this task in privileged mode:

Task

Command

Step 1

Enable IGMP fast-leave processing on the switch.

set igmp fastleave enable

Step 2

Verify that IGMP fast-leave processing is enabled.

show igmp leave

This example shows how to enable IGMP fast-leave processing and verify the configuration:
Console> (enable) set igmp fastleave enable
IGMP fastleave set to enable.
Console> (enable) show igmp statistics
IGMP enabled
IGMP fastleave enabled
IGMP statistics for vlan 1:
Total valid pkts rcvd:           18951
Total invalid pkts recvd         0
General Queries recvd            377
Group Specific Queries recvd     0
MAC-Based General Queries recvd  0
Leaves recvd                     14
Reports recvd                    16741
Other Pkts recvd                 0
Queries  Xmitted                 0
GS Queries Xmitted               16
Reports Xmitted                  0
Leaves Xmitted                   0
Failures to add GDA to EARL      0
Topology Notifications rcvd      10
Console> (enable) 
Displaying Multicast Router Information

When you enable IGMP snooping, the switch automatically learns to which ports a multicast router is connected.

To display the dynamically learned multicast router information, perform one of these tasks in privileged mode:

Task

Command

Display information on dynamically learned and manually configured multicast router ports.

show multicast router [mod/port] [vlan_id]

Display information only on those multicast router ports learned dynamically using IGMP snooping.

show multicast router igmp [mod/port] [vlan_id]

This example shows how to display information on all multicast router ports (the asterisk [*] next to the multicast router on port 5/7 indicates that the entry was configured manually):
Console> (enable) show multicast router
CGMP disabled
IGMP enabled
Port       Vlan
---------  ----------------
 1/1       1
 2/1       2,99,255
 5/7    *  99
Total Number of Entries = 3
'*' - Configured
Console> (enable)
This example shows how to display only those multicast router ports that were learned dynamically through IGMP:
Console> (enable) show multicast router igmp
CGMP disabled
IGMP enabled
Port       Vlan
---------  ----------------
 1/1       1
 2/1       2,99,255
Total Number of Entries = 2
'*' - Configured
Console> (enable)
Displaying Multicast Group Information

To display information about multicast groups, perform one of these tasks in privileged mode:

Task

Command

Display information about multicast groups.

show multicast group [mac_addr] [vlan_id]

Display only information about multicast groups learned dynamically through IGMP.

show multicast group igmp [mac_addr] [vlan_id]

Display the total number of multicast addresses (groups) in each VLAN.

show multicast group count [vlan_id]

Display the total number of multicast addresses (groups) in each VLAN that were learned dynamically through IGMP.

show multicast group count igmp [vlan_id]

This example shows how to display information about all multicast groups on the switch:
Console> (enable) show multicast group
CGMP disabled
IGMP enabled
VLAN  Dest MAC/Route Des  Destination Ports or VCs / [Protocol Type]
----  ------------------  ----------------------------------------------------
1     01-00-11-22-33-44*  2/6-12
1     01-11-22-33-44-55*  2/6-12
1     01-22-33-44-55-66*  2/6-12
1     01-33-44-55-66-77*  2/6-12
Total Number of Entries = 4
Console> (enable)
Displaying IGMP Statistics

To check IGMP snooping statistics on the switch, perform this task:

Task

Command

Display IGMP snooping statistics.

show igmp statistics [vlan_id]

This example shows how to display IGMP snooping statistics:
Console> (enable) show igmp statistics
IGMP enabled
IGMP fastleave enabled
IGMP statistics for vlan 1:
Total valid pkts rcvd:           18951
Total invalid pkts recvd         0
General Queries recvd            377
Group Specific Queries recvd     0
MAC-Based General Queries recvd  0
Leaves recvd                     14
Reports recvd                    16741
Other Pkts recvd                 0
Queries  Xmitted                 0
GS Queries Xmitted               16
Reports Xmitted                  0
Leaves Xmitted                   0
Failures to add GDA to EARL      0
Topology Notifications rcvd      10
Console> (enable) 
Disabling IGMP Fast-Leave Processing

To disable IGMP fast-leave processing, perform this task in privileged mode:

Task

Command

Disable IGMP fast-leave processing on the switch.

set igmp fastleave disable

This example shows how to disable IGMP fast-leave processing on the switch:
Console> (enable) set igmp fastleave disable
IGMP fastleave set to disable.
Console> (enable) 
Disabling IGMP

To disable IGMP snooping on the switch, perform this task in privileged mode:

Task

Command

Disable IGMP snooping on the switch.

set igmp disable

This example shows how to disable IGMP snooping:
Console> (enable) set igmp disable
IGMP feature for IP multicast disabled
Console> (enable)
Configuring RGMP

The following sections describe the commands for configuring RGMP on your switch.

•Default RGMP Configuration

•Enabling and Disabling RGMP

•Displaying RGMP Group Information

•Displaying and Clearing RGMP VLAN Statistics

•Displaying RGMP-Capable Router Ports

•Displaying Multicast Protocol Status

•Clearing RGMP Statistics

•RGMP-Related CLI Commands

Default RGMP Configuration

Table 16-4 shows the RGMP default configuration.

Table 16-4 RGMP Default Configuration

Feature

Default Value

RGMP

Disabled

Enabling and Disabling RGMP

Note To enable RGMP, you must have IGMP enabled.

To enable or disable RGMP, perform the following task in privileged mode:

Task

Command

Enable RGMP.

set rgmp enable

Disable RGMP.

set rgmp disable

This example shows how to enable RGMP:
Console> (enable) set rgmp enable
RGMP enabled.
This example shows how to disable RGMP:
Console> (enable) set rgmp disable
RGMP disabled.
Displaying RGMP Group Information

Use these commands to display all multicast groups that were joined by one or more RGMP-capable routers and to display the count of multicast groups that were joined by one or more RGMP-capable routers.

To display RGMP group information, perform these tasks in privileged mode:

Task

Command

Display all multicast groups that were joined by one or more RGMP-capable routers.

show rgmp group [mac_addr] [vlan_id]

Display the count of multicast groups that were joined by one or more RGMP-capable routers.

show rgmp group count [vlan_id]

This example shows how to display RGMP group information:
Console> show rgmp group
Vlan	Dest MAC/Route Des	RGMP Joined Router Ports
---------------------------------------------------------------------------------------
1	01-00-5e-00-01-28	5/1,5/15
1	01-00-5e-01-01-01	5/1
2	01-00-5e-27-23-70*		3/1, 5/1
Total Number of Entries = 3
`*' - Configured
Console> show rgmp group count 1
Total Number of Entries = 2
Console>
Displaying and Clearing RGMP VLAN Statistics

To display and clear RGMP statistics for a given VLAN, perform one of these tasks in privileged mode:

Task

Command

Display the RGMP statistics for a specified VLAN.

show rgmp statistics [vlan]

Clear RGMP statistics

clear rgmp statistics

This example shows how to display RGMP statistics:
Console> show rgmp statistics 23
RGMP enabled
RGMP Statistics for vlan <23>:
Receive:
Valid pkts:	20
Hellos:	10
Joins:	5
Leaves:	5
Byes:	0
Discarded:	0
Transmit:
Total Pkts:	10
Failures:	0
Hellos:	10
Joins:	0
Leaves:	0
Byes:	0
Console>
This example shows how to clear RGMP statistics:
Console> (enable) clear rgmp statistics
Displaying RGMP-Capable Router Ports

This command displays detected RGMP-capable routers. A plus in front of the router port indicates that it is an RGMP-capable router.

To display RGMP-capable router ports, perform the following task in privileged mode:

Task

Command

Display RGMP-capable router ports.

show multicast router [igmp | rgmp] [mod/port] [vlan_id]

This example shows how to display RGMP-capable router ports:
Console> show multicast router
Port	Vlan
------	------
5/1 +	1
5/14 +	2
5/15	1
Total Number of Entries = 3
'*' - Configured
'+' - RGMP-capable
Console>
Displaying Multicast Protocol Status

This command displays the status (enabled or disabled) of the Layer-2 multicast protocols on the switch.

To display the multicast protocol status, perform the following task in privileged mode:

Task

Command

Display the multicast protocol status.

show multicast protocols status

This example shows how to display the multicast protocol status:
Console> show multicast protocols status
IGMP disabled
IGMP fastleave enabled
RGMP enabled
GMRP disabled
Console>
Clearing RGMP Statistics

To clear stored RGMP statistics, perform the following task in privileged mode:

Task

Command

Clear RGMP statistics.

clear rgmp statistics

This example shows how to clear RGMP statistics:
Console> (enable) clear rgmp statistics
RGMP-Related CLI Commands

The following RGMP-related commands are accessible from the router:

Command

Purpose </