Re: BSR question.......

From: Craig Miller <ripperthejack2001_at_yahoo.com>
Date: Thu, 23 Jul 2009 09:31:56 -0700 (PDT)

I think your problem is the sparse-mode configuration, your RP and BSR haven't learned about each other because of the sparse-mode, sparse dense mode would resolve that, because the dense mode would allow the the 224.0.1.39 and 224.0.1.40 traffic to flood to and from the BSR.

Multicasting is probably my weakest area at the moment, so I hope this helps point you in the right direction.

--- On Thu, 7/23/09, Rana Bilal <rab_91_at_hotmail.com> wrote:

> From: Rana Bilal <rab_91_at_hotmail.com>
> Subject: BSR question.......
> To: ccielab_at_groupstudy.com, asequeira_at_ine.com
> Date: Thursday, July 23, 2009, 11:19 AM
> Hi Experts,
>
> My
> question is related to BSR candidate impelmentation on a
> network. Lets say I have 3 routers running PIM sparse mode
> and I'm planning to
> make one router as rp candidate and 2nd one as the bsr
> candidate. I'm doing an
> IGMP join on one of the interfaces of the third router. But
> not able to ping
> that group from any of the three routers in sparse mode
> domain. How ever when
> I make my first router both as rp candiate and bsr
> candidate, I'm able to ping
> the multicast group address. Does any one knows why this is
> happening, or is
> it mandatory to have rp candiate and bsr candidate
> configured on the same
> router in order for the multicast to work properly. Any
> help will be
> appreciated.....
>
>
>
>
>
>
>
>
>
> ~Ahmad Bilal
>
> _________________________________________________________________
> Show them the way! Add maps and directions to your party
> invites.
> http://www.microsoft.com/windows/windowslive/products/events.aspx
>
>
> 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
Received on Thu Jul 23 2009 - 09:31:56 ART

This archive was generated by hypermail 2.2.0 : Sat Aug 01 2009 - 13:10:23 ART