From: Sergey (public@svlp.net)
Date: Fri Jul 20 2007 - 00:58:04 ART
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?
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:41 ART