From: allboutcisco (frenzeus@streamyx.com)
Date: Sun Apr 23 2006 - 04:54:16 GMT-3
Hi group,
I was labbing on IEWB v3 lab 11 & came across Task4.8 which seems quite straight forward that R2 is to be configured as an eigrp stub router to prevent R5 from further querying it in the event that there is a topo change in the eigrp domain.
As i scheme through the doc cd on eigrp stub, it says:
"Multi-access interfaces, such as ATM, Ethernet, Frame Relay etc are supported by the EIGRP Stub Routing feature only when all routers on that interface, except the hub, are configured as stub routers."
Which makes perfect sense since on R5 int s0/0 is connected to both R3 & R2, and in the event of a topo change in the eigrp domain, R5 would multicast 1st query out int s0/0 (since to L3 process, R5 sees this as 1 interface but when reaches L2 there are actually 2 PVCs) and in turn would replicate them out DLCI 513 & 502 which would be received by both R3 & R2 at the other end of the PVCs.
From the solution guide, only R2 is configured as eigrp stub & in the event of a topo change, R5 would still multicasts 1st query out int se0/0 & would still be replicated to both R3 & R2, which to my understanding, defeats the stub feature if only configured on R2 since R2 is still receiving the replicated query via it's PVC to R5.
Appreciate the feedback if i'm looking at this in the wrong direction.
Many thanks in advance.
-K
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:59 GMT-3