install (Protocols MPLS)
Syntax
install {
destination-prefix <active>;
}
Hierarchy Level
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name], [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name ingress], [edit protocols mpls label-switched-path lsp-name], [edit protocols mpls static-label-switched-path lsp-name ingress] [edit protocols source-packet-routing source-routing-path lsp-name]
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.
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
toaddress. 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:
[edit protocols source-packet-routing]
segment-list path-1 {
hop-1 ip-address 172.0.12.2;
hop-2 label 1000012;
hop-3 label 1000013;
hop-4 label 1000014;
}
source-routing-path lsp1 {
to 10.10.10.1;
install 20.20.20.2;
install 30.30.30.3;
primary {
path-1;
}
}
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 Note:
The |
| destination-prefix | IPv4 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.
Release Information
Statement introduced before Junos OS Release 7.4.
Support at the [edit protocols source-packet-routing source-routing-path lsp-name] hierarchy level introduced in Junos OS
Release 19.1R1.