From: Nigel Taylor (nigel_taylor@xxxxxxxxxxx)
Date: Tue Aug 28 2001 - 09:16:08 GMT-3
Voytek,
The problem here is that NSSA area does not accept type 5
LSa's. In this scenario R3 is the NSSA ABR, and R4 is the NSSA ASBR. Since
you already redistributed connected the loopback on R1 possibly to meet a
requirement, then you can look at using the "area 1 range" command which
would generate a type 3. LSA(network summary) allowing those routes to get
through to the NSSA area and to IGRP.
The other question here would be is all of the addressing classfull or not.
Because depending on the nature of the mask and how the addressing scheme is
implemented you could still have a problem getting that route to show up on
R5(VLSM <-> FLSM issues)
HTH
You might want to try reading the RFC 2328. Doyle's - Routing TCP/IP is a
good text to have also..
Nigel..
Anyone care to add to this...
----- Original Message -----
From: Voytek Mielczarek <Voytek.Mielczarek@nec.com.au>
To: <ccielab@groupstudy.com>
Sent: Tuesday, August 28, 2001 3:05 AM
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
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:59 GMT-3