This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
dexter gerrit-no-reply at lists.osmocom.orgReview at https://gerrit.osmocom.org/1497 Describe how to run multiple instances of osmo-nitb and osmo-bts Change-Id: I69adeef85adda6f08b31b7d176f51e16968c1435 --- M OsmoBTS/chapters/configuration.adoc M OsmoNITB/chapters/running.adoc 2 files changed, 62 insertions(+), 0 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/97/1497/1 diff --git a/OsmoBTS/chapters/configuration.adoc b/OsmoBTS/chapters/configuration.adoc index b91d8ac..86d8457 100644 --- a/OsmoBTS/chapters/configuration.adoc +++ b/OsmoBTS/chapters/configuration.adoc @@ -179,3 +179,29 @@ 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 comes included with its individual PCU instance, +the socket-path between PCU and BTS has to be individualized as well. 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 interfaces of the different instances. +The VTY can be bound to a free ip-address from the loopback range: + +.Example: Binding VTY to a specific ip-address +---- +line vty + bind 127.0.0.2 +---- diff --git a/OsmoNITB/chapters/running.adoc b/OsmoNITB/chapters/running.adoc index ae2c3fc..7b903f6 100644 --- a/OsmoNITB/chapters/running.adoc +++ b/OsmoNITB/chapters/running.adoc @@ -58,3 +58,39 @@ *-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 bind 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 be separated by binding it to different ip +addresses. In general it is not possible to use addresses from the loopback +address range here since the address we binding on has to be reachable (from +outside) to the bts. If only one ethernet interface is available, subdevices +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. It might also be necessary to point to different +database and config files using command line options (see option -l and -c). -- To view, visit https://gerrit.osmocom.org/1497 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I69adeef85adda6f08b31b7d176f51e16968c1435 Gerrit-PatchSet: 1 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: dexter <pmaier at sysmocom.de>