Re: Trouble with Multi-Area ISIS instance

L2 (Area 0002) -> L1 (Area 0001)-> L1 (Area 0001) -> L2 (Area 0002)
    R1 R2 R3
        R4

You can configure both areas under the isis routing process on R2 and
R3 for example and limit the clns type adjacencies on the interfaces
to L1 or L2. Then you could use route-leaking.

I guess the problem will come on R3 for example to redistribute those
"inter-area" (from R1) type routes in the L1 database to its L2
database. I'm not sure if that is possible since it runs contrary to
the purpose of an L1 area not meant to be a backbone.

-Rich

On Mon, May 17, 2010 at 11:45 AM, Hewie McDuck <hmd2207_at_gmail.com> wrote:
> Couldn't you use route-leaking? Leak the L2 routes into L1 at each end. By
> default, the L1 are added to the L2 database at the far end. Use the
> command "isis circuit-type" on the interfaces to get them into the right
> database.
>
> Hewie
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Tolulope Adeniji
> Sent: Monday, May 17, 2010 1:47 AM
> To: ccielab_at_groupstudy.com
> Subject: Trouble with Multi-Area ISIS instance
>
> Hi
>
> Please how do you run a multi-area ISIS on a router under one ISIS
> instance/process? How do i form a converged isis database between two
> discontigous L2 links separated by L1 links as shown below;
>
> L2 (Area 0002) -> L1 (Area 0001)-> L1 (Area 0001) -> L2 (Area 0002)
>
> Cheers

Blogs and organic groups at http://www.ccie.net
Received on Mon May 17 2010 - 13:57:07 ART