From: Sergey (public@svlp.net)
Date: Sun Aug 19 2007 - 07:41:38 ART
R3---R1---R2
Link between R3 & R1 is PPP, between R1 & R2 FR
EIGRP is routing protocol
R1 config
interface Serial1/1
description Link to R3
ip address 164.1.13.1 255.255.255.0
encapsulation ppp
interface Serial1/0
description Link to R2
ip address 164.1.12.1 255.255.255.0
encapsulation frame-relay
router eigrp 10
network 164.1.12.1 0.0.0.0
network 164.1.13.1 0.0.0.0
Rack1R1#sh ip ro 164.1.13.3
Routing entry for 164.1.13.3/32
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via eigrp 10
Advertised by eigrp 10
Routing Descriptor Blocks:
* directly connected, via Serial1/1
Route metric is 0, traffic share count is 1
Ok it is normal, it is ppp peer neighbor-route,
but why eigrp process advertise it in eigrp domain?? Other routing protocols don't do it.
Rack1R2#sh ip ro 164.1.13.3
Routing entry for 164.1.13.3/32
Known via "eigrp 10", distance 90, metric 11023872, type internal
Redistributing via eigrp 10
Last update from 164.1.12.1 on Serial1/0.12, 00:14:30 ago
Routing Descriptor Blocks:
* 164.1.12.1, from 164.1.12.1, 00:14:30 ago, via Serial1/0.12
PS: Explain please what do keywords "Known via", "Redistributing via" and "Advertised by" mean?
Rack1R3#sh ip ro 164.1.12.0
Routing entry for 164.1.12.0/24
Known via "eigrp 10", distance 90, metric 18063872, type internal
Redistributing via eigrp 10, ospf 10
Advertised by ospf 10 subnets
Last update from 164.1.13.1 on Serial1/2, 00:08:38 ago
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:12 ART