From: Swan, Jay (jswan@sugf.com)
Date: Sun Oct 14 2007 - 00:06:48 ART
I think the issue here is that the whole point of setting the stub flag
in EIGRP Hellos is to tell your neighbors that you don't want to receive
queries (i.e., you have no alternate paths to networks that you're not
advertising directly). If a hub router has multiple neighbors on a
multi-access interface and not all of them are stubs, it *must* send
queries on that interface to support the non-stub neighbors. Thus, the
stub is going to receive those multicast queries on the multi-access
interface whether it wants to or not.
Jay
> >
> > On 10/13/07, shiran guez <shiranp3@gmail.com> wrote:
> > > Can someone clarify that note from the command guide of EIGRP:
> > >
> > >
> > > *Multi-access interfaces, such as ATM, Ethernet, Frame Relay, ISDN
PRI,
> and
> > > X.25, are supported by the
> > > EIGRP Stub Routing feature only when all routers on that
interface,
> except
> > > the hub, are configured as
> > > stub routers.*
> > > Dose it mean that when I am using in for example a FR hub and
spoke
> > >
> > > R1 is hub and R2 R3 R4 are spokes, if I enable EIGRPStub in R2 I
must
> enable
> > > it on R3 and R4 as well?
> > >
> > > Or if I am in a Ethernet Segment :
> > >
> > > R1 and R2 and R3 are on the same segment if one is Stub all need
to be
> Stub
> > > Router?
> > >
> > > it doesn't make any sense!
> > >
> > >
> > > --
> > > Shiran Guez
> > > MCSE CCNP NCE1
> > > http://cciep3.blogspot.com
> > > http://www.linkedin.com/in/cciep3
> > >
> > >
>
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:14 ART