Configuring IGMP Proxy

note.gif

Note ●blank.gif For complete syntax and usage information for the commands used in this chapter, see these publications:

http://www.cisco.com/en/US/products/ps11845/prod_command_reference_list.html

  • Cisco IOS Release 15.0SY supports only Ethernet interfaces. Cisco IOS Release 15.0SY does not support any WAN features or commands.

 

Tip For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page:

http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html

Participate in the Technical Documentation Ideas forum

 

Prerequisites for IGMP Proxy

Before you configure VPLS, ensure that the network is configured as follows:

  • All devices on the IGMP UDL have the same subnet address. If all devices on the UDL cannot have the same subnet address, the upstream device must be configured with secondary addresses to match all of the subnets to which the downstream devices are attached.
  • IP multicast is enabled and the PIM interfaces are configured.
note.gif

Note Use the following guidelines when configuring PIM interfaces for IGMP proxy:

  • Use PIM sparse mode (PIM-SM) when the interface is operating in a sparse-mode region and you are running static RP, bootstrap (BSR), or Auto-RP with the Auto-RP listener capability.
  • Use PIM sparse-dense mode when the interface is running in a sparse-dense mode region and you are running Auto-RP without the Auto-RP listener capability.
  • Use PIM dense mode (PIM-DM) when the interface is operating in dense mode and is, thus, participating in a dense-mode region
  • Use PIM-DM with the proxy-register capability when the interface is receiving source traffic from a dense-mode region that needs to reach receivers that are in a sparse-mode region

Information About IGMP Proxy

IGMP Proxy

An IGMP proxy enables hosts in a unidirectional link routing (UDLR) environment that are not directly connected to a downstream router to join a multicast group sourced from an upstream network.

The figure below illustrates a sample topology that shows two UDLR scenarios:

  • Traditional UDL routing scenario--A UDL device with directly connected receivers.
  • IGMP proxy scenario--UDL device without directly connected receivers.
note.gif

Noteblank.gif IGMP UDLs are needed on the upstream and downstream devices.

note.gif

Noteblank.gif Although the following illustration and example uses routers in the configuration, any device (router or switch) can be used.

 

121929.ps

Scenario 1--Traditional UDLR Scenario (UDL Device with Directly Connected Receivers)

For scenario 1, no IGMP proxy mechanism is needed. In this scenario, the following sequence of events occurs:

  • User 2 sends an IGMP membership report requesting interest in group G.
  • Router B receives the IGMP membership report, adds a forwarding entry for group G on LAN B, and proxies the IGMP report to Router A, which is the UDLR upstream device.
  • The IGMP report is then proxied across the Internet link.
  • Router A receives the IGMP proxy and maintains a forwarding entry on the unidirectional link.

Scenario 2--IGMP Proxy Scenario (UDL Device without Directly Connected Receivers)

For scenario 2, the IGMP proxy mechanism is needed to enable hosts that are not directly connected to a downstream device to join a multicast group sourced from an upstream network. In this scenario, the following sequence of events occurs:

  • User 1 sends an IGMP membership report requesting interest in group G.
  • Router C sends a PIM Join message hop-by-hop to the RP (Router B).
  • Router B receives the PIM Join message and adds a forwarding entry for group G on LAN B.
  • Router B periodically checks its mroute table and proxies the IGMP membership report to its upstream UDL device across the Internet link.
  • Router A creates and maintains a forwarding entry on the unidirectional link (UDL).

In an enterprise network, it is desirable to be able to receive IP multicast traffic via satellite and forward the traffic throughout the network. With unidirectional link routing (UDLR) alone, scenario 2 would not be possible because receiving hosts must be directly connected to the downstream device, Router B. The IGM proxy mechanism overcomes this limitation by creating an IGMP report for (*, G) entries in the multicast forwarding table. To make this scenario functional, therefore, you must enable IGMP report forwarding of proxied (*, G) multicast static route (mroute) entries (using the ip igmp mroute-proxy command) and enable the mroute proxy service (using the ip igmp proxy-service command) on interfaces leading to PIM-enabled networks with potential members.

note.gif

Noteblank.gif Because PIM messages are not forwarded upstream, each downstream network and the upstream network have a separate domain.

How to Configure IGMP Proxy

Configuring the Upstream UDL Device for IGMP UDLR

Perform this task to configure the upstream UDL device for IGMP UDLR.

 

 
Command or Action
Purpose

Step 1

Device> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

Device# configure

Enters global configuration mode.

Step 3

Device (config)# interface interface-type number

Enters the interface configuration mode.

  • For the type and number arguments, specify the interface to be used as the UDL on the upstream device.

Step 4

Device (config-if)# ip igmp unidirectional-link

Configures IGMP on the interface to be unidirectional for

IGMP UDLR

Step 5

Device (config-if)# end

Ends the current configuration session and returns to privileged EXEC mode.

Configuring the Downstream UDL Device for IGMP UDLR with IGMP Proxy Support

Perform this task to configure the downstream UDL device for IGMP UDLR with IGMP proxy support

 
Command or Action
Purpose

Step 1

Device> enable

Enables privileged EXEC mode.

  • Enter your password if prompted.

Step 2

Device# configure

Enters global configuration mode.

Step 3

Device (config)# interface interface-type number

Enters the interface configuration mode.

  • For the type and number arguments, specify the interface to be used as the UDL on the downstream device for IGMP UDLR.

Step 4

Device (config-if)# ip igmp unidirectional-link

Configures IGMP on the interface to be unidirectional for

IGMP UDLR

Step 5

Device (config-if)# exit

Exits interface configuration mode and returns to global configuration mode.

Step 6

Device (config)# interface interface-type number

Enters the interface configuration mode.

  • For the type and number arguments, select an interface that is facing the nondirectly connected hosts.

Step 7

Device (config-if)# ip igmp mroute-proxy type number

Enables IGMP report forwarding of proxied (*, G) multicast static route (mroute) entries.

  • This step is performed to enable the forwarding of IGMP reports to a proxy service interface for all (*, G) forwarding entries in the multicast forwarding table.
  • In this example, the ip igmp mroute-proxy command is configured on Gigabit Ethernet interface 1/0/0 to request that IGMP reports be sent to loopback interface 0 for all groups in the mroute table that are forwarded to Gigabit Ethernet interface 1/0/0.

Step 8

Device (config-if) exit

Exits interface configuration mode and returns to global configuration mode.

Step 9

Device (config)# interface interface-type number

 

Enters interface configuration mode for the specified interface.

  • In this example, loopback interface 0 is specified.

Step 10

Device (config-if)# ip igmp helper-address udl interface-type interface-number

Configures IGMP helpering for UDLR.

  • This step allows the downstream device to helper IGMP reports received from hosts to an upstream device connected to a UDL associated with the interface specified for the interface-type and interface-number arguments.
  • In the example topology, IGMP helpering is configured over loopback interface 0 on the downstream device. Loopback interface 0, thus, is configured to helper IGMP reports from hosts to an upstream device connected to Gigabit Ethernet interface 0/0/0.

Step 11

Device (config-if)# ip igmp proxy-service

Enables the mroute proxy service.

  • When the mroute proxy service is enabled, the device periodically checks the static mroute table for (*, G) forwarding entries that match interfaces configured with the ip igmp mroute-proxy command (see Step 7) based on the IGMP query interval. Where there is a match, one IGMP report is created and received on this interface.
note.gif

Noteblank.gif The ip igmp proxy-service command is intended to be used with the ip igmp helper-address (UDL) command.

  • In this example, the ip igmp proxy-service command is configured on loopback interface 0 to enable the forwarding of IGMP reports out the interface for all groups on interfaces registered through the ip igmp mroute-proxy command (see Step 7).

Step 12

Device (config-if)# end

Ends the current configuration session and returns to privileged EXEC mode.

Step 13

Device# show ip igmp interface

(Optional) Displays multicast-related information about an interface.

Step 14

Device# show ip igmp udlr

(Optional) Displays UDLR information for directly connected multicast groups on interfaces that have a UDL helper address configured.

 

Configuration Examples for IGMP Proxy

Example: IGMP Proxy Configuration

Example: IGMP Proxy Configuration

The following example shows how to configure the upstream UDL device for IGMP UDLR and the downstream UDL device for IGMP UDLR with IGMP proxy support.

Upstream Device Configuration

interface gigabitethernet 0/0/0
ip address 10.1.1.1 255.255.255.0
ip pim dense-mode
!
interface gigabitethernet 1/0/0
ip address 10.2.1.1 255.255.255.0
ip pim dense-mode
ip igmp unidirectional-link
!
interface gigabitethernet 2/0/0
ip address 10.3.1.1 255.255.255.0

Downstream Device Configuration

ip pim rp-address 10.5.1.1 5
access-list 5 permit 239.0.0.0 0.255.255.255
!
interface loopback 0
ip address 10.7.1.1 255.255.255.0
ip pim dense-mode
ip igmp helper-address udl ethernet 0
ip igmp proxy-service
!
interface gigabitethernet 0/0/0
ip address 10.2.1.2 255.255.255.0
ip pim dense-mode
ip igmp unidirectional-link
!
interface gigabitethernet 1/0/0
ip address 10.5.1.1 255.255.255.0
ip pim sparse-mode
ip igmp mroute-proxy loopback 0
!
interface gigabitethernet 2/0/0
ip address 10.6.1.1 255.255.255.0

Feature Information for IGMP Proxy

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 1-1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 1-1 Feature Information for Power over Ethernet
Feature Name
Releases
Feature Information

PIM Join to IGMP Proxy Support

Cisco IOS Release 15.5(1)SY3

This feature was introduced.

Tip For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page:

http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html

Participate in the Technical Documentation Ideas forum