Home > Articles > Cisco Network Technology > General Networking > Configuring IS-IS Protocol

Configuring IS-IS Protocol

  • Sample Chapter is provided courtesy of Cisco Press.
  • Date: Mar 21, 2003.

Contents

  1. Overview of OSI Protocols and IS-IS Routing
  2. Operation of IS-IS for CLNS/CLNP
  3. IP and OSI Routing with Integrated IS-IS
  4. Basic Integrated IS-IS Router Configuration
  5. Modeling WAN Networks in Integrated IS-IS
  6. Summary
  7. Configuration Exercise: Configuring a Multiarea IS-IS Network
  8. Answers to Configuration Exercise: Configuring a Multiarea IS-IS Network

Chapter Description

This supplemental material provides an overview of Intermediate System-to-Intermediate System (IS-IS) technology and its structures and protocols, along with basic configuration examples.

From the Book

Building Scalable Cisco Networks

Building Scalable Cisco Networks

$60.00

Configuration Exercise: Configuring a Multiarea IS-IS Network

Configuration Exercises

In this book, configuration exercises are used to provide practice in configuring routers with the commands presented. If you have access to real hardware, you can try these exercises on your routers. Refer to Appendix H in the Cisco Press book Building Scalable Cisco Networks (and the online addendum to Appendix H) for a list of recommended equipment and configuration commands for the backbone routers. However, even if you don't have access to any routers, you can go through the exercises and keep a log of your own running configurations on separate sheets of paper.

Commands used and answers to the configuration exercises are provided at the end of the exercise.

In these exercises, you are in control of a pod of 3 routers; there are assumed to be 12 pods in the network. The pods are interconnected to a backbone. In most of the exercises, there is only one router in the backbone; in some cases, another router is added to the backbone. Each of the configuration exercises in this book assumes that you have completed the previous exercises on your pod.

NOTE

This configuration exercise assumes that you have completed the OSPF exercises in Chapter 4 of the Cisco Press book Building Scalable Cisco Networks. The configuration for the backbone_r1 router for this exercise is provided on the Cisco Press website in the addendum to Appendix H.

In this exercise, you will configure IS-IS within your pod to the backbone_r1 router.

Objectives

In the following configuration exercise, you will do the following:

  • Configure the pxr1, pxr2, and pxr3 routers in your pod to be in a specific IS-IS area.

  • Enable IS-IS on the proper interfaces on the pxr1, pxr2, and pxr3 routers.

  • Configure the pxr2 and pxr3 routers to be Level 1 routers.

  • Configure the pxr1 router to perform route summarization.

  • Verify proper Level 1 adjacencies among the pxr1, pxr2, and pxr3 routers within your pod.

  • Verify proper Level 2 adjacencies between your pxr1 router and the backbone_r1 router.

  • Verify that the pxr1 router is advertising a default route to the pxr2 and pxr3 routers.

  • Verify which router is the designated IS router on the Ethernet link between pxr2 and pxr3.

  • Verify and change the Ethernet interface IS-IS router priority.

  • Verify proper network connectivity.

  • Use show and debug commands to verify IS-IS operations.

Visual Objective

Figure S-24 illustrates the topology used in the network.

Figure S-24Figure S-24 Configuration Exercise Topology

Command List

In this exercise, you will use commands in Table S-15. Refer to this list if you need configuration command assistance during the exercise.

Table S-15 Configuration Exercise Command List

Command

Description

router isis

Enables IS-IS

net 00.000x.xyxy.xyxy.xyxy.00

Configures the NET

ip router isis

Enables IS-IS on the interface

is-type level-1

Configures the router as a Level 1 IS-IS router

summary-address 192.168.x.0 255.255.255.0

Configures route summarization

isis priority 63

Changes the IS-IS router priority on the Ethernet interface to influence the DR election

show clns interface s0

Displays CLNS interface status and configuration

show clns is-neighbors

Displays the IS-IS neighbor table

show isis database

Displays the IS-IS link-state database

show isis spf-log

Displays how often and why the router has run a full SPF calculation

debug isis adj-packets

Displays IS-IS adjacency-related packets

debug isis update-packets

Displays IS-IS update-related packets


Setup

To set up, do the following:

Step 1

Disable OSPF on all the routers within your pod.

Step 2

Shut the pxr1 S3 interface.

Task 1: Enabling IS-IS Within Your Pod

Complete the following steps:

Step 1

Enable IS-IS on the pxr1, pxr2, and pxr3 routers within your pod.

Step 2

Configure the pxr1, pxr2, and pxr3 routers within your pod with the IS-IS NETs shown in the following table.

Pod

pxr1 NET

pxr2 NET

pxr3 NET

1

00.0001.1111.1111.1111.00

00.0001.1212.1212.1212.00

00.0001.1313.1313.1313.00

2

00.0002.2121.2121.2121.00

00.0002.2222.2222.2222.00

00.0002.2323.2323.2323.00

3

00.0003.3131.3131.3131.00

00.0003.3232.3232.3232.00

00.0003.3333.3333.3333.00

4

00.0004.4141.4141.4141.00

00.0004.4242.4242.4242.00

00.0004.4343.4343.4343.00

5

00.0005.5151.5151.5151.00

00.0005.5252.5252.5252.00

00.0005.5353.5353.5353.00

6

00.0006.6161.6161.6161.00

00.0006.6262.6262.6262.00

00.0006.6363.6363.6363.00

7

00.0007.7171.7171.7171.00

00.0007.7272.7272.7272.00

00.0007.7373.7373.7373.00

8

00.0008.8181.8181.8181.00

00.0008.8282.8282.8282.00

00.0008.8383.8383.8383.00

9

00.0009.9191.9191.9191.00

00.0009.9292.9292.9292.00

00.0009.9393.9393.9393.00

10

00.0010.A1A1.A1A1.A1A1.00

00.0010.A2A2.A2A2.A2A2.00

00.0010.A3A3.A3A3.A3A3.00

11

00.0011.B1B1.B1B1.B1B1.00

00.0011.B2B2.B2B2.B2B2.00

00.0011.B3B3.B3B3.B3B3.00

12

00.0012.C1C1.C1C1.C1C1.00

00.0012.C2C2.C2C2.C2C2.00

00.0012.C3C3.C3C3.C3C3.00

NOTE

The backbone_r1 router is configured with a NET of 00.0013.1111.2222.3333.00.

Step 3

Enable IS-IS on the interfaces specified in the following table on the pxr1, pxr2, and pxr3 routers within your pod.

Router

Interfaces on Which to Enable IS-IS

Router

Interfaces on Which to Enable IS-IS

Router

Interfaces on Which to Enable IS-IS

pxr1

S0

S1

S2

pxr2

S0

S1

E0

Loopback10

pxr3

S0

E0

Loopback11

Loopback12

Loopback13

NOTE

For this task, the pxr1 S3 interface is shut down.

Step 4

Display the routing table of the pxr1, pxr2, and pxr3 routers within your pod, and verify that you have full connectivity within your pod.

Step 5

Examine the pxr1 routing table and answer the following questions:

Does IS-IS load-balance by default?

What is the IS-IS routing metric based on by default?

Use the show clns int s0 command to determine the Level 1 and Level 2 default metric.

What is the default administrative distance of IS-IS routes?

Step 6

Save the current configurations of all the routers within your pod to NVRAM.

Task 2: Enabling Connectivity to the backbone_r1 Router

Complete the following steps:

Step 1

No shut the S3 interface on the pxr1 router.

Step 2

Enable IS-IS on the S3 interface on the pxr1.

Step 3

Display the routing table of the pxr1, pxr2, and pxr3 routers within your pod, and verify that you have full connectivity to the backbone_r1 router.

Do you see the backbone_r1 router's loopback interfaces in your routing table? (Note that you also might see routes to the other pods.)

Does IS-IS perform autosummarization across the network boundary by default?

Does IS-IS use the same default administrative distance for Level 1 and Level 2 routes?

Make sure that you can ping the loopback interfaces on the backbone_r1 router from the pxr1, pxr2, and pxr3 routers within your pod.

Step 4

Save the current configurations of all the routers within your pod to NVRAM.

Task 3: Changing the IS-IS Router Type

Complete the following steps:

Step 1

By default, the pxr1, pxr2, and pxr3 routers within your pod are what type of IS-IS router (Level 1, Level 2, or Level 1–2)?

What command can be used to determine the IS-IS router type?

Step 2

Examine the IS-IS link state database of the pxr1, pxr2, and pxr3 routers within your pod. Do you see both the Level 1 and Level 2 link-state database on all the routers?

In the link-state database, which link-state packet (LSP) is identified with an asterisk?

Examine the routing table of the pxr2 and pxr3 routers within your pod. Do you see both the Level 1 and Level 2 routes?

Step 3

Configure the pxr2 and pxr3 routers within your pod to be Level 1 IS-IS routers.

Step 4

What are the advantages of configuring the pxr2 and pxr3 routers within your pod to be Level 1 IS-IS routers?

Step 5

Re-examine the link-state database of the pxr2 and pxr3 routers within your pod. Do the pxr2 and pxr3 routers contain only the Level 1 link-state database now?

Step 6

Re-examine the routing table of the pxr2 and pxr3 routers now. What are the differences after they became Level 1–only IS-IS routers?

Step 7

In the pxr2 and pxr3 routing tables, do you see a default route through the pxr1 router?

Step 8

From the pxr2 or pxr3 routers, can you still ping the backbone_r1 router's loopback interfaces?

Step 9

Save the current configurations of all the routers within your pod to NVRAM.

Task 4: Configure Route Summarization

Complete the following steps:

Step 1

From pxr3, telnet to the backbone_r2 router using the password cisco.

Step 2

Display the routing table of the backbone_r1 router. Do you see your 192.168.x.y/28 and 172.26.x.y/28 subnets?

Step 3

Exit the telnet to the backbone_r1 router.

Step 4

Configure the Level 1–2 router within your pod to perform route summarization. Summarize the 192.168.x.y/28 and 172.26.x.y/28 subnets within your pod to 192.168.x.0/24 and 172.26.x.0/24 (where x is your pod number).

Step 5

Telnet to the backbone_r1 router.

Step 6

Re-examine the routing table of the backbone_r1 router. Do you see your summarized routes?

Step 7

From the backbone_r1 router, can you ping all the interfaces within your pod?

Step 8

Exit the telnet to the backbone_r1 router.

Step 9

Save the current configurations of all the routers within your pod to NVRAM.

Task 5: Using IS-IS show and debug Commands

Complete the following steps:

Step 1

At the pxr2 router, enable the debug isis adj-packets command and observe the debug output.

What type of hello is pxr2 sending to pxr3 over the Ethernet interface?

Step 2

Shut the pxr2 E0 interface and observe the debug output.

Step 3

No shut the pxr2 E0 interface and observe the debug output. From the debug output, determine which router (pxr2 or pxr3) is elected as the DR.

In the debug output, you should see something similar to the output shown in Example S-29 if pxr3 is the DR.

Example S-29 debug isis adj-packets Command Output from Router pxr2 If Router pxr3 Is the DR

02:23:12: ISIS-Adj: Adjacency state goes to Up
02:23:12: ISIS-Adj: Run level 1 DR election for Ethernet0
02:23:12: ISIS-Adj: New level 1 DR 3333.3333.3333 on Ethernet0
 pxr2#

Or, in the debug output, you should see something similar to the output shown in Example S-30 if pxr2 is the DR.

Example S-30 debug isis adj-packets Command Output from Router pxr2 If Router pxr2 Is the DR

05:19:43: ISIS-Adj: Run level 1 DR election for Ethernet0
05:19:43: ISIS-Adj: No change (it's us)
 pxr2#

What determines who will be elected as the DR on the Ethernet?

Step 4

Disable debug isis adj-packets at the pxr2 router.

Step 5

At the DR (as determined from Step 3), enter the show clns int e0 command. What is the default IS-IS router priority set to?

Step 6

At the DR (as determined from Step 3), change the E0 interface IS-IS router priority to 63.

Step 7

At the DR (as determined from Step 3), enter the show clns int e0 command again and verify that the DR is now changed to the other router.

The Circuit ID field in the show clns int e0 output identifies which router is the DR. Example S-31 shows the output of this command on the pxr3 router. In this example, the DR is the pxr2 router and the pxr3 router has an IS-IS priority of 63.

Example S-31 show clns Command Output from Router pxr3 If Router pxr2 Is the DR 

	pxr3#show clns int e0
Ethernet0 is up, line protocol is up
 Checksums enabled, MTU 1497, Encapsulation SAP
 ERPDUs enabled, min. interval 10 msec.
 RDPDUs enabled, min. interval 100 msec., Addr Mask enabled
 Congestion Experienced bit set at 4 packets
 CLNS fast switching enabled
 CLNS SSE switching disabled
 DEC compatibility mode OFF for this interface
 Next ESH/ISH in 21 seconds
 Routing Protocol: IS-IS
  Circuit Type: level-1-2
  Interface number 0x1, local circuit ID 0x1
  Level-1 Metric: 10, Priority: 63, Circuit ID: 2222.2222.2222.01
  Number of active level-1 adjacencies: 1
 Next IS-IS LAN Level-1 HELLO in 8 seconds

Step 8

At the pxr2 router, enable the debug isis update-packets command. Shut and no shut the E0 interface on the pxr2 router and observe the debug output.

Step 9

Disable debug isis update-packets at the pxr2 router.

Step 10

At the pxr2 router, use the proper show command to verify how often and why the router has run a full SPF calculation.

Step 11

At the pxr2 router, use the proper show command to examine the IS-IS neighbor table. How many entries do you see? Are they all Level 1 adjacency?

Step 12

At the pxr1 router, use the proper show command to examine the IS-IS neighbor table. How many entries do you see? Do you see both Level 2 and Level 1 adjacencies?

Step 13

Display the running configuration of the pxr1 router. Is clns routing enabled by default?

Step 14

Save the current configurations of all the routers within your pod to NVRAM.

Completion Criteria

You have successfully completed this configuration exercise if you correctly supplied the commands required to configure IS-IS within your pod and to the backbone_r1 router, and if you were able to correctly answer the questions in the exercise. At the end of this exercise, all the routers should have full connectivity to each other. All routers will be running the IS-IS routing protocol.

8. Answers to Configuration Exercise: Configuring a Multiarea IS-IS Network | Next Section Previous Section

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020