From: Padhu (LFG) (padhu@xxxxxxxxxxxx)
Date: Thu Aug 23 2001 - 18:08:08 GMT-3
It shows as a L1 route.
R4 is the L1/L2 router and the term server is a L1 downstream. If you look
at the config on R4 you will see that one L2 route is leaked into L1. I
don't think this is supported in the RFC though.Just like the default...RFC
says default in L2 only but cisco has a knob for L1 too.
You could control which L1 routes get into L2 also ..See distribute-list
150.
Cheers,Padhu
R4#
router isis
summary-address 172.16.22.0 255.255.255.0
summary-address 172.16.60.0 255.255.255.0
redistribute isis ip level-1 into level-2 distribute-list 150
redistribute isis ip level-2 into level-1 distribute-list 160
default-information originate route-map isis-default
net 00.0459.0004.0004.0004.00
log-adjacency-changes
R4#show access-list 160
Extended IP access list 160
permit ip host 111.111.111.111 any log (8 matches)
R4#
Terminal_Server#ship isis
111.0.0.0/32 is subnetted, 1 subnets
i L1 111.111.111.111 [115/152] via 172.16.60.129, Ethernet0
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
i L1 172.16.4.0/24 [115/20] via 172.16.60.129, Ethernet0
i L1 192.1.44.0/24 [115/20] via 172.16.60.129, Ethernet0
i*L1 0.0.0.0/0 [115/10] via 172.16.60.129, Ethernet0
-----Original Message-----
From: Cox, Bryan [mailto:bryan.cox@avistacorp.com]
Sent: Thursday, August 23, 2001 2:26 PM
To: 'Padhu (LFG)'; 'jonatale@earthlink.net'; Cox, Bryan
Cc: 'Yves Fauser'; 'ccielab@groupstudy.com'
Subject: RE: isis over frame relay-Level-1 routers will never see L2
route s
Padhu,
I agree that a L1 router shouldn't see an L2 route under IS-IS. I wasn't
aware of the ability to selectively leak L2 routes into an L1 area. Do they
show up as L1 routes inside the L1 area? Do you have a specific example?
Bryan
-----Original Message-----
From: Padhu (LFG) [mailto:padhu@steinroe.com]
Sent: Thursday, August 23, 2001 8:36 AM
To: 'jonatale@earthlink.net'; Cox, Bryan
Cc: 'Yves Fauser'; 'ccielab@groupstudy.com'
Subject: RE: isis over frame relay-Level-1 routers will never see L2
route s
Bryan,
Level-1 routers will never see L2 routes. Think of it more like ospf totally
stubby area. They only should see a default derived from their nearest L1/L2
routers.
However in 12.x codes you can leak certain L2 routes into L1 by carefully
using distribute-list to select optimum paths.Now its more like OSPF NSSA.
Cheers,Padhu
-----Original Message-----
From: jonatale@earthlink.net [mailto:jonatale@earthlink.net]
Sent: Thursday, August 23, 2001 12:33 AM
To: Cox, Bryan
Cc: 'Yves Fauser'; 'ccielab@groupstudy.com'
Subject: Re: isis over frame relay
if it is level 1 only then both routers need to be in same (same ...AA) isis
area
also, sysID must always be diff
(...AA-SS-SS-SS-SS-SS-SS-00)
Cox, Bryan wrote:
> Yves,
>
> I was working in my lab last night on physical interfaces with the same
> IS-IS hub and spoke configuration that you and I exchanged e-mails on last
> week. I haven't tried multipoint interfaces yet though.
>
> In any case it appears to me that there is a basic problem. From my
reading
> it appears that level-1 areas never receive routes from level-2 areas. So
> in my configuration with physical interfaces, the level-2 spoke sees the
> router from the level-1 spoke, but the level-1 spoke never sees the router
> from the level-2 area.
>
> Can you post your configs that you got working with the
point-to-multipoint
> configuration?
>
> Bryan
>
> -----Original Message-----
> From: Yves Fauser [mailto:Yves@Fauser.de]
> Sent: Wednesday, August 22, 2001 12:35 AM
> To: jonatale@earthlink.net
> Cc: hans; ccielab@groupstudy.com
> Subject: Re: isis over frame relay
>
> Hi Hans, hi all,
>
> again, for isis on frame :
>
> 1. Remember to map clns
> 2. Isis has two network types, broadcast and point-to-point, these types
> must match on both Sides of the link.
> 3. Isis elects ar DR on a broadcast network, this DR is only used for
> controlling purposes, on a broadcast network you need an any-to-any
> adjacency. Obviously this doesn't work on FR. So with multipoint or
> physical interfaces there can be only one adjacency per level-type
> (because one DR is elected for level-2 and one DR is elected for
> level-1) between the spokes and the hub.
> If you have two spokes, configure one as a level-1 neighbor, and the
> other as level-2 neighbor. With tree spokes it can't work.
> 4. Isis works perfect with point-to-point subinterfaces
>
> Yves
>
> P.S. http://www.groupstudy.com/archives/ccielab/200108/msg00763.html
>
> jonatale@earthlink.net wrote:
>
> > map clns
> >
> > hans wrote:
> >
> > > Hi all,
> > >
> > > Does anyone know how to configure ISIS over frame relay?
> > >
> > > R2/s0----------s0/R1/s0------------s0.1/R3
> > >
> > > R1 is the hub, it use int s0 (2 DLCI) to connect with R2 and R3.
> > >
> > > I have router isis and net xxxxxx configured on all three routers.
> > > I also have all the interfaces configured with ip router isis.
> > >
> > > When I do show clns is-neighbors, I can not find neighbors at all.
> > >
> > > Need your help on it.
> > >
> > > Thanks,
> > >
> > > Hans
> > > **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
> **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
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:57 GMT-3