From: Voytek Mielczarek (Voytek.Mielczarek@xxxxxxxxxx)
Date: Wed Aug 29 2001 - 11:24:07 GMT-3
Guys,
Thanks for all the responses. Tried the following:
1) "area X nssa default-information" command injected default route to the
nssa, but could not in any way "grab" it and pass to r4 router. "area X nssa no
-summary" command also tried but with much the same results. Any suggestions we
lcome. The routing table on R4 was:
r4#sh ip r
I 172.0.0.0/16 [100/8976] via 172.16.0.2, 00:00:43, Serial0/1
I 172.1.0.0/16 [100/8976] via 172.16.0.2, 00:00:43, Serial0/1
I 172.2.0.0/16 [100/8976] via 172.16.0.2, 00:00:43, Serial0/1
I 172.3.0.0/16 [100/8976] via 172.16.0.2, 00:00:43, Serial0/1
172.16.0.0/16 is variably subnetted, 7 subnets, 4 masks
O IA 172.16.150.0/24 [110/65] via 172.16.30.1, 00:05:44, FastEthernet0/0
C 172.16.50.0/27 is directly connected, Loopback0
O N2 172.16.35.0/28 [110/20] via 172.16.30.1, 00:05:45, FastEthernet0/0
C 172.16.30.0/28 is directly connected, FastEthernet0/0
O IA 172.16.10.0/24 [110/846] via 172.16.30.1, 00:05:43, FastEthernet0/0
C 172.16.0.0/24 is directly connected, Serial0/1
O N2 172.16.30.90/32 [110/20] via 172.16.30.1, 00:05:45, FastEthernet0/0
O*N2 0.0.0.0/0 [110/1] via 172.16.30.1, 00:05:45, FastEthernet0/0
r4#
2)Tried the "interface Virtual-TokenRing255" scenario. Michael, could you p
lease verify on which router this needs to be configured, in my case R4 is the
ASBR with both OSPF and IGRP.
3) Also observed (see above) that "redistributed-connected" loopbacks from
R3 get to R4 as N2. I suppose, for the two routes R3 is ASBR, but did not manag
e to redistribute them to IGRP either.
Please see brief config attached:
======================================
r1#sh run
!
interface Loopback0
ip address 172.16.10.129 255.255.255.255
!
interface Loopback1
ip address 172.16.10.193 255.255.255.240
!
interface Serial0/0
ip address 172.16.10.1 255.255.255.252
!
router ospf 64
redistribute connected subnets route-map loops
network 172.16.10.0 0.0.0.3 area 1
!
route-map loops permit 10
match interface Loopback0 Loopback1
r1#
========================================
r3#sh run
interface Loopback0
ip address 172.16.30.90 255.255.255.255
!
interface Loopback1
ip address 172.16.35.1 255.255.255.240
!
interface Ethernet0/0
ip address 172.16.30.1 255.255.255.240
!
interface Serial0/1
ip address 172.16.150.2 255.255.255.252
!
router ospf 64
area 0 range 172.16.150.0 255.255.255.0
area 2 nssa
redistribute connected subnets route-map loops
network 172.16.30.0 0.0.0.15 area 2
network 172.16.150.0 0.0.0.3 area 0
!
route-map loops permit 10
match interface Loopback0 Loopback1
r3#
=============================================
r4#
interface Loopback0
ip address 172.16.50.1 255.255.255.224
!
interface FastEthernet0/0
ip address 172.16.30.2 255.255.255.240
!
interface FastEthernet0/1
ip address 172.16.0.1 255.255.255.0
duplex auto
speed auto
!
router ospf 64
area 2 nssa
summary-address 172.16.30.0 255.255.255.0
redistribute connected subnets route-map loops
redistribute igrp 64 subnets
network 172.16.30.0 0.0.0.15 area 2
!
router igrp 64
redistribute ospf 64 metric 1000 10 255 1 1500
passive-interface FastEthernet0/0
network 172.16.0.0
!
route-map loops permit 10
match interface Loopback0
r4#
=====================================================
Regards, Voytek
-----Original Message-----
From: Nigel Taylor [mailto:nigel_taylor@hotmail.com]
Sent: Tuesday, 28 August 2001 10:25 PM
To: Michael Wong; Voytek Mielczarek; ccielab@groupstudy.com
Subject: Re: Revised - ospf nssa backwards
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:32:00 GMT-3