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

Step 1: Configure Link Protection

Purpose

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

Action

To configure link protection, follow these steps:

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

    user@R1# edit protocols rsvp interface type-fpc/pic/port

For example:

[edit]

user@R1# edit protocols rsvp interface fe-0/1/0
  1. Configure link protection for the interface:
    2. [edit protocols rsvp interface type-fpc/pic/port]

    user@R1# set link-protection
  2. Verify the link protection configuration for the interface:
    3. [edit protocols rsvp interface type-fpc/pic/port]

    user@R1# show
  3. Configure link protection for LSPs requiring use of the bypass path:
    4. [edit protocols rsvp interface fe-0/1/0.0]

    user@R1# top

    

    [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 link protection for the LSP:
    2. [edit protocols mpls label-switched-path lsp-path-name]

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

    user@R1# show

    user@R1# commit

Sample Output

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



[edit protocols rsvp]

user@R1# show 

interface fe-0/1/0.0 {

    link-protection; #Protection for the RSVP interface 

}



[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 { #Path level of the hierarchy

    to 192.168.5.1;

    link-protection;



[edit protocols mpls]

user@R1# commit 

commit complete

What It Means

The sample output shows link protection for a specific interface. After link protection is configured, a bypass path is signaled to avoid that link in case of a failure. Having a bypass path available does not in itself provide protection for LSPs that traverse the protected link. You must configure link protection on the ingress router for each LSP that will benefit from the bypass path.

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