Configuring LDP and RSVP with a Configuration Editor
To configure either LDP or RSVP as a signaling protocol on the device to establish LSPs through an IP network, perform one of the following tasks:
For information about using the J-Web and CLI configuration editors, see the J-Web Interface User Guide and the Junos CLI User Guide.
Configuring LDP-Signaled LSPs
Using LDP as a signaling protocol, you create LSPs between routers in an IP network. A sample network is shown in Figure 79.
Figure 79: Typical LDP-Signaled LSP

To establish an LSP between Routers R6 and R7, you must configure LDP on Routers R5, R6, and R7. This configuration ensures that Hosts C1 and C2 use the LDP-signaled LSP when the entry (ingress) router is R6 or R7.
To configure LDP to establish the LSP shown in Figure 79, perform these steps:
- Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
- Perform the configuration tasks described in Table 144.
- If you are finished configuring the router, commit the configuration.
- Go on to Verifying an LDP-Signaled LSP.
Table 144: Configuring an LDP-Signaled LSP
Task | J-Web Configuration Editor | CLI Configuration Editor |
|---|---|---|
Navigate to the Interfaces level of the configuration hierarchy |
| From the [edit] hierarchy level, enter edit interfaces |
Enable the MPLS family on all transit interfaces on each router in the MPLS network. |
|
|
Enable the MPLS process on all MPLS interfaces for each router in the MPLS network. (See the interface naming conventions in Network Interface Naming.) |
|
|
Create the LDP instance on each router in the MPLS network. |
|
|
Set the keepalive interval to 10 seconds. The keepalive interval specifies the number of seconds between the transmission of keepalive messages along the LDP link. |
| On each router in the MPLS network, enter set keepalive-interval 10 |
Configuring RSVP-Signaled LSPs
Using RSVP as a signaling protocol, you create LSPs between routers in an IP network. A sample network is shown in Figure 80.
Figure 80: Typical RSVP-Signaled LSP

To establish an LSP between routers R1 and R7, you must configure RSVP on all MPLS transit interfaces in the network. This configuration ensures that Hosts C1 and C2 use the RSVP-signaled LSP corresponding to the network IGP's shortest path. Additionally, this configuration reserves 10 Mbps of bandwidth.
To configure RSVP to establish the LSP shown in Figure 80, perform these steps:
- Navigate to the top of the configuration hierarchy in either the J-Web or CLI configuration editor.
- Perform the configuration tasks described in Table 145.
- If you are finished configuring the router, commit the configuration.
- Go on to Verifying an RSVP-Signaled LSP.
Table 145: Configuring an RSVP-Signaled LSP
Task | J-Web Configuration Editor | CLI Configuration Editor |
|---|---|---|
Navigate to the Interfaces level of the configuration hierarchy |
| From the [edit] hierarchy level, enter edit interfaces |
Enable the MPLS family on all transit interfaces on each router in the MPLS network. |
|
|
Enable the MPLS process on all MPLS interfaces for each router in the MPLS network. |
|
|
Create the RSVP instance on each router in the MPLS network. (See the interface naming conventions in Network Interface Naming.) |
|
|
On the entry (ingress) router, R1, define the LSP r1–r7, using Router R7's loopback address (10.0.9.7). |
|
|
Reserve 10 Mbps of bandwidth on the LSP. |
| Enter set label-switched-path r1–r7 bandwidth 10m |
Disable the use of the Constrained Shortest Path First (CSPF) algorithm. By disabling the CSPF algorithm, you specify that traffic through the LSP is to be routed along the network IGP's shortest path. |
| Enter set label-switched-path r1–r7 no-cspf |
Hide Navigation Pane
Show Navigation Pane
Download
SHA1