[Contents] [Prev] [Next] [Index] [Report an Error]

Step 1: Configure Node-Link Protection

Configuring node-link protection is a two-part process. The first part involves configuring node-link protection for any LSPs traversing the protected node that require use of the bypass path, and the second part sets link protection on the outgoing RSVP interface on routers in the LSP.

Action

To configure node-link protection, follow these steps:

  1. In configuration mode, go to the following hierarchy level:
    2. [edit]

    user@R1# edit protocols mpls label-switched-path lsp-path-name

For example:

[edit]

user@R1# edit protocols mpls label-switched-path lsp2-r1-to-r5
  1. Configure node-link protection for the LSP:
    2. [edit protocols mpls label-switched-path lsp-path-name]

    user@R1# set node-link-protection
  2. Verify the node-link protection configuration for the LSP:
    3. [edit protocols mpls label-switched-path lsp-path-name]

    user@R1# show
  3. Configure link protection for the interface:
    4. [edit protocols]

    user@R1# edit protocols rsvp interface interface-name

For example:

[edit protocols]

user@R1# edit protocols rsvp interface fe-0/1/0
  1. Configure link protection:
    2. [edit protocols rsvp interface interface-name]

    user@R1# set link-protection
  2. Verify the link protection configuration for the interface, and commit both configurations:
    3. [edit protocols rsvp interface interface-name]

    user@R1# show

    user@R1# commit
  3. Repeat Step 1 through Step 3 on any other ingress routers that have LSPs requiring use of the bypass path.
  4. Repeat Step 4 and Step 5 on routers with outgoing interfaces in the LSP.

Sample Output

The following sample output shows the configuration of node-link protection on ingress router R1 in the network shown in Figure 6:



[edit protocols mpls label-switched-path lsp2-r1-to-r5]

user@R1# up 



[edit protocols mpls]

user@R1# show 

label-switched-path lsp2-r1-to-r5 { #Label-switched-path level of the hierarchy

    to 192.168.5.1;

    node-link-protection; #LSP node-link protection



[edit protocols rsvp]

user@R1# show 

interface fe-0/1/0.0 {

    link-protection; #Link protection for the RSVP interface

}



[edit protocols rsvp]

user@R1# commit 

commit complete

What It Means

The sample output shows the configuration of node-link protection for an LSP. After node-link protection is configured, bypass paths are signaled to avoid the protected link or node in case of failure. Having bypass paths available does not in itself provide protection for LSPs that traverse the protected node. You must include the node-link-protection statement on the ingress router for each LSP that will benefit from the bypass path.

[Contents] [Prev] [Next] [Index] [Report an Error]