Brocade BigIron RX Series Configuration Guide - Manual (Page 733)

BigIron RX Series Configuration Guide 655
53-1002484-04
IP multicast boundaries
24
Defining the maximum number of DVMRP cache entries
The DVMRP cache system parameter defines the maximum number of repeated DVMRP traffic
being sent from the same source address and being received by the same destination address. To
define this maximum, enter a command such as the following.
BigIron RX(config)# system-max dvmrp-mcache 500
Syntax: system-max dvmrp-mcache <num>
The <num> parameter specifies the maximum number of multicast cache entries for DVMRP.
Enter a number from 128 – 2048. The default is 512.
Defining the maximum number of PIM cache entries
The PIM cache system parameter defines the maximum number of repeated PIM traffic being sent
from the same source address and being received by the same destination address. To define this
maximum, enter a command such as the following.
BigIron RX(config)# system-max pim-mcache 999
Syntax: system-max pim-mcache <num>
The <num> parameter specifies the maximum number of multicast cache entries for PIM. Enter a
number from 256 – 4096. The default is 1024.
IP multicast boundaries
The Multicast Boundary feature is designed to selectively allow or disallow multicast flows to
configured interfaces.
The ip multicast-boundary command allows you to configure a boundary on PIM enabled interface
by defining which multicast groups may not forward packets over a specified interface. This
includes incoming and outgoing packets. By default, all interfaces that are enabled for multicast
are eligible to participate in a multicast flow provided they meet the multicast routing protocol’s
criteria for participating in a flow.
Configuration considerations
• Normal ACL restrictions apply as to how many software ACLs can be created, but there are no
hardware restrictions on ACLs with this feature.
• Creation of a static IGMP client is allowed for a group on a port that may be prevented from
participation in the group on account of an ACL bound to the port’s interface. In such a
situation, the ACL would prevail and the port will not be added to the relevant entries.
• Either standard or extended ACLs can be used with the multicast boundary feature. When a
standard ACL is used, the address specified is treated as a group address and NOT a source
address.
• When a boundary is applied to an ingress interface, all packets destined to a multicast group
that is filtered out will be dropped by software. Currently, there is no support to drop such
packets in hardware.
• The ip multicast-boundary command may not stop clients from receiving multicast traffic if the
filter is applied on the egress interface up-stream from RP.