From: Nigel Taylor (nigel_taylor@xxxxxxxxxxx)
Date: Tue Aug 28 2001 - 09:24:30 GMT-3
Michael,
Just to think through this.. suppose your entire network was
addressed with the same network (i.e 172.16.10.x). How is R5 able to ping
the R1 loopback... Now remember that IGRP does not understand 0/0 (default
routes). So how exactly is this going to work... :->
Nigel.. let's put on our thinking caps..
----- Original Message -----
From: Michael Wong <Michael.Wong@nec.com.au>
To: Voytek Mielczarek <Voytek.Mielczarek@nec.com.au>;
<ccielab@groupstudy.com>
Sent: Tuesday, August 28, 2001 7:28 AM
Subject: RE: ospf nssa backwards
> Voytek
>
> RFC1587 page 3 pretty much sums up the answer to your question ....
quote-unquote.
>
> o Type-7 LSAs may be originated by and advertised
> throughout an NSSA; as with stub areas, NSSA's do not
> receive or originate type-5 LSAs.
>
> Reading this statement, I interpret it as NSSA's are like stub areas and
do not permit type-5 LSA's. Your connected loopbacks at R1 are considered
type 5 LSA's and therefore would not enter the NSSA. You shouldn't really
need the connected routes entering the NSSA, a default route injected into
the NSSA should do the trick.
>
> Your thoughts ..... MW :)
>
>
>
> -----Original Message-----
> From: Voytek Mielczarek
> Sent: Tuesday, 28 August 2001 5:05 pm
> To: ccielab@groupstudy.com
> Subject: ospf nssa backwards
>
>
> Group,
>
> How would you get routes E1 or E2 through NSSA as below:
>
>
> area1 area0 nssa IGRP
> R1----------R2----------R3----------R4----------R5
>
>
> Loopback interfaces on R1 get "redistributed connected" and appear on R3
as E2 routes, but do not appear on R4.
> They need to be propagated across nssa out to IGRP. Is this a mission
impossible?
>
> Thanks, Voytek
> **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:59 GMT-3