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

Example: Node-Link Protection Configuration

Figure 11: Node-Link Protection Topology Diagram

Image g017145.gif

Figure 11 shows an example of how you can implement node-link protection. An LSP is initiated on Router 0 with a strict path travelling through Router 1, Router 2, Router 3, and Router 4. You configure node-link protection within the LSP and link protection on all RSVP interfaces in the path.

On Router 0, configure an LSP to travel across routers 1, 2, 3, and 4. Include the node-link-protection statement in the LSP and configure link protection on outgoing RSVP interface fe-0/1/1. To support the LSP, configure OSPF, MPLS, and RSVP on the needed interfaces.

Router 0

[edit]
interfaces {
fe-0/1/1 {
unit 0 {
family inet {
address 10.11.1.10/30;
}
family mpls;
}
}
so-0/0/2 {
unit 0 {
family inet {
address 10.11.1.22/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.11.220/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-0/1/1.0;
interface so-0/0/2.0;
}
traffic-engineering;
}
mpls {
statistics {
file mplsStat.log size 1m;
interval 30;
display-id;
}
traffic-engineering bgp-igp-both-ribs;
traceoptions {
file mpls.log size 5m world-readable;
flag cspf;
flag cspf-link;
flag cspf-node;
flag state;
flag error;
}
explicit-null;
label-switched-path test_r0_r4 {
from 10.255.11.220;
to 10.255.11.215;
node-link-protection; # Apply node-link protection to the LSP.
primary pathP;
}
path pathP {# Define the LSP path across routers 1, 2, 3, and 4.
10.11.1.9 strict;
10.11.1.2 strict;
10.11.2.1 strict;
10.11.2.10 strict;
}
interface fe-0/1/1.0;
interface so-0/0/2.0;
}
rsvp {
traceoptions {
file rsvp.log size 3m files 12 world-readable;
flag event;
flag state;
flag error;
flag packets detail;
}
interface fe-0/1/1.0 {
link-protection; # Apply link protection to RSVP interfaces in the LSP path.
}
interface so-0/0/2.0;
}
}

On Router 1, configure link protection on outgoing RSVP interface so-0/0/3. Configure OSPF, MPLS, and RSVP on all transit interfaces.

Router 1

[edit]
interfaces {
fe-0/1/0 {
unit 0 {
family inet {
address 10.11.3.1/30;
}
family mpls;
}
}
fe-2/2/1 {
unit 0 {
family inet {
address 10.11.1.9/30;
}
family mpls;
}
}
so-0/0/3 {
unit 0 {
family inet {
address 10.11.1.1/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.11.223/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-0/1/0.0;
interface fe-2/2/1.0;
interface so-0/0/3.0;
}
traffic-engineering;
}
mpls {
traffic-engineering bgp-igp-both-ribs;
explicit-null;
interface fe-0/1/0.0;
interface fe-2/2/1.0;
interface so-0/0/3.0;
}
rsvp {
interface fe-0/1/0.0;
interface fe-2/2/1.0;
interface so-0/0/3.0 {
link-protection; # Apply link protection on all RSVP interfaces in the LSP path.
}
}
}

On Router 2, configure link protection on outgoing RSVP interface so-0/0/0. Configure OSPF, MPLS, and RSVP on all transit interfaces.

Router 2

[edit]
interfaces {
so-0/0/0 {
unit 0 {
family inet {
address 10.11.2.2/30;
}
family mpls;
}
}
so-0/0/2 {
unit 0 {
family inet {
address 10.11.1.21/30;
}
family mpls;
}
}
so-0/0/3 {
unit 0 {
family inet {
address 10.11.1.2/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.11.218/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface so-0/0/0.0;
interface so-0/0/2.0;
interface so-0/0/3.0;
}
traffic-engineering;
}
mpls {
traffic-engineering bgp-igp-both-ribs;
explicit-null;
interface so-0/0/0.0;
interface so-0/0/2.0;
interface so-0/0/3.0;
}
rsvp {
interface so-0/0/0.0 {
link-protection; # Apply link protection to RSVP interfaces in the LSP path.
}
interface so-0/0/2.0;
interface so-0/0/3.0;
}
}

On Router 3, configure link protection on outgoing RSVP interface fe-0/1/2. Configure OSPF, MPLS, and RSVP on all transit interfaces.

Router 3

[edit]
interfaces {
fe-0/1/0 {
unit 0 {
family inet {
address 10.11.3.2/30;
}
family mpls;
}
}
fe-0/1/2 {
unit 0 {
family inet {
address 10.11.2.9/30;
}
family mpls;
}
}
so-0/0/0 {
unit 0 {
family inet {
address 10.11.2.1/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.11.216/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-0/1/0.0;
interface fe-0/1/2.0;
interface so-0/0/0.0;
}
traffic-engineering;
}
mpls {
traffic-engineering bgp-igp-both-ribs;
explicit-null;
interface fe-0/1/0.0;
interface fe-0/1/2.0;
interface so-0/0/0.0;
}
rsvp {
interface fe-0/1/0.0;
interface fe-0/1/2.0 {
link-protection; # Apply link protection to RSVP interfaces in the LSP path.
}
interface so-0/0/0.0;
}
}

Because Router 4 is the endpoint of the LSP, you can configure interfaces and protocols as usual. There is no need to configure any node-link protection or link protection statements on this router.

Router 4

[edit]
interfaces {
fe-0/1/2 {
unit 0 {
family inet {
address 10.11.2.10/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.11.215/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-0/1/2.0;
}
traffic-engineering;
}
mpls {
traffic-engineering bgp-igp-both-ribs;
explicit-null;
interface fe-0/1/2.0;
}
rsvp {
interface fe-0/1/2.0;
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.