From: Yasser Abdullah (yasser@alharbitelecom.com)
Date: Sat May 22 2004 - 06:01:52 GMT-3
Why would level 1 work? Since the spokes are on the same segment, they will
need to form full adjacencies with each other. L1 or L2, there will be
problems if the FR isn't fully meshed.
If I remember correctly, there are 3 solutions for ISIS over partial-meshed
frame-relay network:
1- Use P2P subinterfaces
2- Use a GRE tunnel
3- Make the hub a L1/L2 router, one spoke a L2 and the other a L1.
I think this should work as well: Make the hub a L1/L2 router. Spoke one is
a L1 router in area 1 and spoke 2 is a L1 router in area 2.
Brgds,
Yasser
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Richard Dumoulin
Sent: Friday, May 21, 2004 8:42 PM
To: ccie2be; Group Study
Subject: RE: ISIS over Frame Relay
If it is not full mesh then for this to work you need level-1 only and the
hub to be the DIS. With level-2 it will not work if I remember well,
--Richard
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: viernes, 21 de mayo de 2004 19:10
To: Group Study
Subject: ISIS over Frame Relay
Hi guys,
When configuring the above in a hub and spoke topology and using only the
physical interfaces, does it matter if the hub becomes the DIS? In all the
examples I've seen so far, I've never seen the isis priority command used to
force the hub to become the DIS and I don't understand why that is.
Also, are the following config's on the hub router equally valid?
Method 1 - Static mapping
Hub rtr
int s0
ip addr x.x.x.1/24
encap fram
ip router isis
fram map clns 122 broad
fram map clns 123 broad
fram map ip x.x.x.2 122 broad
fram map ip x.x.x.3 123 broad
*********************
Method 2 - Dynamic Mapping
Hub rtr
int s0
ip addr x.x.x.1/24
encap fram
ip router isis
fram interface-dlci 122
fram interface-dlci 123
It would be great if someone could explain why or why not these config's
aren't both valid.
Thanks in advance. Any feedback would be greatly appreciated, Tim
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:15 GMT-3