From: Jason Madsen (madsen.jason@gmail.com)
Date: Fri Jul 11 2008 - 13:06:44 ART
I believe auto-rp listener uses dense mode only to contact the RP and
Mapping Agent groups (224.0.0.39 and .40), while DM Fallback allows Dense
mode (source to client) operation in the event of no RP.
Jason
On Fri, Jul 11, 2008 at 9:54 AM, David Lonnie <david.lonnie@gmail.com>
wrote:
> Hi,experts:
> I am confused with these 2 commands.
> ip pim dm-fallback is enable by default.and it means,it will fallback to
> dense-mode,regardless of interface mode configuration.
> if this is right.so why need to configure ip pim autorp listener when using
> sparse-mode?
>
> anybody can clarify for me?
>
>
> Thanks in advance.
>
>
> David
>
>
>
>
> ip pim autorp listener
>
> To cause IP multicast traffic for the two Auto-RP groups 224.0.1.39 and
> 224.0.1.40 to be Protocol Independent Multicast (PIM) dense mode flooded
> across interfaces operating in PIM sparse mode, use the ip pim autorp
> listener command in global configuration mode. To disable this feature, use
> the *no* form of this command.
>
> ip pim dm-fallback
>
> To enable Protocol Independent Multicast (PIM) dense mode (DM) fallback,
> use
> the *ip pim dm-fallback* command in global configuration mode. To prevent
> PIM dense mode fallback and to block all multicast traffic for groups not
> specifically configured, use the *no* form of this command.
>
> *ip pim dm-fallback *
>
> *no ip pim dm-fallback *
> Syntax Description
>
> This command has no arguments or keywords.
> Command Default
>
> PIM dense mode fallback is enabled. That is, a multicast group in the
> absence of rendezvous point (RP) information will fall to dense mode,
> regardless of the interface mode configuration.
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:54 ART