diff options
authorNeels Hofmeyr <neels@hofmeyr.de>2018-10-31 02:27:28 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2018-11-27 17:12:40 +0100
commitaa4a3e7259ad8c1421f6e1b1b0bfbd70d66d9bc9 (patch)
parent48758488533d93017c0a2a1c93122e5d95b09734 (diff)
bsc: handover: mention the need to resend SI for telnet neighbor cfg
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/manuals/chapters/handover.adoc b/doc/manuals/chapters/handover.adoc
index b76370100..297eafc1f 100644
--- a/doc/manuals/chapters/handover.adoc
+++ b/doc/manuals/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