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/defaults.conf

122 lines
2.0 KiB
Plaintext
Raw Normal View History

core implementation code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9
2017-03-28 12:30:28 +00:00
nitb:
net:
nitb,sysmobts: tweak config Set saner MCC+MNC, use more power.
2017-05-04 12:29:47 +00:00
mcc: 901
mnc: 70
MSC+BSC: add test api to run OsmoMSC and OsmoBSC with AoIP Change-Id: I5842e8f1cba8e8e6bedfc08540efcafe207159cb
2017-05-18 13:24:02 +00:00
short_name: osmo-gsm-tester-nitb
long_name: osmo-gsm-tester-nitb
auth_policy: closed
Use own format to specify encryption algorithm ... instead of using the one from from osmo vty directly. This way we avoid having multiple word attribute value and we can skip using quotes in the conf files. Change-Id: I5265cc9990dd5e99dba1f6262b3a8c597a3e958d
2017-09-04 14:26:08 +00:00
encryption: a5_0
MSC+BSC: add test api to run OsmoMSC and OsmoBSC with AoIP Change-Id: I5842e8f1cba8e8e6bedfc08540efcafe207159cb
2017-05-18 13:24:02 +00:00
bsc:
net:
mcc: 901
mnc: 70
short_name: osmo-gsm-tester-msc
long_name: osmo-gsm-tester-msc
Use own format to specify encryption algorithm ... instead of using the one from from osmo vty directly. This way we avoid having multiple word attribute value and we can skip using quotes in the conf files. Change-Id: I5265cc9990dd5e99dba1f6262b3a8c597a3e958d
2017-09-04 14:26:08 +00:00
encryption: a5_0
osmo-bsc: Parametrize codec-list VTY cfg Change-Id: I1678aba43e8d399ecad192cbc416698373e3c0a0
2018-08-27 10:53:41 +00:00
codec_list:
defaults.conf: Set valid default codec_list matching avail TS types By default, all channels are TCH/F, and as a result we cannot run half rate codecs on it. Since recent versions of osmo-bsc, it checks this kind of misconfigurations and answers with an Assignment Failure: .... 20181029162133430 DMSC <0007> codec_pref.c:445 codec-support/trx config of BTS 0 does not intersect with codec-list of MSC 0 20181029162133430 DMSC <0007> osmo_bsc_main.c:887 Configuration contains mutually exclusive codec settings -- check configuration! .... 20181029162255253 DMSC <0007> osmo_bsc_bssap.c:859 Rx MSC DT1 BSSMAP ASSIGNMENT REQ 20181029162255254 DMSC <0007> osmo_bsc_bssap.c:718 No supported audio type found for channel_type = { ch_indctr=0x1, ch_rate_type=0xa, perm_spch=[ 42 21 11 01 25 05 ] Change-Id: Ie6b37839fe363b5d1ba64c267d751221434cdedb
2018-10-29 16:46:59 +00:00
- fr1
MSC+BSC: add test api to run OsmoMSC and OsmoBSC with AoIP Change-Id: I5842e8f1cba8e8e6bedfc08540efcafe207159cb
2017-05-18 13:24:02 +00:00
msc:
net:
mcc: 901
mnc: 70
short_name: osmo-gsm-tester-msc
long_name: osmo-gsm-tester-msc
Use own format to specify encryption algorithm ... instead of using the one from from osmo vty directly. This way we avoid having multiple word attribute value and we can skip using quotes in the conf files. Change-Id: I5265cc9990dd5e99dba1f6262b3a8c597a3e958d
2017-09-04 14:26:08 +00:00
encryption: a5_0
Add support for authentication VTY param in msc and bsc Change-Id: Ie1eb76149d4b006631050f8a1e532fbdbdad6a7f
2017-08-23 15:39:54 +00:00
authentication: optional
core implementation code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9
2017-03-28 12:30:28 +00:00
rename more items from nitb to bsc A NITB is a BSC + MSC, and if a BTS talks to a NITB, it talks to the BSC part of the NITB. Hence it makes more sense to name certain things 'bsc' instead of 'nitb', to prepare for a separate BSC process appearing soon. Change-Id: I6a0343b9243b166d4053cc44f523543f1245d772
2017-05-18 17:31:44 +00:00
bsc_bts:
core implementation code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9
2017-03-28 12:30:28 +00:00
base_station_id_code: 63
stream_id: 255
fix octphy, fix conf, improve logging Clearly separate the kinds of BTS hardware the GSM tester knows ('type') from the NITB's bts/type config item ('osmobsc_bts_type' -- not 'osmonitb_...' to stay in tune with future developments: it is the libbsc that needs this). For BTS hardware kinds, use the full name of the binary for osmo driven models: osmo-bts-sysmo, osmo-bts-trx, osmo-bts-octphy. Change-Id: I1aa9b48e74013a93f9db1a34730f17717fb3b36c
2017-04-13 01:11:59 +00:00
osmobsc_bts_type: sysmobts
Add channel_allocator cfg attr to bts resources Change-Id: I682809d4aeb91a36e3a35fc481e8d40d0b084fa0
2018-08-22 09:01:32 +00:00
channel_allocator: ascending
Add support to enable EGPRS Change-Id: I682f0c1b4cb97b704d646f18f54e748baaefd677
2018-10-29 10:30:00 +00:00
gprs_mode: gprs
bts: Allow setting amount of TRX and timeslot in cfg and from test at runtime The num_trx attribute for a given BTS states the number of TRX to be used by that BTS. If more than num_trx are configured in trx_list in the cfg file, then only up to num_trx are taken into account. If a num_trx value higher than max_trx is specified throuygh config file or at runtime by the test, an exception is raised explaining the issue. The num/max_trx attributes are overlayed along the config levels (generic -> bsc_bts -> specific bts-type -> specific resource object). This way we can specify a long list of trx+timeslot config in the generic config (bsc_bts), and tune for each model and specific BTS which is the desired default number of TRX, as well as the maximum supported per type. Change-Id: I7f46eaf7a16f03268653299c93600c0443f691ac
2018-05-07 11:49:33 +00:00
num_trx: 1
max_trx: 1
core implementation code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9
2017-03-28 12:30:28 +00:00
trx_list:
nominal_power and max_power_red attrs can now be set per resource Before this commit, only max_power_red was specified and it could only be used as a defaults and could not be set per object. Together with nominal_power, it can be useful to be able to set them to different values for different objects, as for example different osmo-bts-trx objects can require different values. Change-Id: I472742e98052cc39686d38c945be76d7f50eeebd
2017-09-14 11:52:28 +00:00
- nominal_power: 23
max_power_red: 0
core implementation code bomb implementing the bulk of the osmo-gsm-tester Change-Id: I53610becbf643ed51b90cfd9debc6992fe211ec9
2017-03-28 12:30:28 +00:00
arfcn: 868
timeslot_list:
- phys_chan_config: CCCH+SDCCH4
- phys_chan_config: SDCCH8
defaults.conf: use only TCH/F instead of dynamic channels Let's opt for the oldest/simplest case by default. Change-Id: I89d634cc51e13bdf6ec157ffb64baa80a469f4c8
2017-05-06 23:25:26 +00:00
- phys_chan_config: TCH/F
- phys_chan_config: TCH/F
- phys_chan_config: TCH/F
- phys_chan_config: TCH/F
defaults.conf: Add PDCH channels to test GPRS Change-Id: I8c90e2ef14a3556b62240e335ea3147df1467657
2017-11-20 19:35:01 +00:00
- phys_chan_config: PDCH
- phys_chan_config: PDCH
bts: Allow setting amount of TRX and timeslot in cfg and from test at runtime The num_trx attribute for a given BTS states the number of TRX to be used by that BTS. If more than num_trx are configured in trx_list in the cfg file, then only up to num_trx are taken into account. If a num_trx value higher than max_trx is specified throuygh config file or at runtime by the test, an exception is raised explaining the issue. The num/max_trx attributes are overlayed along the config levels (generic -> bsc_bts -> specific bts-type -> specific resource object). This way we can specify a long list of trx+timeslot config in the generic config (bsc_bts), and tune for each model and specific BTS which is the desired default number of TRX, as well as the maximum supported per type. Change-Id: I7f46eaf7a16f03268653299c93600c0443f691ac
2018-05-07 11:49:33 +00:00
- nominal_power: 23
max_power_red: 0
osmo-trx: Add multi_arfcn support 2nd TRX arfcn is changed in defaults.conf because multi_arfcn requires them to be alocated in steps of 4 starting from TRX0. It is not enabled by default yet on B200 (it must use it to support several TRX) because current host running osmo-gsm-tester is not performant enough and cannot keep up with timers due to multi-arfcn CPU overhead. Change-Id: I096df82ad1f4cbb41dfbd6a78466a845f34be385
2018-09-17 18:25:55 +00:00
arfcn: 872
bts: Allow setting amount of TRX and timeslot in cfg and from test at runtime The num_trx attribute for a given BTS states the number of TRX to be used by that BTS. If more than num_trx are configured in trx_list in the cfg file, then only up to num_trx are taken into account. If a num_trx value higher than max_trx is specified throuygh config file or at runtime by the test, an exception is raised explaining the issue. The num/max_trx attributes are overlayed along the config levels (generic -> bsc_bts -> specific bts-type -> specific resource object). This way we can specify a long list of trx+timeslot config in the generic config (bsc_bts), and tune for each model and specific BTS which is the desired default number of TRX, as well as the maximum supported per type. Change-Id: I7f46eaf7a16f03268653299c93600c0443f691ac
2018-05-07 11:49:33 +00:00
timeslot_list:
- phys_chan_config: TCH/F
defaults.conf: Add SDCCH8 ts in TRX1 cfg This way we can test too if SDCH8 channels are allocated and used correctly in TRX1 in multiTRX setups. Change-Id: I9d08f3d019a28cf775d70d941c5a60a7e7ca20a9
2018-10-04 09:49:25 +00:00
- phys_chan_config: SDCCH8
bts: Allow setting amount of TRX and timeslot in cfg and from test at runtime The num_trx attribute for a given BTS states the number of TRX to be used by that BTS. If more than num_trx are configured in trx_list in the cfg file, then only up to num_trx are taken into account. If a num_trx value higher than max_trx is specified throuygh config file or at runtime by the test, an exception is raised explaining the issue. The num/max_trx attributes are overlayed along the config levels (generic -> bsc_bts -> specific bts-type -> specific resource object). This way we can specify a long list of trx+timeslot config in the generic config (bsc_bts), and tune for each model and specific BTS which is the desired default number of TRX, as well as the maximum supported per type. Change-Id: I7f46eaf7a16f03268653299c93600c0443f691ac
2018-05-07 11:49:33 +00:00
- phys_chan_config: TCH/F
- phys_chan_config: TCH/F
- phys_chan_config: TCH/F
- phys_chan_config: TCH/F
Add testsuite + scenarios to test nanoBTS multiTRX Currently only 2 nanoBTS in the 900 band are attached together as a multiTRX setup. We thus set num_trx to 2 and set channel allocator descending to force the BTS to use the 2nd TRX when allocating channels. Change-Id: I12e1bcb047c4efac5693cf725739e0ce2e0532ee
2018-08-22 09:24:48 +00:00
- phys_chan_config: PDCH
- phys_chan_config: PDCH
bts: Allow setting amount of TRX and timeslot in cfg and from test at runtime The num_trx attribute for a given BTS states the number of TRX to be used by that BTS. If more than num_trx are configured in trx_list in the cfg file, then only up to num_trx are taken into account. If a num_trx value higher than max_trx is specified throuygh config file or at runtime by the test, an exception is raised explaining the issue. The num/max_trx attributes are overlayed along the config levels (generic -> bsc_bts -> specific bts-type -> specific resource object). This way we can specify a long list of trx+timeslot config in the generic config (bsc_bts), and tune for each model and specific BTS which is the desired default number of TRX, as well as the maximum supported per type. Change-Id: I7f46eaf7a16f03268653299c93600c0443f691ac
2018-05-07 11:49:33 +00:00
osmo_bts_octphy:
max_trx: 2
nanobts: Support multiTRX num_trx is left for now by default to 1, but it has been tested to work properly (current tests pass and both trx are configured) with num_trx=2. Change-Id: Ib3962f824a804e2aa582601475a8514c6cb0d8e7
2018-07-27 14:24:29 +00:00
nanobts:
max_trx: 2
Add testsuite + scenarios to test nanoBTS multiTRX Currently only 2 nanoBTS in the 900 band are attached together as a multiTRX setup. We thus set num_trx to 2 and set channel allocator descending to force the BTS to use the 2nd TRX when allocating channels. Change-Id: I12e1bcb047c4efac5693cf725739e0ce2e0532ee
2018-08-22 09:24:48 +00:00
trx_list:
- {}
- timeslot_list:
- {}
- {}
- {}
- {}
- {}
- {}
- phys_chan_config: TCH/F # nanobts only supports PDCH in TRX0.
- phys_chan_config: TCH/F
osmo-bts-trx: Big refactor and cleanup of osmo-trx related code * This commit is a preparation for future commits to add support for different osmo-trx devices and backends like osmo-trx-lms. * Drop deprecated osmo-trx-* cmd line params and use VTY cfg to set them. * As number of osmo-trx related osmo-gsm-tester attributes grow, group them togther in an "osmo_trx" dictionary. Change-Id: I77d29413c9e3b600b796627ba366f80c3281b7e1
2018-08-27 15:07:41 +00:00
osmo-bts-trx: Add multiTRX support Support is limited to 1 osmo-trx with 1 phy and multiple instances. Change-Id: If2bda5ec7ac9fa3fe6bc5d71f323c3ccc2a70158
2018-09-17 18:24:13 +00:00
osmo_bts_trx:
max_trx: 2
osmo-bts-trx: Big refactor and cleanup of osmo-trx related code * This commit is a preparation for future commits to add support for different osmo-trx devices and backends like osmo-trx-lms. * Drop deprecated osmo-trx-* cmd line params and use VTY cfg to set them. * As number of osmo-trx related osmo-gsm-tester attributes grow, group them togther in an "osmo_trx" dictionary. Change-Id: I77d29413c9e3b600b796627ba366f80c3281b7e1
2018-08-27 15:07:41 +00:00
osmo_trx:
type: uhd
launch_trx: true
clock_reference: internal
ms_driver: Add a virtual bts and make use of it 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
2018-12-06 18:34:53 +00:00
osmo_bts_virtual:
max_trx: 1
Integrate osmo-{bts,pcu}-oc2g Change-Id: I446e27039f75e63c2870d751c190a4fd76947000
2019-03-04 17:37:04 +00:00
osmo_bts_oc2g:
max_trx: 1
trx_list:
- nominal_power: 25
Initial srsLTE support 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
2020-02-11 16:45:26 +00:00
srsepc:
mcc: 901
mnc: 70
Introduce LTE Transmission Mode and RLC DRB mode params Change-Id: I38f247f266ba736cdbb6f36ba5673b8fd46a8d67
2020-02-27 17:02:20 +00:00
rlc_drb_mode: UM
srs{ue,enb,epc}: Disable pcap by default, allow enabling by param 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
2020-03-16 11:42:17 +00:00
enable_pcap: false
Initial srsLTE support 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
2020-02-11 16:45:26 +00:00
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-30 11:51:21 +00:00
enb:
Initial srsLTE support 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
2020-02-11 16:45:26 +00:00
mcc: 901
mnc: 70
Introduce LTE Transmission Mode and RLC DRB mode params Change-Id: I38f247f266ba736cdbb6f36ba5673b8fd46a8d67
2020-02-27 17:02:20 +00:00
transmission_mode: 1
srs_enb: add num_cells param to srsENB 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
2020-03-24 09:04:48 +00:00
num_cells: 1
srs{ue,enb,epc}: Disable pcap by default, allow enabling by param 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
2020-03-16 11:42:17 +00:00
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-30 11:51:21 +00:00
srsenb:
num_prb: 100
enable_pcap: false
amarisoftenb:
license_server_addr: 10.12.1.139
num_prb: 100
enable_pcap: false
srs{ue,enb,epc}: Disable pcap by default, allow enabling by param 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
2020-03-16 11:42:17 +00:00
srsue:
enable_pcap: false
srs_ue: add scenario for airplane mode simulation in srsUE Change-Id: I5db2ff325ce4b4236c1ceec0831dd7420d52dedb
2020-03-23 17:52:41 +00:00
airplane_t_on_ms: -1
airplane_t_off_ms: -1
defaults.conf: set num_carriers default value Change-Id: Ibe94fada0a40c499dd516408756c4ef7988ccec5
2020-03-24 20:21:16 +00:00
num_carriers: 1