cellular-infrastructure
/
osmo-gsm-tester
mirror of https://gerrit.osmocom.org/osmo-gsm-tester
9
0
Fork 0
Code Issues Releases Wiki Activity
osmo-gsm-tester/sysmocom
History
Neels Hofmeyr ecce402f43 configure fixed ARFCN per bts 
Remove ARFCNs as a concept from resource pool, assign a fixed ARFCN to
each BTS and TRX in the resource pools.

Using ARFCNs on specific bands as resources was an idea that is hard to
implement, because specific BTS dictate selection of bands which
influences which ARFCNs can be picked. That means reserving ARFCN
resources is only possible after reserving specific BTS resources, but
the tester is currently not capable of such two-stage resolution.

Writing handover tests, I got the problem that both BTS in a scenario
attempt to use the same ARFCN.

The by far easiest solution is to assign one fixed ARFCN to each BTS and
TRX. If ever needed, a scenario modifier can still configure different
ARFCNs.

(Due to uncertainty about OC2G operation stability, I prefer to leave
OC2G on ARFCN 50, as it happened to end up being configured before this
patch.)

Change-Id: I0a6c60544226f4261f9106013478d6a27fc39f38
 		2020-12-11 00:19:13 +01:00
..
scenarios ms_amarisoft: fix various regressions 2020-11-23 12:33:52 +01:00
suites iperf3_{dl,ul}: adapt pass/fail threshold 2020-11-11 12:47:47 +01:00
ttcn3 ttcn3/lib/testlib.py: increase test suite execution timeout 2020-08-14 14:05:53 +07:00
README.md Cmdline arg -c sets main configuration file (old paths.conf) instead of dir containing it 2020-05-12 14:07:29 +02:00
default-suites.conf sysmocom: Enable emergency call testing in default-suites.conf 2020-10-15 15:50:48 +00:00
defaults.conf configure fixed ARFCN per bts 2020-12-11 00:19:13 +01:00
main.conf config: suites_dir and scenarios_dir are now a list of paths 2020-05-25 13:33:50 +02:00
resources.conf.prod configure fixed ARFCN per bts 2020-12-11 00:19:13 +01:00
resources.conf.rnd configure fixed ARFCN per bts 2020-12-11 00:19:13 +01:00
resources.conf.virtual Move example/ and ttcn3/ to sysmocom/ and sysmocom/ttcn3 2020-04-10 19:00:14 +02:00

README.md

This a real 2G test suite configured and ready to use. The only thing missing is a trial dir containing binaries.

You can point osmo-gsm-tester.py at this config using the '-c $DIR/main.conf' command line argument, where DIR is the directory path where this README file resides.

If you have your trial with binary tar archives in ~/my_trial you can run the suite for example like this:

osmo-gsm-tester.py -c $DIR/main.conf ~/my_trial

Alternatively you can setup this example as default config for your user by doing something like:

mkdir -p ~/.config
ln -s "$DIR" ~/.config/osmo-gsm-tester

A ./state dir will be created to store the current osmo-gsm-tester state. If you prefer not to write to $DIR, set up an own configuration pointing at a different path (see main.conf: 'state_dir').