From: wing_lam@jossynergy.com
Date: Mon Jul 28 2003 - 11:20:57 GMT-3
Thanks for you guys' response.
The same as I guess, I just wonder whether there is a better soultion.
Thx,
BBD (big Black Dog)
"Glenn Johnson"
<gjcomcast@comcas To: <wing_lam@jossynergy.com>
t.net> cc:
Subject: RE: ISIS neighbor
07/28/2003 10:00
PM
Please respond to
gjcomcast
Your choice 1 seems preferable -- going with authentication sounds like too
much, almost like an ACL that blocks all traffic -- that would be too easy.
I think they are looking for your knowledge of L1 and L2 adjacencies.
Are you talking about changing via circuit-type? Thanks
Specifying the Interface Circuit Type
You can specify adjacency levels on a specified interface. This parameter
is
also referred to as the interface circuit type.
To specify the interface circuit type, use the following command in
interface configuration mode:
Command Purpose
Isis circuit-type {level-1 | level-1-2 | level-2-only} Configure the type
of adjacency desired for neighbors on the specified interface (the
interface
circuit type).
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
wing_lam@jossynergy.com
Sent: Monday, July 28, 2003 9:33 AM
To: ccielab@groupstudy.com
Subject: ISIS neighbor
Hi Group,
With the following scenario:
R1, R2, R3 on the same subnet,
When the question asking you to do:
a) establish a R1--R2 L1 neighbor
b) establish a R2--R3 L2 neighbor
c) There should be no any neighbor relationship between R1 & R3
I think it will be no problem for anybody in a) & b), but for c), I can
think of two fast solution:
1) Set R1 as L1 only, R3 as L2 only
2) Set link authentication for R3's L1
The question is open; (i.e. no request you to do any authentication or
limitation)
Which one is better? Or some other better solutions?
Thx,
BBD (Big Black Dog)
DISCLAIMER:- This email is confidential and intended only for the use of
the individual or entity named above and may contain information that is
privileged. If you are not the intended recipient, you are notified that
any
dissemination, distribution or copying of this email is strictly
prohibited.
If you have received this email in error, please notify us immediately by
return email or telephone and destroy the original message. Thank you.
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:55 GMT-3