path: root/tests
diff options
authorNeels Hofmeyr <neels@hofmeyr.de>2021-07-08 06:20:46 +0200
committerlaforge <laforge@osmocom.org>2021-07-16 16:04:18 +0000
commitae0b737c62e4f8953dc64b67515fff5f2b330fea (patch)
tree8b34928a8b443fddede661758a19d9359d07cc6a /tests
parent71b4f94601cbd1aa97729be2d789d21d20aea706 (diff)
separate 'interference-meas level-bounds' cfg and used
The VTY defun already indicates BSC_VTY_ATTR_RESTART_ABIS_OML_LINK correctly, but so far we would immediately start using the new values internally, and wrongly interpret interference levels. Fix that. Have bts->interf_meas_params twice: interf_meas_params_cfg for the VTY configured values, and interf_meas_params_used for the values that the BTS actually knows about, after they were sent via OML. In a running BSC, when changing the interference level boundaries on the telnet VTY, the BTS is not immediately told about the change. That would require a BTS restart. Hence store the cfg values separately in interf_meas_params_cfg. For comparing/printing interference levels in a running BTS, only employ the values that were actually sent via OML and placed in interf_meas_params_used. Related: SYS#5313 Change-Id: Iad8cf4151ff7f86dc0549158ed5d91d788d40b1f
Diffstat (limited to 'tests')
1 files changed, 3 insertions, 0 deletions
diff --git a/tests/handover/handover_test.c b/tests/handover/handover_test.c
index 331726af2..315fc1043 100644
--- a/tests/handover/handover_test.c
+++ b/tests/handover/handover_test.c
@@ -1118,6 +1118,9 @@ DEFUN(res_ind, res_ind_cmd,
uint8_t *res_info_len;
+ /* In this test suite, always act as if the interf_meas_params_cfg were already sent to the BTS via OML */
+ bts->interf_meas_params_used = bts->interf_meas_params_cfg;
argv += 2;
argc -= 2;