Auto-rp listener is used to treat the groups 224.0.1.39 and
224.0.1.40 in a dense-mode to overcome the chicken & egg problem of
auto-rp with sparse-mode. If you are using sparse-dense-mode you don't
need the auto-rp listener because if the RP is not known the interface
falls back to dense mode to discover the RP. But if you are using only
sparse-mode , you still need to send mcast packets for groups
224.0.1.39 and 224.0.1.40 out every PIM enabled interface to discover
the RP and that's what the auto-rp listener does .
HTH
Ravi
On Thu, Apr 16, 2009 at 6:08 PM, Ryan West <rwest_at_zyedge.com> wrote:
> Jason,
>
> Your interfaces would be configured for ip pim sparse-mode.
>
> -ryan
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Jason Alex
> Sent: Thursday, April 16, 2009 1:02 PM
> To: Cisco certification
> Subject: Auto RP Listener
>
> Dear All,
> As i know that the command "*ip pim auto-rp listener*"
> configures sparse mode operation for all the multicast groups except "*
> 224.0.1.39*" & "*224.0.1.40*" works as a dense mode operation
>
> So the question is , should i configure the PIM interfaces with "*ip pim
> sparse-mode*" or "*ip pim sparse-dense-mode*" ?
>
> Thanks In Advance
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Apr 16 2009 - 18:34:26 ART
This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:12 ART