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/example
History
Pau Espin 786a6bcd20 Introduce initial Amarisoft ENB support 
* object class expects the amarisoft software to be placed in directory
  provided by env var AMARISOFT_PATH_ENB. On local runs, it will run the
  software from there. On remote runs it will copy over that directory to
  the slave.
* Configuration provided works with 6 PRBs, but probably won't work for
  other values (yet).
* ZMQ support not yet available, only UHD.

One can select the Amarisoft ENB by declaring it in resources.conf:
"""
- label: AmarisoftENB-B200
  type: amarisoftenb
  rf_dev_type: uhd
  rf_dev_args: "type=b200,serial=317B9FE,recv_frame_size=9232,send_frame_size=9232"
  remote_user: jenkins
  addr: 10.12.1.206
"""

And running:
"""
$ export AMARISOFT_PATH_ENB=/path/to/binaries
$ osmo-gsm-tester.py ... -s 4g:amarisoftenb-rftype@uhd+srsue-rftype@UHD+mod-enb-nprb@6 -t ping
"""

Change-Id: I1ddf4962ea6438ad977382ab201b724028ca46b3
 		2020-03-31 08:22:18 +00:00
..
scenarios Introduce initial Amarisoft ENB support 2020-03-31 08:22:18 +00:00
README.txt put the example suite in /example, not /selftest/real_suite 2017-05-04 16:42:50 +02:00
default-suites.conf scenarios: Use parametrized scenario for rftype 2020-03-04 13:33:21 +01:00
defaults.conf Introduce initial Amarisoft ENB support 2020-03-31 08:22:18 +00:00
paths.conf paths: have one common parent dir /var/tmp/osmo-gsm-tester 2017-05-11 17:39:02 +02:00
resources.conf.prod srsLTE: Support configuring different RF backends 2020-02-20 15:54:33 +01:00
resources.conf.rnd resources.conf: Mark osmo-bts-trx as supporting a5/3 2019-11-26 14:19:37 +01:00
resources.conf.virtual nitb_netreg_mass: Provide 100 subscribers 2019-03-07 10:05:48 +00:00

README.txt 

This a real gsm 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 OSMO_GSM_TESTER_CONF
environment variable:

    export OSMO_GSM_TESTER_CONF="$PWD"

When there is no OSMO_GSM_TESTER_CONF set, osmo-gsm-tester will instead look
for conf files in several locations like ~/.config/osmo-gsm-tester,
/usr/local/etc/osmo-gsm-tester, /etc/osmo-gsm-tester.

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 ~/my_trial

Specifically, from this dir:

    OSMO_GSM_TESTER_CONF="$PWD" ../src/osmo-gsm-tester.py ~/my_trial

Alternatively you can setup this example as permanent config using something
like:

    mkdir -p ~/.config
    ln -s "$PWD" ~/.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 $PWD, set up an own configuration pointing at a
different path (see paths.conf: 'state_dir').