This manual explains how to use the OpenSAND testbed by means of the OpenSAND Manager and monitor OpenSAND (logs/metrics) by means of OpenSAND Collector. OpenSAND software must already be installed, and the testbed configured. Refer to the installation and configuration manuals.
OpenSAND Manager is a graphical application based on GTK that allows the user to control the OpenSAND testbed. Some of its features include:
OpenSAND manager uses zeroconf to detect the different OpenSAND hosts in the platform, which is why it is important that the machine be connected to the same network as the hosts, and that the service name be unique. If the default service name is used (
_opensand._tcp), then the manager can be launched with:
Else, the service name must be specified:
sand-manager -t <service_name>
In order to start a simulation, the user can simply click on the
Start OpenSAND button, located on the upper left corner of the
Run tab (or click
Start OpenSAND on the
Simulation menu). This will start the OpenSAND processes on all the testbed hosts. Once the simulation is started, user workstations can send and receive network traffic over the satellite network.
The spot besides each host name indicates the state of said host. When launching the simulation, all hosts states should turn green, which means that the hosts are running. Red and orange colours indicate that there is a problem with the daemon.
The output view displays messages relayed from the daemons to the manager, and include a message indicating that a simulation has successfully started.
Run ID field allows the user to specify a name for the session. By default, the
Run ID is named
N incremented on each start.
In order to stop a simulation while it is running, the user can simply click on the
Stop OpenSAND button, located on the upper left corner of the
Run tab (or click
Stop OpenSAND on the
Simulation menu). This will stop the OpenSAND processes on all the testbed hosts. Once simulation is stopped, user workstations can no longer send nor receive network traffic over the satellite network.
OpenSAND manager will print messages to show which actions are executed, and eventual errors. The spot of each component should turn red after stopping the simulation.
OpenSAND manager allows the user to save and load previous simulations. A simulation contains the manager configuration, the hosts' configurations, and all the simulation results, which can be loaded on the
Simulations are stored in dedicated folters: to save a simulation, the user must create a new folder; to load one, the user must provide the path to a folder. By default, all simulations are saved in
~/.opensand/default folder, and cleaned on exit. To keep the results, the user must specify another folder.
The current scenario name is displayed in the window title.
The configuration in OpenSAND Manager is divided in two tabs:
Resource Configuration, and
Resource Configuration tab allows the user to configure parameters linked with the waveforms used, such as the available MODCODs and the available bandwidth, the GW associated to each ST, as well as its category.
Configuration tab, the user can select the type of LAN adaptation to use, the encapsulation protocols on the forward and return link, and whether to use physical attenuation or not. For more advanced configurations, the
Advanced button will display the Advanced Configurations Dialog.
The complete list of satcom features implemented by OpenSAND is presented in the emulated satcom features page. Each feature contains at least one page, with information about how it is implemented in OpenSAND, and how to make use of it.
Furthermore, the OpenSAND Testbed Description page presents the different characteristics specific of the OpenSAND test platform.
A script is available (modcod2attenuation), which allows the user to convert MODCOD trace files to attenuation files: this way, the user can specify the evolution of the MODCODs used on a link (forward or return), and the script will calculate the attenuations needed to obtain such MODCODs. Refer to its page for more information about how to use it.
This manual documents the different parts composing the OpenSAND's collector, their configuration and their usage.
The OpenSAND collector is composed of:
It also installs the following visualization tool:
Each component is brought as dependency of the
opensand-collector package and set-up to work with one another.
Kibana is installed and configured by the
opensand-collector package as a way to visualize the logs sent by OpenSAND.
It provides a web server that is listening on port 5601 by default. In order to visualize your logs, fire a web browser and open it to:
To explore the logs, go to the Dashboard tab on the left pane. The default view will list the logs received by the collector during the past 15 minutes. You can select the refresh and time-period options by using the menu in the top-right corner.
Chronograf is installed and configured by the
opensand-collector package as a way to visualize the probes sent by OpenSAND.
It provides a web server that is listening on port 8888 by default. In order to visualize your logs, fire a web browser and open it to:
In order to explore your probes, go to the Explore tab on the left pane and choose the
opensand.autogen retention policy (see highlighted fields in the picture below). Probes emitted by OpenSAND will be shown and you will be able to select those that are of interest to you (we recommend you to disable the mean function when you select each Probe).
We recommend you to use the Chronograf manual Chronograf.
You can also create your own dashboards for monitoring OpenSAND. Go to the Dashboards tab on the left pane, then:
An example of dashboard Chronograf with OpenSAND probes is shown below: