Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

install (Protocols MPLS)

 

Syntax

Hierarchy Level

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 13.2X51-D15 for the QFX Series.

Statement introduced in Junos OS Release 14.1X53-D30 for the QFX Series Virtual Chassis and Virtual Chassis Fabric.

Support at the [edit protocols source-packet-routing source-routing-path lsp-name] hierarchy level introduced in Junos OS Release 19.1R1.

Description

Associate one or more prefixes with an LSP. When the LSP is up, all the prefixes are installed as entries into the inet.3 or inet6.3 routing table.

The support of the install statement at the [edit protocols source-packet-routing source-routing-path lsp-name] is applicable for both colored and non-colored segment routing LSPs.

For static colored LSPs, when the install prefix is configured, a route similar to the tunnel ingress route is installed in the inetcolor.0 or inet6color.0 routing table.

On the other hand, for static non-colored LSPs, when the install prefix is configured, a route similar to the tunnel to route is installed in inet.3 or inet6.3 routing table.

You can use the show route table command to view the install routes for both colored and non-colored segment routing traffic-engineered LSPs.

Note

Take the following into consideration when configuring the install destination-prefix statement at the [edit protocols source-packet-routing source-routing-path lsp-name] hierarchy level:

  • The install prefixes should be unique in a tunnel, and should not be the same as the tunnel to address. A commit check is done to ensure that the prefixes are unique.

  • If two install prefixes are same across two different tunnels, then the gateways of the both tunnels are considered only if the segment lists are of the same resolution type. If the first hop resolution types vary, the route is not installed. In such cases, a system log message is generated to record the error.

For example:

The inet.3 routing table has two additional routes (to 20.20.20.2 and 30.30.30.3) with next hops derived from the same segment list path-1 with same attributes as the to address route.

Options

active(Optional) Install the route into the inet.0 or inet6.0 routing table. This allows you to issue a ping or traceroute command on this address.
Note

The install destination-prefix active statement is not supported on static LSPs. When the install destination-prefix active statement is configured for a static LSP, the MPLS routes do not get installed into the inet.0 routing table.

destination-prefixIPv4 or IPv6 address to associate with the LSP.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.