From: Bajo (bajoalex@gmail.com)
Date: Sat Oct 13 2007 - 07:04:19 ART
Hi Shiran,
The context of that statement is "the hub is the only connection to
the Internet (or corporate network) and the spokes do not need any
specific routes from Internet. They do not want to be bothered for
any updates either" So you are trying to avoid any eigrp update
exchanges from the spokes routers to any other external routers. The
spokes want the hub to do that for them . So spokes send this stub
flag ( an "inaccessible." message) (like saying do not bother me....)
Refer to the 12.4 guide (better written):
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cg/hirp_c/ch07/erconfig.htm#wp1003890
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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Kind Regards,Bajo
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:14 ART