[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-ospf
Subject:    Re: Cisco OSPF question
From:       Chris Whyte <cwhyte () CISCO ! COM>
Date:       1998-11-10 23:40:14
[Download RAW message or body]


If memory serves, it depends on how Router A loses it's connectivity to the
outside. For example, just loses it's adjacency (but not physical
connectivity) vs loses physical connectivity. I'm almost certain we treat
these two occurences differently.

The way we treat the former doesn't necessarily conform to the spec (again
if I remember correctly). But conforming to the spec isn't always the best
thing to do either. There were some good reasons why we do what we do but I
suggest you address this issue through better channels as this mailing list
is not intended to deal with cisco related OSPF issues.

Using Open Forum on CCO, send an e-mail to cisco@spot.colorado.edu or work
through your local SE. Meanwhile I'll dig through my notes or see if I can
remember our reasons and respond directly.

Thanks,

Chris

At 04:35 PM 11/10/98 +0100, Derick Winkworth wrote:
>Consider the following Configuration:
>
>Routers A and B are running IOS v10.2 (7).  Both have links to "the rest of
>the world."  So I put the following line under each router's config:
>"default-information originate metric-type 1".  So each router advertises a
>default-route as long as it has a default-route itself (which in this
>instant both are receiving from routers outside of our network via IGRP)..
>
>So in every single router's OSPF database on our network there are two AS
>external paths 0.0.0.0, each path has a different metric depending on how
>close a particular router is to Router A or Router B.
>
>This works okay.  The problem is when Router A loses it's outside
>connectivity.  It loses it's default-route from IGRP, so it stops
>advertising 0.0.0.0.  I would think that Router A would, at this point,
>recognize the 0.0.0.0 being advertised by Router B...  Unfortunately it will
>not.
>
>Is OSPF supposed to do this?  Is this a Cisco thing?
>
>Derick
>

[prev in list] [next in list] [prev in thread] [next in thread]