This sections presents OpenBACH reference scenarios.
They are organized in :
Before launching the reference scenarios below, here are several points :
To go further, there are the developer manual for jobs and OpenBACH API scenarios programming.
This section details the available scenarios to generate OpenSAND scenario.
| ||Configure network, run an OpenSAND emulation test and clear network configuration||command shellopensand, ip_route and ip_address|
| ||Run an Opensand emulation test (network is not configured)||opensand|
|OpenSAND Net Conf||Apply the network configuration required to run OpenSAND properly||ip_route, ip_tuntap, ip_address, sysctl, ip_link|
|OpenSAND Satcom Conf||Apply a SATCOM configuration based in configuration files|| Usage of
|OpenSAND Run||Run an Opensand emulation test (network is not configured)||opensand|
This section details the available scenarios for OpenBACH to test basic network metrology metrics.
|Delay metrology||Scenario to compare two different delay measurements methods||fping, d-itg_send, d-itg_recv|
|One Way Delay metrology||Scenario to compare one way delay metric||owamp-server, owamp-client, d-itg_send, d-itg_recv|
|Jitter metrology||Different scenarios to compare different jitter measurements methods||owamp-server, owamp-client, D-ITG (coming soon), iperf3|
|Rate metrology||Compare different rate measurements methods||iperf3, iperf2, nuttcp, rate_monitoring|
The idea is to provide a full network diagnostic allowing the assessment of three metrics: delay, jitter and rate. Each metric can be computed following several tools and the scenarios herein enable the comparison between these different tools. Each tool may compute the metric of interest following another method or formula. The detail of one scenario (with a succinct formalization of the metric and it relative tools) is available in the dedicated wiki page of the metric section.
This section details the available scenarios allowing to configure your network topology.
This section details the available scenarios to generate transport-level data and configure kernel stacks (and more specifically transport parameters).
This section details the available scenarios to generate traffic. Each scenario allows to launch one traffic between two OpenBACH agent. They are summarized in the following table.
|VoIP traffic||Scenario to generate VoIP traffic||voip_qoe_src, voip_qoe_dest|
|DASH traffic||Scenario to transfer a video using DASH||dash player&server, dash client|
|Web browsing traffic||Scenario to load Web pages from an Apache server||apache2, web_browsing_qoe|
|Data transfer traffic||Scenario to transfer data using iperf3 in TCP mode||iperf3|
|Service FTP||Scenario to transfer a file on FTP||ftp_clt and ftp_srv|
A global scenario named service_traffic allows to launch and schedule several traffics (VoIP, DASH, Web browsing and Data transfer).