From: Ouellette, Tim (tim.ouellette@xxxxxxx)
Date: Sun Mar 03 2002 - 21:35:15 GMT-3
George,
My understanding of the two commands is as follows.
By default, an IS-IS router is setup to try and form L1/L2 adjancencies on
it's interfaces. If you want to "nail down" the fact that it's only
allowed to form an L1 adjacency on an interface, you'd use the "ISIS
circuit-type" under that particular interface and it'll only allow an
adjacency to form based on the L1/L2 type you define.
The "is-type" command is very similar. A router that has been configured
for isis will default to a L1/L2 router. Why should it maintain multiple
databases? Nail it down to be a "stub-type" router with the Is-type command.
This will force it to be a level 1 / level 2 router. Which you prefer.
Hopefully my understanding is correct and that I've conveyed it to you
properly *grin*
Tim
-----Original Message-----
From: George Spahl [mailto:g.spahl@insightbb.com]
Sent: Sunday, March 03, 2002 12:09 PM
To: ccielab@groupstudy.com
Subject: ISIS Circuit-type vs. IS-type
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