From: Chris Lewis (chrlewiscsco@yahoo.com)
Date: Sun Nov 27 2005 - 23:55:02 GMT-3
Administrative distance is only ever locally significant and is never transmitted to other routers.
EIGRP routers know to apply a different AD to external routes as they are transmitted using a different TLV (type 0x0103 as opposed to 0x0102 for internal TLV)
No such distinction applies for summary routes.
Chris
Primetek_Easyman <easyman@primetek.com.tw> wrote:
Dear GS gurus,
The issue had been solved by using NAT.
Thanks.
But I have another confusion, following are part of the config.
The lab topology:
R9(e0/0)-----------------------------(e0)BB3
R9
interface Ethernet0/0
ip address 170.1.15.9 255.255.255.192
ip summary-address eigrp 69 172.16.0.0 255.255.0.0 5
half-duplex
router eigrp 69
variance 128
network 170.1.9.9 0.0.0.0
network 170.1.15.0 0.0.0.63
network 170.1.69.0 0.0.0.3
no auto-summary
BB3
interface Ethernet0
ip address 170.1.15.13 255.255.255.192 secondary
ip address 150.50.9.210 255.255.255.128
ip nat outside
ip summary-address eigrp 69 4.0.0.0 255.0.0.0 5
ip nat inside source static 150.50.9.210 170.1.15.13
router eigrp 69
network 4.0.0.0
network 150.50.0.0
network 170.1.15.0 0.0.0.63
no auto-summary
As you can see in both routers I put the " ip summary-address eigrp 69
x.x.x.x x.x.x.x" on.
The output from "sh ip route" of both routers as following.
R9
r9#sh ip route eigrp
170.1.0.0/16 is variably subnetted, 16 subnets, 5 masks
D EX 170.1.150.0/24 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.200.0/27 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.8.8/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.7.7/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.6.6/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.5.5/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.4.4/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.2.2/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.1.1/32 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.100.8/30 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.100.4/30 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.100.0/30 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D EX 170.1.78.0/30 [170/2169856] via 170.1.69.1, 11:48:38, Serial0/1
D 4.0.0.0/8 [90/409600] via 170.1.15.13, 00:09:01, Ethernet0/0
D EX 192.168.10.0/24 [170/2169856] via 170.1.69.1, 11:48:39, Serial0/1
172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
D EX 172.16.0.0/22 [170/2169856] via 170.1.69.1, 11:48:39, Serial0/1
D 172.16.0.0/16 is a summary, 01:41:41, Null0
150.50.0.0/24 is subnetted, 1 subnets
D EX 150.50.4.0 [170/2169856] via 170.1.69.1, 11:48:39, Serial0/1
BB3
BB3#sh ip route eig
170.1.0.0/16 is variably subnetted, 16 subnets, 5 masks
D EX 170.1.150.0/24 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.200.0/27 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.1.1/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.2.2/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.4.4/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.5.5/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.6.6/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.7.7/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.8.8/32 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D 170.1.9.9/32 [90/409600] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.100.8/30 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.100.4/30 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.100.0/30 [170/2195456] via 170.1.15.9, 00:09:25, Ethernet0
D EX 170.1.78.0/30 [170/2195456] via 170.1.15.9, 00:09:26, Ethernet0
D 170.1.69.0/30 [90/2195456] via 170.1.15.9, 00:09:26, Ethernet0
4.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
D 4.0.0.0/8 is a summary, 00:09:29, Null0
D EX 192.168.10.0/24 [170/2195456] via 170.1.15.9, 00:09:26, Ethernet0
D 172.16.0.0/16 [90/2195456] via 170.1.15.9, 00:09:26, Ethernet0
150.50.0.0/16 is variably subnetted, 2 subnets, 2 masks
D EX 150.50.4.0/24 [170/2195456] via 170.1.15.9, 00:09:26, Ethernet0
The strange part made me confused is the summary route.
Both routers learned the summary route from each other.
On R9 the learned summary is
D 4.0.0.0/8 [90/409600] via 170.1.15.13, 00:09:01, Ethernet0/0
On BB3 the learned summary is
D 172.16.0.0/16 [90/2195456] via 170.1.15.9, 00:09:26, Ethernet0
Why do they both have administrative distance "90" rather than "5"?
The theory I've learned is eigrp summary route should have ad of "5".
Regards,
Lin
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Monday, November 28, 2005 9:23 AM
To: 'Primetek_Easyman'; 'GroupStudy CCIE-Lab'
Subject: RE: Eigrp Secondary address question ?
You can form the relationship, but then your neighbors will complain about
"Neighbor not on common subnet" and ignore any routes.
Fix the IPs!
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Primetek_Easyman
Sent: Sunday, November 27, 2005 8:02 PM
To: GroupStudy CCIE-Lab
Subject: Eigrp Secondary address question ?
Dear Group Study gurus:
I have a question about secondary address issue in eigrp.
Is it possible to forming adjacency from different primary network addresses
on two routers?
This is an imaginary scenario.
Say two routers -- R1 and R2
R1(e0/0) -----------------(e0/0)R2
R1
Interface e0/0
Ip address 1.1.1.1 255.255.255.0
Ip address 1.1.2.1 255.255.255.0 secondary Router eigrp 1 Network 1.0.0.0
R2
Interface e0/0
Ip address 1.1.2.2 255.255.255.0
Router eigrp 1
Network 1.0.0.0
In rip world we have an option called "no validate-update-source" to conquer
this restriction.
But after searching the CCO I could not find the equivalent as above in
eigrp world.
Can we still have the adjacency forming up without change the primary or
secondary address?
Thanks
Lin
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:08 GMT-3