Enterprise 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. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Introduction to multicast ····································································································································· 1
Information transmission techniques ·········································································································· 1
Multicast features ······································································································································· 3
Common notations in multicast ·················································································································· 4
Protocols and standards ·························································································································· 17
Configuration restrictions and guidelines ································································································· 17
IGMP snooping configuration task list ·············································································································· 17
IGMP snooping configuration task list for VLANs ···················································································· 18
IGMP configuration task list for VSIs········································································································ 18
Configuring basic IGMP snooping features ····································································································· 19
Specifying an IGMP snooping version ····································································································· 20
Setting the maximum number of IGMP snooping forwarding entries ······················································· 20
Configuring static multicast MAC address entries ···················································································· 21
Setting the IGMP last member query interval ·························································································· 21
Configuring IGMP snooping port features ········································································································ 22
Setting aging timers for dynamic ports ····································································································· 22
Disabling a port from becoming a dynamic router port ············································································ 25
Configuring the IGMP snooping querier ··········································································································· 25
Configuring user port attributes ················································································································ 61
Assigning user ports to a multicast VLAN ································································································ 62
Setting the maximum number of multicast VLAN forwarding entries ······························································· 62
Displaying and maintaining multicast VLANs ··································································································· 63
Multicast VLAN configuration examples ·········································································································· 63
Sub-VLAN-based multicast VLAN configuration example ······································································· 63
Port-based multicast VLAN configuration example ·················································································· 66
Configuring multicast routing and forwarding ··············································· 70
Configuring a multicast forwarding boundary ··························································································· 76
Enabling multicast forwarding between sub-VLANs of a super VLAN ····························································· 76
Displaying and maintaining multicast routing and forwarding ·········································································· 77
Configuration examples ··································································································································· 79
Changing an RPF route ··························································································································· 79
Creating an RPF route ····························································································································· 81
Multicast forwarding over a GRE tunnel ··································································································· 82
Troubleshooting multicast routing and forwarding ··························································································· 85
Configuring an RP ·································································································································· 127
Configuring a BSR ································································································································· 129
Configuring an RP ·································································································································· 133
Configuring a BSR ································································································································· 135
Configuring the SSM group range ·········································································································· 138
Configuring common PIM features················································································································· 139
Configuration task list ····························································································································· 139
Protocols and standards ························································································································ 201
How MD VPN works······································································································································· 201
Protocols and standards ························································································································ 266
Configuration restrictions and guidelines ······································································································· 266
MLD snooping configuration task list ············································································································· 267
MLD snooping configuration task list for VLANs ···················································································· 267
MLD snooping configuration task list for VSIs························································································ 267
Configuring basic MLD snooping features ····································································································· 268
Specifying an MLD snooping version ····································································································· 269
Setting the maximum number of MLD snooping forwarding entries ······················································ 270
Configuring static IPv6 multicast MAC address entries ········································································· 270
Setting the MLD last listener query interval ···························································································· 271
Configuring MLD snooping port features ······································································································· 271
Setting aging timers for dynamic ports ··································································································· 272
Disabling a port from becoming a dynamic router port ·········································································· 274
Configuring the MLD snooping querier ·········································································································· 275
Configuring user port attributes ·············································································································· 311
Assigning user ports to an IPv6 multicast VLAN ···················································································· 312
Setting the maximum number of IPv6 multicast VLAN forwarding entries ····················································· 312
Displaying and maintaining IPv6 multicast VLANs························································································· 313
IPv6 multicast VLAN configuration examples ································································································ 313
Sub-VLAN-based IPv6 multicast VLAN configuration example ····························································· 313
Configuring an IPv6 multicast forwarding boundary··············································································· 323
Enabling IPv6 multicast forwarding between sub-VLANs of a super VLAN ··········································· 324
Displaying and maintaining IPv6 multicast routing and forwarding ································································ 324
IPv6 multicast routing and forwarding configuration example ········································································ 326
Configuring an RP ·································································································································· 369
Configuring a BSR ································································································································· 371
Configuring an RP ·································································································································· 375
Configuring a BSR ································································································································· 377
Configuring IPv6 PIM-SSM ···························································································································· 379
IPv6 PIM-SSM configuration task list ····································································································· 379
Configuring the IPv6 SSM group range ································································································· 380
Configuring common IPv6 PIM features ········································································································ 381
Configuration task list ····························································································································· 381
Remote support ······································································································································ 411
Index ·········································································································· 413
viii
Multicast overview
Source
Receiver
Receiver
Receiver
Host A
Host B
Host C
Host D
Host E
Packets for Host B
Packets for Host D
Packets for Host E
IP network
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 bandwidth-critical and
time-critical information services. These services include live webcasting, Web TV , distance learning,
telemedicine, Web radio, and real-time video conferencing.
Information transmission techniques
The information transmission techniques include unicast, broadcast, and multicast.
Unicast
In unicast transmis sion, the information sourc e must send a se parate copy of inform ation to each
host that needs the inf ormation.
Figure 1 Unicast transmission
In Figure 1, 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.
In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts
that need the information. I f a large number of hosts need t he information, the inf ormation source
must send a separate copy of the same inform ation 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.
1
Broadcast
Source
Receiver
Receiver
Receiver
Host A
Host B
Host C
Host D
Host E
Packets for all hosts
A network segment
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, 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.
Multicast provides point-to-m ultipoint data transmissions with the minimum networ k consumption.
When some hosts on the n etwork need multicast inf ormation, the inform ation 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
•
•
•
•
•
•
Source
Receiver
Receiver
Receiver
Host A
Host B
Host C
Host D
Host E
Packets for the multicast group
IP network
The multicast source s ends only one copy of the inf ormation to a m ulticast group. Host B, Hos t D,
and Host E, which are information receivers, 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—Multicast data is replicated and distributed until it flows to the
farthest-possible node from the source. The increase of receiver hosts will not remarkably
increase the load of the source or the usage of network resources.
Advantages over broadcast—Multicast data is sent only to the receivers that need it. This
saves network bandwidth and enhances network security. In addition, multicast data is not
confined to the same subnet.
Multicast features
A multicast group is a multicast receiver set identified by an IP multicast address. Hosts must
join a multicast group to become members of the multicast group before they receive the
multicast data addressed to that multicast group. Typically, a multicast source does not need to
join a multicast group.
A multicast source is an information sender. It can send data to multiple multicast groups at the
same time. Multiple multicast sources can send data to the same multicast group at the same
time.
The group memberships are dynamic. Hosts can join or leave multicast groups at any time.
Multicast groups are not subject to geographic restrictions.
Multicast routers or Layer 3 multicast devices are routers or Layer 3 switches that support Layer
3 multicast. They provide multicast routing and manage multicast group memberships on stub
subnets with attached grou p members. A multicast router itself can be a multicast group
member.
For a better understandi ng of the m ulticas t c onc ep t, you can compare multic ast tr ans mission to the
transmission of TV programs.
3
Table 1 Comparing TV program transmission and multicast transmissio n
TV program transmission
Multicast 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 on the channel.
The user turns off the TV set or tunes to another
channel.
A multicast source sends multicast data to a multicast
group.
The receiver starts to receive the multicast data sent by
the source to the multicast group.
The receiver leaves the multicast group or joins another
group.
Common notations in m ulticast
The following notations are commonly used in multicast transmission:
(*, G)—Rendezvous point tree (RPT), or a multicast packet that any multicast source sends to
multicast group G. The asterisk (*) represents any multicast source, and "G" represents a
specific multicast group.
(S, G)—Shortest path tree (SPT), or a multicast packet that multicast source "S" sends to
multicast group "G." "S" represents a specific multicast source, and "G" represents a specific
multicast group.
For more inf ormation about the c oncepts RPT and SPT, see "Configuring PIM" and "Configuring
IPv6 PIM."
Multicast benefits and applications
Multicast benefits
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
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
Multicast models
Based on how th e receivers treat th e multicast sources, the multicast m odels include any-source
multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM).
ASM model
In the ASM model, any multicast sources can send infor mation to a multicast gr o up. R eceivers can
join a multicast group and get multicast inform ation addressed to that multicast group from any
4
multicast sources. In this m odel, receivers do not know the positions of the multicast sources in
•
•
•
•
•
•
•
•
•
Address block
Description
maintenance, and so on. Table 3 lists com mon per mane nt
advance.
SFM model
The SFM model is deri ved from the ASM model. To a multicast source, the two models appear to
have the same multicast membership architecture.
The SFM model func tionall y extends t he ASM model. The upper-layer software c hecks the source
address of received multicast pack ets and perm its or d enies m ulticast t raffic from specific sources.
The receivers obtain the multicast data from only part of the multicast sources. To a receiver,
multicast sources are not all valid, but are filtered.
SSM model
The SSM model provides a transmission service that enables multicast receivers to specify the
multicast sources in which t he y are interes ted.
In the SSM model, receivers have already determined the locations of the multicast sources. This is
the main difference between the SSM model and the ASM model. In addition, the SSM model uses a
different multicast address r ange than the ASM/SFM model. Dedic ated multicast forwarding paths
are established between receivers and the specified multicast sources.
Multicast architecture
IP multicast addresses the following issues:
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 is the information 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.
Multicast addresses
IP multicast addresses
IPv4 multicast addresses:
IANA assigned the Class D address block (224.0.0.0 to 239.255.255.255) to IPv4 multicast.
Table 2 Class D IP address blocks and description
224.0.0.0 to 224.0.0.255
Reserved permanent group addresses. The IP address
224.0.0.0 is reserved. Other IP addre sses can be use d by
routing protocols and for topology searching, protocol
5
Address block
Description
group addresses. A packet destined for an address in this
block will not be forw arded b eyond the l ocal subnet r egard les s
224.0.1.0 to 238.255.255.255
NOTE:
Glop is a mechanism for assigning multicast addresses between different ASs. By filling an AS
number into the middle two bytes of 233.0.0.0, you get 255 multicast addresses for that AS. For
more information, see RFC 2770.
Address
Description
•
239.0.0.0 to 239.255.255.255
of the 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.
• 233.0.0.0/8—Glop group addr esses.
Administratively scoped multicast addresses. These
addresses are considered locally unique rather than global ly
unique. You can reuse them in domains administered by
different organizations without causing conflicts. For more
information, see RFC 2365.
Table 3 Common permanent multicast group addresses
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 DVMRP routers.
224.0.0.5 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 RIPv2 routers.
224.0.0.11 Mobile agents.
224.0.0.12 DHCP server/relay agent.
224.0.0.13 All Protocol Independent Multicast (PIM) routers.
224.0.0.14 RSVP encapsulation.
224.0.0.15 All Core-Based Tree (CBT) routers.
224.0.0.16 Designated SBM.
224.0.0.17 All SBMs.
224.0.0.18 VRRP.
IPv6 multicast addresses:
6
Figure 4 IPv6 multicast format
Bit
Description
Value
Meaning
Group ID (112 bits)
0xFF
Flags
Scope
07111531
0
R
P
T
The following describes the fields of an IPv6 multicast address:
0xFF—The most significant eight bits are 11111111.
Flags—The Flags field contains four bits.
Figure 5 Flags field format
Table 4 Flags field description
0 Reserved, set to 0.
•When set to 0, this address is an IPv6 multicast
address without an embedded RP address.
R
•When set to 1, 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, this address is an IPv6 multicast
address not based on a unicast prefix.
P
•When set to 1, this address is an IPv6 multicast
address based on a un icast p refix . (The T bit must a lso
be set to 1.)
•When set to 0, this address is an IPv6 multicast
T
address permanently-assigned by IANA.
•When set to 1, this address is a transient or
dynamically assigned IPv6 multicast address.
Scope—The Scope field contains four bits, which represent the scope of the IPv6
internetwork for which the multicast traffic is intended.
Table 5 Values of the Scope field
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.
7
•
•
•
XXXX X
XXXX XXXX
XXXX XXXX
XXXX XXXX
1110 XXXX
0XXX XXXX
XXXX XXXX
XXXX XXXX
0000 0001
0000 0000
0101 1110
32-bit IPv4 address
48-bit MAC address
5 bits lost
25
-
bit MAC address prefix
…
23 bits
mapped
…
FF1E00000000000000000000F30E0101
0101aF30E
48-bit MAC address
3333
32 bits
mapped
128-bit IPv6 address
……
16-bit MAC
address prefix
Group ID—The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast
group in the scope that the Scope field defines.
Ethernet multicast MAC addresses
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 an IPv4 multicast
address.
Table 6 IPv4-to-MAC address mapping
The most significant four bits of an IPv4 multicast address are fixed at 1110. In an IPv4-to-MAC
address mapping, five bits of the IPv4 multicast address are lost. As a result, 32 IPv4 multicast
addresses are mapped to the same IPv4 multicast MAC address. A device might rec eive
unwanted multicast data at Layer 2 processing, which needs to be filtered by the upper layer.
IPv6 multicast MAC addresses:
As defined by IANA, the most significant 16 bits of an IPv6 multicast MAC address are 0x3333.
The least significant 32 bits are mapped from the least significant 32 bits of an IPv6 multicast
address. Therefore, the problem of duplicate IPv6-to-MAC address mapping also arises like
IPv4-to-MAC address mapping.
Table 7 IPv6-to-MAC address mapping
Multicast protoc ol s
Multicast protocols include the following categories:
Layer 3 and Layer 2 multicast protocols:
Layer 3 multicast refers to IP multicast operating at the network layer.
Layer 2 multicast refers to IP multicast operating at the data link layer.
This section provides o nly general descriptions a bout applications and f unc t ions 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 pro tocols include multicast group managem ent protocols and multicast routing
protocols.
Figure 6 Positions of Layer 3 multicast protocols
Multicast group management protocols:
Multicast routing protocols:
Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) protocol
are multicast group management protocols. Typically, they run between hosts and Layer 3
multicast devices that directly connect to the hosts to establish and maintain multicast group
memberships.
A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain
multicast routes and correctly and efficiently forward multicast packets. Multicast routes
constitute loop-free data transmission paths (also known as multicast distribution trees) from a
data source to multiple receivers.
In the ASM model, multicast routes include intra-domain routes and inter-domain routes.
distribution trees within an AS to deliver multicast data to receivers. Among a variety of
mature intra-domain multicast routing protocols, 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 delivering multicast information
between two ASs. So far, mature solutions include Multicast Source Discovery Protocol
(MSDP) and MBGP. MSDP propagates multicast source information among different ASs.
9
MBGP is an extension of the MP-BGP for exchanging multicast routing information among
•
•
•
IPv4/
IPv6 multicast packets (S1, G1)
IPv4/IPv6 multicast packets (S2, G2)
Source 1
Source 2
Receiver
IGMP Snooping
/MLD Snooping
ReceiverReceiver
Multicast VLAN
/IPv6 Multicast VLAN
PIM Snooping
/
IPv6 PIM Snooping
different ASs.
For the SSM model, multicast routes are not divided into intra-domain routes and inter-domain
routes. Because receivers know the positions of the multicast sources, channels established
through PIM-SM are sufficient for the transpor t 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 7 Positions of Layer 2 multicast pro to cols
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. This effectively
controls the flooding of multicast data in Layer 2 networks.
PIM snooping and IPv6 PIM snooping:
PIM snooping and IPv6 PIM snooping run on Layer 2 devices. They work with IGMP snooping
or MLD snooping to analyze received PIM messages. Then, they add the ports that are
interested in specific multicast data to a PIM snooping routing entry or IPv6 PIM snooping
routing entry. In this way, multicast data can be forwarded to only the ports that are interested in
the data.
Multicast VLAN and IPv6 multicast VLAN:
Multicast VLAN or IPv6 multicast VLAN runs on a Layer 2 device in a multicast network where
multicast receivers for the same group exist in different VLANs. With these protocols, 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 method avoids waste of network bandwidth and extra burden
on the Layer 3 device.
Multicast packet forwarding mechanism
In a multicast model, receiver hosts of a multicast group are usually located at different areas on the
network. They are ide ntified by the same m ulticast group address . To deliver multicast packets to
these receivers, a multicast source encapsulates the multicast data in an IP packet with the multicast
group address as the destination address. Multicast routers on the forwarding paths forward
10
multicast packets that an incoming interface receives through multiple outgoing interfaces.
•
•
•
•
VPN A
VPN A
VPN A
VPN BVPN B
Public network
P
PE 1
PE
2
PE 3
CE b3
CE a2
CE a3
CE b
1
CE a
1
CE b2
Compared to a unicast model, a multicast model is more complex in the following aspects:
To ensure multicast packet transmission on the network, different routing tables are used to
guide multicast forwarding. These routing tables include unicast routing tables, routing tables
for multicast (for example, the MBGP routing table), and static multicast routing tables.
T o process the same multicast information from different peers received on different interfaces,
the multicast device performs an RPF check on each multicast packet. The RPF check result
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.
For more information about the RPF mechanism, see "Configuring multicast routing and
forwarding" and "Configuring IPv6 multicast routing and forwarding."
Multicast support for VPNs
Multicast support for VPNs refers to multicast applied in VPNs.
Introduction to VPN instances
VPNs are isolated from one another and from the public network. As shown in Figure 8, VPN A and
VPN B separately access the public network through PE devices.
Figure 8 VPN networking diagram
The P device belongs to the public network. The CE devices belong to their respective VPNs.
Each CE device serves its own VPN and maintains only one set of forwarding mechanisms.
The PE devices connect to the public network and the VPNs. Each PE device must strictly
distinguish the information for different networks, and maintain a separate forwarding
mechanism for each network. On a PE device, a set of software and hardware that serve the
same network forms an instance. Multiple instances can exist on the same PE device, and an
instance can reside on different PE devices. On a PE device, the instance for the public network
is called the public network instance, and those for VPNs are called VPN instances.
11
Multicast application in VPNs
•
•
•
A PE device that supports multicast for VPNs does the following operations:
Maintains an independent set of multicast forwarding mechanisms for each VPN, including the
multicast protocols, PIM neighbor information, and multicast routing table. In a VPN, the device
forwards multicast data based on the forwarding table or routing table for that VPN.
Implements the isolation between different VPNs.Implements information exchange and data conversion between the public network and VPN
instances.
For example, as shown in Figure 8, a multicast source in VPN A sends multicast data to a multicast
group. Only receivers t hat belong t o both t he multicas t group and VPN A can receive the m ulticast
data. The multicast data is multicast both in VPN A and on the public network.
12
Configuring IGMP snooping
Multicast packet transmission
without IGMP snooping
Source
Multicast router
Host A
Receiver
Host B
Host C
Receiver
Multicast packets
Layer 2
switch
Multicast packet transmission
when IGMP
snooping runs
Source
Multicast router
Host A
Receiver
Host B
Host C
Receiver
Layer 2 switch
Overview
IGMP snooping runs on a Layer 2 device as a multicast constraining mechanism to improve
multicast forwarding efficiency. It creates La yer 2 multicast forwarding e ntries from IGMP packets
that are exchanged between the hosts and the router.
As shown in Figure 9, when IGMP snooping is not enabled, the Layer 2 switch floods multicast
packets to all hosts in a VLAN or VSI. When IGMP snooping is enabled, the Layer 2 switch forwards
multicast packets of known multicast groups to only the receivers.
Figure 9 Multicast packet transmission without and with IGMP snooping
IGMP snooping ports
As shown in Figure 10, IGMP snooping runs on Switch A and Switch B, and Host A and Host C are
receivers in a multicast group. IGMP snooping ports are divided into member ports and router ports.
13
Figure 10 IGMP snooping ports
•
•
•
•
Router ASwitch A
Switch B
GE1/0/1GE1/0/2
GE1/0/3
GE
1/
0/
1
GE1
/0/2
Receiver
Receiver
Host A
Host B
Host C
Host D
Source
Multicast packets
Router port
Member port
Router ports
On an IGMP snooping La yer 2 d evice, t he por ts to ward La yer 3 m ulticast d evices are c alled r outer
ports. In Figure 10, GigabitEth ernet 1/0/1 of Switch A and GigabitEthernet 1/0/1 of Switc h B are
router ports.
Router ports contain the following types:
Dynamic router port—When a port receives an IGMP general query whose source address is
not 0.0.0.0 or receives a PIM hello message, the port is added into the dynamic router port list.
At the same time, an aging timer is started for the port. If the port receives either of the
messages before the timer expires, the timer is reset. If the port does not receive either of the
messages when the timer expires, the port is removed from the dynamic router port list.
Static router port—When a port is statically configured as a router port, it is added into the
static router port list. The static router port does not age out, and it can be deleted only
manually.
Do not confuse th e "router port" i n IGMP snoop ing wit h the "rout ed inter face" co mmonl y known as
the "Layer 3 interface." The router port in IGMP snooping is a Layer 2 interface.
Member ports
On an IGMP snooping Layer 2 device, the ports tow ard rece iver h osts are c alled m em ber ports . In
Figure 10, GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 of Switch A and GigabitEthernet 1/0/2 of
Switch B are member ports.
Member ports contain the following types:
Dynamic member port—When a port receives an IGMP report, it is added to the associated
dynamic IGMP snooping forwarding entry as an outgoing interface. At the same time, an aging
timer is started for the port. If the port receives an IGMP report before the timer expires, the
timer is reset. If the port does not receive an IGMP report when the timer expires, the port is
removed from the associated dynamic forwarding entry.
Static member port—When a port is statically configured as a member port, it is added to the
associated static IGMP snooping forwarding entry as an outgoing interface. The static member
port does not age out, and it can be deleted only manually.
Unless otherwise spec if ied, router ports and member ports in this document include both static and
dynamic router ports and member ports.
14
How IGMP snooping works
•
•
•
•
•
•
•
The ports in this section are dynamic ports. For information about how to configure and remove static
ports, see "Configuring static ports."
IGMP messages types include general query, IGMP report, and leave message. An IGMP
snooping-enabled Layer 2 device performs differently depending on the message types.
General query
The IG MP querier periodically sends IGM P general queries to all hosts and routers on th e local
subnet to check for the existence of multicast group members.
After receiving an IGMP general query , the Layer 2 device forwards the query to all ports in the VLAN
or VSI except the receiving port. The Layer 2 device also performs one of the following actions:
If the receiving port is a dynamic router port in the dynamic router port list, the Layer 2 device
restarts the aging timer for the port.
If the receiving port does not exist in the dynamic router port list, the Layer 2 device adds the
port to the dynamic router port list. It also starts an aging timer for the port.
IGMP report
A host sends an IGMP report to the IGMP querier for the following purposes:
Responds to queries if the host is a multicast group member.Applies for a multicast group membership.
After receiving an IGM P report from a host, the L ayer 2 device forw ards the report throu gh all the
router ports in the VL AN or VSI. It also resol ves the address of the r eported multicast gr oup, and
looks up the forwarding table for a matching entry as follows:
If no match is found, the Layer 2 device creates a forwarding entry with the receiving port as an
outgoing interface. It also marks the receiving port as a dynamic member port and starts an
aging timer for the port.
If a match is found but the matching forwarding entry does not contain the receiving port, the
Layer 2 device adds the receiving port to the outgoing interface list. It also marks the receiving
port as a dynamic member port and starts an aging timer for the port.
If a match is found and the matching forwarding entry contains the receiving port, the Layer 2
device restarts the aging timer for the port.
In an application with a group policy configured on an IGMP snooping-enabled Layer 2 device, when
a user requests a m ulticast program, the us er's host initiates an IG MP report. After receiving this
report, the Layer 2 device resolves the multicast group address in the rep ort and performs ACL
filtering on the report. If the report passes ACL filtering, the Layer 2 device creates an IGMP
snooping forwarding entry for the multicast group with the receiving port as an outgoing interface. If
the report does not pass ACL filtering, the Layer 2 device drops this report. The multicast data for the
multicast group is not sent to this port, and the user cannot re trie ve the progr am.
A Layer 2 device does not forward an IGMP report thr ough a non-router p ort because of the host
IGMP report suppression mechanism. For more information about the IGMP report suppression
mechanism, see "Configuring IGMP."
Leave message
An IGMPv1 receiver host does not send any leave messages when it leaves a multicast group. The
Layer 2 device cannot imm ediate ly update the s tatus of the por t that conn ects to the rec eiver host.
The Layer 2 device does not remove the port from the outgoing interface list in the associated
forwarding entry until the aging time for the group expires.
An IGMPv2 or IGMPv3 host sends an IGMP leave message when it leaves a multicast group.
When the Layer 2 device receives an IGMP leave message on a dynamic member port, the Layer 2
device first examines whether a forwarding entry matches the group address in the message.
15
•
•
•
•
•
•
Host A
Receiver
Host B
Host C
Receiver
IGMP Querier
Router A
Proxy
Switch A
Query from Router A
Report from Switch A
Query from Switch A
Report from Host
IP network
If no match is found, the Layer 2 device discards the IGMP leave message. If a match is found but the receiving port is not an outgoing interface in the forwarding entry , the
Layer 2 device discards the IGMP leave message.
If a match is found and the receiving port is not the only outgoing interface in the forwarding
entry, the Layer 2 device performs the following actions:
Discards the IGMP leave message.
Sends an IGMP group-specific query to identify whether the group has active receivers
attached to the receiving port.
Sets the aging timer for the receiving port to twice the IGMP last member query interval.
If a match is found and the receiving port is the only outgoing interface in the forwarding entry,
the Layer 2 device performs the following actions:
Forwards the IGMP leave message to all router ports in the VLAN or VSI.
Sends an IGMP group-specific query to identify whether the group has active receivers
attached to the receiving port.
Sets the aging timer for the receiving port to twice the IGMP last member query interval.
After receiving the IGMP leave mes sage on a port, the IGMP querier resol ves the multicast group
address in the message. Then, it sends an IGMP group-specific query to the multicast group through
the receiving port.
After receiving the IGM P group-specific query, the Layer 2 device f orwards the query through all
router ports and mem ber ports of the group in the VLAN or V SI. Then, it waits for the respon ding
IGMP report from the directly connected hosts. For the dynamic member port that received the leave
message, the Layer 2 device also performs one of the following actions:
If the port receives an IGMP report before the aging timer expires, the Layer 2 device resets the
aging timer.
If the port does not receive an IGMP report when the aging timer expires, the Layer 2 device
removes the port from the forwarding entry for the multicast group.
IGMP snooping proxying
As shown in Figure 11, to reduce the number of IGMP reports and leave messages received by the
upstream device, you can enable IGM P snooping prox ying on the edge device . The edge device
then acts as a host to send IGMP reports and leave messages to Router A.
An edge device enabled with IGMP snooping proxying does not support the host IGMP report
suppression mechanism. For more information about the IGMP report suppression mechanism, see
"Configuring IGMP."
Figure 11 IGMP snooping proxying
16
•
•
•
•
•
•
•
The IGMP snooping proxy device processes different IGMP messages as follows:
General query.
After receiving an IGMP general query, the device forwards the query to all ports in the VLAN
except the receiving port. The device also generates an IGMP report based on the local
membership information and sends the report to all router ports.
Group-specific query or group-and-source-specific query.
After receiving an IGMP group-specific query or group-and-source-specific query, the device
forwards the query to all router ports in the VLAN except the receiving port. If the forwarding
entry has a member port, the device sends a report to all router ports in the VLAN.
Report.
After receiving an IGMP report from a host, the devic e looks up the forwarding table for a
matching entry as follows:
If a match is found and the matching forwarding entry contains the receiving port, the device
resets the aging timer for the port.
If a match is found but the matching forwarding entry does not contain the receiving port, the
device adds the receiving port to the outg oin g interface list. It also marks the receiving port
as a dynamic member port and starts an aging timer for the port.
If no match is found, the device creates a forwarding entry with the receiving port as an
outgoing interface. It also marks the receiving port as a dynamic member port and starts an
aging timer for the port. Then it sends the report to all router ports.
Leave message.
After receiving an IGMP leave message on a port, the device sends an IGMP group-specific
query through the receiving port. The device sends the IGMP leave message to all router ports
only when the last member port is removed from the forwarding entry.
Protocols and standards
RFC 4541, Considerat ions for Internet G ro up Man agement Protoc ol ( IG MP) and Multicast Lis tener Discovery (MLD) Snooping Switches
Configuration restrictions and guidelines
When you configure IGMP snooping, follow these restrictions and guidelines:
If you change the VPN instance bound to the VLAN interface of a VLAN, Layer 2 multicast traffic
in the VLAN is interrupted. To allow new IGMP snooping forwarding entries to be created,
execute the reset igmp-snooping group command.
For IGMP reports received from secondary VLANs, the relevant IGMP snooping forwarding
entries are maintained by the primary VLAN. Therefore, you need to enable IGMP snooping
only for the primary VLAN. The IGMP snooping configuration made in secondary VLANs does
not take effect. For more information about primary VLANs and secondary VLANs, see Layer 2—LAN Switching Configuration Guide.
The IGMP snooping configurations made on Layer 2 aggregate interfaces do not interfere with
the configurations made on member ports. In addition, the configurations made on Layer 2
aggregate interfaces do not take part in aggregation calculations. The configuration made on a
member port of the aggregate group takes effect after the port leaves the aggregate group.
IGMP snooping configuration task list
You can configure IGMP snooping for VLANs or VSIs.
17
IGMP snooping configuration t as k list for VLANs
Tasks at a glance
Tasks at a glance
Configuring basic IGMP snooping features:
• (Required.) Enabling IGMP snooping
• (Optional.) Specifying an IGMP snooping version
• (Optional.) Setting the maximum number of IGMP snooping forwarding entries
• (Optional.) Configuring static multicast MAC address entries
• (Optional.) Setting the IGMP last member query interval
Configuring IGMP snooping port features:
• (Optional.) Setting aging timers for dynamic ports
• (Optional.) Configuring static ports
• (Optional.) Configuring a port as a simulated member host
• (Optional.) Enabling fast-leave processing
• (Optional.) Disabling a port from becoming a dynamic router port
Configuring the IGMP snooping querier:
• (Optional.) Enabling the IGMP snooping querier
• (Optional.) Configuring parameters for IGMP general queries and responses
(Optional.) Enabling IGMP snooping proxying
Configuring parameters for IGMP messages:
• (Optional.) Configuring the source IP address for IGMP messages
• (Optional.) Setting the 802.1p priority for IGMP messages
Configuring IGMP snooping policies:
• (Optional.) Configuring a multi cast group policy
• (Optional.) Enabling multicast source port filtering
• (Optional.) Enabling dropp ing unknown multicast data
• (Optional.) Enabling IGMP report suppression
• (Optional.) Setting the maximum number of multicast groups on a port
• (Optional.) Enabling mul tic ast group r epl ace men t
• (Optional.) Enabling host tracking
IGMP configuration task list for VSIs
Configuring basic IGMP snooping features:
• (Required.) Enabling IGMP snooping
• (Optional.) Specifying an IGMP snooping version
• (Optional.) Setting the maximum number of IGMP snooping forwarding entries
• (Optional.) Setting the IGMP last member query interval
Configuring IGMP snooping port features:
•(Optional.) Setting aging timers for dynamic ports
Configuring the IGMP snooping querier:
• (Optional.) Enabling the IGMP snooping querier
• (Optional.) Configuring parameters for IGMP general queries and responses
Configuring parameters for IGMP messages:
•(Optional.) Configuring the source IP address for IGMP messages
18
Tasks at a glance
•(Optional.) Setting the 802.1p priority for IGMP messages
Configuring IGMP snooping policies:
•
•
•
•
•
•
•
Step
Command
Remarks
Step
Command
Remarks
5.
By default, IGMP snooping is
• (Optional.) Enabling dropp ing unknown multicast data
• (Optional.) Enabling mul tic ast group r epl ace men t
Configuring basic IGMP snooping features
Before you configure basic IGMP snooping features, complete the following tasks:
Configure VLANs or VSIs.
Determine the IGMP snooping version.
Determine the maximum number of IGMP snooping forwarding entries.
Determine the IGMP last member query interval.
Enabling IGMP s nooping
When you enable IGMP snooping, follow these restrictions and guidelines:
You must enable IGMP snooping globally before you enable it for a VLAN or VSI. IGMP snooping configuration made in VLAN or VSI view takes effect only on the member ports
in that VLAN or VSI.
You can enable IGMP snooping for the specified VLANs in IGMP-snoopi ng vi e w, for a VSI in
VSI view, or for a VLAN in VLAN view. For a VLAN, the configuration in VLAN view has the
same priority as the configuration in IGMP-snooping view, and the most recent configuration
takes effect.
Enabling IGMP snooping in IGMP-snooping view
1. Enter system view.
2. Enable IGMP snooping
globally and enter
IGMP-snooping view.
3. Enable IGMP snooping for
the specified VLANs.
system-view
igmp-snooping
enable vlan
vlan-list
Enabling IGMP snooping in VLAN or VSI view
1. Enter system view.
2. Enable IGMP snooping
globally and enter
IGMP-snooping view.
3. Return to system view.
4. Enter VLAN view or VSI
view.
system-view
igmp-snooping
quit
•Enter VLAN view:
vlan vlan-id
• Enter VSI view:
vsivsi-name
N/A
By default, IGMP snooping is
globally disabled.
By default, IGMP snooping is
disabled for a VLAN.
N/A
By default, IGMP snooping is
globally disabled.
N/A
N/A
Enable IGMP snooping for
igmp-snooping enable
19
Step
Command
Remarks
the VLAN or VSI.
disabled in a VLAN or VSI.
•
•
•
•
•
Step
Command
Remarks
Step
Command
Remarks
Specifying an IGMP snooping version
Different IGMP snooping versions process different versions of IGMP messages.
IGMPv2 snooping processes IGMPv1 and IGMPv2 messages, but it floods IGMPv3 messages
in the VLAN instead of processing them.
IGMPv3 snooping processes IGMPv1, IGMPv2, and IGMPv3 messages.
If you change IGMPv3 snooping to IGMPv2 snooping, the device performs the following actions:
Clears all IGMP snooping forwarding entries that are dynamicall y added.
Keeps static IGMPv3 snooping forwarding entries (*, G).
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 IGMP snooping forwarding entries, see "Configuring static ports."
Y ou can specify the version for the specified VLANs in IGMP-snooping view, for a VSI in VSI view, or
for a VLAN in VLAN v ie w. For a VLAN, the c onf igura ti on i n V LA N v ie w has t he same priority as the
configuration in IGMP-snooping view, and the most recent configuration takes effect.
Specifying an IGMP snooping version in IGMP-snooping view
1. Enter system view.
2. Enable IGMP snooping
globally and enter
IGMP-snooping view.
3. Specify an IGMP snooping
version for the specified
VLANs.
system-view
igmp-snooping
version
vlan-list
version-number
vlan
N/A
N/A
The default setting is 2.
Specifying an IGMP snooping version in VLAN or VSI view
1. Enter system view.
2. Enter VLAN view or VSI view.
3. Specify an IGMP snooping
version for the VLAN or VSI.
system-view
•Enter VLAN view:
vlan vlan-id
• Enter VSI view:
vsi vsi-name
igmp-snooping version
version-number
N/A
N/A
The default setting is 2.
Setting the maximum number of IGMP s noopi ng forwarding
entries
You can modify the maximum number of IGMP snooping forwarding entries, including dynamic
entries and static entr ies. W hen the number of forwardin g entries on the de vice reaches the upper
limit, the device does not automatically remove any existing entries. To allow new entries to be
created, remove some entries manually.
20
Loading...
+ 431 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.