RE: redistribute ospf to igrp again

From: Omer Ansari (omer@ansari.com)
Date: Wed Sep 04 2002 - 20:24:12 GMT-3


howdy,

two questions:

1. amongst the VLSM/FLSM resolution techniques, i've heard/tried several
options:

secondary address
tunnelling
area X range/summary-address
ip summary-address eigrp
etc etc..

is the touted secondary address solution the one you presented below?

also, my reasoning behind its working:
note that the /30 route is in the IGRP db also on the ASBR, however,
when it gets redist'ed to OSPF, ospf rejects it because it already sees
this route as connected..however a secondary address on which ospf is not
running, would then get redist'ed into ospf, seen as an External LSA.
and then the summary-address would do its magic.

in other words if we had
router ospf X
network 172.16.0.0 0.0.255.255 area X

this solution would not work. correct?

2. remember we once discussed this, when you and I were learning this
method, and i mentioned using a loopback interface for 172.16.0.1/24 but
the idea was shot down.

just want to make sure why that would be a bad idea, b/c i still like
using it :)

regards,
Omer

On Wed, 4 Sep 2002, Volkov, Dmitry (Toronto - BCE) wrote:

> Hello,
>
> Since R2 is not ABR but ASBR we can not use area range command.
> I case if You are doing redistr between OSPF and IGRP You can just put
> "summary-address 172.16.0.0 255.255.255.0" under OSPF process on R2
> It will create automatically route to Null
> This route will be propagated into IGRP.
> You can also just put secondary address (like 172.16.0.1/24) on R2 interface
> faced to R1
>
> Dmitry
>
> > -----Original Message-----
> > From: elping [mailto:elpingu@acedsl.com]
> > Sent: Tuesday, September 03, 2002 12:37 AM
> > To: frank.yu@japan.bnpparibas.com
> > Cc: ccielab@groupstudy.com
> > Subject: Re: redistribute ospf to igrp again
> >
> >
> > do an area range command for the /30
> >
> > frank.yu@japan.bnpparibas.com wrote:
> >
> > > Group,
> > >
> > > As you can see the following diagram, R2 is ospf
> > ASBR and running
> > > igrp too.
> > > My question is how can R3 reach ospf area0, except
> > R2 advertising a
> > > default route to igrp?
> > > Is there a way for R2 to summary the ospf backbone
> > into 24bit route
> > > and redistribute it to igrp domain?
> > > Thanks!
> > >
> > > 172.16.0.0/30 172.16.1.0/24
> > > R1-------------------R2--------------------R3
> > > ospf area0 igrp
> > >
> > > Frank
> > >
> > > This message and any attachments (the "message") is
> > > intended solely for the addressees and is confidential.
> > > If you receive this message in error, please delete it and
> > > immediately notify the sender. Any use not in accord with
> > > its purpose, any dissemination or disclosure, either whole
> > > or partial, is prohibited except formal approval. The internet
> > > can not guarantee the integrity of this message.
> > > BNP PARIBAS (and its subsidiaries) shall (will) not
> > > therefore be liable for the message if modified.
> > >
> > > ---------------------------------------------
> > >
> > > Ce message et toutes les pieces jointes (ci-apres le
> > > "message") sont etablis a l'intention exclusive de ses
> > > destinataires et sont confidentiels. Si vous recevez ce
> > > message par erreur, merci de le detruire et d'en avertir
> > > immediatement l'expediteur. Toute utilisation de ce
> > > message non conforme a sa destination, toute diffusion
> > > ou toute publication, totale ou partielle, est interdite, sauf
> > > autorisation expresse. L'internet ne permettant pas
> > > d'assurer l'integrite de ce message, BNP PARIBAS (et ses
> > > filiales) decline(nt) toute responsabilite au titre de ce
> > > message, dans l'hypothese ou il aurait ete modifie.



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:44 GMT-3