Application Note 316

SLA Monitoring Using the Two-Way Active

Measurement Protocol (TWAMP)
By Thierno Diallo, Product Manager, EXFO Service Assurance

As Internet protocol (IP) becomes the transport layer of choice, EXFO’s implementation of TWAMP supports the testing of both
operators are faced with significant challenges to provide accurate sender and responder capabilities, enabling full flexibility. Users can
and relevant measurement of IP network performance. Tools are perform tests from EXFO probes to vendors’ devices or provide a
available such as ICMP Ping/TraceRoute and UDP Echo, but these high-performance responder for troubleshooting purposes.
provide limited value in the context of performance as they typically
lack precision, accuracy or relevancy for assuring carrier-grade
performance. Other tools exist that leverage the TCP/IP suite but TWAMP Test Modes
lack the broad acceptance of the network equipment manufacturer TWAMP process is defined in two different modes, the Light mode
community that is required for seamless operation in cross-network/ and the Full mode.
multi-vendor environments.
TWAMP Full Mode
In that context, the Internet Engineering Task Force (IETF)’s working
The TWAMP Full mode test is designed to work in a client-server
group on IP Performance and Metrics developed RFC-5357, the
relationship, where the control of the test may be managed by
Two-Way Active Measurement Protocol (TWAMP). The TWAMP
separate devices from the devices that will be sending and receiving
protocol is a standards-based and effective performance monitoring
the test traffic. There are two protocols linking the devices in question:
process that expands upon the One-Way Active Measurement
TWAMP-Control and TWAMP-Test. Test sessions are initiated,
Protocol (OWAMP) specification defined in RFC-4656 with the
started and stopped using TWAMP-Control and test packets are
addition of the performance measurement of round-trip and two-way
exchanged between TWAMP nodes through TWAMP-Test. As
metrics for IP based networks. TWAMP delivers a flexible method
shown in figure 1, the test is initiated by a controller requesting a
for accurately measuring unidirectional and round-trip performance
test run to a server, which then initiates the appropriate processes
between two TWAMP-supported endpoints, regardless of device
to reflect traffic from the sender. Once the session is approved, the
type or vendor.
sender starts the test under the control of the client.
This application note will explain the fundamental architecture of
TWAMP, define TWAMP terminologies and how EXFO Service TWAMP-Test
Session- Session-
Assurance solutions use the TWAMP protocol in its test solutions. Sender Reflector

THE FUNDAMENTALS OF TWAMP

The TWAMP protocol includes several key components discussed TWAMP-Control
below: test endpoints; two inter-related protocols, namely TWAMP- Control-Client Server
control and TWAMP-test; and Modes (Light or Full).
Figure 1. TWAMP Full mode test example #1
TWAMP Test Endpoints, TWAMP-Control and TWAMP-Test
TWAMP architecture is built around two hosts or endpoints each
Modules defined in figure 1 above, may be co-hosted by others, as
with specific roles thus simplifying the measurement process.
shown in figure 2. The combination of the session-sender and the
TWAMP endpoints can be categorized as either the session-
control-client in this example become the controller. The session-
sender or the session-reflector/responder nodes.
reflector and server modules together become the responder. This
The session-sender node is responsible for generating test traffic eliminates the need for dedicated channels for each module. The
and processing the returned traffic in order to measure performance. establishment of test and control channels still remains intact.
It is also the master of the measurement process and controls all
aspects of the test. The reflector node processes and returns test
traffic received from the sender node. Besides looping back the Controller TWAMP-Test Responder
traffic, the reflector (sometimes known as responder) also inserts Session-Sender Session-Reflector
and processes timestamps and sequence numbers in the response Control-Client Server
packet for more accurate one-way measurement of performance.
TWAMP-Control
In terms of deployment, while there can be a multitude of TWAMP
nodes, an exchange is always defined as being between two nodes Figure 2. TWAMP Full mode test example #2
at all times, where one is the session-sender and the other the
receiver. Some vendors refer to their implementation as a “TWAMP
Server” in order to enforce the fact that their particular TWAMP
node is not able to generate TWAMP traffic but only to respond to it.

TWAMP Light Mode
TWAMP Light mode is designed to help implement the TWAMP
standard across entities that act as active responders to TWAMP
controllers within the network, thereby enabling the measurement of
two-way IP performance from anywhere within that network.
In TWAMP-Light, the TWAMP-control protocol is eliminated and the
session-sender, control-client and server are combined into one host:
the controller. The function of the session-reflector is executed by a
separate host: the responder.
The responder, or in this case the session-reflector alone, simply
sends incoming packets back to the controller. Simultaneously the
responder copies required information and generates sequence
numbers and timestamp values without knowledge of the state of
the session. This is the simplest form of deploying TWAMP with a
session-reflector.
Controller Responder
Session-Sender TWAMP-Test
Control-Client Session-Reflector
Server
Figure 3. TWAMP Light-mode test configuration
TWAMP Exchange: Full Mode and Light Mode Differences
The TWAMP Exchange is the test process that is performed between
endpoints. This process is similar for both TWAMP Full and Light
modes. The key and important difference is that during a Full-mode
TWAMP session, the session is established between the sender
and responder through a control channel within a control session
that negotiates communication between devices. In a Light-mode
TWAMP scenario, no negotiation occurs between the endpoint and
the client.
TWAMP Full Mode:
IP Endpoint
TWAMP Control Session
TWAMP Client
TWAMP
Server
Packet Loopback
› The TWAMP session is established by the client via the control
channel within the control session. Parameters such as UDP
ports are negotiated between the sender and the responder.
› Once negotiation is complete, the client transmits test packets
to the server
› The server loops back packets to the client with embedded
timing and sequence information
› Client computes two-way IP KPI’s (loss, latency, jitter,
duplicates, out of order). Synchronized clients may also compute
one-way KPI’s (latency and jitter)
Application Note 316
TWAMP Light Mode:
IP Endpoint
TWAMP Client
TWAMP
Server
Packet Loopback
› Client transmits test packet to the server without any negotiation
› Server loops back packets to client with embedded timing and
sequence information
› Client computes two-way IP KPI’s (loss, latency, jitter,
duplicates, out of order). Synchronized clients also may compute
one-way KPI’s (latency and jitter)
EXFO SERVICE ASSURANCE SOLUTIONS FOR TWAMP
As thought leaders in L3 monitoring, EXFO was one of the first
telecom test and service assurance solution providers to implement
the TWAMP protocol as part of its service assurance offerings. Below
are several ways EXFO solutions leverage TWAMP throughout the
testing process.
TWAMP Sender Tests
The EXFO Service Assurance approach to TWAMP enables testing
of both periodic and continuous sender traffic.
Periodic TWAMP Sender Tests
The periodic test mode is defined as a test that is started and
stopped at varying intervals within a user-defined test period, as seen
in figure 4. This enables the test management engine to randomly
start a test within a test period enabling a long-term measurement of
performance without patterns of test start. Periodic TWAMP enables
a higher scalability of tests as multiple tests can be performed
simultaneously while consuming less aggregate bandwidth as traffic
is spread across measurement periods.
A periodic TWAMP sender test enables a probe to perform TWAMP
measurement against another probe or any TWAMP compatible
responder according to the test mode selected. The test supports
one-way and roundtrip IP performance and reports on key metrics
such as:
› One-way and round-trip delay and delay variation
› Per-direction packet statistics (sent, lost, duplicate and out-of-order)
› Total and internal delay measurements
Test Reporting
Packets Period
Figure 4: Periodic TWAMP testing
© 2015 EXFO Inc. All rights reserved.
 Application Note 316

Continuous TWAMP Sender Tests Deployment Scenarios

The continuous TWAMP test is an extension of the periodic TWAMP
test where the test is run in a continuous mode. In continuous mode,
as depicted in figure 5, the TWAMP test continuously and evenly
injects test traffic into the test channel at user-defined intervals. This
enables a more granular and uniform measurement of performance
as all measurement seconds will be filled with a steady stream of
test packets.
This test supports TWAMP Full mode and Light mode and can be
used with IPv4 and IPv6 addresses/reflectors. Additionally, different
test packet parameters can be configured such as test packet
lengths, period and Ethernet/IP priority fields.
Test Reporting
Packets Period
The flexibility of the TWAMP test enables EXFO’s Service Assurance
solutions to reach out to other areas of the network or into partner
networks and test to TWAMP compliant devices or even other
probes not under the control of the local EXFO solution.
Within a provider network, as seen in figure 6, the TWAMP Light-
mode sender is easy to deploy and manage between devices. When
necessary, the TWAMP Full-mode protocol can be used to reach
out to third parties where a device only supports the TWAMP Full-
mode protocol.
Complete TWAMP Activation and SLA testing
The EXFO Service Assurance solution provides a complete solution
for service delivery and service level agreement (SLA) management
through its extended TWAMP capabilities:

1. In activation, use TWAMP encapsulation to perform full Y.1564

to a compatible endpoint, enabling complete service activation
while eliminating the need for a service truck roll.

Figure 5. Continuous TWAMP testing 2. In SLA management, use the flexibility of TWAMP Light and Full
modes to perform SLA testing to any endpoint
TWAMP Reflector Test 3. In troubleshooting, use TWAMP encapsulation and RFC-2544
The TWAMP reflector test acts as a service that listens for data to measure available resources while again eliminating the
from TWAMP sender traffic. This test simply enables a responder associated service truck roll.
on a probe to be used against a sender. As with the sender test, the
reflector test supports Light and Full modes and IPv4/v6. As a high TWAMP Enabled
performance application, the reflector test can process a high rate
of packets or support multiple senders simultaneously.
ode
ll M
Partner Probe
P Fu
M
TWAMP-Encapsulated Activation Tests TWA
ORK
An additional enhancement to TWAMP is the ability to use ET W
Probe ode NER
N
TWAMP packets in turn-up tests. Turn-up tests are typically used ht M T
Lig PAR
MP
before commissioning of the service to measure compliance and TWA
configuration of circuits. Turn-up tests typically consist of high-
throughput layer-2/3 tests and two typical turn-up tests are the Probe e
Mod
RFC-2544 Benchmarking Test and Y.1564 Service Activation ght
A M P Li
Methodology test. TW
de
The TWAMP-encapsulated activation test is typically used for l Mo
TWAMP Enabled
P Ful
service activation scenarios or troubleshooting scenarios where M
TWA
the objective is to measure the maximum capabilities of a service
or a circuit by leveraging RFC-2544 and Y.1564 tests. The benefit
of using this test is to leverage far-end responder capabilities thus Figure 6. Deployment scenario
entirely eliminating the need for a service truck roll.

Reference: Internet Engineering Task Force (IETF), Request for Comments—RFC 5357: A Two-Way Active Measurement Protocol (TWAMP), October 2008

EXFO Headquarters > Tel.: +1 418 683-0211 | Toll-free: +1 800 663-3936 (USA and Canada) | Fax: +1 418 683-2170 | info@EXFO.com | www.EXFO.com

EXFO serves over 2000 customers in more than 100 countries. To find your local office contact details, please go to www.EXFO.com/contact.

2008
APNOTE316.1AN © 2015 EXFO Inc. All rights reserved. Printed in Canada 15/03