US 11,843,535 B2
Key performance indicators (KPI) for tracking and correcting problems for a network-under-test
Jyotikumar U. Menon, Clarksburg, MD (US)
Assigned to Spirent Communications, Inc., San Jose, CA (US)
Filed by Spirent Communications, Inc., San Jose, CA (US)
Filed on Oct. 24, 2022, as Appl. No. 17/972,386.
Application 17/972,386 is a continuation of application No. 16/950,790, filed on Nov. 17, 2020, granted, now 11,483,226.
Application 16/950,790 is a continuation of application No. 15/936,346, filed on Mar. 26, 2018, granted, now 10,841,196, issued on Nov. 17, 2020.
Prior Publication US 2023/0085976 A1, Mar. 23, 2023
Int. Cl. H04L 43/50 (2022.01); H04L 69/16 (2022.01); H04L 43/0829 (2022.01); H04L 43/0864 (2022.01); H04L 43/16 (2022.01); H04L 43/087 (2022.01)
CPC H04L 43/50 (2013.01) [H04L 43/087 (2013.01); H04L 43/0829 (2013.01); H04L 43/0864 (2013.01); H04L 43/16 (2013.01); H04L 69/16 (2013.01)] 9 Claims
OG exemplary drawing
 
1. A method of recovering test sessions including a Two-Way Active Measurement Protocol (TWAMP) control-server running on a first virtual test agent (VTA), from a temporary failure of the first VTA, the first VTA participating in a mesh of TWAMP test sessions on a network,
wherein the first VTA temporarily fails or is taken away for maintenance;
wherein the mesh of test sessions on the network includes dozens to thousands of control-clients and control-servers running on VTAs as part of a test, and wherein test sessions running concurrently between pairs of a control-client running on one VTA and a control-server running on another VTA and collectively forming the mesh of test sessions;
the method including:
a second control-client running on a second VTA detecting a fault due to packet loss during a first test session between the second control-client and a first control-server running on the first VTA and in response to the packet loss setting a fault state variable to ‘fault’;
a thread running on the second VTA responding to setting of the fault state variable to ‘fault’ by stopping the first test session, attempting unsuccessfully to restart a control setup of the first control-server, then responding to the unsuccessful restart by repeatedly attempting to restart the control setup, and repeating the attempts until the restart of the control setup is successful;
the first VTA, after the temporary failure, restarting a first session-reflector; and
the second control-client resuming the first test session by sending packets from a second session-sender controlled by the second VTA, to the first session-reflector, as part of the mesh of test sessions, without requiring restart of the test.