sla-tracking
Syntax
sla-tracking {
route destination-prefix {
metric metric;
next-hop next-hop {;
rpm {
owner name;
test test-name;
}
twamp {
connection name;
test test-name;
}
}
preference preference;
tag tag;
}
}
Hierarchy Level
[edit routing-options]
Description
(Junos OS Evolved only) You configure this configuration statement when you
want to install static routes only if they meet the criteria of a given
service level agreement (SLA). You configure an RPM or TWAMP test instance
with the criteria for the SLA at either the [edit services
monitoring rpm] or the [edit services monitoring
twamp] hierarchy levels. You then configure this statement to
couple the SLA-tracked static route with the configured RPM or TWAMP test
instance. The system then installs or removes the static routes according to
the results of the given RPM or TWAMP test. When installed, these routes are
automatically given a preference of 1, and so are preferred over static
routes that may already exist with the same prefix. You use the command
show route sla-tracking to see the results of the
tests.
If the test result is “success,” then all SLA-tracked static routes that match the probe owner (RPM), connection name (TWAMP), and the test name of the successful test are added to the routing table and are considered to be in an active state. If the test result is “failure,” then all SLA-tracked static routes that match the probe owner (RPM), connection name (TWAMP), and test name of the failed test are placed into an inactive state.
Static route tracking supports both IPv4 and IPv6 routes. SLA-tracked static routes are configured individually; wildcards, ranges, and regular expressions are not supported.
Default
See individual options for any defaults.
Options
| metric metric |
(Optional) Set the route metric for the destination prefix. The route with the lowest metric is active in the routing table.
|
| next-hop next-hop |
(Required) Configure a next-hop address. Must be an IPv4 or IPv6 address. You can configure up to 16 multiple paths (next-hops) for any given SLA-tracked static route. |
| preference preference |
(Optional) Set the route preference value for the destination
prefix. The route with the lowest preference value is
active in the routing table. Qualified next hops are not
supported with SLA-tracked static routes. Hence, the
setting of the
|
| route destination-prefix |
(Required) Configure an SLA-tracked static route. Must be an IPv4 or IPv6 destination prefix. The maximum allowed number of SLA-tracked routes is 10000. |
| rpm owner name test test-name | Associate the path for an SLA-tracked static route with a
particular RPM owner and test. You must also configure an RPM
test owner and test name using the owner
statement at the [edit services monitoring rpm]
hierarchy level. |
| twamp connection name test test-name | Associate the path for an SLA-tracked static route with a
particular TWAMP connection and test. You must also configure a
TWAMP control connection and test session using the
control-connection statement at the
[edit services monitoring twamp client]
hierarchy level. |
| tag tag |
(Optional) Set the route tag value for the destination prefix. The route with the lowest tag value is active in the routing table.
|
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Support introduced in Junos OS Evolved Release 24.4R1.