test-session (Junos OS Evolved)

Name of the test session.

Specify the size of the data portion of the test packet, in bytes.

• Range: 0 through 65400 bytes

• Default: 0

Specify the User Datagram Protocol (UDP) port number to which a probe is sent. You must have the control-type option for the control-connection statement set to light to be able to configure a destination port for a particular test session. If you set the control-type option to managed, the destination port is negotiated for you between the client and the server, and so you cannot configure the destination port for a particular test session.

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

• Default: 862 (IANA port for TWAMP)

Configure the value of the Differentiated Services (DiffServ) field within the IP header. The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern.

• Values: Configure a valid 6-bit pattern; for example, 001111, or one of the following DSCP aliases:

  • af11—Default: 001010

  • af12—Default: 001100

  • af13—Default: 001110

  • af21—Default: 010010

  • af22—Default: 010100

  • af23 —Default: 010110

  • af31 —Default: 011010

  • af32 —Default: 011100

  • af33 —Default: 011110

  • af41 —Default: 100010

  • af42 —Default:100100

  • af43 —Default:100110

  • be—Default: 000000

  • cs1—Default: 001000

  • cs2—Default: 010000

  • cs3—Default: 011000

  • cs4—Default: 100000

  • cs5—Default: 101000

  • cs6—Default: 110000

  • cs7—Default: 111000

  • ef—Default: 101110

  • nc1—Default: 110000

  • nc2—Default: 111000

Specify the number of stored history entries. The value configured for the history-size option must be equal to or larger than the value configured for the probe-count option, or the configuration will not commit.

• Range: 0 to 255

• Default: 50

Enable statistical calculations to be performed across a configurable number of the most recent samples.

• Range: 0 through 512

• Default: 0 (disable)

Enable timestamping of TWAMP probe messages in the Routing Engine, inline in the hardware, or Packet Forwarding Engine host processor. Prior to Junos OS Evolved 22.3R1, for IPv6 traffic, you must configure none, as only Routing Engine timestamping is supported. Starting in Junos OS Evolved 22.3R1, you can configure the pfe-timestamping option for IPv6 traffic.

• none—Timestamping in the Routing Engine.

• inline-timestamping—Timestamping inline, in the hardware at the generator, and reflection in the hardware at the reflector. When this option is configured for an ACX router, the ACX can act as either a server or client, but not both. Also for an ACX router, inline-timestamping is not supported on PM50 ports if FEC74 is enabled on that port. You can configure the inline-timestamping option for up to 256 test sessions.

• pfe-timestamping—Timestamping in the Packet Forwarding Engine.

• Default: pfe-timestamp

Specify the number of probes within a test. The value configured for the probe-count option must be smaller than the value configured for the history-size option, or the configuration will not commit.

• Range: 1 through 255

• Default: 1

Specify the number of seconds to wait before sending the next probe.

• Range: 1 through 255 seconds

• Default: 1

Specify the IPv4 or IPv6 source address used for test probes. If the source address is not one of the device’s assigned addresses, the probe 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 probes:

• 0.0.0.0

• 127.0.0.0/8 (loopback)

• 224.0.0.0/4 (multicast)

• 255.255.255.255 (broadcast)

When an IPv6 link-local address is configured with the target target-address local-link IPv6-link-local-interface-name option, you cannot configure the source-address address option. Instead, the operating system sets this option for you.

Specify the IPv4 or IPv6 address for the target destination of the probe. Prior to Junos OS Evolved 22.3R1, you cannot use an IPv6 link-local address for the target destination of a probe. Starting in Junos OS Evolved 22.3R1, for TWAMP Light test sessions with IPv6 target addresses (where the control-type light statement is configured for the control connection), configure the link-local logical interface name for the egress interface. You cannot configure IPv6 link-local addresses for TWAMP managed test sessions (where the control-type managed statement is configured for the control connection) .

Specify the maximum number of hops a TWAMP probe can travel. You configure the ttl option when necessary to restrict the scope of a probe, so that a probe does not unintentionally monitor an alternative path to the destination (such as may occur after a BGP re-routing). You can also use the ttl option to monitor direct reachability by specifying a TTL of 1. Probes that exceed the number configured are discarded.

• Range: 1 through 255 hops

• Default: 64 hops