Supported Platforms
Related Documentation
- ACX, M, MX, T Series
- Example: Configuring Static Route Preferences and Qualified Next Hops
- ACX, J, M, MX, QFX, SRX, T Series
- Example: Enabling BFD on Qualified Next Hops in Static Routes
qualified-next-hop (Static Routes)
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Description
Configure a static route with multiple possible next hops, each of which can have its own preference value, IGP metric that is used when the route is exported into an IGP, and Bidirectional Forwarding Detection (BFD) settings. If multiple links are operational, the one with the most preferred next hop is used. The most preferred next hop is the one with the lowest preference value.
Options
address—IPv4, IPv6, or ISO network address of the next hop.
interface-name—Name of the interface on which to configure an independent metric or preference for a static route. To configure an unnumbered interface as the next-hop interface for a static route, specify qualified-next-hop interface-name, where interface-name is the name of the IPv4 or IPv6 unnumbered interface.
![]() | Note: For an Ethernet interface to be configured as the qualified next hop for a static route, it must be an unnumbered interface. To configure an Ethernet interface as an unnumbered interface, configure the unnumbered-address <interface-name> statement at the [edit interfaces <interface-name> unit <logical-unit-number> family <family-name>] hierarchy level as described in Configuring an Unnumbered Interface. |
The remaining statements are explained separately.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, MX, T Series
- Example: Configuring Static Route Preferences and Qualified Next Hops
- ACX, J, M, MX, QFX, SRX, T Series
- Example: Enabling BFD on Qualified Next Hops in Static Routes
Published: 2013-01-17
Supported Platforms
Related Documentation
- ACX, M, MX, T Series
- Example: Configuring Static Route Preferences and Qualified Next Hops
- ACX, J, M, MX, QFX, SRX, T Series
- Example: Enabling BFD on Qualified Next Hops in Static Routes