HP HP 3100-8 v2, HP 3100-16 v2, HP 3100-16-PoE v2, HP 3100-24-PoE v2, HP 3100-24 v2 Configuration Manual
...
HP 3100 v2 Switch Series
IP Multicast
Configuration Guide
HP 3100-8 v2 SI Switch (JG221A)
HP 3100-16 v2 SI Switch (JG222A)
HP 3100-24 v2 SI Switch (JG223A)
HP 3100-8 v2 EI Switch (JD318B)
HP 3100-16 v2 EI Switch (JD319B)
HP 3100-24 v2 EI Switch (JD320B)
HP 3100-8-PoE v2 EI Switch (JD311B)
HP 3100-16-PoE v2 EI Switch (JD312B)
HP 3100-24-PoE v2 EI Switch (JD313B)
Part number: 5998-5994
Software version: Release 5203P05
Document version: 6W100-20140603
Legal and notice information
© Copyright 2014 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.
Contents
Multicast overview ······················································································································································· 1
Introduction to multicast ···················································································································································· 1
Information transmission techniques ······················································································································· 1
Multicast features ······················································································································································ 3
Common notations in multicast ······························································································································· 4
Multicast advantages and applications ················································································································· 4
Multicast models ································································································································································ 5
Multicast architecture ························································································································································ 5
Multicast addresses ·················································································································································· 6
Multicast protocols ··················································································································································· 9
Multicast packet forwarding mechanism ····················································································································· 11
Configuring IGMP snooping ····································································································································· 12
Overview ········································································································································································· 12
Basic concepts in IGMP snooping ······················································································································· 12
How IGMP snooping works ································································································································· 14
IGMP snooping proxying ····································································································································· 15
Protocols and standards ······································································································································· 17
IGMP snooping configuration task list ························································································································· 17
Configuring basic IGMP snooping functions ·············································································································· 18
Enabling IGMP snooping ····································································································································· 18
Specifying the version of IGMP snooping ·········································································································· 18
Configuring static multicast MAC address entries ····························································································· 19
Configuring IGMP snooping port functions ················································································································· 20
Setting aging timers for dynamic ports ··············································································································· 20
Configuring static ports ········································································································································· 21
Configuring a port as a simulated member host ······························································································· 21
Enabling IGMP snooping fast-leave processing ································································································· 22
Disabling a port from becoming a dynamic router port ··················································································· 23
Configuring IGMP snooping querier ··························································································································· 24
Enabling IGMP snooping querier ························································································································ 24
Configuring parameters for IGMP queries and responses ··············································································· 24
Configuring the source IP addresses for IGMP queries ····················································································· 25
Configuring IGMP snooping proxying ························································································································ 26
Enabling IGMP snooping proxying ····················································································································· 26
Configuring a source IP address for the IGMP messages sent by the proxy ·················································· 26
Configuring an IGMP snooping policy ························································································································ 27
Configuring a multicast group filter ····················································································································· 27
Configuring multicast source port filtering ·········································································································· 28
Enabling dropping unknown multicast data ······································································································· 29
Configuring IGMP report suppression ················································································································ 29
Setting the maximum number of multicast groups that a port can join ··························································· 30
Enabling multicast group replacement ················································································································ 30
Setting the 802.1p precedence for IGMP messages ························································································ 31
Configuring a multicast user control policy (available only on the HP 3100 v2 EI) ······································ 32
Enabling the IGMP snooping host tracking function ························································································· 32
Setting the DSCP value for IGMP messages ······································································································· 33
Displaying and maintaining IGMP snooping ·············································································································· 33
IGMP snooping configuration examples ····················································································································· 34
i
Group policy and simulated joining configuration example ············································································ 34
Static port configuration example ······················································································································· 36
IGMP snooping querier configuration example ································································································· 40
IGMP snooping proxying configuration example ······························································································ 42
Multicast source and user control policy configuration example (available only on the HP 3100 v2 EI) ··· 44
Troubleshooting IGMP snooping ·································································································································· 49
Layer 2 multicast forwarding cannot function ···································································································· 49
Configured multicast group policy fails to take effect ······················································································· 49
Configuring multicast VLANs ····································································································································· 51
Overview ········································································································································································· 51
Multicast VLAN configuration task list ························································································································· 52
Configuring a port-based multicast VLAN ··················································································································· 52
Configuration prerequisites ·································································································································· 52
Configuring user port attributes ··························································································································· 53
Configuring multicast VLAN ports ······················································································································· 53
Displaying and maintaining multicast VLAN ··············································································································· 54
Multicast VLAN configuration examples ······················································································································ 54
Configuring MLD snooping (available only on the HP 3100 v2 EI) ······································································ 58
Overview ········································································································································································· 58
Basic concepts in MLD snooping ························································································································· 58
How MLD snooping works ··································································································································· 60
MLD snooping proxying ······································································································································· 61
Protocols and standards ······································································································································· 62
MLD snooping configuration task list ··························································································································· 62
Configuring basic MLD snooping functions ················································································································ 63
Enabling MLD snooping ······································································································································· 64
Specifying the version of MLD snooping ············································································································ 64
Configuring IPv6 static multicast MAC address entries ····················································································· 65
Configuring MLD snooping port functions ··················································································································· 65
Configuring aging timers for dynamic ports ······································································································ 66
Configuring static ports ········································································································································· 66
Configuring a port as a simulated member host ······························································································· 67
Enabling fast-leave processing ····························································································································· 68
Disabling a port from becoming a dynamic router port ··················································································· 68
Configuring MLD snooping querier ····························································································································· 69
Enabling MLD snooping querier ·························································································································· 69
Configuring parameters for MLD queries and responses ················································································· 70
Configuring the source IPv6 addresses for MLD queries ·················································································· 71
Configuring MLD snooping proxying ·························································································································· 71
Enabling MLD snooping proxying ······················································································································· 71
Configuring the source IPv6 addresses for the MLD messages sent by the proxy ········································· 72
Configuring an MLD snooping policy ·························································································································· 72
Configuring an IPv6 multicast group filter ·········································································································· 72
Enabling dropping unknown IPv6 multicast data ······························································································ 73
Configuring MLD report suppression ·················································································································· 74
Setting the maximum number of multicast groups that a port can join ··························································· 74
Enabling IPv6 multicast group replacement ······································································································· 75
Setting the 802.1p precedence for MLD messages ·························································································· 76
Configuring an IPv6 multicast user control policy ······························································································ 76
Enabling the MLD snooping host tracking function ··························································································· 77
Setting the DSCP value for MLD messages ········································································································· 78
Displaying and maintaining MLD snooping ················································································································ 78
MLD snooping configuration examples ······················································································································· 79
ii
IPv6 group policy and simulated joining configuration example ···································································· 79
Static port configuration example ······················································································································· 81
MLD snooping querier configuration example ··································································································· 84
MLD snooping proxying configuration example ································································································ 86
IPv6 multicast source and user control policy configuration example ····························································· 89
Troubleshooting MLD snooping ···································································································································· 93
Layer 2 multicast forwarding cannot function ···································································································· 93
Configured IPv6 multicast group policy fails to take effect ··············································································· 94
Configuring IPv6 multicast VLANs (available only on the HP 3100 v2 EI) ··························································· 95
Overview ········································································································································································· 95
IPv6 multicast VLAN configuration task list ················································································································· 96
Configuring a port-based IPv6 multicast VLAN ·········································································································· 96
Configuration prerequisites ·································································································································· 96
Configuring user port attributes ··························································································································· 97
Configuring IPv6 multicast VLAN ports ··············································································································· 97
Displaying and maintaining IPv6 multicast VLAN ······································································································ 98
IPv6 multicast VLAN configuration examples ·············································································································· 98
Support and other resources ·································································································································· 102
Contacting HP ······························································································································································ 102
Subscription service ············································································································································ 102
Related information ······················································································································································ 102
Documents ···························································································································································· 102
Websites ······························································································································································· 102
Conventions ·································································································································································· 103
Index ········································································································································································ 105
iii
Multicast overview
Introduction to multicast
As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the
issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data
transmission over a network, multicast greatly saves network bandwidth and reduces network load.
By using multicast technology, a network operator can easily provide new value-added services, such as
live webcasting, web TV, distance learning, telemedicine, web radio, real time video conferencing, and
other bandwidth-critical and time-critical information services.
The term "router " in this document refers to both routers and Layer 3 switches.
Unless otherwise stated, the term "multicast" in this document refers to IP multicast.
Information transmission techniques
The information transmission techniques include unicast, broadcast, and multicast.
Unicast
In unicast transmission, the information source must send a separate copy of information to each host that
needs the information.
Figure 1 Unicast transmission
Host A
Receiver
Host B
Source
Host C
Receiver
Host D
IP network
Packets for Host B
Packets for Host D
Packets for Host E
Receiver
Host E
In Figure 1, assume that Host B, Host D and Host E need the information. A separate transmission channel
must be established from the information source to each of these hosts.
1
Broadcast
In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts that
need the information. If a large number of hosts need the information, the information source must send
a separate copy of the same information to each of these hosts. Sending many copies can place a
tremendous pressure on the information source and the network bandwidth.
Unicast is not suitable for batch transmission of information.
In broadcast transmission, the information source sends information to all hosts on the subnet, even if
some hosts do not need the information.
Figure 2 Broadcast transmission
Multicast
In Figure 2, assume that only Host B, Host D, and Host E need the information. If the information is
broadcast to the subnet, Host A and Host C also receive it. In addition to information security issues,
broadcasting to hosts that do not need the information also causes traffic flooding on the same subnet.
Broadcast is disadvantageous in transmitting data to specific hosts. Moreover, broadcast transmission is
a significant waste of network resources.
Unicast and broadcast techniques cannot provide point-to-multipoint data transmissions with the
minimum network consumption.
Multicast transmission can solve this problem. When some hosts on the network need multicast
information, the information sender, or multicast source, sends only one copy of the information.
Multicast distribution trees are built through multicast routing protocols, and the packets are replicated
only on nodes where the trees branch.
2
Figure 3 Multicast transmission
The mul ticast s ource sen ds only one co py of the inform ation to a mul ticast g ro up. Host B, Host D an d Host
E, which are receivers of the information, must join the multicast group. The routers on the network
duplicate and forward the information based on the distribution of the group members. Finally, the
information is correctly delivered to Host B, Host D, and Host E.
To summarize, multicast has the following advantages:
• Advantages over unicast—Because multicast traffic flows to the farthest-possible node from the
source before it is replicated and distributed, an increase in the number of hosts does not increase
the load of the source or remarkably add to the usage of network resources.
• Advantages over broadcast—Because multicast data is sent only to the receivers that need it,
multicast uses network bandwidth reasonably and enhances network security. In addition, data
broadcast is confined to the same subnet, but multicast is not.
Multicast features
• A multicast group is a multicast receiver set identified by an IP multicast address. Hosts join a
multicast group to become members of the multicast group before they can receive the multicast
data addressed to that multicast group. Typically, a multicast source does not need to join a
multicast group.
• An information sender is called a "multicast source". A multicast source can send data to multiple
multicast groups at the same time, and multiple multicast sources can send data to the same
multicast group at the same time.
• All hosts that have joined a multicast group become members of the multicast group. The group
memberships are dynamic. Hosts can join or leave multicast groups at any time. Multicast groups
are not subject to geographic restrictions.
• Routers or Layer 3 switches that support Layer 3 multicast are called "multicast routers" or "Layer 3
multicast devices". In addition to providing the multicast routing function, a multicast router can also
manage multicast group memberships on stub subnets with attached group members. A multicast
router itself can be a multicast group member.
3
For a better understanding of the multicast concept, you can compare multicast transmission to the
transmission of TV programs.
Table 1 Comparing TV program transmission and multicast transmission
TV transmission
A TV station transmits a TV program through a
channel.
A user tunes the TV set to the channel. A receiver joins the multicast group.
The user starts to watch the TV program transmitted
by the TV station via the channel.
The user turns off the TV set or tunes to another
channel.
Common notations in multicast
The following notations are commonly used in multicast transmission:
• (*, G)—Indicates a rendezvous point tree (RPT), or a multicast packet that any multicast source sends
to multicast group G. Here, the asterisk represents any multicast source, and "G" represents a
specific multicast group.
• (S, G)—Indicates a shortest path tree (SPT), or a multicast packet that multicast source S sends to
multicast group G. Here, "S" represents a specific multicast source, and "G" represents a specific
multicast group.
Multicast transmission
A multicast source sends multicast data to a multicast
group.
The receiver starts to receive the multicast data that the
source is sending to the multicast group.
The receiver leaves the multicast group or joins another
group.
Multicast advantages and applications
Multicast advantages
Advantages of the multicast technique include the following:
• Enhanced efficiency—Reduces the processor load of information source servers and network
devices.
• Optimal performance—Reduces redundant traffic.
• Distributed application—Enables point-to-multipoint applications at the price of minimum network
resources.
Multicast applications
The scenarios in which the multicast technique can be effectively applied are:
• Multimedia and streaming applications, such as web TV, web radio, and real time video/audio
conferencing
• Communication for training and cooperative operations, such as distance learning and
telemedicine
• Data warehouse and financial applications (stock quotes)
• Any other point-to-multipoint application for data distribution
4
Multicast models
Based on how the receivers treat the multicast sources, the multicast models include any-source multicast
(ASM), source-filtered multicast (SFM), and source-specific multicast (SSM).
ASM model
In the ASM model, any sender can send information to a multicast group as a multicast source, and
receivers can join a multicast group (identified by a group address) and obtain multicast information
addressed to that multicast group. In this model, receivers do not know the positions of the multicast
sources in advance. However, they can join or leave the multicast group at any time.
SFM model
The SFM model is derived from the ASM model. To a sender, the two models appear to have the same
multicast membership architecture.
The SFM model functionally extends the ASM model. The upper-layer software checks the source address
of received multicast packets and permits or denies multicast traffic from specific sources. Therefore,
receivers can receive the multicast data from only part of the multicast sources. To a receiver, multicast
sources are not all valid; they are filtered.
SSM model
Users might be interested in the multicast data from only certain multicast sources. The SSM model
provides a transmission service that enables users to specify the multicast sources that they are interested
in at the client side.
The main difference between the SSM model and the ASM model is that in the SSM model, receivers
have already determined the locations of the multicast sources by some other means. In addition, the
SSM model uses a multicast address range that is different from that of the ASM/SFM model, and
dedicated multicast forwarding paths are established between receivers and the specified multicast
sources.
Multicast architecture
IP multicast addresses the following questions:
• Where should the multicast source transmit information to? (Multicast addressing.)
• What receivers exist on the network? (Host registration.)
• Where is the multicast source that will provide data to the receivers? (Multicast source discovery.)
• How should information be transmitted to the receivers? (Multicast routing.)
IP multicast is an end-to-end service. The multicast architecture involves the following parts:
• Addressing mechanism—A multicast source sends information to a group of receivers through a
multicast address.
• Host registration—Receiver hosts can join and leave multicast groups dynamically. This mechanism
is the basis for management of group memberships.
• Multicast routing—A multicast distribution tree (a forwarding path tree for multicast data on the
network) is constructed for delivering multicast data from a multicast source to receivers.
• Multicast applications—A software system that supports multicast applications, such as video
conferencing, must be installed on multicast sources and receiver hosts. The TCP/IP stack must
support reception and transmission of multicast data.
5
Multicast addresses
p
g
g
p
Network-layer multicast addresses (multicast IP addresses) enables communication between multicast
sources and multicast group members. In addition, a technique must be available to map multicast IP
addresses to link-layer multicast MAC addresses.
IP multicast addresses
• IPv4 multicast addresses
Internet Assigned Numbers Authority (IANA) assigned the Class D address space (224.0.0.0 to
239.255.255.255) to IPv4 multicast.
Table 2 Class D IP address blocks and description
Address block Descri
Reserved permanent group addresses. The IP address 224.0.0.0 is
reserved. Other IP addresses can be used by routing protocols and
224.0.0.0 to 224.0.0.255
224.0.1.0 to 238.255.255.255
for topology searching, protocol maintenance, and so on. Table 3
lists common permanent group addresses. A packet destined for an
address in this block will not be forwarded beyond the local subnet
regardless of the Time to Live (TTL) value in the IP header.
Globally scoped group addresses. This block includes the following
types of designated group addresses:
• 232.0.0.0/8—SSM group addresses.
tion
• 233.0.0.0/8—Glop group addresses.
Administratively scoped multicast addresses. These addresses are
239.0.0.0 to 239.255.255.255
considered locally unique rather than globally unique, and can be
reused in domains administered by different organizations without
causing conflicts. For more information, see RFC 2365.
NOTE:
"Glop" is a mechanism for assi
ning multicast addresses between different autonomous systems (ASs). By
filling an AS number into the middle two bytes of 233.0.0.0, you
For more information, see RFC 2770.
Table 3 Some reserved multicast addresses
et 255 multicast addresses for that AS.
Address Descri
224.0.0.1 All systems on this subnet, including hosts and routers
224.0.0.2 All multicast routers on this subnet
224.0.0.3 Unassigned
224.0.0.4 Distance Vector Multicast Routing Protocol (DVMRP) routers
224.0.0.5 Open Shortest Path First (OSPF) routers
224.0.0.6 OSPF designated routers and backup designated routers
224.0.0.7 Shared Tree (ST) routers
224.0.0.8 ST hosts
224.0.0.9 Routing Information Protocol version 2 (RIPv2) routers
224.0.0.11 Mobile agents
tion
6
Address Description
p
224.0.0.12 Dynamic Host Configuration Protocol (DHCP) server/relay agent
224.0.0.13 All Protocol Independent Multicast (PIM) routers
224.0.0.14 Resource Reservation Protocol (RSVP) encapsulation
224.0.0.15 All Core-Based Tree (CBT) routers
224.0.0.16 Designated Subnetwork Bandwidth Management (SBM)
224.0.0.17 All SBMs
224.0.0.18 Virtual Router Redundancy Protocol (VRRP)
• IPv6 multicast addresses
Figure 4 IPv6 multicast format
The following describes the fields of an IPv6 multicast address:
{ 0xFF—The most significant eight bits are 11111111, which indicates that this address is an IPv6
multicast address.
{ Flags—The Flags field contains four bits.
Figure 5 Flags field format
Table 4 Flags field description
Bit Descri
0 Reserved, set to 0.
tion
• When set to 0, it indicates that this address is an IPv6 multicast
address without an embedded RP address.
R
• When set to 1, it indicates that this address is an IPv6 multicast
address with an embedded RP address. (The P and T bits must
also be set to 1.)
• When set to 0, it indicates that this address is an IPv6 multicast
address not based on a unicast prefix.
P
• When set to 1, it indicates that this address is an IPv6 multicast
address based on a unicast prefix. (The T bit must also be set to
1. )
• When set to 0, it indicates that this address is an IPv6 multicast
T
address permanently-assigned by IANA.
• When set to 1, it indicates that this address is a transient, or
dynamically assigned IPv6 multicast address.
7
{ Scope—The Scope field contains four bits, which indicate the scope of the IPv6 internetwork for
g
which the multicast traffic is intended.
Table 5 Values of the Scope field
Value Meanin
0, F Reserved
1 Interface-local scope
2 Link-local scope
3 Subnet-local scope
4 Admin-local scope
5 Site-local scope
6, 7, 9 through D Unassigned
8 Organization-local scope
E Global scope
{ Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 mul tic ast group in
the scope that the Scope field defines.
Ethernet multicast MAC addresses
A multicast MAC address identifies a group of receivers at the data link layer.
• IPv4 multicast MAC addresses
As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E.
Bit 25 is 0, and the other 23 bits are the least significant 23 bits of a multicast IPv4 address.
Figure 6 IPv4-to-MAC address mapping
The most significant four bits of a multicast IPv4 address are 1110, which indicates that this
address is a multicast address. Only 23 bits of the remaining 28 bits are mapped to a MAC
address, so five bits of the multicast IPv4 address are lost. As a result, 32 multicast IPv4 addresses
map to the same IPv4 multicast MAC address. Therefore, in Layer 2 multicast forwarding, a switch
might receive some multicast data destined for other IPv4 multicast groups. The upper layer must
filter such redundant data.
• IPv6 multicast MAC addresses
The most significant 16 bits of an IPv6 multicast MAC address are 0x3333. The least significant
32 bits are the least significant 32 bits of a multicast IPv6 address.
8
Figure 7 An example of IPv6-to-MAC address mapping
Multicast protocols
Generally, Layer 3 multicast refers to IP multicast working at the network layer. The corresponding
multicast protocols are Layer 3 multicast protocols, which include IGMP, MLD, PIM, IPv6 PIM, MSDP,
MBGP, and IPv6 MBGP. Layer 2 multicast refers to IP multicast working at the data link layer. The
corresponding multicast protocols are Layer 2 multicast protocols, which include IGMP snooping, MLD
snooping, PIM snooping, IPv6 PIM snooping, multicast VLAN, and IPv6 multicast VLAN.
IGMP snooping, PIM snooping, multicast VLAN, IGMP, PIM, MSDP, and MBGP are for IPv4, and MLD
snooping, IPv6 PIM snooping, IPv6 multicast VLAN, MLD, IPv6 PIM, and IPv6 MBGP are for IPv6.
This section provides only general descriptions about applications and functions of the Layer 2 and Layer
3 multicast protocols in a network. For more information about these protocols, see the related chapters.
Layer 3 multicast protocols
Layer 3 multicast protocols include multicast group management protocols and multicast routing
protocols.
Figure 8 Positions of Layer 3 multicast protocols
• Multicast group management protocols
Typically, the Internet Group Management Protocol (IGMP) or Multicast Listener Discovery Protocol
(MLD) is used between hosts and Layer 3 multicast devices that directly connect to the hosts. These
9
protocols define the mechanism of establishing and maintaining group memberships between
hosts and Layer 3 multicast devices.
• Multicast routing protocols
A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain multicast
routes and forward multicast packets correctly and efficiently. Multicast routes constitute loop-free
data transmission paths from a data source to multiple receivers, namely, a multicast distribution
tree.
In the ASM model, multicast routes include intra-domain routes and inter-domain routes.
{ An intra-domain multicast routing protocol discovers multicast sources and builds multicast
distribution trees within an AS to deliver multicast data to receivers. Among a variety of mature
intra-domain multicast routing protocols, Protocol Independent Multicast (PIM) is most widely
used. Based on the forwarding mechanism, PIM has dense mode (often referred to as
"PIM-DM"), and sparse mode (often referred to as "PIM-SM").
{ An inter-domain multicast routing protocol is used for delivery of multicast information between
two ASs. So far, mature solutions include Multicast Source Discovery Protocol (MSDP) and
Multicast Border Gateway Protocol (MBGP). MSDP propagates multicast source information
among different ASs. MBGP is an extension of the Multiprotocol Border Gateway Protocol
(MP-BGP) for exchanging multicast routing information among different ASs.
For the SSM model, multicast routes are not divided into intra-domain routes and inter-domain
routes. Because receivers know the position of the multicast source, channels established through
PIM-SM are sufficient for the transport of multicast information.
Layer 2 multicast protocols
Layer 2 multicast protocols include IGMP snooping, MLD snooping, PIM snooping, IPv6 PIM snooping,
multicast VLAN, and IPv6 multicast VLAN.
Figure 9 Positions of Layer 2 multicast protocols
• IGMP snooping and MLD snooping
IGMP snooping and MLD snooping are multicast constraining mechanisms that run on Layer 2
devices. They manage and control multicast groups by monitoring and analyzing IGMP or MLD
messages exchanged between the hosts and Layer 3 multicast devices, effectively controlling the
flooding of multicast data in a Layer 2 network.
10
• PIM snooping and IPv6 PIM snooping
PIM snooping and IPv6 PIM snooping run on Layer 2 devices. They determine which ports are
interested in multicast data by analyzing the received IPv6 PIM messages, and add the ports to a
multicast forwarding entry to make sure that multicast data can be forwarded to only the ports that
are interested in the data.
• Multicast VLAN and IPv6 multicast VLAN
In the traditional multicast-on-demand mode, when users in different VLANs on a Layer 2 device
need multicast information, the upstream Layer 3 device must forward a separate copy of the
multicast data to each VLAN of the Layer 2 device. When the multicast VLAN or IPv6 multicast
VLAN feature is enabled on the Layer 2 device, the Layer 3 multicast device sends only one copy
of multicast to the multicast VLAN or IPv6 multicast VLAN on the Layer 2 device. This approach
avoids waste of network bandwidth and extra burden on the Layer 3 device.
Multicast packet forwarding mechanism
In a multicast model, a multicast source sends information to the host group identified by the multicast
group address in the destination address field of IP multicast packets. To deliver multicast packets to
receivers located at different positions of the network, multicast routers on the forwarding paths usually
need to forward multicast packets that an incoming interface receives to multiple outgoing interfaces.
Compared with a unicast model, a multicast model is more complex in the following aspects:
• To ensure multicast packet transmission in the network, unicast routing tables or multicast routing
tables (for example, the MBGP routing table) specially provided for multicast must be used as
guidance for multicast forwarding.
• To process the same multicast information from different peers received on different interfaces of the
same device, every multicast packet undergoes a reverse path forwarding (RPF) check on the
incoming interface. The result of the RPF check determines whether the packet will be forwarded or
discarded. The RPF check mechanism is the basis for most multicast routing protocols to implement
multicast forwarding.
11
Configuring IGMP snooping
Overview
Internet Group Management Protocol (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 that runs IGMP snooping establishes mappings
between ports and multicast MAC addresses, and forwards multicast data based on these mappings.
As shown in Figure 10, w
all devices at Layer 2. With IGMP snooping enabled, the Layer 2 switch forwards multicast packets for
known multicast groups to only the receivers that require the multicast data at Layer 2. This feature
improves bandwidth efficiency, enhances multicast security, and helps per-host accounting for multicast
users.
Figure 10 Before and after IGMP snooping is enabled on the Layer 2 device
ithout IGMP snooping enabled, the Layer 2 switch floods multicast packets to
Basic concepts in IGMP snooping
IGMP snooping related ports
As shown in Figure 11, 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 as members of a multicast group.
12
Figure 11 IGMP snooping related ports
A
y
The following describes the ports involved in IGMP snooping:
• Router port—Layer 3 multicast device-side port. Layer 3 multicast devices include designated
routers (DRs) and IGMP queriers. In Figure 11, Ether
net 1/0/1 of Switch A and Ethernet 1/0/1 of
Switch B are router ports. The switch registers all its router ports in its router port list.
Do not confuse the "router port" in IGMP snooping with the "routed interface" commonly known as
the "Layer 3 interface." The router port in IGMP snooping is the Layer 2 interface.
• Member port—Multicast receiver-side port. In Figure 11, Ether
net 1/0/2 and Ethernet 1/0/3 of
Switch A and Ethernet 1/0/2 of Switch B are member ports. The switch registers all its member
ports in its IGMP snooping forwarding table.
Unless otherwise specified, router ports and member ports in this document include both static and
dynamic router ports and member ports.
NOTE:
n 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 that receive PIM hello messages are received are dynamic router ports.
Aging timers for dynamic ports in IGMP snooping and related messages and actions
Timer Description
For each dynamic router
port, the switch starts an
Dynamic router port
aging timer
aging timer. When the
timer expires, the
dynamic router port ages
out.
Message before expiry Action after expir
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.
13
Timer Description
y
When a port dynamically
joins a multicast group,
Dynamic member port
aging timer
the switch starts an aging
timer for the port. When
the timer expires, the
dynamic member port
ages out.
NOTE:
In IGMP snooping, only dynamic ports age out. Static ports never age out.
How IGMP snooping works
In this section, the involved ports are dynamic ports. For information about how to configure and remove
static ports, see "Configuring static ports."
A switch that runs IGMP snooping performs different actions when it receives different IGMP messages.
When receiving a general query
The IGMP querier periodically sends IGMP general queries to all hosts and routers identified by the
address 224.0.0.1 on the local subnet to determine whether any active multicast group members exist on
the subnet.
Message before expiry Action after expir
The switch removes this
IGMP membership
report.
port from the IGMP
snooping forwarding
table.
After receiving an IGMP general query, the switch forwards it to all ports in the VLAN, except the port
that received the query. The switch also performs one of the following actions:
• If the receiving port is a dynamic router port in the router port list, restarts the aging timer for the
port.
• If the receiving port is not in its router port list, adds it into its router port list as a dynamic router port
and starts an aging timer for the port.
When receiving a membership report
A host sends an IGMP report to the IGMP querier for the following purposes:
• If the host has been a member of a multicast group, responds to the query with an IGMP report.
• Applies for joining a multicast group.
After receiving an IGMP report, the switch forwards it through all the router ports in the VLAN, resolves
the address of the reported multicast group. The switch also performs one of the following actions:
• If no forwarding entry matches the group address, creates a forwarding entry for the group, adds
the receiving port as a dynamic member port to the forwarding entry, and starts an aging timer for
the port.
• If a forwarding entry matches the group address, but the receiving port is not in the forwarding
entry for the group, adds the port as a dynamic member port to the forwarding entry and starts an
aging timer for the port.
• If a forwarding entry matches the group address and the receiving port is in the forwarding entry
for the group, restarts the aging timer for the port.
A switch does not forward an IGMP report through a non-router port. If the switch forwards a report
message through a member port, the IGMP report suppression mechanism causes all the attached hosts
14
that are monitoring the reported multicast address suppress their own reports. This makes the switch
unable to know whether the reported multicast group still has active members attached to that port.
When receiving a leave message
When an IGMPv 1 host leaves a mu ltic ast g ro up, th e hos t doe s not send an I GMP l eave m essag e, and the
switch cannot know immediately that the host has left the multicast group. However, because the host
stops sending IGMP reports as soon as it leaves the multicast group, the switch removes the port that
connects to the host from the forwarding entry for the multicast group when the aging timer for the port
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 examines
whether a forwarding entry matches the group address in the message, and, if a match is found, whether
the forwarding entry for the group contains the dynamic member port.
• If no forwarding entry matches the group address, or if the forwarding entry does not contain the
port, the switch directly discards the IGMP leave message.
• If a forwarding entry matches the group address and the forwarding entry contains the port, the
switch forwards the leave message to all router ports in the 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 forwarding entry for that group. Instead, it restarts
the aging timer for the port.
After receiving the IGMP leave message, the IGMP querier resolves the multicast group address in the
message and sends an IGMP group-specific query to the multicast group through the port that received
the leave message. After receiving the IGMP group-specific query, the switch forwards it through all its
router ports in the VLAN and all member ports of the multicast group. The switch also performs the
following judgment for the port that received the IGMP leave message:
• If the port (assuming that it is a dynamic member port) receives an IGMP report in response to the
group-specific query before its aging timer expires, it indicates that some host attached to the port
is receiving or expecting to receive multicast data for the multicast group. The switch restarts the
aging timer for the port.
• If the port receives no IGMP report in response to the group-specific query before its aging timer
expires, it indicates that no hosts attached to the port are still listening to that group address. The
switch removes the port from the forwarding entry for the multicast group when the aging timer
expires.
IGMP snooping proxying
You can configure the IGMP snooping proxying function on an edge device to reduce 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.
15
Figure 12 Network diagram
g
IP network
Proxy & Querier
Switch A
Host A
Receiver
Host B
IGMP Querier
Router A
Query from Router A
Report from Switch A
Query from Switch A
Report from Host
Host C
Receiver
As shown in Figure 12, Swi tch A works as an IGMP snooping proxy. As a host from the perspective of the
querier Router A, Switch A represents its attached hosts to send membership reports and leave messages
to Router A.
Table 6 IGMP message processing on an IGMP snooping proxy
IGMP messa
General query
e Actions
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 of all router ports.
Group-specific query
Report
Leave
In response to the IGMP group-specific query for a certain multicast
group, the proxy sends the report to the group out of all router ports if the
forwarding entry for the group still contains a member port.
After receiving a report for a multicast group, the proxy looks up the
multicast forwarding table for the forwarding entry for the multicast
group.
• If a forwarding entry matches the multicast group and contains the
receiving port as a dynamic member port, the proxy restarts the
aging timer for the port.
• If a forwarding entry matches the multicast group but does not
contain the receiving port, the proxy adds the port to the forwarding
entry as a dynamic member port and starts an aging timer for the
port.
• If no forwarding entry matches the multicast group, the proxy creates
a forwarding entry for the multicast group, adds the receiving port to
the forwarding entry as a dynamic member port, and starts an aging
timer for the port.
In response to an IGMP leave message for a multicast group, the proxy
sends a group-specific query out of 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 of all
router ports.
16
Protocols and standards
RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener
Discovery (MLD) Snooping Switches
IGMP snooping configuration task list
Task Remarks
Configuring basic
IGMP snooping
functions
Configuring IGMP
snooping port
functions
Configuring IGMP
snooping querier
Configuring IGMP
snooping proxying
Enabling IGMP snooping Required
Specifying the version of IGMP snooping Optional
Configuring static multicast MAC address entries Optional
Setting aging timers for dynamic ports Optional
Configuring static ports Optional
Configuring a port as a simulated member host Optional
Enabling IGMP snooping fast-leave processing Optional
Disabling a port from becoming a dynamic router port Optional
Enabling IGMP snooping querier Optional
Configuring parameters for IGMP queries and responses Optional
Configuring the source IP addresses for IGMP queries Optional
Enabling IGMP snooping proxying Optional
Configuring a source IP address for the IGMP messages sent by
the proxy
Configuring a multicast group filter Optional
Configuring multicast source port filtering Optional
Enabling dropping unknown multicast data Optional
Optional
Configuring IGMP report suppression Optional
Configuring an IGMP
snooping policy
Setting the maximum number of multicast groups that a port
can join
Setting the 802.1p precedence for IGMP messages Optional
Enabling multicast group replacement Optional
Configuring a multicast user control policy (available only on
the HP 3100 v2 EI)
Enabling the IGMP snooping host tracking function Optional
Setting the DSCP value for IGMP messages Optional
Optional
Optional
For the configuration tasks in this section:
• In IGMP snooping view, the configurations that you make are effective in all VLANs. In VLAN view,
the configurations that you make are effective on only the ports that belong to the current VLAN. For
a given VLAN, a configuration that you make in IGMP snooping view is effective only if you do not
make the same configuration in VLAN view.
17
• In IGMP snooping view, the configurations that you make are effective on all ports. In Layer 2
Ethernet interface view or Layer 2 aggregate interface view, the configurations that you make are
effective only on the current port. In port group view, the configurations that you make are effective
on all ports in the current port group. For a given port, a configuration that you make in IGMP
snooping view is effective only if you do not make the same configuration in Layer 2 Ethernet
interface view, Layer 2 aggregate interface view, or port group view.
• For IGMP snooping, the configurations that you make on a Layer 2 aggregate interface do not
interfere with those you make on its member ports, nor do they participate in aggregation
calculations. Configurations that you make on a member port of an aggregate group do not take
effect until it leaves the aggregate group.
Configuring basic IGMP snooping functions
Before you configure basic IGMP snooping functions, complete the following tasks:
• Configure the corresponding VLANs.
• Determine the version of IGMP snooping.
Enabling IGMP snooping
When you enable IGMP snooping, follow these guidelines:
• You must enable IGMP snooping globally before you enable it in a VLAN.
• When you enable IGMP snooping in a specified VLAN, IGMP snooping works only on the ports in
this VLAN.
To enable IGMP snooping:
Step Command
1. Enter system view.
2. Enable IGMP snooping globally
and enter IGMP-snooping view.
3. Return to system view.
4. Enter VLAN view.
5. Enable IGMP snooping in the
VLAN.
system-view N/A
igmp-snooping Disabled by default
quit N/A
vlan vlan-id N/A
igmp-snooping enable
Specifying the version of IGMP snooping
Different versions of IGMP snooping can process different versions of IGMP messages:
• IGMPv2 snooping can process IGMPv1 and IGMPv2 messages, but cannot process IGMPv3
messages, which will be flooded in the VLAN.
• IGMPv3 snooping can process IGMPv1, IGMPv2 and IGMPv3 messages.
Remarks
Disabled by default
If you change IGMPv3 snooping to IGMPv2 snooping, the system:
• Clears all IGMP snooping forwarding entries that are dynamically added.
• Keeps static IGMPv3 snooping forwarding entries (*, G).
18
• Clears static IGMPv3 snooping forwarding entries (S, G), which will be restored when IGMP
snooping is switched back to IGMPv3 snooping.
For more information about static joins, see "Configuring static ports."
To specify the version of IGMP snooping:
Step Command
1. Enter system view.
2. Enter VLAN view.
3. Specify the version of IGMP
snooping.
system-view N/A
vlan vlan-id N/A
igmp-snooping version
version-number
Remarks
Version 2 by default
Configuring static multicast MAC address entries
In Layer-2 multicast, a Layer 2 multicast protocol (such as IGMP snooping) can dynamically add multicast
MAC address entries. Or, you can manually configure multicast MAC address entries.
Configuration guidelines
• In system view, the configuration is effective for the specified ports. In interface view or port group
view, the configuration is effective only on the current port or the ports in the current port group.
• Any legal multicast MAC address except 0100-5Exx-xxxx (where "x" represents a hexadecimal
number from 0 to F) can be manually added to the multicast MAC address table. Multicast MAC
addresses are the MAC addresses whose the least significant bit of the most significant octet is 1.
Configuration procedure
To configure a static multicast MAC address entry in system view:
Step Command
1. Enter system view.
2. Configure a static multicast
MAC address entry.
To configure static multicast MAC address entries in interface view:
Step Command
1. Enter system view.
2. Enter Layer 2 Ethernet
interface view, Layer 2
aggregate interface view, or
port group view.
Remarks
system-view N/A
mac-address multicast
mac-address interface interface-list
vlan vlan-id
No static multicast MAC address
entries exist by default.
Remarks
system-view N/A
• Enter Layer 2 Ethernet interface
view or Layer 2 aggregate
interface view:
interface interface-type
interface-number
Use either command.
• Enter port group view:
port-group manual
port-group-name
3. Configure a static multicast
MAC address entry.
mac-address multicast
mac-address vlan vlan-id
19
No static multicast MAC address
entries exist by default.
Configuring IGMP snooping port functions
Before you configure IGMP snooping port functions, complete the following tasks:
• Enable IGMP snooping in the VLAN.
• Configure the corresponding port groups.
• Determine the aging time of dynamic router ports.
• Determine the aging time of dynamic member ports.
• Determine the multicast group and multicast source addresses.
Setting aging timers for dynamic ports
If a switch receives no IGMP general queries or PIM hello messages on a dynamic router port when the
aging timer of the port expires, the switch removes the port from the router port list.
If the switch receives no IGMP reports for a multicast group on a dynamic member port when the aging
timer of the port expires, the switch removes the port from the multicast forwarding entry for that multicast
group.
If the memberships of multicast groups change frequently, you can set a relatively small value for the
aging timer of the dynamic member ports. If the memberships of multicast groups change rarely, you can
set a relatively large value.
Configuring aging timers for dynamic ports globally
Step Command
1. Enter system view.
2. Enter IGMP-snooping view.
3. Set the aging timer for
dynamic router ports.
4. Set the aging timer for
dynamic member ports.
system-view N/A
igmp-snooping N/A
router-aging-time interval
host-aging-time interval
Configuring aging timers for dynamic ports in a VLAN
Step Command
1. Enter system view.
2. Enter VLAN view.
3. Set the aging timer for
dynamic router ports.
4. Set the aging timer for
dynamic member ports.
system-view N/A
vlan vlan-id N/A
igmp-snooping router-aging-time
interval
igmp-snooping host-aging-time
interval
Remarks
105 seconds by default
260 seconds by default
Remarks
105 seconds by default
260 seconds by default
20
Configuring static ports
If all 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 the
port as a static member port for the specified multicast group or the specified multicast source and group.
You can also configure a port as a static router port, through which the switch can forward all the
multicast traffic that it received.
Configuration guidelines
• A static member port does not respond to queries from the IGMP querier; when you configure a port
as a static member port or cancel this configuration on the port, the port does not send an
unsolicited IGMP report or an IGMP leave message.
• Static member ports and static router ports never age out. To remove such a port, use the
corresponding undo command.
Configuration procedure
To configure static ports:
Step Command
1. Enter system view.
system-view N/A
Remarks
• Enter Layer 2 Ethernet interface
view or Layer 2 aggregate
2. Enter Layer 2 Ethernet
interface view, Layer 2
aggregate interface view, or
port group view.
3. Configure the port as a static
member port.
4. Configure the port as a static
router port.
interface view:
interface interface-type
interface-number
• Enter port group view:
port-group manual
port-group-name
igmp-snooping static-group
group-address [ source-ip
source-address ] vlan vlan-id
igmp-snooping static-router-port
vlan vlan-id
Use either command.
No static member ports exist by
default.
No static router ports exist by
default.
Configuring a port as a simulated member host
Generally, a host t hat runs I GM P can respond to IGMP queries that the IGM P querier sends. If a host fails
to respond, the multicast router might deem that no member of this multicast group exists on the network
segment, and removes the corresponding forwarding path.
To avoid this situation, you can configure the port as a simulated member host for a multicast group. A
simulated host is equivalent to an independent host. For example, when a simulated member host
receives an IGMP query, it gives a response separately. Therefore, the switch can continue receiving
multicast data.
A simulated host acts like a real host in the following ways:
• When a port is configured as a simulated member host, the switch sends an unsolicited IGMP
report through the port, and can respond to IGMP general queries with IGMP reports through the
port.
21
• When the simulated joining function is disabled on a port, the switch sends an IGMP leave
message through the port.
Unlike a static member port, a port that you configure as a simulated member host ages out like a
dynamic member port.
To configure a port as a simulated member host:
Step Command
1. Enter system view.
system-view N/A
Remarks
• Enter Layer 2 Ethernet interface
view or Layer 2 aggregate
2. Enter Layer 2 Ethernet
interface view, Layer 2
aggregate interface view, or
port group view.
3. Configure a port as a
simulated member host.
interface view:
interface interface-type
interface-number
• Enter port group view:
port-group manual
port-group-name
igmp-snooping host-join
group-address [ source-ip
source-address ] vlan vlan-id
Use either command.
Not configured by default.
Enabling IGMP snooping fast-leave processing
IGMP snooping fast-leave processing enables the switch to process IGMP leave messages quickly. With
IGMP snooping fast-leave processing enabled, when the switch receives an IGMP leave message on a
port, it immediately removes that port from the forwarding entry for the multicast group specified in the
message. Then, when the switch receive s IGMP group-specific queries for th at multicast group, it does not
forward them to that port.
On a port that has only one host attached, you can enable IGMP snooping fast-leave processing to save
bandwidth and resources. However, on a port that has multiple hosts attached, you should not enable
IGMP snooping fast-leave processing if you have enabled dropping unknown multicast data globally or
for the port. Otherwise, if a host on the port leaves a multicast group, the other hosts attached to the port
in the same multicast group cannot receive the multicast data for the group.
Enabling IGMP snooping fast-leave processing globally
Step Command
1. Enter system view.
2. Enter IGMP-snooping view.
3. Enable IGMP snooping
fast-leave processing.
system-view N/A
igmp-snooping N/A
fast-leave [ vlan vlan-list ] Disabled by default
Enabling IGMP snooping fast-leave processing on a port
Step Command
1. Enter system view.
system-view N/A
Remarks
Remarks
22
Step Command
• Enter Layer 2 Ethernet interface
view or Layer 2 aggregate
2. Enter Layer 2 Ethernet
interface view, Layer 2
aggregate interface view, or
port group view.
interface view:
interface interface-type
interface-number
• Enter port group view:
port-group manual
port-group-name
Remarks
Use either command.
3. Enable IGMP snooping
fast-leave processing.
igmp-snooping fast-leave [ vlan
vlan-list ]
Disabled by default.
Disabling a port from becoming a dynamic router port
The following problems might exist in a multicast access network:
• After receiving an IGMP general query or a PIM hello message from a connected host, a router port
becomes a dynamic router port. Before its timer expires, this dynamic router port receives all
multicast packets within the VLAN where the port belongs, and forwards them to the host, affecting
normal multicast reception of the host.
• In addition, the IGMP general query or PIM hello message that the host sends affects the multicast
routing protocol state on Layer 3 devices, such as the IGMP querier or DR election, and might
further cause network interruption.
To solve these problems, disable that router port from becoming a dynamic router port after the port
receives an IGMP general query or a PIM hello message, so as to improve network security and control
over multicast users.
To disable a port from becoming a dynamic router port:
Step Command
1. Enter system view.
system-view N/A
Remarks
• Enter Layer 2 Ethernet interface
view or Layer 2 aggregate
2. Enter Layer 2 Ethernet
interface view, Layer 2
aggregate interface view, or
port group view.
3. Disable the ports from
becoming dynamic router
port.
interface view:
interface interface-type
interface-number
• Enter port group view:
port-group manual
port-group-name
igmp-snooping router-port-deny
[ vlan vlan-list ]
Use either command.
By default, a port can become a
dynamic router port.
NOTE:
This configuration does not affect the static router port configuration.
23
Configuring IGMP snooping querier
g
Before you configure IGMP snooping querier, complete the following tasks:
• Enable IGMP snooping in the VLAN.
• Determine the IGMP general query interval.
• Determine the IGMP last-member query interval.
• Determine the maximum response delay for IGMP general queries.
• Determine the source address of IGMP general queries.
• Determine the source address of IGMP group-specific queries.
Enabling IGMP snooping querier
In an IP multicast network that runs IGMP, a multicast router or Layer 3 multicast switch sends IGMP
queries, so that all Layer 3 multicast devices can establish and maintain multicast forwarding entries, in
order to forward multicast traffic correctly at the network layer. This router or Layer 3 switch is called the
"IGMP querier."
However, a Layer 2 multicast switch does not support IGMP, and therefore cannot send general queries
by default. When you enable IGMP snooping querier on a Layer 2 switch in a VLAN where multicast
traffic is switched only at Layer 2 and no multicast routers are present, the Layer 2 switch sends IGMP
queries, so that multicast forwarding entries can be established and maintained at the data link layer.
To enable IGMP snooping querier:
Step Command Remarks
1. Enter system view.
2. Enter VLAN view.
3. Enable IGMP snooping
querier.
IMPORTANT:
system-view N/A
vlan vlan-id N/A
igmp-snooping querier
Disabled by default
In a multicast network that runs IGMP, you do not need to configure an IGMP snooping querier because
it may affect IGMP querier elections by sending IGMP general queries with a low source IP address.
Configuring parameters for IGMP queries and responses
CAUTION:
In the confi
delay for IGMP general queries. Otherwise, multicast group members might be deleted by mistake.
You can modify the IGMP general query interval based on actual condition of the network.
uration, make sure that the IGMP general query interval is larger than the maximum response
A multicast listening host starts a timer for each multicast group that it has joined when it receives an
IGMP query (general query or group-specific query). This timer is initialized to a random value in the
range of 0 to the maximum response delay advertised in the IGMP query message. When the timer value
decreases to 0, the host sends an IGMP report to the multicast group.
24
To speed up the response of hosts to IGMP queries and avoid simultaneous timer expirations causing
IGMP report traffic bursts, you must properly set the maximum response delay.
• The maximum response delay for IGMP general queries is set by the max-response-time command.
• The maximum response delay for IGMP group-specific queries equals the IGMP last-member query
interval.
Configuring the global parameters for IGMP queries and responses
Step Command
1. Enter system view.
2. Enter IGMP-snooping view.
3. Set the maximum response
delay for IGMP general
queries.
4. Set the IGMP last-member
query interval.
system-view N/A
igmp-snooping N/A
max-response-time interval 10 seconds by default
last-member-query-interval interval
Configuring the parameters for IGMP queries and responses in a VLAN
Step Command
1. Enter system view.
2. Enter VLAN view.
3. Set the interval for sending
IGMP general queries.
4. Set the maximum response
delay for IGMP general
queries.
5. Set the IGMP last-member
query interval.
system-view N/A
vlan vlan-id N/A
igmp-snooping query-interval interval 60 seconds by default
igmp-snooping max-response-time interval
igmp-snooping
last-member-query-interval interval
Remarks
1 second by default
Remarks
10 seconds by default
1 second by default
Configuring the source IP addresses for IGMP queries
After the switch receives an IGMP query whose source IP address is 0.0.0.0 on a port, it does not enlist
that port as a dynamic router port. This might prevent multicast forwarding entries from being correctly
created at the data link layer and eventually cause multicast traffic forwarding to fail. To avoid this
problem, when a Layer 2 switch acts as the IGMP snooping querier, HP recommends you to configure a
non-all-zero IP address as the source IP address of IGMP queries.
IMPORTANT:
The source address of IGMP query messages might affect the IGMP querier election within the segment
To configure the source IP addresses for IGMP queries:
Step Command
1. Enter system view.
system-view N/A
25
Remarks
Loading...