close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

show services monitoring twamp client probe-results

date_range 18-Jan-24

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
show services monitoring twamp client probe-results
<control-connection control-connection-name>
<source-address>
<status (FAIL | PASS)>
<target>
<test-session test-session-name>

Description

Display the results of the most recent Two-Way Active Measurement Protocol (TWAMP) probes. By default, all probe results are displayed, unless you specify the control-connection option when you issue the command. The control-connection option is required when you want to issue the command with one of the other options. For example, to see the probe results for a particular test session, you must also include the control-connection option to specify which connection contains the test session: show services monitoring twamp client probe-results control-connection control-connection-name test-session test-session-name.

Options

control-connection `control-connection-name`	(Optional, but required if specifying one of other options as well) Display probe results for the specified control connection between a TWAMP client and a TWAMP server.
source-address `address`	(Optional) Display results only for those probes with the specified IPv4 source address associated with a particular control connection.
status (FAIL \| PASS)	(Optional) Display results only for those probes with the specified status associated with a particular control connection. Values: Specify one of the following: FAIL—Display results for failed probes. PASS—Display results for passed probes.
target `address`	(Optional) Display results only for those probes with the specified IPv4 target address associated with a particular control connection.
test-session `test-session-name`	(Optional) Display probe results for the specified test session associated with the control connection between a TWAMP client and a TWAMP server.

Required Privilege Level

view

Output Fields

Table 1 lists the output fields for the show services monitoring twamp client probe-results command. Output fields are listed in the approximate order in which they appear.

Table 1: show services monitoring twamp client probe-results Output Fields
Field Name	Field Description	Level of Output
`Owner`	Owner name. Entries are listed in alphabetical order by owner name and then by test name. When you configure the control-connection statement at the `[edit services monitoring twamp client]` hierarchy level, this field displays the configured control-connection name.	All levels
`Test`	Name of a test representing a collection of probes. When you configure the test-session test-name statement at the `[edit services monitoring twamp client control-connection]` hierarchy level, the field displays the configured test-session name.	All levels
`Target address`	Destination address used for the probes. This field is displayed when the probes are sent to the configured targets.	All levels
`Source address`	Source address used for the probes.	All levels
`Probe type`	Protocol configured on the receiving probe server: `twamp`	All levels
`Test size`	Number of probes within a test.	All levels
`Probe results`	Raw measurement of a particular probe sample done by a remote host. This data is provided separately from the calculated results. The following information is contained in the raw measurement: `Probe response received` `Probe sent time`—Timestamp when the probe’s results were sent. `Probe rcvd time`—Timestamp when the probe’s results were received. `Client and server offload timestamping`—If PFE timestamping is configured, an entry appears at this point. `Rtt`—Average ping round-trip time (RTT), in microseconds. `Rtt jitter`—Round-trip jitter, in microseconds. `Egress jitter`—Egress jitter, in microseconds. `Ingress jitter`—Ingress jitter, in microseconds.	All levels
`Results over current test`	Probes are grouped into tests, and the statistics are calculated for each test. If a test contains 10 probes, the average, minimum, and maximum results are calculated from the results of those 10 probes. If the command is issued while the test is in progress, the statistics use information from the completed probes. `Probes sent`—Number of probes sent within the current test. `Probes received`—Number of probe responses received within the current test. `Egress loss inferred`—Computed unidirectional loss towards server (available only when `stateful-sequence` is enabled on the server) `Loss percentage`—Percentage of lost probes for the current test. `Measurement`—Measurement type: round-trip time, round-trip jitter, egress delay, egress jitter, ingress delay, or ingress jitter. For each measurement type, the following individual calculated results are provided: `Samples`—Number of probes. `Minimum`—Minimum RTT measured over the course of the current test. `Maximum`—Maximum RTT measured over the course of the current test. `Average`—Average RTT measured over the course of the current test. `Stddev`—Standard deviation, in microseconds.	All levels
`Results over last test`	Results for the most recently completed test. If the command is issued while the first test is in progress, this information is not displayed. `Probes sent`—Number of probes sent for the most recently completed test. `Probes received`—Number of probe responses received for the most recently completed test. `Egress loss inferred`—Computed unidirectional loss towards server (available only when `stateful-sequence` is enabled on the server) `Loss percentage`—Percentage of lost probes for the most recently completed test. `Measurement`—Measurement type: round-trip time, round-trip jitter, egress delay, egress jitter, ingress delay, or ingress jitter. For each measurement type, the following individual calculated results are provided: `Samples`—Number of probes. `Minimum`—Minimum RTT measured for the most recently completed test. `Maximum`—Maximum RTT measured for the most recently completed test. `Average`—Average RTT measured for the most recently completed test. `Stddev`—Standard deviation, in microseconds.	All levels
`Results over all tests`	Displays statistics made for all the probes, independently of the grouping into tests, as well as statistics for the current test. `Probes sent`—Number of probes sent in all tests. `Probes received`—Number of probe responses received in all tests. `Egress loss inferred`—Computed unidirectional loss towards server (available only when `stateful-sequence` is enabled on the server) `Loss percentage`—Percentage of lost probes in all tests. `Measurement`—Measurement type: round-trip time, round-trip jitter, egress delay, egress jitter, ingress delay, or ingress jitter. For each measurement type, the following individual calculated results are provided: `Samples`—Number of probes. `Minimum`—Minimum RTT measured over the course of the current test. `Maximum`—Maximum RTT measured over the course of the current test. `Average`—Average RTT measured over the course of the current test. `Stddev`—Standard deviation, in microseconds.	All levels

Sample Output

show services monitoring twamp probe-results (Junos OS Evolved Release 23.4R1 and later)
show services monitoring twamp client probe-results
show services monitoring twamp client probe-results control-connection test-session

show services monitoring twamp probe-results (Junos OS Evolved Release 23.4R1 and later)

content_copy zoom_out_map
user@host> show services monitoring twamp probe-results
Owner: light-remote-dflt-v64, Test: dflt-3-v4 Target address: 10.61.1.1, Source address: 10.61.1.2, Probe type: twamp, Test size: 100
  Probe results:
    Probe response received
    Probe sent time: 01/17/24 02:19:55.774425
    Probe rcvd time: 01/17/24 02:19:55.800658, Client and server offload timestamping
    Rtt: 14806 usec, Rtt jitter: 413 usec
    Egress jitter: 56 usec, Ingress jitter: 357 usec
  Results over current test:
    Probes sent: 41, Probes received: 19, Egress loss inferred: 22, Loss percentage: 53.66
    Measurement: Round trip time (usec)
      Samples: 19, Minimum: 12356, Maximum: 17668, Average: 14818, Stddev: 1136
    Measurement: Round trip jitter (usec)
      Samples: 18, Minimum: 251, Maximum: 5312, Average: 1612, Stddev: 1261
    Measurement: Egress delay (usec)
      Samples: 19, Minimum: 6333, Maximum: 10255, Average: 8279, Stddev: 854
    Measurement: Egress jitter (usec)
      Samples: 18, Minimum: 56, Maximum: 3922, Average: 1087, Stddev: 889
    Measurement: Ingress delay (usec)
      Samples: 19, Minimum: 5934, Maximum: 7413, Average: 6538, Stddev: 434
    Measurement: Ingress jitter (usec)
      Samples: 18, Minimum: 70, Maximum: 1390, Average: 603, Stddev: 411
  Results over last test:
    Probes sent: 100, Probes received: 100, Loss percentage: 0.00
    Measurement: Round trip time (usec)
      Samples: 100, Minimum: 12993, Maximum: 22654, Average: 15905, Stddev: 1860
    Measurement: Round trip jitter (usec)
      Samples: 99, Minimum: 6, Maximum: 8249, Average: 1840, Stddev: 1807
    Measurement: Egress delay (usec)
      Samples: 100, Minimum: 6584, Maximum: 15577, Average: 9123, Stddev: 1486
    Measurement: Egress jitter (usec)
      Samples: 99, Minimum: 4, Maximum: 7587, Average: 1475, Stddev: 1586
    Measurement: Ingress delay (usec)
      Samples: 100, Minimum: 5722, Maximum: 12514, Average: 6782, Stddev: 964
    Measurement: Ingress jitter (usec)
      Samples: 99, Minimum: 0, Maximum: 6321, Average: 773, Stddev: 1022
  Results over all tests:
    Probes sent: 141, Probes received: 119, Egress loss inferred: 22, Loss percentage: 15.60
    Measurement: Round trip time (usec)
      Samples: 119, Minimum: 12356, Maximum: 22654, Average: 15732, Stddev: 1804
    Measurement: Round trip jitter (usec)
      Samples: 118, Minimum: 6, Maximum: 8249, Average: 1796, Stddev: 1732
    Measurement: Egress delay (usec)
      Samples: 119, Minimum: 6333, Maximum: 15577, Average: 8988, Stddev: 1439
    Measurement: Egress jitter (usec)
      Samples: 118, Minimum: 4, Maximum: 7587, Average: 1406, Stddev: 1504
    Measurement: Ingress delay (usec)
      Samples: 119, Minimum: 5722, Maximum: 12514, Average: 6743, Stddev: 906
    Measurement: Ingress jitter (usec)
      Samples: 118, Minimum: 0, Maximum: 6321, Average: 744, Stddev: 952