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

Example: RSVP LSP Tunnel Configuration

Figure 12: RSVP LSP Tunnel Topology Diagram

Image g017200.gif

Figure 12 shows an end-to-end RSVP LSP called e2e_lsp_r0r5 that originates on Router 0 and terminates on Router 5. In transit, this LSP traverses the FA-LSP fa_lsp_r1r4. The return path is represented by the end-to-end RSVP LSP e2e_lsp_r5r0 that travels over the FA-LSP fa_lsp_r4r1.

On Router 0, configure the end-to-end RSVP LSP that travels to Router 5. Use a strict path that traverses Router 1 and the LMP TE link traveling from Router 1 to Router 4.

Router 0



[edit]
interfaces {


so-0/0/3 {


unit 0 {


family inet {
address 10.1.2.1/30;
}


family mpls;
}


}




lo0 {


unit 0 {


family inet {
address 10.255.41.222/32;
}


family mpls;
}


}


}
routing-options {


forwarding-table {
export pplb;
}


}
protocols {


rsvp {
interface all;


interface fxp0.0 {
disable;
}


}




mpls {


admin-groups {
fa 1;
backup 2;
other 3;
}




                   
label-switched-path e2e_lsp_r0r5
{ # An end-to-end LSP traveling to Router 5.
to 10.255.41.221;
bandwidth 30k;
                   
primary path-fa; # Reference the requested path here.
}




                   
path path-fa { # Configure the strict path here.
10.1.2.2 strict;
                   
172.16.30.2 strict; # This traverses the TE link heading to Router 4.
}


interface all;


interface fxp0.0 {
disable;
}




interface so-3/2/1.0 {
 admin-group other;
}




interface so-0/0/3.0 {
admin-group other;
}


}




ospf {
traffic-engineering;


area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface all;
}


}


}
policy-options {


policy-statement pplb {


then {
load-balance per-packet;
}


}


}

On Router 1, configure an FA-LSP to reach Router 4. Establish an LMP TE link and LMP peer relationship with Router 4. Reference the FA-LSP in the TE link and add the peer interface into both OSPF and RSVP.

When the return path end-to-end LSP arrives at Router 1, the routing platform performs a routing lookup and can forward traffic to Router 0. Make sure you configure OSPF correctly between Routers 0 and 1.

Router 1



[edit]
interfaces {


so-0/0/1 {


unit 0 {


family inet {
address 10.2.3.1/30;
}


family mpls;
}


}




so-0/0/2 {


unit 0 {


family inet {
address 10.2.4.1/30;
}


family mpls;
}


}




so-0/0/3 {


unit 0 {


family inet {
address 10.1.2.2/30;
}


family mpls;
}


}




fe-0/1/2 {


unit 0 {


family inet {
address 10.2.5.1/30;
}


family mpls;
}


}




at-1/0/0 {


atm-options {
vpi 1;
}




 unit 0 {
vci 1.100;


family inet {
address 10.2.3.5/30;
}


family mpls;
}


}


}
routing-options {


forwarding-table {
export [ pplb choose_lsp ];
}


}
protocols {


rsvp {
interface all;


interface fxp0.0 {
disable;
}


                 
peer-interface r4; # Apply the LMP peer interface here.
}




mpls {


admin-groups {
fa 1;
backup 2;
other 3;
}




                   
label-switched-path fa_lsp_r1r4
{ # Configure your FA-LSP to Router 4 here.
to 10.255.41.217;
bandwidth 400k;
                   
primary path_r1r4; # Apply the FA-LSP path here.
}




                   
path path_r1r4 { # Configure the FA-LSP path here.
10.2.4.2;
10.4.5.2;
10.3.5.1;
}




interface so-0/0/3.0 {
admin-group other;
}




interface so-0/0/1.0 {
admin-group fa;
}




interface at-1/0/0.0 {
admin-group backup;
}




interface fe-0/1/2.0 {
admin-group backup;
}




interface so-0/0/2.0 {
admin-group fa;
}


}




ospf {
traffic-engineering;


area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface all;
                   
peer-interface r4; # Apply the LMP peer interface here.
}


}




                 
link-management { # Configure LMP statements here.


te-link link_r1r4 { # Assign a name to the TE link here.
local-address 172.16.30.1; # Configure a local address
for the TE link.
remote-address 172.16.30.2; # Configure a remote address
for the TE link.
te-metric 1; # Manually set a metric here if you are not
relying on CSPF.
label-switched-path fa_lsp_r1r4; # Reference the FA-LSP
here.
}




peer r4 { # Configure LMP peers here.
address 10.255.41.217; # Configure the loopback address
of your peer here.
te-link link_r1r4; # Apply the LMP TE link here.
}


}


}
policy-options {


policy-statement choose_lsp {


term A {
from community choose_e2e_lsp;


then {
install-nexthop strict lsp e2e_lsp_r1r4;
accept;
}


}




term B {
from community choose_fa_lsp;


then {
install-nexthop strict lsp fa_lsp_r1r4;
accept;
}


}


}




policy-statement pplb {


then {
load-balance per-packet;
}


}


community choose_e2e_lsp members 1000:1000;
community choose_fa_lsp members 2000:2000;
community set_e2e_lsp members 1000:1000;
community set_fa_lsp members 2000:2000;
}

On Router 2, configure OSPF, MPLS, and RSVP on all interfaces that transport the FA-LSPs across the core network.

Router 2



[edit]
interfaces {


so-0/0/0 {


unit 0 {


family inet {
address 10.4.5.1/30;
}


family mpls;
}


}




so-0/0/1 {


unit 0 {


family inet {
address 10.1.4.2/30;
}


family mpls;
}


}




so-0/0/2 {


unit 0 {


family inet {
address 10.2.4.2/30;
}


family mpls;
}


}




fe-0/1/2 {


unit 0 {


family inet {
address 10.3.4.2/30;
}


family mpls;
}


}


}
routing-options {


forwarding-table {
export pplb;
}


}
               
protocols { #
OSPF, MPLS, and RSVP form the core backbone for the FA-LSPs.


                 
rsvp {    
          

interface all;


interface fxp0.0 {
disable;
}


}




                 
mpls {    
          



admin-groups {
fa 1;
backup 2;
other 3;
}




path path_r1 {
10.2.4.1;
}




path path_r3r4 {
10.4.5.2;
10.3.5.1;
}


interface all;


interface fxp0.0 {
disable;
}




interface so-0/0/1.0 {
admin-group other;
}




interface fe-0/1/2.0 {
admin-group backup;
}




interface so-0/0/2.0 {
admin-group fa;
}




interface so-0/0/0.0 {
admin-group fa;
}


}




                 
ospf {    
          

traffic-engineering;


area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface all;
}


}


}
policy-options {


policy-statement pplb {


then {
load-balance per-packet;
}


}


}

On Router 3, configure OSPF, MPLS, and RSVP on all interfaces that transport the FA-LSPs across the core network.

Router 3



[edit]
interfaces {


so-0/0/0 {


unit 0 {


family inet {
address 10.4.5.2/30;
}


family mpls;
}


}




so-0/0/1 {


unit 0 {


family inet {
address 10.5.6.1/30;
}


family mpls;
}


}




so-0/0/2 {


unit 0 {


family inet {
address 10.3.5.2/30;
}


family mpls;
}


}




fe-0/1/2 {


unit 0 {


family inet {
address 10.2.5.2/30;
}


family mpls;
}


}


}
routing-options {


forwarding-table {
export pplb;
}


}

protocols { # OSPF, MPLS, and
RSVP form the core backbone for the FA-LSPs.



rsvp {

interface all;


interface fxp0.0 {
disable;
}


}




                 
mpls {    
          



admin-groups {
fa 1;
backup 2;
other 3;
}




path path_r4 {
10.3.5.1;
}




path path_r2r1 {
10.4.5.1;
10.2.4.1;
}


interface all;


interface fxp0.0 {
disable;
}




interface so-0/0/2.0 {
admin-group fa;
}




interface fe-0/1/2.0 {
admin-group backup;
}




interface so-0/0/1.0 {
admin-group other;
}




interface so-0/0/0.0 {
 admin-group fa;
}


}




                 
ospf {    
          

traffic-engineering;


area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface all;
}


}


}
policy-options {


policy-statement pplb {


then {
load-balance per-packet;
}


}


}

On Router 4, configure a return path FA-LSP to reach Router 1. Establish an LMP TE link and LMP peer relationship with Router 1. Reference the FA-LSP in the TE link and add the peer interface into both OSPF and RSVP.

When the initial end-to-end LSP arrives at Router 4, the routing platform performs a routing lookup and can forward traffic to Router 5. Make sure you configure OSPF correctly between Routers 4 and 5.

Router 4



[edit]
interfaces {


so-0/0/0 {


unit 0 {


family inet {
address 10.3.6.1/30;
}


family mpls;
}


}




so-0/0/1 {


unit 0 {


family inet {
address 10.2.3.2/30;
}


family mpls;
}


}




so-0/0/2 {


unit 0 {


family inet {
address 10.3.5.1/30;
}


family mpls;
}


}




fe-0/1/2 {


unit 0 {


family inet {
address 10.3.4.1/30;
}


family mpls;
}


}




at-1/0/0 {


atm-options {
vpi 1;
}




unit 0 {
vci 1.100;


family inet {
address 10.2.3.6/30;
}


family mpls;
}


}


}
routing-options {


forwarding-table {
export [ pplb choose_lsp ];
}


}
protocols {


rsvp {
interface all;


interface fxp0.0 {
disable;
}


                 
peer-interface r1; # Apply the LMP peer interface here.
}




mpls {


admin-groups {
fa 1;
backup 2;
other 3;
}




                   
label-switched-path fa_lsp_r4r1
{ # Configure your FA-LSP here.
to 10.255.41.216;
 bandwidth 400k;
                   
primary path_r4r1; # Apply the FA-LSP path here.
}




                   
path path_r4r1 { # Configure the FA-LSP path here.
10.3.5.2;
10.4.5.1;
10.2.4.1;
}


interface all;


interface fxp0.0 {
disable;
}




interface at-1/0/0.0 {
admin-group backup;
}




interface so-0/0/2.0 {
admin-group fa;
}




interface fe-0/1/2.0 {
admin-group backup;
}




interface so-0/0/0.0 {
admin-group other;
}




interface so-0/0/1.0 {
admin-group fa;
}


}




ospf {          
traffic-engineering;


area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface all;
                   
peer-interface r1; # Apply the LMP peer interface here.
}


}




                 
link-management { # Configure LMP statements here.



te-link link_r4r1 { # Assign
a name to the TE link here.
                   
local-address 172.16.30.2; # Configure a local address for the TE link.

remote-address 172.16.30.1; #
Configure a remote address for the TE link.
                   
te-metric 1; # Manually set a metric here if you are not relying on CSPF.

label-switched-path fa_lsp_r4r1; # Reference the FA-LSP here.
}




                   
peer r1 { # Configure LMP peers here.

address 10.255.41.216; # Configure
the loopback address of your peer here.
                   
te-link link_r4r1; # Apply the LMP TE link here.
}


}


}
policy-options {


policy-statement choose_lsp {


term A {
from community choose_e2e_lsp;


then {
install-nexthop strict lsp e2e_lsp_r4r1;
accept;
}


}




term B {
from community choose_fa_lsp;


then {
install-nexthop strict lsp fa_lsp_r4r1;
accept;
}


}


}




policy-statement pplb {


then {
load-balance per-packet;
}


}


community choose_e2e_lsp members 1000:1000;
community choose_fa_lsp members 2000:2000;
community set_e2e_lsp members 1000:1000;
community set_fa_lsp members 2000:2000;
}

On Router 5, configure the return path end-to-end RSVP LSP that travels to Router 0. Use a strict path that traverses Router 4 and the LMP TE link traveling from Router 4 to Router 1.

Router 5



[edit]
interfaces {


so-0/0/2 {


unit 0 {


family inet {
address 10.3.6.2/30;
}


family mpls;
}


}




lo0 {


unit 0 {


family inet {
address 10.255.41.221/32;
}


}


}


}
routing-options {


forwarding-table {
export pplb;
}


}
protocols {


rsvp {
interface all;


interface fxp0.0 {
disable;
}


}




mpls {


admin-groups {
fa 1;
backup 2;
other 3;
}




                   
label-switched-path e2e_lsp_r5r0
{ # An end-to-end LSP returning to Router 0.
to 10.255.41.222;
bandwidth 30k;
                   
primary path-fa; # Reference the requested path here.
}




                   
path path-fa { # Configure the strict path here.
10.3.6.1 strict;
                   
172.16.30.1 strict; # This traverses the TE link heading to Router 1.
}


interface all;


interface fxp0.0 {
disable;
}




interface so-0/0/2.0 {
admin-group other;
}




interface so-0/0/1.0 {
admin-group other;
}


}




ospf {
traffic-engineering;


area 0.0.0.0 {


interface fxp0.0 {
disable;
}


interface all;
}


}


}
policy-options {


policy-statement pplb {


then {
load-balance per-packet;
}


}


}

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