Difference between revisions of "Setting up the BSC"

Latest revision as of 20:58, 14 January 2017

Other languages:

English • ‎español

These instruction are specific to our installations at rhizomatica using our servers and VPN setups. Some cleverness amay be required to fill in some of the holes...

# Site specific info
rhizo::bts1_ip_address:  "172.16.0.11"
rhizo::site_name:   "Tabaa"
rhizo::postcode:    "68847" 	# we use the postal code for the dialing prefix
rhizo::pbxcode:"1"
rhizo::network_name:"TabaaGSM"
rhizo::arfcn_A:"239" # channel
rhizo::arfcn_B:"243" #channel 
rhizo::auth_policy: "closed"
rhizo::vpn_ip_address:   "10.23.1.15" #this is just part of our own VPN
rhizo::wan_ip_address:   "192.168.0.0" # ip from isp add this later - used for VOIP

#Emergency call contact
rhizo::emergency_contact:"12345" 

# VoIP provider info
rhizo::voip_provider_name:    "provider"
rhizo::voip_username:    "1234567890"
rhizo::voip_fromuser:    "1234567890"
rhizo::voip_password:    "1234"
rhizo::voip_proxy:  "169.132.196.11"
rhizo::voip_did:    "12345678901"
rhizo::voip_cli:    "12345678901"

Back on BSC

 puppet agent --test

 q:How does some stranger get puppet setup?
 a: set up the puppet master on bsc and set up the agent on 'localhost'

  cd /root
  tar -zxf /home/rhizomatica/git_key.tar.gz 

  ./git_rccn.sh #to pull from git

  puppet agent --test (again to generate config python file: /var/rhizomatica/rccn/config_values.py )

  python /var/rhizomatica/rccn/install.py


  
  nano /etc/default/puppet
  
  #change to  START=yes #make puppet auto start
  
  service puppet start

as root:

  update-rc.d osmocom-nitb disable #disable osmocom standard script because we do it different

Reboot the BSC!

Network config on the BSC:

 nano /etc/network/interfaces

Leave the primary interface as DHCP

add:

 
#LAN2 BTS interface
auto eth1
iface eth1 inet static
 address 172.16.0.1 
 netmask 255.255.255.0 

#LAN4 local admin PC
auto eth3
 iface eth3 inet static
 address 192.168.100.1 
 netmask 255.255.255.0

 ifup eth1
 ifup eth3

Language Setup

If Spanish lang pages are in english, spanish PHP support can be generated via:

 locale-gen es

BSC LAN PORTS

LAN 1	LAN 2	LAN 3	LAN 4
Internet	BTS	available	Admin compu
Assigned by DHCP	172.16.0.11 and 172.16.0.12	available	192.168.100.1

Difference between revisions of "Setting up the BSC"

Latest revision as of 20:58, 14 January 2017

Contents

Hardware

BIOS Changes:

Prepare Ubuntu for install

Boot it up!

INSTALL PUPPET

Back on BSC:

on work machine:

Back on BSC

Network config on the BSC:

Language Setup

BSC LAN PORTS

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools

@@ Line 1: / Line 1: @@
+<languages/>
+<translate>
+<!--T:1-->
 These instruction are specific to our installations at rhizomatica using our servers and VPN setups. Some cleverness amay be required to fill in some of the holes...
-==== Hardware ====
+==== Hardware ==== <!--T:2-->
+<!--T:3-->
 In our installations, we use this: http://www.jetwaycomputer.com/JBC373F38.html
+<!--T:4-->
 We like these because they are fanless, tough, no moving parts and have a 4 ethernet ports.
-==== BIOS Changes: ====
+==== BIOS Changes: ==== <!--T:5-->
+<!--T:6-->
 First we need to make some changes in the BIOS:
+<!--T:7-->
 Bios Feature Integrated Peripheral > onboard SATA fnct > AHCI
+<!--T:8-->
 Power Management >
+<!--T:9-->
 ERP Function > Disabled (power saving)
+<!--T:10-->
 PWR Status after Power failure > Always On
+<!--T:11-->
 PC Health Status > Shutdown Temp 75C
-==== Prepare Ubuntu for install ====
+==== Prepare Ubuntu for install ==== <!--T:12-->
+<!--T:13-->
 Download Ubuntu 12.04 server & put it on a USB drive
+<!--T:14-->
 replace /preseed/ubuntu.seed on USB drive with preseed file from git: https://github.com/Rhizomatica/puppet/blob/master/rhizomatica.seed
+<!--T:15-->
 install Ubuntu on BSC with US english keyboard and Mexico City timezone
-==== Boot it up! ====
+==== Boot it up! ==== <!--T:16-->
+<!--T:17-->
 connect to LAN1
+<!--T:18-->
 login: rhizomatica rhizomatica   (has this changed?)
+<!--T:19-->
 <pre>  here we edited out a bunch of rhizo specific networking and VPN info</pre>
-==== INSTALL PUPPETT ====
-Maybe start by taking a look at [[https://docs.puppetlabs.com/guides/install_puppet/install_debian_ubuntu.html]] or [[https://apt.puppetlabs.com/]]
+==== INSTALL PUPPET ==== <!--T:20-->
-   wget https://apt.puppetlabs.com/puppetlabs-release-precise.deb #just the repo info
+<!--T:21-->
+Maybe start by taking a look at [[https://docs.puppetlabs.com/guides/install_puppet/install_debian_ubuntu.html|https://docs.puppetlabs.com/guides/install_puppet/install_debian_ubuntu.html]] or [[https://apt.puppetlabs.com/|https://apt.puppetlabs.com/]]
+   <!--T:22-->
+wget https://apt.puppetlabs.com/puppetlabs-release-precise.deb #just the repo info
    dpkg -i puppet.deb file # just install repos
@@ Line 50: / Line 74: @@
    apt-get install puppet
-   puppet agent --test # run to gen key, but server won't accept new key
+   See the README at https://github.com/Rhizomatica/puppet
-==== key signing with puppet ====
-possibly not necessary now we have it on git?
-==== Back on BSC: ====
+==== Back on BSC: ==== <!--T:23-->
-   puppet agent --test #again - cannot find items..
+   <!--T:24-->
+puppet agent --test
-==== on work machine: ====
+==== on work machine: ==== <!--T:25-->
+<!--T:26-->
 We use a git repo of .yaml files to set up our various BSCs. How would this get set up by someone trying to do it themselves?
+<!--T:27-->
 example file:
+<!--T:28-->
 <pre>
 # Site specific info
@@ Line 81: / Line 106: @@
 rhizo::wan_ip_address:   "192.168.0.0" # ip from isp add this later - used for VOIP
+<!--T:29-->
 #Emergency call contact
 rhizo::emergency_contact:"12345"
+<!--T:30-->
 # VoIP provider info
 rhizo::voip_provider_name:    "provider"
@@ Line 94: / Line 121: @@
 </pre>
-==== Back on BSC ====
-  puppet agent --test
+==== Back on BSC ==== <!--T:31-->
-   q:How does some stranger get puppet setup?
+   <!--T:32-->
+puppet agent --test
+  <!--T:33-->
+q:How does some stranger get puppet setup?
    a: set up the puppet master on bsc and set up the agent on 'localhost'
+<!--T:34-->
 <pre>
    cd /root
    tar -zxf /home/rhizomatica/git_key.tar.gz
-   ./git_rccn.sh #to pull from git
+   <!--T:35-->
+./git_rccn.sh #to pull from git
-   puppet agent --test (again to generate config python file: /var/rhizomatica/rccn/config_values.py )
+   <!--T:36-->
+puppet agent --test (again to generate config python file: /var/rhizomatica/rccn/config_values.py )
-   python install.py
+   <!--T:37-->
+python /var/rhizomatica/rccn/install.py
 </pre>
+<!--T:38-->
 <pre>
-  psql -f /var/rhizomatica/db/migration/011_location.sql
    nano /etc/default/puppet
@@ Line 123: / Line 158: @@
   </pre>
+<!--T:39-->
 as root:
 <pre>  update-rc.d osmocom-nitb disable #disable osmocom standard script because we do it different</pre>
+<!--T:40-->
 Reboot the BSC!
-==== Network shit on the BSC: ====
-  nano /etc/network/interfaces
+==== Network config on the BSC: ==== <!--T:41-->
+  <!--T:42-->
+nano /etc/network/interfaces
+<!--T:43-->
 Leave the primary interface as DHCP
+<!--T:44-->
 add:
 <pre>
@@ Line 143: / Line 184: @@
   netmask 255.255.255.0
+<!--T:45-->
 #LAN4 local admin PC
 auto eth3
@@ Line 150: / Line 192: @@
 </pre>
-   ifup eth1
+   <!--T:46-->
+ifup eth1
    ifup eth3
-==== Language Setup ====
+==== Language Setup ==== <!--T:47-->
+<!--T:48-->
 If Spanish lang pages are in english, spanish PHP support can be generated via:
-   locale-gen es
+   <!--T:49-->
+locale-gen es
-== BSC LAN PORTS ==
+== BSC LAN PORTS == <!--T:50-->
+<!--T:51-->
 {| class="wikitable"
 |-
@@ Line 179: / Line 227: @@
 | 192.168.100.1
 |}
+</translate>