Can anyone explain the following curious behaviour?
I have three routers, each of which has directly-connected
interfaces to a Vlan812 and a static pointing to a connected
next-hop out of that interface. The statics on two of the
routers (down-3 & cent-8) have their admin distances set to
200. Vlan812 is up on all the routers. The statics are covered
by OSPF 'network' statements, and also redistributed as external
type E1 routes.
Why is it that cent-8 is ignoring the directly-connected next-
hop in favour of the OSPF next-hop from cent-3's redistributed
static, whilst down-3 is honouring its own static and ignoring
the OSPF next-hop from cent-3 ? Is this a new innovation that
allows one to override directly-connected next-hops, which is
only available in newer IOS versions or similar (the versions
are as follows: cent-3: 12.1(7a)E1, cent-8: 12.0(10)W5(18a),
down-3: 12.0(19). References to the Fine Manual appreciated. :-)
route-cent-3.cam.ac.uk#show ip route 131.111.227.0
Routing entry for 131.111.227.0/24
Known via "static", distance 1, metric 0
Redistributing via ospf 1
Advertised by ospf 1 metric-type 1 subnets
Routing Descriptor Blocks:
* 131.111.12.94
Route metric is 0, traffic share count is 1
route-down-3.cam.ac.uk#show ip route 131.111.227.0
Routing entry for 131.111.227.0/24
Known via "static", distance 200, metric 0
Redistributing via ospf 1
Advertised by ospf 1 metric-type 1 subnets
Routing Descriptor Blocks:
* 131.111.12.94
Route metric is 0, traffic share count is 1
route-cent-8.cam.ac.uk#show ip route 131.111.227.0
Routing entry for 131.111.227.0/24
Known via "ospf 1", distance 110, metric 30, type extern 1
Redistributing via ospf 1
Last update from 131.111.2.3 on Vlan99, 12:36:23 ago
Routing Descriptor Blocks:
* 131.111.2.3, from 192.153.213.45, 12:36:23 ago, via Vlan99
Route metric is 30, traffic share count is 1
Cheers,
M.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:52 EDT