Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Enabling Wide IS-IS Metrics for Traffic Engineering


This example shows how to allow a wide range of metric values on IS-IS interfaces.


Before you begin, configure IS-IS on both routers. See Example: Configuring IS-IS for information about the sample IS-IS configuration.


Figure 1 shows the topology used in this example.

Figure 1: IS-IS Wide Metrics Topology
IS-IS Wide Metrics Topology

This example describes the steps on Device R1.


CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Device R1

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

To configure IS-IS checksums:

  1. Configure a metric of 100 on the interface at both IS-IS levels.
  2. Enable wide metrics.


From configuration mode, confirm your configuration by entering the show protocols command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

If you are done configuring the device, enter commit from configuration mode.


Confirm that the configuration is working properly.

Verifying That Wide Metrics Are Enabled


Make sure that the interface has the expected metric.


From operational mode, enter the show isis interface extensive command.

user@R1> show isis interface lt-1/2/0.1 extensive


The output shows that the metric is set to 100, as expected, at both Level 1 and Level 2.