From: Simon Hope (shope@xxxxxxxxxxx)
Date: Thu Feb 15 2001 - 13:53:01 GMT-3
You also shouldnt confuse connected interfaces that happen to also be in
ISIS (or any other protocol). The important thing is to see what process has
introduced them to your routing table. In this case it will be the CONNECTED
"process"
If its not in your routing table with an "i L1" or "iL2" next to it, then no
amount of redistribution is going to get it into ospf, even if its in your
ISIS LS database etc etc
If the question doesnt permit you putting the loopbacks directly into the
OSPF network process (by making them passive interfaces as curtis
suggested), then you have to redistribute connected to get them in. Use a
filter to control which connected interfaces go into OSPF and which dont.
Simon
----- Original Message -----
From: "Curtis Call" <curtiscall@home.com>
To: "Kyle Galusha" <kgalusha@cisco.com>
Cc: <ccielab@groupstudy.com>
Sent: Thursday, February 15, 2001 3:39 PM
Subject: Re: ISIS to OSPF
> Why not just make them passive OSPF interfaces? It seems silly to
> redistribute a router's own links.
>
> At 07:36 AM 2/15/01 -0600, you wrote:
> >I went through the archives and someone had asked a similar question a
> >while back but didn't get an answer (but did mention the issue was in
> >bootcamp lab17).
> >
> >Here is the issue. Is there a trick to redistributing connected
> >(loopbacks) ISIS networks into OSPF if the loopback/networks are on the
> >redistributing router. I can get all the ospf routes into the isis
domain
> >but the directly connected isis loopbacks don't seem to get into isis.
> >Other isis routes (including isis loopbacks on other ISIS routers do
> >redistribute into ospf).
> >
> >The loopbacks look something like this on the mutually redistribution
router
> >
> >inter lo38
> >ip address 38.38.38.1 255.255.255.0
> >ip router isis
> >
> >int lo99
> >ip addr 99.99.99.1 255.255.255.0
> >ip router isis
> >
> >I am using route-maps with prefix-list to stop any route feedback.
> >
> >
> >Thanks,
> >Kyle
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:49 GMT-3