From: Thounda Craig, Jr. (hjcgroup@xxxxxxxxxxxxxx)
Date: Mon Aug 20 2001 - 15:06:43 GMT-3
Hmm!
It's true, my friend... just did it for 700 (plus) sites.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Bob Chahal
Sent: Monday, August 20, 2001 1:57 PM
To: rsevier; Atakan San
Cc: Daniel Young; ccielab@groupstudy.com
Subject: Re: RPF lookup failed stuff with auto rp
I can't find any CCO documentation to backup what you say but Jeff Doyles
Vol 2 page 553, he states that when configuring the mapping agent the
interface associated with the MA must have PIM enabled.
----- Original Message -----
From: "rsevier" <rsevier@zealousolutions.com>
To: "Atakan San" <asan@cisco.com>
Cc: "Daniel Young" <danyoung99@mediaone.net>; <ccielab@groupstudy.com>
Sent: Monday, August 20, 2001 6:40 PM
Subject: RE: RPF lookup failed stuff with auto rp
> A- It sounds like you had the mapping agent and the candidate rp pointing
> to your loopback, is that safe to assume? Let's understand the process
now.
> C-RP's will begin multicasting their candidacy to be the RP via
RP-announce
> messages which are sent via the 224.0.1.39 group. The mapping agents will
> multicast the contents of their group-to-RP mapping cache to the
224.0.1.40
> group. All other routers will join the 224.0.1.40 group. So I am going
to
> guess that if the interface that you have as the C-RP and the MA needs to
be
> in the PIM process in order to participate in the 224.0.1.39 & 224.0.1.40
> groups. I will try to validate with some reference documentation at a
later
> time. Hope this helps.
>
> Raymond
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Atakan San
> Sent: Monday, August 20, 2001 9:28 AM
> To: rsevier
> Cc: ccielab@groupstudy.com
> Subject: Re: RPF lookup failed stuff with auto rp
>
>
> Thanks for all answers and further commends on this guys
> I put ip pim sparse-dense-mode under loopback and it worked
> Raymond I checked your stuff My loopback is/was always reachable via
unicast
> At this point, I have no possibility to have a kind of pim neighbor with
> loopback0 but needed to put pim command why ?
> Cheers
> Atakan
>
> rsevier wrote:
>
> > Atakan - Check your unicast table. The RPF lookups are dependent on
the
> > unicast table and mroutes.
> >
> > Raymond
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Atakan SAN
> > Sent: Monday, August 20, 2001 7:46 PM
> > To: ccielab@groupstudy.com
> > Subject: RPF lookup failed stuff with auto rp
> >
> > Hi Group
> >
> > Very straightforward but hitting a strange issue
> > sparse-dense mode all
> >
> > X3---------------- X2
> > '
> > '
> > '
> > '
> > X1
> >
> > Testing auto-rp---> X3' s loopback0 192.19.27.7 is used for both
> > announce and discovery messages for auto-rp
> >
> > I am having RPF lookup faileds as follows on X1
> > 15:55:47: IP: s=192.19.27.7 (Serial0.12) d=224.0.1.39 len 52, RPF lookup
> > faileds
> > 15:55:47: IP: s=192.19.27.7 (Serial0.13) d=224.0.1.39 len 52, RPF lookup
> > faileds
> > 15:55:47: IP: s=192.19.27.7 (Serial0.12) d=224.0.1.40 len 52, RPF lookup
> > faileds
> > 15:55:47: IP: s=192.19.27.7 (Serial0.13) d=224.0.1.40 len 52, RPF lookup
> > faileds
> > X1#
> > 15:56:47: IP: s=192.19.27.7 (Serial0.12) d=224.0.1.39 len 52, RPF lookup
> > faileds
> > 15:56:47: IP: s=192.19.27.7 (Serial0.13) d=224.0.1.39 len 52, RPF lookup
> > faileds
> > 15:56:47: IP: s=192.19.27.7 (Serial0.12) d=224.0.1.40 len 52, RPF lookup
> > faileds
> > 15:56:47: IP: s=192.19.27.7 (Serial0.13) d=224
> >
> > Thanks
> > Atakan
> > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:54 GMT-3