AW: Redistributing variably subnetted routes from OSPF into RIP (+default-route)

From: Markus Haas (mh@xxxxxxxxxxxxx)
Date: Sun Apr 01 2001 - 12:39:42 GMT-3


   
Hi Nigel,

R2 is getting the default-route from R1. I configured on R1
"area 1 nssa default-information-originate" on R1.
R2 see the default-route from R1 and the "Gateway of
last resort will set proper. Look:

R2#sh ip route
.
.
Gateway of last resort is 192.168.0.1 to network 0.0.0.0
.
.
   11.0.0.0/32 is subnetted, 1 subnets
O IA 11.11.11.11 [110/65] via 192.168.0.1, 00:19:10, Serial1
C 192.168.0.0/24 is directly connected, Serial1
O*N2 0.0.0.0/0 [110/1] via 192.168.0.1, 00:14:28, Serial1

On R2 I redistribute the Network 192.168.0.0/24 and 11.11.11.0/24
into the RIP domain. That's working fine and I see the OSPF routes
inside the RIP domain. Look:

R3#sh ip route
.
.
Gateway of last resort is not set
.
.
R 11.0.0.0/8 [120/10] via 10.1.3.1, 00:00:18, Ethernet0
R 192.168.0.0/24 [120/1] via 10.1.3.1, 00:00:18, Ethernet0

The problem is that the RIP don't pick the default-route and propagate
it within RIP. I tried the command "default-information originate" on R2
under the rip process. But it doen't work.
Any other idea's ? I will also read Doyle. Maybe he has an answer for me.

Markus

> -----Urspr|ngliche Nachricht-----
> Von: Nigel Taylor [mailto:nigel_taylor@hotmail.com]
> Gesendet: Sonntag, 1. April 2001 16:37
> An: Markus Haas; A.Strobel
> Cc: CCIELAB
> Betreff: Re: Redistributing variably subnetted routes from OSPF into RIP
> (+default-route)
>
>
> Marcus,
> My first question is "how is r2 getting the default-route
> from r1 now...? There's actually a couple of ways to get your desired
> results in this scenario.
>
> 1. If all you need is a default-route to propagate into your rip domain
> then the "area X nssa default-information originate on the NSSA ABR should
> get this done.
> 2. If you have specific requirements to filter IA(type 3&4 LSAs) then the
> "area X nssa no-summary" will fulfill this requirement.
>
> Check out Doyle's book on page 537-544, there are some great examples
> there..
>
> HTH
>
> Nigel..
>
>
> ----- Original Message -----
> From: Markus Haas <mh@nmc-m.dtag.de>
> To: A.Strobel <anja10@usa.net>
> Cc: CCIELAB <ccielab@groupstudy.com>
> Sent: Sunday, April 01, 2001 5:49 AM
> Subject: AW: Redistributing variably subnetted routes from OSPF into RIP
> (+default-route)
>
>
> > Hi,
> >
> > I have a similar problem too. I'am dealing with
> > default-routes between OSPP and RIPv1.
> >
> > R1--<OSPF>--R2--<RIP>--R3
> >
> > R1= NSSA ABR
> > R2= NSSA ASBR
> > R3= RIPv1 only
> >
> >
> > My problem is that I want to use the default-route
> > who's R2 is receiving from R1 inside my RIP domain.
> > I tried several thing's, but I cant get it running.
> > Have you an idea how it would work
> >
> > Markus
> >
> > > -----Urspr|ngliche Nachricht-----
> > > Von: nobody@groupstudy.com [mailto:nobody@groupstudy.com]Im
> Auftrag von
> > > A.Strobel
> > > Gesendet: Samstag, 31. Mdrz 2001 13:10
> > > An: ccielab@groupstudy.com
> > > Betreff: Redistributing variably subnetted routes from OSPF into RIP
> > >
> > >
> > > Redistributing variably subnetted routes from OSPF into RIP
> > >
> > > R3---<OSPF--<<-R2--->>>RIP-->>R1
> > >
> > > R2 is the ASBR
> > >
> > > I know one way to accomplish this is to summarize the routes and
> > > use of "IP
> > > route xxxx null0" on R2.
> > >
> > > Correct me if I am wrong, but the other solution is the use of " ip
> > > default-network xxx " on R1.
> > > This works and I can reach the VLSM routes of R3 from R1, but
> something
> > > strange happens:
> > > After I enter the command
> > >
> > > config t
> > > ip default-network 10.1.3.0 (10.1.3.0 is on R3, with
> RIP-compatible
> > > mask)
> > > end
> > > show run
> > > .
> > > .
> > > .
> > > ip route 10.0.0.0 255.0.0.0 10.1.3.0
> > >
> > > As you see, my "ip default-network" command changes into "ip
> > > route" command!
> > >
> > > Is this behavior normal?
> > >
> > >
> > > I am puzzled. Any light would be appreciated
> > >
> > > A. Strobel
> > >
> > >
> > >
> > >
> > >
> > >
> > >



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:38 GMT-3