summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNeels Hofmeyr <neels@hofmeyr.de>2018-10-31 02:27:28 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2018-11-01 18:07:11 +0100
commitd3c34d6a9d33ea3aeb7e199b1eaf6d7a20cb85d6 (patch)
treebdff811f8a3f2c9f3ebf28001567d811d1d2e20b
parent61ce5449265f4dd1209c90836a4b1e9a66219ba1 (diff)
bsc: handover: mention the need to resend SI for telnet neighbor cfg
-rw-r--r--OsmoBSC/chapters/handover.adoc9
1 files changed, 9 insertions, 0 deletions
diff --git a/OsmoBSC/chapters/handover.adoc b/OsmoBSC/chapters/handover.adoc
index b763701..297eafc 100644
--- a/OsmoBSC/chapters/handover.adoc
+++ b/OsmoBSC/chapters/handover.adoc
@@ -307,6 +307,15 @@ list items. Hence, to be able to send several alternative remote neighbors to
the MSC, the configured cell identifiers must be of the same type. If in doubt,
use the full CGI identifier everywhere.
+==== Reconfiguring Neighbors in a Running OsmoBSC
+
+When modifying a cell's neighbor configuration in a telnet VTY session while a cell is already active,
+the neighbor configuration will merely be cached in the BSC's local config. To take actual effect, it is
+necessary to
+
+- either, re-connect the cell to the BSC (e.g. via `drop bts connection <0-255> oml`)
+- or, re-send the System Information using `bts <0-255> resend-system-information`.
+
=== Configuring Handover Decisions
For a long time, OsmoBSC has supported handover based on reception level