Download complete user manual (PDF). - Brocade
Download complete user manual (PDF). - Brocade
Download complete user manual (PDF). - Brocade
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
IPv6 Multicast Boundaries 4<br />
IPv6 Multicast Boundaries<br />
The Multicast Boundary feature is designed to selectively allow or disallow multicast flows to<br />
configured interfaces.<br />
The ipv6 multicast-boundary command allows you to configure a boundary on PIM enabled<br />
interface by defining which multicast groups may not forward packets over a specified interface.<br />
This includes incoming and outgoing packets. By default, all interfaces that are enabled for<br />
multicast are eligible to participate in a multicast flow provided they meet the multicast routing<br />
protocol’s criteria for participating in a flow.<br />
Configuration considerations<br />
• Only one ACL can be bound to any interface.<br />
• Normal ACL restrictions apply as to how many software ACLs can be created, but there is no<br />
hardware restrictions on ACLs with this feature.<br />
• Creation of a static MLD client is allowed for a group on a port that may be prevented from<br />
participation in the group on account of an ACL bound to the port’s interface. In such a<br />
situation, the ACL would prevail and the port will not be added to the relevant entries.<br />
• Either standard or extended ACLs can be used with the multicast boundary feature. When a<br />
standard ACL is used, the address specified is treated as a group address and NOT a source<br />
address.<br />
• When a boundary is applied to an ingress interface, all packets destined to a multicast group<br />
that is filtered out will be dropped by software. Currently, there is no support to drop such<br />
packets in hardware.<br />
• The ipv6 multicast-boundary command may not stop clients from receiving multicast traffic if<br />
the filter is applied on the egress interface up-stream from RP.<br />
Configuring multicast boundaries<br />
To define boundaries for PIM enabled interfaces, enter a commands such as the following.<br />
<strong>Brocade</strong>(config)# interface ethernet 1/2<br />
<strong>Brocade</strong>(config-if-e1000-1/2)#ipv6 multicast-boundary My<strong>Brocade</strong>AccessList<br />
Syntax: [no] ipv6 multicast-boundary acl-spec<br />
Use the acl-spec parameter to define the number or name identifying an access list that controls<br />
the range of group addresses affected by the boundary.<br />
Use the no ipv6 multicast boundary command to remove the boundary on a PIM enabled interface.<br />
The ACL, My<strong>Brocade</strong>AccessList can be configured using standard ACL syntax. Some examples of<br />
how ACLs can be used to filter multicast traffic are as follows:<br />
ACL to permit multicast traffic<br />
To permit multicast traffic for group ff1e::300 and deny all other traffic, enter the following<br />
commands.<br />
<strong>Brocade</strong>(config)# ipv6 access-list abc<br />
<strong>Brocade</strong>(config-ipv6-access-list abc)# permit ipv6 any host ff1e::300<br />
<strong>Brocade</strong>(config-ipv6-access-list abc)# deny ipv6 any any<br />
FastIron Ethernet Switch IP Multicast Configuration Guide 195<br />
53-1002638-02
Change language