From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Fri Jan 04 2002 - 13:39:47 GMT-3
Multi-area ISIS is really a CLNS topic. It is indeed not recommend that
one run multi-area for IP only routing. Some use in transition networks may
take place, but your better to simply interconnect with a proper L2
backbone than merge areas.
The command clns routing is only required if you intend to route clns. For
IP only environments, it is not needed. In IP only, you configure one NET
per ISIS instance, and one ISIS instance per L1 area you intend to form
adjacencies within. The configs your looking at on CCO likely include the
command clns router isis on each interface. I doubt there are many IP only
multi-area configs on CCO given it is not a recommended practise.
Pete
At 09:32 AM 1/4/2002 -0600, Michael C. Popovich wrote:
>I have double checked on Documentation CD regarding IS-IS and the need
>for CLNS. Peter is definitely right in the fact that CLNS is not
>required to route IP using IS-IS. This question is for Peter and anyone
>else with a good understanding of IS-IS.
>
>Reading through the Documentation CD on Integrated IS-IS I have a
>question regarding multi-area. The way I read it I am assuming that if
>you implement a multi-area IS-IS solution then you in fact do need to
>enable CLNS routing. Is this true? The examples given in the
>Documentation CD show that a single area IS-IS network doesn't need CLNS
>routing but in the multi-area scenario they have CLNS routing enabled.
>This isn't specifically addressed but I assume with the need for
>different areas using different NET addresses requires the CLNS
>protocol.
>
>Please correct me if I have misinterpreted this.
>
>Thanks,
>
>Michael Popovich
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:16 GMT-3