Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring Link and Node Protection for IS-IS Routes

 

Understanding Loop-Free Alternate Routes for IS-IS

In Junos OS Release 9.5 and later, support for IS-IS loop-free alternate routes enables IP fast-reroute capability for IS-IS. Junos OS precomputes loop-free backup routes for all IS-IS routes. These backup routes are preinstalled in the Packet Forwarding Engine, which performs a local repair and implements the backup path when the link for a primary next hop for a particular route is no longer available. With local repair, the Packet Forwarding Engine can correct a path failure before it receives recomputed paths from the Routing Engine. Local repair reduces the amount of time needed to reroute traffic to less than 50 milliseconds. In contrast, global repair can take up to 800 milliseconds to compute a new route. Local repair and global repair are thus complementary. Local repair enables traffic to continue to be routed using a backup path until global repair is able to calculate a new route.

A loop-free path is one that does not forward traffic back through the routing device to reach a given destination. That is, a neighbor whose shortest path to the destination traverses the routing device is not used as a backup route to that destination. To determine loop-free alternate paths for IS-IS routes, Junos OS runs shortest-path-first (SPF) calculations on each one-hop neighbor. You can enable support for alternate loop-free routes on any IS-IS interface. Because it is common practice to enable LDP on an interface for which IS-IS is already enabled, this feature also provides support for LDP label-switched paths (LSPs).

Note

If you enable support for alternate loop-free routes on an interface configured for both LDP and IS-IS, you can use the traceroute command to trace the active path to the primary next hop.

The level of backup coverage available through IS-IS routes depends on the actual network topology and is typically less than 100 percent for all destinations on any given routing device. You can extend backup coverage to include RSVP LSPs.

Junos OS provides two mechanisms for route redundancy for IS-IS through alternate loop-free routes: link protection and node-link protection. When you enable link protection or node-link protection on an IS-IS interface, Junos OS creates a single alternate path to the primary next hop for all destination routes that traverse a protected interface. Link protection offers per-link traffic protection. Use link protection when you assume that only a single link might become unavailable but that the neighboring node on the primary path would still be available through another interface.

Node-link protection establishes an alternate path through a different routing device altogether. Use node-link protection when you assume that access to a node is lost when a link is no longer available. As a result, Junos OS calculates a backup path that avoids the primary next-hop routing device. In Junos OS Release 9.4 and earlier, only the RSVP protocol supports Packet Forwarding Engine local repair and fast reroute as well as link protection and node protection.

In Figure 1, Case 2 shows how link protection allows source Router A to switch to Link B when the primary next hop Link A to destination Router C fails. However, if Router B fails, Link B also fails, and the protected Link A is lost. If node-link protection is enabled, Router A is able to switch to Link D on Router D and bypass the failed Router B altogether. As shown in Case 1, with node-link protection enabled, Router A has a node-link protection alternate path available through Router D to destination Router C. That means that if Router B fails, Router A can still reach Router C because the path from Router A to Link D remains available as an alternate backup path.

Figure 1: Link Protection and Node-Link Protection Comparison for IS-IS Routes
Link Protection and Node-Link
Protection Comparison for IS-IS Routes

The Junos OS implementation of support for loop-free alternate paths for IS-IS routes is based on the following standards:

  • RFC 5286, Basic Specification for IP Fast-Reroute: Loop-free Alternates

  • RFC 5714, IP Fast Reroute Framework

You can configure link protection on any interface for which IS-IS is enabled. When you enable link protection, Junos OS creates one alternate path to the primary next hop for all destination routes that traverse a protected interface. Link protection assumes that only a single link becomes unavailable but that the neighboring node would still be available through another interface.

Note

You must also configure a per-packet load-balancing routing policy to ensure that the routing protocol process installs all the next hops for a given route in the routing table.

To enable link protection, include the link-protection statement at the [edit protocols isis interface interface-name] hierarchy level:

You can configure node-link protection on any interface for which IS-IS is enabled. Node-link protection establishes an alternate path through a different routing device altogether for all destination routes that traverse a protected interface. Node-link protection assumes that the entire routing device, or node, has failed. Junos OS therefore calculates a backup path that avoids the primary next-hop routing device.

Note

You must also configure a per-packet load-balancing routing policy to ensure that the routing protocol process installs all the next hops for a given route in the routing table.

To enable node-link protection, include the node-link-protection statement at the [edit protocols isis interface interface-name] hierarchy level:

Excluding an IS-IS Interface as a Backup for Protected Interfaces

By default, all IS-IS interfaces that belong to the master instance or a specific routing instance are eligible as backup interfaces for protected interfaces. You can specify that any IS-IS interface be excluded from functioning as a backup interface to protected interfaces. To exclude an IS-IS interface as a backup interface, include the no-eligible-backup statement at the [edit protocols isis interface interface-name] hierarchy level:

Configuring RSVP Label-Switched Paths as Backup Paths for IS-IS

Relying on the shortest-path-first (SPF) calculation of backup paths for one-hop neighbors might result in less than 100 percent backup coverage for a specific network topology. You can enhance coverage of IS-IS and LDP label-switched paths (LSPs) by configuring RSVP LSPs as backup paths. To configure a specific RSVP LSP as a backup path, include the backup statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level:

When configuring an LSP, you must specify the IP address of the egress routing device with the to statement. For detailed information about configuring LSPs and RSVP, see the Junos OS MPLS Applications Library for Routing Devices.

Using Operational Mode Commands to Monitor Protected IS-IS Routes

You can issue operational mode commands that provide more details about your link-protected and node-link-protected IS-IS routes. The following guidelines explain the type of information available from the output of each command:

  • show isis backup label-switched-path—Displays which MPLS LSPs have been designated as backup paths and the current status of those LSPs.

  • show isis backup spf results—Displays SPF calculations for each neighbor for a given destination. Indicates whether a specific interface or node has been designated as a backup path and why. Use the no-coverage option to display only those nodes that do not have backup coverage.

  • show isis backup coverage —Displays the percentage of nodes and prefixes for each type of address family that is protected.

  • show isis interface detail—Displays the type of protection (link or node-link) applied to each protected interface.

Example: Configuring Node-Link Protection for IS-IS Routes in a Layer 3 VPN

Node-link protection establishes an alternate path through a different routing device. Use node-link protection when you assume that access to a node is lost when a link is no longer available. Junos OS calculates a backup path that avoids the primary next-hop routing device.

Requirements

This example requires Junos OS Release 9.5 or later.

No special configuration beyond device initialization is required before configuring this example.

Overview

In this example, core-facing interfaces are enabled for IS-IS Level 2, LDP, and RSVP. Node-link protection is enabled on all the core-facing interfaces, which means that if the primary next hop for any destination that traverses the interfaces becomes unavailable, Junos OS uses a backup link that avoids the next-hop router altogether if necessary.

You also need to configure a routing policy that requires all traffic to use per-packet load balancing in order to enable Packet Forwarding Engine local repair. With local repair, the Packet Forwarding Engine can correct a path failure and implement a backup loop-free alternate route before it receives recomputed paths from the Routing Engine.

Figure 2 shows the topology used in this example.

On Device PE1, an RSVP LSP is configured as a backup path for IS-IS. Relying on the shortest-path-first (SPF) calculation of backup paths for one-hop neighbors might result in less than 100 percent backup coverage for a specific network topology. You can enhance coverage of IS-IS and LDP LSPs by configuring RSVP LSPs as backup paths. To configure a specific RSVP LSP as a backup path, include the backup statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level.

CLI Quick Configuration shows the configuration for all of the devices in Figure 2. The section Step-by-Step Procedure describes the steps on Device P1.

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 CE1

Device PE1

Device P1

Device P2

Device P3

Device PE2

Device CE2

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 multi-level IS-IS:

  1. Configure the interfaces.

    Enable IS-IS and MPLS.

  2. Configure the IS-IS interfaces for Level 2.
  3. Enable IS-IS node-link protection, which also automatically extends backup coverage to all LDP LSPs.
  4. (Optional) Configure a 1000-millisecond time interval between the detection of a topology change and when the SPF algorithm runs.
  5. Configure MPLS to use both RSVP and LDP label-switched paths (LSPs).
  6. (Optional) For LDP, enable forwarding equivalence class (FEC) deaggregation, which results in faster global convergence.
  7. To enable Packet Forwarding Engine local repair, establish a policy that forces the routing protocol process to install all the next hops for a given route.

    This policy ensures that the backup route is installed in the forwarding table used by the Packet Forwarding Engine to forward traffic to a given destination.

  8. Apply the policy to the forwarding table of the local router with the export statement.

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show policy-options, and show routing-options commands. 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.

Verification

Confirm that the configuration is working properly.

Checking the MPLS LSP Backup Path

Purpose

Display information about the MPLS label-switched-paths (LSPs) designated as the backup route for the IS-IS routes.

Action

On Device PE1, from operational mode, enter the show isis backup label-switched-path command.

Meaning

The output shows that the backup path is up and operational.

Checking Which Next-Hop Neighbors Are Designated as Backup Paths to the Destination Node

Purpose

Display SPF calculations for each neighbor for a given destination.

Action

On Device PE1, from operational mode, enter the show isis backup spf results command.

Meaning

The output indicates whether a specific interface or node has been designated as a backup path and why.

Checking the Backup Coverage

Purpose

Check the percentage of protected nodes and prefixes.

Action

From operational mode, enter the show isis backup coverage command.

Meaning

The level of backup coverage available through IS-IS routes depends on the actual network topology and is typically less than 100 percent for all destinations on any given routing device. You can extend backup coverage to include RSVP LSPs.

Checking the Type of Protection Configured

Purpose

On all nodes in the IS-IS domain, check the type and percentage of protected nodes and prefixes.

Action

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

user@PE1> show isis interface detail

Meaning

The output shows that node-link protection is configured on the interfaces.