Chapter 15: Multicast Filtering
Layer 2 IGMP (Snooping and Query for IPv4)
– 521 –
acceptable), but for IGMPv3 hosts, it may include a specific address when
requested.
Only IGMPv3 hosts can request service from a specific multicast source.
When downstream hosts request service from a specific source for a
multicast service, these sources are all placed in the Include list, and traffic
is forwarded to the hosts from each of these sources. IGMPv3 hosts may
also request that service be forwarded from any source except for those
specified. In this case, traffic is filtered from sources in the Exclude list,
and forwarded from all other available sources.
N
OTE
:
When the switch is configured to use IGMPv3 snooping, the
snooping version may be downgraded to version 2 or version 1, depending
on the version of the IGMP query packets detected on each VLAN.
N
OTE
:
IGMP snooping will not function unless a multicast router port is
enabled on the switch. This can accomplished in one of two ways. A static
router port can be manually configured (see
for a Multicast Router” on page 526
). Using this method, the router port is
never timed out, and will continue to function until explicitly removed. The
other method relies on the switch to dynamically create multicast routing
ports whenever multicast routing protocol packets or IGMP query packets
are detected on a port.
N
OTE
:
A maximum of up to 1023 multicast entries can be maintained for
IGMP snooping. Once the table is full, no new entries are learned. Any
subsequent multicast traffic not found in the table is dropped if
unregistered-flooding is disabled (default behavior) and no router port is
configured in the attached VLAN, or flooded throughout the VLAN if
unregistered-flooding is enabled (see
“Configuring IGMP Snooping and
).
Static IGMP Router Interface – If IGMP snooping cannot locate the IGMP
querier, you can manually designate a known IGMP querier (i.e., a
multicast router/switch) connected over the network to an interface on
your switch (
). This interface will then join all the current
multicast groups supported by the attached router/switch to ensure that
multicast traffic is passed to all appropriate interfaces within the switch.
Static IGMP Host Interface – For multicast applications that you need to
control more carefully, you can manually assign a multicast service to
specific interfaces on the switch (
IGMP Snooping with Proxy Reporting – The switch supports last leave, and
query suppression (as defined in DSL Forum TR-101, April 2006):
•
When proxy reporting is disabled, all IGMP reports received by the
switch are forwarded natively to the upstream multicast routers.
•
Last Leave: Intercepts, absorbs and summarizes IGMP leaves coming
from IGMP hosts. IGMP leaves are relayed upstream only when
necessary, that is, when the last user leaves a multicast group.
•
Query Suppression: Intercepts and processes IGMP queries in such a
way that IGMP specific queries are never sent to client ports.
Summary of Contents for SSE-G2252
Page 42: ...44 General IP Routing on page 627...
Page 603: ...Chapter 16 IP Configuration Setting the Switch s IP Address IP Version 6 609...
Page 883: ...Chapter 24 General Security Measures Port based Traffic Segmentation 894...
Page 989: ...Chapter 30 Congestion Control Commands Automatic Traffic Control Commands 1000 Console...
Page 1007: ...Chapter 33 Address Table Commands 1019...
Page 1137: ...Chapter 38 Quality of Service Commands 1150...