Re: redistribute OSPF routes into IGRP

From: John Conzone (jkconzone@xxxxxxxx)
Date: Sat Sep 02 2000 - 19:14:25 GMT-3


   
    Great! Thats what I had sort of. I redistributed connected from R5 into
R4, then did a default network statement to that network from R4. Not pretty
but it worked.
    I just got done with the first part and getting the 172.168.80 and
172.168.70 to ping from R4 was rough! My R4 default network sent it to R2
who did a recursive lookup and passed it to R5, but R5 doesn't do BGP and
didn't have routes to those nets so he dropped it.
    I ended up redistributing the external BGP routes into OSPF on R6 and
R1, and then using distribute list in on the OSPF processes of all the OSPF
proccess except R5 to stop the flaps. Now R4 pings just fine, but man is it
UGLY! Hey it works! Marc does it totally different but I wasn;t gonna redo 8
hours of work.
    I just wanted to make sure I was having one of my brain farts.
    Thanks!
----- Original Message -----
From: "Fred Ingham" <fningham@worldnet.att.net>
To: "John Conzone" <jkconzone@home.com>; "ccielab" <ccielab@groupstudy.com>
Sent: Saturday, September 02, 2000 1:28 PM
Subject: Re: redistribute OSPF routes into IGRP

> Do the default network thing. The default network should be in
> the r5 routing table and entered in the default network statement as a
> classful address. r4 should have the ip classless statement and ip
> split horizon enabled on s1.
>
> Redistribute ospf into igrp on r5.
>
> HTH, Fred.
>
> > John Conzone wrote:
> >
> > I am working on Lab 8, and am having a problem getting OSPF VLSM
> > routes into IGRP. Router 5 has 2 subs, one a OSPF multipoint link
> > addressed 137.20.100.34/27. The other sub is a IGRP interface
> > addressed 137.20.200.18/28 connected to 137.20.200.17/28 (router R4
> > running IGRP).
> > When I debug IGRP on R5 to see what he's sending to R4, he's only
> > sending the 200.200.200.0/24 and 200.200.100.0/24 routes. In other
> > words only the classful routes. The other routes to the 137.20.x.x
> > VLSM class B routes don't get sent.
> > So if the network on the link is 137.20.x.x with a 28 bit mask, no
> > routes for 137.20.x.x without a 28 bit mask will be sent, right?
> > Am I missing something? I've been doing all the oddball stuff for
> > a month and I'm boning back up on FLSM to VLSM redistribution. Anyway,
> > is there anyway to get R4 out to the other 137.20.x.x nets that don't
> > have a 28 bit mask without doing the deafult network thing? Here's a
> > copy of the debug from R5 as he send an IGRP update to R4:
> >
> > IGRP: sending update to 255.255.255.255 via Serial0.2 (137.20.200.17)
> > network 200.200.100.0, metric=5001
> > network 200.200.200.0, metric=5001
> > IGRP: Update contains 0 interior, 2 system, and 0 exterior routes.
> >
> > Route tables from R5 and R4 are below.
> > Thanks for any help you guys can offer.
> >
> >
> > John
> >
> > Routes form r5:
> >
> > r5#sho ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
> > BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * -
> > candidate default
> > U - per-user static route, o - ODR
> >
> > Gateway of last resort is not set
> >
> > 200.200.100.0/32 is subnetted, 1 subnets
> > O 200.200.100.1 [110/65] via 137.20.100.33, 00:14:25, Serial0.1
> > 137.20.0.0/16 is variably subnetted, 9 subnets, 5 masks
> > C 137.20.200.16/28 is directly connected, Serial0.2
> > C 137.20.25.0/24 is directly connected, Serial1
> > O IA 137.20.20.0/24 [110/74] via 137.20.100.33, 00:14:25, Serial0.1
> > I 137.20.40.16/28 [100/8486] via 137.20.200.18, 00:00:46,
> > Serial0.2
> > O 137.20.100.33/32 [110/64] via 137.20.100.33, 00:14:25,
> > Serial0.1
> > C 137.20.100.32/27 is directly connected, Serial0.1
> > O 137.20.100.35/32 [110/64] via 137.20.100.35, 00:14:25,
> > Serial0.1
> > C 137.20.64.0/20 is directly connected, Ethernet0
> > O 137.20.100.0/24 is a summary, 00:14:20, Null0
> > 200.200.200.0/32 is subnetted, 1 subnets
> > O 200.200.200.1 [110/65] via 137.20.25.1, 00:14:26, Serial1
> >
> > Routes from R4:
> >
> > r4#sho ip route
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B -
> > BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
> > inter area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> > Gateway of last resort is not set
> >
> > I 200.200.200.0/24 [100/8477] via 137.20.200.17, 00:00:34, Serial1
> > 137.20.0.0/28 is subnetted, 2 subnets
> > C 137.20.200.16 is directly connected, Serial1
> > C 137.20.40.16 is directly connected, FastEthernet0
> > I 200.200.100.0/24 [100/8477] via 137.20.200.17, 00
> >
> >
> >
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:51 GMT-3