From: Darby Weaver (darbyweaver@yahoo.com)
Date: Sun May 27 2007 - 10:56:57 ART
So...
Did you understand how to make Multicast work in just
Sparse-Mode and "ONLY" Sparse-Mode with no DENSE-mode
elements?
I did not get that this happened for you.
If so, I suspect you did not learn what that lesson is
trying to teach you to ocnfigure.
Think about it 224.0.0.40 and 224.0.0.39 - What are
they used for? When? Which mode?
If the lab asked you to get multicast working using
Sparse-Mode, then making it work using
Sparse-Dense-Mode probably did not meet the objective
of the task.
And are you sure you need ip pim nbma mode and ip
mroute for Sparse-Mode to function over a hub and
spoke frame cloud? Why? Why not? Which is it?
Think on it a bit, try it, and let us know...
You may want to throw us a bone and show us the
appropriate show commands as well.
And maybe a copy of your routing table for the routers
involved.
Perhaps perform an extended ping to 224.1.1.1 and show
some of the results to give us a clear more complete
picture of what you are experiencing.
Their are different combos involved in configuring
Multicast and this is the challenge.
Sparse-Mode will work by itself, but think about what
it needs to function by itself. And you should start
the lab perhaps with just two ethernet interfaces
connected back-to-back, with a hub, or on the same
vlan, over a P2P interface etc. - Just to start off as
basic as possible and then build on that.
--- Ovidiu Neghina <o.neghina@gmail.com> wrote:
> hi,
>
> After I enabled ip pim autorp listener in each
> router R1,R2,R3 it started to
> work. I should have looked at the configuration
> guide for enabling sparse
> mode with autorp :((
>
> * 5. *Either perform Steps 6 and 7 and proceed to
> Step 9 or perform Step 8
> and then proceed to Step 9.
> *6. **ip pim sparse-mode
> 7. **ip pim autorp listener
> 8. **ip pim sparse-dense-mode
> 9. **end*
> However I was expecting to work only with sparse
> mode enabled on the
> interfaces but now i realize my expectation was
> wrong.
> If I have a multicast group in dense mode I will not
> ever flood that group
> over sparse mode interfaces even if that group is
> 224.0.1.40 - the discovery
> group.
>
> going back to next lab now :)
>
> Ovidiu
> On 5/27/07, Dan C <cdan2154@gmail.com> wrote:
> >
> > Hi Ovidiu,
> >
> > In sparse mode over FR you may need to enable ip
> pim nbma-mode on the
> > serial interface of the hub router. Also on the
> spoke try to assign one more
> > interface to the pim process. If you still have
> problems just past in a show
> > ip mroute.
> >
> > cheers,
> > Dan
> >
> > On 5/27/07, Ovidiu Neghina <o.neghina@gmail.com>
> wrote:
> >
> > > Hi dear all
> > > I have a situation where a router R1 has 2
> point-to-point frame-relay
> > > interfaces towards another 2 routers. One of
> them is RP and Mapping
> > > agent
> > > (R2) for 224.1.1.1/32 .
> > > The problem that I have is R1 does not forward
> the mapping information
> > > towards the other router R3 , i.e. does not
> forward the 224.0.1.40 on
> > > the
> > > point-to-point link.
> > > every router is configured with sparse-mode on
> the interfaces.
> > > Is this normal ? Shouldn't packets destined to
> 224.0.1.40 be sent
> > > everywhere interface/subinterface where it has a
> pim neighbor ?
> > >
> > > Thank you
> > > Ovidiu
> > >
> > >
>
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:22 ART