sla-rule
Syntax
sla-rule sla-rule-name {
active-probe-params {
probe-params-name;
}
link-preferences {
preferred-tag preferred-tag;
affinity strict;
}
metrics-profile {
metric-profile-name;
}
passive-probe-params {
sampling-percentage {
percentage;
}
sampling-period {
period;
}
type {
book-ended;
}
switch-idle-time {
period;
}
type {
saas;
}
violation-count {
count;
}
}
Syntax (Prior Junos OS Release 21.2R1)
sla-rule sla-rule-name {
active-probe-params {
probe-params-name;
}
link-type-affinity strict;
metrics-profile {
metric-profile-name;
}
passive-probe-params {
sampling-percentage {
percentage;
}
sampling-period {
period;
}
type {
book-ended;
}
preferred-link-type (Any | IP | MPLS);
sla-export-factor {
value;
}
switch-idle-time {
period;
}
type {
saas;
}
violation-count {
count;
}
}
Hierarchy Level
[edit security advance-policy-based-routing]
Description
Configure an SLA rule.
An SLA rule includes all information required to measure the SLA and to identify whether any SLA violation has occurred or not. It contains the complete probe profiles, time interval which the profiles need to be sent, preferred SLA configuration, and so on.
When you configure an APBR rule, you must associate the corresponding SLA rule for the application.
The presence of SLA rule in the APBR configuration triggers the AppQoE functionality; If there are no SLA profiles available, APBR operates without AppQoE.
Options
| active-probe-params probe-params-name |
Name of the active probe parameter. Associate the active probe parameter with the SLA rule. |
| affinity |
Define link type affinity. For strict affinity, AppQoE ensures that the selected path is always from the preferred tag. For the default affinity (loose), if there is no SLA meeting link in the preferred tag, AppQoE selects a link outside the preferred tag that meets the SLA requirements.
|
||||||||||||||||||||||||||||
| link-type-affinity (strict) |
(optional) Configure the link-type affinity as strict for the preferred link type. For strict affinity, AppQoE ensures that the path selected is always of the preferred link type. When the default affinity (loose) is configured and if there are no SLA meeting links belonging to the preferred link type available, then AppQoE selects a link outside the preferred link type that meets the SLA requirements. Following table provides details on AppQoE pat selection mechanism based on affinity type.
Prior to Junos OS Release 21.2R1, during traffic flow, switching from a link with a lower priority value that meets the SLA requirements to a link with a higher priority is not supported when the link with higher priority meets the SLA requirements. When a currently selected link and the highest priority link are part of a indirect next-hop table (belonging to a different routing instance), the application traffic does not switch to the highest priority link. It switches to the highest priority link only when the SLA manager is triggered. The SLA manager is triggered for the following reasons:
|
||||||||||||||||||||||||||||
| metrics-profile profile-name |
Metric profile name. The SLA rule contains metric profiles that provide the acceptable threshold. If the violation goes beyond the threshold, an alternate path is identified and then traffic is rerouted. |
| passive-probe-params |
Passive probe parameter name. Passive probes are installed on links within the network, and they monitor all the traffic that flows through those links.. This option is not supported for SaaS applications. |
| preferred-link-type (IP | MPLS | Any) |
Select an MPLS or Internet link as the preferred path. If you do not
select
|
| preferred-tag |
Define a custom tag such as ISP1, ISP2, WAN1, IP, MPLS, and so on as per
the requirement. The security device does not support the preferred tag
as The preferred tag is case sensitive. For example, the security device
considers the prefered tag
Custom Link Tag SLA link preference for security device interfaces support custom
link tags. If there are multiple links that meet SLA, you can set
link preference by configuring the Application Traffic Switch to the Higher Priority Link of the Preferred Tags During the traffic flow, AppQoE allows the application traffic to switch from a lower priority link to a higher priority link that meets SLA requirements. Non-SLA metrics Based Deployments We support AppQoE for application-based traffic or non-application based traffic even when the SLA metrics are not available. Overlay Interface Attribute Preference In case of conflicting attributes within an overlay or between an
overlay and corresponding underlay interfaces, the highest level
overlay link attributes take precedence. Link attribute
|
| sla-export-factor value |
Set interval to report passive probe report metrics at the application level. Example: When you configure the With application-level summarization, each probe candidate session must send data to central location where the metrics are aggregated. The data thus aggregated is sent out once the configured SLA export factor is met.
|
| switch-idle-time period |
Path switch idle time in seconds. This is the period during which no subsequent switching of application traffic path occurs until the switch idle time expires. This idle time starts when application traffic switches the path.
|
| type |
Define SLA rule type.
|
| violation-count number |
Indicates the number of violations that must occur in a sampling-period for a given session before a link is marked as having violated the SLA.
|
Required Privilege Level
services—To view this statement in the configuration.
services-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 18.2R1.
The options preferred-link-type and
link-type-affinity are introduced in Junos OS Release
18.4R1.
The options sla-export-factor and violation-count
are moved to [edit security advance-policy-based-routing sla-rule] hierarchy in
Junos OS Release 19.2R1.
The options preferred-tag and affinity are
introduced in Junos OS Release 21.2R1.