24.10.2014 Views

Download complete user manual (PDF). - Brocade

Download complete user manual (PDF). - Brocade

Download complete user manual (PDF). - Brocade

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

IGMP V3 3<br />

IGMPv2 SSM mapping<br />

The PIM-SSM feature requires all IGMP hosts to send IGMPv3 reports. Where you have an IGMPv2<br />

host, this can create a compatibility problem. In particular, the reports from an IGMPv2 host<br />

contain a Group Multicast Address but do not contain source addresses. The IGMPv3 reports<br />

contain both the Group Multicast Address and one or more source addresses. This feature converts<br />

IGMPv2 reports into IGMPv3 reports through use of the ip igmp ssm-map commands and a<br />

properly configured ACL.<br />

The ACL used with this feature filters for the Group Multicast Address. The ACL is then associated<br />

with one or more source addresses using the ip igmp ssm-map command. When the ip igmp<br />

ssm-map enable command is configured, IGMPv3 reports are sent for IGMPv2 hosts.<br />

The following sections describe how to configure the ACL and the ip igmp ssm-map commands to<br />

use the IGMPv2 SSM mapping feature:<br />

• Configuring an ACL for IGMPv2 SSM mapping<br />

• Configuring the IGMPv2 SSM Mapping Commands<br />

NOTE<br />

IGMPv2 SSM Mapping is not supported for IGMP static groups.<br />

Configuring an ACL for IGMPv2 SSM mapping<br />

You can use either a standard or extended ACL to identify the group multicast address you want to<br />

add source addresses to when creating a IGMPv3 report.<br />

For standard ACLs, you must create an ACL with a permit clause and the ip-source-address variable<br />

must contain the group multicast address. This can be configured directly with a subnet mask or<br />

with the host keyword in which case a subnet mask of all zeros (0.0.0.0) is implied.<br />

In the following example, access-list 20 is configured for the group multicast address: 224.1.1.0<br />

with a subnet mask of 0.0.0.255.<br />

<strong>Brocade</strong>(config)# access-list 20 permit 224.1.1.0 0.0.0.225<br />

In the following example, access-list 20 is configured for the group multicast address: 239.1.1.1 by<br />

including the host keyword.<br />

<strong>Brocade</strong>(config)# access-list 20 host 239.1.1.1<br />

For extended ACLs, the source address variable must contain either 000 or the any keyword.<br />

Additionally, the extended ACL must be configured with a permit clause and the host keyword. This<br />

can be configured directly with a subnet mask or with the host keyword in which case a subnet<br />

mask of all zeros (0.0.0.0) is implied.<br />

The ip-destination-address variable must contain the group multicast address.<br />

In the following example, access-list 100 is configured for the group multicast address: 232.1.1.1<br />

with a subnet mask of 0.0.0.255.<br />

<strong>Brocade</strong>(config)# access-list 20 permit 224.1.1.0 0.0.0.225<br />

In the following example, access-list 100 is configured for the group multicast address: 232.1.1.1.<br />

<strong>Brocade</strong>(config)# access-list 100 permit any host 232.1.1.1<br />

FastIron Ethernet Switch IP Multicast Configuration Guide 149<br />

53-1002638-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!