Current Mld Snooping Functional Limitations; Summary - Dell PowerConnect 8024 User Configuration Manual

Hide thumbs Also See for PowerConnect 8024:
Table of Contents

Advertisement

stream even when a Report message is successfully forwarded up to the
querier. This problem is seen when multicast data forwarding behavior on
snooping switches is configured to forward registered multicast groups and
drop unregistered multicast groups.
To overcome this problem, the administrator should configure static
multicast forwarding entries on intermediate snooping switches to forward
the multicast stream to the multicast querier.
Alternatively, a better option is to reconfigure the topology to make sure
multicast streams always reach the multicast querier without getting dropped
by intermediate network elements. The Snooping on a Multicast Router
section describes this problem.

Current MLD Snooping Functional Limitations

Summary

This section outlines known functional limitations regarding MLD snooping
in its ability to support multicast in a L2/L3 mixed topology. This section is
intended to be read after the reader has acquired a thorough understanding of
the connection setup/teardown steps that snooping undergoes, as outlined in
the examples presented in the "Multicast Snooping Case Study" on page 736.
The following are known possible issues, depending upon the total number of
unique multicast groups, their sources, and their data rates:
1 As described in "Topologies Where the Multicast Source Is Not Directly
Connected to the Querier" on page 687, when operating in flood mode
(see "L2 Multicast Forwarding Modes" on page 682), multicast streams
towards a multicast (that is, PIM) router will be blocked by the multicast
server's local layer 2 switch, inhibiting the router from discovering the
stream.
688
Configuring L2 Multicast Features

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents