Feature #1601
closedVTY parameters become active when?
100%
Description
Document which VTY parameters become active immediately, and which require an OML re-start of the BTS.
Maybe we can even improve this to a point where we can apply OML changes to a BTS without a full re-connect, so that we don't lose all current users.
Alternatively introduce a way where we can schedule a BTS re-start as soon as all active transactions are finished.
It might make sense if the information on 'when a change becomes active' was somehow explicit when using the VTY.
Related issues
Updated by laforge about 7 years ago
- Related to Bug #77: Fix/Define when VTY changes take effect added
Updated by laforge about 7 years ago
- Assignee set to wirelesss
- Priority changed from Low to Normal
Updated by wirelesss almost 7 years ago
- % Done changed from 0 to 10
Reading
http://ftp.osmocom.org/docs/latest/osmobts-abis.pdf
http://ftp.osmocom.org/docs/latest/osmonitb-vty-reference.pdf
and 3GPP TS 12.21.
- network country code
- mobile network code
- arfcn
required an OML re-start.
Updated by laforge over 3 years ago
- Status changed from In Progress to New
- Assignee set to Hoernchen
Updated by fixeria over 3 years ago
- Status changed from New to In Progress
- Assignee changed from Hoernchen to fixeria
Updated by fixeria about 3 years ago
- Assignee changed from fixeria to dexter
- % Done changed from 10 to 90
Please see: https://gerrit.osmocom.org/c/osmo-bsc/+/19670.
Updated by dexter about 3 years ago
Status update:
All VTY commands in the osmocom applications that are related to the ran (osmo-bts, osmo-trx, osmo-pcu, osmo-bsc, osmo-mgw, libosmo-sccp, libosmo-abis) are reviewed and tagged with appropriate attributes. The attributes tell the user (and the scripts that generate the VTY reference manuals) when a configuration change takes effect. Also the work on the infrastructure (vty commands to display the attributes / xml generation) is done.
Updated by laforge about 3 years ago
- Status changed from In Progress to Resolved
