Setting up the BTS

From Rhizomatica Wiki
Revision as of 16:46, 10 July 2015 by Onion (Talk | contribs) (Created page with "====== BTS SETUP ====== ==== Connect antennas: ==== Transceiving antenna needs to be dual band / receiving doesn't matter ==== On work machine ==== Create shared ethernet...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
BTS SETUP

Connect antennas:

Transceiving antenna needs to be dual band / receiving doesn't matter

On work machine

Create shared ethernet connection: set ipv4 settings to "Shared to other computers"

Get the 2 ips from the BTS:

 arp -n #shows arp table

turn on bts - will assign ip to bts

 arp-n # will now show 2 new ips, probably on eth0  (of each bts in box)

log into BTS:

 ssh root@IP #either new IP address from 2nd arp -n
 sbts2050-util  

check power status:

 sbts2050-util sbts2050-pwr-status

example:

root@NTQ0107973S:~# sbts2050-util sbts2050-pwr-status
Main Supply :(ON)  [(24.00)Vdc, 1.34 A]
Master SF   : ON   [  4.97 Vdc, 0.97 A]
Slave SF    : ON   [  4.97 Vdc, 0.91 A]
Power Amp   : ON   [ 24.75 Vdc, 0.77 A]
PA Bias: ON   [  9.00 Vdc, ---- A]

(this power amp is ON!)

turn off power amplifier

 sbts2050-util sbts2050-pwr-enable 1 1 0  #1 1 0 = master slave amplifier

For power amp to be off this should be:


root@NTQ0107973S:~# sbts2050-util sbts2050-pwr-status
Main Supply :(ON)  [(24.00)Vdc, 0.56 A]
Master SF   : ON   [  4.94 Vdc, 0.98 A]
Slave SF    : ON   [  4.97 Vdc, 0.91 A]
Power Amp   : OFF  [ 10.75 Vdc, 0.05 A]
PA Bias: OFF  [  0.00 Vdc, ---- A]  #means power amp is OFF!

sbts2050-util sbts2050-temp 

- during troubleshooting : 75C pretty high 50-60 normal

sysmobts-util :

This is the sysmoBTS utility cli thing:

 sysmobts-util trx-nr #shows which transceiver we are on (0 master, 1 slave)

Possible param names: ethaddr clk-factory temp-dig-max temp-rf-max serial-nr hours-running boot-count key model-nr model-flags trx-nr

On work machine:

Run a script to put all the sysmocom stuff on the bts:

 chmod +x setup-bts.py # makes the scripts executable
 ./setup-bts.py -H btsip setup

wait a while till finished , then do it on other bts

when both are done, ssh into each box and reboot both of them

Upon reboot, DHCP issued IP will be replaced by a static ip for each: 172.16.0.11 and 172.16.0.12

The BTS led should now show only if BSC is connected

Connect to web interface on the BSC:

Get the ip from Oaxaca (10.23.1.0/24) table at new_network_scheme

eg. for Alotepec: 10.23.1.16/rai

admin:admin1

Copy keys to BTS from BSC

from inside BSC: ssh-copy-id root@172.16.0.11


NOW TEST IT!

☎☎ make some calls! ☎☎☎


Potential troubleshooting

    • Crashing network script:**

Problem: Sometimes setup-bts.py has trouble with updating packages.

ssh into the BTS and run package scripts by hand:

opkg update opkg upgrade

go back and run the script again.

    • Quick and dirty fix**

That is caused by some SSL/HTTPS misconfiguration. Quick and dirty way to fix it:

  1. sed -i -e 's/https/http/g' /etc/opkg/*.conf
    • Malconfigured IP Address (still looking for IP via DHCP)**

Ciaby's fix from the July Cajonos Fracoso:

How to look for DHCP and/or ARP packets: tcpdump -v -n -i eth1 port 67 or port 68 or arp

I configured the 172.16.0.0/24 network in /etc/dhcp/dhcpd.conf, rebooted the secondary BTS, it got 172.16.0.100 assigned. Ssh into it, configure /etc/network/interfaces manually, adding:

gateway 172.16.0.1

as the last line. also:

echo "nameserver 8.8.8.8" > /etc/resolv.conf

Rebooted it, then copied setup-bts.py on the BSC and run it against the secondary BTS (who was now on 172.16.0.2).