Age | Commit message (Collapse) | Author | Files | Lines |
|
This content is mostly specific to sysmocom's setup (thought it can
still be re-used by other people if willing to).
symlinks in ttcn3/ pointing to example/ are redone to point to
sysmocom/.
Change-Id: I364e0859c0851b9167907a4d948b659a0f6a19fb
|
|
example/paths.conf and documentation are updated accordingly.
Test suites should have been moved a long time ago, since the they are
user or setup-specific based on what needs to be tested.
Change-Id: I154b19979b545deba8b232b60172903f63fd9e28
|
|
this commit adds basic support for configuring measurements in the
eNB config. It currently support A1, A2, and A3 events.
By default UE measurements are turned off and need to be enabled by
configuring an event with:
+mod-enb-meas-event@{name},{report_type},{value},{hysterisis},{time to trigger}
For example one can update the a2 and a3 event with:
+mod-enb-meas-event@a2,rsrq,-40,2,480+mod-enb-meas-event@a3,rsrp,6,1,512
Change-Id: Ia7657be2396886840570bc41645450a268b4cfff
|
|
Change-Id: Idda0d3a040663969dd71781814198b47fff7daf3
|
|
Change-Id: I21b7d7009f9b0df8ec4f59189a65cfc26f164f04
|
|
This allows selecting modem by supported network type. It will allow
using 4G modems with type different than srsue in 4g suite in the future.
Change-Id: I38bcf6abf789f52c3ed0bee7911567fa872e2491
|
|
Change-Id: Ie438c8aa9992dbc61b2133473a83d565cf5c7056
|
|
Older versions of srsLTe.git required passing UHD in caps to the conf
file, but that's not the case anymore. Let's use lowcase then.
Change-Id: If8a289ba110229d31b62b0d3adc1ae97324e6d27
|
|
the time is passed as a string param and is then converted
into seconds when literals "h" or "m" are found.
So it would accept 2m and would convert it to 120s, for example.
Example:
+cfg-iperf3-time@15+
Change-Id: Iff28816f83670751e9e91de31ec59b1b0ad8fc0d
|
|
* Since license_server_addr logic is generic among all amarisoft
software, let's move it to its own config category "amarisoft", which
all amarisoft classes (amarisoft_{enb,epc}.py as of now) will import
during configure().
* The license server is disabled by default (value 0.0.0.0) since the
usual case is to have a license in the local system.
* the license server can be enabled using scenario
cfg-amarisoft-license@A.B.C.D where A.B.C.D is the address to use.
Change-Id: Id5456ad9497e91370857b80ff9a389111d3611ff
|
|
width for B2XX
Change-Id: I2de0526ee9bd2f7bb75c7d529b3f52d75117c5cc
|
|
* A new abstract generic base class EPC is created
* srsEPC and AmarisoftEPC inherit from that class
* options are loaded from defaults.conf in cascade. First generic "epc",
afterwards the specific enb type.
* A new scenario is added to select the EPC type to use. srsEPC is the
default unless stated by an scenario.
* AmarisoftEPC delegates setup of the tun IP address to an "ifup"
script. As a result, since we run without root permissions (ony with
CAP_NET_ADMIN), the ifup script itself is unablet o set the IP
address. To solve this, we introduce a new osmo-gsm-tester helper
script which must be installed in the slave node which can be called
through sudo to increase privileges to do so.
With this commit, I can already get srsUE<->amarisoftENB<->amarisoftEPC
to pass ping and iperf3 4g tests.
Change-Id: Ia50ea6a74b63b2d688c8d683aea11416ad40a6d3
|
|
* 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
|
|
Change-Id: Ibe94fada0a40c499dd516408756c4ef7988ccec5
|
|
this allows to configure a UE to support multiple carriers
Change-Id: I4fa0a0c6e52efb17aa0b07e55abb5470d8028e8b
|
|
this is needed to support the upcoming multi-cell feature in srsENB.
It's required for carrier aggregation (CA) but can also
be used for (currently) two independent 4G cells.
This commit adds baseline support for the parameter. Upcoming
commits will add hooks to configure the cell's EARFCN, etc.
Change-Id: I6d1658bf820163aee03b64b0f4ac68046c243f37
|
|
Change-Id: I5db2ff325ce4b4236c1ceec0831dd7420d52dedb
|
|
There's already a parametrized scenario handling it. We don't use any
soapy backend for srsue anyway yet.
Change-Id: Ie680178d2b16139473b5899803fb69a715a79216
|
|
Take the change to fix several small things and support recording pcap
in srsENB.
pcap generation can be enabled with scenario cfg-srs-enable-pcap.
Change-Id: Ia096a9be7efb2123f95115c751e2402fb4fec935
|
|
Change-Id: Ib3d7db13d7de492eee5ad25cf5c88239be9e9fbf
|
|
Change-Id: I38f247f266ba736cdbb6f36ba5673b8fd46a8d67
|
|
Change-Id: Iec7d7e6312aee6f4e4ce6710bc78a144beff2f39
|
|
Change-Id: I0b8c834f1c67cc4bf4d07d03358ba2012331cbde
|
|
Change-Id: I336e71f53556596050cf3eb55a7810a009dbf7a8
|
|
Before this patch, only virtual RF through ZeroMQ was supported.
This patch allows configuring srsUE and srsENB to use a real SDR with
UHD/SoapySDR backend connected through a physical RF network, while
still keeping compatibility to run on virtual RF ZeroMQ network, based
on the resources used (controlled by scenarios). For instance, one can
first run a suite through the phyisical RF (using 2 UHD-controlled SDRs)
and afterwards with ZeroMQ using the following default-suites.conf:
- 4g:srsenb-rftype-uhd+srsue-rftype-uhd
- 4g:srsenb-rftype-zmq+srsue-rftype-zmq
Change-Id: I7dbbe328f4c0225fe74e878bb2da13fe39ccf049
|
|
Change-Id: I3f8c3588d7b139f044462d02069919256126bf57
|
|
2 tests (iperf3, ping) working against a full srs{UE,ENB,EPC} network
using ZeroMQ backend for RF (so no real RF support yet, that will come
next).
Related: OS##4295, OS#4296
Change-Id: I290c0d79258a9f94f00c7ff2e1c6c5579c0e32f4
|
|
Change-Id: Iec50662580479bf7b6dc08d08a1de8075b2da078
|
|
Change-Id: I7f774e7bf6539c5afd1d3e35da765ba8d702fdb7
|
|
bts_osmotrx will check if target host can run the inst, and otherwise
run osmo-trx-lms already present in the system (installed by other
means). This way same class can be used both ways, since the only real
difference between the 2 scenarios is:
* copying inst vs not copying it.
* Running binary from inst vs running it from PATH.
This commit does not provide a mechanism to make sure the osmo-trx or its
dependencies are up-to-date in the target system. A solution for that
will be provided separately.
Related: SYS#4663
Change-Id: I6bd76f6d7e0cb2b6f7bdde971b6515846048a341
|
|
Change-Id: Iddb0f20366c3242098bdf869f39fc3e2244c13e7
|
|
Change-Id: I478e0719589a8055e7b16536e679d2801efc5caf
|
|
This reverts commit 91199a31377fe94a79376eca9232151a3f637bce.
Since we now support powercycling the SC5, we don't longer need to use a
different ARFCN for it.
Change-Id: Ie8b49c556c90b4a97a73695a93ac4108660a217f
|
|
* Add powersupply related code to bts_osmotrx.py to power cycle the
board.
* Each time the board is started, we need to unlock the RF (start TRX
implementation).
Change-Id: I8a1428c1ff90c9f5b42d7ffe86a6fc763819cba2
|
|
Change-Id: I8e87aa5e24d1ed0737ec50e6a0f7fd8779a3c15b
|
|
Change-Id: Ic124c51aac26769058f0e90dc5497d16b44be085
|
|
The feature is not supported yet and it seems to be leaving osmo-trx-lms
in a zombie state preventing it to exit and blocking other tests.
Let's disable it until this feature is working properly under manual
use.
Related: OS#4151
Change-Id: Ic255481e6f1fbbf06c4576f924cf27ae80567801
|
|
Due to a bug in sysmocell-5K's TRX implementation, it may keep polluting
the air transmitting after the BTS is disconnected. This could cause
interferences with other tests. Correct fix would be to RF lock it after
test finishes (through ccli), but let's simply use a different ARFCN for
now.
Related: OS#4129
Change-Id: I6d5555aa8740b262ee92110987189c076db44f76
|
|
Force TRXDv0 when using sysmocell-5k as a TRX, since its implementation
(different than osmo-trx) doesn't support higher versions. Furthermore,
it will crash upon receival of SETFORMAT string. By forcing maximum TRXD
version to 0, osmo-bts-trx won't sent any SETFORMAT message since 0 is
the initial version to use.
Depends: osmo-bts.git I5eb1fdc002f9d7f4acf475356d8fc998dc8f6326
Related: OS#4006
Change-Id: Ic95c38d91dba354ae64c5edbfcea3fbbf34a7de3
|
|
Change-Id: I5cfce927569b6a2d8ca57d3394116bbcff3eee56
|
|
Change-Id: I5599c86565ebb6d7d6931d36fd49e57fe2020d1f
|
|
Change-Id: I446e27039f75e63c2870d751c190a4fd76947000
|
|
Change-Id: I386885f4179d4fc2df23cc48cd1eda850b5a990b
|
|
Add a new resource and make a reservation in the suite.
Change-Id: Ic26aa63cad62323bb85f952640672eb28af0eadc
|
|
Change-Id: I6ef234edb06031644758174e93a9d3817d0acc1f
|
|
Create a dedicated resources file for running "virtual" tests. If all
components run on the same machine we can avoid having to manage
separate network.
Change-Id: I0da1267a71dc06fd06f3cf4fc3dcfefda4bcf40b
|
|
It's very close to the osmo-bts-trx but without osmo-trx. Modify
the suite to make use of this BTS.
Change-Id: I9f5a2501eb4473ccf2287c902ee207c6a45a1bc5
|
|
nanoBTS doesn't support SDCCH8 in TS!=1 according to osmo-bsc code.
Let's use in this case TCH/H to make sure they are not used for the test
(since we require osmo-bsc to use full rate codecs for the call).
Change-Id: I37f3fe813d4074fbfe64ff3176048e7d25d470e2
|
|
osmo-trx-uhd uses these args during device search/selection process. As
those were not set until now for B200, it means when a B200 was used by
osmo-gsm-tester any UHD device could be picked up and used by UHD.
That was actually happening since inclusion of UmTRX devices in Prod
setup, when running tests against desired B200, actually the UmTRX
device was being used.
Change-Id: I696bbc800b05fdd9a68a77f363d76dcc53ef24ee
|
|
Given current bad support of most features used, gobi2k modem was
removed and an EC20 was added instead.
Change-Id: I2df38547978c7d2b1a1309f6e73b5a59413e08ff
|