Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


control-connection (Junos OS Evolved)


Hierarchy Level


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.



Name of the control client.

control-type (managed | light)

Specify how you want to manage the control connection.

  • Values: Configure one of the following:

    • managed—Specify that you want to have a stateful version of TWAMP where test parameters are negotiated. You can specify particular source or target addresses, or non-default destination ports for the control connections. The ports are negotiated and agreed upon between the client and server. All test packets received by the server on a destination port are reflected back and forgotten right away.

    • light—Specify that you want a stateless version of TWAMP where test parameters are predefined instead of negotiated. All test packets received by the server on a destination port are reflected back and forgotten right away.

  • Default: managed

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 managed to set the destination port for the entire control connection. Otherwise, if the control-type option is set to light, you will have to configure the destination-port option on each test session.

  • Range: You can specify port 862, or any port from 49152 through 65535.

  • Default: 862 (IANA port for TWAMP)

routing-instance instance-name

Specify the routing instance used by the probes. This routing instance is configured at the [edit routing-instance] hierarchy level.


The media interface from where the TWAMP control and test or data packets arrive and exit must be part of the same routing instance.

  • Default: No routing instance is used. The Internet (IPv4) routing table inet.0 is used instead.

source-address address

Specify the IPv4 source address used for control connections. If the IPv4 source address is not one of the device’s assigned addresses, the control connection uses the outgoing interface’s IPv4 address as its source.

The following addresses cannot be used for the source address for control connections:


  • (loopback)

  • (multicast)

  • (broadcast)

target target-address

Specify the IPv4 address for the target destination for the control connection.


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.

  • Values: Configure one of the following:

    • auto—Start test sessions as soon as you commit the configuration.

    • manual—Wait to start test sessions until you issue the request services monitoring twamp client start operational mode command.

  • Default: auto

test-interval seconds

Specify the time to wait between tests.

  • Range: 1 through 86400 seconds

  • Default: 1

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 20.3R1.