resolution
Syntax
resolution {
(preserve-nexthop-hierarchy | no-preserve-nexthop-hierarchy);
rib routing-table-name {
import [ policy-names ];
inet-import [ policy-names ];
inet-resolution-ribs [ routing-table-names ];
inet6-import [ policy-names ];
inet6-resolution-ribs [ routing-table-names ];
iso-import [ policy-names ];
iso-resolution-ribs [ routing-table-names ];
mpls-import [ policy-names ];
resolution-family resolution-family;
resolution-ribs [ routing-table-names ];
}
}
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options]
Description
Configure the router to perform custom route resolution on protocol next hops of routes in a certain routing table. The protocol next hop is used to determine the forwarding next hop.
For example, you might want to direct inet.2 route resolution to use topology routing tables :red.inet.0 and :blue.inet.0 for protocol next-hop IP address lookups. Or you might want to direct bgp.l3vpn.0 to use the information in inet.0 to resolve routes, thus overriding the default behavior, which is to use inet.3.
You can specify up to two routing tables in the resolution-ribs statement. The route resolution scheme first checks the first-listed
routing table for the protocol next-hop address. If the address is
found, it uses this entry. If it is not found, the resolution scheme
checks the second-listed routing table. Hence, only one routing table
is used for each protocol next-hop address. For example, if you configure resolution rib bgp.l3vpn.0 resolution-ribs [inet.0 inet.3],
inet.0 is checked first and then inet.3 is checked.
Customizing route resolution might cause the routing protocol
process (rpd) to consume more memory resources than it ordinarily
would. When you customize route resolution, we recommend that you
check the memory resources by running the show system processes and the show task memory commands. For more information,
see Routing Protocol Process Overview
for EX Series Switches.
The remaining statements are explained separately. See CLI Explorer.
Options
| disable-auto-resolve-on-scheme-changes | (Optional) Service routes are not re-resolved automatically when resolution schemes are created, deleted, or changed. However, you can manually trigger route re-resolution on resolution scheme changes. |
| inet-import [ policy-names ] |
(Optional) Import policy for IPv4 family resolution tree. |
| inet-resolution-ribs [ routing-table-names | (Optional) Specify routing tables to use for IPv4 family protocol-next-hop resolution. |
| inet6-import [ policy-names ] | (Optional) Import policy for IPv6 family resolution tree. |
| inet6-resolution-ribs [ routing-table-names ] | (Optional) Specify routing tables to use for IPv6 family protocol-next-hop resolution. Enabling the |
| iso-import [ policy-names ] | (Optional) Import policy for ISO family resolution tree. |
| iso-resolution-ribs [ routing-table-names ] | (Optional) Specify routing tables to use for ISO family protocol-next-hop resolution. |
| resolution-family resolution-family | (Optional) Specify a family of resolution tree. |
| preserve-nexthop-hierarchy | Preserve nexthop hierarchy when installing nexthop to forwarding plane. |
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.
inet6-import and inet6-resolution-ribs options added in Junos OS Release 17.2R1.