From: Scott Morris (swm@emanon.com)
Date: Tue Mar 04 2003 - 12:24:18 GMT-3
Or the public version of that document:
http://www.cisco.com/en/US/tech/tk472/tk474/technologies_tech_note09186a
008009445a.shtml
Bottom line is that you only have two options in ISIS, point-to-point or
broadcast. So your interfaces have to match in some form, or you
"cheat" by creating an additional logical interface to do your routing
over!
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Herve Bruyere
Sent: Tuesday, March 04, 2003 4:19 AM
To: Dimitris Vassilopoulos
Cc: 'ccielab@groupstudy.com'
Subject: Re: ISIS on multipoint
Some good hints here:
http://www.cisco.com/warp/customer/97/isis-frint.html
And I can add something I tested in a prep setup: if R2 is a
point-to-point subif and R1 a natural interface (so network type
multipoint), you can create the adjacencies by using a tunnel between
the two routers.
rv
Dimitris Vassilopoulos wrote:
> All,
>
> Suppose that we are told to setup ISIS between two routers. One of
> them
> is the F/R hub
> and the other one is a spoke:
>
> R1
> / R2 --- R3
> \
> R4
>
> R2, R3, R4 run OSPF, so my question is only for R2-R1 which run ISIS.
>
> No subinterfaces allowed on the R1, while R2 should have a
> subinterface
> for R1.
>
> I know that ISIS runs on point-to-point F/R subinterfaces, but how is
> R1 going to learn
> about other routes if it cannot use point-to-point subinterface for
the
> connection to R2?
>
> What I did is:
> I chose to have point-to-multipoint subinterface on R2 for the
> connection to R1 and physical
> interface on R1 (multipoint), so adjacencies and routing is possible.
>
> Is this the proper solution?
>
> Any input would be welcomed....
>
> D.
>
-
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:32 GMT-3