Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

IP SLAs Configuration Guide, Cisco IOS XE Fuji 16.8.x (Cisco ASR 920 Series)

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

IP SLAs Configuration Guide, Cisco IOS XE Fuji 16.8.x (Cisco ASR 920 Series)

Chapter Title

IP SLAs TWAMP Responder

Results

Updated:
April 22, 2018

Chapter: IP SLAs TWAMP Responder

IP SLAs TWAMP Responder

This module describes how to configure an IETF Two-Way Active Measurement Protocol (TWAMP) responder on a Cisco device to measure IP performance between the Cisco device and a non-Cisco TWAMP control device on your network.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Prerequisites for IP SLAs TWAMP Responder

  • A TWAMP control-client and the session-sender must be configured in your network.

  • IP SLA responder must be configured on the device. Use the command ip sla responder twamp to configure IP SLA responder.

Restrictions for IP SLAs TWAMP Responder

  • For IP SLAs TWAMP Responder v1.0, the TWAMP server and the session-reflector must be configured on the same Cisco device.

Information About IP SLAs TWAMP Responder

TWAMP

The IETF Two-Way Active Measurement Protocol (TWAMP) defines a standard for measuring round-trip network performance between any two devices that support the TWAMP protocols. The TWAMP-Control protocol is used to set up performance measurement sessions. The TWAMP-Test protocol is used to send and receive performance-measurement probes.

The TWAMP architecture is composed of the following four logical entities that are responsible for starting a monitoring session and exchanging packets:

  • The control-client sets up, starts, and stops TWAMP-Test sessions.

  • The session-sender instantiates TWAMP-Test packets that are sent to the session-reflector.

  • The session-reflector reflects a measurement packet upon receiving a TWAMP-Test packet. The session reflector does not collect packet statistics in TWAMP.

  • The TWAMP server is an end system that manages one or more TWAMP sessions and is also capable of configuring per-session ports in the end points. The server listens on the TCP port. The session-refector and server make up the TWAMP responder in an IP SLAs operation.

Although TWAMP defines the different entities for flexibility, it also allows for logical merging of the roles on a single device for ease of implementation. The figure below shows the four entities that make up the TWAMP architecture.

Figure 1. TWAMP Architecture

IP SLAs TWAMP Responder v1.0

A TWAMP responder interoperates with the control-client and session-sender on another device that supports TWAMP. In the IP SLAs TWAMP Responder v1.0 feature, the session-reflector and TWAMP server that make up the responder must be co-located on the same device.

In the figure below, one device is the control-client and session-sender (TWAMP control device), and the other two devices are Cisco devices that are configured as IP SLAs TWAMP responders. Each IP SLAs TWAMP responder is both a TWAMP server and a session-reflector.

Figure 2. IP SLAs TWAMP Responders in a Basic TWAMP Deployment


Note

Cisco ASR 920 supports only hardware time stamping.

Two-Way Active Measurement Protocol

The Two-Way Active Measurement Protocol (TWAMP) defines a flexible method for measuring round-trip IP performance between any two devices.

Advantages of TWAMP

  • TWAMP enables complete IP performance measurement.

  • TWAMP provides a flexible choice of solutions as it supports all devices deployed in the network.

The TWAMP entities

The TWAMP system consists of 4 logical entities:

  • server - manages one or more TWAMP sessions and also configures per-session ports in the end-points.

  • session-reflector - reflects a measurement packet as soon as it receives a TWAMP test packet.

  • control-client - initiates the start and stop of TWAMP test sessions.

  • session-sender - instantiates the TWAMP test packets sent to the session reflector.

The TWAMP protocols

The TWAMP protocol includes three distinct message exchange categories, they are:

  • Connection set-up exchange: Messages establish a session connection between the Control-Client and the Server. First the identities of the communicating peers are established via a challenge response mechanism. The Server sends a randomly generated challenge, to which the Control-Client then sends a response by encrypting the challenge using a key derived from the shared secret. Once the identities are established, the next step negotiates a security mode that is binding for the subsequent TWAMP-Control commands as well as the TWAMP-Test stream packets.


    Note

    A server can accept connection requests from multiple control clients.

  • TWAMP-control exchange: The TWAMP-Control protocol runs over TCP and is used to instantiate and control measurement sessions. The sequence of commands is as follows, but unlike, the Connection setup exchanges, the TWAMP-Control commands can be sent multiple times. However, the messages cannot occur out of sequence although multiple request-session commands can be sent before a session-start command.

    • request-session

    • start-session

    • stop-session

  • TWAMP-test stream exchange: The TWAMP-Test runs over UDP and exchanges TWAMP-Test packets between Session-Sender and Session-Reflector. These packets include timestamp fields that contain the instant of packet egress and ingress. The packet also includes a Sequence Number.

TWAMP-Control and TWAMP-test stream support only unauthenticated security mode.

How to Configure an IP SLAs TWAMP Responder


Note
Time stamping for sender (T1, T4) and receiver (T3, T2) is performed by hardware, instead of software to improve the accuracy of jitter and latency measurements effective Cisco IOS-XE Everest 16.6.1.

Configuring the TWAMP Server


Note

For IP SLAs TWAMP Responder v1.0, the TWAMP server and the session-reflector are configured on the same device.

SUMMARY STEPS

    1.    enable

    2.    configure terminal

    3.    ip sla server twamp

    4.    port port-number

    5.    timer inactivity seconds

    6.    end


DETAILED STEPS
    Step 1   enable


    Example:
    Device> enable

    Enables privileged EXEC mode.

    • Enter your password if prompted.

    Step 2   configure terminal


    Example:
    Device# configure terminal

    Enters global configuration mode.

    Step 3   ip sla server twamp


    Example:
    Device(config)#  ip sla server twamp

    Configures the device as a TWAMP server and enters TWAMP server configuration mode.

    Step 4   port port-number


    Example:
    Device(config-twamp-srvr)# port 9000

    (Optional) Configures the port to be used by the TWAMP server to listen for connection and control requests.

    Step 5   timer inactivity seconds


    Example:
    Device(config-twamp-srvr)# timer inactivity 300

    (Optional) Configures the inactivity timer for a TWAMP control session.

    Step 6   end


    Example:
    Device(config-twamp-srvr)# end

    Returns to privileged EXEC mode.

    Configuring the Session-Reflector


    Note

    For IP SLAs TWAMP Responder v1.0, the TWAMP server and the session-reflector are configured on the same device.

    SUMMARY STEPS

      1.    enable

      2.    configure terminal

      3.    ip sla responder twamp

      4.    timeout seconds

      5.    end


    DETAILED STEPS
      Step 1   enable


      Example:
      Device> enable

      Enables privileged EXEC mode.

      • Enter your password if prompted.

      Step 2   configure terminal


      Example:
      Device# configure terminal

      Enters global configuration mode.

      Step 3   ip sla responder twamp


      Example:
      Device(config)# ip sla responder twamp

      Configures the device as a TWAMP responder and enters TWAMP reflector configuration mode.

      Step 4   timeout seconds


      Example:
      Device(config-twamp-ref)#  timeout 300

      (Optional) Configures an inactivity timer for a TWAMP test session.

      Step 5   end


      Example:
      Device(config-twamp-ref)# end

      Exits to privileged EXEC mode.

      Configuration Examples for IP SLAs TWAMP Responder

      IP SLAs TWAMP Responder v1.0 Example

      The following example and partial output shows how to configure the TWAMP server and the session-reflector for IP SLAs TWAMP Responder v1.0 on the same Cisco device. In this configuration, port 862 is the (default) port to be used by the TWAMP server to listen for connection and control requests. The port for the server listener is the RFC-specified port and can be reconfigured, if required.


      Note

      For the IP SLAs TWAMP responder to function, a control-client and the session-sender must be configured in your network.

      The following examples are for non-VRF scenarios (default): 

      Device> enable
Device# configure terminal
Router(config)# ip sla serv twamp
Router(config-twamp-srvr)# port 12000
Router(config-twamp-srvr)# timer inactivity 1200
Router(config-twamp-srvr)# exit
Router(config)# ip sla responder tw
Router(config)# ip sla responder twamp
Router(config-twamp-ref)# resp
Router(config-twamp-ref)# time
Router(config-twamp-ref)# timeout 2000
Router(config-twamp-ref)# exit

Router# show ip sla twamp connection requests
    Connection-Id     Client Address   Client Port      Client VRF
          A3              100.1.0.1         59807         default

Router# show ip sla twamp connection detail
Connection Id:          A3
  Client IP Address:    100.1.0.1
  Client Port:          59807
  Client VRF:           intf2
  Mode:                 Unauthenticated
  Connection State:     Connected
  Control State:        Active
  Number of Test Requests - 0:1

Router# show ip sla twamp session
IP SLAs Responder TWAMP is: Enabled
Recvr Addr: 100.1.0.2
Recvr Port: 7
Sender Addr: 100.1.0.1
Sender Port: 34608
Sender VRF: default
Session Id: 100.1.0.2:15833604877498391199:6D496912
Connection Id: 101

Router# sh running-config | b twamp
ip sla responder twamp
 timeout 2000
ip sla responder
ip sla enable reaction-alerts
ip sla server twamp
 port 12000
 timer inactivity 1200
!
!

      The following examples are for VRF scenarios: 

      Router# show ip sla twamp session
IP SLAs Responder TWAMP is: Enabled
Recvr Addr: 100.1.0.2
Recvr Port: 7
Sender Addr: 100.1.0.1
Sender Port: 51486
Sender VRF: intf1
Session Id: 100.1.0.2:9487538053959619969:73D5EDEA
Connection Id: D0

Router# show ip sla twamp connection detail
Connection Id:          A3
  Client IP Address:    100.1.0.1
  Client Port:          52249
  Client VRF:           intf2
  Mode:                 Unauthenticated
  Connection State:     Connected
  Control State:        Active
  Number of Test Requests - 0:1

Router# show ip sla twamp connection requests
  Connection-Id    Client Address   Client Port    Client VRF
             A3       100.1.0.1       52249          intf2
 Total number of current connections: 1

      Note
      The default port for IP SLA server is 862.

      Additional References

      Related Documents

      Related Topic

      Document Title

      Cisco IOS commands

      Cisco IOS Master Commands List, All Releases

      IP SLAs commands

      Cisco IOS IP SLAs Command Reference

      Standards and RFCs

      Standard/RFC

      Title

      RFC 5357

      Two-Way Active Measurement Protocol (TWAMP)

      RFC 4656

      One-way Active Measurement Protocol (OWAMP)

      Technical Assistance

      Description

      Link

      The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

      http:/​/​www.cisco.com/​cisco/​web/​support/​index.html

      Feature Information for IP SLAs TWAMP Responder

      The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

      Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

      Table 1 Feature Information for IP SLAs TWAMP Responder

      Feature Name

      Releases

      Feature Information

      Hardware Timestamping for IP SLA UDP Jitter Statistics

      Cisco IOS XE Everest 16.6.1

      This feature was introduced on the Cisco ASR 920 Series Aggregation Services Router (ASR-920-12CZ-A, ASR-920-12CZ-D, ASR-920-4SZ-A, ASR-920-4SZ-D, ASR-920-24SZ-IM, ASR-920-24SZ-M, ASR-920-24TZ-M, and ASR-920-12SZ-IM).

      IP SLAs TWAMP Responder on IP VRF Interface

      Cisco IOS XE Release 3.18SP

      This feature was introduced on the Cisco ASR 920 Series Aggregation Services Router (ASR-920-12CZ-A, ASR-920-12CZ-D, ASR-920-4SZ-A, ASR-920-4SZ-D, ASR-920-24SZ-IM, ASR-920-24SZ-M, ASR-920-24TZ-M, and ASR-920-12SZ-IM).

      IP SLAs TWAMP Responder v1.0

      Cisco IOS XE Release 3.13.0S

      This feature was introduced on the Cisco ASR 920 Series Aggregation Services Router (ASR-920-12CZ-A, ASR-920-12CZ-D, ASR-920-4SZ-A, ASR-920-4SZ-D).

      Was this Document Helpful?

      FeedbackFeedback

      Contact Cisco

      Related Cisco Community Discussions

      About Us
      Contact Us
      Work with Us