qualified-next-hop (Static Routes)
Syntax
qualified-next-hop (address | interface-name) {
bfd-liveness-detection {
authentication {
algorithm (keyed-md5 | keyed-sha-1 | meticulous-keyed-md5 | meticulous-keyed-sha-1 | simple-password);
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
holddown-interval milliseconds;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}
interface interface-name;
metric metric;
preference preference;
}
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static route destination-prefix], [edit logical-systems logical-system-name routing-options rib inet6.0 static route destination-prefix], [edit logical-systems logical-system-name routing-options static route destination-prefix], [edit routing-instances routing-instance-name routing-options static route destination-prefix], [edit routing-options rib inet6.0 static route destination-prefix], [edit routing-options static route destination-prefix]
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.
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. See CLI Explorer.
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.