RE: ospf nssa qustion

From: lim es (tiga72@yahoo.com)
Date: Thu Jan 19 2006 - 02:22:47 GMT-3


Hi Lin,

Absolutely, u are right. It is very much clearer now.

Thanks alot:)

Lim

--- easyman <easyman@primetek.com.tw> wrote:

> Hi, Lim
> 1) Yes, area type is one of the attributes which
> must be agreed by all
> router in the same area, others like mtu, area-id,
> ....etc. So I think both
> r2 and r3 need area nssa command.
>
> 2) About r2 can't see r3's loopback interface.
> Because area3 is not directly connected to area0.
> You might need area23 to be the transit-area to
> solve this issue.
> But since in question 1), area23 is nssa area so it
> can't configured as the
> transit-area.
>
> So I think one of the solutions is that you might
> create a tunnel interface
> between r1 & r3 and make area3 truly connected to
> area0.
> The other solution might be put area3 on r3 on
> another ospf process-id and
> redistribute between the two ospf process.
>
> Regards,
> HTH.
> Lin
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of lim
> es
> Sent: Thursday, January 19, 2006 12:41 PM
> To: ccielab@groupstudy.com
> Subject: ospf nssa qustion
>
> Hi Group,
>
> If i have this network
>
> r1------r2-------r3------r4
>
>
> r1 and r2: ospf area 0
>
> r2 and r3: ospf nssa, area 23
>
> r3 and r4: ripv2
>
>
> 1) do i configure "nssa" commands on both r2 and r3?
> i find that it works even when i just do it at
> r2.
> I think it is need on both r2 and r3, stub flags
> have to agree
>
> 2) if i create a area3 in r3, put a loopback
> interface
> into area 3, r2 doesnt get that route
>
> that means can i add another ospf area on the
> edge
> of
> nssa area, r3 ? that might be the reason why r2
> cannot
> receive the route when i do that?
>
> Appreciate any inputs
>
> Thanks
>
> Lim
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
> protection around
> http://mail.yahoo.com
>
>



This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:49 GMT-3