From: Peter Van Oene (pvo@xxxxxxxxxxxx)
Date: Wed Jun 13 2001 - 12:53:54 GMT-3
>From what I can tell on a quick read this looks normal. Area 2 is a stub area
and thus won't see the type 5 external that contains the 192 prefix, while it
correctly see's the type 7 3/8 advertisement.
*********** REPLY SEPARATOR ***********
On 6/13/2001 at 10:36 AM Don Dettmore wrote:
>Ok, go with me on this one - I thought NSSA areas were quite easy, but
>apparently I don't understand them:
>
>(192.168.49.0)-----RouterA---(172.16.253.0)---RouterB-----(2.2.2.0)-----Route
>rC-----(3.0.0.0)
>
>Router C runs:
>- EIGRP 3 on the 3.0.0.0 interface
>- OSPF Area 2 on the 2.2.2.0 interface
>- OSPF Area 0 on all other interfaces (not shown in diagram)
>
>Router B runs OSPF Area 2 on all interfaces
>
>RouterA runs:
>- OSPF Area 2 on the 172.16.253.0 interface
>- EIGRP 25 on the 192.168.49.0 interface
>
>Area2 is an NSSA area. RouterC is configured to originate a default route
>into Area 2 (command= area 2 nssa default-information-originate)
>
>I am redistributing the following routes into OSPF:
>- 3.0.0.0 on RouterC
>- 192.168.55.0 on RouterA (this is a network that exists out in the EIGRP
>25
>domain)
>
>What I don't understand is the routing table on RouterB. It contains the
>following:
>- A route (N2) to 3.0.0.0. It shouldn't have this, should it?
>- No route at all to 192.168.55.0, though this route exists on RouterC as
>an
>N2 route
>
>I thought it should be reverse - RouterB would see 192.168.55.0 as an N2
>route
>(type 7LSA) and no route to 3.0.0.0 - a default route instead. (it DOES
>see
>the default route).
>
>Note that other Area 0 routers further down the chain (not shown on the
>diagram) properly see both 3.0.0.0 and 192.168.55.0 as E2 routes.
>
>Can anyone explain this?
>
>TIA
>
>Don Dettmore
>**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:23 GMT-3