Thanks all for your replies, they're really helping to make me think about this.
Bob - my problem is the opposite, on the LAN I only see the route advertised by
R2 and therefore I concluded it must be becasue of split horizon.
Here is the topology -
Sw1----R12---R1--|
| |
192.168.101.0/24-| |-------R3
| |
Sw2-------R2-------|-------R4
Having a better look at it, R1 is learning the prefix from R12 and from the LAN
(advertised by R2) with the same metric which also has implication on load
balancing from R1 which I had not thought about.
R1#show ip route 192.168.101.0
Routing entry for 192.168.101.0/24
Known via "eigrp 1", distance 90, metric 3584, type internal
Redistributing via eigrp 1
Last update from 192.168.238.231 on Vlan699, 4d01h ago
Routing Descriptor Blocks:
192.168.238.231, from 192.168.238.231, 4d01h ago, via Vlan699 *********R2
Route metric is 3584, traffic share count is 1
Total delay is 40 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 11/255, Hops 3
* 192.168.219.173, from 192.168.219.173, 4d01h ago, via GigabitEthernet2/13
********** R12
Route metric is 3584, traffic share count is 1
Total delay is 40 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 3
So I suppose, it is indeed split horizon stopping R1 to advertise the prefix on
the LAN as it is a *best* route. Taking this a step further, what would happen
if I made the metric for that prefix look little worse on the LAN as far as R1
is concerned with an offset list? I suppose testing would be one answer, as
this is a live network I would have to replicate it in the lab.
Fulvio
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
http://onlinestudylist.com/mailman/listinfo/ccie_rs