From: Sergey (public@svlp.net)
Date: Fri Jul 20 2007 - 01:38:59 ART
Sergey wrote:
> Hello, it seems that AutoRP very sticking thing, if it enabled in one multicast domain it tends to jump
> in another multicast domain in pim sparse dense environment.
>
> Could you confirm or disprove some of my knowlenge?
>
> 1) It has higher priority than BSR, even more if BSR knows about AuroRP, it starts send AutoRP value not rp-candidate value.
> 2) AutoRP listener could not be disabled on cisco router.
> 3) AutoRP can not be filtered with ip pim bsr border
> 4) AutoRP can to be filtered with ip pim rp-announce-filter on non mapping agent routeres
> 5) It can be filtered only with
>
> ip multicast boundary ACL filter-autorp
> or with interface ACL.
> PS: Is "ip multicast boundary ACL filter-autorp" affect other (non autorp) multicast traffic?
I've tested in lab, yes it affect! It filter PIM join/prune message
Mar 1 19:18:07.056: PIM(0): Received v2 Join/Prune on Serial1/0.100 from 192.168.10.2, to us
Mar 1 19:18:07.060: PIM(0): No addition to olist at scoped boundaryrpt-bit src 200.0.0.1 grp 224.1.7.1
Mar 1 19:18:07.060: PIM(0): Received v2 Join/Prune on Serial1/0.100 from 192.168.10.2, to us
Mar 1 19:18:07.064: PIM(0): No addition to olist at scoped boundaryrpt-bit src 200.0.0.1 grp 224.1.7.1
so is interface ACL only one method to filter AutoRp?
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:41 ART