From: Narbik Kocharians (narbikk@gmail.com)
Date: Sat Apr 21 2007 - 13:58:51 ART
This is what i found when i tried filtering. If the RP was claiming to be
the RP for only two Mcast groups, the downstream router (The mapping agent)
was able to filter one of the groups. But if the RP was the RP for all
groups i could not filter one of the group addresses successfuly.
On 4/21/07, Riapolov, Bradley <BRiapolo@wm.com> wrote:
>
> Two RPs (172.16.101.1, 172.16.103.1), R4 is mapping and has elected the
> highest ip as the acting RP. Now, I would like to test RP-FILTERING with
> the
> intent to make 172.16.101.1 the RP - it does not work, why - am I missing
> how
> this is supposed to work? When I run debug ip pim auto-rp, filtering does
> not
> happen!
> R4#sri pim
> ip pim send-rp-discovery Loopback104 scope 16
> ip pim rp-announce-filter rp-list 1 group-list 2
> ip pim rp-announce-filter rp-list 3 group-list 4
> R4#sri access-list
> access-list 1 permit 172.16.101.1
> access-list 2 permit 224.0.0.0 15.255.255.255
> access-list 3 deny any
> access-list 4 deny any
>
> R4(other routers show the same info) #sh ip pim rp
> Group: 231.1.1.1, RP: 172.16.103.1, v2, v1, uptime 00:11:55, expires
> 00:02:0
>
> Thank you,
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Narbik Kocharians CCIE# 12410 (R&S, SP, Security) CCSI# 30832 Network Learning, Inc. (CCIE class Instructor) www.ccbootcamp.com (CCIE Training)
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:36 ART