resolution
Syntax
resolution {
allow-expanded-over-compressed;
disable-auto-resolve-on-scheme-changes;
no-allow-expanded-over-compressed;
no-policy-metric-for-non-recursive-routes;
no-prefer-recursive-primary-path;
no-preserve-nexthop-hierarchy;
prefer-recursive-primary-path;
preserve-nexthop-hierarchy;
rib;
scheme;
tracefilter tracefilter;
traceoptions {
file filename <files files> <no-stamp> <no-world-readable> <replace> <size size> <world-readable>;
flag < name> <detail> <disable> <receive> <send>;
}
}
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
| allow-expanded-over-compressed |
Allow resolution of expanded hierarchy over compressed |
| disable-auto-resolve-on-scheme-changes | (Optional) Disable automatic re-evaluation of existing service routes when
there is an addition, deletion or change in the resolution schemes. Service
routes include BGP service routes such as IPv4 and IPv6 unicast (internet)
routes, L3VPN and L2VPN routes , VPLS routes , EVPN routes, Flowspec routes
and more. Note: When this option is configured, you
must manually trigger route re-resolution for resolution scheme changes
using the
clear bgp neighbor soft-reconfig
command. |
| no-allow-expanded-over-compressed |
Don't allow resolution of expanded hierarchy over compressed |
| no-policy-metric-for-non-recursive-routes |
Disable metric manipulation via policy for non-recursive routes |
| no-prefer-recursive-primary-path |
Don't prefer primary path to resolve nexthop during recursive-resolution |
| no-preserve-nexthop-hierarchy |
Don't preserve nexthop hierarchy when installing nexthop to forwarding plane |
| prefer-recursive-primary-path |
Prefer primary path to resolve nexthop during recursive-resolution |
| preserve-nexthop-hierarchy |
Preserve nexthop hierarchy when installing nexthop to forwarding plane Note: amruthav: PR1697176
Enable the
|
| tracefilter |
Filter policy |
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.