From: Peter van Oene (pvo@usermail.com)
Date: Sun Mar 16 2003 - 21:11:07 GMT-3
At 03:05 PM 3/16/2003 -0600, Voss, David wrote:
>Unfortunately not.
>
>The discreptancy in my mind lies in the following:
>
>global command: clns routing, not required
This enables routing of clns traffic which is different from the below as
shown.
>frame relay map: frame map clns 403 broadcast, required
This allows ISIS and CLNP packets to find their way into the right DLCI's
as they are transmitted directly over layer two. Although you are using
ISIS packets to provide a routing service for IP, the packets themselves
are not IP and thus you need to link them to layer 2 in the same way you
would IP.
>dialer map: dialer map clns ..., required
Same deal here, tell the router to bring up L2 when it sees ISIS packets
coming down the stack
>dialer list: dialer-list 1 protocol clns_is permit, required
Ditto :)
>-----Original Message-----
>From: Brian Dennis [mailto:brian@labforge.com]
>Sent: Sunday, March 16, 2003 2:27 PM
>To: Voss, David; ccielab@groupstudy.com
>Subject: RE: ISIS/CLNS Routing
>
>
>CLNS routing is not needed in the global configuration. Did they tell
>you why it's not needed in the class?
>
>Brian Dennis, CCIE #2210 (R&S/ISP Dial/Security) CCSI# 98640
>brian@labforge.com
>
>
>-----Original Message-----
>From: Voss, David [mailto:dvoss@heidrick.com]
>Sent: Sunday, March 16, 2003 11:37 AM
>To: 'Brian Dennis'; ccielab@groupstudy.com
>Subject: ISIS/CLNS Routing
>
>I was told at a highly respected and well-known training class that
>enabling
>"clns routing" is not required, only "router isis" when working with
>ISIS.
>I was told this by 2 different instructors. I see that in my ISIS book
>and
>also on groupstudy that most use the clns routing command in conjunction
>with router isis. Is this really needed?
>
>Quick thoughts on this?
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:40 GMT-3