Discussion

aviva@R3# set rsvp interface fxp0.0 disable
Then, on the ingress router, set up the LSP:
[edit protocols mpls]
aviva@R1# set mpls label-switched-path R1-to-R6 to 10.0.0.6
Also set up a return LSP from R6 to R1 so that the LSP is bidirectional and traffic can
travel from the egress router back to the ingress router:
[edit protocols]
aviva@R6# set mpls label-switched-path R6-to-R1 to 10.0.0.1
Discussion
This recipe shows how to use RSVP as the signaling protocol for MPLS, based on the
topology shown in Figure 14-6. Interfaces running MPLS must also be running BGP
and an IGP (either IS-IS or OSPF). In this topology, all interfaces are running IS-IS
and OSPF.
so-0/0/2
10.1.13.1/30
so-0/0/2
10.1.13.2/30
so-0/0/3
10.1.36.1/30
so-0/0/3
10.1.36.2/30
R1
10.0.0.1
Ingress router
R3
10.0.0.3
Transit router
R6
10.0.0.6
Egress router
LSP R1-to-R6
Figure 14-6. MPLS with RSVP topology
LSP R6-to-R1
As with the LDP configuration, first configure the MPLS address family on the logical
interfaces so the interface can process labeled packets. On the ingress router, R1,
set the MPLS family on the so-0/0/2 interface. On the transit router, R3, add it to the
so-0/0/2 and so-0/0/3 interfaces. On the egress router, R6, configure it on the so-0/0/
3 interface. The configuration for each physical interface now has three families, IPv4
(inet), iso (for IS-IS), and MPLS:
aviva@R1> show configuration interfaces
so-0/0/2 {
unit 0 {
family inet {
address 10.1.13.1/30;
}
family iso;
family mpls;
}
Setting Up RSVP-Signaled LSPs | 503
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.