From: san (san.study@gmail.com)
Date: Tue May 10 2005 - 14:23:14 GMT-3
NBMA example on the bottom of the link shows, We need to enable "ip
pim nbma" on Spokes also. (I didnt try this before). Now, I guess
this command is tied to NBMA interface & not specific to HUB.
http://www.cisco.com/en/US/tech/tk828/technologies_white_paper09186a00800d6b61.shtml#99498
/SAN
On 5/9/05, san <san.study@gmail.com> wrote:
> Taylor,
>
> I also faced exactly same problem. I don't know a way to resolve it.
> (tried "static rp address to spoke & auto-rp address to spoke...with
> & without pim NBMA mode...with sparse mode )
>
> Problem only clears only if i move RP to Hub. Lets see if anyone can
> help us to figure this problem.
>
> /SAN
>
>
> On 5/9/05, Wang, Ting (Taylor) <wangting@avaya.com> wrote:
> > Hi All,
> > I faced a problem on the multicast NBMA. The R1 is the Hub , R5, R6 are the spoke.
> >
> > R1 S0/0 --- R2 and others
> > |
> > | |
> > | NMBA |
> >
> > s0/0 S0/0
> > Ether - R5 ( RP) R6--- Ether (225.1.1.1)
> >
> > If one Spoke ( R5 in this case) is RP and the group member is in another spoke( R6, e.g) , the RP can't receive the join message. I notice from the R6 that the PIMv2 join message was sent to the S0/0 ip addresss of R5, but R5 never get it. The PIM NBMA mode can't help. I guess R1 doesn't forword the PIMv2 packet to R5 correctly. Anyone have the idea?
> >
> > Thanks,
> > Taylor
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:57 GMT-3