From: Muralidhar Devarasetty (dhar_murali@xxxxxxxxxxx)
Date: Wed Nov 03 1999 - 11:51:13 GMT-3
javier,
The problem here is since the 137.12.0.0 is major class of the N/W
(137.12.12.0) and it is dicontiguous R2 will treat that r1 is directly
connected to this N/W and never send this update to R1.
If this update reaches R1 then ipclassless will eork fine.but now the
problem is R1 will never get this route from R2(Update will be suppresed at
R2 itself).
Any idea???????
Murali
----Original Message Follows----
From: GRIZZUTI Javier <jgrizzut@softnet.com.ar>
Reply-To: GRIZZUTI Javier <jgrizzut@softnet.com.ar>
To: Muralidhar Devarasetty <dhar_murali@hotmail.com>
CC: ccielab@groupstudy.com
Subject: RE: OSPF NSSA Default;'s!!
Date: Tue, 2 Nov 1999 18:51:13 -0300
Devarasetty
In my opinion you should configure default-network 137.12.0.0 on router R2 (
where I supose you will make the redistribution IGRP->OSPF ) , you should
configure ip classless on R1 , this will allow R1 to apply its ip mask to
the default information.
Javier Grizzuti
-----Original Message-----
From: Muralidhar Devarasetty [mailto:dhar_murali@hotmail.com]
Sent: Tuesday, November 02, 1999 3:41 PM
To: vantech@sympatico.ca; chad@wa.net
Cc: ccielab@groupstudy.com
Subject: Re: OSPF NSSA Default;'s!!
Hi all,
I was just working with similar setup but facing some problems.
137.12.12.0/24 137.12.23.0/24
---(e0)R1(s0)--------(s0)R2(s1)------------(s0)R3(e0)---
137.12.1.1/24 137.12.3.0/24
R2 and R3 are running with ospf.And R1 and R2 are running IGRP.
All the interfaces are using same major network for ex:-137.12.x.x with 24
bit mask.
If I want to avoide redistribution of OSPF in to IGRP and use default
network command
In R2 under IGRP I would include
ip default-network 137.12.23.0 (which is actually OSPF route)and since I am
runnign IGRP on 137.12.0.0 this default network will be automatically
included in IGRP eventhough it is OSPF netwok.
and expect every thing work and all routers in R1 side to ping all the OSPF
networks thr' default netwok.
here is my problem.When I include default-network 137.12.23.0 it is
taking as classfull i.e. 137.12.0.0, and R2 is not advertising this
137.12.0.0 to R1 since it belongs to same major N/W used in
R1-R2 WAN interface. So norouter in IGRP (including R1) are aware of default
netwok.Process may work fine if the major N/W is different how do U resolve
this ?
Any ideas??????? Any input will be appriciated.
Thanks in advance..
Muralidhar
----Original Message Follows----
From: "Peter Van Oene" <vantech@sympatico.ca>
Reply-To: "Peter Van Oene" <vantech@sympatico.ca>
To: "Chad Marsh" <chad@wa.net>
CC: <ccielab@groupstudy.com>
Subject: Re: OSPF NSSA Default;'s!!
Date: Mon, 27 Sep 1999 13:01:42 -0700
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:55 GMT-3