policy-multipath
Syntax
policy-multipath policy [ policy }
traceoptions <file filename <files files> <size size> <(world-readable | no-world-readable)>> name detail disable receive send
}
Hierarchy Level
[edit logical-systems name routing-instances name routing-options rib], [edit logical-systems name routing-options rib], [edit logical-systems name tenants name routing-instances name routing-options rib], [edit routing-instances name routing-options rib], [edit routing-options rib], [edit tenants name routing-instances name routing-options rib]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Create policy-based multipath route using a combination of segment routing traffic-engineered (SR-TE) LDP or RSVP routes and SR-TE IP routes. You can resolve BGP service routes over the mutlipath route, and apply export policies to steer traffic differently for different prefixes. The policy-based multipath feature is supported for both IP and IPv6 protocols.
Options
| policy |
Import policy to create policy-based multipath. Note:
This statement is supported only at the Any action commands configured in the policy, such as apply, is evaluated using the active route. For non-active routes, the policy is applied to check if the routes can participate in the multipath route or not. Multipath routes inherit all attributes of the active route. These attributes can be modified using the multipath policy configuration. |
| preserve-nexthop-hierarchy |
Enable expanded nh hierarchy support for policy-multipath routes for RIBs. For any inet[6].3 RIBs, the preserve-nexthop-hierarchy is enabled by default. Note:
This statement is supported only at the |
policy-multipath routes, Junos OS
assigns the preference value of the least-preferred (highest numerical) route among
the eligible routes instead of using the active route's preference. It ignores any
user-configured preference applied through policy for
policy-multipath routes and always applies the highest
preference value from the eligible route entries.Junos OS and Junos OS Evolved correctly reports metric 2 values for BGP routes
configured with policy-multipath. When the active prefix for
the route is SR‑TE and undergoing resolution, the system accurately reflects the
metric 2 value in the route metrics. This modification ensures that routing
decisions are based on accurate metrics, improving overall network performance
and reliability.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing
Release Information
Statement introduced in Junos OS Release 19.1R1.