Project

General

Profile

OsmoNITB Migration Guide » History » Version 8

neels, 10/27/2017 02:31 AM

1 3 neels
{{>toc}}
2 3 neels
3 1 neels
h1. OsmoNITB Migration Guide
4 1 neels
5 2 neels
Historically, Osmocom offered the [[OsmoNITB:]] "Network-In-The-Box" as an actual single program. It was a useful simplification at the time, but in 2017, Osmocom have decided to split OsmoNITB into programs more closely resembling traditional network architecture. It is recommended to use the new separate components instead of the OsmoNITB, since active development focus has moved there.
6 2 neels
7 2 neels
Creating a new Network In The Box from scratch is described at [[Osmocom Network In The Box]], please refer to that page to complement the descriptions found here.
8 2 neels
9 2 neels
This page aims at describing the steps necessary to move from a working operation of osmo-nitb to the new split components.
10 2 neels
11 2 neels
h1. Subscriber Database
12 2 neels
13 4 neels
With OsmoHLR comes *@osmo-hlr-db-tool@*, which is capable of importing the most important subscriber data from a database that was used with OsmoNITB.
14 4 neels
15 5 neels
In a standard installation, the osmo-nitb database should be found at @/var/lib/osmocom/hlr.sqlite3@, and the osmo-hlr database is expected at @/var/lib/osmocom/hlr.db@. Hence the migration command becomes:
16 5 neels
17 1 neels
<pre>
18 8 neels
osmo-hlr-db-tool --database /var/lib/osmocom/hlr.db --import-nitb-db /var/lib/osmocom/hlr.sqlite3
19 4 neels
</pre>
20 4 neels
21 8 neels
If no @--database@ is passed, @./hlr.db@ is assumed.
22 1 neels
If the target @hlr.db@ does not exist yet, it is created.
23 8 neels
If no @--import-nitb-db@ is passed, a @hlr.db@ without any subscriber data is created.
24 8 neels
25 8 neels
You may repeat / combine imports to the same @hlr.db@; any subscribers that already exist will be skipped with an error message. It is possible to do an import while osmo-hlr is actively using the database, but that is not recommended.
26 8 neels
27 8 neels
Take care that the resulting hlr.db has the proper read and write permissions by the user that will run OsmoHLR. Probably, the same ownership and permissions that the previous OsmoNITB database had is the correct choice.
28 4 neels
29 1 neels
Note that not all information is copied to the hlr.db, just IMSI and 2G auth tokens.
30 5 neels
31 5 neels
To avoid future confusion, it may be desirable to remove the legacy hlr.sqlite3 from the system (i.e. backup to somewhere else), or rename it to something like @osmo-nitb.db@, so that it is not mistaken for the OsmoHLR database.
32 2 neels
33 2 neels
h1. Configuration Files
34 2 neels
35 6 neels
Most of the current OsmoNITB config options still exist, but are now moved to OsmoMSC or OsmoBSC. Few are required in both.
36 6 neels
37 2 neels
TODO
38 2 neels
39 2 neels
h1. Service Files
40 2 neels
41 2 neels
TODO