From: Pearson John (jnhpearson@yahoo.co.jp)
Date: Wed Apr 20 2005 - 22:26:32 GMT-3
Hi Lanny and Paresh,
You should keep in mind that when redistributing IS-IS
into another routing protocol, the connected routes in the
IS-IS domain on that router are not injected. They need to
be redistributed as connected routes into the target
routing protocol.
Cheers,
John
--- Paresh Khatri <Paresh.Khatri@aapt.com.au> $B$+$i$N%a%C(B
$B%;!<%8!'(B
> Hi Lanny,
>
> When redistributing routes, routes for the connected
> interfaces over which the "source" protocol is
> running are injected as well...
>
> HTH,
> Paresh.
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com]On Behalf Of
> Lanny Ballard
> Sent: Thursday, 21 April 2005 10:34 AM
> To: ccielab@groupstudy.com
> Subject: route redistribution question
>
>
> I am doing yet another route redistribution lab, and
> i have a question
> I was under the assumption that in order to
> redistribut a route into a
> routing protocol, that route had to be in the rout
> table; however, i have
> done a lab recently where I was redistribution ospf
> into eigrp, and eigrp
> advertised a route that was connected, and not an
> ospf route.
>
> here is the example.
>
> route 5 is mutually redistributing between ospf and
> eigrp.
> Now if you notice I have added 10.5.5.5 to the ospf
> process. This address
> is a loopback interface. But eigrp is also
> advertising it. Why is this? I
> thought eigrp should only advertise this route if it
> was in the route table
> as an ospf route, but it is in the route table as
> connected.
>
> C 10.5.5.0 is directly connected, Loopback0
>
>
> router eigrp 100
> redistribute ospf 1 metric 1544 100 255 1 1500
> network 172.150.1.5 0.0.0.0
> no auto-summary
> !
> router ospf 1
> router-id 10.5.5.5
> log-adjacency-changes
> area 0 authentication message-digest
> area 1 nssa default-information-originate
> redistribute eigrp 100 metric 10 subnets
> network 10.5.5.5 0.0.0.0 area 0
> network 172.150.5.5 0.0.0.0 area 0
> network 172.150.8.5 0.0.0.0 area 1
> neighbor 172.150.5.6
> neighbor 172.150.5.2
>
>
>
>
> TIA for any help!
> Lanny
>
>
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:55:05 GMT-3