From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Sun Mar 03 2002 - 16:01:08 GMT-3
Hey George,
If you run multi-area ISIS (ie multiple NET's, one per routing instance)
the IS-type command is necessary to control the default behavior in your
non initial ISIS instances (first defaults to 1/2, rest default to
1-only) However, multi-area ISIS really only comes into play in legacy
CLNS networks and thus shouldn't be a topic one concerns oneself with in an
IP-only environment. Beyond that, I tend to set the IS-Type
(config-router) to either explicitly note L1/L2 (which is default) or to
set all interfaces into either L1 or L2 should the router either be all
backbone, or all single area. As well, for L1L2 routers, the
IS-Circuit-Type (config-interface) can be used to set some interfaces to
L1-only, and others to L2-only to control adjacency formation. In this
case, the router itself maintains to databases, one per level, while
individual interfaces only attempt to build the necessary adjacencies.
Hope that helps?
Pete
At 12:08 PM 3/3/2002 -0500, George Spahl wrote:
>Greetings,
>
>I was wondering if any of our resident ISIS gurus (or anyone else who'd
>like to take a shot at it!) could clarify the use of these two commands,
>specifically as to whether the interface command "ISIS circuit-type"
>would override what had been set by the router configuration command
>"IS-type" or if this is for some other purpose altogether. It looks as
>if they both relate to controlling what kind of adjacencies can be set
>up with other ISIS routers, the first at the router level and the other
>by interface, but I have the feeling that there are some subtleties to
>applying them that I'm overlooking.
>
>Thanks,
>
>George
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:51 GMT-3