path: root/OsmoBSC
diff options
authorNeels Hofmeyr <neels@hofmeyr.de>2018-10-31 02:27:28 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2018-10-31 02:28:46 +0100
commit8a7e602f183fe5a3fbe70e2d6f7434d2f4a5abae (patch)
treed600cbde7480d0bb6ab69ff6ddff7c88339472fb /OsmoBSC
parent4f06dd168c5a84858ff57b33c7446a408436a01c (diff)
bsc: handover: mention the need to resend SI for telnet neighbor cfgneels/inter_bsc_ho
Diffstat (limited to 'OsmoBSC')
1 files changed, 9 insertions, 0 deletions
diff --git a/OsmoBSC/chapters/handover.adoc b/OsmoBSC/chapters/handover.adoc
index 833ee19..b05ad00 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