Describe how to run multiple instances of osmo-nitb and osmo-bts

Change-Id: I69adeef85adda6f08b31b7d176f51e16968c1435

2 files changed, 74 insertions, 1 deletions

diff --git a/OsmoBTS/chapters/configuration.adoc b/OsmoBTS/chapters/configuration.adoc
index b91d8ac..980f835 100644
--- a/OsmoBTS/chapters/configuration.adoc
+++ b/OsmoBTS/chapters/configuration.adoc
@@ -179,3 +179,32 @@ configuration file.
 
 De-activating power-ramping can be performed by setting the max-initial value
 to the nominal power. The default max-initial value is 23 dBm.
+
+
+==== Running multiple instances
+
+It is possible to run multiple instances of `osmo-bts` on one and the same
+machine, if the phy-interface is flexible enough to distinguish between
+different phy hardware interfaces.
+
+Since usually a BTS instance runs in conjunction with a dedicated PCU instance,
+the socket path between PCU and BTS has to be distinguished between the running
+instances. It is possible to change the default socket path via VTY config:
+
+.Example: Personalize PCU socket path
+----
+bts 0
+ pcu-socket /tmp/pcu_bts_2
+----
+
+It is also necessary to separate the VTY anc CTRL interfaces of the different
+instances. The VTY, as well as the CTRL interface can be bound to a free IP
+address from the loopback range:
+
+.Example: Binding VTY and CTRL interface to a specific IP address
+----
+line vty
+ bind 127.0.0.2
+ctrl
+ bind 127.0.0.2
+----
diff --git a/OsmoNITB/chapters/running.adoc b/OsmoNITB/chapters/running.adoc
index ae2c3fc..406c41c 100644
--- a/OsmoNITB/chapters/running.adoc
+++ b/OsmoNITB/chapters/running.adoc
@@ -49,12 +49,56 @@ arguments:
 	Enable the RTP proxy code inside OsmoNITB.  This will force all
 	voice RTP data to pass through OsmoNITB, rather than going
 	directly from BTS to MGW, or BTS to BTS.
-*-m, --mncc-sock*::
+*-M, --mncc-sock-path*::
 	Enable the MNCC socket for an external MNCC handler. See
 	<<mncc>> for further information.
+*-m, --mncc-sock*::
+	Same as option -M (deprecated).
 *-C, --no-dbcounter*::
 	Disable the regular periodic synchronization of statistics
 	counters to the database.
 *-r, --rf-ctl 'RFCTL'*::
 	Offer a Unix domain socket for RF control at the path/filename
 	'RFCTL' in the file system.
+
+
+=== Multiple instances
+
+Running multiple instances of `osmo-nitb` is possible if all interfaces (VTY,
+OML) are separated using the appropriate configuration options. The IP based
+interfaces are binding to local host by default. In order to separate the
+processes, the user has to bind those services to specific but different
+IP addresses.
+
+The VTY and the control interface can be bound to IP addresses from the loopback
+address range.
+
+.Example: Binding VTY and control interface to a specific ip-address
+----
+line vty
+ bind 127.0.0.2
+ctrl
+ bind 127.0.0.2
+----
+
+The OML interface also needs to be separated by binding it to different IP
+addresses. Usually it is not possible to use addresses from the loopback
+address range here since the OML interface needs to be reachable by an external
+BTS. If only one ethernet interface is available, sub-devices with different IP
+addresses can be created.
+
+.Example: Binding OML to a specific IP address
+----
+e1_input
+ ipa bind 10.9.1.101
+----
+
+NOTE: Depending on the application, it is necessary to have different ARFCN,
+MCC, MNC and network name settings. It might also be necessary to point to
+different database and config files using command line options (see option
+-l and -c).
+
+NOTE: If an external MNCC handler is used, the user has to assign a different
+socket path to reach osmo-nitb instance using commandline option -M. If option
+-M is left out, the internal MNCC handler is used and no further configuration
+is required