Layer 2 multicast filters, Layer 2 multicast, Filters – Brocade BigIron RX Series Configuration Guide User Manual

Page 812: Configuration considerations, Configuring layer 2 multicast boundaries

Advertising
background image

734

BigIron RX Series Configuration Guide

53-1002484-04

Configuring IP multicast traffic reduction

24

When the device starts up, it forwards all multicast groups even though multicast traffic filters are
configured. This process continues until the device receives a group membership report. Once the
group membership report is received, the device drops all multicast packets for groups other than
the ones for which the device has received the group membership report.

To enable IP multicast filtering, enter the following command.

BigIron RX(config)# ip multicast filter

Syntax: [no] ip multicast filter

NOTE

If the “route-only” feature is enabled on a BigIron RX, PIM SM traffic snooping will not be supported.

Layer 2 multicast filters

You can define multicast boundaries on a per VLAN basis. The multicast-boundary command
allows you to configure a boundary on IGMP snooping enabled interface by defining which
multicast groups may not forward packets over a specified interface.

Configuration considerations

Only one ACL can be bound to any interface or VLAN.

If a new multicast boundary has to be applied, you must delete the old bounder first, then
apply the new ACL.

To avoid temporary loss in multicast traffic, ACLs should be configured before applying them to
multicast boundaries.

Modifying an already applied ACL will take effect immediately.

Configurations shoube be generated at the VLAN level if user has explicitly configured it,
regardless of whether it matches the global snooping configuration.

You can issue the “no multicast” command to erase all VLAN-level configuration and force the
VLAN to inherit the global configuration.

You can issue the [no] multicast active|passive command to explicitly set the VLAN-level
configuration.

NOTE

Issuing the [no] multicast active|passive command causes this configuration to always be
generated for this VLAN.

Global configurations will not affect any explicit VLAN-level configurations.

Configuring Layer 2 multicast boundaries

You can define multicast boundaries on a per VLAN basis by entering commands such as the
following.

BigIron RX(config)# vlan 100

BigIron RX(config-vlan-100)# multicast boundary MyBrocadeAccessList ethernet 3/22

Syntax: [no] multicast-boundary <acl-spec> [ ethernet <slot/port>]

Advertising