blob: 60c393619bf14d58c7f7abd91b94032034a86ca9 [file] [log] [blame]
Pau Espin Pedrol7e0b2dd2020-03-10 11:46:39 +01001== Hardware Choice and Configuration
2
3=== SysmoBTS
4
5To use the SysmoBTS in the osmo-gsm-tester, the following systemd services must
6be disabled:
7
8----
9systemctl mask osmo-nitb osmo-bts-sysmo osmo-pcu sysmobts-mgr
10----
11
12This stops the stock setup keeping the BTS in operation and hence allows the
13osmo-gsm-tester to install and launch its own versions of the SysmoBTS
14software.
15
16==== IP Address
17
18To ensure that the SysmoBTS is always reachable at a fixed known IP address,
19configure the eth0 to use a static IP address:
20
21Adjust '/etc/network/interfaces' and replace the line
22
23----
24iface eth0 inet dhcp
25----
26
27with
28
29----
30iface eth0 inet static
31 address 10.42.42.114
32 netmask 255.255.255.0
33 gateway 10.42.42.1
34----
35
36You may set the name server in '/etc/resolve.conf' (most likely to the IP of
37the gateway), but this is not really needed by the osmo-gsm-tester.
38
39==== Allow Core Files
40
41In case a binary run for the test crashes, a core file of the crash should be
42written. This requires a limits rule. Append a line to /etc/limits like:
43
44----
45ssh root@10.42.42.114
46echo "* C16384" >> /etc/limits
47----
48
49==== Reboot
50
51Reboot the BTS and make sure that the IP address for eth0 is now indeed
5210.42.42.114, and that no osmo* programs are running.
53
54----
55ip a
56ps w | grep osmo
57----
58
59==== SSH Access
60
61Make sure that the jenkins user on the main unit is able to login on the
62sysmoBTS, possibly erasing outdated host keys after a new rootfs was loaded:
63
64On the main unit, for example do:
65
66----
67su - jenkins
68ssh root@10.42.42.114
69----
70
71Fix any problems until you get a login on the sysmoBTS.
72
73
74[[hardware_modems]]
75=== Modems
76
77TODO: describe modem choices and how to run ofono
78
79[[hardware_trx]]
80=== osmo-bts-trx
81
82TODO: describe B200 family