Configuring multicast boundaries
•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
Configuring multicast boundaries
To define boundaries for PIM enabled interfaces, enter a commands such as the following.
device(config)# interface ve 40
Syntax: [no] ip multicast-boundary acl-spec
Use the
Use the no ip multicast boundary command to remove the boundary on a PIM enabled interface.
The ACL, MyBrocadeAccessList can be configured using standard ACL syntax. Some examples of how ACLs can be used to filter multicast traffic are as follows:
Standard ACL to permit multicast traffic
To permit multicast traffic for group 225.1.0.2 and deny all other traffic, enter the following command.
device(config)#
Extended ACL to deny multicast traffic
To deny multicast data traffic from group 225.1.0.1 and permit all other traffic, enter the following command.
device(config)#
Extended ACL to permit multicast traffic
To permit multicast data traffic from source 97.1.1.50 for group 225.1.0.1 and deny all other traffic, enter the following commands:
Device(config)#
Device(config)#
Displaying multicast boundaries
To display multicast boundary information, enter the show ip pim interface command.
device# show ip pim interface ethernet 1/1/7 |
|
| |||
Flags | : SM | - Sparse Mode v2, DM - Dense Mode v2, P - Passive Mode | |||
+ |
| TTLMulticast VRF | |||
InterfaceLocal | ModeSt Designated Router | ||||
DR | Override |
|
|
|
|
80 | FastIron Ethernet Switch IP Multicast Configuration Guide |
|