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.
Configure MPLS to install the LSP routes into the
inet.0 unicast routing table:
[edit protocols mpls] aviva@R1#
set traffic-engineering bgp-igp
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:
show route table inet.3inet.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
inet.0 routing table contains the expected
unicast routes from IS-IS, OSPF, and BGP:
show route table inet.0inet.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 ...