Installing LSPs into the Unicast Routing Table

Problem

You want to install the routes from the label forwarding table, inet.3, into the unicast routing table, inet.0, so that applications such as ping can use LSPs.

Solution

Configure MPLS to install the LSP routes into the inet.0 unicast routing table:

[edit protocols mpls] aviva@R1# set traffic-engineering bgp-igp

Discussion

One of the main reasons that you configure LSPs on your network is to control the shortest path between two points on the network. By default, the JUNOS MPLS software stores the LSP routes in the inet.3 routing table, which can be used by MPLS and BGP. Applications such as ping and traceroute, which use the routes in the inet.0 table, cannot take advantage of the LSP routes.

You can confirm the default behavior by looking at the two routing tables. One LSP is configured on router R1, and the inet.3 table contains the RSVP route for that LSP:

aviva@R1> show route table inet.3 inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.6/32 *[RSVP/7] 00:00:07, metric 2 > via so-0/0/2.0, label-switched-path R1-to-R6

The inet.0 routing table contains the expected unicast routes from IS-IS, OSPF, and BGP:

aviva@R1> show route table inet.0 inet.0: 14 destinations, 18 routes (14 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0.0.0.0/0 *[Static/5] 5w0d 05:51:43 Discard 10.0.0.1/32 *[Direct/0] 5w0d 05:51:43 > via lo0.0 10.0.0.3/32 *[OSPF/10] 00:00:14, metric 1 > via so-0/0/2.0 [IS-IS/18] 00:00:14, metric 10 > to 10.1.13.2 via so-0/0/2.0 10.0.0.6/32 *[OSPF/10] 00:00:14, metric 2 > via so-0/0/2.0 [IS-IS/18] 00:00:14, metric 20 > to 10.1.13.2 via so-0/0/2.0 10.1.13.0/30 *[Direct/0] 00:16:20 > via so-0/0/2.0 [OSPF/10] 00:00:14, metric 1 > via so-0/0/2.0 10.1.13.1/32 *[Local/0] 2d 20:39:51 Local via so-0/0/2.0 10.1.36.0/30 *[OSPF/10] 00:00:14, metric 2 > via so-0/0/2.0 [IS-IS/18] 00:00:14, metric 20 > to 10.1.13.2 via so-0/0/2.0 100.100.6.0/24 *[BGP/170] 00:15:37, localpref 100, from 10.0.0.6 AS path: I > via so-0/0/2.0, label-switched-path R1-to-R6 192.168.0.0/16 *[Static/5] 4d 16:57:10 > to 192.168.71.254 via fxp0.0 192.168.64.0/21 *[Direct/0] 4d 16:57:10 > via fxp0.0 192.168.70.143/32 *[Local/0] 5w0d 05:51:43 Local via fxp0.0 224.0.0.5/32 *[OSPF/10] 5w0d 05:51:44, metric 1 MultiRecv

This recipe configures the router to install the routes from the inet.3 routing table into the inet.0 unicast routing table so they are accessible to ping and traceroute. Simply use the set traffic-engineering bgp-igp command to modify where the routes are installed. To check the effect, first look at the inet.3 routing table:

aviva@R1> show route table inet.3 aviva@R1>

This command shows that this routing table is empty. Then look at the unicast routing table:

aviva@R1> show route table inet.0 inet.0: 14 destinations, 19 routes (14 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 0.0.0.0/0 *[Static/5] 5w0d 05:53:28 Discard 10.0.0.1/32 *[Direct/0] 5w0d 05:53:28 > via lo0.0 10.0.0.3/32 *[OSPF/10] 00:00:05, metric 1 > via so-0/0/2.0 [IS-IS/18] 00:00:05, metric 10 > to 10.1.13.2 via so-0/0/2.0 10.0.0.6/32 *[RSVP/7] 00:00:05, metric 2 > via so-0/0/2.0, label-switched-path R1-to-R6 [OSPF/10] 00:00:05, metric 2 > via so-0/0/2.0 [IS-IS/18] 00:00:05, metric 20 > to 10.1.13.2 via so-0/0/2.0 10.1.13.0/30 *[Direct/0] 00:18:05 > via so-0/0/2.0 [OSPF/10] 00:00:05, metric 1 > via so-0/0/2.0 10.1.13.1/32 *[Local/0] 2d 20:41:36 Local via so-0/0/2.0 10.1.36.0/30 *[OSPF/10] 00:00:05, metric 2 > via so-0/0/2.0 [IS-IS/18] 00:00:05, metric 20 > to 10.1.13.2 via so-0/0/2.0 100.100.6.0/24 *[BGP/170] 00:17:22, localpref 100, from 10.0.0.6 AS path: I > via so-0/0/2.0, label-switched-path R1-to-R6 192.168.0.0/16 *[Static/5] 4d 16:58:55 > to 192.168.71.254 via fxp0.0 192.168.64.0/21 *[Direct/0] 4d 16:58:55 > via fxp0.0 192.168.70.143/32 *[Local/0] 5w0d 05:53:28 Local via fxp0.0 224.0.0.5/32 *[OSPF/10] 5w0d 05:53:29, metric 1 MultiRecv

The LSP route to 10.0.0.6, which is learned from RSVP and had been in the inet.3 routing table, is now installed in the inet.0 table.

See Also

Recipe 8.1