Bug #2761
closedosmo-gsm-tester: add test case: Test 2nd trx is correctly used
100%
Description
We may need to add a "supported_trx" config in resources.conf to specify how many TRX can a given BTS support. This way we can use scenarios to filter for a BTS which supports that number of TRX (but we cannot match for <=, need to think more about it). Alternatively, we can use one of the BTS that we now supports it, like ":octphy".
To test that the 2nd trx is used correctly, we can use an already existing BSC/BTS VTY cmd called "channel allocator" which can have parameters "ascend" or "descend".
One of those options changes the algo used to allocate channels to start from the latest one available, ie. last timeslot in the 2nd TRX.
We can use that and place a voice call and make sure somehow that the 2nd TRX is being used (checking the log file?).
Related issues
Updated by pespin over 6 years ago
- Related to Feature #2760: osmo-gsm-tester: Add support for several (osmo-)trx to OsmoBtsTrx added
Updated by laforge over 6 years ago
On Fri, Dec 15, 2017 at 12:35:49PM +0000, pespin [REDMINE] wrote:
We can use that and place a voice call and make sure somehow that the
2nd TRX is being used (checking the log file?).
The VTY would also show it, but that's of course also not very elegant.
Updated by pespin over 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
Following patches have been submitted to test multiTRX with nanoBTS.
https://gerrit.osmocom.org/#/c/osmo-gsm-tester/+/10582 Add channel_allocator cfg attr to bts resources
remote: https://gerrit.osmocom.org/#/c/osmo-gsm-tester/+/10583 Add testsuite + scenarios to test nanoBTS multiTRX
Tests are passing but looking at the logs it seems only channels from first TRX are available when looking for a channel.
Updated by pespin over 5 years ago
- Status changed from In Progress to Feedback
- Assignee changed from pespin to dexter
Assigning to dexter since he was assigned a related ticket to fix second TRX not being used during channel allocation time when using a nanobts with MultiTRX.
Once it has been fixed and we see multitrx tests in osmo-gsm-tester using the second TRX, we can close this ticket.
Updated by laforge over 5 years ago
- Related to Bug #3560: nanoBTS multiTRX tests in osmo-gsm-tester Prod setup failing added
Updated by pespin over 5 years ago
- Status changed from Feedback to Resolved
- % Done changed from 50 to 100
Closing, as we there's already a test checking multitrx support for nanoBTS and B200 with multi_arfcn.
Tickets exists which track status of bugs found while running the tests.