Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring TWAMP Client and TWAMP Server to Reconnect Automatically After TWAMP Server Unavailability

You can run TWAMP client automatically without any manual intervention during network failures or configuration changes. In case of a network outage or connection loss between a TWAMP client and TWAMP server, all the affected TWAMP TCP control connections and UDP test-sessions are lost. At each test-interval, the TWAMP client continues to send the control packets to re-establish connectivity with TWAMP server till is successful. All the statistics will be maintained during that network failure.

This procedure is for Junos OS only. To configure the TWAMP client:

  1. Configure the interfaces.
  2. Configure the chassis.
  3. Configure the services.

To configure the TWAMP server:

  1. Configure the interfaces.

  2. Configure the chassis.

  3. Configure the services.

When the TWAMP server is reachable, the output for Junos OS is as follows. The TWAMP-Server-Status is Connected and the Number-Of-Retries-With-TWAMP-Server is 1

After the server is deactivated using the command deactivate interfaces si-1/1/0 unit 30 , the output is as follows for Junos OS. The TWAMP-Server-Status is Not Connected and the Number-Of-Retries-With-TWAMP-Server is 12:

After activating the server using the activate interfaces si-1/1/0 unit 30 command the output is as follows for Junos OS. The TWAMP-Server-Status is Connected and the Number-Of-Retries-With-TWAMP-Server is 12.

Related Documentation