From: Hobbs (deadheadblues@gmail.com)
Date: Fri Aug 15 2008 - 22:12:20 ART
I got it to work. I need this on all routers:
ip pim rp-address 1.1.1.1 1
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
my hub loopback was 1.1.1.1.
Without these commands on the spokes the RP lookup fails. Do a debug ip
mpacket to see what's going on. If you can't see any output disable ip
mroute-cache on your interfaces:
int s1/0
no ip mroute-cache
int s1/1
no ip mroute-cache
Also, don't forget ip pim nbma-mode on the hub.
hope that helps.
On Fri, Aug 15, 2008 at 6:46 PM, Hobbs <deadheadblues@gmail.com> wrote:
> im gonna lab it right now. see what i can find
>
>
> On Fri, Aug 15, 2008 at 6:38 PM, Majonestx <majonestx@gmail.com> wrote:
>
>> Yes! You got it. I'll tell you one thing internetworkexpert materials can
>> fry your brain at times.
>>
>> :)
>>
>> Sent from my iPhone
>>
>> On Aug 15, 2008, at 7:35 PM, Hobbs <deadheadblues@gmail.com> wrote:
>>
>> Is your requirement not to use sparse-dense mode or autorp listener? Never
>> tried that but it's interesting...
>>
>> On Fri, Aug 15, 2008 at 4:54 PM, Michael Jones < <majonestx@gmail.com>
>> majonestx@gmail.com> wrote:
>>
>>> Experts I can not wrap my brain around this, please help!
>>>
>>> Scenario: I'm running all sparse mode interfaces, the workbook is asking
>>> for
>>> R2(below) to be Auto RP/ C-RP and MA.
>>>
>>> The announce command takes care of the C-RP
>>> The discovery command takes care of MA
>>> The static RP command takes care of the auto rp- because its tied to
>>> the
>>> access lits. The access lists says only permit 150.1.2.2 to be the auto
>>> rp
>>> for the mentioned groups.
>>>
>>> What I do understand is that the candidate RP will talk on the
>>> 224.0.1.39address while the Mapping agent listens exclusively for any
>>> Candidates
>>> talking on that address. The Mapping agent then turns around and speaks
>>> on
>>> the 224.0.1.40 for the "client routers"and tells them who the RP is.
>>> What I
>>> don't understand is, why do you need the access lists ?? If 150.1.2.2is
>>> the only speaking candidate in the network, shouldn't this become the RP
>>> by
>>> default for all multicast groups ? Also is this really auto RP ? Because
>>> without the Auto rp listener command or sparse dense mode on the
>>> interface
>>> how is that 224.0.1.39/40 even getting pushed out since they're no
>>> sparse-dense/dense mode interfaces ???
>>>
>>>
>>> ip pim rp-address 150.1.2.2 1
>>> ip pim send-rp-announce 150.1.2.2 scope 16
>>> ip pim send-rp-discovery Loopback0 scope 16
>>> !
>>> access-list 1 permit 224.0.1.39
>>> access-list 1 permit 224.0.1.40
>>>
>>>
>>> Thanks in advance for getting me straightened out!
>>>
>>>
>>> Blogs and organic groups at <http://www.ccie.net>http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> <http://www.groupstudy.com/list/CCIELab.html>
>>> 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:30 ART