Knowledge base
Canceling Scenarios on Wireless Endpoints
Posted by Pieter Vandercammen, Last modified by Wouter Debie on 26 April 2019 03:18 PM

The ByteBlower App for the Wireless Endpoint is used for reliable network testing. One can use it for any type of network, but most of its features are designed for wireless networks. Especially for such networks, there is a trade-off between loading the network and making it the App easy to use. As we will show in this article, cancelling a scenario is one such situation where both can't be met simultaneously. We'll discuss first how to stop a scenario on a Wireless Endpoint. Next we'll detail the reasoning behind our design.

A scenario-run is shown in the images below. The right one is taken from the App itself. The 'Running' state, shown top right, indicates that the device is currently performing a test. The same state is visible from the GUI. A red play-button is added to the Wireless Endpoint after a refresh

 

The cancel button in the ByteBlower GUI stops a scenario early. Pressing the button shown in the image, halts the traffic on the ByteBlower server and frees up the GUI for the next scenario. Unfortunately new scenarios with any Wireless Endpoint in the cancelled test will still wait for the remaining duration of the configured scenario.

 

 

On long tests, waiting for the end of the test might not be an option. In this case, one will need to restart the App manually. The MeetingPoint is robust against such changes and immediately picks up a fresh start. In the GUI, it might necessary to refresh the app.

The reason for this manual work is already hinted to in the introduction. The functionality on the Wireless Endpoints has a trade-off between user-friendliness and correctly testing the network. To complicate matters further, because of NAT, the Wireless Endpoint is often not directly reachable by the MeetingPoint. Heavily loaded networks with poor reception make this even more difficult.

To avoid changing the behaviour of the network, the management communication of the App remains quiet during test runs.
This is different from the management communication with the ByteBlower server. Commands between them are sent out over a different network, and the ByteBlower server proportioned for this extra traffic. During a test, the GUI remains in contact with the server.

Scenarios on the server can thus easily be cancelled. Since there is no communicating between GUI and Wireless Endpoints, it is not possible for the App to stop early. Of course, a cancellation feature is still being worked on and future versions of the App will add improvements.  

(0 vote(s))
Helpful
Not helpful

Comments (0)

We to help you!