Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
IS-IS User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

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

date_range 24-Nov-23

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 1 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 1. The section #configuration364__isis-node-link-protection-step-by-step describes the steps on Device P1.

Topology

Configuration

Procedure

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

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.

content_copy zoom_out_map
user@P1# show interfaces
fe-1/2/0 {
    unit 0 {
        family inet {
            address 10.0.0.6/30;
        }
        family iso;
        family mpls;
    }
}
fe-1/2/1 {
    unit 0 {
        family inet {
            address 10.0.0.9/30;
        }
        family iso;
        family mpls;
    }
}
fe-1/2/2 {
    unit 0 {
        family inet {
            address 10.0.0.25/30;
        }
        family iso;
        family mpls;
    }
}
lo0 {
    unit 0 {
        family inet {
            address 10.255.3.3/32;
        }
        family iso {
            address 49.0001.0010.0000.0303.00;
        }
    }
}
content_copy zoom_out_map
user@P1# show protocols
rsvp {
    interface all;
    interface fxp0.0 {
        disable;
    }
}
mpls {
    interface all;
    interface fxp0.0 {
        disable;
    }
}
isis {
    spf-options delay 1000;
    interface all {
        node-link-protection;
        level 2 metric 10;
        level 1 disable;
    }
    interface fxp0.0 {
        disable;
    }
    interface lo0.0 {
        level 2 metric 0;
    }
}
ldp {
    deaggregate;
    interface all;
    interface fxp0.0 {
        disable;
    }
}
content_copy zoom_out_map
user@P1# show policy-options
policy-statement ecmp {
    term 1 {
        then {
            load-balance per-packet;
        }
    }
}
content_copy zoom_out_map
user@P1# show routing-options
forwarding-table {
    export ecmp;
}

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.

content_copy zoom_out_map
user@PE1> show isis backup label-switched-path
Backup MPLS LSPs:
to-p2, Egress: 10.255.4.4, Status: up, Last change: 01:17:45
  TE-metric: 19, Metric: 0, Refcount: 1

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.

content_copy zoom_out_map
user@PE1> show isis backup spf results
 
 IS-IS level 1 SPF results:
  0 nodes

 IS-IS level 2 SPF results:
PE2.00
  Primary next-hop: fe-1/2/2.0, IPV4, P3, SNPA:  0:5:85:8f:c8:bd
    Root: P2, Root Metric: 20, Metric: 10, Root Preference: 0x0
      track-item: P2.00-00
      Eligible, Backup next-hop: fe-1/2/1.0, LSP, to-p2
    Root: P3, Root Metric: 10, Metric: 10, Root Preference: 0x0
      Not eligible, Reason: Interface is already covered 
    Root: P1, Root Metric: 10, Metric: 20, Root Preference: 0x0
      track-item: P3.00-00
      Not eligible, Reason: Interface is already covered 
P2.00
  Primary next-hop: fe-1/2/1.0, IPV4, P1, SNPA:  0:5:85:8f:c8:bd
    Root: P2, Root Metric: 20, Metric: 0, Root Preference: 0x0
      track-item: P2.00-00
      Not eligible, Reason: Primary next-hop link fate sharing 
    Root: P1, Root Metric: 10, Metric: 10, Root Preference: 0x0
      Not eligible, Reason: Primary next-hop link fate sharing 
    Root: P3, Root Metric: 10, Metric: 20, Root Preference: 0x0
      track-item: P1.00-00
      Not eligible, Reason: Primary next-hop node fate sharing 
P3.00
  Primary next-hop: fe-1/2/2.0, IPV4, P3, SNPA:  0:5:85:8f:c8:bd
    Root: P2, Root Metric: 20, Metric: 20, Root Preference: 0x0
      track-item: P3.00-00
      track-item: P2.00-00
      track-item: P1.00-00
      Eligible, Backup next-hop: fe-1/2/1.0, LSP, to-p2
    Root: P3, Root Metric: 10, Metric: 0, Root Preference: 0x0
      Not eligible, Reason: Interface is already covered 
    Root: P1, Root Metric: 10, Metric: 10, Root Preference: 0x0
      track-item: P3.00-00
      Not eligible, Reason: Interface is already covered 
P1.00
  Primary next-hop: fe-1/2/1.0, IPV4, P1, SNPA:  0:5:85:8f:c8:bd
    Root: P2, Root Metric: 20, Metric: 10, Root Preference: 0x0
      track-item: P2.00-00
      track-item: P1.00-00
      Not eligible, Reason: Primary next-hop link fate sharing 
    Root: P1, Root Metric: 10, Metric: 0, Root Preference: 0x0
      Not eligible, Reason: Primary next-hop link fate sharing 
    Root: P3, Root Metric: 10, Metric: 10, Root Preference: 0x0
      track-item: P1.00-00
      Eligible, Backup next-hop: fe-1/2/2.0, IPV4, P3, SNPA:  0:5:85:8f:c8:bd
  4 nodes

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.

content_copy zoom_out_map
user@PE1> show isis backup coverage 
Backup Coverage:
Topology        Level   Node    IPv4    IPv6    CLNS
IPV4 Unicast        1   0.00%   0.00%   0.00%   0.00%
IPV4 Unicast        2  75.00%  87.50%   0.00%   0.00%
content_copy zoom_out_map
user@P1> show isis backup coverage 
Backup Coverage:
Topology        Level   Node    IPv4    IPv6    CLNS
IPV4 Unicast        1   0.00%   0.00%   0.00%   0.00%
IPV4 Unicast        2  75.00%  71.43%   0.00%   0.00%
content_copy zoom_out_map
user@P2> show isis backup coverage 
Backup Coverage:
Topology        Level   Node    IPv4    IPv6    CLNS
IPV4 Unicast        1   0.00%   0.00%   0.00%   0.00%
IPV4 Unicast        2  50.00%  37.50%   0.00%   0.00%
content_copy zoom_out_map
user@P3> show isis backup coverage 
Backup Coverage:
Topology        Level   Node    IPv4    IPv6    CLNS
IPV4 Unicast        1   0.00%   0.00%   0.00%   0.00%
IPV4 Unicast        2  75.00%  71.43%   0.00%   0.00%
content_copy zoom_out_map
user@PE2> show isis backup coverage 
Backup Coverage:
Topology        Level   Node    IPv4    IPv6    CLNS
IPV4 Unicast        1   0.00%   0.00%   0.00%   0.00%
IPV4 Unicast        2  50.00%  37.50%   0.00%   0.00%

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.

content_copy zoom_out_map
user@PE1> show isis interface detail

IS-IS interface database:
lo0.0
  Index: 76, State: 0x6, Circuit id: 0x1, Circuit type: 0
  LSP interval: 100 ms, CSNP interval: disabled
  Adjacency advertisement: Advertise
  Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
    1             0       64      0 Passive
    2             0       64      0 Passive
fe-1/2/2.0
  Index: 79, State: 0x6, Circuit id: 0x1, Circuit type: 2
  LSP interval: 100 ms, CSNP interval: 10 s
  Adjacency advertisement: Advertise
  Protection Type: Node Link
  Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
    2             1       64     10     9.000       27 P3.03 (not us)
fe-1/2/1.0
  Index: 77, State: 0x6, Circuit id: 0x1, Circuit type: 2
  LSP interval: 100 ms, CSNP interval: 10 s
  Adjacency advertisement: Advertise
  Protection Type: Node Link
  Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
    2             1       64     10     9.000       27 P1.02 (not us)

Meaning

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

footer-navigation