From: Gupta, Gopal (NWCC) (gopal.gupta@hp.com)
Date: Mon Nov 12 2007 - 14:03:23 ART
That's really helpful JOSEPH SAAD.
Thanks a lotttttt
I got the point
Best Regards,
Gops
-----Original Message-----
From: Joseph Saad [mailto:joseph.samir.saad@gmail.com]
Sent: Monday, November 12, 2007 22:29
To: Gupta, Gopal (NWCC)
Cc: Joseph Brunner; Cisco certification
Subject: Re: Rp-Announce & RP-Discovery
It's a little bit difficult which Joseph you mean :-)
But those 2 commands mean that: Set those 2 groups to use
Manually-configured RP.
This is what happens when you define an RP to a group. It sets the group
into Sparse mode as the determining factor for a group being in dense or
sparse mode.
Because of the chicken and egg problem, you can't automatically assign
auto-rp to those 2 groups 224.0.1.39/40 until you discover the RP first.
That's why those 2 groups natively work in Dense mode.
By using those commands, you are assigning an RP to those 2 groups,
which means you are forcing them into sparse even before discovery of
the RP via the Auto-RP mechanism.
Other people are free to comment.
Cheers,
Joseph
On Nov 12, 2007 8:36 PM, Gupta, Gopal (NWCC) <gopal.gupta@hp.com> wrote:
> HiJoseph,
>
> If I am not wrong, This command means that only these 2 groups will be
> in Dense mode and others all will be in Sparse until RP is reachable.
> My Question is even 224.0.1.39/40 should show in Routing table as
> sparse and not dense.
>
> Regards,
> Gops
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Joseph Brunner
> Sent: Monday, November 12, 2007 21:30
> To: Gupta, Gopal (NWCC); 'Cisco certification'
> Subject: RE: Rp-Announce & RP-Discovery
> Importance: Low
>
>
> Ip pim autorp listener
>
> DOC It..
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Gupta, Gopal (NWCC)
> Sent: Monday, November 12, 2007 10:40 AM
> To: Cisco certification
> Subject: Rp-Announce & RP-Discovery
>
> Hi Folks,
>
> Can we make these 2 groups working in Sparse mode anyway.
> 224.0.1.39 & 224.0.1.40
>
> Suppose R1 is the hub and it has 2 spokes R2 and R3 ; and R2 is RP &
MA.
> So R1 wont be able to forward these mapping aganet discovery messages
> to R3. because these 2 groups work in Dense mode and wont be able to
> cross from spoke to spoke.
> one workaround is to configure Tunnel bet R2 and R3 Spokes.
> Is there any way we can make them working in sparse mode and then
> enableing NBMA Mode on R1 without using tunnels.
>
> Regards,
> Gops
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:29 ART