BSCIv ISIS

BSCI
Click Here to Post Review Comments
Building Scalable Cisco

Internetworks
Version 1.2
Student Guide
Text Part Number: Review Copy
The products and specifications, configurations, and other technical information regarding the products
in this manual are subject to change without notice. All statements, technical information, and
recommendations in this manual are believed to be accurate but are presented without warranty of any
kind, express or implied. You must take full responsibility for their application of any products
specified in this manual.
LICENSE
PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THE MANUAL,
DOCUMENTATION, AND/OR SOFTWARE (“MATERIALS”). BY USING THE MATERIALS YOU
AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS LICENSE. IF YOU DO NOT
AGREE WITH THE TERMS OF THIS LICENSE, PROMPTLY RETURN THE UNUSED
MATERIALS (WITH PROOF OF PAYMENT) TO THE PLACE OF PURCHASE FOR A FULL
REFUND.
Cisco Systems, Inc. (“Cisco”) and its suppliers grant to you (“You”) a nonexclusive and nontransferable
license to use the Cisco Materials solely for Your own personal use. If the Materials include Cisco
software (“Software”), Cisco grants to You a nonexclusive and nontransferable license to use the
Software in object code form solely on a single central processing unit owned or leased by You or
otherwise embedded in equipment provided by Cisco. You may make one (1) archival copy of the
Software provided You affix to such copy all copyright, confidentiality, and proprietary notices that
appear on the original. EXCEPT AS EXPRESSLY AUTHORIZED ABOVE, YOU SHALL NOT:
COPY, IN WHOLE OR IN PART, MATERIALS; MODIFY THE SOFTWARE; REVERSE COMPILE
OR REVERSE ASSEMBLE ALL OR ANY PORTION OF THE SOFTWARE; OR RENT, LEASE,
DISTRIBUTE, SELL, OR CREATE DERIVATIVE WORKS OF THE MATERIALS.
You agree that aspects of the licensed Materials, including the specific design and structure of individual
programs, constitute trade secrets and/or copyrighted material of Cisco. You agree not to disclose,
provide, or otherwise make available such trade secrets or copyrighted material in any form to any
third party without the prior written consent of Cisco. You agree to implement reasonable security
measures to protect such trade secrets and copyrighted Material. Title to the Materials shall remain
solely with Cisco.
This License is effective until terminated. You may terminate this License at any time by destroying all
copies of the Materials. This License will terminate immediately without notice from Cisco if You fail
to comply with any provision of this License. Upon termination, You must destroy all copies of the
Materials.
Software, including technical data, is subject to U.S. export control laws, including the U.S. Export
Administration Act and its associated regulations, and may be subject to export or import regulations in
other countries. You agree to comply strictly with all such regulations and acknowledge that it has the
responsibility to obtain licenses to export, re-export, or import Software.
This License shall be governed by and construed in accordance with the laws of the State of California,
United States of America, as if performed wholly within the state and without giving effect to the
principles of conflict of law. If any portion hereof is found to be void or unenforceable, the remainin g
provisions of this License shall remain in full force and effect. This License constitutes the entire
License between the parties with respect to the use of the Materials
Restricted Rights - Cisco’s software is provided to non-DOD agencies with RESTRICTED RIGHTS and
its supporting documentation is provided with LIMITED RIGHTS. Use, duplication, or disclosure by the
U.S. Government is subject to the restrictions as set forth in subparagraph “C” of the Commercial
Computer Software - Restricted Rights clause at FAR 52.227-19. In the event the sale is to a DOD
agency, the U.S. Government’s rights in software, supporting documentation, and technical data are
governed by the restrictions in the Technical Data Commercial Items clause at DFARS 252.227-7015
and DFARS 227.7202.
DISCLAIMER OF WARRANTY. ALL MATERIALS ARE PROVIDED “AS IS” WITH ALL
FAULTS. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST
PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE
THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. In no event shall Cisco’s or its suppliers’ liability to You,
whether in contract, tort (including neglige nce), or otherwise, exceed the price paid by You. The
foregoing limitations shall apply even if the above-stated warranty fails of its essential purpose.
The following information is for FCC compliance of Class A devices: This equipment has been tested
and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules.
These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate
radio-frequency energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a residential area is
likely t o cause harmful interference, in which case users will be required to correct the interference at
their own expense.
The following information is for FCC compliance of Class B devices: The equipment described in this
manual generates and may radiate radio -frequency energy. If it is not installed in accordance with
Cisco’s installation instructions, it may cause interference with radio and television reception. This
equipment has been tested and found to comply with the limits for a Class B digital device in accordance
with the specifications in part 15 of the FCC rules. These specifications are designed to provide
reasonable protection against such interference in a residential installation. However, there is no
guarantee that interference will not occur in a particular installation.
You can determine whether your equipment is causing interference by turning it off. If the interference
stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment
causes interference to radio or television reception, try to correct the interference by using one or
more of the following measures:
• Turn the television or radio antenna until the interference stops.
• Move the equipment to one side or the other of the television or radio .
• Move the equipment farther away from the television or radio.
• Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is,
make certain the equipment and the television or radio are on circuits controlled by different circuit
breakers or fuses.)
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and
negate your authority to operate the product.
The following third-party software may be included with your product and will be subject to the
software license agreement:
CiscoWorks software and documentation are based in part on HP OpenView under license from the
Hewlett-Packard Company. HP OpenView is a trademark of the Hewlett-Packard Company. Copyright
© 1992, 1993 Hewlett-Packard Company.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the
University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX
operating system. All rights reserved. Co pyright © 1981, Regents of the University of California.
Network Time Protocol (NTP). Copyright © 1992, David L. Mills. The University of Delaware makes
no representations about the suitability of this software for any purpose.
Point-to-Point Protocol. Co pyright © 1989, Carnegie-Mellon University. All rights reserved. The
name of the University may not be used to endorse or promote products derived from this software
without specific prior written permission.
The Cisco implementation of TN3270 is an adaptation of the TN3270, curses, and termcap programs
developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of
the UNIX operating system. All rights reserved. Copyright © 1981-1988, Regents of the University of
California.
Cisco incorporates Fastmac and TrueView software and the RingRunner chip in some Token Ring
products. Fastmac software is licensed to Cisco by Madge Networks Limited, and the RingRunner chip is
licensed to Cisco by Madge NV. Fastmac, RingRunner, and TrueView are trademarks and in some
jurisdictions registered trademarks of Madge Networks Limited. Copyright © 1995, Madge Networks
Limited. All rights reserved.
XRemote is a trademark of Network Computing Devices, Inc. Copyright © 1989, Network Computing
Devices, Inc., Mountain View, California. NCD makes no representations about the suitability of this
software for any purpose.
The X Window System is a trademark of the X Consortium, Cambridge, Massachusetts. All rights
reserved.
Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone
numbers, and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offices.
Argentina Australia Austria Belgium Brazil Bulgaria Canada Chile China PRC Colombia Costa Rica
Croatia Czech Republic Denmark Dubai, UAE Finland France Germany Greece Hong Kong SAR
Hungary India Indonesia Ireland Israel Italy Japan Korea Luxembourg Malaysia Mexico The
Netherlands New Zealand Norway Peru Philippines Poland Portugal Puerto Rico Romania Russia Saudi
Arabia Scotland Singapore Slovakia Slovenia South Africa Spain Sweden Switzerland Taiwan Thailand
Turkey Ukraine United Kingdom United States Venezuela Vietnam Zimbabwe
Copyright  2001, Cisco Systems, Inc. All rights reserved. AccessPath, AtmDirector, Browse
with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco
NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, Fast
Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ
Breakthrough, iQ Expertise, iQ FastTrack, the iQ logo, iQ Net Readiness Scorecard, MGX, the
Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath,
Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.;
Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, and Empowering
the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst,
Cisco, the Cisco Certified Internetwork Expert Logo, Cisco IOS, the Cisco IOS logo, Cisco Systems,
Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub,
FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post -Routing, Pre-Routing,
Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of
Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of
their respective owners. The use of the word partner does not imply a partnership relationship between
Cisco and any other company. (0104R)
This Document is strictly controlled through the Cisco Learning Partner license
agreement. Accordingly, do not copy, print or distribute this preliminary document.
Building Scalable Cisco Internetworks, Revision 1.2: Student Guide

Copyright  2001, Cisco Systems, Inc.
All rights reserved. Printed in USA.
Table of Contents
Click Here to Post Review Comments
INTRODUCTION 1-1
Overview 1-1
Course Objectives 1-2
Course Objectives (cont.) 1-3
Course Topics 1-4
Prerequisites 1-5
Participant Role 1-8
General Administration 1-10
Sources of Information 1-11
Course Syllabus 1-12
Graphic Symbols 1-14
ROUTING PRINCIPLES 2-1

Overview 2-1
Objectives 2-2
Classful Routing Protocol Overview 2-3
Classless Routing Overview 2-6
Distance Vector Operation 2-9
Link-State Operation 2-10
Written Exercise: Comparing Routing Protocols 2-29
Objective 2-29
Task 2-29
Completion Criteria 2-30
Summary 2-31
Review Questions 2-32
EXTENDING IP ADDRESSES 3-1

Overview 3-1
Objectives 3-2
IP Addressing Issues 3-3
IP Addressing Solutions 3-4
Hierarchical Addressing 3-9
VLSMs 3-11
Written Exercise 1: Calculating VLSMs 3-14
Objective 3-14
Task 3-14
Route Summarization 3-15
Written Exercise 2: Using Route Summarization 3-25
Objective 3-25
Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking v

Task 1 3-25
Task 2 3-26
Classless Interdomain Routing 3-27
Summary 3-29
CONFIGURING EIGRP 4-1

Overview 4-1
Outline 4-1
Objectives 4-2
EIGRP Overview 4-4
EIGRP Operation 4-13
Written Exercise: EIGRP Overview 4-34
Objective 4-34
Task 4-34
Configuring EIGRP 4-35
Using EIGRP in Scalable Internetworks 4-54
Verifying EIGRP Operation 4-69
Summary 4-71
CONFIGURING OSPF IN A SINGLE AREA 5-1

Overview 5-1
Objectives 5-2
Objectives (cont.) 5-3
OSPF Overview 5-4
OSPF Terminology 5-7
OSPF Operation 5-9
OSPF Operation in a Broadcast Multiaccess Topology 5-10
OSPF Operation in a Point-to-Point Topology 5-21
OSPF Operation in an NBMA Topology 5-22
Written Exercise: OSPF Operation 5-34
Objective 5-34
Task 5-34
Configuring OSPF in a Single Area 5-36
Verifying OSPF Operation 5-48
Summary 5-57
Summary (cont.) 5-58
INTERCONNECTING MULTIPLE OSPF AREAS 6-1

Overview 6-1
Objectives 6-2
vi Building Scalable Cisco Internetworking Copyright  2001, Cisco Systems, Inc.

Creating Multiple OSPF Areas 6-4
Routing Table Results with Different Areas 6-14
OSPF Operation Across Multiple Areas 6-15
Virtual Links Overview 6-18
Written Exercise: OSPF Operation Across Multiple Areas 6-20
Objective 6-20
Task 6-20
Using and Configuring OSPF Multiarea Components 6-22
Verifying OSPF Operation 6-40
Summary 6-42
CONFIGURING IS-IS PROTOCOL 7-1

Overview 7-1
Objectives 7-2
Introduction to OSI Protocols and IS-IS Routing 7-3
Operation of IS-IS 7-28
IP and OSI Routing with Integrated IS-IS 7-53
Basic Integrated IS-IS Router Configuration 7-69
Modeling WAN Networks in Integrated IS-IS 7-83
Summary 7-97
OPTIMIZING ROUTING UPDATE OPERATION 8-1

Overview 8-1
Objectives 8-2
Redistribution Between Multiple Routing Protocols 8-4
Configuring Redistribution 8-12
Controlling Routing Update Traffic 8-27
Verifying Redistribution Operation 8-41
Written Exercise: Redistribution and Controlling Routing Update Traffic 8-43
Objectives 8-43
Task 8-43
Policy-Based Routing Using Route Maps 8-45
Verifying Policy-Based Routing 8-58
Summary 8-62
Review Questions (cont.) 8-65
CONFIGURING BASIC BGP 9-1

Overview 9-1
Objectives 9-2
BGP Overview 9-4
Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking vii
When Not to Use BGP 9-10
BGP Terminology 9-14
BGP Operation 9-38
Written Exercise: BGP Terminology and Operation 9-44
Objectives 9-44
Task 9-44
Configuring BGP 9-46
Verifying BGP 9-57
Summary 9-62
IMPLEMENTING BGP IN SCALABLE NETWORKS 10-1

Overview 10-1
Objectives 10-2
Scalability Problems with IBGP 10-4
Route Reflectors 10-7
Policy Control 10-17
Written Exercise: BGP Route Reflectors and Policy Control 10-28
Objectives 10-28
Task 10-28
Multihoming 10-30
Redistribution with IGPs 10-45
Summary 10-52
JOB AIDS AND SUPPLEMENTS A-1

Overview A-1
Extending IP Addresses A-2
Job Aids A-3
IP Addresses and Subnetting A-3
Decimal-to-Binary Conversion Chart A-4
Binary A-4
Supplement 1: Addressing Review A-5
Supplement 2: IP Access Lists A-16
Supplement 3: IP Features A-56
Using IP Unnumbered Interfaces A-56
Using Helper Addresses A-59
Supplement 4: EIGRP A-66
Supplement 5: OSPF A-70
Supplement 6: Route Optimization A-85
Supplement 7: BGP A-109
ROUTER PASSWORD RECOVERY B-1

Overview B-1
viii Building Scalable Cisco Internetworking Copyright  2001, Cisco Systems, Inc.
Router Password Recovery Procedure B-2
ANSWERS C-1
Overview C-1
Chapter 2 Exercises C-2
Answers to Written Exercise: Comparing Routing Protocols C-2
Answers to Review Questions C-3
Answers to Written Exercise: Calculating VLSMs C-4
Answers to Written Exercises: Using Route Summarization C-5
Answers to Written Exercise: EIGRP Overview C-6
Answers to Written Exercise: OSPF Operation C-8
Answers to Written Exercise: OSPF Operation Across Multiple Areas C-10
Chapter 7 C-13
Answers To Review Questions 13
Answers to Written Exercise: Redistribution and Controlling Routing Update
Traffic C-15
Answers To Review Questions C-16
Answers to Written Exercise: BGP Terminology and Operation C-18
Answers to Written Exercise: BGP Route Reflectors and Policy Control C-21
Appendix A Exercises C-23
Answers to Extending IP Addressing Written Exercise: Calculating Subnet
Masks C-23
Answers to IP Access Lists Written Exercise: IP Extended Access Lists C-24
Laboratory Exercises Written Questions C-25
Laboratory Exercise 1: Configuring EIGRP C-25
Laboratory Exercise 2: Configuring OSPF for a Single Area C-25
Laboratory Exercise 3: Configuring OSPF for a Single Area in an NBMA
Environment C-25
Laboratory Exercise 4: Configuring a Multiarea OSPF Network C-26
Laboratory Exercise 5: Configuring a Multiarea IS-IS Network C-26
Laboratory Exercise 6: Configuring Policy-Based Routing C-26
Laboratory Exercise 7: Configuring Route Redistribution between OSPF and
EIGRP C-27
Laboratory Exercise 8: Configuring BGP C-27
Laboratory Exercise 9: Configuring BGP Route Reflectors and Prefix-List
Filtering C-27
Laboratory Exercise 10: Configuring Multihomed BGP C-27
Laboratory Exercise 12: Super Lab Part I and Part II C-27
LABORATORY EXERCISES D-1
Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking ix

Introduction D-1
Laboratory Exercise 1: Configuring EIGRP D-2
Objectives D-2
Visual Objective D-3
Command List D-3
Setup D-4
Scenario D-4
Task 1: Enabling EIGRP Within Your Pod D-6
Task 2: Enabling EIGRP Connectivity to the backbone_r1 Router D-7
Completion Criteria D-9
Student Notes D-10
Laboratory Exercise 2: Configuring OSPF for a Single Area D-11
Objectives D-11
Command List D-12
Setup D-12
Scenario D-12
Task 1: Enabling OSPF Within Your Pod D-13
Task 2: Enabling OSPF Connectivity to the Backbone_r1 Router D-15
Student Notes D-17
Laboratory Exercise 3: Configuring OSPF for a Single Area in an NBMA
Environment D-18
Objectives D-18
Command List D-20
Setup D-20
Scenario D-20
Task 1: Creating the Frame Relay Switch D-21
Task 2: Enabling OSPF Over an NBMA Network Using a Main Interface D-22
Task 3: Enabling OSPF Over an NBMA Network Using a Point-to-Point
Subinterface D-23
Student Notes D-24
Laboratory Exercise 4: Configuring a Multiarea OSPF Network D-25
Objectives D-25
Command List D-27
Setup D-28
Scenario D-29
Task 1: Enabling OSPF with Multiple Areas and Area Summarization D-29
Task 2: Enabling OSPF Stub Area D-31
Task 3: Enabling an OSPF Totally Stubby Area D-31
Task 4: Enabling OSPF Not-So-Stubby Area (Optional) D-32
Task 5: Enabling an OSPF Virtual Link to Support an OSPF Area not
Connected to Area 0 (Optional) D-35
Student Notes D-38
Laboratory Exercise 5: Configuring a Multiarea IS-IS Network D-39
Objectives D-39
Command List D-41
router isis D-41
router isis D-42
Setup D-42
Scenario D-42
x Building Scalable Cisco Internetworking Copyright  2001, Cisco Systems, Inc.

Task 1: Enabling IS-IS within your pod D-42
Task 2: Enabling connectivity to the backbone_r1 router D-44
Task 3: Changing the IS-IS router type D-44
Task 4: Configure route summarization D-45
Task 5: Using IS-IS show and debug commands D-46
Student Notes D-49

Laboratory Exercise 6: Configuring Policy-Based Routing D-50
Objectives D-50
Command List D-51
Setup D-51
Scenario D-51
Task 1: Enable IP Policy-Based Routing at pxr1 D-52
Student Notes D-55
Laboratory Exercise 7: Configuring Route Redistribution Between OSPF and
EIGRP D-56
Objectives D-56
Command List D-57
Setup D-57
Scenario D-57
Task 1: Enabling OSPF Between pxr1 (S0 and S1)
and pxr2 (S0 and S1) D-58
Task 2: Enabling EIGRP Between pxr1 (S2) and pxr3 (S0) D-58
Task 3: Enabling Route Redistribution Between OSPF and EIGRP D-58
Task 4: Enabling Route Redistribution from EIGRP
to OSPF with Filtering D-59
Student Notes D-61
Laboratory Exercise 8: Configuring BGP D-62
Objectives D-62
Command List D-63
Setup D-65
Scenario D-65
Task 1: Enabling EBGP D-66
Task 2: Enabling Full-Mesh IBGP Within Your Pod (AS) D-68
Student Notes D-71
Laboratory Exercise 9: Configuring BGP Route Reflectors and Prefix-List
Filtering D-72
Objectives D-72
Command List D-73
Setup D-73
Scenario D-73
Task 1: Enabling pxr1 to be the Route Reflector D-74
Task 2: Enabling Inbound Prefix-List D-76
Student Notes D-77
Laboratory Exercise 10: Configuring Multi-homed BGP D-78
Objectives D-78
Command List D-79
Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking xi

Setup D-80
Scenario D-80
Task 1: Enabling a Second EBGP Connection D-81
Laboratory Exercise 11: Super Lab I D-85
Part I D-85
Objectives D-85
Command List D-86
Setup D-86
Scenario D-86
Task D-88
Student Notes D-89
Laboratory Exercise 12: Super Lab II D-90
Part II D-91
Objectives D-92
Command List D-92
Setup D-92
Scenario D-92
Task D-94
Student Notes D-95
xii Building Scalable Cisco Internetworking Copyright  2001, Cisco Systems, Inc.
1 7 Click Here to Post Review Comments
2 Configuring IS-IS Protocol
3 Overview
4 This lesson provides an overview of Intermediate System-to-Intermediate System (IS-IS)
5 technology, and its structures and protocols, as well as basic configuration examples. The lesson
6 begins with Open System Interconnection (OSI) routing and then focuses on Integrated IS-IS as
7 a version that supports IP networks. Basic IS-IS and Integrated IS-IS router configuration
8 commands, examples, and some troubleshooting guidelines are presented at the end of the
9 lesson. The major part of this lesson is dedicated to an explanation of IS-IS concepts and
10 capabilities, including hierarchy and addressing of OSI-based networks.
11 Outline
12 The lesson includes these sections:
13 n Objectives
14 n Introduction to OSI Protocols and IS-IS Routing
15 n Operation of IS-IS
16 n IP and OSI Routing with Integrated IS-IS
17 n Basic Integrated IS-IS Router Configuration
18 n Modeling WAN Networks in Integrated IS-IS
19 n Summary
20 n Review Questions
21 Objectives
22 This section lists the lesson objectives.
Objectives
Upon completing this lesson, you will be able to:

• Explain basic OSI terminology and network layer
protocols used in OSI
• Identify similarities and differences between
Integrated IS -IS and OSPF
• Identify characteristics of an effective addressing
plan for IS-IS deployment
• Explain how networks and interfaces are
represented in IS-IS
• List the types of IS -IS routers and their role in IS-IS
area design
• Describe the hierarchical structure of IS-IS areas
© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-2
Insert Slide here.

23 n Explain basic OSI terminology and network layer protocols used in OSI
24 n Identify similarities and differences between Integrated IS-IS and OSPF
25 n Identify characteristics of an effective addressing plan for IS-IS deployment
26 n Explain how networks and interfaces are represented in IS-IS
27 n List the types of IS-IS routers and their role in IS-IS area design
28 n Describe the hierarchical structure of IS-IS areas
7-2 Building Scalable Cisco Internetworks (BSCI) v1.2 Copyright  2001, Cisco Systems, Inc.
29 Objectives (cont.)
Objectives (cont.)
• Describe the concept of establishing adjacencies

• Describe the concepts of routing traffic transport and
database synchronization
• Explain the basic principles of area routing
• Explain IS-IS NBMA (non-broadcast multi-access
network) modeling solutions in switched WAN
networks
• Given an addressing scheme and other laboratory
parameters, identify the steps to configure Cisco
routers for proper Integrated IS-IS operation
• Identify verification methods which ensure proper
operation of Integrated IS-IS on Cisco routers
Insert Slide here.

30 n Describe the concept of establishing adjacencies
31 n Describe the concepts of routing traffic transport and database synchronization
32 n Explain the basic principles of area routing
33 n Explain IS-IS nonbroadcast multiaccess (NBMA) network modeling solutions in switched

34 WAN networks
35 n Identify the steps to configure Cisco routers for proper Integrated IS-IS operation, given an
36 addressing scheme and other laboratory parameters
37 n Identify verification methods that ensure proper operation of Integrated IS-IS on Cisco
38 routers
Copyright  2001, Cisco Systems, Inc. Configuring IS-IS Protocol 7-3

39 Introduction to OSI Protocols and IS-IS
40 Routing
OSI Protocols
ISO and OSI?

• The International Organization for
Standardization (ISO) has been constituted to
develop standards for data networking.
• The Open System Interconnection (OSI)
protocols represent an international
standardization program that facilitates
multivendor equipment interoperability.
Insert Slide here.

41 The OSI protocols are part of an international program to develop data-networking protocols
42 and other standards that facilitate multivendor equipment interoperability. The OSI program
43 grew out of a need for international networking standards and is designed to facilitate
44 communication between hardware and software systems despite differences in underlying
45 architectures.
46 The OSI specifications were conceived and implemented by two international standards
47 organizations: the International Organization for Standardization (ISO) and the International
48 Telecommunication Union Telecommunication Standardization Sector (ITU-T).
49 The world of OSI internetworking includes various network services with these characteristics:
50 n Independence of underlying communications infrastructure
51 n End-to-end transfer
52 n Transparency
53 n Quality of service (QoS) selection
54 n Addressing
OSI Protocols (cont.)
The OSI protocol suite supports:

• Numerous standard protocols at each layer of
the OSI reference model
• OSI network-layer
hierarchical addressing
• Two routing protocols at the
network layer
Insert Slide here.

55 The OSI protocol suite supports numerous standard protocols at the physical, data-link, network,
56 transport session, presentation, and application layers.
57 OSI network-layer addressing is implemented by using two types of hierarchical addresses:
58 network service access point (NSAP) addresses and network-entity titles. An NSAP is a
59 conceptual point on the boundary between the network and the transport layers. The NSAP is
60 the location at which OSI network services are provided to the transport layer. Each transport-
61 layer entity is assigned a single NSAP, which is individually addressed in an OSI internetwork
62 using NSAP addresses.
63 The OSI protocol suite specifies two routing protocols at the network layer: End System-to-
64 Intermediate System (ES-IS) and Intermediate System-to-Intermediate System (IS-IS). In
65 addition, the OSI suite implements two types of network services: connectionless service and
66 connection-oriented service.

OSI Protocols—
Terminology
Terminology used in OSI

• End system (ES) is any nonrouting
network nodes (host)
• Intermediate system (IS) is a router
• An area is a logical entity
–Formed by a set of contiguous routers,
hosts, and the data links that connect them
• Domain is a collection of connected areas
Insert Slide here.

67 In an OSI network four significant architectural entities exist: hosts, areas, a backbone, and a
68 domain. A domain is any portion of an OSI network that is under a common administrative
69 authority. Within any OSI domain, one or more areas can be defined. An area is a logical entity;
70 it is formed by a set of contiguous routers and the data links that connect them. All routers in
71 the same area exchange information about all the hosts that they can reach. The areas are
72 connected to form a backbone. All routers on the backbone know how to reach all areas. The
73 term “end system” (ES) refers to any nonrouting host or node; “intermediate system” (IS)
74 refers to a router. These terms are the basis for the OSI ES-IS and IS-IS protocols.
OSI Protocol Suite and its Mapping to the
OSI Reference Model
Insert Slide here.

75 The OSI protocol suite supports numerous standard protocols at each of the seven OSI layers.
76 The figure here illustrates the entire OSI protocol suite and its relation to the layers of the OSI
77 reference model.

OSI Network Services—
What to Route in OSI Environment?
Two types of OSI network-layer services

are available to the OSI transport layer:
• Connectionless Network Service (CLNS)
–CLNS performs datagram transport
• Connection-Mode Network Service (CMNS)
–CMNS requires explicit establishment
of paths between communicating transport-
layer entities
Insert Slide here.

78 Connectionless Network Service (CLNS) uses a datagram data transfer service and does not
79 require a circuit to be established before data is transmitted. In contrast, Connection-Mode
80 Network Service (CMNS) requires a circuit to be established before transmitting data. While
81 CLNS and CMNS define the actual services provided to the OSI transport layer entitie s that
82 operate immediately above the network layer, Connectionless Network Protocol (CLNP) and
83 Connection-Oriented Network Protocol (CONP) name the protocols that these services use to
84 convey data at the network layer. CLNP is the OSI equivalent of IP.
Connection-Oriented Mode
CMNS/CONP:
• CONP is an OSI network-layer protocol that
carries upper-layer data and error indications
over connection-oriented links
• CMNS performs functions related to the
explicit establishment of paths via CONP
• When support is provided for CMNS, the
routing uses the X.25 protocols as the
relaying functions
© 2001, Cisco Systems, Inc. BSCI v1.2— 7-10
Insert Slide here.

85 CONP is based on the X.25 Packet-Layer Protocol (PLP) and is described in the ISO 8208
86 standard “X.25 Packet-Layer Protocol for DTE.”
87 CONP provides the interface between CMNS and upper layers. It is a network-layer service
88 that acts as the interface between the transport layer and CMNS and is described in the ISO
89 8878 standard. CMNS functions include connection setup, maintenance, and termination; it also
90 provides a mechanism for requesting a specific QoS.

Connectionless Mode
CLNP/CLNS:
• CLNP is an OSI network-layer protocol that
carries upper-layer data and error indications
over connectionless links
• CLNS provides network-layer services to the
transport layer via CLNP
• When support is provided for CLNS, the
routing uses routing protocols to exchange
routing information
Insert Slide here.

91 CLNP is an OSI network-layer protocol that carries upper-layer data and error indications over
92 connectionless links. CLNP provides the interface between CLNS and upper layers. CLNS
93 does not perform connection setup or termination because paths are determined independently
94 for each packet that is transmitted through a network. In addition, CLNS provides best-effort
95 delivery, which means that no guarantee exists that data will not be lost, corrupted, misordered,
96 or duplicated. CLNS relies on transport-layer protocols to perform error detection and
97 correction.
OSI Network Services—Routing
Protocols
ISO has developed standards for two

types of protocols:
• ES-IS dicovery protocols: “routing” between
End Systems and Intermediate Systems
referred as level-0 “routing”
• IS-IS routing protocols: hierarchical
(level-1, level-2 and level-3) routing between
Intermediate Systems
Insert Slide here.

98 The OSI protocol suite includes several routing protocols and one router discovery protocol (ES-
99 IS, an analog to Address Resolution Protocol [ARP] in IP). Although not explicitly a routing
100 protocol, ES-IS is included in this lesson because it is commonly used with routing protocols to
101 provide end-to-end data movement through an internetwork.
102 To simplify router design and operation, OSI distinguishes between level-1, level-2, and level-3
103 routing. Level-1 ISs communicate with other level-1 ISs in the same area. Level-2 ISs route
104 between level-1 areas and form an intradomain routing backbone. Level-3 routing is done
105 between separate domains.
106 Hierarchical routing simplifies backbone design, because level-1 ISs only need to know how to
107 get to the nearest level-2 IS.

OSI Network Services—OSI Routing
in Operation
Level-3
Level-3 routing between separate domains
Domain
IS IS
Level-2 routing between different
Level-2 routing between different
areas
areas within
within the
the same
same domain
domain
Area-1
Area-2
IS IS
Level-1
Level-1 routing
routing between
between ISs
ISs
within the same area
Level-0
Level-0 routing
routing between
between ESs
ESs and
and
ES ES
ISs on the
the same
same subnet
subnet
Insert Slide here.

108 Each ES lives in a particular area. OSI routing begins when the ESs discover the nearest IS by
109 listening to Intermediate System Hello (ISH) packets. When an ES wants to send a packet to
110 another ES, it sends the packet to one of the ISs on its directly attached network (level-0
111 routing). The router then looks up the destination address and forwards the packet along the
112 best route. If the destination ES is on the same subnetwork, the local IS will know this from
113 listening to End System Hello (ESH) packets and will forward the packet appropriately. The IS
114 also might provide a redirect message back to the source to tell it that a more direct route is
115 available.
116 If the destination address is an ES on another subnetwork in the same area, the IS will know the
117 correct route (level-1 routing) and will forward the packet appropriately.
118 If the destination address is an ES in another area, the level-1 IS sends the packet to the nearest
119 level-2 IS (level-2 routing). Forwarding through level-2 ISs continues until the packet reaches a
120 level-2 IS in the destination area. Within the destination area, ISs forward the packet along the
121 best path until the destination ES is reached.
122 Routing between separate domains is referred to as level-3 routing.
OSI Network Services—IS-IS Routing
Intermediate System to Intermediate

System (IS-IS) is a dynamic link-state
routing protocol in ISO CLNS environment
for routing CLNP
• Link-state routing protocol in the OSI stack
Alternative to IS-IS protocols is deploying
CISCO ISO-IGRP or static routing
Insert Slide here.

123 For routing in the ISO CLNS/CLNP environment, Cisco routers support these protocols:
124 n IS-IS: Routers usually operate as ISs and can exchange reachability information with other
125 ISs using the IS-IS protocol. As an IS, a Cisco router can operate at level 1 only, at level 2
126 only, or at both levels. In the last case, the router can advertise itself at level 1 as an exit
127 point from the area. Integrated IS-IS allows the IS-IS protocol to propagate routing
128 information for other protocols as well as, or instead of, CLNS. Specifically, IS-IS can route
129 CLNS, IP, or both (“dual” mode).
130 n ISO-IGRP: Cisco routers have available a proprietary routing protocol for CLNS. ISO-
131 IGRP is, as its name suggests, based on Cisco’s Interior Gateway Routing Protocol (IGRP).
132 It uses distance vector technology to propagate routing information. As such, it shares some
133 of the limitations of its IP counterpart, including long convergence times (due to periodic
134 updates and long invalid-times and holdtimes).
135 n Static CLNS routes: As with IP, static CLNS routes can be created.

Recommended Reading
• ISO 8473—documents ISO Connectionless

Network Protocol (CLNP)
• ISO/IEC 8348 Appendix A—documents NSAP
addresses
• ISO 9542—documents the ES-IS routing
exchange protocol
• ISO/IEC 10589—documents IS-IS intradomain
routing exchange protocol
Insert Slide here.

136 Various aspects of IS-IS are described in these ISO documents:
137 n ISO 8473: Documents the ISO CLNP.
138 n ISO/IEC 8348, Appendix A: Documents NSAP addresses.
139 n ISO 9542: Documents the ES-IS routing exchange protocol.
140 n ISO/IEC 10589: Documents the IS-IS intradomain routing exchange protocol.
141 Additionally, the function of Integrated IS-IS - the use of OSI IS-IS for routing in TCP/IP and
142 dual environments - is described in RFC 1195.
Integrated IS-IS vs. OSPF
Integrated IS-IS is an extended

version of IS-IS for mixed ISO CLNS
and IP environments
• Integrated IS-IS (RFC 1195) represents
an alternative to OSPF in the IP world
• Integrated IS-IS and OSPF are both
link-state protocols with similar:
–Link-state representation, aging, metrics
–Link-state databases, SPF algorithms
–Update, decision, and flooding processes
Insert Slide here.

143 IS-IS is the dynamic link-state routing protocol for the OSI protocol stack. As such, it distributes
144 routing information for routing CLNP data for the ISO CLNS environment.
145 Integrated IS-IS is an implementation of the IS-IS protocol for routing multiple network
146 protocols. Integrated IS-IS tags CLNP routes with information regarding IP networks and
147 subnets. It provides an alternative to OSPF in the IP world, mixing ISO CLNS and IP routing in
148 one protocol. It can be used purely for IP routing, purely for ISO routing, or for a combination of
149 the two.

Integrated IS-IS vs.
OSPF—Area Design
Area design
• OSPF is based on a central backbone with
all other areas being attached to it
–In OSPF the border is inside routers (ABRs)
–Each link belongs to one area
• In IS-IS the area borders lie on links
–Each IS-IS router belongs to exactly
one level-2 area
–IS-IS allows a more flexible approach
to extending the backbone
Insert Slide here.

150 Because the configuration of OSPF is based on a central backbone (area 0), with all other
151 areas, ideally, being physically attached to area 0, certain design constraints will inevitably exist.
152 When this type of hierarchical model is used, a good, consistent IP addressing structure is
153 necessary to summarize addresses into the backbone and reduce the amount of information that
154 is carried in the backbone and advertised across the network.
155 In comparison, IS-IS also has a hierarchy with level-1 and level-2 routers (area borders lie on
156 links). However, significantly fewer Link State Packets (LSPs; also known as Link State
157 PDUs) get used, and thus, many more routers (at least 1000) can reside in a single area. This
158 capability makes IS-IS more scalable than OSPF. IS-IS allows a more flexible approach to
159 extending the backbone. Adding further level-2 routers can extend the backbone. And this
160 process is less complex than with OSPF.
Integrated IS-IS vs.
OSPF— (cont.)
Resource usage
• One link-state packet per IS-IS router in one
area (including redistributed prefixes)
compared to many OSPF LSAs
Scalability of link-state protocols has
been proved (live ISP backbones)
• Convergence capabilities are similar
(same algorithm)
• OSPF has more features (route tags,
Stub/NSSA, OSPF over Demand Circuit…)
Insert Slide here.

161 With regard to CPU use and the processing of routing updates, IS-IS is more efficient. Not only
162 are there fewer LSPs to process (link-state advertisements [LSAs] in OSPF terminology) but
163 the mechanism by which IS-IS installs and withdraws prefixes is less intensive.
164 Both OSPF and IS-IS are link-state protocols and thus provide fast convergence. The
165 convergence time depends on a number of factors (timers, number of nodes, type of router,
166 etc.).
167 Based on the default timers, IS-IS will detect a failure quicker than OSPF and thus should
168 converge more rapidly. Of course, if there are many neighbors and adjacencies to consider, the
169 convergence time may also depend on the processing power of the router. IS-IS tends to be less
170 CPU intensive than OSPF.
171 The timers in IS-IS allow more tuning than OSPF. There are more timers to adjust, and thus
172 finer granularity can be achieved. By tuning the timers, convergence time can be significantly
173 decreased. However, this speed may be at the expense of stability, so a trade-off may have to
174 be made. The network operator should understand the implications of doing this.

175 Operation of IS-IS
OSI Address Assignment
OSI network-layer addressing is

implemented with network service access
point (NSAP) addresses
• NSAP address identifies any system
in OSI network
• Various NSAP formats for various systems
–Different protocols may use different
representation of NSAP
Insert Slide here.

176 The LSPs, hello PDUs, and other routing PDUs are OSI-format PDUs; therefore, every IS-IS
177 router requires an OSI address. IS-IS uses the OSI address in the LSPs to identify the router,
178 build the topology table, and build the underlying IS-IS routing tree.
179 OSI addresses take the form of NSAPs, containing:
180 n The OSI address of the device
181 n The link to the higher-layer process

182 The NSAP address can be thought of as equivalent to the combination of IP address and upper-
183 layer protocol in an IP header.
IS-IS NSAP Address—Structure
IS-IS (ISO/IEC 10589) distinguishes only three

fields in NSAP address:
• Area Address: variable-length field composed of
high-order octets, excluding System ID and SEL
• System ID: ES or IS identifier in an area;
fixed length of 6 octets in Cisco IOS
• NSEL: N-selector, service identifier
Insert Slide here.

184 Cisco routers can route CLNS data that uses addressing conforming to the ISO 10589 standard.
185 ISO NSAP addresses consist of these parts:
186 n The “Authority and Format ID” (AFI) byte specifies the format of the address and the
187 authority that assigned that address.
188 n The “Inter-Domain ID” (IDI) identifies this domain.
189 n The AFI and IDI together make up the “Inter-Domain Part” (IDP) of the NSAP address.
190 This can loosely be equated to an IP classful “major net.”
191 n The High-Order DSP is used for subdividing the domain into areas. This can be considered
192 loosely as the OSI equivale nt of a “subnet” in IP.
193 n The System ID identifies an individual OSI device. In OSI, a device has an address, just as
194 it does in DECnet (while in IP an interface has an address).
195 n The NSAP-Selector (NSEL) identifies a process on the device. It is a loose equivalent of a
196 port or socket in IP. The NSEL is not used in routing decisions.
197 n The HODSP, System ID, and NSEL together make up the Domain-Specific Part (DSP) of
198 the NSAP address.
199 ISO-IGRP routes are based on a three-level architecture: Domain (AFI + IDI, level-3), Area
200 (HODSP, level-2) and System ID (level-1).
201 IS-IS uses a simple two-layer architecture, joining the IDP and HODSP together and treating
202 them as its area-ID (level-2), with the remaining System ID used for level-1 routing.

OSI Addressing—IS-IS vs.
ISO-IGRP NSAPs
IS-IS NSAP is divided into three parts

• 1 octet NSEL , 6 octets for System ID, and from 1 to
13 octets for Area Address field
• Total length of NSAP from 8 (minimum) up to 20
octets (maximum)
ISO-IGRP NSAP is divided as follows:
• Area Address, composed of the first two octets
of the NSAP after the System ID and NSEL fields
• Domain, composed of high order octets
(from 1 to 11) of the NSAP, excluding the Area,
System ID, and NSEL fields
• ISO-IGRP requires at least 10 bytes of NSAP
Insert Slide here.

203 An OSI NSAP address can be up to 20 octets long.
204 The last byte is the N-Selector. Where the NSEL is set to 00, this identifies the device itself -
205 its network-level address. In this case, the NSAP is known as a NET (Network Entity Title).
206 Preceding the N-Selector is the System ID. OSI does not specify a fixed length for the System
207 ID, but Cisco IOS® does: IOS fixes the System ID as the 6 bytes preceding the 1-byte N-
208 Selector.
209 In IS-IS, everything to the left of the System ID is used as the area-ID. The minimum length of
210 this area-ID is a single byte; the maximum is the remaining 13 bytes permitted by the ISO
211 standard. Therefore, an NSAP for an IS-IS network could be as little as 8 bytes in length but is
212 usually longer to permit some granularity in the allocation of areas.
213 What IS-IS treats simply as the area-ID, ISO-IGRP splits into a domain and an area. ISO-
214 IGRP sets the 2 bytes to the left of the System ID as the area-ID, allowing for a theoretical
215 65,535 areas in an ISO-IGRP network. Everything else is treated as a Domain ID. Therefore,
216 the minimum length for an ISO-IGRP NSAP is 10 bytes (1-byte NSEL, 6-bytes System ID, 2-
217 bytes area, minimum 1-byte domain).
218 ISO-IGRP sends routing information based on domain (variable length), area (length fixed by
219 the protocol at 2 bytes), and finally by System ID (fixed at 6 bytes). The NSEL is not used by
220 ISO-IGRP.
OSI Addressing—
Network Entity Title
• Network Service Access Point (NSAP)—address

which (at the network layer) includes a service
identifier (“protocol number”)
• Network Entity Title (NET)—NSAP with service
identifier of 00
–Used in routers since they implement network
layer only (base for SPF calculation)
• The official NSAP prefixes are required for
CLNS routing—AFI 49 (Authority and Format
Identifier) denotes private address space
Insert Slide here.

221 If the upper-layer process ID is 00, then the NSAP refers to the device itself – that is, it is the
222 equivalent of the Layer 3 OSI address of that device. This is known as the NET.
223 The NET is used by routers to identify themselves in the LSPs and therefore forms the basis for
224 the OSI routing calculation.
225 Addresses starting with value 49 (AFI = 49) are considered as private addresses (analogous to
226 RFC 1918 for IP addresses). These addresses are routed by IS-IS. However, this group of
227 addresses should not be advertised to other CLNS networks.
228 Addresses starting with AFI values 39 and 47 represent ISO Data Country Code and ISO
229 International Code Designator, respectively.

OSI Addressing—NET and System
Identifier Rules
NET must begin with an octet
• 47.xxxx....;
• 0111.xxxx... Not 111.xxxx...
NET must end with a single octet set to 00,
identifying network entity (for example, router)
itself
• ...xxxx.00
System ID normally six octets (on Cisco six!)
and has to be the same length everywhere
Examples: 47.0001.0000.0c12.3456.00
01.1921.6811.1003.00
1047.0001.1234.5678.9101.00
Insert Slide here.

230 NETs and NSAPs must specify all hex digits and must start and end on a byte boundary.
231 Cisco IOS interprets the NSAP address as follows (from the right-hand end):
232 n The last byte is the N-Selector (NSEL) and must be specified as a single -byte length
233 (preceded by a “.”). A NET definition must set the N-Selector to “00”.
234 n The preceding six bytes are the System ID. IOS fixes this length at 6 bytes. It is customary
235 to use either a Media Access Control (MAC) address from the router, or (for Integrated
236 IS-IS) to code the IP address (for example, of a loopback interface) into the System ID.
237 n The rest of the address is treated by IOS as the area-ID.

238 — Can be any length up to 13 bytes.
239 — The Area Address can be as small as 1 byte, although this limits the scope for area
240 definitions. The customary simplest area-ID consists of 3 bytes, with an AFI of 1 byte
241 (47 in the figure) and 2 additional bytes for area-IDs (0001 in the figure) for an
242 effective area-ID of 47.0001.
243 — IOS will attempt to summarize the area-ID as far as possible. For example, if an IS-IS
244 network is organized with major areas subdivided into minor areas, and this is reflected
245 in the area-ID assignments:
246 n Between the minor areas, IOS will route based on the whole area-ID.
247 n Between the major areas, IOS will summarize into the area-ID portion up to the major area
248 boundary.
OSI Addressing—NSAP Examples
Example 1: NSAP 47.0001.aaaa.bbbb.cccc.00

• IS-IS: Area = 47.0001,
System ID = aaaa.bbbb.cccc, NSEL = 00
• ISO-IGRP: Domain = 47 Area = 0001,
System ID = aaaa.bbbb.cccc, NSEL = 00
Example 2: NSAP 39.0f01.0002.0000.0c00.1111.00

• IS-IS: Area = 39.0f01.0002,
System ID = 0000.0c00.1111, NSEL = 00
• ISO-IGRP: Domain= 39.0f01 Area = 0002,
System ID = 0000.0c00.1111, NSEL = 00
Insert Slide here.

249 1. The NSAP 47.0001.aaaa.bbbb.cccc.00 consists of:
250 n For IS-IS:

251 — Area = 47.0001
252 — System ID = aaaa.bbbb.cccc
253 — N-Selector = 00
254 n For ISO-IGRP:

255 — Domain = 47
256 — Area = 0001
257 — System ID = aaaa.bbbb.cccc
258 — N-Selector = ignored by ISO-IGRP
259 2. The NSAP 39.0f01.0002.0000.0c00.1111.00 is regarded:
260 n By IS-IS:
261 — Area = 39.0f01.0002
262 — System ID = 0000.0c00.1111
263 — N-Selector = 00

264 n By ISO-IGRP:
265 — Domain = 39.0f01
266 — Area = 0002
267 — System ID = 0000.0c00.1111
Identifying Systems in IS-IS
The area address uniquely identifies

the routing area and the System ID
identifies each node
• All routers within an area must use the same
area address
• An ES may be adjacent to a level-1
router only if they both share a common area
address
• Area address is used in level-2 routing
Insert Slide here.

268 The area-ID is associated with the IS-IS routing process – a router can be a member of only
269 one level-2 area. Other restrictions are as follows:
270 n All routers in an area must use the same area address. Indeed, it is the shared area address
271 that actually defines the area.
272 n ESs will recognize only ISs (and ESs on the same subnetwork) that share the same area
273 address.
274 n Area routing (level-1) is based on System IDs. Therefore, each device (ES and IS) must
275 have a unique System ID within the area.
276 n All level-2 ISs come to know about all other ISs in the level-2 backbone. Therefore, they,
277 too, must have unique System IDs.

Identifying Systems
in IS-IS—System ID
System ID may be the MAC address

(CLNS) or IP address of an interface
(IP world)
• System ID used in level-1 routing and has to
be unique within an area (and of same length)
• System ID has to be unique within level-2
routers that form routing domain
• General recommendation: domain-wide
unique System ID
Insert Slide here.

278 The System ID must be unique inside an area. It is customary to use either a MAC address
279 from the router, or (particularly for Integrated IS-IS) to code the IP address (for example, of a
280 loopback interface) into the System ID.
281 It is generally recommended that the System IDs remain unique across the domain; that way
282 there can never be a conflict at level 1 or level 2 if a device is moved into a different area, for
283 example.
284 All the System IDs in a domain must be of equal length. This is an OSI directive; Cisco
285 enforces this by fixing the length of the System ID at 6 bytes in all cases.
Identifying Systems—Subnetwork
and Circuit
SNPA (Subnetwork Point of Attachment)
identified by:
• Encapsulation type or DLCI address
on point-to-point interfaces (HDLC, FR)
• MAC address on LAN interfaces (0000.0c12.3456)
Interfaces uniquely identified by Circuit ID:
• One octet number on point-to-point interfaces (03)
• Circuit ID concatenated with 6 octet System ID
of a designated router on broadcast multiaccess
networks to form 7 octet LAN ID-
(1921.6811.1001.03)
Insert Slide here.

286 Some more IS-IS terms are:
287 n A subnetwork point of attachment (SNPA) is the point at which subnetwork services are
288 provided. This is the equivalent of the Layer 2 address corresponding to the Layer 3 (NET
289 or NSAP) address and is therefore usually a MAC address on a LAN or Virtual Circuit ID
290 in X.25, Frame-Relay, or ATM.
291 n A circuit is an interface.

292 A link is the path between two neighbor ISs and is defined as being “up” when communication
293 is possible between the two neighbors’ SNPAs.
294 SNPA is taken from:
295 n The MAC address on a LAN interface
296 n The Virtual Circuit ID from X.25 or ATM and the data-link connection identifier (DLCI)
297 from Frame-Relay
298 For High-Level Data Link Control (HDLC) interfaces, the SNPA is simply HDLC.
299 The router assigns a Circuit ID (one octet) to each interface on the router.
300 n In the case of point-to-point interfaces, this is the sole identifier for the circuit - for example,
301 “03”.
302 n In the case of LAN interfaces, this circuit ID is tagged to the end of the System ID of the
303 designated IS to form a 7-byte LAN ID - for example, 1921.6811.1001.03.

Identifying Systems—OSI
Addressing in Network
39.0002.4444.4444.4444.00 39.0003 .7777.7777.7777.00
39.0002 .5555.5555.5555.00
39.0002 .3333.3333.3333.00
39.0002 .6666.6666.6666.00
39. 0004.8888.8888.8888.00
39.0004 .9999.9999.9999.00
39.0001 .2222.2222.2222.00
39.0001.1111.1111.1111.00
Insert Slide here.

304 The diagram shows examples of NETs for routers in an IS-IS domain:
305 n The 1-byte N-Selectors (set to “00” indicating these are NETs)
306 n The 6-byte System IDs, unique across the network
307 n The 3-byte area-IDs, common to areas and distinct between areas.
ISO IS-IS—IS-IS PDU
IS-IS protocol data units (PDUs) are

encapsulated directly into a data-link
frame
There is no CLNS or IP header in a PDU:
• Hello (ESH, ISH, IIH)
• LSP (nonpseudonode and pseudonode)
• PSNP (partial sequence number PDU)
• CSNP (complete sequence number PDU)
Insert Slide here.

308 IS-IS protocol data units (PDUs) are encapsulated directly into an OSI data-link frame. There is
309 no CLNP header and no IP header.
310 The four types of IS-IS PDU are:
311 n Hello PDU (ESH, ISH, IS-IS Hello [IIH]): Used to establish and maintain adjacencies
312 n LSP: Used to distribute link-state information
313 n Partial sequence number PDU (PSNP): Used to acknowledge and request link-state
314 information
315 n Complete sequence number PDU (CSNP): Used to distribute a router’s complete link-
316 state database

ISO IS-IS PDU—(cont.)
PDU (protocol data unit) between peers

• Network PDU = datagram, packet
• Data-link PDU = frame
Data-link header IS-IS header (first
IS-IS: (OSI family 0xFEFE) IS-IS TLVs
byte is 0x83)
Data-link header ES-IS header (first

ES-IS: ES-IS TLVs
(OSI family 0xFEFE) byte is 0x82)
Data-link header CLNP header (first

CLNP CLNS
(OSI family 0xFEFE) byte is 0x81)
Insert Slide here.

317 The OSI stack defines a unit of data as a PDU. A frame is therefore regarded by OSI as a
318 data-link PDU, and a packet (or datagram, in the IP world) is regarded as a network PDU.
319 Three types of PDUs (802.2 Logical Link Control encapsulation) are shown in the figure. From
320 these it can be seen that the IS-IS and ES-IS PDUs are encapsulated directly in a data-link
321 PDU, while true CLNP (data) packets contain a full CLNP header between the data-link
322 header and any higher-layer CLNS information.
323 The IS-IS and ES-IS PDUs contain variable -length fields, depending on the function of the
324 PDU. Each field contains a type code, a length, and then the appropriate values, hence the
325 abbreviation TLV: Type, Length, Value fields.
Link State Packets—Network
Representation
Generally, physical links can be placed in two
groups:
• Broadcast—multiaccess subnetworks that support
addressing of a group of attached systems (LANs)
• Point-to-point links, multipoint links, dynamically
established links
Only two link-state representations are
available in IS-IS:
• Broadcast for LANs
• Point-to-point for all other topologies
Insert Slide here.

326 In the OSI model, two main types represent physical links:
327 n Broadcast: multiaccess media types that support addresses referring to groups of attached
328 systems and are typically LANS.
329 n Nonbroadcast: media types that must address ESs individually and are typically WAN
330 links.
331 Consequently, IS-IS supports only two media representations for its link states:
332 n Broadcast for LANs
333 n Point-to-point for all other media
334 Note IS-IS has no concept of an NBMA network. It is recommended that point-to-point links (for
335 example, subinterfaces) be used over NBMA networks such as native ATM (that is, not
336 LAN emulation [LANE]), Frame Relay, or X.25.

Link State Packets
Representing Routers
Router describes
itself with the
LSP Header Link State Packet (LSP)
• LSP header contents:
– PDU type, Length, LSP
ID, Sequence Number,
IS neighbors Remaining Lifetime
• Type Length Value (TLV)
variable-length fields:
ES neighbors – IS neighbors
– ES neighbors
............... – Authentication
Information
– ....
Insert Slide here.

337 In IS-IS a router describes itself with an LSP. The router’s LSP contains:
338 n An LSP header, describing:

339 — The PDU type and length
340 — The LSP ID and sequence number (used to identify duplicate LSPs and to ensure the
341 latest LSP information is stored in the topology table)
342 — The remaining lifetime for this LSP (used to age-out LSPs)
343 n Type Length Value (TLV) variable -length fields:

344 — The router’s neighbor ISs (used to build the map of the network)
345 — The router’s neighbor ESs
346 — Authentication information (used to secure routing updates)
347 — Attached IP subnets (optional for Integrated IS-IS)
LSP Representing
Routers—LSP Header
LSPs are sequenced to prevent duplication

of LSPs
• Assists with synchronization
• Sequence numbers begin with 1
Sequence numbers are increased to
indicate newest LSP
• LSPs in LSDB have a remaining lifetime
• Allows synchronization
• Decreasing timer
Insert Slide here.

348 LSPs are given sequence numbers, to enable receiving routers to ensure they use only the latest
349 LSPs in their route calculations and to avoid duplicate LSPs being entered in the topology tables.
350 When a router reloads, the sequence number is set initially to 1. The router may then receive its
351 own old LSPs back from its neighbors (which will have the last good sequence number before
352 the router reloaded). It records this number and reissues its own LSPs with the next highest
353 sequence number.
354 Each LSP has a “remaining lifetime” that is used by the LSP ageing process to ensure that
355 outdated and invalid LSPs are removed from the topology table after a suitable period. (Count to
356 zero operation - 1200 is a default start value.)
357

LSP Representing Routers—LAN
Representation
Pseudonode—logically
“connected” to all other nodes
IS DIS IS
IS IS
Logical
NOTE: All (physical) routers still phisycal
establish adjacency to each other
Insert Slide here.

358 Dijkstra’s algorithm requires a virtual router (pseudonode) for broadcast media to build a
359 directed graph.
360 For this reason, the Designated Intermediate System (DIS) is elected (by configurable priority,
361 then by highest MAC address) to generate an LSP representing a virtual router connecting all
362 attached routers to a star-shaped topology.
363 In IS-IS all routers on the LAN establish adjacencies with all other routers and with the DIS.
364 Thus, if the DIS fails, another router can take over immediately with little or no impact on the
365 topology of the network.
366 In OSPF, once the Designated Router (DR) and a Backup DR (BDR) are elected, the other
367 routers on the LAN establish adjacencies only with the DR and BDR (the BDR is elected and
368 then promoted to DR, in case of DR failure).
LSP Representing Routers—
Variables
Router specific information is encoded in

the variable field with TLVs
(Type Length Value)
Metric is associated with an outgoing
interface
• Four types (three optional, intended to be
used in Type of Service (ToS) routing)
• Delay, default, expense, and error—Cisco
uses default metric only
Insert Slide here.

369 The LSPs include specific information about the router’s attachments. This information is
370 included in multiple TLV fields in the main body of the LSP:
371 n The links to neighbor routers (ISs), including the metrics of those interfaces
372 n The links to neighbor ESs

373 — If Integrated IS-IS is operational, the attached IP subnets are described as ESs, using a
374 special TLV specified for IP information.
375 The metrics of IS-IS links are associated with the outgoing interface toward the neighbor IS
376 (router). Up to four metrics can be specified:
377 n Default (required): The only metric supported by Cisco IOS.
378 n Delay, Expense, and Error (optional): Intended for use in Type of Service (ToS)
379 routing. These could be used to calculate alternative routes referring to the DTR (Delay,
380 Throughput, Reliability) bits in the IP ToS field.
381

L1, L2 and L1/L2 Routers
Two-level structure of areas forms IS-IS
domains
Intermediate Systems can be:
• L1, level 1 (equivalent to OSPF internal
nonbackbone routers), responsible for
intra-area routing
• L1/L2, level 1-2 (in OSPF these are area-border
routers), performing intra- and
interarea routing
• L2, level 2 (backbone routers in OSPF),
interarea only
Insert Slide here.

382 An IS-IS network is termed a domain (the equivalent of an autonomous system [AS]). Within
383 the domain is a two-level hierarchy:
384 n Level-1 ISs (the equivalent of OSPF internal nonbackbone routers) are responsible for
385 routing to ESs inside an area.
386 n Level-2 ISs (backbone routers in OSPF) route between areas only.
387 n Level-1-2 Intermediate ISs (equivalent to area border routers [ABRs] in OSPF) route
388 between areas and the backbone. They participate in the level-1 intra-area routing and the
389 level-2 interarea routing.
L1 and L2 Routers
Level-1 (L1) routers referred to as

station routers
• L1 routers constitute an area
• L1 routers keep one copy of the link-state
database (its own area “picture”; intra-area
information only)
• They enable “stations” (ESs) to communicate
Level-2 (L2) routers referred to as area routers
• They store interarea information
• They interconnect areas
Insert Slide here.

390 Level-1 routers are also referred to as station routers because they enable stations (ESs) to
391 communicate with each other and the rest of the network.
392 A contiguous group of level-1 routers defines an area. The level-1 routers maintain the level-1
393 database, which defines the picture of the area itself and its exit points to neighboring areas.
394 Level-2 routers are also referred to as area routers because they interconnect the level-1 areas.
395 Level-2 routers store a separate database, which contains only the interarea topology
396 information.

L1/L2 Router
• Level 1-2 (L1/L2) routers keep two separate

copies of link-state databases
–For level 1 and level 2
–Inform L1 routers about an exit point
• Level 1 area is a collection of
L1 and L1/L2 routers
• Backbone area (level 2) is a set of L1/L2 and
L2 routers and has to be contiguous
Insert Slide here.

397 Level 1-2 routers act as if they were two IS-IS routers:
398 n They support a level-1 function to communicate with the other level-1 routers in their area
399 and maintain the level-1 LSP information in a level-1 topology database. They inform other
400 level-1 routers that they are an exit point from the area.
401 n They support a level-2 function to communicate with the rest of the backbone and maintain
402 a level-2 topology database separately from their level-1 database.
403 IS-IS does not share the concept of an area 0 with OSPF. Rather, it can appear as a set of
404 distinct areas interconnected by a chain of level-2 routers, weaving their way through and
405 between the level-1 areas.
L1, L2 and L1/L2 —LSP Features
Two-level nature of IS-IS requires separate

types of link-state packets
• Level 1 and level 2 LSPs
Designated IS is a representative of a LAN
and performs additional duties
• Pseudo level 1 and level 2 LSPs on behalf of the
LAN—separate DIS for L1 and L2;
no backup DIS
LSPs sent to a unicast address on
point-to-point links and to a multicast address
on broadcast multiaccess networks
Insert Slide here.

406 IS-IS uses a two-level hierarchy. The link-state information for these two levels is distributed
407 separately, giving rise to level-1 LSPs and level-2 LSPs.
408 LSPs on point-to-point links are sent to a unicast address. LSPs on broadcast media (LANs)
409 are sent to a multicast address.
410 As with OSPF, one router on a LAN sends out the LSP information on behalf of that LAN. In
411 IS-IS this router is called the DIS. It creates a pseudonode, the representation of the LAN, and
412 sends out the separate level-1 and level-2 LSPs for this pseudonode.

Example #1: Area Configuration—
Physical View
R2 and R3 belong to their respective level-1 areas
and provide a physical connection between them
L1L2 routers
R2 R3
Area-1 Area-2
R1 R4
L1 routers
Insert Slide here.

413 Physically, a level-1-2 router connects to level-1 routers inside its area and to level-2 routers in
414 the backbone.
415 Note The boundary between areas in IS-IS exists on a link between routers and not on an ABR
416 itself, as in OSPF.
Example #1: Area Configuration—
Logical View
R2 and R3 are still L1 routers, but, in addition, they
provide an entry point to the level-2
backbone interconnecting both level-1 areas
R2 L2 R3
L2
L1
L1 L1
R1 R4
Insert Slide here.

417 Logically, the level-1-2 router acts (for the purposes of IS-IS routing) as if it were two logical
418 routers. It operates a:
419 n Level-1 routing process (with its own level-1 topology table and adjacency table) to other
420 level-1 routers (and ESs)
421 n Level-2 routing process (with a separate level-2 topology table and a separate level-2
422 adjacency table) to its neighbor backbone routers

Example #2: L2 and L1/L2 Routers
Forming L2 Backbone
This router must behave as level 2 as
as well
well in
in order
order
to guarantee backbone continuity.
continuity.
Area-3
L1L2 L2-only
L1-only
L1L2
L1L2
Area-2 L1-only
Area-4
L1L2 L1-only
L1L2
Area-1
L1-only IS-IS domain
Backbone
links
Insert Slide here.

423 For example:
424 n Area 1 contains two routers:

425 — One router borders to area 2 and therefore is a level-1-2 IS.
426 — The other router is contained totally within the area and therefore is level-1-only.
427 n Area 2 has many routers:

428 — Some routers are specified as level-1-only and can route internally to that area only
429 (and to the exit points).
430 — Level-1-2 routers form a chain across the area linking to the neighbor areas.
431 — Even though the middle of these three level-1-2 routers does not link directly to another
432 area, it must support level-2 routing so the backbone is contiguous.
433 — If that middle router fails, the other level-1-only routers (though providing a physical
434 path across the area) could not perform the level-2 function, and the backbone would be
435 broken.
436 n Area 3 contains one router that borders to area 3, but has no intra-area neighbors, and is
437 therefore level-2-only. In the event that another router was added to area 3, the border
438 router would revert to level-1-2.
439 The diagram also shows that the border between the areas in an IS-IS network exists on the
440 links between level-2 routers (in contrast to OSPF where the border exists inside the ABR
441 itself).
Identifying Types of
Systems—Hello Messages
Periodic hello messages (hello PDU) are used,

as in any other link-state protocol
Three types:
• ESH (End System Hello), between ES and IS
• ISH (Intermediate System Hello), sent by
IS to ES
• IIH (IS-IS Hello, used between two ISs)
HELLOS carry information on the system itself,
its capabilities and interface parameters
Insert Slide here.

442 IS-IS uses hello PDUs to establish adjacencies with other routers (ISs) and ESs. Hello PDUs
443 carry information about the system, its parameters and capabilities.
444

Identifying Types of Systems— ES
and IS Hello Packets
ES ES ES
SNPA ESH
ES-IS
ISH
IS IS-IS IS
IIH SNPA
IS
Insert Slide here.

445 There are three types of hello PDUs:
446 n The ESH is sent from an ES to an IS.
447 n The ISH is sent from an IS to an ES.
448 n The IIH is used between ISs.

449
IS-IS and ES-IS Communication
Intermediate Systems establish and maintain

neighbor relationships through the use of IS-IS
hellos (IIHs)
• Then they exchange LSPs
End Systems do not need any configuration for
finding their respective IS
• End Systems listen to Intermediate System
Hellos (ISHs) to find their “way to the world”
• Initially ES picks a router randomly
(whichever is heard)
Insert Slide here.

450 ISs use IIHs to establish and maintain their neighbor relationships. Once an adjacency is
451 established, the ISs exchange link-state information with LSPs.
452 ISs also send out ISHs. ESs listen for these ISHs and randomly pick an IS (the first ISH they
453 hear) to forward all their packets to. Hence, OSI ESs require no configuration to forward
454 packets to the rest of the network.
455

IS-IS and ES-IS
Communication (cont.)
Routers listen to ESH and thus find all the

end systems on a segment
• Routers include information on end systems
in link-state packets
• Routers send redirect message to help ES in
finding the most optimal exit from a segment
Insert Slide here.

456 ISs listen to the ESHs and learn about all the ESs on a segment. ISs include this information in
457 their LSPs.
458 For particular destinations, ISs may send redirect messages to ESs to provide them with an
459 optimal route off the segment.
Neighbors and Adjacencies
IIH (IS-IS Hello) between routers

• Two types of HELLOS on LAN—L1 and L2
• Only one on p2p (with the type of desired adjacency
described—L1, L2 or both)
• HELLOS sent every 10 seconds, holdtime 30 seconds
(default)
Separate adjacencies are built for L1 and L2 routers
• L1/L2 routers keep two tables
Routers form adjacencies with all other routers
and send LSPs to all routers on the LAN
(unlike OSPF routers)
Insert Slide here.

460 Separate adjacencies are established for level 1 and level 2. If two neighboring routers in the
461 same area run both level 1 and level 2, they will establish two adjacencies, one for each level.
462 The level-1 and level-2 adjacencies are stored in separate level-1 and level-2 adjacency tables.
463 On LANs, the two adjacencies are established with specific Layer 1 and Layer 2 IIH PDUs.
464 Routers on a LAN establish adjacencies with all other routers on the LAN (unlike OSPF, where
465 routers establish adjacencies only with the designated router).
466 On point-to-point links there is a common IIH format, part of which specifies whether the
467 HELLO relates to level 1, level 2, or both.
468 By default, hello PDUs are sent every 10 seconds; the timeout to declare a neighbor down is 30
469 seconds (that is, missing three hello packets). These timers can be reconfigured.

LAN Adjacencies
Adjacencies are established based on the area address

announced in the incoming IIHs and the type of the
router
Area-1 Area-1
Area-1
L1 L1/L2 L1/L2
Area-1 L1 adjacency
Area-2 L2 adjanceny
L1 L1/L2
Insert Slide here.

470 IIH PDUs announce the area-ID. Separate IIH packets announce the level-1 and level-2
471 neighbors.
472 For example, where a LAN has routers from two areas attached:
473 n The routers from one area accept level-1 IIH PDUs only from their own area and therefore
474 establish adjacencies only with their own area routers.
475 n The routers from a second area similarly accept level-1 IIH PDUs only from their own
476 area.
477 n The level-2 routers (or the level-2 process within any level-1-2 router) accept only level-2
478 IIH PDUs and establish only level-2 adjacencies.
WAN Adjacencies
Area-1 Area-1 Area-1 Area-1

L1 L2
L1 L1 L2 L2

L1 L2
L1/L2 L2 L1/L2
L1

# L2
L1 L1/L2 L2 L1/L2
L1L2
Area-1 Area-1
L1/L2 L1/L2
Insert Slide here.

479 On point-to-point links (that is, on a WAN), the IIH PDUs are common to both levels but
480 announce the level type and the area-ID in the HELLOs.
481 n Level-1 routers in the same area (which includes links between level-1 only and level-1-2
482 routers) exchange IIH PDUs specifying level-1 and establish a level-1 adjacency.
483 n Level-2 routers (in the same area or between areas, and including links between level-2-
484 only and level-1-2 routers) exchange IIH PDUs specifying level-2 and establish a level-2
485 adjacency.
486 n Two level-1-2 routers in the same area establish both level-1 and level-2 adjacencies, and
487 maintain these with a common IIH PDU specifying both the level-1 and level-2 information.
488 n Two level-1 routers which may be physically connected but are not in the same area
489 (including a level-1 only to a level-1-2 router in a different level-1 area) exchange level-1
490 IIH PDUs but ignore these as the area-IDs do not match. Therefore, they do not establish
491 adjacency.

Continous Flow of L2 Adjacencies
Area-1 and Area-2 are level-1 areas

Level-2 backbone is a set of L1/L2 and L2 routers
and overlaps attached level-1 areas
L1-only
L1L2
Area-3
Area-2 L1L2
L2-only
L1L2
Area-1
L1 adjacencies
L1-only
L1L2 L2 adjacencies
L1 and L2 adjacencies
Insert Slide here.

492 The figure shows examples of:
493 n Level-1-only routers establishing level-1 adjacencies
494 n Level-2 routers establishing only level-2 adjacencies (between areas)
495 n Level-1-2 routers establishing both level-1 and level-2 adjacencies with their level-1-2
496 neighbors in the same area
497 Note L2 adjacency exists independent of area and must be contiguous (area 2 is n ot a
498 backbone area).
Link-State Database Synchronization
SNP (Sequence Number PDU) packets used

to ensure synchronization and reliability
• Contents are “LSP descriptions”
PSNP (Partial SNP) used:
• For acknowledgment of LSPs on p2p links
• To request missing pieces of link-state database
CSNP (Complete SNP) used:
• Periodically by DIS on LAN to ensure reliability
• On point-to-point link when the link comes up
Insert Slide here.

499 Sequence number PDUs (SNPs) ensure LSPs are sent reliably. SNPs contain LSP descriptors;
500 not the actual, detailed LSP information, but headers describing the LSPs.
501 PSNPs usually contain only one LSP descriptor block. They are used:
502 n To acknowledge receipt of an LSP
503 n To request a complete LSP for an entry missing in the originating router’s topology
504 database
505 CSNPs are a list of the LSPs held by a router.
506 n CSNPs are sent periodically on LANs. Receiving routers can compare the list of LSPs in
507 the CSNP with their link-state database and request (with a PSNP) any missing LSPs.
508 n CSNPs are sent on point-to-point links when the link comes active. In Cisco IOS, periodic
509 CSNPs can be configured on point-to-point links.

Link-State Database
Synchronization—P2P
R1 LSP 33 R3
III. ACK:
Thank you for
for s0
LSP 33 PSNP R2 I. Link
Link
went
went down
down
II. New
New LSP
LSP
describing
describing the
the
current
current situation
situation
Insert Slide here.

510 This figure shows the following example:
511 n A link fails.
512 n The middle router (R2) notices this failure and issues a new LSP noting the change.
513 n The left router (R1) receives the LSP, stores it in its topology table, and sends a PSNP back
514 to the middle router to acknowledge receipt of the LSP.
Link-State Database
Synchronization—LAN
CSNP sent periodically

(every 10 s) by DIS
R2/DIS I.
I. CSNP:
CSNP:
LSP76
LSP77
LSP88
PSNP
R1 II. Request:
Request:
Sorry.
Sorry. I CSNP
missed
missed LSP
LSP 77
77
PSNP
Insert Slide here.

515 The DIS periodically (every 10 seconds) sends CSNPs listing the LSPs it holds in its link-state
516 database. This is a broadcast to all IS-IS routers on the LAN.
517 In the example, the bottom-left router (R1) compares this list of LSPs with its topology table and
518 realizes it is missing one LSP. Therefore, it sends a PSNP to the DIS (R2) to request the
519 missing LSP. The DIS reissues that LSP, and the bottom-left router acknowledges it with a
520 PSNP as in the previous diagram (not shown).

521 IP and OSI Routing with Integrated IS-IS
Integrated IS-IS Routing Protocol
Integrated IS-IS allows for three types

of routing domains (OSI, IP, Dual)
Therefore, an IS-IS LSP may contain
multiple variable-length fields (TLV)
• Some contain OSI-specific information
• Some contain IP-specific information
Insert Slide here.

522 Integrated IS-IS supports three types of networks:
523 n OSI
524 n IP
525 n Dual (that is, both the above)

526 The LSPs can contain many variable -length TLV fields, describing:
527 n OSI state information
528 n IP state information
Integrated IS-IS—Representing
IP Networks
LSP describes IP information

in the same way as ESs
Integrated IS-IS has all the features
of modern routing protocols
• Variable-length mask
• Redistribution
• Summarization
Insert Slide here.

529 Integrated IS-IS LSPs describe IP information in a similar manner to the way IS-IS describes
530 ESs. There are specific TLV types for IP information.
531 Like all modern routing protocols, Integrated IS-IS supports:
532 n Variable -Length Subnet Masks (VLSMs) - the mask is sent with the prefix in the updates
533 n Redistribution of IP routes into and out of IS-IS
534 n Summarization of IP routes

Integrated
Integrated IS-IS—NET
Address Planning
Common CLNS parameters (NET)

and area planning are still required
even in an IP environment
• Even when Integrated IS-IS is used only
for IP routing, routers still establish CLNS
adjacencies and use CLNS packets
Insert Slide here.

535 IS-IS can be enabled on Cisco routers for:
536 n Pure CLNS support
537 n IP support (Integrated IS-IS), additional to CLNS, or for IP only

538 However, even if Integrated IS-IS is being used only for IP routing, a NET address is required
539 for Layer 2 forwarding and Dijkstra’s algorithm computation:
540 n OSI protocols are used to form the neighbor relationship between routers.
541 n SPF calculations rely on a configured NET address to identify the routers.
OSI Area Routing—Building
OSI Forwarding Table
• When databases are synchronized, Dijkstra
(SPF) algorithm is run on the LSDB to calculate
the SPF tree
– Criteria: the shortest path to the destination
is the lowest total sum of metrics
– Separate route calculations made for L1 and
L2 areas in L1/L2 routers
• Partial route calculation (PRC) run to calculate
ES reachability
• Best paths are placed in the OSI L1 and L2
forwarding tables
Insert Slide here.

542 To build the OSI forwarding database (the CLNS routing table):
543 n The link-state database is used to calculate the Shortest-Path-First (SPF) tree to OSI
544 destinations (NETs). The link metrics are totaled along each path to decide which is the
545 shortest to any given destination.
546 n There are separate link-state databases for level-1 and level-2 routes. Therefore, SPF is run
547 twice (once for each level), and separate SPF trees are created for each level.
548 n ES reachability is calculated with a partial route calculation (PRC) based on the above
549 level-1 and level-2 SPF trees. (There are no OSI ESs if it is a pure IP Integrated IS-IS
550 environment).
551 n The best paths are inserted in the CLNS routing table (OSI forwarding database).

OSI Area Routing
Level-1 intermediate systems

• Routing within the area is based on the
System ID portion of the ISO address
• If the destination belongs to another area, they route
to the nearest active level-1-2 router
Level-2 intermediate systems
• Routing between areas is based on the area address
and considers only the area cost
• If the destination belongs to the same area,
they use the least-cost path to the System ID
Insert Slide here.

552 Routing inside a level-1 area is based on the System ID of the destination OSI (NSAP) address.
553 OSI Packets to other areas are routed to the nearest level-1-2 router.
554 Level-2 routing is based on the area-ID. If a level-1-2 router receives a packet (from a level-2
555 neighbor) destined for its own area, it will route it as for level 1, based on the System ID.
OSI Area Routing—Routing
Between Areas
From level 1 via level 2 to level 1

• L1 always sends a packet to a nearest
active L1/L2 router (default routing)
• Then the packet travels via L2 routing
towards the destination area where the
best L1 path is used
Note: L1/L2 router performs L1 and
L2 routing
Insert Slide here.

556 When routing a packet from one area that is destined for another area:
557 n The level-1 routers route the packet to the nearest level-1-2 router. They find the closest
558 exit point from the area, based on receipt of default routes from the level-1-2 routers in their
559 area.
560 n The level-1-2 router routes the packets into the level-2 backbone based on the destination
561 area-ID. The packet travels across the level-2 backbone to the destination area.
562 n Once it arrives in the destination area, level-1 routing is again used to route the packet to its
563 final destination inside that area.
564 The interface between the level-1 world and the level-2 world takes place on a level-1-2 router.
565 The level-1-2 router behaves as if it were both a level-1 router (routing to level-1 destinations)
566 and a level-2 router (routing between areas).

OSI Area Routing—Suboptimal
Interarea Routing
R2 takes the closest exit; then
Area-2 L1L2 takes the closest entry
15 Area-3
R2
L2
10 10
L1L2 15
L1L2
L1L2 10 Area-4
10
10
L1L2 Area-5
R1 L2
10 Area-1 10
Network path from router R2 to R1
Network path from router R1 to R2
Insert Slide here.

567 The fact that level-1 routers see a default route only to the nearest level-2 routers can lead to
568 suboptimal routing, as shown in the diagram.
569 Router R1 routes packets to Router R2 to its level-1-2 router. This router looks at the
570 destination area and routes directly into area 2. Once in area 2, the packets are routed as level 1
571 (even though the initial next hop is another level-1-2 router, the routing is level 1) to Router R2.
572 Return packets from Router R2 to Router R1 are routed by R2 to its nearest level-1-2 router.
573 This router happens to see the best route to area 1 as being via area 4 and routes the return
574 packets by a different route to the incoming packets. The path taken is not actually the least
575 cost from R2 to R1.
576 Asymmetric routing (packets in different directions taking different paths) is not necessarily
577 detrimental to the network but can make troubleshooting difficult.
578 A feature available since IOS Release 12.0 allows level-2 routes to be leaked in a controlled
579 manner into the level-1 area to help avoid this situation.
OSI Area Routing— Interconnecting
IS-IS Domains
IS-IS routing domain is a collection

of IS-IS areas
When interconnecting IS-IS domains
the following applies:
• In pure IP-environment use BGP
• In pure CLNS use ISO-IGRP or static
CLNS routes
Insert Slide here.

580 An IS-IS domain is the equivalent of an IP AS.
581 IS-IS can support the interconnection of multiple domains:
582 n In a pure-OSI environment, ISO-IGRP (Cisco proprietary) interprets the initial domain
583 identifier (IDI) portion of CLNS routes and allows routing between domains. There is also a
584 standard OSI Interdomain Routing Protocol (IDRP), which provides the same function (but
585 is not supported by Cisco).
586 In an IP environment, an IP interdomain protocol is required. The most common of these is the
587 Border Gateway Protocol (BGP).

Example #1: OSI Intra- and
Interarea Routing
Routing in a two-level area structure

Area 49.0001 Area 49.0002
E0 E0
L2
S0
R2 - L1L2 R5 - L2
L1 S1
L1
S0
L1
R1 - L1 S1 R4 - L1
Insert Slide here.

588 This diagram forms the basis for the following examples.
Example #1—Level-1 and Level-2
Topology Table
R1#show
R1#show isis
isis topology
topology
IS-IS
IS-IS paths
paths to
to level-1
level-1 routers
routers
System
System Id
Id Metric
Metric Next-Hop
Next-Hop Interface
Interface SNPA
SNPA
R1
R1 --
R2 10 R2 Se0 *HDLC*
R4 10 R4 Se1 *HDLC*
R2#show
R2#show isis
isis topology
topology
IS-IS
IS-IS paths
paths to
to level-1
level-1 routers
routers
System
System Id
Id Metric
Metric Next-Hop
Next-Hop Interface
Interface SNPA
SNPA
R1 10 R1 Se0 *HDLC*
R2
R2 --
R4 10 R4 Se1 *HDLC*
IS-IS
IS-IS paths
paths to
to level-2
level-2 routers
routers
System
System Id
Id Metric
Metric Next-Hop
Next-Hop Interface SNPA
R2
R2 --
R5 10 R5 Et0 0010.7bb5.9e20
Insert Slide here.

589 The show isis topology command displays the least-cost paths to the destination NETs:
590 n The System ID shows the NET of the destination. IOS uses Dynamic Hostname Mapping
591 (RFC 2763) to map this to a hostname (a router’s hostname is included in its outgoing LSP),
592 where that hostname is available to the router.
593 n The Metric shows the sum of the metrics on the least-cost path to the destination.
594 n The next-hop router (IS) is shown, plus the interface through which that next hop is
595 reached, and the SNPA of that next hop (HDLC is shown as the next hop across a serial
596 line).
597 The output for Router R2 shows that separate topology databases exist for level 1 and level 2.

Example #1—Intra-area
Routing on R1
R1#show
R1#show clns
clns route
CLNS Prefix Routing
Routing Table
Table
49.0001.0000.0000.0001.00, Local NET Entry
R1#show
R1#show isis
isis route
IS-IS
IS-IS Level-1
Level-1 Routing
Routing Table
Table - version 312
System
System Id Next-Hop
Next-Hop Interface
Interface SNPA
SNPA Metric
Metric State
State
R2 R2 Se0
Se0 *HDLC*
*HDLC* 10 Up L2-IS
R4 R4 Se1
Se1 *HDLC*
*HDLC* 10 Up
Up
R1
R1 --
Default route out of area -- (via 2 L2-attached
L2-attached ISs)
ISs)
System
System Id Next-Hop
Next-Hop Interface
Interface SNPA
SNPA Metric
Metric State
State
R2 Se0 *HDLC*
*HDLC* 10 Up
Insert Slide here.

598 The show clns route command displays the CLNS destinations to which this router can route
599 packets. R1 shows only its local NET entry, because it is a level-1-only router and therefore has
600 no level-2 area routes to display.
601 The show isis routes command shows the level-1 routes to IS-IS neighbors. R1 has visibility
602 of the other level-1 routers in its area.
603 The level-1-2 routers appear in the level-1 routing table (by virtue of their level-1 connection)
604 with a note at the end of their entry to show that they also act at level 2. The closest level-1-2
605 router also appears as the default route out of area.
606 Again, the next-hop IS, its SNPA, the interface over which that next hop is reached, and the
607 summed metric to that destination are shown for all IS routes. The neighbors show that their
608 state is “up” - the hello process has established an adjacency.
Example #1—Intra- and Interarea
Routing on R2
R2#show
R2#show clns
clns route
CLNS Prefix Routing
Routing Table
Table
49.0001.0000.0000.0002.00, Local NET Entry
49.0002 [110/10]
[110/10]
via
via R5,
R5, IS-IS, Up, Ethernet0
49.0001
49.0001 [110/0]
[110/0]
via
via R2,
R2, IS-IS, Up
R2#show
R2#show isis
isis route
IS-IS
IS-IS Level-1
Level-1 Routing
Routing Table
Table - version 47
47
System
System Id
Id Next-Hop
Next-Hop Interface
Interface SNPA Metric State
R4
R4 R4 Se1 *HDLC*
*HDLC* 1010 Up
Up
R1 R1 Se0 *HDLC* 10 Up
Insert Slide here.

609 The same commands, executed on R2 give these results:
610 n show clns routing shows the local NET entry. It also shows the level-2 routes to its own,
611 and the neighbor, areas.
612 Note Level 2 regards the route to R2’s own area as being through itself - further emphasizing
613 that the level-1 and level-2 processes operate separately.
614 n show clns routes shows the IS-IS neighbors.

Example #1—Which Route in L1?
R1#which-route
R1#which-route 49.0001.0000.0000.0002.00
49.0001.0000.0000.0002.00 - (R2
(R2 NSAP)
NSAP)
Route
Route look-up
look-up for
for destination
destination 49.0001.0000.0000.0002.00
49.0001.0000.0000.0002.00
Found
Found route
route in IS-IS
IS-IS level-1
level-1 routing table
Adjacency
Adjacency entry
entry used:
used:
System
System Id
Id Interface
Interface SNPA
SNPA State
State Holdtime
Holdtime Type
Type Protocol
Protocol
0000.0000.0002
0000.0000.0002 Se0
Se0 *HDLC*
*HDLC* Up
Up 26
26 L1 IS-IS
IS-IS
Area
Area Address(es):
Address(es): 49.0001
49.0001
Uptime:
Uptime: 00:09:50
R1#which-route
R1#which-route 49.0002.0000.0000.0005.00
49.0002.0000.0000.0005.00 - (R5 (R5 NSAP)
Route
Route look-up
look-up for
for destination
destination 49.0002.0000.0000.0005.00
49.0002.0000.0000.0005.00
Using
Using route
route to
to closest
closest IS-IS
IS-IS level-2 router
router
Adjacency
Adjacency entry
entry used:
used:
System
System Id Interface SNPA State Holdtime Type Protocol
0000.0000.0002
0000.0000.0002 Se0
Se0 *HDLC*
*HDLC* Up
Up 27
27 L1 IS-IS
IS-IS
Area
Area Address(es):
49.0001
Uptime:
Uptime: 00:09:57
Insert Slide here.

615 An alternative method of finding the route to a destination NET or NSAP is to use the which-
616 route command.
617 In this case, the command is entered on the level-1-only router, R1.The command returns the
618 next hop to the destination and states whether the destination is reachable by level 1 or by the
619 default exit point to level 2.
Example #1—Which Route in L2?
R5#which-route
R5#which-route 49.0001.0000.0000.0002.00
49.0001.0000.0000.0002.00 (R2 NSAP)
NSAP)
Found
Found route
route in
in CLNS
CLNS L2
L2 prefix
prefix routing
routing table
table
Route entry used:
i 49.0001
49.0001 [110/10]
[110/10] via
via R2,
R2, Ethernet0/0
Ethernet0/0
Adjacency
Adjacency entry
entry used:
used:
System
System Id
Id Interface
Interface SNPA
SNPA State Hold. Type Prot
R2 Et0/0 0000.0c92.e515
0000.0c92.e515 UpUp 24
24 L2 IS-IS
IS-IS
Area
Area Address(es):
49.0001
R5#which-route
R5#which-route 49.0001.0000.0000.0001.00
49.0001.0000.0000.0001.00 (R1
(R1 NSAP)
NSAP)
Found route in CLNS L2L2 prefix
prefix routing
routing table
table
Route entry used:
i 49.0001
49.0001 [110/10]
[110/10] via
via R2,
R2, Ethernet0/0
Ethernet0/0
Adjacency
Adjacency entry
entry used:
used:
System
System Id Interface
Interface SNPA State Hold. Type Prot.
R2 Et0/0 0000.0c92.e515 Up 21 L2 IS-IS
Area
Area Address(es):
49.0001
Insert Slide here.

620 Executing the which-route command on a level-2 router specifies the next hop and also states
621 that the route was matched by an entry from the CLNS level-2 routing table.

Building IP Forwarding Table
PRC is also run to calculate IP reachability

• Since IP and ES are represented as leaf
objects they do not participate in SPF
Best paths are placed in the IP forwarding
table following IP preferential rules
• They appear as L1 or L2 IP routes
Insert Slide here.

622 So far, the process and outputs have referred to the OSI part of the IS-IS process. These are
623 the same as for pure OSI IS-IS routing.
624 However, in the IP world, when running Integrated IS-IS, IP information is included in the
625 LSPs. IP reachability behaves in IS-IS as if it were ES information.
626 IP information takes no part in the calculation of the SPF tree - it is simply information about
627 leaf connections to the tree. Therefore, updating the IP reachability is only a PRC (similar to ES
628 reachability).
629 IP routes are generated by the PRC and offered to the routing table, where they will be
630 accepted based on routing table rules comparing, for example, administrative distance. When
631 entered in the routing table, IP IS-IS routes are shown as being via level 1 or level 2, as
632 appropriate.
633 The separation of IP reachability from the core IS-IS network architecture gives Integrated IS-
634 IS better scalability than, for example, OSPF:
635 n OSPF sends LSAs for individual IP subnets. If an IP subnet fails, then the LSA is flooded
636 through the network and, in all circumstances, all routers must run a full SPF calculation.
637 n In an Integrated IS-IS, the SPF tree is built from CLNS information. If an IP subnet fails in
638 Integrated IS-IS, the LSP is flooded as for OSPF. However, if this is a leaf IP subnet (that
639 is, the loss of the subnet has not affected the underlying CLNS architecture), the SPF tree
640 is unaffected and, therefore, only a PRC happens.
Building IP Forwarding Table (cont.)
The IP addresses on loopbacks of routers are 1.0.0.1/8-

Area 49.0001 Area 49.0002
R1, 2.0.0.1/8-R2,
2.0.0.1/8-R2, 4.0.0.1/8-R4
4.0.0.1/8-R4 and 5.0.0.1/8-R5.
5.0.0.1/8-R5.
R2#sh ip route
i L1
L1 1.0.0.0/8
1.0.0.0/8 [115/10]
[115/10] via
via 10.12.0.1,
10.12.0.1, Ser0
Ser0 -(R1)
-(R1)
i L1
L1 4.0.0.0/8
4.0.0.0/8 [115/10]
[115/10] via
via 10.24.0.4,
10.24.0.4, Ser1
Ser1 -(R4)
-(R4)
i L2
L2 5.0.0.0/8
5.0.0.0/8 [115/10]
[115/10] via
via 11.0.0.10,
11.0.0.10, Eth0
Eth0 -(R5)
-(R5)
E0 L2
S0 R2 - L1L2
S1 R5- L2
L1
L1
L1
R1 - L1 R4 - L1
Insert Slide here.

641 show ip route shows IP IS-IS routes in the IP routing table. The “i” indicates that the route
642 was sourced from IS-IS; “L1” and “L2” show whether the IS-IS path to these destination IP
643 networks is via IS-IS level-1 or level-2 routing. The next-hop IP addresses are matched from
644 the corresponding next-hop IS-IS neighbor routers.

645 Basic Integrated IS-IS Router Configuration
Integrated
Integrated IS-IS Configuration Steps
Step1: Define areas, prepare addressing plan

(NETs) for routers, and determine
interfaces
Step2: Enable IS-IS in a router
Step3: Configure the NET
Step4: Enable Integrated IS-IS on the proper
interfaces—do not forget interfaces to
stub IP networks, such as loopbacks
(although no CLNS neighbors there)
Insert Slide here.

646 To enable Integrated IS-IS on a router for IP routing, you need only three commands (there are
647 many more commands to tune the IS-IS processes, but only three are required to start
648 Integrated IS-IS):
649 n Enable IS-IS as an IP routing protocol (router isis) and assign a tag to the process (if
650 required).
651 n Identify the router for IS-IS by assigning a NET to the router (net …).
652 n Enable IS-IS on the interfaces (ip router isis) that run IS-IS (this is slightly different to
653 most other IP routing protocols where the interfaces are defined by network statements -
654 there is no network statement under the IS-IS process).
655 To troubleshoot Integrated IS-IS, even in an IP-only world, requires some investigation of
656 CLNS data. For example, the IS-IS neighbor relationships are established over OSI, not over IP,
657 so to show IS-IS neighbors requires using the show clns neighbors command. Indeed, two
658 ends of a CLNS adjacency can actually have IP addresses on different subnets, with no impact
659 to the operation of IS-IS (although IP next-hop resolution could be an issue).
IS-IS Configuration Steps—IS-IS
Survival Kit Commands
router(config)#
router isis [tag]
• Enable the IS-IS routing protocol; tag—name for a process;

when routing of clns packet is also needed use the
clns routing command
router(config-router)#
net network-entity-title
• Configure an IS-IS NET address for the routing process
router(config-if)#
ip router isis [tag]
clns router isis [tag]
• Start an IS-IS routing process on an interface (IP, CLNS, both)
Insert Slide here.

660 The commands to enable Integrated IS-IS are:
661 n The router is-is (global configuration) command enables Integrated IS-IS on the router.
662 Optionally, a tag can be applied to identify multiple IS-IS processes - if it is omitted, IOS
663 assumes a tag of 0.
664 n After the IS-IS process is enabled, the router must be identified for IS-IS by assigning a
665 network-entity-title to the router with the net (config-router) command.
666 n Finally, interfaces that are to use IS-IS to distribute their IP information (and additionally
667 may be used to establish IS-IS adjacencies) must be configured using the ip router is-is
668 interface command. If there is more than one IS-IS process, interfaces must state which
669 IS-IS process they belong to by specifying the appropriate tag.
670 These commands enable Integrated IS-IS on the router. However, further commands may be
671 required to tune the IS-IS operation.

IS-IS Configuration Steps—IS-IS
Good to Know Commands
router(config-router)#
is-type {level-1 | level-1-2 | level-2-only}
• Configure the IS-IS level globally on a router;

default = L1/L2 (station/area)
router(config-if)#
isis circuit-type {level-1 | level-1-2 | level-2-only}
• Configure the type of adjacency on an interface;

default = L1/L2
router(config-if)#
isis metric default-metric {level-1 | level-2}
• Configure the metric for an interface; default = 10
Insert Slide here.

672 By default, Cisco IOS enables both level-1 and level-2 operations on IS-IS routers. If a router is
673 to operate only as an area router, or only as a backbone router, then this can be specified by
674 entering the is-type command (this is a router configuration command). To specify that the
675 router will act only as an area (or level-1) router, specify is-type level-1. To specify that the
676 router will act only as a backbone (or level-2) router, specify is-type level-2-only.
677 Similarly, although the router may be a level-1-2 router, it may be required to establish level-1
678 adjacencies only over certain interfaces and level-2 adjacencies over other interfaces. Thus, the
679 interface command isis circuit-type can specify either level-1 or level-2-only. If this is not
680 specified, the IOS will attempt to establish both types of adjacency over the interface.
681 Unlike some other IP protocols, IS-IS takes no account of line speed or bandwidth when setting
682 its link metrics. All interfaces are assigned a metric of 10. To change this value, you need to use
683 the interface command isis metric <value > level-1 |level-2. The metric can have different
684 values for level 1 and level 2 over the same interface.
IS-IS Configuration Steps—Simple
Integrated IS-IS Example
The configured router acts as IP-only L1/L2 router
router
router isis
isis
net 01.0001.0000.0000.0002.00
01.0001.0000.0000.0002.00
!!
interface
interface ethernet 0
ip address 10.1.1.1 255.255.255.0
ip router isis
!!
interface
interface serial
serial 00
ip address 10.1.2.1 255.255.255.0
ip router isis
Insert Slide here.

685 This is an example of the simple Integrated IS-IS configuration, specifying only the IS-IS
686 process and the NET, and enabling IS-IS on the interfaces. This router will act as a level-1-2
687 router.

Example #1: Sample Two-Area
Configuration
Configure routers for routing IP within

two-level area structure
L1L2 routers
E0 E0
R2 R3
S0 S0
Area 49.0001 Area 49.0002

S0 S0
R1 R4
L1 routers
Insert Slide here.

688 This example shows how to configure a simple two-area IS-IS network, optimizing the level-1
689 and level-2 operations of the links and routers.
Configuration (L1 routers)
R1 has to be L1-only router

hostname
hostname R1
R1
!!
interface
interface Serial0
Serial0
ip address 192.168.120.1
192.168.120.1 255.255.255.0
ip router isis
!!
router
router isis
isis
is-type level-1
net 49.0001.1921.6800.1005.00
49.0001.1921.6800.1005.00
Insert Slide here.

690 Router R1 is in area 49.0001 with no links outside that area and, therefore, needs to operate
691 only as a level-1 router.
692 The is-type level-1 command under router isis ensures that the router creates only a level-1
693 database and takes part only in level-1 adjacencies over its interfaces - it is not necessary to
694 also specify the circuit-type on the interfaces in this case. Level 1 on the interfaces is implied
695 by setting the IS-IS process as level-1-only.
696 The serial interface has an isis metric set to better reflect the throughput of the line (compared
697 with, say, an Ethernet).

Configuration (L1/L2 routers)
R2 has to be L1/L2-router (optimized)
hostname
hostname R2
!!
interface
interface Ethernet0
Ethernet0
ip
ip address
address 192.168.220.2
192.168.220.2 255.255.255.0
ip
ip router
router isis
isis
isis circuit-type
circuit-type level-2
level-2
!!
interface
interface Serial0
Serial0
ip
ip address
address 192.168.120.2
192.168.120.2 255.255.255.0
ip
ip router
router isis
isis
isis circuit-type
circuit-type level-1
level-1
!!
router
router isis
isis
net
net 49.0001.1921.6800.1006.00
49.0001.1921.6800.1006.00
Insert Slide here.

698 Router R2 is a member of area 49.0001 but also links that area with the neighboring area
699 49.0002. Thus, it is required to act as both a level-1 and a level-2 router. This is the default
700 operation of router isis, so no specific configuration is required in the router definition.
701 However, to optimize the operation of the neighbor links, the interfaces to its two neighbors
702 specify the type of adjacency to be established. The interface toward Router R1 (in the same
703 area) specifies isis circuit-type level-1, while the interface toward Router R3 (different area,
704 hence level-2) has isis circuit-type level-2 specified.
705 Both interfaces have isis metrics defined as an example of this command.
Troubleshooting Commands—CLNS
router#
show clns
• Display information about the CLNS network

router#
show clns protocol [tag]
• List the protocol-specific information

router#
show clns interface [type number]
• List the CLNS-specific information about each interface

router#
show clns neighbors [type number] [detail]
• Display both ES and IS neighbors
Insert Slide here.

706 Some useful commands to troubleshoot the Integrated IS-IS network are:
707 n show clns displays general information about the CLNS network
708 n show clns protocol displays information for the specific IS-IS processes in the router
709 n show clns interface displays information about the interfaces running IS-IS.
710 n show clns neighbors is a very useful command, because it displays the neighbor ISs (and
711 ES neighbors, if there are any) - that is, the routers with which this router has IS-IS
712 adjacencies. The optional keyword detail displays comprehensive information about the
713 neighbors, rather than listing a summary of the neighbors, as is the case without that
714 keyword specified. The list can be reduced to those neighbors across a particular interface
715 by specifying the interface in the command.

Troubleshooting Commands—
CLNS and IS-IS
router#
show isis route
• Display IS-IS level-1 routing table

router#
show clns route
• Display CLNS routing table
router#
show isis database
• Display the IS-IS link-state database
Insert Slide here.

716 Further commands to troubleshoot the Integrated IS-IS network are:
717 n show isis route displays the IS-IS level-1 routing table (that is, all other System IDs in the
718 area)
719 n show clns route displays the IS-IS level-2 routing table
720 n show isis database displays the contents of the IS-IS link-state database
721 To force IS-IS to refresh its link-state database and recalculate all routes, issue the clear isis
722 command specifying the IS-IS process tag or * to clear all IS-IS
Troubleshooting Commands—IP
router#
show ip protocols
• Display the parameters and current state of the

active routing protocol process
router#
show ip route [address [mask]] | [protocol [process-id]]
• Display the current state of the routing table
© 2001, Cisco Systems, Inc. www.cisco.com Overview of IS -IS Technologies, Structures and Protocols 82
Insert Slide here.

723 To troubleshoot the IP functionality of the Integrated IS-IS network, you can use standard IP
724 display commands:
725 n show ip protocols displays the active routing protocols, what interfaces they are active on,
726 and what networks they are routing for.
727 n show ip route displays the routing table. The detail for a particular route or a list of all
728 routes in the routing table from a particular process can be specified.

Example #2: Simple Troubleshooting—
What About CLNS Protocol?
R2#show
R2#show clns
clns protocol
protocol
IS-IS
IS-IS Router:
Router: <Null
<Null Tag>
Tag>
System
System Id:
Id: 1921.6800.1006.00
1921.6800.1006.00 IS-Type:
IS-Type: level-1-2
level-1-2
Manual
Manual area
area address(es):
address(es):
49.0001
49.0001
Routing
Routing for
for area
area address(es):
address(es):
49.0001
49.0001
Interfaces
Interfaces supported
supported by
by IS-IS:
IS-IS:
Serial0
Serial0 - IP
Eethernet0
Eethernet0 - IP
IP
Redistribute:
Redistribute:
static (on by default)
Distance
Distance for
for L2
L2 CLNS
CLNS routes:
routes: 110
110
RRR
RRR level:
level: level-1
level-1
Generate
Generate narrow
narrow metrics:
metrics: level-1-2
Accept
Accept narrow
narrow metrics:
metrics: level-1-2
Generate
Generate wide
wide metrics:
metrics: none
none
Accept
Accept wide
wide metrics:
metrics: none
none
Insert Slide here.

729 This is an example output from the show clns protocols command showing:
730 n The Integrated IS-IS process, its tag (if present), and the level type(s) on the router
731 n The System ID and area-ID for this router
732 n The interfaces using Integrated IS-IS for routing (including whether that is for IP or CLNS
733 or both)
734 n Any redistribution of other route sources
735 n Information about the acceptance and generation of metrics, and distances for level-2
736 routing
Example #2: Are Adjacencies
Established?
R2#show
R2#show clns
clns neighbors
neighbors
System
System Id
Id Interface
Interface SNPA State
State Holdtime
Holdtime Type
Type Protocol
Protocol
R1
R1 Se0
Se0 *HDLC*
*HDLC* Up
Up 28
28 L1
L1 IS-IS
IS-IS
R3
R3 Et0
Et0 0000.0c92.de4c
0000.0c92.de4c Up
Up 20
20 L2
L2 IS-IS
IS-IS
R2#show
R2#show clns interface serial 00
Serial0
Serial0 is
is up,
up, line
line protocol
protocol is
is up
up
Checksums
Checksums enabled,
enabled, MTU
MTU 1500,
1500, Encapsulation
Encapsulation HDLC
HDLC
ERPDUs
ERPDUs enabled,
enabled, min.
min. interval
interval 1010 msec.
msec.
RDPDUs
RDPDUs enabled,
enabled, min.
min. interval
interval 100
100 msec.,
msec., Addr
Addr Mask
Mask enabled
enabled
Congestion
Congestion Experienced
Experienced bit
bit set
set at
at 44 packets
packets
CLNS
CLNS fast
fast switching disabled
CLNS
CLNS SSE
SSE switching
switching disabled
disabled
DEC
DEC compatibility
compatibility mode
mode OFF
OFF for this interface
Next
Next ESH/ISH
ESH/ISH in
in 12
12 seconds
seconds
Routing
Routing Protocol:
Protocol: IS-IS
IS-IS
Circuit
Circuit Type:
Type: level-1
level-1
Interface
Interface number
number 0x1,
0x1, local
local circuit
circuit ID
ID 0x101
0x101
Level-1
Level-1 Metric:
Metric: 10,
10, Priority:
Priority: 64,
64, Circuit
Circuit ID:
ID: R2.00
R2.00
Number
Number of
of active
active level-1
level-1 adjacencies:
adjacencies: 1
Next
Next IS-IS
IS-IS Hello
Hello in
in 55 seconds
seconds
Insert Slide here.

737 This is an example of output from the show clns neighbors command, showing:
738 n The IS-IS neighbors
739 n Their SNPAs and state
740 n The timeout (for receipt of no HELLOs) before the neighbor would be declared down
741 (holdtime)
742 n The neighbor’s level and type

743 The figure also provides an example of output from the show clns interfaces command,
744 showing:
745 n That the interface is running IS-IS and is attempting to establish both level-1 and level-2
746 adjacencies
747 n The interface numbers and circuit ID for IS-IS purposes
748 n The metric(s) for the interface and a priority for DIS negotiation (not relevant in this case
749 because it is a serial interface)
750 n Information about hello timers and the number of adjacencies that have been established

Example #2: Is Integrated
IS-IS Running?
R2#show
R2#show ip
ip protocols
protocols
Routing
Routing Protocol
Protocol is
is "isis"
"isis"
Sending
Sending updates
updates every
every 00 seconds
seconds
Invalid
Invalid after 0 seconds, hold
after 0 seconds, hold down
down 0,
0, flushed
flushed after
after 00
Outgoing
Outgoing update
update filter
filter list
list for
for all
all interfaces
interfaces is
is
Incoming
Incoming update
update filter
filter list
list for
for all
all interfaces
interfaces is
is
Redistributing:
Redistributing: isis
isis
Address
Address Summarization:
Summarization:
None
None
Routing
Routing for
for Networks:
Networks:
Serial0
Serial0
Ethernet0
Ethernet0
Routing
Routing Information
Information Sources:
Sources:
Gateway
Gateway Distance
Distance Last
Last Update
Update
11.0.0.1
11.0.0.1 115
115 00:11:44
00:11:44
13.0.0.1
13.0.0.1 115
115 00:11:44
00:11:44
14.0.0.1
14.0.0.1 115
115 00:11:44
00:11:44
Distance:
Distance: (default
(default is
is 115)
115)
Insert Slide here.

751 This is an example of output from the show ip protocols command, showing that Integrated
752 IS-IS is running. It also shows the interfaces taking part in Integrated IS-IS and the sources of
753 routing information (the neighbor routers).
Example #2: Do We See Any
IP Routes?
R2#show
R2#show ip
ip route
route isis
isis
i L1
L1 11.0.0.0/8
11.0.0.0/8 [115/10]
[115/10] via 192.168.20.1, Serial0
i L1
L1 13.0.0.0/8
13.0.0.0/8 [115/10]
[115/10] via 192.168.220.3, Ethernet0
Ethernet0
i L1
L1 14.0.0.0/8
14.0.0.0/8 [115/20] via 192.168.220.3, Ethernet0
Ethernet0
Insert Slide here.

754 This is an example of output from the show ip route command, showing only the IS-IS routes.
755 These routes are all from level 1 as indicated by the “i L1” tag.
756 Integrated IS-IS uses an administrative distance of 115 by default the metric shown for each
757 route [115/20] is taken from the IS-IS cost to the destination.

758 Modeling WAN Networks in Integrated IS-IS
Integrated IS-IS over WANs
Three categories:
• Point-to-Point leased circuits
–Few or no issues for IS-IS
• Dialup
–Avoid IS-IS over dialup except for backup
• Switched WAN
–Various design options exist for NBMA
networks
Insert Slide here.

759 WANs are typically implemented as either point-to-point or point-to-multipoint, and most support
760 multiple connections. These WANs typically do not support broadcasting and are thus classified
761 as NBMA.
762 Point-to-point WANs are typically leased circuits between two routers. A point-to-point WAN
763 has two devices attached - one at each end of the circuit. Usually such links will run Cisco
764 HDLC or Point-to-Point Protocol (PPP). These correspond exactly to the Integrated IS-IS
765 classification of a point-to-point network.
766 Note A point-to-point circuit is still regarded as an NBMA network, just as a back-to-back
767 Ethernet connection is still a LAN. Both are examples of multiple-access networks that
768 have only two devices attached.
769 Dialup networks using dial-on-demand routing (DDR) can be configured as either point-to-point
770 or point-to-multipoint WAN implementations:
771 n Legacy DDR dialup connections (that is, “dialer map” statements) are NBMA (even
772 though they may use PPP as their line protocol), because a single interface can support
773 multiple destinations.
774 n Dialer profiles and dia ler virtual profiles are point-to-point connections (one Dialer Profile
775 equals one remote profile), but these can suffer from the same loss-of-neighbor delays as
776 NBMA networks.
777 n Dialer virtual profiles are point-to-point connections where the interface drops immediately
778 if the remote end disconnects, leading to faster neighbor-loss detection and faster
779 convergence.
780 Dial interfaces are not dealt with in this lesson. As a general rule, you should avoid IS-IS over
781 dialup, except to provide dial-backup functionality.

Configuring IS-IS in
Switched WANs
Don’t use the broadcast model on

NBMA clouds
• Supported and works nicely as long as all
VCs of a fully meshed topology are up
(p2mp interfaces!)
Use p2p subinterfaces
• Unnumbered (to loopback), or
• Each subinterface in its own subnet
Insert Slide here.

782 IS-IS can work only over NBMA clouds configured with a full mesh. Anything less than a full
783 mesh could cause serious connectivity and routing issues. However, even if a full mesh is
784 configured, this is no guarantee that a full mesh will exist at all times. A failure in the underlying
785 switched WAN network, or a misconfiguration on one or more routers, could break the full
786 mesh either temporarily or permanently. Therefore, you should avoid NBMA multipoint
787 configurations for IS-IS networks. Use point-to-point subinterfaces instead.
788 Point-to-point interfaces should usually be configured with an IP subnet (that is, a 30-bit mask).
789 In modern IP networks using private addressing and/or variable -length subnetting, there are
790 usually plenty of spare IP addresses to apply to point-to-point interfaces.
791 Alternatively, as Integrated IS-IS uses CLNS packets for its route propagation, “ip
792 unnumbered” can be used on point-to-point interfaces. However, this works only on more
793 recent IOS releases (12.x) - earlier releases fail to establish an IS-IS adjacency because the IP
794 subnets do not match at either end of the link. Although “IP unnumbered” can be used by IS-IS,
795 it cannot be used in other routing protocols, such as OSPF.
Configuring
Configuring IS-IS—NBMA
Configuration Steps
Start IS-IS routing process on a router
and define NET(s)
For each NBMA interface:
• Configure the point-to-point subinterface
• Assign appropriate virtual circuit and
address (CLNS, IP) to it
• Define mapping
• Start IS-IS on a subinterface
Optional: adjust timers and LSP flooding
Insert Slide here.

796 To enable IS-IS over switched WAN media:
797 n Start the IS-IS process and assign NETs as usual
798 n On each NBMA interface:

799 — Design a mesh between the NBMA peers (full or partial).
800 — Configure point-to-point subinterfaces for each NBMA VC and assign IP addresses.
801 — Define the mapping of level-3 protocols/addresses to the VC. If manual mappings are
802 used (for example, x25 map, frame-relay map), then the CLNS mapping must specify
803 “broadcast” (to support routing packets), but the IP mapping does not require this (it is
804 used only for next-hop resolution).
805 — Start IS-IS processing on the subinterface (ip router isis). This command must not be
806 used on the “main” interface or that (multipoint) interface will generate a pseudonode
807 LSP for itself.
808 n You can use further tuning commands to control the flooding of link-state information with
809 timer and blocking commands (discussed later in this lesson).

Configuring IS-IS (cont.)
On a p2p link, only one type of IS-IS Hello

(IIH) regardless of level type
When adjacency on p2p link is
established, LSPs get exchanged through
CSNP (once only)
• Missing LSPs not present in the received
CSNP are sent to neighbors
• Missing pieces from CSNP not present in link-
state database requested by PSNP
• Received LSPs acknowledged by PSNP
Insert Slide here.

810 On a point-to-point link a single IIH PDU is sent. This can specify whether the adjacency is at
811 level-1, level-2 or both.
812 When the adjacency is established, each neighbor sends a CSNP describing the contents of its
813 link-state database. Each router then requests any missing LSPs from the neighbor using
814 PSNPs and acknowledges the receipt of the LSPs with PSNPs.
815 This activity reduces the amount of routing traffic across the point-to-point link - each router
816 exchanges only the information missing from its link-state database rather than the entire link-
817 state database of its neighbor router.
Example #1: Running
IS-IS on P2P Links
interface
interface s0/0.1
s0/0.1 point-to-point
point-to-point
ip
ip address
address 10.1.1.1
10.1.1.1 255.255.255.252
255.255.255.252
interface
interface s0/0.2
point-to-point
ip
ip address
address 10.1.1.5
10.1.1.5 255.255.255.252
255.255.255.252
interface
interface s0/0.3
point-to-point 10.1.1.2 R1
ip
ip address
address 10.1.1.9
10.1.1.9 255.255.255.252
255.255.255.252 DLCI 400 p2p
Frame Relay
DLCI 100
p2p
R4 DLCI 200 R2
DLCI 300 10.1.1.6
DLCI 400
Point-to-point p2p
sub-interfaces
sub-interfaces
10.1.1.10 R3
Frame
Frame relay
relay modelled
modelled as aa collection
collection of
of DLCI 400
subnets
subnets (each sub-interface
sub-interface in
in its
its own subnet)
Insert Slide here.

818 This is an example of a router network connected over Frame Relay and using point-to-point
819 subinterfaces. Each Frame Relay permanent virtual circuit (PVC) is treated as its own point-to-
820 point network, with its own IP addresses.
821 The example is of a star network topology. It is important to note that the routers at the “points”
822 of the star are also configured with point-to-point subinterfaces even though (unlike the central
823 router) they connect to only one VC. This is the best practice for all routing protocols (it allows
824 further VCs to be added without affecting the existing VC, but it is imperative to IS-IS. A
825 “main” interface is a multipoint interface, even if it happens to have only one VC configured. If
826 the single VC were configured under a main interface, IS-IS would treat this as a broadcast
827 network and attempt to elect a DIS. Also, the adjacency would not establish because the
828 multipoint end would send broadcast, network-style HELLOs, but the central router would send
829 point-to-point hello PDUs.

Example #1: Frame Relay
Subinterface Configuration
One router (R4) p2p FR subinterface (no maps)

interface
interface Serial0/0
Serial0/0
encapsulation frame-relay
frame-relay
!!
interface
interface Serial0/0.1
Serial0/0.1 point-to-point
point-to-point
ip address 10.1.1.1 255.255.255.252
ip router
router isis
frame-relay
frame-relay interface-dlci 100
!!
interface
point-to-point
ip address 10.1.1.5
10.1.1.5 255.255.255.252
ip router
router isis
frame-relay
!!
interface
point-to-point
ip address 10.1.1.9
10.1.1.9 255.255.255.252
ip router
router isis
frame-relay
Insert Slide here.

830 Here is the configuration of the central router from the previous example. It shows the
831 following:
832 n The encapsulation type (frame-relay) is set under the main interface (Serial0/0). No IP or
833 IS-IS configuration is included under the main interface.
834 n Three subinterfaces are defined; one for each VC. Each subinterface specifies:
835 — The IP address and subinterface for that point-to-point link: a different subnet for each
836 subinterface.
837 — Integrated IS-IS as the routing protocol over that subinterface (ip router isis).
838 — The VC to use for that point-to-point subinterface, using the frame-relay interface-
839 dlci command. This is the only command needed to enable both IP and CLNS across
840 this VC. The router automatically enables, across this VC, all the protocols that are
841 enabled on the point-to-point subinterface, and “broadcast” for all those protocols.
Mapping and Neighbors
R4#show
R4#show frame-relay
frame-relay map
map
Serial0/0.1
Serial0/0.1 (up):
(up): point-to-point
point-to-point dlci,
dlci, dlci
dlci 100(0x64,0x1840),
100(0x64,0x1840), broadcast
broadcast
status
status defined,
defined, active
active
Serial0/0.2
Serial0/0.2 (up):
(up): point -to-point
dlci, dlci
dlci 200(0xC8,0x3080),
200(0xC8,0x3080), broadcast
broadcast
status
status defined,
defined, active
active
Serial0/0.3
Serial0/0.3 (up):
(up): point -to-point
dlci, dlci
dlci 300(0xA4,0x4580),
300(0xA4,0x4580), broadcast
broadcast
status
status defined,
defined, active
active
R4#debug
R4#debug isis
isis adj-packet
adj-packet
ISIS-Adj:
ISIS-Adj: Sending
Sending serial
serial IIH
IIH on Serial0/0.1,
Serial0/0.1 , length
length 1499
1499
ISIS-Adj:
ISIS-Adj: Rec
Rec serial
serial IIH
IIH from DLCI 100 (Serial0/0.1)
(Serial0/0.1),, cir
cir type
type L1L2,
L1L2, cir
cir id
id
00,
00, length
length 1499
1499
ISIS-Adj:
ISIS-Adj: rcvd
rcvd state
state UP,
UP, old
old state
state UP,
UP, new
new state
state UP
UP
ISIS-Adj:
ISIS-Adj: Action
Action == ACCEPT
ACCEPT
...
...
ISIS-Adj:
ISIS-Adj: Sending
Sending serial
serial IIH
IIH on
on Serial0/0.2,
Serial0/0.2, length
length 1499
1499
ISIS-Adj:
ISIS-Adj: Rec
Rec serial
serial IIH
IIH from
from DLCI
DLCI 200
200 (Serial0/0.2),
(Serial0/0.2), cir
cir type
type L1L2,
L1L2, cir
cir id
id
01,
01, length
length 1499
1499
ISIS-Adj:
ISIS-Adj: Sending
Sending serial
serial IIH
IIH on
on Serial0/0.3,
Serial0/0.3, length
length 1499
1499
ISIS-Adj:
ISIS-Adj: Rec
Rec serial
serial IIH
IIH from
from DLCI
DLCI 300 (Serial0/0.3),
(Serial0/0.3), cir
cir type
type L1L2,
L1L2, cir
cir id
02,
02, length
length 1499
Insert Slide here.

842 This figure shows some monitoring commands for the example network:
843 n show frame -relay map displays the status of each Frame Relay VC, giving:
844 — Its status - “defined” means it has been configured on the Frame-Relay switch, and
845 “active” indicates that this VC is operational
846 — Its type - point-to-point, meaning it has been assigned to a point-to-point subinterface
847 — Its assigned subinterface - for example, Serial0/0.1
848 — The VC identification - for example, dlci 100
849 — Whether it supports broadcast (for example, routing) packets
850 n debug isis adj-packet shows the neighborship establishment across one of the
851 subinterfaces (Serial0/0.1); sending and receiving serial (that is, point-to-point) IIH PDUs
852 and declaring the adjacency “up.” Ongoing hello conversations for the other subinterfaces
853 are also shown.

Example #2: Running
IS-IS on P2MP Links
Outgoing (locally
significant) DLCI
DLCI to
to
which
which remote
remote IP
IP address
(Inverse
(Inverse ARP)
ARP) and
and CLNS
CLNS R1
protocols are mapped 10.0.0.1
DLCI 400 p2mp
s0/0.2 Frame Relay

multipoint p2mp
DLCI 100
DLCI 200 R2
R4
10.0.0.4 DLCI 300 10.0.0.2
DLCI 400
p2mp
Frame Relay
Relay modeled as
as one
one IP
IP
subnet
subnet (full
(full mesh
mesh needed
needed although
although
10.0.0.3 R3
not shown in the picture) DLCI 400
Insert Slide here.

854 The alternative NBMA version of the example network is shown in this figure. In this case, all
855 the Frame Relay ports are configured as multipoint interfaces, either as a multipoint subinterface
856 (on the central router R4) or, possibly, the “main” interfaces on the other routers. All interfaces
857 share the same IP subnet.
858 The diagram shows the star topology from the previous example. In a multipoint environment it
859 is important that a full mesh be implemented; therefore, all other routers will also have VCs
860 interconnecting them, although these are not shown in the diagram.
861 If this were a true hub-and-spoke environment, and the spoke sites had no need to communicate
862 to each other, this topology could work with only the indicated DLCIs. In this case, the central
863 router (R4) must become the DIS for the NBMA network (as it is the only router visible to all
864 others), so a suitable IS-IS priority should be set on the Frame Relay interface. Routes would be
865 installed in each spoke router toward the other spoke routers via their local IP addresses.
866 However, packets to these destinations would be dropped, as there are no direct VCs between
867 the spokes.
Example #2: CLNS Mapping
• One router (R4) p2mp Frame Relay subinterface

(map CLNS to DLCI, IP mapped by inverse ARP)
interface
interface Serial0/0
Serial0/0
encapsulation frame-relay
frame-relay
!!
interface
Serial0/0.2 multipoint
multipoint
ip address
address 10.0.0.4
10.0.0.4 255.0.0.0
255.0.0.0
ip router
router isis
frame-relay
frame-relay map clns
clns 100
100 broadcast
broadcast
frame-relay
clns 200
200 broadcast
broadcast
frame-relay
clns 300
300 broadcast
broadcast
frame-relay
frame-relay
frame-relay
!!
router
router isis
isis
net 00.0001.0000.0000.0004.00
Insert Slide here.

868 This figure shows the configuration of the multipoint interface on the central router (R4). In a
869 multipoint environment, IP and CLNS maps must be configured separately:
870 n The frame-relay interface-dlci command is used to enable IP across the Frame Relay
871 PVCs. Inverse ARP will resolve the remote end IP addresses. On a point-to-point
872 subinterface, this command enables all traffic, but in a multipoint environment this enables
873 only IP.
874 n Alternatively, the IP maps could be entered explicitly using frame-relay map ip <ip
875 address> <dlci>. In this case, “broadcast” is not necessary (for IP) as only directed IP
876 packets will use this VC.
877 n To enable CLNS - which must be done separately from IP in a multipoint environment - the
878 frame-relay map clns command is used. CLNS is used for the IS-IS routing packets and
879 therefore “broadcast” must be specified.

Mapping and Neighbors
R4#show
R4#show frame-relay
frame-relay map
map
Serial0/0.4
Serial0/0.4 (up):
(up): CLNS dlci 400(0x190,0x6400),
400(0x190,0x6400), static,
static,
broadcast,
CISCO,
CISCO, status defined, active
Serial0/0.4
Serial0/0.4 (up):
(up): ip 10.1.4.3
10.1.4.3 dlci 400(0x190,0x6400),
400(0x190,0x6400), dynamic,
broadcast,, status defined, active
R4#debug
R4#debug isis adj-packet
ISIS-Adj:
ISIS-Adj: Sending
Sending L2
L2 LAN
LAN IIH
IIH on
on Serial0/0.2,
Serial0/0.2, length
length 1500
ISIS-Adj:
ISIS-Adj: Rec
Rec L2 IIH
IIH from
from DLCI
DLCI 400
400 (Serial0/0.2),
(Serial0/0.2), cir
cir type L1L2,
cir
cir id
id 0000.0000.0004.03,
0000.0000.0004.03, length
length 1500
1500
ISIS-Adj:
ISIS-Adj: Sending L1 LAN IIH on Serial0/0.2, length 1500
ISIS-Adj:
ISIS-Adj: Rec
Rec L1 IIH from DLCI 400 (Serial0/0.2), cir type L1L2,
cir
cir id
id 0000.0000.0004.03,
0000.0000.0004.03, length
length 1500
1500
Insert Slide here.

880 This figure shows how the same monitoring commands, as used previously, produce a slightly
881 different output for the multipoint environment.
882 Some monitoring commands are shown for the example network:
883 n show frame -relay map again displays the status of each Frame Relay VC. This time,
884 separate entries are created for the IP and CLNS mappings (even though they use the
885 same VC):
886 — The CLNS map shows that it is created as a “static” map and that “broadcast” was
887 specified
888 — The IP map is “dynamic” because the IP address was resolved by Inverse ARP
889 n debug isis adj-packet again shows the neighborship establishment. This time, the
890 adjacency uses LAN IIH PDUs because this is a multipoint environment.
Detecting Mismatched Interfaces
One router (R4) configured as p2mp (sending LAN IIHs),

the other (R2) as p2p (sending p2p IIHs)
Question: Why is the adjacency UP on p2p but
stays in INIT on the p2mp side?
R2#show
R2#show clns
clns neighbors
neighbors
System
System Id
Id Interface
Interface SNPA
SNPA State
State Holdtime
Holdtime Type
Type Protocol
0000.0000.0004
0000.0000.0004 Se0/0.2
Se0/0.2 DLCI
DLCI 300
300 Up
Up 88 L1
L1 IS-IS
IS-IS
R5
R5 Et0/0
Et0/0 0050.3ef1.5960
0050.3ef1.5960 Up
Up 88 L2
L2 IS-IS
IS-IS
R1
R1 Se0/0.1
Se0/0.1 DLCI
DLCI 100
100 Up
Up 23
23 L1
L1 IS-IS
IS-IS
R4#show
R4#show clns
clns neighbors
neighbors
System
System Id
Id Interface
Interface SNPA
SNPA State
State Holdtime
Holdtime Type
Type Protocol
R6
R6 Et0/0
Et0/0 0010.117e.74a8
0010.117e.74a8 Up
Up 26
26 L2
L2 IS-IS
IS-IS
R3
R3 Se0/0.3
Se0/0.3 DLCI
DLCI 400
400 Up
Up 28
28 L2
L2 IS-IS
IS-IS
0000.0000.0002
0000.0000.0002 Se0/0.2
Se0/0.2 DLCI
DLCI 300
300 Init
Init 29
29 L1
L1 IS-IS
IS-IS
0000.0000.0001
0000.0000.0001 Se0/0.1
Se0/0.1 DLCI
DLCI 200
200 Up
Up 290
290 IS
IS ES-IS
ES-IS
Insert Slide here.

891 An example of a misconfiguration is shown. One end of a link (R2) is specified as a point-to-
892 point subinterface, but the other (R4) is using a point-to-multipoint interface.
893 Issuing the show clns neighbors on each router shows the mismatch:
894 n R2 (the point-to-point end) shows the adjacency as “up”
895 n R4 (the multipoint end), the adjacency is stuck in the init state
896 The misconfiguration results from the fact that the two ends of the VC are set to different
897 types. The point-to-point end sends Serial IIH PDUs. The multipoint end sends LAN IIH
898 PDUs.

Detecting Mismatched
Interfaces (cont.)
Answer: This type of configuration is illegal

• LAN adjacencies have a type of “three-way-hand
shake" (Down-Init-Up)
• For such a handshake on p2p links, Cisco
introduced TLV 240
– In ISO 10589 bidirectionality is only checked
during the SPF computation
• An adjacency is Up if the other side puts your
identity in the hello packet
– Is valid if a previous match is found (Area
Address, Protocol Supported, IP Interface
Address) for a certain level
Insert Slide here.

899 The ISO standard defines a three-way handshake for initiating LAN adjacencies:
900 n The adjacency starts in the “down” state. The IS sends out LAN IIH PDUs (identifying
901 itself).
902 n If a LAN IIH PDU is received, the adjacency is installed in the init state. This router then
903 sends out an IIH PDU to the neighbor, including the neighbor's SNPA in the hello packet.
904 The neighbor does the same thing with this router’s SNPA.
905 n The IS receives a second IIH from the neighbor router with its own SNPA identified in the
906 packet. On receipt of this, the IS understands that the new neighbor knows of its presence
907 and therefore declares the adjacency “up.”
908 According to the ISO standard (ISO 10589), this process is omitted for a point-to-point
909 adjacency. However, Cisco IOS implements the same three-way handshake by adding a Point-
910 to-Point Adjacency State TLV (TLV 240) in the serial hello PDUs. In a similar manner to the
911 LAN adjacency, the router checks for its own SNPA in the neighbor's hello PDU before
912 declaring the adjacency “up.”
Detecting Mismatched
Interfaces (cont.)
R4 (p2mp) receives a p2p IIH, and doesn't realize
it is a p2p IIH
• Creates a (LAN) adjacency
• Looks for a TLV 6, doesn't find it, so it puts the
adjacency in INIT
R2 (p2p) receives a LAN IIH, and doesn't realize
it is a LAN IIH
• Creates a (p2p) adjacency
• There is no TLV 240 in the packet, so the router omits
the three-way handshake for backwards compatibility,
and puts the adjacency in the Up state
– Fixed since IOS 12.1(1)T
Insert Slide here.

913 The result of the example mismatch depends on the IOS release level. Prior to Release
914 12.1(1)T:
915 n R4 (multipoint) receives the point-to-point HELLO from R2 but treats it as a LAN HELLO
916 and puts the adjacency in the init state. It looks for its own SNPA in the received hello
917 PDUs (in a LAN hello PDU this would be identifie d in TLV 6 - IS Neighbors - but this
918 TLV is not present in a serial HELLO) but never finds them; therefore, the adjacency
919 remains in the init state.
920 n R2 (point-to-point) receives a LAN hello PDU and treats it as a point-to-point HELLO. It
921 checks the HELLO for a TLV 240 (point-to-point adjacency state) and fails to find one. For
922 backward compatibility, or perhaps to allow the link to be made to a non-Cisco IS-IS device,
923 the router assumes this is an ISO-specified point-to-point link, ignores the Cisco three-way
924 handshake, and allows the adjacency to establish, setting it to “up.”
925 Since Release 12.1(1)T:
926 n R4 (multipoint) receives the point-to-point HELLO, realizes it is the wrong hello type, and
927 installs the neighbor as an ES. R4 would show R2 in the show clns neighbors with
928 protocol “ES-IS.”
929 R2 (point-to-point) receives the LAN HELLO, recognizes the mismatch, and ignores the
930 neighbor. R4 would not appear at all in R2's show clns neighbors output. A debug isis adj-
931 packets output shows the incoming LAN IIH PDU and R2 declaring the mismatch.

932 Summ ary
Summary
After completing this lesson, you should be

able to:
• Explain basic OSI terminology and network layer
protocols used in OSI
• Identify similarities and differences between
Integrated IS -IS and OSPF
• Identify characteristics of an effective addressing
plan for IS-IS deployment
• Explain how networks and interfaces are
represented in IS-IS
• List the types of IS -IS routers and their role in IS-IS
area design
• Describe the hierarchical structure of IS-IS areas
933 MISSING SLIDE
Summary (cont.)
• Describe the concept of establishing adjacencies

• Describe the concepts of routing traffic transport and
database synchronization
• Explain the basic principles of area routing
• Explain IS-IS NBMA (non-broadcast multi-access
network) modeling solutions in switched WAN networks
• Given an addressing scheme and other laboratory
parameters, identify the steps to configure Cisco routers
for proper Integrated IS-IS operation
• Identify verification methods which ensure proper
operation of Integrated IS-IS on Cisco routers
934 Insert Slide here.

935
936
937 Review Questions
938 Answer the following questions. Appendix C contains answers to written exercises, review questions, and
939 laboratory exercises.
940
941
Review Questions 942
943
944
945
1. What is common to OSPF and Integrated IS-IS?
946
2. How is the router identified in an IS-IS environment? 947
3. What is the difference between NSAP and NET? 948
949
4. What does a unique System ID define? 950
5. Which network representations are supported 951
by IS-IS? 952
953
6. What is a pseudonode? 954
7. How do two level-1 areas communicate? 955
956
8. How do systems find each other in IS-IS? 957
9. List the types of adjacencies between IS-IS systems.958
959
10. How is IS-IS routing enabled on Cisco routers?
960
961
962
MISSING SLIDE

962
963
964
965

BSCIv ISIS

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSCIv ISIS

Hochgeladen von

Copyright:

Verfügbare Formate

BSCI

Click Here to Post Review Comments

Building Scalable Cisco

Building Scalable Cisco Internetworks, Revision 1.2: Student Guide

ROUTING PRINCIPLES 2-1

EXTENDING IP ADDRESSES 3-1

Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking v

CONFIGURING EIGRP 4-1

CONFIGURING OSPF IN A SINGLE AREA 5-1

INTERCONNECTING MULTIPLE OSPF AREAS 6-1

vi Building Scalable Cisco Internetworking Copyright  2001, Cisco Systems, Inc.

CONFIGURING IS-IS PROTOCOL 7-1

OPTIMIZING ROUTING UPDATE OPERATION 8-1

CONFIGURING BASIC BGP 9-1

IMPLEMENTING BGP IN SCALABLE NETWORKS 10-1

JOB AIDS AND SUPPLEMENTS A-1

ROUTER PASSWORD RECOVERY B-1

LABORATORY EXERCISES D-1

Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking ix

x Building Scalable Cisco Internetworking Copyright  2001, Cisco Systems, Inc.

Student Notes D-49

Copyright  2001, Cisco Systems, Inc. Building Scalable Cisco Internetworking xi

2 Configuring IS-IS Protocol

14 n Introduction to OSI Protocols and IS-IS Routing

16 n IP and OSI Routing with Integrated IS-IS

17 n Basic Integrated IS-IS Router Configuration

18 n Modeling WAN Networks in Integrated IS-IS

Upon completing this lesson, you will be able to:

Insert Slide here.

24 n Identify similarities and differences between Integrated IS-IS and OSPF

25 n Identify characteristics of an effective addressing plan for IS-IS deployment

26 n Explain how networks and interfaces are represented in IS-IS

28 n Describe the hierarchical structure of IS-IS areas

• Describe the concept of establishing adjacencies

© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-3

Insert Slide here.

31 n Describe the concepts of routing traffic transport and database synchronization

32 n Explain the basic principles of area routing

33 n Explain IS-IS nonbroadcast multiaccess (NBMA) network modeling solutions in switched

Copyright  2001, Cisco Systems, Inc. Configuring IS-IS Protocol 7-3

ISO and OSI?

© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-5

Insert Slide here.

50 n Independence of underlying communications infrastructure

53 n Quality of service (QoS) selection

The OSI protocol suite supports:

© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-6

Insert Slide here.

Copyright  2001, Cisco Systems, Inc. Configuring IS-IS Protocol 7-5

Terminology used in OSI

© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-7

Insert Slide here.

© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-8

Insert Slide here.

Copyright  2001, Cisco Systems, Inc. Configuring IS-IS Protocol 7-7

Two types of OSI network-layer services

© 2001, Cisco Systems, Inc. BSCI v1.2 — 7-9

Insert Slide here.

© 2001, Cisco Systems, Inc. BSCI v1.2— 7-10

Insert Slide here.

Copyright  2001, Cisco Systems, Inc. Configuring IS-IS Protocol 7-9

© 2001, Cisco Systems, Inc. BSCI v1.2— 7-11