From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Tue Jan 17 2006 - 00:40:10 GMT-3
Is your AutoRP requesting the 239 range? From your debug, it doesn't show
that the RP is requesting it. It is my understanding that the mapping agent
will filter the only when the RP requests a range that is denied by the
filter, but if it doesn't request the group, then there is nothing to filter.
Someone please correct me if this wrong.
Dave
-----Original Message-----
From: nobody@groupstudy.com
To: Cisco certification
Sent: 1/16/2006 4:02 PM
Subject: rp-announce-filter not working as expected
It seems the rp-announce-filter command does not work on ranges of group
addresses.
I am saying this because I have one router announcing the entire
224.0.0.0/4range while the mapping agent has a filter configured for
239.0.0.0/8. A debug shows that the 224.0.0.0/4 is being filtered by the
mapping agent.
See example below:
This is the RP ---> (R3)------(R1) <----- This is the mapping agent with
rp-announce-filter
Here are the configs:
R3:
ip pim send-rp-announce Loopback0 scope 15
R1:
ip pim send-rp-discovery Serial0/0 scope 15
ip pim rp-announce-filter rp-list R3 group-list R3-groups
ip access-list standard R3
permit 150.1.3.3
ip access-list standard R3-groups
permit 239.0.0.0 0.255.255.255
Debug ip pim auto-rp on R1 shows the following:
*Mar 1 23:34:21.671: Auto-RP(0): Received RP-announce, from 150.1.3.3,
RP_cnt 1, ht 181
*Mar 1 23:34:21.671: Auto-RP(0): Filtered 224.0.0.0/4 for RP 150.1.3.3
*Mar 1 23:34:21.671: Auto-RP(0): Received RP-announce, from 150.1.3.3,
RP_cnt 1, ht 181
*Mar 1 23:34:21.671: Auto-RP(0): Filtered 224.0.0.0/4 for RP 150.1.3.3
Any idea why R1 is not permitting the 239.0.0.0 range?
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:49 GMT-3