Discussion

family to the t1-4/0/0 interface; on the transit router, RouterJ, add it to the t1-5/0/0
and fe-1/0/1 interfaces; and on the egress router, RouterF, add it to the fe-0/0/1
interface. The interface configuration now has two families, IPv4 (inet) and MPLS:
aviva@RouterG> show configuration interfaces
t1-4/0/0 {
unit 0 {
family inet {
address 10.0.0.1/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 192.168.19.1/32;
}
}
}
The output shows the MPLS family on the t1-4/0/0 interface on the ingress router
but not on the loopback interface. Because the loopback interface isn’t a transit interface
and never carries labeled packets, you don’t need to configure it for the MPLS
family.
Use the show interfaces terse command to verify that the MPLS family is configured
on all expected interfaces. Here’s the output for the transit router:
aviva@RouterJ> show interfaces terse
Interface Admin Link Proto Local Remote
fe-0/0/0 up up
fe-0/0/0.0 up up inet 172.19.121.117/24
fe-1/0/1 up up
fe-1/0/1.0 up up inet 10.0.8.1/24
mpls
t1-5/0/0 up up
t1-5/0/0.0 up up inet 10.0.0.2/24
mpls
lo0 up up
lo0.0 up up inet 192.168.17.1 --> 0/0
lo0.16385 up up inet 10.0.0.1 --> 0/0
10.0.0.16 --> 0/0
This output confirms that the two MPLS interfaces, fe-1/0/1 and t1-5/0/0, are configured
with the MPLS family and have IPv4 addresses, and that the loopback interface,
lo0.0, has only an IPv4 address and is not configured for the MPLS family.
Next, configure the router to run the MPLS protocol. The basic configuration is very
simple. In the [edit protocols mpls] section of the configuration hierarchy, list the
router interfaces on which MPLS will run. For the ingress router, configure MPLS on
the interface that leads toward the far end of the LSP:
[edit protocols]
aviva@RouterG# set mpls interface t1-4/0/0
Configuring LSPs Using LDP as the Signaling Protocol | 487
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.