Knowledge base:
Overview: Using the ByteBlower Server
Posted by Pieter Vandercammen, Last modified by Pieter Vandercammen on 06 April 2021 06:59 PM

This article discusses the client facing components of a ByteBlower setup. As shown in the picture further below, the ByeBlower server performs the heavy-lifting to generate traffic and measurement results. This part is shown left. All systems are available as a 1U rack system. The client computer (shown left) drives the setup, even for traffic generation.

Client software is freely available for all major platforms. Testing is possible using graphical ByteBlower GUI application or command-line with the ByteBlower-CLT. Both share the same file formats, all stored locally on the client computer. These applications include a reporting engine that generate general reports in various formats, including HTML and PDF.

More scripting is available through Python and Tcl libraries, these allow you to use the ByteBlower API directly. The base building blocks are the same as found in the ByteBlower GUI but without the separate reporting engine. Overall, both programming languages give more flexibility for more complex scenarios and more results for in-depth analysis.

There are no software restrictions on the number of clients. In fac,t it's common to share a single system across multiple users. Download links are found in the following website:

Managing the ByteBlower server is possible using SSH. For the very first setup it's advised to connect a screen and keyboard the system. For those familiar, non-physical access is also possible using IPMI.

(0 vote(s))
Not helpful

Comments (0)

We to help you!