Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Two-Way Active Measurement Protocol (TWAMP)

SUMMARY The Cloud-Native Router supports Two-Way Active Management Protocol (TWAMP) for network performance measurement and monitoring in 5G transport networks. It supports managed and light TWAMP.

The Two-Way Active Management Protocol (TWAMP), described in RFC 5357, is a network performance measurement and monitoring service used for active performance monitoring of 5G transport networks. TWAMP is an extension of the One-Way Active Management Protocol (OWAMP) providing two-way or round-trip measurements instead of unidirectional capabilities. Two-way measurements do not require local and remote clock synchronization. The remote host support can be limited to a simple echo function. TWAMP defines an open protocol for measuring two-way or round-trip metrics with greater accuracy than other methods by using time-stamps, while accounting for processing delays. Please review Understanding Two-Way Active Measurement Protocol topic for more details.

JCNR supports two flavors of TWAMP implementation:

  • Managed TWAMP—A TCP control connection is established between control client and responder server for exchanging test session information. Measurement and monitoring tests run between session-sender and session-reflector.
  • Light TWAMP—No control connection is established between the control client and responder server. The session-sender directly runs measurement and monitoring tests with the session-reflector. The session-reflector has no knowledge of the session state.

Please note the following JCNR behavior for timestamping the TWAMP test packets:

  • Timestamp for the test packet sent by the TWAMP session-sender is set by the application
  • Timestamp for the test packet received by the TWAMP session-reflector is set by the kernel

  • Timestamp for the test packet reflected by the TWAMP session-reflector is set by the application
  • Timestamp for the reflected packet received by the TWAMP session-sender is set by the kernel

Configuration

You can configure the TWAMP server and client with minimum configuration. There are additional configuration parameters with default values which may be modified as per your requirement. Please review edit services rpm twamp command for more information on each configuration option. The default values for the options is provided in the below tables:

Table 1: TWAMP Client Default Values

Option

Default value

control-type (light | managed)

managed

destination-port (862 - 65535)

862

history-size (0 - 512)

50

moving-average-size (0 - 512)

0

persistent-results (enable | disable)

disable

target-address

An IPv4 address. This field is mandatory for managed control-type. The configuration commit fails if configured for light control-type.

tcp-keepcnt (1 - 50)

6

tcp-keepidle (1 - 600 seconds)

120

tcp-keepintvl (1 - 600 seconds)

5

test-count (0 - 4294967290)

0

test-interval (1 - 255)

1

test-session (name)

Mandatory

data-size (60 - 1400)

60

destination-port (862 - 65535)

862

dscp-code-points

000000

probe-count (1 - 4294967290) 1

probe-interval (1 - 255)

1

Table 2: TWAMP Server Default Values

Options

Values

port (862 - 65535) [light]

862

max-connection-duration (0 - 120 hours)

24

maximum-connections (0 - 1000)

64

maximum-connections-per-client (1 - 500)

64

maximum-sessions (1 - 2048)

64

maximum-sessions-per-connection (1 - 1024)

64

port (1 - 65535) [server]

862

port (1 - 65535) [routing-instance-list]

862

server-inactivity-timeout (0 - 30 minutes)

15

tcp-keepcnt (1 - 50)

6

tcp-keepidle (1 - 600 seconds)

120

tcp-keepintvl (1 - 600 seconds)

5

Sample TWAMP client and server configurations for managed or TWAMP light are provided below. Use the configlet resource to configure cRPD:

TWAMP Client/Server Configuration (Managed, Minimum Configuration)

Client Configuration

Server Configuration

TWAMP Client/Server Configuration (Managed, Optional Configuration)

Client Configuration

Server Configuration

TWAMP Client/Server Configuration (Light, Minimum Configuration)

Client Configuration

Server Configuration

TWAMP Client/Server Configuration (Light, Optional Configuration)

Client Configuration

Server Configuration

Note:

By default the client control connection test-count is set to zero. In this case the TWAMP test automatically starts after the configuration is committed and continues to run until the configuration is deleted. If test-count is configured to a non-zero value, the TWAMP test must be started or stopped using below commands:

Verification

You can use the show services rpm twamp client probe-results command to verify the TWAMP probe results on cRPD shell:

Additional show commands include: