From: Scott Strobeck (scott@strobeck.net)
Date: Sat Aug 09 2008 - 15:16:33 ART
I had to go look this up, of course :-) So the command 'ip pim autorp
listener' tells a router to flood 224.0.1.39 (autorp announce) and
224.0.1.40 (autorp discovery) out sparse interfaces. In essence, this
allows autorp to run across sparse interfaces.
Thanks, Hobbs. . .I'll update my blog!
Scott
Hobbs wrote:
You can use autorp listener which technically is not sparse-dense.
All your interfaces may be sparse-mode and you can use autorp.
On Sat, Aug 9, 2008 at 8:35 AM, Scott Strobeck <scott@strobeck.net>
wrote:
Hi Anant,
autoRP only works with sparse-dense mode. If you're running
sparse and want to do 'automatic' mapping, you have to use bsr.
The reason is that the autoRP feature uses dense mode mcast to
propagate.
I actually did a write up explaining this and some other issues
with mcast on ccie.net. . .
http://www.ccie.net/blogs/clarifying-multicast-automatic-rp-configurations
Scott
Anant Tamgole wrote:
Hi,
I have a scenario where
1. R1 is hub and R2,R3 spokes.
2. OSPF is running on main interfaces as NBMA mode.
3. AutoRP is running on Hub R1.
4. igmp join for 224.1.1.1 is on R3's ethernet.
Problem: Not able to ping 224.1.1 from R1. If I give reapeat
count 10, first
ping succeeds but then it stops,
From R1 to R3 ping is ok.
I tried with ip pim nbma mode on Hub and ip pim spt-threshold
infinity on R3
, It does not help.
Anant
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
This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:29 ART