Professional Documents
Culture Documents
V100R006C00
Issue 01
Date 2011-07-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Intended Audience
This document describes the multicast service supported by the S2700, including basic
knowledge, protocol implementation, configuration procedures, and configuration examples.
This document guides you through the configuration of the multicast service of the S2700.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
&<1-n> The parameter before the & sign can be repeated 1 to n times.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Contents
This chapter describes the procedure for configuring IGMP snooping and maintenance
commands, and provides configuration examples.
The IGMP snooping protocol forwards multicast information only to the specified receivers
through Layer 2 multicast. It has the following advantages:
l Reducing broadcast packets on Layer 2 networks, saving network bandwidth
l Enhancing the security of multicast information
l Performing accounting for each host independently
IGMP Snooping
The S2700 supports VLAN-based IGMP snooping.
IGMP snooping implements Layer 2 multicast and controls multicast data forwarding by
listening to multicast protocol packets sent between an upstream router and a downstream host
and maintaining downstream interface information.
You can configure user hosts to join a multicast group statically so that user hosts can steadily
receive multicast data packets.
You can also enable the S2700 to actively send IGMP Query messages so that the S2700 can
rapidly sense a Layer 2 network topology change and forward multicast data based on the new
topology, preventing multicast services from being interrupted.
Prompt Leave
When an interface of the S2700 receives an IGMP Leave message to leave a specified multicast
group, the S2700 deletes the interface from the downstream interface list of this multicast group
immediately. This is called prompt leave of a multicast group member. This feature is used in
the multicast IPTV scenario where one interface of the S2700 is commonly connected to only
one user host. Therefore, the prompt leave function shortens the speed at which the user switches
channels.
Applicable Environment
VLAN-based IGMP snooping runs on the S2700 between an upstream router and hosts. The
S2700 monitors the multicast protocol packets exchanged between the router and hosts to
maintain the forwarding entries for the multicast packets. In this manner, the S2700 manages
and controls forwarding of multicast data packets to implement Layer 2 multicast.
Pre-configuration Tasks
Before configuring IGMP snooping in a VLAN, complete the following tasks:
l Connecting interfaces and configuring the physical parameters of each interface to make
the physical layer in Up state
l Creating a VLAN
l Adding interfaces to the VLAN
Data Preparation
To configure IGMP snooping in a VLAN, you need the following data.
No. Data
1 ID of the VLAN
Context
By default, IGMP snooping is disabled on the S2700. You need to enable IGMP snooping on
the S2700 globally.
Procedure
Step 1 Run:
system-view
Step 2 Run:
igmp-snooping enable
Step 3 Run:
vlan vlan-id
Step 4 Run:
igmp-snooping enable
NOTE
To enable the IGMP Snooping function of multi-VLANs, run the igmp-snooping enable [ vlan vlan-id1
[ to vlan-id2 ] & <1-10> ] command in the system-view.
If IGMP snooping is enabled in a VLAN, global VLAN mapping cannot be configured.
----End
Context
According to the version of IGMP applied on a network, you can set the version of IGMP
messages that the S2700 with the IGMP snooping function can process.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping version { 1 | 2 |3 }
The version of IGMP messages that the S2700 can process is set.
By default, the S2700 can process messages of IGMPv1 and IGMPv2 but cannot process
messages of IGMPv3.
NOTE
When the forwarding in a VLAN is based on the MAC address, the IGMP message version cannot be set
to IGMPv3.
----End
Context
On a network whose topology seldom changes, if a host needs to receive certain multicast packets
for a long time, you can configure the interface on the S2700 as a static router interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number
Step 3 Run:
igmp-snooping static-router-port vlan { vlan-id [ to vlan-id ] } &<1-10>
----End
Context
To control the multicast packets received by hosts, you can disable dynamic learning on
interfaces. After the dynamic learning function is disabled on interfaces, you can only configure
the static router interface and forwarding entries manually.
l After dynamic learning of router interfaces is disabled in a VLAN, interfaces in the VLAN
do not listen on IGMP Query messages. In this case, you need to configure a static router
interface manually.
l After dynamic learning is disabled on multicast member interfaces, you can only add
interfaces to a multicast group manually.
Procedure
l Disabling dynamic learning of router interfaces in a VLAN
1. Run:
system-view
----End
Context
To limit the number of multicast programs available to users and multicast data traffic on an
interface, set the maximum number of multicast groups that users can join.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number
Step 3 Run:
igmp-snooping group-limit group-limit vlan {vlan-id [ to vlan-id ] } &<1-10>
The maximum number of multicast groups that hosts attached to the interface can join.
If vlan-id is specified, the maximum number of multicast groups that hosts attached to the
interface in a specified VLAN can join is set.
----End
Context
If IGMP messages sent from the upstream router cannot reach the S2700 for certain reasons, for
example, IGMP is not enabled or if the multicast forwarding entries on the upstream router are
statically configured and do not need to be dynamically learned, you can configure the IGMP
snooping querier on the S2700. The IGMP snooping querier then sends IGMP Query messages.
You can adjust parameters of the IGMP snooping querier as required.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping querier enable
The interval at which the querier sends IGMP General Query messages is set.
By default, the interval for sending IGMP General Query messages is 60 seconds.
The interval at which the querier sends Last Member Query messages is set.
By default, the interval for sending Last Member Query messages is 1 second.
----End
Context
A multicast group policy in a VLAN is used to add the hosts in the VLAN to the specified
multicast groups and limit the number of multicast groups that a host can join.
NOTE
When you create an ACL for a multicast group policy of a VLAN, the configuration takes effect only if
you select deny in the rule command. That is, a multicast group policy can only prohibit hosts in a VLAN
from accessing all or specified multicast groups.
Procedure
Step 1 Run:
system-view
A multicast group policy is configured for the VLAN. Interfaces in the VLAN can dynamically
join only the multicast group that matches the specified ACL rules.
By default, no multicast group policy is available in a VLAN. That is, hosts in a VLAN can join
any multicast group. If the IGMP version is not specified for a multicast policy, the S2700 applies
the policy to all IGMP messages regardless of their versions.
NOTE
If an advanced ACL is referenced by the group-policy, the ACL applies to the multicast group regardless
of the protocol type specified in the ACL.
----End
Prerequisite
A basic ACL is configured to specify the IP multicast groups that hosts can leave.
For the configuration of the ACL, see ACL Configuration in the Quidway S2700 Series Ethernet
Switches Configuration Guide - Security.
Context
When an interface on the S2700 receives an IGMP Leave message from a host, the S2700 deletes
the forwarding entry that corresponds to the interface from the multicast forwarding table
immediately without waiting for the aging of the forwarding entry. This is called prompt leave.
When each interface in a VLAN is connected to only one host, you can enable prompt leave for
interfaces in the VLAN.
NOTE
Prompt leave takes effect for interfaces in a VLAN only when the S2700 can process IGMPv2 or IGMPv3
messages.
Procedure
Step 1 Run:
system-view
NOTE
On the S2700, the permit rule is applicable to all multicast groups by default. To configure prompt leave
for a specified multicast group, you need to use the rule deny source any command.
----End
Context
This task is performed to enable the S2700 to detect changes of a Layer 2 network topology and
forward multicast packets correctly based on the new topology.
Do as follows on the S2700 that receives multicast packets from a router and forwards the
multicast packets to hosts.
Procedure
Step 1 Run:
system-view
The S2700 enabled with IGMP snooping is configured to respond to changes of a Layer 2
network topology.
NOTE
The function of responding to changes of Layer 2 network topology is usually used on a ring network.
When the topology of the ring network changes, theS2700 sends an IGMP Query message with the source
IP address being 192.168.0.1. The source IP address can be changed by the igmp-snooping send-query
source-address source-address command.
----End
Context
You can modify parameters of IGMP snooping to optimize the multicast performance on the
S2700 according to the actual situation of the network. The following parameters can be
modified:
l Suppression duration of IGMP messages
Within the suppression duration, the S2700 sends only one copy of the same IGMP
messages continuously sent by hosts to the upstream router. This reduces the number of
redundant messages.
l Aging time of a router interface
When a short-run congestion occurs on the network, the transmission of Query messages
from the IGMP querier to the S2700 takes a longer time. If the router interface ages in this
period, the S2700 does not send Report or Leave messages to the router interface. In this
case, forwarding of multicast data may be interrupted. As a result, you should set a longer
aging time for router interfaces on an unstable network.
l Maximum response time for IGMP Query messages
When hosts are required to respond to IGMP Query messages quickly, you can set a shorter
maximum response time. To avoid congestion caused by a large number of Response
messages sent by hosts, you can set a longer maximum response time.
l Router Alert option
The S2700 determines whether to process IGMP messages by checking the Router Alert
option in the messages. You can determine whether IGMP messages contains the Router
Alert option.
l Source IP address of IGMP Query messages sent by the S2700
Procedure
Step 1 Run:
system-view
Step 3 Run:
igmp-snooping suppress-time suppress-time
NOTE
For IGMP Report and Leave messages, it is recommended that you set the suppression duration the same
as the maximum response time for these messages in a VLAN.
Step 4 Run:
igmp-snooping router-aging-time router-aging-time
By default, the S2700 sets the aging time of the router interface as follows:
l If the router interface receives an IGMP Query message, the S2700 sets the aging time of
the interface to 180 seconds.
l If the router interface receives a PIM Hello message and the holdtime value of the Hello
message is larger than the remaining aging time of the interface, the S2700 sets the aging
time of the interface to the holdtime value contained in the PIM Hello message. If the holdtime
value is smaller than the remaining aging time of the router interface, the S2700 does not
change the aging time of the interface.
Step 5 Run:
igmp-snooping max-response-time max-response-time
NOTE
The maximum response time must be shorter than the interval for sending IGMP General Query messages.
Step 6 Run:
igmp-snooping require-router-alert
The S2700 is configured to process only the IGMP messages that contain the Router Alert option
in the IP header.
By default, the S2700 can process the IGMP messages that do not contain the Router Alert option
in the IP header from a VLAN.
Step 7 Run:
igmp-snooping send-router-alert
The S2700 is configured to send the IGMP messages that contain the Router Alert option in the
IP header.
By default, the S2700 sends the IGMP messages that contain the Router Alert option in the IP
header.
Step 8 Run:
quit
Step 9 Run:
igmp-snooping send-query source-address ip-address
----End
Context
After the IGMP proxy is configured on the S2700, the S2700 replaces the upstream router to
send IGMP Query messages to the downstream devices, and receives the IGMP Report and
IGMP Leave messages from the downstream devices. In this way, bandwidth consumption
between the upstream router and the S2700 is reduced and the workload on the upstream router
is also reduced.
Procedure
Step 1 Run:
system-view
NOTE
After IGMP snooping proxy is enabled, the switch broadcasts IGMP Query messages to all interfaces in a
VLAN periodically, including the routing interfaces in the VLAN. This may result in the reelection of
IGMP querier. If the multicast network already has a querier, you are advised to use the igmp-snooping
proxy-uplink-port command to configure an interface as an IGMP snooping proxy uplink interface. No
IGMP Query message can be sent to this interface.
IGMP snooping proxy and IGMP snooping querier cannot be configured in the same VLAN.
----End
Prerequisite
The configuration of IGMP snooping in a VLAN is complete.
Procedure
l Run the display igmp-snooping configuration command to check the configuration of
IGMP snooping.
l Run the display igmp-snooping [ vlan vlan-id ] command to check the configuration of
IGMP snooping in a VLAN.
l Run the display igmp-snooping statistics vlan [ vlan-id ] command to check the statistics
of IGMP snooping on a VLAN.
l Run the display igmp-snooping port-info [ vlan vlan-id [ group-address group-
address ] ] [ verbose ] command to check the information about member interfaces of a
multicast group.
l Run the display igmp-snooping router-port vlan vlan-id command to check the
information about router interfaces.
l Run the display igmp-snooping querier vlan [ vlan-id ] command to check the enabling
information about the IGMP snooping querier.
l Run the display l2-multicast forwarding-table vlan vlan-id [ source-address source-
address group-address | group-address ] command to check the multicast forwarding
table of a VLAN.
----End
Example
NOTE
If IGMP snooping is disabled in a VLAN, you can still configure IGMP snooping functions, but the
configuration does not take effect. In this case, no information is displayed after you run the display igmp-
snooping command.
If the configurations succeed, you can obtain the following information after running the display
igmp-snooping [ vlan vlan-id ] command:
l IGMP snooping is enabled in the VLAN.
l The IGMP version is set correctly.
l A multicast group policy is correctly set for the VLAN.
l Prompt leave is enabled for interfaces in the VLAN.
l Aging time of the router interface, interval for sending Last Member Query messages,
interval for sending IGMP General Query messages, maximum response time, suppression
duration of IGMP messages, and IGMP robustness variable are correctly set.
l The Router Alert option is set correctly.
The following is an example.
<Quidway> display igmp-snooping vlan 3
IGMP Snooping Information for VLAN 3
IGMP Snooping is Enabled
IGMP Version is Set to default 2
IGMP Query Interval is Set to default 125
IGMP Max Response Interval is Set to default 10
IGMP Robustness is Set to default 2
IGMP Last Member Query Interval is Set to default 1
IGMP Router Port Aging Interval is Set to 180s or holdtime in hello
IGMP Filter Group-Policy is Set to default : Permit All
IGMP Prompt Leave Disable
IGMP Router Alert is Not Required
IGMP Send Router Alert Enable
IGMP Proxy Enable
IGMP Report Suppress Disable
When the dynamic interface learning is disabled, if you run the display igmp-snooping port-
info [ vlan vlan-id ] [ group-address group-address ] [ verbose ] command, only the static
entries are displayed.
<Quidway> display igmp-snooping port-info
-----------------------------------------------------------------------
(Source, Group) Port Flag
Flag: S:Static D:Dynamic M: Ssm-mapping
-----------------------------------------------------------------------
VLAN 101, 1 Entry(s)
(*, 225.0.0.1) GE0/0/1 -D-
1 port(s)
VLAN 102, 1 Entry(s)
(*, 225.0.0.1) GE0/0/24 -D-
1 port(s)
-----------------------------------------------------------------------
<Quidway> display igmp-snooping router-port vlan 3
Port Name UpTime Expires Flags
--------------------------------------------------------------
VLAN 3, 2 router-port(s)
GE0/0/1 1d:22h 00:01:20 DYNAMIC
GE0/0/2 2d:10h -- STATIC
Run the display igmp-snooping querier vlan [ vlan-id ] command. If the querier is displayed
as Enabled, it indicates that the querier is successfully enabled.
<Quidway> display igmp-snooping querier vlan
VLAN Querier-state
-----------------------------------------------
3 Enable
total entry 1
<Quidway> display l2-multicast forwarding-table vlan 7
VLAN ID : 7, Forwarding Mode : IP
-----------------------------------------------------------------------
(Source, Group) Interface Out-Vlan
-----------------------------------------------------------------------
(1.1.1.1, 232.1.1.1) GigabitEthernet0/0/1 7
-----------------------------------------------------------------------
Total Group(s) : 1
Applicable Environment
In a metro Ethernet, if a host connected to an interface of the S2700 needs to receive the multicast
flow of a certain multicast group for a long time, you can add the interface to the multicast group.
After static Layer 2 multicast is configured, hosts can receive the multicast flows of the registered
multicast group in a steady and timely manner for a long time. However, in this mode, all the
forwarding entries need to be manually configured. This makes the maintenance difficult, so
this mode is not applicable to a complicated network.
Pre-configuration Tasks
Before configuring static Layer 2 multicast in a VLAN, complete the following tasks:
l Connecting interfaces and configuring the physical parameters of each interface to make
the physical layer in Up state
l Enabling IGMP snooping globally
Data Preparation
To configure static Layer 2 multicast, you need the following data.
No. Data
Procedure
Step 1 Run:
system-view
----End
Procedure
Step 1 Run:
system-view
Step 3 Run:
port hybrid tagged vlan { { vlan-id1 [ to vlan-id2 ] }&<1-10> | all }
NOTE
If multicast VLAN replication is not configured, the interface of the S2700 that connects to a router and
receives the multicast packets from the router and the interface that connects to users and sends multicast
packets to users must be added to the same VLAN.
----End
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number
Step 3 Run:
l2-multicast static-group [ source-address source-ip-address ] group-address group-
ip-address vlan { vlan-id1 [ to vlan-id2 ] } &<1-10>
The interface is added to the multicast group statically. You can also run the l2-multicast static-
group [ source-address source-ip-address ] group-address group-ip-address1 to group-ip-
address2 vlan vlan-id command to join the interface to the group-address in batches.
After an interface is added to a multicast group statically, multicast protocol packets are not
forwarded to the router interface.
----End
Prerequisite
The configuration of static Layer 2 multicast for a VLAN is complete.
Procedure
l Run the display l2-multicast forwarding-table vlan vlan-id [ source-address source-
address group-address group-address ] command to check the multicast forwarding table
of a VLAN.
----End
Example
<Quidway> display l2-multicast forwarding-table vlan 10
VLAN ID : 10, Forwarding Mode : IP
--------------------------------------------------------------------
(Source, Group) Interface Out-Vlan
--------------------------------------------------------------------
Router-port GigabitEthernet0/0/1 10
(*, 225.1.1.1) GigabitEthernet0/0/1 10
GigabitEthernet0/0/2 10
(*, 225.1.1.2) GigabitEthernet0/0/1 10
GigabitEthernet0/0/2 10
(*, 225.1.1.3) GigabitEthernet0/0/1 10
GigabitEthernet0/0/2 10
--------------------------------------------------------------------
Total Group(s) : 3
Applicable Environment
If the switch connected to user hosts is configured with IGMPv3, SSM mapping needs to be
configured on the switch to map the multicast group addresses not in the SSM group to the
specified source addresses.
When the switch running IGMPv3 receives an IGMPv2 packet whose address is in the SSM
group, the SSM mapping function can automatically map the address of the packet to the
specified source.
Pre-configuration Tasks
Before configuring SSM mapping, complete the following task:
l Enabling global IGMP snooping
Data Preparation
To configure SSM mapping, you need the following data.
No. Data
No. Data
Context
If a user joins an ASM multicast group, you need to configure an SSM group policy in the VLAN
to add the multicast group address to the range of SSM group addresses.
NOTE
When you create an ACL for an SSM policy, the configuration takes effect only if you select permit and
specify a multicast address in the rule command. The configuration does not take effect if deny is selected
or if the specified address is not a multicast address.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping ssm-policy basic-acl-number
By default, the address of an SSM group ranges from 232.0.0.0 to 232.255.255.255. After you
configure an SSM policy, the multicast groups specified in the SSM policy are considered as
SSM groups.
----End
Context
By configuring SSM mapping, you can set up one-to-one mappings between multicast groups
and multicast sources.
SSM mapping can be configured only when IGMP snooping is enabled globally and in the
corresponding VLAN and when the IGMP messages version is set to IGMPv3 in the VLAN.
If the multicast replication function is configured, you only need to configure SSM mapping in
the multicast VLAN.
Procedure
Step 1 Run:
system-view
The mapping between a multicast group address and a multicast source is configured.
The specified multicast group address must be in the range of multicast group addresses specified
by the SSM policy. For the configuration of the SSM policy, see 1.5.2 (Optional) Configuring
an SSM Group Policy.
----End
Procedure
l Run the display igmp-snooping port-info command to view the IGMP snooping entries
on an interface.
----End
Example
Run the display igmp-snooping port-info command, and you can view the IGMP snooping
entries on the interface. For example:
<Quidway> display igmp-snooping port-info vlan 10
-----------------------------------------------------------------------
(Source, Group) Port Flag
Context
CAUTION
Static entries in a forwarding table cannot be restored after you clear them and you have to
configure them again. Confirm the operation before you run the following command.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number
Step 3 Run:
undo l2-multicast static-group [ source-address source-ip-address ] group-address
group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } & <1-10> }
Or run:
undo l2-multicast static-group [ source-address source-ip-address ] group-address
group-ip-address1 to group-ip-address2 vlan vlan-id
----End
Context
CAUTION
Running this command disables hosts in a VLAN from receiving certain multicast flows. The
hosts in the VLAN receive the multicast flows again only after the S2700 receives IGMP Report
messages from the hosts again and the forwarding entries are regenerated on the S2700.
Procedure
l Run the reset igmp-snooping group { all | vlan { vlan-id | all } } command in the user
view to clear the dynamic forwarding entries in the multicast forwarding table.
NOTE
This command cannot clear static forwarding entries and dynamic router port entries.
----End
Context
CAUTION
The statistics on IGMP snooping cannot be restored after you clear them. So, confirm the action
before you use the command.
Procedure
l Run the reset igmp-snooping statistics { all | vlan { vlan-id | all } } command in the user
view to clear the statistics on IGMP snooping.
----End
Context
CAUTION
Debugging affects the performance of the system. So, after debugging, run the undo debugging
igmp-snooping all command to disable it immediately.
Procedure
l Run the debugging igmp-snooping { all | aps | event | fwd | general | leave [ basic-acl-
number ] | mvlan | packet [ advance-acl-number ] | query [ advance-acl-number ] |
report [ advance-acl-number ] | syn | timer } command in the user view to enable
debugging of IGMP snooping.
----End
Networking Requirements
As shown in Figure 1-1, Eth 0/0/1 of the S2700 is connected to a router on the multicast source
side, and Eth 0/0/2 is connected to hosts. You are required to configure IGMP snooping to ensure
that three hosts in VLAN 3 can receive multicast data from multicast groups in the range of
225.1.1.1 to 225.1.1.3 permanently.
IP/MPLS core
Eth0/0/1
Switch
Eth0/0/2
VLAN3
Configuration Roadmap
The configuration roadmap is as follows:
Data Preparation
To complete the configuration, you need the following data:
l ID of the VLAN that Eth 0/0/2 and Eth 0/0/1 belong to: VLAN 3
l Static router interface: Eth0/0/1
l Addresses of static multicast groups: 225.1.1.1, 225.1.1.2, 225.1.1.3
Procedure
Step 1 Create a VLAN and add interfaces to the VLAN.
<Switch> system-view
[Switch] vlan 3
[Switch-vlan3] quit
[Switch] interface ethernet 0/0/1
[Switch-Ethernet0/0/1] port hybrid tagged vlan 3
[Switch-Ethernet0/0/1] quit
[Switch] interface ethernet 0/0/2
[Switch-Ethernet0/0/2] port hybrid tagged vlan 3
[Switch-Ethernet0/0/2] quit
According to the preceding information, the IGMP snooping of the VLAN is enabled.
# Check the configuration of the static router interface.
According to the preceding information, Eth 0/0/1 is configured as a static router interface.
# Verify the information about member interfaces of a static multicast group.
[Switch] display igmp-snooping port-info
-----------------------------------------------------------------------
(Source, Group) Port Flag
Flag: S:Static D:Dynamic M: Ssm-mapping
-----------------------------------------------------------------------
VLAN 3, 3 Entry(s)
(*, 225.1.1.1) Eth0/0/2 S--
1 port(s)
(*, 225.1.1.2) Eth0/0/2 S--
1 port(s)
(*, 225.1.1.3) Eth0/0/2 S--
1 port(s)
-----------------------------------------------------------------------
According to the preceding information, multicast groups 225.1.1.1 to 225.1.1.3 are configured
with static forwarding entries.
# View the multicast forwarding table.
[Switch] display l2-multicast forwarding-table vlan 3
The preceding information shows the VLAN ID and outgoing interface mapping the data from
multicast groups 225.1.1.1 to 225.1.1.3.
----End
Configuration Files
l Configuration file of the S2700
#
sysname Switch
#
vlan batch 3
#
igmp-snooping enable
#
vlan 3
igmp-snooping enable
#
interface Ethernet0/0/1
port hybrid tagged vlan 3
Networking Requirements
On the network shown in Figure 1-2, IGMPv2 is run on Switch and Host 1 and Host 2, and
IGMPv3 is run on the last-hop router Router A on the multicast source side. Switch A is the
S2700 device. Eth 0/0/1 on Switch A is connected to Router A and Eth 0/0/2 on Switch A is
connected to a switch directly connected with users. Eth 0/0/1 on Switch A is a static router
interface and Eth 0/0/2 is statically added to multicast group 224.1.1.1. Eth 0/0/1 and Eth 0/0/2
both join VLAN 10 and IGMP SSM mapping is deployed on Router A.
It is required that IGMP snooping SSM mapping be configured on Switch A in the VLAN to
work jointly with IGMP SSM mapping. IGMP snooping SSM mapping also generates a mapping
between a multicast group and a multicast source. (*, G) information in IGMPv1 or IGMPv2
multicast data packets is then mapped to (S, G) information, providing SSM services for the
hosts running IGMPv1 or IGMPv2.
Figure 1-2 Networking diagram for configuring IGMP snooping SSM mapping
Source 2
10.1.1.2
Internet/
Source 1 Intranet
10.1.1.1
RouterA
Eth0/0/1 Swtich
Eth0/0/2
SwitchA
SSM Mapping
VLAN10
Host1 Host2
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure basic IGMP snooping functions so that users can receive multicast data from
multicast sources.
2. Configure an SSM group policy for IGMP snooping to add the ASM group addresses of
users to the SSM group address range.
3. Configure IGMP snooping SSM mapping so that users can receive multicast data from a
specified multicast source.
Data Preparation
To complete the configuration, you need the following data:
l VLAN 10 to which Eth 0/0/1 and Eth 0/0/2 on Switch A are added
l IGMPv3 run on Switch A and IGMPv2 run on Switch, Host 1, and Host 2
l Multicast source address 10.1.1.2
Procedure
Step 1 Configure a VLAN.
# Configure Switch A.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] vlan 10
[SwitchA-vlan10] quit
[SwitchA] interface ethernet 0/0/1
[SwitchA-Ethernet0/0/1] port hybrid pvid vlan 10
[SwitchA-Ethernet0/0/1] port hybrid untagged vlan 10
[SwitchA-Ethernet0/0/1] quit
[SwitchA] interface ethernet 0/0/2
[SwitchA-Ethernet0/0/2] port hybrid pvid vlan 10
[SwitchA-Ethernet0/0/2] port hybrid untagged vlan 10
[SwitchA-Ethernet0/0/2] quit
Step 2 Enable global IGMP snooping and IGMP snooping in the VLAN.
# Configure Switch A.
[SwitchA] igmp-snooping enable
[SwitchA] vlan 10
[SwitchA-vlan10] igmp-snooping enable
Step 3 Configure IGMPv3 on Switch A and configure IGMPv2 on hosts. The hosts are not allowed to
upgrade the IGMP version to 3.
# Configure SwitchA.
[SwitchA-vlan10] igmp-snooping version 3
[SwitchA-vlan10] quit
Step 5 Configure an SSM group policy for IGMP snooping and enable IGMP snooping SSM mapping.
[SwitchA] acl number 2008
[SwitchA-acl-basic-2008] rule 5 permit source 224.1.1.1 0
[SwitchA-acl-basic-2008] quit
[SwitchA] vlan 10
[SwitchA-vlan10] igmp-snooping ssm-policy 2008
# After SwitchA receives a Report message, run the display igmp-snooping port-info command
to view the configurations on the interface.
[SwitchA] display igmp-snooping port-info
-----------------------------------------------------------------------
(Source, Group) Port Flag
Flag: S:Static D:Dynamic M: Ssm-mapping
-----------------------------------------------------------------------
VLAN 10, 1 Entry(s)
(10.1.1.2, 224.1.1.1) Eth0/0/2 --M
1 port(s)
-----------------------------------------------------------------------
----End
Configuration Files
l Configuration file of Switch A
#
sysname SwitchA
#
vlan batch 10
#
igmp-snooping enable
#
acl number 2008
rule 5 permit source 224.1.1.1 0
#
vlan 10
igmp-snooping enable
igmp-snooping ssm-mapping enable
igmp-snooping version 3
igmp-snooping ssm-policy 2008
igmp-snooping ssm-mapping 224.1.1.0 255.255.255.0 10.1.1.2
#
interface Ethernet0/0/1
port hybrid pvid vlan 10
port hybrid untagged vlan 10
igmp-snooping static-router-port vlan 10
#
interface Ethernet0/0/2
port hybrid pvid vlan 10
port hybrid untagged vlan 10
#
return
This chapter describes the procedure for configuring multicast VLAN replication and
maintenance commands, and provides configuration examples.
NOTE
In traditional multicast transmission mode, the upstream router must copy multicast data for
each user VLAN and send all copies to the switch when users in different VLANs request the
program provided by the same multicast source. This mode wastes network bandwidth and adds
workload on the router.
When users in multiple VLANs require the program of the same multicast source, you can
configure the VLANs as the user VLANs of a multicast VLAN on the switch. The upstream
router only needs to send multicast data to the multicast VLAN and does not need to send a copy
to each user VLAN. When the switch receives multicast data packets from the upstream router,
it distributes multicast data packets to the user VLANs that have multicast receivers.
Multicast Packet
VLAN 2 Receiver
VLAN 3 HostA
VLAN 4 VLAN 2
Receiver
HostB
Source Router Switch
VLAN 3
Receiver
HostC
VLAN 4
Figure 2-2 shows multicast data transmission after multicast VLAN replication is configured.
The router only needs to copy multicast data for the multicast VLAN and sends the data to the
switch. This saves network bandwidth and reduces workload of the router.
Multicast Packet
Multicast VLAN Receiver
VLAN 2 HostA
VLAN 3 VLAN 2
VLAN 4
Receiver
HostB
Source Router Switch
VLAN 3
Receiver
HostC
VLAN 4
The S2700 supports the following mapping modes between multicast VLANs and user VLANs:
l One-to-many mapping between a multicast VLAN and user VLANs
Applicable Environment
In traditional multicast transmission mode, a router must copy multicast data for each user VLAN
and send all copies to the downstream device when users in different VLANs request the program
provided by the same multicast source. This mode wastes network bandwidth and adds workload
on the router.
Multicast VLAN replication helps to manage and control the multicast source and the multicast
group members. This function enables users in different VLANs to receive the same multicast
flow and saves bandwidth.
In multicast VLAN replication implementation, VLANs are classified into multicast VLANs
and multiple user VLANs. The S2700 interface connected to a multicast source belongs to a
multicast VLAN, and interfaces connected to members of a multicast group belong to user
VLANs. The multicast VLAN aggregates multicast flows, and user VLANs receive data from
the multicast VLAN.
Pre-configuration Tasks
Before configuring multicast VLAN replication based on user VLANs, complete the following
tasks:
l Connecting interfaces and setting physical parameters for the interfaces to ensure that the
physical status of the interfaces is Up
l Enabling IGMP snooping globally
Data Preparation
To configure multicast VLAN replication based on user VLANs, you need the following data.
No. Data
1 Multicast VLAN ID
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
igmp-snooping enable
Step 4 Run:
multicast-vlan enable
Multicast VLAN replication is enabled, and the VLAN is configured as a multicast VLAN.
Step 5 Run:
multicast-vlan user-vlan { { vlan-id1 [ to vlan-id2 ] } & <1-10> }
The vlan-id1 and vlan-id2 parameters specify user VLAN IDs. The value of vlan-id2 must be
greater than the value of vlan-id1.
NOTE
The user VLANs specified in the command must be existing VLANs enabled with IGMP snooping and
cannot be multicast VLANs or user VLANs of another multicast VLAN.
----End
Procedure
Step 1 Run:
system-view
NOTE
On the S2700EI, a user-side interface must be added to the multicast VLAN and user VLAN in the same
mode.
CAUTION
If the network-side interface is added to a user VLAN, a traffic policy needs to be configured
on the network-side interface to prevent the IGMP Query packets destined for the user
VLAN from being sent to the CPU because the IGMP Query packets will overload the
S2700 CPU. For example, if VLAN 1000 is the multicast VLAN and GE0/0/1 is the
network-side interface, run the following commands:
<Quidway> system-view
[Quidway] acl 3000
[Quidway-acl-adv-3000] rule 5 permit igmp
[Quidway-acl-adv-3000] quit
[Quidway] traffic classifier other_vlan operator and
[Quidway-classifier-other_vlan] if-match acl 3000
[Quidway-classifier-other_vlan] quit
[Quidway-classifier-mvlan] if-match vlan-id 1000
[Quidway-classifier-mvlan] if-match acl 3000
[Quidway-behavior-other_vlan] deny
[Quidway-behavior-other_vlan] quit
[Quidway] traffic behavior mvlan
[Quidway-behavior-mvlan] permit
[Quidway-behavior-mvlan] quit
[Quidway] traffic policy igmp
[Quidway-trafficpolicy-igmp] classifier mvlan behavior mvlan
[Quidway-trafficpolicy-igmp] classifier other_vlan behavior other_vlan
[Quidway] interface gigabitethernet0/0/1
[Quidway-GigabitEthernet0/0/1] traffic-policy igmp inbound
----End
Prerequisite
The configuration of multicast VLAN replication is complete.
Procedure
l Run the display multicast-vlan vlan [ vlan-id ] command to view information about a
multicast VLAN.
----End
Example
Run the display multicast-vlan vlan [ vlan-id ] command to view information about a multicast
VLAN.
<Quidway> display multicast-vlan vlan 3
Multicast-vlan : 3
User-vlan Number : 2
IGMP snooping state : Enable
MLD snooping state : Disable
User-vlan Snooping-state
-----------------------------------------------
100 IGMP Enable /MLD Disable
200 IGMP Enable /MLD Disable
Run the display user-vlan vlan [ vlan-id ] command to view information about user VLANs.
<Quidway> display user-vlan vlan
Total user vlan 2
user-vlan snooping-state multicast-vlan snooping-state
---------------------------------------------------------
100 IGMP Enable /MLD Disable 3 IGMP Enable /MLD Disable
200 IGMP Enable /MLD Disable 3 IGMP Enable /MLD Disable
Networking Requirements
As shown in Figure 2-3, RouterA is connected to the multicast source. GE 1/0/0 of RouterA is
connected to Eth0/0/1 of SwitchA. Eth0/0/1 of SwitchA belongs to VLAN 10. HostA, HostB,
and HostC are connected to Eth0/0/2, Eth0/0/3, and Eth0/0/4 of SwitchA and belong to VLAN
100, VLAN 200, and VLAN 300 respectively.
To save network bandwidth, you can configure multicast VLAN replication based on user
VLANs on SwitchA. RouterA then only needs to send one copy of multicast data to the multicast
VLAN, and SwitchA distributes multicast data to user VLANs.
Figure 2-3 Networking diagram for configuring multicast VLAN replication based on user
VLANs
VLAN10
Eth0/0/1 SwitchA
Eth0/0/2 Eth0/0/4
Eth0/0/3
VLAN100 VLAN200 VLAN300
Configuration Roadmap
The configuration roadmap is as follows:
1. Enable IGMP snooping globally.
2. Create a multicast VLAN and enable IGMP snooping in the multicast VLAN.
3. Create user VLANs and enable IGMP snooping in the user VLANs.
4. Bind the user VLANs to the multicast VLAN.
5. Add the network-side interface and user-side interfaces to VLANs as hybrid interfaces.
Data Preparation
To complete the configuration, you need the following data:
l Interface connected to RouterA and the VLAN that the interface belongs to
l User-side interfaces and the VLANs that the interfaces belong to
Procedure
Step 1 Enable IGMP snooping globally.
<SwitchA> system-view
[SwitchA] igmp-snooping enable
Step 2 Create a multicast VLAN and enable IGMP snooping in the multicast VLAN.
<SwitchA> system-view
[SwitchA] igmp-snooping enable
[SwitchA] vlan 10
[SwitchA-vlan10] igmp-snooping enable
[SwitchA-vlan10] multicast-vlan enable
[SwitchA-vlan10] quit
Step 3 Create user VLANs and enable IGMP snooping in the user VLANs.
[SwitchA] vlan 100
[SwitchA-vlan100] igmp-snooping enable
[SwitchA-vlan100] quit
[SwitchA] vlan 200
[SwitchA-vlan200] igmp-snooping enable
[SwitchA-vlan200] quit
[SwitchA] vlan 300
[SwitchA-vlan300] igmp-snooping enable
[SwitchA-vlan300] quit
Step 4 Bind user VLANs 100, 200, and 300 to multicast VLAN 10.
[SwitchA] vlan 10
[SwitchA-vlan10] multicast-vlan user-vlan 100 200 300
[SwitchA-vlan10] quit
# Add Eth0/0/2, Eth0/0/3, and Eth0/0/4 to user VLANs 100, 200, and 300 respectively.
[SwitchA] interface ethernet0/0/2
[SwitchA-Ethernet0/0/2] port hybrid pvid vlan 100
[SwitchA-Ethernet0/0/2] port hybrid untagged vlan 10 100
[SwitchA-Ethernet0/0/2] quit
[SwitchA] interface ethernet0/0/3
[SwitchA-Ethernet0/0/3] port hybrid pvid vlan 200
[SwitchA-Ethernet0/0/3] port hybrid untagged vlan 10 200
[SwitchA-Ethernet0/0/3] quit
[SwitchA] interface ethernet0/0/4
[SwitchA-Ethernet0/0/4] port hybrid pvid vlan 300
[SwitchA-Ethernet0/0/4] port hybrid untagged vlan 10 300
[SwitchA-Ethernet0/0/4] quit
----End
Configuration Files
l Configuration file of SwitchA
#
sysname SwitchA
#
vlan batch 10 100 200 300
#
igmp-snooping enable
#
vlan 10
igmp-snooping enable
multicast-vlan enable
multicast-vlan user-vlan 100 200 300
#
vlan 100
igmp-snooping enable
#
vlan 200
igmp-snooping enable
#
vlan 300
igmp-snooping enable
#
interface Ethernet0/0/1
port hybrid pvid vlan 10
port hybrid untagged vlan 10
#
interface Ethernet0/0/2
port hybrid pvid vlan 100
port hybrid untagged vlan 10 100
#
interface Ethernet0/0/3
port hybrid pvid vlan 200
port hybrid untagged vlan 10 200
#
interface Ethernet0/0/4
port hybrid pvid vlan 300
port hybrid untagged vlan 10 300
#
return
This chapter describes the principle of controllable multicast and procedures for configuring
controllable multicast.
Traditional multicast services are uncontrollable. Users running traditional multicast need to
send IGMP Report messages to join related multicast groups, and then receive multicast packets
of the groups. With the development of IPTV services, uncontrollable multicast services cannot
meet the operation requirements. IPTV services aim to make prohibits. Users can watch a
program (that is, join a multicast group) only after they pay fees. If users are not authenticated,
the requirements of IPTV operation cannot be met. Therefore, controllable multicast is
developed to control the authorities of users to join a certain multicast group. When a user
requests to join a multicast group, the Switch must authenticate the request, and reject illegal or
unauthorized requests.
Multicast Group
A multicast group corresponds to a multicast address such as 224.1.1.1. A multicast group can
be regarded as a channel or program of IPTV.
Multicast Profile
A multicast profile is a set of multicast group lists, and defines the frame of users' rights to join
related multicast groups. A multicast profile can contain several multicast group lists. For
example, in Figure 3-1, multicast profile P1 contains L1, L2, and L3. A multicast group list can
be contained in several multicast profiles. For example, L2 is contained in P1 and P2. Multicast
group lists that are added to a profile have their attributes, that is, watch. If a multicast group list
is added to a multicast profile in watch mode, users of the multicast profile can watch all multicast
groups in the list..
Control Flow
The S2700 on which controllable multicast is applied can control the generation of Layer 2
multicast forwarding entries by intercepting IGMP Report messages. After receiving an IGMP
Report message from a user, the S2700 obtains the profile based on the VLAN to which the
message belongs. If the group is not in the list of the profile, the user cannot join the group. The
S2700 intercepts the IGMP Report message and do not generate the related forwarding entry.
Therefore, the user cannot receive data flows of this group. If the multicast group is in the list
of the profile, check the mode through which the list is added to the profile. If the list is added
to the profile in watch mode, the S2700 allows the IGMP Report message to pass through.
Pre-configuration Tasks
Before configuring controllable multicast, complete the following task:
l Configuring Layer 2 multicast, that is, IGMP snooping, to forward multicast packets
normally
NOTE
In the multicast VLAN, controllable multicast needs to be configured in the user VLAN.
Data Preparation
To configure controllable multicast, you need the following data.
No. Data
Procedure
Step 1 Run:
system-view
Step 2 Run:
btv
Step 3 Run:
multicast-group group-name { ip-address multicast-group-address [ source ipv4-
source-address ] | ipv6-address mld-group-address [ source ipv6-source-address ] }
NOTE
If the interface connected to the user device is configured IGMPv2, you do not need to specify the
source ipv4-source-address parameter; if the interface is configured with IGMPv3, you must specify
source ipv4-source-address.
If the configured multicast groups have the same address, you can use the group-name parameter to change
the names of multicast groups.
----End
Procedure
Step 1 Run:
system-view
Step 2 Run:
btv
Step 3 Run:
multicast-list list-name
A multicast group list is created and the view of the multicast group list is displayed.
Step 4 Run:
add multicast-group { name group-name | index start-index to end-index }
----End
Procedure
Step 1 Run:
system-view
Step 2 Run:
btv
Step 3 Run:
multicast-profile profile-name
A multicast profile is created and the view of the multicast profile is displayed.
Step 4 Run:
add multicast-list { name list-name | index start-index to end-index } watch
Step 5 Run:
max-program-num max-value
The maximum number is configured for multicast groups that users in the multicast profile can
simultaneously join.
NOTE
On the S2700, users in a multicast profile can simultaneously join a maximum of eight multicast groups.
This is also the default setting.
----End
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
attach multicast-profile profile-name [ interface interface-type interface-number
| mac-address mac-address ] *
The binding relationship is set between the VLAN and the multicast profile.
By default, the binding relationship between the VLAN and the multicast profile is not set in
S2700.
NOTE
The S2700 supports the port+VLAN multicast control mode. To configure the multicast service for multiple
user interfaces in the same VLAN, you need to specify a multicast profile for each interface individually
by specifying the interface interface-type interface-number parameter.
----End
Procedure
Step 1 Run the display multicast-group [ group-name ] command to check information about a
multicast group.
Step 2 Run the display multicast-list [ list-name ] command to check information about a multicast
group list.
Step 3 Run the display multicast-profile [ profile-name [ verbose ] ] command to check information
about a multicast profile.
Step 4 Run the display multicast-profile-apply command to information about a VLAN where a
multicast profile is applied.
----End
Networking Requirements
As shown in Figure 3-2, multicast group G1 (225.0.0.1), G2 (225.0.0.2), G3 (225.0.0.3), and
G4 (225.0.0.4) exist in the network connected to the router. You are required to configure users
in VLAN 1 and VLAN 2 to watch G1 and G2,and users in VLAN 3 and VLAN 4 to watch all
multicast groups.
Network
G2(11.1.1.1,225.0.0.1) G4(13.1.1.1,225.0.0.1)
Switch
Configuration Roadmap
The configuration roadmap is as follows:
Data Preparation
To complete the configuration, you need the following data:
1. Name of each multicast group
2. Name of each multicast group list
Configuration Procedure
1. Configure user VLANs and add the interface to the user VLANs. The configuration details
are not provided here.
2. Configure IGMP snooping.
<Switch> system-view
[Switch] igmp-snooping enable
[Switch] vlan 1
[Switch-vlan1] igmp-snooping enable
[Switch-vlan1] quit
[Switch] vlan 2
[Switch-vlan2] igmp-snooping enable
[Switch-vlan2] quit
[Switch] vlan 3
[Switch-vlan3] igmp-snooping enable
[Switch-vlan3] quit
[Switch] vlan 4
[Switch-vlan4] igmp-snooping enable
[Switch-vlan4] quit
3. Configure controllable multicast.
# Configure multicast groups.
[Switch] btv
[Switch-btv] multicast-group G1 ip-address 225.0.0.1
[Switch-btv] multicast-group G2 ip-address 225.0.0.2
[Switch-btv] multicast-group G3 ip-address 225.0.0.3
[Switch-btv] multicast-group G4 ip-address 225.0.0.4
# Configure multicast group lists.
[Switch-btv] multicast-list L1
[Switch-btv-list-L1] add multicast-group name G1
[Switch-btv-list-L1] add multicast-group name G2
[Switch-btv-list-L1] quit
[Switch-btv] multicast-list L2
[Switch-btv-list-L2] add multicast-group name G3
[Switch-btv-list-L2] add multicast-group name G4
[Switch-btv-list-L2] quit
# Configure multicast profiles.
[Switch-btv] multicast-profile P1
[Switch-btv-profile-P1] add multicast-list name L1 watch
[Switch-btv-profile-P1] quit
[Switch-btv] multicast-profile P2
[Switch-btv-profile-P2] add multicast-list name L1 watch
[Switch-btv-profile-P2] add multicast-list name L2 watch
[Quidway-btv-profile-P2] quit
[Quidway-btv] quit
# Apply multicast profiles to VLANs.
[Switch] vlan 1
[Switch-vlan1] attach multicast-profile P1
[Switch-vlan1] quit
[Switch] vlan 2
[Switch-vlan2] attach multicast-profile P1
[Switch-vlan2] quit
[Switch] vlan 3
[Switch-vlan3] attach multicast-profile P2
[Switch-vlan3] quit
[Switch] vlan 4
[Switch-vlan4] attach multicast-profile P2
[Switch-vlan4] quit
# Verify the configuration.
[Switch-btv] display multicast-profile-apply
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Vlan1 -- -- 8 1 P1
Vlan2 -- -- 8 1 P1
Vlan3 -- -- 8 2 P2
Vlan4 -- -- 8 2 P2
Total: 4
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
1 P1 1 2
2 P2 2 2
Total: 2
[Switch-btv] display multicast-list
-------------------------------------------------------------------------
Index Multicast-list-name Multicast-
group
-------------------------------------------------------------------------
1 L1
2
2 L2
2
Total: 2
-------------------------------------------------------------------------
1 G1 225.0.0.1
2 G2 225.0.0.2
3 G3 225.0.0.3
4 G4 225.0.0.4
Total: 4
Configuration Files
sysname Switch
#
vlan batch 1 to 4
#
igmp-snooping enable
#
#
btv
multicast-group G1 ip-address 225.0.0.1
multicast-group G2 ip-address 225.0.0.2
multicast-group G3 ip-address 225.0.0.3
multicast-group G4 ip-address 225.0.0.4
#
multicast-list L1
add multicast-group name G1
This chapter describes the implementation and configuration procedures of Multicast Listener
Discovery (MLD) snooping on the S2700.
4.1 Overview of MLD Snooping
When MLD snooping is enabled, the S2700 creates a Layer 2 forwarding table for multicast
data packets by listening to MLD messages. In this manner, the S2700 manages and controls
the forwarding of multicast data packets to ensure that these packets are sent only to the hosts
that need the multicast data.
4.2 MLD Snooping Features Supported by the S2700
This section describes the MLD snooping features supported by the S2700.
4.3 Enabling MLD Snooping
This section describes how to enable MLD snooping, add an interface to a multicast group
statically, and configure an interface as a static router interface.
4.4 Configuring a Multicast Group Policy for a VLAN
This section describes how to configure a multicast group policy for a VLAN.
4.5 Configuring Prompt Leave of Interfaces
This section describes how to configure prompt leave of interfaces in a VLAN.
4.6 Configuring the MLD Snooping Querier
This section describes how to configure the MLD snooping querier.
4.7 (Optional) Modifying Parameters of MLD Snooping
This section describes how to optimize the performance of MLD snooping by modifying MLD
snooping parameters, including the aging time of the router interface, interval for sending Last
Member Query messages, interval for sending the General Query messages, maximum response
time for MLD messages, MLD robustness variable, source IP address of the MLD message sent
to respond to changes of Layer 2 network topology, MLD version, duration for suppressing the
same Report messages, maximum number of MLD snooping entries, and whether the Router
Alert option is contained in MLD messages.
4.8 Maintaining MLD Snooping
This section describes how to maintain MLD snooping.
4.9 Configuration Examples
If MLD snooping is disabled, IPv6 multicast packets are broadcast in the VLAN, which wastes
network bandwidth. MLD snooping has the following advantages:
l Interval for sending the MLD Last Member Query messages. This timer helps the S2700
adapt to the change of load on the network.
l Duration for suppressing the Report messages. This timer saves network bandwidth and
reduces loads on the network.
Applicable Environment
By default, MLD snooping is disabled on the S2700. Therefore, you need to enable MLD
snooping on the S2700 globally.
After MLD snooping is enabled on the S2700 globally, MLD snooping remains disabled in a
VLAN by default. Therefore, you also need to enable MLD snooping in the VLAN.
If the hosts connected to an interface need to receive the multicast data of a certain group, you
can add the interface statically to the multicast group. The interface is called a static member
interface. The static member interface never ages.
On a network with stable topology, you can set the router interface on the S2700 as a static router
interface. The static router interface never ages, and can be deleted only through a certain
command.
Pre-configuration Tasks
Before enabling MLD snooping, complete the following tasks:
l Creating a VLAN
l Adding interfaces to the VLAN
Data Preparation
To enable MLD snooping, you need the following data.
No. Data
No. Data
Procedure
Step 1 Run:
system-view
----End
Procedure
Step 1 Run:
system-view
----End
Context
To add an interface to a multicast group statically, do as follows on the S2700.
Procedure
Step 1 Run:
system-view
Step 3 Run:
mld-snooping static-group { group-ipv6-address [ source source-ipv6-address ]
vlan vlan-id }
NOTE
l Before using the mld-snooping static-group command, ensure that the interface is added to the VLAN
specified by vlan-id; otherwise, the configuration fails.
l If the source-address parameter is specified in the mld-snooping static-group command, the MLD
version must be V2; otherwise, the configuration does not take effect even though the command can
be run.
----End
Context
To configure an interface as a static router interface, do as follows on the S2700.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface interface-type interface-number
NOTE
Before using the mld-snooping static-router-port vlan vlan-id command, ensure that the interface is
added to the VLAN specified by vlan-id; otherwise, the configuration fails.
----End
Procedure
Step 1 Run:
system-view
The version is configured for MLD protocol packets that can be processed by MLD snooping.
The version can be set to 1 or 2.
By default, the S2700 can process MLDv1 packets.
----End
Procedure
Step 1 Run the display mld-snooping configuration command to check the configuration information
of MLD snooping.
Step 2 Run the display mld-snooping [ vlan vlan-id ] command to check the status of MLD snooping
in a VLAN.
Step 3 Run the display mld-snooping port-info [ vlan vlan-id [ group group-ipv6address [ source-
address source-ipv6address ] | verbose ] ] command to check information about member
interfaces of a multicast group and the router interface in a VLAN.
Step 4 Run the display mld-snooping router-port [ vlan vlan-id ] command to check information
about the router interface in a VLAN.
NOTE
The display mld-snooping port-info command displays only the information about the static member
interface or static router interface in Up state. If the static member interface or static router interface in
Down state, you can run the display mld-snooping configuration command to check the configuration
of the interface.
----End
Pre-configuration Tasks
Before configuring a multicast group policy for a VLAN, complete the following task:
l 4.3 Enabling MLD Snooping
Data Preparation
To configure a multicast group policy for a VLAN, you need the following data.
No. Data
Procedure
Step 1 Run:
system-view
Step 2 Run:
vlan vlan-id
Step 3 Run:
mld-snooping group-policy acl-number [ mld-version ]
By default, no multicast group policy is available in a VLAN. That is, hosts in a VLAN can join
any multicast group. MLDv1/v2 is used.
Only a basic or advanced ACL6 can be used. Before configuring a multicast group policy, ensure
that an ACL6 has been created and a rule has been defined. For details, see Configuring ACL6.
NOTE
l When a multicast policy is configured for a VLAN, the multicast policy does not take effect if the
ACL6 specified by the ACL number does not exist; therefore, the hosts in the VLAN can join any
multicast group.
l If you run the undo acl ipv6 command to delete the ACL6 used by the multicast policy, hosts in the
VLAN can join any multicast group.
l A multicast policy is invalid for static multicast entries.
----End
Procedure
Step 1 Run the display mld-snooping [ vlan vlan-id ] [ configuration ] command to check the
configuration of MLD snooping in a VLAN.
Step 2 Run the display mld-snooping port-info [ vlan vlan-id [ group group-ipv6-address [ source-
address source-ipv6-address ] | verbose ] ] command to check the configuration of MLD
snooping on an interface.
----End
Applicable Environment
If each interface in a VLAN is connected to only one multicast receiver, you can enable prompt
leave on the interfaces to save bandwidth.
Pre-configuration Tasks
Before configuring the prompt leave function for interfaces in a VLAN, complete the following
tasks:
l 4.3 Enabling MLD Snooping
l Creating an ACL6
Data Preparation
To configure the prompt leave function for interfaces in a VLAN, you need the following data.
No. Data
Procedure
Step 1 Run:
system-view
----End
Procedure
Step 1 Run the display mld-snooping [ vlan vlan-id ] [ configuration ] command to check the
configuration of MLD snooping in a VLAN.
If the configuration is successful, you can find that the prompt leave function is configured
correctly in the VLAN.
----End
Applicable Environment
If a network does not have a Layer 3 multicast device, the MLD querier functions are unavailable
because the Layer 2 devices do not support MLD. To solve this problem, you can enable the
MLD snooping querier on the Layer 2 devices so that the Layer 2 devices can create and maintain
the IPv6 multicast forwarding entries at the data link layer. In this way, the IPv6 multicast data
can be forwarded at the data link layer.
Pre-configuration Tasks
Before configuring the MLD snooping querier on the VLAN, complete the following task:
l Enabling the MLD snooping function on the VLAN
Data Preparation
To configure the MLD snooping querier in a VLAN, you need the following data.
No. Data
Context
Do as follows on the S2700.
Procedure
Step 1 Run:
system-view
NOTE
----End
Procedure
Step 1 Run:
system-view
The interval for sending the MLD Snooping General Query messages is set.
Step 4 Run:
mld-snooping max-response-time max-response-time
The maximum response time of the MLD Snooping General Query messages is set.
Step 5 Run:
mld-snooping last-listener-query-interval time-value
The interval for sending the MLD Snooping Specific-Group Query messages is set.
----End
Context
Do as follows on the S2700.
Procedure
Step 1 Run:
system-view
Step 2 Run:
mld-snooping send-query source-address ipv6-address
----End
Procedure
Step 1 Run the display mld-snooping [ vlan vlan-id ] [ configuration ] command to check the
configuration of MLD snooping in a VLAN.
[Quidway]display mld-snooping vlan 95 configuration
MLD Snooping Configuration for VLAN 95
mld-snooping enable
mld-snooping version 2
Step 2 Run the display mld-snooping configuration command to view the global configuration of
MLD snooping.
[Quidway] display mld-snooping configuration
MLD Snooping Configuration for VLAN 11
mld-snooping enable
mld-snooping group-policy 2000 2
MLD Snooping Configuration for VLAN 12
mld-snooping enable
----End
Applicable Environment
You can modify parameters of MLD snooping to optimize the multicast performance on the
S2700 according to the actual situation of the network.
Pre-configuration Tasks
Before modifying parameters of MLD snooping, complete the following task:
l 4.3 Enabling MLD Snooping
Data Preparation
To modify parameters of MLD snooping, you need the following data.
No. Procedure
No. Procedure
Procedure
Step 1 Run:
system-view
----End
Procedure
Step 1 Run:
system-view
The interval for sending the General Query messages is set. The default value is 60 seconds.
Step 4 Run:
mld-snooping max-response-time max-response-time
The maximum response time of MLD messages is set. The default value is 10 seconds.
Step 5 Run:
mld-snooping robust-count robust-count
----End
Procedure
Step 1 Run:
system-view
The MLD snooping module of the S2700 is enabled to respond to changes of the Layer 2 network
topology.
Step 3 Run:
mld-snooping send-query source-address ipv6-address
The source IPv6 address of the MLD General Query messages that the MLD snooping module
sends to respond to changes of the Layer 2 network topology is set.
By default, the source IPv6 address of the MLD General Query message sent by the S2700 is
FE80::.
Step 3 is optional. After the S2700 is enabled to respond to changes of the Layer 2 network
topology, it sends an MLD General Query message to the downstream S2700 when receiving a
Topology Change message. Then the downstream S2700 can learn the new router interface.
When a member interface receives the MLD General Query message, the member interface
responds with an MLD Report message. Then the S2700 and its downstream S2700 can learn
the new multicast forwarding entry. This function enables the S2700 to forward multicast data
correctly after the Layer 2 topology changes.
----End
Context
To set the duration for suppressing the MLD Report messages with the same content, do as
follows on the S2700.
Procedure
Step 1 Run:
system-view
Step 2 Run:
mld-snooping suppression-time time-value
The duration for suppressing the same MLD Report messages is set.
NOTE
l By default, the duration for suppressing the same MLD Report messages is 10 seconds.
l The MLD snooping function is applicable to only the MLDv1 packets, but is invalid for the MLDv2
packets.
----End
Procedure
Step 1 Run the display mld-snooping [ vlan vlan-id ] command to check information about MLD
snooping in a VLAN.
----End
Example
If the preceding configurations are successful, the following information is displayed:
<Quidway> display mld-snooping vlan 10
MLD Snooping Vlan Information for VLAN 10
MLD Snooping is Enable
MLD Version is Set to default 1
MLD Query Interval is Set to default 125
MLD Max Response Interval is Set to default 10
MLD Robustness is Set to default 2
MLD Last Member Query Interval is Set to default 1
MLD Router Port Aging Interval is Set to 180s or holdtime in hello
MLD Filter Group-Policy is Set to default : Permit All
MLD Prompt Leave Disable
MLD Router Alert is Not Required
MLD Send Router Alert Enable
MLD Snooping Querier Disable
Context
CAUTION
Use this command with caution. After the MLD snooping entries, that is, the dynamic forwarding
entries, of a VLAN are deleted from the multicast forwarding table, the multicast flows sent to
hosts in the VLAN are interrupted. The hosts can receive multicast flows again only after the
S2700 receives the MLD Membership Report messages from the hosts and generates new
forwarding entries.
To clear the dynamic forwarding entries from the multicast forwarding table, run the following
command in the user view.
Procedure
Step 1 Run the reset mld-snooping group { vlan { vlan-id | all } | all } command to clear the dynamic
forwarding entries from the multicast forwarding table.
----End
Context
CAUTION
The statistics on MLD snooping cannot be restored after you clear them. So, confirm the action
before you use the command. To clear the statistics on MLD snooping, run the following
command in the user view.
Procedure
Step 1 Run the reset mld-snooping statistics [ vlan vlan-id ] command to clear the statistics on MLD
snooping in a VLAN.
----End
Context
CAUTION
Debugging affects the performance of the system. So, after debugging, run the undo debugging
mld-snooping all command to disable it immediately.
When a fault occurs in MLD Snooping, you can run the following debugging command in the
user view to debug MLD snooping and locate the fault.
Procedure
Step 1 Run the debugging mld-snooping [ all | event | done [ basic-acl-number ] | packet [advance-
acl-number ] | query [ advance-acl-number ] | report [ advance-acl-number ] | timer |
general ] command in the user view to enable debugging of MLD snooping.
----End
Networking Requirements
As shown in Figure 4-1, Eth 0/0/1 and Eth 0/0/2 on of Switch A are connected to only one
receiver respectively. Other hosts connected to Eth 0/0/1 and Eth 0/0/2 do not need to receive
multicast packets. Therefore, when receiving MLD Leave messages from the two interfaces,
Switch A deletes the forwarding entries of the multicast groups that the hosts leave without
waiting for the timeout of the aging timer. This saves the bandwidth and system resources.
Figure 4-1 Networking diagram for configuring prompt leave of interfaces in a VLAN
IP/MPLS
core
Eth0/0/3
SwitchA
Eth0/0/1 Eth0/0/2
VLAN 3
Configuration Roadmap
The configuration roadmap is as follows:
1. Create VLAN 3 on Switch A and add Eth 0/0/1, Eth 0/0/2, and Eth 0/0/3 to VLAN 3.
2. Enable MLD snooping globally on Switch A.
3. Enable prompt leave of interfaces in VLAN 3 on Switch A.
4. Enable MLD snooping in VLAN 3 on Switch A.
Data Preparation
To complete the configuration, you need the following data:
l ID of the VLAN where prompt leave is enabled: 3
Procedure
Step 1 Create VLAN 3 on Switch A and add Eth 0/0/1, Eth 0/0/2, and Eth 0/0/3 to VLAN 3. The
configuration procedure is not provided here.
Step 5 Verify the configuration. Run the display mld-snooping command on Switch A.
[SwitchA] display mld-snooping vlan 3
MLD Snooping Vlan Information for VLAN 3
MLD Snooping is Enable
MLD Version is Set to default 1
MLD Query Interval is Set to default 125
MLD Max Response Interval is Set to default 10
MLD Robustness is Set to default 2
MLD Last Member Query Interval is Set to default 1
MLD Router Port Aging Interval is Set to 180s or holdtime in hello
MLD Filter Group-Policy is Set to default : Permit All
MLD Prompt Leave Enable
MLD Router Alert is Not Required
MLD Send Router Alert Enable
MLD Snooping Querier Disable
As shown in the preceding output, "MLD Prompt Leave enable" indicates that the configuration
of prompt leave for interfaces in VLAN 3 is successful.
----End
Configuration Files
#
sysname SwitchA
#
mld-snooping enable
#
vlan batch 3
#
vlan 3
mld-snooping enable
mld-snooping prompt-leave
#
interface Ethernet0/0/1
port hybrid tagged vlan 3
#
interface Ethernet0/0/2
port hybrid tagged vlan 3
#
interface Ethernet0/0/3
port hybrid tagged vlan 3
#
return