Table of Contents

Related Documents

22-IGMP Configuration Examples

Title	Size	Download
22-IGMP Configuration Examples	145.03 KB


H3C S12500R Switch Router Series
IGMP Configuration Examples

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.

Introduction

This document provides IGMP configuration examples.

Prerequisites

The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

This document assumes that you have basic knowledge of IGMP.

Example: Configuring basic IGMP features

Network configuration

As shown in Figure 1:

· OSPF and PIM-DM run on the network.

· VOD streams are sent in multicast. Hosts of different organizations form stub networks N1 and N2.

· IGMPv2 runs between Device A and N1, and between the other two switches and N2. Device A acts as the IGMP querier in N1. Device B acts as the IGMP querier in N2 because it has a lower IP address.

Configure basic IGMP features on the switches to meet the following requirements:

· Hosts in N1 can join any multicast groups.

· Hosts in N2 can join only multicast group 224.1.1.1.

Figure 1 Network diagram

Analysis

To limit the multicast groups that hosts can join, create an IPv4 basic ACL and specify the multicast groups that you want the hosts to join.

Software versions used

This configuration example was created and verified on Release 3606.

Restrictions and guidelines

The protocol packets of different IGMP versions are different in structures and types. For IGMP to operate correctly, you must enable the same IGMP version for all switches on the same subnet.

You must configure the same multicast group policy for all switches on the same subnet.

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

Procedures

1. Assign an IP address and subnet mask to each interface, as shown in Figure 1. (Details not shown.)

2. Configure OSPF on the switches in the PIM-DM domain. (Details not shown.)

3. Configure Device A:

# Enable IP multicast routing.

<DeviceA> system-view

[DeviceA] multicast routing

[DeviceA-mrib] quit

# Enable IGMP on the receiver-side interface HundredGigE 1/0/1.

[DeviceA] interface hundredgige 1/0/1

[DeviceA-Hundredgige1/0/1] igmp enable

[DeviceA-Hundredgige1/0/1] quit

# Enable PIM-DM on HundredGigE 1/0/2.

[DeviceA] interface hundredgige 1/0/2

[DeviceA-Hundredgige1/0/2] pim dm

[DeviceA-Hundredgige1/0/2] quit

4. Configure Device B:

# Create ACL 2001 to permit IGMP reports for multicast group 224.1.1.1.

<DeviceB> system-view

[DeviceB] acl basic 2001

[DeviceB-acl-ipv4-basic-2001] rule permit source 224.1.1.1 0

[DeviceB-acl-ipv4-basic-2001] quit

# Enable IP multicast routing.

[DeviceB] multicast routing

[DeviceB-mrib] quit

# Enable IGMP on the receiver-side interface HundredGigE 1/0/1.

[DeviceB] interface hundredGigE 1/0/1

[DeviceB-HundredGigE1/0/1] igmp enable

# Configure a multicast group policy that uses ACL 2001.

[DeviceB-HundredGigE1/0/1] igmp group-policy 2001

[DeviceB-HundredGigE1/0/1] quit

# Enable PIM-DM on HundredGigE 1/0/2.

[DeviceB] interface hundredGigE 1/0/2

[DeviceB-HundredGigE1/0/2] pim dm

[DeviceB-HundredGigE1/0/2] quit

5. Configure Device C:

# Create ACL 2001 to permit IGMP reports for multicast group 224.1.1.1.

<DeviceC> system-view

[DeviceC] acl basic 2001

[DeviceC-acl-ipv4-basic-2001] rule permit source 224.1.1.1 0

[DeviceC-acl-ipv4-basic-2001] quit

# Enable IP multicast routing.

[DeviceC] multicast routing

[DeviceC-mrib] quit

# Enable IGMP on the receiver-side interface HundredGig E1/0/1.

[DeviceC] interface hundredGigE 1/0/1

[DeviceC-HundredGigE1/0/1] igmp enable

# Configure a multicast group policy that uses ACL 2001.

[DeviceC-HundredGigE1/0/1] igmp group-policy 2001

[DeviceC-HundredGigE1/0/1] quit

# Enable PIM-DM on HundredGigE 1/0/2.

[DeviceC] interface hundredGigE 1/0/2

[DeviceC-HundredGigE1/0/2] pim dm

[DeviceC-HundredGigE1/0/22] quit

Verifying the configuration

1. Verify that hosts in N1 can join the multicast groups 224.1.1.1 and 224.1.1.2:

# Send IGMP reports from Host A (10.110.1.10) to join the multicast groups 224.1.1.1 and 224.1.1.2. (Details not shown.)

# Display information about IGMP groups that hosts have dynamically joined on Device A.

[DeviceA] display igmp group

IGMP groups in total: 2

HundredGigE 1/0/1(10.110.1.1):

IGMP groups reported in total: 2

Group address Last reporter Uptime Expires

224.1.1.1 10.110.1.10 00:02:04 00:01:15

224.1.1.2 10.110.1.10 00:02:00 00:01:19

The output shows that Host A has joined the multicast groups 224.1.1.1 and 224.1.1.2.

2. Verify that hosts in N2 can join only multicast group 224.1.1.1:

# Send IGMP reports from Host C (10.110.2.10) to join the multicast groups 224.1.1.1 and 224.1.1.2. (Details not shown.)

# Display information about IGMP groups that hosts have dynamically joined on Device B.

[DeviceB] display igmp group

IGMP groups in total: 1

HundredGigE 1/0/1(10.110.2.1):

IGMP groups reported in total: 1

Group address Last reporter Uptime Expires

224.1.1.1 10.110.2.10 04:36:03 00:01:23

# Display information about IGMP groups that hosts have dynamically joined on Device C.

[DeviceC] display igmp group

IGMP groups in total: 1

HundredGigE 1/0/1(10.110.2.2):

IGMP groups reported in total: 1

Group address Last reporter Uptime Expires

224.1.1.1 10.110.2.10 04:21:03 00:01:13

The output shows that Device B and Device C each have IGMP information about only the multicast group, 224.1.1.1. The multicast group policy has taken effect, and hosts in N2 can join only multicast group 224.1.1.1.

Configuration files

· Device A:

interface HundredGigE1/0/1

ip address 10.110.1.1 255.255.255.0

igmp enable

interface HundredGigE1/0/2

ip address 10.111.1.1 255.255.255.0

pim dm

multicast routing

· Device B:

acl basic 2001

rule 0 permit source 224.1.1.1 0

interface HundredGigE1/0/1

ip address 10.110.2.1 255.255.255.0

igmp enable

igmp group-policy 2001

interface HundredGigE1/0/2

ip address 10.111.2.1 255.255.255.0

pim dm

multicast routing

· Device C:

acl basic 2001

rule 0 permit source 224.1.1.1 0

interface HundredGigE1/0/1

ip address 10.110.2.2 255.255.255.0

igmp enable

igmp group-policy 2001

interface HundredGigE1/0/2

ip address 10.111.3.1 255.255.255.0

pim dm

multicast routing

Example: Configuring IGMP static group members

Network configuration

As shown in Figure 2:

· OSPF and PIM-DM run on the network.

· VOD streams are sent in multicast. Hosts of different organizations form stub networks N1 and N2.

· IGMPv2 runs between Device A and N1, and between the other two switches and N2. Device A acts as the IGMP querier in N1. Device B acts as the IGMP querier in N2 because it has a lower IP address.

Configure the switches to meet the following requirements:

· Hosts in N1 can join any multicast groups, and Host A can permanently receive multicast data addressed to multicast group 224.1.1.2.

· Hosts in N2 can join only multicast group 224.1.1.1.

Figure 2 Network diagram

Analysis

For Host A to permanently receive multicast data addressed to the group 224.1.1.2, configure VLAN-interface 100 on Device A as a static member of the multicast group.

To limit the multicast groups that hosts can join, create an IPv4 basic ACL and specify the multicast groups that you want the hosts to join.

Software versions used

This configuration example was created and verified on Release 3606.

Restrictions and guidelines

The protocol packets of different IGMP versions are different in structures and types. For IGMP to operate correctly, specify the same IGMP version for all switches on the same subnet.

You must configure the same multicast group policy for all switches on the same subnet.

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

Procedures

1. Assign an IP address and subnet mask to each interface, as shown in Figure 2. (Details not shown.)

2. Configure OSPF on the switches in the PIM-DM domain. (Details not shown.)

3. Configure Device A:

# Enable IP multicast routing.

<DeviceA> system-view

[DeviceA] multicast routing

[DeviceA-mrib] quit

# Enable PIM-DM on HundredGigE 1/0/2.

[DeviceA] interface hundredgige 1/0/2

[DeviceA-HundredGigE1/0/2] pim dm

[DeviceA-HundredGigE1/0/2] quit

# Enable IGMP on the receiver-side interface HundredGigE 1/0/1.

[DeviceA] interface hundredgige 1/0/1

[DeviceA-HundredGigE1/0/1] igmp enable

# Configure VLAN-interface 100 as a static member of multicast group 224.1.1.2.

[DeviceA-HundredGigE1/0/1] igmp static-group 224.1.1.2

[DeviceA-HundredGigE1/0/1] quit

4. Configure Device B:

# Enable IP multicast routing.

<DeviceB> system-view

[DeviceB] multicast routing

[DeviceB-mrib] quit

# Enable PIM-DM on HundredGigE 1/0/2.

[DeviceB] interface hundredgige 1/0/2

[DeviceB-Hundredgige1/0/2] pim dm

[DeviceB-Hundredgige1/0/2] quit

# Create ACL 2001 to permit IGMP reports for multicast group 224.1.1.1.

[DeviceB] acl basic 2001

[DeviceB-acl-ipv4-basic-2001] rule permit source 224.1.1.1 0

[DeviceB-acl-ipv4-basic-2001] quit

# Enable IGMP on the receiver-side interface HundredGigE 1/0/1.

[DeviceB] interface hundredgige 1/0/1

[DeviceB-Hundredgige1/0/1] igmp enable

# Configure a multicast group policy that uses ACL 2001.

[DeviceB-Hundredgige1/0/1] igmp group-policy 2001

[DeviceB-Hundredgige1/0/10] quit

5. Configure Device C:

# Enable IP multicast routing.

<DeviceC> system-view

[DeviceC] multicast routing

[DeviceC-mrib] quit

# Enable PIM-DM on HundredGigE 1/0/2.

[DeviceC] interface hundredgige 1/0/2

[DeviceC-Hundredgige1/0/2] pim dm

[DeviceC-Hundredgige1/0/22] quit

# Create ACL 2001 to permit IGMP reports for multicast group 224.1.1.1.

[DeviceC] acl basic 2001

[DeviceC-acl-ipv4-basic-2001] rule permit source 224.1.1.1 0

[DeviceC-acl-ipv4-basic-2001] quit

# Enable IGMP on HundredGigE1/0/1.

[DeviceC] interface hundredgige1/0/1

[DeviceC-Hundredgige1/0/1] igmp enable

# Configure a multicast group policy that uses ACL 2001.

[DeviceC-Hundredgige1/0/1] igmp group-policy 2001

[DeviceC-Hundredgige1/0/10] quit

Verifying the configuration

1. Verify that hosts in N1 can join the multicast groups 224.1.1.1 and 224.1.1.2:

# Send IGMP reports from Host A (10.110.1.10) to join the multicast groups 224.1.1.1 and 224.1.1.2. (Details not shown.)

# Display information about IGMP groups that hosts have dynamically joined on Device A.

[DeviceA] display igmp group

IGMP groups in total: 2.

Hundredgige1/0/1(10.110.1.1):

IGMP groups reported in total: 2

Group address Last reporter Uptime Expires

224.1.1.1 10.110.1.10 00:02:04 00:01:15

224.1.1.2 10.110.1.10 00:02:00 00:01:19

The output shows that Host A has dynamically joined the multicast groups 224.1.1.1 and 224.1.1.2.

# Display information about IGMP groups that hosts have statically joined on Device A.

[DeviceA] display igmp group static

Entries in total: 1

Group address Source address Interface Expires

224.1.1.2 0.0.0.0 HGE1/0/1 Never

The output shows that Host A has statically joined multicast group 224.1.1.1 through VLAN-interface 100.

2. Verify that hosts in N2 can join only multicast group 224.1.1.1:

# Send IGMP reports from Host C (10.110.2.10) to join multicast groups 224.1.1.1 and 224.1.1.2. (Details not shown.)

# Display information about IGMP groups that hosts have dynamically joined on Device B.

[DeviceB] display igmp group

IGMP groups in total: 1

Hundredgige1/0/1(10.110.2.1):

IGMP groups reported in total: 1

Group address Last reporter Uptime Expires

224.1.1.1 10.110.2.10 04:36:03 00:01:23

# Display information about IGMP groups that hosts have dynamically joined on Device C.

[DeviceC] display igmp group

IGMP groups in total: 1

Hundredgige1/0/1(10.110.2.2):

IGMP groups reported in total: 1

Group address Last reporter Uptime Expires

224.1.1.1 10.110.2.10 04:21:03 00:01:13

The output shows that Device B and Device C each have information only about multicast group 224.1.1.1. The multicast group policy has taken effect, and hosts in N2 can join only multicast group 224.1.1.1.

Configuration files

· Device A:

interface HundredGigE1/0/1

ip address 10.111.1.1 255.255.255.0

pim dm

interface HundredGigE1/0/2

ip address 10.110.1.1 255.255.255.0

igmp enable

igmp static-group 224.1.1.2

multicast routing

· Device B:

acl basic 2001

rule 0 permit source 224.1.1.1 0

interface HundredGigE1/0/1

ip address 10.111.2.1 255.255.255.0

pim dm

interface HundredGigE1/0/2

ip address 10.110.2.1 255.255.255.0

igmp enable

igmp group-policy 2001

multicast routing

· Device C:

acl basic 2001

rule 0 permit source 224.1.1.1 0

interface HundredGigE1/0/1

ip address 10.111.3.1 255.255.255.0

pim dm

interface HundredGigE1/0/2

ip address 10.110.2.2 255.255.255.0

igmp enable

igmp group-policy 2001

multicast routing

Example: Configuring IGMP SSM mappings

Network configuration

As shown in Figure 3:

· The SSM group range for the PIM-SSM domain is 232.1.1.0/24.

· Device A and Device B in the PIM-SSM domain run IGMPv3.

· Host A in N1 and Host B in N2 run IGMPv2, and they do not support IGMPv3. The other hosts in N1 and N2 run IGMPv3.

Configure IGMP SSM mappings on Device A and Device B to meet the following requirements:

· Hosts in N1 receive multicast data only from Source 1.

· Hosts in N2 receive multicast data only from Source 2.

Figure 3 Network diagram

Software versions used

This configuration example was created and verified on Release 3606.

Restrictions and guidelines

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

Procedures

1. Assign an IP address and subnet mask to each interface, as shown in Figure 3. (Details not shown.)

2. Configure OSPF on the switches in the PIM-SSM domain. (Details not shown.)

3. Enable IP multicast routing and enable PIM-SM:

# On Device A, enable IP multicast routing, and enable PIM-SM on HundredGigE 1/0/1.

<DeviceA> system-view

[DeviceA] multicast routing

[DeviceA-mrib] quit

[DeviceA] interface hundredgige1/0/1

[DeviceA-HundredGigE1/0/1] pim sm

[DeviceA-HundredGigE1/0/1] quit

# Configure Device B in the same way Device A is configured. (Details not shown.)

# On Router C, enable IP multicast routing, and enable PIM-SM on each interface.

<DeviceC> system-view

[DeviceC] multicast routing

[DeviceC-mrib] quit

[DeviceC] interface hundredgige1/0/1

[DeviceC-Hundredgige1/0/1] pim sm

[DeviceC-Hundredgige1/0/1] quit

[DeviceC] interface hundredgige1/0/2

[DeviceC-Hundredgige1/0/2] pim sm

[DeviceC-Hundredgige1/0/2] quit

[DeviceC] interface hundredgige1/0/3

[DeviceC-Hundredgige1/0/3] pim sm

[DeviceC-Hundredgige1/0/3] quit

4. On Device C, configure VLAN-interface 200 as a C-BSR and a C-RP:

[DeviceC] pim

[DeviceC-pim] c-bsr 192.168.1.1

[DeviceC-pim] c-rp 192.168.1.1

[DeviceC-pim] quit

5. Configure IGMPv3 on the receiver-side interfaces:

# On Device A, enable IGMP, and specify IGMP version 3 on HundredGigE 1/0/2.

[DeviceA] interface hundredgige 1/0/2

[DeviceA-Hundredgige1/0/2] igmp enable

[DeviceA-Hundredgige1/0/2] igmp version 3

[DeviceA-Hundredgige1/0/2] quit

# Configure Device B in the same way Device A is configured. (Details not shown.)

6. Configure the SSM group range:

# On Device A, configure the SSM group range as 232.1.1.0/24.

[DeviceA] acl basic 2000

[DeviceA-acl-ipv4-basic-2000] rule permit source 232.1.1.0 0.0.0.255

[DeviceA-acl-ipv4-basic-2000] quit

[DeviceA] pim

[DeviceA-pim] ssm-policy 2000

[DeviceA-pim] quit

# Configure Device B and Device C in the same way Device A is configured. (Details not shown.)

7. Configure IGMP SSM mappings:

# On Device A, configure an IGMP SSM mapping with multicast source 10.110.5.100 and multicast group range 232.1.1.0/24 specified in ACL 2000.

[DeviceA] igmp

[DeviceA-igmp] ssm-mapping 10.110.5.100 2000

[DeviceA-igmp] quit

# On Device B, configure an IGMP SSM mapping with multicast source 10.110.5.101 and multicast group range 232.1.1.0/24 specified in ACL 2000.

[DeviceB] igmp

[DeviceB-igmp] ssm-mapping 10.110.5.101 2000

[DeviceB-igmp] quit

Verifying the configuration

# Send IGMPv2 reports from Host A and Host C to join multicast group 232.1.1.1. (Details not shown.)

# Send multicast data from Source 1 and Source 2 to multicast group 232.1.1.1. (Details not shown.)

# Display IGMP SSM mappings for multicast group 232.1.1.1 on Device A.

[DeviceA] display igmp ssm-mapping 232.1.1.1

Group: 232.1.1.1

Source list:

10.110.5.100

The output shows that multicast group 232.1.1.1 is associated with Source 1 (10.110.5.100). Device A will translate (0.0.0.0, 232.1.1.1) in IGMPv2 reports to (10.110.5.100, 232.1.1.1).

# Display the PIM routing table on Device A.

[DeviceA] display pim routing-table

Total 0 (*, G) entries; 1 (S, G) entries

(10.110.5.100, 232.1.1.1)

Protocol: pim-ssm, Flag:

UpTime: 00:13:25

Upstream interface: HundredGigE1/0/1

Upstream neighbor: 192.168.1.1

RPF prime neighbor: 192.168.1.1

Downstream interface(s) information:

Total number of downstreams: 1

1: HundredGigE1/0/2

Protocol: igmp, UpTime: 02:54:43, Expires: 00:02:47

The output shows that Device A has the (10.110.5.100, 232.1.1.1) entry.

# Display IGMP SSM mappings for multicast group 232.1.1.1 on Device B.

[DeviceB] display igmp ssm-mapping 232.1.1.1

Group: 232.1.1.1

Source list:

10.110.5.101

The output shows that multicast group 232.1.1.1 is associated with Source 2 (10.110.5.101). Device B will translate (0.0.0.0, 232.1.1.1) in IGMPv2 reports to (10.101.5.101, 232.1.1.1).

# Display the PIM routing table on Device B.

[DeviceB] display pim routing-table

Total 0 (*, G) entries; 1 (S, G) entries

(10.110.5.101, 232.1.1.1)

Protocol: pim-ssm, Flag:

UpTime: 00:12:16

Upstream interface: HundredGigE1/0/1

Upstream neighbor: 192.168.2.1

RPF prime neighbor: 192.168.2.1

Downstream interface(s) information:

Total number of downstreams: 1

1: HundredGigE1/0/2

Protocol: igmp, UpTime: 02:54:43, Expires: 00:02:47

The output shows that Device B has the (10.110.5.101, 232.1.1.1) entry.

Configuration files

· Device A:

interface HundredGigE1/0/1

pim sm

interface HundredGigE1/0/2

igmp enable

igmp version 3

multicast routing

pim

ssm-policy 2000

igmp

ssm-mapping 10.110.5.100 2000

acl basic 2000

rule 0 permit source 232.1.1.0 0.0.0.255

· Device B:

interface HundredGigE1/0/1

pim sm

interface HundredGigE1/0/2

igmp enable

igmp version 3

multicast routing

pim

ssm-policy 2000

igmp

ssm-mapping 10.110.5.100 2000

acl basic 2000

rule 0 permit source 232.1.1.0 0.0.0.255

· Device C:

interface HundredGigE1/0/1

pim sm

interface HundredGigE1/0/2

pim sm

interface HundredGigE1/0/3

pim sm

multicast routing

pim

c-bsr 192.168.1.1

c-rp 192.168.1.1

H3C S12500R Ethernet Switch Router Series Config Examples-Release 36xx-6W100

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us