To find the CLNS adjacency state on Cisco IOS, as the slide shows, we use the command: "show clns neighbor" and that shows where the router has found adjacencies talking the CLNS protocol. To find the IS-IS adjacency state, in other words we have exchanged IPv4 prefixes, do: "show IS-IS neighbor" and that shows the IP address of the neighboring router and various other information, including the holdtime, which is the time the router waits before it declares the neighbor has vanished. Starting IS-IS on Cisco routers is very simply a case of doing: "router isis" and then specifying an identifier. The identifier could be the operator's "AS" number or some other word to indicate the process ID. Most operators prefer to insert a process ID. That same process ID has to be used in all interfaces that are participating in IS-IS on that router and it avoids configuration accidents and errors happening within the network. The process ID is not passed between routers in the autonomous system, it is unique just to the router and gives the possibility of running multiple instances of IS-IS on one router if desired. IP routing protocols have a router ID to uniquely identify the router. What IS-IS is not an IP based routing protocol, so it doesn't use the router ID in the same way as OSPF and other protocols do. Instead it has a Network Entity Title (NET) which can be from 64 to 160 bits long. The typical scheme used by many operators today is, as shown on the slide. The first 8 bits we usually pick a number and it's usually 49, doesn't have to be, but that seems to be widely used. The next 16 bits is the area, typically 0001 is used. The next 48 bits are the router loopback address, where we take the IP address of the router and code it into 48 bits, and the final 8 bits are 0. So for example we could have an NSAP of 49.0001.1921.6800.1001.00 That is generated from the IP address used for the loopback. The IP address is 192.168.1.1 We insert the leading zeros in that IP address, move the dots across and we get the: 1921.6800.1001 to form the 48 bits of the NSAP address. This way we can make sure we have a unique NSAP address for every single router on the network, because the loopback address has to be unique on every single router in the network as well. Other operators use this alternative scheme. This one is a little simpler, where the first 8 bits are usually picking a number. Next 16 bits are the area, which we leave at 0001. The next 16 bits would be our Point of Presence identifier. The next 16 bits will be our router identifier, and the final 8 bits would be 0. Many operators [who] are deploying IPv6 use a similar type of PoP and router identifier scheme for doing the v6 addressing across their backbone. So this NSAP addressing plan maps very nicely onto deployed v6 addressing plans. So in the example I've shown, the NSAP address would be 49.0001.0009.0003 which represents router number 3 in Point of Presence number 9.
© Produced by Philip Smith and the Network Startup Resource Center, through the University of Oregon.
Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
This is a human-readable summary of (and not a substitute for) the license. Disclaimer. You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. NonCommercial — You may not use the material for commercial purposes. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.