From: Niche (jackyliu419@gmail.com)
Date: Thu Nov 03 2005 - 02:36:28 GMT-3
Hi there,
As far as I know, normally, ISIS require a fully meshed Layer-2 connectivity
between all peers if they are in the same subnet.
If you are in the lab environment, may be try to form a fully meshed layout
or use 2 point-to-point links (tunnels also works but the configuration is
kinda complex).
Cheers~
Jacky
P.S. I have been told that if you configure the hub ISIS router as DIS then
you can also solve the problem. I don't have a chance to try it out
thought..
On 11/3/05, Chacko, Raj <RChacko@draftnet.com> wrote:
>
> Hi, I am struggling with the following topology and for the life of me, I
> don't understand why is it that R6, one of the spokes, doesn't install L2
> routes learnt from the HUB which R4 has learnt from R2. I see that the
> routes from R5 do show up in the R6 RIB as L2 routes however. (when I
> redistributed L1 into L2 at the Hub, I see these routes in R6 as ia, but
> why
> do I have to dot that)
> Thanks & Regards,
> Raj
> --------------Here is the topology--------------------
> Hub and spoke design with R4 as the HUB, a Multipoint subinterface
> connecting to R2 and R6 and a Point-2-Point connecting to R5
>
> R2(L2only)_____NET0102__
> \
> \
> \R4(L1 on s0.54),(DIS)
> / \
> / \(NET0045)
> / \
> R6(L1,L2)_____NET0426__/ \__R5(L1 only)
>
>
> ---------R4 has two ISIS processes as follows--------
>
> R4#sh run | b ^router isis
> router isis 426
> net 47.0426.4444.4444.4444.00
> redistribute isis ip level-2 into level-1 distribute-list 138
> !
> router isis
> net 47.0045.4444.4444.4444.00
> is-type level-1
> max-lsp-lifetime 3600
>
> access-list 138 permit ip host 137.10.200.0 <http://137.10.200.0> host
> 255.255.255.0 <http://255.255.255.0>
>
> -------------------AND THE INTERFACES-----------------
> R4#sh run int s0.54
> Building configuration...
>
> Current configuration : 283 bytes
> !
> interface Serial0.54 multipoint
> ip address 137.10.45.4 <http://137.10.45.4>
255.255.255.240<http://255.255.255.240>
> ip router isis
> frame-relay map clns 405 broadcast
> frame-relay map ip 137.10.45.4 <http://137.10.45.4> 405
> frame-relay map ip 137.10.45.5 <http://137.10.45.5> 405 broadcast compress
> active
> isis circuit-type level-1
> isis hello-multiplier 20
> end
>
> R4#sh run int s0.246
> Building configuration...
>
> Current configuration : 323 bytes
> !
> interface Serial0.246 multipoint
> ip address 137.10.100.4 <http://137.10.100.4>
255.255.255.224<http://255.255.255.224>
> ip router isis 426
> frame-relay map clns 401 broadcast
> frame-relay map clns 406 broadcast
> frame-relay map ip 137.10.100.2 <http://137.10.100.2> 401 broadcast
> frame-relay map ip 137.10.100.4 <http://137.10.100.4> 406
> frame-relay map ip 137.10.100.6 <http://137.10.100.6> 406 broadcast
> isis priority 125
> end
> ------------------------------------------------------------
>
> R6#sh run | b ^router isis
> router isis
> net 47.0426.6666.6666.6666.00
> !___________________________________________________________
>
> R2#sh run | b ^router isis
> router isis
> net 47.0102.2222.2222.2222.00
> redistribute connected route-map conn2isis
> redistribute ospf 1 metric 20 match internal external 1 external 2
> route-map ospf2isis
> passive-interface Loopback0
> is-type level-2-only
> !______________________________________________________________
>
> R5#sh run | b ^router isis
> router isis
> net 47.0045.5555.5555.5555.00
> passive-interface Loopback1
> passive-interface Loopback2
> passive-interface Loopback3
> is-type level-1
> _______________________________________________________________
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:05 GMT-3