From: Mohmmad, Imran (Imran.Mohmmad@amd.com)
Date: Wed Apr 09 2008 - 05:05:29 ART
Hi Experts,
Need to know what is the desired behavior of "ip pim
rp-announce-filter", as per CDOC if I am interpreting it correctly, it
says that when applied on RP mapping agent it will allow the Mapping
Agent to accept RP announcement from the RP those are permitted in
rp-list.
When configured on MA its denying the RP announcement messages from the
RP that is permitted in rp-list, and if put the deny statement in
rp-list acl it starts accepting the announcement.
Is this behaviour is normal?
Rack1R5#
ip pim autorp listener
ip pim send-rp-announce Loopback0 scope 16 interval 3
ip pim send-rp-discovery Loopback0 scope 16
ip pim rp-announce-filter rp-list 5
ip mroute 204.12.1.254 255.255.255.255 Serial1/1
interface Serial1/1
ip address 141.1.45.5 255.255.255.0
ip access-group 1 in
ip accounting access-violations
ip pim sparse-mode
serial restart-delay 0
interface Ethernet0/1
ip address 141.1.0.5 255.255.255.0
ip pim sparse-mode
no ip route-cache
no ip mroute-cache
full-duplex
Rack1R5#sh access-lists 5
Standard IP access list 5
20 permit 150.1.4.4 (306 matches)
Rack1R5#sh ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent (Loopback0)
Group(s) 224.0.0.0/4
RP 150.1.5.5 (?), v2v1
Info source: 150.1.5.5 (?), elected via Auto-RP
Uptime: 00:07:17, expires: 00:00:08
Now when I have explicitly permitted the RP 150.1.5.5 in ACL 5, it
doesn't show me the RP mapping.
Rack1R5#sh access-lists 5
Standard IP access list 5
20 permit 150.1.4.4 (336 matches)
10 permit 150.1.5.5 (1 match)
Rack1R5#sh ip pim rp mapping
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent (Loopback0)
Imran
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:50 ART