02-IGMP Snooping Configuration
Chapters Download (404.05 KB)
Basic Concepts in IGMP Snooping
IGMP Snooping Configuration Task List
Configuring Basic Functions of IGMP Snooping
Configuring the Version of IGMP Snooping
Configuring IGMP Snooping Port Functions
Configuring Aging Timers for Dynamic Ports
Configuring Fast Leave Processing
Configuring IGMP Snooping Querier
Enabling IGMP Snooping Querier
Configuring IGMP Queries and Responses
Configuring Source IP Address of IGMP Queries
Configuring IGMP Snooping Proxying
Enabling IGMP Snooping Proxying
Configuring a Source IP Address for the IGMP Messages Sent by the Proxy
Configuring an IGMP Snooping Policy
Configuring a Multicast Group Filter
Configuring the Function of Dropping Unknown Multicast Data
Configuring IGMP Report Suppression
Configuring Maximum Multicast Groups that Can Be Joined on a Port
Configuring Multicast Group Replacement
Configuring 802.1p Precedence for IGMP Messages
Displaying and Maintaining IGMP Snooping
IGMP Snooping Configuration Examples
Group Policy and Simulated Joining Configuration Example
Static Port Configuration Example
IGMP Snooping Querier Configuration Example
IGMP Snooping Proxying Configuration Example
Troubleshooting IGMP Snooping Configuration
Switch Fails in Layer 2 Multicast Forwarding
Configured Multicast Group Policy Fails to Take Effect
When configuring IGMP Snooping, go to the following sections for information you are interested in:
l IGMP Snooping Configuration Task List
l Displaying and Maintaining IGMP Snooping
l IGMP Snooping Configuration Examples
l Troubleshooting IGMP Snooping Configuration
Internet Group Management Protocol Snooping (IGMP Snooping) is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups.
By analyzing received IGMP messages, a Layer 2 device running IGMP Snooping establishes mappings between ports and multicast MAC addresses and forwards multicast data based on these mappings.
As shown in Figure 1-1, when IGMP Snooping is not running on the switch, multicast packets are broadcast to all devices at Layer 2. When IGMP Snooping is running on the switch, multicast packets for known multicast groups are multicast to the receivers, rather than broadcast to all hosts, at Layer 2.
Figure 1-1 Before and after IGMP Snooping is enabled on the Layer 2 device
IGMP Snooping forwards multicast data to only the receivers requiring it at Layer 2. It brings the following advantages:
l Reducing Layer 2 broadcast packets, thus saving network bandwidth.
l Enhancing the security of multicast traffic.
l Facilitating the implementation of per-host accounting.
As shown in Figure 1-2, Router A connects to the multicast source, IGMP Snooping runs on Switch A and Switch B, and Host A and Host C are receiver hosts (namely, multicast group members).
Figure 1-2 IGMP Snooping related ports
Ports involved in IGMP Snooping, as shown in Figure 1-2, are described as follows:
l Router port: A router port is a port on an Ethernet switch that leads the switch towards a Layer 3 multicast device (DR or IGMP querier). In the figure, GigabitGigabitEthernet 1/0/0/1 of Switch A and GigabitGigabitEthernet 1/0/0/1 of Switch B are router ports. The switch registers all its local router ports in its router port list.
l Member port: A member port is a port on an Ethernet switch that leads the switch towards multicast group members. In the figure, GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 of Switch A and GigabitEthernet 1/0/2 of Switch B are member ports. The switch registers all the member ports on the local device in its IGMP Snooping forwarding table.
l Whenever mentioned in this document, a router port is a port on the switch that leads the switch to a Layer 3 multicast device, rather than a port on a router.
l Unless otherwise specified, router/member ports mentioned in this document include static and dynamic ports.
l An IGMP-snooping-enabled switch deems that all its ports on which IGMP general queries with the source IP address other than 0.0.0.0 or PIM hello messages are received are dynamic router ports.
Table 1-1 Aging timers for dynamic ports in IGMP Snooping and related messages and actions
|
Timer |
Description |
Message before expiry |
Action after expiry |
|
Dynamic router port aging timer |
For each dynamic router port, the switch sets a timer initialized to the dynamic router port aging time. |
IGMP general query of which the source address is not 0.0.0.0 or PIM hello |
The switch removes this port from its router port list. |
|
Dynamic member port aging timer |
When a port dynamically joins a multicast group, the switch sets a timer for the port, which is initialized to the dynamic member port aging time. |
IGMP membership report |
The switch removes this port from the IGMP Snooping forwarding table. |
The port aging mechanism of IGMP Snooping works only for dynamic ports; a static port will never age out.
A switch running IGMP Snooping performs different actions when it receives different IGMP messages, as follows:
The description about adding or deleting a port in this section is only for a dynamic port. Static ports can be added or deleted only through the corresponding configurations. For details, see Configuring Static Ports.
The IGMP querier periodically sends IGMP general queries to all hosts and routers (224.0.0.1) on the local subnet to find out whether active multicast group members exist on the subnet.
Upon receiving an IGMP general query, the switch forwards it through all ports in the VLAN except the receiving port and performs the following to the receiving port:
l If the receiving port is a dynamic router port existing in its router port list, the switch resets the aging timer of this dynamic router port.
l If the receiving port is not a dynamic router port existing in its router port list, the switch adds it into its router port list and sets an aging timer for this dynamic router port.
A host sends an IGMP report to the IGMP querier in the following circumstances:
l Upon receiving an IGMP query, a multicast group member host responds with an IGMP report.
l When intended to join a multicast group, a host sends an IGMP report to the IGMP querier to announce that it is interested in the multicast information addressed to that group.
Upon receiving an IGMP report, the switch forwards it through all the router ports in the VLAN, resolves the address of the reported multicast group, and performs the following:
l If no forwarding table entry exists for the reported group, the switch creates an entry, adds the port as a dynamic member port to the outgoing port list, and starts a member port aging timer for that port.
l If a forwarding table entry exists for the reported group, but the port is not included in the outgoing port list for that group, the switch adds the port as a dynamic member port to the outgoing port list, and starts an aging timer for that port.
l If a forwarding table entry exists for the reported group and the port is included in the outgoing port list, which means that this port is already a dynamic member port, the switch resets the aging timer for that port.
A switch does not forward an IGMP report through a non-router port. This is because if the switch forwards a report message through a member port, all the attached hosts listening to the reported multicast address will suppress their own reports upon receiving this report according to the IGMP report suppression mechanism on them, and this will prevent the switch from knowing whether the reported multicast group still has active members attached to that port.
When an IGMPv1 host leaves a multicast group, the host does not send an IGMP leave message, so the switch cannot know immediately that the host has left the multicast group. However, as the host stops sending IGMP reports as soon as it leaves a multicast group, the switch deletes the forwarding entry for the dynamic member port corresponding to the host from the forwarding table when its aging timer expires.
When an IGMPv2 or IGMPv3 host leaves a multicast group, the host sends an IGMP leave message to the multicast router.
When the switch receives an IGMP leave message on a dynamic member port, the switch first checks whether a forwarding table entry for the group address in the message exists, and, if one exists, whether the outgoing port list contains the port.
l If the forwarding table entry does not exist or if the outgoing port list does not contain the port, the switch discards the IGMP leave message instead of forwarding it to any port.
l If the forwarding table entry exists and the outgoing port list contains the port, the switch forwards the leave message to all router ports in the native VLAN. Because the switch does not know whether any other hosts attached to the port are still listening to that group address, the switch does not immediately remove the port from the outgoing port list of the forwarding table entry for that group; instead, it resets the aging timer for the port.
Upon receiving the IGMP leave message from a host, the IGMP querier resolves the multicast group address in the message and sends an IGMP group-specific query to that multicast group through the port that received the leave message. Upon receiving the IGMP group-specific query, the switch forwards it through all its router ports in the VLAN and all member ports for that multicast group, and performs the following to the port on which it received the IGMP leave message:
l If any IGMP report in response to the group-specific query is received on the port (suppose it is a dynamic member port) before its aging timer expires, this means that some host attached to the port is receiving or expecting to receive multicast data for that multicast group. The switch resets the aging timer of the port.
l If no IGMP report in response to the group-specific query is received on the port before its aging timer expires, this means that no hosts attached to the port are still listening to that group address: the switch removes the port from the outgoing port list of the forwarding table entry for that multicast group when the aging timer expires.
You can configure the IGMP snooping proxying function on an edge device, which then can represent its attached hosts to send membership reports and leave messages, thus reducing the number of IGMP reports and leave messages sent to its upstream device. The device configured with IGMP snooping proxying is called an IGMP snooping proxy. It is a host from the perspective of its upstream device.
Even though an IGMP Snooping proxy is a host from the perspective of its upstream device, the IGMP membership report suppression mechanism for hosts does not take effect on it.
Figure 1-3 Network diagram for IGMP Snooping Proxying
As shown in Figure 1-3, Switch A works as an IGMP Snooping proxy. It represents its attached hosts to send membership reports and leave messages to Router A.
Table 1-2 describes how an IGMP Snooping proxy processes IGMP messages.
Table 1-2 IGMP message processing on an IGMP Snooping proxy
|
IGMP message |
Actions |
|
General query |
When receiving an IGMP general query, the proxy forwards it to all ports but the receiving port. In addition, the proxy generates a report according to the group memberships it maintains and sends the report out all router ports. |
|
Group-specific query |
In response to the IGMP group-specific query for a certain multicast group, the proxy sends the report to the group out all router ports if the forwarding entry for the group still contains a member port. |
|
Report |
When receiving a report for a multicast group, the proxy looks up the multicast forwarding table for the entry for the multicast group. If the forwarding entry is found with the receiving port contained as a dynamic member port in the outgoing port list, the proxy resets the aging timer for the entry. If the forwarding entry is found but the outgoing port list does not include the receiving port, the proxy adds the port to the outgoing port list as a dynamic member port and starts an aging timer for it. If no forwarding entry is found, the proxy creates the entry, adds the receiving port to the outgoing port list as a dynamic member port and starts an aging timer for the port, and then, sends a report to the group out all router ports. |
|
Leave |
In response to an IGMP leave message for a multicast group, the proxy sends a group-specific query out the receiving port. After making sure that no member port is contained in the forwarding entry for the multicast group, the proxy sends a leave message to the group out all router ports. |
IGMP Snooping is documented in:
l RFC 4541: Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches
Complete these tasks to configure IGMP Snooping:
|
Task |
Remarks |
|
|
Required |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Configuring a Source IP Address for the IGMP Messages Sent by the Proxy |
Optional |
|
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Configuring Maximum Multicast Groups that Can Be Joined on a Port |
Optional |
|
|
Optional |
||
|
Optional |
||
l Configurations made in IGMP Snooping view are effective for all VLANs, while configurations made in VLAN view are effective only for ports belonging to the current VLAN. For a given VLAN, a configuration made in IGMP Snooping view is effective only if the same configuration is not made in VLAN view.
l Configurations made in IGMP Snooping view are effective for all ports; configurations made in Ethernet interface view are effective only for the current port; configurations made in Layer 2 aggregate interface view are effect only for the current interface; configurations made in port group view are effective only for all the ports in the current port group. For a given port, a configuration made in IGMP Snooping view is effective only if the same configuration is not made in Ethernet interface view, Layer 2 aggregate interface view or port group view.
l For IGMP Snooping, configurations made on a Layer 2 aggregate interface do not interfere with configurations made on its member ports, nor do they take part in aggregation calculations; configurations made on a member port of the aggregate group will not take effect until it leaves the aggregate group.
Before configuring the basic functions of IGMP Snooping, complete the following task:
l Configure the corresponding VLANs.
Before configuring the basic functions of IGMP Snooping, prepare the following data:
l Version of IGMP Snooping.
Follow these steps to enable IGMP Snooping:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enable IGMP Snooping globally and enter IGMP-Snooping view |
igmp-snooping |
Required Disabled by default |
|
Return to system view |
quit |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Enable IGMP Snooping in the VLAN |
igmp-snooping enable |
Required Disabled by default |
l IGMP Snooping must be enabled globally before it can be enabled in a VLAN.
l When you enable IGMP Snooping in a specified VLAN, this function takes effect for the ports in this VLAN only.
By configuring an IGMP Snooping version, you actually configure the version of IGMP messages that IGMP Snooping can process.
l IGMP Snooping version 2 can process IGMPv1 and IGMPv2 messages, but not IGMPv3 messages, which will be flooded in the VLAN.
l IGMP Snooping version 3 can process IGMPv1, IGMPv2 and IGMPv3 messages.
Follow these steps to configure the version of IGMP Snooping:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Configure the version of IGMP Snooping |
igmp-snooping version version-number |
Optional Version 2 by default |
If you switch IGMP Snooping from version 3 to version 2, the system will clear all IGMP Snooping forwarding entries from dynamic joins, and will:
l Keep forwarding entries for version 3 static (*, G) joins;
l Clear forwarding entries from version 3 static (S, G) joins, which will be restored when IGMP Snooping is switched back to version 3.
For details about static joins, Refer to Configuring Static Ports.
Before configuring IGMP Snooping port functions, complete the following tasks:
l Enable IGMP Snooping in the VLAN
l Configure the corresponding port groups.
Before configuring IGMP Snooping port functions, prepare the following data:
l Aging time of dynamic router ports,
l Aging time of dynamic member ports, and
l Multicast group and multicast source addresses
If the switch receives no IGMP general queries or PIM hello messages on a dynamic router port, the switch removes the port from the router port list when the aging timer of the port expires.
If the switch receives no IGMP reports for a multicast group on a dynamic member port, the switch removes the port from the outgoing port list of the forwarding table entry for that multicast group when the aging timer of the port for that group expires.
If multicast group memberships change frequently, you can set a relatively small value for the dynamic member port aging timer, and vice versa.
Follow these steps to configure aging timers for dynamic ports globally:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP Snooping view |
igmp-snooping |
— |
|
Configure dynamic router port aging time |
router-aging-time interval |
Optional 105 seconds by default |
|
Configure dynamic member port aging time |
host-aging-time interval |
Optional 260 seconds by default |
Follow these steps to configure aging timers for dynamic ports in a VLAN:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Configure dynamic router port aging time |
igmp-snooping router-aging-time interval |
Optional 105 seconds by default |
|
Configure dynamic member port aging time |
igmp-snooping host-aging-time interval |
Optional 260 seconds by default |
If all the hosts attached to a port are interested in the multicast data addressed to a particular multicast group or the multicast data that a particular multicast source sends to a particular group, you can configure static (*, G) or (S, G) joining on that port, namely configure the port as a group-specific or source-and-group-specific static member port.
You can configure a port of a switch to be a static router port, through which the switch can forward all the multicast traffic it received.
Follow these steps to configure static ports:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet interface/Layer 2 aggregate interface view or port group view |
interface interface-type interface-number |
Required Use either approach |
|
port-group manual port-group-name |
||
|
Configure the port(s) as static member port(s) |
igmp-snooping static-group group-address [ source-ip source-address ] vlan vlan-id |
Required No static member ports by default |
|
Configure the port(s) as static router port(s) |
igmp-snooping static-router-port vlan vlan-id |
Required No static router ports by default |
l A static member port does not respond to queries from the IGMP querier; when static (*, G) or (S, G) joining is enabled or disabled on a port, the port does not send an unsolicited IGMP report or an IGMP leave message.
l Static member ports and static router ports never age out. To remove such a port, you need to use the corresponding undo command.
Generally, a host running IGMP responds to IGMP queries from the IGMP querier. If a host fails to respond due to some reasons, the multicast router may deem that no member of this multicast group exists on the network segment, and therefore will remove the corresponding forwarding path.
To avoid this situation from happening, you can enable simulated joining on a port of the switch, namely configure the port as a simulated member host for a multicast group. When receiving an IGMP query, the simulated host gives a response. Thus, the switch can continue receiving multicast data.
A simulated host acts like a real host, as follows:
l When a port is configured as a simulated member host, the switch sends an unsolicited IGMP report through that port.
l After a port is configured as a simulated member host, the switch responds to IGMP general queries by sending IGMP reports through that port.
l When the simulated joining function is disabled on a port, the switch sends an IGMP leave message through that port.
Follow these steps to configure simulated joining:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet interface/Layer 2 aggregate interface view or port group view |
interface interface-type interface-number |
Required Use either approach |
|
port-group manual port-group-name |
||
|
Configure simulated (*, G) or (S, G) joining |
igmp-snooping host-join group-address [ source-ip source-address ] vlan vlan-id |
Required Disabled by default |
l Each simulated host is equivalent to an independent host. For example, when receiving an IGMP query, the simulated host corresponding to each configuration responds respectively.
l Unlike a static member port, a port configured as a simulated member host will age out like a dynamic member port.
In VLANs where only one host is attached to each port, fast leave processing helps improve bandwidth and resource usage. However, if fast leave processing is enabled on a port to which more than one host is attached, when one host leaves a multicast group, the other hosts attached to the port and interested in the same multicast group will fail to receive multicast data for that group. Therefore, if the function of dropping unknown multicast traffic is already enabled on the switch or in the VLANs, the fast leave processing function should not be enabled.
Follow these steps to configure fast leave processing globally:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP Snooping view |
igmp-snooping |
— |
|
Enable fast leave processing |
fast-leave [ vlan vlan-list ] |
Required Disabled by default |
Follow these steps to configure fast leave processing on a port or a group of ports:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet interface/Layer 2 aggregate interface view or port group view |
interface interface-type interface-number |
Required Use either approach |
|
port-group manual port-group-name |
||
|
Enable fast leave processing |
igmp-snooping fast-leave [ vlan vlan-list ] |
Required Disabled by default |
Before configuring IGMP Snooping querier, complete the following task:
l Enable IGMP Snooping in the VLAN.
Before configuring IGMP Snooping querier, prepare the following data:
l IGMP general query interval,
l IGMP last-member query interval,
l Maximum response time to IGMP general queries,
l Source address of IGMP general queries, and
l Source address of IGMP group-specific queries.
However, a Layer 2 multicast switch does not support IGMP, and therefore cannot send general queries by default. By enabling IGMP Snooping on a Layer 2 switch in a VLAN where multicast traffic needs to be Layer-2 switched only and no multicast routers are present, the Layer 2 switch will act as the IGMP Snooping querier to send IGMP queries, thus allowing multicast forwarding entries to be established and maintained at the data link layer.
Follow these steps to enable IGMP Snooping querier:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Enable IGMP Snooping querier |
igmp-snooping querier |
Required Disabled by default |
It is meaningless to configure an IGMP Snooping querier in a multicast network running IGMP. Although an IGMP Snooping querier does not take part in IGMP querier elections, it may affect IGMP querier elections because it sends IGMP general queries with a low source IP address.
You can tune the IGMP general query interval based on actual condition of the network.
Upon receiving an IGMP query (general query or group-specific query), a host starts a timer for each multicast group it has joined. This timer is initialized to a random value in the range of 0 to the maximum response time (the host obtains the value of the maximum response time from the Max Response Time field in the IGMP query it received). When the timer value comes down to 0, the host sends an IGMP report to the corresponding multicast group.
An appropriate setting of the maximum response time for IGMP queries allows hosts to respond to queries quickly and avoids bursts of IGMP traffic on the network caused by reports simultaneously sent by a large number of hosts when the corresponding timers expire simultaneously.
l For IGMP general queries, you can configure the maximum response time to fill their Max Response time field.
l For IGMP group-specific queries, you can configure the IGMP last-member query interval to fill their Max Response time field. Namely, for IGMP group-specific queries, the maximum response time equals to the IGMP last-member query interval.
Follow these steps to configure IGMP queries and responses globally:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP Snooping view |
igmp-snooping |
— |
|
Configure the maximum response time to IGMP general queries |
max-response-time interval |
Optional 10 seconds by default |
|
Configure the IGMP last-member query interval |
last-member-query-interval interval |
Optional 1 second by default |
Follow these steps to configure IGMP queries and responses in a VLAN:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Configure IGMP general query interval |
igmp-snooping query-interval interval |
Optional 60 seconds by default |
|
Configure the maximum response time to IGMP general queries |
igmp-snooping max-response-time interval |
Optional 10 seconds by default |
|
Configure the IGMP last-member query interval |
igmp-snooping last-member-query-interval interval |
Optional 1 second by default |
In the configuration, make sure that the IGMP general query interval is larger than the maximum response time for IGMP general queries. Otherwise, multicast group members may be deleted by mistake.
Upon receiving an IGMP query whose source IP address is 0.0.0.0 on a port, the switch does not enlist that port as a dynamic router port. This may prevent multicast forwarding entries from being correctly created at the data link layer and cause multicast traffic forwarding failure in the end. When a Layer 2 device acts as an IGMP-Snooping querier, to avoid the aforesaid problem, you are commended to configure a non-all-zero IP address as the source IP address of IGMP queries.
Follow these steps to configure source IP address of IGMP queries:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Configure the source address of IGMP general queries |
igmp-snooping general-query source-ip { ip-address | current-interface } |
Optional 0.0.0.0 by default |
|
Configure the source IP address of IGMP group-specific queries |
igmp-snooping special-query source-ip { ip-address | current-interface } |
Optional 0.0.0.0 by default |
The source address of IGMP query messages may affect IGMP querier selection within the segment.
Before configuring IGMP Snooping Proxying in a VLAN, enable IGMP Snooping in the VLAN and prepare the following data:
l Source IP address for the IGMP reports sent by the proxy
l Source IP address for the IGMP leave messages sent by the proxy
The IGMP Snooping Proxying function works on a per-VLAN basis. After you enable the function in a VLAN, the device works as the IGMP Snooping proxy for the downstream hosts and upstream router in the VLAN.
Follow these steps to enable IGMP Snooping Proxying in a VLAN:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Enable IGMP Snooping Proxying in the VLAN |
igmp-snooping proxying enable |
Required Disabled by default. |
You can set the source IP addresses in the IGMP reports and leave messages sent by the IGMP Snooping proxy on behalf of its attached hosts.
Follow these steps to configure the source IP addresses for the IGMP messages sent by the IGMP Snooping proxy on behalf of its attached hosts in a VLAN:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Configure a source IP address for the IGMP reports sent by the proxy |
igmp-snooping report source-ip { ip-address | current-interface } |
Required The default is 0.0.0.0. |
|
Configure a source IP address for the IGMP leave messages sent by the proxy |
igmp-snooping leave source-ip { ip-address | current-interface } |
The default is 0.0.0.0. |
Before configuring an IGMP Snooping policy, complete the following task:
l Enable IGMP Snooping in the VLAN
Before configuring an IGMP Snooping policy, prepare the following data:
l ACL rule for multicast group filtering
l The maximum number of multicast groups that can pass the ports
l 802.1p precedence for IGMP messages
On an IGMP Snooping–enabled switch, the configuration of a multicast group allows the service provider to define restrictions on multicast programs available to different users.
In an actual application, when a user requests a multicast program, the user’s host initiates an IGMP report. Upon receiving this report message, the switch checks the report against the configured ACL rule. If the port on which the report was received can join this multicast group, the switch adds an entry for this port in the IGMP Snooping forwarding table; otherwise the switch drops this report message. Any multicast data that has failed the ACL check will not be sent to this port. In this way, the service provider can control the VOD programs provided for multicast users.
Follow these steps to configure a multicast group filter globally:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP Snooping view |
igmp-snooping |
— |
|
Configure a multicast group filter |
group-policy acl-number [ vlan vlan-list ] |
Required No group filter is configured by default. |
Follow these steps to configure a multicast group filter on a port or a group of ports:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet interface/Layer 2 aggregate interface view or port group view |
interface interface-type interface-number |
Required Use either approach |
|
port-group manual port-group-name |
||
|
Configure a multicast group filter |
igmp-snooping group-policy acl-number [ vlan vlan-list ] |
Required No group filter is configured by default. |
If the specified ACL does not exist or the ACL rule is null, all multicast groups will be filtered out.
Unknown multicast data refers to multicast data for which no entries exist in the IGMP Snooping forwarding table. When receiving such multicast traffic, the switch floods it in the VLAN, incurring network bandwidth waste and low forwarding efficiency.
With the function of dropping unknown multicast data enabled, the switch forwards unknown multicast data to its router ports instead of flooding it in the VLAN. If no router ports exist, the switch drops the unknown multicast data
Follow these steps to configure the function of dropping unknown multicast data in a VLAN:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Enable the function of dropping unknown multicast data |
igmp-snooping drop-unknown |
Required Disabled by default |
When a Layer 2 device receives an IGMP report from a multicast group member, the device forwards the message to the Layer 3 device directly connected with it. Thus, when multiple members of a multicast group are attached to the Layer 2 device, the Layer 3 device directly connected with it will receive duplicate IGMP reports from these members.
With the IGMP report suppression function enabled, within each query cycle, the Layer 2 device forwards only the first IGMP report per multicast group to the Layer 3 device and will not forward the subsequent IGMP reports from the same multicast group to the Layer 3 device. This helps reduce the number of packets being transmitted over the network.
Follow these steps to configure IGMP report suppression:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP Snooping view |
igmp-snooping |
— |
|
Enable IGMP report suppression |
report-aggregation |
Optional Enabled by default |
On an IGMP snooping proxy, IGMP membership reports are suppressed if the entries for the corresponding groups exist in the forwarding table, no matter the suppression function is enabled or not.
By configuring the maximum number of multicast groups that can be joined on a port, you can limit the number of multicast programs on-demand available to users, thus to regulate traffic on the port.
Follow these steps to configure the maximum number of multicast groups allowed on a port or ports:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet interface/Layer 2 aggregate interface view or port group view |
interface interface-type interface-number |
Required Use either approach |
|
port-group manual port-group-name |
||
|
Configure the maximum number of multicast groups allowed on the port(s) |
igmp-snooping group-limit limit [ vlan vlan-list ] |
Optional By default, the maximum number of multicast groups allowed on the port(s) is 1000 |
l When the number of multicast groups a port has joined reaches the maximum number configured, the system deletes all the forwarding entries persistent to that port from the IGMP Snooping forwarding table, and the hosts on this port need to join the multicast groups again.
l If you have configured static or simulated joins on a port, however, when the number of multicast groups on the port exceeds the configured threshold, the system deletes all the forwarding entries persistent to that port from the IGMP Snooping forwarding table and applies the static or simulated joins again, until the number of multicast groups joined by the port comes back within the configured threshold.
For some special reasons, the number of multicast groups that can be joined on the current switch or port may exceed the number configured for the switch or the port. In addition, in some specific applications, a multicast group newly joined on the switch needs to replace an existing multicast group automatically. A typical example is “channel switching”, namely, by joining a new multicast group, a user automatically switches from the current multicast group to the new one.
To address such situations, you can enable the multicast group replacement function on the switch or certain ports. When the number of multicast groups joined on the switch or a port has joined reaches the limit:
l If the multicast group replacement feature is enabled, the newly joined multicast group automatically replaces an existing multicast group with the lowest address.
l If the multicast group replacement feature is not enabled, new IGMP reports will be automatically discarded.
Follow these steps to configure multicast group replacement globally:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP Snooping view |
igmp-snooping |
— |
|
Enable multicast group replacement |
overflow-replace [ vlan vlan-list ] |
Required Disabled by default |
Follow these steps to configure multicast group replacement on a port or a group of ports:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter Ethernet interface/Layer 2 aggregate interface view or port group view |
interface interface-type interface-number |
Required Use either approach |
|
port-group manual port-group-name |
||
|
Enable multicast group replacement |
igmp-snooping overflow-replace [ vlan vlan-list ] |
Required Disabled by default |
Be sure to configure the maximum number of multicast groups allowed on a port (refer to Configuring Maximum Multicast Groups that Can Be Joined on a Port) before enabling multicast group replacement. Otherwise, the multicast group replacement functionality will not take effect.
You can change 802.1p precedence of IGMP messages so that they can be assigned higher forwarding priority when congestion occurs on their outgoing ports.
Follow these steps to configure 802.1p precedence for IGMP messages globally:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter IGMP-Snooping view |
igmp-snooping |
— |
|
Configure 802.1p precedence for IGMP messages |
dot1p-priority priority-number |
Required The default 802.1p precedence for IGMP messages is 0. |
Follow these steps to configure 802.1p precedence for IGMP messages in a VLAN:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter VLAN view |
vlan vlan-id |
— |
|
Configure 802.1p precedence for IGMP messages in the VLAN |
igmp-snooping dot1p-priority priority-number |
Required The default 802.1p precedence for IGMP messages is 0. |
|
To do... |
Use the command... |
Remarks |
|
Display IGMP Snooping multicast group information |
display igmp-snooping group [ vlan vlan-id ] [ verbose ] |
Available in any view |
|
Display the statistics information of IGMP messages learned by IGMP Snooping |
display igmp-snooping statistics |
Available in any view |
|
Clear IGMP Snooping multicast group information |
reset igmp-snooping group { group-address | all } [ vlan vlan-id ] |
Available in user view |
|
Clear the statistics information of all kinds of IGMP messages learned by IGMP Snooping |
reset igmp-snooping statistics |
Available in user view |
l The reset igmp-snooping group command works only on an IGMP Snooping–enabled VLAN.
l The reset igmp-snooping group command cannot clear the IGMP Snooping multicast group information for static joins.
l As shown in Figure 1-4, Router A connects to the multicast source through GigabitEthernet 1/0/2 and to Switch A through GigabitEthernet 1/0/1.
l IGMPv2 is required on Router A, IGMP Snooping version 2 is required on Switch A, and Router A will act as the IGMP querier on the subnet.
l It is required that the receivers, Host A and Host B, attached to Switch A can receive multicast traffic addressed to multicast group 224.1.1.1 only.
l It is required that multicast data for group 224.1.1.1 can be forwarded through GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Switch A even if Host A and Host B accidentally, temporarily stop receiving multicast data.
Figure 1-4 Network diagram for group policy simulated joining configuration
Configure an IP address and subnet mask for each interface as per Figure 1-4. The detailed configuration steps are omitted.
2) Configure Router A
# Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
<RouterA> system-view
[RouterA] multicast routing-enable
[RouterA] interface gigabitethernet 1/0/1
[RouterA-GigabitEthernet1/0/1] igmp enable
[RouterA-GigabitEthernet1/0/1] pim dm
[RouterA-GigabitEthernet1/0/1] quit
[RouterA] interface gigabitethernet 1/0/2
[RouterA-GigabitEthernet1/0/2] pim dm
[RouterA-GigabitEthernet1/0/2] quit
3) Configure Switch A
# Enable IGMP Snooping globally.
<SwitchA> system-view
[SwitchA] igmp-snooping
[SwitchA-igmp-snooping] quit
# Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP Snooping and the function of dropping unknown multicast traffic in the VLAN.
[SwitchA] vlan 100
[SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4
[SwitchA-vlan100] igmp-snooping enable
[SwitchA-vlan100] igmp-snooping drop-unknown
[SwitchA-vlan100] quit
# Configure a multicast group filter so that the hosts in VLAN 100 can join only the multicast group 224.1.1.1.
[SwitchA] acl number 2001
[SwitchA-acl-basic-2001] rule permit source 224.1.1.1 0
[SwitchA-acl-basic-2001] quit
[SwitchA] igmp-snooping
[SwitchA-igmp-snooping] group-policy 2001 vlan 100
[SwitchA-igmp-snooping] quit
# Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as simulated hosts for multicast group 224.1.1.1.
[SwitchA] interface gigabitethernet 1/0/3
[SwitchA-GigabitEthernet1/0/3] igmp-snooping host-join 224.1.1.1 vlan 100
[SwitchA-GigabitEthernet1/0/3] quit
[SwitchA] interface gigabitethernet 1/0/4
[SwitchA-GigabitEthernet1/0/4] igmp-snooping host-join 224.1.1.1 vlan 100
[SwitchA-GigabitEthernet1/0/4] quit
4) Verify the configuration
# Display the detailed IGMP Snooping multicast groups information in VLAN 100 on Switch A.
[SwitchA] display igmp-snooping group vlan 100 verbose
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Port flags: D-Dynamic port, S-Static port, C-Copy port
Subvlan flags: R-Real VLAN, C-Copy VLAN
Vlan(id):100.
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Router port(s):total 1 port.
GE1/0/1 (D) ( 00:01:30 )
IP group(s):the following ip group(s) match to one mac group.
IP group address:224.1.1.1
(0.0.0.0, 224.1.1.1):
Attribute: Host Port
Host port(s):total 2 port.
GE1/0/3 (D) ( 00:03:23 )
GE1/0/4 (D) ( 00:04:10 )
MAC group(s):
MAC group address:0100-5e01-0101
Host port(s):total 2 port.
GE1/0/3
GE1/0/4
As shown above, GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 of Switch A has joined multicast group 224.1.1.1.
l As shown in Figure 1-5, Router A connects to a multicast source (Source) through GigabitEthernet 1/0/2, and to Switch A through GigabitEthernet 1/0/1.
l IGMPv2 is to run on Router A, and IGMPv2 Snooping is to run on Switch A, Switch B and Switch C, with Router A acting as the IGMP querier.
l Host A and host C are permanent receivers of multicast group 224.1.1.1. GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 on Switch C are required to be configured as static member ports for multicast group 224.1.1.1 to enhance the reliability of multicast traffic transmission.
l Suppose STP runs on the network. To avoid data loops, the forwarding path from Switch A to Switch C is blocked under normal conditions, and multicast traffic flows to the receivers attached to Switch C only along the path of Switch A—Switch B—Switch C.
l It is required to configure GigabitEthernet 1/0/3 that connects Switch A to Switch C as a static router port, so that multicast traffic can flow to the receivers nearly uninterruptedly along the path of Switch A—Switch C in the case that the path of Switch A—Switch B—Switch C gets blocked.
If no static router port is configured, when the path of Switch A—Switch B—Switch C gets blocked, at least one IGMP query-response cycle must be completed before the multicast data can flow to the receivers along the new path of Switch A—Switch C, namely multicast delivery will be interrupted during this process.
Figure 1-5 Network diagram for static port configuration
1) Configure IP addresses
Configure an IP address and subnet mask for each interface as per Figure 1-5. The detailed configuration steps are omitted.
2) Configure Router A
# Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
<RouterA> system-view
[RouterA] multicast routing-enable
[RouterA] interface gigabitethernet 1/0/1
[RouterA-GigabitEthernet1/0/1] igmp enable
[RouterA-GigabitEthernet1/0/1] pim dm
[RouterA-GigabitEthernet1/0/1] quit
[RouterA] interface gigabitethernet 1/0/2
[RouterA-GigabitEthernet1/0/2] pim dm
[RouterA-GigabitEthernet1/0/2] quit
3) Configure Switch A
# Enable IGMP Snooping globally.
<SwitchA> system-view
[SwitchA] igmp-snooping
[SwitchA-igmp-snooping] quit
# Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to this VLAN, and enable IGMP Snooping in the VLAN.
[SwitchA] vlan 100
[SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3
[SwitchA-vlan100] igmp-snooping enable
[SwitchA-vlan100] quit
# Configure GigabitEthernet 1/0/3 to be a static router port.
[SwitchA] interface gigabitethernet 1/0/3
[SwitchA-GigabitEthernet1/0/3] igmp-snooping static-router-port vlan 100
[SwitchA-GigabitEthernet1/0/3] quit
4) Configure Switch B
# Enable IGMP Snooping globally.
<SwitchB> system-view
[SwitchB] igmp-snooping
[SwitchB-igmp-snooping] quit
# Create VLAN 100, assign GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to this VLAN, and enable IGMP Snooping in the VLAN.
[SwitchB] vlan 100
[SwitchB-vlan100] port gigabitethernet 1/0/1 gigabitethernet 1/0/2
[SwitchB-vlan100] igmp-snooping enable
[SwitchB-vlan100] quit
5) Configure Switch C
# Enable IGMP Snooping globally.
<SwitchC> system-view
[SwitchC] igmp-snooping
[SwitchC-igmp-snooping] quit
# Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5 to this VLAN, and enable IGMP Snooping in the VLAN.
[SwitchC] vlan 100
[SwitchC-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/5
[SwitchC-vlan100] igmp-snooping enable
[SwitchC-vlan100] quit
# Configure GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 as static member ports for multicast group 224.1.1.1.
[SwitchC] interface gigabitethernet 1/0/3
[SwitchC-GigabitEthernet1/0/3] igmp-snooping static-group 224.1.1.1 vlan 100
[SwitchC-GigabitEthernet1/0/3] quit
[SwitchC] interface gigabitethernet 1/0/5
[SwitchC-GigabitEthernet1/0/5] igmp-snooping static-group 224.1.1.1 vlan 100
[SwitchC-GigabitEthernet1/0/5] quit
6) Verify the configuration
# Display the detailed IGMP Snooping multicast group information in VLAN 100 on Switch A.
[SwitchA] display igmp-snooping group vlan 100 verbose
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Port flags: D-Dynamic port, S-Static port, C-Copy port
Subvlan flags: R-Real VLAN, C-Copy VLAN
Vlan(id):100.
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Router port(s):total 2 port.
GE1/0/1 (D) ( 00:01:30 )
GE1/0/3 (S)
IP group(s):the following ip group(s) match to one mac group.
IP group address:224.1.1.1
(0.0.0.0, 224.1.1.1):
Attribute: Host Port
Host port(s):total 1 port.
GE1/0/2 (D) ( 00:03:23 )
MAC group(s):
MAC group address:0100-5e01-0101
Host port(s):total 1 port.
GE1/0/2
As shown above, GigabitEthernet 1/0/3 of Switch A has become a static router port.
# Display the detailed IGMP Snooping multicast group information in VLAN 100 on Switch C.
[SwitchC] display igmp-snooping group vlan 100 verbose
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Port flags: D-Dynamic port, S-Static port, C-Copy port
Subvlan flags: R-Real VLAN, C-Copy VLAN
Vlan(id):100.
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Router port(s):total 1 port.
GE1/0/2 (D) ( 00:01:23 )
IP group(s):the following ip group(s) match to one mac group.
IP group address:224.1.1.1
(0.0.0.0, 224.1.1.1):
Attribute: Host Port
Host port(s):total 2 port.
GE1/0/3 (S)
GE1/0/5 (S)
MAC group(s):
MAC group address:0100-5e01-0101
Host port(s):total 2 port.
GE1/0/3
GE1/0/5
As shown above, GigabitEthernet 1/0/3 and GigabitEthernet 1/0/5 on Switch C have become static member ports for multicast group 224.1.1.1.
l As shown in Figure 1-6, in a Layer 2–only network environment, two multicast sources Source 1 and Source 2 send multicast data to multicast groups 224.1.1.1 and 225.1.1.1 respectively, Host A and Host C are receivers of multicast group 224.1.1.1, while Host B and Host D are receivers of multicast group 225.1.1.1.
l All the receivers are running IGMPv2, and all the switches need to run IGMP Snooping version 2. Switch A, which is close to the multicast sources, is chosen as the IGMP-Snooping querier.
l To prevent flooding of unknown multicast traffic within the VLAN, it is required to configure all the switches to drop unknown multicast data packets.
l Because a switch does not enlist a port that has heard an IGMP query with a source IP address of 0.0.0.0 (default) as a dynamic router port, configure a non-all-zero IP address as the source IP address of IGMP queries to ensure normal creation of Layer 2 multicast forwarding entries.
Figure 1-6 Network diagram for IGMP Snooping querier configuration
1) Configure switch A
# Enable IGMP Snooping globally.
<SwitchA> system-view
[SwitchA] igmp-snooping
[SwitchA-igmp-snooping] quit
# Create VLAN 100 and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/3 to the VLAN.
[SwitchA] vlan 100
[SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/3
# Enable IGMP Snooping and the function of dropping unknown multicast traffic in VLAN 100.
[SwitchA-vlan100] igmp-snooping enable
[SwitchA-vlan100] igmp-snooping drop-unknown
# Enable the IGMP-Snooping querier function in VLAN 100
[SwitchA-vlan100] igmp-snooping querier
# Set the source IP address of IGMP general queries and group-specific queries to 192.168.1.1 in VLAN 100.
[SwitchA-vlan100] igmp-snooping general-query source-ip 192.168.1.1
[SwitchA-vlan100] igmp-snooping special-query source-ip 192.168.1.1
[SwitchA-vlan100] quit
2) Configure Switch B
# Enable IGMP Snooping globally.
<SwitchB> system-view
[SwitchB] igmp-snooping
[SwitchB-igmp-snooping] quit
# Create VLAN 100, and assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to the VLAN.
[SwitchB] vlan 100
[SwitchB-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4
# Enable IGMP Snooping and the function of dropping unknown multicast traffic in VLAN 100.
[SwitchB-vlan100] igmp-snooping enable
[SwitchB-vlan100] igmp-snooping drop-unknown
[SwitchB-vlan100] quit
Configurations on Switch C and Switch D are similar to the configuration on Switch B.
3) Verify the configuration
After the IGMP Snooping querier starts to work, all the switches but the querier can receive IGMP general queries. By using the display igmp-snooping statistics command, you can view the statistics information about the IGMP messages received. For example:
# Display the IGMP message statistics on Switch B.
[SwitchB] display igmp-snooping statistics
Received IGMP general queries:3.
Received IGMPv1 reports:0.
Received IGMPv2 reports:12.
Received IGMP leaves:0.
Received IGMPv2 specific queries:0.
Sent IGMPv2 specific queries:0.
Received IGMPv3 reports:0.
Received IGMPv3 reports with right and wrong records:0.
Received IGMPv3 specific queries:0.
Received IGMPv3 specific sg queries:0.
Sent IGMPv3 specific queries:0.
Sent IGMPv3 specific sg queries:0.
Received error IGMP messages:0.
As shown in Figure 1-7,
l Router A connects to a multicast source through port GigabitEthernet 1/0/2, and to Switch A through port GigabitEthernet 1/0/1.
l Router A runs IGMPv2 and Switch A runs IGMPv2 Snooping. Router A serves as an IGMP querier.
Configure IGMP Snooping Proxying on Switch A, enabling the switch to forward IGMP reports and leave messages on behalf of attached hosts and to respond to IGMP queries from Router A and forward the queries to the hosts on behalf of Router A.
Figure 1-7 Network diagram for IGMP Snooping Proxying configuration
1) Configure IP addresses for interfaces
Configure an IP address and subnet mask for each interface as per Figure 1-7. The configuration steps are omitted here.
2) Configure Router A
# Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet 1/0/1.
<RouterA> system-view
[RouterA] multicast routing-enable
[RouterA] interface gigabitethernet 1/0/1
[RouterA-GigabitEthernet1/0/1] igmp enable
[RouterA-GigabitEthernet1/0/1] pim dm
[RouterA-GigabitEthernet1/0/1] quit
[RouterA] interface gigabitethernet 1/0/2
[RouterA-GigabitEthernet1/0/2] pim dm
[RouterA-GigabitEthernet1/0/2] quit
3) Configure Switch A
# Enable IGMP Snooping globally.
<SwitchA> system-view
[SwitchA] igmp-snooping
[SwitchA-igmp-snooping] quit
# Create VLAN 100, assign ports GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP Snooping and IGMP Snooping Proxying in the VLAN.
[SwitchA] vlan 100
[SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4
[SwitchA-vlan100] igmp-snooping enable
[SwitchA-vlan100] igmp-snooping proxying enable
[SwitchA-vlan100] quit
4) Verify the configuration
After the configuration is completed, Host A and Host B send IGMP join messages for group 224.1.1.1. Receiving the messages, Switch A sends a join message for the group out port GigabitEthernet 1/0/1 (a router port) to Router A.
Use the display igmp-snooping group command and the display igmp group command to display information about IGMP Snooping multicast groups and IGMP multicast groups. For example:
# Display information about IGMP Snooping multicast groups on Switch A.
[SwitchA] display igmp-snooping group
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Port flags: D-Dynamic port, S-Static port, C-Copy port
Subvlan flags: R-Real VLAN, C-Copy VLAN
Vlan(id):100.
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Router port(s):total 1 port.
GE1/0/1 (D) ( 00:01:23 )
IP group(s):the following ip group(s) match to one mac group.
IP group address:224.1.1.1
(0.0.0.0, 224.1.1.1):
Host port(s):total 2 port.
GE1/0/3 (D)
GE1/0/4 (D)
MAC group(s):
MAC group address:0100-5e01-0101
Host port(s):total 2 port.
GE1/0/3
GE1/0/4
# Display information about IGMP multicast groups on Router A.
[RouterA] display igmp group
Total 1 IGMP Group(s).
Interface group report information of VPN-Instance: public net
GigabitEthernet1/0/1(10.1.1.1):
Total 1 IGMP Group reported
Group Address Last Reporter Uptime Expires
224.1.1.1 0.0.0.0 00:00:06 00:02:04
When Host A leaves the multicast group, it sends an IGMP leave message to Switch A. Receiving the message, Switch A removes port GigabitEthernet 1/0/3 from the member port list of the forwarding entry for the group; however, it does not remove the group or forward the leave message to Router A because Host B is still in the group. Use the display igmp-snooping group command to display information about IGMP Snooping multicast groups. For example:
# Display information about IGMP Snooping multicast groups on Switch A.
[SwitchA] display igmp-snooping group
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Port flags: D-Dynamic port, S-Static port, C-Copy port
Subvlan flags: R-Real VLAN, C-Copy VLAN
Vlan(id):100.
Total 1 IP Group(s).
Total 1 IP Source(s).
Total 1 MAC Group(s).
Router port(s):total 1 port.
GE1/0/1 (D) ( 00:01:23 )
IP group(s):the following ip group(s) match to one mac group.
IP group address:224.1.1.1
(0.0.0.0, 224.1.1.1):
Host port(s):total 1 port.
GE1/0/4 (D)
MAC group(s):
MAC group address:0100-5e01-0101
Host port(s):total 1 port.
GE1/0/4
A switch fails to implement Layer 2 multicast forwarding.
IGMP Snooping is not enabled.
1) Enter the display current-configuration command to view the running status of IGMP Snooping.
2) If IGMP Snooping is not enabled, use the igmp-snooping command to enable IGMP Snooping globally, and then use igmp-snooping enable command to enable IGMP Snooping in VLAN view.
3) If IGMP Snooping is disabled only for the corresponding VLAN, just use the igmp-snooping enable command in VLAN view to enable IGMP Snooping in the corresponding VLAN.
Although a multicast group policy has been configured to allow hosts to join specific multicast groups, the hosts can still receive multicast data addressed to other multicast groups.
l The ACL rule is incorrectly configured.
l The multicast group policy is not correctly applied.
l The function of dropping unknown multicast data is not enabled, so unknown multicast data is flooded.
1) Use the display acl command to check the configured ACL rule. Make sure that the ACL rule conforms to the multicast group policy to be implemented.
2) Use the display this command in IGMP Snooping view or in the corresponding interface view to check whether the correct multicast group policy has been applied. If not, use the group-policy or igmp-snooping group-policy command to apply the correct multicast group policy.
3) Use the display current-configuration command to check whether the function of dropping unknown multicast data is enabled. If not, use the igmp-snooping drop-unknown command to enable the function of dropping unknown multicast data.
