control-connection (Junos OS Evolved)
Syntax
control-connection control-client-name {
control-type (managed | light);
destination-port destination-port;
routing-instance routing-instance-name;
source-address source-address;
target target-address;
test-start (auto | manual);
test-interval seconds;
traps {
control-connection-closed;
test-iteration-done;
}
test-session name {
data-size data-size;
destination-port destination-port;
dscp-code-points dscp-code-points;
history-size history-size;
moving-average-size moving-average-size;
offload-type (none | inline-timestamping | pfe-timestamp);
probe-count probe-count;
probe-interval seconds;
source-address source-address;
target target-address local-link IPv6-link-local-interface-name;
thresholds {
control-failure (on | off);
successive-loss number;
total-loss number;
threshold-type (microseconds | average);
}
traps {
egress-jitter-exceeded
egress-time-exceeded;
ingress-jitter-exceeded;
ingress-time-exceeded;
jitter-exceeded;
probe-failure;
rtt-exceeded;
test-completion;
test-failure;
}
ttl hop-count;
}
}
Hierarchy Level
[edit services monitoring twamp client]
Description
For Junos OS Evolved, configure all the Two-Way
Active Measurement Protocol (TWAMP) control clients that can connect
to the server. A TWAMP control connection is responsible for initiating,
starting, and ending the test sessions between a TWAMP client and
a TWAMP server for performance measurement. However, when the control-type
option is set to light, the test session parameters are
predefined and not negotiated, and no control session is created.
Therefore, with TWAMP light, UDP probe generation and reception, as
well as reflection, is not part of a control session.
Options
| control-client-name | Name of the control client. |
| control-type (managed | light) | Specify how you want to manage the control connection.
|
| destination-port port | Specify the Transmission Control Protocol (TCP) port
number for the endpoint of the control connection. You must set the
control-type option to
|
| routing-instance instance-name | Specify the routing instance used by the probes. This routing instance is configured at the [edit routing-instance] hierarchy level. Note:
The media interface from where the TWAMP control and test or data packets arrive and exit must be part of the same routing instance.
|
| source-address address |
Specify the IPv4 or IPv6 source address used for control connections. If the source address is not one of the device’s assigned addresses, the control connection uses the outgoing interface’s address as its source. You cannot use IPv6 link-local addresses or the following addresses as the source address for control connections:
|
| target target-address | Specify the IPv4 or IPv6 address for the target destination for the control connection. You cannot use IPv6 link-local addresses as the target destination for the control connection. Note:
You can configure this option only when the control-type option is set or defaulted to managed. The target option is required for a managed control connection. |
| test-start (auto | manual) | Specify whether or not you want to manually start TWAMP tests.
|
| test-interval seconds | Specify the time to wait between tests.
|
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Evolved Release 20.3R1.
traps option introduced in Junos OS Evolved Release 21.3R1.
IPv6 address support introduced in Junos OS Evolved Release 21.4R1.
The local-link sub-option of the target option for
TWAMP Light test sessions introduced in Junos OS Evolved Release 22.3R1.
The inline-timestamping suboption of the
offload-type option introduced in Junos OS Evolved 22.4R1.