From: gladston@br.ibm.com
Date: Mon Aug 15 2005 - 12:52:34 GMT-3
Have you seen this behavior?
A router acting as BSR will advertises the presence of RP if it receives RP-announces using auto-RP.
R5 is acting as C-BSR and auto-RP mapping agent
R2 sends auto-RP announces for 239.22.1.1
R3 is connected to R5. R3 learns the RP address via auto-RP and via bootstrap:
Rack2R3#sh ip pim rp ma
Group(s) 239.22.1.1/32
RP 148.5.2.1 (?), v2v1
Info source: 148.5.5.1 (?), elected via Auto-RP, via bootstrap, priority 0
Uptime: 01:27:28, expires: 00:02:05
On another test, R6 is connected to R2. If auto-RP messages are filtered, R6 learns the RP for 239.22.1.1
through BSR:
Rack2R2
ip multicast boundary 84
access-list 84 deny 224.0.1.39
access-list 84 deny 224.0.1.40
access-list 84 deny 239.0.0.0 0.255.255.255
access-list 84 permit 224.0.0.0 15.255.255.255
Rack2R6#sh ip pim rp ma
PIM Group-to-RP Mappings
Group(s) 239.22.1.1/32
RP 148.5.2.1 (?), v2v1
Info source: 148.5.5.1 (?), elected via Auto-RP, via bootstrap, priority 0
Uptime: 00:30:29, expires: 00:00:21
Rack2R6#sh ip pim rp ma
PIM Group-to-RP Mappings <------------ expired
Rack2R6#sh ip pim rp ma
PIM Group-to-RP Mappings
Group(s) 239.22.1.1/32
RP 148.5.2.1 (?), v2
Info source: 148.5.5.1 (?), via bootstrap, priority 0 <---- learned via bootstrap
Uptime: 00:01:00, expires: 00:02:21
configs:
R5
ip pim bsr-candidate Loopback0
ip pim send-rp-discovery Loopback0 scope 10
R2
ip pim send-rp-announce Loopback0 scope 10 group-list 81
!
access-list 81 permit 239.22.1.1
Version is:
C2600-J1S3-M, Version 12.2(15)T5
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3