Multicast: rp-announce-filter is filtering all groups

Unanswered Question
Aug 8th, 2008

Hello,

I want R2 to be RP for 232.0.0.0/8 and R3 to be RP for 233.0.0.0/8. I want to do the filtering on the mapping agent only.

R1: mapping agent

R2: RP (2.2.2.2)

R3: RP (3.3.3.3)

R1 connected to R2 and R3 via serial links.

I have the following on R1:

access-list 2 permit 2.2.2.2

access-list 3 permit 3.3.3.3

access-list 20 permit 232.0.0.0 0.255.255.255

access-list 30 permit 233.0.0.0 0.255.255.255

ip pim send-rp-discovery Loopback0 scope 10

ip pim rp-announce-filter rp-list 3 group-list 30

ip pim rp-announce-filter rp-list 2 group-list 20

Yet R1 is still filtering all groups. See the log below:

*Mar 1 00:14:40.555: Auto-RP(0): Received RP-announce, from 2.2.2.2, RP_cnt 1,

ht 181

*Mar 1 00:14:40.559: Auto-RP(0): Filtered 224.0.0.0/4 for RP 2.2.2.2

*Mar 1 00:14:46.959: Auto-RP(0): Received RP-announce, from 3.3.3.3, RP_cnt 1,

ht 181

*Mar 1 00:14:46.963: Auto-RP(0): Filtered 224.0.0.0/4 for RP 3.3.3.3

Is there a problem with my config?

thank you,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Fri, 08/08/2008 - 13:10

Hello,

yes because without any specific configurations a candidate RP will advertise itself for the whole 224.0.0.0/4 multicast address space and this is what happening on the candidate RPs and they are filtered.

Add the right ACL on each candidate RP

ip pim send-rp-announce loopN scope TTL# group-list ACL#

Hope to help

Giuseppe

Giuseppe Larosa Fri, 08/08/2008 - 13:12

Hello,

I didn't see you were the same that had opened the thread !

I'm really tired ..

Excuse me

Best Regards

Giuseppe

Actions

This Discussion