From: Brian Hescock (bhescock@xxxxxxxxx)
Date: Tue Feb 06 2001 - 10:54:51 GMT-3
I like using the KISS principle. Why use the highest ip address on the
router and make it more difficult than it is? Sure, in real-world that's
fine but for lab purposes, try something like this:
AFI.area.unique-system-id.00
49.0000. router number .00
router 1
router isis
net 49.0000.1111.1111.1111.00
router 2
router isis
net 49.0000.2222.2222.2222.00
router 3
router isis
net 49.0000.3333.3333.3333.00
etc
Similarly, when using ipx routing, for router 1 use "ipx routing
1.1.1" Use tricks like this that are easy to use and
troubleshoot. Another example, when numbering your ipx links, I use the
router numbers also. So if the ipx link is between router 2 and 5 it's
ipx network 25. It makes it very easy to see which network is which in
the routing table and to troubleshoot it.
B.
On Mon, 5 Feb 2001, Chuck Larrieu wrote:
> Check out Doyle's chapter on ISIS for a reasonably clear explanation.
> Slattery's chapter on ISIS is pretty good, but very little is said about the
> addressing scheme. Ironically, Perlman's book is fairly useless for any real
> information about ISIS.
>
> Format AA.BBBB.CCCC.CCCC.CCCC.00
>
> These are hex numbers.
>
> AA is the AFI identifier. There are certain "registered" numbers apparently,
> but none of the sources above specify. Doyle likes 47. Slattery likes 49.
>
> BBBB is the area i.d.
>
> The C's represent the system ID and must be unique in an ISIS domain.
> Slattery recommends using a pneumonic based on a router's primary IP
> address. This can get a little interesting if you have not practiced it. For
> example, if a router's loopback is 124.17.100.5 Slattery would write this at
> 1240.1710.0005 ( yeah, I know. )
>
> The last number is 00. If it is anything other than 00 then the rest of the
> identifier is an NSAP address and must conform to NSAP rules ( no I don't
> know what those are )
>
> One other thing that takes a bit of getting used to. In the ISIS scheme of
> things, routers are placed into areas. With OSPF, interfaces are placed into
> areas. With EIGRP, IGRP, and RIP, networks are placed into the routing
> processes, which may or may not include all or part of any router's set of
> interfaces. This difference can be the source of a bit of confusion is
> putting together labs and designs, until one has worked with it a bit.
>
> HTH
>
> Chuck
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of CCIE
> yong
> Sent: Monday, February 05, 2001 7:45 PM
> To: ccielab@groupstudy.com
> Subject: IS-IS Routing
>
> Hi,
>
> Wondering how to derive the network parameter under
> "router ISIS
> net xxx.xxx.xxx.xxx.xx.xx"
>
> Sorry for bothering you guys,
>
> Thanks
> Yonger
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:38 GMT-3