From 8a7e602f183fe5a3fbe70e2d6f7434d2f4a5abae Mon Sep 17 00:00:00 2001
From: Neels Hofmeyr <neels@hofmeyr.de>
Date: Wed, 31 Oct 2018 02:27:28 +0100
Subject: bsc: handover: mention the need to resend SI for telnet neighbor cfg

Change-Id: I305ef558b75697015e2532aa7c135f7995662e0d
---
 OsmoBSC/chapters/handover.adoc | 9 +++++++++
 1 file changed, 9 insertions(+)

(limited to 'OsmoBSC/chapters/handover.adoc')

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
-- 
cgit v1.2.3

