IGMP Profile

If your action is permit then everything else is going to be denied, if your action is deny then everything else would be permitted

Lets then test the above

The topology looks like

R3 is acting like a Server, running in ip pim dense for simplicity only on R3 Ethernet

R4 is configured to Join the 224.1.1.1 and the 224.2.2.2 Multicast Groups

R3#show ip pim neigh
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR
Priority,
      S - State Refresh Capable
Neighbor          Interface                Uptime/Expires    Ver   DR
Address
Prio/Mode
R3#
R4#show ip pim inter
Address          Interface                Ver/   Nbr    Query  DR     DR
                                          Mode   Count  Intvl  Prior
R4#show ip igmp grou
IGMP Connected Group Membership
Group Address    Interface                Uptime    Expires   Last
Reporter
224.1.1.1        FastEthernet0/0          00:01:58  stopped 150.34.34.4
224.2.2.2        FastEthernet0/0          00:01:57  stopped 150.34.34.4

With out any IGMP Profile Configured at the Switch1, let’s see if it works

R3#clear ip mroute *
R3#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 150.34.34.4, 8 ms
R3#ping 224.2.2.2

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:

Reply to request 0 from 150.34.34.4, 8 ms

Cool it works

Now With this configuration at Sw1

Sw1(config)#ip igmp profile 6
Sw1(config-igmp-profile)#permit
Sw1(config-igmp-profile)#range 224.1.1.1
Sw1(config-igmp-profile)#end
Sw1(config)#do show ip igmp profile 6
IGMP Profile 6
    permit
    range 224.1.1.1 224.1.1.1
Sw1(config)#int f0/3
Sw1(config-if)#ip igmp filter 6

Now let’s test at R3 Again

R3#clear ip mroute *
R3#ping 224.1.1.1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 150.34.34.4, 4 ms
R3#ping 224.2.2.2

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
.
R3#

Now with the Deny Action:

Sw1(config)#ip igmp profile 2
Sw1(config-igmp-profile)#deny
Sw1(config-igmp-profile)#range 224.2.2.2
Sw1(config-igmp-profile)#end
Sw1(config)#do show ip igmp profile 2
IGMP Profile 2
    range 224.2.2.2 224.2.2.2
Sw1(config)#int f0/3
Sw1(config-if)#ip igmp fil 2

Let’s try it again:

R3#clear ip mroute *
R3#ping 224.1.1.1   

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:

Reply to request 0 from 150.34.34.4, 8 ms
R3#ping 224.2.2.2   

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
.
R3#

And this works very nice!!

A Networker Blog

Advertisements

2 thoughts on “IGMP Profile

  1. Nice! It helped.

    Oh BTW: you can verify by debugging igmp profile as well:
    ip igmp profile 1 <- drops
    range 224.2.2.2 224.2.2.2

    SW1#deb ip igmp filter
    event debugging is on
    SW1#
    *Mar 1 00:36:25.693: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/43: permit
    *Mar 1 00:36:26.415: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.2.2.2 from Fa0/41: deny
    *Mar 1 00:36:33.461: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/42: permit

    ip igmp profile 1 <- drops (i.e permits only 224.2.2.2)
    range 224.0.0.0 224.2.2.1
    range 224.2.2.3 239.255.255.255
    !
    *Mar 1 00:56:32.512: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/42: deny
    *Mar 1 00:56:34.760: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/43: deny
    *Mar 1 00:56:35.423: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.2.2.2 from Fa0/41: permit
    *Mar 1 00:56:36.513: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/42: deny
    *Mar 1 00:56:37.763: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/43: deny
    *Mar 1 00:57:28.850: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/43: deny
    *Mar 1 00:57:34.814: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.0.1.40 from Fa0/42: deny
    *Mar 1 00:57:36.517: IGMPFILTER: igmp_filter_process_pkt(): checking group 224.2.2.2 from Fa0/41: permit

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s