From: kym blair (kymblair@hotmail.com)
Date: Fri Apr 25 2003 - 19:16:37 GMT-3
Eric,
ISIS was developed by ISO as part of the Connectionless Network Services
(CLNS) suite, as was Connectionless Network Protocol (CLNP), the competition
to IP.
However, ISIS is capable of running in an IP environment, so does not
require CLNS routing.
Your bottom config is correct, except for one mistake. You DO need the clns
map statement for ISIS over Frame Relay, but the map statement would not
have an IP address (frame relay is a layer 2 protocol):
frame-relay clns 103 broadcast
You wouldn't need it on a point-to-point subinterface since that doesn't
accept a map statement.
HTH, Kym
>From: Eric Fisher <efisher@optonline.net>
>Reply-To: Eric Fisher <efisher@optonline.net>
>To: ccielab@groupstudy.com
>Subject: Router ISIS
>Date: Fri, 25 Apr 2003 14:10:30 -0400
>
>Do you need to enable clns routing to get ISIS to work. I have seen two
>types of configs and this is getting me a little confused.
>
>clns routing
>interface ser 1
>encap frame
>interface ser 1.1 point-to-point
>ip address 10.20.20.2 255.255.255.0
>ip router isis
>clns router isis <---is this needed.
>frame-relay interface-dlci 103
>
>router isis
>net 49.0001.2222.2222.2222.00
>is-type level-2
>
>the above came from cisco
>
>this config below came from a ccie class
>
>interface ser 1
>encap fram
>ip add 10.20.20.2 255.255.255.0
>ip router isis
>fram map ip 10.20.20.1 103 broad
>fram map clns 10.20.20.1 103 broad
>
>router isis
>network 49.0001.2222.2222.2222.00
>is type level-2
>
>
>
>what does the clns router isis command do, . and do you need to enable clns
>routing because the answer sheet I have from the class clns routing is not
>in there but the map statements are.
>
>
>
>Thanks
>Eric
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:36:07 GMT-3