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

Configuring the MPLS LSP Tunnel Between the PE Routers

In this configuration example, RSVP is used for VPN signaling. Therefore, in addition to configuring RSVP, you must enable traffic engineering support in an IGP and you must create an MPLS LSP to tunnel the VPN traffic.

On PE Router A, enable RSVP and configure one end of the MPLS LSP tunnel. In this example, traffic engineering support is enabled for Open Shortest Path First (OSPF). When configuring the MPLS LSP, include interface statements for all interfaces participating in MPLS, including the interfaces to the PE and CE routers. The statements for the interfaces between the PE and CE routers are needed so that the PE router can create an MPLS label for the private interface. In this example, the first interface statement configures MPLS on the interface connected to the LSP, and the remaining three configure MPLS on the interfaces that connect the PE router to the CE routers.



[edit]
protocols {


rsvp {
interface so-3/0/0.0;
}




mpls {


label-switched-path RouterA-to-RouterC {
to 10.255.245.47;
}


interface so-3/0/0.0;
interface so-6/0/0.0;
interface so-6/0/1.0;
interface ge-0/3/0.0;
}




ospf {
traffic-engineering;


area 0.0.0.0 {
interface so-3/0/0.0;
}


}


}

On PE Router C, enable RSVP and configure the other end of the MPLS LSP tunnel. Again, traffic engineering support is enabled for OSPF, and you configure MPLS on the interfaces to the LSP and the CE routers.



[edit]
protocols {


rsvp {
interface so-2/0/0.0;
}




mpls {


label-switched-path RouterC-to-RouterA {
to 10.255.245.68;
}


interface so-2/0/0.0;
interface ge-1/0/0.0;
interface at-1/2/0.0;
}




ospf {
traffic-engineering;


area 0.0.0.0 {
interface so-2/0/0.0;
}


}


}

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