From: Daniel C. Young (danyoung99@xxxxxxxxxxxx)
Date: Sat May 26 2001 - 16:38:55 GMT-3
I'm guessing that since you only have one router, OSPF may only consider
those loopbacks as connected interfaces. Loopbacks, when redistributed, are
usually considered as host routes. Perhaps since you only have a single
router, you won't see them in the database and the routing table unless they
are summarized. If these loopbacks are included in the network statement,
then OSPF will naturally generate type-3 LSAs for them.
Don't know, Guy. That does sound very strange. Try to connect to another
router, perhaps you will see something. Let me know.
Daniel C. Young
Sr. Network Engineer
CCNP (ATM, Security & Voice Specialist),
CCDP, CCSE, MCSE+I
SBC Internet Data Center
(949) 221-1928 Work
(714) 350-8945 Cell
young@pobox.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Guy
Farber
Sent: Thursday, May 24, 2001 9:30 AM
To: W. Alan Robertson; ccielab@groupstudy.com
Subject: RE: Redistributing connected into ospf
Thanks Alan. Actually the setup is very simple - it's only one router with
some loopbacks so yeah everything is in area 0. And yes the I'm
redistributing with the "subnets" keyword.
-----Original Message-----
From: W. Alan Robertson [mailto:warobertson@earthlink.net]
Sent: Thu, May 24, 2001 6:24 PM
To: Guy Farber; ccielab@groupstudy.com
Subject: Re: Redistributing connected into ospf
The router where you are attempting to redistribute...
Is it in area 0, or another area?
If it's in another area, is the area configured as a stub, or
totally-stubbed
area? Stub and Totally-stubbed areas do not mix with external routes, which
is
what you end up with when redistributing. To preserve the 'stub' benefits
in a
non-zero area, but allow for external networks, look into the use of OSPF's
not-so-stubby-area features. NSSAs were specifically developed so that
ASBRs
would not have to exist in area 0. Prior to the NSSA, external routes had
to be
introduced into the OSPF routing domain by an ASBR in area 0. This
limitation
led to the growth of area 0, eventually leading to instability.
Another possibility is that you've ommitted the 'subnets' switch on your
redistribute command. Without it, the command will only redistribute the
connected networks if the interface masks jive along classful boundaries.
This
quirk leads most of us to always use the 'subnets' switch whenever we
redistribute into ospf. There is no case that I'm aware of where the
'subnets'
switch would have an adverse effect.
Hope this helps...
Alan
----- Original Message -----
From: "Guy Farber" <gfarber@cisco.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, May 24, 2001 11:14 AM
Subject: Redistributing connected into ospf
> Hi,
>
> When I'm redistributing connected networks into ospf they don't appear in
> the database. This only happens if those interfaces are running ospf at
the
> same time. Another thing I've noticed is that if I summarize these
networks
> they do appear in the database and the routing table. Can anyone explain?
>
> Guy
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:54 GMT-3