From: Lee Donald (Lee.Donald@t-systems.co.uk)
Date: Thu Oct 20 2005 - 06:01:16 GMT-3
Ryan,
You need a group list on the RP announce, and also a filter on the mapping
agent for this situation.
I don't know why Cisco have implemented this like this, but for the RP to be
just for 2 groups and nothing else, 2 filters must be used. One on the RP
and the other on the mapping agent.
Regards
Lee.
-----Original Message-----
From: The Great Ryan [mailto:pv.ryan@gmail.com]
Sent: 19 October 2005 17:21
To: Cisco certification
Subject: Use of "ip pim rp-announce-filter"
Hi, Group,
---(e0)R1(s1)------(s1)R2(e0)---
I setup a lab for RP Filtering by using Auto-RP
R1 acts as RP announcement
R2 acts as mapping agent
In R1, I already limit the use of RP by access-list 11 (i.e. 224.0.0.0
7.255.255.255)
Is it necessary to also set a RP-filter on the mapping agent to limit
the use of RP?
I have no idea where I should put "ip pim rp-announce-filter" in
multicast network. Thanks !
Ryan
=======================================
R2#show ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP-mapping agent (Loopback0)
Group(s) 224.0.0.0/5
RP 172.16.1.1 (?), v2v1
Info source: 172.16.1.1 (?), elected via Auto-RP
Uptime: 00:20:11, expires: 00:02:48
================R1 Config========================
interface Loopback 0
ip address 172.16.1.1 255.255.255.0
interface serial 1
ip pim sparse-dense-mode
!
ip pim send-rp-announce Loopback0 scope 15 group-list 11
access-list 11 permit 224.0.0.0 7.255.255.255
================R2 Config========================
R2
interface s1
ip pim sparse-dense-mode
!
ip pim send-rp-discovery Loopback0 scope 15
ip pim rp-announce-filter rp-list 1 group-list 11
access-list 1 permit 172.16.1.1
access-list 11 permit 224.0.0.0 7.255.255.255
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:51 GMT-3