From: Edward Taggart (etaggart@xxxxxxxxx)
Date: Mon Sep 27 1999 - 19:58:31 GMT-3
Peter, Rather than trying to inject a default route into your IGRP network,
if you are simply attempting to solve the vlsm/flsm redistribution problem
could you summarize your non 24 bit addresses on your ospf network to 24 bit
addresses so they will properly redistribute into igrp?
- Ed
-----Original Message-----
From: Peter Van Oene <vantech@sympatico.ca>
To: Chad Marsh <chad@wa.net>
Cc: ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Monday, September 27, 1999 1:08 PM
Subject: Re: OSPF NSSA Default;'s!!
>I like this idea Chad.
>
>The overall limitations that I have that Cheryl made reference too are not
>of a real world nature. I'm simply working things in odd ways to ensure
>that I know them well enough to answer CCIE lab questions.
>
>Thanks again all for the good answers!
>
>Peter Van Oene
>Senior Systems Engineer
>UNIS LUMIN Inc.
>www.unislumin.com
>
>----- Original Message -----
>From: Chad Marsh <chad@wa.net>
>To: Peter Van Oene <vantech@sympatico.ca>
>Cc: <ccielab@groupstudy.com>
>Sent: Monday, September 27, 1999 9:49 AM
>Subject: Re: OSPF NSSA Default;'s!!
>
>
>> Peter, the only way (as far as I know) to get a default route into an
>> IGRP speaking router is to use the 'ip default-network' command.
>> You can either put it on R1 and have it advertised, or put it on R6
>> directly.
>> It does not matter if it is the same default route that you are
>> propagating through your OSPF domain.
>> I am assuming your IGRP domain is a stub network, so all you have to do
>> is get it to default to anything that has a valid next hop of R1, R1 is
>> wise and will know the correct way to route the packet.
>> The 'ip default-network' must reference a classful network, and R6 must
>> have an entry for that classful network (not just a subnet of it) in
>> it's routing table.
>> If you don't have a candidate routing entry that meets that criteria,
>> here is an easy way to spoof it:
>> Creat a loopback on R1, (careful about affecting your OSPF RID) say
>> 172.16.1.1 255.255.0.0, and add this network to IGRP. Then on either R1
>> or R6, add 'ip default-network 172.16.0.0'
>> That should do the trick, R6 will send unknown packets to R1, which will
>> then forward them to the "correct' default route.
>>
>> Hope that helps,
>>
>> Chad
>>
>>
>> Peter Van Oene wrote:
>> >
>> > Heres the final Config. Just an aside however, I still can't get a
>default
>> > route to hit the IGRP side :)
>> >
>> > R5
>> >
>> > router ospf 1
>> > network 150.100.1.6 0.0.0.0 area 1
>> > network 150.100.10.9 0.0.0.0 area 0
>> > network 150.100.10.19 0.0.0.0 area 0
>> > default-information originate always
>> > area 0 range 150.100.10.0 255.255.255.0
>> > area 1 nssa default-information-originate
>> > !
>> > ip classless
>> > ip route 0.0.0.0 0.0.0.0 150.100.10.17
>> > ip route 150.100.10.0 255.255.255.0 Null0
>> >
>> > R1
>> >
>> > router ospf 1
>> > redistribute igrp 1 subnets
>> > network 150.100.1.5 0.0.0.0 area 1
>> > network 150.100.1.250 0.0.0.0 area 1
>> > area 1 nssa
>> > !
>> >
>> > Peter Van Oene
>> > Senior Systems Engineer
>> > UNIS LUMIN Inc.
>> > www.unislumin.com
>> >
>> > ----- Original Message -----
>> > From: Richardson, Cheryl <cheryl.richardson@lmco.com>
>> > To: 'Peter Van Oene' <vantech@sympatico.ca>
>> > Sent: Monday, September 27, 1999 7:58 AM
>> > Subject: RE: OSPF NSSA Default;'s!!
>> >
>> > > Your welcome. So what did the final configuration look like?
>> > >
>> > > Cheryl
>> > >
>> > > > -----Original Message-----
>> > > > From: Peter Van Oene [SMTP:vantech@sympatico.ca]
>> > > > Sent: Monday, September 27, 1999 1:44 PM
>> > > > To: Richardson, Cheryl
>> > > > Subject: Re: OSPF NSSA Default;'s!!
>> > > >
>> > > > Ahhh.. That did it.. My understanding of the default-info orig
>statement
>> > > > was incorrect. Many books reference it as a redistribution
oriented
>> > > > command
>> > > > which I suppose it is, but it added an ambiguity. I had thought it
>> > > > instructed the router to redistribute the 0.0.0.0 route to another
>> > routing
>> > > > protocol. However it obviously means redist the 0.0.0.0 route to
>the
>> > OSPF
>> > > > domain regardless of where the 0.0.0.0 route was learned.
>> > > >
>> > > > Thanks for your insight
>> > > >
>> > > >
>> > > > Peter Van Oene
>> > > > Senior Systems Engineer
>> > > > UNIS LUMIN Inc.
>> > > > www.unislumin.com
>> > > >
>> > > > ----- Original Message -----
>> > > > From: Richardson, Cheryl <cheryl.richardson@lmco.com>
>> > > > To: 'Peter Van Oene' <vantech@sympatico.ca>
>> > > > Sent: Monday, September 27, 1999 7:30 AM
>> > > > Subject: RE: OSPF NSSA Default;'s!!
>> > > >
>> > > >
>> > > > > Hi Peter,
>> > > > > Does R5 have a 0.0.0.0 entry in it's routing table? Have you
>tried
>> > > > the
>> > > > > always keyword? or even "default-information originate" under
ospf
>1?
>> > > > Not
>> > > > > just on the nssa statement..
>> > > > >
>> > > > > Cheryl Richardson
>> > > > >
>> > > > > > -----Original Message-----
>> > > > > > From: Peter Van Oene [SMTP:vantech@sympatico.ca]
>> > > > > > Sent: Monday, September 27, 1999 12:49 PM
>> > > > > > To: ccielab@groupstudy.com
>> > > > > > Subject: OSPF NSSA Default;'s!!
>> > > > > >
>> > > > > > Ok, 3 days before my lab and I'm going nuts:)
>> > > > > >
>> > > > > > I have the following R6 IGRP R1 Ospf R5
>> > > > > >
>> > > > > > R1 is area 1
>> > > > > > R5 is ABR
>> > > > > >
>> > > > > > Area 1 is nssa.
>> > > > > >
>> > > > > > I wish to propogate a default route to eventually R6, but first
>to
>> > R1
>> > > > from
>> > > > > > 5.
>> > > > > >
>> > > > > > my R5 config looks like this
>> > > > > >
>> > > > > > router ospf 1
>> > > > > > network 150.100.1.6 0.0.0.0 area 1
>> > > > > > network 150.100.10.9 0.0.0.0 area 0
>> > > > > > network 150.100.10.19 0.0.0.0 area 0
>> > > > > > area 0 range 150.100.10.0 255.255.255.0
>> > > > > > area 1 nssa default-information-originate
>> > > > > >
>> > > > > > However on my R1, I see no type 7 LSA for 0.0.0.0 and obviously
>> > > > > > no route shows up in the routing table. I'm losing my mind!
>> > > > > >
>> > > > > > Any thoughts?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Peter Van Oene
>> > > > > > Senior Systems Engineer
>> > > > > > UNIS LUMIN Inc.
>> > > > > > www.unislumin.com
>> > > > > >
>> > > > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:51 GMT-3