Configure MPLS LSPs Using RSVP

To configure the MPLS LSPs using the Resource Reservation Protocol (RSVP), perform the following steps:

1. On each PE router, configure traffic engineering. To do this, you must configure an IGP that supports traffic engineering (either IS-IS or OSPF) and enable traffic engineering support for that protocol.

To enable OSPF traffic engineering support, include the traffic-engineering statement at the [edit protocols ospf] hierarchy level:

[edit protocols ospf]

traffic-engineering;

For IS-IS, traffic engineering support is enabled by default.

2. On each PE and provider router, enable RSVP on the router interfaces that participate in the LSP. On the PE router, these are the interfaces that are the ingress and egress points to the LSP. On the provider router, these are the interfaces that connect the LSP between the PE routers.

To configure RSVP on the PE and provider routers, include the interface statement at the [edit rsvp] hierarchy level. Include one interface statement for each interface on which you are enabling RSVP.

[edit]

rsvp {

    interface interface-name;

    interface interface-name;

}

3. On each PE router, configure an MPLS LSP to the PE router that is the LSP's egress point. To do this, include the label-switched-path and interface statements at the [edit mpls] hierarchy level.

[edit]

mpls {

    label-switched-path lsp-path-name {

        to ip-address;

    }

    interface interface-name;

}

In the to statement, specify the address of the LSP's egress point, which is an address on the remote PE router.

In the interface statement, specify the name of the interface (both the physical and logical portions). Include one interface statement for the interface associated with the LSP.

When you configure the same interface at the [edit interfaces] hierarchy level, you must also configure family mpls and family inet when configuring the logical interface:

[edit interfaces]

interface-name {

    unit logical-unit-number {

        family inet;

        family mpls;

    }

}

4. On all provider routers that participate in the LSP, enable MPLS by including the interface statement at the [edit mpls] hierarchy level. Include one interface statement for each connection to the LSP.

[edit]

mpls {

    interface interface-name;

    interface interface-name;

}

5. Enable MPLS on the interface between the PE and CE routers by including the interface statement at the [edit mpls] hierarchy level. Doing this allows the PE router to assign an MPLS label to traffic entering the LSP or to remove the label from traffic exiting the LSP.

[edit]

mpls {

    interface interface-name;

}

For information about configuring RSVP or MPLS, see the JUNOS Internet Software Configuration Guide: MPLS Applications.