From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Mon Jan 16 2006 - 20:02:48 GMT-3
Yes. It's designed to stop arbitrary devices from announcing themselves as RPs for your network or for a specific group.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
________________________________________
From: CCIEin2006 [mailto:ciscocciein2006@gmail.com]
Sent: Monday, January 16, 2006 4:56 PM
To: Brian McGahan
Cc: Cisco certification
Subject: Re: rp-announce-filter not working as expected
Thanks but isn't the rp-announce filter unecessary if you are specifying the groups you want to announce on the rp itself? Or is this more of a fail-safe mechanism for a misconfigured RP?
On 1/16/06, Brian McGahan <bmcgahan@internetworkexpert.com> wrote:
Actually it is working as expected. The range announced by the
candidate RP must match the range configured on the mapping agent in the
rp-announce-filter. The rp-announce-filter is not used to control group
to rp mappings, but instead is used to globally permit or deny a
candidate rp's announcements.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> CCIEin2006
> Sent: Monday, January 16, 2006 3:03 PM
> To: Cisco certification
> 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