summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNeels Hofmeyr <neels@hofmeyr.de>2018-10-31 02:18:39 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2018-10-31 02:19:31 +0100
commit4f06dd168c5a84858ff57b33c7446a408436a01c (patch)
treeedf010119863f58987718e615f832f61db7cb80f
parent5df5dcc2970b04c105c0e4e94fa8aecb71941d4a (diff)
bsc: handover: clarify default of all-cells-are-neighbors
-rw-r--r--OsmoBSC/chapters/handover.adoc16
1 files changed, 16 insertions, 0 deletions
diff --git a/OsmoBSC/chapters/handover.adoc b/OsmoBSC/chapters/handover.adoc
index 3c9204e..833ee19 100644
--- a/OsmoBSC/chapters/handover.adoc
+++ b/OsmoBSC/chapters/handover.adoc
@@ -166,6 +166,22 @@ new `neighbor` configuration described below.
| ✓ | ✓ | neighbor cgi 001 01 200 3 arfcn 123 bsic 1
|====
+==== Default: All Local Cells are Neighbors
+
+For historical reasons, the default behavior of OsmoBSC is to add all local-BSS cells as neighbors. To
+maintain a backwards compatible configuration file format, this is still the case: as soon as no explicit
+neighbor cell is configured with a `neighbor` command (either none was configured, or all configured
+neighbors have been removed again), a cell automatically lists all of the local-BSS cells as neighbors.
+These are implicit mappings in terms of the legacy neighbor configuration scheme, and re-using ARFCN+BSIC
+combinations within a BSS will not work well this way.
+
+As soon as the first explicit neighbor relation is added to a cell, the legacy behavior is switched off,
+and only explicit neighbors are in effect.
+
+NOTE: If a cell is required to not have any neighbors, it is recommended to rather switch off handover
+for that cell with `handover 0`. An alternative solution is to set `neighbor-list mode manual` and not
+configure any `neighbor-list` entries.
+
==== Local-BSS Neighbors
Local neighbors can be configured by just the local BTS number, or by LAC+CI,