Project

General

Profile

Feature #1601

VTY parameters become active when?

Added by laforge over 4 years ago. Updated 14 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/23/2016
Due date:
% Done:

100%

Spec Reference:

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

Related to OpenBSC - Bug #77: Fix/Define when VTY changes take effectClosed

History

#1 Updated by laforge about 4 years ago

  • Related to Bug #77: Fix/Define when VTY changes take effect added

#2 Updated by laforge almost 4 years ago

  • Assignee set to wirelesss
  • Priority changed from Low to Normal

#3 Updated by neels almost 4 years ago

  • Description updated (diff)

#4 Updated by wirelesss almost 4 years ago

  • Status changed from New to In Progress

#5 Updated by wirelesss almost 4 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.

In any case, VTY parameters such as :
  • network country code
  • mobile network code
  • arfcn

required an OML re-start.

#6 Updated by laforge over 3 years ago

  • Assignee deleted (wirelesss)

#7 Updated by laforge almost 3 years ago

  • Project changed from OsmoNITB to OsmoBSC

#8 Updated by laforge 4 months ago

  • Status changed from In Progress to New
  • Assignee set to Hoernchen

#9 Updated by laforge 4 months ago

#10 Updated by fixeria about 2 months ago

  • Status changed from New to In Progress
  • Assignee changed from Hoernchen to fixeria

#11 Updated by fixeria about 1 month ago

  • Assignee changed from fixeria to dexter
  • % Done changed from 10 to 90

#12 Updated by dexter 14 days 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.

#13 Updated by dexter 14 days ago

  • % Done changed from 90 to 100

#14 Updated by laforge 14 days ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)