Re: Setting distance on statics to connected next-hops

From: Martin Cooper (mjc@cooper.org.uk)
Date: Tue Oct 23 2001 - 09:41:42 EDT


Ryan O'Connell <ryan@complicity.co.uk> writes:

> On Tue, Oct 23, 2001 at 04:21:12AM +0100, Martin Cooper wrote:
> > 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.
>
> [snip]
>
> The admin distance of you've set on your statics (200) is higher
> than the admin distance of OSPF, so OSPF will be preferred. It
> looks like down-3 isn't learning the OSPF route for some reason.

Except it is... :-)

route-down-3.cam.ac.uk#show ip ospf database external 131.111.227.0

       OSPF Router with ID (192.153.213.107) (Process ID 1)

                Type-5 AS External Link States

  Routing Bit Set on this LSA
  LS age: 1045
  Options: (No TOS-capability, DC)
  LS Type: AS External Link
  Link State ID: 131.111.227.0 (External Network Number )
  Advertising Router: 192.153.213.45
  LS Seq Number: 80000013
  Checksum: 0xB8C4
  Length: 36
  Network Mask: /24
        Metric Type: 1 (Comparable directly to link state metric)
        TOS: 0
        Metric: 20
        Forward Address: 131.111.12.94
        External Route Tag: 0

M.



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:52 EDT